ADSM-L

Re: EXCLUDE / Client Opt and 2K3

2003-10-15 17:48:49
Subject: Re: EXCLUDE / Client Opt and 2K3
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 15 Oct 2003 15:47:03 -0600
That is correct.

Also note that ntbackup lets you modify this list, so be careful doing
that... if you go to the "Tools/Options" menu and make changes to the
"Exclude Files" tab, that actually modifies the "FilesNotToBackup" subkey
values.

In other words, there is no fixed Exclude list that covers all Windows
OSes, nor can we even assume that the list is fixed for all instances of a
given Windows OS.

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

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




Simeon Johnston <simeonuj AT INDIVISUALLEARNING DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/15/2003 14:32
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: EXCLUDE / Client Opt and 2K3


Also note that, if you use the built-in backup/restore function of
windows2k/XP/Server it also keys off of those registry settings.
HKLM\System\CurrentControlSet\Control\BackupRestore\FilesNotToBackup
It is not something that TSM sets up.  It is installed with the system.
I think it would also be different depending on what OS you installed as
well i.e. 2k reg would have different settings than the XP reg.  That
goes double for Win (whatever) Server.

Maybe I'm wrong but that's what I've experienced recently.

sim

> -----Original Message-----
> From: Andrew Raibeck [mailto:storman AT US.IBM DOT COM]
> Sent: Wednesday, October 15, 2003 3:57 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: EXCLUDE / Client Opt and 2K3
>
>
> I don't recall the client level off-hand, but it's been there
> quite a while -- *at least* since 4.2.
>
> Why hasn't it been an issue in the past? I don't know enough
> about your environment to give you a definitive answer to
> that question. I guess you could start with an examination of
> QUERY INCLEXCL (might need SHOW INCLEXCL instead of QUERY
> INCLEXCL on pre-5.1 clients) output on machines that don't
> get the message versus machines that do get the message.
>
> Where can you get the list? Same answer as above. "dsmc query
> inclexcl" will show you at run-time what is excluded ("Source
> file" column says "Operating System").
>
> Regards,
>
> Andy

<Prev in Thread] Current Thread [Next in Thread>