Hey @Fernando Souza !  I’m only seeing a screenshot from your CS DR copy (which is small).

I’m assuming you need to add a mount path to your main Storage Policy.

This document shows how to create a library and mount path:

https://documentation.commvault.com/11.23/expert/9299_disk_libraries_getting_started.html

Check out this link for setting up spare mount paths you can migrate in as needed:

https://documentation.commvault.com/11.23/expert/9312_spare_mount_path_provisioning_and_migration.html

Hi @Fernando Souza 

For CommserveDR storage policy, Deduplication is disabled.

If you’re in a DR scenario and needing to restore this data as the Commserve has been lost, deduplication and DDB interaction would make restore very problematic, so CommserveDR storage policy is not deduplicated.

You can still add further mount paths across multiple MAs, as I can see you have already done for CommserveDR policy.

For other deduplicated storage policies, it should be a similar task with DDB consideration.

Deduplication Building Block Guide - Datapaths explains how multiple data paths can be used.

If you are load balancing datapaths between MAs, either for load or resiliency, I suggest you also consider multiple DDB partitions for the same reasons:
Configuring Additional Partitions for a Deduplication Database

Thanks,

Stuart

Hello @Mike Struening 
Sorry for taking too long to answer, i was in a client.

and i talked to a co-worker who did the implementation of this Commvault and he indicated to just add the MA to do load balance, not to create new DDBs (Just partition the DDB) and mount path, because it´s not necessary.

Then i´m just going to add spare mount path and DDB with Round Robin.
(the DDB don´t need new space).

If one MA fails, i will have another one to replace.

and generate Forecast before and after MA addition and pass to the cliente the new report.

And what do you think @Stuart Painter ?

Hi @Fernando Souza 

If you are simply adding a new MA for load balancing and to spread the load, Data Retention Forecast and Compliance Report will show you where you have data within retention and ready for pruning.

Disk Library Utilization Report may also help show which libraries are most used and might benefit from load balance.

Thanks,

Stuart