Re: [Veritas-bu] Some Help Please - Status 89 on Win2k3 Standard Server SSO San Media
We started to get lots and lots of status 89s on our hp-ux media server. It ended up being a memory leak and symantec gave us an eeb. should be fixed with 6.5.4 On Tue, Mar 17, 2009 at 11:50 AM, rusty.ma...@sungard.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/* 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. *WEAVER, Simon \(external\) simon.wea...@astrium.eads.net* Sent by: veritas-bu-boun...@mailman.eng.auburn.edu 03/16/2009 02:47 AM To VERITAS-BU@mailman.eng.auburn.edu cc Subject [Veritas-bu] Some Help Please - Status 89 on Win2k3 Standard Server SSO San Media 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@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Some Help Please - Status 89 on Win2k3 Standard Server SSO San Media
I dont! That was the point . Win2k3 Standard Server mate. ... as per subject line :-) And as per my email The docuemnts seem to show its related to a Solaris box, but this is a Windows SAN Media Server. Simon From: Steve Fogarty [mailto:steve.foga...@gmail.com] Sent: Tuesday, March 17, 2009 6:40 PM To: WEAVER, Simon (external) Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Some Help Please - Status 89 on Win2k3 Standard Server SSO San Media What version of Solaris are you running? Pre Solaris 10, you will have to set the shared memory parameters for NBU in /etc/system? bash-3.00# /usr/openv/netbackup/bin/admincmd/bperror -S 89 -r problems encountered during setup of shared memory The NetBackup processes use shared memory for some operations. This status is returned when an error is encountered in the initialization of the shared memory by the operating system's APIs. This is the normal recommendation. set msgsys:msginfo_msgmni=1024 set msgsys:msginfo_msgtql=1024 set semsys:seminfo_semmni=2048 set semsys:seminfo_semmns=2048 set semsys:seminfo_semopm=128 set shmsys:shminfo_shmmax=33554432 set shmsys:shminfo_shmmni=512 Steve On Mon, Mar 16, 2009 at 4:24 AM, WEAVER, Simon (external) simon.wea...@astrium.eads.net wrote: 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@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu 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@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Some Help Please - Status 89 on Win2k3 Standard Server SSO San Media
Hi This problem caught Symantec out, as the failures were 40, 41, 89 and 174 - very very odd, and happening with one client. After over 1.2gb of logs, the problem I found (not symantec) was due to a hardware problem, that DIDNT even report it had a problem ! Even so, since last night, the backups have been found. The Technote that Pete shared (and I had used prior to posting here) was of little help, and Symantec did respond by admitting that 89's on a Windows box are not fully documented or Technoted - they have to retrieve old records of similar reported issues :-( Shame. Simon From: rusty.ma...@sungard.com [mailto:rusty.ma...@sungard.com] Sent: Tuesday, March 17, 2009 5:51 PM To: WEAVER, Simon (external) Cc: VERITAS-BU@mailman.eng.auburn.edu; veritas-bu-boun...@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Some Help Please - Status 89 on Win2k3 Standard Server SSO San Media 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/ 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. WEAVER, Simon \(external\) simon.wea...@astrium.eads.net Sent by: veritas-bu-boun...@mailman.eng.auburn.edu 03/16/2009 02:47 AM To VERITAS-BU@mailman.eng.auburn.edu cc Subject [Veritas-bu] Some Help Please - Status 89 on Win2k3 Standard ServerSSO San Media 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@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu 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@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Some Help Please - Status 89 on Win2k3 Standard Server SSO San Media
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. WEAVER, Simon \(external\) simon.wea...@astrium.eads.net Sent by: veritas-bu-boun...@mailman.eng.auburn.edu 03/16/2009 02:47 AM To VERITAS-BU@mailman.eng.auburn.edu cc Subject [Veritas-bu] Some Help Please - Status 89 on Win2k3 Standard Server SSO San Media 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@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Some Help Please - Status 89 on Win2k3 Standard Server SSO San Media
What version of Solaris are you running? Pre Solaris 10, you will have to set the shared memory parameters for NBU in /etc/system? bash-3.00# /usr/openv/netbackup/bin/admincmd/bperror -S 89 -r problems encountered during setup of shared memory The NetBackup processes use shared memory for some operations. This status is returned when an error is encountered in the initialization of the shared memory by the operating system's APIs. This is the normal recommendation. set msgsys:msginfo_msgmni=1024 set msgsys:msginfo_msgtql=1024 set semsys:seminfo_semmni=2048 set semsys:seminfo_semmns=2048 set semsys:seminfo_semopm=128 set shmsys:shminfo_shmmax=33554432 set shmsys:shminfo_shmmni=512 Steve On Mon, Mar 16, 2009 at 4:24 AM, WEAVER, Simon (external) simon.wea...@astrium.eads.net wrote: 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@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Some Help Please - Status 89 on Win2k3 Standard Server SSO San Media
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@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
