Changes between Version 1 and Version 2 of TracBackup


Ignore:
Timestamp:
Mar 12, 2015, 4:35:26 PM (10 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracBackup

    v1 v2  
    22[[TracGuideToc]]
    33
    4 Since Trac uses a database backend, some extra care is required to safely create a backup of a [wiki:TracEnvironment project environment]. Luckily, [wiki:TracAdmin trac-admin] has a command to make backups easier: `hotcopy`.
     4Backups 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].
    55
    66  ''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.''
     
    99
    1010To create a backup of a live TracEnvironment, simply run:
    11 {{{
    12   $ trac-admin /path/to/projenv hotcopy /path/to/backupdir
     11 {{{#!sh
     12$ trac-admin /path/to/projenv hotcopy /path/to/backupdir
    1313}}}
    1414
     
    1717The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`.
    1818
     19Please 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].
     20
    1921=== Restoring a Backup ===
    2022
    21 Backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the SQLite database.
     23To 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.
    2224
    23 To restore an environment from a backup, simply stop the process running Trac (i.e. the Web server or [wiki:TracStandalone tracd]), restore the directory structure from the backup and restart the service.
    24 
    25   ''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.''
     25To restore a PostgreSQL database backup, use the command:
     26{{{#!sh
     27psql -U <user> -d <database> -f postgresql.dump
     28}}}
     29The `<database>` option is the same as the [TracEnvironment#DatabaseConnectionStrings database connection string] in the `[trac]` `database` option of //trac.ini//.
    2630
    2731----
    28 See also: TracAdmin, TracEnvironment, TracGuide
     32See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate TracMigrate]