The way this is done with agents is by creating a second scheduler service/daemon using a separate dsm.opt file. Since you then have two clients as far as TSM is concerned you can have two schedules: one for normal files excluding the db files and one just for the database. The schedule for the db backup is probably a command that runs the backup2.cmd file. In the options file for client one you exclude the oracle files. In the options file for client two you exclude the system files. It might be easier in that case to exclude everything and only include the directories where the database files exist.
This is the simplest way to accomplish what you're after, but will consume another client license in the process. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Tony Sinclair Sent: Wednesday, December 19, 2001 12:05 PM To: [EMAIL PROTECTED] Subject: Re: Help with scheduling I would like some input from the group on how I could accomplish the following with the least amount of user intervention/maintenance. The following is my dilemma: There are two sets of backups on the client server. One is the system backup and the other is the database backup (not yet implemented). The system backup needs to exclude the Oracle database data files. Since this backup is done when the database is open, there is no point in backing up these files because they're useless in a restore/recovery situation. The attached file is a list of files that need to be excluded from the system backup. The database backup needs to be run on Sunday's, starting around 11:00 am. It needs to exclude the files backed up in the system backup. This backup needs to be done when the database is in a shutdown state. The file in /oradata/jobs/bkup/scripts/tsm/backup2.cmd(which is executed via the OPTION section on the schedule) is set up to include all the appropriate files. Now since the TSM client uses the same DSM.SYS file how can I resolve this dilemma? How can I keep the DSMSCHED.LOG's seperate? Or how would you handle this situation? Tony Sinclair TSM ADMIN/STOR. Manager [EMAIL PROTECTED] =========================================================================== IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.
