Steve3 Posted July 21, 2008 Report Share Posted July 21, 2008 So, I have a corrupt catalog file, [color:red]again.[/color] Retrospect won't groom it, so I tell it to rebuild the catalog from the 3 local disk members. It works for about 4 hours, then complains "not enough application memory". Is there any option besides "stick more RAM in the backup server"? Retrospect Multi-server 7.5.508 Driver and HotFix 7.5.14.102 Windows XP. Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 22, 2008 Report Share Posted July 22, 2008 Retrospect Multi-server 7.5.508Driver and HotFix 7.5.14.102 Windows XP. How much RAM do you have? What is running besides Retrospect? And I don't just mean applications, I mean RAM hogging services, too. A server operating system would be much more stable than a personal OS like XP. (And that is valid even if M$ calls it "Professional".) Quote Link to comment Share on other sites More sharing options...
Steve3 Posted July 22, 2008 Author Report Share Posted July 22, 2008 The machine has 1 gig now. It's dedicated to running Retrospect, so it does essentially nothing else. No other services at all, and it is XP Pro. The OS is plenty stable- I don't think this machine has ever BSOD'ed, and Retrospect application crashes don't exceed my expectations for a Windows app. I've rebuilt catalogs before.... just need a workaround for this "not enough application memory" issue. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 22, 2008 Report Share Posted July 22, 2008 How many files/GB have been read when the memory error happens? How much free space do you have on the C: Disk? Quote Link to comment Share on other sites More sharing options...
Steve3 Posted July 22, 2008 Author Report Share Posted July 22, 2008 Hi Robin, There's 18.9 gigs open on C: I don't get the opportunity to see how many files/GB are read before the error. It starts rebuilding the catalog, works for about 3-4 hours, then presents a dialog stating Save the partial session? Save will keep all files already found, omitting the remainder of this member. Revert will permit the rebuild to start again with this member. [save] [Revert] I don't want to omit part of a member... what if the file I need to restore is in that omitted section? But if I revert, it restarts, and 3-4 hours later I end up in exactly the same spot. Quote Link to comment Share on other sites More sharing options...
Steve3 Posted July 22, 2008 Author Report Share Posted July 22, 2008 I chose save this time, and got to see that it ran through 303303 files, 224.9GB And then the operation is done. Log doesn't provide anything else new.... "not enough application memory", execution incomplete, and the stats of files, GB read, performance and duration Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 22, 2008 Report Share Posted July 22, 2008 After you click save. Are you able to use tools>Repair>Update existing catalog file? Retrospect could be reaching a corrupted file within the backup data files and gets stuck. Update Existing Catalog should continue from the stopped point. Quote Link to comment Share on other sites More sharing options...
Steve3 Posted July 22, 2008 Author Report Share Posted July 22, 2008 I did start an Update Existing process after that last post.... 42gigs into it right now. I'll update the thread when there's more to say. Quote Link to comment Share on other sites More sharing options...
Steve3 Posted July 23, 2008 Author Report Share Posted July 23, 2008 Yes, it appears that after it fails with the not enough memory error, you can continue with a Update Existing catalog. That finished without issues, and seems to work properly. 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.