Back up and restore a QBCore server

A backup is valid only after a successful restore test. Protect three independent layers: repository/files, database, and deployment configuration/secrets.

Before the backup

1. Schedule a write pause or maintenance window.
2. Record deployed repository commits and current database/schema identity.
3. Identify storage outside the live server directory.
4. Define encryption, retention, and access controls.

Capture

• Git commits plus patches for uncommitted local changes
• Resource/config files that are not generated
• A consistent database dump from the database’s supported tool
• txAdmin profile/recipe configuration without exposing secrets
• A manifest with timestamps, checksums, host, and operator

Restore rehearsal

Restore into an isolated directory and database, update connection details, start the server, and run the first-boot smoke test. Record duration, errors, and the exact backup identifier.

Do not publish commands containing production paths, credentials, or unresolved environment variables. Follow your database vendor’s current backup documentation for consistency options.