VMware Cloud Community
vmhelp201110141
Enthusiast
Enthusiast

VMware SRM 6.1 and IBM Storwize SRA 3.1 Issues

hello ,

We have sites,  all critical   VM's protected with VMware Srm + IBM SVC. During the  setup phase we did the fail-over and fail-back tests and everything works smooth.

Recently we had a storage  outage  and we lost the all the LUNs in primary location, then we have tried to recover the VM's  in secondary location using  SRM . unforunatly its not working with below error.

"The error is "Error failed to promote replicate devices. SRA command 'failover' failed. Invalid Array ID. Refer to IBM SAN Volume Controller troubleshooting Failed to promote replica devices. SRA command 'failover failed' Invalid Array ID. Refer to IBM SAN Volume Controller troubleshooting"


Sadly we have manually mount the LUN's to ESXi servers and started the VMs manually.


Does anyone seen the error  ?



The next step  was we have  built the SRM test environment  and did the following  tests..

1.  failover and failback tests  - the result  was success..

2.  deleting the LUN in primary location and recovering the VM from DR location . Unfortunately its failed with same as above SRA error.

.

How do we simulate the real disaster scenario with  SRM ?


"Like  deleting  the primary location VM lun and recover the VM from secondary site with SRM" is that right test case ?


Regards,

Surya







.

Surya
Reply
0 Kudos
3 Replies
vbrowncoat
Expert
Expert

If your SRA supports it you may be able to run a SRM recovery plan test with the network connection between your protected and recovery sites disconnected.

I would highly suggest taking your logs and working with IBM on this issue. SRM is designed to work regardless of whether or not the protected site is available. It would likely make sense to open a ticket with VMware as well but this looks to be primarily an issue with the IBM storage and their SRA.

Reply
0 Kudos
rcporto
Leadership
Leadership

Just to confirm, you're running the SVC in stretched cluster setup ? Or just two standalone IO Groups ?

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
Reply
0 Kudos
vmhelp201110141
Enthusiast
Enthusiast

Its two standalone IO Groups.

Surya
Reply
0 Kudos