Practice Free COH-285 Cohesity Certified Protection Professional – NetBackup Appliances Exam Questions Answers With Explanation

The correct setting is Network Connections > Maximum concurrent jobs. In Cohesity NetBackup documentation, the Scalable Storage host property is accessed from Hosts > Host properties, selecting the media server, editing media server properties, and choosing Scalable storage. These settings cover cloud encryption, metering, bandwidth throttling, and network connections between NetBackup hosts and the cloud storage provider. The key requirement in the question is to reduce network use by limiting the number of parallel backup streams. Cohesity documents Maximum concurrent jobs as “the default maximum number of concurrent jobs that the media server can run for the cloud storage server,” and notes that when jobs exceed the allowed connection count, additional backup or restore jobs fail after the maximum is reached. By reducing this value, the administrator directly limits simultaneous cloud backup streams and therefore reduces concurrent network consumption. The other options control different behaviors: Metering interval affects reporting collection frequency, Total available bandwidth defines the cloud connection speed, and Sampling interval controls how often bandwidth usage is measured for throttling. References/topics: Scalable Storage properties, Network Connections, Maximum concurrent jobs, and Cloud storage server bandwidth throttling properties.

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 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 command is vxlogview -o 118 -d D,T,x. Status code 96 commonly indicates that NetBackup could not allocate required media or storage resources, so troubleshooting should focus on the NetBackup Resource Broker, also known as nbrb. Cohesity NetBackup documentation identifies originator ID 118 as nbrb, the NetBackup Resource Broker, which maintains available resource information and locates the physical and logical resources needed for backup and tape restore operations. The vxlogview command is the supported utility for reading unified logs, because unified log files are binary and must be assembled by vxlogview. The -o 118 option filters log records for the Resource Broker originator, while -d D,T,x displays the required fields: date, timestamp, and actual log message text. The command reference defines D as display date, T as display timestamp, and x as display actual log message text. Option C is incorrect because w displays who logged diagnostic/debug messages, not the actual message text. References/topics: NetBackup unified logging, vxlogview, originator IDs, nbrb Resource Broker logging, and status 96 resource allocation troubleshooting.

( 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.)

( 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.)

The correct answer is media servers and clients. Cohesity NetBackup documentation defines VxUpdate as a deployment-management mechanism for updating non-primary NetBackup hosts. The official NetBackup Upgrade Guide states that “VxUpdate provides a policy-based upgrade tool for media servers and clients,” and further explains that the policy format simplifies media server and client upgrades while signed packages are added to the VxUpdate repository on the primary server for later deployment. Cohesity’s Repository management topic reinforces this by stating that the VxUpdate repository resides on the primary server and contains packages that can be deployed to media servers and clients. It also explicitly says that administrators can upgrade NetBackup media servers and clients to a newer NetBackup version with VxUpdate.

Therefore, option D is correct. Option A is incorrect because the primary server hosts the VxUpdate repository and controls deployment, but it is not itself upgraded through VxUpdate deployment policies. Option B and option C are incomplete because VxUpdate is not limited to only one of those host roles. Reference topics: NetBackup Deployment Management with VxUpdate, About VxUpdate, and Repository management.

The correct log to review is nbpem, the NetBackup Policy Execution Manager log. Cohesity NetBackup documentation states that nbpem creates policy and client tasks and determines when jobs are run, and its logging location is install_path\NetBackup\logs\nbpem on Windows and /usr/openv/logs/nbpem on UNIX/Linux. In the scheduled backup workflow, nbpem initiates a backup when the job becomes due. It determines whether the policy, schedule, and backup window are valid, retrieves policy information through nbproxy, and then submits the due job to nbjm to obtain a job ID.

Therefore, when an automatic schedule does not launch a backup at the expected time, the first diagnostic focus is the scheduler and policy-evaluation component, not the later job-control or resource-allocation components. nbjm manages submitted jobs after nbpem hands them off, nbrb brokers resources, and nbemm manages media and device/resource database functions. Since the failure occurs before the job launches automatically, nbpem is the authoritative debug log for determining why the policy schedule did not trigger. Reference topics: Backup process, nbpem logging, and Policy Execution Manager scheduling behavior.

( To configure AdvancedDisk storage in NetBackup, you need to specify the AdvancedDisk storage path and disk group parameters, including the disk type, RAID level, and capacity.)

With ALL_LOCAL_DRIVES and Allow multiple data streams enabled, NetBackup can split each client backup into separate streams per drive or file system; Cohesity documentation states that NetBackup backs up the client and “splits the data from each drive” into its own stream when multiple data streams are enabled. However, the number of streams that can run concurrently is still constrained by job limits. Cohesity’s policy documentation states that concurrent stream count is affected by Maximum jobs per client, Limit jobs per policy, and related storage limits; when Maximum data streams is not explicitly set, NetBackup uses the lower of Maximum jobs per client or Limit jobs per policy. The default Maximum jobs per client is one job, so only one backup stream per client can run. With five clients, that means 5 active backup jobs, not 15.

The storage unit’s Maximum concurrent jobs = 15 does not restrict restores, because Cohesity states this setting controls backup and duplication traffic, not restore jobs. The disk pool’s Maximum I/O Streams = 20 limits read and write streams; restores read backup images and backups write them. Five backups plus ten restores equals 15 total streams, so all 10 restores can run.

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 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 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 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 Staging Schedule option in the Change Storage Units dialog allows you to define a schedule for moving backup data from the staging area to secondary storage, enabling you to optimize your backup storage utilization and reduce storage costs.)

The correct action is to increase the Maximum I/O Streams for the MSDP disk pool. In NetBackup disk storage, the disk pool stream limit is the effective gate for concurrent read/write activity against that pool. Cohesity documentation identifies Limit I/O streams as the disk-pool property that controls read and write streams, and notes that if the limit is reached, NetBackup queues jobs until a volume becomes available. The storage-unit Maximum concurrent jobs setting controls how many jobs NetBackup sends to a disk storage unit, but Cohesity also states that this setting is not the only concurrency limiter and depends on disk-pool and media-server factors. NetBackup performance guidance is more explicit for this scenario: the disk pool Max I/O Streams value sets concurrent read/write operations, while the storage unit concurrent-jobs value addresses backup/restore jobs and does not control secondary operations such as duplications and replications; those are usually dictated by Max I/O Streams. Therefore, increasing storage-unit jobs or SLP priority does not guarantee that AIR replications can run while backups consume all available disk-pool streams. The correct tuning point is the disk pool’s Maximum I/O Streams.

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.