|
|
Planning can and should be done prior to performing your backdate.
The backdate requires downtime and planning it ensures that all
the requirements are met. The sections include:
Determine Your Backdate Method
There are essentially three methods for backdating your system
software version level. The methods are as follows:
Method 1: Using a Customized System Load Tape together with the
Fundamental Operating System (FOS) and Purchasable Products (SUBSYS)
tapes from the earlier release.
The CSLT you use to backdate your system could have been created
under many different circumstance. For example:
During a system update (with no patches)
While installing patches from a PowerPatch tape
While updating and installing patches from a PowerPatch
tape
Method 2: Using Factory System Load Tape (SLT) and Fundamental
Operating System (FOS) and Purchasable Products (SUBSYS) tapes from
the earlier release.
Method 3: Using a Factory Preload Tape (FPT). If your system was
preinstalled at the factory, you must backdate using the FPT.
The system software version level options are:
Backdate from 6.5 to 6.0
Backdate from 6.5 to 5.5
 |
NOTE: Backdating from 6.5 to a release before 5.5 (General
Release) is not supported.
|
To determine which method is optimal for your system and your
situation, call the Response Center, if you have a software support
contract, or your HP representative, before deciding to backdate
your system.
If your Hewlett-Packard representative and you both agree
that backdating your operating system is necessary, follow the steps
below. Please read all the instructions in this chapter before you
begin your backdate. Determine what prior IO devices you will back date to.
Verify Your Requirements
To verify your requirements for backdating:
Review and confirm the process you are going to perform with the
HP Response Center or your representative.
Table D-1 "List of required
materials" has a list of materials required for each of the
possible backdating methods.
Table D-1 List of required materials
Requirement |
Method 1 |
Method 2 |
Method 3 |
CSLT (for the release to which you want to backdate) from the system
you want to backdate. | Required | | |
HP-provided factory SLT (for the release to which you want to
backdate). | | Required | |
HP-provided factory preload tape (FPT) that came with the system. |
| | Required |
Fundamental Operating Software (FOS) tape from the release to which you
want to backdate. | Required | Required | |
SUBSYS tape from the release to which you want to backdate, if you
installed or updated any optional products with that release. |
Required | Required | Required |
A STORE tape with HPSWINFO.PUB.SYS,
NMCONFIG.PUB.SYS, and NMINIT.PUB.SYS from the release to
which you want to backdate. | Required | Required |
Required |
A STORE tape with @.CONFIG.SYS from the release to
which you want to backdate. If this is not available, run SYSGEN
and customized the factory supplied configuration file for your system. |
Recommended | | Recommended |
Current full system backup tapes. | Required | Required |
Required |
Patch tapes (to reapply patches) if you had installed patches onto the
earlier release of the system. | | Required |
Required |
Compatibility Issues
While backdating, you may encounter compatibility issues that arise from
backdating certain purchasable products. Before you proceed, we recommend that
you read:
The Communicator 3000 for the release you are backdating
to, as well as the copy you received with your new release. These
documents provide additional information on backdating specific
products.
Check that any new disk drive in the configuration is supported
on the release you are backdating to.
Patch Considerations
If you have applied patches to your level 6.0 or 5.5 system
software, read the section appropriate to the backdating method
you are using. The sections are:
Method 1: Using a CSLT
The CSLT you use to backdate your system could have been created
under many different circumstances. For example:
During a system update (with no patches)
While installing patches from a PowerPatch tape
While updating and installing patches from a PowerPatch tape
 |
