Re: NDMP over IP Performance

[Ian-IT Smith]

Over LAN Free, it flies approx 60MBs.

Still have performance problems over IP. The backup threads run at around
15 MBs, but a restore thread runs at 4MBs. Using virtualfsmapping means
the volume can be broken down into multiple threads. However, it is still
clear that per thread the performance especially on restore is horrific.


Ian Smith




Robert Clark <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
29/11/2007 05:28
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] NDMP over IP Performance






I haven't run any throughput tests against NDMP yet, but I'm curious
to see what kind of numbers it can do.

If the TSM server runs on AIX, you can look at the output from
"vmstat -i 1" to see how many interrupts are are being processed per
second.

Going to jumbo packets and using interrupt mitigation can usually
increase overall network throughput.

I wonder what throughput will be like on 10Gbit ethernet?

[RC]

On Nov 20, 2007, at 12:34 PM, Ian-IT Smith wrote:

> Thanks Neil. I greatly appreciate your time on this. Everything you
> have
> said is very useful!!!
>
> In the mean time, we have found an issue that may be the cause. The
> Network switch ports that the backup NIC is set to is configured to
> the
> Flow Control -OFF.
>
> Looking at this we are planning to enable flowcontrol for send and
> recieve. I will keep you update at the performance. I have been
> advised by
> NetApp that 28MB/s is a good performance per volume. Then to
> configure it
> to backup 8 at the same time.
>
> We are using Flexvols...
>
> Ian Smith
>
>
>
>
> "Strand, Neil B." <[EMAIL PROTECTED]>
> Sent by: "ADSM: Dist Stor Manager" 
> 20/11/2007 20:25
> Please respond to
> "ADSM: Dist Stor Manager" 
>
>
> To
> ADSM-L@VM.MARIST.EDU
> cc
>
> Subject
> Re: [ADSM-L] NDMP over IP Performance
>
>
>
>
>
>
> Ian,
> Nothing special on the NetApp.
> - The data being backed up is a snapshot of a LUN and there are no NAS
> shares on the filer so there is little contention for ethernet.
> - I do have multiple Gb ethernet interfaces VIFed on the filer.
> - Verify that you are using a Gb interface and not the 100Mb onboard
> interface if you are using a FAS960 or some other ancient filer.
>
> Nothing special on the TSM server.
> - I have virtualfsmap to the snapshot defined.  The snapshot is
> created
> with snapmanager for Exchange once a day.
> - Backups are run from an admin script on the TSM server.
> - I backup about 5TB from 6 filers in 10 hours to a single TSM server
> using NDMP over ethernet.  My bottleneck is the CPU on the TSM server
> which is consistantly pegged at 100% during the backup evolution.
>
> Things to look at:
> 1. Verify that your ethernet settings on both the TSM server and NAS
> filer AND the switch between them are all consistent and correct.
> There
> should be no retransmits.  If there is a router between your filer and
> TSM server, the routing delay may be a factor.  If the filer is a NAS
> filer, there may be contention for ethernet bandwidth.
>
> 2. Take the tape out of the picture by creating a small disk pool of
> known performance and designate it as the target and run a test
> backup.
>
> 3. If your SAN interface is the bottleneck, play around with your
> num_cmd_elems, buffers and max_xfr_size (on AIX).
>
> 4. Ensure your filer is configured for performance.  Are you using
> flex
> vols with the aggregrate spread across as many disks as possible (good
> performance) or traditional vols with a couple of disks (not so good
> performance)?
>
>
>
> Cheers,
> Neil Strand
> Storage Engineer - Legg Mason
> Baltimore, MD.
> (410) 580-7491
> Whatever you can do or believe you can, begin it.
> Boldness has genius, power and magic.
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
> Behalf Of
> Ian-IT Smith
> Sent: Tuesday, November 20, 2007 1:27 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] NDMP over IP Performance
>
> That performance is superb!!
>
> To get that, did you go with the defaults, or was any significant
> tuning
> done?
>
> Were there any filer settings that needed to be changed?
>
> Also, was there any network gotchas that you encountered?
>
>
> Thanks so so much!
>
> Ian
>
>
>
> "Strand, Neil B." <[EMAIL PROTECTED]> Sent by: "ADSM: Dist
> Stor Manager" 
> 20/11/2007 18:15
> Please respond to
> "ADSM: Dist Stor Manager" 
>
>
> To
> ADSM-L@VM.MARIST.EDU
> cc
>
> Subject
> Re: [ADSM-L] NDMP over IP Performance
>
>
>
>
>
>
> Ian,
>I am backing up a NetApp 3070 to a TSM 5.4.1.1 server on a P55a
> with
> AIX 5.3 to a TS7520 VTL over ethernet.
>
> There is a significant ethernet workload on the TSM server because
> I am
> backing up 6 Netapp filers simultaneously.
>
> Sar shows 100% cpu utilization on the TSM server during the processing
> due to the high ethernet load.
>
> I have one 50GB backup that takes 30 minutes (1.6GB/minute)
>
> Make sure you are using TSM 5.4.1.1 or later because it addresse

Sizing virtual tapes

[David E Ehresman]

How large are you making the max size of your virtual tapes?  Why?

I let my TS7520 emulating 3592E tapes default to a max size of 460GB but I'm 
starting to think a smaller size would make more sense.  The median size of 
occupancy for my nodes is around 40GB so I'm thinking that might be a better 
max size to facilicate reclamination.

