Free and Premium Cohesity COH-285 Dumps Questions Answers

The correct command is nbcertcmd -listCertDetails. Cohesity NetBackup documentation states that host ID-based certificate details can be viewed with the NetBackup web UI, the nbcertcmd command, or NetBackup APIs. In the command procedure, Cohesity specifically instructs administrators to run nbcertcmd -listCertDetails on the NetBackup host to view host IDs and associated certificate details for that host. The NetBackup Commands Reference also confirms that nbcertcmd is the utility used to request and manage host ID-based security certificates on NetBackup hosts, including primary servers, media servers, and clients. It lists -listCertDetails as the operation that displays certificate details for security certificates deployed on the NetBackup host.

Option A is incorrect because -listCACertDetails displays trusted CA certificate details, not the local host-ID certificate expiry. Option B is invalid in this context because enrollment status is not viewed with bpclntcmd. Option C, -hostSelfCheck, checks whether the host certificate is revoked, not its expiration date. Reference topics: NetBackup Security and Encryption Guide, Viewing host ID-based certificate details, and nbcertcmd command reference.

The unavailable feature is Spanning volumes. In NetBackup cloud storage, disk-volume spanning is not supported by cloud vendors for backup images. The official NetBackup Cloud Administrator’s Guide lists cloud-storage limitations and explicitly states that cloud vendors do not support disk volume spanning of backup images. This makes option C the only correct answer. The other options are valid cloud-storage configuration capabilities. Compression is available in the Cloud Storage Server Configuration Wizard; the wizard provides a setting to compress backup data before writing to cloud storage. Encryption is also a supported wizard function, including AES-256 encryption and KMS-related configuration for data written to cloud storage. Secure Sockets Layer is likewise a supported connection property: NetBackup cloud storage server properties include USE_SSL and USE_SSL_RW, with SSL enabled by default for control APIs and read/write operations. Therefore, because encryption, SSL, and compression are configurable cloud features, while disk-volume spanning is a documented cloud-storage limitation, the correct selection is C. Spanning volumes. Reference topics: NetBackup Cloud Administrator’s Guide, “Configuring cloud storage,” “Cloud storage server connection properties,” and “Support limitations for NetBackup cloud storage.”

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 NetBackup Appliance product page provides detailed information about the hardware specifications of the appliance, including processor, memory, and storage capacities, to help customers choose the right appliance for their backup and recovery needs.)

The correct answer is AES 256 bit CTR encryption and SHA256/SHA-2 fingerprinting. In NetBackup, MSDP stands for Media Server Deduplication Pool, and its security model protects deduplicated data using modern encryption and fingerprinting algorithms. Cohesity NetBackup documentation identifies the MSDP data-at-rest cipher as AES-256-CTR, specifically listing “MSDP: AES-256-CTR” under NetBackup data-at-rest encryption ciphers. For fingerprinting, Cohesity documents that NetBackup 8.1 introduced a more secure MSDP fingerprint algorithm where the SHA-2 algorithm replaces the existing MD5-like algorithm. The upgrade documentation further explains that rolling MSDP data conversion converts older containers to the AES encryption and SHA-2 fingerprint algorithm, confirming that Blowfish and MD5-like fingerprints are legacy mechanisms rather than the current MSDP security standard. Therefore, option A is the only choice that combines the correct MSDP encryption mode, AES-256-CTR, with the correct secure fingerprinting family, represented in the option as SHA256 fingerprinting. References/topics: NetBackup Security and Encryption Guide, Ciphers used in NetBackup, MSDP fingerprinting algorithm changes, and MSDP rolling data conversion.

( NetBackup storage units define the physical locations where backup data is stored, whether on disk or tape, and enable efficient storage utilization for backup data.)

A Storage Unit is a logical NetBackup object used to represent the storage destination for backup data. The official Cohesity NetBackup documentation defines it directly: “A storage unit is a label that NetBackup associates with physical storage.” It further explains that the label can identify a robot, a path to a volume, or a disk pool. This makes option C the precise definition. Option A is incomplete because a storage unit does not merely define a physical location; it abstracts storage resources so policies and storage lifecycle operations can target them. Option B is incorrect because storage plans or lifecycle policies may use storage units, but a storage unit itself is not created for the sole purpose of creating a plan. Option D is too narrow because Media Manager is associated primarily with tape/robotic media handling, while storage units are broader NetBackup entities and can represent tape, disk, or disk-pool destinations. Cohesity NetBackup storage topics also describe storage units as part of the recognized storage configurations and note that they can be included in storage unit groups or storage lifecycle policies.

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.

