Hi Community,Same environment as above: one CommServe at HO and 4 remote sites, each with its own on-prem MediaAgent and Disk Library (primary copy).Planned design:Primary copy: local Disk Library at each site (30-day retention). Secondary copy: Commvault Air Gap Protect (Azure), with extended retention of 3 years for Prod and 1 year for Non-Prod. Remote sites: direct internet (HTTPS 443) plus site-to-site VPN to HO.Questions:Once AGP is licensed and configured on the HO CommServe, can each remote site's MediaAgent be added as a data path and write the Aux Copy directly to AGP, without routing data through HO? Is any extra license or install needed on the remote MediaAgents for AGP, apart from opening outbound 443? What's the recommended approach: one shared AGP storage pool with all 5 MediaAgents as data paths, or a separate AGP storage per site, each with its own DDB on the local MediaAgent? We want to avoid DDB lookups over the WAN/VPN. MediaAgents added through a client group get Read access by default. Do we need to change it to Read/Write for each remote MediaAgent before running Aux Copy? Can one AGP subscription (capacity) be shared across all storages and sites in the same CommCell?Thanks in advance.

Question

Storage / Air Gap Protect Title: Can remote on-prem MediaAgents send Aux Copy directly to Air Gap Protect (AGP)?

Hi Community,

Same environment as above: one CommServe at HO and 4 remote sites, each with its own on-prem MediaAgent and Disk Library (primary copy).

Planned design:

Primary copy: local Disk Library at each site (30-day retention).
Secondary copy: Commvault Air Gap Protect (Azure), with extended retention of 3 years for Prod and 1 year for Non-Prod.
Remote sites: direct internet (HTTPS 443) plus site-to-site VPN to HO.

Questions:

Once AGP is licensed and configured on the HO CommServe, can each remote site's MediaAgent be added as a data path and write the Aux Copy directly to AGP, without routing data through HO?
Is any extra license or install needed on the remote MediaAgents for AGP, apart from opening outbound 443?
What's the recommended approach: one shared AGP storage pool with all 5 MediaAgents as data paths, or a separate AGP storage per site, each with its own DDB on the local MediaAgent? We want to avoid DDB lookups over the WAN/VPN.
MediaAgents added through a client group get Read access by default. Do we need to change it to Read/Write for each remote MediaAgent before running Aux Copy?
Can one AGP subscription (capacity) be shared across all storages and sites in the same CommCell?

Thanks in advance.