I will try Netware with compression directive on the next backups. As for shrinking the data, this may not be possible as I already tried to get rid almost all used data. We have T-3 running between two places and data transfer speed is also slow even for regular file transfer but that's another issues. For the hardware, it's a really old compaq proliant server running novell 5.1 and I wouldn't dare touching any of the hardware for now. According to the logs, I do believe it has something to do with time-out issue but I'm not sure if the netware client is causing the problem or something else. I do have another networker 7.3.3 test server so I will also give it a shot on that one and see if that can handle it.
Below is the error message from the log that I usually get after backup failed.
And most of the time, novell networker client would also be down and I ended up
reloading and restarting the networker client module manually on the novell box.
Thanks for all your help.
Zwe
=========================================================
NetWorker savegroup: (alert) ballston completed, total 1 client(s), 0
Hostname(s) Unresolved, 1 Failed, 0 Succeeded. (bc Failed)
Start time: Mon Oct 15 15:45:42 2007
End time: Wed Oct 17 08:26:49 2007
--- Unsuccessful Save Sets ---
* bc:DATA: 5 retries attempted
* bc:DATA: 10/17/07 08:24:20 nsrexec: SYSTEM error: Connection refused
* bc:DATA: aborted due to inactivity
--- Successful Save Sets ---
mc: index:bc level=full, 500 MB 00:02:25 266 files
=========================================================
From networker server /nsr/logs/daemon.log
10/17/07 04:58:45 nsrd: bc:<10>DATA: continuing save 2000 MB
10/17/07 04:58:45 nsrd: bc:<11>DATA: saving to pool 'mc lto' (MCLTO.005)
10/17/07 06:52:05 nsrd: bc:<11>DATA: continuing save 2000 MB
10/17/07 06:52:06 nsrd: bc:<12>DATA: saving to pool 'mc lto' (MCLTO.005)
bc:DATA: exceeded inactivity timeout, aborting
* bc:DATA: Completed open file support for volume DATA
10/17/07 08:21:38 savegrp: bc:DATA: will retry 5 more time(s)
10/17/07 08:22:01 nsrd: media notice: Save set (3742755157) bc:<12>DATA: volume
MCLTO.005 on rd=bc:/dev/rmt/0cbn is being terminated because: inactivity timeout
10/17/07 08:22:01 nsrd: bc.marymount.edu:<12>DATA: done saving to pool 'mc lto'
(MCLTO.005) 846 MB
10/17/07 08:22:11 savegrp: command 'save -s mc -g ballston -LL -f - -m bc -l
full -q -W 78 -N DATA: DATA: ' for client bc exited with return code 1.
* bc:DATA: 1 retry attempted
* bc:DATA: 10/17/07 08:22:11 nsrexec: SYSTEM error: Connection refused
10/17/07 08:22:11 savegrp: bc:DATA: will retry 4 more time(s)
10/17/07 08:22:43 savegrp: command 'save -s mc -g ballston -LL -f - -m bc -l
full -q -W 78 -N DATA: DATA: ' for client bc exited with return code 1.
* bc:DATA: 2 retries attempted
* bc:DATA: 10/17/07 08:22:43 nsrexec: SYSTEM error: Connection refused
10/17/07 08:22:43 savegrp: bc:DATA: will retry 3 more time(s)
10/17/07 08:23:15 savegrp: command 'save -s mc -g ballston -LL -f - -m bc -l
full -q -W 78 -N DATA: DATA: ' for client bc exited with return code 1.
::::
::::
::::
10/17/07 08:26:49 nsrd: savegroup alert: ballston completed, total 1 client(s),
0 Hostname(s) Unresolved, 1 Failed, 0 Succeeded. (bc Failed)
=========================================================
It kept going on like that and failed and the client on novell box would also
down most of the time. I'm not sure if there's any way to check the log on
novell box for the networker client.
Fazil Saiyed wrote:
One thing to try would be to use compression on the client resource via
directive.
You have done right by breaking up the client save set, for the largest
saveset that fails , check and see if there is any data you can retire to
further shrink it.
You did not mention what type of connection you have to remote site and
what errors do you have when backups fail ?If the problem is server
hardware(on the client), could it get an update ?
Is it a time-out issues ? could you run the backups for the failed saveset
at different time ? is it possible to move the saveset to another server
at the same location ?
If the data transfer rate is low, you might benefit by backing up to disk
type of device(ADV File-Device). ( If you already have disk backup
licence, it may be worth a try)
Try compression option first, you can consider the rest if it makes sense
in your environment.
HTH
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
