I've been observing consistent CPU utilization spikes on our Check Point Quantum 6000 appliances that correlate directly with our configured nightly backup window. The primary process responsible appears to be `cprid`, which consumes the entire core it's running on, pushing overall CPU to 100% for the duration of the backup operation.
Our current environment and backup configuration:
* **Appliance Model:** Quantum 6000 (model 6175)
* **R80.40 Take:** 269
* **Backup Method:** Scheduled policy backup to an external SMB share
* **Backup Size:** Approximately 4.2 GB
* **Duration of Spike:** 45-60 minutes
Monitoring via `top` and `ps` during the event shows:
```bash
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
11245 admin 20 0 721948 21376 4820 R 100.0 0.1 45:32.17 cprid
```
Has anyone else encountered this specific `cprid` process behavior during backups? I'm trying to isolate if this is:
* A known issue with the backup mechanism to network shares in this version.
* Related to the size or composition of our policy (we have a large number of rules and objects).
* An expected overhead for the encryption/compression process.
I've reviewed sk170161 regarding high CPU, but it primarily addresses `cprid` usage during policy installation, not backup operations. Any data points on whether switching to FTP/SCP backup targets reduces this load, or if a specific Jumbo Hotfix Accumulator resolves it, would be valuable.
Numbers don't lie