21c2d767-6670-4671-ba85-7fe66d5cc6aa Posted June 25, 2011 Report Share Posted June 25, 2011 Hello, I have Retrospect v8.2.0 (399) installed on OS X Server v10.6.5 with 7GB RAM. I am using Retrospect to backup a .bak file (SQL) from a Windows 7 Pro 64-bit system with 8GB RAM. Both the server (Mac) and the client (Win) identify their network connections as operating at 1Gbps. This particular file transfer is slow. The performance at the moment is 6.8MB/s. The network utilization in the task manager for Windows shows less than 1% in use. Activity monitor for the Mac server shows network activity on the order of tens of KB. I am not encrypting the Retrospect traffic. Where should I be looking for what is causing Retrospect to backup at such a slow speed? Thanks for reading! Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted June 25, 2011 Report Share Posted June 25, 2011 Hello, I have Retrospect v8.2.0 (399) installed on OS X Server v10.6.5 with 7GB RAM. I am using Retrospect to backup a .bak file (SQL) from a Windows 7 Pro 64-bit system with 8GB RAM. Both the server (Mac) and the client (Win) identify their network connections as operating at 1Gbps. This particular file transfer is slow. The performance at the moment is 6.8MB/s. The network utilization in the task manager for Windows shows less than 1% in use. Activity monitor for the Mac server shows network activity on the order of tens of KB. I am not encrypting the Retrospect traffic. Where should I be looking for what is causing Retrospect to backup at such a slow speed? Thanks for reading! It could be anything: The NIC in the Wiundows machine. The NIC drivers in the Windows machine. The network outlet used by the Windows machine. (We had this problem once: All network traffic was working just OK, but Retrospect didn't. Setting a small 8-port switch in the next office and connected to here instead: Presto: no more slow backups.) The network switches. The nework routers. You name it... Quote Link to comment Share on other sites More sharing options...
21c2d767-6670-4671-ba85-7fe66d5cc6aa Posted June 30, 2011 Author Report Share Posted June 30, 2011 Restarting the Windows 7 server solved the problem. My guess is that the Retrospect daemon/process (whatever you call it on Windows) was not operating at maximum speed. 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.