Re: Fiddling with exclude statement
Hi Eric,
Thanks for pointing out that doc issue. I am looking into getting that
resolved. It is correct that the EXCLUDE (without the .DIR) and INCLUDE operate
on file objects only, not directories.
I agree that the approach you are using is probably the easiest if the backup
of undesired directory objects is only an annoyance. The alternative I
mentioned might be more viable if there were a huge number, say, tens of
thousands or more, of directories you did not want to back up, or if traversing
the directories you did not want to back up was too time consuming.
Best regards,
Andy
Andrew Raibeck
IBM Storage Protect Level 3
stor...@us.ibm.com
From: ADSM: Dist Stor Manager on behalf of Loon, Eric
van (ITOP DI) - KLM
Date: Friday, March 8, 2024 at 09:50
To: ADSM-L@VM.MARIST.EDU
Subject: [EXTERNAL] Re: Fiddling with exclude statement
Hi Andy,
I have been able to get the job done through the following lines in the
cloptset:
Use Option Set Value (FORCE): No
Option Value: EXCLUDE '/tech/splunk/.../*'
Option: INCLEXCL
Sequence number: 105
Use Option Set Value (FORCE): No
Option Value: INCLUDE '/tech/splunk/etc/.../*'
Option: INCLEXCL
Sequence number: 106
Use Option Set Value (FORCE): No
Option Value: INCLUDE '/tech/splunk/var/.../*'
Option: INCLEXCL
Sequence number: 107
Use Option Set Value (FORCE): No
Option Value: EXCLUDE.DIR '/tech/splunk/var/run'
This still causes the subdirectories to be backed up in /tech/splunk (except
for /tech/splunk/var/run and everything below), but I think I can live with
that. I was put on the wrong foot by one of the examples in the manual:
https://www.ibm.com/docs/en/storage-protect/8.1.21?topic=options-examples-using-wildcards-include-exclude-patterns.
In table 1 it states:
EXCLUDE /.../Documents/.../*
INCLUDE "/home/aleko/Documents/
Current"
Exclude all files and directories under any Documents directory that might
exist, except for the Current file of user aleko.
In the example above, all files are excluded, NOT the subdirectories. So, I
guess the manual is wrong here?
Thanks for your work-around. I like the idea, but the only downside would be
that the restore command syntax changes, which will most likely be very
confusing for the end user.
Kind regards,
Eric van Loon
Air France/KLM Core Infra
From: ADSM: Dist Stor Manager on behalf of Andrew
Raibeck
Sent: Friday, March 8, 2024 13:35
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Fiddling with exclude statement
Hi Eric,
Based on your previous response to the exclude.dir suggestion, I suppose you
have a scenario like this:
* Exclude all other files underneath /tech/splunk,
* but directory objects are still processed.
exclude /tech/splunk/.../*
* Back up everything in /tech/splunk/keep1 and /tech/splunk/keep2
include /tech/splunk/keep1/.../*
include /tech/splunk/keep2/.../*
In this case, you cannot avoid scanning and backing up all subdirectories of
/tech/splunk.
Another alternative is to consider using the VIRTUALMOUNTPOINT
(https://www.ibm.com/docs/en/storage-protect/8.1.21?topic=reference-virtualmountpoint)
option in dsm.sys, like this:
...
virtualmountpoint /tech/splunk
virtualmountpoint /tech/splunk/keep1
virtualmountpoint /tech/splunk/keep2
exclude.fs /tech/splunk
...
The virtual mount points are effectively treated like separate file systems.
The exclude.fs then prevents backup of everything in /tech/splunk that is NOT
part of the other virtual mount points.
When using the command line client for queries and restores, you might need to
put curly braces '{' and '}' around the file system name to avoid ambiguity in
file specifications. For example, if you want to search for a file named
myfile.txt, but you are not sure in which directory the file resides, then you
will have to do this:
dsmc query {/tech/splunk/
Also, if you want to restore everything you backed up under /tech/splunk, you
cannot do this:
dsmc restore /tech/splunk/ -subdir=yes
Instead, you need to do this:
dsmc restore {/tech/splunk/keep1} -subdir=yes
dsmc restore {/tech/splunk/keep2} -subdir=yes
I suggest trying this concept in a test environment first, to see if it is
feasible for you.
Regards,
Andy
Andrew Raibeck
IBM Storage Protect Level 3
stor...@us.ibm.com
-Original Message-
From: ADSM: Dist Stor Manager On Behalf Of Loon, Eric
van (ITOP DI) - KLM
Sent: Tuesday, 27 February, 2024 08:55
To: ADSM-L@VM.MARIST.EDU
Subject: [EXTERNAL] Re: Fiddling with exclude statement
Hi Skylar,
Yes, we have a DIRMC set in the client option file. I removed it, just to check
whether it makes any difference, but the subdirectories are still being backed
up, with the only difference that they are bound to the longest retention
mg
Re: Fiddling with exclude statement
Hi Andy,
I have been able to get the job done through the following lines in the
cloptset:
Use Option Set Value (FORCE): No
Option Value: EXCLUDE '/tech/splunk/.../*'
Option: INCLEXCL
Sequence number: 105
Use Option Set Value (FORCE): No
Option Value: INCLUDE '/tech/splunk/etc/.../*'
Option: INCLEXCL
Sequence number: 106
Use Option Set Value (FORCE): No
Option Value: INCLUDE '/tech/splunk/var/.../*'
Option: INCLEXCL
Sequence number: 107
Use Option Set Value (FORCE): No
Option Value: EXCLUDE.DIR '/tech/splunk/var/run'
This still causes the subdirectories to be backed up in /tech/splunk (except
for /tech/splunk/var/run and everything below), but I think I can live with
that. I was put on the wrong foot by one of the examples in the manual:
https://www.ibm.com/docs/en/storage-protect/8.1.21?topic=options-examples-using-wildcards-include-exclude-patterns.
In table 1 it states:
EXCLUDE /.../Documents/.../*
INCLUDE "/home/aleko/Documents/
Current"
Exclude all files and directories under any Documents directory that might
exist, except for the Current file of user aleko.
In the example above, all files are excluded, NOT the subdirectories. So, I
guess the manual is wrong here?
Thanks for your work-around. I like the idea, but the only downside would be
that the restore command syntax changes, which will most likely be very
confusing for the end user.
Kind regards,
Eric van Loon
Air France/KLM Core Infra
From: ADSM: Dist Stor Manager on behalf of Andrew
Raibeck
Sent: Friday, March 8, 2024 13:35
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Fiddling with exclude statement
Hi Eric,
Based on your previous response to the exclude.dir suggestion, I suppose you
have a scenario like this:
* Exclude all other files underneath /tech/splunk,
* but directory objects are still processed.
exclude /tech/splunk/.../*
* Back up everything in /tech/splunk/keep1 and /tech/splunk/keep2
include /tech/splunk/keep1/.../*
include /tech/splunk/keep2/.../*
In this case, you cannot avoid scanning and backing up all subdirectories of
/tech/splunk.
Another alternative is to consider using the VIRTUALMOUNTPOINT
(https://www.ibm.com/docs/en/storage-protect/8.1.21?topic=reference-virtualmountpoint)
option in dsm.sys, like this:
...
virtualmountpoint /tech/splunk
virtualmountpoint /tech/splunk/keep1
virtualmountpoint /tech/splunk/keep2
exclude.fs /tech/splunk
...
The virtual mount points are effectively treated like separate file systems.
The exclude.fs then prevents backup of everything in /tech/splunk that is NOT
part of the other virtual mount points.
When using the command line client for queries and restores, you might need to
put curly braces '{' and '}' around the file system name to avoid ambiguity in
file specifications. For example, if you want to search for a file named
myfile.txt, but you are not sure in which directory the file resides, then you
will have to do this:
dsmc query {/tech/splunk/
Also, if you want to restore everything you backed up under /tech/splunk, you
cannot do this:
dsmc restore /tech/splunk/ -subdir=yes
Instead, you need to do this:
dsmc restore {/tech/splunk/keep1} -subdir=yes
dsmc restore {/tech/splunk/keep2} -subdir=yes
I suggest trying this concept in a test environment first, to see if it is
feasible for you.
Regards,
Andy
Andrew Raibeck
IBM Storage Protect Level 3
stor...@us.ibm.com
-Original Message-
From: ADSM: Dist Stor Manager On Behalf Of Loon, Eric
van (ITOP DI) - KLM
Sent: Tuesday, 27 February, 2024 08:55
To: ADSM-L@VM.MARIST.EDU
Subject: [EXTERNAL] Re: Fiddling with exclude statement
Hi Skylar,
Yes, we have a DIRMC set in the client option file. I removed it, just to check
whether it makes any difference, but the subdirectories are still being backed
up, with the only difference that they are bound to the longest retention
mgmtclass ofcourse.
Thanks for your help.
Kind regards,
Eric van Loon
Air France/KLM Core Infra
From: ADSM: Dist Stor Manager on behalf of Skylar
Thompson
Sent: Monday, February 26, 2024 17:07
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Fiddling with exclude statement
Do you have DIRMC set? My experience is that supersedes any normal exclude
rules, though would only backup the directories and not their contents. I think
exclude.dir would work to exclude that path and avoid the directories being
backed up, though.
On Mon, Feb 26, 2024 at 03:59:47PM +, Loon, Eric van (ITOP DI) - KLM wrote:
> Hi everybody,
>
> I'm trying to exclude a directory called /tech/splunk (including all
> subdirectories) through a client option set. The exclude on the client seem
> to be process
Re: Fiddling with exclude statement
Hi Eric,
Based on your previous response to the exclude.dir suggestion, I suppose you
have a scenario like this:
* Exclude all other files underneath /tech/splunk,
* but directory objects are still processed.
exclude /tech/splunk/.../*
* Back up everything in /tech/splunk/keep1 and /tech/splunk/keep2
include /tech/splunk/keep1/.../*
include /tech/splunk/keep2/.../*
In this case, you cannot avoid scanning and backing up all subdirectories of
/tech/splunk.
Another alternative is to consider using the VIRTUALMOUNTPOINT
(https://www.ibm.com/docs/en/storage-protect/8.1.21?topic=reference-virtualmountpoint)
option in dsm.sys, like this:
...
virtualmountpoint /tech/splunk
virtualmountpoint /tech/splunk/keep1
virtualmountpoint /tech/splunk/keep2
exclude.fs /tech/splunk
...
The virtual mount points are effectively treated like separate file systems.
The exclude.fs then prevents backup of everything in /tech/splunk that is NOT
part of the other virtual mount points.
When using the command line client for queries and restores, you might need to
put curly braces '{' and '}' around the file system name to avoid ambiguity in
file specifications. For example, if you want to search for a file named
myfile.txt, but you are not sure in which directory the file resides, then you
will have to do this:
dsmc query {/tech/splunk/
Also, if you want to restore everything you backed up under /tech/splunk, you
cannot do this:
dsmc restore /tech/splunk/ -subdir=yes
Instead, you need to do this:
dsmc restore {/tech/splunk/keep1} -subdir=yes
dsmc restore {/tech/splunk/keep2} -subdir=yes
I suggest trying this concept in a test environment first, to see if it is
feasible for you.
Regards,
Andy
Andrew Raibeck
IBM Storage Protect Level 3
stor...@us.ibm.com
-Original Message-
From: ADSM: Dist Stor Manager On Behalf Of Loon, Eric
van (ITOP DI) - KLM
Sent: Tuesday, 27 February, 2024 08:55
To: ADSM-L@VM.MARIST.EDU
Subject: [EXTERNAL] Re: Fiddling with exclude statement
Hi Skylar,
Yes, we have a DIRMC set in the client option file. I removed it, just to check
whether it makes any difference, but the subdirectories are still being backed
up, with the only difference that they are bound to the longest retention
mgmtclass ofcourse.
Thanks for your help.
Kind regards,
Eric van Loon
Air France/KLM Core Infra
From: ADSM: Dist Stor Manager on behalf of Skylar
Thompson
Sent: Monday, February 26, 2024 17:07
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Fiddling with exclude statement
Do you have DIRMC set? My experience is that supersedes any normal exclude
rules, though would only backup the directories and not their contents. I think
exclude.dir would work to exclude that path and avoid the directories being
backed up, though.
On Mon, Feb 26, 2024 at 03:59:47PM +, Loon, Eric van (ITOP DI) - KLM wrote:
> Hi everybody,
>
> I'm trying to exclude a directory called /tech/splunk (including all
> subdirectories) through a client option set. The exclude on the client seem
> to be processed OK:
>
> [root@hostname ~]# dsmc q inclexcl|grep splunk
> Exclude All /tech/splunk/.../* Server
>
> But when I run an incremental on /tech, I do see subdirectories being backed
> up:
>
> Incremental backup of volume '/tech'
> Directory--> 1,024 /tech/splunk/etc [Sent]
> Directory--> 1,024 /tech/splunk/var [Sent]
> Directory--> 1,024 /tech/splunk/var/run [Sent]
> Successful incremental backup of '/tech'
>
> I don't understand why, what am I doing wrong here? Thanks for any help in
> advance!
>
>
> Kind regards,
>
> Eric van Loon
>
> Air France/KLM Core Infra
>
> For information, services and offers, please visit our web site:
> http://www.klm.com<http://www.klm.com> . This e-mail and any attachment may
> contain confidential and privileged material intended for the addressee only.
> If you are not the addressee, you are notified that no part of the e-mail or
> any attachment may be disclosed, copied or distributed, and that any other
> action related to this e-mail or attachment is strictly prohibited, and may
> be unlawful. If you have received this e-mail by error, please notify the
> sender immediately by return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission of
> this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
> Dutch Airlines) is registered in Amstelveen, The Netherlands, with
> registered number 33014286
> **
Re: Fiddling with exclude statement
Hi Skylar, Yes, we have a DIRMC set in the client option file. I removed it, just to check whether it makes any difference, but the subdirectories are still being backed up, with the only difference that they are bound to the longest retention mgmtclass ofcourse. Thanks for your help. Kind regards, Eric van Loon Air France/KLM Core Infra From: ADSM: Dist Stor Manager on behalf of Skylar Thompson Sent: Monday, February 26, 2024 17:07 To: ADSM-L@VM.MARIST.EDU Subject: Re: Fiddling with exclude statement Do you have DIRMC set? My experience is that supersedes any normal exclude rules, though would only backup the directories and not their contents. I think exclude.dir would work to exclude that path and avoid the directories being backed up, though. On Mon, Feb 26, 2024 at 03:59:47PM +, Loon, Eric van (ITOP DI) - KLM wrote: > Hi everybody, > > I'm trying to exclude a directory called /tech/splunk (including all > subdirectories) through a client option set. The exclude on the client seem > to be processed OK: > > [root@hostname ~]# dsmc q inclexcl|grep splunk > Exclude All /tech/splunk/.../* Server > > But when I run an incremental on /tech, I do see subdirectories being backed > up: > > Incremental backup of volume '/tech' > Directory--> 1,024 /tech/splunk/etc [Sent] > Directory--> 1,024 /tech/splunk/var [Sent] > Directory--> 1,024 /tech/splunk/var/run [Sent] > Successful incremental backup of '/tech' > > I don't understand why, what am I doing wrong here? Thanks for any help in > advance! > > > Kind regards, > > Eric van Loon > > Air France/KLM Core Infra > > For information, services and offers, please visit our web site: > https://urldefense.com/v3/__http://www.klm.com__;!!K-Hz7m0Vt54!g42kTl8HJ8JxbVJ1A40Zb9fXV8E9lnOPTSU5QvlEdQAVjSL3ipdypfRwLqD5zxRFgyzCjalDnKMBFkvzrNrVPw$ > . This e-mail and any attachment may contain confidential and privileged > material intended for the addressee only. If you are not the addressee, you > are notified that no part of the e-mail or any attachment may be disclosed, > copied or distributed, and that any other action related to this e-mail or > attachment is strictly prohibited, and may be unlawful. If you have received > this e-mail by error, please notify the sender immediately by return e-mail, > and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its > employees shall not be liable for the incorrect or incomplete transmission of > this e-mail or any attachments, nor responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch > Airlines) is registered in Amstelveen, The Netherlands, with registered > number 33014286 > -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department (UW Medicine), System Administrator -- Foege Building S046, (206)-685-7354 -- Pronouns: He/Him/His For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
Re: Fiddling with exclude statement
Hi Andy, That would be much easier, the problem is that I need to include two subdirectories too and an exclude.dir won't allow you to include subdirectories... Thanks for your help. Kind regards, Eric van Loon Air France/KLM Core Infra From: ADSM: Dist Stor Manager on behalf of Andrew Raibeck Sent: Monday, February 26, 2024 17:13 To: ADSM-L@VM.MARIST.EDU Subject: Re: Fiddling with exclude statement Hi Eric, I think you need to use exclude.dir, like this: define clientopt myoptset inclexcl "exclude.dir /tech/splunk" Regards, Andy Andrew Raibeck IBM Storage Protect Level 3 stor...@us.ibm.com -Original Message- From: ADSM: Dist Stor Manager On Behalf Of Skylar Thompson Sent: Monday, 26 February, 2024 11:07 To: ADSM-L@VM.MARIST.EDU Subject: [EXTERNAL] Re: Fiddling with exclude statement Do you have DIRMC set? My experience is that supersedes any normal exclude rules, though would only backup the directories and not their contents. I think exclude.dir would work to exclude that path and avoid the directories being backed up, though. On Mon, Feb 26, 2024 at 03:59:47PM +, Loon, Eric van (ITOP DI) - KLM wrote: > Hi everybody, > > I'm trying to exclude a directory called /tech/splunk (including all > subdirectories) through a client option set. The exclude on the client seem > to be processed OK: > > [root@hostname ~]# dsmc q inclexcl|grep splunk > Exclude All /tech/splunk/.../* Server > > But when I run an incremental on /tech, I do see subdirectories being backed > up: > > Incremental backup of volume '/tech' > Directory--> 1,024 /tech/splunk/etc [Sent] > Directory--> 1,024 /tech/splunk/var [Sent] > Directory--> 1,024 /tech/splunk/var/run [Sent] > Successful incremental backup of '/tech' > > I don't understand why, what am I doing wrong here? Thanks for any help in > advance! > > > Kind regards, > > Eric van Loon > > Air France/KLM Core Infra > > For information, services and offers, please visit our web site: > http://www.klm.com . This e-mail and any attachment may contain confidential > and privileged material intended for the addressee only. If you are not the > addressee, you are notified that no part of the e-mail or any attachment may > be disclosed, copied or distributed, and that any other action related to > this e-mail or attachment is strictly prohibited, and may be unlawful. If you > have received this e-mail by error, please notify the sender immediately by > return e-mail, and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its > employees shall not be liable for the incorrect or incomplete transmission of > this e-mail or any attachments, nor responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal > Dutch Airlines) is registered in Amstelveen, The Netherlands, with > registered number 33014286 > -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department (UW Medicine), System Administrator -- Foege Building S046, (206)-685-7354 -- Pronouns: He/Him/His For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
Re: Fiddling with exclude statement
Hi Eric, I think you need to use exclude.dir, like this: define clientopt myoptset inclexcl "exclude.dir /tech/splunk" Regards, Andy Andrew Raibeck IBM Storage Protect Level 3 stor...@us.ibm.com -Original Message- From: ADSM: Dist Stor Manager On Behalf Of Skylar Thompson Sent: Monday, 26 February, 2024 11:07 To: ADSM-L@VM.MARIST.EDU Subject: [EXTERNAL] Re: Fiddling with exclude statement Do you have DIRMC set? My experience is that supersedes any normal exclude rules, though would only backup the directories and not their contents. I think exclude.dir would work to exclude that path and avoid the directories being backed up, though. On Mon, Feb 26, 2024 at 03:59:47PM +, Loon, Eric van (ITOP DI) - KLM wrote: > Hi everybody, > > I'm trying to exclude a directory called /tech/splunk (including all > subdirectories) through a client option set. The exclude on the client seem > to be processed OK: > > [root@hostname ~]# dsmc q inclexcl|grep splunk > Exclude All /tech/splunk/.../* Server > > But when I run an incremental on /tech, I do see subdirectories being backed > up: > > Incremental backup of volume '/tech' > Directory--> 1,024 /tech/splunk/etc [Sent] > Directory--> 1,024 /tech/splunk/var [Sent] > Directory--> 1,024 /tech/splunk/var/run [Sent] > Successful incremental backup of '/tech' > > I don't understand why, what am I doing wrong here? Thanks for any help in > advance! > > > Kind regards, > > Eric van Loon > > Air France/KLM Core Infra > > For information, services and offers, please visit our web site: > http://www.klm.com . This e-mail and any attachment may contain confidential > and privileged material intended for the addressee only. If you are not the > addressee, you are notified that no part of the e-mail or any attachment may > be disclosed, copied or distributed, and that any other action related to > this e-mail or attachment is strictly prohibited, and may be unlawful. If you > have received this e-mail by error, please notify the sender immediately by > return e-mail, and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its > employees shall not be liable for the incorrect or incomplete transmission of > this e-mail or any attachments, nor responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal > Dutch Airlines) is registered in Amstelveen, The Netherlands, with > registered number 33014286 > -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department (UW Medicine), System Administrator -- Foege Building S046, (206)-685-7354 -- Pronouns: He/Him/His
Re: Fiddling with exclude statement
Do you have DIRMC set? My experience is that supersedes any normal exclude rules, though would only backup the directories and not their contents. I think exclude.dir would work to exclude that path and avoid the directories being backed up, though. On Mon, Feb 26, 2024 at 03:59:47PM +, Loon, Eric van (ITOP DI) - KLM wrote: > Hi everybody, > > I'm trying to exclude a directory called /tech/splunk (including all > subdirectories) through a client option set. The exclude on the client seem > to be processed OK: > > [root@hostname ~]# dsmc q inclexcl|grep splunk > Exclude All /tech/splunk/.../* Server > > But when I run an incremental on /tech, I do see subdirectories being backed > up: > > Incremental backup of volume '/tech' > Directory--> 1,024 /tech/splunk/etc [Sent] > Directory--> 1,024 /tech/splunk/var [Sent] > Directory--> 1,024 /tech/splunk/var/run [Sent] > Successful incremental backup of '/tech' > > I don't understand why, what am I doing wrong here? Thanks for any help in > advance! > > > Kind regards, > > Eric van Loon > > Air France/KLM Core Infra > > For information, services and offers, please visit our web site: > https://urldefense.com/v3/__http://www.klm.com__;!!K-Hz7m0Vt54!g42kTl8HJ8JxbVJ1A40Zb9fXV8E9lnOPTSU5QvlEdQAVjSL3ipdypfRwLqD5zxRFgyzCjalDnKMBFkvzrNrVPw$ > . This e-mail and any attachment may contain confidential and privileged > material intended for the addressee only. If you are not the addressee, you > are notified that no part of the e-mail or any attachment may be disclosed, > copied or distributed, and that any other action related to this e-mail or > attachment is strictly prohibited, and may be unlawful. If you have received > this e-mail by error, please notify the sender immediately by return e-mail, > and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its > employees shall not be liable for the incorrect or incomplete transmission of > this e-mail or any attachments, nor responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch > Airlines) is registered in Amstelveen, The Netherlands, with registered > number 33014286 > -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department (UW Medicine), System Administrator -- Foege Building S046, (206)-685-7354 -- Pronouns: He/Him/His
Fiddling with exclude statement
Hi everybody, I'm trying to exclude a directory called /tech/splunk (including all subdirectories) through a client option set. The exclude on the client seem to be processed OK: [root@hostname ~]# dsmc q inclexcl|grep splunk Exclude All /tech/splunk/.../* Server But when I run an incremental on /tech, I do see subdirectories being backed up: Incremental backup of volume '/tech' Directory--> 1,024 /tech/splunk/etc [Sent] Directory--> 1,024 /tech/splunk/var [Sent] Directory--> 1,024 /tech/splunk/var/run [Sent] Successful incremental backup of '/tech' I don't understand why, what am I doing wrong here? Thanks for any help in advance! Kind regards, Eric van Loon Air France/KLM Core Infra For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
Re: Exclude statement
\...\ means all directories and sub directories so when there are two folders
\one\two\ you only need a single \...\ you don't need two of them as in your
example.
Shannon Bach <[EMAIL PROTECTED]> wrote:
There is an extra directory in there you're not coveringtry this,
c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\5236
"*:\...\...\Local Settings\Temp\...\*"
Madison Gas & Electric Co
Operations Analyst -Data Center Services
Information Management Systems
[EMAIL PROTECTED]
Office 608-252-7260
Larry Peifer <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
06/27/2005 03:07 PM
Please respond to "ADSM: Dist Stor Manager"
To:ADSM-L@VM.MARIST.EDU
cc:
Subject:Re: Exclude statement
Well yes, EXCLUDE "*:\...\Local Settings\Temp\...\*" was my first choice
also but it isn't working any other ideas?
"Bos, Karel" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
06/27/2005 09:30 AM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] Exclude statement
Hi,
Just add
EXCLUDE "*:\...\Local Settings\Temp\...\*"
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Larry Peifer
Sent: maandag 27 juni 2005 18:13
To: ADSM-L@VM.MARIST.EDU
Subject: Exclude statement
The following files are failing during backup of our Win2003 node using
TSM Client 5.3.0 and TSM Server 5.3.1 on AIX.
\\sosim\c$\Documents and Settings\jadmin\Local
Settings\Temp\hsperfdata_jadmin\5236
\\sosim\c$\Documents and Settings\jadmin\Local
Settings\Temp\hsperfdata_jadmin\9544
\\sosim\c$\Documents and Settings\jadmin\Local
Settings\Temp\hsperfdata_jadmin\9860
I'm trying to exclude everything below the ...\Local Settings\Temp\
directory structure. So I've added this line to the dsm.opt file.
EXCLUDE "*:\...\Local Settings\Temp\*"
We're running the CAD to control the Scheduler and have SCHEDMODE set to
polling; all of which is working fine.
I've added other patterns for exclude processing and they are all
working fine. It's just this one that I must be missing something with.
Thanks in advance.
Larry Peifer
San Onofre Nuclear Generating Station
UNIX System Admin
[EMAIL PROTECTED]
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: Exclude statement - fixed
Thanks for the help. It's working now, sintax error as usual.
Bad
EXCLUDE "*:\...\Local Settings\Temp\*"
Good
EXCLUDE "*:\...\Local Settings\Temp\...\*"
Shannon Bach <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
06/27/2005 01:31 PM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] Exclude statement
There is an extra directory in there you're not coveringtry this,
c$\Documents and Settings\jadmin\Local
Settings\Temp\hsperfdata_jadmin\5236
"*:\...\...\Local Settings\Temp\...\*"
Madison Gas & Electric Co
Operations Analyst -Data Center Services
Information Management Systems
[EMAIL PROTECTED]
Office 608-252-7260
Larry Peifer <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
06/27/2005 03:07 PM
Please respond to "ADSM: Dist Stor Manager"
To:ADSM-L@VM.MARIST.EDU
cc:
Subject:Re: Exclude statement
Well yes, EXCLUDE "*:\...\Local Settings\Temp\...\*" was my first choice
also but it isn't working any other ideas?
"Bos, Karel" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
06/27/2005 09:30 AM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] Exclude statement
Hi,
Just add
EXCLUDE "*:\...\Local Settings\Temp\...\*"
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Larry Peifer
Sent: maandag 27 juni 2005 18:13
To: ADSM-L@VM.MARIST.EDU
Subject: Exclude statement
The following files are failing during backup of our Win2003 node using
TSM Client 5.3.0 and TSM Server 5.3.1 on AIX.
\\sosim\c$\Documents and Settings\jadmin\Local
Settings\Temp\hsperfdata_jadmin\5236
\\sosim\c$\Documents and Settings\jadmin\Local
Settings\Temp\hsperfdata_jadmin\9544
\\sosim\c$\Documents and Settings\jadmin\Local
Settings\Temp\hsperfdata_jadmin\9860
I'm trying to exclude everything below the ...\Local Settings\Temp\
directory structure. So I've added this line to the dsm.opt file.
EXCLUDE "*:\...\Local Settings\Temp\*"
We're running the CAD to control the Scheduler and have SCHEDMODE set to
polling; all of which is working fine.
I've added other patterns for exclude processing and they are all
working fine. It's just this one that I must be missing something with.
Thanks in advance.
Larry Peifer
San Onofre Nuclear Generating Station
UNIX System Admin
[EMAIL PROTECTED]
Re: Exclude statement
There is an extra directory in there you're not coveringtry this, c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\5236 "*:\...\...\Local Settings\Temp\...\*" Madison Gas & Electric Co Operations Analyst -Data Center Services Information Management Systems [EMAIL PROTECTED] Office 608-252-7260 Larry Peifer <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 06/27/2005 03:07 PM Please respond to "ADSM: Dist Stor Manager" To: ADSM-L@VM.MARIST.EDU cc: Subject: Re: Exclude statement Well yes, EXCLUDE "*:\...\Local Settings\Temp\...\*" was my first choice also but it isn't working any other ideas? "Bos, Karel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 06/27/2005 09:30 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Exclude statement Hi, Just add EXCLUDE "*:\...\Local Settings\Temp\...\*" Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Larry Peifer Sent: maandag 27 juni 2005 18:13 To: ADSM-L@VM.MARIST.EDU Subject: Exclude statement The following files are failing during backup of our Win2003 node using TSM Client 5.3.0 and TSM Server 5.3.1 on AIX. \\sosim\c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\5236 \\sosim\c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\9544 \\sosim\c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\9860 I'm trying to exclude everything below the ...\Local Settings\Temp\ directory structure. So I've added this line to the dsm.opt file. EXCLUDE "*:\...\Local Settings\Temp\*" We're running the CAD to control the Scheduler and have SCHEDMODE set to polling; all of which is working fine. I've added other patterns for exclude processing and they are all working fine. It's just this one that I must be missing something with. Thanks in advance. Larry Peifer San Onofre Nuclear Generating Station UNIX System Admin [EMAIL PROTECTED]
Re: Exclude statement
Well yes, EXCLUDE "*:\...\Local Settings\Temp\...\*" was my first choice also but it isn't working any other ideas? "Bos, Karel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 06/27/2005 09:30 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Exclude statement Hi, Just add EXCLUDE "*:\...\Local Settings\Temp\...\*" Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Larry Peifer Sent: maandag 27 juni 2005 18:13 To: ADSM-L@VM.MARIST.EDU Subject: Exclude statement The following files are failing during backup of our Win2003 node using TSM Client 5.3.0 and TSM Server 5.3.1 on AIX. \\sosim\c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\5236 \\sosim\c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\9544 \\sosim\c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\9860 I'm trying to exclude everything below the ...\Local Settings\Temp\ directory structure. So I've added this line to the dsm.opt file. EXCLUDE "*:\...\Local Settings\Temp\*" We're running the CAD to control the Scheduler and have SCHEDMODE set to polling; all of which is working fine. I've added other patterns for exclude processing and they are all working fine. It's just this one that I must be missing something with. Thanks in advance. Larry Peifer San Onofre Nuclear Generating Station UNIX System Admin [EMAIL PROTECTED]
Re: Exclude statement
Hi, Just add EXCLUDE "*:\...\Local Settings\Temp\...\*" Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Larry Peifer Sent: maandag 27 juni 2005 18:13 To: ADSM-L@VM.MARIST.EDU Subject: Exclude statement The following files are failing during backup of our Win2003 node using TSM Client 5.3.0 and TSM Server 5.3.1 on AIX. \\sosim\c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\5236 \\sosim\c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\9544 \\sosim\c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\9860 I'm trying to exclude everything below the ...\Local Settings\Temp\ directory structure. So I've added this line to the dsm.opt file. EXCLUDE "*:\...\Local Settings\Temp\*" We're running the CAD to control the Scheduler and have SCHEDMODE set to polling; all of which is working fine. I've added other patterns for exclude processing and they are all working fine. It's just this one that I must be missing something with. Thanks in advance. Larry Peifer San Onofre Nuclear Generating Station UNIX System Admin [EMAIL PROTECTED]
Exclude statement
The following files are failing during backup of our Win2003 node using TSM Client 5.3.0 and TSM Server 5.3.1 on AIX. \\sosim\c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\5236 \\sosim\c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\9544 \\sosim\c$\Documents and Settings\jadmin\Local Settings\Temp\hsperfdata_jadmin\9860 I'm trying to exclude everything below the ...\Local Settings\Temp\ directory structure. So I've added this line to the dsm.opt file. EXCLUDE "*:\...\Local Settings\Temp\*" We're running the CAD to control the Scheduler and have SCHEDMODE set to polling; all of which is working fine. I've added other patterns for exclude processing and they are all working fine. It's just this one that I must be missing something with. Thanks in advance. Larry Peifer San Onofre Nuclear Generating Station UNIX System Admin [EMAIL PROTECTED]
Re: INCLUDE/EXCLUDE STATEMENT
Hi Gerardo, Unless I am mistaken (others correct me if I am wrong) The include/exclude list is read from the bottom up. By including /t/.../* you have also included the 'tuxedo' directory and subdirectories. The would therefore be subject to the rules of policy1. You should redo the order of the statements in your include/exclude file include /t/.../* policy1 include /t/tuxedo/bialog/.../ politicy2 include /t/tuxedo/procesos/.../ politicy2 As long as you do not change the include/exclude file you should not see any rebinding after the first backup. Remember 1 mgmtclass per file. The only way to apply different mgmtclasses to any given file is to define more than one server stanza in your dsm.sys file, and that can get ugly real quick if you're not careful Jim -Original Message- From: Gerardo Zapata [mailto:[EMAIL PROTECTED]] Sent: Monday, June 18, 2001 6:21 PM To: [EMAIL PROTECTED] Subject: INCLUDE/EXCLUDE STATEMENT 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 STATEMENT
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
Re: exclude statement
>ANS1036S Invalid option '/home/hosp.../data/.../*.TMP' Nothing in TSM generates more confusion than specifying exclusions with wildcards. We all dread having to deal with it, particularly as it doesn't exactly conform to any common wildcard conventions we're used to. The B/A manual says that wildcards are not allowed in the higher level portions of file path specifications, and this seems to bear that out. I think you're left to either specify each /home/hosp___ file system on its own Exclude statement or go with an Exclude of /home/.../data/.../*.TMP if that does what you need. The current Exclude capability is rather limited. Richard Sims, BU
Re: exclude statement
Kai, exclude /home/hosp.../data/.../*.TMP This syntax is invalid, use 'show inclexcl' will show you that. * # dsmc show inclexcl ANS1036S Invalid option '/home/hosp.../data/.../*.TMP' found in options file '/usr/tivoli/tsm/client/ba/bin/inclexcl' at line number : 5 Invalid entry : 'exclude /home/hosp.../data/.../*.TMP' ANS1042S Include/Exclude pattern has a '...' without beginning/ending directory delimiter ** - Estee >From: Kai Hintze <[EMAIL PROTECTED]> >Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: exclude statement >Date: Fri, 29 Sep 2000 14:44:56 + > > > Hi, > > > > Is this exclude statement valid? > > **inclexcl*** > > exclude /home/hosp*/data/.../*.TMP > > > >I believe it should be >exclude /home/hosp.../data/.../*.TMP > >The directory wildcard is "..." not "*". > >- Kai. > > > > I still getting this error : > > > > ***dsmsched.log > > 09/27/00 20:02:54 ANS1228E Sending of bject > > '/home/hospc3/data/doc/srvinst4.TMP' failed > > 09/27/00 20:02:54 ANS4005E Error processing > > '/home/hospc3/data/doc/srvinst4.TMP': file not found > > > > Thanks, > > Estee Chen (GLIC) > > _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.
Re: exclude statement
> Hi, > > Is this exclude statement valid? > **inclexcl*** > exclude /home/hosp*/data/.../*.TMP > I believe it should be exclude /home/hosp.../data/.../*.TMP The directory wildcard is "..." not "*". - Kai. > I still getting this error : > > ***dsmsched.log > 09/27/00 20:02:54 ANS1228E Sending of bject > '/home/hospc3/data/doc/srvinst4.TMP' failed > 09/27/00 20:02:54 ANS4005E Error processing > '/home/hospc3/data/doc/srvinst4.TMP': file not found > > Thanks, > Estee Chen (GLIC) >
