include/exclude

[goc]

hi all,
a short one
in
exclude "*:/.../nohup.out*"
what does *: mean ?
and then with dsmc q inclexcl
*** FILE INCLUDE/EXCLUDE ***
Mode Function  Pattern (match from top down)  Source File
 - -- -
No exclude filespace statements defined.
No exclude directory statements defined.
Exclude All   /.../*:/.../nohup.out*
/usr/local/etc/inclexcl.file
No DFS include/exclude statements defined.

thanks in advance ?

include/exclude

[Moses Show]

Hi,
Am fairly new to TSM but when reading through some of the
literature I have it gives advice and commands on how to view objects
which are included or excluded from a backup. The command offered is dsmc
query inclexcl which I presume is used on the command line of the client
or server. When I try this from the BAClient Gui however this command does
not seem to work, even when missing out the dsmc from the beginning of the
command. Can somebody help me sort this out as I need to try and find out
what files should be  being include/excluded, without having to keep
searching the options files.

Regards
==
This communication, together with any attachments hereto or links contained herein, is 
for the sole use of the intended recipient(s) and may contain information that is 
confidential or legally protected. If you are not the intended recipient, you are 
hereby notified that any review, disclosure, copying, dissemination, distribution or 
use of this communication is STRICTLY PROHIBITED.  If you have received this 
communication in error, please notify the sender immediately by return e-mail message 
and delete the original and all copies of the communication, along with any 
attachments hereto or links herein, from your system.
==
The St. Paul Travelers e-mail system  made this annotation on 05/11/2004 
05:03:49 AM.

include/exclude

[goc]

8hi all ...

how to include content of /usr/local/cvs/ directory and subdirs into one
management class when doing incremental backups ?

is this enough ?

include.backup /usr/local/cvs/* MC_CVS

... it seems not working , i mean the backup works but files are not stored
with this mgmt class,

thanks in advace for any answer

g

include/exclude

[David E Ehresman]

I can seem to get my head wrapped around include/exclude.  What set of
statemetns would allow me to backup /web and /home directories but
nothing else.

Include/Exclude

[Mahesh Tailor]

Hello, all!

I have a clarification question about include/exclude statements.  One of
our Netware guru's pointed this out to me.  Here's what I have (NetWare 5)
in my dsm.opt file:

EXCLUDE *:\...\*.*
INCLUDE DATA:\USERS\...\*.*

When I perform an incremental backup of the node, the system backs up
everything on the system.  If on the other had I do the following:

INCLUDE DATA:\USERS\...\*.*
EXCLUDE *:\...\*.*

The system does not backup anything except the files in the
data:\users\...\*.* directories.

It seems the system is doing just the opposite of what it's supposed to
since these statements are supposed to the processed from the bottom
statement up. [See excerpt from Tivoli Storage Manager for NetWare Using
the Backup-Archive Client manual.]

Excerpt:
These options are checked from the bottom of the include-exclude list up,
until a match is found. If a match is found, the processing stops and
checks whether the option is include or exclude. If the option is include,
the file is backed up. If the option is exclude, the file is not backed
up.

Has something changed?  Can someone explain this?

TIA

Mahesh

Include/Exclude

[Mahesh Tailor]

I had posted this a few days ago, but I am not sure if anyone got it (my
Internet email gateway has not been behaving) . . .


Hello, all!

I have a clarification question about include/exclude statements.  One of
our Netware guru's pointed this out to me.  Here's what I have (NetWare 5)
in my dsm.opt file:

EXCLUDE *:\...\*.*
INCLUDE DATA:\USERS\...\*.*

When I perform an incremental backup of the node, the system backs up
everything on the system.  If on the other had I do the following:

INCLUDE DATA:\USERS\...\*.*
EXCLUDE *:\...\*.*

The system does not backup anything except the files in the
data:\users\...\*.* directories.

It seems the system is doing just the opposite of what it's supposed to
since these statements are supposed to the processed from the bottom
statement up. [See excerpt from Tivoli Storage Manager for NetWare Using
the Backup-Archive Client manual.]

Excerpt:
These options are checked from the bottom of the include-exclude list up,
until a match is found. If a match is found, the processing stops and
checks whether the option is include or exclude. If the option is include,
the file is backed up. If the option is exclude, the file is not backed
up.

Has something changed?  Can someone explain this?

TIA

Mahesh

Include/Exclude

[LeBlanc, Patricia]

I'm wondering how the "operating system" excludes get set.  Below is a
test screen capture of a w2k server, opening up the dsmc.exe and typing
in q inclexcl.
I wanted to INCLUDE the C:\adsm.sys..but how do I update the
operating system excludes



tsm> q inclexcl
*** FILE INCLUDE/EXCLUDE ***
Mode Function  Pattern (match from top down)  Source File
 - -- -
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
Excl Directory *\...\ntds dsm.opt
Excl Directory *\...\ntfrs\jetdsm.opt
Excl Directory *\...\system32\config  dsm.opt
Excl Directory *\...\system32\dhcpdsm.opt
Excl Directory *\...\system32\LServer dsm.opt
Excl Directory *\...\system32\winsdsm.opt
Exclude All   C:\WINNT\system32\NtmsData\...\* Operating System
Exclude All   C:\WINNT\system32\inetsrv\metabase.xml Operating
System
Exclude All   C:\WINNT\system32\inetsrv\metabase.bin Operating
System
Exclude All   C:\WINNT\system32\inetsrv\mbschema.xml Operating
System
Exclude All   C:\WINNT\System32\DtcLog\MSDTC.LOG Operating System

include/exclude

[Stephen Fromm]

I'm backing up files on a Solaris 2.5.1 box and on a Solaris 2.7 box using
Server Version 3, Release 1, Level 2.20.

I want to exclude files and directories so as not to run up my bill with the
people providing the backup service.  Many of my exclude commands don't seem
to work, however.  I took over simple admin jobs for this (I assume I'm
administering the *client*, not the *server*) from someone; her exclude
statements seemed to work pretty well.  Backups are automated (scheduled),
occuring weekdays at midnight, and are incremental.

(1) If I change the include/exclude file, when are the changes "read"?  Do I
have to kill and then restart the daemon (dsmc)?

(2) Is there any way to test my include/exclude statements using the
backup/restore GUI?

Syntax questions:

>From HTML help files:
Using the UNIX Backup-Archive Clients:
Exclude:
"The exclude.dir option works only if the excluded directory is a
subdirectory; if you explicitly specify the directory or the files within
it, the file is backed up."
- I don't understand that.  Does it just mean "use exclude.dir with
directories only, not files"?

"You cannot, however, specify wildcard characters on the directory name when
you want to exclude a single directory."
- I'm confused by this.  I assume what the authors really intended was that
it's not a good idea, since the pattern might match other directories that
you didn't intend.  As written, though, it states the syntax is *illegal*.

Under the discussion of the "pattern" parameter, it states:
"For the exclude.dir option, the pattern is a directory name, not a file
specification, and wildcards are not permitted."
- If /export/home/foo is a directory, does this mean /.../foo is illegal, or
/export/home/fo* is illegal, or both?

sjfromm

Include/Exclude

[Ibán Bernaldo de Quirós y Márquez]

Hi,

Why the options file could be edited locally by users who owns root 
privileges (ex: users with laptops), why this information is not kept in 
the server and manage by TSM administrators ¿?


It seems that some users could manage their own backups, and backup 
something that will occupy space without being important for restore 
(ex: movie files, music, photos,...)


What do you think ¿?

Thanks,

Regards,
Ibán.

Include/Exclude

[Sascha Braeuning]

Hi TSMers,

I've got backed up some directories and files, which I should not. Now I
changed my include/exclude list. What happened with files, which are backed
up but now actually excluded? When these files remain on the server: Is
there a possibility to delete these files?

MfG/regards
Sascha Bräuning


Sparkassen Informatik, Fellbach

OrgEinheit: 6322
Wilhelm-Pfitzer Str. 1
70736 Fellbach

Telefon:   (0711) 5722-2144
Telefax:   (0711) 5722-1634

Mailadr.:  [EMAIL PROTECTED]

Include/Exclude

[Gill, Geoffrey L.]

I've just installed WIN2K client 5.1.0.1 on a system to play with and from
what I can see the Exclude list does not work. I have some Exclude.Dir lines
and these directories will probably back up since I still see the files
normally with the GUI. Within those directories I can see specific excludes
from other excludes I do have on specific types of files that do work. I've
tried * and ? with no success.

Anyone else seen this?

Anyone have a Win2k or NT dsm.opt they've tested on the V5 client with the
"standards" that work?

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail: [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 905-7154

include \ exclude

[Tim Brown]

Attempting to include just one subfolder within a folder that I want to exclude.
Cant  seem to come up with right combination.

Is the 2nd overriding the first?

Include "D:\USR1\Folder1\Folder2\Folder3\Folder4\...\*.*"

Exclude "D:\USR1\Folder1\...\*.*"

Thanks,

Tim

Domino Include/Exclude

[Zoltan Forray/AC/VCU]

Can someone please send me their include/exclude statements for
redirecting Domino/Notes backups to a specific managementclass ?

We are trying to direct "weekly" backups to an MC that goes straight to
tape but still have the "daily" go to an MC that points to a disk landing
zone. Yes we have multiple node definitions, per the "cookbook".

We seem to be doing something wrong and getting various error
messages/failures !

ACD0215E All backup objects do not have the same management class backup
copy destination.
Explanation: In order to maintain backup data integrity, multiple backup objects are
sent to the Tivoli Storage Manager server within a single transaction. All
backup objects within a single transaction are required to have the same
management class backup copy destinations.

Thanks !

Re: INCLUDE/EXCLUDE

[Lepre, James]

TSMer's

 

  I have excluded a number of files in the .opt file for a server, yet
they are still coming up in the activity log.  Can someone shed some
light on this?

 

The B/A GUI states that these particular files are excluded.

 

Server Level 5.4.1.1

Client Level 5.3.0.5

 

Thank you in advance

 

James

 

Activity Log 

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_334.dat': the object is in
use by another process (SESSION: 23442)

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_390.dat': the object is in
use by another process (SESSION: 23442)

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_528.dat': the object is in
use by another process (SESSION: 23442)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\msdbdata.mdf': the object is in use
by another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\msdblog.ldf': the object is in use by
another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NCS_CONVERSION_Data.MDF': the object
is in use by another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NCS_CONVERSION_Log.LDF': the object
is in use by another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_Data.MDF': the object is in use
by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_LIFELINE_Data.MDF': the object is
in use by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_LIFELINE_Log.LDF': the object is
in use by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_Log.LDF': the object is in use by
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\pa_usf.ldf': the object is in use by
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\pa_usf.mdf': the object is in use by
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\QuestWorkDatabase_Data.mdf': the
object is in use by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\QuestWorkDatabase_Log.ldf': the
object is in use by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\scanning_Data.MDF': the object is in
use by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\scanning_Log.LDF': the object is in
use by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\tempdb.mdf': the object is in use by
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\templog.ldf': the object is in use by
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\TPM30.mdf': the object is in use by
another process (SESSION: 23450)

 

 

 


  
  
---
Confidentiality Notice: The information in this e-mail and any attachments 
thereto is intended for the named recipient(s) only.  This e-mail, including 
any attachments, may contain information that is privileged and confidential  
and subject to legal restrictions and penalties regarding its unauthorized 
disclosure or other use.  If you are not the intended recipient, you are hereby 
notified that any disclosure, copying, distribution, or the taking of any 
action or inaction in reliance on the contents of this e-mail and any of its 
attachments is STRICTLY PROHIBITED.  If you have received this e-mail in error, 
please immediately notify the sender via return e-mail; delete this e-mail and 
al

Re: INCLUDE/EXCLUDE

[Ochs, Duane]

Send a capture of the excludes.
Did you restart the scheduler service after making the additions ?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lepre, 
James
Sent: Wednesday, January 16, 2008 3:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: INCLUDE/EXCLUDE

TSMer's

 

  I have excluded a number of files in the .opt file for a server, yet they are 
still coming up in the activity log.  Can someone shed some light on this?

 

The B/A GUI states that these particular files are excluded.

 

Server Level 5.4.1.1

Client Level 5.3.0.5

 

Thank you in advance

 

James

 

Activity Log 

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_334.dat': the object is in use by 
another process (SESSION: 23442)

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_390.dat': the object is in use by 
another process (SESSION: 23442)

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_528.dat': the object is in use by 
another process (SESSION: 23442)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\msdbdata.mdf': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\msdblog.ldf': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NCS_CONVERSION_Data.MDF': the object is in 
use by another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NCS_CONVERSION_Log.LDF': the object is in 
use by another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_Data.MDF': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_LIFELINE_Data.MDF': the object is in use 
by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_LIFELINE_Log.LDF': the object is in use 
by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_Log.LDF': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\pa_usf.ldf': the object is in use by another 
process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\pa_usf.mdf': the object is in use by another 
process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\QuestWorkDatabase_Data.mdf': the object is 
in use by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\QuestWorkDatabase_Log.ldf': the object is in 
use by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\scanning_Data.MDF': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\scanning_Log.LDF': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\tempdb.mdf': the object is in use by another 
process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\templog.ldf': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\TPM30.mdf': the object is in use by another 
process (SESSION: 23450)

 

 

 


  
  
---
Confidentiality Notice: The information in this e-mail and any attachments 
thereto is intended for the named recipient(s) only.  This e-mail, including 
any attachments, m

Re: INCLUDE/EXCLUDE

[Lepre, James]

Yes I restarted it 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ochs, Duane
Sent: Wednesday, January 16, 2008 4:07 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE/EXCLUDE

Send a capture of the excludes.
Did you restart the scheduler service after making the additions ?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lepre, 
James
Sent: Wednesday, January 16, 2008 3:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: INCLUDE/EXCLUDE

TSMer's

 

  I have excluded a number of files in the .opt file for a server, yet they are 
still coming up in the activity log.  Can someone shed some light on this?

 

The B/A GUI states that these particular files are excluded.

 

Server Level 5.4.1.1

Client Level 5.3.0.5

 

Thank you in advance

 

James

 

Activity Log 

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_334.dat': the object is in use by 
another process (SESSION: 23442)

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_390.dat': the object is in use by 
another process (SESSION: 23442)

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_528.dat': the object is in use by 
another process (SESSION: 23442)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\msdbdata.mdf': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\msdblog.ldf': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NCS_CONVERSION_Data.MDF': the object is in 
use by another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NCS_CONVERSION_Log.LDF': the object is in 
use by another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_Data.MDF': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_LIFELINE_Data.MDF': the object is in use 
by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_LIFELINE_Log.LDF': the object is in use 
by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_Log.LDF': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\pa_usf.ldf': the object is in use by another 
process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\pa_usf.mdf': the object is in use by another 
process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\QuestWorkDatabase_Data.mdf': the object is 
in use by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\QuestWorkDatabase_Log.ldf': the object is in 
use by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\scanning_Data.MDF': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\scanning_Log.LDF': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\tempdb.mdf': the object is in use by another 
process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\templog.ldf': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\TPM30.mdf': the object is in use by another 
process (SESSION: 23450)

 

 

 


  
  

Re: INCLUDE/EXCLUDE

[Lepre, James]

Exclude "*:\microsoft uam volume\...\*"
Exclude "*:\microsoft uam volume\...\*.*"
Exclude "*:\...\EA DATA. SF"
Exclude *:\...\pagefile.sys
Exclude *:\IBMBIO.COM
Exclude *:\IBMDOS.COM
Exclude *:\MSDOS.SYS
Exclude *:\IO.SYS
Exclude *:\...\SYSTEM32\CONFIG\...\*
Exclude *:\...\SYSTEM32\CONFIG\...\*.*
Exclude *:\...\Profiles\...\ntuser.dat* 
Exclude *:\...\system32\Perflib*.dat
Exclude.dir *:\...\system32\wins
Exclude.dir *:\...\system32\LServer
Exclude.dir *:\...\system32\dhcp
Exclude.dir *:\...\system32\config
Exclude.dir *:\...\ntfrs\jet
Exclude.dir *:\...\ntds
Exclude.dir "*:\System Volume Information"
Exclude.dir "*:\...\Temporary Internet Files"
Exclude.dir *:\Recycled
Exclude.dir *:\Recycler
Exclude.dir "d:\MSSQL2000\MSSQL\Data\*.*"
EXCLUDE.DIR "*:\...\temp"
EXCLUDE.DIR "*:\...\$*$"
EXCLUDE.DIR "*:\...\tivoli" 
EXCLUDE.BACKUP "*:\...\*.ldf"
EXCLUDE.BACKUP "*:\...\*.mdf"
EXCLUDE.BACKUP "*:\...\*.ndf"
EXCLUDE.BACKUP "*:\Documents and Settings\...\*.DAT" 
EXCLUDE.BACKUP "*:\Documents and Settings\...\*.DAT.log"
EXCLUDE.BACKUP "*:\WebTools\...\*.000"
EXCLUDE.BACKUP "*:\Inetpub\...\*.000"
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ochs, Duane
Sent: Wednesday, January 16, 2008 4:07 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE/EXCLUDE

Send a capture of the excludes.
Did you restart the scheduler service after making the additions ?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lepre, 
James
Sent: Wednesday, January 16, 2008 3:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: INCLUDE/EXCLUDE

TSMer's

 

  I have excluded a number of files in the .opt file for a server, yet they are 
still coming up in the activity log.  Can someone shed some light on this?

 

The B/A GUI states that these particular files are excluded.

 

Server Level 5.4.1.1

Client Level 5.3.0.5

 

Thank you in advance

 

James

 

Activity Log 

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_334.dat': the object is in use by 
another process (SESSION: 23442)

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_390.dat': the object is in use by 
another process (SESSION: 23442)

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_528.dat': the object is in use by 
another process (SESSION: 23442)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\msdbdata.mdf': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\msdblog.ldf': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NCS_CONVERSION_Data.MDF': the object is in 
use by another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NCS_CONVERSION_Log.LDF': the object is in 
use by another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_Data.MDF': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_LIFELINE_Data.MDF': the object is in use 
by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_LIFELINE_Log.LDF': the object is in use 
by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_Log.LDF': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\pa_usf.ldf': the object is in use by another 
process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\pa_usf.mdf': the object is in use by another 
process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\QuestWorkDatabase_Data.mdf': the object is 
in use by another process (SESSION: 2

Re: INCLUDE/EXCLUDE

[Hart, Charles A]

Log on to your client using the cmd line, type q inclexcl   This will tell you 
what the client is actually trying to process...  

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lepre, 
James
Sent: Wednesday, January 16, 2008 3:10 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE/EXCLUDE

Exclude "*:\microsoft uam volume\...\*"
Exclude "*:\microsoft uam volume\...\*.*"
Exclude "*:\...\EA DATA. SF"
Exclude *:\...\pagefile.sys
Exclude *:\IBMBIO.COM
Exclude *:\IBMDOS.COM
Exclude *:\MSDOS.SYS
Exclude *:\IO.SYS
Exclude *:\...\SYSTEM32\CONFIG\...\*
Exclude *:\...\SYSTEM32\CONFIG\...\*.*
Exclude *:\...\Profiles\...\ntuser.dat* 
Exclude *:\...\system32\Perflib*.dat
Exclude.dir *:\...\system32\wins
Exclude.dir *:\...\system32\LServer
Exclude.dir *:\...\system32\dhcp
Exclude.dir *:\...\system32\config
Exclude.dir *:\...\ntfrs\jet
Exclude.dir *:\...\ntds
Exclude.dir "*:\System Volume Information"
Exclude.dir "*:\...\Temporary Internet Files"
Exclude.dir *:\Recycled
Exclude.dir *:\Recycler
Exclude.dir "d:\MSSQL2000\MSSQL\Data\*.*"
EXCLUDE.DIR "*:\...\temp"
EXCLUDE.DIR "*:\...\$*$"
EXCLUDE.DIR "*:\...\tivoli" 
EXCLUDE.BACKUP "*:\...\*.ldf"
EXCLUDE.BACKUP "*:\...\*.mdf"
EXCLUDE.BACKUP "*:\...\*.ndf"
EXCLUDE.BACKUP "*:\Documents and Settings\...\*.DAT" 
EXCLUDE.BACKUP "*:\Documents and Settings\...\*.DAT.log"
EXCLUDE.BACKUP "*:\WebTools\...\*.000"
EXCLUDE.BACKUP "*:\Inetpub\...\*.000"
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ochs, Duane
Sent: Wednesday, January 16, 2008 4:07 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE/EXCLUDE

Send a capture of the excludes.
Did you restart the scheduler service after making the additions ?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lepre, 
James
Sent: Wednesday, January 16, 2008 3:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: INCLUDE/EXCLUDE

TSMer's

 

  I have excluded a number of files in the .opt file for a server, yet they are 
still coming up in the activity log.  Can someone shed some light on this?

 

The B/A GUI states that these particular files are excluded.

 

Server Level 5.4.1.1

Client Level 5.3.0.5

 

Thank you in advance

 

James

 

Activity Log 

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_334.dat': the object is in use by 
another process (SESSION: 23442)

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_390.dat': the object is in use by 
another process (SESSION: 23442)

1/15/08 1:05:39 AM EST

ANE4987E (Session: 23442, Node: NSISQL1) Error processing
'\\nsisql1\c$\WINNT\system32\Perflib_Perfdata_528.dat': the object is in use by 
another process (SESSION: 23442)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\msdbdata.mdf': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\msdblog.ldf': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NCS_CONVERSION_Data.MDF': the object is in 
use by another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NCS_CONVERSION_Log.LDF': the object is in 
use by another process (SESSION: 23450)

1/15/08 1:06:09 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_Data.MDF': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_LIFELINE_Data.MDF': the object is in use 
by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_LIFELINE_Log.LDF': the object is in use 
by another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\NSI_Log.LDF': the object is in use by 
another process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Node: NSISQL1) Error processing
'\\nsisql1\d$\MSSQL2000\MSSQL\Data\pa_usf.ldf': the object is in use by another 
process (SESSION: 23450)

1/15/08 1:06:10 AM EST

ANE4987E (Session: 23450, Nod

Re: INCLUDE/EXCLUDE

[Lepre, James]

Here is the output from the client


Node Name: NSISQL1
Session established with server TIVOLIHQ1: Windows
  Server Version 5, Release 4, Level 1.1
  Data compression forced off by the server
  Server date/time: 01/16/2008 16:56:54  Last access: 01/16/2008 16:09:28

tsm> q inclexcl
*** FILE INCLUDE/EXCLUDE ***
Mode Function  Pattern (match from top down)  Source File
 - -- -
Excl Directory C:\adsm.sysOperating System
Excl Directory *\...\tivoli   dsm.opt
Excl Directory *\...\$*$  dsm.opt
Excl Directory *\...\temp dsm.opt
Excl Directory d:\MSSQL2000\MSSQL\Data\*.*dsm.opt
Excl Directory *\Recycler dsm.opt
Excl Directory *\Recycled dsm.opt
Excl Directory *\...\Temporary Internet Files dsm.opt
Excl Directory *\System Volume Informationdsm.opt
Excl Directory *\...\ntds dsm.opt
Excl Directory *\...\ntfrs\jetdsm.opt
Excl Directory *\...\system32\config  dsm.opt
Excl Directory *\...\system32\dhcpdsm.opt
Excl Directory *\...\system32\LServer dsm.opt
Excl Directory *\...\system32\winsdsm.opt
Exclude All   C:\WINNT\system32\NtmsData\...\* Operating System
Exclude All   C:\WINNT\system32\inetsrv\metabase.xml Operating System
Exclude All   C:\WINNT\system32\inetsrv\metabase.bin Operating System
Exclude All   C:\WINNT\system32\inetsrv\mbschema.xml Operating System
Exclude All   C:\WINNT\System32\DTCLog\MSDTC.LOG Operating System
Exclude All   C:\WINNT\system32\config\system.log Operating System
Exclude All   C:\WINNT\system32\config\system.alt Operating System
Exclude All   C:\WINNT\system32\config\system Operating System
Exclude All   C:\WINNT\system32\config\software.log Operating System
Exclude All   C:\WINNT\system32\config\software Operating System
Exclude All   C:\WINNT\system32\config\security.log Operating System
Exclude All   C:\WINNT\system32\config\security Operating System
Exclude All   C:\WINNT\system32\config\sam.log Operating System
Exclude All   C:\WINNT\system32\config\sam   Operating System
Exclude All   C:\WINNT\system32\config\default.log Operating System
Exclude All   C:\WINNT\system32\config\default Operating System
Exclude All   C:\WINNT\schedlgu.txt  Operating System
Exclude All   C:\WINNT\registration\*.clbOperating System
Exclude All   C:\WINNT\netlogon.chg  Operating System
Exclude All   C:\WINNT\debug\*   Operating System
Exclude All   C:\WINNT\csc\...\* Operating System
Exclude All   C:\DOCUME~1\ADMINI~1.NSI\LOCALS~1\Temp\a\...\* Operating Syst
m
Exclude All   C:\Documents and Settings\administrator.NSISQL1\...\index.dat
Operating System
Exclude All   *\Pagefile.sys Operating System
Exclude All   *\hiberfil.sys Operating System
Exclude All   *\...\*.crmlog Operating System
Exclude Backup*\Inetpub\...\*.000dsm.opt
Exclude Backup*\WebTools\...\*.000   dsm.opt
Exclude Backup*\Documents and Settings\...\*.DAT.log dsm.opt
Exclude Backup*\Documents and Settings\...\*.DAT dsm.opt
Exclude Backup*\...\*.ndfdsm.opt
Exclude Backup*\...\*.mdfdsm.opt
Exclude Backup*\...\*.ldfdsm.opt
Exclude All   *\...\system32\Perflib*.datdsm.opt
Exclude All   *\...\Profiles\...\ntuser.dat* dsm.opt
Exclude All   *\...\SYSTEM32\CONFIG\...\*.*  dsm.opt
Exclude All   *\...\SYSTEM32\CONFIG\...\*dsm.opt
Exclude All   *\IO.SYS   dsm.opt
Exclude All   *\MSDOS.SYSdsm.opt
Exclude All   *\IBMDOS.COM   dsm.opt
Exclude All   *\IBMBIO.COM   dsm.opt
Exclude All   *\...\pagefile.sys dsm.opt
Exclude All   *\...\EA DATA. SF  dsm.opt
Exclude All   *\microsoft uam volume\...\*.* dsm.opt
Exclude All   *\microsoft uam volume\...\*   dsm.opt
Include All   *\...\*dsm.opt

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Hart, 
Charles A
Sent: Wednesday, January 16, 2008 4:37 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE/EXCLUDE

Log on to your client using the cmd line, type q inclexcl   This will tell you 
what the client is actually trying to process...  

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lepre, 
James
Sent: Wednesday, January 16, 2008 3:10 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE/EXCLUDE

Exclude "*:\microsoft uam volume\...\*"
Exclude "*:\microsoft uam volume\...\*.*"
Exclude "*:\...\EA DATA. SF"
Exclude *:\...\pagefile.sys
Exclude *:\IBMBIO.

Re: INCLUDE/EXCLUDE

[Richard Sims]

James -

I'm not a Windows guru, but one thing apparent from your Exclude
specifications is that

   Exclude.dir "d:\MSSQL2000\MSSQL\Data\*.*"

doesn't make sense for what I perceive you are trying to achieve:
that's a filename pattern on the end, for legacy "8.3" filenames,
with a dot in them, whereas Exclude.Dir is supposed to simply name a
single directory or a wildcard-identified set of directories.

   Richard Sims a DOS survivor

Re: INCLUDE/EXCLUDE

[Lepre, James]

Ok that is true thank you.. However I also have 

EXCLUDE.BACKUP "*:\...\*.ldf"
EXCLUDE.BACKUP "*:\...\*.mdf"
EXCLUDE.BACKUP "*:\...\*.ndf"

And these extensions are still showing up in the activity log as open
files that are trying to be backed up.. Any thoughts
-Original Message-- ---
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: Wednesday, January 16, 2008 7:27 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] INCLUDE/EXCLUDE

James -

I'm not a Windows guru, but one thing apparent from your Exclude
specifications is that

Exclude.dir "d:\MSSQL2000\MSSQL\Data\*.*"

doesn't make sense for what I perceive you are trying to achieve:
that's a filename pattern on the end, for legacy "8.3" filenames,
with a dot in them, whereas Exclude.Dir is supposed to simply name a
single directory or a wildcard-identified set of directories.

Richard Sims a DOS survivor

  
  
---
Confidentiality Notice: The information in this e-mail and any attachments 
thereto is intended for the named recipient(s) only.  This e-mail, including 
any attachments, may contain information that is privileged and confidential  
and subject to legal restrictions and penalties regarding its unauthorized 
disclosure or other use.  If you are not the intended recipient, you are hereby 
notified that any disclosure, copying, distribution, or the taking of any 
action or inaction in reliance on the contents of this e-mail and any of its 
attachments is STRICTLY PROHIBITED.  If you have received this e-mail in error, 
please immediately notify the sender via return e-mail; delete this e-mail and 
all attachments from your e-mail  system and your computer system and network; 
and destroy any paper copies you may have in your possession. Thank you for 
your cooperation.

Re: INCLUDE/EXCLUDE

[Malith G. Fernando]

Hi admin,

Pls exclude from  this mailing list asap.


Thank You

Malith Fernando

Re: INCLUDE/EXCLUDE

[Richard Sims]

On Jan 16, 2008, at 7:42 PM, Lepre, James wrote:


Ok that is true thank you.. However I also have

EXCLUDE.BACKUP "*:\...\*.ldf"
EXCLUDE.BACKUP "*:\...\*.mdf"
EXCLUDE.BACKUP "*:\...\*.ndf"

And these extensions are still showing up in the activity log as open
files that are trying to be backed up.. Any thoughts



James -

Unless there is something beyond my ken going on, I would have to
conclude that either the operation being performed is not Backup, or
that the process performing what we perceive to be a Backup is not
using the expected options file to pick up those Excludes.  I would
recommend verifying whether the issue persists in a manual backup
that was preceded by a verifying 'dsmc q inclexcl'.  You could pursue
a client trace to further narrow down the problem.  Consider also
boosting the maintenance level of that client, which is currently
very early 5.3.

If this problem started happening at a point in time, and was not
happening before, look into what system changes and/or service
restarts coincidentally occurred.

   Richard Sims

Re: include/exclude

[Sal Mangiapane]

goc wrote:
hi all,
a short one
in
exclude "*:/.../nohup.out*"
what does *: mean ?
and then with dsmc q inclexcl
*** FILE INCLUDE/EXCLUDE ***
Mode Function  Pattern (match from top down)  Source File
 - -- -
No exclude filespace statements defined.
No exclude directory statements defined.
Exclude All   /.../*:/.../nohup.out*
/usr/local/etc/inclexcl.file
No DFS include/exclude statements defined.

thanks in advance ?


The : is the drive delimiter.
The *: means any drive.
But, nohup.out is probably a file on a UNIX based computer and drive
letters don't really make sense.
Hope this helps,

Re: include/exclude

[Jansson Tommy]

Yes, this is done from the command line. There's a tool called dsmc
which is basically the command line version of the backup/archive
client.
This is how it's done (on a Windows client):

cd "c:\program files\tivoli\tsm\baclient"   (or whereever you installed
the TSM client)
dsmc query inclexcl

Now you should see a list of objects included and excluded. Notice that
in the Source File column it's stated from where objects were included
or excluded (for example Operating System or dsm.opt).

Regards, Tommy.


-Original Message-
From: Moses Show [mailto:[EMAIL PROTECTED] 
Sent: den 11 maj 2004 11:08
To: [EMAIL PROTECTED]
Subject: include/exclude


Hi,
Am fairly new to TSM but when reading through some of the
literature I have it gives advice and commands on how to view objects
which are included or excluded from a backup. The command offered is
dsmc query inclexcl which I presume is used on the command line of the
client or server. When I try this from the BAClient Gui however this
command does not seem to work, even when missing out the dsmc from the
beginning of the command. Can somebody help me sort this out as I need
to try and find out what files should be  being include/excluded,
without having to keep searching the options files.

Regards

==
This communication, together with any attachments hereto or links
contained herein, is for the sole use of the intended recipient(s) and
may contain information that is confidential or legally protected. If
you are not the intended recipient, you are hereby notified that any
review, disclosure, copying, dissemination, distribution or use of this
communication is STRICTLY PROHIBITED.  If you have received this
communication in error, please notify the sender immediately by return
e-mail message and delete the original and all copies of the
communication, along with any attachments hereto or links herein, from
your system.

==
The St. Paul Travelers e-mail system  made this annotation on
05/11/2004 05:03:49 AM.

Re: include/exclude

[Stapleton, Mark]

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
Behalf Of goc
>how to include content of /usr/local/cvs/ directory and 
>subdirs into one
>management class when doing incremental backups ?
>
>is this enough ?
>
>include.backup /usr/local/cvs/* MC_CVS

The syntax for your include line should be

include /usr/local/cvs/.../*  MC_CVS

in order to back up all subdirectories using the desired management
class.

--
Mark Stapleton

Re: include/exclude

[goc]

thanks

- Original Message -
From: "Stapleton, Mark" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 02, 2004 4:57 PM
Subject: Re: include/exclude


From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of goc
>how to include content of /usr/local/cvs/ directory and
>subdirs into one
>management class when doing incremental backups ?
>
>is this enough ?
>
>include.backup /usr/local/cvs/* MC_CVS

The syntax for your include line should be

include /usr/local/cvs/.../*  MC_CVS

in order to back up all subdirectories using the desired management
class.

--
Mark Stapleton

Re: include/exclude

[Luc Beaudoin]

hi ,,
what is the OS ?





David E Ehresman <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
2004-08-11 12:54 PM
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
    Subject:include/exclude


I can seem to get my head wrapped around include/exclude.  What set of
statemetns would allow me to backup /web and /home directories but
nothing else.

Re: include/exclude

[David E Ehresman]

The client is a Linux box.

>>> [EMAIL PROTECTED] 8/11/2004 12:55:40 PM >>>
hi ,,
what is the OS ?





David E Ehresman <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
2004-08-11 12:54 PM
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
    cc:
Subject:include/exclude


I can seem to get my head wrapped around include/exclude.  What set of
statemetns would allow me to backup /web and /home directories but
nothing else.

Re: include/exclude

[Stapleton, Mark]

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
Behalf Of David E Ehresman
>I can seem to get my head wrapped around include/exclude.  What set of
>statemetns would allow me to backup /web and /home directories but
>nothing else.

Put the following lines *in the order they're written*... 

exclude /.../*
include /web/.../*
include /home/.../*

Includes and excludes are executed from the bottom of the list upward.

--
Mark Stapleton

include/exclude statements

[Richard Mochnaczewski]

Hi,

I'm setting up my include/exclude statements dsm.sys file on all my AIX
servers, and I'm running into problem with the excludes. I want to exclude
the following filesystems :

/
/usr
/var
/tmp

I'm using the following statements in my dsm.sys :

exclude.dir "/"
exclude.dir "/usr"
exclude.dir "/var"
exclude.dir "/tmp"

followed by whatever other filesystems I want excluded . The four I've
pointed out are are constantly being backed up. I'm running version TSM
5.2.2 on AIX 5.2 server. All my clients are 5.2.2. Any ideas ?

Rich




This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations. Any distribution, use or copying
of this e-mail or the information it contains by other than an intended
recipient is unauthorized. If you received this e-mail in error, please
advise me (by return e-mail or otherwise) immediately. 

Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux
droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou
copie de ce message ou des renseignements qu'il contient par une personne
autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez
ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de
courriel ou par un autre moyen.

Include/Exclude Question

[Jones, Kelli]

Server:
TSM 5.1.7.0
AIX 5.1

Client:
NT 4.0

We need to set up include/exclude statements for a node that has drives C thru M.  We 
need to back up only C, G and J.  How do I set up options file to back up only those 
drives (and everything on them minus various system file) and nothing on the other 
drives. 

Thanks,
Kelli Jones
[EMAIL PROTECTED]   
Chesterfield County IST 
804-748-1951

include exclude list

[Hashim, Shukrie BSP-ISM/116]

hi all,

I would like to know exactly ... what I should type if I want to exclude any directory 
that is named ".snapshot" and all the files in it of course for example I have these 
directory and filesystems (Unix system)

/apps/.snapshot/
/.snapshot/
/local/apps/.snapshot/
/local/long/short/down/.snapshot/

so I want to exclude all the directories and files that is in the .snapshot directory. 
can I do it using 

exclude.fs /.../.snapshot/.../*   < will this work for all subdirectories ?

or 

exclude.dir /*/*/.snapshot/.../*   < will this only go down to 2 level of 
subdirectory ?

I really need to know how to exclude this directory ... as long as TSM sees it's 
.snapshot it will skip that directory .. and exclude it from the backup ... !

Regards
Shukrie

Re: Include/Exclude

[David Longo]

Yes, I saw this a few days ago.  Don't know what it is offhand, it is indeed working 
the opposite of what it is supposed to.  Do you have any Client OPtions set for this 
node?  What verions of *SM are you runing?  What version of NW (5.0, 5.1)?  Do you 
have any other NW clients?  

Perhaps show us more of your dsm.opt file.


David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5525
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 05/22/01 10:30AM >>>
I had posted this a few days ago, but I am not sure if anyone got it (my
Internet email gateway has not been behaving) . . .


Hello, all!

I have a clarification question about include/exclude statements.  One of
our Netware guru's pointed this out to me.  Here's what I have (NetWare 5)
in my dsm.opt file:

EXCLUDE *:\...\*.*
INCLUDE DATA:\USERS\...\*.*

When I perform an incremental backup of the node, the system backs up
everything on the system.  If on the other had I do the following:

INCLUDE DATA:\USERS\...\*.*
EXCLUDE *:\...\*.*

The system does not backup anything except the files in the
data:\users\...\*.* directories.

It seems the system is doing just the opposite of what it's supposed to
since these statements are supposed to the processed from the bottom
statement up. [See excerpt from Tivoli Storage Manager for NetWare Using
the Backup-Archive Client manual.]

Excerpt:
These options are checked from the bottom of the include-exclude list up,
until a match is found. If a match is found, the processing stops and
checks whether the option is include or exclude. If the option is include,
the file is backed up. If the option is exclude, the file is not backed
up.

Has something changed?  Can someone explain this?

TIA

Mahesh



"MMS " made the following
 annotations on 05/22/01 10:43:28
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==

Re: Include/Exclude

[Kevin Kinder]

Mahesh,

I'm not sure if this will help, but we had some problems getting TSM to recognize and 
execute out incl/excl statements correctly in the NetWare enivronment.  Tivoli tech 
suppor recommended that we use full paths in our incl/excl statements.  Here's a 
sample of the statements we are using on NW 5.x servers:

EXCLUDE servername\*:/.../vol$log.err
EXCLUDE servername*:/.../tts$log.err
EXCLUDE servername*:/.../sys$log.err
EXCLUDE servername*:/.../events.log
EXCLUDE servername*:/.../secaudit.log
EXCLUDE servername*:/.../system.log
EXCLUDE servername*:/.../net$obj.sys
EXCLUDE servername*:/.../net$prop.sys
EXCLUDE servername*:/.../net$val.sys
EXCLUDE servername\sys:system/cmaster.dba
EXCLUDE servername\sys:system/btrieve.trn
EXCLUDE servername\sys:system/tsa/tsa$temp.*
EXCLUDE servername\sys:system/tsa/err$log.*
EXCLUDE servername\sys:system/tsa/skip$log.*
EXCLUDE servername\sys:system/tsa/err$hst.*
EXCLUDE servername\sys:_SWAP_.MEM
exclude.dir servername\sys:\queues

Note the exclude.dir statement - as noted in another reply, this should specifically 
remove scanning of the specified dirs and all other dirs.

When we used this format, the odd behavior of these statements in NetWare ceased - at 
least from our perspective.  Hope that helps.


Kevin Kinder
558-8844

>>> Mahesh Tailor <[EMAIL PROTECTED]> 5/22/01 10:30:05 AM >>>
I had posted this a few days ago, but I am not sure if anyone got it (my
Internet email gateway has not been behaving) . . .


Hello, all!

I have a clarification question about include/exclude statements.  One of
our Netware guru's pointed this out to me.  Here's what I have (NetWare 5)
in my dsm.opt file:

EXCLUDE *:\...\*.*
INCLUDE DATA:\USERS\...\*.*

When I perform an incremental backup of the node, the system backs up
everything on the system.  If on the other had I do the following:

INCLUDE DATA:\USERS\...\*.*
EXCLUDE *:\...\*.*

The system does not backup anything except the files in the
data:\users\...\*.* directories.

It seems the system is doing just the opposite of what it's supposed to
since these statements are supposed to the processed from the bottom
statement up. [See excerpt from Tivoli Storage Manager for NetWare Using
the Backup-Archive Client manual.]

Excerpt:
These options are checked from the bottom of the include-exclude list up,
until a match is found. If a match is found, the processing stops and
checks whether the option is include or exclude. If the option is include,
the file is backed up. If the option is exclude, the file is not backed
up.

Has something changed?  Can someone explain this?

TIA

Mahesh

Re: Include/Exclude

[Prather, Wanda]

I don't know why you are having the overall problem, but there is also a
problem in your specification.

Periods are treated just like any other character, not a wild card.
So when you specify:
INCLUDE DATA:\USERS\...\*.*

you are telling TSM to match filenames that have at least one . in the name.

If you want to include everything, you need:
INCLUDE DATA:\USERS\...\*

-Original Message-
From: Mahesh Tailor [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 22, 2001 10:30 AM
To: [EMAIL PROTECTED]
Subject: Include/Exclude


I had posted this a few days ago, but I am not sure if anyone got it (my
Internet email gateway has not been behaving) . . .


Hello, all!

I have a clarification question about include/exclude statements.  One of
our Netware guru's pointed this out to me.  Here's what I have (NetWare 5)
in my dsm.opt file:

EXCLUDE *:\...\*.*
INCLUDE DATA:\USERS\...\*.*

When I perform an incremental backup of the node, the system backs up
everything on the system.  If on the other had I do the following:

INCLUDE DATA:\USERS\...\*.*
EXCLUDE *:\...\*.*

The system does not backup anything except the files in the
data:\users\...\*.* directories.

It seems the system is doing just the opposite of what it's supposed to
since these statements are supposed to the processed from the bottom
statement up. [See excerpt from Tivoli Storage Manager for NetWare Using
the Backup-Archive Client manual.]

Excerpt:
These options are checked from the bottom of the include-exclude list up,
until a match is found. If a match is found, the processing stops and
checks whether the option is include or exclude. If the option is include,
the file is backed up. If the option is exclude, the file is not backed
up.

Has something changed?  Can someone explain this?

TIA

Mahesh

INCLUDE/EXCLUDE STATEMENT

[Gerardo Zapata]

Hello,

I have a question about the utilization of the include exclude list.
I have specified the following statments in the list:

include /t/tuxedo/bialog/.../ politicy2
include /t/tuxedo/procesos/.../ politicy2
include /t/.../* policy1

The intention is to backup /t/.../* filesystem using the rules specified in
the policy1 management class (general policy for the filesystem.
And apply policy2 management class rules to the two specific directories.
We have a schdeuler that launches the /t/tuxedo/bialog and /t/tuxedo/procesos
backups (includeing subdirectories) and another scheduler three hours later
that launches the backup of the /t/* filesystem (including subdirectories).

Is this combination valid?
Won't I have binding/rebinding problems in the future?

Thanks in advance

Regards,
Gerardo Zapata
IT Specialist
IBM Mexico
(52)-5270-5889
[EMAIL PROTECTED]


Get free email and a permanent address at http://www.netaddress.com/?N=1

Include Exclude Problem

[John Freeman]

Fellow TSM's

As a TSM newbie I am having some difficulty configuring an incl excl list.

(Windows Client 4.1.3 to Windows Server 4.1.0)

I want to backup a single directory on the D drive of a client and want to exclude 
everything else on both C and D drives.

My incl_excl file looks as follows:

include "d:\data\*"
exclude "c:\*"

I have also tried the following:

include "d:\data\*"
exclude "*"

The first combination backs up everything and the second one backs up nothing.

Some help would be greatly appreciated.

Rgds
John

Include/exclude issue ?

[Justin Case]

I need to exclude oradata files from the OS incremental backup "exclude.dir
/exlibris1/oradat*" where they lice but I need
to backup (include some *.archive files in same path but in subdirectories)

I have included the archive path /exlibris2/oradata/aleph1/arch/ but it
still thinks that they are excluded with the inclexcl statements I have
listed below,
Does any one see what would help us to exclude what we need to but include
what we need to backup in the sub-path ?


INCLEXCL file
exclude.dir /exlibris1/oradat*
exclude.dir /exlibris2/oradat*
include /exlibris2/oradata/aleph1/arch/
exclude.dir /var/run
exclude.dir /etc/mnttab
exclude.dir /proc
exclude.dir /backup


I am not seeing something
Thanks for any help.

Justin

Re: Include/Exclude

[Andrew Raibeck]

Patricia,

TSM uses the system registry for most of the operating system excludes.
FYI, the registry key is
HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup. TSM
just reads from this key; it does not write to it. The key entries are
established by Windows, and in some cases, by other products, too.

adsm.sys is an exception: we implicitly exclude it, and we show it as
excluded by the OS, but in fact, that exclude is done by TSM, and you
won't see it in the FilesNotToBackup key.

Note that adsm.sys is automatically included in the system object backup.
The excludes/includes are for regular file backup only, and thus do not
apply to system object. So if you back up the system object, you'll see
adsm.sys getting backed up as a part of that operation.

Regards,

Andy

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

IBM Tivoli Storage Manager support web page:
http://www-306.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 02/15/2006
13:11:41:

> I'm wondering how the "operating system" excludes get set.  Below is a
> test screen capture of a w2k server, opening up the dsmc.exe and typing
> in q inclexcl.
> I wanted to INCLUDE the C:\adsm.sys..but how do I update the
> operating system excludes
>
>
>
> tsm> q inclexcl
> *** FILE INCLUDE/EXCLUDE ***
> Mode Function  Pattern (match from top down)  Source File
>  - -- -
> 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
> Excl Directory *\...\ntds dsm.opt
> Excl Directory *\...\ntfrs\jetdsm.opt
> Excl Directory *\...\system32\config  dsm.opt
> Excl Directory *\...\system32\dhcpdsm.opt
> Excl Directory *\...\system32\LServer dsm.opt
> Excl Directory *\...\system32\winsdsm.opt
> Exclude All   C:\WINNT\system32\NtmsData\...\* Operating System
> Exclude All   C:\WINNT\system32\inetsrv\metabase.xml Operating
> System
> Exclude All   C:\WINNT\system32\inetsrv\metabase.bin Operating
> System
> Exclude All   C:\WINNT\system32\inetsrv\mbschema.xml Operating
> System
> Exclude All   C:\WINNT\System32\DtcLog\MSDTC.LOG Operating System

include/exclude options

[Gerald Wichmann]

Howcome on some systems I can throw lots of options in the .opt file but
more recently I’ve noticed some systems I can’t. specifically I have two AIX
4.3.3 boxes running TSM 3.7.2 and 3.7.0.. Initially I put my include/exclude
statements in the dsm.opt file but when I run dsmc it complains that it’s an
invalid option. The same happens if I put schedlogretention or
passwordaccess or ANYTHING it seems except “servername”..

Now I KNOW I have systems (NT4 for example) where I have all these things in
dsm.opt. This is seriously confusing.. What is going on here?

Specifically we’d like to run a second scheduler on this one particular AIX
4.3.3 box where each scheduler that’s running has it’s own nodename and
include/exclude statements. It seems I can’t do it even though I can tell
dsmc to run using a different options file, I CANT have different info in
that options file. This seems contrary to what the manuals say and some of
my past experiences.

Gerald Wichmann
RS Engineer
Sansia System Solutions
408-844-8893 work
408-844-9801 fax

Include/Exclude list

[Jim Kirkman]

Hey again,

We've been forced into the workstation backup business and I'm trying to
come up with as restrictive an options file as we can get away with.

The goal is to restrict backups to personal documents and Netscape
browser and email settings (well the real goal is to have folks use the
existing server to store files but...). We've been playing with various
include and exclude arrangements and have noticed some interesting
behavior. We can get it down to where we've got the desired files and
folders backed up using the list below:

Include "C:\Documents & Settings\XXX\My Documents\XXX\*.*"
Include "C:\Documents & Settings\XXX\My Documents\XXX\*"
Include "C:\Documents & Settings\XXX\My Documents\XXX\...\*"
Include "C:\Documents & Settings\XXX\My Documents\XXX\...\*.*"
Include "C:\Program Files\Netscape\Users\default\*.*"
Include "C:\Program Files\Netscape\Users\default\*"
Include "C:\Program Files\Netscape\Users\default\...\*"
Include "C:\Program Files\Netscape\Users\default\...\*.*"
Exclude.dir "C:\Program Files\Netscape\users\default\cache"

Now, if I put Exclude "?:*" at the top of this list, no other files on
the disk are backed up but the directory structure is. Not terrible from
a space standpoint but could be pretty confusing for a user trying to
restore something. If, however I make the top (last) statement
Exclude.dir "?:*" then nothing but files at the root of C: are backup up
!? In other words it overrides all the include statements below it,
what's up with that?

Any suggestions other than a whole slew of exclude.dir statements? What
I really need is a global exclude after processing the includes.

This is client level 4.1.1_16 backing up to ADSM 3.1.2.50 on OS\390 2.6

thanks,

--
Jim Kirkman
AIS - Systems
UNC-Chapel Hill
966-5884

Re: include/exclude

[Joel Fuhrman]

> (1) If I change the include/exclude file, when are the changes "read"?  Do I
> have to kill and then restart the daemon (dsmc)?

The include/exclude file is read when the program starts thus it must be
restarted after each change.

> (2) Is there any way to test my include/exclude statements using the
> backup/restore GUI?

Yes, the GUI marks excluded files with a red x and excluded file systems are
not shown in the list of files.  Again, you must restart the GUI each time
you change the include/exclude file.

Re: include/exclude

[Richard Sims]

> (2) Is there any way to test my include/exclude statements using the
> backup/restore GUI?

There is also 'dsmc show inclexcl'.  The "show" commands remain undocumented and
officially unsupported, which is a shame given that this command is vital to
making sense of the combined include-exclude specs in the client options file
and the server cloptset, which has been seen to frequently confuse customers
who look at just the client options file and wonder why include-exclude is not
doing what they expect.
Richard Sims, BU

Include-Exclude Survey

[Lori Simcox]

I'd like to query this forum about the usability of TSM's include-exclude
list to determine how we might improve upon this feature of the product.

1. What do you like about TSM's include-exclude functionality?  What are
some problems/difficulties you have run into using the TSM include-exclude
functionality?
2. How are you using include-exclude lists?  Do you set client option sets
on the TSM Server for your clients?  Do you let users create
include-exclude lists on the TSM Client?  Or do you allow a combination of
both?  What are the reasons for your strategy?
3.  Includes/excludes set up on the TSM Server via client options sets take
precedence over include/excludes set in the client's options file.  If you
set the include-exclude list via the TSM Server, do you want your TSM
Clients to be able to add their own includes/excludes at all?
4. TSM's include-exclude functionality also allows you to bind management
classes, indicate files to encrypt/compress, set options for image backup,
among others.  How do you use these options in your include-exclude list?
5. How do you create your include-exclude lists?  Do you ever use the TSM
Client GUI preferences editor to set up your include-exclude list, and if
so, what do you think of it?
6.  If you had a wizard on the TSM Client to help you set up your
include-exclude strategy, would it help?  If so, what would you like it to
do?
7.  Do you need to know and can you easily tell which objects are excluded
using the TSM Client GUI?  Would more information be helpful?
8.  Do you have a strategy for binding files to management classes?  How
usable is TSM as far as helping you do that?

To avoid cluttering up this forum, you may send responses to
[EMAIL PROTECTED]

Thanks in advance,
Lori Simcox
TSM Client Development

include/exclude question

[Rainer Holzinger]

Hi all,

I'm  trying  to  exclude  a  group  of filesystems from backup but not from
archive.  But I don't have success. It seems that 'exclude.fs' is excluding
the filesystems for archive processing too. I'm trying to do that with ITSM
HPUX  client  version  5.2.2.0.  Are  there  any design changes within ITSM
client  version  5.2.2.0?  I have for example noticed that every exclude.fs
statement  is  now  mentioned with a warning message (ANS1050W File space '
filespace_name'  skipped: excluded by EXCLUDE.FS option'). I don't see that
as an error, it's just the way I would like to have it.

My include/exclude list is as follows:

  include/.../* mc00a1-hpux
  exclude.fs /cdrom
  *  - exclude SAP R/3 file systems and directories
  --
  *  -  backed  up  by  TDP for ERP (Oracle) or not
  needed ---
  exclude.fs   /oracle/???/mirrlogA
  exclude.fs   /oracle/???/mirrlogB
  exclude.fs/oracle/???/oraarch
  exclude.fs   /oracle/???/origlogA
  exclude.fs   /oracle/???/origlogB
  exclude.fs   /oracle/???/sapdata*
  include.archive/oracle/???/sapdata*/*
  exclude.fs   /oracle/???/sapreorg
  exclude.dir   /oracle/???/saparch
  exclude.dir /oracle/???/sapbackup
  exclude  /usr/sap/???/DVEBMGS??/data/PAGFIL??
  exclude  /usr/sap/???/DVEBMGS??/data/ROLLFL??
  *  -  exclude  files  you  do  not need to backup
  ---
  exclude.dir  /dev
  exclude.dir   /.../lost+found
  exclude.file/.../core

