Jump to content
Sign in to follow this  

-505 error in proactive backups

Recommended Posts

When a client has multiple favorite folders used as sources in a proactive script, it appears that two activity threads can attempt to back up two different favorite folders on the same client simultaneously. This generates a -505 error, which results in neither folder being backed up. Retrospect will then not attempt to access the client again until the error wait interval specified in the script has passed. This is probably not a big deal if the proactive script is active all the time, but can cause a source to miss a backup opportunity if the failure occurs too close to a specified script stop time, as we have discovered.

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