That's great, thanks for the help.
Farren Minns
Solaris System Admin / Oracle DBA
IT - Hosting Services
|+------------------------------+-----------------------------------------|
|| Andrew Raibeck | |
|| <storman AT US.IBM DOT COM> |
|
|| Sent by: "ADSM: Dist Stor | To: ADSM-L AT VM.MARIST DOT EDU
|
|| Manager" | cc: |
|| <ADSM-L AT VM.MARIST DOT EDU> | Subject: Re: [ADSM-L]
|
|| | Question about excludes and expiration|
|| 27/04/2005 16:38 | |
|| Please respond to "ADSM: | |
|| Dist Stor Manager" | |
|+------------------------------+-----------------------------------------|
The next time TSM runs incremental backup against the file system, it will
not consider them eligible for backup. Rather, it will treat the files as
if they no longer exist on the machine: they will be expired on the TSM
server, and from then on, the server side copy group settings VERDELETED
and RETONLY will go into effect.
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.
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-04-27
08:14:40:
> Hi TSMers
>
> Running TSM 5.1.6.2 on Solaris and backing up a number of UNIX and
Windows
> 2000 clients.
>
> Quick question for you. If I have been backing up a large directory with
> many sub directories and files, and those files have changed a number of
> times so that I have a lot of active and inactive copies, what happens
if I
> then exclude that entire directory from backup?
>
> Do some or all of those files undergo expiration or does TSM just ignore
> them for good?
>
> Thanks
>
> Farren Minns
> Solaris System Admin / Oracle DBA
> IT - Hosting Services
>
> John Wiley & Sons, Ltd
>
>
> ######################################################################
> The information contained in this e-mail and any subsequent
> correspondence is private and confidential and intended solely
> for the named recipient(s). If you are not a named recipient,
> you must not copy, distribute, or disseminate the information,
> open any attachment, or take any action in reliance on it. If you
> have received the e-mail in error, please notify the sender and delete
> the e-mail.
>
> Any views or opinions expressed in this e-mail are those of the
> individual sender, unless otherwise stated. Although this e-mail has
> been scanned for viruses you should rely on your own virus check, as
> the sender accepts no liability for any damage arising out of any bug
> or virus infection.
> ######################################################################
######################################################################
The information contained in this e-mail and any subsequent
correspondence is private and confidential and intended solely
for the named recipient(s). If you are not a named recipient,
you must not copy, distribute, or disseminate the information,
open any attachment, or take any action in reliance on it. If you
have received the e-mail in error, please notify the sender and delete
the e-mail.
Any views or opinions expressed in this e-mail are those of the
individual sender, unless otherwise stated. Although this e-mail has
been scanned for viruses you should rely on your own virus check, as
the sender accepts no liability for any damage arising out of any bug
or virus infection.
######################################################################
|
