VMware Cloud Community
chandramn
Contributor
Contributor
Jump to solution

SRM 6.1 Recovery for Stretched storage executes Prepare storage step twice

Hi

This query is regarding SRM 6.1 recovery workflow (failover) for stretched storage using SRA. (Policy based replication using Storage array adapter)

Failover Workflow report of SRM indicates issuing of SRM command preparefailover twice to SRA running at Protected site

one after the step "Suspend non-critical VMs at recovery site for live migration"

     4. Prepare stretched storage for VM migration at protected site

           4.1.2. Prepare stretched storage consistency groups for VM migration at protected site

another one after step "Unregister VMs at protected site"

14. Prepare storage for migration at protected site

     14.1.2. Prepare storage consistency groups at protected site for migration

What is the difference and workings between step 4.1.2  and Step 14.1.2

Again in unplanned Failover, Step 4 will be skipped, but Step 14 will be executed. Please explain

Thanks

Chandra

0 Kudos
1 Solution

Accepted Solutions
vbrowncoat
Expert
Expert
Jump to solution

Step 4 is specific to stretched storage.

Step 14 is for all other non stretched storage

The reason you only see these uses in a planned failover with stretched storage is that is the only situation where stretched storage (cross-vCenter vMotion) will be utilized. During a disaster recovery workflow VMs will be powered down at the protected site and powered on at the recovery site as in any other recovery workflow.

View solution in original post

0 Kudos
1 Reply
vbrowncoat
Expert
Expert
Jump to solution

Step 4 is specific to stretched storage.

Step 14 is for all other non stretched storage

The reason you only see these uses in a planned failover with stretched storage is that is the only situation where stretched storage (cross-vCenter vMotion) will be utilized. During a disaster recovery workflow VMs will be powered down at the protected site and powered on at the recovery site as in any other recovery workflow.

0 Kudos