Changes between Version 1 and Version 2 of TracBackup
- Timestamp:
- 11/04/11 12:44:50 (20 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracBackup
v1 v2 2 2 [[TracGuideToc]] 3 3 4 Como o Trac usa um banco de dados backend, ele requer alguns cuidados extras para se criar um backup seguro de um TracEnvironment. Por sorte, TracAdmin tem um comando para fazer backups facilmente - o '''hotcopy'''.4 Since Trac uses a database backend, some extra care is required to safely create a backup of a [wiki:TracEnvironment project environment]. Luckily, [wiki:TracAdmin trac-admin] has a command to make backups easier: `hotcopy`. 5 5 6 '''Nota:''' O Trac usa a nomeclatura ''hotcopy'' para igualar ao [http://subversion.tigris.org/ Subversion], o que faz com que fique mais fácil de lembrar quando estiver gerencinado um servidor Trac e um servidor Subversion. 6 ''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.'' 7 7 8 == Cr iando umBackup ==8 == Creating a Backup == 9 9 10 Para criar um backup de um TracEnvironment, basta executar:10 To create a backup of a live TracEnvironment, simply run: 11 11 {{{ 12 $ trac-admin /some/where/mytracenv hotcopy /my/vault/mytracenv-backup 12 13 $ trac-admin /path/to/projenv hotcopy /path/to/backupdir 14 13 15 }}} 14 16 15 '''Nota:''' TracAdmin irá travar o banco de dados enquanto estiver fazendo a cópia. 17 [wiki:TracAdmin trac-admin] will lock the database while copying.'' 16 18 17 Depois de terminar o backup, esse pode ser manipulado pelos comandos tar ou dump/restore.19 The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`. 18 20 21 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]. 19 22 20 === Restaurando um Backup === 21 Os backups são cópias de toda a estrutura do diretório do TracEnvironment , incluido o banco de dados SQLite. 23 === Restoring a Backup === 22 24 23 Para restaurar um ambiente a partir de um backup, basta "desligar" o seu servidor Trac (Servidor web ou tracd), restaurar a estrutura do diretório a partir do backup e "iniciar" o servidor novamente. 25 Backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the SQLite database. 24 26 27 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. 28 29 ''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.'' 25 30 26 31 ---- 27 Veja também: TracAdmin, TracGuide 32 See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate TracMigrate]
