Jump to content

impala

Members
  • Content count

    121
  • Joined

  • Last visited

Community Reputation

0 Neutral

About impala

  • Rank
    Occasional Forum Poster
  1. thanks everyone! rebuild catalog was smooth verify was OK repeating the copy backup script was smooth.
  2. I would still like to know the difference between repair catalog and rebuild catalog. Thanks for your suggestions. I did a disk utility repair operation on all the volumes as soon as I could after the forced power-off. No errors were found. I just now connected the toshiba-1 drive via sata instead of usb and disk utility reports the smart status is verified. so I have no other indication the drive is failing. I admit it is always possible. The volume name actually is toshiba-1 which represents member 1 of the toshiba disk media set. I plan to add more members as space is required. When I devised my naming system, I didn't know retrospect did it the other way around. ie: 1-toshiba
  3. just for fun I tried the verify again, and it stopped at the same point. Instead of trying to get it to use the member, I just stopped it. This time the log doesn't have an error, it just says execution stopped by operator.
  4. what's the difference between repair a catalog and rebuild a catalog?
  5. After I stopped the media request, I found this in the log: + Executing verify at 1/27/2010 7:58 PM (Execution unit 1) - 1/27/2010 7:58:14 PM: Verifying toshiba TMacVol::GetInfo: UGetDevicePathFromVolume failed, error 2 Total duration: 21:53:24 (21:05:22 idle/loading/preparing)
  6. which log? This is all I find: + Executing verify at 1/27/2010 7:58 PM (Execution unit 1) - 1/27/2010 7:58:14 PM: Verifying toshiba
  7. Retrospect 8.1 build 626 Mac Pro 10.6.2 I have an USB attached disk media set with one member. Yesterday Retrospect stalled during a copy backup to this media set from another disk media set. It said something about needing access to the member. I cannot find the script activity in the log, maybe because I had to force power-off the mac because the engine refused to quit. Anyway, I decided to verify this media set. Now the verify has stalled with 1,212 files to go saying it needs media. There is no other member to this media set! What now? Do I rebuild the catalog or something?
  8. In the console, go to the menu: Retrospect > Preferences. Look for the 'Rules' tab.
  9. impala

    Proactive scripts refuse to run

    thanks for sharing about the optional proactive backup log. Are there any other optional logs we can enable?
  10. impala

    Change to script Source

    I don't know the answer to your question, but I have a question. Why not create a rule to exclude the folder you do not want? It will still be scanned, but not saved.
  11. yes, all my clients are on the same subnet as the server. There is a managed cisco switch between them. I have no control over the switch. Nothing different that I can tell. I've tried it using a different network port with the same result. I ran msconfig and disabled all the non-microsoft services and startup processes except for the retrospect client, and the behavior persisted. I uninstalled client 7.6.107, renamed the system, rebooted, installed the new client 7.7.106. On the server I removed the old client and added it as a new client. same behavior. I don't know what else to try.
  12. When the firewall is off the proactive backup still does not run. I observed the following sequence of messages in the status window (on the client): Ready Connected In use by (server) for preparing.... Ready Connected In use by (server) for proactive1 Ready This would seem to correspond to the inbound tcp connections in the firewall log.
  13. When it says "waiting to retry failed attempt" is there a log somewhere that will tell me about the failed attempt?
×