If you traverse the adsm.sys directory, you will find that WMI and EVENTLOG are directories; hence they are not covered by the exclude. See the APAR I mentioned in my post for more info on the skipped file part.
The exclude for adsm.sys had *better* be in your q inclexcl output! :-) Take a closer look, or post the output from q inclexcl here. You should have a line that looks like this: Excl All C:\adsm.sys\...\* Operating System You may safely add exclude.dir c:\adsm.sys to your include/exclude list to avoid the annoying skipped files problem. 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. TSM_User <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 05/07/2004 15:45 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: ADSM.SYS folder needed for restores? Andy, All of our Windows 2003 servers (running the V5.2.2.9 client) report skipped files for \\server\c$\\adsm.sys\WMI, \\server\c$\adsm.sys\IIS and \\server\c$\adsm.sys\EVENTLOG. I had always thought there was an implicit exclude of that folder as you said but when I ran q inclexcl I didn't see it. Maybe it isn't shown. Still I was wondering if you could explain why if the files are excluded they show up as skipped files? I was wondering if I could just enter my own exclude in the dsm.opt and now I see that I can based on your note so I will do that. Thanks Andrew Raibeck <[EMAIL PROTECTED]> wrote: Yes, adsm.sys is always backed up as part of the systemstate and systemservices objects. For W2K+3 this directory includes VSS metadata that we need to back up. During backup of the c: drive, the client will traverse the adsm.sys tree and back up the directories contained therein. However, there is an implicit "exclude c:\adsm.sys\...\*" in the client, so the *files* will be skipped, unless you overrode with an include. APAR IC40016 asks that this exclude be changed to exclude.dir. Since backup of this directory is already covered in systemstate/systemservices backup (which is *not* affected by the exclude), there is no need to include adsm.sys as part of the c: drive backup. Therefore you may safely use "exclude.dir c:\adsm.sys" to suppress traversal of the tree during c: backup processing. 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. "Spearman, Wayne" Sent by: "ADSM: Dist Stor Manager" 05/07/2004 08:40 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject ADSM.SYS folder needed for restores? I'm not a Windows Admin. Does the adsm.sys folder need to be backed up for Windows 2003? I thought this folder was needed for restoring the server the registry Thanks, Wayne ----------------------------------------- This message and any included attachments are from NOVANT HEALTH INC. and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail. Thank you. --------------------------------- Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs
