Veritas-bu

Re: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11

2012-03-16 23:30:26
Subject: Re: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11
From: Steve Quan <skq01 AT hotmail DOT com>
To: <jmarti05 AT intersil DOT com>, <veritas-bu AT mailman.eng.auburn DOT edu>
Date: Fri, 16 Mar 2012 23:30:20 -0400
Yes, 32 to 64 is OK so long as it's the same NBU version/release. Can you show us the output of, "bpps -a" ? Also, what are in the logs on NBU startup after the catalog restore ? Any indications in the
windows event viewer ?

/Steve


Subject: RE: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11
Date: Fri, 16 Mar 2012 15:32:44 -0400
From: JMARTI05 AT intersil DOT com
To: skq01 AT hotmail DOT com; veritas-bu AT mailman.eng.auburn DOT edu

Just to clarify, this is our second Windows 2003 x86 to Windows 2008 x64 NBU 6.5.6 upgrade via cold catalog backup. We preformed our first last December in the same manner with much success. There is a possibility that the cold backup was bad, and we�d like to test a hot catalog backup as well. Unfortunately we�re bound by significant  time and hardware constraints, so troubleshooting the cold catalog backup we have is less painful than getting a 2nd outage for another cold catalog or finding an LTO drive to test with.

 

-Jonathan

 

From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Steve Quan
Sent: Friday, March 16, 2012 8:54 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11

 

What seems to "stick out", is the target OS is 64bit (vs the original 32bit OS) .... and the problem only shows up after a "good" catalog restore ....

/Steve
---

> From: veritas-bu-request AT mailman.eng.auburn DOT edu
> Subject: Veritas-bu Digest, Vol 71, Issue 11
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Date: Fri, 16 Mar 2012 07:00:04 -0500
>
> Send Veritas-bu mailing list submissions to
> veritas-bu AT mailman.eng.auburn DOT edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> or, via email, send a message with subject or body 'help' to
> veritas-bu-request AT mailman.eng.auburn DOT edu
>
> You can reach the person managing the list at
> veritas-bu-owner AT mailman.eng.auburn DOT edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Veritas-bu digest..."
>
>
> Today's Topics:
>
> 1. cold catalog recovery (Infantino, Joe (Contractor))
> 2. Re: cold catalog recovery (Shekel Tal)
> 3. Re: cold catalog recovery (Infantino, Joe (Contractor))
> 4. Re: cold catalog recovery (Infantino, Joe (Contractor))
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 15 Mar 2012 16:38:58 -0400
> From: "Infantino, Joe (Contractor)" <JINFANTINO AT intersil DOT com>
> Subject: [Veritas-bu] cold catalog recovery
> To: <veritas-bu AT mailman.eng.auburn DOT edu>
> Message-ID:
> <13E204E614D8E04FAF594C9AA9ED0BB712D79E43 AT PBCOMX02.intersil DOT corp>
> Content-Type: text/plain; charset="us-ascii"
>
> We are trying to upgrade our NBU hardware and OS and are running into
> some issues that seem related to doing a cold catalog recovery and name
> resolution.
>
> Current setup:
> Windows 2003 x86 SP2
> NBU 6.5.6
>
> New setup:
> Windows 2008 x64 SP2
> NBU 6.5.6
>
> Current server and new server are configured with the same name and ip
> address.
>
> ISSUE:
> We can do a cold catalog backup and restore just fine but have a serious
> issue in the end. After both successes if we open the Activity Monitor
> we get an error - "Not connected, check if services are up."
>
> All service are up.
>
> bpjobsd log shows
>
> <2> job_connect: Can't connect automatically to client pbcobk01 status =
> 25 err = 10061
> <2> job_connect: Can't connect to client pbcobk01
> <16> main: Can't connect to pbcobk01 (46)
>
> We did a complete system rebuild, installed NBU 6.5.6, and configured to
> write to disk. Test backup ran and Activity Monitor worked fine. Did
> the catalog recovery and the issue came back.
>
> I did some bpclntcmd tests and they all come back with the correct name
> but the IP shows as 127.0.0.1. I added the hostname and real IP to the
> hosts file with no luck.
>
> I tried the following tests:
> bpclntcmd -pn = correct short name with 127.0.0.1
> bpclntcmd -self = correct short name with 127.0.0.1
> bpclntcmd -hn pbcobk01 = correct short name with 127.0.0.1
> bpclntcmd -ip xxx.xxx.xxx.xxx = correct host and xxx.xxx.xxx.xxx for ip
> address
>
> If I do these test on the current server they come back with the actual
> IP of the system.
>
> TIA
>
> Joe Infantino
> MCP, MCSA, Security+, ITILv3
> Senior Systems Analyst
> Security and Server Operations
> Intersil Corporation
>
> email: jinfantino AT intersil DOT com
>
> www.intersil.com
>

<<<snip>>>

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