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. How to identify performance bottlenecks
  4. Introduction
NetBackup™ Backup Planning and Performance Tuning Guide

Introduction

Performance issues are different from other product defects and therefore the regular debugging process is not useful for debugging performance issues. When troubleshooting a product failure, the most common first step of debugging is to examine the default logs collected. If there is not enough information in the default logs, the next step is to elevate the logging level to collect more detail logs. For performance issue troubleshooting, elevating the log level is not recommended. This is because elevating the log level changes the system resource usage pattern and can substantially slow down the performance, masking the original problem and possibly creating a different performance issue.

This section discusses the correct approach for troubleshooting performance problems and covers the following sections:

  • Proper mind set for performance issue RCA

  • The 6 steps of performance issue RCA and resolution

  • Flowchart of performance data analysis

Feedback

Was this page helpful?
Previous

How to identify performance bottlenecks

Next

Proper mind set for performance issue RCA

Feedback

Was this page helpful?