000028179 - KB-1229 - Automating the backup and restore process

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000028179
Applies ToAffected Versions: 4.2.X; 3.6.X

This Script was created using ACM V3.6 and 4.x. It has not been tested for ACM 5.x or 6.x, and should not be used for those versions without testing.

It is provided as a convenience to our customers and is not an official part of the ACM product. It is provided as is, and there is no guarantee that it will work with future versions.



The recommended automated backup and restore process uses the Oracle datapump ( the same underlying technology used in the AVDB_Export_AVUSER.sh and AVDB_Import_AVUSER.sh scripts) but with automated mounting, error checking and moving/copying of the backup to another device.
The scripts provide the following functionality:

  1. Email on success or failure
  2. Test for enough disk space before starting a backup
  3. Use a non default (/home/oracle/AveksaEportImportDir) directory for the backup file
  4. Temporarily mount a foreign file system for file storage (using clear text or a password file)
  5. Move the backup file to a designated directory
  6. SCP the backup to a third system (trust must be established between the machines)
  7. Cleanup old log files that are N days old (default is 3 days)
  8. Remove backup files greater than N days old (backup only) default = 14
  9. Archive system level files (no automatic restore)
Both the backup and restore can be scripted (using cron - see appendix in documentation) to provide a customized automated solution.
See the attached files for the scripts and implementation documentation.
Note: Scripts are provided as is and Aveksa is not responsible for debugging or enhancing them for a particular environment

updated 10/01/2010