Changes between Version 1 and Version 2 of TracBackup


Ignore:
Timestamp:
Jun 6, 2013 4:39:50 AM (14 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracBackup

    v1 v2  
    11= 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'''. 
     2[[TracGuideToc]] 
    33 
    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. 
     4Since 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`. 
     5 
     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.'' 
    57 
    68== Creating a Backup == 
     9 
    710To create a backup of a live TracEnvironment, simply run: 
    811{{{ 
    9   $ trac-admin /some/where/mytracenv hotcopy /my/vault/mytracenv-backup 
     12 
     13  $ trac-admin /path/to/projenv hotcopy /path/to/backupdir 
     14 
    1015}}} 
    1116 
    12 '''Note:''' TracAdmin will lock the database while copying. 
     17[wiki:TracAdmin trac-admin] will lock the database while copying.'' 
    1318 
    14 The resulting backup copy is safe to handle using standard file-based backup tools like tar or dump/restore. 
     19The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`. 
    1520 
     21Please, 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]. 
    1622 
    1723=== Restoring a Backup === 
    18 Backups are simply a copied snapshot of the entire TracEnvironment directory structure, including the SQLite database.  
    1924 
    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. 
     25Backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the SQLite database.  
     26 
     27To 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. 
    2128 
    2229---- 
    23 See also: TracAdmin, TracGuide 
     30See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate TracMigrate]