Veritas-bu

[Veritas-bu] Allocation failed error

2007-02-05 23:21:17
Subject: [Veritas-bu] Allocation failed error
From: Eric.Ljungblad at CopleyPress.com (Eric Ljungblad)
Date: Mon, 5 Feb 2007 20:21:17 -0800
Is this a cluster with alternating nodes?


-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu on behalf of Jeff Lightner
Sent: Mon 2/5/2007 1:29 PM
To: Jeff Cleverley; veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Allocation failed error
 
Left out:   HP-UX has kernel parameters (swapchunks, maxswchunks...)
that control how large swap can get.  If you exceed the amount of swap
these kernel parameters allow for it will just allocate the amount of
swap it can and won't give much complaint.   You may want to check to
see if you have already allocated enough swap but aren't able to use it
all due to the above parameters.

-----Original Message-----
From: Jeff Lightner 
Sent: Monday, February 05, 2007 4:25 PM
To: 'Jeff Cleverley'; veritas-bu at mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Allocation failed error

I believe the memory is for the media server itself assuming the tape
mounted there.   The master would presumably only need enough memory to
issue commands - it is the actual data handling of the tape restore
eating up memory.

Was the tape originally backed up on the media server you're trying to
restore to?  If not you may unintentionally be doing a network restore
where it is actually mounting on the original server and restoring from
there via network.   To get around this you set the
FORCE_RESTORE_MEDIA_SERVER option in bp.conf e.g.
FORCE_RESTORE_MEDIA_SERVER = <original media/master> <target
media/master>.  You then have to run bpadm g (global) m (modify) d
(notify request daemon) to reread the bp.conf - this is done on the
master server.

As to swap - my rule of thumb has always been 2 x Physical Memory.  With
11.x theoretically you don't need that much but I always do it for the
virtual memory allowances it makes.

We do this kind of cross server restore in our HP-UX environment on a
disgustingly regular basis mainly for database refreshes.

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Jeff
Cleverley
Sent: Monday, February 05, 2007 3:56 PM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] Allocation failed error

Greetings,

I'm running 5.1 mp4 in a hpux environment.  I have a master and 6 SAN 
media server systems.  When I tried to do a restore of a large file 
system on a media server this past weekend, the job failed with status 
code 10.  The master server has the catalog database and the restore was

being performed from a media server to a new file system on the same 
media server.  The book states that status 10 means you need to add more

memory or swap. 

In a case like this, do I need to add the memory to the master or the 
media server?  Is there some type of formula that tells how much 
memory/swap will be needed?  This one file system in particular has over

8 million inodes in use.  We have several others like it.

I don't remember what the settings were, but we did make sure that we 
had the recommended tuning parameters for Veritas.  The hardware on both

servers is hpux 11.11, rp5470, 4 gig of ram.

Thanks,

Jeff
_______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20070205/4857e8fb/attachment.html

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