David

Re: Sizing virtual tapes

[Schneider, John]

David,
Your question is a good one.  On our EMC Disk Libraries we
emulate LTO1 tape drives, with 50GB maximum tapes.  I believe this
improves overall disk utilization for just the reason you mention.  You
can reclaim the smaller tapes sooner.  TSM won't have to wait until
~250GB of data, which may have been written over a period of weeks,
expires before the virtual tape is ready to reclaim.

Best Regards,

John D. Schneider
Lead Systems Administrator - Storage
Sisters of Mercy Health Systems
Email:  [EMAIL PROTECTED]


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
David E Ehresman
Sent: Thursday, November 29, 2007 8:01 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Sizing virtual tapes


How large are you making the max size of your virtual tapes?  Why?

I let my TS7520 emulating 3592E tapes default to a max size of 460GB but
I'm starting to think a smaller size would make more sense.  The median
size of occupancy for my nodes is around 40GB so I'm thinking that might
be a better max size to facilicate reclamination.

David

Re: Sizing virtual tapes

[Johnson, Milton]

Here is my response to an earlier question on sizing a VTL.  I have been
using a 10GB tape volume size for a couple of years and have not seen a
reason to change.  I originally chose 10GB because ISM recommended that
size when using sequential file devices.

Yes that is an approach that will work. I used:
(Total_Bytes_in_Primary_STG + ((Max_Daily_Amt_Backed-up X (ReuseDelay +
2))) X Growth_factor

I then let the compression factor be my fudge factor.

However give some thought to the size (native capacity) of your virtual
tape volumes.  In the physical world you have little control over this
(we generally use the largest size cartridge we can get to have the
greatest capacity [volume size times fixed number of cartridge slots =
total capacity online]).  In the VTL world things are different, you
total capacity is fixed (determined by the disk space you purchased) but
YOU can determine the volume size and the number cartridge slots equals
the total capacity divided by the size of your virtual tape volumes.

This said, what can you do with it?  I went with a small tape size
(10GB) and have the following benefits:
A) If I need a file at the end of the tape I spin through 10GB not 100GB
of data (ignoring compression).
B) No matter what reclamation threshold you use, you will have tapes
that are 1% short of being reclaimed.  Small tapes in this state "waste"
less space then large tapes in that state.

One gotcha is deciding which physical library you are emulating.  When I
first brought my VTL up, TSM choked.  Why?  Because TSM "knew" that the
library I was emulating could not have 1,415 physical tape slots.  I
changed the emulation to an "ADIC Scalar 10K" and the problem was
solved.  Sorry I don't remember the original library emulation.

Just a thought, think outside the physical box, it's all virtual.

Thanks,
H. Milton Johnson 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
David E Ehresman
Sent: Thursday, November 29, 2007 8:01 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Sizing virtual tapes

How large are you making the max size of your virtual tapes?  Why?

I let my TS7520 emulating 3592E tapes default to a max size of 460GB but
I'm starting to think a smaller size would make more sense.  The median
size of occupancy for my nodes is around 40GB so I'm thinking that might
be a better max size to facilicate reclamination.

David

Re: Sizing virtual tapes

[Strand, Neil B.]

David,
   I originally set my TS7510 to the default 300GB vtape size with
dynamic allocation where only 5GB is initially allocated and the space
is grown as data is written.  I found out that once data is written to a
vtape, the vtape will retain that size until it is scratched AND THEN
written to again - at which point it will revert to the initial size.
I had a bunch of scratch vtapes that were consuming 300GB of space on
the VTL because they were not written to AFTER they had been scratched.

   I now use 60GB 3592J vtapes on my TS7520 and it seems to work well.
   By the way - If you also use dynamic allocation, make sure you patch
your TS7520 to Version 05F which was just released yesterday.  I have
experienced numerous system hangs because there is a bug that causes a
race condition when two or more vtapes are being resized simultaneously.

Cheers,
Neil Strand
Storage Engineer - Legg Mason
Baltimore, MD.
(410) 580-7491
Whatever you can do or believe you can, begin it.
Boldness has genius, power and magic.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
David E Ehresman
Sent: Thursday, November 29, 2007 9:01 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Sizing virtual tapes

How large are you making the max size of your virtual tapes?  Why?

I let my TS7520 emulating 3592E tapes default to a max size of 460GB but
I'm starting to think a smaller size would make more sense.  The median
size of occupancy for my nodes is around 40GB so I'm thinking that might
be a better max size to facilicate reclamination.

David

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.

Re: Sizing virtual tapes

[Loon, E.J. van - SPLXM]

I agree with John. We are currently using 100Gb. volumes in out DL700,
but I'm frequently called by user who's restore seems to hang.
In most cases the tape is in use by another restore or in use by a
backup storagepool/reclamation which first has to finish the file it's
backing up or reclaiming.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Schneider, John
Sent: donderdag 29 november 2007 15:55
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Sizing virtual tapes

David,
Your question is a good one.  On our EMC Disk Libraries we
emulate LTO1 tape drives, with 50GB maximum tapes.  I believe this
improves overall disk utilization for just the reason you mention.  You
can reclaim the smaller tapes sooner.  TSM won't have to wait until
~250GB of data, which may have been written over a period of weeks,
expires before the virtual tape is ready to reclaim.

Best Regards,

