COH-285 Cohesity Certified Protection Professional – NetBackup Appliances Question and Answers

The correct action is to resume the job from Activity Monitor. Cohesity NetBackup documentation states that Activity Monitor provides a Resume action for jobs that are suspended or in an Incomplete state; the documented procedure is to open Activity Monitor > Jobs, select the incomplete job, and choose Actions > Resume Job. This is the supported way to make the same incomplete backup continue before the next scheduled backup starts. It is especially important in a multiple data streams policy, where each stream appears as an individual job and the failed stream should be resumed rather than replaced by a new manual backup. The Move backup job from incomplete state to done state property only controls how long a failed backup can remain incomplete before Activity Monitor shows it as Done; reducing that value would shorten the recovery window, not rerun the backup. Cohesity also notes that a resumed job reuses the same job ID, whereas a restarted job receives a new job ID. Running a manual client or mount-point backup would create a separate backup operation and would not verify completion of the existing incomplete job. References/topics: Activity Monitor job actions, Resume incomplete jobs, Checkpoint restart, and Clean-up host properties.

The correct action is to increment the job priority in Activity Monitor for the specific queued job. Cohesity NetBackup documentation states that an administrator can dynamically change the priority of selected queued or active jobs that wait for resources directly from the Activity Monitor by selecting the job and choosing Change Job Priority. The available options include setting a specific priority, incrementing the job priority, or decrementing it, and the change affects only the selected job rather than all jobs of that type. This matches the requirement: a small subset of queued jobs must be favored during the same backup session, without changing long-term policy behavior.

Changing the priority in the policy is less appropriate because the policy attribute defines how that policy competes with other policies for resources, and is a configuration-level setting rather than an immediate per-job intervention. NetBackup uses job priority as a scheduling guide; higher-priority requests are evaluated before lower-priority requests, although resource optimization can still influence final selection. Therefore, the operationally correct response is option A.

With ALL_LOCAL_DRIVES and Allow multiple data streams enabled, NetBackup can split each client backup into separate streams per drive or file system; Cohesity documentation states that NetBackup backs up the client and “splits the data from each drive” into its own stream when multiple data streams are enabled. However, the number of streams that can run concurrently is still constrained by job limits. Cohesity’s policy documentation states that concurrent stream count is affected by Maximum jobs per client, Limit jobs per policy, and related storage limits; when Maximum data streams is not explicitly set, NetBackup uses the lower of Maximum jobs per client or Limit jobs per policy. The default Maximum jobs per client is one job, so only one backup stream per client can run. With five clients, that means 5 active backup jobs, not 15.

The storage unit’s Maximum concurrent jobs = 15 does not restrict restores, because Cohesity states this setting controls backup and duplication traffic, not restore jobs. The disk pool’s Maximum I/O Streams = 20 limits read and write streams; restores read backup images and backups write them. Five backups plus ten restores equals 15 total streams, so all 10 restores can run.

The replication job starts when the force interval for small replication jobs is reached. NetBackup SLP settings control how Storage Lifecycle Policy jobs are maintained and executed for the selected primary server. Cohesity documentation identifies these as SLP settings used to customize how SLP jobs run. For AIR replication batching, the controlling parameter here is SLP.MIN_SIZE_PER_REPLICATION_JOB. Official NetBackup documentation defines it as the smallest batch size that can run as a single replication job and states that the job does not run until enough images accumulate to reach that size, or until the force interval for small replication jobs is reached. (veritas.com)

In this scenario, three backups of 5GB each create only 15GB of eligible replication data. That is below the configured 20GB threshold, so NetBackup does not start the replication job based on size. Because the backup window has closed and no additional backup images will arrive, the batch cannot reach 20GB. NetBackup therefore submits the small replication batch when the oldest image reaches the configured 60-minute force interval. The force interval is specifically designed to prevent NetBackup from waiting too long before submitting a small replication job. (veritas.com)

The correct procedure is to delete the incorrectly discovered tape entry, configure the Media ID generation rule correctly, re-inventory the library, and then run the recovery. The catalog recovery request requires MediaID GBP847 for barcode GBP847S1, but the new server inventoried the tape as P847S1. Cohesity NetBackup documentation explains that, by default, NetBackup generates a media ID from the last six characters of a tape barcode. For barcode GBP847S1, the last six characters are P847S1, which exactly matches the incorrect media ID shown in the Administration Console. Cohesity further states that media ID generation rules override this default and define which barcode characters NetBackup uses to create the media ID. In this case, the rule must generate the media ID from the first six characters, producing GBP847. The rule is configured from the robot inventory advanced options under Media ID Generation. A barcode rule is not sufficient because barcode rules assign media attributes such as media type or volume pool, whereas media ID generation controls the actual media ID. bplabel is also inappropriate because it can relabel media and risks invalidating existing backup data. References/topics: Catalog recovery, robot inventory, media ID generation rules, and tape barcode handling.

The correct behavior is that Maximum jobs per client is ignored, and NetBackup applies the lower value between Maximum data streams and Limit jobs per policy. In Cohesity NetBackup, the Maximum data streams property is configured under Hosts > Host properties > primary server > Client attributes > General tab. This setting defines the maximum number of jobs allowed at one time for each selected client, and Cohesity documentation clarifies that it applies to client job count even when multistreaming is not used. The guide further states that when Maximum data streams is not set, NetBackup limits jobs by either Maximum jobs per client or Limit jobs per policy, whichever is lower. However, when Maximum data streams is set, NetBackup ignores Maximum jobs per client and uses either Maximum data streams or Limit jobs per policy, whichever is lower. Therefore, option B precisely matches the documented interaction. The storage-unit Maximum concurrent jobs setting is unrelated to this specific client attribute behavior, so options C and D are incorrect. Reference topics: Client attributes properties, General tab of the Client attributes properties, and Limit jobs per policy.