NOTE: If you installed patches using a PowerPatch tape, you
must use the CSLT generated during the process.
|
If you installed patches from a PowerPatch tape on your system,
you need to restore the STORE files that are appended to the CSLT
created during the installation of the most recent PowerPatch tape.
Refer to "Restore FOS and SUBSYS" for directions
on restoring the STORE portion of the CSLT.
If you applied other patches to your system (such as reactive
patches), you need to reapply them at the end of the process.
If you are not sure what patches have been applied to your
system, be sure to call the Response Center or HP Representative
before backdating your system.
Method 2: Using a Factory SLT
If any patches were applied to your 6.0 or 5.5 system, they
must be reapplied from the PowerPatch tape(s) after the backdate.
Follow the appropriate manual for the release you are backdating to.
To determine the patches that were applied to your system, restore the
HPSWINFO file from a backup of the release you are backdating to.
Method 3: Using an FPT
If any patches were applied to your 6.0 or 5.5 system, they
must be reapplied from the PowerPatch tape(s) after the backdate.
Follow the appropriate manual for the release you are backdating to.
Check Patch Tape Media
To verify the patch tape source media and contents:
Log on from the console with the following conditions.
:HELLO MANAGER.SYS,INSTALL;HIPRI
:OPENQ LP
:STREAMS streams_device
An LP device must be configured in SYSGEN. A common
streams_device value is 10.
Already spooled and streamed messages might display.
Collect the tape media you will be using as source material to
modify the system software. This includes the PowerPatch and Reactive
Patch tapes.
If you have a PowerPatch tape, check it to ensure the tape is not
damaged.
If you do not have a PowerPatch tape, proceed to Step 4.
Mount PowerPatch tape.
:FILE TAPE;DEV=TAPE
:VSTORE *TAPE;@.INSTALL.SYS;SHOW
Reply to the tape request.
vstore displays a listing of verified files. These files
are not being restored to disk.
If you have a Reactive patch tape, check it to ensure that it is
not damaged.
If you do not have a Reactive patch tape, proceed to Step 5.
Mount Reactive tape.
:FILE TAPE;DEV=TAPE
:VSTORE *TAPE;@.@.@;SHOW
Reply to the tape request.
vstore displays a listing of verified files. These files
are not being restored to disk.
If any files are not verified or if you receive any errors or
warnings, ensure your tape drive is clean and repeat the procedure to
be sure it is a media problem and not a dirty tape drive.
Run the cleaning cartridge through your DDS drive at least three
times to ensure that the drive is thoroughly cleaned.
If your media is bad, contact your local HP Support
Representative.
Validate Your System Backup (Method 1)
If you are using a CSLT (Method 1) to backdate your system,
perform the steps in this section.
If you are using a Factory SLT (Method 2) or a Factory Preload
Tape (Method 3), proceed to "Check for Disk Space."
Before you begin the process of backdating, log on and verify
that your backup tape is valid.
From the console, log on with the following conditions.
:HELLO MANAGER.SYS,INSTALL;HIPRI
:SPOOLER LP;OPENQ
:STREAMS streams_device
where streams_device is the device number. A common
streams_device value is 10.
An LP device must be configured in SYSGEN. Already spooled
and streamed messages might display.
Validate the backup created before you started the update process
that you are now backdating from. You need the valid backup to
restore the NMCONFIG file.
Use the VSTORE command to make sure that the full backup is
readable.
:FILE TAPE;DEV=tape_device
:VSTORE *TAPE;@.@.@;SHOW=OFFLINE;DIRECTORY
If your backup is not valid, you must use Method 2 or
Method 3.
Check for Disk Space
Ensure you have sufficient disk space to backdate your system.
Refer to "Estimating Disk Space" in Chapter 3 "Planning for
Your Task" and Appendix C "Managing Disk Space"
for additional information about these steps.
Reserve contiguous and non-contiguous disk space.
:BUILD AXLDEV1;DISC=n,1,1;DEV=1
:BUILD AXLSPACE;DISC=m,32,32
where:
- n
AXLDEV1 number, determined in
Chapter 3 "Planning for Your Task" or
use the default of 120,000 sectors.
- m
AXLSPACE number, use the maximum value 1,084,000
(for 6.0 or 5.5 versions)
If a colon (:) prompt is returned. The files were built and you have
enough disk space.
If you receive a message: Out of disk space, you need to
make more space.
Purge the AXLSPACE file. The AXLDEV1 file is
automatically purged by the UPDATE tool.
:PURGE AXLSPACE
If you do not have enough disk space, either contiguous
(AXLDEV) or non-contiguous (AXLSPACE):
Store files to tape. Purge the stored files from the
system.
Purge the files and groups as directed in Steps 8 through 10
of the next section, "Securing Your System."
Refer to Appendix C "Managing Disk
Space" for directions on clearing space.
|