NetBackup and Hyper-V Virtualization Technologies

Microsoft Application Virtualization (App-V) is the Microsoft technology specifically designed for virtualizing and distributing applications. It allows applications to run without being fully installed on the local machine. MDOP is a suite that includes App-V, RDS is for remote desktop sessions, and WDS is for OS deployment.

In Hyper-V networking, private networks are isolated networks that only allow communication between virtual machines on the same host. They cannot access the host OS or external physical networks. This makes them ideal for isolating VMs for testing or security purposes.

Hyper-V requires three hardware capabilities: 64-bit processor support (x64 architecture), Hardware-Assisted Virtualization (Intel VT-x or AMD-V), and Data Execution Prevention (DEP/NX bit). All three must be present for the role to install. Option D is incomplete; E is the full correct set.

System Center Operations Manager (SCOM) is the monitoring and management suite in the System Center family. It provides performance monitoring, alerting, and health tracking for virtual machines and other infrastructure. Configuration Manager is for deployment, DPM for backup, and VMM for VM management.

On Server Core installations of Windows Server 2008, roles and features are installed using the ocsetup command with the Start /w flag to wait for completion. 'Microsoft-Hyper-V' is the correct package name. Option D is nonsensical syntax.

Hyper-V does not support direct passthrough of USB devices to virtual machines. USB devices must be accessed through the host OS or via Remote Desktop Protocol (RDP) redirection to the VM. The answer is correctly False.

Hyper-V requires physical network adapters that are Ethernet-based. It cannot use ATM, Token Ring (legacy technologies), or wireless adapters for VM network connectivity. Only physical NICs with specific driver support are compatible.

SCONFIG is the Server Configuration tool available on Windows Server 2012 and later. It includes an option to configure Windows Update settings (enable/disable, manual/automatic). For Server 2008, this is done differently via PowerShell or registry.

The Enterprise Media Manager (EMM) server is the NetBackup component that manages resources (tape drives, media, storage units). In standard NetBackup architecture, EMM runs on the Master Server and contains the relational database tracking all backup resources and policies.

To add a client to a NetBackup policy, you modify the policy's Clients list and add the hostname. Backup Selections defines what to back up (paths/file lists), Schedules defines when, and Attributes defines policy options - none of these add clients.

Max Jobs per Client = 2 limits concurrent jobs per client. Even though Allow Multiple Data Streams is enabled (multiplexing drives) and ALL_LOCAL_DRIVES creates multiple streams, the Max Jobs per Client cap restricts active jobs to 2. Additional jobs queue until active jobs complete.

The NetBackup Enterprise Media Manager (EMM) server contains the embedded SQL database that stores all configuration data: policies, clients, media, storage units, and image catalogs. Master/Media/Client servers do not host this database.

The bpps (bp processes) command displays the status of NetBackup daemons and processes on a server. bpnos and bpsl are not valid NetBackup commands. bpverify is for verifying backup images, not process monitoring.

In NetBackup, the primary backup types are Full backup, Differential Incremental backup, and Cumulative Incremental backup. These represent the fundamental backup methodologies that determine how much data is backed up each time. User-directed backups and archives are also valid backup operations in NetBackup. Therefore all listed options represent legitimate backup types or categories.

In NetBackup architecture, storage units are logical entities that represent storage resources. They provide a logical abstraction layer above physical devices like tape drives or disk pools. This logical abstraction allows flexible allocation and management without being tied to specific physical hardware.

The robtest utility in NetBackup is specifically designed for testing and managing robotic tape libraries. It allows administrators to view and manipulate the contents of media access ports (MAPs), which are the entry/exit points for tapes in the robotic library. Other utilities like vmquery, tpconfig, and tpautoconf serve different purposes for volume management and device configuration.

Volume group information is recorded and managed by the Enterprise Media Manager (EMM) server. The EMM server is responsible for maintaining the media database and volume configuration information in NetBackup's distributed architecture. Media servers report to the EMM server, and the master server manages policies but does not directly maintain volume group records.

The Inventory Robot function in the NetBackup Administration console updates the volume configuration by reading the actual contents of the robotic library and reconciling it with the database. It synchronizes the volume database with the physical tape inventory, ensuring accurate tracking of tape locations and status. It does not list ejected tapes, delete media, or unfreeze frozen media - those are separate operations.

A policy's start window defines the timeframe during which new backup jobs can be initiated. If set to 8:00 p.m. to 11:00 p.m., backups can start anytime within that window, but cannot start after 11:00 p.m. Backups that started before 11:00 p.m. may continue running past the window end - only new starts are prohibited. There is no pausing behavior at 11:00 p.m.