freddieleatham wrote:Thanks for the quick reply!
What happens if I failover manually. I would like my tests to not depend on the Veeam infrastructure so I ssh onto the DR esx, create snapshots of all the machines, then power them on. If this is a basic DR test I will stop the machines and revert the snapshots, but if users are involved I will need to failback the VMs.
Is this possible? Or is it perhaps sensible to use the Veeam infrastructure for tests where I need to failback and only do manual ones where I can discard the delta?
freddieleatham wrote:Is this possible? Or is it perhaps sensible to use the Veeam infrastructure for tests where I need to failback and only do manual ones where I can discard the delta?
Gostev wrote:Actually, no - the changes will not be overwritten. This is due to how snapshot tree works in VMware - the changes you've made will be kept intact in the corresponding snapshot that VMware will automatically create once you start the VM on any existing restore point (to protect said restore point snapshot, since VMware wants you to be able to go back to it). You will be able to return to this state at any time later, until you remove this snapshot tree point manually - it is very important to remember to do this, since Veeam's retention will only manage its own restore point snapshots. If you don't remove the snapshot, it may eventually grow to the size of the corresponding VMDK file.
james575 wrote:I do not want/care about changes made to the replica during the testing phase. When I am done testing it, I want to power it down and have the replication job continue as normal. Should I then go into vSphere and delete the most recent snapshot on the replica?
Users browsing this forum: Sixela and 65 guests