Skip to main content
Solved

Veeam Backup Server Placement

NemanjaJanicic
Forum|alt.badge.img+1

Me again with new topic šŸ˜

At the moment our VBR Server is located on the Hyper-V Host where are also the 50% of VMs that we are backing up.
 

Without Using Off-Host proxies I can guess that all load will come to Hyper-V host which is hosting VMs and VBR also.
I guess that data movers from source VM and VBR are run on the Hyper-V host itself.

What would be the best practice for placement of VBR?
Is it good idea then to isolate it from the VMs that we are backing up or?
I can host it on some Hyper-V Host which doesnā€™t have productive VMs or any

Also then our off-host backup proxy should be physical machine or somewhere where we also dont have anything?

Best answer by Moustafa_Hindawi

Hello @NemanjaJanicic 

It is better to place VBR out of Hyber-V if you have only single host, that is for disaster recovery.

For Off-Host proxy, it should be physical, creating off-host proxy virtual is not a good idea (Hyper-V nested inside another hypervisor), because off-host proxy must be a windows server with Hyper-V role installed.

View original
    Did this topic help you find an answer to your question?

    3 comments

    coolsport00
    Forum|alt.badge.img+20
    • coolsport00
    • Veeam Legend
    • 4187 comments
    • November 11, 2023

    @NemanjaJanicic -- the BP Guide and link I provided in your previous post discuss HV On/Off Proxy decision based off pros/cons...did you read it? They generally recommend on-host unless thereā€™s some dire need to have off-host. The Guide also talks about VBR placement , generally to be placed in the main DC alongside the infrastructure backing up.

    Choosing between physical vs virtual Proxy depends mostly the transport mode you wanna go with - DirectStorage (SAN/NFS) or hotadd. You canā€™t go wrong with either tbh.

    Hope that helps.

    Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
    Chris.Childerhose
    HangTen416
    2 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • HangTen416
      HangTen416
    Moustafa_Hindawi
    Forum|alt.badge.img+6

    Hello @NemanjaJanicic 

    It is better to place VBR out of Hyber-V if you have only single host, that is for disaster recovery.

    For Off-Host proxy, it should be physical, creating off-host proxy virtual is not a good idea (Hyper-V nested inside another hypervisor), because off-host proxy must be a windows server with Hyper-V role installed.

    Moustafa Hindawi | Blogger | Nutanix Technology Champion | NCSE | NCM-MCI | VMCE | 2xVCAP-DTM & DCV | 2xVCP-NV & CMA | LinkedIn: https://www.linkedin.com/in/moustafaadelmoustafa/ | My Blog: https://cloudwhales.co.uk/author/mhindawi/
    DChiavari
    Forum|alt.badge.img+7
    • DChiavari
    • Veeam MVP
    • 55 comments
    • November 12, 2023

    For Hyper-V I usually recommend to use On-Host backup, because ā€œit just worksā€ šŸ˜€ Off-Host is great if you want to completely offload operations from your Hyper-V cluster, but in my experience, itā€™s usually more trouble than itā€™s worthā€¦ thereā€™s a lot of rather strict requirements.

    One important difference in Hyper-V, compared to vSphere, itā€™s that by default *all hosts* of the Hyper-V cluster are used as Data Movers (source proxies)ā€¦ not the VBR server, not (only) the Hyper-V host it runs on (if itā€™s a Hyper-V VM, just like your case).

    So you also get better / more even load distribution. If your hosts are generally not super loaded CPU-wise, I would definitely recommend using On-Host backup.

     

    Danilo Chiavari - Veeam Sr. Presales Manager, Italy - www.danilochiavari.com
    Iams3le
    1 person likes this
    • Iams3le
      Iams3le

    Comment


    Terms & Conditions