Jump to content
Sign in to follow this  
twickland

"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

The general consensus is that Retrospect is setting permissions (ACLs) on the restored files.  Depending on whether they are all "user" files or an OS installation, this may or may not matter but for an OS installation it usually will.

The process is incredibly slow.  Overnight seems to be not uncommon.

The Retrospect user interface for this step leaves a WHOLE LOT to be desired, as there is no status bar, progress report, or active display of file path information to let the user know what is happening (that is, to show that progress is being made), and there's no clear statement of what's being done -- "Completing restore" is remarkably uninformative.

Since this has been reported and commented on many times in the past, it's hard to believe that anything will ever be done to make it better.  Documentation would help.

Dr. Tom Blinn

  • Like 1

Share this post


Link to post
Share on other sites

Oh, and if it's any consolation, Retrospect for Windows doesn't do this any better (or worse) than the Mac versions.  I can't speak to the Linux versions.

  • Like 1

Share this post


Link to post
Share on other sites

drtomblinn,

You don't say what version of Retrospect Mac you are running on your "backup server", nor what version of macOS you are running it under on your "backup server" or your "client".  However, if you want to submit a Retrospect Inc. Support Case for your bug, here is why and how to do so.

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  

×