Changes between Version 2 and Version 3 of TracBackup


Ignore:
Timestamp:
May 22, 2013, 9:36:13 PM (11 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracBackup

    v2 v3  
    1919The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`.
    2020
    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.
     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].
    2222
    2323=== Restoring a Backup ===
     
    2525Backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the SQLite database.
    2626
    27 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.
     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.
    2828
    2929  ''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.''
    3030
    3131----
    32 See also: TracAdmin, TracEnvironment, TracGuide, TracMigrate
     32See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate TracMigrate]