John D. Schneider
Lead Systems Administrator - Storage
Sisters of Mercy Health Systems
Email:  [EMAIL PROTECTED]


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
David E Ehresman
Sent: Thursday, November 29, 2007 8:01 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Sizing virtual tapes


How large are you making the max size of your virtual tapes?  Why?

I let my TS7520 emulating 3592E tapes default to a max size of 460GB but
I'm starting to think a smaller size would make more sense.  The median
size of occupancy for my nodes is around 40GB so I'm thinking that might
be a better max size to facilicate reclamination.

David
**
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286 
**

INCLUDE for new management class

[Fred Johanson]

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 can't see anything syntactically wrong, but it does not work.  He's
also tried 'f:...' with no effect.  He says that he's restarted the
service after each change.  

Can anyone see his error? 

Fred Johanson
TSM Administrator
University of Chicago

773-702-8464

Re: INCLUDE for new management class

[Richard Sims]

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 "F:\NSIT\FieldSupport\University Administration\Budget
Office\*.*" LONGADMIN

I can't see anything syntactically wrong, but it does not work.  He's
also tried 'f:...' with no effect.  He says that he's restarted the
service after each change.

Can anyone see his error?



Fred -

What are the details of "does not work"?
Are any problems/conflicts reported by 'dsmc q inclexcl'?
Has the Policy Set been activated with that Managment Class?

   Richard Sims

Re: INCLUDE for new management class

[Fred Johanson]

"Does not work", his term, which means the files show up on the gui as
being in the default management class.

The new management class does not show up in "Q inclexcl".

