Hi Thomas,
First, I do not disagree that our documentation is sometimes less than
clear. While it does not explicitly state "you need two include
statements", a careful reading of the information in chapter 9, the
"Include options" section, will yield the information. (However, I will
feed this back to the developers who work on our manuals for their
consideration.)
For example, at the beginning of the section, note the 4th bullet below,
which implies that "include" is not quite the same as "include.subfile":
--------------------
The include options specify any of the following:
* Objects within a broad group of excluded objects that you want to
include for backup, archive, and image services.
* Files that are included for backup or archive processing that you want
to include for encryption processing.
* Files that are included for backup or archive processing that you also
want to include for compression processing.
* Files that are included for backup processing that you also want to
include for adaptive subfile backup processing.
* Objects to which you want to assign a specific management class.
* A management class to assign to all objects to which you do not
explicitly assign a management class.
--------------------
Then a little further down:
--------------------
Tivoli Storage Manager processes exclude.dir and other include-exclude
statements first. Tivoli Storage Manager then considers any
include.compression, include.encrypt and include.subfile statements. For
example, consider the following include-exclude list:
--------------------
Then later on in the "syntax" section, it says to use "include" to bind
files to management classes:
--------------------
include, include.backup, include.file
These options are equivalent. Use these options to include files or assign
management classes for backup processing.
--------------------
And a little further down in the same section, it says that you use
"include.subfile" to include files for adaptive subfile backup:
--------------------
include.subfile
Includes files for adaptive subfile backup processing. This option does
not apply to archive processing. This option is valid for all Windows
clients.
--------------------
If you also look up the "Exclude options" section in chapter 9, there is a
subsection, "Adaptive subfile backup processing" that has similar
information.
Best regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
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" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-10-11
23:34:25:
> Thanks a lot for your explanation!
> I thought it had to be something like that.
> Do you think the 5.3 Windows Backup-Archive Clients Installation and
> User's Guide
> is clear enough about that? I tried to find the page in the manual
> that states that
> you need two include statements to get the job done.
>
> Thanks and greetings from Austria
> Thomas
>
> -----Ursprüngliche Nachricht-----
> Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im
> Auftrag von Andrew Raibeck
> Gesendet: Dienstag, 11. Oktober 2005 20:25
> An: ADSM-L AT VM.MARIST DOT EDU
> Betreff: Re: [ADSM-L] include.subfile and management class
>
>
> include.subfile and exclude.subfile are used only to include/exclude
files
> from *subfile* processing. They don't affect whether the files are
backed
> up at all, nor do they affect management class binding.
>
> When enabled for subfile backup, all files are eligible for the subfile
> treatment unless you explicitly exculde them via exclude.subfile.
>
> If you are not excluding files from subfile backup processing, then you
> can just use include to bind the files to the desired management class.
> For example:
>
> include c:\myudir\*.doc mymgmtclass
>
> If you are using exclude.subfile in a way that requires you to also use
> include.subfile, then you'll need to use both include and
include.subfile.
> For example:
>
> include c:\mydir\...\* mymgmtclass
> exclude.subfile c:\mydir\...\*
> include.subfile c:\mydir\...\*.doc
>
> In the above example:
>
> - all *.doc files in c:\mydir are eligible for subfile backup
processing.
> - all other files in c:\mydir will be backed up with normal
(non-subfile)
> processing.
> - all files in c:\mydir will be bound to mymgmtclass
>
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Development
> Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
> Internet e-mail: storman AT us.ibm DOT com
>
> 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" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-10-11
> 10:32:44:
>
> > Hi TSM-ers,
> >
> > TSM 5.1.5.9 client for Windows doesn't seem to use the management
class
> > in
> >
> > INCLUDE.SUBFILE G:\MailArchiv\rt\*.pst mailarchive
> >
> > whereas in
> >
> > INCLUDE G:\MailArchiv\rt\*.pst mailarchive
> >
> > it does.
> > Is there anything obvious I don't see or understand?
> >
> > Thanks in advance
> >
> > Thomas Rupp
|
