Re: [Veritas-bu] cold catalog recovery

2012-03-16 Thread Shekel Tal
Doesn't sound like a netbackup issue
Sounds like a host configuration issue - maybe dns

Are you returning 127.0.0.1 even when you have any entry in your local hosts?
The system could be configured not to look at hosts

Can you resolve forward and reverse lookup when using nslookup?

Regards,
Tal Shekel
CSA
FUJITSU

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Infantino, Joe 
(Contractor)
Sent: 15 March 2012 20:39
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] cold catalog recovery


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: jinfant...@intersil.commailto:jinfant...@intersil.com

www.intersil.comfile:///\\www.intersil.com

Unless otherwise stated, this email has been sent from Fujitsu Services 
Limited, from Fujitsu (FTS) Limited, or from Fujitsu Telecommunications Europe 
Limited, together Fujitsu.
 
This email is only for the use of its intended recipient.  Its contents are 
subject to a duty of confidence and may be privileged.  Fujitsu does not 
guarantee that this email has not been intercepted and amended or that it is 
virus-free.

Fujitsu Services Limited, registered in England No 96056, registered office 22 
Baker Street, London W1U 3BW.

Fujitsu (FTS) Limited, registered in England No 03808613, registered office 22 
Baker Street, London W1U 3BW.

Fujitsu Telecommunications Europe Limited, registered in England No 2548187, 
registered office Solihull Parkway, Birmingham Business Park, Birmingham, B37 
7YU.___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] cold catalog recovery

2012-03-16 Thread Infantino, Joe (Contractor)
That's what we thought also, but why then would it work just fine before
the catalog recovery?

 

I do have a hosts file entry for the system.

 

Currently it is off the network so nslookup is not working, but even
when it was on the network and name resolution was working fine the
issue was still there.

 

 

Joe Infantino

MCP, MCSA, Security+, ITILv3

Senior Systems Analyst

Security and Server Operations

Intersil Corporation

 

email: jinfant...@intersil.com mailto:jinfant...@intersil.com 

office: 321-724-7119

fax: 321-729-1186

 

www.intersil.com

 

From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com] 
Sent: Friday, March 16, 2012 5:56 AM
To: Infantino, Joe (Contractor); veritas-bu@mailman.eng.auburn.edu
Subject: RE: cold catalog recovery

 

Doesn't sound like a netbackup issue

Sounds like a host configuration issue - maybe dns

 

Are you returning 127.0.0.1 even when you have any entry in your local
hosts?

The system could be configured not to look at hosts

 

Can you resolve forward and reverse lookup when using nslookup?

 

Regards,

Tal Shekel

CSA
FUJITSU

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
Infantino, Joe (Contractor)
Sent: 15 March 2012 20:39
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] cold catalog recovery

 

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: jinfant...@intersil.com mailto:jinfant...@intersil.com 

www.intersil.com file:///\\www.intersil.com 


Unless otherwise stated, this email has been sent from Fujitsu Services
Limited, from Fujitsu (FTS) Limited, or from Fujitsu Telecommunications
Europe Limited, together Fujitsu.

This email is only for the use of its intended recipient. Its contents
are subject to a duty of confidence and may be privileged. Fujitsu does
not guarantee that this email has not been intercepted and amended or
that it is virus-free.

Fujitsu Services Limited, registered in England No 96056, registered
office 22 Baker Street, London W1U 3BW.

Fujitsu (FTS) Limited, registered in England No 03808613, registered
office 22 Baker Street, London W1U 3BW.

Fujitsu Telecommunications Europe Limited, registered in England No
2548187, registered office Solihull Parkway, Birmingham Business Park,
Birmingham, B37 7YU.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] cold catalog recovery

2012-03-16 Thread Infantino, Joe (Contractor)
It is a standard system build.  I did the build and did not change
anything to do with DNS

 

Firewall is also turned off.  I tried with the firewall service disabled
and after a reboot and the error still exists.

 

 

