COH-285 Exam Results

A Storage Unit is a logical NetBackup object used to represent the storage destination for backup data. The official Cohesity NetBackup documentation defines it directly: “A storage unit is a label that NetBackup associates with physical storage.” It further explains that the label can identify a robot, a path to a volume, or a disk pool. This makes option C the precise definition. Option A is incomplete because a storage unit does not merely define a physical location; it abstracts storage resources so policies and storage lifecycle operations can target them. Option B is incorrect because storage plans or lifecycle policies may use storage units, but a storage unit itself is not created for the sole purpose of creating a plan. Option D is too narrow because Media Manager is associated primarily with tape/robotic media handling, while storage units are broader NetBackup entities and can represent tape, disk, or disk-pool destinations. Cohesity NetBackup storage topics also describe storage units as part of the recognized storage configurations and note that they can be included in storage unit groups or storage lifecycle policies.

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.