Jump to content

Suspicious verify behaviour


Recommended Posts

Tried to verify a 40G backup with Retrospect 5.1.167(Mac) Desktop of a 5.0.238(Mac) set of DVD disks which was the backup from an external Firewire disk. Retrospect calls for the first disk and then proceeds to verify all ~40G without asking for the second disk??? (There's only 4.2G on one disk)

 

And to further confuse the issue, the progress window has the remaining file size goes below zero and numbers like 429,496,718.8G display which then proceed to decrease further.

 

No error issued to the screen!!, but the log reports about thirty instances of Backup set inconsistency and Bad backup set header. Surprisingly, the log reports that 34.7GB was completed????? which is impossible because the sole DVD disk inserted has only 4.2G of information.

 

I had seen this behavior with 5.0 and hoped that 5.1 would fix this. If you're only as good as your last backup, I'm worried.

 

How should a verify proceed with a backup set of 10 members? And does a Retrospect "Verify" compare the backup catalog with the ability to read the file from the media? Is there some other verify tool I should use?

 

 

Link to comment
Share on other sites

It sounds like Retrospect gave up (and things are bad!). What does it say at the end of the log from the verify?

 

Quote:

How should a verify proceed with a backup set of 10 members? And does a Retrospect "Verify" compare the backup catalog with the ability to read the file from the media? Is there some other verify tool I should use?

 


 

The verify should ask for each backup set member. The "Verify" compares very closely with the ability to read the file from the media (it is exactly what it is for!).

 

Additional information which might be useful:

- are you doing verify on same DVD drive as the original backup?

- Mac OS version?

- DVD, model and firmware version?

- the log from the verify

Link to comment
Share on other sites

The log reports about thirty instances of "Backup set inconsistency" and "Bad backup set header". No final log entry because I terminated the verify as the "remaining file counter" went below zero (and numbers like 429,496,718.8G display which then proceed to decrease further).

 

MacOS X.2.6 on Dual 867 MDD with Pioneer DVR-104 (Device Revision A227 from Apple System Profiler)

 

Thanks for the help and ideas

 

Detailed log follows

Executing Verify at 9/11/2003 4:56 PM

To backup set Backup FWExt 0903…

Bad backup set header found (0x436f6e74 at 3,245,107).

Backup set format inconsistency (4 at 3344384)

Backup set format inconsistency (4 at 4392960)

Bad backup set header found (0x436f6e74 at 5,441,587).

Backup set format inconsistency (4 at 5540864)

Backup set format inconsistency (4 at 6589440)

Bad backup set header found (0x436f6e74 at 7,638,067).

Backup set format inconsistency (4 at 7737344)

Backup set format inconsistency (4 at 8785920)

Bad backup set header found (0x436f6e74 at 9,834,547).

Backup set format inconsistency (4 at 9933824)

Backup set format inconsistency (4 at 10982400)

Bad backup set header found (0x436f6e74 at 12,031,027).

Backup set format inconsistency (4 at 12130304)

Backup set format inconsistency (4 at 13178880)

Bad backup set header found (0x436f6e74 at 14,227,507).

Backup set format inconsistency (4 at 14326784)

Backup set format inconsistency (4 at 15375360)

Bad backup set header found (0x436f6e74 at 16,423,987).

Backup set format inconsistency (4 at 16523264)

Backup set format inconsistency (4 at 17571840)

Bad backup set header found (0x436f6e74 at 18,620,467).

Backup set format inconsistency (4 at 18719744)

Backup set format inconsistency (4 at 19768320)

Bad backup set header found (0x436f6e74 at 20,816,947).

Backup set format inconsistency (4 at 20916224)

Backup set format inconsistency (4 at 21964800)

Bad backup set header found (0x436f6e74 at 23,013,427).

Backup set format inconsistency (4 at 23112704)

Backup set format inconsistency (4 at 24161280)

Bad backup set header found (0x436f6e74 at 25,209,907).

Backup set format inconsistency (4 at 25309184)

Backup set format inconsistency (4 at 26357760)

Bad backup set header found (0x436f6e74 at 27,406,387).

Backup set format inconsistency (4 at 27505664)

Backup set format inconsistency (4 at 28554240)

Bad backup set header found (0x436f6e74 at 29,602,867).

Backup set format inconsistency (4 at 29702144)

Backup set format inconsistency (4 at 30750720)

Bad backup set header found (0x436f6e74 at 31,799,347).

Backup set format inconsistency (4 at 31898624)

Backup set format inconsistency (4 at 32947200)

Bad backup set header found (0x436f6e74 at 33,995,827).

Backup set format inconsistency (4 at 34095104)

Backup set format inconsistency (4 at 35143680)

Bad backup set header found (0x436f6e74 at 36,192,307).

Backup set format inconsistency (4 at 36291584)

9/11/2003 8:57:50 PM: Execution stopped by operator.

Remaining: 212078 files, 429,496,718.8 GB

Completed: 37832 files, 34.7 GB

Performance: 147.3 MB/minute

Duration: 04:01:30 (00:00:59 idle/loading/preparing)

Quit at 9/11/2003 8:57 PM

 

 

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...