Dell PowerStore 9200T EMC PowerStore Protecting Your Data - Page 24

Unplanned Failover, Virtual volumes replication, Pre-requisites

Page 24 highlights

Unplanned Failover Unplanned failover occurs following source system events such as source system failure, or events that leads to downtime for production access. Unplanned failover is initiated from the destination system, and provides production access to the original destination resource from a point-in-time snapshot. When you initiate an unplanned failover, you can select whether to use the most recent data copy or a snapshot of the data (if available) as the data source. When the connection to the source system is re-established, the original source resource is placed into destination mode. Use the Reprotect option to synchronize the destination storage resource, and then resume the replication session. Virtual volumes replication PowerStore integrates with VMware Site Recovery Manager (SRM) to support asynchronous replication of virtual volume. Virtual machine remote protection is configured using vSphere Storage Policy-Based Management (SPBM). For recovery from failure, failover of virtual machines is configured using VMware SRM. VMware SRM is a VMware disaster recovery solution that automates recovery or migration of virtual machines between a protected site and a recovery site. Snapshot and Replication rules that are created in PowerStore are exposed to vSphere and can be added to protection policies. vSphere provides a storage policy to PowerStore during vVol creation. A replication group, that includes virtual volumes that should be replicated together, is the replication and failover unit configured in vSphere. To view the details of a virtual volume replication session: 1. Select Protection > Replication. 2. Click the replication session status to view it details. The graphic in the replication session details window indicates that vSphere manages the replication session. From the replication window you can do the following: ● View the replication session details. ● Rename the replication group. ● Pause and resume the replication session. ● Synchronize the replication session. Pre-requisites Before configuring virtual volume replication, ensure that the following pre-requisites are met: ● Both local and remote system must be connected and must have vVol capability (see Remote systems). ● Storage containers must be defined on both systems (Storage > Storage Containers > Create) so that they can be paired. If there is a single storage container on each system, the storage containers are paired automatically. Otherwise, it is required to manually specify the storage container destination (Storage > Storage Containers > [storage container] > Protection > Create). Create a virtual volume replication session About this task For information about the required configuration on vSphere, see VMware SRM user documentation. Steps 1. On PowerStore, create a replication rule. The replication rule is exposed to vCenter as a Replication capability. 2. On vSphere, create a policy using the exposed rule. 24 Replication

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33

Unplanned Failover
Unplanned failover occurs following source system events such as source system failure, or events that leads to downtime for
production access. Unplanned failover is initiated from the destination system, and provides production access to the original
destination resource from a point-in-time snapshot.
When you initiate an unplanned failover, you can select whether to use the most recent data copy or a snapshot of the data (if
available) as the data source.
When the connection to the source system is re-established, the original source resource is placed into destination mode. Use
the
Reprotect
option to synchronize the destination storage resource, and then resume the replication session.
Virtual volumes replication
PowerStore integrates with VMware Site Recovery Manager (SRM) to support asynchronous replication of virtual volume.
Virtual machine remote protection is configured using vSphere Storage Policy-Based Management (SPBM). For recovery from
failure, failover of virtual machines is configured using VMware SRM.
VMware SRM is a VMware disaster recovery solution that automates recovery or migration of virtual machines between a
protected site and a recovery site.
Snapshot and Replication rules that are created in PowerStore are exposed to vSphere and can be added to protection policies.
vSphere provides a storage policy to PowerStore during vVol creation.
A replication group, that includes virtual volumes that should be replicated together, is the replication and failover unit
configured in vSphere.
To view the details of a virtual volume replication session:
1.
Select
Protection
>
Replication
.
2.
Click the replication session status to view it details.
The graphic in the replication session details window indicates that vSphere manages the replication session.
From the replication window you can do the following:
View the replication session details.
Rename the replication group.
Pause and resume the replication session.
Synchronize the replication session.
Pre-requisites
Before configuring virtual volume replication, ensure that the following pre-requisites are met:
Both local and remote system must be connected and must have vVol capability (see
Remote systems
).
Storage containers must be defined on both systems (
Storage
>
Storage Containers
>
Create
) so that they can be
paired. If there is a single storage container on each system, the storage containers are paired automatically. Otherwise, it
is required to manually specify the storage container destination (
Storage
>
Storage Containers
>
[storage container]
>
Protection
>
Create
).
Create a virtual volume replication session
About this task
For information about the required configuration on vSphere, see VMware SRM user documentation.
Steps
1.
On PowerStore, create a replication rule.
The replication rule is exposed to vCenter as a Replication capability.
2.
On vSphere, create a policy using the exposed rule.
24
Replication