I asked this question of BMC at least 6-12 months ago and officially got the answer of "this is unsupported ". We are getting around it by creating a separate profile in a different location and move it back and forth between the temporary area, and the real area before starting the backup. Seemed like a reasonable request to have 2 different mgmtclasses for backups, and archives, but they said no.
Steve Argersinger Ruan Transportation -----Original Message----- From: Rolf Meyer [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 05, 2002 12:25 AM To: [EMAIL PROTECTED] Subject: Re: how does TSM / sql backtrack use management classes? Hello, using SQL BackTrack, all retention management is done by SQL-BT acording to definitions in the so called Oracatalog. Every backup object is unique, because the name includes a timestamp. Versioning from TSM sight cannot be established. In the inst. guide of SQLBT-interface mode to TSM, called obsi.adsm, you find the nessessary defs for the backup or archive copy groups. Greetings Rolf Meyer On Monday, 4. March 2002 22:20, you wrote: > We're using SQL backtrack to backup our oracle database. If two backtrack > backup scripts are run using two different management classes against the > same database, (ie.. management class one has 3 version, 30 days and > management class two has 6 versions 60 days) how does TSM handle the > backup? Will it in effect use the shortest management class. Or will it > keep two sets of the database, one for 3/30 and the other for 6/60?
