In our network, we have multiple servers and some of these are Virtual Machines. In order to back these up, we use a Disk-to-Disk and a Disk-to-Disk-to-Tape strategy, using BackupAssist v5.
Let’s look at how we do this.
Windows Server #1: SBS 2003 – This is our main server, domain controller, print and file server. We have three backup jobs:
- Full backup to USB HDD – backing up the complete system, Exchange Server and mailboxes, file system to USB HDD
- File Replication of the filesystem to Server 2 (Mirror mode) – to ensure that our file system is also backed up to an additional location
- Rsync our file system to an offsite location
Windows Server #2: Windows Server 2003 – this is a VM host machine running the free VMware Server, and also has a DLT4 tape drive installed. We have two jobs running here:
- File replication of our VM guests to a local disk – we do this by using the File Replication job in Mirror mode to mirror the entire directories of our VM guests to a separate internally installed hard drive.
- Tape backup – backup the system partition, the mirror of the VMs (that were created by the previously described job), the mirror of the file system from Server 1, plus the backups of the VM guests (described later), to tape.
On Server 2, there are three VM guests:
- Linux machine #1 – our source code repository – which is backed up as part of job #1 on the host, Server 2. We also have a scheduled rsync job that syncs the source code repository to an external site.
- Linux machine #2 – our issue tracking system – which is backed up as part of job #1 on the host, Server 2. We also have a scheduled rsync job that syncs the database to an external site.
- Windows Server #3 – our CRM system – which runs BackupAssist and does a filesystem backup and a SQL Server backup to the host, Windows Server #2. This is then picked up in the Tape job as previously described.
Notice that the 3 virtual machine guests do not need an internal system backup from within the guest because the host is backing up the entire guests, so a bare-metal restore would simply involve copying back the VM guests to a new server and running them from there.
When backing up the VM guests, we suspend the virtual machine to ensure that all data is flushed to disk. For more information about how to backup VM guests, please refer to this document: BackupAssist Usage Scenarios Guide
The next thing I’m going to investigate is whether it’s possible (and practical) to Rsync our guest VMs offsite. That means to say, as well as backing them up to tape, to have an additional job to sync them to a remote server via the Internet.
I’ll keep everyone posted on how it goes!