The Reg Date SQL Backup Core Service (SQBCoreService) ate 86.8% of the CPU resources, maxing the CPU to 100% utilization. It finally gave up hogging the CPU after 5 separate Alerts were emitted and 42 minutes of the total run-time of 50 had elapsed.
Firstly, it's a good job there were no users on the system at midnight EDT!
Secondly, this isn't a good thing Would you please recommend how one can reduce the CPU percentage hogged by the new and obviously improved SQBCoreService?
Some factors you might be interested in:
- 1. We have ample CPU to spare "normally". Approx 5% to 20% max usage daylong is our norm.
2. We have an Indian office that will use CPU during our U.S. nighttime, and their calculations are cpu hogs, too, so we need to give them some headroom.
3. We are utterly disk-space-challenged, hence the use of compression level 4.