Jump to content
Sign in to follow this  
BillIrwin

Groom says backup set format inconsistency

Recommended Posts

MS7 on Windows 2003 server

There's no error number associated with this, but it's happened twice now from a Groom task. It takes about 6 minutes to give up.

 

+ Executing Groom 3 at 8/20/2005 11:26 AM (Execution unit 1)

Grooming Backup Set Disk 3...

Backup Set format inconsistency (10 at 32967820)

Groomed zero KB from Backup Set Disk 3.

8/20/2005 11:33:20 AM: 1 execution errors

Duration: 00:06:22 (00:00:01 idle/loading/preparing)

 

Groom jobs on other disk sets work fine.

Share this post


Link to post
Share on other sites

Hi

 

Be sure to update to Retrospect 7.0.326. Does a verify of the backup set give any errors? How about a catalog rebuild?

 

Thanks

Nate

Share this post


Link to post
Share on other sites

I've updated to 326. The set verified with 2 files not. Then a groom failed. Strange that the backup worked flawlessly on the set.

 

+ Executing Verify at 8/20/2005 12:41 PM (Execution unit 2)

To Backup Set Disk 3...

2 files were not verified

8/20/2005 1:55:37 PM: 1 execution errors

Remaining: 2 files, zero KB

Completed: 355800 files, 132.5 GB

Performance: 2258.7 MB/minute

Duration: 01:13:52 (00:13:48 idle/loading/preparing)

 

+ Executing Groom 3 at 8/20/2005 2:20 PM (Execution unit 1)

Grooming Backup Set Disk 3...

Backup Set format inconsistency (10 at 32967820)

Groomed zero KB from Backup Set Disk 3.

8/20/2005 2:27:55 PM: 1 execution errors

Duration: 00:07:50 (00:00:01 idle/loading/preparing)

 

+ Normal backup using Network at 8/21/2005 2:00 AM (Execution unit 1)

To Backup Set Disk 3...

 

- 8/21/2005 2:00:00 AM: Copying NT 4 (C:) on nsaserver

8/21/2005 2:00:00 AM: Connected to nsaserver

TFileLocappl.gifGetParent: folder is root, "C:"

8/21/2005 2:40:00 AM: Snapshot stored, 72.3 MB

8/21/2005 2:40:09 AM: Comparing NT 4 (C:) on nsaserver

8/21/2005 2:42:09 AM: Execution completed successfully

Completed: 470 files, 251.8 MB, with 0% compression

Performance: 82.7 MB/minute (61.1 copy, 128.0 compare)

Duration: 00:42:09 (00:36:03 idle/loading/preparing)

 

 

- 8/21/2005 2:42:15 AM: Copying Users (D:) on nsaserver

8/21/2005 5:51:09 AM: Snapshot stored, 138.7 MB

8/21/2005 5:51:20 AM: Comparing Users (D:) on nsaserver

8/21/2005 6:02:23 AM: Execution completed successfully

Completed: 3232 files, 1.1 GB, with 14% compression

Performance: 70.3 MB/minute (55.0 copy, 97.6 compare)

Duration: 03:20:07 (02:49:38 idle/loading/preparing)

 

 

- 8/21/2005 6:02:26 AM: Copying Local Disk (C:)

8/21/2005 6:08:31 AM: Snapshot stored, 213.7 MB

8/21/2005 6:08:58 AM: Comparing Local Disk (C:)

8/21/2005 6:10:19 AM: Execution completed successfully

Completed: 643 files, 298.3 MB, with 38% compression

Performance: 241.8 MB/minute (259.3 copy, 226.5 compare)

Duration: 00:07:52 (00:05:23 idle/loading/preparing)

 

 

- 8/21/2005 6:10:19 AM: Copying User (E:)

8/21/2005 6:13:59 AM: Snapshot stored, 2,697 KB

8/21/2005 6:14:02 AM: Comparing User (E:)

8/21/2005 6:16:40 AM: Execution completed successfully

Completed: 3066 files, 1.3 GB, with 0% compression

Performance: 444.5 MB/minute (399.1 copy, 504.7 compare)

