COH-285 Cohesity Certified Protection Professional – NetBackup Appliances Free Practice Exam Questions (2026 Updated)

The correct log to analyze is the nbdb log. The nbdb_ping utility is specifically used to check and display the status of the NetBackup database, including NBDB, NBAZDB, and BMRDB. Cohesity’s NetBackup Commands Reference states that running nbdb_ping with no options displays the status of NBDB, which directly matches the diagnostic command in the question. When nbdb_ping reports “Database [NBDB] is not available,” the most relevant NetBackup diagnostic logging is produced under the nbdb log area, not emm.log or nbrb-style service logs. Official NetBackup support examples show the same failure being diagnosed from the nbdb log at /usr/openv/netbackup/logs/nbdb, including entries from nbdb_ping, configuration-file read failures, and the exact message Database [NBDB] is not available. Another NetBackup case with the same nbdb_ping error shows server.log containing no useful errors while /usr/openv/netbackup/logs/nbdb contains the actionable nbdb_admin and nbdb_ping failures. Therefore, the log identified by option A is the appropriate troubleshooting source.

( The Staging Schedule option in the Change Storage Units dialog allows you to define a schedule for moving backup data from the staging area to secondary storage, enabling you to optimize your backup storage utilization and reduce storage costs.)

The Enable FIPS mode option is presented during a fresh NetBackup installation of primary, media, client, or clustered server software. Cohesity NetBackup Installation Guide procedures show that, during local, remote, or clustered server installation, the installer displays the FIPS Compliance in NetBackup screen where the administrator can enable or disable FIPS mode; by default, FIPS mode is disabled. The guide further states that enabling FIPS causes the NetBackup installer and subsequent operations to run in FIPS mode, and that enabling it during clustered installation applies it to the nodes added on the NetBackup Remote Hosts screen. Client installation follows the same model: the Windows client installation procedure includes a FIPS Compliance in NetBackup screen where FIPS mode can be enabled or disabled. Option C is incorrect because Cohesity explicitly states that NetBackup does not support changing FIPS mode during upgrade; it must be enabled before upgrade or after upgrade as a post-install configuration. Reference topics: NetBackup Installation Guide, FIPS Compliance in NetBackup, and Enable FIPS mode on NetBackup during installation.

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.