Status 41, 25, 202

[cjouault]

Hi,

My configuration is :

Master/media : W2003/NetBackup 5.0MP5S2
Client : W2003 /Netbackup 5.0MP5, SQL Server 2000
Library with 1 drive

When I backup the database on the client, sometimes the backup failed with the error 41 or 25 or 202. I don't know where is the problem because, isn't for all the backup.

I have checked the network, the DNS, .....
I have no solution. The support is on the problem but They find nothing.

Please, Help me.

 

[Stumpr]

Check the name resolution for the name inside the db scripts

Bob Stump
Just because the VERITAS documentation states a certain thing does not make it a fact and that is truth.

 

[cjouault]

Hi,

The name resolution is ok. I don't find this problem for all backup. There only 1 backup failed per 15.

Please.

 

[Vela]

Status 41 is fairly hard to troubleshoot-

If the server is down you will usually see status 41, but if the server isn't down that's where it get's rough.

We're currently having an issue after a server patch where 20-50 client's drop with a status 41 in a 2minute period.

Most likely this will be a network card or network issue in general.

Good luck
Ryan

 

[Stumpr]

STATUS CODE 25, 41, 58, and 160: Oracle RMAN backups fail intermit

http://seer.support.veritas.com/docs/280909.htm

Although this technote is written for Oracle, it is good to take a look at it for SQL as well.

Bob Stump
Just because the VERITAS documentation states a certain thing does not make it a fact and that is truth.

 

[Vela]

We are now thinking our failures have to do with the HP APA port aggregation software we use.

I read that the primary link could drop and try to switch to the secondary link and when that fails, if there is no second link, it will switch back to the primary resulting in a brief network drop.

Are your client's at an older version of Netbackup? Can you upgrade them?

 

[cjouault]

Hi,

I have read the link about "STATUS CODE 25, 41, 58, and 160: Oracle RMAN backups fail intermit" and I have almost the same problem.

The only different is I don't have the error 160.

The second difference is my network configuration.

My network configuration is :

Master Server/Media Server (on the same server) : I have 3 networks interfaces
- Administration Network
- Backup dedicated Network
- Application Network 1 (default network)

Clients (cluster) : I have 4 networks interfaces
- Administration network
- Backup dedicated network
- Application network 1 (default network)
- Application network 2

On the client, the application network 1 and 2 are in teaming.
But normally, I use only the Backup dedicated network.
On the other hand, I'm not sure the communication between the master and the media server use only the backup network. Master and Media server are on the same server.
So I don't know how I can configure the media server and how I can see which interface network is used by media server.

I have see in the NetBackup documentation the Master communicates with the media server and the media server communicates with the client.

So If the media server use the application Network 1, I think the client use also this network (teamed NIC) but I'm
not sure.

Can you help me?
What can I do?

Thanks

 

[cjouault]

Hi all,

I think I have resolve my problem but without the Veritas Support.

For an other error, I have updated my configuration with the MP6 (NetBackup 5.0). And since 2 week, I never see the error again.

The correction of the problem was the MP6 manage windows 2003 and the earlier wersion of MP6 not.

 

[Vela]

So, you upgraded the client version?

I know this works sometimes to resolve the 41s.

 

[cjouault]

Yes,
all my server and client are upgraded with the MP6