This post is more than 5 years old
58 Posts
0
25728
July 29th, 2013 12:00
Testing failover with VMware vCenter / SRM and SQL on protected volume.
Ok, SRM working fine in test mode, although, we would like to test a failover/then a failback on the weekend...
We run SQL 2012 on a VM as well as vCenter/SRM on another VM, both on protected volumes.
If failover shuts down all VM's, makes a new replication then fires up VM's at DR site, would it fail because we had SQL and SRM on a protected volume? I can understand moving protected site vCenter / SRM VM to another volume but the SQL server is also used for other databases which we want protected. My guess is SRM is not smart enough to not shut down the SQL server last. What to do? What is everyone else doing?
Thanks in advance.
No Events found!
Origin3k
4 Operator
•
2.3K Posts
1
July 30th, 2013 07:00
You need a SRM and SRMDB on both sites. The SRM on the DR site will manage the whole process and not the vcenter/srm on the production site.
Btw. a Microsoft SQL Server 2008 Express (R2 SP1) - 64-bit is supportet for SRMDB. Check partnerweb.vmware.com/.../interop_matrix.php
Regards,
Joerg
vmbru
58 Posts
0
July 30th, 2013 06:00
Right, we have all that working. (vCenter/SRM at both sites and Linked mode, etc..)
Doing an SRM Test and Cleanup works fine, pretty snappy look/feel.
Although, we'd like to test a planned migration next then a failback, etc.. take it another level. The way the planned migration works/problem we face is... is that it powers off all your protected sites VM's. If the SQL server (where the SRM databse is) powers off, the whole thing would crash.
We think we'll have to bite the bullet and place MS SQL VM server that houses the protected site SRM database on a non-protected volume. We already placed vCenter/SRM VM on another non-SRM protected volume since DR site will have a vCenter anyway.
Our issue is we use other databases on that SQL server and would like it protected. Too bad SRM can't use a built-in local database SQL Express or maybe MySQL. Or better yet, VSM handles all these extra things we have to do to run a DR test. Oh well.
If any tips, please share.
Origin3k
4 Operator
•
2.3K Posts
0
July 30th, 2013 06:00
Yes, 2 vCenters are needed (but no Link Mode).
Regards,
Joerg
Dev Mgr
4 Operator
•
9.3K Posts
0
July 30th, 2013 06:00
I haven't worked a lot with SRM, but I thought that SRM required 2 vCenters; one at each site (linked together).
vmbru
58 Posts
0
July 30th, 2013 07:00
Right, we do.
>manage whole process
Even if planned migration started on vCenter at protected site? Or maybe I just need to run planned migration from DR site vCenter instead? That would make sense. Let me know if you confirm, then I can adjust our procedure.
Thanks for insight on SRM and SQL Express, that may be a lifesaver. Thanks.
vmbru
58 Posts
0
July 30th, 2013 12:00
Thanks Joerg, I was able to install SRM using a SQL 2008 Express database on both ends. Should be good now.