Index: openacs-4/packages/acs-core-docs/www/automated-backup.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/automated-backup.adp,v diff -u -r1.3 -r1.4 --- openacs-4/packages/acs-core-docs/www/automated-backup.adp 8 Nov 2017 09:42:10 -0000 1.3 +++ openacs-4/packages/acs-core-docs/www/automated-backup.adp 25 Apr 2018 08:38:27 -0000 1.4 @@ -3,11 +3,11 @@ Automated Backup -
+ leftLink="snapshot-backup" leftLabel="Prev" + title="Chapter 8. Backup and +Recovery" + rightLink="backups-with-cvs" rightLabel="Next"> +

Automated Backup

The recommended backup strategy for a production sit is to use an automated script which first backs up the database to a file in @@ -19,21 +19,18 @@

  • Make sure that the manual backup process described above works.

  • Customize the default backup script. Edit /var/lib/aolserver/$OPENACS_SERVICE_NAME/etc/backup.sh with your specific parameters.

  • -

    Make sure the file is executable:

    -chmod +x backup.sh
    -
    +

    Make sure the file is executable:

    chmod +x backup.sh
  • Set this file to run automatically by adding a line to root's crontab. (Typically, with export EDITOR=emacs; crontab -e.) This example runs the backup script at 1:30 am every day.

    -30 1 * * *        sh /var/lib/aolserver/$OPENACS_SERVICE_NAME/etc/backup.sh
    -
    +30 1 * * * sh /var/lib/aolserver/$OPENACS_SERVICE_NAME/etc/backup.sh
  • - \ No newline at end of file + leftLink="snapshot-backup" leftLabel="Prev" leftTitle="Manual backup and recovery" + rightLink="backups-with-cvs" rightLabel="Next" rightTitle="Using CVS for backup-recovery" + homeLink="index" homeLabel="Home" + upLink="backup-recovery" upLabel="Up"> + \ No newline at end of file