Changes between Version 7 and Version 8 of TracBackup
- Timestamp:
- Aug 1, 2024, 10:29:33 AM (5 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracBackup
v7 v8 3 3 [[TracGuideToc]] 4 4 5 Trac backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the database. Backups can be created using the `hotcopy` command in [wiki:TracAdmin trac-admin].5 Trac backups are a copied snapshot of the entire [TracEnvironment project environment] directory, including the database. Backups can be created using the `hotcopy` command of [TracAdmin trac-admin]. 6 6 7 '''Note''': Trac uses the `hotcopy` nomenclature to match that of [http ://subversion.tigris.org/ Subversion], to make it easier to remember when managing both Trac and Subversion servers.7 '''Note''': Trac uses the `hotcopy` nomenclature to match that of [https://subversion.apache.org/ Subversion]. 8 8 9 9 == Creating a Backup 10 10 11 To create a backup of a live TracEnvironment simply run:11 Create a backup of a live TracEnvironment by running: 12 12 {{{#!sh 13 13 $ trac-admin /path/to/projenv hotcopy /path/to/backupdir 14 14 }}} 15 15 16 [wiki:TracAdmin trac-admin] will lock the database while copying.16 The database will be locked while hotcopy is running. 17 17 18 18 The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`. 19 19 20 Please note, the `hotcopy` command will not overwrite a target directory and when such exists, the operation ends with an error: `Command failed: [Errno 17] File exists:` This is discussed in [trac:ticket:3198 #3198].20 Please note, the `hotcopy` command will not overwrite a target directory. When the target exists the operation will end with an error: `Command failed: [Errno 17] File exists:` This is discussed in [trac:#3198 #3198]. 21 21 22 22 == Restoring a Backup 23 23 24 To restore an environment from a backup, stop the process running Trac, ie the Web server or [wiki:TracStandalone tracd], restore the contents of your backup (path/to/backupdir) to your [wiki:TracEnvironment project environment] directory and restart the service. 24 To restore an environment from a backup, stop the process running Trac, ie the web server or [TracStandalone tracd], restore the contents of your backup to your [TracEnvironment project environment] directory and restart the process. 25 26 If you are using a database other than SQLite, you'll need to restore the database from the dump file. The dump file is saved in the environment `db` directory. 25 27 26 28 To restore a PostgreSQL database backup, use the command: 27 29 {{{#!sh 28 psql -U <user> -d <database> -fpostgresql.dump30 $ psql -U <user> -d <database> -f /path/to/postgresql.dump 29 31 }}} 30 32 31 The `<database>` option is the same as the [TracEnvironment#DatabaseConnectionStrings database connection string] in the `[trac]` `database` option of //trac.ini//. 33 The `<database>` option is the same as the [TracEnvironment#DatabaseConnectionStrings database connection string] in the [TracIni#trac-database-option "[trac] database"] option of the project's `trac.ini` file. 34 35 Similarly, for MySQL: 36 37 {{{#!sh 38 $ mysql -u <user> -p <database> < /path/to/mysql.dump 39 }}} 32 40 33 41 ---- 34 See also: TracAdmin, TracEnvironment, TracGuide,[trac:TracMigrate TracMigrate]42 See also: TracAdmin, TracEnvironment, [trac:TracMigrate TracMigrate]