willfurby Posted May 9, 2014 Report Share Posted May 9, 2014 Windows 7 Pro SP1 x64 with 8GB RAM Retrospect Multi Server v9.0.1 (110) I have a client who is experiencing quite a number of assertion errors. He has already renamed the programdata\retrospect folder and recreated scripts, and recataloged backup sets. This morning he received Assertion failure at "glyphco.cpp-2862" I am attaching the assert_log.utx file. Any assistance would be appreciated. assert_log.utx 1 Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 9, 2014 Report Share Posted May 9, 2014 Do you know what Retrospect is doing at the time the assert happens? Does it happen when opening the program? Scanning, copying, matching, etc…. 1 Quote Link to comment Share on other sites More sharing options...
willfurby Posted May 9, 2014 Author Report Share Posted May 9, 2014 It was matching. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 12, 2014 Report Share Posted May 12, 2014 This type of error can happen when Retrospect is running low on memory. How large is the backup set you are matching against? How many files/folders are on the source volume? Do you run multiple executions? If you check the task manager during this operation, how much RAM is Retrospect using? How much is available on the system? Quote Link to comment Share on other sites More sharing options...
willfurby Posted May 12, 2014 Author Report Share Posted May 12, 2014 I'll have to look into that. I will talk with the client and get back to you. Quote Link to comment Share on other sites More sharing options...
willfurby Posted May 12, 2014 Author Report Share Posted May 12, 2014 The Retrospect computer is a Windows 7 Pro workstation with 8GB RAM. The backup set is on a NAS, so is not attached to the workstation at all. The client is going to run a recycle backup of his servers. I asked him to pause the schedule on any other scripts, so that we only have one operation running. We'll see how that goes and I will post an update. Quote Link to comment Share on other sites More sharing options...
willfurby Posted May 15, 2014 Author Report Share Posted May 15, 2014 Backing up with only one execution running seems to work. Must be too much for the computer to run multiple executions. Quote Link to comment Share on other sites More sharing options...
bdunagan Posted May 27, 2014 Report Share Posted May 27, 2014 Thanks for posting this assert. We've identified and fixed the issue (#4670), and it will be in the next release. 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.