Can't Run Backup - Hangs or Write Error
I have a machine running Windows 10. I've tried both Acronis 2016, then Acronis 2019. But either version eventually gets:
The last backup has been stopped. It will be restarted ...
Write error
We have lots of machines running various version of TI, and none of the others get this problem writing to the same networked drive. At first I thought it was related to VSS, but I tried Acronis snapshot and it too fails. Any ideas?
I see some "access is denied" messages but I'm sure you can analyze this better than me. It should have full access to the network drive. I test that with connect. The logs are attached.
Joel, thanks for the log, what it does do is to confirm a known and unresolved issue present in older versions of ATI...!
15/01/2022 10:11:48:971 AM Writing full version to file: ADMIRALS-PC_full_b1_s1_v1.tib
15/01/2022 10:11:48:971 AM Error 0x1e50023: Please close the application that may currently use the file: \\REPLICA\Acronis Backups\Admiral's Room\ADMIRALS-PC_full_b1_s1_v11.tib
See forum topic: The mysterious _v11.tib file access error.
MVP BrunoC who raised the topic outlines an approach that he has used to get around the issue!
Interesting, so the mysterious and infamous V11.tib issue. Well, using the workaround:
The only way I could get by it was to 1) remove the backup task (but not deleting the files), 2) add the backup task from the latest backup file, 3) reconfigure the backup task as I'd like it.
Won't help me, because I don't have any copies of the backup for this machine to use to add backup task. They're long gone. I wonder if I could use any backup of a machine that I have, and then change all of the parameters.
Joel, the workaround simply means taking the following steps:
- Use Delete for the existing, problem task to remove only the settings for it.
Note: make a note of the important task settings first or capture screen shots of same. - Click on the option to 'Add existing backup' (found hidden under the caret 'v' to the right of the normal '+ Add backup' option).
- Select the latest backup .tib file from your network location to be added - this will create a new task from it but which will need to be reconfigured.
- Reconfigure the new added back task, including schedule etc.
Select the latest backup .tib file from your network location to be added
My problem is that I don't have one from this machine. Can I use one from another machine?
Joel, sorry but adding back a backup from another machine would only create other problems due to the volume of differences that would then be identified for any subsequent backup actions. It would be better to simply create a whole new backup from the problem machine than using one from a different machine.
If the problem backup is also the initial / first backup from this system, then my advice would be to try a different backup application to confirm the issue is definitely only with ATI. Download a copy of Macrium Reflect Free and test with that application.
OK, I got a chance to try Macrium Reflect today. It worked just fine, adding to the mystery of why ATI won't work. What would my next step be?
Joel, if the backup with MR was successful, then again it points to an issue with ATI 2019 on that system.
The options here would be to try a repair install of ATI 2019 initially to see if that resolves the issue, if not, then doing a clean install using the Acronis Cleanup tool (link below) and creating a new backup task. If both these actions still yield problems, then use MR for this system!
You should be aware that Acronis no longer provide perpetual licenses for their products starting with ACPHO, so if you wanted to pursue this issue via Support, you would be required to take out a subscription to ACPHO and show that it happens with that version first!
See KB 68375: Licensing change FAQ: Acronis products switch to subscription-only licenses - where this change was announced!
Joel,
Can you tell me what "\\REPLICA\Acronis Backups\Admiral's Room\ADMIRALS-PC_full_b1_s1_v1.tib" is exactly?
The file name here indicates that this task will create the first backup of the created backup task and your comments support that because you say you do not have any existing backups from which to add back into the Acronis application to recreate the task.
If my conclusion above is correct then the error indicates that you have an open connection to the path \\REPLICA\Acronis Backups\Admiral's Room\ and that is the reason for your access denied error message.
So Macrium succeeded in creating a backup, was that backup to this same path? Did the Acronis task exist previously and you modified it to create a new backup chain?
I see the reference that Steve mentions about the b1_s1_v11.tib but your comments leads me to believe that file cannot exist since you say there are no other backups of the task to work with.
If you have attempted to clone a task for reuse I recommend against doing that. It is always advisable to create a new task when starting a new backup chain.
OK, here's the deal. This PC had TI 2016 and had been working previously doing weekly backups. They were going to the exact same path as now. But at some point a month or so ago the backups would fail, timing out. At that point I did a clean uninstall of TI 2016 using the Acronis tool, then a reinstall, defined the backup again, but it had the same exact bad result. So I figured maybe TI 2016 was having problems and I had a copy of TI 2019 to use. So I did a clean uninstall again of TI 2016, then installed TI 2019, with the exact same result, and to the same path. At this point I no longer had a old backup to recreate the definition with. That's when I first posted on here. Macrium was pointed to the exact same location and had no problem today.
Steve, I'm aware of the "no perpetual license" deal. Not that I like it though.
My suggestion would be to establish a new folder in the backup path and create a new backup task using the new folder as the destination location for the backup files.
Even though you have done uninstalls and re-installs, there remains an issue with the task configuration that is producing the error. Starting anew should fix the issue.
Well, I tried a different folder, but no dice. I got this:
1/23/2022 08:50:46:546 AM -06:00 15040 E01E50023: Error 0x1e50023: Please close the application that may currently use the file: \\REPLICA\Acronis Backups\Admirals Room\ADMIRALS-PC_full_b1_s1_v11.tib
The folder name this time didn't have an apostrophe. So then i tried another external hard drive at the same location, and it's working. Doesn't make sense. But my plan will be to Add Existing Backup from the newly created file once it finishes, and then change the options to point to the location I'd like it to be and try again. We'll see what happens.
Joel, I hadn't picked up on the apostrophe in your network path which Enchantech looks to have noticed, but any special characters in the path can be an issue and should be avoided where possible!
Joel, please look at the post I just added to this forum...
Well, I did the Add Existing Backup from the different EHD on the networked server, simply changed the destination to the original folder I always had, and it's now working. Go figure.
Well, I'm back to this issue again. This time on a brand new PC with a new OS, running Windows 10 21H1. I can't back up to the same location that about 45 other machines are successfully backing up to multiple times a week. So I backed up to a different external hard drive on the same server, no problem. Then I attempted to add that existing backup to Acronis, then reconfigured it to the problem location, and as opposed to before, it gets the same write error again. The previous machine where I did this is fine and continues to run. So now i don't have a workaround. Any other ideas?
Also, I don't see any reference to v11.tib in this. The MVP log viewer only shows this as the problem:
1/30/2022 11:52:50:483 AM -06:00 9272 I01E50023: Error 0x1e50023: Reattempting the operation. Error: Please close the application that may currently use the file: \\replica\Acronis Backups\Kadi Burleson\KBURLESON-PC_full_b1_s1_v1.tib.
So it's as if it thinks something is holding the resource. But nothing is as far as I know, and that's not fixed with a reboot.
Joel, have you installed the latest ATI 2019 release (1/27/22)? The release notes claim to fix some write errors.
Well, I think this was the deal. I couldn't even write to that area with Windows Explorer. That drive has 2 shares:
\\server\D\acronis backups
and
\\server\acronis backups
and while both of the shares allow full access, the D share works fine. Without D it doesn't, and just using the Acronis Backups share it won't work.
Your example is typical of SMB share permissions. Your full path in this case is and must include the D. If you wish to change that you would need to create a new share at \\server\ This is expected behavior.