+1Hey,
I was wondering if the VSA Proxy on VMware could have a Storage Accelerator role, so it could write directly to, for example, Flash Blade S3? "So, read data using Hot-Add, then write it to the S3 bucket and send only the metadata to the Media Agent/DDB.
Best answer by Arvind
Good Day
No, the VSA Proxy in Commvault for VMware cannot function as a Storage Accelerator to write backup data directly to S3 object storage (such as Pure FlashBlade S3) while sending only metadata to the Media Agent/DDB.
Assuming that, you are using the VSA proxy just for VSA operations that is responsible for reading VM data from VMware environments using HotAdd, SAN, or NBD transport modes. It is not designed to write backup data directly to any storage target, including S3 object storage.
In Commvault’s architecture, the VSA Proxy reads the VM data and sends that data to a Media Agent. The Media Agent performs deduplication, compression, and all data movement operations required to write into S3-compatible storage, and Storage Accelerator is not supported on VSA Proxies for direct object storage writes. Its purpose is to optimize data transfer between clients and Media Agents, not to bypass the Media Agent layer or the DDB.
So, the VSA Proxy alone cannot bypass the Media Agent or DDB and write directly to S3 storage.
The supported workflow is:
VSA Proxy reads VM data → sends data to Media Agent → Media Agent performs dedupe/compression → Media Agent writes to S3
If required, the VSA Proxy host can also function as a Media Agent by installing the Media Agent package. In that configuration, the system can perform Storage Accelerator operations and write directly to the storage target because it is acting in the Media Agent role. However, the host will now be handling both VSA and Media Agent workloads, so it’s important to review and size the system appropriately to ensure it can support the combined responsibilities without performance impact.
Hope this helps with the information, let me know if any additional questions!
+5Good Day
No, the VSA Proxy in Commvault for VMware cannot function as a Storage Accelerator to write backup data directly to S3 object storage (such as Pure FlashBlade S3) while sending only metadata to the Media Agent/DDB.
Assuming that, you are using the VSA proxy just for VSA operations that is responsible for reading VM data from VMware environments using HotAdd, SAN, or NBD transport modes. It is not designed to write backup data directly to any storage target, including S3 object storage.
In Commvault’s architecture, the VSA Proxy reads the VM data and sends that data to a Media Agent. The Media Agent performs deduplication, compression, and all data movement operations required to write into S3-compatible storage, and Storage Accelerator is not supported on VSA Proxies for direct object storage writes. Its purpose is to optimize data transfer between clients and Media Agents, not to bypass the Media Agent layer or the DDB.
So, the VSA Proxy alone cannot bypass the Media Agent or DDB and write directly to S3 storage.
The supported workflow is:
VSA Proxy reads VM data → sends data to Media Agent → Media Agent performs dedupe/compression → Media Agent writes to S3
If required, the VSA Proxy host can also function as a Media Agent by installing the Media Agent package. In that configuration, the system can perform Storage Accelerator operations and write directly to the storage target because it is acting in the Media Agent role. However, the host will now be handling both VSA and Media Agent workloads, so it’s important to review and size the system appropriately to ensure it can support the combined responsibilities without performance impact.
Hope this helps with the information, let me know if any additional questions!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
