The dsmsched.log file should show "rebinding", IF the file still existed on the client at the time of the backup. Files that are still on the client should be rebound. Files that are inactive (i.e, no longer exist on the client) cannot be rebound. Make sure the restart the scheduler after making the changes to the dsm.opt file.
________________________________ From: ADSM: Dist Stor Manager on behalf of Shawn Malone Sent: Sat 10/7/2006 8:05 PM To: [email protected] Subject: Re: Re-Binding to a New Mgmt Class Hi Wanda, It does not seem to have worked, because after expiration ran today, all 45 copies were still on the TSM Server. Will the files that are on the TSM server already, be re-bound to the new mgmt class or will they have to run there course under the mgmt class they were backed up under? I am in the process of obtaining the log file and dsm.opt file from the Windows team, as we do not have access to the those servers. Shouldn't the log show the binding to the new mgmt class? I really appreciate your help. Shawn "Prather, Wanda" <[EMAIL PROTECTED]> wrote: The correct syntax is: include j:\...\* SQL "*.*" is incorrect, but may work much of the time. The * is a wildcard that matches any number of characters, but the . requires an exact match. So *.* will ONLY match files that have at least one . in the name. The ... is a wildcard to match any number of directories. When you specify j:\* , it only matches files in the root of J: The easiest way to check the management class is to start the client and click RESTORE. Browse your way to the files you have backed up on J:. Scroll to the far right, and you can see what management class the file is bound to. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Malone Sent: Friday, October 06, 2006 12:16 PM To: [email protected] Subject: Re-Binding to a New Mgmt Class We are curently running TSM 5.3,2.3 on a RS6000 running AIX. We have a Windows 2003 Server which has 5 filesystems that currently backup to our standard backup policy which states to delete files in 45 days. The problem is that we only need to keep 8 copies of 1 of these filesystems. We have created a new management class named SQL on the TSM server and found from TSM documentation that we needed to have the windows team enter the following into their dsm.opt file. include j:\*.* SQL We have also tried; include "j:\*.*" SQL <--- With Quotes & include j:\* SQL <----- Just 1 * J is the drive on the windows server that we need to only keep 8 copies of. We then had the team stop and restart the TSM Scheduler Service and then run a backup of this drive. After the backup completed, we ran expire and the additional 38 copies were not removed. We reviewed the dsmsched.log and did not see where this drive did a re-binding to the new mgmt class. My question is, did we put the option in the dsm.opt file correctly. When I do a q fi for this node, the filespace reads: \\bjcnxcls01\j$ So does the include statement need to look like the following: include \\bjcnxcls01\j$ SQL Any help would be appreciated. Shawn
