What Triggers the Automatic Installation of Storage Accelerator?

Hi, hope you’re doing well.

I believe in 11.26 and above, the Storage Accelerator package is automatically pushed out as a means to circumvent MediaAgent servers where possible (if the backup can be taken from the client/source directly). There is even a setting which dictates this behaviour.

Source: https://documentation.commvault.com/2024e/expert/media_management_configuration_service_configuration.html (Refer to Auto push install storage accelerator package)

This only applies to greenfield environments. Existing environments who were originally setup in11.25 or prior it remains disabled. 

Yes, this is referenced in the documentation source.

It has led to a lot of confusion as I don’t believe the communication regarding Storage Accelerator, its purpose and its features were explicit. It does serve a purpose but we have had instances where it has caused unintended errors and configuration issues with some environments in the past.

Yes, and I can understand why as it is a hidden gem that fundamentally changes the way how the data is send across the wire to the backend storage. The feature itself is unique, but it is so hidden in terms of visibility and it is lacking capabilities to perform tests from Command Center. 

Hi ​@Jon Vengust, thanks for the response.

I can confirm that the CommServe was setup well before Version 11, and that the “Auto push install storage accelerator package” is set to 0. (Sorry, I should have put that in the original post).

So, flipping it from 0 → 1 should solve your question. 

Except I am trying to disable the behaviour. 

So, even though the install.log refers to it is it actually installed on the client? Disabling SA can also be achieved using a key https://documentation.commvault.com/v11/expert/enabling_or_disabling_storage_accelerator.html

Hey Onno, the user is selecting the File System and SQL Agents, however the Storage Accelerator Package is being installed as a “required package”. I want to understand the underlying logic, as it doesn’t seem to occur for every client, and I would like to avoid having to manually disable Storage Accelerator.

I have also noticed this behaviour because for every new client the backup jobs generate error events as the cloud storage is not accessible for clients in our environment.

The Media Management setting is set to 0 for a while now, but the Storage Accelerator is installed nevertheless for every new client.

I did also try setting the “Auto push install storage accelerator package” additional setting to 0, but this did not help either.

So if there is a solution/fix for that issue I would also be interested.