Steven,
I feel your pain. Here are the steps you can take to temporarily ease
the pain while someone architects the real solution.
1. what you have done so far is correct
2. make sure you have a good list of excludes, especially directory
excludes, to reduce what has to be backed up
3. implement journal backups if you haven't already
4. given the problem of getting the backup to complete (which has to
happen in order for the journals to become valid, and therefor,
helpful), you will likely need to initially backup 1 volume at a time
manually. The caveat is that each time the server gets rebooted, the
journals will reset and you will probably need to do this again.
5. if there are candidates for subfile backup (e.g. .pst .mdb etc)
implement it
These are all steps we had to take to get our aging, bloated windows
fileservers to limp along while we came up with a new scheme.
Good luck,
Steve Schaub
Systems Engineer, Windows
Blue Cross Blue Shield of Tennessee
423-535-6574 (desk)
423-785-7347 (mobile)
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Steven Harris
Sent: Wednesday, April 30, 2008 9:35 PM
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
Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer: http://www.bcbst.com/email_disclaimer.shtm
|
