Jump to content

Configurable Automatic Client Timeout

Recommended Posts

If a brief glitch occurs in the network during a backup involving the Windows Agent, an error occurs along the lines:


Can't access volume Local Disk (C:) on server01, error -519 (network communication failed)


The problem is that this server misses all subsequent backups because the agent still thinks that it is in use by the server, and the server gets messages (only if you click on client properties and refresh) that the client is reserved, even days later.


I had to logon to the server, use the Retrospect agent from the control panel, flick the switch OFF then ON.


The feature request is a configurable client option where if a client doesn't actively communicate with a server during a backup for say a 24 hour period, it automatically ends the session and gets ready for the next one.


Also if the server could send an email alert an log an error if there exists a client that is included in a proactive script that hasn't been backed up in say 3 days due to "client reserved" reasons.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...