Backup strategy - virtualisation changes everything
Working under a brand new set of rules.
By John Brandon, Computerworld US | Techworld | Published: 10:00, 21 February 2008
Backup agents are included with VMware and other virtualisation products to help administrators integrate VMs into the traditional backup process. The main advantage is cost: The agents are free or add a relatively minimal fee. On the downside, agents force administrators to use a fairly simplistic approach: Admins can archive an entire virtualised server, but not pick and choose volumes or guest operating systems. Nor can server administrators restore specific portions of data, or substantiate (verify the data integrity) of VM volumes.
VM snapshots A new trend is for companies to create mirrors of the VM volumes, says Russell, because it provides more flexibility, reduces costs and allows a company to substantiate an entire location, which fits into an enterprisewide backup strategy for disaster recovery.
For example, at the Immune Tolerance Network (ITN) - part of the University of California clinical research group in San Francisco - virtualisation backups have become not just a part of disaster planning, but they actually help researchers with clinical trials to fight new diseases.
ITN archives the LUN, or the specific address of the hard disk drive. Using data de-duplication algorithms that weed out redundant data, it keeps multi-terabyte archives of virtual servers. Researchers can request additional archival LUNs, a process that would be difficult or impossible with physical servers.
"The traditional method of putting a tape in a backup system serving multiple servers is outdated," says Michael Williams, ITN's executive director of IT. "Once you move to virtual storage and separation of the volume from the physical disk, you can do very interesting things. The first thing we do when we provision a LUN is we oversubscribe it. A researcher believes they have 2TB volumes - and they do."
But in reality, the LUNs are thin-provisioned, or allocated just enough storage space on a physical disk, based on snapshot policies, and they might only be 20GB each. That volume of data is backed up every four hours. This is equivalent to a hard crash backup (a complete archive of data that can be restored to a prior state), Williams says.
Williams explains that the archives - created using Network Appliance's SnapShot and SnapMirror - are then moved to an off-site location and archived further using Veritas NetBackup over a wide-area network to create a full-image backup on low-cost Serial Advanced Technology Attachment drives.
He describes the snapshot process as beneficial to the researchers because it is easier to request a restore and faster than it was in previrtualisation days, but it is still complex for IT. A scientist could request a data retrieval, which is similar to a traditional storage-restore request, and not have to wait for IT to access a library of tapes and make the restore. But the virtual restore process is more complex for IT, because staffers might have to, say, find and mount a virtual LUN from a restore point located on a separate backup system, such as a Veritas archive. The end user can access the data in a matter of hours instead of the much longer time frames required by tape.