Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About airnorth

  • Rank
    Occasional Forum Poster

Profile Information

  • Gender
  • Location
    San Antonio, TX
  1. I've found the only way to reduce the CPU cycle usage was to exclude all mounted volumes in the config file. My problem now is that the retroISA process continues to consume large amounts of RAM - between 1.18 and 1.25GB. That seems excessive and I have not found a way to reduce it. Killing the process and restarting starts at a few MB but rapidly grows to consume over 1GB in seconds. Has anyone else observed this? Today, retroISA process is consuming 1.15GB real memory and 1.22GB virtual memory. On an 8GB system this is a lot of memory to be eating up for one process. This really needs to be corrected along with the excessive CPU usage of the scanning.
  2. Well my system is backing up to SATA HD's not tape. And yes, I heard Larry comment on MacVoices (or maybe MacNotables) as well. I like Retrospect, but it seems as if it is falling behind. While Retrospect lead the pack back in the 90's and early 2000, it is now just barely holding on. Someone really needs to get the Mac version on par with the PC version. I'm on a Gig network and am using all dual processor systems. We could really take advantage of backing up multiple computers at the same time rather than running things sequentially all weekend long.
  3. For some time now I've noticed that Retrospect will show up in the Activity Monitor as not responding. Typically after it's done a scan, then matching, and again when closing the catalog. I've recently moved this from an old G4 tower to a newer G5 2x2GHz machine and have the exact same behavior. Is this a known issue? I've searched the forums and have found a lot about hangs and quits, but nothing that seems to match what I'm seeing. And while we are at it, has anyone noticed that this program hasn't been updated since 2005? I think it was in October 2005 when the last update was released. I've used Retrospect for 10 years now, but I'm already looking around for other more up-to-date software.
  4. I've got a PM G4 with OS X.4.3 running nightly backups. Since the 10.4.3 update, Retrospect has been hanging the machine, resulting in corrupted backup sets and catalogs. I'm just wondering if anyone else has been having this problem. If not, I'm going to conclude it is the machine and start there. I have already run TTP and DiskWarrior and that has not solved the problem. I've also tried running it under a different user to rule out problems with a particular account. I've also noticed that Retrospect tends to hang on this machine for minutes at a time when it is scanning and matching (using Activity Monitor I can see it go red and start using 80-90% of the CPU). All suggestions welcome.
  5. Dave, The article you reference deals with Duplicating a drive, however I am doing a backup. That not withstanding, I'm not getting an assertion check error either - just the internal consistency check error. I only found it curious that if I delete the directory Flash creates on launch Retrospect will backup without errors. If I leave that directory, Retro will crash with the internal consistency check error. If I leave the Flash created directory, but run Disk Utility and let it repair the permissions and then run Retrospect, the backup will succeed; if I don't correct the permissions, the backup fails. So they way I see it several things are happening. Flash is creating a directory in /Users/Shared that clearly Retrospect doesn't like and even Apple's Disk Utility identifies as having incorrect permissions set. There might be a problem with the Flash application, specifically the 7.2 update. If I run version 7.0 that directory never gets created and Retrospect marches on. Retrospect may be having problems in regard to the new features in Tiger - I know that there are outstanding issues and that the recently released update wasn't meant to be the final fix for all Tiger related issues. On a personal note, I've been reading these forums for a while and I have a lot of respect for your knowledge of the application and I value your opinions and suggestions. However, in this form of communication tone is sometimes hard to distinguish and so I can't really tell if you are being sarcastic in your post or incredibly condescending.
  6. I have been having an interesting problem with performing a Retrospect backup lately and I thought it was tied to Flash. Here is the scenario: Retrospect server which is an AGP G4, 1GHz, 1.5GB RAM, 2x100GB HDs on Apple bus, 2x250GB Western Digital HDs on a Sonnet PCI 133 card. OS is 10.4 and 10.3.9 (I have a version of each OS, 10.3.9 on one internal 100GB drive, 10.4 on the other) and Retrospect version 6.0.212. Retrospect client is a G5 running OS X.4, latest firmware, 4GB RAM, 2x250 internal HD in RAID 0 stripe, client version of Retrospect is 6.0.110. After upgrading to Tiger (format and clean installed – no upgrades or archive installs) the Retrospect software was updated. For the next week backups proceeded without problems, but then, two days ago, I started getting the following: Trouble in Retrospect – Internal Consistency Check failed: Assertion check at “tree.c-3444” I looked up the error in the Retrospect manual and tried the suggestions there. First, rebuilding the backup set catalog. Got the same failure at the same point in the backup. I then moved the Retro.config and Retro.icons files out of the Retrospect folder and into the trash, per instructions, and tried again. Same error. I made a note of the file where Retrospect was failing (00002912.html) and then went to the client and did a search for it. On the G5, in /Users/Shared there is the following: /Library/Application Support/Macromedia/Flash MX 2004/en/Configuration/00002912.html Just for grins I deleted the /Users/Shared/Library directory and left the Finder window open. I launched Flash MX 2004 again and saw the Library and all subdirectories recreated. I deleted it again and re-ran Retrospect. Retrospect ran completely, backing up all 47.2GB without errors. I've run Flash again since then and the directory is recreated, but this time different - it contains under Configuration /Help Panel/Dump. So, I am wondering if anyone else out there has had this problem yet? I’m also wondering why Flash is creating this directory in /Users/Shared and not in /Library or ~/Library? I don’t use Flash very often, so deleting that directory is no big deal for me but I would like to know if this is my problem or if anyone else has seen it? I checked both the Retrospect forums and Flash support sites and didn’t seen anything relevant. I’m guessing that this is something specific to my installation on the G5.
  7. Yep, that took care of it. Thanks Dave. I use VersionTracker to try and keep everything updated, but I guess I missed that one.
  8. I ran this again, but interupted the shutdown process and just quit Retrospect, then started it again and no error message. Is it possible that if Retrospect is running and the computer (even if the script is what causes the system to power off) shuts down without quiting Retrospect first, it sets this flag? That would make sense because as far as the application is concerned the computer was powered down for some reason without it terminating first.
  9. I have it scheduled to shutdown the computer. The script is scheduled to run at 12:01 AM. It runs fine and does shutdwon the computer correctly. The next time Retrospect launches the message window pops up and reads "Automatic execution unexpectedly terminated, possibly due to a power failure or system crash..." A review of the log file shows that all scheduled backup have completed successfuly. For example, here is one I did following your request: ? Retrospect version 5.0.203 automatically launched at 6/12/2002 3:39 AM + Normal backup using User Directory backup at 6/12/2002 3:40 AM To backup set user stempnad Backup… - 6/12/2002 3:40:09 AM: Copying Users on Macintosh HD X… 6/12/2002 3:42:31 AM: Execution completed successfully. Completed: 73 files, 151.9 MB, with 25% compression Performance: 132.0 MB/minute Duration: 00:02:22 (00:01:13 idle/loading/preparing)
  10. Sorry about that... Version 5.0.203 under OS X.1.5
  11. I have Retrospect on a desktop configured to do a backup and then shutdown. When I start Retrospect, or if it launches automatically, a window pops up saying that the last backup failed possibly due to a system crash or power failure. A check of the Retrospect logs shows that all scheduled backups have completed successfully and checks of the backup sets, including restores, work perfectly. Has anyone else seen this? Any ideas why the backup failed flag may be getting set?