All  '/oracle/???/sapdata*'  filesystems  should  be  excluded  from backup
processing but archiving these should be possible.
Can someone point me to the right direction?

Thanks and best regards,

   (Embedded  Rainer Holzinger
  image moved Solution Specialist, Data Backup &
   to file:   Data Center Facilities
 pic03183.gif)UPM-Kymmene
  IT Services and e-Business
  Georg-Haindl-Str. 5, D-86153
  Augsburg
  Tel. +49 821 3109 590
  Fax. +49 821 3109 115
  Mobile +49 170 4037 616
  [EMAIL PROTECTED]




<>

include/exclude question

[Rainer Holzinger]

Hi all,

I'm  trying  to  exclude  a  group  of filesystems from backup but not from
archive.  But I don't have success. It seems that 'exclude.fs' is excluding
the filesystems for archive processing too. I'm trying to do that with ITSM
HPUX  client  version  5.2.2.0.  Are  there  any design changes within ITSM
client  version  5.2.2.0?  I have for example noticed that every exclude.fs
statement  is  now  mentioned with a warning message (ANS1050W File space '
filespace_name'  skipped: excluded by EXCLUDE.FS option'). I don't see that
as an error, it's just the way I would like to have it.

My include/exclude list is as follows:

  include/.../* mc00a1-hpux
  exclude.fs /cdrom
  *  - exclude SAP R/3 file systems and directories
  --
  *  -  backed  up  by  TDP for ERP (Oracle) or not
  needed ---
  exclude.fs   /oracle/???/mirrlogA
  exclude.fs   /oracle/???/mirrlogB
  exclude.fs/oracle/???/oraarch
  exclude.fs   /oracle/???/origlogA
  exclude.fs   /oracle/???/origlogB
  exclude.fs   /oracle/???/sapdata*
  include.archive/oracle/???/sapdata*/*
  exclude.fs   /oracle/???/sapreorg
  exclude.dir   /oracle/???/saparch
  exclude.dir /oracle/???/sapbackup
  exclude  /usr/sap/???/DVEBMGS??/data/PAGFIL??
  exclude  /usr/sap/???/DVEBMGS??/data/ROLLFL??
  *  -  exclude  files  you  do  not need to backup
  ---
  exclude.dir  /dev
  exclude.dir   /.../lost+found
  exclude.file/.../core

