Best way to assign multiple MediaAgents to one StoreOnce in Commvault?

Question

Dear community,We are currently implementing HPE StoreOnce with two MediaAgents. At the moment, the same StoreOnce device shows up twice in Commvault (one entry per MediaAgent). Jobs are working, but for HA and load balancing, should best practice be to add StoreOnce as a single library/store and associate both MediaAgents, or keep separate StoreOnce entries per MediaAgent?Additionally, ideally we need to separate specific backup workloads (e.g., VM backups handled by MA1, database backups by MA2). What is the recommended configuration for both high availability and dedicated backup flows per MediaAgent?I found also this from from documentation, but I’m not sure if this is my case here. https://documentation.commvault.com/11.42/software/adding_additional_mediaagents_to_existing_hpe_storeonce_library.htmlWould appreciate input from anyone with similar experience. Best regards,Nikos

Pradeep · Answer

Hi ​@Nikos.Kyrm,When an HPE StoreOnce device appears twice once for each MediaAgent. this typically indicates that the library was configured separately on each MediaAgent, rather than being shared as a single library across multiple MediaAgents. This is not the intended configuration for a shared StoreOnce Catalyst library.Separate Configuration:If you add the StoreOnce library independently on each MediaAgent, Commvault treats each as a distinct library, even if they point to the same StoreOnce device.Correct Method:The correct approach is to configure the StoreOnce library once, then add additional MediaAgents to that existing library as shared access nodes.

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded