Jump to content

mrjimfuller

Members
  • Content count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mrjimfuller

  • Rank
    Newbie
  1. I have found a work-round to my problem. Rather than try and backup the Netware server complete, and let Retrospect discover what volumes are on the server, I have set up each volume as a separate job. This has worked well.
  2. Hi, I am having problems backup up a Netware server to our Retrospect Server. The versions involved are:- Netware O/S 6.5 SP5 Netware Client 7.5 Retrospect Server O/S Windows Server 2003 SP2 Retrospect Server Version 7.5.508 (Driver & Hotfix 7.5.14.102) Every time we try and backup the neware server it sucessfully backs up the first few (small) volumes, then the first couple of hundred of Mb of the next volume, Then it fails as follows:- ..................... - 19/02/2009 11:56:11: Copying Server Specific Info on I-HOLD 19/02/2009 11:56:29: Snapshot stored, 5 KB 19/02/2009 11:56:30: Execution completed successfully Completed: 1 files, 1 KB Performance: 0.1 MB/minute Duration: 00:00:18 (00:00:13 idle/loading/preparing) - 19/02/2009 11:56:33: Copying SHRDATA: on I-HOLD Trouble reading files, error -519 (network communication failed) 19/02/2009 12:07:34: Execution incomplete Remaining: 453 files, 631.0 MB Completed: 1 files, 2 KB Performance: 0.1 MB/minute Duration: 00:11:00 (00:05:47 idle/loading/preparing) - 19/02/2009 12:07:34: Copying SOECIC: on I-HOLD Can't reserve backup client I-HOLD, error -519 (network communication failed). .......................... Meanwhile the retroclient.log on the Netware server is giving :- 1234882664: Connection established by 152.78.136.114:1033 1234882689: ConnReadData: Connection with 152.78.136.114:1033 closed The next time we try an run this it carries on where it left off, backs up a few hundred Mb more and then fails. There is no shortage of space on the Retrospect Server. We have many hundreds of users at the site of the Netware system successfully accessing resources at the location of the Retrospect Server, so we are happy the network is working OK. Does anyone have any idea what is going wrong ? Jim
×