Joe Infantino

MCP, MCSA, Security+, ITILv3

Senior Systems Analyst

Security and Server Operations

Intersil Corporation

 

email: jinfant...@intersil.com mailto:jinfant...@intersil.com 

office: 321-724-7119

fax: 321-729-1186

 

www.intersil.com

 

From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com] 
Sent: Friday, March 16, 2012 7:55 AM
To: Infantino, Joe (Contractor); veritas-bu@mailman.eng.auburn.edu
Subject: RE: cold catalog recovery

 

It could just be down to the way your host is configured to lookup names

 

Is this a standard windows build or a bespoke build created by your sys
admins?

They could have changed the way the build resolves hostnames as a
security feature?

 

Regards,

Tal Shekel

CSA
FUJITSU

 

From: Infantino, Joe (Contractor) [mailto:jinfant...@intersil.com] 
Sent: 16 March 2012 11:53
To: Shekel Tal; veritas-bu@mailman.eng.auburn.edu
Subject: RE: cold catalog recovery

 

That's what we thought also, but why then would it work just fine before
the catalog recovery?

 

I do have a hosts file entry for the system.

 

Currently it is off the network so nslookup is not working, but even
when it was on the network and name resolution was working fine the
issue was still there.

 

 

Joe Infantino

MCP, MCSA, Security+, ITILv3

Senior Systems Analyst

Security and Server Operations

Intersil Corporation

 

email: jinfant...@intersil.com mailto:jinfant...@intersil.com 

office: 321-724-7119

fax: 321-729-1186

 

www.intersil.com

 

From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com] 
Sent: Friday, March 16, 2012 5:56 AM
To: Infantino, Joe (Contractor); veritas-bu@mailman.eng.auburn.edu
Subject: RE: cold catalog recovery

 

Doesn't sound like a netbackup issue

Sounds like a host configuration issue - maybe dns

 

Are you returning 127.0.0.1 even when you have any entry in your local
hosts?

The system could be configured not to look at hosts

 

Can you resolve forward and reverse lookup when using nslookup?

 

Regards,

Tal Shekel

CSA
FUJITSU

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
Infantino, Joe (Contractor)
Sent: 15 March 2012 20:39
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] cold catalog recovery

 

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: jinfant...@intersil.com mailto:jinfant...@intersil.com 

www.intersil.com file:///\\www.intersil.com 


Unless otherwise stated, this email has been sent from Fujitsu Services
Limited, from Fujitsu (FTS) Limited, or from Fujitsu Telecommunications
Europe Limited, together Fujitsu.

This email is only for the use of its intended recipient. Its contents
are subject to a duty of confidence and may be privileged. Fujitsu does
not guarantee that this email has not been intercepted and amended or
that it is virus-free.

Fujitsu Services Limited, registered in England No 96056, registered
office 22 Baker Street, London W1U 3BW.

Fujitsu (FTS) Limited, registered in England No 03808613, registered
office 22 Baker Street, London W1U 3BW.

Fujitsu Telecommunications Europe Limited, registered in England No
2548187, registered office Solihull Parkway, Birmingham Business Park,

Re: [Veritas-bu] cold catalog recovery

2012-03-16 Thread Shekel Tal
It could just be down to the way your host is configured to lookup names

Is this a standard windows build or a bespoke build created by your sys admins?
They could have changed the way the build resolves hostnames as a security 
feature?

Regards,
Tal Shekel
CSA
FUJITSU

From: Infantino, Joe (Contractor) [mailto:jinfant...@intersil.com]
Sent: 16 March 2012 11:53
To: Shekel Tal; veritas-bu@mailman.eng.auburn.edu
Subject: RE: cold catalog recovery

That's what we thought also, but why then would it work just fine before the 
catalog recovery?

I do have a hosts file entry for the system.

Currently it is off the network so nslookup is not working, but even when it 
was on the network and name resolution was working fine the issue was still 
there.


