technology Online Quiz - 1683

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).

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.

To route traffic through the backup network, the media server must use its -bkup hostname (B) so clients can connect via that interface. Clients also need the -bkup hostname in their NetBackup server list (C) to know which address to use. Configuring client-side network settings (A) or adding clients to media server lists (D) won't direct the traffic correctly.

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.

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.

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.

The vxlogcfg command in NetBackup is used for log configuration and management. Option A is correct because vxlogcfg can display current log settings for specific originators (components). Option C is correct because it lists all configured products in the logging system. Option D is correct because it can show log files and their locations for specified originators. Options B (copying files) and E (managing rollover) are not vxlogcfg functions - those are handled by other commands or mechanisms.

NetBackup mixed version environments require strict version hierarchy rules. Option B is correct because clients must not run a higher version than their media server to avoid compatibility issues. Option C is correct because media servers cannot exceed their master server's version - the master is the highest in the hierarchy. Option E is correct because all master servers in a domain must run the same version for proper coordination. Option A is backwards (masters should be highest). Option D is incorrect because media servers version higher than clients is normal and expected.

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.

Multiple media server installations follow specific NetBackup requirements. Option A is correct because each media server consumes a server license from the license pool. Option C is correct because installation requires root (Unix) or administrator (Windows) privileges to modify system configuration. Option B is incorrect because media servers can be installed locally, not just pushed from the master. Option D is incorrect because only the master server can push installations, not other media servers. Option E is incorrect because disk storage units are valid - tape drives are not mandatory.

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.

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.

P4 tickets typically have a 30-minute response time SLA in most IT service management frameworks. P1 is usually critical (15 min or less), P2 is high (1 hour), P3 is medium (4 hours), and P4 is low priority (30 minutes to 1 business day depending on organization).

Chrysler's brand portfolio includes Chrysler, Dodge, Jeep, and MOPAR (their parts and service division). Option A incorrectly includes Chevrolet (GM brand). Option B excludes Jeep and MOPAR. Option C correctly lists all four Chrysler brands.

In IT Service Management, when a ticket status changes to 'Pending' (awaiting customer input or third-party action), the SLA clock is paused. The clock only runs when the ticket is actively being worked on by the service team. This prevents the service provider from being penalized for waiting periods outside their control.

Quality gates in SERV represent critical approval and delivery points. QG1 confirms initial detailed estimates are approved, while QG2 validates the solution through User Acceptance Testing. Subsequent gates track the production launch and final service request closure, ensuring comprehensive project governance.

DLE in SERV stands for Detailed Level Estimates, which are the comprehensive work and resource estimates prepared for a service request. These estimates provide the projected effort, duration, and resource requirements needed to complete the request before detailed planning begins.

IT Delivery Date in SERV marks when the service request is handed over to the user for User Acceptance Testing (UAT). This is the transition point from development/IT ownership to customer validation, occurring before the actual production deployment.

Service Contracts generate direct revenue for Chrysler through paid maintenance agreements where customers pay for ongoing vehicle service. Unlike warranty work which is a cost obligation, service contracts represent a revenue-generating business model where customers voluntarily purchase coverage.