Duration: 00:06:21 (00:00:28 idle/loading/preparing)

 

8/21/2005 6:16:41 AM: Execution completed successfully

Total performance: 129.7 MB/minute with 0% compression

Total duration: 04:16:39 (03:31:33 idle/loading/preparing)

Location of backup report is C:\Retrospect Catalog Files\.

Share this post


Link to post
Share on other sites

Hi

 

What is the grooming level set to? I wonder if things will improve if you save fewer snapshots.

 

If the backup set is damaged you could try a snapshot transfer of the most recent snapshots into a new set. Then delete the old set that won't groom.

 

Have you checked the disk for errors?

 

Thanks

nate

Share this post


Link to post
Share on other sites

Nate:

I reduced the groom history from Defined Policy to 10, which allowed a groom of 10.3 GB.

 

+ Executing Groom 3 at 8/24/2005 12:09 AM (Execution unit 1)

Grooming Backup Set Disk 3...

Groomed 10.3 GB from Backup Set Disk 3.

8/24/2005 1:00:47 AM: Execution completed successfully

Duration: 00:46:27 (00:10:31 idle/loading/preparing)

 

However, the nightly backup that immediately followed this, to Set 3, had a chunk checksum problem. I received no e-mail this morning and, when I logged into the server, I found the error box on screen waiting for me to click OK. This should not have stopped the entire backup job from completing and sending a notice of failure.

 

8/24/2005 11:31:30 AM: Script execution terminated at specified stop time.

8/24/2005 11:31:29 AM: Script execution terminated at specified stop time.

8/24/2005 11:31:28 AM: Script execution terminated at specified stop time.

Can't compress Catalog File for Backup Set Disk 3, error -641 (chunk checksum didn't match)

Can't compress Catalog File for Backup Set Disk 3, error -641 (chunk checksum didn't match)

8/24/2005 11:31:39 AM: Execution incomplete

Total performance: 118.6 MB/minute with 29% compression

Total duration: 03:43:22 (03:33:57 idle/loading/preparing)

Location of backup report is C:\Retrospect Catalog Files\.

 

I have had a couple of -641s that required me to rebuild the catalog.

 

Prior to this I ran Checkdsk, which reported no errors.

 

Bill

Share this post


Link to post
Share on other sites

I noticed that I couldn't see one of the external disks, so I asked the office manager to check if it was on. She told me that both disks had an orange light, instead of green. She power cycled them both. The catalogue rebuild completed perfectly after that. Tonight the backup will use it, and I suspect all will be well for a while. Then I think a -641 will appear.

 

I'm now logging when these appear and on which disk sets. Stay tuned ...

 

Thanks Nate.

Share this post


Link to post
Share on other sites

I've also been having a lot of "chunk checksum" issues with the lastest releases of Retrospect. Even on sets that aren't set to groom. :~( Needless to say, I'll be watching this thread.

Share this post


Link to post
Share on other sites

As suspected, the backup worked fine last night on the freshly recatalogued set 3. I'm not sure what an orange light on the external USB disks means, other than a problem. Both disks had an orange light yet one, containing sets 1 & 3, was still visible in Explorer.

 

I frequently get told a groom couldn't complete because the disk filled. It seems the auto-grooming leaves things too long until there's not enough space on the disk to do the groom. I've created four Groom jobs that each groom one set every 4 weeks, which is just prior to the set going into service for a week.

 

I've also set the grooms to 10 because this allowed the recent groom failure to complete before I got the chuck checksum and had to rebuild the catalogue.

 

I'm now logging when a set gets a chucnk checksum and when I rebuild catalogues.

 

Bill

Share this post


Link to post
Share on other sites

Bex:

No System Restore (it's 2003 server) or swap files. Two USB drives of 200 GB each. Each partitioned into two, with first disk holding Disk 1 and Disk 3 partitoions, and 2nd disk with Disk 2 and Disk 4 partitions. The idea being that one disk gets taken offsite each week.

 

I know ... without a 3rd disk we have both of them onsite on switch day which, given Murphey's Law (what number is it?), will be the day the fire hits or the bomb goes off.

 

Bill

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
Sign in to follow this  

×