Get Cohesity COH-285 Exam Practice Questions - Real and Updated

Answer : A

The correct log to analyze is the nbdb log. The nbdb_ping utility is specifically used to check and display the status of the NetBackup database, including NBDB, NBAZDB, and BMRDB. Cohesity's NetBackup Commands Reference states that running nbdb_ping with no options displays the status of NBDB, which directly matches the diagnostic command in the question. When nbdb_ping reports ''Database [NBDB] is not available,'' the most relevant NetBackup diagnostic logging is produced under the nbdb log area, not emm.log or nbrb-style service logs. Official NetBackup support examples show the same failure being diagnosed from the nbdb log at /usr/openv/netbackup/logs/nbdb, including entries from nbdb_ping, configuration-file read failures, and the exact message Database [NBDB] is not available. Another NetBackup case with the same nbdb_ping error shows server.log containing no useful errors while /usr/openv/netbackup/logs/nbdb contains the actionable nbdb_admin and nbdb_ping failures. Therefore, the log identified by option A is the appropriate troubleshooting source.

Answer : D

Answer : D

Answer : D

Answer : D

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. Reference/topics: Synthetic backup schedule attribute, Synthetic cumulative incremental backups, and Schedules required for synthetic backups.