In a scenario involving a NetBackup Appliance upgrade to 11.2 where VxUpdate repository space is limited to 15 GB on the master server, and multiple platform client packages need population, which actions prevent repository overflow while enabling selective deletions after phased rollouts?
suse_ppc64le until phase 2
B. Monitor space with df -h /usr/openv/var/global/vxupdate after each nbrepo -add, setting a script to alert at 80% utilization via threshold 12 GB
C. After phase 1 rollout, execute nbrepo -delete ID=3 for obsolete 10.3 packages listed via nbrepo -list, verifying EMM metadata removal
D. Configure deployment policy with -limitConcurrentJobs 50 to stagger upgrades, reducing temporary staging cache on the media server filesystem
Answer: A, C
Explanation: The VxUpdate repository on a NetBackup Appliance master server requires careful space management, as full population for all platforms and versions can exceed 20 GB; selectively add high-priority packages like vxupdate_nbclient_11.2_windows_x64.sja and vxupdate_nbclient_11.2_redhat_x64.sja using nbrepo -add, which places them in /usr/openv/var/global/vxupdate and updates EMM, deferring less critical ones to avoid overflow within the 15 GB limit. Post-phased rollout, identify and delete unneeded packages (e.g., ID=3 for 10.3 variants) using nbrepo
-delete ID=3 after listing with nbrepo -list, which removes both filesystem artifacts and database metadata to free space; concurrent job limits in policies control deployment pacing but do not directly impact repository storage, while space monitoring via df is manual and not automated in standard VxUpdate.
An administrator notices a spike in failed backup jobs in NetBackup 11.0. Which
A. Prioritize adding vxupdate_nbclient_11.2_windows_x64.sja (2.5 GB) and vxupdate_nbclient_11.2_redhat_x64.sja (1.8 GB) using nbrepo -add, skipping
command should be used to generate a report detailing the failure reasons for all jobs in the past 7 days?
bpdbjobs -report -failed -days 7
nbreport -failure -detail -timeframe 7d
nbdeployutil --failure --report
nbstlutil -jobs -failed
Explanation: vxupdate status provides current appliance update state and details about installed patches and updates.
incrementals fails due to metadata mismatch. Which CSI attribute synchronizes volume metadata during optimized synthesis?
A. Kubernetes Policy = CSI; Index Rebuild = Yes
B. Volume Snapshot = True; Synthetic PV = Optimized
C. PV Retention = Target; Component Sync = Full
D. CSI Metadata Sync = Enabled in Synthetic Answer: D
Explanation: Enabling CSI Metadata Sync in the synthetic operation aligns volume metadata across components, enabling successful PV synthesis. Volume Snapshot is base; Retention is SLP; Index is for search.
Which combination of NetBackup settings is required to ensure Sheltered Harbor endorsement compliance related to data retention and immutable backups?
A. Enable immutable storage for backup copies
B. Set backup retention policies to meet Sheltered Harbor timeframes
C. Disable incremental backups to avoid data gaps
D. Configure encrypted backup vaults with access logging
For implementing synthetic backups in NetBackup 10.4 for Kubernetes persistent volumes with Cohesity, the policy uses CSI snapshots. Synthesis from multiple PV
Answer: A,B,D
Explanation: Sheltered Harbor mandates immutable backups to prevent tampering, retention policies to retain data for mandated durations, and encrypted vaults with access logging for security and auditability. Disabling incremental backups is unnecessary and not a Sheltered Harbor requirement.
What is the result of setting the Storage Unit Group attribute “Max Jobs per Storage Unit” to 2 and having a group with 3 storage units?
The maximum of 6 concurrent jobs can be processed by the group
No more than 2 jobs will ever run concurrently, regardless of units
Each storage unit can serve unlimited jobs, overridden by group limit
Answer: A
Explanation: Setting limits per unit means each unit can handle up to 2 jobs, so with 3 units total concurrency is 6.
Which NetBackup setting controls automatic job suspension duration before cancelling the job?
A. JOB_SUSPEND_TIMEOUT in bp.conf
B. SUSPEND_DURATION_LIMIT in Admin Console
C. MAX_JOB_SUSPEND_TIME in policy attributes
D. AUTO_CANCEL_AFTER_SUSPEND timeout parameter Answer: A
Explanation: The JOB_SUSPEND_TIMEOUT parameter in bp.conf defines how long jobs may remain suspended before being cancelled automatically. The other options are not valid NetBackup settings.
An optimized duplication job from MSDP to a cloud OST storage unit fails with status 191 (no images found) due to missing fingerprint metadata. The SLP has a 48-hour
The setting disables new jobs once 2 total jobs run in the group
duplication window. Which settings and commands ensure metadata sync?
Configure SLP operation 2 with -preservemetadata 1 via nbstl -modify -operation 2
Run nbdevconfig -changepd -storage_server -stype PureDisk -setattribute MetadataSyncEnabled
Set bp.conf OPT_DUP_METADATA_RETENTION=72h on source media server
Use nbstlutil stlilist -slp -validate to check metadata propagation
Answer: A, B, C
Which syntax correctly enables incremental backups for Amazon RDS workloads using NetBackup CLI?
A. nbbackup -policy -backupType incremental -target RDS
B. bpbackup -policy -incremental -target RDS
C. bpincrbackup -policy -target RDS
D. nbbackup -policy -type inc -service RDS Answer: B
Explanation: bpbackup with -incremental flag and target specified is the correct syntax for incremental backups; others are invalid.
An administrator is setting up optimized duplication between two NetBackup domains to replicate deduplicated data to a secondary site. Which command verifies the replication status?
A. bpimagelist -backupid -rl
B. nbreplicate -status -target_stu
C. nbdevquery -listdv -stype PureDisk
D. bpstsinfo -lsu -storage_server
Explanation: Enabling -preservemetadata 1 in the SLP operation ensures fingerprint metadata is transferred during optimized duplication. Setting MetadataSyncEnabled via nbdevconfig on the MSDP server guarantees metadata consistency with the cloud OST. Configuring OPT_DUP_METADATA_RETENTION to 72h in bp.conf retains metadata beyond the duplication window, preventing status 191 by ensuring availability for cloud- side imports.
Answer: B
Explanation: The nbreplicate -status command checks the status of optimized duplication jobs between NetBackup domains, ensuring deduplicated data is successfully replicated to the target storage unit. The other commands are used for different purposes: bpimagelist for listing backup images, nbdevquery for disk volume details, and bpstsinfo for storage server information.
In securing NetBackup hosts with certificates, what is the role of host ID certificates?
They control user console login access
C. They encrypt catalog databases on NetBackup servers
D. They authenticate and encrypt communication between NetBackup components Answer: D
Explanation: Host ID certificates enable mutual authentication and encryption between NetBackup servers, media servers, and clients to ensure secure communication. They do not sign images, encrypt catalogs, or manage console user access.
A high-difficulty tuning scenario for NDMP backups to a Cohesity Appliance NAS filer shows slow transfer rates of 50MB/s on a 10GbE link, with ndmpd log: "ndmpd (pid=66666) mover stalled: Cohesity NAS protocol mismatch, expected NFSv4.1 but received v3, status: 5150, MOVER_READ_WINDOW_SIZE=64KB." The NDMP policy uses Direct NDMP=Yes, preferred network=10GbE, and the filer's export is coh_nas_export --path /backup --protocol NFSv4.1 --access rw. The backup selects 1PB of data with multi-streaming=16 streams, and iperf tests confirm 9.5Gbps raw bandwidth.
Which three NDMP configuration changes and commands will align protocols and boost rates to >500MB/s?
A. Set NDMP_MOVER_WINDOW_SIZE=1MB in ndmp.conf on the filer, then inquire with ndmp_query_host -h -port 10000 -protocol NFSv4.1 to verify
They are used to sign backup images for tamper-proof storage
Update policy via bpplinfo -modify -pt 4 -add_direct :/backup -streams 16, followed by ndmp_start_backup -policy -force to test
On Cohesity, run coh_ndmp_config --filer --protocol NFSv4.1 --window 1024KB -- mtu 9000, then restart ndmpd with kill -HUP
Execute ndmpadm connect 10000; ndmpadm set mover -window-size 1MB -language en; ndmpadm log debug to enable logging and confirm v4.1 handshake
Use vm.conf NDMP_DEFAULT_PROTOCOL=NFSv4.1 on the master, then nbemmcmd UPDATE_NDMP_HOST -host -preferred_protocol 4 to enforce v4.1 for the
host
Answer: C, D, E
mover parameters for better throughput, and ndmpadm log debug enables detailed logs to confirm the v4.1 handshake and 64KB->1MB window upgrade. Using vm.conf NDMP_DEFAULT_PROTOCOL=NFSv4.1 sets the global default on the master server, and nbemmcmd UPDATE_NDMP_HOST -host -preferred_protocol 4 updates the host record in EMM to prioritize v4.1, ensuring multi-stream NDMP backups leverage the full 9.5Gbps for >500MB/s rates.
What is the correct syntax for adding a NetBackup master server to a deduplication pool via CLI?
A. nbpool -modify -poolname DedupPool1 -addserver master01.example.com
B. nbpool -edit -name DedupPool1 -server add master01.example.com
C. nbdedupe pool add-server -name DedupPool1 -server master01.example.com
D. nbpool -addmasterserver -pool DedupPool1 -server master01.example.com Answer: A
Explanation: The command to modify an existing pool and add a server is "nbpool
-modify -poolname ... -addserver ..."
Explanation: On Cohesity, running coh_ndmp_config --filer --protocol NFSv4.1 -- window 1024KB --mtu 9000 configures the NAS export for v4.1 with larger windows and jumbo frames to match 10GbE, and restarting ndmpd with kill -HUP applies without downtime, resolving the protocol mismatch. Executing ndmpadm connect 10000 connects interactively, ndmpadm set mover -window-size 1MB -language en sets the
An administrator wants to be notified immediately of critical backup or restore failures. Which NetBackup feature should be configured?
Job notification subscriptions with email alerts focused on failure statuses
Incident response modules external to NetBackup
Daily backup job summary reports
Automatic job retries on failure
Answer: A
Explanation: Job notification subscriptions with filtering enable immediate email alerts on failures, facilitating prompt response.
Administration Console reports fragmented images preventing cleanup, with status 423 (storage full). Which console disk management steps and CLI defragmentations free space?
A. Console: Storage > Disk > right-click pool > Properties > Defragment > Schedule Daily, then nbdevconfig -defragment -dp -force -v
B. Navigate to Media > Images on Disk > Expire Fragments > Auto, verified by nbdevquery -listdp -dp | grep -i fragmented=0
C. From console Activity Monitor > Disk Cleanup > Run Now > Priority High, followed by tpconfig -dmanage -delete_all -type BasicDisk -pool
D. Use Storage > Volumes > right-click volume > Evict Images > Non-duplicated, checked by bpstsinfo -dp -size
Answer: A, B
Explanation: Scheduling defragmentation via Storage > Disk > Properties > Defragment in the console consolidates the 110 TB fragments, with nbdevconfig -defragment -force executing it verbosely to drop below 95% watermark. Auto-expiring fragments under Media > Images on Disk > Expire Fragments frees non-critical space, verified by nbdevquery output showing fragmented=0, resolving status 423 in BasicDisk pools.
A company uses NetBackup 11.0 to protect a Kubernetes cluster running cloud-native applications. The administrator needs to recover a specific namespace after a data
In NetBackup 10.5, managing a 110 TB BasicDisk pool with high watermark at 95%, the
corruption incident. Which command ensures the recovery is performed with data integrity verification?
bprestore -C -t k8s -namespace
nbk8s restore --backupid --namespace --verify-integrity
bpduplicate -id -dstunit -namespace
nbcloud restore --source --target --verify
Answer: B
Which encryption cipher suite is supported by NetBackup's KMS for deduplication pools?
A. AES-256-GCM
B. ChaCha20-Poly1305
C. RSA-2048
D. DES-CBC
Answer: A
Explanation: AES-256-GCM is industry-standard for secure encryption used in dedup pool encryption. ChaCha20-Poly1305 and RSA-2048 are used elsewhere, and DES-CBC is deprecated.
A NetBackup environment must comply with an SLA requiring 99.9% backup success rate. Which monitoring practices ensure compliance?
A. Configure OpsCenter to generate daily backup success rate reports
B. Set up alerts for failed backup jobs using nbemmcmd
C. Monitor deduplication efficiency with nbstlutil
D. Use bpdbjobs to analyze job completion status daily
Explanation: The nbk8s restore command with --verify-integrity ensures that the Kubernetes namespace is restored from the specified backup ID while verifying data integrity. The bprestore command is not specific to Kubernetes. The bpduplicate command is for duplicating backups, not restoring. The nbcloud command is for general cloud operations, not namespace-specific recovery.
Answer: A,D
Explanation: Configuring OpsCenter for daily backup success rate reports provides visibility into backup performance, helping track the 99.9% success rate. Using bpdbjobs to analyze job completion status daily identifies failed jobs and trends, ensuring SLA compliance. Setting alerts with nbemmcmd is proactive but does not directly measure success rates. Monitoring deduplication efficiency with nbstlutil is unrelated to backup
success rates.
A. Configure IA mount as SMB share: nbdiscover -backupImage 67890 -mount SMB://scanhost/share -expireAfter 24h
B. Fallback to NetBackup Malware Scanner: nbmscan -imageID 67890 -scanner nbmalware -host scanhost1 -forceRemount
C. In Web UI > Storage > MSDP > Instant Access, enable "Allow third-party scanner access" for cloud imported copies
D. Verify mount with nbimgr -listMounts | grep 67890, checking status "mounted: SMB active" before scan initiation
Answer: A, C
Explanation: For imported S3 images in MS-Windows policies, "mount point unavailable" errors occur if Instant Access (IA) shares are not configured for scanner access; enable in Web UI > Storage > MSDP > Instant Access > "Allow third-party scanner access" to permit mounts for malware tools like MS Defender. Mount via nbdiscover -backupImage 67890 -mount SMB://scanhost/share -expireAfter 24h for persistent SMB access (NFS for Linux), expiring after use to free resources; fallback uses nbmscan with -scanner nbmalware but requires successful remount (-forceRemount retries), and nbimgr -listMounts confirms status for troubleshooting, ensuring scans proceed on 500 GB datasets without full restore.
In a scenario where a NetBackup global deduplication pool is nearing capacity, what actions should be taken to maintain backup performance without losing deduplication
NetBackup Appliance malware scans on imported cloud images (S3) fail with "mount point unavailable" for 500 GB sets. Which Instant Access configurations and fallback commands resolve for MS-Windows policies?
benefits?
Expand storage capacity for deduplication pool by adding more disk units
Reconfigure backup policies to disable deduplication temporarily
Purge older duplicated data based on retention policies to free up space
Enable compression at client level to offset deduplication pool consumption Answer: A,C
Explanation: Adding storage expands deduplication capability, and purging expired data according to policies helps reclaim space. Disabling deduplication or changing compression options can reduce dedup benefits or have little effect on pool consumption.
media server?
A. Check client connectivity logs
B. Restart the media server and watch startup logs
C. Run vmquery –device or view Device Status in the Administration Console
D. Run bpdevice -list on the client Answer: C
Explanation: Device queries and device status in the Administration Console provide current connectivity and recognition status for devices on media servers.
Which NetBackup CLI command can be used to manually retry a failed backup job from the last checkpoint?
A. bpdbjob -resubmit
B. bpbackup -retry -jobid
C. There is no direct retry command; the job must be manually resubmitted
D. bpbackup -restart
Answer: C
How do you verify if a device is properly connected and recognized by NetBackup on a
Explanation: NetBackup does not provide a direct CLI command to retry failed jobs from checkpoints. The operator must cancel the failed job and resubmit the backup manually through the Console or CLI.
A NetBackup Appliance is reporting error code 2067 (Disk volume not found). What should you do to resolve this?
Check the disk pool configuration and recreate the volume
Restart the NetBackup services
Update the appliance firmware
Explanation: Error code 2067 indicates that the specified disk volume is missing. Checking the disk pool configuration and recreating the volume resolves this issue. Restarting services, updating firmware, or verifying network configuration does not address a missing disk volume.
An administrator is troubleshooting a failed optimized duplication job with the error: "Replication failed due to invalid storage server credentials (status 191)." Which command resolves this issue?
A. tpconfig -update -storage_server -sts_user_id -password
B. nbkmsutil -modify -keyname -keygroup
C. bpstsinfo -update -storage_server -password
D. nbdevconfig -changests -storage_server -password Answer: A
Explanation: Status code 191 indicates invalid credentials for the target storage server during optimized duplication. The tpconfig -update command updates the storage server credentials with the correct user ID and password, resolving the issue. The other commands are used for KMS key management or storage server configuration but do not address credential updates.
Verify the network configuration Answer: A
A NetBackup Powered Appliance is configured with a deduplication pool. To optimize performance for a high-throughput backup job, which parameter should be adjusted in the pd.conf configuration file?
BLOCK_SIZE=128
MAX_IMG_DISK=100
NUMBER_DATA_BUFFERS=64
SIZE_DATA_BUFFERS=262144
Answer: D
processed. Other parameters like BLOCK_SIZE or MAX_IMG_DISK are not valid for deduplication tuning, and NUMBER_DATA_BUFFERS affects the number of buffers, not their size.
Explanation: The SIZE_DATA_BUFFERS parameter in the pd.conf file controls the buffer size for deduplication I/O operations. Increasing it to 262144 (256 KB) optimizes performance for high-throughput backup jobs by allowing larger data chunks to be