Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About cfrost113

  • Rank
  1. I recently purchased this product on behalf of a large medical establishment in the midwest. I am highly disappointed in the workmanship of this software and how many errors we have experienced. I am considering going back to the FREE solution that was working before we had Macintosh's to back up. It is called "BackupPC" and works great for Windows workstations. It can also be configured for a Macintosh from what I understand. It can use SSH/rsync which is very fast. I use it to back up workstations across slow WAN links, fast WAN links, LAN's, etc with no "network timeout" issues or other various errors that we have dealt with recently. The pain of converting the base OS on the backup server now is probably not going to let me go back since it runs on Linux (i use Debian primarily), and it was switched to Windows Server 2008 R2 64bit. I have also put in a few tickets through before and it took them weeks to get an answer. Not really an answer just a "blame the OS" or "blame the hardware" response, with no real resolution suggestion. Hindsight is 20/20, and I wished I found this forum before purchasing this software, for sure. I understand that most of the problems everyone is experiencing is due to the changing of hands and lack of development time because of the reorganization, but please don't sell a product you CAN'T support, period.
  2. Still getting this issue after adjusting various TCP/IP settings, and reverting to default settings. I am also getting this issue from all of my Windows Servers/client workstations that are on the proactive backup scripts. Any solutions suggestions? Does anyone even listen to these forums anymore? Did Roxio forget people still use/buy this product?
  3. I have done some optimization of my network adapter's settings on the server just to see if this had any effect. I am running an Intel Pro 1000/EB network adapter on a S5000VSA motherboard. The main issue that i was having was a TCP/IP problem. We were getting a lot of TCP Zero Window packets coming from the clients because they were receiving too much data from the server. The server was basically not waiting for the clients to be done processing packets and send another window to receive more packets. I actually turned off all flow control of any Tx and Rx packets on the server and this mitigated the issue somewhat. Also, I turned off TCP Checksum Offload and IPv4 checksum offload, because for some reason Wireshark will get these as error packets before the NIC has a chance to process them, so i turned it off to clean up the packet capture a bit. This could have affected the performance of the CPU on the server somewhat, but since i'm running a Xeon 5570, i'm not worried :X Has anyone else seen this issue? Please post your thoughts and any experience you might have had with this error. Thanks! I was able to back up a client Macintosh with no issues of timeouts or anything. Got a full backup out of the first try.
  4. Thank you for that, I will try this and I'll post my findings on here for all to see
  5. This seems to happen on all macintosh workstations that we have configured for. They are all running the latest version of the Retrospect client (6.0.329) on MacBook Pro's running OSX 10.6.4, and the server runs version 7.7.341 (64bit) on Windows Server 2008 R2. It seems that when doing either a proactive or a scheduled script for each Macintosh (they have their own backup set for each laptop), they start ok and get some data then fail. Here's an example output from the log of one laptop: + Normal backup using %username%'s Macintosh Backups at 11/8/2010 2:30 PM (Execution unit 1) To Backup Set Mac Backup Set A... - 11/8/2010 2:30:19 PM: Copying Macintosh HD on %username%’s MacBook Pro Trouble reading files, error -519 ( network communication failed) 11/8/2010 2:49:43 PM: Execution incomplete Remaining: 30232 files, 18.2 GB Completed: 264 files, 1.1 GB, with 0% compression Performance: 110.9 MB/minute Duration: 00:19:23 (00:09:32 idle/loading/preparing) To mitigate this so i can get an entire backup set to start from, i set the retry timeout to 1 minute and all of the other laptops kept doing this error, but i eventually accumulated all of their data. I was able to get my initial first full backup from them. One of the laptops i have still not been able to get a full backup only because this error constantly comes up so often that it crashes or freezes the "retroclient" process on the MacBook Pro it's running on. I have even seen it kernel panic because of this. I verified the entire time that network connectivity was ensured. There is only 2 switches in between the server's NIC and the client's NIC's. Basically, the layer 2 would be from Server NIC, to switchport on server switch 1, through trunk to distribution switch, to switch port of the client, through a Cisco Voip phone, to the client workstation. I even tried without the Voip phone on the same switch and still got the network timeout values. I took all spanning tree configurations out and any QoS configurations out also. This just makes no sense now, so any help is greatly appreciated!