Difference between revisions of "Backup/Restore procedure"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
== Current Strategy == | == Current Strategy == | ||
| + | === Backup === | ||
Currently running a [[backup script]] at 06:00 UTC | Currently running a [[backup script]] at 06:00 UTC | ||
| + | |||
| + | The VMWare virtual machine is snapshotted and then its file system is rsync'd. It is supposed to minimise the | ||
| + | |||
| + | ===Restore to original host=== | ||
| + | |||
| + | Copy the rsync copy back to its original location | ||
| + | |||
| + | === Restore to another host === | ||
| + | |||
| + | Needs VMWare Server 2.0 installed | ||
| + | |||
| + | gpl.openqm.com DNS to point to new server. | ||
== Problems with current strategy == | == Problems with current strategy == | ||
Revision as of 10:51, 10 December 2008
Contents
Current Strategy
Backup
Currently running a backup script at 06:00 UTC
The VMWare virtual machine is snapshotted and then its file system is rsync'd. It is supposed to minimise the
Restore to original host
Copy the rsync copy back to its original location
Restore to another host
Needs VMWare Server 2.0 installed
gpl.openqm.com DNS to point to new server.
Problems with current strategy
- Only one physical backup copy overwritten daily so no possibility to go back more than one day if a corrupt system is backed up
- No regular verification if the backup copy is usable so the procedure could fail silently eg if there is anything wrong in the scripts
- Only SteveB has overview and responsible which is a single point of failure
