Jump to content
Richy_Boy

Slow matching under 7.7?

Recommended Posts

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?

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

We have reproduced the problem and we believe we have a fix, which is currently in internal testing.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

 

Share this post


Link to post
Share on other sites

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.

 

 

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

 

Share this post


Link to post
Share on other sites

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)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×