Deploy the MediaAgent in the same cloud region as the cloud storage destination when possible. The MediaAgent doesn't need to be in the same network as the CommServe server.
Important
Deploying the MediaAgent in a different region from the cloud storage destination can result in egress charges from the cloud provider.
MediaAgent responsibilities
Cloud MediaAgents are used primarily for hosting the Deduplication Database (DDB), indexing, and data pruning operations. Depending on the configuration, a MediaAgent can also perform auxiliary copy and synthetic full backup operations. A MediaAgent configured as an access node can perform data movement.
Storage Accelerator
When Storage Accelerator is enabled and the client can connect to the cloud storage library, the client sends backup data directly to the library. If the client cannot connect directly, backup data is sent through the MediaAgent.
For more information, see Accelerating Backups to Cloud Storage Libraries.
Resiliency and scaling
Deploy a minimum of two cloud MediaAgents for resiliency, regardless of the amount of data that you protect. As your environment grows, increase the resources assigned to each MediaAgent up to the supported large configuration. After reaching that configuration, add MediaAgents to scale out the environment.
For sizing information, see MediaAgent: System Requirements and Index Server: Hardware Requirements.
Metadata protection
DDB and index metadata are self-protected and can be reconstructed if a MediaAgent is lost.
For more information, see Deduplication Building Block Guide and Indexing Overview.
Cloud deployment procedures
Select the cloud environment where you want to deploy the MediaAgent: