RecoverPoint and VMWare SRM

Hello,

I am currently testing VMware SRM with RP SRA and facing some issues.

I was able to successfully create a PG and a recovery plan using RP array based replication.

When i am testing the recovery plan , all steps pass till Create Wrietable Storage Snapshot.

Error seen is :

4. Create Writeable Storage SnapshotError - Failed to recover datastore 'SRM-Vol-6083'. VMFS volume residing on recovered devices '"60:06:01:60:09:40:33:00:0B:D2:BB:00:32:DB:E3:11"' cannot be found.2014-05-15 12:49:48 (UTC 0)2014-05-15 12:51:37 (UTC 0)
4.1. Protection Group PG-SRMVOLError - Failed to recover datastore 'SRM-Vol-6083'. VMFS volume residing on recovered devices '"60:06:01:60:09:40:33:00:0B:D2:BB:00:32:DB:E3:11"' cannot be found.2014-05-15 12:49:48 (UTC 0)2014-05-15 12:51:37 (UTC 0)

i have ensured that the target lun with the above WWN has been presented to target/recovery ESX host.

Also when i manually try to mount that device as a datastore on my recovery ESX , i also face an error -

Call "HostDatastoreSystem.CreateVmfsDatastore" for object "datastoreSystem-228" on vCenter Server "LGLW0250" failed.

So basically unable to mount the target lun as a data store.

Please advise. Any suggestions will be very useful. i have tried several things , but nothing worked so far.

Thanks a lot .

Reply
6 Replies
Highlighted
pinnas
3 Argentium

Re: RecoverPoint and VMWare SRM

You may refer to KB article "184265 "  

Reply
Highlighted
etaljic81
4 Tellurium

Re: RecoverPoint and VMWare SRM

Did you enabled SRM for the CG and set it to be managed by SRM?

Reply
Highlighted

Re: RecoverPoint and VMWare SRM

Thanks Suman and Ernes. i was able to overcome that error and make progress.

However , i am stuck in this step now :

Change Recovery Site Storage to WriteableError - Failed to promote replica devices. Timed out (300 seconds) while waiting for SRA to complete 'failover' command.2014-05-15 16:01:22 (UTC 0)2014-05-15 16:06:23 (UTC 0)
8.1. Protection Group PG-SRM-Vol-50GBError - Failed to promote replica devices. Timed out (300 seconds) while waiting for SRA to complete 'failover' command.2014-05-15 16:01:22 (UTC 0)2014-05-15 16:06:23 (UTC 0)

i also changed the timeout value to 1800 to give more time but it is still failing. it is not able to cross this step.

Any idea ? Please advise.

Thanks a lot.

Reply
Highlighted
forshr
4 Tellurium

Re: RecoverPoint and VMWare SRM

Hi Ramya,

One of the more common reason for this behaviour is the amount of journal lag on a CG(s) prior to invoking any recovery mode activity with SRM. Without VSI integration (available at RP 4.0), SRM will create its own bookmark which will be queued and dependent on data lag, journal lag and the distribution process.

Please check this and let me know if this is an issue.

Regards,

Rich Forshaw

Consultant Corporate Systems Engineer - RecoverPoint & VPLEX (EMEA)

Data Protection & Availability Division

Reply
Highlighted

Re: RecoverPoint and VMWare SRM

Thanks Rich.

I suspect that maybe the issue , not sure though.

However , is there a way to fix this? Any work around , so i can successfully peform the recovery?

Thanks,

Ramya

Reply
Highlighted
forshr
4 Tellurium

Re: RecoverPoint and VMWare SRM

If it is excessive journal lag then you may have insufficient numbers of disk for your journal to faciliate faster distribution.

Reply