ADSM-L

Re-Binding to a New Mgmt Class

2006-10-06 12:17:24
Subject: Re-Binding to a New Mgmt Class
From: Shawn Malone <shawnm1964 AT YAHOO DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 6 Oct 2006 09:16:21 -0700
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

<Prev in Thread] Current Thread [Next in Thread>