We used to be very concerned with SPOOL file recovery in moving from one configuration to another, but that was when we had real users. Now we don 't have users who need their old spool file, just servers that are creating new console log spool files. I resurrected an old idea about saving DCSSes on a minidisk rather than on a tape that needs to be carried to each system fo r recovery. I have a server that will resave all of the changed DCSSes lat e at night. I haven't yet built the automatic restore to spool area, but it
only takes me a minute or two in the middle of our Disaster Recovery to d o it manually. The minidisk is allocated on the sysres volume. The CMS Util ity Feature programs DCSSBKUP and DCSSRSAV work nicely for DCSSes, but not fo r NSSes. I stole the basic idea of CMS and GCS regeneration from the installation script and have a BLDCMS and BLDGCS server can resave these NSSes. /Tom Kern On Thu, 25 Jan 2007 10:37:27 -0600, Mary Anne Link <[EMAIL PROTECTED] M> wrote: >Uh oh. Why do I feel like a little mouse and Alan is the cat toying with me. > :) > >Well, I guess I will copy spool as well. I can't think of a reason I wou ld >want to reuse SPL if I have replaced the res, so essentially I guess the y go >together. We only use SFS files for console logs so I can re-init those. >What else would there be? > >MA > >======================== ========================= =======================
