close Warning: Can't synchronize with repository "(default)" (/common/SVN/wimax does not appear to be a Subversion repository.). Look in the Trac log for more information.

Changes between Version 3 and Version 4 of TracBackup


Ignore:
Timestamp:
Jan 30, 2019, 11:46:28 PM (19 months ago)
Author:
trac
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • TracBackup

    v3 v4  
    33[[TracGuideToc]]
    44
    5 Trac 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].
     5Trac 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].
    66
    77'''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.
     
    99== Creating a Backup
    1010
    11 Create a backup of a live TracEnvironment by running:
     11To create a backup of a live TracEnvironment simply run:
    1212{{{#!sh
    1313$ trac-admin /path/to/projenv hotcopy /path/to/backupdir
    1414}}}
    1515
    16 The database will be locked while hotcopy is running.
     16[wiki:TracAdmin trac-admin] will lock the database while copying.
    1717
    1818The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`.
    1919
    20 Please 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].
     20Please 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].
    2121
    2222== Restoring a Backup
    2323
    24 To 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.
    25 
    26 If 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.
     24To 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.
    2725
    2826To restore a PostgreSQL database backup, use the command:
    2927{{{#!sh
    30 $ psql -U <user> -d <database> -f /path/to/postgresql.dump
     28psql -U <user> -d <database> -f postgresql.dump
    3129}}}
    3230
    33 The `<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.
    34 
    35 Similarly, for MySQL:
    36 
    37 {{{#!sh
    38 $ mysql -u <user> -p <database> < /path/to/mysql.dump
    39 }}}
     31The `<database>` option is the same as the [TracEnvironment#DatabaseConnectionStrings database connection string] in the `[trac]` `database` option of //trac.ini//.
    4032
    4133----
    42 See also: TracAdmin, TracEnvironment, [trac:TracMigrate TracMigrate]
     34See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate TracMigrate]