I am working on a situation where the Hyper-V backups are at one location and the VMware Hosts are at another location.
Instant restore and then sVmotion over the WAN is proving to be far too slow.
I am considering Instant Restore at the location where the backup files are and then replication from the instant restore to the target over the WAN?
Question is, should I sVmotion IR to prod storage before replication, or replicate right off of the IR on repo?
THX,
-JB
-
- Service Provider
- Posts: 235
- Liked: 40 times
- Joined: Mar 08, 2010 4:05 pm
- Full Name: John Borhek
- Contact:
Instant restore from Hyper-V to VMware over the WAN
John Borhek, Solutions Architect
https://vmsources.com
https://vmsources.com
-
- Veeam Software
- Posts: 2648
- Liked: 614 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Instant restore from Hyper-V to VMware over the WAN
Hi John,
> Question is, should I sVmotion IR to prod storage before replication, or replicate right off of the IR on repo?
Migrate to production first will likely produce better results. As I see it, without migrate to production first, the situation is still the same: Instant Recovery + copy over WAN, just the instant recovery process is isolated to one site.
Do you have space for backup copies at the VMware location? I think the most ideal solution would be to do backup copies to the VMware location and then initiate restores from those backup copies -- with backup copy seeding, link speed should not be as significant of a factor, so if the space is available consider this option.
> Question is, should I sVmotion IR to prod storage before replication, or replicate right off of the IR on repo?
Migrate to production first will likely produce better results. As I see it, without migrate to production first, the situation is still the same: Instant Recovery + copy over WAN, just the instant recovery process is isolated to one site.
Do you have space for backup copies at the VMware location? I think the most ideal solution would be to do backup copies to the VMware location and then initiate restores from those backup copies -- with backup copy seeding, link speed should not be as significant of a factor, so if the space is available consider this option.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: Amazon [Bot] and 42 guests