Changes between Version 17 and Version 18 of TracBackup

Timestamp:

Jul 14, 2008, 6:39:21 PM (16 years ago)

Author:

ebray <hyugaricdeau@…>

Comment:

This is poor, only partially accurate advice. All initenv does concerning the database path is to set it in the environment's trac.ini when it is created. So yes, if you do initenv again you can set a new database string. However, if you backup includes that environment's trac.ini (which it should) then this will clobber any new settings you created via initenv. The easier, and better thing to do is to modify the trac.ini file. You can do this by hand, or you can automate it with your own restore script.

TracBackup

@@ -27 +27 @@
 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.[[BR]]
 
-To restore the environment from a backup from a different server (a copy), you must before init the environment like that
-trac-admin /path/to/project/trac/ initenv
-After that copy the backup in the correct place (replace the files created by initenv)
-If you don't do an "initenv", trac won't be able to find the database path.
-
   ''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.''