How To Monitor Grooming

[ee7a94c0-36fb-48b6-870b-70326606df30]

Hi,

 

We have a grooming that has been going on for ~48 hours by now, and I would like to know if there is a way to tell how far it has come, and if there are some specific problems. It's set to grooming according to the default policy when running out of space.

 

Kind regards,

Fredrik

[ee7a94c0-36fb-48b6-870b-70326606df30]

A little FYI, the grooming is now finished a little more than 91 hours later! With backups locked for 91 hours, I would really like to have some sort of indication of the progress!

[Richy_Boy]

Fred, just be gratful you groom actually completed successfully!

 

I constantly get these:

 

+ Executing Groom DR at 26/09/2011 11:58 (Execution unit 3)

Grooming Backup Set DR (Non CORE)...

Groomed zero KB from Backup Set DR (Non CORE).

Grooming Backup Set DR (Non CORE) failed, error -1101 ( file/directory not found)

You must recreate the Backup Set's Catalog File.

See the Retrospect User's Guide or online help for details on recreating Catalog Files.

Can't compress Catalog File for Backup Set DR (Non CORE), error -1 ( unknown)

 

Grooming Backup Set DisasterRecovery2010...

Groomed 276.3 MB from Backup Set DisasterRecovery2010.

Grooming Backup Set DisasterRecovery2010 failed, error -1116 ( can't access network volume)

You must recreate the Backup Set's Catalog File.

See the Retrospect User's Guide or online help for details on recreating Catalog Files.

Can't compress Catalog File for Backup Set DisasterRecovery2010, error -1 ( unknown)

26/09/2011 12:28:31: 4 execution errors

Duration: 00:23:46 (00:01:03 idle/loading/preparing)

 

I recreate the catalog from scratch, it'll groom once then throw this same error.

 

What spec server and disks are you using for Retrospect and your catalog files? I switched to using an SSD disk to hold the catalogs and it's muuuuch faster now.

 

Rich