bobinpas Posted January 13, 2006 Report Share Posted January 13, 2006 I recently replaced one of my licensed client workstations with a new Mac. When we installed the new computer, we used the direct Firewire connection to automatically copy all of the data from the old Mac to the new one (as a function of the set-up assistant on the new Mac). When I went to update the existing scripts on our server I'm getting a problem -- the server recognizes the new computer but shows two sub volumes: the actual hard drive of the new computer (generically identified as "40 GB Drive") and the old workstation name (showing as a subvolume of the new computer rather than a stand-alone volume). I can't open either subvolume (the old workstation is a phantom as it's no longer running nor connected to the LAN) and get a "can't access 40 GB Drive error - 120" when I try to open the 40 GB (using the "subvolume" button). I'm assuming the license is creating the confusion and is still identifying the old volume as an active and available volume? Is there a way to redirect the license to recognize the new computer? Note: the globe icon for the old "phantom" workstation has the extra power button(?) bit on the lower right while the new "40 BG Drive" globe icon does not. I'm assuming the extra "power button" bit indicates it's a licensed client? Link to comment Share on other sites More sharing options...
CallMeDave Posted January 13, 2006 Report Share Posted January 13, 2006 The license manager doesn't deal with volumes, only with the client. So if you can see the client information in the Configure tab then the clinet is logged in. The Retrospect Volumes database will always show old volumes as grey, in case the volume comes back online. If that volume is gone forever, you should select it and press Delete to Forget it. You write: >the actual hard drive of the new computer (generically identified as "40 GB Drive") Is "40 GB Drive" the correct name of the boot volume on the new client machine? Link to comment Share on other sites More sharing options...
bobinpas Posted January 14, 2006 Author Report Share Posted January 14, 2006 No, it's called "minimouse." I think I may be confusing two things that are totally unrelated... What prompted this whole event was that my employee told me that she'd been getting a message that her workstation was not getting backed-up ever since we replaced her Mac. When I checked the log it said it couldn't "access the volume **folder icon** Library on minimouse error -5023 (server: password wrong/missing)". My first reaction was to check the script to make sure the right back-up client and subvolume path was correct. I opened the volume database. In the top section under "Local Desktop," minimouse and its properly defined subvolumes were grayed out. Below under "Back Up Clients," however, minimouse was active. That's where I noticed that the old computer was appearing as a subvolume of minimouse and the "40 GB Drive." I tried to open the 40 GB Drive to define the Library folder. That's when I got the other "can't access 40 GB Drive error -120" message. So I assumed that was my problem. Now I'm thinking it's totally unrelated. After I posted my original query above, however, I went back and tried executing the script manually. It prompted me for the password -- which I entered -- and it executed without a hitch. I manually executed every script for that workstation (there are 4 different scripts that back-up different items on different schedules) -- each one prompted me for a password first and then executed without a problem. HOWEVER, when I tried executing them a second time, they didn't prompt me for the password and executed -- so I'm guessing they'll run unattended now when the scripts execute autmatically tonight (when I'm home fast asleep)? So, long story short -- I guess it's OK now. Could this just be a new keychain issue and I just needed to enter the password on first execution? I assumed all of the passwords would have copied correctly to the new minimouse's key chain on the initial set-up -- but I guess not. I won't know until tomorrow if the scripts execute automatically tonight. I'll post again if it's still getting stuck on the password. Link to comment Share on other sites More sharing options...
bobinpas Posted January 16, 2006 Author Report Share Posted January 16, 2006 It didn't work. It still prompts for a password for the new computer when you execute the script. I've tried reentering the password in the configure clients section but it doesn't make any difference. It doesn't seem to remember the password for the new computer. Also, I went ahead and connected to the computer manually and ran the script. It ran fine except now I'm getting a handful of preference files that return an execution error 5000 no priveleges. I didn't have this problem before. Oy vey, what a pain. Link to comment Share on other sites More sharing options...
CallMeDave Posted January 16, 2006 Report Share Posted January 16, 2006 Sine the information you've provided is somewhat scattered and conflicting (the boot volume of the Client machine is named "minimouse," but "the old computer was appearing as a subvolume of minimouse and the "40 GB Drive." ", I'd suggest that the best course of action for you would be: 1 - Forget the Client from the Client Database 2 - Use the Client Installer application to Uninstall the Client software on the Client machine 3 - Restart the Client 4 - Use the Client Installer application to Install the Client software on the Client machine 5 - Add the Client machine to the Retrospect Client Database 6 - Reconfigure your scripts as necessary to access the newly installed Client software Link to comment Share on other sites More sharing options...
bobinpas Posted January 17, 2006 Author Report Share Posted January 17, 2006 That worked -- everything's running fine now. No more "phantom" drives either. Thanks for your patience! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.