Joe Infantino
MCP, MCSA, Security+, ITILv3
Senior Systems Analyst
Security and Server Operations
Intersil Corporation

email: jinfant...@intersil.commailto:jinfant...@intersil.com
office: 321-724-7119
fax: 321-729-1186

www.intersil.com

From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com]
Sent: Friday, March 16, 2012 5:56 AM
To: Infantino, Joe (Contractor); veritas-bu@mailman.eng.auburn.edu
Subject: RE: cold catalog recovery

Doesn't sound like a netbackup issue
Sounds like a host configuration issue - maybe dns

Are you returning 127.0.0.1 even when you have any entry in your local hosts?
The system could be configured not to look at hosts

Can you resolve forward and reverse lookup when using nslookup?

Regards,
Tal Shekel
CSA
FUJITSU

From: 
veritas-bu-boun...@mailman.eng.auburn.edumailto:veritas-bu-boun...@mailman.eng.auburn.edu
 [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Infantino, Joe 
(Contractor)
Sent: 15 March 2012 20:39
To: veritas-bu@mailman.eng.auburn.edumailto:veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] cold catalog recovery


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: jinfant...@intersil.commailto:jinfant...@intersil.com

www.intersil.comfile:///\\www.intersil.com

Unless otherwise stated, this email has been sent from Fujitsu Services 
Limited, from Fujitsu (FTS) Limited, or from Fujitsu Telecommunications Europe 
Limited, together Fujitsu.

This email is only for the use of its intended recipient. Its contents are 
subject to a duty of confidence and may be privileged. Fujitsu does not 
guarantee that this email has not been intercepted and amended or that it is 
virus-free.

Fujitsu Services Limited, registered in England No 96056, registered office 22 
Baker Street, London W1U 3BW.

Fujitsu (FTS) Limited, registered in England No 03808613, registered office 22 
Baker Street, London W1U 3BW.

Fujitsu Telecommunications Europe Limited, registered in England No 2548187, 
registered office Solihull Parkway, Birmingham Business Park, Birmingham, B37 
7YU.

Unless otherwise stated, this email has been sent from Fujitsu Services 
Limited, from Fujitsu (FTS) Limited, or from Fujitsu Telecommunications Europe 
Limited, together Fujitsu.
 
This email is only for the use of its intended recipient.  Its contents are 
subject to a duty of confidence and may be privileged.  Fujitsu does not 
guarantee that this email has not been intercepted and amended or that it is 
virus-free.

Fujitsu Services Limited, registered in England No 96056, registered office 22 
Baker Street, London W1U 3BW.

Fujitsu (FTS) Limited, registered in England No 03808613, registered office 22 

Re: [Veritas-bu] cold catalog recovery

2012-03-16 Thread Shekel Tal
That's odd
If you have any entry in the host file bpclntcmd should pick it up

Still sounds like host config though
Although this is probably not the issue check if there are any entries under 
veritas\netbackup\remote_versions - that should affect name resolution but may 
be worth cleaning out

The errors in your log (25  46) both refer to hostname resolution issues and 
bpclntcmd confirms this
Try add an entry for a dummy server into for a different hostname into your 
hosts file and see if you can resolve it
From the sound of it you wont be able to

Regards,
Tal Shekel
CSA
FUJITSU

From: Infantino, Joe (Contractor) [mailto:jinfant...@intersil.com]
Sent: 16 March 2012 11:56
To: Shekel Tal; veritas-bu@mailman.eng.auburn.edu
Subject: RE: cold catalog recovery

It is a standard system build.  I did the build and did not change anything to 
do with DNS

Firewall is also turned off.  I tried with the firewall service disabled and 
after a reboot and the error still exists.


Joe Infantino
MCP, MCSA, Security+, ITILv3
Senior Systems Analyst
Security and Server Operations
Intersil Corporation

email: jinfant...@intersil.commailto:jinfant...@intersil.com
office: 321-724-7119
fax: 321-729-1186

www.intersil.com

