Andy,
I got a note that said that all is now as the users want. thanks for the help.
From: ADSM: Dist Stor Manager on behalf of Andrew Raibeck
Sent: Mon 12/3/2007 3:15 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE for new management class
Hi
: [ADSM-L] INCLUDE for new management class
Hi Fred,
FORCE has no effect on INCLEXCL, so that's a nonstarter.
Try this: remove the INCLUDE statement from the dsm.opt file and instead
add it to the client option set on the server. But instead of using the
drive letter, use the UNC name, e.g
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE for new management class
Hi Fred,
FORCE has no effect on INCLEXCL, so that's a nonstarter.
Try this: remove the INCLUDE statement from the dsm.opt file and instead
add it to the client option set on the server. But instead of using the
drive
Administrator
University of Chicago
773-702-8464
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Raibeck
Sent: Monday, December 03, 2007 12:34 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE for new management class
A couple
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE for new management class
A couple of things:
1. Is the actual machine name tank1.ad.uchicago.edu? In other words,
if
from that machine you run SET COMPUTERNAME from an OS prompt, is that
what
it shows? Or does it just show tank1? Make
-8464
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Raibeck
Sent: Monday, December 03, 2007 12:45 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE for new management class
OK, so my comments re: your INCLUDE file spec stand
] On Behalf Of
Andrew Raibeck
Sent: Monday, December 03, 2007 12:45 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE for new management class
OK, so my comments re: your INCLUDE file spec stand. Once that is fixed
up
to match the actual file space name, it should work.
Regards,
Andy
Andy Raibeck
Our desktop support unit has a user that wants a new retention policy on
their file share. The admin added this to the dsm.opt:
INCLUDE F:\NSIT\FieldSupport\University Administration\Budget Office\*
LONGADMIN
INCLUDE F:\NSIT\FieldSupport\University Administration\Budget
Office\*.* LONGADMIN
I
On Nov 29, 2007, at 3:23 PM, Fred Johanson wrote:
Our desktop support unit has a user that wants a new retention
policy on
their file share. The admin added this to the dsm.opt:
INCLUDE F:\NSIT\FieldSupport\University Administration\Budget
Office\*
LONGADMIN
INCLUDE
:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: Thursday, November 29, 2007 2:35 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE for new management class
On Nov 29, 2007, at 3:23 PM, Fred Johanson wrote:
Our desktop support unit has a user that wants a new retention
policy
Nothing wrong per se, although the second INCLUDE appears redundant.
The first place to start with these kinds of issues is to use dsmc query
inclexcl to makes sure those files aren't being picked up by an earlier
filter.
Also make sure the updated policy was activated.
Regards,
Andy
Andy
Of
Andrew Raibeck
Sent: Thursday, November 29, 2007 2:29 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE for new management class
Nothing wrong per se, although the second INCLUDE appears redundant.
The first place to start with these kinds of issues is to use dsmc
query
inclexcl to makes
Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Raibeck
Sent: Thursday, November 29, 2007 4:48 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE for new management class
Yes, but it's not position in the dsm.opt file that matters when client
option
Subject: Re: [ADSM-L] INCLUDE for new management class
Yes, but it's not position in the dsm.opt file that matters when client
option sets are at issue. Use dsmc query inclexcl to see the final
list
that TSM actually uses.
I suspect it is that client option set that is overriding the dsm.opt
file
: Re: [ADSM-L] INCLUDE for new management class
Nothing wrong per se, although the second INCLUDE appears redundant.
The first place to start with these kinds of issues is to use dsmc
query
inclexcl to makes sure those files aren't being picked up by an earlier
filter.
Also make sure
down, I see this above the INCLUDE for the new
management class:
Include All *\...\*Server
So that's why the new INCLUDE is ineffective. There are a lot of other
excluded files below that are probably getting backed up.
Regards,
Andy
Andy Raibeck
IBM Software Group
?
From: ADSM: Dist Stor Manager on behalf of Andrew Raibeck
Sent: Thu 11/29/2007 4:21 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE for new management class
OK, the Q INCLEXCL output is what we're interested in.
You read the Q INCLEXCL from
Raibeck
Sent: Thu 11/29/2007 4:21 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE for new management class
OK, the Q INCLEXCL output is what we're interested in.
You read the Q INCLEXCL from the top down (opposite of the dsm.opt file).
Notice that all the dir excludes (EXCLUDE.DIR
line will be bound to the initial include.
I hope that's as clear as it is brief.
From: ADSM: Dist Stor Manager on behalf of Andrew Raibeck
Sent: Thu 11/29/2007 6:53 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE for new management class
Fred, I
19 matches
Mail list logo
