White Papers

Configuring replication
24 Dell EMC SC Series: VMware Site Recovery Manager Best Practices | 2007-M-BP-V
3. Once the SRM recovery snapshot has been taken, a view volume is created from that snapshot.
4. The view volume is then presented to the vSphere host (or hosts) at the DR site for the SRM to begin
a test execution of the recovery plan.
During an actual disaster recovery or planned migration execution, a view volume from a snapshot is not
mounted to the remote vSphere hosts. Instead, the destination volume itself is mounted to the remote hosts.
This change in behavior from SRM 4.x is to facilitate the reprotect and failback features introduced in SRM
5.x.
5.7 Replication dependencies and replication transfer time
If the application has multiple volumes in a data set, it is important to remember that not all volumes may
finish replicating within the same timeframe.
Replication dependencies and transfer times
Due to various factors (such as rate of change, replication network bandwidth, volume size, and replication
QoS), it is possible for multiple volumes in a backup set to finish replicating frozen snapshots at different
times. In this scenario, SRM does not use incomplete replication snapshots. This means that if the plan is
started before the frozen snapshot replications have completely transferred all of the data (as seen in Figure
8), then the volume A snapshot from 4 p.m. will be mounted, the volume B snapshot from 3 p.m. will be
mounted, and the volume C snapshot from 3 p.m. will be mounted. If all three volumes are part of a
consistency group, and are in use for a tiered application or database application, then the application
volumes presented from different points in time may cause problems with the application. If this happens,
manual intervention may be required to present the previous set of consistent snapshots back to the host (for
example, the 3 p.m. snapshot from volumes A, B, and C may need to be forced).