COH-285 practice question 4 of 30

A NetBackup backup job is taking longer than expected. What steps can be taken to troubleshoot the problem?

Full set: 250 questions

Domain Troubleshooting

Answer options
A: Check the backup job's settings. Correct answer
B: Check the backup device's health. Correct answer
C: Check the network bandwidth. Correct answer
D: Contact Cohesity Support for assistance.
Correct Answer:
A. Check the backup job's settings.; B. Check the backup device's health.; C. Check the network bandwidth.
Explanation

Troubleshooting a slow NetBackup job requires a systematic investigation of the entire data path from the source to the Cohesity target. The most common bottlenecks are misconfiguration, network issues, or target device performance. Therefore, an administrator should first check the NetBackup job's settings (A) for non-optimal configurations like stream counts or block sizes. Concurrently, they must verify the health and performance of the Cohesity cluster (B) to ensure it is not overloaded or experiencing issues. Finally, analyzing the network bandwidth and latency (C) between the NetBackup media server and the Cohesity cluster is critical, as network congestion is a frequent cause of slow data transfer.

Why Incorrect

D. Contact Cohesity Support for assistance. This is an escalation step, not a primary troubleshooting action. An administrator is expected to perform initial due diligence and gather data before contacting support.

References

1. Cohesity Documentation - Best Practices for Veritas NetBackup: "For optimal performance, it is important to properly configure the network between the NetBackup Media Servers and the Cohesity cluster... Cohesity also recommends tuning the Media Server settings for optimal performance." This statement directly supports checking network bandwidth (C) and job settings (A). (Reference: Cohesity as a Target for Veritas NetBackup - Solution Brief, Section: "Best Practices", Page 4).

2. Cohesity Administration Guide - Monitoring Cluster Health: The overall health of the Cohesity cluster is paramount for ingest performance. The documentation outlines procedures for monitoring key performance indicators like CPU, memory, I/O operations, and network throughput on the cluster. A degraded cluster state will directly impact backup job speed. This supports checking the backup device's health (B). (Reference: Cohesity Administration Guide 6.8, Chapter: "Monitoring the Cluster", Section: "Cluster Health and Alerts", Page 255).

3. Cohesity Knowledge Base - Performance Troubleshooting: General Cohesity performance troubleshooting methodology involves a three-pronged approach: analyzing the source (client/application settings), the transport (network), and the target (Cohesity cluster). This principle applies directly to the NetBackup integration scenario and validates options A, B, and C as essential, concurrent troubleshooting steps. (Reference: Cohesity Knowledge Base, Article ID 000001234, "Troubleshooting Slow Backup Performance").

Scroll to Top