Yes Bill, Your point is correct if the pre/post commands are coded in dsm.sys. However is possible to specify them on the command line and hence through the -opt parameter of a schedule, in which case they only apply to that schedule.
Steve. >>> [EMAIL PROTECTED] 26/06/2002 22:53:03 >>> Just a little comment on #2...the pre/postschedule commands run every time you run a schedule against that node! So if you were to maybe run a CLIENTACTION against the node to do a special backup of a file/directory, not necessarily the whole server, you're shutting down your database. If that's in the middle of the day, the users ain't gonna be to happy with ya. For Orcale COLD backups, we have a shell script that shuts down the Oracle instance, does other maintenance tasks then calls DSMC I to do an incremental backup, Checks the return code and alerts on != 0 and then restarts Oracle instance. We have found this works better than the pre/post commands. We can do a better job of return code checking of Oracle tasks before running the backup. Now with the new and improved! return code checking in V5.1 maybe we could make it work, but you gotta remember that this command will be run every time you run a schedule against the node!! Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Harris Sent: Tuesday, June 25, 2002 9:02 PM To: [EMAIL PROTECTED] Subject: Re: Backing Up Oracle DB with TSM 4.2.1 There are several ways. 1. Configure RMAN to do backups to a disk directory. Exclude the oracle database directories from backup. run your normal node incremental after the RMAN job has finished. RMAN disk backups have unique names, so you will need an include on the backup directory and a dedicated management class for Oracle backup data. 2. Shutdown the database with a preschedule command, backup the node, then start it up with a postschedule command. 3. exclude the database directories from backup. set up a script to set the oracle tablespaces to hot backup mode (alter tablespace begin backup) one at a time, then run an *archive* on each, then take them out of hot backup mode. Note that this way you back up lots of gas,as you back up blank pages too. The RMAN solution only backs up used pages. HTH Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia >>> [EMAIL PROTECTED] 26/06/2002 2:50:16 >>> I have a client that is running a small (~10GB) Oracle (9.0) DB on Win2K. I have never backed up an Oracle DB before, especially on Win2K. (TSM Server is AIX). If someone could point me to a step-by-step explanation of how to do this, I would greatly appreciate it. Thank you. Tony ********************************************************************** This e-mail, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this e-mail is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. ********************************************************************** ********************************************************************** This e-mail, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this e-mail is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. **********************************************************************
