Trac Backup

Backups are simply a copied snapshot of the entire project environment directory, including the database. Backups can be created using the hotcopy command in trac-admin.

Note: Trac uses the hotcopy nomenclature 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 tar or dump/restore.

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 #3198.

Restoring a Backup

To restore an environment from a backup, stop the process running Trac, ie the Web server or tracd, restore the contents of your backup (path/to/backupdir) to your project environment directory and restart the service.

To restore a PostgreSQL database backup, use the command:

psql -U <user> -d <database> -f postgresql.dump

The <database> option is the same as the database connection string in the [trac] database option of trac.ini.


See also: TracAdmin, TracEnvironment, TracGuide, TracMigrate

Last modified 18 months ago Last modified on Feb 21, 2018, 8:12:12 AM

NOTE: The content of this website is accessible with any browser. The graphical design though relies completely on CSS2 styles. If you see this text, this means that your browser does not support CSS2. Consider upgrading to a standard conformant browser like Mozilla Firefox or Opera but also Apple's Safari or KDE's Konqueror for example. It may also be that you are looking at a mirror page which did not copy the CSS for this page. Or if some pictu res are missing, then the mirror may not have picked up the contents of the inc directory.