The new management class shows up on the active policy set.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[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 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 can't see anything syntactically wrong, but it does not work.  He's
> also tried 'f:...' with no effect.  He says that he's restarted the
> service after each change.
>
> Can anyone see his error?
>

Fred -

What are the details of "does not work"?
Are any problems/conflicts reported by 'dsmc q inclexcl'?
Has the Policy Set been activated with that Managment Class?

Richard Sims

Re: INCLUDE for new management class

[Andrew Raibeck]

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 Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 11/29/2007
01:23:35 PM:

> 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 can't see anything syntactically wrong, but it does not work.  He's
> also tried 'f:...' with no effect.  He says that he's restarted the
> service after each change.
>
> Can anyone see his error?
>
> Fred Johanson
> TSM Administrator
> University of Chicago
>
> 773-702-8464

Re: INCLUDE for new management class

[Fred Johanson]

Andy,

His additions are at the bottom of his dsm.opt file.  There is also a
client optionset that has:

Include ?:* FILESERVER



Fred Johanson
TSM Administrator
University of Chicago

773-702-8464


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf 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 sure those files aren't being picked up by an earlier
filter.

Also make sure the updated policy was activated.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan
ager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 11/29/2007
01:23:35 PM:

> 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 can't see anything syntactically wrong, but it does not work.  He's
> also tried 'f:...' with no effect.  He says that he's restarted the
> service after each change.
>
> Can anyone see his error?
>
> Fred Johanson
> TSM Administrator
> University of Chicago
>
> 773-702-8464

Re: INCLUDE for new management class

[Strand, Neil B.]

The options defined in server client optins have precidence
>From page 353 in the server guide V5.4

 Any include-exclude statements in the server client option set have
priority over the include-exclude statements in the local client options
file. The server include-exclude statements are always enforced and
placed at the bottom of the include-exclude list and evaluated before
the client include-exclude statements.



Neil Strand
Storage Engineer - Legg Mason
Baltimore, MD.
(410) 580-7491
Whatever you can do or believe you can, begin it.
Boldness has genius, power and magic.


-Original 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 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.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail:
[EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan
ager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 11/29/2007
02:41:26 PM:

> Andy,
>
> His additions are at the bottom of his dsm.opt file.  There is also a
> client optionset that has:
>
> Include ?:* FILESERVER
>
>
>
> Fred Johanson
> TSM Administrator
> University of Chicago
>
> 773-702-8464
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
> 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 sure those files aren't being picked up by an

> earlier filter.
>
> Also make sure the updated policy was activated.
>
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Product Development Level 3 Team Lead
> Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet
> e-mail: [EMAIL PROTECTED]
>
> IBM Tivoli Storage Manager support web page:
> http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageM
> an
> ager.html
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager"  wrote on 11/29/2007
> 01:23:35 PM:
>
> > 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 can't see anything syntactically wrong, but it does not work.
> > He's also tried 'f:...' with no effect.  He says that he's restarted

> > the service after each change.
> >
> > Can anyone see his error?
> >
> > Fred Johanson
> > TSM Administrator
> > University of Chicago
> >
> > 773-702-8464

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.

Re: INCLUDE for new management class

[Fred Johanson]

There are no 'INCLUDE' lines in the option set other than the initial
one.

This is the dsm.opt:

EXCLUDE.BACKUP "*:\microsoft uam volume\...\*" 
EXCLUDE.BACKUP "*:\microsoft uam volume\...\*.*" 
EXCLUDE.BACKUP "*:\...\EA DATA. SF" 
EXCLUDE.BACKUP "*:\IBMBIO.COM" 
EXCLUDE.BACKUP "*:\IBMDOS.COM" 
EXCLUDE.BACKUP "*:\IO.SYS" 
EXCLUDE.BACKUP "*:\...\system32\config\...\*" 
EXCLUDE.BACKUP "*:\...\system32\Perflib*.dat" 
EXCLUDE.BACKUP "*:\...\system32\dhcp\...\*" 
INCLUDE.BACKUP "*:\...\system32\dhcp\backup\...\*" 
EXCLUDE.BACKUP "*:\...\system32\dns\...\*" 
INCLUDE.BACKUP "*:\...\system32\dns\backup\...\*" 
EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*" 
EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*.*" 
EXCLUDE.ARCHIVE "*:\...\EA DATA. SF" 
EXCLUDE.ARCHIVE "*:\IBMBIO.COM" 
EXCLUDE.ARCHIVE "*:\IBMDOS.COM" 
EXCLUDE.ARCHIVE "*:\IO.SYS" 
EXCLUDE.ARCHIVE "*:\...\system32\config\...\*" 
EXCLUDE.ARCHIVE "*:\...\system32\Perflib*.dat" 
EXCLUDE.ARCHIVE "*:\...\system32\dhcp\...\*" 
INCLUDE.ARCHIVE "*:\...\system32\dhcp\backup\...\*" 
EXCLUDE.ARCHIVE "*:\...\system32\dns\...\*" 
INCLUDE.ARCHIVE "*:\...\system32\dns\backup\...\*" 
EXCLUDE.DIR "*:\System Volume Information" 
EXCLUDE.DIR "*:\...\Temporary Internet Files" 
EXCLUDE.DIR "*:\Recycled" 
EXCLUDE.DIR "*:\Recycler"
INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget Office\*"
LONGADMIN
INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget
Office\*.*" LONGADMIN

And the dsmc q inclexcl:

*** FILE INCLUDE/EXCLUDE ***
Mode Function  Pattern (match from top down)  Source File
 - -- -
Excl Directory *\winnt\system32\wins  Server
Excl Directory *\temp Server
Excl Directory *\Recycle* Server
Excl Directory *\I386 Server
Excl Directory *\Program Files\Network Associates\VirusScan NT Server
Excl Directory C:\adsm.sysOperating System
Excl Directory *\Recycler dsm.opt
Excl Directory *\Recycled dsm.opt
Excl Directory *\...\Temporary Internet Files dsm.opt
Excl Directory *\System Volume Informationdsm.opt
Exclude All   *\winnt\system32\DTCLog\MsDTC.log Server
Exclude All   *\winnt\netlogon.chg   Server
Exclude All   *\winnt\debug\*.*  Server
Exclude All   *\winnt\debug\*Server
Exclude All   *\winnt\csc\*.*Server
Exclude All   *\winnt\csc\*  Server
Exclude All   *\winnt\Registration\*.clb Server
Exclude All   *\hibernate.datServer
Exclude All   *\hiberfil.sys Server
Exclude All   *\ffastun*.ff? Server
Exclude All   *\MSDOS.SYSServer
Exclude All   *\IO.SYS   Server
Exclude All   *\IBMDOS.COM   Server
Exclude All   *\IBMBIO.COM   Server
Exclude All   *\...\pagefile.sys Server
Exclude All   *\...\SYSTEM32\CONFIG\...\*Server
Exclude All   *\...\SYSTEM32\CONFIG\*.*  Server
Exclude All   *\...\Cache\*.*Server
Exclude All   *\...\Cache\*  Server
Exclude All   *\*.crmlog Server
Exclude All   *\microsoft uam volume\...\*.* Server
Exclude All   *\microsoft uam volume\...\*   Server
Exclude All   *\microsoft uam volume\*.* Server
Exclude All   *\microsoft uam volume\*   Server
Exclude All   *\macintosh volume\...\*.* Server
Exclude All   *\macintosh volume\...\*   Server
Exclude All   *\macintosh volume\*.* Server
Exclude All   *\macintosh volume\*   Server
Exclude All   *\Documents and setting\...\index.dat Server
Exclude All   *\Documents and Settings\...\ntuser.dat.log Server
Exclude All   *\Documents and Settings\...\ntuser.dat Server
Exclude All   *\Documents and Settings\...\Local Settings\temp\*.*
Server
Exclude All   *\Documents and Settings\...\Local Settings\temp\*
Server
Exclude All   *\Documents and Settings\...\Local
Settings\Application Data\Microsoft\Windows\UsrClass.dat.log Server
Exclude All   *\Documents and Settings\...\Local
Settings\Application Data\Microsoft\Windows\UsrClass.dat Server
Exclude All   *\...\Temporary Internet Files\*.* Server
Exclude All   *\...\Temporary Internet Files\* Server
Exclude All   *\...\EA DATA. SF  Server
Include All   *\...\*Server
Exclude All   C:\WINDOWS\usrclass.dat.logOperating System
Exclude All   C:\WINDOWS\usrclass.datOperating System
Exclude All   C:\WINDOWS\Tasks\schedlgu.txt  Operating System
Exclude All   C:\WINDOWS\system32\WBEM\Repository\...\*.* Operating
System
Exclude All   C:\WINDOWS\system32\NtmsData\...\* Operating System
Exclude All   C:\WINDOWS\system32\MSDtc\trace\dtctrace.log Operating
Sy

Re: INCLUDE for new management class

[Andrew Raibeck]

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.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 11/29/2007
02:41:26 PM:

> Andy,
>
> His additions are at the bottom of his dsm.opt file.  There is also a
> client optionset that has:
>
> Include ?:* FILESERVER
>
>
>
> Fred Johanson
> TSM Administrator
> University of Chicago
>
> 773-702-8464
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf 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 sure those files aren't being picked up by an earlier
> filter.
>
> Also make sure the updated policy was activated.
>
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Product Development
> Level 3 Team Lead
> Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
> Internet e-mail: [EMAIL PROTECTED]
>
> IBM Tivoli Storage Manager support web page:
> http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan
> ager.html
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager"  wrote on 11/29/2007
> 01:23:35 PM:
>
> > 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 can't see anything syntactically wrong, but it does not work.  He's
> > also tried 'f:...' with no effect.  He says that he's restarted the
> > service after each change.
> >
> > Can anyone see his error?
> >
> > Fred Johanson
> > TSM Administrator
> > University of Chicago
> >
> > 773-702-8464

Re: INCLUDE for new management class

[Andrew Raibeck]

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) are at the top, since those
are always filtered first, regardless of how they are positioned.

So starting from the top 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
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 11/29/2007
03:00:42 PM:

> There are no 'INCLUDE' lines in the option set other than the initial
> one.
>
> This is the dsm.opt:
>
> EXCLUDE.BACKUP "*:\microsoft uam volume\...\*"
> EXCLUDE.BACKUP "*:\microsoft uam volume\...\*.*"
> EXCLUDE.BACKUP "*:\...\EA DATA. SF"
> EXCLUDE.BACKUP "*:\IBMBIO.COM"
> EXCLUDE.BACKUP "*:\IBMDOS.COM"
> EXCLUDE.BACKUP "*:\IO.SYS"
> EXCLUDE.BACKUP "*:\...\system32\config\...\*"
> EXCLUDE.BACKUP "*:\...\system32\Perflib*.dat"
> EXCLUDE.BACKUP "*:\...\system32\dhcp\...\*"
> INCLUDE.BACKUP "*:\...\system32\dhcp\backup\...\*"
> EXCLUDE.BACKUP "*:\...\system32\dns\...\*"
> INCLUDE.BACKUP "*:\...\system32\dns\backup\...\*"
> EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*"
> EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*.*"
> EXCLUDE.ARCHIVE "*:\...\EA DATA. SF"
> EXCLUDE.ARCHIVE "*:\IBMBIO.COM"
> EXCLUDE.ARCHIVE "*:\IBMDOS.COM"
> EXCLUDE.ARCHIVE "*:\IO.SYS"
> EXCLUDE.ARCHIVE "*:\...\system32\config\...\*"
> EXCLUDE.ARCHIVE "*:\...\system32\Perflib*.dat"
> EXCLUDE.ARCHIVE "*:\...\system32\dhcp\...\*"
> INCLUDE.ARCHIVE "*:\...\system32\dhcp\backup\...\*"
> EXCLUDE.ARCHIVE "*:\...\system32\dns\...\*"
> INCLUDE.ARCHIVE "*:\...\system32\dns\backup\...\*"
> EXCLUDE.DIR "*:\System Volume Information"
> EXCLUDE.DIR "*:\...\Temporary Internet Files"
> EXCLUDE.DIR "*:\Recycled"
> EXCLUDE.DIR "*:\Recycler"
> INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget Office\*"
> LONGADMIN
> INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget
> Office\*.*" LONGADMIN
>
> And the dsmc q inclexcl:
>
> *** FILE INCLUDE/EXCLUDE ***
> Mode Function  Pattern (match from top down)  Source File
>  - -- -
> Excl Directory *\winnt\system32\wins  Server
> Excl Directory *\temp Server
> Excl Directory *\Recycle* Server
> Excl Directory *\I386 Server
> Excl Directory *\Program Files\Network Associates\VirusScan NT Server
> Excl Directory C:\adsm.sysOperating System
> Excl Directory *\Recycler dsm.opt
> Excl Directory *\Recycled dsm.opt
> Excl Directory *\...\Temporary Internet Files dsm.opt
> Excl Directory *\System Volume Informationdsm.opt
> Exclude All   *\winnt\system32\DTCLog\MsDTC.log Server
> Exclude All   *\winnt\netlogon.chg   Server
> Exclude All   *\winnt\debug\*.*  Server
> Exclude All   *\winnt\debug\*Server
> Exclude All   *\winnt\csc\*.*Server
> Exclude All   *\winnt\csc\*  Server
> Exclude All   *\winnt\Registration\*.clb Server
> Exclude All   *\hibernate.datServer
> Exclude All   *\hiberfil.sys Server
> Exclude All   *\ffastun*.ff? Server
> Exclude All   *\MSDOS.SYSServer
> Exclude All   *\IO.SYS   Server
> Exclude All   *\IBMDOS.COM   Server
> Exclude All   *\IBMBIO.COM   Server
> Exclude All   *\...\pagefile.sys Server
> Exclude All   *\...\SYSTEM32\CONFIG\...\*Server
> Exclude All   *\...\SYSTEM32\CONFIG\*.*  Server
> Exclude All   *\...\Cache\*.*Server
> Exclude All   *\...\Cache\*  Server
> Exclude All   *\*.crmlog Server
> Exclude All   *\microsoft uam volume\...\*.* Server
> Exclude All   *\microsoft uam volume\...\*   Server
> Exclude All   *\microsoft uam volume\*.* Server
> Exclude All   *\microsoft uam volume\*   Server
> Exclude All   *\macintosh volume\...\*.* Server
> Exclude All   *\macintosh volume\...\*   Server
> Exclude All   *\macintosh volume\*.* Server
> Exclude All   *\macintosh volume\*   Server
> Exclude All   *\Docum

Re: INCLUDE for new management class

[Andrew Raibeck]

Fred, I cannot give you a definitive to answer your question since I do
not know your shop, its policies, service level agreement, etc., For
example, it could be your shop policy that the INCLUDE *:\...\* is
deliberate to prevent users from overriding via dsm.opt settings.

Having said that: removing that INCLUDE would enable use of the
client-side option (I leave it to you to review the Q INCLEXCL output to
confirm there no other interfering settings). Whether you really want to
do that, I cannot say.

Another alternative is to make a new client option set for this user that
does not have the INCLUDE *:\...\*. Or set the node to not use any client
option set. Or configure a special node name for backing up just those
files.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 11/29/2007
05:38:30 PM:

> So how does he get what he wants.  The option set is to set a
> management class for a number of clients.  The new management class
> applies to 1 of the 10.  Will setting the OVERRIDE=yes have the
> desired effect?
>
> 
>
> 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 the top down (opposite of the dsm.opt
file).
> Notice that all the dir excludes (EXCLUDE.DIR) are at the top, since
those
> are always filtered first, regardless of how they are positioned.
>
> So starting from the top 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
> Tivoli Storage Manager Client Product Development
> Level 3 Team Lead
> Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
> Internet e-mail: [EMAIL PROTECTED]
>
> IBM Tivoli Storage Manager support web page:
> http://www.ibm.
> com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager"  wrote on 11/29/2007
> 03:00:42 PM:
>
> > There are no 'INCLUDE' lines in the option set other than the initial
> > one.
> >
> > This is the dsm.opt:
> >
> > EXCLUDE.BACKUP "*:\microsoft uam volume\...\*"
> > EXCLUDE.BACKUP "*:\microsoft uam volume\...\*.*"
> > EXCLUDE.BACKUP "*:\...\EA DATA. SF"
> > EXCLUDE.BACKUP "*:\IBMBIO.COM"
> > EXCLUDE.BACKUP "*:\IBMDOS.COM"
> > EXCLUDE.BACKUP "*:\IO.SYS"
> > EXCLUDE.BACKUP "*:\...\system32\config\...\*"
> > EXCLUDE.BACKUP "*:\...\system32\Perflib*.dat"
> > EXCLUDE.BACKUP "*:\...\system32\dhcp\...\*"
> > INCLUDE.BACKUP "*:\...\system32\dhcp\backup\...\*"
> > EXCLUDE.BACKUP "*:\...\system32\dns\...\*"
> > INCLUDE.BACKUP "*:\...\system32\dns\backup\...\*"
> > EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*"
> > EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*.*"
> > EXCLUDE.ARCHIVE "*:\...\EA DATA. SF"
> > EXCLUDE.ARCHIVE "*:\IBMBIO.COM"
> > EXCLUDE.ARCHIVE "*:\IBMDOS.COM"
> > EXCLUDE.ARCHIVE "*:\IO.SYS"
> > EXCLUDE.ARCHIVE "*:\...\system32\config\...\*"
> > EXCLUDE.ARCHIVE "*:\...\system32\Perflib*.dat"
> > EXCLUDE.ARCHIVE "*:\...\system32\dhcp\...\*"
> > INCLUDE.ARCHIVE "*:\...\system32\dhcp\backup\...\*"
> > EXCLUDE.ARCHIVE "*:\...\system32\dns\...\*"
> > INCLUDE.ARCHIVE "*:\...\system32\dns\backup\...\*"
> > EXCLUDE.DIR "*:\System Volume Information"
> > EXCLUDE.DIR "*:\...\Temporary Internet Files"
> > EXCLUDE.DIR "*:\Recycled"
> > EXCLUDE.DIR "*:\Recycler"
> > INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget
Office\*"
> > LONGADMIN
> > INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget
> > Office\*.*" LONGADMIN
> >
> > And the dsmc q inclexcl:
> >
> > *** FILE INCLUDE/EXCLUDE ***
> > Mode Function  Pattern (match from top down)  Source File
> >  - -- -
> > Excl Directory *\winnt\system32\wins  Server
> > Excl Directory *\temp Server
> > Excl Directory *\Recycle* Server
> > Excl Directory *\I386 Server
> > Excl Directory *\Program Files\Network Associates\VirusScan NT Server
> > Excl Directory C:\adsm.sysOperating System
> > Excl Di

Re: INCLUDE for new management class

[Fred Johanson]

So how does he get what he wants.  The option set is to set a management class 
for a number of clients.  The new management class applies to 1 of the 10.  
Will setting the OVERRIDE=yes have the desired effect?



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 the top down (opposite of the dsm.opt file).
Notice that all the dir excludes (EXCLUDE.DIR) are at the top, since those
are always filtered first, regardless of how they are positioned.

So starting from the top 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
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 11/29/2007
03:00:42 PM:

> There are no 'INCLUDE' lines in the option set other than the initial
> one.
>
> This is the dsm.opt:
>
> EXCLUDE.BACKUP "*:\microsoft uam volume\...\*"
> EXCLUDE.BACKUP "*:\microsoft uam volume\...\*.*"
> EXCLUDE.BACKUP "*:\...\EA DATA. SF"
> EXCLUDE.BACKUP "*:\IBMBIO.COM"
> EXCLUDE.BACKUP "*:\IBMDOS.COM"
> EXCLUDE.BACKUP "*:\IO.SYS"
> EXCLUDE.BACKUP "*:\...\system32\config\...\*"
> EXCLUDE.BACKUP "*:\...\system32\Perflib*.dat"
> EXCLUDE.BACKUP "*:\...\system32\dhcp\...\*"
> INCLUDE.BACKUP "*:\...\system32\dhcp\backup\...\*"
> EXCLUDE.BACKUP "*:\...\system32\dns\...\*"
> INCLUDE.BACKUP "*:\...\system32\dns\backup\...\*"
> EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*"
> EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*.*"
> EXCLUDE.ARCHIVE "*:\...\EA DATA. SF"
> EXCLUDE.ARCHIVE "*:\IBMBIO.COM"
> EXCLUDE.ARCHIVE "*:\IBMDOS.COM"
> EXCLUDE.ARCHIVE "*:\IO.SYS"
> EXCLUDE.ARCHIVE "*:\...\system32\config\...\*"
> EXCLUDE.ARCHIVE "*:\...\system32\Perflib*.dat"
> EXCLUDE.ARCHIVE "*:\...\system32\dhcp\...\*"
> INCLUDE.ARCHIVE "*:\...\system32\dhcp\backup\...\*"
> EXCLUDE.ARCHIVE "*:\...\system32\dns\...\*"
> INCLUDE.ARCHIVE "*:\...\system32\dns\backup\...\*"
> EXCLUDE.DIR "*:\System Volume Information"
> EXCLUDE.DIR "*:\...\Temporary Internet Files"
> EXCLUDE.DIR "*:\Recycled"
> EXCLUDE.DIR "*:\Recycler"
> INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget Office\*"
> LONGADMIN
> INCLUDE "F:\NSIT\FieldSupport\University Administration\Budget
> Office\*.*" LONGADMIN
>
> And the dsmc q inclexcl:
>
> *** FILE INCLUDE/EXCLUDE ***
> Mode Function  Pattern (match from top down)  Source File
>  - -- -
> Excl Directory *\winnt\system32\wins  Server
> Excl Directory *\temp Server
> Excl Directory *\Recycle* Server
> Excl Directory *\I386 Server
> Excl Directory *\Program Files\Network Associates\VirusScan NT Server
> Excl Directory C:\adsm.sysOperating System
> Excl Directory *\Recycler dsm.opt
> Excl Directory *\Recycled dsm.opt
> Excl Directory *\...\Temporary Internet Files dsm.opt
> Excl Directory *\System Volume Informationdsm.opt
> Exclude All   *\winnt\system32\DTCLog\MsDTC.log Server
> Exclude All   *\winnt\netlogon.chg   Server
> Exclude All   *\winnt\debug\*.*  Server
> Exclude All   *\winnt\debug\*Server
> Exclude All   *\winnt\csc\*.*Server
> Exclude All   *\winnt\csc\*  Server
> Exclude All   *\winnt\Registration\*.clb Server
> Exclude All   *\hibernate.datServer
> Exclude All   *\hiberfil.sys Server
> Exclude All   *\ffastun*.ff? Server
> Exclude All   *\MSDOS.SYSServer
> Exclude All   *\IO.SYS   Server
> Exclude All   *\IBMDOS.COM   Server
> Exclude All   *\IBMBIO.COM   Server
> Exclude All   *\...\pagefile.sys Server
> Exclude All   *\...\SYSTEM32\CONFIG\...\*Server
> Exclude All   *\...\SYSTEM32\CONFIG\*.*  Server
> Exclude All   *\...\Cache\*.*Server
> Exclude All   *\...\Cache\*  Server
> Exclude All   *\*.crmlog Server
> Exclude All   *\microsoft uam volume\...\*.* Server
> Exclude All   

Re: INCLUDE for new management class

[Fred Johanson]

Thanks Andy,
 
I'll try to make this brief.  I had thought of making a special cloptset for 
this client, but the machine admin figures that once this special exception 
becomes known, the other 15 to 20 users of the box will want their own 
exceptions.  Being a nice guy, he figures I've got better things to do that 
creating special client  options in the general cloptset.
 
The way of avoiding this, I guess, is redefining the initial INCLUDE (include 
?:* nondefault-mgmtc) with FORCE=NO, if that does mean that all files, 
directories, filespaces, etc., not covered by a separate include 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 cannot give you a definitive to answer your question since I do
not know your shop, its policies, service level agreement, etc., For
example, it could be your shop policy that the INCLUDE *:\...\* is
deliberate to prevent users from overriding via dsm.opt settings.

Having said that: removing that INCLUDE would enable use of the
client-side option (I leave it to you to review the Q INCLEXCL output to
confirm there no other interfering settings). Whether you really want to
do that, I cannot say.

Another alternative is to make a new client option set for this user that
does not have the INCLUDE *:\...\*. Or set the node to not use any client
option set. Or configure a special node name for backing up just those
files.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 11/29/2007
05:38:30 PM:

> So how does he get what he wants.  The option set is to set a
> management class for a number of clients.  The new management class
> applies to 1 of the 10.  Will setting the OVERRIDE=yes have the
> desired effect?
>
> 
>
> 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 the top down (opposite of the dsm.opt
file).
> Notice that all the dir excludes (EXCLUDE.DIR) are at the top, since
those
> are always filtered first, regardless of how they are positioned.
>
> So starting from the top 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
> Tivoli Storage Manager Client Product Development
> Level 3 Team Lead
> Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
> Internet e-mail: [EMAIL PROTECTED]
>
> IBM Tivoli Storage Manager support web page:
> http://www.ibm  .
> com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager"  wrote on 11/29/2007
> 03:00:42 PM:
>
> > There are no 'INCLUDE' lines in the option set other than the initial
> > one.
> >
> > This is the dsm.opt:
> >
> > EXCLUDE.BACKUP "*:\microsoft uam volume\...\*"
> > EXCLUDE.BACKUP "*:\microsoft uam volume\...\*.*"
> > EXCLUDE.BACKUP "*:\...\EA DATA. SF"
> > EXCLUDE.BACKUP "*:\IBMBIO.COM"
> > EXCLUDE.BACKUP "*:\IBMDOS.COM"
> > EXCLUDE.BACKUP "*:\IO.SYS"
> > EXCLUDE.BACKUP "*:\...\system32\config\...\*"
> > EXCLUDE.BACKUP "*:\...\system32\Perflib*.dat"
> > EXCLUDE.BACKUP "*:\...\system32\dhcp\...\*"
> > INCLUDE.BACKUP "*:\...\system32\dhcp\backup\...\*"
> > EXCLUDE.BACKUP "*:\...\system32\dns\...\*"
> > INCLUDE.BACKUP "*:\...\system32\dns\backup\...\*"
> > EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*"
> > EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*.*"
> > EXCLUDE.ARCHIVE "*:\...\EA DATA. SF"
> > EXCLUDE.ARCHIVE "*:\IBMBIO.COM"
> > EXCLUDE.ARCHIVE "*:\IBMDOS.COM"
> > EXCLUDE.ARCHIVE "*:\IO.SYS"
> > EXCLUDE.ARCHIVE "*:\...\system32\config\...\*"
> > EXCLUDE.ARCHIVE "*:\...\system32\Perflib*.dat"
> > EXCLUDE.ARCHIVE "*:\...\system32\dhcp\...\*"
> > INCLUDE.ARCHIVE "*:\...\system32\dhcp\backup\...\*"
> > EXCLUDE.ARCHIVE "*:\...\system32\dns\...\*"
> > INCLUDE.ARCHIVE "*:\...\system32\dns\backup\...\*"
> > EXCLUDE.DIR

Re: INCLUDE for new management class

[Andrew Raibeck]

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.:

define clientopt  inclexcl 'include
"\\machname\f$\nsit\fieldsupport\university administration\budget
office\*" longadmin'

where machname is the machine name for this client. Make sure to insert it
in the sequence so it tested before include *:\...\*.

Note that you don't need the second include with the *.* spec, as that is
redundant.

The idea is that other clients will pick up this include as well, but it
will have no effect due the differing UNC names.

See if that does the trick. On the machine in question, this include
statement will show up as F: in the Q INCLEXCL output; but on other
machines, you'll see it as the UNC name, so it should have no effect on
those machines.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 11/29/2007
07:25:16 PM:

> Thanks Andy,
>
> I'll try to make this brief.  I had thought of making a special
> cloptset for this client, but the machine admin figures that once
> this special exception becomes known, the other 15 to 20 users of
> the box will want their own exceptions.  Being a nice guy, he
> figures I've got better things to do that creating special client
> options in the general cloptset.
>
> The way of avoiding this, I guess, is redefining the initial INCLUDE
> (include ?:* nondefault-mgmtc) with FORCE=NO, if that does mean that
> all files, directories, filespaces, etc., not covered by a separate
> include 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 cannot give you a definitive to answer your question since I do
> not know your shop, its policies, service level agreement, etc., For
> example, it could be your shop policy that the INCLUDE *:\...\* is
> deliberate to prevent users from overriding via dsm.opt settings.
>
> Having said that: removing that INCLUDE would enable use of the
> client-side option (I leave it to you to review the Q INCLEXCL output to
> confirm there no other interfering settings). Whether you really want to
> do that, I cannot say.
>
> Another alternative is to make a new client option set for this user
that
> does not have the INCLUDE *:\...\*. Or set the node to not use any
client
> option set. Or configure a special node name for backing up just those
> files.
>
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Product Development
> Level 3 Team Lead
> Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
> Internet e-mail: [EMAIL PROTECTED]
>
> IBM Tivoli Storage Manager support web page:
> http://www.ibm.
> com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager"  wrote on 11/29/2007
> 05:38:30 PM:
>
> > So how does he get what he wants.  The option set is to set a
> > management class for a number of clients.  The new management class
> > applies to 1 of the 10.  Will setting the OVERRIDE=yes have the
> > desired effect?
> >
> > 
> >
> > 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 the top down (opposite of the dsm.opt
> file).
> > Notice that all the dir excludes (EXCLUDE.DIR) are at the top, since
> those
> > are always filtered first, regardless of how they are positioned.
> >
> > So starting from the top 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
> > Tivoli Storage Manager Client Product Development
> > Level 3 Team Lead
> > Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL