cancel
Showing results for 
Search instead for 
Did you mean: 

Error 13 and 42 windows client 2003

Arturo_Lopez
Level 5
Partner Accredited

Hello,

Recently, we recovered the comunication with a windows client 6.5. We have problems with error 13 and 42 when backup is doing.

The master server is Solaris 9 with Netbackup 6.5.

Regards.

9 REPLIES 9

BTLOMS
Level 5

Is this client in a seperate network?

Is there a firewall somewhere in between? Windows firewall?

From the master, in the NBU GUI, can you connect to this client?

Can you telnet the netbackup master / media server on the netbackup ports 1556 and 13724 (i think)?

Arturo_Lopez
Level 5
Partner Accredited

The client it's in the same network, there isn't any firewall.

Yes i can connect with the client and the telnet works without problems

13/42 is often caused by a timeout somewhere along the line.

The usually solutions are defragmentation (faster reading of the files), increasing the client read timeout, fix any issue with VSS system. If there are a firewall between the machines decreasing the TCP keepalive time to 5 minutes or less is a good idea.

But without any logs or job details it is impossible to be more specific.

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Hi Arturo_Lopez,

Restart the PBX service from the client and kill the hung processes any and retry the backups.

Kesavan.P

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

This entire environment is so old that nothing is supported anymore - OS vendors and Veritas.

You need to get OS admins as well as network admins involved to health-check NIC drivers and settings on the servers as well as the network switch.

Mismatched switch port and NIC settings can cause this - check that everything is configured the same way - fixed speed or Auto-negotiate. 

TCP Chimney settings on W2003 is also known for causing network errors.

NetBackup is the casualty of your aged infrastructure and is merely reporting the errors - not causing it. 

 

Arturo_Lopez
Level 5
Partner Accredited

Ok, we will check with the administrators.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

TN with list of possible causes:

http://www.veritas.com/docs/000028869

 

Arturo_Lopez
Level 5
Partner Accredited

Thanks Marianne!!

BTLOMS
Level 5

have you tried restarting the Windows client?