We have identified a known issue that can lead to sustained high CPU usage when environments upgrade to Veeam ONE v13 and enable the new Veeam Analytics Service while the monitored backup servers run Veeam Backup & Replication v12.x.
Who is affected
- Veeam ONE v13 with Analytics Service enabled
- One or more Veeam Backup & Replication servers on v12.x
- Abnormal, and constant elevated CPU on the VBR server
- Abnormal, and constant elevated Windows Defender CPU usage
Still under research for the new Veeam ONE Analytics processes, what is know is that the new Analytics Service uses a high-churn working directory. Real time antivirus scanning of this directory increases overhead and can indirectly drive CPU usage during data collection.
Immediate recommendation
Add the standard Veeam antivirus exclusions on all Veeam servers, with special attention to the Analytics Service path. Follow our official guidance in KB1999.
KB1999: Antivirus exclusions for Veeam components
Notes
These exclusions are part of our standard recommendations. The Analytics Service working path is intentionally update heavy, so allowing it through antivirus scanning prevents unnecessary rescans and reduces CPU pressure.
We will update the threat as soon as we have more information.