Jump to content

inchley

Members
  • Content count

    10
  • Joined

  • Last visited

Community Reputation

1 Neutral

About inchley

  • Rank
    Newbie
  1. inchley

    Repeated catalog errors

    OK, Russ. Many thanks. Martin
  2. Anyone interested in this thread please note that I posted it again in a more appropriate forum - the one specifically for Retrospect 8.1. There's been a discussion there about a possible bug or an incompatibility with the VXA-320 drive. We'll close this thread here. Martin
  3. inchley

    Repeated catalog errors

    Thanks Russ. I don't know where this leaves me. Retrospect 6.1 gives me a different set of problems which I was hoping to cure with an upgrade. Does experience suggest this might get addressed quickly if it is a bug (I don't know who you mean by 'Robin')? I would probably be moving to different software by now (e.g. Tolis BRU), if it were not for Retrospect's proactive function, which is really useful for a couple of staff with laptops and local accounts. Any final comments welcome. Happy Christmas! Martin
  4. inchley

    Repeated catalog errors

    Russ -some extra Info: I installed Retrospect on a 2009 Xserve running OS X Server 10.5.8 and transferred the VXA-320 to that machine, to check that it was not the Mac mini itself. I ran an equivalent test – Recycle backup of the main hard drive (about 35 Gb of files) followed by a normal backup of the same drive. I got exactly the same behaviour as with the Mac mini - the Recycle backup was fine, while the Normal backup failed at some point during or after scanning, with the Catalog file out of sync message. Console log for this point reads: 12/23/09 1:11:59 PM Retrospect[51999] *** -[NSCFString appendString:]: nil argument 12/23/09 1:12:02 PM Retrospect[51999] *** -[NSCFString appendString:]: nil argument 12/23/09 1:13:23 PM com.retrospect.RetroEngine[51981] #2> !/&OK//&Stop///!$[43]Catalog File out of sync with Media Set "$[01]Media Set A$[02]". 12/23/09 1:13:23 PM com.retrospect.RetroEngine[51981] To repair it, use Tools>Repair Catalog>Update existing Catalog File. Martin
  5. inchley

    Repeated catalog errors

    Thanks for the response, Russ. I downloaded the trial last Friday (18th December) Retrospect Console 8.1 build 626. I assume the engine is the same, though I can't see where the info is obtainable. All the settings are standard: Mac mini HD formatted HFS+. This is the only hard drive, and is running the Retrospect engine. Same behaviour whether I use the console from my 10.5.8 iMac, or locally on the Mac mini. Retrospect files at /Volumes/Macintosh HD/Library/Application Support/Retrospect. Catalog folder is there. Martin
  6. inchley

    Repeated catalog errors

    Just to note: A 'recycle' backup, backing up only the backup server's own HD, worked fine. A 'normal' incremental backup immediately following, again backing up only the backup server's own HD, failed with a 'catalog file out of sync' error. Martin
  7. I've already posted this in a different forum, but this is probably the more appropriate one. Sorry if it offends anyone posting twice. I'm evaluating Retrospect 8.1, after limping along with 6.1. We've been with Retrospect for years, and with VXA for about 6 years. Backup Server: Mac mini, Intel Core 2 duo 1.83 GHz, 2Gb RAM, OS X 10.5.8. Backup device: Tandberg VXA-320 tape storageloader, Firewire, about a year old. Source clients: about 10 Macs, mixture of G4, G5, Intel, all OS X 10.4 or 10.5, including two on OS X Server. Retrospect 8.1 multi-server edition, under an evaluation licence. Running a script (Recycle or Normal - behaviour the same with both )to back up all machines, the Mac mini itself is backed up, including a successful verification, but as soon as the script starts on the next machine in the list, we get a Catalog out-of-sync message. I have: 1. Checked that all software and firmware on the Mac mini and the VXA drive is up to date. 2. Changed the firewire cable. 3. Tried the Repair function - Retrospect reported success in repairing but then immediately gave the same error when I tried to do a backup. 4. Tried the Rebuild function - again, Retrospect reported success in rebuilding but then immediately gave the same error when I tried to do a backup. 5. Tried omitting the first networked computer in the list from the script in case the computer was the problem - no effect. 6. Completely uninstalled Retrospect 8 and all its files, followed by a reinstall. No effect. 7. Tried running it both from the server itself and from a networked Mac. No difference. 8. Used vxatool and libtool to move the tapes around the VXA-320 and re-format them. (Note that you need to stop the Retrospect engine via System Prefs first, to avoid horrible conflicts from having two processes address the backup device at the same time.) No benefit. I note that another thread also suggested Retrospect 8.1 and the VXA-320 do not get along. Is this what it is? I'm very open to questions and suggestions - I really do want to buy this software but it's not looking likely at the moment. Martin
  8. I'm evaluating Retrospect 8.1, after limping along with 6.1. We've been with Retrospect for years, and with VXA for about 6 years. Backup Server: Mac mini, Intel Core 2 duo 1.83 GHz, 2Gb RAM, OS X 10.5.8. Backup device: Tandberg VXA-320 tape storageloader, Firewire, about a year old. Source clients: about 10 Macs, mixture of G4, G5, Intel, all OS X 10.4 or 10.5, including two on OS X Server. Retrospect 8.1 multi-server edition, under an evaluation licence. Running a script (Recycle or Normal - behaviour the same with both )to back up all machines, the Mac mini itself is backed up, including a successful verification, but as soon as the script starts on the next machine in the list, we get a Catalog out-of-sync message. I have: 1. Checked that all software and firmware on the Mac mini and the VXA drive is up to date. 2. Changed the firewire cable. 3. Tried the Repair function - Retrospect reported success in repairing but then immediately gave the same error when I tried to do a backup. 4. Tried the Rebuild function - again, Retrospect reported success in rebuilding but then immediately gave the same error when I tried to do a backup. 5. Tried omitting the first networked computer in the list from the script in case the computer was the problem - no effect. 6. Completely uninstalled Retrospect 8 and all its files, followed by a reinstall. No effect. 7. Tried running it both from the server itself and from a networked Mac. No difference. 8. Used vxatool and libtool to move the tapes around the VXA-320 and re-format them. (Note that you need to stop the Retrospect engine via System Prefs first, to avoid horrible conflicts from having two processes address the backup device at the same time.) No benefit. I note that another thread also suggested Retrospect 8.1 and the VXA-320 do not get along. Is this what it is? I'm very open to questions and suggestions - I really do want to buy this software but it's not looking likely at the moment Martin
  9. I think it would be almost impossible to get anything from Activity Monitor. We would only know there was an issue after the event, when Retrospect reports that the backup failed. Activity Monitor shows real time scenarios. I understand what you mean about Rosetta, but I would have thought that 2 Gb was enough for Retrospect 6.1 since this is the only application running.
  10. Running Retrospect 6.1, I get regular 'not enough memory' messages (error -108). Sometimes Retrospect then continues OK to the next machine, sometimes the backup terminates. Before upgrading to Retrospect 8, I need to know the cause, and would be grateful for comments. Martin Setup: Retrospect 6.1.230 Server version - this is the only application running apart from the system software. Mac mini, 1.83 GHz Intel Core Duo, 2 Gb RAM, Mac OS X 10.5.8 Tandberg VXA-320 Firewire StorageLoader Backing up about 12 networked computers (Mac OS X 10.4 or 10.5), including 2 servers running OS X Server Message in Console at the time when the problem occurs: 15/12/2009 23:13:55 Retrospect[14990] Retrospect(14990,0xa09b6820) malloc: *** mmap(size=147025920) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug
×