The correct recovery options are recovering the MSDP catalog from an MSDP catalog backup and restoring the MSDP catalog from an MSDP catalog shadow copy. Cohesity documentation explains that the NetBackup Deduplication Manager automatically creates daily MSDP catalog shadow copies and transaction logs. If corruption is detected, the Deduplication Manager restores the catalog from the most recent shadow copy and replays the transaction log so the recovered catalog is current. Cohesity also states that administrators should protect the MSDP catalog with a dedicated MSDP catalog backup policy, because a NetBackup catalog backup does not include the MSDP catalog. The MSDP catalog backup is the second tier of protection and is used when shadow copies are unavailable or corrupt. The official recovery guidance identifies the two MSDP catalog recovery options as Restore from a shadow copy and Recover from a backup, specifically noting that a hardware problem can cause complete loss of the MSDP catalog and shadow copies. Options C and D are not the documented standard recovery choices for bringing the MSDP catalog online, and option E is incorrect because the NetBackup catalog backup excludes the MSDP catalog. References/topics: MSDP shadow catalog, MSDP catalog backup policy, Recovering the MSDP catalog, and drcontrol-based catalog protection.

The unsupported backup storage is BasicDisk. In NetBackup, Media server load balancing is a storage unit group selection method that directs jobs based on a capacity-managed approach, helping NetBackup avoid sending backup work to overloaded media servers. Cohesity NetBackup documentation states that NetBackup evaluates factors such as media server rank, current job count, and available disk space before selecting the most suitable storage unit. Most importantly, the same official topic explicitly states that Media server load balancing cannot be selected for a storage unit group that includes a BasicDisk storage unit, and a BasicDisk storage unit cannot be added to an existing group where Media server load balancing is already enabled.

This makes option C correct. AdvancedDisk, MSDP, and Media Manager storage are valid NetBackup storage technologies used in storage unit group designs, though the recommended selection method can vary by storage type. Cohesity documentation notes that Failover is recommended for AdvancedDisk, MSDP, and OpenStorage, while Media server load balancing remains a selectable storage unit group method for supported configurations. Reference topics: Configuring storage unit groups, Storage unit selection criteria within a group, and Media server load balancing.

The correct answer is C because the failure is an authorization problem on the NetBackup client, not a basic network-connectivity failure. The job output explicitly states that nbumaster8 “is not an authorized server for host nbclient1,” followed by status 59: access to the client was not allowed. Cohesity NetBackup documentation maps status code 59 to “Access to the client was not allowed.” The controlling configuration is the client’s SERVER list. Cohesity states that the SERVER entry defines the list of NetBackup primary and media servers that can access the NetBackup client, and that media servers or other primary servers must be added for that client. Cohesity also explains that on UNIX servers and clients, the SERVER entries in bp.conf define the NetBackup servers that are allowed access, with additional entries identifying servers that can initiate scheduled backups. Therefore, the client rejected the backup request because the requesting server name was missing from the client’s server list or did not match the expected resolved name. References/topics: Status code 59, SERVER option for NetBackup clients, bp.conf, Host Properties > Clients > Servers, and NetBackup host-name authorization.

The replication job starts when the force interval for small replication jobs is reached. NetBackup SLP settings control how Storage Lifecycle Policy jobs are maintained and executed for the selected primary server. Cohesity documentation identifies these as SLP settings used to customize how SLP jobs run. For AIR replication batching, the controlling parameter here is SLP.MIN_SIZE_PER_REPLICATION_JOB. Official NetBackup documentation defines it as the smallest batch size that can run as a single replication job and states that the job does not run until enough images accumulate to reach that size, or until the force interval for small replication jobs is reached. (veritas.com)

In this scenario, three backups of 5GB each create only 15GB of eligible replication data. That is below the configured 20GB threshold, so NetBackup does not start the replication job based on size. Because the backup window has closed and no additional backup images will arrive, the batch cannot reach 20GB. NetBackup therefore submits the small replication batch when the oldest image reaches the configured 60-minute force interval. The force interval is specifically designed to prevent NetBackup from waiting too long before submitting a small replication job. (veritas.com)

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 default summary interval is 24 hours. In NetBackup Appliance AutoSupport/Call Home behavior, when Call Home is enabled and a monitored hardware or software failure occurs, the appliance uploads diagnostic and monitoring information to the AutoSupport server and also generates email notifications to the configured recipient list. The official Appliance AutoSupport Reference Guide describes three email notification types: an initial error notification when the failure is detected, a resolved notification when the failure clears, and “a 24-hour summary by email” for unresolved errors. The NetBackup Appliance Security Guide states the same operational sequence: the appliance sends an error email, a resolved email, and a 24-hour summary of currently unresolved errors. Therefore, 15 minutes, 1 hour, and 12 hours are not the documented default intervals for unresolved-error summary notification. Those values may resemble polling or alerting intervals in other monitoring systems, but NetBackup Appliance Call Home uses the daily summary model to reduce repeated notifications while keeping administrators informed of unresolved conditions. Reference topics: Appliance AutoSupport Reference Guide – About Call Home, Settings > Notification > Alert Configuration, and NetBackup Appliance Security Guide – Call Home alert behavior.