Skip to main content
Question

Hyper-V VM backups directly to Dell Data Domain using Storage Accelerator


Nikos.Kyrm
Community All Star
Forum|alt.badge.img+17

Hi everyone,


We are exploring the possibility of backing up Hyper-V VMs directly to Dell Data Domain using DD Boost, without routing the backup data through a MediaAgent.

The official documentation states that "Storage Accelerator is supported. You need to install Storage Accelerator and Storage Accelerator Add-on package on the clients." https://documentation.commvault.com/11.46/software/accelerating_backups_to_data_domain_boost_client_library.html
 

However, it is unclear whether this functionality is supported for Hyper-V backups at the hypervisor level.

Can anyone confirm whether Storage Accelerator supports client-direct backups of Hyper-V VMs to Dell Data Domain using DD Boost in Commvault 11.44? Are there any specific prerequisites or limitations?


Thanks in advance for your help!
Nikos

4 replies

Hi ​@Nikos.Kyrm , Storage Accelerator is supported with VSA yes, including Hyper-V, it’s not crystal clear on the docs yes, but it’s supported,

The Storage Accelerator and Storage Accelerator Add-on package can be installed on 64-bit Windows and Linux clients. (All the agents supported on Windows and Linux clients are supported.)

Accelerating Backups to Data Domain Boost Client Library

A media agent still needs to be on the library for DDB/Indexing just as any Storage Accelerator (SA) setup.

Thanks,

Abdu



Nikos.Kyrm
Community All Star
Forum|alt.badge.img+17
  • Author
  • Community All Star
  • October 27, 2026

Hi ​@AbdulRahman AlSindiony 

Thanks for the clarification!

Just to confirm, with Storage Accelerator enabled for Hyper-V VSA backups, the backup data is transferred directly from the Hyper-V nodes to the Data Domain, meaning that the backup processing and associated workload are handled by the Hyper-V nodes rather than the MediaAgent. Is that correct?

Thanks again!
Nikos


Yes Nikos, that’s correct, storage accelerator helps minimize the sizing for the MA, but the tradeoff is that the Hyper-V host will do more tasks and get more load.