One could do a full system install on the new machine from the original FOS,
PROD/SUBSYS, Patches, etc. But assuming the new machine will have the same
software configuration, it is a heck of a lot easier to use an SLT and
change the hardware config.
You can create an SLT using the "TAPE" command. You can also direct SYSGEN
to a different configuration group.
You can use the NEWGROUP parameters on either the original activation of
SYSGEN or the keep command to keep to a different group. But I find it a
little safer to copy to a new group first and then direct SYSGEN totally
there (BASEGROUP). Less chance of forgetting a group name on the keep and
screwing up your real system configuration.
My usual process would be:
On Old HP3000:
1. Create group CFGNEW.SYS.
2. :MPEX COPY @.CONFIG.SYS,=.CFGNEW.SYS
3. :SYSGEN CFGNEW
4. Modify configuration to that of new HP3000.
5. io> HO
6. sysgen> KE
(you now have the new HP3000 config in CFGNEW without changing your real
config in CONFIG)
7. sysgen> TAPE
(This stores the new HP3000 configuration plus all critical system files to
tape)
(Many people add extra store files to the TAPE command as in:
sysgen> TAPE STORE=<fileset>
See thread "Files that cannot be backed up" April 19/20, 2002)
On new HP3000: (commands differ slightly with different HP3000 models):
1. BO ALT
2. INSTALL
3. START NORECOVERY
4. Logon to MANAGER.SYS and use DTSTAT ALL, VOLUTIL, etc. to initialize disc
volumes.
5. From a full backup;
:RESTORE *T;@[log in to unmask]@.CONFIG.SYS-NMCONFIG.PUB.SYS;SHOW;DIRECTORY;CREATE
6. Use NMMGR to make any network modifications as needed.
7. :RESTORE *T;@[log in to unmask]@[log in to unmask]@.SYS;SHOW,DIRECTORY;CREATE;KEEP
8. Use an appropriate method to finish rebuilding account structures, UDC's,
etc. There has been discussion on the various methods here in the past. I
think the "Files that cannot be backed up" thread also went into it a bit.
9. Reboot BO PRI
10. Check all third party software. You will often have some which uses the
HP SUSAN number for licensing. You will need to call for a license
modification, etc.
11. Check a bunch of other things. This depends on your system. Printers,
DTCs, ports, modems, other peripherals, yada-yada-yada.
That is pretty much our procedure for a reload to a new machine or new
system volume set. You mileage may vary. Some details have been left out to
keep this shorter. Our actual check lists are generally 6 to 10 pages long.
Timothy Atwood
Holtenwood Computing
http://www.holtenwood.bc.ca/computing/
for Domtar Vancouver Mill
(Opinions expressed are mine and do not reflect Domtar)
-----Original Message-----
From: Andrew Cartledge [mailto:[log in to unmask]]
Sent: Friday, May 10, 2002 1:45 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] System replacement planning
Slightly sideways to original question.
I noted back references to previous maintenance of file stored to the SLT
but I am still unclear.
What function does the SLT perform. What is on it and, in the context of
disaster recovery, what if any affect does cutting an SLT on one machine
have on another in the context of hardware and software config on the
new/backup box (which may not be identical).
My experience of SLT's come from installing from scratch, and so having to
further configure the hardware, and recovering from disc failures. I know
that as if by magic my account structures reappear but given the fact that
the priority is to get the system back up I've never before thought 'how
did that happen'.
Any articles available that explain?
TIA
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
