Cohesity Updated COH-285 Exam Questions and Answers by franciszek

The correct feature is Synthetic backups. Cohesity NetBackup documentation explains that, in a traditional full backup, all files are copied from the client to the primary or media server, even if the files have not changed. With a synthetic full backup, NetBackup combines the previous full backup with subsequent incremental backups on the media server to create a new full image. Because the processing occurs on the primary and media servers rather than repeatedly reading all data from the client, synthetic backups reduce client-to-server network traffic; files are transferred over the network only once. Synthetic backups can also be written to disk storage units, making them appropriate for an AdvancedDisk target backed by a high-speed disk array. This fits the scenario because Windows and Linux file servers map to MS-Windows and Standard policy types, which are supported for synthetic backups. NetBackup Accelerator is not the best answer here because Accelerator requires supported disk targets such as MSDP, NetBackup appliance storage, cloud storage, or qualified OST storage, not a generic AdvancedDisk storage unit. Client-side deduplication similarly requires deduplication storage, and network resiliency improves fault tolerance rather than reducing backup traffic. References/topics: Synthetic backups, AdvancedDisk storage units, backup traffic optimization, and Accelerator requirements.

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.