ADSM-L

Re: [ADSM-L] TSM Exclude/Expiration

2010-03-26 15:57:11
Subject: Re: [ADSM-L] TSM Exclude/Expiration
From: Richard Sims <rbs AT BU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 26 Mar 2010 15:55:54 -0400
On Mar 26, 2010, at 2:05 PM, Jones, Eric J wrote:

> Good Afternoon.
> We have a TSM AIX server running TSM 5.4 and a Windows 2008 running TSM 
> client 5.5
> We currently have 53 million files on a single partition and plan to break it 
> up into 3 partitions to help with backup times, etc..
> The plan was to move about 1/3 of the data to the other partition, leave the 
> current data where is it for now and "Exclude" it from the backups on the 
> original partition.  Can I assume since around 16-17 million files will be 
> excluded from the original backup that the backup time will improve or does 
> it still look at those files during the inspection until they are deleted.   
> We'll be backing up the new partitions with a separate backup session.   I 
> was fairly confident it would skip them during the inspection but some 
> questions came up and I wanted to verify.
> Also will TSM expire the files once I delete them from the original partition 
> and remove the "Exclude" or will there be any issues since it has not see the 
> files due to the exclude in the most recent backups.

Exclude.Dir and Exclude.FS preclude entry into the specified areas when the 
backup is by file system: other forms of Exclude involve entry and scanning and 
attendant overhead.  However, expiration effect rules for the two are different 
(see the manual).  You may want to commit to the elimination of the 1/3 from 
the original file system, with perhaps a safety Archive of them beforehand.

   Richard Sims

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