-
- Enthusiast
- Posts: 76
- Liked: 8 times
- Joined: Jun 08, 2013 10:52 am
- Full Name: Peter Howarth
- Contact:
Migration after/during Instant Recovery
Hi.
Having just deployed Veeam over the weekend, I did a test InstantRecovery of a small rarely-used VM to understand the basic process last night.
It worked great in mounting it to our ESX environment. The statistics panel logging then stopped at 'Waiting for user to migrate'.
I'm not sure what options I found, but I somehow initiated a Migration job which successfully migrated the disks of the InstantRecovered VM to the live datastores. However the InstantRecovery job was still running, so I stopped it. The statistics panel logs then gave me a warning about the data files having already been migrated? Shouldn't the InstantRecovery provide a method to migrate it's data to the live environment in the background once the DR disaster has been resolved?
What is the correct process for migrating a machine which has been InstantRecovered, say if our SAN dies and we have to order a new one - we'd InstantRecover the servers via NFS and continue using them, but then want to migrate the data onto the new SAN when it arrives?
Cheers,
Peter
Having just deployed Veeam over the weekend, I did a test InstantRecovery of a small rarely-used VM to understand the basic process last night.
It worked great in mounting it to our ESX environment. The statistics panel logging then stopped at 'Waiting for user to migrate'.
I'm not sure what options I found, but I somehow initiated a Migration job which successfully migrated the disks of the InstantRecovered VM to the live datastores. However the InstantRecovery job was still running, so I stopped it. The statistics panel logs then gave me a warning about the data files having already been migrated? Shouldn't the InstantRecovery provide a method to migrate it's data to the live environment in the background once the DR disaster has been resolved?
What is the correct process for migrating a machine which has been InstantRecovered, say if our SAN dies and we have to order a new one - we'd InstantRecover the servers via NFS and continue using them, but then want to migrate the data onto the new SAN when it arrives?
Cheers,
Peter
-
- Product Manager
- Posts: 20108
- Liked: 2209 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Migration after/during Instant Recovery
In fact, instantly recovered VMs can be migrated back to production in different ways:What is the correct process for migrating a machine which has been InstantRecovered?
• vMotion (via vSphere Client)
• If for some reason you can’t utilize vMotion functionality, you can still put into use VB&R Quick Migration mechanism.
Either of methods should work fine.
Hope this helps.
Thanks.
-
- Enthusiast
- Posts: 76
- Liked: 8 times
- Joined: Jun 08, 2013 10:52 am
- Full Name: Peter Howarth
- Contact:
Re: Migration after/during Instant Recovery
Hi Vladimir,
So the warning we get in the statistics panel when stopping the Instant Recovered session isn't something we need to worry about?
Peter
So the warning we get in the statistics panel when stopping the Instant Recovered session isn't something we need to worry about?
Peter
-
- Product Manager
- Posts: 20108
- Liked: 2209 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Migration after/during Instant Recovery
Hi, Peter.
Are talking about “VM was moved or migrated” warning?
Providing that you’ve successfully migrated VM back to production through one the above mentioned options, you can manually stop publishing instantly recovered VM without any issues.
Thanks.
Are talking about “VM was moved or migrated” warning?
Providing that you’ve successfully migrated VM back to production through one the above mentioned options, you can manually stop publishing instantly recovered VM without any issues.
Thanks.
-
- Enthusiast
- Posts: 76
- Liked: 8 times
- Joined: Jun 08, 2013 10:52 am
- Full Name: Peter Howarth
- Contact:
Re: Migration after/during Instant Recovery
Thanks - yes, I think that's what the error said.
(Veeam is currently offline for some maintenance so I can't check it)
Peter
(Veeam is currently offline for some maintenance so I can't check it)
Peter
-
- Product Manager
- Posts: 20108
- Liked: 2209 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Migration after/during Instant Recovery
In order to understand whether a given VM has been migrated successfully or not you can go to the “History” node and take a look at the corresponding “Quick Migration” session. There you can also get information regarding migration type that has been used (Quick Migration/vMotion).
Hope this helps.
Thanks.
Hope this helps.
Thanks.
Who is online
Users browsing this forum: Bing [Bot] and 90 guests