Free Practice Questions for Cohesity COH-285 Exam

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 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 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.

The default summary interval is 24 hours. In NetBackup Appliance AutoSupport/Call Home behavior, when Call Home is enabled and a monitored hardware or software failure occurs, the appliance uploads diagnostic and monitoring information to the AutoSupport server and also generates email notifications to the configured recipient list. The official Appliance AutoSupport Reference Guide describes three email notification types: an initial error notification when the failure is detected, a resolved notification when the failure clears, and “a 24-hour summary by email” for unresolved errors. The NetBackup Appliance Security Guide states the same operational sequence: the appliance sends an error email, a resolved email, and a 24-hour summary of currently unresolved errors. Therefore, 15 minutes, 1 hour, and 12 hours are not the documented default intervals for unresolved-error summary notification. Those values may resemble polling or alerting intervals in other monitoring systems, but NetBackup Appliance Call Home uses the daily summary model to reduce repeated notifications while keeping administrators informed of unresolved conditions. Reference topics: Appliance AutoSupport Reference Guide – About Call Home, Settings > Notification > Alert Configuration, and NetBackup Appliance Security Guide – Call Home alert behavior.