Tar file write error 10054, status 14 (file write failed) ??? 1

[pctekk]

sorry gang newbee to netbackup 4.5

were backing up across the wire to
Server A has intel 10/100 nic Win2k srv 1.2ghz 1gig ram
and getting this error, it did a few files at 243 kb/sec

but we have been backing up another server
Server B right next to it (Running win2003 w/ Gig NIC) 1.4 ghz 1gig ram
just fine, no error/issues 8373 kb/sec

any ideas would greatly appreciate it !!!

 

[630111]

Assuming you're running your master server on Solaris, type the following

# bperror -S 14 -r

If you're running a Windows or another UNIX, not sure what the command is. This will give you

file write failed
A write to a file or socket failed. Possible causes include:
* I/O error writing to the file system.
* Write to a socket failed. This can be caused by a network problem or a problem with the process reading from the socket.
* Writing to a full disk partition.

Try the following:

* Check the NetBackup Problems report for clues on where and why the problem occurred.
* For detailed troubleshooting information, create a debug log directory for the process that returned this status code, retry the operation, and check the resulting debug log.
* Make sure that routers, bridges, and other network devices are all at "full" duplex.
* Use a "sniffer" program to determine the number of packets being rejected and/or re-requested.
* On Windows systems, the client bpbkar log may contain a 10054 "Connection Reset Error"error (usually indicates a hardware error). Somewhere between the NetBackup client and server, the connection was reset. When NetBackup receives this error, it is unable to continue the backup. This error has been attributed to the following:
* A hiccup in the network.
* A bad network interface card on a NetBackup client.
* A bad network interface card on the NetBackup server.
* Faulty routers.
* Other applications interfering with NetBackup connections.
* On Novell systems, status code 14 has also been attributed to network issues. Try a "sniffer" program, as suggested above.

I'd first check to make sure you have enough space on the drive that gave you the 14 error. In particular, look for a VPCache*.VSP file that might reside there. These sometimes take up ALOT of space if you're using VSP.

Please let us know if this helps or not.

630111

 

[pctekk]

were actually on windows 2000, i have the printout of the info you put in here, but didnt know where to go from there.

Were running netbackup on Server B trying to backup remotely Server A
so i should check Server A for the vpcache*.vsp
file ???
what is vsp and do i need it ??
On server A though, the c drive is about 1.3 free
could that make a difference also ??
the D drive what we really are trying to backup is about 120 gig w/ 100 free.

I also did just install a Gig nic on Server A to see if that makes a difference instead of the 10/100.

 

[630111]

Vspcache*.vsp are files created by the Veritas Snapshot Provider feature. In a nutshell, this feature creates a snapshot of a volume and NetBackup backs this up. It is my understanding that this file should be deleted automatically after it is used but I have found that sometimes it is not. If you see this file and a backup is not in progress, it should be ok to delete the file. I'd start by disabling this and deleting the .vsp file to see if you get the same error.

The gigabit nic should definitely help! Make sure you're running it and the switch port at 1000/Full

630111

 

[pctekk]

did the nic, ran successfully at 400-600 kb/sec
only but will have to do for now.
my other srv(win2003) runs at 4000 kb/sec
going through same switch etc......

how do u "disable" this feature ??
nope...didnt find any on NBU master

 

[630111]

Remember, I'm using the Java GUI so your location may vary

NetBackup Management --> Host Properties --> Clients. Right-click your client and select "Properties". Look under "Windows Client" and highlight "VSP". Deselect "Enable VSP during backups".

Honestly, I don't always get the full rate of a gigabit card. My Sun and NetWare boxes seem to do pretty well, with newer Compaq servers running a close third. What has helped with the Compaq servers in the past is upgrading the driver on the gigabit NIC to a newer version.

630111

 

[pctekk]

Gotcha !!

Thanks

under my Windows Client all i have is "Archive Bit"
nothing else.........hmmmmmmmmmmm