1bdb4f25-865c-49fd-9b71-d85f702209ac Posted July 7, 2011 Report Share Posted July 7, 2011 Here's the configuration: Retrospect Server: WinXP Dual 2GHz processor, 2.5G RAM Client: Win Server 2003 Source of files to be backed up: SAN attached to Windows server (the client) on gigabit ethernet Destination of files to be backed up: NAS on gigabit ethernet Retrospect Server, client, NAS on Subnet1 SAN on Subnet2 (Win Server (the client) has 2 ethernet cards, both gigabit, one on the net with the SAN, the other on the net with the Retrospect server and the NAS) Every time i try to back up the drive, it fails with error 519 after a while. It starts and runs a while, then fails. Thoughts? Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 7, 2011 Report Share Posted July 7, 2011 -519 means that the "client" stops communicating with the "server" (in terms of Retrospect context). It happens often here, when a laptop user unplugs the laptop in the middle of a backup and leaves the office. Does this happen at a specific file? At a specific time? Is the "client" extremely busy when this happens? Anything in the logs on the "client". Quote Link to comment Share on other sites More sharing options...
1bdb4f25-865c-49fd-9b71-d85f702209ac Posted July 7, 2011 Author Report Share Posted July 7, 2011 -519 means that the "client" stops communicating with the "server" (in terms of Retrospect context). It happens often here, when a laptop user unplugs the laptop in the middle of a backup and leaves the office. Does this happen at a specific file? At a specific time? Is the "client" extremely busy when this happens? Anything in the logs on the "client". Thanks for responding. So far it happens every time. I'm just now implementing the software and have tried multiple times this afternoon. The client is a rarely-used file server (but it has almost 2T of files). Monitoring network and cpu load shows nothing excessive. In the client log file it says : Can't reserve backup client client_name error -519 (network communication failed) [date/time] Execution Incomplete Total Performance 243.5 MB/minute Total Duration 00:44:04 (00:18:54 idle/loading/preparing) Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 7, 2011 Report Share Posted July 7, 2011 In the client log file it says : Can't reserve backup client client_name error -519 (network communication failed) [date/time] Execution Incomplete Total Performance 243.5 MB/minute Total Duration 00:44:04 (00:18:54 idle/loading/preparing) Isn't that the Retrospect log on the Retrospect server? While we discuss that, please post all the relevant lines, from connecting to that client until the backup fails. And please don't erase the date/time. In my first post, I meant the Windows logs on the "client". Look for something bad happening around the time the backup fails. There is a time-out on the Retrospect server, so the "bad thing" might happen on the "client" several minutes before it is reported in the "server" log. Quote Link to comment Share on other sites More sharing options...
1bdb4f25-865c-49fd-9b71-d85f702209ac Posted July 7, 2011 Author Report Share Posted July 7, 2011 Isn't that the Retrospect log on the Retrospect server? While we discuss that, please post all the relevant lines, from connecting to that client until the backup fails. And please don't erase the date/time. In my first post, I meant the Windows logs on the "client". Look for something bad happening around the time the backup fails. There is a time-out on the Retrospect server, so the "bad thing" might happen on the "client" several minutes before it is reported in the "server" log. Oops - so client means client and not server, huh? Sorry.. Here is my entire log (not too long, but longer than i like to post on fora like this) Note: 10.0.0.3 is the client interface on the SAN network 192.168.9.30 is its interface on the NAS network 192.168.9.53 is the retrospect server The NAS IP, 192.168.9.222, never shows up. 1310046389: Main: Client version is 7.7.114 1310046389: NetStop: signaling gEndEnumIntfEvent 1310046393: NetStart: starting interface thread 1310046398: ConnStartListen: starting thread ConnStartListen for 127.0.0.1:58999 1310046398: netCheckNewInterfaces: found new address 10.0.0.3:0 1310046398: iplud: bound to address 10.0.0.3 1310046398: ipludAddMembership: adding membership for 10.0.0.3 1310046404: IPNSRegister(1): registered: "apps2"/"f87a5b2cc3ad6130" 1310046404: ConnStartListen: starting thread ConnStartListen for 10.0.0.3:0 1310046404: netCheckNewInterfaces: found new address 192.168.9.30:0 1310046404: iplud: bound to address 192.168.9.30 1310046404: ipludAddMembership: adding membership for 192.168.9.30 1310046410: IPNSRegister(1): registered: "apps2"/"7ede50ed7d67d291" 1310046410: ConnStartListen: starting thread ConnStartListen for 192.168.9.30:0 1310046431: Connection established by 192.168.9.53:1124 1310046447: IPNSRegister(0): registered: "apps2"/"7ede50ed7d67d291" 1310046467: ConnReadData: Connection with 192.168.9.53:1124 closed 1310046502: Connection established by 192.168.9.53:1127 1310046535: ConnReadData: Connection with 192.168.9.53:1127 closed 1310047374: Connection established by 192.168.9.53:1139 1310047398: ConnReadData: Connection with 192.168.9.53:1139 closed 1310047430: Connection established by 192.168.9.53:1142 1310047446: ConnReadData: Connection with 192.168.9.53:1142 closed 1310049412: Connection established by 192.168.9.53:1158 1310049435: ConnReadData: Connection with 192.168.9.53:1158 closed 1310049541: Connection established by 192.168.9.53:1161 1310049571: ConnReadData: Connection with 192.168.9.53:1161 closed 1310050284: Connection established by 192.168.9.53:1200 1310050293: ConnReadData: Connection with 192.168.9.53:1200 closed 1310050365: Connection established by 192.168.9.53:1205 1310050389: ConnReadData: Connection with 192.168.9.53:1205 closed 1310050389: Connection established by 192.168.9.53:1208 1310056587: ConnReadData: Connection with 192.168.9.53:1208 closed 1310056601: Connection established by 192.168.9.53:1279 1310056625: ConnReadData: Connection with 192.168.9.53:1279 closed 1310056626: Connection established by 192.168.9.53:1282 1310059688: ConnWriteData: send() failed with error 10054 1310059688: ConnReadData: Connection with 192.168.9.53:1282 was reset 1310059688: ConnWriteData: send() failed with error 10054 1310064514: Connection established by 192.168.9.53:1364 1310064538: ConnReadData: Connection with 192.168.9.53:1364 closed 1310064539: Connection established by 192.168.9.53:1367 1310066907: ConnReadData: Connection with 192.168.9.53:1367 was reset 1310066907: ConnWriteData: send() failed with error 10054 1310066907: ConnWriteData: send() failed with error 10038 Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 8, 2011 Report Share Posted July 8, 2011 Oops - so client means client and not server, huh? Sorry.. Yes, from Retrospect's point of view, a client is a client, even if it runs a server OS. 1310056626: Connection established by 192.168.9.53:1282 1310059688: ConnWriteData: send() failed with error 10054 1310059688: ConnReadData: Connection with 192.168.9.53:1282 was reset 1310059688: ConnWriteData: send() failed with error 10054 1310064514: Connection established by 192.168.9.53:1364 1310064538: ConnReadData: Connection with 192.168.9.53:1364 closed 1310064539: Connection established by 192.168.9.53:1367 1310066907: ConnReadData: Connection with 192.168.9.53:1367 was reset 1310066907: ConnWriteData: send() failed with error 10054 1310066907: ConnWriteData: send() failed with error 10038 It seems as the client can't send data back to the server for some reason. My guess is that you have a network problem.Try another network cable. Try another network outlet. Make sure the Windows' firewall allows port 497 (both TCP and UDP). Quote Link to comment Share on other sites More sharing options...
1bdb4f25-865c-49fd-9b71-d85f702209ac Posted July 8, 2011 Author Report Share Posted July 8, 2011 Yes, from Retrospect's point of view, a client is a client, even if it runs a server OS. It seems as the client can't send data back to the server for some reason. My guess is that you have a network problem. Try another network cable. Try another network outlet. Make sure the Windows' firewall allows port 497 (both TCP and UDP). Thanks. i've got a trouble ticket open with Roxio. Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 8, 2011 Report Share Posted July 8, 2011 Thanks. i've got a trouble ticket open with Roxio. OK. Please let us know what the problem was. Quote Link to comment Share on other sites More sharing options...
1bdb4f25-865c-49fd-9b71-d85f702209ac Posted July 26, 2011 Author Report Share Posted July 26, 2011 Never found a cause. Switched to a different server and it seems okay now. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.