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.13 -r1.14 --- openacs-4/packages/acs-core-docs/www/install-next-backups.html 7 Aug 2017 23:47:50 -0000 1.13 +++ openacs-4/packages/acs-core-docs/www/install-next-backups.html 8 Nov 2017 09:42:11 -0000 1.14 @@ -1,16 +1,22 @@ -
+
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 @@ -24,13 +30,16 @@
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/
,
and back up the database nightly to a file in
- $OPENACS_SERVICE_NAME
//var/lib/aolserver/$OPENACS_SERVICE_NAME/database-backup
,
+ /var/lib/aolserver/
,
then you can apply standard file-based backup strategies to
- $OPENACS_SERVICE_NAME
/database-backup/var/lib/aolserver/$OPENACS_SERVICE_NAME
-
/var/lib/aolserver/$OPENACS_SERVICE_NAME
+
+