bengeo wrote on Jan 13^th, 2007 at 3:04am:


What criteria are you using or telling Ghost to manage the disk space?  I specify the number of backup generations to keep and it works most of the time.

However, I have seen a problem similar to what you have described.  It usually started happening after there was some Ghost problem with the backup or some interruption.  Thereafter Ghost didn't seem to be looking at the catalog or definition properly.

The way I solved it was to delete the Ghost 10 backup definition.  (That shouldn't delete your backups, just the Ghost backup definition.)  Then I defined a complete new Ghost backup.  However, on the new definition I changed the name of the backup files slightly.  Instead of C_Drive001 which would be the default, I changed it to C_Drive001a so that Ghost would start creating the backups with a different naming convention.  I also always check "verify" which makes the backup take only slightly longer.

Then I manually deleted my old backups using Explorer after I was satisfied that Ghost was working ok again.