In the SRDF/AR Single Hop scenario illustrated above, the Source site has become unavailable. All BCV pairs where spilt at the time of failure, and the Source R1-BCV to Target R2 synchronization was incomplete. Restarting the application at the Target site is required, but an additional clean copy of the data must be maintained in case of corruption during the restart procedure. How would this restart objective be accomplished?

A.
Check for device locks on the Target site BCV devices. Suspend RDF links and Write-enable the BCV devices. Import Volume Groups, mount Filesystems and restart application form the Target site BCV device

B.
Check for device locks on the Target site R2 and BCV devices. Suspend RDF links and Write-enable the R2 devices. Perform an incremental Establish from the Target site R2 to the BCV. Wait for synchronization to complete and then Split the Target site R2 and BCV. Import Volume Groups, mount Filesystmes and restart application from the R2 devices.

C.
Check for device locks on the Target site R2 and BCV devices. Suspend RDF links and Write-enable the R2 devices. Perform an incremental Establish from the Target site R2 to the BCV. Import Volume Groups, mount Filesystems and restart application from the R2 devices.

D.
Check for device locks on the Target site R2 and BCV devices. Suspend RDF links and Write-enable the R2 devices. Perform an incremental Restore from the Target site BCV to the R2. Import Volume Groups, mount Filesystmes and restart application from the R2 devices.

E.
Check for the device locks on the Target site R2 and BCV devices. Suspend RDF links and Write-enable the R2 devices. Perform an incremental Restore from the Target BCV to the R2. Wait for synchronization to complete and then Split the Target BCV and R2. Import Volume Groups, mount Filesystems and restart application from the R2 devices.