Hi, Andy. I've included some text from the 3.1 and 4.2 Windows client manuals. It looks like selective backup behavior regarding exclude.dir has been consistent. A selective backup should be able to backup files excluded by exclude.dir. I didn't see any notice about this kind of change in the readme. Not to be a noodge, but if you're seeing otherwise with the 4.2.1 client, I feel that should either be reported as an APAR or, if it's a planned change in functionality, that should be changed in the documentation.
Thanks, Alex Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail 4.2 manual Selective Backup Requirements When you request a selective backup, TSM backs up a file if all of the following requirements are met: The file is not specified on an exclude statement in your include-exclude list. If you do not have an include-exclude list, all files are considered for backup. Exclude option excerpt: exclude.dir Excludes a directory, its files, and all its subdirectories and their files from backup services. The exclude.dir option works only if the excluded directory is a subdirectory. Use this option to exclude a portion of your data in which no underlying files need to be backed up. When you exclude a directory, you can still back up specific files within that directory using a selective backup. However, the next time you perform an incremental backup, these backup versions are expired. 3.1 manual When you request a selective backup, ADSM backs up a file if all of the following requirements are met: The file is not specified on an exclude statement in your include-exclude list. If you do not have an include-exclude list, all files are considered for backup. Exclude option excerpt: .dir Excludes an entire directory from backup services. The pattern is used to find matching directory names. If a matching directory is found, that directory, its files, and all its subdirectories and their files are excluded from backup services. When you exclude a directory, you can still back up specific files within that directory, using selective backup. -----Original Message----- From: Andrew Raibeck [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 28, 2001 7:59 AM To: [EMAIL PROTECTED] Subject: Re: Selective backup and Incl/excl Interesting... I guess my wish *was* granted! I just tested this with 4.2.1 (on Windows) and it looks like the item I warned about in my prior post is no longer an issue.... at least at the 4.2.1 level. At 4.2.1, when I try to do a SELECTIVE backup on files or directories in a directory for which I coded EXCLUDE.DIR, it refuses to back it up. That's good! Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS 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. John Naylor <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/28/2001 08:20 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: Selective backup and Incl/excl Andy, Yes I want exclude.dir to work during a selective full backup ie. I do not want it to traverse certain directory structures with huge numbers of small files. My concern was that the client backup manual for netware seems to suggest that exclude.dir does not work for selective backups. Is the manual actually meaning that exclude.dir does not work when it says "When you run a selective backup, TSM also backs up all directory information. You can exclude the files within a directory, but you cannot exclude a directory from being backed up." Thanks, John Andrew Raibeck <[EMAIL PROTECTED]> on 11/28/2001 01:25:27 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: (bcc: John Naylor/HAV/SSE) Subject: Re: Selective backup and Incl/excl During incremental backup, EXCLUDE.DIR causes TSM to not even bother traversing directory(ies) that match the given pattern. For example suppose you have: EXCLUDE.DIR C:\MYDIR EXCLUDE.DIR *:\...\TEMP* These will bypass processing of directory C:\MYDIR and any directories on any volume where the directory name begins with TEMP (i.e. D:\XYZ\TEMPORARYFILES, C:\TEMP, etc.). Thus neither files nor directories matching the above patterns are backed up. When TSM is processing the include/exclude list, EXCLUDE.DIR is always processed first, regardless of position within dsm.opt. EXCLUDE.DIR C:\MYDIR INCLUDE C:\MYDIR\FILE*.TXT and INCLUDE C:\MYDIR\FILE*.TXT EXCLUDE.DIR C:\MYDIR are exactly the same: the EXCLUDE.DIR for C:\MYDIR will be matched first, so regardless of the position of the INCLUDE, no files or subdirectories in C:\MYDIR will be backed up. Warning: EXCLUDE.DIR doesn't stop you from selectively backing up files in C:\MYDIR. So DSMC SELECTIVE C:\MYDIR\ -SUBDIR=YES will back up the files and directories in C:\MYDIR. However, during the next incremental backup of C:, any backup versions of files in C:\MYDIR will be expired. My own opinion: any attempt to do a SELECTIVE backup on C:\MYDIR should be met with a message saying the files are excluded; but for now, this is a known limitation. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS 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. John Naylor <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/28/2001 03:14 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Selective backup and Incl/excl Thoughts on this welcome. Client manual says re selective backup When you run a selective backup, TSM also backs up all directory information. You can exclude the files within a directory, but you cannot exclude a directory from being backed up. So how does it treat exclude.dir in the dsm.opt Is it ignored completely and all the files backed up or is it honoured to the extent that the files are not backed up, only the directory information. Thanks ********************************************************************** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **********************************************************************
