Jump to content

Recommended Posts

Dear all,

 

 

 

Several days ago, I decided to run a verification on my backup set. This is what I got back:

 

 

 

? Retrospect version 5.0.203

 

launched at 4/24/2002 12:19 AM

 

 

 

+ Executing Verify at 4/24/2002 11:28 AM

 

To backup set Primary Backup Set…

 

Bad backup set header found (0x24c2767f at 9,790,417).

 

Backup set format inconsistency (12 at 9790673)

 

Bad backup set header found (0x0ac026b0 at 9,793,014).

 

Bad backup set header found (0x63115ad0 at 11,887,329).

 

Backup set format inconsistency (12 at 11887834)

 

Bad backup set header found (0xaf348f20 at 11,887,847).

 

Backup set format inconsistency (4 at 13984218)

 

58,340 files were not verified.

 

4/24/2002 6:06:47 PM: Execution stopped by operator.

 

Remaining: 61130 files, 2.6 GB

 

Completed: 147477 files, 13.8 GB

 

Performance: 63.0 MB/minute

 

Duration: 06:37:51 (02:55:10 idle/loading/preparing)

 

Quit at 4/24/2002 6:07 PM

 

 

 

From what I am reading, some problem with the media may be causing large chunks of data to become unreadable. This brings up several questions. Although the definitions and information on the two error messages are sparce, I can get their meaning. However, I'd still appreciate a more detailed explanation of the errors.

 

 

 

The first thing I would like to know is: If I have to do a restore of my entire disk, will the 58,340 simply not be restored? Or will Retrospect attempt to access the files? I'd appreciate knowing what would happen in such a case.

 

 

 

Also, how can I backup the the unverified files again? I know that most of them haven't changed since their initial backup, so how can I get Retrospect to back them up again? Hopefully it doesn't involve going through my entire drive(s) and searching for 58,340 files. I definitely want to know the answer to this!

 

 

 

Well, that's it for now. Thanks in advance for your answer! I am using a PowerMac G3 with 384Mb RAM, two hard drives (with more than enough free space), the latest Mac OS X (10.1.4/5Q125), the latest Retrospect (5.0.205), and on OnStream Echo FireWire 30GB tape drive (compatible drive) with the latest firmware version connected directly to the computer. Although the error occurred in Retrospect 5.0.203, based on the readme for 5.0.205, re-running the verification should not make a difference.

Link to comment
Share on other sites

I have encountered similar problems. Yesterday while trying to restore a disk, the restore failed with "bad backup set header" messages. A verify of the tape gives the same messages.

 

 

 

 

...

 

Bad backup set header found (0x036c024e at 541).

 

Bad backup set header found (0x089a087c at 9160).

 

Bad backup set header found (0x32150fdb at 17,900).

 

...

 

 

 

 

Config: Retrospect 5.0.205, HP DDS-4 tape drive, G4/500, OS X.1.4, 1 GB RAM

 

 

 

This is my first attempt to restore a version 5 backup set; very discouraging.

Link to comment
Share on other sites

Please provide details on your configuration:

 

 

 

Computer Model and speed

 

