Veritas-bu

[Veritas-bu] Failures with status code 219

2002-10-29 15:36:07
Subject: [Veritas-bu] Failures with status code 219
From: joe.lamanna AT citigroup DOT com (La Manna, Joe [IT])
Date: Tue, 29 Oct 2002 15:36:07 -0500
what is your tcp_close_wait_interval set to ? - you may want to reduce it so
the sockets free
sooner.
 
 

-----Original Message-----
From: Koduru, Kishan [mailto:KKoduru AT ea DOT com]
Sent: Tuesday, October 29, 2002 3:24 PM
To: Donaldson, Mark; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Failures with status code 219



There are no duplications going on the server. Also, the backups were
working fine till yesterday. When I do a netstat -a| grep bp I see lot of
processes in TIME_WAIT state, which is not the case on other NBU servers.
Any ideas??

 

Thanks

Kishan

 

-----Original Message-----
From: Donaldson, Mark [mailto:Mark.Donaldson AT experianems DOT com] 
Sent: Tuesday, October 29, 2002 9:36 AM
To: Koduru, Kishan; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Failures with status code 219

 

I had this problem a lot with v3.4 during duplications, too.  The
duplication doesn't register itself well with the scheduler so the scheduler
tries to run backups unaware that the drives are taken up.  You should check
your general storage unit availability, too.

I reduced the 219's due to duplication by adding the following to bp.conf
(from a previous post): 

----------------- 

I decided to send a quick summary since others have told me that they were
having similar issues.  My original posting is below.

I've managed to make the error 213's go away.  

Step one: Change any classes using "Any Available" as a storage pool to
point directly to the tape pool.  The settings on the disk unit weren't
going to let it be picked anyway (it's set to on-demand only).  This seemed
to change a 213 to a 219.

Step two: Add this to the bp.conf file: 
  QUEUE_ON_ERROR 
  WAIT_IN_QUEUE 
  TIMEOUT_IN_QUEUE = 43200 

..which seems to combat the 219's by getting them to resubmit on error. 

Backups seem more stable. 

-Mark 
-----Original Message----- 
From: Koduru, Kishan [ mailto:KKoduru AT ea DOT com <mailto:KKoduru AT ea DOT 
com> ] 
Sent: Tuesday, October 29, 2002 9:09 AM 
To: veritas-bu AT mailman.eng.auburn DOT edu 
Subject: [Veritas-bu] Failures with status code 219 

 

All of my backups started failing with status code 219. Anyone has an idea
why? All help is appreciated. 
  
NBU 3.4 
Sol 2.6 
  
Thanks 
Kishan 


<Prev in Thread] Current Thread [Next in Thread>