Free Cohesity COH-285 Practice Exam with Questions & Answers | Set: 3

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 correct command is nbstlutil. In NetBackup, lifecycle-managed images are controlled by Storage Lifecycle Policies (SLPs), and the dedicated command-line utility for inspecting and intervening in SLP processing is nbstlutil. Cohesity’s NetBackup Commands Reference defines nbstlutil as the command used to “run the NetBackup storage lifecycle policies utility,” and its description states that it provides a way for users to intervene in storage lifecycle policy operations. Most directly, the same official command reference lists the report function under nbstlutil and states that report shows a rollup of incomplete copies of lifecycle-managed images. Therefore, the practical command would be nbstlutil report, with optional filters such as lifecycle name, client, media ID, media server, storage server, or SLP version.

The other commands do not target this SLP-specific view. bpimage is associated with backup image operations, bpimmedia reports media/image relationships, and bpimagelist lists backup image catalog information. They do not provide the SLP incomplete-copy rollup requested in the question. Reference topics: NetBackup Commands Reference Guide, nbstlutil, Storage Lifecycle Policy operations, and lifecycle-managed image status reporting.

The correct options are A and E. The warning indicates that the catalog disaster recovery file is being written to a location that would likely be lost with the NetBackup catalog during a disk or server failure. Cohesity NetBackup documentation for the NBU-Catalog policy’s Disaster Recovery tab states that the DR path is where disaster recovery information is saved, and explicitly recommends not saving that information to the local computer; instead, it should be saved to a network share or removable device. It also states that, on UNIX, the path cannot be on the same partition as /usr/openv/netbackup; it must be changed to a directory on a different partition. Therefore, placing the DR file on a volume other than the NetBackup volume resolves the warning. Cohesity also documents the Send disaster recovery email option, where one or more administrator email addresses can be entered so NetBackup sends DR information after every catalog backup. The disaster recovery email includes recovery instructions and the image file/package attachments needed for catalog recovery. References/topics: NBU-Catalog policy, Disaster Recovery tab, DR file path, and disaster recovery email configuration.