From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com]
Sent: Friday, March 16, 2012 7:55 AM
To: Infantino, Joe (Contractor); veritas-bu@mailman.eng.auburn.edu
Subject: RE: cold catalog recovery

It could just be down to the way your host is configured to lookup names

Is this a standard windows build or a bespoke build created by your sys admins?
They could have changed the way the build resolves hostnames as a security 
feature?

Regards,
Tal Shekel
CSA
FUJITSU

From: Infantino, Joe (Contractor) [mailto:jinfant...@intersil.com]
Sent: 16 March 2012 11:53
To: Shekel Tal; 
veritas-bu@mailman.eng.auburn.edumailto:veritas-bu@mailman.eng.auburn.edu
Subject: RE: cold catalog recovery

That's what we thought also, but why then would it work just fine before the 
catalog recovery?

I do have a hosts file entry for the system.

Currently it is off the network so nslookup is not working, but even when it 
was on the network and name resolution was working fine the issue was still 
there.


Joe Infantino
MCP, MCSA, Security+, ITILv3
Senior Systems Analyst
Security and Server Operations
Intersil Corporation

email: jinfant...@intersil.commailto:jinfant...@intersil.com
office: 321-724-7119
fax: 321-729-1186

www.intersil.com

From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com]
Sent: Friday, March 16, 2012 5:56 AM
To: Infantino, Joe (Contractor); 
veritas-bu@mailman.eng.auburn.edumailto:veritas-bu@mailman.eng.auburn.edu
Subject: RE: cold catalog recovery

Doesn't sound like a netbackup issue
Sounds like a host configuration issue - maybe dns

Are you returning 127.0.0.1 even when you have any entry in your local hosts?
The system could be configured not to look at hosts

Can you resolve forward and reverse lookup when using nslookup?

Regards,
Tal Shekel
CSA
FUJITSU

From: 
veritas-bu-boun...@mailman.eng.auburn.edumailto:veritas-bu-boun...@mailman.eng.auburn.edu
 [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Infantino, Joe 
(Contractor)
Sent: 15 March 2012 20:39
To: veritas-bu@mailman.eng.auburn.edumailto:veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] cold catalog recovery


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: 

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

2012-03-16 Thread Steve Quan

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-requ...@mailman.eng.auburn.edu
 Subject: Veritas-bu Digest, Vol 71, Issue 11
 To: veritas-bu@mailman.eng.auburn.edu
 Date: Fri, 16 Mar 2012 07:00:04 -0500
 
 Send Veritas-bu mailing list submissions to
   veritas-bu@mailman.eng.auburn.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-requ...@mailman.eng.auburn.edu
 
 You can reach the person managing the list at
   veritas-bu-ow...@mailman.eng.auburn.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) jinfant...@intersil.com
 Subject: [Veritas-bu] cold catalog recovery
 To: veritas-bu@mailman.eng.auburn.edu
 Message-ID:
   13e204e614d8e04faf594c9aa9ed0bb712d79...@pbcomx02.intersil.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: jinfant...@intersil.com
 
 www.intersil.com
 

snip___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


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

2012-03-16 Thread Shekel Tal
Did you try run bpclntcmd prior to the upgrade?

I also noticed the 64 bit and 32 bit change but wouldn't have thought it would 
make a difference

Regards,
Tal Shekel
CSA
FUJITSU

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Steve Quan
Sent: 16 March 2012 12:54
To: veritas-bu@mailman.eng.auburn.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-requ...@mailman.eng.auburn.edu
 Subject: Veritas-bu Digest, Vol 71, Issue 11
 To: veritas-bu@mailman.eng.auburn.edu
 Date: Fri, 16 Mar 2012 07:00:04 -0500

 Send Veritas-bu mailing list submissions to
 veritas-bu@mailman.eng.auburn.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-requ...@mailman.eng.auburn.edu

 You can reach the person managing the list at
 veritas-bu-ow...@mailman.eng.auburn.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) jinfant...@intersil.com
 Subject: [Veritas-bu] cold catalog recovery
 To: veritas-bu@mailman.eng.auburn.edu
 Message-ID:
 13e204e614d8e04faf594c9aa9ed0bb712d79...@pbcomx02.intersil.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: jinfant...@intersil.com

 www.intersil.com

