Mayoff Posted March 15, 2010 Report Share Posted March 15, 2010 For those with slow matching. Can you be really hear about a few points: 1) Are you using 32 bit or 64 bit Retrospect 2) What is the Exact Retrospect version being used? Quote Link to comment Share on other sites More sharing options...
mwilliamson Posted March 15, 2010 Report Share Posted March 15, 2010 I have given this info. to you before and also to the support team. I am running 32-bit Windows 2003 Server SP2 with 4GB of RAM. Retrospect version is 7.7.208 with Driver Update and Hot Fix version 7.7.1.102. Quote Link to comment Share on other sites More sharing options...
railes Posted March 15, 2010 Report Share Posted March 15, 2010 64 bit Retrospect version 7.7.208 with Driver Update and Hot Fix version 7.7.1.102. Windows 2003 R2 sp2 64 bit Quote Link to comment Share on other sites More sharing options...
jrosebrook Posted March 15, 2010 Report Share Posted March 15, 2010 I was also running 7.7.208 on 2003 R2 64bit. Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted March 16, 2010 Author Report Share Posted March 16, 2010 7.7.208 on Windows XP (32-bit) I don't know whether it's a good or bad thing to be asked such a simple question after all this time ranting. Can the RS team team really not see this when backing up a significant amount of data? Rich Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 16, 2010 Report Share Posted March 16, 2010 We have reproduced the problem and we believe we have a fix, which is currently in internal testing. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 18, 2010 Report Share Posted March 18, 2010 I wanted to share some test results internally. With the new code changes, we have seen matching operations go from over 150 minutes to under 5 minutes using our test data! We will get this change out to customers next month. Hopefully earlier half of the month. Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted March 18, 2010 Author Report Share Posted March 18, 2010 Great, but I do hope that someone at Retrospect looks at how this was messed up in the first place and even more so, how it got past testing. I mean, you released 7.7 without noticing that matching took 30 times longer than under 7.6?! Many thanks for sharing some info though, it makes a nice change from being treated like mushrooms. Rich Quote Link to comment Share on other sites More sharing options...
mwilliamson Posted March 18, 2010 Report Share Posted March 18, 2010 Am also hoping the "tmemory" crashes will also be remedied. I still can only use 2 execution units. If I use any more the system inevitably crashes after several hours. On 7.6 I had no trouble running 4 execution units for several days at a time without crashes. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 29, 2010 Report Share Posted March 29, 2010 An update to Retrospect for Windows has been released. This update is version 7.7.325 and is recommended for all Retrospect 7.7 customers. This update includes bug files for exchange, proactive backup, improved memory management and more. You can download the update from http://www.retrospect.com/updates and it will be available over automatic updates soon. Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted March 29, 2010 Author Report Share Posted March 29, 2010 Hi Mayoff, have you got a list of the issues fixed in it? Rich Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 29, 2010 Report Share Posted March 29, 2010 http://kb.dantz.com/article.asp?article=9729&p=2 Quote Link to comment Share on other sites More sharing options...
jrosebrook Posted March 29, 2010 Report Share Posted March 29, 2010 Going to install it in VMWare to see if the matching problem is actually fixed. I'd rather not have to go through the nightmare of upgrading my live server again. I'll let you all know what happens. Quote Link to comment Share on other sites More sharing options...
utig Posted April 27, 2010 Report Share Posted April 27, 2010 so - who has actually tested the 3/21 release and found that it addressed their slow matching issues? I'll be darned if I go through that agony again without some expectation that it will improve things. 7.6 has remained fairly stable for us (few crashes in 4 months, and no failed catalog rebuilds) - the reasons we originally went to 64 bit 7.7 in January. Quote Link to comment Share on other sites More sharing options...
robvil Posted April 28, 2010 Report Share Posted April 28, 2010 Good question... I´m thinking the same as you. I´m still on 7.6 due to all the issues there was/is with 7.7 so it would be nice to hear if anybody is running the lasted 7.7 without issues. Anybode out there? Regards Robert Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 28, 2010 Report Share Posted April 28, 2010 Keep in mind, it is working for 1000's of customers.... When something works they typically don't come to the support forum to share stories. The fact that you are not hearing from new people reporting the matching issue is a sign it is working. Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted April 30, 2010 Author Report Share Posted April 30, 2010 Hi Robert, I have upgraded again to RS 7.7 and it seems to be working well. However, I haven't tried restoring servers to simulate DR yet, but have restored client/server data which has been deleted by accident by the user. Richard Quote Link to comment Share on other sites More sharing options...
robvil Posted May 3, 2010 Report Share Posted May 3, 2010 Thanks. Maybe it´s time to upgrade then. Regards Robert Quote Link to comment Share on other sites More sharing options...
mjbarry Posted May 12, 2010 Report Share Posted May 12, 2010 We have upgraded to version 7.7.325 and are having problem similar to this. When retrospect goes to build a catalog with a large number of files it hangs and never completes. It also appears that retrospect takes all available memory. Is there a way to figure out why it hung? The logs do not show anything. Quote Link to comment Share on other sites More sharing options...
robvil Posted May 12, 2010 Report Share Posted May 12, 2010 I´ve been running 7.7.325 for a week now on a 32bit Windows 2008 and so far things works as it did in 7.6. Only found some minor issues. Regards Robert Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 12, 2010 Report Share Posted May 12, 2010 How much memory do you have? How many operations running at once? How big is the backup set? How big is the source volume (number of files) Quote Link to comment Share on other sites More sharing options...
mjbarry Posted May 12, 2010 Report Share Posted May 12, 2010 We have 12 GB of RAM. 1 operation was running. Total size of the NAS being backed up was 442 GB (282,311 files). Quote Link to comment Share on other sites More sharing options...
mjbarry Posted May 12, 2010 Report Share Posted May 12, 2010 I am running this version on a 64bit SBS 2008 Standard Server. I am not sure if that would make any difference. 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.