We once successfully did a VM:Backup restore of the ADSM database. It was
taken on a running system, so it was a bit corrupted. (This was back on
V1, pre BACKUP DB.) It was not pretty at all. AUDITDB fixed things up,
but it took several CPU-days, with all of nervously watching it and
trying to do avoid anything which would risk a system crash.

I agree completely that now we have tools to avoid this kind of calamity.
One of the lab exercises in the ADSM Advanced Topics course I recently
took was to - get this - erase the database from under a running ADSM.
Full and complete recovery up to the moment of this staged disaster,
using the volume history file, the database backup, and the recovery log,
worked flawlessly. It takes a little planning to set this up, but it is
well worth it.

B.T.W. I keep a month's worth of database backups, just in case of
calamity.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu
Aliases:                  u52983 AT uicvm.uic DOT edu        R.Deschner AT uic 
DOT edu
======I have not lost my mind -- it is backed up on tape somewhere.=====