Changes between Version 2 and Version 3 of TracBackup
- Timestamp:
- Oct 29, 2015, 1:00:54 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracBackup
v2 v3 9 9 10 10 To create a backup of a live TracEnvironment, simply run: 11 {{{ 12 13 $ trac-admin /path/to/projenv hotcopy /path/to/backupdir 14 11 {{{#!sh 12 $ trac-admin /path/to/projenv hotcopy /path/to/backupdir 15 13 }}} 16 14 … … 19 17 The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`. 20 18 21 Please , note, that hotcopy command does not overwrite target directory and when such exists, hotcopyends with error: `Command failed: [Errno 17] File exists:` This is discussed in [trac:ticket:3198 #3198].19 Please note, the `hotcopy` command will not overwrite a target directory and when such exists the operation ends with error: `Command failed: [Errno 17] File exists:` This is discussed in [trac:ticket:3198 #3198]. 22 20 23 21 === Restoring a Backup === … … 27 25 To restore an environment from a backup, stop the process running Trac (i.e. 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. 28 26 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.''30 31 27 ---- 32 28 See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate TracMigrate]