The method that is not able to provide historical performance information is running nbperfchk on the command line. nbperfchk is a standalone diagnostic utility used to test current disk I/O and network transfer rates. Official NetBackup guidance describes it as a tool used to determine base disk performance for backup disk devices and network throughput to a disk volume; it generates performance results from the test being run, not from prior NetBackup jobs or stored catalog/reporting data. By contrast, the other options are valid historical performance sources. The Activity Monitor job details provide job-level performance fields such as Start Time/End Time, Elapsed Time, KB per Second, and Kilobytes. The All Log Entries report can be run for a selected Date/Time Range and displays transfer-rate information useful for evaluating backup performance and predicting future backup windows. OpsCenter Disk and Tape Device Activity reports provide storage-device activity, utilization, throughput, and capacity-related reporting across NetBackup storage resources. Therefore, nbperfchk is a point-in-time benchmarking tool, not a historical reporting mechanism. References/topics: NetBackup performance evaluation, Activity Monitor job details, All Log Entries report, OpsCenter Disk and Tape Device Activity reports, and nbperfchk performance testing.

The correct answer is C because the failure is an authorization problem on the NetBackup client, not a basic network-connectivity failure. The job output explicitly states that nbumaster8 “is not an authorized server for host nbclient1,” followed by status 59: access to the client was not allowed. Cohesity NetBackup documentation maps status code 59 to “Access to the client was not allowed.” The controlling configuration is the client’s SERVER list. Cohesity states that the SERVER entry defines the list of NetBackup primary and media servers that can access the NetBackup client, and that media servers or other primary servers must be added for that client. Cohesity also explains that on UNIX servers and clients, the SERVER entries in bp.conf define the NetBackup servers that are allowed access, with additional entries identifying servers that can initiate scheduled backups. Therefore, the client rejected the backup request because the requesting server name was missing from the client’s server list or did not match the expected resolved name. References/topics: Status code 59, SERVER option for NetBackup clients, bp.conf, Host Properties > Clients > Servers, and NetBackup host-name authorization.

The correct command is nbstlutil. In NetBackup, lifecycle-managed images are controlled by Storage Lifecycle Policies (SLPs), and the dedicated command-line utility for inspecting and intervening in SLP processing is nbstlutil. Cohesity’s NetBackup Commands Reference defines nbstlutil as the command used to “run the NetBackup storage lifecycle policies utility,” and its description states that it provides a way for users to intervene in storage lifecycle policy operations. Most directly, the same official command reference lists the report function under nbstlutil and states that report shows a rollup of incomplete copies of lifecycle-managed images. Therefore, the practical command would be nbstlutil report, with optional filters such as lifecycle name, client, media ID, media server, storage server, or SLP version.

The other commands do not target this SLP-specific view. bpimage is associated with backup image operations, bpimmedia reports media/image relationships, and bpimagelist lists backup image catalog information. They do not provide the SLP incomplete-copy rollup requested in the question. Reference topics: NetBackup Commands Reference Guide, nbstlutil, Storage Lifecycle Policy operations, and lifecycle-managed image status reporting.

The correct log is the vnetd proxy log. NetBackup secure host communication uses host ID-based certificates and certificate revocation lists (CRLs). When communication fails between the primary/master server and a client because a certificate is revoked, unavailable, missing, or affected by CRL validation, the relevant troubleshooting path is the vnetd proxy process log files. Cohesity’s NetBackup Troubleshooting Guide states that for host-certificate troubleshooting, administrators should examine job details for certificate, revocation, and CRL messages, and “may need to examine the vnetd proxy process log files” for related messages and status codes. The same guide notes that NetBackup hosts must have a valid host ID-based security certificate and a valid CRL to communicate; otherwise, communication fails. For a revoked primary server certificate, Cohesity specifically identifies that the vnetd proxy process log files on hosts show that the primary server certificate is revoked. Therefore, nbemm is for Enterprise Media Manager functions, bprd is request processing, and nbrb is resource brokering; none is the primary diagnostic log for certificate revocation analysis. Reference topics: Troubleshooting security certificate revocation, Viewing vnetd proxy log files, and Test the vnetd proxy connections.

The correct answer is A. The DISALLOW_SERVER_FILE_WRITES client configuration entry controls whether NetBackup servers are allowed to write files on the client host. Cohesity NetBackup documentation states that this entry “prevents the NetBackup server from creating files on the NetBackup server or client” and further explains that it prevents NetBackup servers from remotely performing restores or remotely changing client configurations. In practical administration terms, this disables server-directed restores to that client. Cohesity also maps the related Windows Backup, Archive, and Restore interface setting to File > NetBackup Client Properties > Allow server-directed restores, confirming that the function is specifically about whether restores can be initiated from the NetBackup server side toward the client. This is why option A is the best match. Option B refers to redirected restores, which are governed by alternate-client restore permissions and client authorization behavior, not this setting alone. Option C is too broad because client-initiated restore capability is controlled separately, such as by DISALLOW_CLIENT_RESTORE. Option D is unrelated to backup write permission. References/topics: Client configuration options, DISALLOW_SERVER_FILE_WRITES, Allow server-directed restores, and NetBackup host security controls.