I have cured this problem on several machines by switching to Journal based
backup. I am not quite sure why it works, but some of my RC 1450 errors
disappeared. We also eliminated some boot switches having to do with memory,
-3Gb, if I remember right.
In the end, there is an upper limit to how many files TSM can handle within
Windows memory limitations. Are you using 64 bit Windows 2003?
To solve the myriad of issues with large file servers, we have moved them all
to NetApp and use Snapshots and Snapmirror for backup. Works slick!
FYI, there are also some post SP2 Hot fixes for VSS that address a memory leak
in VSS that you may consider deploying. This is probably not related, but I
put it out there. It got rid of a rash of VSS E-OUTOFMEMORY errors for us.
Orville L. Lantto
________________________________
From: ADSM: Dist Stor Manager on behalf of Steven Harris
Sent: Wed 4/30/2008 20:35
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] ANS9999E Win32 RC 1450
Hi All
I have a new client with an enormous file server, running Windows 2003. We
have had a string of problems, most have been fixed by upgrade to TSM
client 5.5.0.4 and OS upgrade to SP2. We are using
MEMORYEFFICIENTBACKUP=DISKCACHE but still get
ANS9999E Win32 RC 1450 as noted in
http://www-1.ibm.com/support/docview.wss?uid=swg21251903
Pointing at the Faulty OS or poor implementation doesn't solve the problem.
This is the client's main file server and hasn't yet had a clean backup.
Has anyone else seen this issue, and developed a workaround that you'd
like to share? All I can think of at this point is a series of backups of
various subtrees,
Thanks
Steve.
Steven Harris
TSM Admin, Sydney Australia
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you have received this email in error please notify the system manager. This
message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail.
|
