Actually, this is not entirely true. * and *.* are NOT exactly the same.
*.* means any file name with the '.' character anywhere in the name.
* means any file name.
So if you have this:
exclude c:\Mydir\*.*
And you have these files in C:\Mydir:
abc.txt
123.txt
myfile
Then myfile will be backed up, but abc.txt and 123.txt will be excluded.
If you want to exclude *all* files (which is usually the intent), you need
to specify this:
exclude c:\Mydir\*
Regards,
Andy
Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."
Hervé CHIBOIS <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 03/19/2001 02:59:38
PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Archive (inspected) vs Backup (inspected)
Hello there
some hints...
re-read your REGEXP definition, you do NOT need to put many lines
* and *.* are EXACTLY the same for *SM
try to use exclude.dir instead of /.../, *SM won't store directory
definitions.
rv
----- Original Message -----
From: "Gerrit van Zyl" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 19, 2001 12:13 PM
Subject: Re: Archive (inspected) vs Backup (inspected)
> Steffan,
>
> No, not at all. It is the standard exclude statements:
>
> Exclude "*:\macintosh volume\*"
> Exclude "*:\macintosh volume\*.*"
> Exclude "*:\macintosh volume\...\*"
> Exclude "*:\macintosh volume\...\*.*"
> Exclude "*:\microsoft uam volume\*"
> Exclude "*:\microsoft uam volume\*.*"
> 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\...\*
>
> Regards
> Gerrit
>
> arhoads wrote:
>
> > Gerrit,
> >
> > Does your include-exclude file exclude ~ 50,000 files?
> >
> > Steffan
> >
> > Gerrit van Zyl wrote:
> > >
> > > Steffan,
> > >
> > > Why would ADSM skip 50000 files for archiving. Their is about 20
files that
> > > gives errors (open), the rest not.
> > >
> > > number of objects inspected: 461,739
> > > number of objects archived: 411,368
> > >
> > > The schedule is to archive c: d: e:
> > >
> > > Thanks and regards
> > > Gerrit van Zyl
> > >
> > > arhoads wrote:
> > >
> > > > Gerrit,
> > > >
> > > > Yes. Archive is not using the Include-Exclude list.
> > > >
> > > > Steffan
> > > >
> > > > Gerrit van Zyl wrote:
> > > > >
> > > > > Hi all TSM'ers,
> > > > >
> > > > > TSM Client 3.1.0.8 on NT
> > > > > TSM Server 3.1.2.58 on AIX
> > > > >
> > > > > I have the following scenario and hope someone can explain this
to
me.
> > > > > When archiving we get the following:
> > > > >
> > > > > 03/11/2001 03:54:57 ANE4952I (Session: 7758, Node: NTSRV01)
Total
> > > > > number of objects inspected: 461,739
> > > > > 03/11/2001 03:54:57 ANE4953I (Session: 7758, Node: NTSRV01)
Total
> > > > > number of objects archived: 411,368
> > > > >
> > > > > When we do a incremental backup we get the following:
> > > > >
> > > > > 03/12/2001 22:57:23 ANE4952I (Session: 8193, Node: NTSRV01)
Total
> > > > > number of objects inspected: 410,653
> > > > > 03/12/2001 22:57:23 ANE4954I (Session: 8193, Node: NTSRV01)
Total
> > > > > number of objects backed up: 3,414
> > > > >
> > > > > Why is there suce a huge difference between objects inspected in
the two
> > > > > cases (50000 objects)? The files were not deleted!! This is the
same
> > > > > everytime.
> > > > >
> > > > > Is archiving inspecting files differently than incremental
backup?
> > > > >
> > > > > Thanks and regards.
> > > > > Gerrit van Zyl
> > > > >
> > > > > IT Consultant
> > > > > Faritec (Pty) Ltd
>
> --
> Gerrit van Zyl
>
> IT Consultant
> Faritec (Pty) Ltd
>
> "This message may contain information which is confidential, private or
> privileged in nature. If you are not the intended recipient, you may not
> peruse, use, disseminate, distribute or copy this message or file which
> is attached to this message. If you have received this message in error,
> please notify the sender immediately by e-mail, facsimile or telephone
> and thereafter return and/or destroy the original message.
> Any views of this communication are those of the sender except where the
> sender specifically states them to be those of Faritec (Proprietary)
> Limited ("Faritec") and/or Midrange Distribution Services (Pty) Ltd.
> Please note that the recipient must scan this e-mail and any attached
> files for viruses and the like. While we do everything possible to
> protect information from viruses, Faritec accepts no liability of
> whatever nature for any loss, liability, damage or expense resulting
> directly or indirectly from the access and/or downloading of any files
> which are attached to this e-mail message."
>
