|Version 1 (modified by 11 years ago) ( diff ),|
Table of Contents
Note: Trac uses the
hotcopynomenclature to match that of Subversion, to make it easier to remember when managing both Trac and Subversion servers.
Creating a Backup
To create a backup of a live TracEnvironment, simply run:
$ trac-admin /path/to/projenv hotcopy /path/to/backupdir
trac-admin will lock the database while copying.
The resulting backup directory is safe to handle using standard file-based backup tools like
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 #3198.
Restoring a Backup
Backups are simply a copied snapshot of the entire project environment directory, including the SQLite database.
To restore an environment from a backup, simply stop the process running Trac (i.e. the Web server or tracd), restore the directory structure from the backup and restart the service.
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.