Différences entre version 1 et version 2 de TracBackup


Ignorer :
Timestamp :
9 oct. 2014 à 13:45:15 (10 ans)
Auteur :
trac
Commentaire :

--

Légende :

Sans modification
Ajouté
Supprimé
Modifié
  • TracBackup

    v1 v2  
    1010To create a backup of a live TracEnvironment, simply run:
    1111{{{
     12
    1213  $ trac-admin /path/to/projenv hotcopy /path/to/backupdir
     14
    1315}}}
    1416
     
    1719The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`.
    1820
     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].
     22
    1923=== Restoring a Backup ===
    2024
    2125Backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the SQLite database.
    2226
    23 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.
    24 
    25   ''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.''
     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.
    2628
    2729----
    28 See also: TracAdmin, TracEnvironment, TracGuide
     30See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate TracMigrate]