NetBackup 6.x Administration

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.

NetBackup writes backup data in tar format and can compress it before writing to storage media. This is a standard archival format that preserves file structure and metadata. GNU cpio, doc, and text are not the formats used by NetBackup for writing backup images.

NetBackup writes data to tapes in tar format, which is a widely-used archival format that maintains file structure and metadata. CPIO is a different archival format not typically used by NetBackup. 'Text Format' and 'Compress format' are not valid media formats for NetBackup tape writes.

On Windows systems, NetBackup temporary files are stored in C:\Program Files\VERITAS\NetBackup\Temp. This is the default installation location for NetBackup on Windows. The other options (Windows folder, VERITAS root, My Documents) are not the correct locations for NetBackup temporary files.

A volume group in NetBackup refers to a physical grouping or location for media tapes within a tape library. It helps organize and manage physical tape resources. A 'logical location for media' or 'drive' would refer to different concepts; volume groups are specifically about physical organization of tapes.

When restoring a UNIX client, you select the 'Standard' policy type. UNIX is not a separate policy type in NetBackup: the policy type refers to the backup method (Standard, MS-Windows-NT, etc.), not the client operating system. The Standard policy type is used for UNIX systems. Linux would also use Standard, and NetWare has its own policy type.

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 bptm (tape manager) and bpdm (disk manager) logs are the primary logs for diagnosing disk and tape storage hardware issues in NetBackup 6.5. nbpem and nbjm relate to job scheduling. bpbrm handles backup requests, and bpdbm manages database operations. nbproxy and bpjpbd are not the correct logs for hardware issues.

RPO (Recovery Point Objective) is the maximum acceptable amount of data loss measured in time. RTO (Recovery Time Objective) is the target time to restore a system or application after a disruption. The other options incorrectly substitute words like 'transfer', 'process', 'real', and 'read' which are not the standard definitions in disaster recovery and backup planning.

NetBackup consists of four main components: Master server (manages backups), EMM server (Enterprise Media Manager, manages media and devices), media server (writes data to storage), and client server (the machine being backed up). Option B is missing EMM. Option C incorrectly includes 'recovery' as a component. Option D would be incorrect because A is the complete, accurate list.

NetBackup 6.x architecture uses three server types: Master server manages backup operations, Media servers handle backup device operations, and EMM (Enterprise Media Manager) stores device configuration and management information. All three are required components in a NetBackup 6.x environment.

The scan command with the -all flag scans all SCSI devices and displays what the operating system can see, making it useful for verifying new tape drive recognition. Other options like scan -os or tape -config are not valid NetBackup commands.

Storage unit groups allow you to combine multiple storage units and apply them as a single unit to policies. By creating a group with only A and B, the policy will use only those specific storage units. 'Any Available' would use all storage units, and the other options suggest incorrect configurations.

Device mappings packages, which contain driver information for specific tape drive models, are installed on the EMM (Enterprise Media Manager) server. This is because the EMM server manages device configuration information for the entire NetBackup environment.

To temporarily suspend backups during maintenance, modifying the policy's schedule with an 'Active Go into effect at date' allows you to skip the Friday window and resume Saturday. The question text contains a copy-paste error ('Which command can be used to help troubleshoot this problem?' doesn't fit the context).

Server groups in NetBackup can include Master servers, Media servers, and NDMP tape servers. EMM (Enterprise Media Manager) servers and NOM (NetBackup Operations Manager) servers cannot be added to server groups as they serve different management functions.

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.

In NetBackup upgrades, master servers must be at the same or higher version than media servers and clients. Therefore, the master can be at 6.5 while media servers remain at 6.0, and media servers at 6.0/6.5 can support older clients (5.1 and 6.0). Clients do not need to match the media server version, and a media server cannot be newer than the master server.

Tapes can be available if they are completely new and unwritten (C), if all images have been manually expired (B), or if images have reached their retention period and expired (E). Option A is incorrect because frozen tapes cannot be overwritten even if expired. Option D creates ambiguity - a tape with mixed expired/unexpired images would not be cleanly available for use.

NetBackup includes three default pools: the NetBackup pool (general backups), Catalog backup pool (for catalog backups), and Data store pool (for disk storage units). The Scratch pool is for available media and Volume pool is a generic pool type, not specifically a default pool.