snip

Unless otherwise stated, this email has been sent from Fujitsu Services 
Limited, from Fujitsu (FTS) Limited, or from Fujitsu Telecommunications Europe 
Limited, together Fujitsu.
 
This email is only for the use of its intended recipient.  Its contents are 
subject to a duty of confidence and may be privileged.  Fujitsu does not 
guarantee that this email has not been intercepted and amended or that it is 
virus-free.

Fujitsu Services Limited, registered in England No 96056, registered office 22 
Baker Street, London W1U 3BW.

Fujitsu (FTS) Limited, registered in England No 03808613, registered office 22 
Baker Street, London W1U 3BW.

Fujitsu Telecommunications Europe Limited, registered in England No 2548187, 
registered office Solihull Parkway, Birmingham Business Park, Birmingham, B37 
7YU.___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


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

2012-03-16 Thread Infantino, Joe (Contractor)
The old system is still up as that was our fallback option.

 

We don't have a spare drive in our lab to use for a hot catalog backup
test, at least not yet.  That was our next option, but we would need
downtime again to do the catalog backup/restore.

 

 

Joe Infantino

MCP, MCSA, Security+, ITILv3

Senior Systems Analyst

Security and Server Operations

Intersil Corporation

 

email: jinfant...@intersil.com mailto:jinfant...@intersil.com 

office: 321-724-7119

fax: 321-729-1186

 

www.intersil.com

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin
Piszcz
Sent: Friday, March 16, 2012 9:02 AM
To: 'Shekel Tal'; 'Steve Quan'; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11

 

Hi,

 

I've gone from 32-bit to 64-bit with Linux on several occasions and did
not have an issue; however I've not tried that with Windows.  Do you
still have the old master running?  Have you tried using a hot catalog
backup (cold backups are deprecated anyhow)?

 

Justin.

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Shekel
Tal
Sent: Friday, March 16, 2012 8:58 AM
To: Steve Quan; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11

 

Did you try run bpclntcmd prior to the upgrade?

 

I also noticed the 64 bit and 32 bit change but wouldn't have thought it
would make a difference

 

Regards,

Tal Shekel

CSA
FUJITSU

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Steve
Quan
Sent: 16 March 2012 12:54
To: veritas-bu@mailman.eng.auburn.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-requ...@mailman.eng.auburn.edu
 Subject: Veritas-bu Digest, Vol 71, Issue 11
 To: veritas-bu@mailman.eng.auburn.edu
 Date: Fri, 16 Mar 2012 07:00:04 -0500
 
 Send Veritas-bu mailing list submissions to
 veritas-bu@mailman.eng.auburn.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-requ...@mailman.eng.auburn.edu
 
 You can reach the person managing the list at
 veritas-bu-ow...@mailman.eng.auburn.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) jinfant...@intersil.com
 Subject: [Veritas-bu] cold catalog recovery
 To: veritas-bu@mailman.eng.auburn.edu
 Message-ID:
 13e204e614d8e04faf594c9aa9ed0bb712d79...@pbcomx02.intersil.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: jinfant...@intersil.com
 
 www.intersil.com
 

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

2012-03-16 Thread scott . george
From what I remember, the recommended catalog backup was the hot backup 
when it first appeared (in 6.0?).  I have had to use it a couple of times 
with success every time.

Even if it could be dumped to disk and transferred/mapped to the new 
system, it would be worth a try.





From:   Justin Piszcz jpis...@lucidpixels.com
To: 'Shekel Tal' tal.she...@uk.fujitsu.com, 'Steve Quan' 
sk...@hotmail.com, veritas-bu@mailman.eng.auburn.edu
Date:   03/16/2012 08:59 AM
Subject:Re: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11
Sent by:veritas-bu-boun...@mailman.eng.auburn.edu