All  '/oracle/???/sapdata*'  filesystems  should  be  excluded  from backup
processing but archiving these should be possible.
Can someone point me to the right direction?

Thanks and best regards,

   (Embedded  Rainer Holzinger
  image moved Solution Specialist, Data Backup &
   to file:   Data Center Facilities
 pic25103.gif)UPM-Kymmene
  IT Services and e-Business
  Georg-Haindl-Str. 5, D-86153
  Augsburg
  Tel. +49 821 3109 590
  Fax. +49 821 3109 115
  Mobile +49 170 4037 616
  [EMAIL PROTECTED]




<>

Include/Exclude issue

[Jelf, Jim]

I have added exclude statements in my dsm.opt file to exclude the dat files
in my Windows2000 Profiles. The syntax of my exclude statement is:



EXCLUDE "d:\...\*.dat"



When I open the GUI on the client and look at the files under the backup
selection, it shows that the files are excluded from backup.



The problem is that TSM is generating errors with our normally scheduled
backups saying that it cannot backup these files because they are in use by
another process.



Why would TSM attempt to be backing up files I've specifically excluded.



Thanks,



Jim Jelf

Sr. Systems Administrator

Superior Consultant

include/exclude errors

[Laura Lantz]

TSM 5.2.2
AIX 5.2

