twickland Posted May 19, 2015 Report Share Posted May 19, 2015 Prior to Retrospect 12, I believe that the idle/loading/preparing time logged for a particular source always applied just to the time spent on that source, which of course is exactly what one would hope to see. However, in Retrospect 12, the idle/loading/preparing time logged for a source also includes whatever time has been spent attempting to access prior client sources in the backup script that were offline at the time of backup. I can confirm that this anomaly occurs with clients that were added by direct IP addressing, which generate a -519 network communication failed error when they are offline. I don't know whether it also occurs with clients that were added via multicast or subnet broadcast, as we do not use those methods. 3 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.