Backing Up Oracle - Computing at Cornell

To use this command file with the script named backup_offline_beach, we just
add the name of the script when calling the AUTORMAN.CMD file.
autorman backup_offline_beach
Windows will then replace each occurrence of %1 in the AUTORMAN.CMD
file with backup_offline_beach. Here is an example of this:
C:\oracle\admin\scripts>autorman backup_offline_beach
C:\oracle\admin\scripts>set ORACLE_SID=BEACH
C:\oracle\admin\scripts>rman target internal/manager@beach
rcvcat rman/rman@rio cmdfile=c:\oracle\admin\scripts\backup_offline_beach
log=c:\oracle\admin\scripts\backup_offline_beach.log
Using this AUTORMAN.CMD file, we can now easily schedule RMAN scripts
using TSM scheduling without creating a separate command file for each
backup.
11.2.1 Scheduling TDP for Oracle backups
In order to use the TSM scheduling services, you must perform configuration
on both the TSM server and the TSM client.
11.2.1.1 TSM server steps for scheduling
On the TSM server you need to perform two commands:
1. DEFINE SCHEDULE
With this command, you must specify the domain where the TDP for Oracle
backup node belongs, ACTION=COMMAND, and OBJECT=. The other options regarding time and frequency can be tailored
to your environment. See the TSM server product documentation for details,
or type HELP DEFINE SCHEDULE at the TSM administrative prompt.
Note
Do NOT define the schedule with ACTION=INCREMENTAL. This would
cause a full incremental backup of the entire machine using the
backup-archive client, but would do it using the TDP for Oracle nodename.
This will show how to schedule the c:\oracle\admin\scripts\autorman.cmd
command that we discussed in the preceding section.
172 Backing Up Oracle using Tivoli Storage Management