I guess I have different questions than I have already seen. How is the memory usage on the node? Is it 32 or 64 bit? Is the agent hanging or working during the 9000 seconds? We have 2 systems that back 10M+ objects in an equally crazy number of directories and we have not seen the error you have. 1 machine is 32 bit and is using memory efficient disk cache and the other one is 64 bit and does not needs memory help. Both have static file systems during the backup. (That is another story.) We have seen a similar error to yours on 2003 servers with SP2. Take a look at Microsoft KB 948496 if the server is running SP2.
Andy Huebner -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of John C Dury Sent: Thursday, January 15, 2009 8:27 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] 2 Windows 2003 clients with huge # of files consistently failing I have two separate Windows 2003 boxes both running running v5.5.1.10 client that are both failing their incrementals every night. Both of these boxes have hundreds of thousand of files all spread into multiple directories. In fact, each day, a new directory is created and then multiple subdirectories are created under it and thousand of files in each of those subdirectories. The reason I say this is because I don't think it is a candidate for multiple virtual nodes because of the new directories that are created every day. I do have journaling turned on although it doesn't seem to help with the large number of files either as when I run an incremental manually,it takes forever and never seems to finish. I thought about doing image backups of the drive where the thousands of files live but when I tried it, it backed up about 14g and then just hung and never continued. I had to cancel it after waiting for an hour or so. What is my best strategy for dealing with these two boxes that are generating thousands of new files in new directories every day? The huge number of objects in the TSM DB are starting to cause quite a few problems with daily processing also as expiration is running longer and longer since I think it is choking on the number of objects. And to make it even weirder, they both fail incrementals at night and the only error I can find is: ANR0481W Session 16603 for node <SERVERNAME> (WinNT) terminated - client did not respond within 9000 seconds. (SESSION: 16603) I'm starting to think that TSM is just not the backup solution for either of these boxes. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.