Database backup and purge is run every Sunday at
2:30AM. Backup and purge applies only to the database stored
locally. The remote database is not affected by these settings
in any way. If the remote database server is not a CIPAFilter,
customer is responsible for implementing backup and
purge.
If restoration of the database after failure is
important for your implementation, the following
responsibilites are incurred by the customer. Speak with Tech
support to help you determine a sensible test and backup
procedure that meets your requirements.
Check this page weekly for anomalies in the backup/purge
log
Periodically download database backups for use in
recovery in the case of mirror failure
Periodically test the backup by restoring a copy to a
Postgress Server
Warning: Increasing purge windows
will increase load, database size and backup size.
Purge Windows
Number of Backups to Retain
Web Usage Reporting: Number of Days to
Retain
Email Archival: Number of Days to Retain
Database Statistics - Estimates Updated Every
Purge Run
/usr/local/sbin/dbmaint: /hda1/etc/init.d/vars/db: No such file or directory
Sun May 6 02:30:01 CDT 2007 Deleting old backups...
Sun May 6 02:30:01 CDT 2007 Beginning Backup...
3482399 May 6 02:30 backup-2007-05-06_02+30.pgdmp
Sun May 6 02:30:06 CDT 2007 Purging contentfilter records...
ERROR: relation "log_raw" does not exist
ERROR: relation "urls" does not exist
ERROR: relation "log_raw" does not exist
Sun May 6 02:30:06 CDT 2007 Purging bandwidth monitoring records...
Sun May 6 02:31:11 CDT 2007 Backup/Purge Complete
