From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Nathan Kippen
Sent: Thursday, March 19, 2009
1:06 PM
To: Rusty.Major AT sungard DOT com
Cc: WEAVER, Simon (external);
VERITAS-BU AT mailman.eng.auburn DOT edu; veritas-bu-bounces AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Some
Help Please - Status 89 on Win2k3 StandardServer SSO San Media
On Tue, Mar 17, 2009 at 11:50 AM, <Rusty.Major AT sungard DOT com> wrote:
Simon,
89
is a shared memory error, usually seen on a Solaris box that is not configured
with the correct mem settings, or is configured to use too much memory. 41's
are usually from the network being ripped away during the backup, usually a
shutdown or nic failure of some sort on the client.
It
sounds to me like you might have a hardware or client OS related issue. Have
you looked in the event log on that client?
Rusty Major, MCSE, BCFP, VCS ▪ Sr.
Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge Suite 200, Houston TX
77079 ▪ 281-584-4693
Keeping
People and Information Connected® ▪ http://availability.sungard.com/
P Think before you print
CONFIDENTIALITY:
This e-mail (including any attachments) may contain confidential, proprietary
and privileged information, and unauthorized disclosure or use is
prohibited. If you received this e-mail in error, please notify the
sender and delete this e-mail from your system.
All
hope I can have some help here. Logged a call 2 days ago with Symantec, due to
the problem with this Server.
NBU 5.1 MP5 Master and 6 SSO SAN Media Servers
1 Particular Server had a problem Thursday night with backup
issues. It was reporting status codes of 41 and 89. Since then, the Full Backup
ran and this failed with 89.
The docuemnts seem to show its related to a Solaris box, but
this is a Windows SAN Media Server. To the very best, no one has altered or
changed anything on this box.
The problem first started with restores causing the Server to
lose what we call "RPC" connectivity. The only way to get the Server
operating was to do a Power Down and Power On.
Since then, its become worse. I have sent over 800mb logs
now, and I wanted to post this out on the Forum in case anyone else has seen
this.
I still have a job running (saying its going to take 227,892
minutes to complete now!)
If anyone has any ideas, truly appreciated.
Regards
Simon
|
This email (including any attachments) may contain
confidential
and/or privileged information or information
otherwise protected
from disclosure. If you are not the intended
recipient, please
notify the sender immediately, do not copy this
message or any
attachments and do not use it for any purpose or
disclose its
content to any person, but delete this message
and any attachments
from your system. Astrium disclaims any and all
liability if this
email transmission was virus corrupted, altered
or falsified.
-o-
Astrium Limited, Registered in England and Wales No. 2449259
Registered Office:
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS,
England
|
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
