Applies to: DynamoDb, Amazon RDS MSSQL
Auto-scaling enhances efficiency and performance, especially for large-scale operations, by dynamically deploying access nodes in a region only when required, and then promptly powering off and decommissioning the access nodes after they are used.
Auto-Scaling for DynamoDB
Supported AWS regions
Auto-scaling is supported for all commercial AWS Regions. Edge locations (such as GovCloud, AWS Outposts, Local Zones, and Wavelength Zones) are not supported.
How auto-scaling works with Amazon DynamoDB
Auto-scaling is managed by a scale configuration that is associated with a Server group. The server group is associated with a workload resource pool in a specific AWS region. The server group can be directly associated with a DynamoDB instance to enable auto-scaling in the AWS account specified in the scale configuration. Based on the workload demand, Commvault automatically provisions the required access nodes from this resource pool to efficiently support DynamoDB backup and restore operations. Browse and detect operations continue to use a permanent access node.
Where auto-scaled access nodes are created
Auto-scaled access nodes are created in the AWS regions and availability zones that you specify in the scale configuration client. The access nodes are deployed in the same region where your S3 buckets reside to optimize data transfer performance and minimize cross-region data transfer costs.
Decommissioning of access nodes
Auto-scaled access nodes terminate after they are idle for 5 minutes. If no active access node is available, auto-scale automatically creates a new access node on demand. If no activity occurs on that access node after the job completes, then the access node is deleted.
Auto-Scaling for Amazon RDS MSSQL
Supported AWS regions
Auto-scaling for Amazon MSSQL uses the AWS Region configured in the auto-scaling configuration. Edge locations (such as GovCloud, AWS Outposts, Local Zones, and Wavelength Zones) are not supported. The temporary access nodes are provisioned within the configured AWS VPC.
How auto-scaling works with Amazon RDS MSSQL
Auto-scaling for Amazon MSSQL is managed by a scale configuration that is associated with a Server group. The server group is associated with a workload resource pool in a specific AWS region. The server group can be directly associated with a MSSQL instance to enable auto-scaling in the AWS account specified in the scale configuration. Based on the workload demand, Commvault automatically provisions the required access nodes from this resource pool to efficiently support MSSQL backup and restore operations.
It uses the auto-scaling framework to provision temporary access nodes on demand for AWS RDS Microsoft SQL Server export-based backup and restore operations. The temporary access nodes are created only when required and are automatically deprovisioned after a short idle period. Browse and detect operations continue to use a permanent access node.
Where auto-scaled access nodes are created
Auto-scaled access nodes are provisioned by the Scale Manager based on the auto-scaling configuration. The temporary EC2 instances are created from Commvault provided AMIs, register with CommServe, and are used for backup and restore operations.
Decommissioning of access nodes
Temporary access nodes remain idle for a short configurable period and are then automatically deprovisioned, regardless of whether the job succeeded or failed.