Changes between Version 4 and Version 5 of TracBackup


Ignore:
Timestamp:
08/08/15 13:07:48 (2 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracBackup

    v4 v5  
    1 = Trac Backup = 
     1= Trac Backup 
     2 
    23[[TracGuideToc]] 
    34 
    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`. 
     5Backups 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]. 
    56 
    6   ''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.'' 
     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. 
    78 
    8 == Creating a Backup == 
     9== Creating a Backup 
    910 
    10 To create a backup of a live TracEnvironment, simply run: 
    11 {{{ 
    12  
    13   $ trac-admin /path/to/projenv hotcopy /path/to/backupdir 
    14  
     11To create a backup of a live TracEnvironment simply run: 
     12{{{#!sh 
     13$ trac-admin /path/to/projenv hotcopy /path/to/backupdir 
    1514}}} 
    1615 
    17 [wiki:TracAdmin trac-admin] will lock the database while copying.'' 
     16[wiki:TracAdmin trac-admin] will lock the database while copying. 
    1817 
    1918The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`. 
    2019 
    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]. 
     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]. 
    2221 
    23 === Restoring a Backup === 
     22=== Restoring a Backup 
    2423 
    25 Backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the SQLite database.  
     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. 
    2625 
    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. 
     26To restore a PostgreSQL database backup, use the command: 
     27{{{#!sh 
     28psql -U <user> -d <database> -f postgresql.dump 
     29}}} 
     30The `<database>` option is the same as the [TracEnvironment#DatabaseConnectionStrings database connection string] in the `[trac]` `database` option of //trac.ini//. 
    2831 
    2932----