Neil-- you're right, I (the TSM admin) wanted it done thru the scheduler,
so I would have the central point of management. However, the deal breaker
was the complexity of setting up the schedulers, so the DBAs assumed
responsibility of monitoring those backups and ran them thru Oracle's CRON.
In hindsight, maybe it worked out for the best after all;-)
lisa
|---------+---------------------------->
| | Neil Rasmussen |
| | <[EMAIL PROTECTED]|
| | COM> |
| | Sent by: "ADSM: |
| | Dist Stor |
| | Manager" <ADSM- |
| | [EMAIL PROTECTED]> |
| | |
| | |
| | 07/31/2002 09:06 |
| | AM |
| | Please respond to|
| | "ADSM: Dist Stor |
| | Manager" |
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: RMAN error
|
>--------------------------------------------------------------------------------------------------------------|
Lisa,
Really, for the most part I do not use the scheduler except where testing
in a development environment is concerned. So with regards to specific
scenarios I believe that, you, the customer are the experts on each of
your specific systems. What I do know is that using CRON for Rman backups
is the easiest to set up. However, what CRON does not offer is a central
point of managing schedules. In most cases I have seen a clear line of
responsibility between the Oracle DBA and the TSM DBA. This means that
usually when it comes to scheduling backups to the TSM Server the TSM DBA
will determine how the backups will be managed and therefor chooses the
TSM scheduler.
Regards,
Neil Rasmussen
Software Development
TDP for Oracle
[EMAIL PROTECTED]
