Changes between Version 1 and Version 2 of TracBackup


Ignore:
Timestamp:
Feb 25, 2025, 12:53:26 PM (5 weeks ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracBackup

    v1 v2  
    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'''.
     1= Trac Backup
    32
    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.
     3[[TracGuideToc]]
    54
    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
     5Trac backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the database. Backups can be created using the `hotcopy` command in [wiki:TracAdmin trac-admin].
     6
     7'''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.
     8
     9== Creating a Backup
     10
     11To create a backup of a live TracEnvironment simply run:
     12{{{#!sh
     13$ trac-admin /path/to/projenv hotcopy /path/to/backupdir
    1014}}}
    1115
    12 '''Note:''' TracAdmin will lock the database while copying.
     16[wiki:TracAdmin trac-admin] will lock the database while copying.
    1317
    14 The resulting backup copy is safe to handle using standard file-based backup tools like tar or dump/restore.
     18The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`.
    1519
     20Please 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 [trac:ticket:3198 #3198].
    1621
    17 === Restoring a Backup ===
    18 Backups are simply a copied snapshot of the entire TracEnvironment directory structure, including the SQLite database.
     22== Restoring a Backup
    1923
    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.
     24To restore an environment from a backup, stop the process running Trac, ie 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.
     25
     26To restore a PostgreSQL database backup, use the command:
     27{{{#!sh
     28psql -U <user> -d <database> -f postgresql.dump
     29}}}
     30
     31The `<database>` option is the same as the [TracEnvironment#DatabaseConnectionStrings database connection string] in the `[trac]` `database` option of //trac.ini//.
    2132
    2233----
    23 See also: TracAdmin, TracGuide
     34See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate TracMigrate]