Hi Karen,
         You could also take a backup of volume history , Devconfig ,
export of all information like admin ,server ,policy
and backup the /usr/lpp/adsm and /usr/lpp/adsmserv directories. You
could also take system backup periodically
preferably keep a printout of all the information related to the ADSM
configuration.

         Db backups never cease unless you delete the volume history
files. Be especially careful while using the volume history files
because you may accidentally render all your DB backup's useless.



> -----Original Message-----
> From: Karen Krowzack [SMTP:Karen.M.Krowzack AT UCM DOT COM]
> Sent: Monday, August 17, 1998 3:59 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Database backup procedures
>
> As a soon-to-be in production ADSM site, I have had a concern
> expressed to
> me about the backup of the ADSM database.  Since the ADSM database is
> so
> critical to the proper functioning of ADSM, what are the best steps
> taken to
> ensure that it can be restored in case of a problem? To date, we are
> doing
> the following:
>
> 1)  Mirroring the db and recovery log
> 2)  Backup the db to a file on disk on the ADSM server every day.
>
> Eventually, we also plan to copy the db file to a tape or onto another
> ADSM
> server.  At what age does that db backup become useless (24 hours, 1
> day, 3
> days???)
>
> Any other ideas on how to take the best care of the database and
> recovery
> log?  If the database is truly lost, can the tapes in the ADSM library
> be
> re-read to re-build the database?
>
> Thank you for your ideas and comments.
>
> Karen Krowzack
> IBM Global Services
> Tieline 461, x7309
> Outside phone - 312-394-7309
> Pager:  800-759-8888, PIN 1967096
> email:  Karen.M.Krowzack AT ucm DOT com