You did not say what type of system the client is. This was easy on our unix boxes. The dsm.sys file is made to be in stanza format and thus we use two different client nodes. One for the system and one for Oracle. Since these are treated as two separate nodes to TSM, they do not get in each others way. They both have their own dsm.opt file which calls out different stanzas in the dsm.sys file and different includes/excludes. The system one excludes the oracle databases. The oracle one uses domain statements and includes to get just the database files. Pre and post commands are used to shutdown the database and start it back. We run these from cron of unix.
With proper scripting and environmental variables one should be able to do this with windows also. Some of the latest versions of TSM for NT and W2K allow for more than one scheduler to run and depict different dsm.opt files. This is how we handle it. -- Phillip Ford Senior Software Specialist Corporate Computer Center Schering-Plough Corp. (901) 320-4462 (901) 320-4856 FAX [EMAIL PROTECTED] -----Original Message----- From: Tony Sinclair [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 1: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. *************************************************************** This message and any attachments is solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use, or distribution of the information included in this message is prohibited -- please immediately and permanently delete this message.
