Jump to content
Sign in to follow this  

"Completing restore" won't quit

Recommended Posts

During a Restore, after Retrospect has copied the requisite files, it then works on "Completing restore." My assumption is that this operation, for which there is no public documentation (c'mon Retrospect, Inc.), and which can go on for quite some time, is probably restoring file and folder metadata.


Because this process is lengthy, there is the distinct possibility that a client computer goes to sleep or is disconnected from the network during the "Completing restore" phase. (It's happened to us a couple of times.) Unfortunately, there appear to be nothing in Retrospect that is designed to recognize or handle this kind of exception; it will blithely say it's "Completing restore," apparently forever until the engine is stopped, long after there is no longer any response from the other end of the line.


Thus far, our users haven't experienced any noticeable issues after their "Completing restore" operations were interrupted. However, I consider Retrospect's inability to deal with this issue a pretty significant lack. 

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
Sign in to follow this