Quantcast
Channel: Data Protection Manager - Hyper-V and CSV Clusters forum
Viewing all articles
Browse latest Browse all 575

DPM 2012 R2 UR3 HV backup behaivor

$
0
0

Hi,

I have a dedicated DPM 2012 R2 UR3 to backup VMs located in HV 2012 Cluster using Software VSS.

I have added a Backup NIC card on each HV host and connect them to a dedicated Switch where the DPM server is also connected to isolate backup traffic from the production.

Each HV node have a MGMT, SAN, HBeat and Backup Network.

I started to test backup one VM to see the DPM behavior and I noticed the following:-

Backup NIC on the HV nodes have no traffic. DPM triggered the agent to start VM backup. VM hosted nodes started to move data through the Backup NIC card. The strange thing is that the Hbeat NIC was transferring the exact same amount of data that the Backup NIC card was transferring. I checked the Backup NIC card and it was used by DPMRA which is perfect. When I checked the Hbeat NIC card it was used by “System”. The normal Hbeat traffic before starting the VM backup was 800 Kbps and the Backup NIC card was 0. When the VM backup started both the Backup and Hbeat NICs started to transfer about 200 Mbps each. The reason that im worried is there is a chance that the Hbeat NIC traffic might be used intensively during the backup which cause the Hbeat to fail to Contact the cluster causing the HV node to restart and you know the rest.

Questions:-

  1. Why the DPM is using the Hbeat?
  2. What is the data path when DPM agent trigger the backup of the VM? DPM Server – HV Node – Storage.
  3. Where does the VM snapshot saved? And how it works.

Just have several questions more but answering these will start a discussion J

Thanks in advance,

Laith


Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.



Viewing all articles
Browse latest Browse all 575

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>