A few things, some have been mentioned already:
1.) You mentioned hardware, so I assume this reload is due to a hardware
problem, which probably means you need to do an INSTALL/RELOAD. That changes
UPDATE CONFIG to INSTALL. If that's the case, then before the restore, you
need to add the volumes back into the sysvolset using volutil (unless they
are avol'd in sysgen);
2.) the ;DIRECTORY option is important. If not using it, then use something
like BULDACCT;
3.) ;KEEP is a standard option for a RELOAD, though it's not terribly
important if the backup is at the same time;
4.) another good one is ;PARTIALDB
5.) If you use parallel STORE/RESTORE, first restore just the directory
(RESTORE *T;;DIRECTORY);

I have a good set of INSTALL guidelines if you want.


-----Original Message-----
From: Steve Hammond <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: Wednesday, December 22, 1999 09:45
Subject: Reload


I suspect I am going to have to do my second reload in just over two months
(stay tuned on comments I will have about a hardware VAR later!).

Luckily, this one will not be as 'urgent' so I will be able to get a full
backup just prior to the reload.

Anyway, I learned some lessons from the last reload but I need a sanity
check on my reload strategy, so here it is, punch holes in it for me.

- make an SLT now!!
- do the full backup
- check the full backup listing for files missed
- deal with the missed files
- system goes down
- drive replaced
- system up, using SLT, UPDATE CONFIG option
- restore @.PUB.SYS;directory; olddate
- restore @[log in to unmask]@[log in to unmask];olddate;progress=10
- wait six hours
- reboot system
- up and running

Where have I had brainlock and forgotten something

thx
steve hammond
[log in to unmask]