Changes between Version 23 and Version 24 of TracBackup

Timestamp:

Aug 16, 2009, 5:26:41 PM (15 years ago)

Author:

anonymous

Comment:

Address and remove user comment about the restoration instructions being too complicated

TracBackup

@@ -25 +25 @@
 Backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the SQLite database. 
 
-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.
-
-{{{Well, how does one "restore the directory structure"?  Is there a trac-admin command?}}}
-{{{Some advice: in technical literature never use: obviously, simply, etc.  It might be simple to you, but not to someone else.  Then, they feel stupid, like I do now.}}}
-
-Is this the correct backup restoration procedure?
-> To restore an environment from a backup, stop the process running Trac (i.e. the Web server or [wiki:TracStandalone tracd]), move the existing Trac directory out of the way and replace it with the backup created above (i.e. {{{/path/to/backupdir}}}). The Trac service can then be started as usual.
+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.
 
   ''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.''