Storage Mirroring Recover overview Page 21 of 677
Storage Mirroring Recover workloads
Building on Storage Mirroring Recover core operations, you can protect specific
workloads to meet your protection goals.
l Full-server workloads—You can protect an entire server, including the data and
system state, which is the server's configured operating system and applications.
In the event of a failure, the target becomes the source.
l Application workloads—You can protect applications running on your source
including Exchange, SQL, BlackBerry, or a Windows file server.
l Virtual workloads—You can protect virtual servers in the following configurations.
l You can protect an entire physical or virtual server to an automatically
provisioned (created) virtual server on a Hyper-V or ESX server. If you are
protecting a virtual server, you are protecting the data within the guest
operating system.
l You can protect a Hyper-V virtual server to a Hyper-V virtual server. In this
case, you are protecting the host-level files (.vhd files), making them highly
available on another Hyper-V server.
l You can protect an ESX virtual server to an ESXvirtual server. In this case,
you are protecting the host-level files (.vmdk files), making them highly
available on another ESXserver.
l Cluster workloads—You can protect two types of clusters.
l You can protect a standard cluster where a single copy of data resides on a
SCSIdisk shared between cluster nodes.
l You can protect a GeoCluster that eliminates the single point of failure of a
shared disk by replicating data between volumes.
Comments to this Manuals