ADSM-L

Re: Need help - TDP for Oracle on Solaris - Scheduler question

2002-04-08 11:50:09
Subject: Re: Need help - TDP for Oracle on Solaris - Scheduler question
From: Neil Rasmussen <rasmussn AT US.IBM DOT COM>
Date: Mon, 8 Apr 2002 08:49:44 -0700
Here are some tidbits to scheduling Rman backups:

First off, the method I am going to discuss can be found at:  
http://www.tivoli.com/asktivoli (registration is required, this is free)


When using the TSM scheduler to automate the TDP Oracle backups, the
differences in how these two clients work must be taken into account:
o  The scheduler runs as root and needs "passwordaccess generate".
o  The TDP Oracle backup runs as an Oracle user and needs "passwordaccess
prompt".

On the TSM server there would normally be two schedules setup for the
machine where Oracle is located:
   1) an incremental file system backup
   2) a command schedule for the TDP backups.  One way to set this up is
to associate both schedules on the TSM server to the node that is
performing the file system backup.  This may initially be confusing as it
would be anticipated that the nodename for the TDP backup should be used
for the command schedule that is going to run the TDP Oracle backup.
However, since the TDP client requires "passwordaccess prompt", it is not
possible to automate the schedule process on the client machine (without
encountering various issues).  If the regular "backup/archive" client node
is associated with the command schedule, this usually has "passwordaccess
generate" already set and is running as root on the client machine.
Additionally, if using the "Backup/Archive" nodename, then only one
scheduler daemon is needed on the client machine.  For the TDP backup, the
script file for the command schedule backup will be launched by the
scheduler daemon.  In this script, it will be necessary to switch user
"su" to the Oracle user that is going to perform the backup.  It is
mandatory that the environment for the Oracle user be in existence, so the
"su" will need to be done such that the ".profile" is sourced (the oracle
variables "esp." the "ORACLE_SID" and "ORACLE_HOME" need to be available
for the "TDP/RMAN" backup).  Then within the command script, launch the
"RMAN" backup script.

Having said this, it may be less confusing to run your backup as a cron
job (this is my opinion).


Regards,

Neil Rasmussen
Software Development
TDP for Oracle
<Prev in Thread] Current Thread [Next in Thread>