Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →A reliable FiveM backup is more than a copy of your resources folder. Stop or quiesce the server, copy the complete server data directory and txAdmin’s txData directory, export every external MySQL or MariaDB database used by your framework, and keep a protected copy on another disk or host. Then prove that the files and database can be restored on an isolated instance.
This guide shows what to save, where txData is found, how txAdmin’s own backup differs from a full server backup, and how to rebuild a server after disk failure.
As an Amazon Associate I earn from qualifying purchases.
What a complete FiveM backup must contain
FiveM can start with an artifact and a configuration file, but a usable production server depends on much more: resources, scripts, streamed assets, permissions, txAdmin state, and persistent player data. Back up each layer as a separate, identifiable artifact so you can restore only what is needed or rebuild the entire host.
| Backup target | What it contains | Why it matters | How to capture it |
|---|---|---|---|
| Complete server data directory | Resources, scripts, stream assets, server.cfg, permissions, and deployment files |
Recreates the running FiveM configuration and content | Copy the entire directory, not selected resources |
txAdmin txData |
txAdmin logs, configurations, and data | Preserves txAdmin profiles, settings, and operational history | Copy the complete directory while the server is stopped or quiesced |
| External framework database | Framework-owned player, character, inventory, economy, or other persistent records | Restores data that is not stored in files | Use the native dump utility for the MySQL or MariaDB engine and provider |
| Secrets and deployment metadata | License values, database credentials, API tokens, keys, host details, and version notes | Allows a rebuild without exposing credentials in public files | Store an encrypted, access-controlled record separately from ordinary archives |
The minimum file scope is the server data directory plus txData. If a framework or resource uses an external database, that database is a separate backup target. A txAdmin player-database backup does not automatically include resources, configuration files, or an external framework database.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Before copying anything: make the server consistent
A file copy taken while resources are writing can contain a mixture of old and new state. Database tables may be changing at the same time, producing a backup whose files and database do not describe the same moment. The safest procedure is a short maintenance window.
- Announce maintenance to players and staff. Note the planned start time and the backup identifier you will use.
- Stop the FiveM server cleanly through your normal txAdmin or service-control workflow. If a full stop is impossible, quiesce writes: prevent new connections, stop scheduled jobs, and confirm that resources are no longer modifying files or database records.
- Wait for the process to exit and verify that no FXServer process still has the data directory open for writing.
- Record the artifact version, framework and resource versions, operating system, database engine, and the exact time at which the backup begins.
Do not treat a running server’s live directory as a guaranteed snapshot. A clean stop is particularly important for SQLite-style files, logs, resource-generated JSON, and any resource that writes state during shutdown.
Find the server data directory and txData
Server data directory
The server data directory is the folder selected when the existing server is configured in txAdmin. It normally contains server.cfg and the resources directory, along with permissions, scripts, stream files, and other deployment material. In txAdmin’s setup flow for an existing server, select the existing data folder and configuration file; txAdmin documentation explicitly advises: “Back up that folder and your txData before making changes.”
Do not assume that the folder containing the FXServer binary is the same as the data directory. Confirm the path shown in your txAdmin profile or service startup configuration, then copy the complete folder tree.
txData on Windows and Linux
txData is txAdmin’s data directory. The txAdmin environment reference describes it as the location containing “the txAdmin logs, configs, and data.” Its location is controlled by the TXHOST_DATA_PATH environment variable.
- On Windows, the default is a path under the parent directory of the FXServer artifact.
- On Linux, the default is a path under the directory that contains
run.sh. - Managed hosts may set a different path. Inspect the provider’s startup configuration or ask the host where
TXHOST_DATA_PATHresolves instead of relying on a local default.
Copy the whole txData directory, including subdirectories and files that look like logs or temporary configuration. Omitting a nested profile can leave txAdmin unable to reproduce the original server setup.
Free tools Windows power users keep installed
One-click scans. No signup required.
Remember that txAdmin is already part of FXServer
txAdmin is included with FXServer; Cfx.re documentation says it comes preinstalled and does not normally need to be downloaded as a separate FiveM resource. Backing up the server therefore means preserving the files used by FXServer and the separate txAdmin data directory, not searching for a resource named txAdmin inside resources.
Step-by-step: create a full backup
1. Create a dated backup workspace
Use a directory whose name includes the server identity and a timestamp in a sortable format, such as the UTC date and time. Keep the server data copy, txData copy, database dump, manifest, and encrypted secret record together in that backup set. Do not place credentials in the folder name or in a public repository.
2. Copy the complete server data directory
Copy every file and subdirectory from the confirmed server data path into the dated workspace. Preserve filenames, directory structure, permissions where the operating system supports them, and symbolic links only if your deployment intentionally uses them. A selective copy of only resources can omit server.cfg, ACLs, startup settings, or scripts stored elsewhere.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
After the copy, compare the source and destination file counts and total sizes. A tool that can generate checksums gives you a stronger integrity check; save the checksum manifest beside the backup so a later restore can detect corruption.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall3. Copy txData separately
Copy the complete directory resolved from TXHOST_DATA_PATH. Label it clearly as txAdmin data rather than merging it invisibly into the server data copy. Keeping the two trees distinct makes it possible to restore a damaged txAdmin profile without overwriting resources, and it mirrors the boundary documented by txAdmin.
4. Export the external database
Identify every resource and framework that connects to MySQL or MariaDB. The connection details may be in server.cfg, an environment file, a secret manager, or a provider dashboard. Export the relevant database with the native dump utility supplied for the engine and hosting provider. The exact command, options, authentication method, character-set handling, and consistency flags depend on that engine and provider, so use their current documentation rather than copying an example intended for a different deployment.
Run the export during the same maintenance window as the file copy. Record the database name, engine and version, dump completion time, and whether the dump is compressed or encrypted. Never paste the password or connection string into a support request or a public tutorial.
5. Preserve deployment metadata and secrets securely
Create a separate encrypted record containing the license and configuration values required to start the server, database endpoint and account, API tokens, firewall or service details, artifact version, framework version, and any host-specific path overrides. Keep this record access-controlled and separate from an archive that might be uploaded to a general file-sharing service.
Recommended Free Tools
The ordinary backup should contain the configuration structure needed for a rebuild, but secrets should be redacted from copies shared with staff or support. A backup that is publicly readable can expose server keys, database credentials, identifiers, and tokens even when the server itself is offline.
6. Make a second copy off the original host
A backup stored on the same disk is not protection against disk failure. Copy the completed set to a different physical disk or host. An external USB hard drive or SSD is a straightforward local option. Encrypted cloud or object storage provides off-site durability when configured with restricted access and encryption.
Verify that the second copy finished before declaring the job complete. Keep the original local recovery copy until the off-host copy has been checked; otherwise a transfer error can leave you with no usable generation.
7. Write a manifest and retention note
For each backup generation, record:
- Server name and environment.
- UTC start and completion times.
- FXServer artifact, framework, and significant resource versions.
- Paths copied, database names exported, and archive or checksum identifiers.
- Where the local and off-host copies are stored.
- Who can decrypt or restore the secrets.
- Whether a restore test has passed and when the next test is due.
Keep more than one generation. If a resource writes corrupted data or an administrator deletes files, the newest backup may faithfully preserve the problem. A practical retention policy keeps recent generations for quick rollback and older generations for recovery from delayed corruption.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Does txAdmin back up the database?
txAdmin provides a backup tool for its self-contained player database. That feature is useful for the data txAdmin itself owns, but it is not a universal FiveM backup. It does not replace copying the server data directory and txData, and it does not automatically export a MySQL or MariaDB database used by a framework installed through a recipe.
Recipes can download resources, write files, connect to databases, and execute queries. Read a recipe before running it, and back up production files and databases first. A recipe change can alter configuration or schema even when txAdmin’s own player-database backup is healthy.
During txAdmin registration, the owner is asked to set a backup password. Treat that password as a secret: store it in the protected deployment record, do not reuse it for unrelated services, and do not include it in a public archive. If you cannot recover the password, a txAdmin backup may be unusable even though the file itself copied successfully.
Choosing a backup approach
The method matters less than scope, consistency, separation, and a tested restore. Use the following comparison when designing a routine.
| Approach | Coverage | Consistency | Recovery speed | Off-host durability | Restore-test effort |
|---|---|---|---|---|---|
| Manual copies plus database dump | Complete when you include server data, txData, and every external database | Good if the server is stopped or writes are quiesced | Moderate; files and database must be placed manually | Depends on where the second copy is stored | Moderate |
| Archive created during maintenance | Same scope as the files selected for the archive; database still needs its own export | Good after a clean stop | Fast to transfer as one compressed artifact | Good when encrypted and copied to another host | Moderate; extract and validate permissions |
| Disk or host snapshot | Can cover the whole machine, but may miss an external database | Depends on whether the snapshot is application-consistent | Fast for a same-provider rollback | Weak if snapshots remain on the failed host or account | Higher; test booting a separate clone |
| Managed encrypted object backup | Depends on the paths and database jobs configured | Good only when jobs quiesce writes or use a consistent database export | Potentially fast after automated provisioning | Strong when stored in a separate account or region with access controls | Must be scheduled and verified, not assumed |
For a small or self-managed server, the manual workflow is often sufficient if it is repeatable and tested. Automation improves reliability only when it checks exit codes, records timestamps, alerts on failure, and preserves multiple generations.
How to restore after disk failure
Restore onto a new disk or isolated host first. Do not overwrite the only remaining copy while you are still determining whether the archive and database dump are valid.
- Provision an operating system and install an FXServer artifact compatible with the recorded deployment. Match the operating system family, architecture, and required service account.
- Install or start the bundled txAdmin through the normal FXServer process. txAdmin is part of FXServer, so do not add a random resource in an attempt to recreate it.
- Stop the new instance before replacing data. Create a clean server profile or use an isolated profile so the restore cannot modify production files.
- Copy the backed-up server data directory into the location selected for the new profile. Restore
server.cfg, resources, stream assets, permissions, and deployment files with their original structure. - Restore the backed-up
txDatadirectory to the path resolved byTXHOST_DATA_PATH. If the host uses a provider-specific path, configure that path before starting txAdmin. - Create the required MySQL or MariaDB database and account, then import the recorded dump using the provider’s supported restore procedure. Confirm engine version and character-set requirements before importing.
- Reapply secrets from the protected deployment record. Do not copy a redacted configuration into production and assume the missing keys will be inferred.
- Start the isolated server and inspect console output, txAdmin logs, resource startup results, database connection messages, and permission behavior.
- Connect with a test account. Verify that resources load, streamed assets appear, framework records resolve, inventories or characters are present, and administrative permissions work.
- Only after validation, schedule the production cutover. Preserve the failed disk or original host until the new instance has operated successfully for the agreed observation period.
A file-only restore can produce a server that starts but has empty characters, inventories, or economies. Conversely, a database-only restore cannot recreate missing scripts or configuration. Recovery is complete only when the files, txData, secrets, and external database agree.
Run a restore drill before you need one
At a planned interval, clone the backup into an isolated server profile or temporary host. Use a copy of the database, never production tables. Follow the same sequence you would use after a disk failure and time each stage.
- Confirm the archive opens and the checksum manifest matches.
- Confirm
server.cfgpoints to the intended test database and does not expose production credentials. - Confirm txAdmin starts with the restored profile and that its logs are readable.
- Confirm every required resource starts without a missing-file or schema error.
- Log in with a test account and verify player data, resources, permissions, and startup configuration.
- Record the elapsed restore time and any manual step that should be automated.
Do not run destructive recipe tasks against production data during a drill. The purpose is to prove that the backup can rebuild a working server, not to experiment on the live database.
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Security, retention, and common failure modes
Credentials leaked in an archive
Configuration files and database dumps can contain credentials, identifiers, or keys. Encrypt off-host copies, restrict access by role, and remove secrets before sharing diagnostic files. Rotate a credential immediately if an archive was exposed.
Only the newest generation exists
Accidental deletion, ransomware, or delayed corruption can make the newest copy unusable. Keep several generations on storage that is not continuously writable by the production service account.
txData was assumed rather than located
Managed hosts may override the documented default. Check TXHOST_DATA_PATH and the provider’s startup configuration, then confirm the copied directory contains txAdmin logs, configuration, and data.
The database dump is missing or empty
Check the dump utility’s exit status and file size, then inspect the dump header or import it into a temporary database. A successful file copy does not prove that authentication succeeded or that tables were exported.
The server starts but players are missing
This usually indicates that the external framework database was omitted, imported into the wrong database, or restored with incompatible credentials or schema. Recheck the recorded database name, engine, connection settings, and import output.
Files and database represent different times
If the server was left running, the database may include writes made after resource files were copied. Repeat the backup with a clean stop or a documented quiescing procedure, and align the file-copy and dump timestamps.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →FiveM backup checklist
- Maintenance window announced and server stopped or writes quiesced.
- Complete server data directory copied, including
server.cfg, resources, stream assets, scripts, and permissions. - Complete txAdmin
txDatadirectory copied from the resolved path. - Every external MySQL or MariaDB database identified and exported.
- Artifact, framework, resource, operating-system, engine, and timestamp metadata recorded.
- Secrets stored in a separate encrypted, access-controlled record.
- Local copy verified and second copy stored on another disk or host.
- Multiple generations retained.
- Isolated restore completed and player data, resources, permissions, and startup configuration verified.
Frequently Asked Questions
Where is txData located on a hosted FiveM server?
Its path is controlled by TXHOST_DATA_PATH. Windows and Linux have different defaults, and managed hosts can override both, so inspect the provider’s startup configuration or environment settings rather than assuming a local path.
Is copying the resources folder enough?
No. Copy the complete server data directory, including server.cfg, permissions, scripts, stream assets, and other deployment files, plus the separate txAdmin txData directory.
Can I back up without stopping the server?
Only if you can reliably quiesce all writes and obtain a consistent database export. A clean stop is safer because live file copies and database dumps can represent different moments.
What should I check when a restored server has no player progress?
Verify that the framework’s external MySQL or MariaDB database was exported and imported, that the connection points to the restored database, and that the import completed without errors.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
