Can I back up virtual machines that are hosted on an Azure Stack HCI cluster?
Yes.
What types of deployments are available in Hyper-V?
You can deploy virtual machines that are hosted on Windows servers and Microsoft Azure Stack HCI.
I removed data from my disks to optimize storage I use on Druva. I haven't added a file but I see a considerable change in Source+Data. What does it mean?
Druva detects a change even if you remove data from your disks. For example, Druva backed up 100 GB of data from your virtual machine. Later on, you removed 25 GB of data and Druva runs another backup for your virtual machine. The Source+Change section shows 125 GB because Druva detects a 25 GB modification on the virtual machine. However, you are not charged for 125 GB. You are charged only for the storage you consume. The Source+Change only shows a chart that indicates the data modified on your server.
How do I configure Druva to use third party VSS providers?
From the command prompt, run the following command:
vssadmin list providers
💡 TipRunning this command displays a list of VSS providers, and the provider IDs.
Stop the Enterprise Workloads agent service.
Open the Phoenix.cfg (For agent version prior to 7.0.0) / Config.yaml or HyperVConfig.yaml (For agent version 7.0.0 and later) file in a text editor.
The Phoenix.cfg (For agent version prior to 7.0.0) and Config.yaml or HyperVConfig.yaml (For agent version 7.0.0 and later) file is available at the following location:
For agent version prior to 7.0.0
C:\ProgramData\Phoenix
For agent version 7.0.0 and laterC:\ProgramData\Druva\EnterpriseWorkloads\Config.yamlC:\ProgramData\Druva\EnterpriseWorkloads\hyperv\HyperVConfig.yaml
Add the
VSS_PROVIDER_ID_VOLUMESparameter, and set its value to reflect the drives for which you want the Enterprise Workloads agent to recognize the third-party VSS provider that you configured.
Use the following format:
VSS_PROVIDER_ID_VOLUMES = {"<Drive>": "{<Provider ID>}", "Drive": "{<Provider ID>}"}
For example, if you want to set VSS providers for C drive, E drive, and the cluster shared volume, the parameter looks like the following:VSS_PROVIDER_ID_VOLUMES = { "C:\\" : "{b5946137-7b9f-4925-af80-51abd60b20d5}", "E:\\" : "{24602736-bed9-4619-91b0-243447c6409c}", "C:\\ClusterStorage\\Volume1\\" : "{b5946137-7b9f-4925-af80-51abd60b20d5}", }
❗ ImportantFor a clustered shared volume, add a double backslash (\\) at the end of the UNC path that you specify (as shown in the example above).
Save the Phoenix.cfg (for agent version prior to 7.0.0) / Config.yaml or HyperVConfig.yaml (for agent version 7.0.0 and later) file.
Start the Enterprise Workloads agent service.
Why is complete disk image uploaded when backing up VMs with dynamic disk
This is an expected behavior, the backup mechanism for Hyper-V uses resilient change tracking (RCT) and only uploads the allocated data. The remaining sparse blocks get uploaded only for the first backup and do not consume any storage. The data displayed under Current source on the dashboard displays the maximum size of the disk.
How does backing up a VM configured with Dynamic disk affect credit consumption?
Druva uploads data after normalizing as per 1MB block-size, only the allocated disk size would consume credits and not the sparse blocks.