Resource throttling in NetBackup for OpenStack
Resource throttling is done to manage performance, prevent system overload, and ensure the fair NetBackup for OpenStack resource allocation among projects. Throttling prevents excessive consumption of resources and helps maintain stability. Throttling also prevents system failures and the issues that occur due to degraded performance.
Table: Resource throttling options in NetBackup for OpenStack
Option | Description |
|---|---|
MAX_BFS_JOBS_PER_NBOS | Resource throttling at the NetBackup side to concurrently run the number of backups from snapshot jobs. Configure the value in the Default value: MAX_BFS_JOBS_PER_NBOS = 3 |
max_snapshot_jobs_per_project | Resource throttling on NetBackup for OpenStack virtual machine to concurrently run the number of snapshot jobs per project. Configure the value in the Restart the nbosjm-scheduler service on one of the nbosvm nodes where this service is running. On a three-node cluster, run the following command to know on which nbosvm node the nbosjm-scheduler service is running: pcs status Default value: max_snapshot_jobs_per_project = 2 |
max_snapshot_expiry_jobs_per_project | Resource throttling on NetBackup for OpenStack virtual machine to concurrently expire the number of snapshot jobs per project. Configure the value in the Restart the nbosjm-scheduler service on one of the nbosvm nodes where this service is running. On a three-node cluster, run the following command to know on which nbosvm node the nbosjm-scheduler service is running: pcs status Default value: max_snapshot_expiry_jobs_per_project = 2 |
max_uploads_pending | Resource throttling on NetBackup for OpenStack datamover to concurrently run data movement operation per compute node. Configure the value in Restart the nbosdm container running on that compute node. Default value: max_uploads_pending = 5 |