Hi,
 
I?ve gone from 32-bit to 64-bit with Linux on several occasions and did 
not have an issue; however I?ve not tried that with Windows.  Do you still 
have the old master running?  Have you tried using a hot catalog backup 
(cold backups are deprecated anyhow)?
 
Justin.
 
From: veritas-bu-boun...@mailman.eng.auburn.edu [
mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Shekel Tal
Sent: Friday, March 16, 2012 8:58 AM
To: Steve Quan; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11
 
Did you try run bpclntcmd prior to the upgrade?
 
I also noticed the 64 bit and 32 bit change but wouldn?t have thought it 
would make a difference
 
Regards,
Tal Shekel
CSA
FUJITSU
 
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Steve Quan
Sent: 16 March 2012 12:54
To: veritas-bu@mailman.eng.auburn.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-requ...@mailman.eng.auburn.edu
 Subject: Veritas-bu Digest, Vol 71, Issue 11
 To: veritas-bu@mailman.eng.auburn.edu
 Date: Fri, 16 Mar 2012 07:00:04 -0500
 
 Send Veritas-bu mailing list submissions to
 veritas-bu@mailman.eng.auburn.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-requ...@mailman.eng.auburn.edu
 
 You can reach the person managing the list at
 veritas-bu-ow...@mailman.eng.auburn.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) jinfant...@intersil.com
 Subject: [Veritas-bu] cold catalog recovery
 To: veritas-bu@mailman.eng.auburn.edu
 Message-ID:
 13e204e614d8e04faf594c9aa9ed0bb712d79...@pbcomx02.intersil.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: jinfant...@intersil.com
 
 www.intersil.com
 
snip

Unless otherwise stated, this email has been sent from Fujitsu Services 
Limited, from Fujitsu (FTS) Limited, or from Fujitsu Telecommunications 
Europe Limited, together Fujitsu.

This email is only for the use 

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

2012-03-16 Thread Justin Piszcz
Hi,

 

Does the D/R site have the same master, media servers as the source site?

Does the master at the D/R site have network connectivity to the media
servers and clients?

If it has the same hostname as the other server, how will the client know
which master server it is talking to?

Or is the client in this case the master?

 

Some screenshots or more logs of what is failing may be helpful.

Bpbrm logs from the master, bpcd from the master, job details, etc.

 

 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)

 

Justin.

 

From: Infantino, Joe (Contractor) [mailto:jinfant...@intersil.com] 
Sent: Friday, March 16, 2012 9:05 AM
To: Justin Piszcz; Shekel Tal; Steve Quan; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11

 

The old system is still up as that was our fallback option.

 

We don't have a spare drive in our lab to use for a hot catalog backup test,
at least not yet.  That was our next option, but we would need downtime
again to do the catalog backup/restore.

 

 

Joe Infantino

MCP, MCSA, Security+, ITILv3

Senior Systems Analyst

Security and Server Operations

Intersil Corporation

 

email:  mailto:jinfant...@intersil.com jinfant...@intersil.com

office: 321-724-7119

fax: 321-729-1186

 

www.intersil.com

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin
Piszcz
Sent: Friday, March 16, 2012 9:02 AM
To: 'Shekel Tal'; 'Steve Quan'; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11

 

Hi,

 

I've gone from 32-bit to 64-bit with Linux on several occasions and did not
have an issue; however I've not tried that with Windows.  Do you still have
the old master running?  Have you tried using a hot catalog backup (cold
backups are deprecated anyhow)?

 

Justin.

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Shekel Tal
Sent: Friday, March 16, 2012 8:58 AM
To: Steve Quan; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11

 

Did you try run bpclntcmd prior to the upgrade?

 

I also noticed the 64 bit and 32 bit change but wouldn't have thought it
would make a difference

 

