Monitoring and Scaling Guidelines for Backup Infrastructure in a Shared Services Environment

Review the following guidelines before you scale out your backup infrastructure in a shared service environment.

Note

Scale up to a medium and large hardware configuration before adding a new node. Extra Large should be used as an exception.

Resource	Scaling Guideline
Web Server and Web Console	20% increase in API requests in a period of 7 days Weekly CPU and RAM is over 90% sustained over a week
Index Server	Add a new node for every 700M items
MediaAgent	Add a new MediaAgent when the number of streams is near the maximum limit and the CPU/RAM is greater than 90% sustained over a week
Access Node (Windows) - used for Microsoft Office 365, Microsoft Dynamics 365, and Active Directory applications	Add a new node if you see a drop in backup health and the CPU/Memory is over 90% sustained over a week.
Access Node (Linux) -Used for Azure Blob, Salesforce, VM and Kubernetes applications	Add a new node if you see a drop in backup health and the CPU/Memory is over 90% sustained over a week.

Sizing details for large and extra large environments: CommCell Sizing.

Related Topics