We are beginning our SRM design/deployment and I am hoping that what I am asking is a dumb question, but even if it is I cannot find an appropriate answer.
All of our production data is on an N-Series 6040 and is being mirrored to another 6040 at another site.
We aim to use SRM to move all the VMs to this second site as well, in the event of a disaster. As far as we can see, SRM takes care of breaking the replication relationships and mounting the mirrored datastores at the other site on the ESX cluster and will bring up the VMs. This seems all fine when the data these VMs use is also in the VM environment, i.e. in VMDK files etc.
My issue is what about the CIFS shares and NFS mounts that are not controlled by VMware. They have been replicated to the other site but the filer IP addresses are different and the mirrored volumes were not necessarilly even called the same thing - I have gone through and renamed all the mirrors ( DFPM's conventions make the names all different :-).
It would seem that we will need to add some scripting to break these mirrors so that the volumes can be mounted but how do we get the VM to mount them ?
I am hoping this is a scenario that is common and there is a well-known solution/process. What are others doing with SRM ?
The other but similar issue is with database ODBC connectors. Our SQL cluster and is failover partner are still on physical hardware ( the LUNs are on N-Series hardware ). The VMs once moved with SRM need to access databases that are on a different server.
Any suggestions or pointers to appropriate literature much appreciated.