Backup Set drive corruption

[banjojr]

Haven't been here in a while. Have a 3 x Firewire drive Backup Set. Just did a (very slow, it seemed), Recycle backup. The source drives are 1 internal on my PPC, plus 2 internals on another PPC. Running v6.0.204. When it got to within 9GB. of backing up the 2nd drive on Mac #2, it showed a disk error in the Log.

Duly used Disk Utility on that Mac; seems to have repaired OK. Can I run a recycle backup for that now-fixed drive alone, and add it to the successful Recycle data on the other 2? I suspect not. I would have to do another Recycle B/U of the full Set, I guess.

This last Recycle Backup seemed to take much too long. Any obvious reasons this may have now happened? We are on Gigabit connection. Performance transfer rates seem within ball-park.

Thanks.

[twickland]

Can I run a recycle backup for that now-fixed drive alone, and add it to the successful Recycle data on the other 2? I suspect not. I would have to do another Recycle B/U of the full Set, I guess.

A recycle backup simply resets the catalog before beginning the backup. If, as in your case, the recycle backup misses one or more source volumes, there is no need to perform another recycle backup. In fact, to do so would reset the catalog again, causing you to lose the data from the volumes that did get backed up.

 

From this point forward, you should perform Normal incremental backups, which will add the data from the missed volumes, as well as new and changed files on the volumes that were backed up earlier.

 

Perform a recycle backup only when you want to clear the decks and start again from scratch.

 

By the way, your version of Retrospect is getting long in the tooth. You may want to download the latest version here; it's free.

[banjojr]

Thanks twickland. I was in fact 'clearing the deck', or attempting to, which I do as the Incrementals gradually fill the Set. I'm more than open to suggestions on changing my routine though.

The reason I assumed that I had a problem was that the error occurred while part-way through backing up the 3rd and final drive. Assumed I would need to commence the Recycle backup again as the full 'clean write' had been interrupted.

Pasted below is an error log from my 2nd attempt last night to repeat the Recycle B/U. What I did notice is that one of the members of the B/Up Set seems to be 'over-filling'. I.e. perhaps not moving on to the next member. My hunch at the moment, at least.

I'm not sure how to proceed with that...maybe from within Retrospect, but maybe not. It may be a drive problem. Does Retrospect control when it moves to the next drive, before the current one 'over-fills'? I assume so. Research continues...

 

 

error evaluating Type 4 function: typecheck.

May 12 15:44:23 KernelEventAgent[39]: tid 00000000 received VQ_NOTRESP event (1)

May 12 15:44:23 KernelEventAgent[39]: tid 00000000 type 'hfs', mounted on '/Volumes/3-Backup Set A', from '/dev/disk2s10', low disk

May 12 15:44:23 KernelEventAgent[39]: tid 00000000 type 'afpfs', mounted on '/Volumes/prepress', from 'afp_002Usx2qTrVu001Eic06SdO0-1.2d00000b', not responding

May 12 15:44:23 KernelEventAgent[39]: tid 00000000 type 'afpfs', mounted on '/Volumes/Prepress HD2', from 'afp_002Usx2qTrVu001Eic06SdO0-2.2d00000c', not responding

May 12 15:44:23 KernelEventAgent[39]: tid 00000000 type 'afpfs', mounted on '/Volumes/Macintosh HD', from 'afp_002Usx2qTrVu001Eic06SdO0-3.2d00000d', not responding

May 12 15:44:23 KernelEventAgent[39]: tid 00000000 found 3 filesystem(s) with problem(s)

May 12 15:45:30 KernelEventAgent[39]: tid 00000000 received VQ_NOTRESP event (1)

May 12 15:45:30 KernelEventAgent[39]: tid 00000000 type 'hfs', mounted on '/Volumes/3-Backup Set A', from '/dev/disk2s10', low disk

May 12 15:45:30 KernelEventAgent[39]: tid 00000000 received VQ_NOTRESP event (1)

May 12 15:45:30 KernelEventAgent[39]: tid 00000000 type 'hfs', mounted on '/Volumes/3-Backup Set A', from '/dev/disk2s10', low disk

May 12 15:45:30 KernelEventAgent[39]: tid 00000000 received VQ_NOTRESP event (1)

May 12 15:45:30 KernelEventAgent[39]: tid 00000000 type 'hfs', mounted on '/Volumes/3-Backup Set A', from '/dev/disk2s10', low disk

May 12 15:46:52 KernelEventAgent[39]: tid 00000000 type 'hfs', mounted on '/Volumes/3-Backup Set A', from '/dev/disk2s10', low disk

