Del, Thanks, this has done the trick. We were using 1024 x 3. We are going to try something like 256 x 3 and see what happens. We are going to see if there is a memory leak causing the problem or we were using the wrong buffer size causing fragmentation issues. We will try to post some results.
Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -----Original Message----- From: Del Hoobler [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 25, 2002 6:15 AM To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange 402 Errors: Second Try > We are experiencing the backup failed 402 error condition nightly on > at least 1 of our Exchange Servers. We are running: > The latest TDP for Exchange > Exchange 5.5 SP4 > NT 4 60a > TSM Server > AIX 4.3.3 ML10 > TSM 4.2.2.12 > Gigabit > The NT hardware is Gigabit ethernet, ESS Disk with the latest SDD > driver, Magstar Tape. LAN Backup. > > The 402 error condition is related to file handle or other memory resource > shortages in Exchange or NT. Essentially, until we reboot the box or cycle > the Exchange service the problem is around and no backups will run. > The funny piece is it can back up the directory but not the > information stores. Paul, One thing to try in order to get your backups working is to change your buffersize to 64K. That is: TDPEXCC SET BUFFERSIZE=64 This reduces the amount of memory needed by the Exchange Information Store for the backup. Most of the time we have seen this, Microsoft has become involved and used various performance tools (like PERFMON for one) to find out what process is eating all of the resources. Thanks, Del ---------------------------------------------------- Del Hoobler IBM Corporation [EMAIL PROTECTED] - Never cut what can be untied. - Commit yourself to constant improvement.
