You are here: Cisco UCS Protection > Working with UCS blade and rack-mount servers > Disaster recovery of UCS clients

Disaster recovery of UCS clients

If you are running VMware or Hyper-V backups for a client, you can restore the VM from any successful backup. If you are running file-level backups for the client, bare metal technology is used for disaster recovery (DR). For most clients, you will need to have set up bare metal protection and created bare metal boot media before performing DR.

DR procedures vary by client type. Follow the steps below, then proceed to the applicable client-specific procedure.

To recover a UCS client

If necessary, restore the client’s service profile. See Restoring UCS service profile backups for details.

Instantiate the client’s service profile and associate it with the desired blade, rack-mount server, or server in a server pool.

Configure a PXE server or map a bootable ISO image to the virtual-media CDROM drive to the applicable hypervisor or operating system. See the Cisco document Cisco UCS Manager Configuration Common Practices and Quick Start Guide for details.

Proceed to one of the following to perform disaster recovery (DR) of the client:

Hypervisor or OS

DR procedure

VMware vCenter or ESX server

Do one of the following:

•

If the new hypervisor is identical to the original, verify that the Unitrends system can connect and see the guest VMs. Select the vCenter or ESX server in the Navigation pane, select Settings > Clients, Networking, and Notifications > Clients, and click Save at the bottom of the Client page. Refresh the list of VMs to be sure the backup system has discovered all VMs. If the Unitrends system cannot connect to the original hypervisor, add a new one as described in the next option.

•

If the new hypervisor is not identical to the original, add it to the Unitrends system as described in Working with vCenter and ESX servers. Do not remove the original hypervisor from the Unitrends system until you are comfortable with the amount of retained backups for the new hypervisor. Backups for the original hypervisor are deleted when you remove it from the Unitrends system.

VMware virtual machine

See Restoring the entire VMware virtual machine.

Note: If you opted to install the Unitrends agent on the VM and did not run VMware backups, DR is based on the operating system of the virtual machine. Locate the OS in this table for the applicable procedures.

Hyper-V hypervisor

Do one of the following:

•

If the new hypervisor is identical to the original, verify that the Unitrends system can connect and see the guest VMs. Select the Hyper-V application in the Navigation pane, select Settings > Clients, Networking, and Notifications > Clients, and click Save at the bottom of the Client page. Next, click Backup and refresh the list of VMs to be sure the backup system has discovered them all. If the Unitrends system cannot connect to the original hypervisor, add a new one as described in the next option.

•

If the new hypervisor is not identical to the original, add it to the Unitrends system as described in Working with Hyper-V servers. Do not remove the original hypervisor from the Unitrends system until you are comfortable with the amount of retained backups for the new hypervisor. Backups for the original hypervisor are deleted when you remove it from the Unitrends system.

Hyper-V virtual machine

See Restoring Hyper-V virtual machines.

Note: If you opted to install the Unitrends agent on the VM and did not run Hyper-V backups, DR is based on the operating system of the virtual machine. Locate the OS in this table for the applicable procedures. For bare metal restores, see Image-based restore to a Hyper-V virtual machine

Linux

See Linux bare metal restore procedure.

Novell Netware

See Using the bare metal crash recovery boot CD.

OES on Linux

See Using the bare metal crash recovery boot CD.

SCO OpenServer

See Using the bare metal crash recovery boot CD.

Solaris (Intel)

See Using the bare metal crash recovery boot CD.

UnixWare

See Bare metal for UnixWare.

Windows

See Windows Bare Metal Protection.

Xen on OES 2

See Bare metal for Xen on OES 2 virtual machines.