Jump to content

jtfey

Members
  • Content count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jtfey

  • Rank
    Occasional Forum Poster
  1. There are no other backup servers. I do have SuperDuper copying one drive to another. Could that interfere with the R9 backup? I will definitely reboot that server. Thanks.
  2. Hello, I'm a newbie using Retrospect 9. I have a Tandberg Data Ultrium 4 Storage Loader. It's connected to an Apple Xserve (10.5). I'm using Retrospect 9. I'm backing up the host server, one Windows Server, one 10.6 Xserve and another 10.5 Xserve. I'm also trying to back up a second generation PowerPC Xserve running 10.4. Occasionally I get a backup, but usually I get the error message listed in the topic title. Retrospect 9 sees the server when I access the Sources window. I reinstalled the PowerPC server's Retrospect client. That worked once. Could this be a networking issue even though the old Xserve is accessible on our LAN and has no trouble connecting to the Web. Thanks.
  3. I'm an old Retrospect 6 / Exabyte 1x10 Packetloader user who's now using Retrospect 9 / Tandberg Data LTO-4 StorageLoader using Ultrium 3 tapes. In the "old days" we did a recycle backup each night night. Now, I'm using incremental. We upgraded because we wanted to backup more of our data, which is about 830 GB. My hope was that I could back up four nights a week using two tapes per backup. After about 4-5 backup sessions, however, Retrospect is asking for new media to complete the backup. I'm assuming that two tapes aren't enough capacity for our backups and that I'll need three days per backup. What's odd is that the tapes are not showing they're full. A question ... why do some tapes show greater capacity than others? Software compression is off. I'm assuming the LTO-4 Drive is using hardware compression Sorry for this rambling statement/question. I'm kind of a newbie. Any suggestions or explanations are appreciated. Thanks.
  4. My clients keep dropping off because, according to Retrospect, I have duplicate IP numbers. One number is 120.3.0.101 (the address of the server) and the other is 127.0.0.1 (default). How can I resolve this issue. I'd like to remove the 127.0.0.1 address. At one time Retospect was installed at the address 120.3.0.101. It's now on a different server, and both servers involved have been completed erased and re-installed. Thanks.
  5. OK' date=' here's where [i']"The latest for Mac...."[/i] is an unresponsive answer to the question Russ posed [color:red]"Which Retrospect client version is on Server B?"[/color] - Which Retrospect client version is on Server B? [color:orange]6.2.234[/color] - When you had the problem with pitond, what version of the client were you using then? [color:orange]6.1.130[/color] That is what I was attempting to get confirmation on. So after Retrospect has successfully connected to the client and completed the backup, the database issues continue? [color:orange]Yes[/color] - Can you confirm that the Retrospect application has reported a successful completion of the backup operation? [color:orange]Yes[/color] After the backup has completed, instead of restarting the machine, what happens if you open the Retrospect Client application, hold the Command key, and click the "off" radio button (confirming that the status field text changes to "Not Running")? [color:red]I will try that. Right now I have Server B set up to reboot after backup.[/color] UPDATE -- Yes, it does switch to Not Running. There is still the question of what Activity Monitor shows for the machine as it is experiencing the database problem. [color:red]I'll check on this. We're now set up to have someone reboot the server before I get here. But I can check on Saturday.[/color] UPDATE -- I see no "situations" in AM. I also see no evidence of pitond. [color:red]Thanks for the help![/color] Dave
  6. OK, here's where "The latest for Mac...." is an unresponsive answer to the question Russ posed [color:red]"Which Retrospect client version is on Server B?"[/color] - Which Retrospect client version is on Server B? [color:orange]6.2.234[/color] - When you had the problem with pitond, what version of the client were you using then? [color:orange]6.1.130[/color] That is what I was attempting to get confirmation on. So after Retrospect has successfully connected to the client and completed the backup, the database issues continue? [color:orange]Yes[/color] - Can you confirm that the Retrospect application has reported a successful completion of the backup operation? [color:orange]Yes[/color] After the backup has completed, instead of restarting the machine, what happens if you open the Retrospect Client application, hold the Command key, and click the "off" radio button (confirming that the status field text changes to "Not Running")? [color:red]I will try that. Right now I have Server B set up to reboot after backup.[/color] There is still the question of what Activity Monitor shows for the machine as it is experiencing the database problem. [color:red]I'll check on this. We're now set up to have someone reboot the server before I get here. But I can check on Saturday.[/color] [color:red]Thanks for the help![/color] Dave
  7. This seems to imply that you see the problem with the client installed, even if you don't actually connect to it with Retrospect? -- Not sure of this statement. With the client installed, there is a problem AFTER the Retrospect script has run. If I restart the server, the problem stops until the next time the script has run. Or are you simply noting that without the client installed, you don't back that machine up. -- Obviously, if the client isn't installed the server isn't back up. Retrospect needs the client to find the server and run the script. A distinction with a difference. -- hmmm? Dave
  8. At my daily newspaper we use an application called CirculationPro. It's a web-based app that connects to a FrontBase database on a server. Server A (Xserve) contains our Retrospect application. Within in the past three weeks I put new disks into Server A and upgraded the OS to 10.4. Server B (Xserve) has been running 10.4 for over a year. Server B is where the Frontbase database is located. It's always had a Retrospect Client installed on it. Within the last week the people using CirculationPro have noticed a slowdown in processing times. Running bigger reports that require more memory have caused the entire app to stall. If I restart Server B after Retrospect is finished with its script, the slowness problems disappear. If I remove the Retrospect Client from Server B the problems are not encountered. Any ideas why the client is causing the problem?
  9. I'm trying to work a backup strategy for 176 gigabytes. My company has an Exabyte VXA-2 1U Packetloader, which has a 10-tape library. I was hoping to do a Normal backup each day Monday through Friday. On Saturday I'm doing a recycle backup. I had figured the weekday backups would use five tapes (1 tape per day) and the weekend Recycle backup would use 2-3 tapes. We're using V23 tapes (80/160 GB). Much of our data is graphics. Most of it won't change from day to day. I'm completing the second week of backups so all the catalogs have been built. But what I'm finding is that my Normal backups are accounting for all 176 gigabytes. I thought the Normal backup would only copy those items that had been altered. The bottom line here is each day's backup is using two tapes. That's fine for the weekend but not the weekday. My question is why do the Normal backups copy all 176 gigs? What am I missing or don't understand? Thanks.
  10. I called Exabyte and the firmware was "good enough." I then reseated the FireWire cable and everything was fine. Thanks.
  11. Just bought the VXA-2 1U Packetloader and upgraded to Retrospect 6. I downloaded the update to 6.02 and the new driver. Our Server is running 10.2.8. After about a dozen force quits of Retrospect and a few restarts of the server, I finally got a script to start up. It backed up about 1 gig and then Retrospect reported it couldn't find the media. I said "enough" and realized this was going to be harder than I thought (what else is new!) Does anyone have list of do's and don'ts for these products? Thanks. I'm pretty much a bare-*ssed newbie.
  12. I'm backing up a Macintosh G3 server (OS 9.0.4) with Retrospect 4.2. The backup drive is an APS SDT-9000 (DDS III). The information is stored on two mirrored 36 GB hard drives. The amount of data on the mirrored volume is less than 15 GB. What's happening every night is that Retrospect kicks out the tape with less than 1 GB remaining and wants a new tape to finish the backup. I'm assuming (sorry) that a tape that supposedly holds 24 GB would easily handle 15 GB. Could my tapes need replacing? Any help appreciated.
×