May 12 15:48:26 KernelEventAgent[39]: tid 00000000 received VQ_NOTRESP event (1)

May 12 15:48:26 KernelEventAgent[39]: tid 00000000 type 'hfs', mounted on '/Volumes/3-Backup Set A', from '/dev/disk2s10', low disk

May 12 15:48:26 KernelEventAgent[39]: tid 00000000 type 'afpfs', mounted on '/Volumes/prepress', from 'afp_002Usx2qTrVu001Eic06SdO0-1.2d00000b', not responding

May 12 15:48:26 KernelEventAgent[39]: tid 00000000 type 'afpfs', mounted on '/Volumes/Macintosh HD', from 'afp_002Usx2qTrVu001Eic06SdO0-3.2d00000d', not responding

May 12 15:48:26 KernelEventAgent[39]: tid 00000000 found 2 filesystem(s) with problem(s)

May 12 15:48:45 KernelEventAgent[39]: tid 00000000 unmounting 2 filesystems

May 12 15:48:45 KernelEventAgent[39]: tid 00000000 type 'hfs', mounted on '/Volumes/3-Backup Set A', from '/dev/disk2s10', low disk

May 12 15:48:46 KernelEventAgent[39]: tid 00000000 type 'hfs', mounted on '/Volumes/3-Backup Set A', from '/dev/disk2s10', [color:red]low disk[/color]

May 12 18:01:30 Paul-Xxxx's-Computer crashdump[12269]: Retrospect crashed

Edited May 12, 2010 by Guest

[banjojr]

A screenshot of what I assume to be the destination drive at issue.

 

[banjojr]

I have replaced a WD Book drive (why did I buy it?), with a LaCie d2 Quadra, I now have a workable Backup Set. But I would like to upgrade anyway. I have sent a message to the Asia-region to ask what upgrade is appropriate for my setup. As far as I can tell, I have a bog-standard version, but that must allow me to back up other drives/volumes on the network, as that's what I'm doing. The various versions on the upgrade site are a bit confusing... I don't want to download the wrong Upgrade. I still haven't heard from them. Been 2 days or so. :confused2:

Anyone give any pointers?

Edited May 26, 2010 by Guest

[rhwalker]

Um, you ought to delete that attachment, which has license code information.

 

It's unclear what you are trying to "upgrade" to.

 

