Software Development and Management

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.

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.

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.

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.

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.

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.

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.

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.

Before catalog recovery, you need physical access to tapes (configure drives and inventory the library to locate them) and the catalog recovery file itself (F). Storage unit configuration (B) is done in normal setup, and moving media to Catalog Backup pool (D) is part of the process, not a prerequisite. The NBU-Catalog policy (E) is for ongoing catalog backups.

Before deleting an Advanced Disk pool, all backups must be expired (A) - you can't delete a pool with active backups. Also, the storage unit must be deleted (D) as it references the pool. Removing volumes (B) isn't required since disk pools don't use traditional volumes. Deleting the storage server (C) or taking media server offline (E) are unrelated.

Storage Snapshot Option (SSO) provides dynamic sharing of individual tape drives (B) - multiple servers can share drives on demand, and heterogeneous SAN-ready storage (D) - supports different OS platforms accessing the same SAN storage. Data encryption (A) is a separate feature. Disk-based protection (C) is not specific to SSO.

NetBackup media server installation has specific prerequisites. Option A is correct because other backup software can conflict with NetBackup's drivers and resources. Option C is correct because mutual recognition between servers and clients is essential for backup/restore operations. Option D is correct because NetBackup only supports specific hardware and OS combinations - unsupported configurations fail. Option B is incorrect because disk-based storage units don't require tape drives. Option E is incorrect because NetBackup supports in-place upgrades without removing previous versions.

Before installing NetBackup 6.5, reviewing specific documentation prevents problems. Option A (Release Notes) is correct because it contains known issues, bug fixes, and critical updates. Option B (Hardware Compatibility Guide) is correct because it lists supported hardware and any restrictions. Option D (OS Compatibility Guide) is correct because it specifies supported OS versions and patch levels. Options C and E are likely duplicates or incorrect document titles - NetBackup uses 'Compatibility Guide' terminology, not 'Supported List'. These documents help avoid unsupported configurations that cause installation failures.