Jump to content
jjevans

Retrospect 10.5.0.110 does not finish backup

Recommended Posts

Retrospect 10.5.0.110 does not finish backup due to the application just closing ~one hour into backup which is 8% of the backup. This is clean install on Windows 10. All drivers updated.

 

What can I do to have it complete the entire backup?

 

Any insight is appreciated.

 

Thank you,

 

JJ

 

 

Share this post


Link to post
Share on other sites

Is it any backup closing after about an hour?

Or just this specific backup?

 

Is it energy saver that comes into action after one hour?

 

I would run CHKDSK on the source in question before trying again.

Share this post


Link to post
Share on other sites

I have the same issue with Retrospect 10.5.0.110 and Win 10.No retrospect log errors, no windows errors. Just dies in the middle of a clients backup. Windows Defender is off, two different backup sets. No disk chkdsk erros.

Share this post


Link to post
Share on other sites

I have the same issue with Retrospect 10.5.0.110 and Win 10.No retrospect log errors, no windows errors. Just dies in the middle of a clients backup. Windows Defender is off, two different backup sets. No disk chkdsk erros.

 

But always at the same stage of same client?

Share this post


Link to post
Share on other sites

No, different times and different clients. It ran fine for two days, then failed, then failed again in 2 hours. It seems to get progressively worse until I reboot. 

40+ clients. Proactive & regular scripts both fail.   Using two USB external drives, both fail. Task manager showed the app gone but the processes still there but no activity.

Share this post


Link to post
Share on other sites

Was this ever solved for 10.5.0.110? Win 10

This happens to me several times over a couple days then after a few reboots it stops. I suspect it is to do with memory conflicts in the boot process.

 

Share this post


Link to post
Share on other sites

pplicit:

I am not a Retrospect Windows administrator.  However the Knowledge Base document "Retrospect 10 for Windows System Requirements" says, under "System Recommendations",  "For Windows 10, Retrospect requires the 64-bit version".  Is the 64-bit version of Windows 10 what you're running on your "backup server" machine?

Share this post


Link to post
Share on other sites

For the record, looking back at all the silent application closings I found the common factor was the backup set. I recycled (emptied) the backup set, started fresh and have had no further problem.

I have often transferred the latest snapshot from one set to a another recycled one and this may have perpetuated the problem.

 

Share this post


Link to post
Share on other sites
1 hour ago, Brinkerhoff said:

I'm having the same issue with the backup, but this didn't help at all. It still continues to crash. Does anyone have any other ideas?

Which version of Retrospect and which version of Windows are you running?

Share this post


Link to post
Share on other sites

I tried many things and this setup is what works now:

I use only proactive backups (not scripts) of the  backup clients container on an alternating days schedule.

I do not let the backup sets groom - when they get close to full, I recycle them and start over clean, always keeping another set up to date.

My selectors exclude most of the windows system files, including users files & programs only.

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

×