Gavinpitt Posted July 21, 2010 Report Share Posted July 21, 2010 I am having a problem with one of my servers in that when it gets backed up at eth end when it creates the catalogue Retrospect crashes. I have reinstalled the client, Recreated the backup sets, created a new catalogue, new script and I am now out of ideas. The error is "assertion failure at tmemory.cpp-382" log at assert_log.utx Please help. Quote Link to comment Share on other sites More sharing options...
Daniels Posted July 21, 2010 Report Share Posted July 21, 2010 Have you reinstalled the actual Retrospect application on the server? If there is a problem with the actual program reinstalling the client would not fix the problem. Quote Link to comment Share on other sites More sharing options...
Gavinpitt Posted July 21, 2010 Author Report Share Posted July 21, 2010 No beacuase it only happens when I backup the domain controller and not when backing up any of the other 20 servers. It has taken me months to set this up and I really am not fond of restarting from scratch because of one problematic machine. Quote Link to comment Share on other sites More sharing options...
Daniels Posted July 21, 2010 Report Share Posted July 21, 2010 When doing an uninstall and re-install it preserves all the scripts, backup sets, settings so you would not lose this information. I would run a chkdsk on the Domain Controller and check the integrity of the drives to see if any are failing. Quote Link to comment Share on other sites More sharing options...
Gavinpitt Posted July 21, 2010 Author Report Share Posted July 21, 2010 I have run a checkdisk and the problem still remains. The drives are all still fine. Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 21, 2010 Report Share Posted July 21, 2010 You seems to have tried everything. I would call Retrospect Support. If you are not on a support contract, buy a support incident. (This is just a user-to-user forum, NOT support.) Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 21, 2010 Report Share Posted July 21, 2010 That error is actually a known bug. We are still working on it. How much RAM do you have? How much free space on the C: disk? Quote Link to comment Share on other sites More sharing options...
Gavinpitt Posted July 21, 2010 Author Report Share Posted July 21, 2010 3GB RAM and 21.4GB free space. Windows Server 2003 SP2. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 21, 2010 Report Share Posted July 21, 2010 How many executions do you run at the same time? Retrospect needs between 5 and 10 GB of free disk space for each execution unit. Quote Link to comment Share on other sites More sharing options...
Gavinpitt Posted July 21, 2010 Author Report Share Posted July 21, 2010 I tried with it set on 8 and then trid with it set to 1. Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 22, 2010 Report Share Posted July 22, 2010 But how many did actually run of the 8 allowed? Quote Link to comment Share on other sites More sharing options...
Gavinpitt Posted July 22, 2010 Author Report Share Posted July 22, 2010 Generally only two and sometimes just one. But it does not make a difference. I also have a proactive backup running but I tried disabling that as well and no go. Quote Link to comment Share on other sites More sharing options...
DeltaBank Posted July 23, 2010 Report Share Posted July 23, 2010 My experience has been running just one execution unit and doing a system state backup needs almost 15GB free space on C:, but that it still crashes with the assert error. Has any progress been made on this issue? Quote Link to comment Share on other sites More sharing options...
ddtmm Posted July 28, 2010 Report Share Posted July 28, 2010 I once had that problem too. After trying just about everything I could think of I deleted the script that was running the backup that made it crash and recreated the script from scratch, along with a new backup set too and the problem went away. I don't know if it was coincidence or not but the problem didn't come back. I am running 7.6.123 multiserver with driver update/hotfix 7.6.2.101 and I mostly back up Mac clients, but a few windows clients too. Quote Link to comment Share on other sites More sharing options...
DeltaBank Posted July 28, 2010 Report Share Posted July 28, 2010 Well, for me 7.6 worked GREAT. But after upgrading to Win2008R2 and Retrospect 7.7, the great part stopped and the issues began. I have tried the fresh new script, fresh new backup set, and fresh new config tricks. No go help each time. Quote Link to comment Share on other sites More sharing options...
suzib6sw Posted August 31, 2010 Report Share Posted August 31, 2010 Same here.. I have two servers running 2 executions at the same time.. Both are running essentially the same scripts.. One is 7.6 the other 7.7. The 7.7 refuses to run 2 executions with any consistency and repeatedly crashes with various assert errors etc. The same server running 7.6 before the upgrade was fine. the other server is still on 7.6 mainly because if I upgrade to 7.7 , Im GOING to get shouted at when (note not IF) it crashes. Honestly, I have lost confidence in Retrospect in our setup. While I respect thet Roxio are getting their feet under the table so to speak, this NEEDS to be fixed sooner rather than later. Pete Oh and yes,.. I have tried everything suggested by both Tech support and the comments in the forum. I even saved the old script folder, re-wrote the simplest ones I could and then ran the two executions, and within 12 hours, 7,7 was down . Quote Link to comment Share on other sites More sharing options...
mwilliamson Posted September 23, 2010 Report Share Posted September 23, 2010 I just wanted to chime in. I too have experienced these same issues since 7.7 came out. I have plenty of free space on C: more than 15GB for each execution unit and is it still crashes. When I run only two execution units it might run for a day or two or even a week but eventually crashes. When I run any more than two execution units it crashes overnight everytime. I am on 32-bin Win 2003 Std. Are any of you running 64-bit? Does it alleviate the issue at all? I read older posts related to 7.6 saying this problem went away on 64-bit installs. 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.