Richy_Boy Posted January 13, 2012 Report Share Posted January 13, 2012 I've been using 7.7.562 for a while now after migrating to a new HP server using SSD disks for application and catalog files. The server is running sweet as a nut. However! I'm forever getting Retrospect problems - 1) Grooming just doesn't work. I have rebuilt the catalog several times and have even binned the backup set and setup a new one, only for that to start failing. This results in the backup set growing bigger and bigger, which impacts offsite duplication times. The only way I can reduce the size of the backup set is to manually delete backups one by one, which is unmanagable. The 'repair catalog' option takes about 10 seconds and seems to do very little in the way of fixing the catalog... + Executing Groom DR at 08/01/2012 19:00 (Execution unit 1) Grooming Backup Set DR (Non CORE)... Groomed 31.9 GB from Backup Set DR (Non CORE). Grooming Backup Set DisasterRecovery1... Groomed zero KB from Backup Set DisasterRecovery1. Grooming Backup Set DisasterRecovery1 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 DisasterRecovery1, error -1 ( unknown) 08/01/2012 19:40:55: 2 execution errors Duration: 00:05:14 (00:00:01 idle/loading/preparing) + Executing Groom DR at 06/01/2012 19:00 (Execution unit 2) Grooming Backup Set DR (Non CORE)... Groomed zero KB from Backup Set DR (Non CORE). Grooming Backup Set DisasterRecovery1... Grooming Backup Set DisasterRecovery1 failed, error -2241 ( Catalog File invalid/damaged) 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 DisasterRecovery1, error -1 ( unknown) 06/01/2012 19:25:16: 2 execution errors Duration: 00:17:56 (00:03:26 idle/loading/preparing) + Executing Groom CORE servers > NAS at 07/01/2012 14:00 (Execution unit 2) Grooming Backup Set DomainCont... Groomed 4.7 GB from Backup Set DomainCont. Grooming Backup Set FileserversBackups... Groomed zero KB from Backup Set FileserversBackups. Grooming Backup Set FileserversBackups 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 FileserversBackups, error -1 ( unknown) Grooming Backup Set CVSServers2011... Groomed zero KB from Backup Set CVSServers2011. Grooming Backup Set DatabaseOnly... Groomed zero KB from Backup Set DatabaseOnly. Grooming Backup Set DatabaseServ... Groomed 9.9 GB from Backup Set DatabaseServ. 07/01/2012 17:05:14: 2 execution errors Duration: 00:24:25 (00:12:13 idle/loading/preparing) 2) Occasionally I get a 'building snapshot' hang, where it'll be right at the end of the proactive backup process and it'll stop dead. Retrospect cannot backup any further users and I cannot manually stop the snapshot/backup by using the 'stop' button in the GUI. The only way I can get backups moving again is by crashing the application and launching it again, where it'll carry on OK again. It's not the same client that it happens on... Is anyone else seeing these issues? Richard Quote Link to comment Share on other sites More sharing options...
mastercam Posted January 13, 2012 Report Share Posted January 13, 2012 WIth some of the grooming issues, I've found I needed to rebuild the catalog file helps (NOT repair...rebuild). I also make sure to, now, place the Cat. File on a different drive than the set it works with. Seems more stable (and is recommended). Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted January 17, 2012 Author Report Share Posted January 17, 2012 Hi MasterCam, thanks for your reply. The Grooming fails even after a rebuild and I have the catalogs on the OS SSD disk and the backups sets on a SMB NAS box. I might have to slice up my Backup Sets more, although even that's a huge manual effort in Retrospect! Rich Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted January 17, 2012 Author Report Share Posted January 17, 2012 Same error: + Executing Grooming at 17/01/2012 12:03 (Execution unit 4) Grooming Backup Set DR (Non CORE)... Groomed 8.6 GB from Backup Set DR (Non CORE). Grooming Backup Set DR (Non CORE) 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. 17/01/2012 12:49:16: Execution incomplete Duration: 00:46:07 (00:06:37 idle/loading/preparing) Freshly rebuild catalog file which was groomed today. The RS Server is backing up other laptops and moving snapshots at the same time, so the NAS target isn't dropping offline or anything - just seems a generic error. Rich Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted January 23, 2012 Author Report Share Posted January 23, 2012 Just some more info on this after spending a day trying to get the grooming working. Having migrated the SQL backups from DR backup set 1 to a new DR backup set 2, only DR backup set 2 is failing to groom now. This suggests it's a problem grooming out SQL backups (using the SQL backup add-on). + Executing Groom DR at 22/01/2012 19:00 (Execution unit 1) Grooming Backup Set DR (Non CORE)... Groomed 27.4 GB from Backup Set DR (Non CORE). Grooming Backup Set DisasterRecovery1... Groomed 138.2 GB from Backup Set DisasterRecovery1. Grooming Backup Set DisasterRecovery2... Groomed 5.9 GB from Backup Set DisasterRecovery2. Grooming Backup Set DisasterRecovery2 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 DisasterRecovery2, error -1 ( unknown) 22/01/2012 20:46:21: 2 execution errors Duration: 00:39:36 (00:01:56 idle/loading/preparing) Just to test things out, I ran the Groom again, just on DR 2 and got this: + Executing Grooming at 23/01/2012 10:35 (Execution unit 1) Grooming Backup Set DisasterRecovery2... Groomed 2.7 GB from Backup Set DisasterRecovery2. 23/01/2012 10:41:40: Execution completed successfully Duration: 00:05:39 (00:01:01 idle/loading/preparing) Strange! Richard Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.