- Service Provider
- Posts: 63
- Liked: 1 time
- Joined: Mar 22, 2010 8:43 am
- Full Name: Andrew Singleton
I am in the process of doing a failover test and am a little confused as to the correct procedure for restoring a VM.
Our setups is 2 ESX hosts on a primary site, 1 ESX host on the DR site, these are connected by a fibre link. I am replicating 2 VM's to my DR site and keeping 10 rollback points for each.
In the event of site one being lost (Total loss - fire etc) My Physical Veeam server is at the DR site (is this a good/bad idea?) If i attempt to do a failover from the wizard I can see the Server and all my rollback points, however when i attempt to failover to it, I get an error about the Virtual Center server being unavailable, this makes sense since it no longer exists and failover fails.
How do i perform the failover if the VC is unavailable?
I have tested just powering on the VM's from a client and they come up fine, but they come up on the latest version (no options for a rollback point)
I though maybe I had to import the backups, but this kicks out an error "Unsupported storage version: "
Could anyone explain the correct procedure for this or is the VCenter server required in order to use a rollback option?
- SVP, Product Management
- Posts: 29346
- Liked: 5475 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
vCenter presence is obviously not necessary if you defined your replication job with source and target ESX added to Veeam Backup as standalone hosts. But with that way of configuring jobs, Veeam Backup looses VMotion support on source VMs.