# Control CPU usage for database backups and restores

Applies to: DB2, Informix, SAP Oracle, Oracle, Oracle RAC

Limit CPU usage for database workloads to maintain predictable performance during backup and restore operations. CPU throttling helps prevent data protection activity from consuming excessive CPU resources and impacting production workloads.

Commvault uses Linux cgroup v2 CPU quotas to control how much CPU time database processes can consume during backup and restore operations.

## When to use CPU throttling

- Shared database servers where backup activity can affect application performance

- High-core systems where data protection operations can otherwise consume all CPU resources

- Environments that require consistent performance during backup windows

- Systems with variable CPU capacity where proportional limits are preferred

## How it works

- CPU limits are enforced using Linux cgroup v2

- Limits apply to database backup and restore processes

- CPU usage is controlled by total compute time, not by pinning processes to specific cores

## Configure CPU throttling

Configure additional settings on the database client to enable and control CPU usage.

Note

For database backups or restores, configure the setting in the respective agent categories. For example, OracleAgent/dCVRCGMGRENABLE.

1. Enable CPU throttling using the dCVRCGMGRENABLE setting.

2. Choose a throttling method based on your requirement:

   Throttling method | When to use | Setting
   --- | --- | ---
   Limit CPU by core count | Use this method when you want a consistent and predictable CPU limit. | dCVRCGMGRCPUCORES
   Limit CPU by percentage | Use this method when you want limits to scale with system size. | dCVRCGMGRCPUSHARE

## Verify the configuration

To confirm that CPU limits are applied, run the following command.

`/sys/fs/cgroup/dbRcgGroup_*.slice/cpu.max`

×

Loading...