To All who have SQL Backtrack backups on ADSM.

My Shop is currently:

ADSM V 2.12   AIX/UNIX( soon to be V3)
2 Unix Nodes running SQL backing up approx. 20 GB in Oracle DB data.
1 NT Node running SQL backing up 2 GB in Oracle DB data.

I need some input from shops that are currently running SQL backups thru
ADSM.

My question is how are other shops doing these backups?

We are currently in the discussion process of determining who will be
responsible for backing up this data, either the ADSM administrator or
the DBA's.  As it stands now ADSM administration executes a SQL
Backtrack script via ADSM Cmd schedule to backup the database. How are
folks out there trapping SQL Backtrack failures when SQL Backtrack is
launched from the ADSM scheduler.

The DBA's are issuing the same SQL Backtrack scripts via crontab.  There
reason the DBA's wish to use cron is because ADSM is unable to pass back
any return code to SQL if there is a problem with the backup.

Or the plan is to use Platinum's Autosys to issue the scheduled backups
to SQL, since it is Autosys has restart capability.

The second policy issue we are deciding upon, is on demand activity.
Should DBA have the authority to do a recovery/backup anytime they feel?
We have limited resources, and ADSM administration  is under the
impression that backups/recoveries should be coordinated through ADSM
administration, rather than at the whim of DBA.


Tony Sinclair
Adsm System Admin.
Snohomish County Public Utility District
Everett WA
tjsinclair AT snopud DOT com