Changes between Initial Version and Version 1 of TracBackup

Jul 30, 2021, 7:39:47 AM (16 months ago)



  • TracBackup

    v1 v1  
     1= Trac Backup
     5Trac backups are a copied snapshot of the entire [TracEnvironment project environment] directory, including the database. Backups can be created using the `hotcopy` command of [TracAdmin trac-admin].
     7'''Note''': Trac uses the `hotcopy` nomenclature to match that of [ Subversion], to make it easier to remember when managing both Trac and Subversion servers.
     9== Creating a Backup
     11Create a backup of a live TracEnvironment by running:
     13$ trac-admin /path/to/projenv hotcopy /path/to/backupdir
     16The database will be locked while hotcopy is running.
     18The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`.
     20Please note, the `hotcopy` command will not overwrite a target directory. When the target exists the operation will end with an error: `Command failed: [Errno 17] File exists:` This is discussed in [trac:#3198 #3198].
     22== Restoring a Backup
     24To restore an environment from a backup, stop the process running Trac, ie the web server or [TracStandalone tracd], restore the contents of your backup to your [TracEnvironment project environment] directory and restart the process.
     26If you are using a database other than SQLite, you'll need to restore the database from the dump file. The dump file is saved in the environment `db` directory.
     28To restore a PostgreSQL database backup, use the command:
     30$ psql -U <user> -d <database> -f /path/to/postgresql.dump
     33The `<database>` option is the same as the [TracEnvironment#DatabaseConnectionStrings database connection string] in the [TracIni#trac-database-option "[trac] database"] option of the project's `trac.ini` file.
     35Similarly, for MySQL:
     38$ mysql -u <user> -p <database> < /path/to/mysql.dump
     42See also: TracAdmin, TracEnvironment, [trac:TracMigrate TracMigrate]