Backup to NAS failing
I've had a series of ATI problems lately on a laptop running ATI 2018 build 10410 under Win10 ver 1709. Yesterday I did a clean reinstall of ATI 2018 10410 everything should be pretty clean but a scheduled backup to a NAS is failing with
12/23/2017 2:10:45 PM: Writing incremental version to file: Entire PC (PUGET-128498)_inc_b1_s2_v1.tib
12/23/2017 2:10:45 PM: Error 0x1e50023: Please close the application that may currently use the file: \\MYBOOKLIVE2\Private\Puget-128498\Backups\Entire PC (PUGET-128498)_inc_b1_s2_v1.tib
12/23/2017 2:11:15 PM: Error 0x1e50023: Reattempting the operation. Error: Please close the application that may currently use the file: \\MYBOOKLIVE2\Private\Puget-128498\Backups\Entire PC (PUGET-128498)_inc_b1_s2_v1.tib.
ATI retries a number of times with the same results.
The problem does not occur if there is already an existing SMB connection to the share. If I use File Explorer to access the share and do not terminate that SMB connection then ATI has no trouble writing the backup. This sort of sounds like a credentials problem, but ATI successfully validated the credentials when I entered them. I used the same network credentials with both ATI and File Explorer I don't think it can be an access authorization problem.
I don't think I had this problem prior to build 10410 and have not yet tried 10640.
This seems to be just the opposite of some NAS problems I've seen described on the forum.
I'm about to try this on another computer and, if it fails, upgrade to 10640.
Patrick,
In the application GUI select this backup and once selected click on the Destination and navigate to the NAS share where the backup is located. At some point in the path to the network share you should get a prompt for credentials. Enter the appropriate credentials then click Test connection. This should establish the connection to the network share anew and the task should now function normally.
The backup task did have a pre/post command but removing the command changed nothing.
I don't get a prompt when navigating to the share in the GUI but I'm pretty sure that's because I've already given Acronis the credentials and it has saved them away in the registry.
Now for the bewildering results of my latest test on a little used test PC. As with my other computers, this is running Win10 1709 and ATI 2018 build 10410. At some time in the past I had had a backup task pointing to the NAS in question but that task has been deleted long ago. So no defined task since probably ATI 2017 but credentials in ATI registry records.
- I defined a backup task with the NAS as target and it ran with no problem. (That is, it started. It would have taken many hours so I stopped it and deleted the task.)
- I uninstalled ATI. I thought the uninstall process was supposed to delete everything but there were still a lot of ATI registry records. I don't know about the Acronis ProgData stuff; I forgot to check.
- I reinstalled ATI 2018 build 10410. The old backup tasks were still there so this wasn't exactly a "clean install".
- I redefined the backup task pointing to the NAS. Now it fails with the same error as on the laptop.
- I installed build 20460 but it had the same failure.
So either something in the uninstall/reinstall has messed something up or maybe the cancelling of the backup task messed something up.
By the way, I did an uninstall/reinstall on the laptop but not until after these symptoms appeared.
Patrick,
Open an admin PowerShell instance and type get-smbmapping
If you this command outputs the share path to the backup location then type remove-smbmapping
You will be prompted to choose and confirm the action, do so and press Enter.
In this instance the connection now being closed should allow for the backup task to run.
Just to confuse the issue, today I've got the laptop backup working. I deleted the old backup definition and re-added it. But this time when specifying the destination I specified path in the "Back up to:" field rather than expanding the Network list in the ATI Explorer (or whatever it's called). I'll try this on my test PC is a few minutes. And if that works I'll add my pre/post command stuff back in the definitions.
By the way, nothing showed in the get-smbmapping display except for a public share on another NAS - probably because I don't have my backup share mapped to anything.
The smbmapping is not like drive mapping, it is connection specific.
So what did you enter in the Back up to field (address)? Did you use device (host) name or IP Address?
I used the device's host name. It also worked on my test PC. I had to delete the backup definition, not just change the destination, but once I did that it worked.
Sorry about my confusion with get-smbmapping . The only SMB connection I've on my "primary" PC is a mapped public share. The display showed mapped drive in the "local path" field.
Status Local Path Remote Path
------ ---------- -----------
OK Z: \\MYBOOKLIVE\Public
As I said before, the SMB connection used by ATI didn't show, and the above display showed no mention of user. Does the command display only SMB connections for the user issuing the command? If so, is there a way to show all active SMB connections?
get-smbmapping shows smb connections by path. This includes all connections on the subnet where run
get-smbconnection shows smb connections by instance This includes all connections on the subnet by share name, username, Credential, Dialect (highest negotiated protocol standard), and number of open shares.
I have no idea what went wrong for your connections here but creating the tasks again anew fixing the problem indicates that the tasks were corrupted presumably because of the IP address. Glad you got it working!