Skip to main content
Solved

Network Segmentation - VB365

  • April 16, 2025
  • 3 comments
  • 52 views

I am currently going through the network segmentation best practices (Segmentation | Veeam Backup & Replication Security Best Practice Guide) and I’m wondering where would be the best zone to place my VB365 server.  Part of me thinks Management since it’s a backup server, and part of me thinks Restricted since I am backing up to a local disk.

Anyone care to share their thoughts?

Thanks!

Best answer by Chris.Childerhose

Typically you would place the VB365 server in the MGMT zone the same as the VBR server, but you can place it in the Restricted zone due to the local storage if you like.  You just need to ensure all the components that need to talk to each can via FW ports, VLANs, etc.

This is all subjective as there is not one right answer.

3 comments

lukas.k
Forum|alt.badge.img+12
  • Veeam Vanguard
  • 357 comments
  • April 16, 2025

Hi ​@stryker54141,

I recommend putting you VB365 server in a separated network / VLAN since it has internet access and the backed up data can be taken as critical data.

There was a presentation on that topic (hardening best practices) that includes network segmentation and hardening.

Event Recap: Veeam Hardening Best Practices (March 19, 2025) | Veeam Community Resource Hub

 

Hope that helps! In case of furher questions just ask. :-)

Lukas


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 9539 comments
  • Answer
  • April 16, 2025

Typically you would place the VB365 server in the MGMT zone the same as the VBR server, but you can place it in the Restricted zone due to the local storage if you like.  You just need to ensure all the components that need to talk to each can via FW ports, VLANs, etc.

This is all subjective as there is not one right answer.


  • Author
  • Comes here often
  • 16 comments
  • April 16, 2025

Thank you both for your responses!

@lukas.k - Thanks for sending that link.  I missed that video but will watch it now!