Viotech Posted April 17, 2009 Report Share Posted April 17, 2009 This Is the error i am getting... - 4/15/2009 6:00:15 PM: Copying Local Disk (C:) 4/15/2009 6:04:38 PM: Grooming Backup Set WD Backup Pro... 4/15/2009 6:15:59 PM: Groomed 6,833 KB from Backup Set WD Backup Pro. Grooming Backup Set WD Backup Pro failed, error -1115 (disk full) You must recreate the Backup Set's Catalog File. See the Retrospect User's Guide or online help for details on recreating Catalog Files. 4/16/2009 9:21:27 AM: Execution stopped by operator Remaining: 921 files, 3.3 GB Completed: 688 files, 145.4 MB, with 35% compression Performance: 136.2 MB/minute Duration: 15:21:11 (15:20:07 idle/loading/preparing) I have aldready recreated the Catalog File however the same error remains. Also according to the history, after completeing the recatalog, i got these errors... + Executing Recatalog at 4/8/2009 4:25 PM To Backup Set WD Backup Pro... The Disk Backup Set data file "AA000051.rdb" reported missing by user Bad Backup Set header found (0xe8400890 at 147,385,496) Bad Backup Set header found (0x759d8900 at 159,461,024) Bad Backup Set header found (0x4ea1e874 at 159,463,848) Bad Backup Set header found (0x16226f6d at 159,469,536) Bad Backup Set header found (0x8cd9905c at 159,469,664) Bad Backup Set header found (0x2c94ab03 at 159,469,728) Bad Backup Set header found (0xb336a95d at 159,469,792) Bad Backup Set header found (0xcf1a4015 at 159,469,856) Bad Backup Set header found (0xda5ae9ca at 159,469,920) Bad Backup Set header found (0x7d20037e at 159,469,984) Bad Backup Set header found (0x15184b98 at 159,470,048) Bad Backup Set header found (0x9fc68661 at 159,470,112) Bad Backup Set header found (0xffd1f02e at 159,470,176) Bad Backup Set header found (0xce82f424 at 159,470,240) Bad Backup Set header found (0x17507c1d at 159,470,304) Bad Backup Set header found (0x051c7c33 at 159,470,368) Bad Backup Set header found (0x1ed3c793 at 159,470,432) 4/8/2009 9:16:09 PM: 18 execution errors Completed: 125553 files, 60.4 GB Performance: 215.1 MB/minute Duration: 04:49:37 (00:02:18 idle/loading/preparing) Are these two issues linked? How can i resolve this issue. Quote Link to comment Share on other sites More sharing options...
blm14 Posted April 17, 2009 Report Share Posted April 17, 2009 You need a fair amount of space on the drive on which your catalog file is stored in order to groom. How much free space do you have? Quote Link to comment Share on other sites More sharing options...
Viotech Posted April 17, 2009 Author Report Share Posted April 17, 2009 I have no space left. But the script we run is supposed to groom automatically to filter out old backups. Quote Link to comment Share on other sites More sharing options...
blm14 Posted April 17, 2009 Report Share Posted April 17, 2009 You misunderstand me. The grooming PROCESS requires space on the drive that catalog file lives on. If you're waiting until the drive the catalog files lives on is full to groom then it's always going to fail... Quote Link to comment Share on other sites More sharing options...
Viotech Posted April 17, 2009 Author Report Share Posted April 17, 2009 Oh ok. I have manually deleted some old backups and created a new backup set with a different grooming process. Im running the new back up now so once its done i will just free up the external disk by deleting all of the backups from the orginal set. thanks for your help Quote Link to comment Share on other sites More sharing options...
blm14 Posted April 17, 2009 Report Share Posted April 17, 2009 I think there's also something about ram requirements for grooming but I dont remember... 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.