Jump to content


  • Posts

  • Joined

  • Last visited

archrenov8's Achievements


Newbie (1/14)



  1. I manage a network of ten macs in our office. When I buy new macs, I give them to our fastest people, and shift their macs to others in the office. Then I clear out the drives, and generally give away the oldest machines. With recent OS improvements, it is relatively easy to transfer the apps and docs from an existing mac to a new (empty) mac, although a few things are still missing). Then I need to reassign that older mac to someone else in the office. For instance, Nick just got a new G5 dual 2.5, and I am now trying to reassign his G4 Dual 1 GHz to Aaron. I wanted to take everything from Aaron's old G4/450 over to the G4 Dual 1 GHz. How do I move his Retropsect Client over? I cannot even see his computer on the Retrospect Network, even though he shows on my network through the finder. I have four other new macs (two G5's and two PowerBooks) coming later in the week, and I don't want to do this wrong again. I will be moving Retrospect to another computer as well, but there are clear instructions for that on your website. It is primarily the client that I am having issues with.
  2. Dave, I just reconnected using the firewire cable, and checked the System Profiler. It showed FireWire> FireWire Device Tree>FireWire Bus>FireWire Device, and then in the box below: FireWire Bus: Speed: 400 Mb/sec Speed So then I restarted my Mac, and in the box below, it showed a little more info: FireWire Bus: Speed: 400 Mb/sec Speed FireWire Device: Speed: 400 Mb/sec Speed Then, when I disconnected the firewire cable, and connect the USB cable into the back of my keyboard, nothing comes up as indicating the tape drive. Same thing even with a direct USB connection to the back of the Mac. I guess I am supposed to be seeing more specific information than that, huh? Actually, the real Retrospect message is "No devices found." Is there a way to actually repair the FireWire bridge. Glen
  3. Hi Nate, It was totally random on the G4/400. Since I replaced the first tape drive with another, and the intermittent problem recurred after a few back-ups, I have not moved the tape drive to another mac again to try to duplicate the results. I have been looking for definitive instructions on hot-swapping firewire devices, or what sequence should be followed in powering them up. I thought those issues vanished with OS X. There didn't seem to be a way from within Retrospect to force it to find the device. Glen
  4. I recently installed Retrospsect 6.0 Workgroup on my G4/400 desktop, running latest version of Panther. I am backing up nine macs all running Panther. I also purchased a LaCie firewire AIT2 U&I Tape drive. For several backup sessions, everything was fine running on the firewire cable. Then, suddenly, with no changes, I started getting the message: "No firewire devices found." when I would check devices, and backups would fail. I called LaCie, and they suggested going to another computer, and trying the same thing, and when that failed as well, they replaced the drive through my vendor. Now I am having the same problems with the new drive, only two weeks old. Except this time, it has been intermittent. I was able to get it to be recognized by unplugging the cables, re-connecting, and restarting. But even that is not consistent. Are there any settings or ports to enable? What is the procedure to connect a firewire device, in terms of it being on when the computer starts up?
  5. When I did my first and only OS X backup, on January 30, (OS X on the server and on three out of eight clients), the size of the backups grew so significantly that it would not fit on one tape. So we weeded out what we were backing up to get them to manageable sizes. A week later, I tried to do another backup, and before doing so, I figured I would check to make sure everyone was still logged in. That is when I noticed the problem with two of the OS X clients. When I was originally configuring the three OS X clients, I had difficulty, and the only way I could get them to be logged in was to "Add by address". My personal computer is one of the three OS X clients, and since I am usually in first in the morning, I think our cable carrier assigns me to the first available address, so RS Server seems to have no problem finding me again. However, my other two OS X clients had different addresses, and that caused the problem. Now that I have read more RS documentation, I realize that I should not have added them that way. So, this morning, I tiried to follow your advice, and I "Forgot" the two troublesome clients. Then, when I went back to try to log in again, they simply did not show up at all. The only option I had was to add them by address again, and I wasn't about to do that. BTW, all of the OS X Clients are set not to sleep. I checked for pitond on the OS X Clients, and that was there. Is "pitond" something that RS Client uses but not RS Server, because it does not show up on the server? I also pinged one of the clients successfully (I didn't bother with the second one). As for seeing "forgotten" clients showing up greyed out, yes, that is the way it has been in the past (at least under OS 9). I don't know what to do to make it see the clients. From the server, I am able to connect to the two missing OS X clients across the network, so I know the network is OK. I was going to try to reinstall the client software this morning, but ran out of time. I don't know what to do next.
  6. Yes, I do see the three OS X Clients when I go to Configure>Clients>Network. It indicates that they are Not Connected. When I click on Connect, it tries to connect and then comes back with "Client not visible on Network-error 1028." It is only connecting with one of the three OS X clients, which happens to have the same IP address as when we backed up last. When I try to Connect using Add by Address..., I plug in the current IP address and then comes back with: "Activator Code conflict found. See log window for details. Different computers may become confused with one another, causing backups to fail."
  7. I have just upgraded to my OS X Server to Retrospect 5.038 as I migrated the server from OS 9.1 to OSX on a beige G3/233, with a variety of OS 9 and OS X clients. All of the OS 9 clients are 5.0.238, and all of my OS X Clients are 5.0.540. I successfully logged on to everyone on the first day, although the first time I had trouble with a two of my three OS X clients. I had to trick it into logging in by "Adding by address". Well, the first attempt at backing up did not go well. I had error -102 trouble communicating with an OS 9 client, followed by error -519 communication failed, and several error -1028 not visible on network on two of my OS X clients, and on two OS 9 clients. Basically, my first OS 9 client was the only one to back up successfully. Today, I went back to the Configure panel, and this time had to log in to all three of my OS X clients by Adding by address". However, with one of them, I couldn't even do that. It said "Activator code ... is used for multiple clients: HGA Powerbook at HGA Powerbook at" It instructed me to go the the Log, which confirmed this. We have a cable modem and router, so we are set to DHCP, so the TCP/IP addresses are changing daily. This seems to be preventing the OS X server from communicating with or logging on to the OS X Client. I also do not want to have to log in by "Adding by address" each day. This would entail opening up the System Preferences >Network panel and copying the assigned TCP/IP number each day for each OS X machine. I do not want to migrate the remaining macs to OS X until I resolve this backup issue.
  8. I had the same situation when I migrated my first client from OS 9 to Jaguar, Error 108. In my architecture firm, we run eight clients off of our OS 9 server (a beige 266 G3 desktop). Through some trial and error, I had to watch what was happening with the backup, and I realized that it was running out of memory when it was backing up the OS X mac, but not the others. It seems that in OS X, it may scan massive amounts of files searching for the enclosing paramters for backup (this is just my guess). At any rate, I had to increase the memory allocation for my OS 9 server to something like 45,000, AND I had to make sure that at the end of the day (since we are scheduled for 8:00 pm backups), that all other apps were quit on the server mac. That way, there was nothing else competing for that kind of RAM. Seems to work fine now. I just wish the OS X client would shut down afterwards. I suspect that you started encountering problems as the sheer number of files to be scanned on your Powerbook increased. Glen Grayson
  • Create New...