Hi there,Site Info
Prod: 3 x ESXi 5.5, Virtual vCenter, Physical Veeam/Proxy Server (V8)
DR: 3 x ESXi, Virtual Center, Physical Veeam/Proxy Server (V8)
Connectivity: Layer 2 stretched WAN - 50Mb (same subnet either end)
Due to a Prod SAN failure, we had to spin up our Exchange Server in our DR site, this worked fine.
Its a single Exchange 2010 with 3 VMware vdisks attached, totaling 565GB. Its now been running in DR for 2.5 days.
Last night I planned to failback, (the original VM was available and turned off in Prod site) hoping that overnight was long enough to get it done (it wasn't)
On the failback job, I was careful to select the correct Proxies for the two sites.
After 9hrs, I don't think it was halfway through - I would have left it going, but for Veeam had turned the Replica off, so Exchange was down for staff, so I had to cancel the failback.http://1drv.ms/1gOSxA1
I wasn't expecting the Replica Server to be off during the long copy back - this seemed different to the Veeam user guide pg150http://1drv.ms/1gOSOmu
1. Is there a way to failback with minimal Server downtime (I would expect/accept a small outage when doing final delta)
2. Is it a good idea to make the failover permanent, then setup a new, reverse replication job so the server can trickle back up to Prod (then do a new failover)