The subject is meant to the be the poorly remembered latin for what
translates into "who will guard the guardians?"

Or: what are people doing for backing up the DASD that they have as their
primary storage pools?

We use VM:Center/E for our environment.  VMBackup backs up the DASD storage
pools and database extents, of course, but there are some tricky issues,
like, if the storage pool is being added to while the backup occurs, or the
database is being updated, what state would the data be in should it be
restored from this point?

Should we code the exit to suspend processing of the data while the backup
is running?  Should we shut the whole process down or vary the storage
pools offline?  What about the database?

Or: should we use EXPORT SERVER?  Is there any way to incrementally export
information so that it needn't add additional gigabytes to the nightly
backup stream?  Are their disaster-recovery issues?  What if one particular
DASD is hit by an error -- do we need to restore the system back to where
it was, or is there a way to rebuild utilizing more current data on another
device that was not affected?

Finally, if we bring down ADSM for backups, what happens to clients that
are using scheduling... can we refuse sessions such that the clients will
"try again" in a reasonable time to connect?

Has anyone gotten into these issues?  How about in WDSF?

Thanks!  _KMP