Changes between Version 3 and Version 4 of TracBackup
- Timestamp:
- 02/01/17 00:37:12 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracBackup
v3 v4 3 3 [[TracGuideToc]] 4 4 5 Backups 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].5 Trac backups 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]. 6 6 7 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. … … 20 20 Please 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]. 21 21 22 == =Restoring a Backup22 == Restoring a Backup 23 23 24 24 To 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. … … 28 28 psql -U <user> -d <database> -f postgresql.dump 29 29 }}} 30 30 31 The `<database>` option is the same as the [TracEnvironment#DatabaseConnectionStrings database connection string] in the `[trac]` `database` option of //trac.ini//. 31 32