70-659 Part 15

Managing Backups

Using Data Protection Manager (DPM) is one of the methods for backing up VMs and host systems. DPM supports two methods for backing up VMs; Live (online backup) and offline backup. Live backups have no downtime for the VM. Offline backups are used for VMs that don’t support live backup. This means that the VMs will be backed up when they are shutdown.

Windows Server Backup (WSB) is built into Windows Server 2008 R2. WSB can use Volume Shadow Copy Service (VSS) writers to perform block level backups which create a disk image.

There are two backup strategies that also can be used:

Host-level backup: In a host-level backup you can run the backup agent run on the host. Note you cannot backup VMs that are connected to pass-through disks or stored in remote storage such as iSCSI.

Guest-level backup: In a guest-level backup, the backup agent is on the VM. This allows you to backup contents within the VM and restores items in the VM.

Performing Non-cluster Migrations

When it comes to performing migrations, VMM will determine what types of migrations are available. These decisions are based on the topology that VMM discovers and what is best suited type of migration to use.

In order to perform a SAN migration, a SAN must be present. VMM only supports SAN migration for Virtual Server and Hyper-V. The following is from one of the links below, but the info is pretty straight forward. For SAN migration to work you need to have:

· One VM per LUN

· The SAN must be managed by VMM

· Virtual Disk Service (VDS) must be installed on the VMM server

· All servers involved must be able to communicate with the SAN

· Fiber Channel should be used

There are a few things to note in order to perform a network migration. First, performing a network migration requires the use of the Background Intelligent Transfer Service (BITS). BITS is used in migrations for Virtual Server and Hyper-V. Second, network migrations are used in transfers from two hosts for which VMM is managing, or transfers between a host and a library server. Lastly, if you are doing an ESX network migration, sFTP will be used for ESX3.0 and 3.5, and HTTPS will be used for ESX1 3.5.

The following blog posts best describe how the two migrations work:



Comments are closed.