canexsu Posted July 23, 2009 Report Share Posted July 23, 2009 Using Retrospect 8.1.148, 3 iMac, 1 XP Pro, 1 Vista Business. The XP Pro works fine, but every time I add the Vista client and then refresh the client list, it tells me the Vista client is busy. What does that mean? Also, this may sound like a stupid question, but, does the client need to be logged in in order for Retrospect to have access? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 24, 2009 Report Share Posted July 24, 2009 What is the exact error being reported? What version of the client is installed? Quote Link to comment Share on other sites More sharing options...
canexsu Posted July 24, 2009 Author Report Share Posted July 24, 2009 In the Sources menu, with the Vista machine selected, (client is 7.6.107), in the bottom section under status, summary selected, it says "client is busy". Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 24, 2009 Report Share Posted July 24, 2009 Are you able to browse any of the volumes from the source screen? If yes, then everything is working. Quote Link to comment Share on other sites More sharing options...
canexsu Posted July 28, 2009 Author Report Share Posted July 28, 2009 Yes I can. It seems that I get the busy message if someone is logged onto the wkstn. I always thought that Client loads at time of logon, so I left the wkstns logged in under my name. I guess logged out is the way to go. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 28, 2009 Report Share Posted July 28, 2009 If you can browse the volume, then a backup should work fine. Are your backups failing? Quote Link to comment Share on other sites More sharing options...
snackdog Posted January 11, 2010 Report Share Posted January 11, 2010 What do I do if I have a client that says Busy that I can't browse? I have a user that hasn't been backed up in a month and Retrospect seems to skip her. She is marked as busy. She's on a Mac running client 6.3.027. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted January 11, 2010 Report Share Posted January 11, 2010 What do I do if I have a client that says Busy that I can't browse? I have a user that hasn't been backed up in a month and Retrospect seems to skip her. She is marked as busy. She's on a Mac running client 6.3.027. Mike, Client is busy (1) what version of Retrospect engine (x.x.x) and Retrospect console (x.x.x) are you running? (2) What version of Mac OS (10.x.x) on the problem client? (3) What version of Mac OS (10.x.x) on the machine running Retrospect engine? (4) Are you aware that there is a later version of the Mac Retrospect client (6.3.028)? Download is here: Retrosspect 8.x Macintosh updates Russ Quote Link to comment Share on other sites More sharing options...
snackdog Posted January 11, 2010 Report Share Posted January 11, 2010 (1) Retrospect console 8.1 (build 626). I;m not sure how to tell which version of the engine I'm running. (2) Mac OS X 10.6.2 on the client. (3) Mac OS X 10.4.11 on the server (its a PowerPC machine too) (4) Yeah I just noticed that and upgraded her client. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted January 11, 2010 Report Share Posted January 11, 2010 I;m not sure how to tell which version of the engine I'm running. You have to log on to the server and do a "Get Info" on the package for the engine. Many have requested that the console show the version of each engine that it knows about. Have you restarted the problem client as suggested in the KB article I linked to? Client is busy Russ Quote Link to comment Share on other sites More sharing options...
snackdog Posted January 11, 2010 Report Share Posted January 11, 2010 It's 8.1.626.1. That feature would be handy -- that's where I looked initially. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted January 11, 2010 Report Share Posted January 11, 2010 It's 8.1.626.1. That feature would be handy -- that's where I looked initially. Yea, that feature was requested many times when the program was in beta testing, and has been requested many times since the program was, um, "released". Not quite sure what to call the current "released" state of the program, with all of its bugs. Once again, Have you restarted the problem client as suggested in the KB article I linked to?Client Busy Russ 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.