Jump to content
Sign in to follow this  
vksmjones

-843, Resource in use by another operation

Recommended Posts

Retrospect crashed last night and now I can't get backups to start on 2 of my backup sets. Backups to 2 different sets are working without issue. 1 job is waiting on backup set week1-1 and the other is waiting on backup set week 1-2. 1 job is running on backup set week1-3 and another is running on set week1-4. After finding Retro crashed this morning, I rebooted the server so there shouldn't be any files left open. Is it possible Retro left a file lock on these 2 sets when it crashed? If so, how do I close the lock?

 

Thanks

Share this post


Link to post
Share on other sites

Hi

 

What version of Retrospect are you using? Make sure you have the latest update for your version. The reboot should have taken care of any locks.

 

Thanks

Nate

Share this post


Link to post
Share on other sites

v7.0.326 update v7.0.6.108.

 

I had to let the jobs that were backing up to sets 3 and 4 complete, restart Retrospect and now I am able to backup to all 4 sets at the same time. Retrospect needs to be specific about what it thinks is using a resource or backup set AND we need a tool that breaks the lock if we know that the resource is not in use.

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  

×