Search the Community
Showing results for tags 'failed scripts'.
The search index is currently processing. Current results may not be complete.
If you have a mobile client, one that disconnects and reconnects from the LAN (wired) Retro 15.6 will fail when the client returns. It's happened to me twice that Retro doesn't recognize the client when it again plugs in / appears on the network on it's next scheduled backup. The error is "Client unavailable." I believe this to be a long standing issue. The Client in System Preferences seems not to give any bad indications and show status as normal, but it clearly isn't. The symptom is the client is un-recognized when refreshing or locating it, it can be seen after such a failure to run a script. I suspect this is a problem with (Retrospect's) multicast service as compared with Apple's Bonjour service. Even a desktop that has been restarted occasionally fails on multicast (due to sleep recognition issues previously reported). Apparently is still runs backups probably because the last time this happened I located to a fixed address. I can report a workaround to this issue which seems to work to recover from the error. Just log out the user and log back in, then launch the Retro app to locate the source client. Retrospect server then recognizes this client on future backup scripts.