Pass the Cohesity Cohesity Protection Professional COH-285 Questions and answers with CertsForce

The correct command is vxlogview -o 118 -d D,T,x. Status code 96 commonly indicates that NetBackup could not allocate required media or storage resources, so troubleshooting should focus on the NetBackup Resource Broker, also known as nbrb. Cohesity NetBackup documentation identifies originator ID 118 as nbrb, the NetBackup Resource Broker, which maintains available resource information and locates the physical and logical resources needed for backup and tape restore operations. The vxlogview command is the supported utility for reading unified logs, because unified log files are binary and must be assembled by vxlogview. The -o 118 option filters log records for the Resource Broker originator, while -d D,T,x displays the required fields: date, timestamp, and actual log message text. The command reference defines D as display date, T as display timestamp, and x as display actual log message text. Option C is incorrect because w displays who logged diagnostic/debug messages, not the actual message text. References/topics: NetBackup unified logging, vxlogview, originator IDs, nbrb Resource Broker logging, and status 96 resource allocation troubleshooting.

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 run content router queue processing on the media server that hosts the MSDP storage server. In an MSDP environment, expiring backup images with bpexpdate removes or marks the NetBackup catalog references, but the deduplicated segment references in MSDP are reclaimed through the deduplication transaction queue. Cohesity NetBackup documentation explains that after images are expired, MSDP may not immediately reclaim the freed space and that administrators can accelerate reclamation by manually processing the MSDP transaction queue. The deduplication process writes transaction log data into the queue directory, and that queue data is later processed during the next content router queue processing operation. Official NetBackup Deduplication procedures specify running crcontrol --processqueue on the MSDP storage server, not on the primary server. Image cleanup alone is not the MSDP space-reclamation mechanism after manual expiration, and a storage-pool inventory does not dereference deduplicated fragments. Therefore, the required step is option A.

The correct permissions are View and Subscribe. In NetBackup RBAC, adding an asset to a Protection Plan is treated as subscribing the asset to that plan, not creating, updating, or managing the plan itself. Cohesity documentation describes the workflow as selecting one or more assets, clicking Add protection, choosing a protection plan, and clicking Protect; it also states that a single asset or group of assets can be subscribed to one or more protection plans. The RBAC permissions model separates plan administration from asset subscription. The role-permissions topic defines protection plans as the area used to manage how backups are performed with protection plans, while assets are managed separately under the Assets permission category. Official NetBackup RBAC guidance states that to add assets to a protection plan, the user requires View and Subscribe permissions on the protection plan, with corresponding asset permissions to view and protect the assets. Therefore, View and Subscribe is the permission pair directly aligned with adding an asset to a Protection Plan. References/topics: RBAC role permissions, Protection Plans, Subscribe an asset or asset group, and Workload asset protection workflow.