Netware 5.1 with networker client 4.22

Question

My networker server 7.2.1 running on Solaris 8 crashed and had to do recovery. After the recovery, all other networker client ran the backup fine except for one of my netware boxes.

It's netware 5.1 with networker client 4.22 and it kept crashing during the backup and on the /nsr/log/daemon.log file, it gave the following error:

--- Unsuccessful Save Sets ---

* bc:DATA:\shares 1 retry attempted
* bc:DATA:\shares 11/07/07 09:12:43 nsrexec: SYSTEM error: Connection refused
* bc:index aborted

I had to manually reload networker module "networkr" to restart the backup. I'm not sure what causing the client to crash during the backup. Would it be the netware problem or the networker?

Networker Server 7.2.1 on Solaris 8
Netware 5.1 with service pack 8, Networker client 4.22
- bsdsock.nlm is 6.09c
- tcpip.nlm is 5.87f
- tsa500.nlm is 5.5
- tcp.nlm is 5.87f

I notice that there's newer client 7.2 is available but I would like to just keep the same client and solve the problem if at all possible.

Thank you

Zwe

ble1 · Answer

I don't think crash is related to failure of NetWare box.. the error message you quoted is typical when daemon (module in this case) is not running (in not loaded) on client. Do you know if module crashes when backup is initiated or does it happen when there is no activity thus when backup kicks in server gets closed doors?

zp · Answer

Thanks for the reply. As far as I'm aware it ran fine when backup is initiated. It happens during the backup and it would run the backup fine in the beginning and fail/crash once it gets middle of the process. Backup data is about 50G and it would crash around 20/30G.

zp · Answer

That's the smallest chunck that I could do. Since it's a directory for about ~600 users folders, I can't find an easy way of spliting the savesets any more by separating user's folder (asmith, jdoe, tjones, ...). Would wild cards work, like a-j for folders starts with a through j, k-t, or something like that for the save sets? As I'm only a backup person on that and have no way of checking the problem on the netware box, I have to keep reloading whenever that backup failed because of the networker client crashed and keep doing until I get a successful backups. About one out of five times usually works. Since it's also a remote backup over wan on very slow speed, it used to take about 4 days to finish that 50G data. That's painful.

Thanks again.

zp

ble1 · Answer

Try to split it if possible - perhaps it will result in something good.

ble1 · Answer

It's going to be hard for you to troubleshoot this if you can't get files for NetWare box. Save works for ssids like a*, b*, c*, etc... ([a-c]* didn't work for me), but it is question if this works on NetWare as it is client's save that has to support that.

NetWorker

Netware 5.1 with networker client 4.22

Was this post helpful?