Are you trying to upgrade to some version of Retrospect 8? Or to the last released version of Retrospect 6.1 (that upgrade/update is free, see Twickland's link above).

 

If you are trying to upgrade to some version of Retrospect 8, then you should repost in the Retrospect 8 forum because that's really a Retrospect 8 question, not a Retrospect 6.x question. The Retrospect 8 forum is here:

Retrospect 8 for Macintosh forum

 

Also, when you repost, needed information that you haven't provided is:

 

(1) What flavor (Server? Non-Server?) of Mac OS X and version (10.x.x) are you running on each of the PPC machines? That will determine whether you need a Retrospect server client license for the second machine.

 

(2) Do your PPC machines meet the minimum requirements for Retrospect 8? Note that Retrospect 8 (at least 8.1.x) runs VERY poorly on a PPC because the media set format is Intel-native (little endian) rather than PPC native (big endian), necessitating lots of byte swapping.

 

(3) If you are moving to Retrospect 8, note that the Retrospect console must run on Mac OS 10.5 (Leopard) or greater.

 

(4) I'd suggest waiting a bit until the big bugfix release for Retrospect 8.x arrives ("real soon, now"), which is rumored to have many bugfixes and stability improvements for Retrospect engine running on PPC.

 

Russ

[banjojr]

Thanks Russ...am I missing something? I wanted to delete the attachment for the reasons you stated, but can't see an 'edit' button anywhere. I'd be happy for a Mod to delete. Wasn't thinking too well when I posted that.

I'll post this...come back on the relevant stuff later...

Thanks

[banjojr]

OK, I see now editing must be on a time limited basis. I seem to have gone over on that one.

[banjojr]

I have just updated to 6.1.230. Set a Recycle, as I have a new Set member. I may or may not have a network access problem with the volumes on the drives of the other Mac. Both on 10.4.11/PPCs. Shall see what's happening in the morning.

 

Also, if the Retrospect Box says nothing about 'Server' on it, I take that as read...not 'Server' version. Thanks for your help; shall check bak in on progress. :happy:

 

Edited May 25, 2010 by Guest

[twickland]

I may or may not have a network access problem with the volumes on the drives of the other Mac.

If your license code enabled you to back up everything you wanted to under 6.0, you should be able to back up the same volumes running 6.1.

[rhwalker]

I have just updated to 6.1.230.

Ok, but you still haven't answered questions necessary to answer your inquiry. See my post upthread.

 

Also, make sure you read the "Read Me" for Retrospect 6.1.x - The Retrospect 6.1 backup set format is different from the Retrospect 6.0.x backup set format. Here is the link:

Retrospect 6.1 for Macintosh Read Me

 

File Backup Sets: Starting with Retrospect 6.1, all newly created file backup sets will be split into separate data and catalog files by default. In order to avoid potential problems, these files must be stored together in the same directory and they should not be renamed. Retrospect still supports older file backup sets with combined data and catalog files and it still provides users with the ability to combine (and separate) the data and catalog files, even for newly created file backup sets. However, once Retrospect determines that the backup set's catalog resource fork will exceed the Mac OS-imposed limit of 16 MB, the file will automatically be split into separate data and catalog files, at which point the files cannot be combined again.

 

Retrospect 6.0 backup sets: Retrospect 6.1 supports backup sets created with Retrospect 6.0. However, once you write to a 6.0 backup set with Retrospect 6.1, you may get errors if you try to use Retrospect 6.0 to restore from this backup set. New backup sets created with Retrospect 6.1 cannot be used with Retrospect 6.0.

Finally, you don't say whether you also installed the Retrospect Driver Update, or what version. You should.

 

Russ

[banjojr]

Have completed a successful Recycle Backup with the updated v6.1. All looks OK so far. Also downloaded and placed 6.1.16.100 Driver Update into Retrospect Folder. It is named as '6.1' on unplacking. I assume this is normal.

 

I hope I've not left any information out, as you refer to. The box in which it came merely refers to Retrospect 6.0 for Mac OSX. No reference to anything else.

Both PPCs on 10.4.11. On Gigabit ethernet.

If there is anything else I've left out, please specify, and I'll try and answer it.

Since adding the new drive, and upgrading to 6.1, things seem to be 'back to normal'.

I still have to absorb the stuff about Catalog and Data files, for 6.1. I haven't yet. It's pretty unfamiliar territory.

Thanks for your help, guys!

[rhwalker]

Have completed a successful Recycle Backup with the updated v6.1. All looks OK so far. Also downloaded and placed 6.1.16.100 Driver Update into Retrospect Folder. It is named as '6.1' on unplacking. I assume this is normal.

It should be named "Retrospect 6.1 Driver Update" and it goes in the same folder as the Retrospect application.

 

I've never done "unplacking", so it's unclear what you did there.

 

You will know that the RDU is installed properly if Retrospect announces the RDU version in the Retrospect log when it starts. Check that to see if you have installed it correctly. Here is a link to the installation instructions:

How do I install the Retrospect Driver Update on Mac OS X?

 

I hope I've not left any information out, as you refer to.

It may not matter if things are back to normal, but here is the information that I requested above in order to answer your original inquiry and which you still have not provided:

 

(1) [color:red]What flavor (Server? Non-Server?) of Mac OS X[/color] and version (10.x.x) are you running on each of the PPC machines? That will determine whether you need a Retrospect server client license for the second machine.

Can't answer your "upgrade" question unless we know whether Mac OS X Server or, instead, Mac OS X non-server, is running on each of the PPC machines. Required Retrospect licenses differ depending on whether Mac OS X Server is running, and how many of the Retrospect and Retrospect clients are running Mac OS X Server.

 

(2) Do your PPC machines meet the minimum requirements for Retrospect 8?

This question may be moot because, contrary to your original post, you seem to have "updated" to Retrospect 6.1.230 from Retrospect 6.0.204, instead of "upgrading" to Retrosepct 8. Because you have never told us any of the specifics (Mac model, speed, etc.) of the two PPC machines, this question hasn't been answered.

 

But, again, the answers to these two questions are probably moot because you now have things running again.

 

See how much easier (and faster) it would have been for us to help you if you had provided complete specifics in your first post, rather than having to try to drag it out of you, piece by piece?

 

Russ

[banjojr]

Suitably chastened. As an old guy I've copped enough in a lifetime not to be thin skinned about it.

Non-server OSX. I gather the specifics of model/speed are now not an issue, as I muddied the waters with update v6 vs. upgrade to v8.

Thanks for the link on the Driver update install.

2nd nightly (incremental), travelled well.

Thanks again.