Jump to content

retrospect error: Bad backup set header found


Recommended Posts

hi,

I work with an OS X Server 10.3.9 and Retrospect 6.1.126. I always get these errors and cant find a solution. Retrospect worked well for about one year - can`t find out the reason of these errors. There are 2 LaCie FireWire Backup-Drives on a G4/733. Tried to erase one of the Discs and started the backupscript again, but the problem still exist. Does anyone have an idea? Thank you very much.

Andi

 

 

10.03.2006 22:04:53 Uhr: Copying Office on Raid…

10.03.2006 22:16:25 Uhr: Comparing Office on Raid…

Bad backup set header found (0x4803df40 at 131.150.864).

Decompression failed due to corrupt input data

Decompression failed due to corrupt input data

Decompression failed due to corrupt input data

Decompression failed due to corrupt input data

Decompression failed due to corrupt input data

Decompression failed due to corrupt input data

Decompression failed due to corrupt input data

 

 

 

File “Kai.dfont”: miscompare at data offset 2.983.923, path: “Administration/02_SOFTWARE/01_INSTALLER/FontCollection/System.font.out/Kai.dfont”.

Bad backup set header found (0x0cb001f8 at 2.027.653).

File “Sturm_C_U320 K100 GCR70.icm”: miscompare at data offset 139.105, path: “Administration/02_SOFTWARE/01_INSTALLER/LIBRARY/ColorSync/Profiles/Sturm_C_U320 K100 GCR70.icm”.

Bad backup set header found (0x6efb09f4 at 2.050.085).

Decompression failed due to corrupt input data

File “hpijs-foomatic-2.0.2.ppc.dmg”: miscompare at data offset 1.703.504, path: “Administration/02_SOFTWARE/01_INSTALLER/PRINTER/hpijs-foomatic-2.0.2.ppc.dmg”.

Bad backup set header found (0x880cfc09 at 2.050.170).

Bad backup set header found (0xd043ea00 at 2.050.174).

Bad backup set header found (0x0130ed2c at 2.050.175).

14.03.2006 10:17:50 Uhr: 716 execution errors.

Remaining: 55 files, 524,3 MB

Completed: 16909 files, 1,7 GB, with 10% compression

Performance: 51,4 MB/minute (276,9 copy, 24,9 compare)

Duration: 01:17:36 (00:00:37 idle/loading/preparing)

 

Quit at 14.03.2006 10:18 Uhr

Link to comment
Share on other sites

Quote:

I always get these errors ...

... There are 2 LaCie FireWire Backup-Drives on a G4/733

 


 

If you are getting bad header errors on two different physical drives, it's possible that the FireWire in your G4 is flaky. Or is there anything else common between the two drives?

 

- Is each physical LaCie plugged into one of the G4 FW ports? Or are they daisy-chained?

 

I'd suggest getting a FireWire PCI card and trying known high-quality cables. If you currently get the error on every execution, you'll know right away if you've solved it.

 

Don't depend on the existing backups; they're unlikely to be able to Restore your data properly.

 

Dave

Link to comment
Share on other sites

I'm getting the exact same errors using Retrospect 6.1. I was archiving files from a LaCie Firewire 800 drive to CDs but, no matter what I did, I kept getting the errors. Finally, I copied my files to a partition on my G4, thinking that would solve all my problems. Unfortunately, I'm getting the exact same errors. Firewire is obviously not the problem. The problem is Retrospect.

Link to comment
Share on other sites

  • 3 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...