Changes between Version 1 and Version 2 of TracBackup
- Timestamp:
- 06/17/09 18:53:29 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracBackup
v1 v2 1 1 = Trac Backup = 2 Since Trac uses a database backend, it requires some extra care to safely create a backup of a TracEnvironment. Luckily, TracAdmin has a command to make backups easier - '''hotcopy'''. 2 [[TracGuideToc]] 3 3 4 '''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. 4 Since Trac uses a database backend, some extra care is required to safely create a backup of a [wiki:TracEnvironment project environment]. Luckily, [wiki:TracAdmin trac-admin] has a command to make backups easier: `hotcopy`. 5 6 ''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.'' 5 7 6 8 == Creating a Backup == 9 7 10 To create a backup of a live TracEnvironment, simply run: 8 11 {{{ 9 $ trac-admin /some/where/mytracenv hotcopy /my/vault/mytracenv-backup 12 13 $ trac-admin /path/to/projenv hotcopy /path/to/backupdir 14 10 15 }}} 11 16 12 '''Note:''' TracAdmin will lock the database while copying. 17 [wiki:TracAdmin trac-admin] will lock the database while copying.'' 13 18 14 The resulting backup copy is safe to handle using standard file-based backup tools like tar or dump/restore.19 The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`. 15 20 21 Please, note, that hotcopy command does not overwrite target directory and when such exists, hotcopy ends with error: `Command failed: [Errno 17] File exists:` This is discussed in [trac:ticket:3198 #3198]. 16 22 17 23 === Restoring a Backup === 18 Backups are simply a copied snapshot of the entire TracEnvironment directory structure, including the SQLite database.19 24 20 To restore an environment from a backup, simply shut down your Trac service (Web server or tracd), restore the directory structure from backup and restart the service. 25 Backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the SQLite database. 26 27 To restore an environment from a backup, simply stop the process running Trac (i.e. the Web server or [wiki:TracStandalone tracd]), restore the directory structure from the backup and restart the service. 28 29 ''Note: Automatic backup of environments that don't use SQLite as database backend is not supported at this time. As a workaround, we recommend that you stop the server, copy the environment directory, and make a backup of the database using whatever mechanism is provided by the database system.'' 21 30 22 31 ---- 23 See also: TracAdmin, Trac Guide32 See also: TracAdmin, TracEnvironment, TracGuide, TracMigrate