Device (from Retrospect's Configure > Devices > Device Status window)

 

Device firmware (in the version column of the Device Status window)

 

Media brand and size

 

Other Devices

 

Adapter Card

 

Adapter Card firmware

 

Adapter Card driver for OS X

 

 

 

Thanks,

 

 

 

Irena Solomon

 

Dantz Tech Support

 

 

Link to comment
Share on other sites

I'm running an Apple PowerMac Blue&White G3 - 350 Mhz. I am running Mac OS X (version 10.1.4 - build 5Q125). I am running Retrospect Desktop 5.205, although the error occurred when I was running 5.203.

 

 

 

The device is an OnStream FW-30, running firmware version 109E (according to Retrospect) / 1.09 (according to the drive label). This is the original firmware on the drive, no updates have been made. The product's full name is the OnStream Echo FW-30. It takes 15Gb (30Gb compressed) ADR tapes. I am using OnStream tapes for the backup.

 

 

 

I have one other FireWire device, a Cyclone CD Revo 24x10x40x. It's connected to the G3 seperately from the tape drive. I don't use the CD drive with Retrospect. Internally, I have a second hard drive connected to an IDE PCI host card, as the revision A B&W G3 has some problems with multiple drives on its built-in host chip. I also have an internal Zip 100 drive and a DVD player (both came with the computer). The second hard drive contains Mac OS X (it's the boot device), as well as Retrospect. On the USB is my Apple keyboard and Microsoft intelliMouse, an Epson Color 740, a USB floppy drive, and a USB-serial adapter. The drivers for all devices are either built into the OS (the mouse/printer/keyboard), or are the latest version (floppy drive and USB-serial adapter).

 

 

 

No adapters are being used. FireWire came standard with the Blue&White G3. No firewire or USB cards are installed.

 

 

 

Hopefully this information helps. However, I don't know how this info can have anything to do with getting Retrospect to re-backup my files. Oh, well... Later!

Link to comment
Share on other sites

Run an incremental backup again to that same set - do you get the same errors? Retrospect should try backing up those files again.

Link to comment
Share on other sites

Okay, here's what I did, as shown by the log files:

 

 

 

? Retrospect version 5.0.205

 

launched at 5/6/2002 8:38 PM

 

 

 

+ Executing Immediate Backup at 5/6/2002 8:51 PM

 

To backup set Primary Backup Set…

 

Warning: volume Macintosh HD has the Ignore privileges setting enabled.

 

 

 

- 5/6/2002 8:51:34 PM: Copying Macintosh HD…

 

5/6/2002 8:55:46 PM: Comparing Macintosh HD…

 

5/6/2002 8:57:35 PM: Execution completed successfully.

 

Completed: 6 files, 7834 KB, with 35% compression

 

Performance: 19.9 MB/minute (11.7 copy, 65.5 compare)

 

Duration: 00:06:01 (00:05:15 idle/loading/preparing)

 

 

 

- 5/6/2002 8:57:36 PM: Copying Macintosh HD 2…

 

5/6/2002 9:04:14 PM: Comparing Macintosh HD 2…

 

File “Operations Log”: different data size (set: 80,980, vol: 81,044), path: “Macintosh HD 2/Library/Preferences/Retrospect/Operations Log”.

 

File “system.log”: different modification date/time (set: 5/6/2002 8:38:25 PM, vol: 5/6/2002 9:00:59 PM), path: “Macintosh HD 2/private/var/log/system.log”.

 

5/6/2002 9:06:08 PM: 2 execution errors.

 

Completed: 108 files, 18.8 MB, with 0% compression

 

Performance: 13.2 MB/minute (7.3 copy, 70.4 compare)

 

Duration: 00:08:32 (00:05:42 idle/loading/preparing)

 

 

 

5/6/2002 9:09:15 PM: 2 execution errors.

 

Total performance: 14.6 MB/minute with 0% compression

 

Total duration: 00:14:34 (00:10:57 idle/loading/preparing)

 

 

 

+ Executing Verify at 5/6/2002 9:10 PM

 

To backup set Primary Backup Set…

 

Bad backup set header found (0x24c2767f at 9,790,417).

 

Backup set format inconsistency (12 at 9790673)

 

Bad backup set header found (0x0ac026b0 at 9,793,014).

 

Bad backup set header found (0x63115ad0 at 11,887,329).

 

Backup set format inconsistency (12 at 11887834)

 

Bad backup set header found (0xaf348f20 at 11,887,847).

 

Backup set format inconsistency (4 at 13984218)

 

58,340 files were not verified.

 

5/7/2002 9:53:41 AM: 8 execution errors.

 

Remaining: 58340 files, zero KB

 

Completed: 153946 files, 18.3 GB

 

Performance: 78.8 MB/minute

 

Duration: 12:42:41 (08:46:20 idle/loading/preparing)

 

 

 

+ Normal backup using Backup Computer at 5/7/2002 9:53 AM

 

To backup set Primary Backup Set…

 

Warning: volume Macintosh HD has the Ignore privileges setting enabled.

 

 

 

- 5/7/2002 9:53:58 AM: Copying Macintosh HD…

 

5/7/2002 9:58:59 AM: Comparing Macintosh HD…

 

5/7/2002 10:00:43 AM: Execution completed successfully.

 

Completed: 6 files, 7834 KB, with 35% compression

 

Performance: 13.9 MB/minute (9.0 copy, 30.6 compare)

 

Duration: 00:06:45 (00:05:39 idle/loading/preparing)

 

 

 

- 5/7/2002 10:00:44 AM: Copying Macintosh HD 2…

 

5/7/2002 10:17:46 AM: Comparing Macintosh HD 2…

 

File “Operations Log”: different data size (set: 83,115, vol: 83,180), path: “Macintosh HD 2/Library/Preferences/Retrospect/Operations Log”.

 

File “system.log”: different modification date/time (set: 5/7/2002 9:09:25 AM, vol: 5/7/2002 10:14:32 AM), path: “Macintosh HD 2/private/var/log/system.log”.

 

5/7/2002 10:19:30 AM: 2 execution errors.

 

Completed: 94 files, 15.5 MB, with 0% compression

 

Performance: 10.7 MB/minute (5.8 copy, 66.3 compare)

 

Duration: 00:18:46 (00:15:54 idle/loading/preparing)

 

 

 

5/7/2002 10:21:40 AM: 2 execution errors.

 

Total performance: 11.6 MB/minute with 0% compression

 

Total duration: 00:25:32 (00:21:33 idle/loading/preparing)

 

Quit at 5/7/2002 10:23 AM

 

 

 

First I ran a regular backup. I ran the backup manually, not through a script. I turned verification and compression on, but all the other settings are at their defaults. After the backup, I ran a verification run. The verification came back with 58,340 errors, as shown above. The large 8-hour delay was due to the fact that it wanted my 2nd tape (it's a 2-tape set) when I was asleep.

 

 

 

After the verification run, the scheduled backup script ran, running an inremental backup. It backed up a total of 100 files, so it doesn't seem like the 58,340 files not verified did not back up. Retrospect then quit.

 

 

 

Just as a last check, I recently re-launched Retrospect and run a regular backup (non-script), with verification and data compression. Here's the log from that:

 

 

 

? Retrospect version 5.0.205

 

launched at 5/7/2002 8:32 PM

 

 

 

+ Executing Immediate Backup at 5/7/2002 8:45 PM

 

To backup set Primary Backup Set…

 

Warning: volume Macintosh HD has the Ignore privileges setting enabled.

 

 

 

- 5/7/2002 8:45:34 PM: Copying Macintosh HD…

 

5/7/2002 8:45:34 PM: No files need to be copied.

 

5/7/2002 8:45:54 PM: Execution completed successfully.

 

Duration: 00:00:20 (00:00:18 idle/loading/preparing)

 

 

 

- 5/7/2002 8:45:54 PM: Copying Macintosh HD 2…

 

5/7/2002 8:54:57 PM: Comparing Macintosh HD 2…

 

File “Operations Log”: different data size (set: 84,470, vol: 84,534), path: “Macintosh HD 2/Library/Preferences/Retrospect/Operations Log”.

 

File “com.apple.internetconfig.plist”: different data size (set: 439,022, vol: 439,642), path: “Macintosh HD 2/Users/akkornel/Library/Preferences/com.apple.internetconfig.plist”.

 

File “Favorites.html”: different modification date/time (set: 5/7/2002 8:48:35 PM, vol: 5/7/2002 8:55:23 PM), path: “Macintosh HD 2/Users/akkornel/Library/Preferences/Explorer/Favorites.html”.

 

File “History.html”: different data size (set: 116,643, vol: 116,639), path: “Macintosh HD 2/Users/akkornel/Library/Preferences/Explorer/History.html”.

 

5/7/2002 8:57:09 PM: 4 execution errors.

 

Completed: 55 files, 13.7 MB, with 0% compression

 

Performance: 6.8 MB/minute (3.9 copy, 28.2 compare)

 

Duration: 00:11:15 (00:07:16 idle/loading/preparing)

 

 

 

5/7/2002 9:00:34 PM: 4 execution errors.

 

Total performance: 6.8 MB/minute with 0% compression

 

Total duration: 00:11:35 (00:07:34 idle/loading/preparing)

 

 

 

As shown above, it still didn't re-backup the files that weren't verified. I should note that my original post said that 58,340 files could not be verified. The verification run above also said that 58,340 files could not be verified. I think that I can say that none of the unverified files could be backed up.

 

 

 

Unfortunately, it seems like regular backup doesn't work. Any other ideas?

Link to comment
Share on other sites

  • 2 weeks later...

The manual verify that you run after the backup will not affect future backups, thus we would not expect the files to be backed up again unless the initial verify failed.

 

 

 

First, we should look at why the Bad Backup Header errors are being reported. Start with a firmware update - 1.09 is the MINIMUM firmware for this drive.

Link to comment
Share on other sites

I'm sorry, I misread your post. I see that you have 1.09 installed.

 

 

 

If you start a new backup set (which I would recommend at this point) what happens? Are you able to verify, or do you get errors?

 

 

 

Thanks,

 

 

 

Irena

Link to comment
Share on other sites

  • 3 weeks later...

If I make a new Backup Set, and back everything up, and then run a verification, everything comes out fine.

 

 

 

On a different note, I did manage to find a possible way to back up my unverified files. After running the verification, when I get the list of execution errors, I highlight everything and make a selector out of the highlighted files. I set it to match exactly those files. Then I run a new backup, matching my drive to that selector. I also change the matching settings to allow duplicates in the backup set. That manages to back everything up. However, a new verification run still reports errors (giving the same list of files), I know that the problem files are still backed up!

Link to comment
Share on other sites

> If I make a new Backup Set, and back everything up, and then run a verification, everything comes out fine.

 

 

 

But incremental backups report errors? It's still not clear what is causing these errors. I'd recommend running disk utilities on the drive that the files are stored on.

 

 

 

Try putting a data CD in your computer and backing that up - do you get the same errors?

 

 

 

Try backing up to a file backup set stored on the local drive - still get errors?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...