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

The correct answer is media servers and clients. Cohesity NetBackup documentation defines VxUpdate as a deployment-management mechanism for updating non-primary NetBackup hosts. The official NetBackup Upgrade Guide states that “VxUpdate provides a policy-based upgrade tool for media servers and clients,” and further explains that the policy format simplifies media server and client upgrades while signed packages are added to the VxUpdate repository on the primary server for later deployment. Cohesity’s Repository management topic reinforces this by stating that the VxUpdate repository resides on the primary server and contains packages that can be deployed to media servers and clients. It also explicitly says that administrators can upgrade NetBackup media servers and clients to a newer NetBackup version with VxUpdate.

Therefore, option D is correct. Option A is incorrect because the primary server hosts the VxUpdate repository and controls deployment, but it is not itself upgraded through VxUpdate deployment policies. Option B and option C are incomplete because VxUpdate is not limited to only one of those host roles. Reference topics: NetBackup Deployment Management with VxUpdate, About VxUpdate, and Repository management.

The correct answer is Cumulative incremental backup. In NetBackup policy schedule configuration, the Synthetic backup schedule attribute is not limited only to a Full schedule. Cohesity documentation states that the Synthetic backup attribute allows a backup image to be assembled from prior backup images and that “a synthetic backup may be a synthetic full or a synthetic cumulative incremental backup.” This directly identifies cumulative incremental as the additional schedule type that can be configured as synthetic. Differential incremental backups are normally used as component images that feed the synthetic operation; they capture changed data and are later consolidated, but they are not the synthetic schedule type in this question. User archive and Vault catalog backup schedules are unrelated to synthetic backup image construction. Cohesity also explains that a synthetic cumulative incremental backup is produced by consolidating component images, including differential incremental backups taken since the last cumulative backup and, when available, the last cumulative incremental backup. Therefore, besides Full, the schedule type that supports synthetic configuration is Cumulative incremental backup. References/topics: Synthetic backup schedule attribute, Synthetic cumulative incremental backups, and Schedules required for synthetic backups.

The required prerequisite is to set an encryption passphrase for disaster recovery packages. In a NetBackup catalog backup workflow, the catalog backup creates disaster recovery information that is required during catalog recovery. Cohesity NetBackup documentation places the passphrase step before the catalog policy is configured. In the manual catalog backup procedure, after creating the DRPackages directory and setting ownership, the guide instructs the administrator to “set the passphrase to be used at time of catalog recovery,” then open the NetBackup Administrator Console and navigate to Security Management > Global Security Setting > Disaster Recovery. In the Encryption for Disaster Recovery section, the administrator must add, confirm, and save the passphrase. Only after these steps does the documented procedure proceed to “Configure NetBackup catalog backup policy.”

This makes option D correct. A universal share is not required; the DR package path can be a configured persistent directory. An email address is optional and only used to send DR packages when email is configured. Logging in as Systems Administrator is not the specific prerequisite identified by the catalog backup procedure. Reference topics: Performing catalog backup and recovery, Backing up a catalog, and Disaster Recovery encryption settings.