Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Backup failed with EC-41 on cluster name

Created: 10 Mar 2010 • Updated: 12 Sep 2010 | 2 comments

Hi Team,

When run backup using cluster name, it gives Error code 41, But we run using on physical name it got successful. Do any one knows the issue.

I have run both File system and oracle backup.

Master and Media server: Sunos 5.10   NB Version 6.5.5

Client: sun 5.8   NB version: 5.1 MP6

Please let us know which logs, I need to check.

Thanks,

Comments 2 CommentsJump to latest comment

Marianne's picture

Please give the error message as well. status 41 has more than one description:
Timeout connecting to client
and
Client Read timeout
The first one is the same as status 54 where 'connect back' from client fails.
With the second one, connection succeeds. The backup times out when no data is received for a fixed period (default is 5 minutes).

With Oracle backups the Client Connect Timeout as well as Client Read Timeout should be increased.

Are both filesystem and Oracle backups failing when you use the virtual name?
Did this backup work fine before upgrading to 6.x? If so, why not upgrade cluster nodes as well?

Create bpcd log on both cluster nodes.
On master and media server, test connectivity to virtual name:

bptestbpcd -clent <virtual_name>

If the test is unsuccessful, check bpcd log on active node.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Baski's picture

Hi

Are both filesystem and Oracle backups failing when you use the virtual name?
Yes, Both are failing when use virtual name
Did this backup work fine before upgrading to 6.x? If so, why not upgrade cluster nodes as well?
Yes, It was working fine, Just two back it is failing with EC-41

On master and media server, test connectivity to virtual name:
bptestbpcd -clent <virtual_name>

Tested on both master and media servers and working fine.

Any other ideas,

Appreciated your help.