Jump to content
H.Pralow

Error -644 (chunk file damaged)

Recommended Posts

Hello everybody,

 

this morning last night's backup presented the following error message to me:

 

!Can't save Catalog File, error -644 ( chunk file damaged during access)

 

Googling for that particular error didn't give a result. I only found some references to an error #-645 which might be related or not.

However, these errors (-645( seem to refer to Retrospect for Windows whereas here, we have Retrospect Mac Version 11.5.3 (103)

running on Mac OS X Server 10.7.5.

 

What does the error mean an how do I salvage it?

 

Thanks in advance

 

Horst

Share this post


Link to post
Share on other sites

Where is the catalog file stored? The default location on the internal boot drive? Or on a USB drive? Or on a NAS server? The latter two locations can maybe explain why you got the error as those are not 100% reliable.

 

Anyway, you should "Rebuild" the catalog file to get i working again.

Share this post


Link to post
Share on other sites

The catalog is stored on the boot volume (Software RAIDED harddisk)

Should be fine, I think.

 

How did the "Rebuild" go?

Share this post


Link to post
Share on other sites

I didn't do a rebuild, since the file, assuming it to be 

 

 /Libary/Application Support/Retrospect/Catalogs/OKT_DEZ_2015.rbc

 

is about 3.5 GB large and stores the catalag of 5 LTO-tapes. So I would expected a rebuild to run longer than

a single night and thus I have delayed it until weekend.

However last night's scheduled backup executed fine without an error, so perhaps the catalog file may

not be corrupted ? I don't know. 

What I'm going to do is to keep an eye on that issue and if the error reoccurs, do a rebuild of the catalog.

Share this post


Link to post
Share on other sites

If you have the option "Fast catalog rebuild" turned on (which is the default), the rebuild uses only the last tape and saves you from reading the first four tapes.

 

The error could hit you when trying to do a restore and time is at a premium. I think you should do a rebuild and not wait for another backup error to occur.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×