# Changes between Version 1 and Version 2 of TracBackup

Ignore:
Timestamp:
05/09/10 05:59:49 (12 years ago)
Comment:

--

### Legend:

Unmodified
 v1 To create a backup of a live TracEnvironment, simply run: {{{ \$ trac-admin /path/to/projenv hotcopy /path/to/backupdir }}} The resulting backup directory is safe to handle using standard file-based backup tools like tar or dump/restore. 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]. === Restoring a Backup === Backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the SQLite database. 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. 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. ''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.'' ---- See also: TracAdmin, TracEnvironment, TracGuide See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate TracMigrate]