Here are four resources on Microsoft Server Hyper-V. Yeah, it’s a big deal.
A Hyper-V & Veeam Happy Ending from Spiceworks
— Veeam® Software (@veeam) April 17, 2014
I also wanted to remind you that Veeam Backup & Replication for Hyper-V only became compatible with Microsoft Hyper-V 2012 R2 after the update R2. My bonus tip here is to suggest that you go here http://www.veeam.com/kb1831, then click “main menu,” ”help,” and “about” to make sure you have an up-to-date version (should be build 220.127.116.111 or newer).
I decided to write this series of posts that I think they might be helpful at least to do the brainstorm to find the best approach for every particular scenario. The reality is that each environment is different and use different hardware, but at least I can help you identify 5 common scenarios on how to squeeze the performance of your hardware.
Now it is the “Hyper-V Integration Services Shadow Copy Provider” that is being used. When the the host initiates a volume snapshot (Microsoft or hardware VSS provider) the host VSS writer goes in to freeze. This process leverages the Hyper-V Integration Services Shadow Copy Provider to create the virtual machine checkpoint. After that the volume/LUN/CSV snapshot is taken. When that is done the host VSS writes goes into thaw and the virtual machine checkpoint is deleted. After that the backup runs against the Volume snapshot and at the end that is also deleted. You can follow this process quite nicely in the GUI of your Hyper-V host, you SAN (if you use a Hardware VSS provider)