Veritas-bu

Re: [Veritas-bu] Catalog restore failing after upgrade to 6.5.4

2009-09-24 11:26:38
Subject: Re: [Veritas-bu] Catalog restore failing after upgrade to 6.5.4
From: Justin Piszcz <jpiszcz AT lucidpixels DOT com>
To: Mark Glazerman <Mark.Glazerman AT spartech DOT com>
Date: Thu, 24 Sep 2009 11:23:31 -0400 (EDT)
Yep,

I got bit by this a few times myself as well-- so its usually the first 
thing I look for when having catalog restore problems.  Thanks for the 
follow up.

Justin.

On Thu, 24 Sep 2009, Mark Glazerman wrote:

> We've resolved this.  It was an oversight on our part.  The admin who setup 
> both of these boxes linked the standard location for catalog data from 
> /usr/openv/netbackup/db to another filesystem.  We'd blown away the netbackup 
> install on the remote test server and hadn't recreated this link.  After 
> recreating the link tha catalog restore was successful.
>
> Mark Glazerman
> Desk: 314-889-8282
> Cell: 618-520-3401
> ? please don't print this e-mail unless you really need to
>
>
> -----Original Message-----
> From: veritas-bu-bounces AT mailman.eng.auburn DOT edu 
> [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Mark 
> Glazerman
> Sent: Tuesday, September 22, 2009 1:16 PM
> To: Justin Piszcz
> Cc: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] Catalog restore failing after upgrade to 6.5.4
>
> Justin,
>
> Thanks for your reply.
>
> Your mention of the exact same error message being linked to a server with 
> dual NIC's hit home because we have added an additional network interface to 
> allow this server to communicate with our data domains over a private network.
>
> We're looking into whether the different hostnames associated with these 
> interfaces may be the problem.
>
> Thanks for giving us some food for thought.
>
> Mark Glazerman
> Desk: 314-889-8282
> Cell: 618-520-3401
> ? please don't print this e-mail unless you really need to
>
>
> -----Original Message-----
> From: Justin Piszcz [mailto:jpiszcz AT lucidpixels DOT com]
> Sent: Tuesday, September 22, 2009 12:25 PM
> To: Mark Glazerman
> Cc: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] Catalog restore failing after upgrade to 6.5.4
>
> Hi,
>
> When you are recovering the catalog are you recovering it to the exact
> same location as you have on your existing master server?
>
> 1. if /usr/openv -> /mypartition
> 2. then on the restore server you have to have the same thing with the
> same hostname as well, or else it won't work.
> 3. Did you include the DR file as well?
>
> But that failure looks a bit strange..
>
> http://www.symantec.com/connect/forums/total-meltdown-unablle-recover-nbdb
>
> http://seer.entsupport.symantec.com/docs/285935.htm
>
> Etrack Incident = ET834802
>
> Description:
>    Catalog recovery from a hot catalog backup would fail with the
> following
>    error when the entry for EMMSERVER in bp.conf was different than the
>    SERVER name for the master server, but, they were actually the same
>    machine.  This would occur when there were two NICs in the master server.
>      "Failed to find last NBDB backup image record for client serverName
>       with policy policyName (227)"
>
> Has anything changed in your environment besides the 6.5.4 upgrade?
>
> Justin.
>
> On Tue, 22 Sep 2009, Mark Glazerman wrote:
>
>> We upgraded to 6.5.4 about 4 months ago and have just started preparing
>> for our first DR test at this version level (previous successful tests
>> at 6.5.1).
>>
>>
>>
>> We have a support call open with datalink because we have so far been
>> unable to restore our catalog to our test master server.
>>
>>
>>
>> The catalog restore (initiated with bprecover -wizard) restores all the
>> client images (25GB or so) but pukes every time with the following
>> error...
>>
>>
>>
>> 12:58:19.201 [13861] <16> bprecover: ERR - Failed to find last NBDB
>> backup image record for client nbumaster01.sun.spartech.com with policy
>> NBU_CATALOG_HOT (227)
>>
>>
>>
>> 12:58:19.221 [13861] <16> bprecover: Failed to recover catalog (227)
>>
>>
>>
>> Has anyone out there seen anything similar since upgrading to 6.5.4 ?
>>
>>
>>
>> As a point of reference our test master server is configured and patched
>> exactly like our production box.
>>
>>
>>
>> Our worry is that besides issues in testing, we may have exposed a huge
>> hole in our production restore capabilities with regard to a master
>> server loss.
>>
>>
>>
>> Thanks in advance,
>>
>>
>>
>> Mark Glazerman
>>
>> Enterprise Storage Administrator
>>
>> Spartech Corporation
>>
>> Desk: 314-889-8282
>>
>> Fax: 314-854-8282
>>
>> Cell: 618-520-3401
>>
>> mark.glazerman AT spartech DOT com <mailto:mark.glazerman AT spartech DOT 
>> com>
>>
>> http://www.spartech.com <http://www.spartech.com/>
>>
>> P please don't print this e-mail unless you really need to
>>
>> This e-mail and any files transmitted with it are confidential, are
>> intended solely for the use of the addressee, and may be legally
>> privileged. If you have received this email in error please notify the
>> sender immediately, and do not copy or forward it.
>>
>>
>>
>>
> _______________________________________________
> 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

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