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

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.

The correct answer is A. The DISALLOW_SERVER_FILE_WRITES client configuration entry controls whether NetBackup servers are allowed to write files on the client host. Cohesity NetBackup documentation states that this entry “prevents the NetBackup server from creating files on the NetBackup server or client” and further explains that it prevents NetBackup servers from remotely performing restores or remotely changing client configurations. In practical administration terms, this disables server-directed restores to that client. Cohesity also maps the related Windows Backup, Archive, and Restore interface setting to File > NetBackup Client Properties > Allow server-directed restores, confirming that the function is specifically about whether restores can be initiated from the NetBackup server side toward the client. This is why option A is the best match. Option B refers to redirected restores, which are governed by alternate-client restore permissions and client authorization behavior, not this setting alone. Option C is too broad because client-initiated restore capability is controlled separately, such as by DISALLOW_CLIENT_RESTORE. Option D is unrelated to backup write permission. References/topics: Client configuration options, DISALLOW_SERVER_FILE_WRITES, Allow server-directed restores, and NetBackup host security controls.

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.