Skip to main content
Solved

Hyper-V Backup Job Issue


Did this topic help you find an answer to your question?
Show first post

29 comments

coolsport00
Forum|alt.badge.img+20
  • Veeam Legend
  • 4139 comments
  • February 14, 2024

"The Hyper-V host was the proxy (on-host) which the VM is on. Had I used the VBR as the proxy then it would have been “off-host” and traffic would more than likely traverse the WAN. The repo is local to the Hyper-V host. After I got my initial backup, I was going to do backup copy to TX and then do instant recovery." <- I understand that, thus why (probably) your Agent job was traversing the WAN. My point was using a VM-based job with your on-host setup wouldn't 😊 My guess is you should then be good to go. Keep us posted. 


Forum|alt.badge.img+1
  • Author
  • Comes here often
  • 37 comments
  • Answer
  • February 19, 2024

We ended up not doing this, I had this idea instead, we brought up a small VM, migrated the SQL express DBs over to it, now it’s on VMware, and not on Hyper-V. Case closed.


coolsport00
Forum|alt.badge.img+20
  • Veeam Legend
  • 4139 comments
  • February 19, 2024

Great idea @jaceg23 . Glad you got it sorted.

 


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8492 comments
  • February 19, 2024

Very interesting solution and glad you solved it.


Comment