We have initiated vm instant recovery and migrated to production . The issue is that we have completed the Migration from vCenter instead of the Veeam console, we just wanted to confirm that we are able to hit stop publishing in the Veeam console without impacting the restored and migrated VM.
Please advise.
Best answer by wesmrt
Did you moved the VM to a production datastore via vMotion?
If so, it’s safe to hit stop publishing. You just need to make sure the VM is now running in a production datastore and not in the Veeam Repository mounted during the instant recovery.
+4Did you moved the VM to a production datastore via vMotion?
If so, it’s safe to hit stop publishing. You just need to make sure the VM is now running in a production datastore and not in the Veeam Repository mounted during the instant recovery.
+21Did you moved the VM to a production datastore via vMotion?
If so, it’s safe to hit stop publishing. You just need to make sure the VM is now running in a production datastore and not in the Veeam Repository mounted during the instant recovery.
Yes would agree with Wesley here as long as you moved it to another datastore other than the mounted one from the instant recovery you will be good. 👍🏼
Did you moved the VM to a production datastore via vMotion?
If so, it’s safe to hit stop publishing. You just need to make sure the VM is now running in a production datastore and not in the Veeam Repository mounted during the instant recovery.
Thanks for the reply In the vCenter console we powered off the instant restored VM and then moved it back into the production server compute and storage resource.
Did you moved the VM to a production datastore via vMotion?
If so, it’s safe to hit stop publishing. You just need to make sure the VM is now running in a production datastore and not in the Veeam Repository mounted during the instant recovery.
Thanks for the reply In the vCenter console we powered off the instant restored VM and then moved it back into the production server compute and storage resource.
If you click stop publishing now, will veeam stop it gracefully, as veeam is not aware of the migration, because it was done outside veeam?
+21Did you moved the VM to a production datastore via vMotion?
If so, it’s safe to hit stop publishing. You just need to make sure the VM is now running in a production datastore and not in the Veeam Repository mounted during the instant recovery.
Thanks for the reply In the vCenter console we powered off the instant restored VM and then moved it back into the production server compute and storage resource.
If you click stop publishing now, will veeam stop it gracefully, as veeam is not aware of the migration, because it was done outside veeam?
It should or will realize not there now and just stop. As long as your VM is running in production you will be fine.
+12Did you moved the VM to a production datastore via vMotion?
If so, it’s safe to hit stop publishing. You just need to make sure the VM is now running in a production datastore and not in the Veeam Repository mounted during the instant recovery.
Thanks for the reply In the vCenter console we powered off the instant restored VM and then moved it back into the production server compute and storage resource.
just a question or hint: why did you powered off the system? You can migrate it via Storage vMotion when it’s powered on. Even if you have a vSphere Essentials+ License and normally no direct Storage vMotion function, it will work, when you select migrate both (compute and storage).
Did you moved the VM to a production datastore via vMotion?
If so, it’s safe to hit stop publishing. You just need to make sure the VM is now running in a production datastore and not in the Veeam Repository mounted during the instant recovery.
Thanks for the reply In the vCenter console we powered off the instant restored VM and then moved it back into the production server compute and storage resource.
If you click stop publishing now, will veeam stop it gracefully, as veeam is not aware of the migration, because it was done outside veeam?
It should or will realize not there now and just stop. As long as your VM is running in production you will be fine.
Thanks for the clarification
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
