Skip to main content
  • EN

Many of my customers (luckily) are using Sure Backups. Some of the subnets are also quite small (i.e., smaller than /24). When configuring the network settings in the Virtual Lab wizard, there is a little problem which can easily be handled.

 

Veeam automatically inserts the appropriate letters for masking in the masquerading network.
For example, if you configure a /24 network, the wizard inserts a “D” in the fourth octet. This is correct and must be done this way.

 

The situation is different if the subnet is smaller. For example, if you have a /25 network and enter it in the wizard, the fourth octet of the masquerading network no longer displays a letter, but the number of the subnet mask.

 

To avoid this, simply click on the fourth octet of the masquerading network and enter a “0”. Then confirm with OK.

 

If you now reopen the configured network in the wizard via “Edit”, the “D” will now also appear here and the network can be used in the Virtual Lab.

Original post on my blog:

Veeam: Virtual Lab/Sure Backup with small subnets - petersvirtualworld.de

Hmm...I wasn’t aware of that behavior. Good to know...thanks for sharing ​@PeteSteven 👍🏻

Interesting behaviour for sure and I will need to play with Virtual Labs in my homelab since it is small and I can change the subnet.

Good to know! Most of us work within standard Class subnets and rarely need to consider classless inter-domain routing (CIDR notation). Thanks for sharing this valuable insight ​@PeteSteven! 

Hi ​@PeteSteven thanks for sharing amazing info i would love to test this. 

Good to know! Most of us work within standard Class subnets and rarely need to consider classless inter-domain routing (CIDR notation). Thanks for sharing this valuable insight ​@PeteSteven! 

Due to strict network segmentation, our customers often have very small networks, but many of them. Here, even with “only” 9 possible networks per virtual lab (a VM can have a maximum of 10 adapters, one of which is already used for the proxy appliance), we often reach the limit and have to build several labs.

Virtual Lab's network masquerading behavior may go unnoticed, but it's essential to ensuring correct routing in an isolated environment. I've encountered situations with subnets smaller than /24, and understanding how Veeam automatically inserts letters into the masquerading IP is helpful when fine-tuning SureBackup tests.

Hi ​@PeteSteven That’s why be a Community Member is valuable, I didn’t know that it was possible, always learning 🙂 Thank you

Comment


Terms & Conditions