TI 2014 Won't Back Up To Samba Share Now - Was Working Fine
Hi folks. :) Hoping someone can help me.
I am doing daily incremental backups of one system that runs Windows XP SP3 using TI 2014. The destination is a Samba share on a Ubuntu 13.10 Linux system on the network.
Everything was working perfectly up until 12/12/2013 (4 days ago) when it just stopped working completely.
I was then only getting error messages from TI like "Failed to prepare datastream. Check whether the source and target partitions exist." or "attempt to open the backup location failed" or "error occurred while creating the file".
Also TI was requesting my windows credentials over and over and the valid login details for the Samba share or my windows login info did not work.
Since I did not change anything intentionally, I'm guessing a security patch for either Ubuntu or Windows or an update to TI 2014 caused this.
I have tried reinstalling TI 2014 but I still cannot get the 'credentials' to work from within TI, so no backups can occur.
The strange thing that makes me think this is a TI problem is that I can access the Samba share just fine from the Windows My Network Places screen.
- Log in to post comments
One thing yiou might try would be to look at the log od the last good backup and note the exact path TI used.
Then look at the failed task log and see if the paths are different.
You might create a new backup task as a test pointing the the samba as the target and backup just one file or folder.
Then look at the log for the new backlup and compare the samba paths.
Something changes. The question is to find out what.
If the test works, you may have just to stop using the old tast and start over with a new task which works.
Any new task should point to a new and empty sub-folder on the samba.
- Log in to post comments
Hi GroverH, thanks for trying to help me, I appreciate it!
I managed to access the logs folder within one of the backups and found that the path is the same as the path that is now unsuccessful.
Working log and Not working log are attached. As you can see, the not working log just repeats the same error a few times.
I have removed and re-created the task before to no avail. However, I will do it as you suggest with backing up a single file to a brand new folder and report back.
- Log in to post comments
I tried backing up a single file and it still cannot access the share. Why would TI have a problem accessing a share that Windows (which TI is running on) has no problem accessing? :) Why even bother with separate credentials, just use the existing access in Windows. Mind boggling. Any help appreciated.
- Log in to post comments
fortitude,
Hopefully, someone else can help you. I am not familiar with your storage so can offer no more assistance. Until you can get the single file test to complete, the other will have to wait.
There is a good chance that the path tothe samba needs a modification or a permissions issue.
You may need to contact Acronis for help rather than volunteers on the forum.
- Log in to post comments
I found a KB article: http://kb.acronis.com/content/10957
"10957: Acronis Backup & Recovery 10 Keeps Asking for Credentials when Trying to Save an Archive to a Linux Share or on a Linux-Based NAS "
Seems to be the same as my issue. It does state that it is a problem with TI. Of course they are referring to an older version, but perhaps there was a regression somewhere.
I'll see if I can figure out how to make "domain-based authentication" work.
- Log in to post comments
Has anything changed on the destination PC?
Have you attempted to run any disk checking utilities on both the Linux and your Windows machine?
If you have a spare drive or partition free, does a locally attached drive or partition task work?
- Log in to post comments
Thank you Colin and Grover. If anyone refers to this thread in the future, I did manage to solve the problem.
On the Windows XP box:
From a command prompt, control keymgr.dll
I removed all old login info.
Start Computer Browser and Server services (they were set to automatic but not actually started).
In TI I removed the old task, "remove from the list".
I then browsed for old backups. I looked under "my network places" then "entire network", then "microsoft windows network".
I then navigated to the workgroup rather than Mshome. My share was showing there, the main difference was that it is under the hostname rather than the netbios name specified in the smb.conf on the Linux box as it has been from Mshome.
So, the old path that all of a sudden failed to work was:
\\netbios name\folder\
The new path that does work is something like:
\\hostname\folder\
Either way worked from within windows explorer, but only one way works for TI.
I then re-created the backup task first by adding the latest full backup to the list of backups.
I can now supply my credentials and access the share from within TI and make backups, as it should be.
There was a lot of other fiddling around but I hope I've boiled it down to the important stuff.
- Log in to post comments
Good for you on both counts.
YOU solved the problem on your own and likewise posted for others the fix info.
Congratulations.
- Log in to post comments