Backups & updates

Back up three separate thingsCopy Anchor Link

1. txData: admin accounts, panel configuration, player database, and any logs you need to retain.
2. Server data: server.cfg, included config files, resources, and custom assets.
3. Framework databases: a consistent database export for any resource using MySQL/MariaDB or another external store.

The master account’s player database download exports playersDB.json. It is useful, but it does not include the whole txData directory, your resources, or the framework database.

Make the snapshot consistentCopy Anchor Link

For a simple file-copy backup, stop the processes that write those files or use a storage snapshot mechanism that gives a consistent view. For external databases, use their supported backup tooling. Keep backups outside the running server’s writable data directory.

Protect backups like live server data: they can contain credentials, staff accounts, moderation history, and private player identifiers.

Before updating artifactsCopy Anchor Link

• Record the working artifact and txAdmin version.
• Save a recoverable backup and check that you can read it.
• Read upstream release notes and framework compatibility requirements.
• Keep your server data and txData separate from replaceable artifact files.
• Test on an isolated server when the change is significant.

txAdmin ships with FXServer, so normal users update it through server artifacts rather than installing an unrelated txAdmin resource.

Verify afterwardCopy Anchor Link

Watch a complete startup, open the panel, sign in, connect a game client, and check critical resources and database-backed features. If a rollback is needed, consider both binaries and any data/configuration migration; do not assume older code can read all newer files.

Test a restoreCopy Anchor Link

Restore into a separate folder and database with different ports. Check admin access and important player records without exposing a second public production server. A backup is only useful when the recovery path works.

---

Source: txAdmin upstream documentation.