Richy_Boy Posted December 24, 2012 Report Share Posted December 24, 2012 Apparently there is a fix on the way for this, but I thought everyone should know... + Executing Grooming at 24/12/2012 11:16 (Execution unit 1) Grooming Backup Set PSTBackups... Assert occurred on 24/12/2012 at 11:17:30 + Retrospect version 8.0.0 (199) Launched at 24/12/2012 11:20 in user account UK\******** + Executing Grooming at 24/12/2012 11:22 (Execution unit 1) Grooming Backup Set PSTBackups... Assert occurred on 24/12/2012 at 11:23:43 Trying to groom the same backup set containing PST files from my client machines. Keeps crashing, so unless a catalog rebuild fixes this, my data is all lost. You would have thought after all this time using the same backup format, a corrupt backup set/catalog would be handled pretty well.. I should point out, RS8 seems to behave better when using clean backup sets (i.e. not from an RS7.7 installation), but it still fails way more often than it should. Richard Quote Link to comment Share on other sites More sharing options...
Mayoff Posted January 2, 2013 Report Share Posted January 2, 2013 Contact tech support. We can point you to a pre-release version that should fix these issues. Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted January 8, 2013 Author Report Share Posted January 8, 2013 Yes it did stop the crashing, thanks. I do wonder how this go through internal testing without crashing though... 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.