- Posts: 387
- Liked: 95 times
- Joined: Mar 24, 2010 5:47 pm
- Full Name: Larry Walker
1) delete the replicate job
2) did a move of the files to get them out of the Veeam backup folder. ( whats the best way to do this when they are staying on the same disk) using VC this took an hour. Didn’t want to edit the files, writing DR steps and the less manual steps the better.
3) deleted the replicas from the Veeam main screen, under replicas.
I think I am good to go, am ?
All the steps for DR testing are well documented in the user manual. I am just the sure when we know we are never going back.
Our only issue in our testing so far was that the DR remote site veeam server needs to pull the VMs and not have the main site veeam server put the VMs on the DR sites ESX SAN. By us putting the VM on the remote site when the main site is gone we can't use the failover wizzid. live and learn.
- Product Manager
- Posts: 24711
- Liked: 2045 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
Yes, you're good to go!
If you want to use the replicated VM as the main one you can just simply start it using vSphere Client and that's it! And yes, you should remove replication job from the Veeam console. Actually you don't have to move anything from the Veeam backup folder on the ESX(i) hosts, but you can do that using FastSCP functionality.
By the way, you can always backup your Veeam SQL DB and use it with the fresh install on any site. It will give you a possibility to use a failover wizard.
Also please note that you've failed over to a replicated VM using failover wizard, and not going to undo failover, don't forget to delete a Veeam snapshot (using Snapshot Manager) that is created to protect replicated VM from user changes.
Hope it helps!
Users browsing this forum: Google [Bot] and 84 guests