Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Backup Planning and Performance Tuning Guide
  3. Media server configuration guidelines
  4. About NetBackup Media Server Deduplication (MSDP)
  5. CPU considerations
NetBackup™ Backup Planning and Performance Tuning Guide

CPU considerations

Each running process consumes certain amount of CPU cycles. The main processes consuming CPU cycles include NetBackup processes such as bptm, bpdm, and MSDP spoold, spad, mtstrmd, and vpfsd if Universal Share and Instant Access are used. More concurrent jobs correspond for more bptms, bpdms processes running at the same time, and more active threads in spoold, spad, mtstrmd and vpfsd.

For target deduplication, segmentation, fingerprint calculation and lookups are done on the same host running spoold, spad and vpfsd. More target deduplication jobs use more CPU cycles from the host. When a media server is bottlenecked on CPU, network and/or memory, adding one or more NetBackup load balancing fingerprinting media servers and/or NetBackup Client Direct (client-side deduplication) ease the CPU, memory and network pressure by offloading some data segmentation and fingerprint calculations to the new server.

Feedback

Was this page helpful?
Previous

Network considerations

Next

OS tuning considerations

Feedback

Was this page helpful?