| |
1 |
= Trac Backup = |
| |
2 |
Since Trac uses a database backend, it requires some extra care to safely create a backup of a TracEnvironment. Luckily, TracAdmin has a command to make backups easier - '''hotcopy'''. |
| |
3 |
|
| |
4 |
'''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. |
| |
5 |
|
| |
6 |
== Creating a Backup == |
| |
7 |
To create a backup of a live TracEnvironment, simply run: |
| |
8 |
{{{ |
| |
9 |
$ trac-admin /some/where/mytracenv hotcopy /my/vault/mytracenv-backup |
| |
10 |
}}} |
| |
11 |
|
| |
12 |
'''Note:''' TracAdmin will lock the database while copying. |
| |
13 |
|
| |
14 |
The resulting backup copy is safe to handle using standard file-based backup tools like tar or dump/restore. |
| |
15 |
|
| |
16 |
|
| |
17 |
=== Restoring a Backup === |
| |
18 |
Backups are simply a copied snapshot of the entire TracEnvironment directory structure, including the SQLite database. |
| |
19 |
|
| |
20 |
To restore an environment from a backup, simply shut down your Trac service (Web server or tracd), restore the directory structure from backup and restart the service. |
| |
21 |
|
| |
22 |
---- |
| |
23 |
See also: TracAdmin, TracGuide |
