Pass the Cohesity Cohesity Protection Professional COH-285 Questions and answers with CertsForce

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)

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 Enable FIPS mode option is presented during a fresh NetBackup installation of primary, media, client, or clustered server software. Cohesity NetBackup Installation Guide procedures show that, during local, remote, or clustered server installation, the installer displays the FIPS Compliance in NetBackup screen where the administrator can enable or disable FIPS mode; by default, FIPS mode is disabled. The guide further states that enabling FIPS causes the NetBackup installer and subsequent operations to run in FIPS mode, and that enabling it during clustered installation applies it to the nodes added on the NetBackup Remote Hosts screen. Client installation follows the same model: the Windows client installation procedure includes a FIPS Compliance in NetBackup screen where FIPS mode can be enabled or disabled. Option C is incorrect because Cohesity explicitly states that NetBackup does not support changing FIPS mode during upgrade; it must be enabled before upgrade or after upgrade as a post-install configuration. Reference topics: NetBackup Installation Guide, FIPS Compliance in NetBackup, and Enable FIPS mode on NetBackup during installation.

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.