How to use a AzureVM MABS to make a data backup for a AVS vm?

Question

Hello, i got a special network with my environment as follows：

AzureVM   
   MABS01.test.local   IP: 10.0.1.1
   Domain01.test.local  IP:10.0.1.5（domain controller and the DNS Server）
AVS
   test01.test.local      NIC1:10.0.2.1 metric:10 (production Network)
                          NIC2:10.0.3.1 meteric:100 (Backup Network)

The production network and the backup network is conneted with the 10.0.1.0/24 by the routing.

I want the Backup data be transfer on the Backup Network but not the production NetWork, what should i do?

Answer 1

Dear

Thank you for your feedback, this is not what you meant in your problem statement.

However, to your new question:

Step 1:

1. Add a DNS record in your domain controller to resolve the MABS server (MABS01.test.local) to the backup network's IP (10.0.3.1).
   • In the DNS Manager on Domain01.test.local:

     - Add a new A record for `MABS01.test.local` pointing to `10.0.3.1`.
     
     1. Ensure the DNS TTL is low during testing for quicker propagation.
     

Step 2:

1. On test01.test.local (AVS VM):
   • Download the DPM protection agent from the MABS console.
     • Install the agent, specifying the FQDN (MABS01.test.local). The agent will use the DNS settings configured in Step 1.
     1. Confirm successful installation and registration of the agent with the MABS server.

Step 3:

1. Set up static routes to prefer the backup network:
   • On test01.test.local, add a route to the MABS server:

      route add 10.0.1.1 mask 255.255.255.255 10.0.3.1 metric 1
   

   • This ensures backup traffic is routed through NIC2.
   1. Configure the firewall on both test01.test.local and MABS01.test.local:
      • Allow necessary ports (e.g., TCP 135, 5718, 5719, and 80) for traffic from 10.0.3.0/24 to 10.0.1.0/24.

Step 4:

1. Use packet capture tools like Wireshark or a network monitor to verify that traffic flows through the backup network during backup operations.
2. Run a test backup job and check the traffic path with:

netstat -an | find "10.0.3."

Hope this is helpful

Success.

Answer 2

Hello li_shouheng,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you would like to know how you can use a AzureVM MABS to make a data backup for a AVS vm.

To achieve your goal:

1. Use static routes to ensure traffic to the MABS server (10.0.1.1) is always routed via NIC2. For an example you can use CMD command: route add 10.0.1.1 mask 255.255.255.255 10.0.3.1 metric 1 and verify the route with: route print
2. This is an optional action because many backup systems do not rely solely on hostname resolution or metrics but use hardcoded settings or pre-configured IP routes. Modify the hosts file and NIC metrics alone will suffice: Edit the C:\Windows\System32\drivers\etc\hosts file to map MABS01.test.local to the IP on NIC2 (10.0.3.1): 10.0.3.1 MABS01.test.local
3. If MABS supports interface selection, configure it explicitly: In the MABS console, navigate to Protection Group Settings and look for network or interface preferences. Alternatively, consult MABS documentation for advanced configuration.
4. Verify that firewall rules on both AVS VM and MABS server should allow the following:
   1. TCP/UDP ports for DPM/MABS (default ports include TCP 135, 5718, 5719, and 80).
   2. Allow traffic between 10.0.3.0/24 (AVS backup network) and 10.0.1.0/24 (MABS).
5. Use your network monitoring tool or any similar tools to capture packets on both NIC1 and NIC2 to verify that backup traffic flows over NIC2. Alternatively, you can use netstat to check active connections during a backup operation for example: netstat -an | find "10.0.3."

Observe any requirements and try to read more on Azure Backup with MABS - https://learn.microsoft.com/en-us/azure/backup

I hope this is helpful! Do not hesitate to let me know if you have any other questions.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

Answer 3

Hello,

 

Thank you for posting in Q&A forum.

This issue could be caused by DHCP configuration:

Here are a few steps that we can try to troubleshoot and resolve the issue:

1.Configure a static IP instead of DHCP to identify if issue is caused by DHCP.

2.Check if DHCP function is working properly and assign IP address to the client properly.

3.Disable IPv6 to avoid conflicts and see if that resolves the issue.

4.Check if there's any firewall configuration that can block the network connection.

 

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.

 

Best regards，

Jill Zhou

 

---

If the Answer is helpful, please click "Accept Answer" and upvote it.