Jump to content
Sign in to follow this  
BillIrwin

Suddenly error -505 backup client reserved

Recommended Posts

Every backup, both data files and Exchange server, for the last three days is generating this error. MS 7.0.301 on Windows 2003 server backing up from NT4 server and Exchange 5.5. Both servers have been restarted.

 

Can't access volume NT 4 (C:) on nsaserver, error -505 (backup client reserved)

Can't access volume Users (D:) on nsaserver, error -505 (backup client reserved)

 

This is the only symptom reported. Any ideas?

 

Bill

Share this post


Link to post
Share on other sites

Try going to nsaserver, open the Retrospect client. Turn off the client, hit Apply, turn the client back on and hit Apply. Verify that the Status says ready and try backing it up again.

Share this post


Link to post
Share on other sites

Ron:

This seems to have done it. I tried a manual backup before restarting the remote client to confirm that I received the -505 when I asked for a preview of the files that will be archived. After restarting the remote client the preview worked. I don't want to run a full backup during the day so I'll see how it goes tonight, but the error went away.

 

Do you know why a restart of the remote computer doesn't fix this, but a restart of the Retro client does?

 

Thanks,

Bill

Share this post


Link to post
Share on other sites

This has resolved the -505 error. The KB article needs to be updated with this solution, especially since it should be tried first, prior to restarting both the backup client and the backup server.

 

Thanks Ron.

Share this post


Link to post
Share on other sites

I would agree that this should be in the KB. I'd tried the old method and for the most part given up for the time being because of other more serious Retrospect issues. :~(

Share this post


Link to post
Share on other sites

I'm getting this also.. restarting our Exchange 2003 server isn't a great solution for us as it means downtime!

 

Any other ways of fixing this? One night it's fixed by restartign services and reinstalling the client... next thing it's broken again! frown.gif

 

Rich

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  

×