Hello Everyone!

I am getting the following errors in my dsierror.log file:

08/08/06   10:54:27 Management class '.../*' named on include/exclude line 0
does not exist.

Here is the actual include statement:

include /back_txprod:backups-3.0/.../* database

I know this a syntax problembecause of the spaces and using a
differerent management class other than the default. Please help with the
correct syntax.

Many thanks,




Laura

INCLUDE / EXCLUDE PROBLEMS

[adrian_compton]

Hi,

 

I have a very confusing scenario that I cant seem to resolve.

I have the following Client Option File set on a node:

 

def clo NT_DISK_EXCLUDE_FILES desc=""

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "INCLUDE '*' NT" force=Yes
seq=0

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP '*:\Program
Files\Microsoft SQL Server\MSSQL\BACKUP\...\*.*'" force=No seq=1

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP '*:\Program
Files\Microsoft SQL Server\MSSQL\data\...\*.*'" force=No seq=2

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\users\...\*.mp3'" force=No seq=3

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\users\...\*.wmv'" force=No seq=4

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\users\...\*.mov'" force=No seq=5

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\users\...\*.bak'" force=No seq=6

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\users\...\*.tmp'" force=No seq=7

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\WINDOWS\PCHealth\HelpCtr\...\*.*'" force=No seq=8

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\microsoft uam volume\...\*'" force=No seq=9

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\microsoft uam volume\...\*.*'" force=No seq=10

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP '*:\...\EA
DATA. SF'" force=No seq=11

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\IBMBIO.COM'" force=No seq=12

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\IBMDOS.COM'" force=No seq=13

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\IO.SYS'" force=No seq=14

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\...\system32\config\...\*'" force=No seq=15

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\...\system32\Perflib*.dat'" force=No seq=16

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\...\system32\dhcp\...\*'" force=No seq=17

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\...\system32\dns\...\*'" force=No seq=18

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\WINDOWS\PCHealth\HelpCtr\...\*.*'" force=No seq=19

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\users\...\*.mp3'" force=No seq=20

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\users\...\*.wmv'" force=No seq=21

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\users\...\*.bak'" force=No seq=22

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\users\...\*.tmp'" force=No seq=23

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\Documents and Settings\...\*.*'" force=No seq=24

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\Documents and Settings\...\*'" force=No seq=25

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\microsoft uam volume\...\*'" force=No seq=26

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\microsoft uam volume\...\*.*'" force=No seq=27

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE '*:\...\EA
DATA. SF'" force=No seq=28

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\IBMBIO.COM'" force=No seq=29

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\IBMDOS.COM'" force=No seq=30

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\IO.SYS'" force=No seq=31

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\...\system32\config\...\*'" force=No seq=32

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\...\system32\Perflib*.dat'" force=No seq=33

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\...\system32\dhcp\...\*'" force=No seq=34

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.ARCHIVE
'*:\...\system32\dns\...\*'" force=No seq=35

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\Empower\*.*'" force=No seq=36

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\EmpowerArchive1DB\*.*'" force=No seq=37

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\Empower\*'" force=No seq=38

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\EmpowerArchive1DB\*'" force=No seq=39

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP
'*:\Documents and Settings\...\*.log'" force=No seq=40

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.BACKUP '*:\Program
Files\Tivoli\tsm\baclient\...\*.log'" force=No seq=41

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.DIR
'*:\...\Temporary Internet Files'" force=No seq=42

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.DIR '*:\System
Volume Information'" force=No seq=43

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.DIR '*:\Recycler'"
force=No seq=44

def clientopt NT_DISK_EXCLUDE_FILES INCLEXCL "EXCLUDE.DIR '*:\Recycled'

include / exclude question

[Hizny, Michael]

In setting up a backup, I am having problems with a specific
include/exclude option.  I want to do the following:

On our users H: drives they have a subdirectory called profiles.  I want
to keep 3 folders under this and exclude the rest. i.e. 

H:\user\profiles\cookiesdon't want to back up
H:\user\profiles\My documents\  want to back this up
H:\user\profiles\application data\  don't want to back up

My opt files has the following:

EXCLUDE.DIR "*:\...\Profiles"
INCLUDE "*:\...\Profiles\My Documents"
INCLUDE "*:\...\Profiles\Desktop"

Yet, when I run this, it excludes the entire profiles directory, even
though the include is at the bottom.  

Any ideas what I am doing wrong?

Thanks,
Mike

Re: Include/Exclude

[Andrew Raibeck]

You can use client option sets (defined on the server, see DEFINE 
CLOPTSET, DEFINE CLIENTOPT, and UPDATE NODE CLOPTSET=nnn server admin 
commands) to control much of this behavior.

For example, you could define a server-side client option set that 
includes something like:

   exclude *:\...\*.mp3
   exclude *:\...\*.wav
   exclude *:\...\*.avi
   exclude *:\...\*.jpg

etc.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
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 02/06/2007 
02:05:22 PM:

> Hi,
> 
> Why the options file could be edited locally by users who owns root 
> privileges (ex: users with laptops), why this information is not kept in 

> the server and manage by TSM administrators ¿?
> 
> It seems that some users could manage their own backups, and backup 
> something that will occupy space without being important for restore 
> (ex: movie files, music, photos,...)
> 
> What do you think ¿?
> 
> Thanks,
> 
> Regards,
> Ibán.

Re: Include/Exclude

[Bos, Karel]

Hi,

I would look at the "client option" options and use this. CLO is defined and 
managed on the ITSM server side and capable to overwrite local defined options.

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ibán 
Bernaldo de Quirós y Márquez
Sent: dinsdag 6 februari 2007 22:05
To: ADSM-L@VM.MARIST.EDU
Subject: Include/Exclude

Hi,

Why the options file could be edited locally by users who owns root privileges 
(ex: users with laptops), why this information is not kept in the server and 
manage by TSM administrators ¿?

It seems that some users could manage their own backups, and backup something 
that will occupy space without being important for restore
(ex: movie files, music, photos,...)

What do you think ¿?

Thanks,

Regards,
Ibán.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request

Re: Include/Exclude

[Ibán Bernaldo de Quirós y Márquez]

Thanks Andrew !!

I will try it.

Regards,
Ibán.

PS: I am always a newbie !!

Andrew Raibeck escribió:
You can use client option sets (defined on the server, see DEFINE 
CLOPTSET, DEFINE CLIENTOPT, and UPDATE NODE CLOPTSET=nnn server admin 
commands) to control much of this behavior.


For example, you could define a server-side client option set that 
includes something like:


   exclude *:\...\*.mp3
   exclude *:\...\*.wav
   exclude *:\...\*.avi
   exclude *:\...\*.jpg

etc.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
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 02/06/2007 
02:05:22 PM:


  

Hi,

Why the options file could be edited locally by users who owns root 
privileges (ex: users with laptops), why this information is not kept in 



  

the server and manage by TSM administrators ¿?

It seems that some users could manage their own backups, and backup 
something that will occupy space without being important for restore 
(ex: movie files, music, photos,...)


What do you think ¿?

Thanks,

Regards,
Ibán.

Include/Exclude question

[Zoltan Forray/AC/VCU]

I am trying to build CLOPTSETs for various, similar boxes. For instance,
NT/W2K boxes that have MS-SQL on them. Unfortunately, I have found at
least 4-different permutation on the directory names used.

I have noticed that in the error messages when attempting to backup the
SQL files as regular files, not using the TDP/TDS, I see these errors:


ANE4987E Error processing '\\acadnt3\d$\MSSQL7\Data \BIS_Data.MDF': the
object is in use by another process


My question, what gives with the extra blank/space after the "\Data" part
of the directory name ?

Re: Include/Exclude

[Henry Chin]

Sascah,

Now that the directory and files are excluded from being backed 
up. The next time that the backup runs. The TSM server will 
think that the directory and file have been deleted from the 
workstation. The directory and files that were backed up 
earlier will be come an inactive version.
The inactive version will remain on the system for how ever 
long. To determine how many days that a delete version will be 
kept, need to look at the copygroup setting.
The "retain only version" controls how many days that the 
directory and file will be kept after the directory and file 
have been deleted from the work station.


I hope this some sense, if not I hope someone else can word it 
better.

Sias





Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag


 On, Sascha Braeuning (Sascha.Braeuning@SPARKASSEN-
INFORMATIK.DE) wrote:

> Hi TSMers,
> 
> I've got backed up some directories and files, which I should 
not. Now I
> changed my include/exclude list. What happened with files, 
which are backed
> up but now actually excluded? When these files remain on the 
server: Is
> there a possibility to delete these files?
> 
> MfG/regards
> Sascha Bräuning
> 
> 
> Sparkassen Informatik, Fellbach
> 
> OrgEinheit: 6322
> Wilhelm-Pfitzer Str. 1
> 70736 Fellbach
> 
> Telefon:   (0711) 5722-2144
> Telefax:   (0711) 5722-1634
> 
> Mailadr.:  [EMAIL PROTECTED]

Re: Include/Exclude

[Salak Juraj]

Hi,

the files will be expired on the server later,
according to the management class used during last backup.

If this is an issue to delete the files from server sooner,
you can
 1) create a management class, let us name it TRASH_MC,
with short retention periods
 2) assign this management class to files concerned
 like:
include.dir  c:\mydir TRASH_MC
include.file c:\myfile.doc TRASH_MC
 3) perform incremental backup, 
this will rebind your files on the server
 4) do your planned stuff: change incl/excl, perform backup
 5) start expire on the server.

Alternatively, 
use "dsmc expire" command.
Only the later will work for inactive files as well.

regards
Juraj, Gmunden, Austria



> -Original Message-
> From: Sascha Braeuning
> [mailto:Sascha.Braeuning@;SPARKASSEN-INFORMATIK.DE]
> Sent: Thursday, November 07, 2002 11:01 AM
> To: [EMAIL PROTECTED]
> Subject: Include/Exclude
> 
> 
> Hi TSMers,
> 
> I've got backed up some directories and files, which I should 
> not. Now I
> changed my include/exclude list. What happened with files, 
> which are backed
> up but now actually excluded? When these files remain on the 
> server: Is
> there a possibility to delete these files?
> 
> MfG/regards
> Sascha Bräuning
> 
> 
> Sparkassen Informatik, Fellbach
> 
> OrgEinheit: 6322
> Wilhelm-Pfitzer Str. 1
> 70736 Fellbach
> 
> Telefon:   (0711) 5722-2144
> Telefax:   (0711) 5722-1634
> 
> Mailadr.:  [EMAIL PROTECTED]
> 

include/exclude list

[Gill, Geoffrey L.]

Will someone please explain the pitfalls of changing the include/exclude
list as it relates to this issue. We have a server that is running Oracle.
There is no TDP for True64 so we're stuck with what we have, the client.
Backing up open Oracle files is a waste of time because we know from testing
restores they are no good. I've suggested to the admins to exclude those
open files from nightly backups because of this. We're talking about
60-70GB. This times 21, the number of versions they have for me is a lot of
space.

I'd like to know if my understanding is correct. If a file is not in the
exclude list then it's backed up, that's an easy one. If it's changed
nightly and been backed up for 3 weeks I have 21 copies. If I now exclude
the file it's not backed up any longer, however what happens to the 21
copies I have in place? Are they all expired immediately except the last one
and removed from the system?

The problem is we "would" be stopping the database on weekends and getting
good backups. If editing the exclude list would force the good copies to go
away then we could not live with that. If there is a way to exclude them
some days and then include them other days and still keep 21 good copies
then would someone please help me to accomplish this. I'm to the point I can
use all the free space I can, got about 20 clients that need backups but I
don't have the space yet.

Thanks for the help.

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:   [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (888) 997-9614

Include/Exclude (again)

[MacMurray, Andrea (CC-ETS Ent Storage Svcs)]

Hello SMS'ers
Question again about include exclude. Server is AIX 4.3.3 tsm version is
4.2.1.9 Client is NT . The customer wants to include only the one file in
the include and exclude all the rest. Following to this is the DSM.OPT file
and this should run. Need some assistance and insight on this one.

Thanks

Andrea Mac Murray
Sen. Systems Administrator
ConAgra Foods Inc.
7300 World Communication Dr.
Omaha,NE, 68122
Ph:(402) 577-3603
Fax;(402) 577-3515







ERRORLOGRETENTION   5 D
SCHEDLOGRETENTION   5 D
PASSWORDACCESS  GENERATE

LARGECOMMBUFFERSNO
COMMMETHOD  TCPIP
TCPSERVERADDRESScagadsm3.conagra.cag
TCPPORT 1500
TCPBUFFSIZE 31
TCPWINDOWSIZE   24

DOMAIN  D:

EXCLUDE.DIR \\*\*\*
EXCLUDE {abcd}:*
EXCLUDE.DIR {abcd}:*

INCLUDE.FILE D:\Oracle\backup\dev8i.dmp MCBKUP4

VERBOSE

DIRMC   MCBKUP4

Include/Exclude again...

[Coats, Jack]

I have an issue that I am having trouble resolving.
Any suggestions would be appreciated.

On one machine (Win2K) we have some large files generated on a directory,
then on occasion they are written to a DVD or two, and are taken offsite for
archive.

I need to
  1. backup the machine
  2. backup the 'temporary data' space on the disk
  3. backup the DVD's to tape if they are still in the computer at backup
time.

I am getting good backups.  But I need to reduce the number of backups I
keep of 2 and 3 above (like to 2 copies till they are removed, and 1 copy
after that for 10 days or so.

If things are working right, (2) stays empty, and (3) takes a week or so to
fill.  If things are wrong, (3) is full or not working, and (2) is filling,
and this
is when the backups are most critical.

Suggestions on how I should set up this machines backups?

Thanks. ... Jack

include/exclude question

[Ruksana Siddiqui]

Hi all,

On NT/ 2000 server I have a drive I want to exclude from the backup but I
have a directory in that drive which I want to include in the backup.
in my dsm.opt file  I have
domain a: b: c: d: f:

and it backups all the drives I mentioned
and even if I don't have the above mentioned line by default it's backing up
all the drives on the server.

I tried doing the following in dsm.opt

exclude.dir "a:\"
exclude.dir "b:\"
exclude.dir "c:\"
exclude.dir "d:\"
exclude.dir "f:\"
include "c:\abc\abc.txt" mgtname

with above nothing works .

what is the procedure I need to follow to backup :
all the drives except f:\
and a directory in f:\

include.dir "a:\"
include.dir "b:\"
include.dir "c:\"
include.dir "d:\"
exclude.dir "f:\"
include "f:\abc\" mgtname

any help is highly appreciated.

CAUTION - This message may contain privileged and confidential information intended 
only for the use of the addressee named above. If you are not the intended recipient 
of this message you are hereby notified that any use, dissemination, distribution or 
reproduction of this message is prohibited. If you have received this message in error 
please notify AMCOR immediately. Any views expressed in this message are those of the 
individual sender and may not necessarily reflect the views of AMCOR.

Re: Include/Exclude

[Rushforth, Tim]

TSM 5.1.1.0 on W2K works for me.  If I have exclude.dir for a directory it
does not show up in the GUI under backup.

my exclude is:
exclude.dir d:\temp
exclude.dir d:\recycler

-Original Message-
From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02, 2002 4:01 PM
To: [EMAIL PROTECTED]
Subject: Include/Exclude


I've just installed WIN2K client 5.1.0.1 on a system to play with and from
what I can see the Exclude list does not work. I have some Exclude.Dir lines
and these directories will probably back up since I still see the files
normally with the GUI. Within those directories I can see specific excludes
from other excludes I do have on specific types of files that do work. I've
tried * and ? with no success.

Anyone else seen this?

Anyone have a Win2k or NT dsm.opt they've tested on the V5 client with the
"standards" that work?

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:<mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 905-7154

Re: Include/Exclude

[Mark Stapleton]

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Gill, Geoffrey L.
> I've just installed WIN2K client 5.1.0.1 on a system to play with and from
> what I can see the Exclude list does not work. I have some
> Exclude.Dir lines
> and these directories will probably back up since I still see the files
> normally with the GUI. Within those directories I can see
> specific excludes
> from other excludes I do have on specific types of files that do
> work. I've
> tried * and ? with no success.

It'd help a lot, Geoffry, if you'd post the includes and excludes you're
trying to use, and what your desired results are.

And, yes, includes/excludes work just fine on 5.1.0.0, 5.1.0.1, and 5.1.1.0.

--
Mark Stapleton ([EMAIL PROTECTED])
Certified TSM consultant
Certified AIX system engineer
MSCE

Re: Include/Exclude

[Edgardo Moso]

That's correct.   But if you have backup previously, it will show up. It
won't delete automatically or expire.





From: "Rushforth, Tim" <[EMAIL PROTECTED]> on 07/02/2002 05:48
  PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:
Subject:  Re: Include/Exclude

TSM 5.1.1.0 on W2K works for me.  If I have exclude.dir for a directory it
does not show up in the GUI under backup.

my exclude is:
exclude.dir d:\temp
exclude.dir d:\recycler

-Original Message-
From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02, 2002 4:01 PM
To: [EMAIL PROTECTED]
Subject: Include/Exclude


I've just installed WIN2K client 5.1.0.1 on a system to play with and from
what I can see the Exclude list does not work. I have some Exclude.Dir
lines
and these directories will probably back up since I still see the files
normally with the GUI. Within those directories I can see specific excludes
from other excludes I do have on specific types of files that do work. I've
tried * and ? with no success.

Anyone else seen this?

Anyone have a Win2k or NT dsm.opt they've tested on the V5 client with the
"standards" that work?

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:<mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 905-7154

Include/Exclude tester?

[Zoltan Forray/AC/VCU]

Has someone created an include/exclude tester to show me the errors of my
ways (besides from the client side)?

I have this statement in my CLOPTSET:   INCLEXCL EXCLUDE *:\...\Sophos\*
   and FORCE=YES

Yet I still see boxes that have this cloptset assigned to them backing up
files like:  \PROGRAM FILES\SOPHOS\SOPHOS ANTI-VIRUS\ AGEN-HTK.IDE


Please show me the errors of my way and how to properly exclude *EVERY*
directory that contains the name/word "sophos" in it!

Re: include \ exclude

[Lee, Gary]

Reverse the order.  Includes and excludes are processed bottom up.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim 
Brown
Sent: Wednesday, June 11, 2014 3:05 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] include \ exclude

Attempting to include just one subfolder within a folder that I want to exclude.
Cant  seem to come up with right combination.

Is the 2nd overriding the first?

Include "D:\USR1\Folder1\Folder2\Folder3\Folder4\...\*.*"

Exclude "D:\USR1\Folder1\...\*.*"

Thanks,

Tim

Re: include \ exclude

[Ron Delaware]

It is always a good practice to put your include statements at the bottom 
of your list and the excludes at the top of the file. Remember that 
exclude.dir is read first, regardless of where it is located in the file 
and trumps any include statement.

To answer your question, yes by having the Exclude 
"D:\USR1\Folder1\...\*.*" before your include, will cause TSM not to 
process your include.

 
Best Regards,
_
Ronald C. Delaware
IBM Level 2 - IT Plus Certified Specialist – Expert
IBM Corporation | Tivoli Software
IBM Certified Solutions Advisor - Tivoli Storage
IBM Certified Deployment Professional
Butterfly Solutions Professional
916-458-5726 (Office
925-457-9221 (cell phone)
email: ron.delaw...@us.ibm.com
Storage Services Offerings


 



From:   Tim Brown 
To: ADSM-L@vm.marist.edu
Date:   06/11/2014 12:06 PM
Subject:    [ADSM-L] include \ exclude
Sent by:"ADSM: Dist Stor Manager" 



Attempting to include just one subfolder within a folder that I want to 
exclude.
Cant  seem to come up with right combination.

Is the 2nd overriding the first?

Include "D:\USR1\Folder1\Folder2\Folder3\Folder4\...\*.*"

Exclude "D:\USR1\Folder1\...\*.*"

Thanks,

Tim

Re: include \ exclude

[Stackwick, Stephen]

And, I would add, change the "*.*"  construct to a "*" pattern. The first only 
INCLUDEs files with a dot in the name, maybe not what you want. Most Windows 
files have a dot, but not all!

STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) | 
stephen.stackw...@icfi.com | icfi.com
ICF INTERNATIONAL | 7125 Thomas Edison Dr, Suite 100, Columbia, Md 21046 | 
443-718-4900  (o)

> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
> Behalf Of Tim Brown
> Sent: Wednesday, June 11, 2014 15:05
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] include \ exclude
> 
> Attempting to include just one subfolder within a folder that I want to
> exclude.
> Cant  seem to come up with right combination.
> 
> Is the 2nd overriding the first?
> 
> Include "D:\USR1\Folder1\Folder2\Folder3\Folder4\...\*.*"
> 
> Exclude "D:\USR1\Folder1\...\*.*"
> 
> Thanks,
> 
> Tim

Re: include \ exclude

[Tim Brown]

That did the trick but it still backs up all folder entries for the excluded 
files

Can those also be excluded?

Dsmsched.log

06/12/2014 19:11:04 Directory-->   0 
\\server\d$\USR1\Folder1\Webfiles [Sent]
06/12/2014 19:11:04 Directory-->   0 
\\server\d$\USR1\Folder1\Webfiles_Backip [Sent]
Dsm.opt

Exclude "D:\USR1\Folder1\...\*.*"
Exclude "D:\USR1\Folder1\...\*"

Include "D:\USR1\Folder1\Folder2\Folder3\Folder4\...\*.*"
Include "D:\USR1\Folder1\Folder2\Folder3\Folder4\...\*"

Tim

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, 
Gary
Sent: Wednesday, 11 June, 2014 3:07 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] include \ exclude

Reverse the order.  Includes and excludes are processed bottom up.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim 
Brown
Sent: Wednesday, June 11, 2014 3:05 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] include \ exclude

Attempting to include just one subfolder within a folder that I want to exclude.
Cant  seem to come up with right combination.

Is the 2nd overriding the first?

Include "D:\USR1\Folder1\Folder2\Folder3\Folder4\...\*.*"

Exclude "D:\USR1\Folder1\...\*.*"

Thanks,

Tim

Include/exclude confusion

[Tom Taylor]

Hello,

I want to understand something and what I read online is
confusing.


On a specific machine I want to back up a folder on "F:" but nothing else


currently under the backup tab of the GUI i do NOT have "F:" selected,
then under include/exclude I have "INCLUDE "F:\foldername" STANDARD"




Will this configuration skip all of "F:" except for the foldername I have
specified in the include? Some things I have read show that "F:" will be
completely ignored even with my include because I do not have it checked
under backup.


I only want to backup "F:\foldername" on F: and I do not even want the
client to look at the rest of "F:"








Thomas Taylor
System Administrator
Jos. A. Bank Clothiers
Cell (443)-974-5768

Multiple include exclude files

[William Goliak]

I've got a set of files, a database, that I want to do a cold backup on 1
time a week.  I also want the nightly backups to keep excluding those DBF
files.  Can I do this within one include exclude file?  Do I need a
second include exclude file, and how go about doing that?


-Bill Goliak
NSIT-SEA Unix Systems Adminstrator
Office: 773 702 9425
Pager:  773 652 0744

Re: Domino Include/Exclude

[Del Hoobler]

Zoltan,

What platform?   Here are some examples (on Windows):

 * To bind all databases in the "mail6" directory
 INCLUDE mail6\...\*  mcname

or

 * To bind all objects
 INCLUDE * mcname


However... if you are doing that, and it still doesn't work...
I should let you know that there is an open APAR - IC35848
to address this problem. We have seen this happen in a few different
situations for Domino, Oracle, and Exchange.

Thanks,

Del



Del Hoobler
IBM Corporation
[EMAIL PROTECTED]

- Remember that the best job security is
doing a job well and doing it cheerfully.

===

> Can someone please send me their include/exclude statements for
> redirecting Domino/Notes backups to a specific managementclass ?
>
> We are trying to direct "weekly" backups to an MC that goes straight to
> tape but still have the "daily" go to an MC that points to a disk landing
> zone. Yes we have multiple node definitions, per the "cookbook".
>
> We seem to be doing something wrong and getting various error
> messages/failures !
>
> ACD0215E All backup objects do not have the same management class backup
> copy destination.
> Explanation: In order to maintain backup data integrity, multiple backup
objects are
> sent to the Tivoli Storage Manager server within a single transaction.
All
> backup objects within a single transaction are required to have the same
> management class backup copy destinations.

Re: Domino Include/Exclude

[Zoltan Forray/AC/VCU]

Sorry about that I did not think the platform made a difference since
it is from the TDP prospective.

Currently, on W2K but will also be encompassing AIX, soon.

We have the latest TDP/fixtest (5.1.5.1) I could find. Is this apar still
open ?





Del Hoobler <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
03/17/2003 02:54 PM
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
    Subject:    Re: Domino Include/Exclude


Zoltan,

What platform?   Here are some examples (on Windows):

 * To bind all databases in the "mail6" directory
 INCLUDE mail6\...\*  mcname

or

 * To bind all objects
 INCLUDE * mcname


However... if you are doing that, and it still doesn't work...
I should let you know that there is an open APAR - IC35848
to address this problem. We have seen this happen in a few different
situations for Domino, Oracle, and Exchange.

Thanks,

Del



Del Hoobler
IBM Corporation
[EMAIL PROTECTED]

- Remember that the best job security is
doing a job well and doing it cheerfully.

=======

> Can someone please send me their include/exclude statements for
> redirecting Domino/Notes backups to a specific managementclass ?
>
> We are trying to direct "weekly" backups to an MC that goes straight to
> tape but still have the "daily" go to an MC that points to a disk
landing
> zone. Yes we have multiple node definitions, per the "cookbook".
>
> We seem to be doing something wrong and getting various error
> messages/failures !
>
> ACD0215E All backup objects do not have the same management class backup
> copy destination.
> Explanation: In order to maintain backup data integrity, multiple backup
objects are
> sent to the Tivoli Storage Manager server within a single transaction.
All
> backup objects within a single transaction are required to have the same
> management class backup copy destinations.

Re: Domino Include/Exclude

[Del Hoobler]

Zoltan,

The platform makes a difference if you specify
directory delimeters only.

The APAR was just opened a week or so ago.
It is still being worked on.

Thanks,

Del



> Sorry about that I did not think the platform made a difference since
> it is from the TDP prospective.
>
> Currently, on W2K but will also be encompassing AIX, soon.
>
> We have the latest TDP/fixtest (5.1.5.1) I could find. Is this apar still
> open ?

IGNORE : Re: include/exclude

[goc]

o yes , sorry ... my bad
this is for windows syntax
sorry once again
g
- Original Message -
From: "Sal Mangiapane" <[EMAIL PROTECTED]>
To: 
Sent: Wednesday, May 11, 2005 12:27 PM
Subject: Re: include/exclude

goc wrote:
hi all,
a short one
in
exclude "*:/.../nohup.out*"
what does *: mean ?
and then with dsmc q inclexcl
*** FILE INCLUDE/EXCLUDE ***
Mode Function  Pattern (match from top down)  Source File
 - -- -
No exclude filespace statements defined.
No exclude directory statements defined.
Exclude All   /.../*:/.../nohup.out*
/usr/local/etc/inclexcl.file
No DFS include/exclude statements defined.

thanks in advance ?


The : is the drive delimiter.
The *: means any drive.
But, nohup.out is probably a file on a UNIX based computer and drive
letters don't really make sense.
Hope this helps,

Include/exclude in linux

[jianyu he]

Hi,

I met some problems when I tried to automatic backup files from a linux client to 
linux server,  the exclude/include did't work. I wrote the following sentence in the 
dsm.sys:

exclude "/home/"
exclude "/opt/"

It still backed up the files of home and opt

I don't know why?

another question is where can I add the environment variables in linux redhat 9

could you give me some advice?

thanks

Andy




-
Post your free ad now! Yahoo! Canada Personals

Include/Exclude in archives

[Mike Bantz]

In further work on our archive problem and solution, I'm having a little
trouble with our inc/exc files.

It's my understanding that the archive runs off of the same dsm.opt file
that the baclient uses, but with slightly different syntax.

For instance, a couple of lines of that .opt file look like this:

INCLUDE "\\blender\c$\* <\\blender\c$\*> "
EXCLUDE.dir "\\blender\c$\rsi_ias_build <\\blender\c$\rsi_ias_build> "

With the corresponding archive entries below:

INCLUDE.archive "\\blender\c$\* <\\blender\c$\*> "
EXCLUDE.archive "\\blender\c$\rsi_ias_build <\\blender\c$\rsi_ias_build> "

Just going through the archive GUI, I'm still seeing those directories
available to me (in contrast to the baclient part of the GUI, where those
directories aren't even visible to select) which I'm taking as a sign that
the .opt file is not set up correctly.

Am I on the right track here?

Thanks in advance...

Mike Bantz
Systems Administrator
Research Systems, Inc

Re: include/exclude statements

[Kamp, Bruce]

Should be exclude.fs 


-
Bruce Kamp
Senior Server Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Richard Mochnaczewski [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 23, 2004 11:54 AM
To: [EMAIL PROTECTED]
Subject: include/exclude statements

Hi,

I'm setting up my include/exclude statements dsm.sys file on all my AIX
servers, and I'm running into problem with the excludes. I want to exclude
the following filesystems :

/
/usr
/var
/tmp

I'm using the following statements in my dsm.sys :

exclude.dir "/"
exclude.dir "/usr"
exclude.dir "/var"
exclude.dir "/tmp"

followed by whatever other filesystems I want excluded . The four I've
pointed out are are constantly being backed up. I'm running version TSM
5.2.2 on AIX 5.2 server. All my clients are 5.2.2. Any ideas ?

Rich




This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations. Any distribution, use or copying
of this e-mail or the information it contains by other than an intended
recipient is unauthorized. If you received this e-mail in error, please
advise me (by return e-mail or otherwise) immediately. 

Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux
droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou
copie de ce message ou des renseignements qu'il contient par une personne
autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez
ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de
courriel ou par un autre moyen.

Re: include/exclude statements

[Richard Sims]

>I'm setting up my include/exclude statements dsm.sys file on all my AIX
>servers, and I'm running into problem with the excludes. I want to =
>exclude
>the following filesystems :
>
>/
>/usr
>/var
>/tmp
>
>I'm using the following statements in my dsm.sys :
>
>exclude.dir "/"
>exclude.dir "/usr"
>exclude.dir "/var"
>exclude.dir "/tmp"
>
>followed by whatever other filesystems I want excluded . The four I've
>pointed out are are constantly being backed up. I'm running version TSM
>5.2.2 on AIX 5.2 server. All my clients are 5.2.2. Any ideas ?

Don't do it backwards... Rather than try to exclude file systems, in general,
only have the ones you want included on a Domain definition.
Right now you're looking at dsm.sys in pursuing the problem.
Do 'dsmc q opt' and 'dsmc q inclexcl' to gauge the true environment,
which also involves the server-resident client options.
Find out where the undesired file systems are being included rather than
trying to blindly nullify their effect.  It will keep your overall configuration
simpler.

   Richard Sims

Re: include/exclude statements

[Luc Beaudoin]

Hi Rich

Instead of using exclude.dir "/var" 
 tryexclude.FS  /var * 
FS for file system

good luck

Luc







Richard Mochnaczewski <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
2004-08-23 11:54 AM
Please respond to "ADSM: Dist Stor Manager"

 
To: [EMAIL PROTECTED]
    cc: 
Subject:include/exclude statements


Hi,

I'm setting up my include/exclude statements dsm.sys file on all my AIX
servers, and I'm running into problem with the excludes. I want to exclude
the following filesystems :

/
/usr
/var
/tmp

I'm using the following statements in my dsm.sys :

exclude.dir "/"
exclude.dir "/usr"
exclude.dir "/var"
exclude.dir "/tmp"

followed by whatever other filesystems I want excluded . The four I've
pointed out are are constantly being backed up. I'm running version TSM
5.2.2 on AIX 5.2 server. All my clients are 5.2.2. Any ideas ?

Rich




This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations. Any distribution, use or copying
of this e-mail or the information it contains by other than an intended
recipient is unauthorized. If you received this e-mail in error, please
advise me (by return e-mail or otherwise) immediately. 

Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux
droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou
copie de ce message ou des renseignements qu'il contient par une personne
autre que le (les) destinataire(s) désigné(s) est interdite. Si vous 
recevez
ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de
courriel ou par un autre moyen.

Re: include/exclude statements

[Richard Mochnaczewski]

Thanks, the exclude.fs worked. 

Rich

-Original Message-
From: Luc Beaudoin [mailto:[EMAIL PROTECTED]
Sent: Monday, August 23, 2004 12:18 PM
To: [EMAIL PROTECTED]
Subject: Re: include/exclude statements


Hi Rich

Instead of using exclude.dir "/var" 
 tryexclude.FS  /var * 
FS for file system

good luck

Luc







Richard Mochnaczewski <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
2004-08-23 11:54 AM
Please respond to "ADSM: Dist Stor Manager"

 
To: [EMAIL PROTECTED]
    cc: 
Subject:include/exclude statements


Hi,

I'm setting up my include/exclude statements dsm.sys file on all my AIX
servers, and I'm running into problem with the excludes. I want to exclude
the following filesystems :

/
/usr
/var
/tmp

I'm using the following statements in my dsm.sys :

exclude.dir "/"
exclude.dir "/usr"
exclude.dir "/var"
exclude.dir "/tmp"

followed by whatever other filesystems I want excluded . The four I've
pointed out are are constantly being backed up. I'm running version TSM
5.2.2 on AIX 5.2 server. All my clients are 5.2.2. Any ideas ?

Rich




This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations. Any distribution, use or copying
of this e-mail or the information it contains by other than an intended
recipient is unauthorized. If you received this e-mail in error, please
advise me (by return e-mail or otherwise) immediately. 

Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux
droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou
copie de ce message ou des renseignements qu'il contient par une personne
autre que le (les) destinataire(s) désigné(s) est interdite. Si vous 
recevez
ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de
courriel ou par un autre moyen.




This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations. Any distribution, use or copying
of this e-mail or the information it contains by other than an intended
recipient is unauthorized. If you received this e-mail in error, please
advise me (by return e-mail or otherwise) immediately. 

Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux
droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou
copie de ce message ou des renseignements qu'il contient par une personne
autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez
ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de
courriel ou par un autre moyen.

Re: Include/Exclude Question

[Mike]

On Wed, 01 Sep 2004, Jones, Kelli wrote:

> Server:
> TSM 5.1.7.0
> AIX 5.1
>
> Client:
> NT 4.0
>
> We need to set up include/exclude statements for a node that has drives C thru M.  
> We need to back up only C, G and J.  How do I set up options file to back up only 
> those drives (and everything on them minus various system file) and nothing on the 
> other drives.

You can use the domain statement (domain c:\), but I think it would
be better to not use any domain statements and exclude the drives
with (exclude d:\...\*).

Mike

Re: Include/Exclude Question

[Stapleton, Mark]

>On Wed, 01 Sep 2004, Jones, Kelli wrote:
>> Server:
>> TSM 5.1.7.0
>> AIX 5.1
>> Client:
>> NT 4.0
>>We need to set up include/exclude statements for a node that 
>>has drives C thru M.  We need to back up only C, G and J.  How 
>>do I set up options file to back up only those drives (and 
>>everything on them minus various system file) and nothing on 
>>the other drives.

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
Behalf Of Mike
>You can use the domain statement (domain c:\), but I think it 
>would be better to not use any domain statements and exclude 
>the drives with (exclude d:\...\*).

The domain statement would be one line, and (I suspect) more efficient,
since there would be no filtering involved:

domain c: g: j:

Also, if you add more drive letters to the node, the above domain
statement would not require modification.

--
Mark Stapleton ([EMAIL PROTECTED])
Berbee Information Networks
Office 262.521.5627

Re: Include/Exclude Question

[Jones, Kelli]

So would it be

include domain c: g: j:
Exclude domain d: e: f: h: i:

and so on?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark
Sent: September 01, 2004 10:43 AM
To: [EMAIL PROTECTED]
Subject: Re: Include/Exclude Question


>On Wed, 01 Sep 2004, Jones, Kelli wrote:
>> Server:
>> TSM 5.1.7.0
>> AIX 5.1
>> Client:
>> NT 4.0
>>We need to set up include/exclude statements for a node that
>>has drives C thru M.  We need to back up only C, G and J.  How 
>>do I set up options file to back up only those drives (and 
>>everything on them minus various system file) and nothing on 
>>the other drives.

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
Behalf Of Mike
>You can use the domain statement (domain c:\), but I think it
>would be better to not use any domain statements and exclude 
>the drives with (exclude d:\...\*).

The domain statement would be one line, and (I suspect) more efficient, since there 
would be no filtering involved:

domain c: g: j:

Also, if you add more drive letters to the node, the above domain statement would not 
require modification.

--
Mark Stapleton ([EMAIL PROTECTED])
Berbee Information Networks
Office 262.521.5627

Re: Include/Exclude Question

[Mike]

On Wed, 01 Sep 2004, Stapleton, Mark wrote:

> >On Wed, 01 Sep 2004, Jones, Kelli wrote:
> >> Server:
> >> TSM 5.1.7.0
> >> AIX 5.1
> >> Client:
> >> NT 4.0
> >>We need to set up include/exclude statements for a node that
> >>has drives C thru M.  We need to back up only C, G and J.  How
> >>do I set up options file to back up only those drives (and
> >>everything on them minus various system file) and nothing on
> >>the other drives.
>
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
> Behalf Of Mike
> >You can use the domain statement (domain c:\), but I think it
> >would be better to not use any domain statements and exclude
> >the drives with (exclude d:\...\*).
>
> The domain statement would be one line, and (I suspect) more efficient,
> since there would be no filtering involved:
>
> domain c: g: j:
>
> Also, if you add more drive letters to the node, the above domain
> statement would not require modification.

True, but if you add more drives that need backing up and
forget to modify the domain statement, then have a problem,
you don't have the files backed up. I prefer to backup too
much and then expire what I don't need. By not using the
domain statement you automatically get everything that is
not excluded.

Mike

Re: Include/Exclude Question

[Mike]

On Wed, 01 Sep 2004, Jones, Kelli wrote:

> So would it be
>
> include domain c: g: j:
> Exclude domain d: e: f: h: i:
>
> and so on?

Either use the 'domain c: g: j:' or not have a domain statement
and have 'exclude d:\...\*', 'exclude e:\...\*', etc.

Mike

Re: Include/Exclude Question

[Jones, Kelli]

Please bear with me as I have never done this before...can you look at what I have so 
far?  

Include J:\...\*
Include G:\...\*
Include C:\...\*
Exclude "*:\microsoft uam volume\...\*"
Exclude "*:\Oracle\ora817\network\log\nmi.log"
Exclude "*:\microsoft uam volume\...\*.*"
Exclude "*:\...\EA DATA. SF"
Exclude *:\...\pagefile.sys
Exclude *:\IBMBIO.COM
Exclude *:\IBMDOS.COM
Exclude *:\MSDOS.SYS
Exclude *:\IO.SYS
Exclude *:\...\SYSTEM32\CONFIG\...\*
Exclude *:\...\SYSTEM32\CONFIG\...\*.*
Exclude *:\...\Profiles\...\ntuser.dat* 
Exclude *:\...\system32\Perflib*.dat
Exclude.dir *:\...\system32\wins
Exclude.dir *:\...\system32\LServer
Exclude.dir *:\...\system32\dhcp
Exclude.dir *:\...\system32\config
Exclude.dir *:\...\ntfrs\jet
Exclude.dir *:\...\ntds
Exclude.dir "*:\System Volume Information"
Exclude.dir "*:\...\Temporary Internet Files"
Exclude.dir *:\Recycled
Exclude.dir *:\Recycler
Exclude.dir C:\TSM\log
Exclude.dir D:\...\*
Exclude.dir E:\...\*
Exclude.dir F:\...\*
Exclude.dir H:\...\*
Exclude.dir K:\...\*
Exclude.dir L:\...\*
Exclude.dir M:\...\*

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mike
Sent: September 01, 2004 10:55 AM
To: [EMAIL PROTECTED]
Subject: Re: Include/Exclude Question


On Wed, 01 Sep 2004, Jones, Kelli wrote:

> So would it be
>
> include domain c: g: j:
> Exclude domain d: e: f: h: i:
>
> and so on?

Either use the 'domain c: g: j:' or not have a domain statement and have 'exclude 
d:\...\*', 'exclude e:\...\*', etc.

Mike

Re: Include/Exclude Question

[Martin Krauß]

No, not exactly,
just fill in the line
domain c: g: j:
in your options file and
exclude   system files (like pagefile.sys)
exclude.dir  system directories  (like drive:\...\recycler\)
in the include/exclude file
Greetings,
Martin Krauss

Jones, Kelli schrieb:
So would it be
include domain c: g: j:
Exclude domain d: e: f: h: i:

and so on?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark
Sent: September 01, 2004 10:43 AM
To: [EMAIL PROTECTED]
Subject: Re: Include/Exclude Question
 

On Wed, 01 Sep 2004, Jones, Kelli wrote:
   

Server:
TSM 5.1.7.0
AIX 5.1
Client:
NT 4.0
We need to set up include/exclude statements for a node that
has drives C thru M.  We need to back up only C, G and J.  How 
do I set up options file to back up only those drives (and 
everything on them minus various system file) and nothing on 
the other drives.
 

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
Behalf Of Mike
 

You can use the domain statement (domain c:\), but I think it
would be better to not use any domain statements and exclude 
the drives with (exclude d:\...\*).
   

The domain statement would be one line, and (I suspect) more efficient, since 
there would be no filtering involved:
   domain c: g: j:
Also, if you add more drive letters to the node, the above domain statement would not 
require modification.
--
Mark Stapleton ([EMAIL PROTECTED])
Berbee Information Networks
Office 262.521.5627
 


--

Martin Krauß
IT-Gruppe Geisteswissenschaften
LMU München
Ludwigsstraße 28
80539 München
Hotline: 2180 6400
Tel.:089 2180 1395
FAX: 089 2180 13543
Email: [EMAIL PROTECTED]

Re: Include/Exclude Question

[Andrew Raibeck]

> True, but if you add more drives that need backing up and
> forget to modify the domain statement, then have a problem,
> you don't have the files backed up. I prefer to backup too
> much and then expire what I don't need. By not using the
> domain statement you automatically get everything that is
> not excluded.

While this would technically work, it would still cause those drives to be
traversed, causing increased backup time. A better approach to excluding
drives in this fashion would be to code:

   exclude d:\*
   exclude.dir d:\*

But in my opinion, the *best* approach is to not bother with exclude to
skip drives, but instead use the DOMAIN statement, which will simplify
include/exclude AND avoid looking at the drives at all. A couple of
methods:

   domain c: g: j:

  or

   domain -d: -e: -f: -h: -i: -k: -l: -m:

The first version is easier to code. However, if drive P: is later added
and you want to back it up, you will need to remember to modify the DOMAIN
statement to ensure it gets backed up. On the other hand, if you don't
want drive P: backed up, then the second version of the domain statement
would have to be updated. Note that the second version covers your point
re: backing up too much rather than too little.

Regards,

Andy


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

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" <[EMAIL PROTECTED]> wrote on 09/01/2004
07:53:53:

> On Wed, 01 Sep 2004, Stapleton, Mark wrote:
>
> > >On Wed, 01 Sep 2004, Jones, Kelli wrote:
> > >> Server:
> > >> TSM 5.1.7.0
> > >> AIX 5.1
> > >> Client:
> > >> NT 4.0
> > >>We need to set up include/exclude statements for a node that
> > >>has drives C thru M.  We need to back up only C, G and J.  How
> > >>do I set up options file to back up only those drives (and
> > >>everything on them minus various system file) and nothing on
> > >>the other drives.
> >
> > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
> > Behalf Of Mike
> > >You can use the domain statement (domain c:\), but I think it
> > >would be better to not use any domain statements and exclude
> > >the drives with (exclude d:\...\*).
> >
> > The domain statement would be one line, and (I suspect) more
efficient,
> > since there would be no filtering involved:
> >
> > domain c: g: j:
> >
> > Also, if you add more drive letters to the node, the above domain
> > statement would not require modification.
>
> True, but if you add more drives that need backing up and
> forget to modify the domain statement, then have a problem,
> you don't have the files backed up. I prefer to backup too
> much and then expire what I don't need. By not using the
> domain statement you automatically get everything that is
> not excluded.
>
> Mike

Re: Include/Exclude Question

[Gill, Geoffrey L.]

>But in my opinion, the *best* approach is to not bother with exclude to
>skip drives, but instead use the DOMAIN statement, which will simplify
>include/exclude AND avoid looking at the drives at all. A couple of
>methods:
>
>   domain c: g: j:
>
>  or
>
>   domain -d: -e: -f: -h: -i: -k: -l: -m:
>
>The first version is easier to code. However, if drive P: is later added
>and you want to back it up, you will need to remember to modify the DOMAIN
>statement to ensure it gets backed up. On the other hand, if you don't
>want drive P: backed up, then the second version of the domain statement
>would have to be updated. Note that the second version covers your point
>re: backing up too much rather than too little.
>
>Regards,
>
>Andy

As it relates to system objects would not the first statement exclude them
and the second pick them up? I'm not sure I saw that addressed but maybe the
original poster might also clarify if they need them.

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:   [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 854-0975

Re: Include/Exclude Question

[Andrew Raibeck]

> As it relates to system objects would not the first statement exclude
them
> and the second pick them up? I'm not sure I saw that addressed but maybe
the
> original poster might also clarify if they need them.

Kelli indicated that the client system is NT 4.0, where the system objects
issue does not apply (use the BACKUPREGISTRY YES | NO option instead). For
W2K and up, you can modify the DOMAIN statement as appropriate to
accommodate your system object needs.

Regards,

Andy

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

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" <[EMAIL PROTECTED]> wrote on 09/01/2004
09:52:33:

> >But in my opinion, the *best* approach is to not bother with exclude to
> >skip drives, but instead use the DOMAIN statement, which will simplify
> >include/exclude AND avoid looking at the drives at all. A couple of
> >methods:
> >
> >   domain c: g: j:
> >
> >  or
> >
> >   domain -d: -e: -f: -h: -i: -k: -l: -m:
> >
> >The first version is easier to code. However, if drive P: is later
added
> >and you want to back it up, you will need to remember to modify the
DOMAIN
> >statement to ensure it gets backed up. On the other hand, if you don't
> >want drive P: backed up, then the second version of the domain
statement
> >would have to be updated. Note that the second version covers your
point
> >re: backing up too much rather than too little.
> >
> >Regards,
> >
> >Andy
>
> As it relates to system objects would not the first statement exclude
them
> and the second pick them up? I'm not sure I saw that addressed but maybe
the
> original poster might also clarify if they need them.
>
> Geoff Gill
> TSM Administrator
> NT Systems Support Engineer
> SAIC
> E-Mail:   [EMAIL PROTECTED]
> Phone:  (858) 826-4062
> Pager:   (877) 854-0975

Re: Include/Exclude Question

[Jones, Kelli]

This may be a strange question, but...we just had a TSM consultant here and he said 
that the dsm.opt file is read from bottom to top.  Is this correct?  Does placement of 
the statements matter either way?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Raibeck
Sent: September 01, 2004 1:48 PM
To: [EMAIL PROTECTED]
Subject: Re: Include/Exclude Question


> As it relates to system objects would not the first statement exclude
them
> and the second pick them up? I'm not sure I saw that addressed but 
> maybe
the
> original poster might also clarify if they need them.

Kelli indicated that the client system is NT 4.0, where the system objects issue does 
not apply (use the BACKUPREGISTRY YES | NO option instead). For W2K and up, you can 
modify the DOMAIN statement as appropriate to accommodate your system object needs.

Regards,

Andy

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

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" <[EMAIL PROTECTED]> wrote on 09/01/2004
09:52:33:

> >But in my opinion, the *best* approach is to not bother with exclude 
> >to skip drives, but instead use the DOMAIN statement, which will 
> >simplify include/exclude AND avoid looking at the drives at all. A 
> >couple of
> >methods:
> >
> >   domain c: g: j:
> >
> >  or
> >
> >   domain -d: -e: -f: -h: -i: -k: -l: -m:
> >
> >The first version is easier to code. However, if drive P: is later
added
> >and you want to back it up, you will need to remember to modify the
DOMAIN
> >statement to ensure it gets backed up. On the other hand, if you 
> >don't want drive P: backed up, then the second version of the domain
statement
> >would have to be updated. Note that the second version covers your
point
> >re: backing up too much rather than too little.
> >
> >Regards,
> >
> >Andy
>
> As it relates to system objects would not the first statement exclude
them
> and the second pick them up? I'm not sure I saw that addressed but 
> maybe
the
> original poster might also clarify if they need them.
>
> Geoff Gill
> TSM Administrator
> NT Systems Support Engineer
> SAIC
> E-Mail:   [EMAIL PROTECTED]
> Phone:  (858) 826-4062
> Pager:   (877) 854-0975

Re: Include/Exclude Question

[Mike]

On Wed, 01 Sep 2004, Jones, Kelli wrote:

> This may be a strange question, but...we just had a TSM consultant here and he said 
> that the dsm.opt file is read from bottom to top.  Is this correct?  Does placement 
> of the statements matter either way?

that's what I've read in the manuals

Re: Include/Exclude Question

[Richard Sims]

On Sep 1, 2004, at 2:08 PM, Mike wrote:
On Wed, 01 Sep 2004, Jones, Kelli wrote:
This may be a strange question, but...we just had a TSM consultant
here and he said that the dsm.opt file is read from bottom to top.
Is this correct?  Does placement of the statements matter either way?
that's what I've read in the manuals
I've been around the product for years, and have never seen any
indication that the client option file(s) is read from the bottom to
the top. In terms of data processing, that doesn't even make sense:
sequential files are physically read from the beginning to the end.
From what I perceive, the client software compiles the options
definitions as it reads the file from beginning to end. It then
processes them as needed. In the case of Include-Exclude statements,
they are subsequently processed from last to first.
Placement of statements matters as defined in the manuals, such as
requirements that some statements appear within server stanzas.
Richard Sims

Re: Include/Exclude Question

[Andrew Raibeck]

The dsm.opt file is not read from top to bottom, but INCLUDE and EXCLUDE
statements are *processed* in bottom-up order. For each file that TSM
looks at, it starts comparing the patterns in the include/exclude
statements, and stops comparing when a match is found. If all
include/exclude patterns don't match, then the file is backed up (i.e. TSM
behaves as if there were an implicit "include *:\...\*" at the top of the
include/exclude list.

Consider the following:

1)
   include c:\mydir\my.critical.file
   exclude c:\mydir\...\*

versus:

2)
   exclude c:\mydir\...\*
   include c:\mydir\my.critical.file

In #1, since processing is bottom-up, when TSM encounters file
c:\mydir\my.critical.file, it will match the "exclude" pattern, and thus
not be backed up.

In #2, when TSM encounters file c:\mydir\my.critical.file, it matches the
"include" pattern, and is thus backed up. On the other hand, when TSM
encounters c:\mydir\some.other.file, it doesn't match the "include"
pattern, but does match the "exclude" pattern, so that file is not backed
up. When TSM encounters c:\yourdir\some.file, none of the patterns are
matched, so the file is backed up.

EXCLUDE.DIR is a bit different: these are always matched first, regardless
of placement in the include/exclude list. Thus the following are
equivalent:

   exclude.dir c:\mydir
   include c:\mydir\my.critical.file

and

   include c:\mydir\my.critical.file
   exclude.dir c:\mydir

In both of these cases, my.critical.file is never backed up because
"exclude.dir" is processed first, regardless of physical position in the
include/exclude list.

Regards,

Andy

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

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" <[EMAIL PROTECTED]> wrote on 09/01/2004
11:07:44:

> This may be a strange question, but...we just had a TSM consultant here
and
> he said that the dsm.opt file is read from bottom to top.  Is this
correct?
> Does placement of the statements matter either way?
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Raibeck
> Sent: September 01, 2004 1:48 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Include/Exclude Question
>
>
> > As it relates to system objects would not the first statement exclude
> them
> > and the second pick them up? I'm not sure I saw that addressed but
> > maybe
> the
> > original poster might also clarify if they need them.
>
> Kelli indicated that the client system is NT 4.0, where the system
objects
> issue does not apply (use the BACKUPREGISTRY YES | NO option instead).
For
> W2K and up, you can modify the DOMAIN statement as appropriate to
accommodate
> your system object needs.
>
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Development
> Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
> Internet e-mail: [EMAIL PROTECTED]
>
> 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" <[EMAIL PROTECTED]> wrote on 09/01/2004
> 09:52:33:
>
> > >But in my opinion, the *best* approach is to not bother with exclude
> > >to skip drives, but instead use the DOMAIN statement, which will
> > >simplify include/exclude AND avoid looking at the drives at all. A
> > >couple of
> > >methods:
> > >
> > >   domain c: g: j:
> > >
> > >  or
> > >
> > >   domain -d: -e: -f: -h: -i: -k: -l: -m:
> > >
> > >The first version is easier to code. However, if drive P: is later
> added
> > >and you want to back it up, you will need to remember to modify the
> DOMAIN
> > >statement to ensure it gets backed up. On the other hand, if you
> > >don't want drive P: backed up, then the second version of the domain
> statement
> > >would have to be updated. Note that the second version covers your
> point
> > >re: backing up too much rather than too little.
> > >
> > >Regards,
> > >
> > >Andy
> >
> > As it relates to system objects would not the first statement exclude
> them
> > and the second pick them up? I'm not sure I saw that addressed but
> > maybe
> the
> > original poster might also clarify if they need them.
> >
> > Geoff Gill
> > TSM Administrator
> > NT Systems Support Engineer
> > SAIC
> > E-Mail:   [EMAIL PROTECTED]
> > Phone:  (858) 826-4062
> > Pager:   (877) 854-0975

Re: Include/Exclude Question

[Davidson, Becky]

My finding is that if you have several stanzas
Server A
...

Server B

And you do a dsmc it will automatically connect to server B and not server
A.  That is important to us because if we have an oracle database connecting
with one node name and the client files being backed up as a different node
name we use the dsmc -se=servera if we want to use servera or vice versa.
If we just typed dsmc we would get serverb.  We had some issues with some
backup software that wouldn't let us specify a node name or a server name so
we had to make it the bottom most stanza so it would connect with the node
name that we preferred and then just used the -se option for everything
else.

Becky


From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims

On Sep 1, 2004, at 2:08 PM, Mike wrote:

> On Wed, 01 Sep 2004, Jones, Kelli wrote:
>
>> This may be a strange question, but...we just had a TSM consultant
>> here and he said that the dsm.opt file is read from bottom to top. Is
>> this correct?  Does placement of the statements matter either way?
>
> that's what I've read in the manuals

I've been around the product for years, and have never seen any indication
that the client option file(s) is read from the bottom to the top. In terms
of data processing, that doesn't even make sense: sequential files are
physically read from the beginning to the end.

 From what I perceive, the client software compiles the options definitions
as it reads the file from beginning to end. It then processes them as
needed. In the case of Include-Exclude statements, they are subsequently
processed from last to first.

Placement of statements matters as defined in the manuals, such as
requirements that some statements appear within server stanzas.

 Richard Sims

Re: Include/Exclude Question

[Andrew Raibeck]

Interesting I'll have to look into this. If you don't specify the
DEAULTSERVERNAME option in dsm.sys, the default stanza should be the
*first* one in the list, not the last.

Regards,

Andy

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

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" <[EMAIL PROTECTED]> wrote on 09/01/2004
11:49:16:

> My finding is that if you have several stanzas
> Server A
> ...
>
> Server B
>
> And you do a dsmc it will automatically connect to server B and not
server
> A.  That is important to us because if we have an oracle database
connecting
> with one node name and the client files being backed up as a different
node
> name we use the dsmc -se=servera if we want to use servera or vice
versa.
> If we just typed dsmc we would get serverb.  We had some issues with
some
> backup software that wouldn't let us specify a node name or a server
name so
> we had to make it the bottom most stanza so it would connect with the
node
> name that we preferred and then just used the -se option for everything
> else.
>
> Becky

Re: Include/Exclude Question

[TSM_User]

I have always seen that the dsm.opt file IS processed from bottom up.  How it is read 
I don't know but everything not just the include/exclude list appears to be processed 
from teh bottom up.

Take a windows client and put 2 "NODE" statements in it.  Notice that it will always 
use the bottom one to connect.

We have seen this with other things like TCPWidowSize.  Someone had accidently put 
that entry in two places in the dsm.opt. One at the top and the other at the bottom.  
We adjusted the one at the top not realizing there was another entry.  Of course 
nothing changed. Once we removed the entry from the bottom all was well.

I just ran the test above again using V5.2.3 on Windows XP.

Further, with TSM servers dsmserv.opt the same thing happens.  When you run the set 
opt command it adds an entry to the bottom of the dsmserv.opt file so that it is read 
in first.  This way if the default option was set above it will use the one at the 
bottom of the file.

Andrew Raibeck <[EMAIL PROTECTED]> wrote:
Interesting I'll have to look into this. If you don't specify the
DEAULTSERVERNAME option in dsm.sys, the default stanza should be the
*first* one in the list, not the last.

Regards,

Andy

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

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 09/01/2004
11:49:16:

> My finding is that if you have several stanzas
> Server A
> ...
>
> Server B
>
> And you do a dsmc it will automatically connect to server B and not
server
> A. That is important to us because if we have an oracle database
connecting
> with one node name and the client files being backed up as a different
node
> name we use the dsmc -se=servera if we want to use servera or vice
versa.
> If we just typed dsmc we would get serverb. We had some issues with
some
> backup software that wouldn't let us specify a node name or a server
name so
> we had to make it the bottom most stanza so it would connect with the
node
> name that we preferred and then just used the -se option for everything
> else.
>
> Becky


-
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!

Re: Include/Exclude Question

[Bill Smoldt]

TSM_User,

I don't understand how your observation supports your conclusion that the
.opt file is read in from the bottom.  I believe it simply means that TSM
uses the last instance of each option that has a unique value in the .opt
file.

The include options are processed in a very specific manner.  Exclude.dir
statements are evaluated first and files in those directories are excluded.
Then, the includes and excludes are "processed" from the bottom up, not read
from the bottom up.

I'd be glad to be corrected by someone who really knows, but the .opt file
is a sequential text file and is likely read sequentially from beginning to
end.  The options are evaluated and stored in structures in the running
instance of dsmc.  Why the developers chose to use a bottom up
reconciliation of the includes and excludes is independent of everything
else in the file and the way it is "processed".

Andy, my experience the dsm.sys file is the opposite of Becky's and
consistent with your expectation.  The first stanza on my UNIX systems is
used by default, and I must specify any other stanza that I want a client to
use.  The only change to this would be if I have a dsm.opt somewhere in my
path that specifies a servername option.

Bill Smoldt
STORServer, Inc.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
TSM_User
Sent: Wednesday, September 01, 2004 5:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Include/Exclude Question

I have always seen that the dsm.opt file IS processed from bottom up.  How
it is read I don't know but everything not just the include/exclude list
appears to be processed from teh bottom up.

Take a windows client and put 2 "NODE" statements in it.  Notice that it
will always use the bottom one to connect.

We have seen this with other things like TCPWidowSize.  Someone had
accidently put that entry in two places in the dsm.opt. One at the top and
the other at the bottom.  We adjusted the one at the top not realizing there
was another entry.  Of course nothing changed. Once we removed the entry
from the bottom all was well.

I just ran the test above again using V5.2.3 on Windows XP.

Further, with TSM servers dsmserv.opt the same thing happens.  When you run
the set opt command it adds an entry to the bottom of the dsmserv.opt file
so that it is read in first.  This way if the default option was set above
it will use the one at the bottom of the file.

Andrew Raibeck <[EMAIL PROTECTED]> wrote:
Interesting I'll have to look into this. If you don't specify the
DEAULTSERVERNAME option in dsm.sys, the default stanza should be the
*first* one in the list, not the last.

Regards,

Andy

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

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 09/01/2004
11:49:16:

> My finding is that if you have several stanzas
> Server A
> ...
>
> Server B
>
> And you do a dsmc it will automatically connect to server B and not
server
> A. That is important to us because if we have an oracle database
connecting
> with one node name and the client files being backed up as a different
node
> name we use the dsmc -se=servera if we want to use servera or vice
versa.
> If we just typed dsmc we would get serverb. We had some issues with
some
> backup software that wouldn't let us specify a node name or a server
name so
> we had to make it the bottom most stanza so it would connect with the
node
> name that we preferred and then just used the -se option for everything
> else.
>
> Becky


-
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!

Re: Include/Exclude Question

[TSM_User]

Backup, wait a minute and read what I said again.

I did not say that it is read from bottom up!  As a matter of fact I said I didn't 
know how it was read!  I said it was processed from bottom up.  If you what to pick on 
my use of processed OK.  Well technically it may be that each line is read one at a 
time from top to bottom.  Then repeated values later in the file are layed over top of 
values that were previousely read in.  I was only trying to point out that when a 
human looks at the file they need to be sure that if there any repeated values the 
ones on the bottom will win.  Of course you shouldn't have any option listed more than 
once in a file but if you do this was my observation.

Yes, you are correct there are other factors at work with includes and excludes like 
exclude.dir.

Further I pointed out what is done with the set opt command on the TSM server.


Bill Smoldt <[EMAIL PROTECTED]> wrote:
TSM_User,

I don't understand how your observation supports your conclusion that the
.opt file is read in from the bottom. I believe it simply means that TSM
uses the last instance of each option that has a unique value in the .opt
file.

The include options are processed in a very specific manner. Exclude.dir
statements are evaluated first and files in those directories are excluded.
Then, the includes and excludes are "processed" from the bottom up, not read
from the bottom up.

I'd be glad to be corrected by someone who really knows, but the .opt file
is a sequential text file and is likely read sequentially from beginning to
end. The options are evaluated and stored in structures in the running
instance of dsmc. Why the developers chose to use a bottom up
reconciliation of the includes and excludes is independent of everything
else in the file and the way it is "processed".

Andy, my experience the dsm.sys file is the opposite of Becky's and
consistent with your expectation. The first stanza on my UNIX systems is
used by default, and I must specify any other stanza that I want a client to
use. The only change to this would be if I have a dsm.opt somewhere in my
path that specifies a servername option.

Bill Smoldt
STORServer, Inc.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
TSM_User
Sent: Wednesday, September 01, 2004 5:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Include/Exclude Question

I have always seen that the dsm.opt file IS processed from bottom up. How
it is read I don't know but everything not just the include/exclude list
appears to be processed from teh bottom up.

Take a windows client and put 2 "NODE" statements in it. Notice that it
will always use the bottom one to connect.

We have seen this with other things like TCPWidowSize. Someone had
accidently put that entry in two places in the dsm.opt. One at the top and
the other at the bottom. We adjusted the one at the top not realizing there
was another entry. Of course nothing changed. Once we removed the entry
from the bottom all was well.

I just ran the test above again using V5.2.3 on Windows XP.

Further, with TSM servers dsmserv.opt the same thing happens. When you run
the set opt command it adds an entry to the bottom of the dsmserv.opt file
so that it is read in first. This way if the default option was set above
it will use the one at the bottom of the file.

Andrew Raibeck wrote:
Interesting I'll have to look into this. If you don't specify the
DEAULTSERVERNAME option in dsm.sys, the default stanza should be the
*first* one in the list, not the last.

Regards,

Andy

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

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 09/01/2004
11:49:16:

> My finding is that if you have several stanzas
> Server A
> ...
>
> Server B
>
> And you do a dsmc it will automatically connect to server B and not
server
> A. That is important to us because if we have an oracle database
connecting
> with one node name and the client files being backed up as a different
node
> name we use the dsmc -se=servera if we want to use servera or vice
versa.
> If we just typed dsmc we would get serverb. We had some issues with
some
> backup software that wouldn't let us specify a node name or a server
name so
> we had to make it the bottom most stanza so it would connect with the
node
> name that we preferred and then just used the -se option for everything
> else.
>
> Becky


-
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!


-
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.