Regards,

Tal Shekel

CSA
FUJITSU

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Steve Quan
Sent: 16 March 2012 12:54
To: veritas-bu@mailman.eng.auburn.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-requ...@mailman.eng.auburn.edu
 Subject: Veritas-bu Digest, Vol 71, Issue 11
 To: veritas-bu@mailman.eng.auburn.edu
 Date: Fri, 16 Mar 2012 07:00:04 -0500
 
 Send Veritas-bu mailing list submissions to
 veritas-bu@mailman.eng.auburn.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-requ...@mailman.eng.auburn.edu
 
 You can reach the person managing the list at
 veritas-bu-ow...@mailman.eng.auburn.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) jinfant...@intersil.com
 Subject: [Veritas-bu] cold catalog recovery
 To: veritas-bu@mailman.eng.auburn.edu
 Message-ID:
 13e204e614d8e04faf594c9aa9ed0bb712d79...@pbcomx02.intersil.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 

Re: [Veritas-bu] Getting Status 96 with 201 scratch tapes

2012-03-16 Thread scott . george
Just so I didn't leave this hanging out there, I had 201 tapes with volume 
expirations that had expired.  It was a good lesson in the difference 
between data expiration and volume expiration.

Thank you for all of the input!



From:   David McMullin david.mcmul...@cbc-companies.com
To: veritas-bu@mailman.eng.auburn.edu 
veritas-bu@mailman.eng.auburn.edu
Date:   03/09/2012 01:12 PM
Subject:Re: [Veritas-bu] Getting Status 96 with 201 scratch tapes
Sent by:veritas-bu-boun...@mailman.eng.auburn.edu



What is the output of this command:

/usr/openv/volmgr/bin/vmpool -list_scratch

Is your defined scratch pool what you expected?

I run a cron job that verifies my available scratch tapes and sets my pool 
several times a day, ever since I found there is a bug in the java gui 
that can set a pool as scratch by mistake...

This command will set it for you: (my scratch pool is named scratch_pool)

/usr/openv/volmgr/bin/vmpool -set_scratch scratch_pool


--

Message: 6
Date: Fri, 9 Mar 2012 09:04:56 -0500
From: scott.geo...@parker.com
Subject: [Veritas-bu] Getting Status 96 with 201 scratch tapes
To: 'Veritas' veritas-bu@mailman.eng.auburn.edu
Message-ID:
 ofc07dd08a.e00282f7-on852579bc.004ccacf-852579bc.004d8...@parker.com
Content-Type: text/plain; charset=us-ascii

Here is my environment:

NBU 7.1.0.3 on an AIX 6.1 Master (also acting as media server in this 
instance)

My scratch pool has 201 tapes inside the robot.  Robot is STK SL8500 with 
20 9840C Drives.  I am using ACSLS.

Overnight vaults failed with the duplication jobs ending in error 96 
(unable to allocate new media for backup, storage unit has none 
available).


What gives? 

PLEASE NOTE: The preceding information may be confidential or
privileged. It only should be used or disseminated for the purpose
of conducting business with Parker. If you are not an intended
recipient, please notify the sender by replying to this message and
then delete the information from your system. Thank you for your
cooperation.

___
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] Veritas-bu Digest, Vol 71, Issue 11

2012-03-16 Thread Infantino, Joe (Contractor)
client = master.  We first saw the issue when we replaced the master
server and had it on the production network.

 

We reverted to the old server to keep things going while I brought the
new hardware back to a lab and rebuilt the OS.  I installed NBU and was
able to configure it up and get things going.  I then did a catalog
recover and the problem came back.

 

The problem exists when connected to the production network in the same
configuration as the old setup and also in the lab with the server
standalone.

 

Joe Infantino

MCP, MCSA, Security+, ITILv3

Senior Systems Analyst

Security and Server Operations

Intersil Corporation

 

email: jinfant...@intersil.com mailto:jinfant...@intersil.com 

office: 321-724-7119

