Jump to content
Sign in to follow this  
MRIS

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.

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  

×