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. The 6 steps of performance issue RCA and resolution
NetBackup™ Backup Planning and Performance Tuning Guide

The 6 steps of performance issue RCA and resolution

Use the following steps iteratively to drive the root cause analysis and resolution. Root cause analysis can be difficult but once the root cause is identified, the solution is usually trivial.

  1. Obtain a clear problem description to ensure that the right problem is being solved.

  2. Ensure the problem can be reproduced consistently. This step is important because if the problem can't be consistently reproduced, you never know whether the problem is resolved. Consistency also includes ensuring the result has minimum run-to-run variation. When run-to-run variation is more than 10 - 15%, it will be hard to determine if the improvement or degradation is due to tuning or just run-to-run variation.

  3. Collect data for RCA. Data collection has to be meticulous. Avoid having other unrelated jobs or activities running while the data collection is in progress.

  4. Perform root cause analysis. In particular, focus on the following two tasks. Use the following flow chart to guide the root cause analysis.

    • Analyze system resource usage

    • Create workload profile

  5. Apply tuning based on the root cause identified in step 4.

  6. If the problem persists, go back to step 2 again. Repeat until the problem is resolved.

Feedback

Was this page helpful?
Previous

Proper mind set for performance issue RCA

Next

Flowchart of performance data analysis

Feedback

Was this page helpful?