Use this dialog box to view or modify the usage properties specified for the mount path of a cloud storage library.
Mount Path Allocation Policy
-
Maximum Allowed Writers
Specifies the maximum number of concurrent writers on the mount path.
-
Allocate No. of Writers
By default, maximum number of concurrent writers are allocated on the mount path. To limit the number of writers, type the number of concurrent writers that you want to allocate.
-
Disable mount path for new data
Specifies that the mount path will not be available for writing data. However read operations can be performed on the data available in the mount path. (If you wish to take the mount path offline, clear the Enable MountPath option in the General tab.)
Prevent data block references for new backups
When selected, the deduplicated blocks in the mount path will not be referenced when there are multiple mount paths in the library. (Choose this option if you plan to retire the mount path.)
Space Allocation
-
No Restriction
Specifies that there are no restrictions for writing data in the mount path.
Use this option to automatically adjust capacity, once in a day, based on usage. This will allow storage pools that gets used the most to automatically get more capacity.
-
Do not consume more than n GB
Specifies the total amount of space that can be used in the mount path. The system stops writing data when the specified space is met.
Use this option to restrict storage pools to a static capacity by setting a limit for each storage pool.
Enable Pruning of Aged Data
By default, pruning is enabled. To prevent pruning of aged data, clear the check box.
-
Enable Micro Pruning
When selected, for cloud storage configured with deduplication, data will be pruned from the cloud storage as soon as the backup jobs associated with that DDB meets the retention rules, without sealing the DDB.
Note
This option will not be available/applicable for cloud storage products that do not support micro pruning. See Supported Devices for a list.
-
Select MediaAgents for pruning aged data based on the associated copy's datapath
By default, pruning request is sent to any MediaAgent that has read and write access to the library, irrespective of whether the MediaAgent is part of the datapath or not.
Select this check box to send the pruning request to only those MediaAgents associated with the datapaths in the Storage Policy copy.
After the software deletes aged jobs, they are not available to view at the storage policy copy level. However, the aged jobs are still available to view from client level or subclient level until the job histories are not pruned.
For HPE StoreOnce Catalyst library, the pruning request must be set to the MediaAgent in which the library is configured, or a MediaAgent that can communicate with the device. This can be done using the SetDeviceControllerProps QScript. For more information on this Qscript, see SetDeviceControllerProps. (For information on configuring the HPE Catalyst Library, see Configuring a Catalyst Store as a Commvault HPE Catalyst Library.)