Backup scripts
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
OpenVista/GT.M Integration | Status tracked in Mainline | |||||
Mainline |
Fix Released
|
High
|
Jon Tai |
Bug Description
Scripts need to be written to back up instances of OpenVista Server.
A suggested approach is to have a script "ovbackup" that takes a single argument - the instance to back up. This script would copy the routines to a temporary directory, run mupip backup to get a consistent snapshot of the globals, tar/zip up the temporary directory, and move the file to the backups directory where it can be copied to other media such as tape. After a successful backup, the script should check a configuration file to see how many backups this instance wants to keep around, then remove the oldest extraneous backups. Old journals should also be purged.
A second script, could be written that simply loops through each of the OpenVista instances and calls "ovbackup" on each one. This second script could be scheduled to run daily via cron. This would be the default backup strategy.
Optionally, an administrator could opt to exclude an OpenVista instance from the daily backup script and schedule backups of that instance separately, allowing maximum flexibility over backup intervals. For example, a backup of the production environment may occur at 6am, noon, 6pm, and midnight every day, but backups of the training environment should only occur at 3am on Mondays, Wednesdays, and Fridays.
Related branches
Changed in openvista-gtm-integration: | |
importance: | Undecided → High |
milestone: | none → phase-1 |
status: | New → Confirmed |
description: | updated |
description: | updated |
At this point, I think the only things left to do on this script are to handle errors and to purge old journals.