On Thu, 12 Feb 2004 09:03:19 -0700 Andrew Raibeck <[EMAIL PROTECTED]> wrote:
> Gretchen, I don't understand the following: > > > Prior to the v4.2 client, you could simply exclude the files on the > > client side and the files would be expired. This probably led to > > unpleasant/unexpected results, so this doesn't work anymore and the > > client expire was introduced. > > What unpleasant/unexpected results are you referring to? If no longer wish > to back up files in c:\junk and it's subdirectories, then I don't see why > using EXCLUDE.DIR wouldn't work. You could use a client options set to do > this. > true, but the files remain on the server, and are not expired when using exclude.dir.... > Regards, > > Andy > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Development > Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] > Internet e-mail: [EMAIL PROTECTED] > > The only dumb question is the one that goes unasked. > The command line is your friend. > "Good enough" is the enemy of excellence. > > > > "Gretchen L. Thiele" <[EMAIL PROTECTED]> > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > 02/12/2004 08:51 > Please respond to > "ADSM: Dist Stor Manager" > > > To > [EMAIL PROTECTED] > cc > > Subject > Client/Server Expiration Problem > > > > > > > Due to a change in policy (and limited storage), we're going to limit > what we back up. The problem lies in how to 'expire' the files on the > server without re-backing up the data, while maintaining deleted files > for the duration of retonly. While we could rename the filespace and > implement the new policy, this is a lot of administrative work and I > don't think we would be able to accomodate the data (storage and > bandwidth). > > Prior to the v4.2 client, you could simply exclude the files on the > client side and the files would be expired. This probably led to > unpleasant/unexpected results, so this doesn't work anymore and the > client expire was introduced. > > THE PROBLEM: I need to expire subdirectories without explicitly > naming them. The client expire command only expires the named > subdirectory, ignoring any include/exclude statements in the config > files and not accepting -subdir=yes on the command line. If I > enter 'expire c:\junk\*', I expire all of the files in the junk > directory, but none of the files in any subdirectories will be > expired. Wildcards, such as c:\junk\...\*, aren't supported, and > the -filelist option requires explicit filenames and/or directories. > > Since I need to run this from the server as a scheduled command and > it's not feasible to get the precise list of subdirectories for each > of 5,000 clients, I'm stumped. Am I missing something? > > Server is AIX 5.1, TSM 5.2.2.1 and the clients are Windows (Win9x, > Win2K, WinXP) with TSM 5.x.x.x (will work on Unix nodes after these > are done). > > Gretchen Thiele > Princeton University -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 8008 Fax. +31 20 668 3167 "I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end." -- Douglas Adams
