Setup: I have primary and secondary storage locations. Data gets copied from primary to secondary with Aux copies. I have 3 Aux copies that are not tied to global deduplication DDB’s and are instead “using their own DDB” for the Aux copy to the secondary). I’m Looking to add more mount points to my media agents (to add more storage capacity) and I ran across this (copilot answer to “To determine whether a library is part of a Network Storage Pool in Commvault”):
- A Network Storage Pool is a logical construct that combines:
- A Disk Library.
- One or more MediaAgents.
- A Global Deduplication Policy.
- When configured, it enables shared access to mount paths across MediaAgents using DataServer-IP transport
My question is: If these Storage policies Aux copy are not tied to a global DDB, then its not part of a Storage pool (this appears to be the case when looking at Storage resources → storage pools as I can see only the Global DDB’s in the pools)? and if so if I add new mount paths to add storage space… will these Aux copies that have their own DDB’s “automatically use those new mount points”? In the storage policy copy properties → data path configuration → for these Aux copies, it has “automatically add new data path” selected… so I’m not sure if it will actually do this ‘completely automatically” or if I have to treat these in some special way/make manual changes after adding the new mount point.
