breadiu Posted April 29, 2005 Report Share Posted April 29, 2005 I just upgraded from Single Server 6.5 to Multi Server 7.0.265 (I also have the 7.0.3.101 driver update). We are using a Dell NAS running W2K3 Appliance Edition to run Retrospect and store the data locally. After upgrading to Retrospect 7, there are problems connecting to all of the clients. The clients are running the 6.5 client. The e-mails I receive say it's a "-519" error, but when I try to "test" a client using the Live Network utility, I get a 541 (client not running) or a 530 (can't connect to client). If I manually install the 7 client, the problem is resolved. This is a big issue because we have a large number of clients, and manually installing the client on each machine is a huge effort. Are there any ideas on how I can fix this problem? Can I remotely install the 7 client? Also, while proactive backup is running, the responsiveness of Retrospect is AWFUL (but only in 7 - it was fine in 6). It's set to wait to poll for 90 seconds - and the other settings were always fine in 6. How can I improve the responsiveness? Thanks! Bret Link to comment Share on other sites More sharing options...
edwardotis Posted May 2, 2005 Report Share Posted May 2, 2005 Bret, did you ever get help with this? I'm interested to find out before we consider upgradeing from 6.5 to 7. Thanks, Ed Link to comment Share on other sites More sharing options...
breadiu Posted May 3, 2005 Author Report Share Posted May 3, 2005 Nope, sure didn't. We couldn't wait any longer, so we started manually upgrading to 7. Link to comment Share on other sites More sharing options...
natew Posted May 20, 2005 Report Share Posted May 20, 2005 Hi Go to configure->clients and click on the update icon. This will allow you to push a client updater file to all clients on the network. No need to manually install. FWIW this info is on page 169 of the user manual in the section entitled "updating clients". Thanks Nate Link to comment Share on other sites More sharing options...
breadiu Posted May 25, 2005 Author Report Share Posted May 25, 2005 Thanks for the advice. I don't know why I overlooked this! Do you have any advice on how to improve the responsiveness? It's still very slow. From clicking the "Stop" proactive button to the Yes/No confirmation popping up is 15 seconds. It makes it nearly impossible to perform any maintenance on the system. Thanks, Bret Link to comment Share on other sites More sharing options...
natew Posted May 27, 2005 Report Share Posted May 27, 2005 Hi Proactive can eat up a fair share of CPU and RAM. What are the hardware specs of the NAS? Any chance you can throw more memory in there? Thanks Nate Link to comment Share on other sites More sharing options...
breadiu Posted May 31, 2005 Author Report Share Posted May 31, 2005 It's a 2.80 GHz P4 with 512MB of RAM. It doesn't look like it's eating processor or RAM, because I can open the task manager, and watch it as I try to move around in Retrospect. When I try to do something in Retro, the processor utilization remains under 2% and the total amount of available physical memory is 287820 K. It seems like it's more something odd in Retrospect, as compared to a lack of resources. Thanks for your advice. Link to comment Share on other sites More sharing options...
natew Posted June 1, 2005 Report Share Posted June 1, 2005 Hi As a test, try setting the Retrospect security preferences to run as "logged in user", relaunch Retrospect and let proactive do its thing. Is it still slow? If this speeds things up then the problem is likely related to domain authentication for the user specified in the Retrospect security settings. Thanks nate Link to comment Share on other sites More sharing options...
breadiu Posted June 1, 2005 Author Report Share Posted June 1, 2005 Unfortunately, it was already set to run as the logged-in user. Any other ideas? Thanks! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.