-
Notifications
You must be signed in to change notification settings - Fork 149
TracBackup
Since Trac uses a database backend, some extra care is required to safely create a backup of a [wiki:TracEnvironment]. Luckily, [wiki:TracAdmin] has a command to make backups easier: `hotcopy`.
''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.''
To create a backup of a live TracEnvironment, simply run:
[wiki:TracAdmin] 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, that hotcopy command does not overwrite target directory and when such exists, hotcopy ends with error: `Command failed: [Errno] File exists:` This is discussed in [trac:ticket:3198].
Backups are simply a copied snapshot of the entire [wiki:TracEnvironment] directory, including the SQLite database.
To restore an environment from a backup, stop the process running Trac (i.e. the Web server or [wiki:TracStandalone]), restore the contents of your backup (path/to/backupdir) to your [wiki:TracEnvironment] directory and restart the service.
See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate]