Changes between Version 2 and Version 3 of TracBackup


Ignore:
Timestamp:
Jan 28, 2018, 12:53:34 PM (6 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracBackup

    v2 v3  
    99
    1010To create a backup of a live TracEnvironment, simply run:
    11 {{{
    12 
    13   $ trac-admin /path/to/projenv hotcopy /path/to/backupdir
    14 
     11 {{{#!sh
     12$ trac-admin /path/to/projenv hotcopy /path/to/backupdir
    1513}}}
    1614
     
    1917The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`.
    2018
    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].
     19Please note, the `hotcopy` command will not overwrite a target directory and when such exists the operation ends with error: `Command failed: [Errno 17] File exists:` This is discussed in [trac:ticket:3198 #3198].
    2220
    2321=== Restoring a Backup ===
     
    2725To 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.
    2826
    29   ''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.''
    30 
    3127----
    3228See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate TracMigrate]