Network

Booting, Installing, Recovery, and Sharing in a vPars Environment from DVD / CDROM / Tape / Network

Page 4 of 6

environment doesn’t have an OS yet if you’re using

this option; therefore there are no drivers available.

(iii) Kernel: You can not use the ke rnel from another

vpar since neither the kernels nor the boot disks are

shared among vpars.

(b) Starting with A.03.03 and A.04.02 for PA-systems:

You Can Install Subsequent Boot Disks using TAPE

Drives from within a vPars Environment.

DVD/CDROM functionality remains unchanged

The A.03.03 and A.04.02 vPars Monitor provides the

capability to now see a bootable tape device. This is

accomplished through an additional path attribute of “TAPE”

as shown in section IV below. This functionality only applies

to tape. The DVD/CDROM boot limitations still remain.

Ignite-UX works differently and is supported for booting within

a vPars environment. From within a running vpar, you can

use the “vparboot” command and point to an existing Ignite-

UX server. The Ignite-UX Server is accessed through the

drivers of the running vpar for PA-systems and the target vpar

for IPF systems and the respective mini-kernel (WINSTALL or

IINSTALL) is loaded into memory. The running vpar then

gives the mini-kernel to the vPars Monitor. The vPars Monitor

can then use it to boot the target vpar. The vPars Monitor

does not access the Ignite-UX server directly nor does it access

any boot install devices directly. From this point, you can

follow the standard Ignite process.

IV. Archiving / Backing-up and Recovering vpars

A. Archiving /Backing-up

vpars can be archived or backed-up to tape (make_tape_recovery) or to an Ignite-UX server

(make_net_recovery). Both of these methods may be done while in a vPars environment and

while other vpars are up and running.

B. Recovering vpars

vpars can be recovered from either a tape image or a network image.

1. Tape Image