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
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.
Testing failover with VMware vCenter / SRM and SQL on protected volume.