ADSM-L

[ADSM-L] DB2/Oracle backup reporting and scheduling

2015-03-06 12:13:17
Subject: [ADSM-L] DB2/Oracle backup reporting and scheduling
From: Rick Adamson <RickAdamson AT BILOHOLDINGS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 6 Mar 2015 17:12:03 +0000
I assume someone has dealt with this I would like to hear how they handled it.

The issue:
DB2 and/or Oracle database backups that are dependent on completion of external 
processes.

Currently our DBA's utilize a variety of methods to initiate DB2 and Oracle 
database backups (CRON, external schedulers, etc) which presents challenges to 
confirm that they are being completed as expected. As a start, I proposed 
creating a client schedule and using the TSM scheduler to trigger these events, 
which would minimally provide a completed/missed/failed status. Complemented by 
routine reporting of stored objects it would give me some assurance that TSM 
had what it needed to assure their recovery.

The DBA's are pushing back (surprise!) claiming that "some" backups have 
special requirements, such as not running during other tasks like payroll 
processing, runstats, etc. so they use the external scheduler to set 
"conditions" that are met before the backup is initiated.

The question proposed to me is can a TSM schedule be triggered by the external 
scheduler once the conditions have been met?

I would be grateful to hear how others handle this, or if they use a different 
approach altogether to assure all DP database backups are completing on a 
timely basis.
TIA

~Rick