Ramon88 2 Report post Posted February 4, 2010 Hmm, strange... Keep us posted. Btw, how much RAM does your Retrospect system have? Share this post Link to post Share on other sites
rcohen 0 Report post Posted February 4, 2010 32 GB. Retrospect's peak memory usage is about 1 GB. Share this post Link to post Share on other sites
Ramon88 2 Report post Posted February 5, 2010 Okay, that should be enough... What kind of backup target for the storage set do you use? Is it possible to use another storage system to test? Btw, we backup a lot of files (in the millions) for some of our clients as well and don't see this problem (using 7.6.123). So I'm interested because we may want to upgrade to 7.7. Share this post Link to post Share on other sites
rcohen 0 Report post Posted February 5, 2010 What kind of backup target for the storage set do you use? Is it possible to use another storage system to test? I'm doing backups to disk, using a Thecus NAS. I have already tried backing up to other systems (actual Windows and Linux servers), with no change in behavior. Share this post Link to post Share on other sites
mwilliamson 0 Report post Posted February 5, 2010 Hi all, below is the thread I have been posting on. The is the same memory error everyone who has large backup jobs is seeing. It almost seems worse after the update from 7.7.203 to 7.7.208. I have been sending my assert and operations logs to EMC support but still no fix for this particular issue. I am completely unable to rebuild a large catalog file and twice have had to blow away my backup sets and start over. http://forums.dantz.com/showtopic.php?tid/32765 -Matt Share this post Link to post Share on other sites
rcohen 0 Report post Posted February 5, 2010 Is this problem in the 32-bit version as well? I have been using the 64-bit version. Share this post Link to post Share on other sites
mwilliamson 0 Report post Posted February 6, 2010 Yes, the support team has confirmed it is happening on both 32 and 64-bit systems. Share this post Link to post Share on other sites
railes 0 Report post Posted March 5, 2010 I'm seeing these errors in all my tape backups. I'm running 7.7.208 on 64 bit Windows 2003. I never saw this in 7.6. I am almost certain I had tons of these errors when I first started with 7.7 the second time (after I'd bailed back to 7.6 waiting for the mem leak fix). But then I changed this setting in the retro.ini file in the Retrospect program directory: MaxMemPercent=70 from the default which I believe is MaxMemPercent=30. I was told by Tech Support many months ago that this config controlled how much system RAM RS was allowed to take up. I'm pretty sure this reduced these Heap Validate Failed errors. Be careful with this setting. Going too high will cause the program to crash with memory assert error. Share this post Link to post Share on other sites
Mayoff 124 Report post Posted March 24, 2010 The 64 bit version of Retrospect does not use the .ini setting, so don't bother making a change. The heap validation issue is fixed in the next release, it's a bug. Share this post Link to post Share on other sites
