Since I posted previously about the SureReplica jobs now running as expected in the DR environment (after the recommendation above about correcting the settings to use DR networks for mappings and production IPs for vNIC configs), I am also on the production site setting up a SureBackup virtual lab to test restore Veeam backups of VMs also from multiple production networks. This is resulting in the same errors as my initial problem, e.g.
"4/10/2025 1:01:11 PM Warning Network 1: production x.x.x.x%2f26-v828, isolated unknown, not mapped"
I made sure to configure the SureBackup's virtual lab so that the 7 vNICs are mapping 7 production networks to isolated networks, with unused VLAN IDs, and then in the Network Settings step each of those vNICs are set with IPs coinciding with the production network gateway IP, prod subnet mask, and some masquerade IP from private network spaces. Back in the mapping step, my selection of production networks are taken directly from browsing the specific ESX host which the lab and proxy are configured to use for bringing up VMs. I have verified that the selected host has the 7 isolated networks available.
When I run the job, I monitor the restored VMs in the lab and see that when they are registered, their NICs do have the correctly assigned isolated network named port group. However once power on of the restored VM commences, the NIC loses that port group assignment and the "isolated unknown, not mapped" errors pop up in the job for each VM being tested.
Anything else I'm missing with the lab config?
"4/10/2025 1:01:11 PM Warning Network 1: production x.x.x.x%2f26-v828, isolated unknown, not mapped"
I made sure to configure the SureBackup's virtual lab so that the 7 vNICs are mapping 7 production networks to isolated networks, with unused VLAN IDs, and then in the Network Settings step each of those vNICs are set with IPs coinciding with the production network gateway IP, prod subnet mask, and some masquerade IP from private network spaces. Back in the mapping step, my selection of production networks are taken directly from browsing the specific ESX host which the lab and proxy are configured to use for bringing up VMs. I have verified that the selected host has the 7 isolated networks available.
When I run the job, I monitor the restored VMs in the lab and see that when they are registered, their NICs do have the correctly assigned isolated network named port group. However once power on of the restored VM commences, the NIC loses that port group assignment and the "isolated unknown, not mapped" errors pop up in the job for each VM being tested.
Anything else I'm missing with the lab config?
Statistics: Posted by joebranca — Apr 10, 2025 8:40 pm
