Index: openacs-4/packages/acs-core-docs/www/install-next-backups.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-next-backups.html,v diff -u -r1.11 -r1.12 --- openacs-4/packages/acs-core-docs/www/install-next-backups.html 31 Jul 2011 23:11:46 -0000 1.11 +++ openacs-4/packages/acs-core-docs/www/install-next-backups.html 27 Oct 2014 16:39:20 -0000 1.12 @@ -1,36 +1,36 @@ - -
+ +
The purpose of backup is to enable recovery. Backup and recovery are always risky; here are some steps that minimize the chance recovery is necessary: -
+
Store everything on a fault-tolerant disk array (RAID 1 or 5 or better). -
+
Use battery backup. -
+
Use more reliable hardware, such as SCSI instead of IDE. -
These steps improve the chances of successful recovery:
+
These steps improve the chances of successful recovery:
Store backups on a third disk on another controller -
+
Store backups on a different computer on a different network in a different physical location. (Compared to off-line backup such as tapes and CDRs, on-line backup is faster and more likely to succeed, but requires maintenance of another machine.) -
+
Plan and configure for recovery from the beginning. -
+
Test your recovery strategy from time to time. -
+
Make it easy to maintain and test your recovery strategy, so that you are more likely to do it.
OpenACS installations comprise files and database contents.
If you follow the reference install and put all files,
including configuration files, in
- /var/lib/aolserver/$OPENACS_SERVICE_NAME/,
+ /var/lib/aolserver/$OPENACS_SERVICE_NAME/
,
and back up the database nightly to a file in
- /var/lib/aolserver/$OPENACS_SERVICE_NAME/database-backup,
+ /var/lib/aolserver/$OPENACS_SERVICE_NAME/database-backup
,
then you can apply standard file-based backup strategies to
- /var/lib/aolserver/$OPENACS_SERVICE_NAME
-
/var/lib/aolserver/$OPENACS_SERVICE_NAME
+