Changes between Version 1 and Version 2 of TracBackup
- Timestamp:
- 09/29/11 01:15:08 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracBackup
v1 v2 19 19 The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`. 20 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.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]. 22 22 23 23 === Restoring a Backup === … … 25 25 Backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the SQLite database. 26 26 27 To restore an environment from a backup, s imply stop the process running Trac (i.e. the Web server or [wiki:TracStandalone tracd]), restore the directory structure from the backupand restart the service.27 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 28 29 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 30 31 31 ---- 32 See also: TracAdmin, TracEnvironment, TracGuide, TracMigrate32 See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate TracMigrate]