fax: 321-729-1186

 

www.intersil.com

 

From: Justin Piszcz [mailto:jpis...@lucidpixels.com] 
Sent: Friday, March 16, 2012 9:14 AM
To: Infantino, Joe (Contractor); 'Shekel Tal'; 'Steve Quan';
veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11

 

Hi,

 

Does the D/R site have the same master, media servers as the source
site?

Does the master at the D/R site have network connectivity to the media
servers and clients?

If it has the same hostname as the other server, how will the client
know which master server it is talking to?

Or is the client in this case the master?

 

Some screenshots or more logs of what is failing may be helpful.

Bpbrm logs from the master, bpcd from the master, job details, etc.

 

 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)

 

Justin.

 

From: Infantino, Joe (Contractor) [mailto:jinfant...@intersil.com] 
Sent: Friday, March 16, 2012 9:05 AM
To: Justin Piszcz; Shekel Tal; Steve Quan;
veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11

 

The old system is still up as that was our fallback option.

 

We don't have a spare drive in our lab to use for a hot catalog backup
test, at least not yet.  That was our next option, but we would need
downtime again to do the catalog backup/restore.

 

 

Joe Infantino

MCP, MCSA, Security+, ITILv3

Senior Systems Analyst

Security and Server Operations

Intersil Corporation

 

email: jinfant...@intersil.com mailto:jinfant...@intersil.com 

office: 321-724-7119

fax: 321-729-1186

 

www.intersil.com

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin
Piszcz
Sent: Friday, March 16, 2012 9:02 AM
To: 'Shekel Tal'; 'Steve Quan'; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11

 

Hi,

 

I've gone from 32-bit to 64-bit with Linux on several occasions and did
not have an issue; however I've not tried that with Windows.  Do you
still have the old master running?  Have you tried using a hot catalog
backup (cold backups are deprecated anyhow)?

 

Justin.

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Shekel
Tal
Sent: Friday, March 16, 2012 8:58 AM
To: Steve Quan; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Veritas-bu Digest, Vol 71, Issue 11

 

Did you try run bpclntcmd prior to the upgrade?

 

I also noticed the 64 bit and 32 bit change but wouldn't have thought it
would make a difference

 

Regards,

Tal Shekel

CSA
FUJITSU

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Steve
Quan
Sent: 16 March 2012 12:54
To: veritas-bu@mailman.eng.auburn.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-requ...@mailman.eng.auburn.edu
 Subject: Veritas-bu Digest, Vol 71, Issue 11
 To: veritas-bu@mailman.eng.auburn.edu
 Date: Fri, 16 Mar 2012 07:00:04 -0500
 
 Send Veritas-bu mailing list submissions to
 veritas-bu@mailman.eng.auburn.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-requ...@mailman.eng.auburn.edu
 
 You can reach the person managing the list at
 veritas-bu-ow...@mailman.eng.auburn.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 

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

2012-03-16 Thread Martin, Jonathan
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-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Steve
Quan
Sent: Friday, March 16, 2012 8:54 AM
To: veritas-bu@mailman.eng.auburn.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-requ...@mailman.eng.auburn.edu
 Subject: Veritas-bu Digest, Vol 71, Issue 11
 To: veritas-bu@mailman.eng.auburn.edu
 Date: Fri, 16 Mar 2012 07:00:04 -0500
 
 Send Veritas-bu mailing list submissions to
 veritas-bu@mailman.eng.auburn.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-requ...@mailman.eng.auburn.edu
 
 You can reach the person managing the list at
 veritas-bu-ow...@mailman.eng.auburn.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) jinfant...@intersil.com
 Subject: [Veritas-bu] cold catalog recovery
 To: veritas-bu@mailman.eng.auburn.edu
 Message-ID:
 13e204e614d8e04faf594c9aa9ed0bb712d79...@pbcomx02.intersil.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: jinfant...@intersil.com
 
 www.intersil.com
 

snip

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu