Cohesity COH-285 - Cohesity Certified Protection Professional – NetBackup Appliances

The correct answer is C. During an image verification operation, NetBackup validates the backup image stored on backup storage by reading the backup volume and comparing what is present on that storage with the metadata recorded in the NetBackup catalog. Cohesity NetBackup documentation states that NetBackup verifies backup contents “by reading the volume and comparing its contents to what is recorded in the NetBackup catalog.” It also clarifies that this operation does not compare the backup image with the original client disk contents. Therefore, the validation scope is the readability and catalog consistency of the stored backup image, not a live comparison against the client file system and not a primary-server data check. This distinction is important operationally: image verification confirms that NetBackup can locate and read the blocks belonging to the backup image and that the stored image aligns with catalog records. It is not a restore test and does not prove that current client data is unchanged. References/topics: Catalog utility, Verify backup images, bpverify, NetBackup catalog image validation, and backup storage readability verification.

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 required step is to verify that the third-party OST target supports Accelerator with VMware-type policies in the Hardware Compatibility List. Cohesity NetBackup documentation states that Accelerator for virtual machines uses VMware Changed Block Tracking (CBT) to identify changes inside the virtual machine, not the Windows NTFS or ReFS change journal. The same VMware Accelerator requirements topic lists supported disk storage destinations and includes qualified third-party OpenStorage devices, then specifically instructs administrators to verify Accelerator support for the storage unit in the NetBackup hardware compatibility list for supported OST vendors. It also warns that if the storage unit does not support Accelerator, the backup can fail with messages such as the storage server type not supporting accelerator backup. The HCL further identifies Accelerator with VMware-type policies as a distinct OpenStorage supported-functionality entry, meaning generic OST support is not sufficient; the vendor/device must support the VMware Accelerator capability. (Veritas Download) Option A applies to file-system Accelerator behavior for Windows clients, not VMware image-level backups. Option C is not mandatory for the first successful VMware backup. Option D is incorrect because VMware Accelerator does not require manually creating a client track log.