Oops, sorry left off that pesky directory option. <rant on> I wish that the directory was part of the SLT and came in on the Install. <rant off> Thanks Mike Hornsby Beechglen Development Inc. Enterprise Solutions & Support www.beechglen.com 513-922-0509 ----- Original Message ----- From: Steve Cole <[log in to unmask]> To: <[log in to unmask]> Sent: Wednesday, October 27, 1999 2:29 PM Subject: Re: was Reload sanity check/ now Reload security check > I agree with the concept of breaking up the restores into multiple parts. > The only modification I would make is that on the backup you store all the > system directories. Then when you do the restore you would restore the > directory: > > restore @[log in to unmask];SHOW;OLDDATE;KEEP;DIRECTORY > > The restore of the system directories recovers the system accounting > structure and the account, group and user capabilities, passwords and access > rights. The CREATE option will rebuild the accounting structure but will > not recover capabilities or passwords. All created accounts, groups and > users are created with default capabilities. > > If after all files have been restored, if there are files that don't > restore because the creator doesn't exist then another way of addressing > this issue is to perform an additional restore: > > restore @[log in to unmask]@;SHOW;OLDDATE;KEEP;CREATOR=manager > > This would restore only those files that originally did not come back due to > the creator problem and would alter the files creator to "manager" or to any > user you specify. > > > ================================= > Steve Cole > Outer Banks Solutions, Inc. > [log in to unmask] > www.outerbankssolutions.com > Phone: 919.231.2171 Fax: 919.231.7077 > Sales: 800.558.5336 > ================================= > ----- Original Message ----- > From: Mike Hornsby <[log in to unmask]> > To: <[log in to unmask]> > Sent: Wednesday, October 27, 1999 10:02 AM > Subject: was Reload sanity check/ now Reload security check > > > > On a larger system, or if the system has a lot of non critical path files, > > (spoolfiles ,test accounts, source code) I would recommend to split the > > restore into three parts. > > > > 1. restore @[log in to unmask];SHOW;OLDDATE;KEEP;CREATE (this gives access to all the > > utilities) > > 2. REBOOT and start the network (I like to see if the reboot will work > ASAP) > > 3. restore @[log in to unmask] ACCOUNTS;SHOW;OLDDATE;KEEP;CREATE > > 4. checkout production applications > > 5. restore @[log in to unmask]@;SHOW;OLDDATE;KEEP;CREATE > > > > This method while slightly more complex has three benefits: > > a. you get to the reboot step sooner. While this doesn't save time it can > be > > disheartening to find out after 6 hours that you don't have the correct > > configuration. > > b. you get to the testing and production sooner. > > c. the busier files are reloaded together and this creates better locality > > on the discs. > > > > ONE OTHER THING, > > AFTER EACH RESTORE IN THE SYS ACCOUNT WITH THE CREATE OPTION, IT IS VERY > > IMPORTANT TO CHECK FOR USERS THAT DON'T HAVE PASSWORDS! Users in the SYS > > account can become group users for PUB and other groups in the SYS > account. > > > > This has long been a bug in MPE RESTORE. <rant on> Why the creator of a > file > > must exist to restore the file when it didn't exist when the file was > stored > > is beyond me. <pun on> But it does CREATE havoc at restore time!<pun off> > > <rant off> > > > > Mike Hornsby > > Beechglen Development Inc. > > Enterprise Solutions & Support > > www.beechglen.com > > 513-922-0509