NetBackup Administration and Configuration

In Unix NetBackup environments, global properties and configuration settings are stored on the Master Server. The Master Server maintains the centralized configuration database that applies to the entire NetBackup domain. Media servers and EMM servers have their own specific roles, but global properties are centrally managed on the Master Server.

The file /usr/openv/volmgr/vm.conf is created only when devices are actually added to the NetBackup configuration. This file stores the volume manager configuration including device mappings and settings. Until devices are added, there is no configuration data to store, so this file does not exist. The other paths listed either have incorrect directory structures or serve different purposes.

When troubleshooting media errors, the 'errors' file provides detailed information about when errors occurred and which hardware components (tape drives) were involved. This log file is essential for diagnosing whether problems are specific to a tape volume or a particular tape drive. The mediaDB, bpdm log, and bpbkar log serve different purposes - mediaDB is the database, while bpdm and bpbkar are specific process logs.

Synthetic backups in NetBackup are supported for policy types Standard and MS-Windows-NT. These policy types allow the creation of synthetic backups which combine existing backup images to create full backup images without reading from the client. DataStore policy types are not applicable for synthetic backups in traditional NetBackup configurations.

A volume pool in NetBackup is a logical collection or grouping of volumes (tapes or other storage media). It provides a way to categorize and manage volumes for different purposes, such as separating backups by type, retention requirements, or application. While volumes are often tapes, the term 'volume' is the correct abstraction - it includes tapes but also other media types. Drives are hardware devices, not what volume pools contain.

To upgrade to NetBackup 6.5, you must have at minimum NetBackup 5.0 MP4 installed. This version provides the necessary foundation components and database schema that the 6.5 installer requires as a baseline. Versions earlier than 5.0 MP4 lack critical dependencies needed for a successful upgrade.

The bptm (NetBackup tape manager) log is the correct log to monitor for multiplexing performance analysis. This log shows how many backup streams are being written together to tape, buffer usage, and throughput per stream. By examining bptm entries, you can see if multiplexing is underutilized or causing contention, helping you determine if adjusting the multiplex count would improve backup performance.

bpbkar32 is the NetBackup backup process that runs on the client and is responsible for reading data from the client filesystem. It traverses directories, reads files, applies exclude/include lists, and sends the data stream to the NetBackup media server. bprd is the request daemon, bpcd is the client daemon that accepts connections, and bpbackup is a command-line utility that initiates backups but does not perform the actual data reading.

NetBackup license keys are installed in the /usr/openv/var directory on Unix systems. Specifically, the license file is typically located at /usr/openv/var/license.txt or a similar path. This directory contains NetBackup configuration and variable data files. The /usr/openv/netbackup directory contains binaries and scripts, /usr/openv/volmgr is for volume management, and /usr/openv/db contains the NetBackup catalog database files.

NetBackup freezes tapes when excessive write errors occur during backup operations. When a tape media experiences repeated write failures beyond a configured threshold, NetBackup automatically freezes it to prevent further backup attempts that could fail or compromise data integrity. This protects backups from being written to unreliable media. Read errors during restore operations do not freeze tapes. Using unlabeled or unformatted tapes triggers labeling or formatting processes rather than freezing.

bpclntcmd is the NetBackup command used to troubleshoot client connectivity issues. It tests communication between the master/media server and the NetBackup client, checking if the client daemon (bpcd) is responding and verifying network connectivity. This makes it the ideal tool for diagnosing Status Code 54 (connection timeout). nbping is not a standard NetBackup command, bpverify verifies backup image integrity, and there is no bpconnect command.

tpconfig is the NetBackup command used to configure tape drives and robotic library devices. This utility launches the device configuration interface where administrators can add, modify, or remove tape drives and robotics. tpautoconfig automatically detects devices but is not for manual configuration. tpreq handles tape mount requests, and tpext is not a standard NetBackup command. The tpconfig command is essential for setting up storage infrastructure.

NetBackup manual (man) pages are located in /usr/openv/man on Unix systems. This directory contains the documentation for NetBackup commands and utilities, accessible via the man command. The path is relative to the NetBackup installation directory /usr/openv. Option A incorrectly places man under netbackup subdirectory, option C is the volume manager directory, and the correct location does exist, making option D incorrect.

NetBackup Operations Manager (NOM) was introduced with NetBackup 6.X versions. NOM is a web-based management console that provides centralized monitoring and administration. It was not available in NetBackup 4.X or 5.X releases, making option B the correct answer. NOM represents a significant management enhancement in the 6.X release cycle and requires a minimum of NetBackup 6.0 to function.

The disaster recovery e-mail from hot catalog backup includes the Media Server name, Catalog Recovery Media information, and the DR file name and location. This e-mail provides essential information for disaster recovery by identifying which server holds the catalog backup, where the catalog recovery media is located, and how to access the disaster recovery file needed to restore the NetBackup catalog after a catastrophic failure. Options A and B incorrectly reference EMM server, and option C uses 'Critical Backup' instead of 'Catalog'.

Staged capacity managed retention in NetBackup storage lifecycles is indeed only available on disk storage units. This feature allows automatic movement of backups between different storage tiers based on retention policies. Option B is false because backups can be ejected early if space is needed. Option C is false because data classifications are not required for tape. Option D is false because backup types in storage lifecycle context refer to Full, Differential, and Incremental, not backup/duplicate/catalog.

To configure NetBackup database (catalog) backups and resolve the 'Hot catalog backup is not configured' message, you must create a policy with policy type NBU-Catalog. This is a specialized policy type designed specifically for backing up the NetBackup catalog database. Option B (Sybase) is incorrect because while the catalog uses Sybase internals, NBU-Catalog is the correct policy type. Option C (Standard) cannot protect the catalog. Option D (MS-Windows-NT) is for Windows file system backups, not catalog backups.

The check_coverage command is specifically designed to verify that all configured clients and their volumes or file systems are covered by existing backup policies. It reports any gaps in coverage, ensuring no data is left unprotected. bp_testall is used for testing backup operations, bpconfirm is for confirming successful backups, and checking Backup_All in every policy is not a practical or systematic approach.

NetBackup automatically freezes tapes that have been used for catalog backups to prevent them from being overwritten with regular backup data. The catalog is critical for disaster recovery, so protecting these tapes is essential. A full tape is not frozen; it's simply marked as full and won't be used for new backups. Expired tapes can be reused, not frozen. A tape already in use would be in a different state.