-
- Influencer
- Posts: 18
- Liked: never
- Joined: Jan 24, 2013 10:15 pm
- Full Name: Asela De Costa
- Contact:
Rolling back changes made by incomplete job run Error
Hi All,
i got following error and cannot backup the servers?
Error: The process cannot access the file because it is being used by another process. Failed to open file [\\NAS01\VeeamProdBackup\ADS01\ADS012015-11-10T214555.vrb] in readonly mode.
As
i got following error and cannot backup the servers?
Error: The process cannot access the file because it is being used by another process. Failed to open file [\\NAS01\VeeamProdBackup\ADS01\ADS012015-11-10T214555.vrb] in readonly mode.
As
-
- Product Manager
- Posts: 6551
- Liked: 765 times
- Joined: May 19, 2015 1:46 pm
- Contact:
Re: Rolling back changes made by incomplete job run Error
Hi,
Please check if any other job/process uses the .vrb file. Also check if there is any antivirus running.
Thank you.
Please check if any other job/process uses the .vrb file. Also check if there is any antivirus running.
Thank you.
-
- VP, Product Management
- Posts: 27377
- Liked: 2802 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Rolling back changes made by incomplete job run Error
The subsequent job run should create a new valid restore point, so there is no need to rollback any changes.
-
- Veteran
- Posts: 635
- Liked: 174 times
- Joined: Jun 18, 2012 8:58 pm
- Full Name: Alan Bolte
- Contact:
Re: Rolling back changes made by incomplete job run Error
I don't understand what you mean by that Vitaliy - reverse incremental (you can tell it's that mode by the .vrb file) always rolls back changes to the full backup file after a failure. "Rolling back changes made by incomplete job run" is what you will see in the real-time statistics during this process. Perhaps you were thinking of forward incremental?
Pavel's right about the possibility of antivirus or similar conflict, but I also occasionally see a NAS decide to lock a file for no obvious reason and not let go until the NAS is fully powered off and back on again (I've even seen a soft reboot not fix it).
What is your support case number?
Pavel's right about the possibility of antivirus or similar conflict, but I also occasionally see a NAS decide to lock a file for no obvious reason and not let go until the NAS is fully powered off and back on again (I've even seen a soft reboot not fix it).
What is your support case number?
-
- VP, Product Management
- Posts: 27377
- Liked: 2802 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Rolling back changes made by incomplete job run Error
I meant to say there is no need to do anything manually, cause if you resolve the issue with a locked file and run a job, we will create a new valid restore point.
-
- Enthusiast
- Posts: 28
- Liked: 3 times
- Joined: Aug 06, 2015 8:21 pm
- Full Name: Weston Strom
- Contact:
Re: Rolling back changes made by incomplete job run Error
I was getting the same error. The job would fail at rolling back changes made by incomplete job run. The only way I was able to get a successful backup was to remove all the old restore points, resyc respository, and start an active full. I did not try to power the NAS on and off. I will try this next time I see the error.
Who is online
Users browsing this forum: Baidu [Spider] and 22 guests