We had 2 physical servers and both running Windows 2012 R2 Server Standard.
We implemented the cross replication method between this 2 servers with NO SAN/NAS at all in between purely just disk on servers which the capacity can handle both servers.
Our servers as follow (as example):
- Physical01 server has VM01 and VM03
- Physical02 server has VM02 and VM04
This method of replication has been running for almost a year and it's been running ok.
This morning we had this situation where there is an electricty outage and set the shutdown/restart. We found that none of the VMs can't be restarted - something to do with VM state issue. After doing troubleshooting we end up kill of the replications instead.
End up running as follow:
- Physical01 server has VM03
- Physical02 server has VM01 (no replication has been setup as yet), VM02 and VM04
Due to all servers except VM01 are not considering a lot of update we managed to use original ones and delete the replication ones, now we are having a dilemma where VM01 (file server) are running on Physical02 as a replica at the moment and there is a data/file
has been changed SO what is the best way to handle this issue?
(1) We are thinking to Enable Replication on VM01 on Physical02 and delete VM01 on the Physical01 and run the replication. It means the data will replicate again to Physical01. Once the data has been replicated ... we could do remove the REPLICATION again
and then shutdown the VM01 and move data from \Replica Targets\ to \Virtual Machines and then change the path for Virtual Hard Disk in VM for Harddrive
... OR ...
(2) We do the latest VM backup of VM01 in Physical02 and restore under Physical01
What do you think? The first approach is good but NOT cleaner as such due the folder structure are messier. We had folders called \VirtualMachines (for virtual machines) and \ReplicaTargets (for VM replicata). Second approach not sure how long this will
be because it's involved backup and restore.
Waiting for your input.
Isadewa