Jump to content

ginnyp

Members
  • Content count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ginnyp

  • Rank
    Occasional forum poster
  1. Well . . . I'm happy!!! Reconfigured the G4 1.25 to 10.3.9, updated anything Retrospect 6 that I could update, and all is well. Got everything moved to this computer and backup ran correctly the first time I tried! Also got the scanner operating correctly on this computer in Native 9, and our "server" drive which contains our brochures and photos and is connected to this computer is accessible by all from their computers! I love working on these computers, but I got really tired of the issues I encountered with what I was trying to do on this move! Happy this one is OVER! Hopefully the next time I need to expand our backup system I won't have to deal with a SCSI device! Thanks for your help, Russ! Ginny
  2. Thanks, Russ . . . That gives me some idea what has been/is going on. Must be using an internal Retrospect driver. I'll check the RDU histories before I take the "leap." I'm a little skittish of updating internal stuff that I don't fully understand and that seems to be working! You've been very helpful. Have a great weekend! Ginny
  3. Thanks. I really appreciate the help. Getting Retrospect to work right all the time has puzzled me quite a few times. Earlier you mentioned updating the RDU. I finally figured out what that meant by digging into the Retrospect manual! I then found a (new) Retrospect driver (version 6116100) under version 6.1 for MAC in the Retrospect website, but I’m puzzled as to whether I should use it. Currently, on the computer that is successfully running Retrospect, when viewed through Retrospect Device Status, my Quantum tape drive shows a driver called “Seagate DAT DDS-DC (5.03)â€. (I know Quantum acquired Seagate.) To update the Retrospect driver, the instructions say if there is a file in the Retrospect folder called “Retrospect 6.x Driver Update†to trash it and replace it with the new one from the mounted disk image. I do not have this file in the Retrospect folder (or anywhere else). With this type of tape drive, should I stay with the driver that must have come with the tape drive instead of switching to the Retrospect version? Or, does the RDU I downloaded from Retrospect affect something else entirely? (I checked the Quantum website to see if they offered anything new for this drive on a MAC, and they don’t.) This driver issue seems to be the last issue I don’t quite understand as I attempt to set this newer computer up to run Retrospect. Again, I do appreciate the guidance. Thanks, Ginny
  4. Think I'll just set the newer computer to run on 10.3.9. Will Retrospect 6.1.230 work OK with 10.3.9, or should I stay with 6.1.126, as I've been using on the older computer I want to take out of service? Thanks, Ginny
  5. Russ, Thanks for your reply confirming my suspicions, and explaining the situation better. It's strange that 10.4 even includes the Adaptec extensions if they don't work! (If they hadn't been there at all, it might have been my "red flag" that it wouldn't work in 10.4!) Based on the cost of the ATTO card, and the fact that I'll probably have to upgrade the whole backup system in a year or two due to capacity, I'll just reconfigure this G4 1.25 to 10.3.9 for now. (Think it came with 10.2.) All that runs on it is the backup system, an old scanner in native OS9, and a shared external drive we store stuff on for general use which is attached to it. When I do upgrade the backup system, hopefully other connections will have evolved to be useful instead of SCSI. (Why was I determined to use 10.4? I wanted to have as new of OS on the computer as I felt was good, and I always liked Tiger! Didn't really like Leopard, and hate Snow Leopard, but two new computers have dictated it!) I assume in 10.3.9, Retrospect 6.1.230 will be good to use? No problems with backing up computers running Leopard and Snow Leopard? (It's been working on the G4 400 running 10.3.9 with Retrospect 6.1.126.) Guess I'll update the various computers being backed up to the newest client version? Also, don't know if I'm having brain freeze, but what does RDU stand for? Thanks in advance for your thoughts. Ginny
  6. I've been successfully running Retrospect 6.1.126 on a G4 400 running 10.3.9 to backup 5 users. The tape drive is a Quantum DAT72, and the SCSI card is an Adaptec 2906. I'm trying to move this to a newer G4 1.25 running 10.4.11. I updated to Retrospect 6.1.230 on this newer computer. On the G4 1.25, in "About This Mac," the SCSI card and tape drive both appear. When I boot the computer in native OS9 to run an old SCSI scanner, there are no communication problems (confirming that the SCSI card does work). (This is the same set-up that's been used on the G4 400 since early 2007.) However, when I try to even access the tape drive with Retrospect in OS X, I get a kernel panic when I quit Retrospect, if not before. I don't have any other OS X programs that access anything through the SCSI drive to test with. Based on the reading I've done, it appears that this SCSI card isn't compatible with Tiger? However, how come it shows up in "About This Mac" and only crashes when I access the drive through Retrospect? Otherwise, it can sit there and run all day with no crashes. I'm just looking for thoughts before I give up and reconfigure this newer computer back to 10.3.9. Thanks for any input! Ginny
  7. Thanks . . . I bought the upgrade directly from EMC, downloaded it, got it installed, and after about 4 attempts, got a successful backup started. (Retrospect is just not a very intuitive program - guess no back-up program is, and I wanted to salvage everything I could off of the old set-up. Unfortunately, I had to set the old computer up again to accomplish - copy - everything!) Didn't want to "do battle" and take the time to do two "full" backups on a program that is potentially too old to ultimately work right. Happy weekend everyone!!! Ginny
  8. Guess I wasn’t real clear about what I’ve already done – am trying to do. I installed Retrospect version 5.1.175, for OS-X and copied the file “DAT Directory” into the Retrospect file of the “new” computer (from the Retrospect file of the old computer running on OS-9). I thought Retrospect would pick up everything it needed from the files in the DAT Directory, but instead, I found it seemed to want me to reconnect to the computers I back up and go through a complete new script set-up. I was hoping it would just be able to continue the “normal” back-up on the two tapes I’ve been alternating on recently, but it appears “full” back-up will be needed. The “new” computer I’m using for back-up is a PowerMac G4, 400 running on OS 10.3.9. It is backing up four MACs running OS 10.4.9 (two are new Intel G5s), and one MAC still on OS-9. The computer I’m running back-up on is one that has been “retired” from daily use and is dedicated for back-up only. I back-up to a Quantum Dat-72 tape drive that is about a year old. I am not backing up everything on every computer – only each person’s work files and select files containing unique data that would help get them running and back-to-normal quicker if their hard drive crashed and lost everything. (After a total crash, I’d rather start with a fresh operating system and freshly-installed software.) Fortunately, for the 12 or so years I’ve been doing the back-up for this department, the only things I’ve had to restore are files a user trashes from their computer in error, then they ask, “can I get it from back-up?” I don’t know what metadata is, if I’m even backing any of it up. Guess I’d better look into upgrading to 6.1, though. Thanks. Ginny
  9. I have a version 5 package that has been backing up several MACs via a MAC on OS-9. I've moved the software to a newer MAC running OS-X. The installation seems to be OK, as it can see the computers I want to back up, but before I really set anything up, was wondering how to get it to work off of the DAT Directory I copied from the old computer to this one. I put it in the Retrospect file. I was hoping I wouldn't have to start an all new back-up. Thanks.
×