On the one system where I do have an ATL and therefore RMSMASTR, I have a lso kept real data out of the VMS* filepools. They are quite small so it is e asy and quick to force RMSMASTR, do the FILEPOOL UNLOAD to CMS disk files an d bring RMSMASTR back up in order to mount the tapes for the largest SFS an d the full volume backups. Or even mount your backup tape, bring down RMSMASTR, backup the VMS* filepools to that tape, then bring RMSMASTR bac k up.
But the key is that NOTHING else is in the VMS* filepools. This would be so much easier if RMSMASTR's configuration files and logs were allowed to be on real CMS minidisks. /Tom Kern /301-903-2211 On Fri, 28 Mar 2008 11:31:58 -0500, Marcy Cortes <[EMAIL PROTECTED]> wrote: >I opened a SHARE requirement about this. > >DFSMS RMS requires stuff in SFS. >To get a valid backup you must either have some software that >understands the SFS or have the SFS down. But you can' t have the SFS >down or you can't mount a tape if they are in an ATL. >But you'd like to have RMS available as soon as you restore your full >pack so that you can use that special SW you purchased to restore your >SFS! >So, you really have to do a fileserve generate and then copy in enough >of your DFSMS configs that hopefully you've kept elsewhere on minidisk >in order to get your ATL to work. > >In reality, what we do is *hope* that the physcial backup while it is up >is ok. We keep nothing but dfsms in there (in the VMS* filepools) in >hopes that since it is static, no issues will arise. > > > >Marcy Cortes >
