Operating Systems

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.

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.

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 bprecover command is the NetBackup utility specifically used for recovering the NetBackup catalog database during disaster recovery scenarios. bprestore is used for restoring client data, not catalogs. dbrecover and ndbrestore are not NetBackup commands, and bpcatrecover does not exist as a standard NetBackup command.

The 'Take checkpoints every' policy attribute allows NetBackup to periodically save backup progress. If a backup fails, it can be restarted from the last checkpoint rather than from the beginning. 'Cross mount points' controls whether backups cross filesystem boundaries. The other options relate to image restore information and disaster recovery, not checkpoint-based restart capability.

The NetBackup catalog consists of three main components: the Image database (contains backup image metadata), a Relational database (stores all catalog information), and NBU configuration (NetBackup configuration data). 'Net backup database' and 'Backup policies' are not catalog components.

To use duplicate tapes as primary copies for restores, use bpchangeprimary (changes a copy from duplicate to primary) or bpimage (manages image information and can change copy attributes). bprecover is for disaster recovery, bpexpdate changes expiration, and bprestore is for performing restores (not changing copy status).

SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS are the key NetBackup parameters for performance tuning on media servers. They control how much data is buffered and how many buffers are used during read/write operations. UPDATE_INTERVAL and REFRESH_INTERVAL are for EMM database polling. DENSITY_DATA_BUFFERS is not a valid parameter.

During restoration, NetBackup checks the NetBackup database (backup metadata), EMM database (media and device information), and NetBackup Logs (for detailed operation records). NetBackup Reports (C) is for reporting, not restoration checks. Image database (E) is not a standard NetBackup component.

NetBackup 6.5 supported specific client platforms based on release timelines (around 2008). Option A (Windows 2000) was supported in NetBackup 6.5 era. Option C (Windows 2003) was a primary server platform for that version. Option E (Solaris 9) was a supported Unix platform. Option B (Windows NT 4.0) was end-of-life well before NetBackup 6.5 and unsupported. Option D (Solaris 7) was also obsolete by the NetBackup 6.5 timeframe. These options reflect the platforms actively maintained when NetBackup 6.5 was current.

Windows Server 2003 Enterprise Edition supported 1 to 8 processors. This was a key differentiator from the Standard Edition which supported 1-2 processors, and the Datacenter Edition which supported 8-32 processors.

ClearCase does not support the MS DOS operating system. ClearCase requires modern operating systems like Unix/Linux, Windows NT-based systems, or macOS. MS DOS is a legacy 16-bit OS that lacks the filesystem, security, and multitasking features ClearCase requires for its version control operations. The answer No (option B) is correct.

Canonical Ltd. is the company that sponsors and develops Ubuntu Linux. They provide commercial support, development resources, and coordination for the Ubuntu operating system, which is a widely-used Debian-based Linux distribution.

IBM Rational ClearCase supports multiple Unix-based operating systems for version control and configuration management. AIX (IBM's Unix), HP-UX (Hewlett-Packard's Unix), and Linux are all supported platforms. While Solaris support may have existed in some versions, the question focuses on the core supported Unix variants.