2GB Backup set limit version 6.1

[chiggins68]

My system:

Running Retrospect Backup 6.1.230 on Xserve running 10.4.11. With XRaid and a Lacie firewire drive

Everything is MacOS journaled.

Two days ago I received this:

4/5/2010 10:00:26 PM: Copying Server1…

chReadChunk: FSReadFork failed, error -36 (i/o error, bad media?)

Trouble matching Server1 to Backup Set A, error -36 (i/o error, bad media?).

 

4/5/2010 10:01:54 PM: Copying leeper_server on Share2…

chReadChunk: FSReadFork failed, error -36 (i/o error, bad media?)

Trouble matching leeper_server on Share2 to Backup Set A, error -36 (i/o error, bad media?).

 

4/5/2010 10:02:09 PM: Copying Shares3…

chReadChunk: FSReadFork failed, error -36 (i/o error, bad media?)

Trouble matching Shares3 to Backup Set A, error -36 (i/o error, bad media?).

 

Now when I try and run again I get this:

 

Can't get that much data to backup set.

The Limit is 2.0 G

Files have been backing up successfully for a few weeks (incrementally) Its a 500GB drive and there is just under a 100GB free. The 2GB limit doesn't apply to the version I am running. I have successfully verified the Backup set but have not tried to rebuild it.

 

Should I try a rebuild? If so the catalog is 373 GB-I'm assuming I should wait until the weekend?

Edited April 7, 2010 by Guest

[rhwalker]

Additional information is needed from you.

 

You say that "everything is Mac OS journaled", but you don't say where you are saving your backup sets and your catalogs, only that you have an Xraid and a LaCie Firewire drive.

 

Either you are having a drive failure (run Disk Utility, etc.), or I would guess that somewhere you have an SMB format filesystem, which has a 2 GB file size limit.

 

Check your filesystem formats again. If I was a betting person (and I'm not), I would bet that the LaCie 500 GB drive has an SMB format filesystem (that's how the LaCie drives come), and that Retrospect can't write big files like it needs.

 

Russ

[chiggins68]

Hi Russ thanks for the reply. The files are being backed up from Server 1, 2, and 3 to the LaCIE 500gb Firewire drive (Backup Set A). Everything is Mac OS Extended (journaled) nothing is SMB. If it was SMB Retrospect wouldn't be able to put a 375GB backup set on the Firewire drive (which it has been doing for weeks). The catalog is on the same LaCie drive.

 

This has been working flawlessly for weeks then the error -36 (i/o error, bad media?). Then the erroneous:

Can't get that much data to backup set.

The Limit is 2.0 G[/color]

Which doesn't make sense because the version I'm running supports catalogs larger then 2GB (version 6.1.230)

[rhwalker]

Ok, I'll take your word for that.

 

What type of a backup set is it? Disk, file, removable disk, etc.? I seem to recall that there is still a size limit on catalogs for certain types of backup sets. We only back up to tape, so the details of other types escape me at the moment. Wait until you get old, and you will understand.

 

Your problem statement is a bit inconsistent, though. In one place (your most recent post) you say the backup set itself is 375 GB, and in another place (your first post) you say that the catalog (?) is 373 GB. I've never heard of a catalog that big.

 

It's possible that the catalog is corrupt. If the backup set itself is 375 GB, that wouldn't need a very large catalog. I've got tape backup sets that have on the order of a terabyte, and their catalogs are only about 1 GB or two.

 

A 375 GB backup set should take less than a day to rebuild.

 

Now, it's possible that you are seeing some other artifact.

 

Do you have room somewhere else to put the catalog on a different drive with more space? All you would need to do is to copy the catalog, then open it in the Finder so that Retrospect knows the new location, then delete the old catalog copy. See the manual section entitled "Moving Retrospect" (check the index).

 

That would settle the question of whether it's the catalog updating that is running out of room or the backup set updating, and wouldn't require a catalog rebuild.

 

Russ

[Lennart_T]

SMB is for file sharing, not local volumes. But replace "SMB" with "FAT32" in this thread and it makes sense (except that the file size limit is 4GB on FAT32, not 2GB).

 

I would take notice of the part of the (original) error message that says "bad media?".

Have you tested the hard drive? (You can use Apple's Disk Utility for that).

Have you scanned it for bad sectors? (You need a third party tool for that.)