Salta al contenuto principale

TI2014 backup to NAS now getting "unable to access data stream" during consolidation

Thread needs solution

Hi,

I am receiving an error on backup that has only recently begun to pop up.

The errors state that the data stream cannot be opened during consolidation due to another program also accessing the files.

The file is writing and appears ok on the target share of the NAS, however the Post-backup commands are not running due to the error.

 

My setup:

I backup my desktop PC to my Synology NAS.

I have windows 10 with latest updates and TI2014 with latest updates.

I updated the synology software on my NAS and now I am receiving the error which is causing the backup to fail.

I use as specific account credentials to login to a share when doing the backup each day (PC turns on and backs up to NAS using the credentials which are not my normal windows login).

My backup login on my nas (call it "Acronis") does not have access to other shares, and my normal windows account login to other NAS shares does not have any access to the backup share. Is this likely to be an issue?

 

WHat I have tried to correct the issue:

I have recreated the backup task and that did not fix the issue.

I will also recreate the share again and reset the permissions but I don't think this is at fault.

 

Hopefully someone can help identify what is going on.

 

PS: I am still using TI 2014 specifically because I can set credentials for share login at backup time. THis allows me to have my backups in a write protected share during normal periods of computer activity. TI2016 was not so great with this and im not sure about TI2017.

 

 

 

 

 

0 Users found this helpful

What messages are shown in the logs for the backup task when this situation is encountered - can you post a copy of the logs?

Your Synology NAS setup sounds very similar to how I use my own Synology NAS except that I am using ATIH 2017 on my Windows 7 & 10 systems and I haven't yet upgraded 10 to the latest Creators Update.  The NAS was updated to the latest DSM version automatically in the last couple of days with no sign of any issues with my backups.

The only computer running ATIH 2014 to the Synology NAS is running XP and that too is showing no issues, which could suggest that the issue may be related to the Creators Update on Windows 10 in conjunction with the NAS and the 2014 version.

Officially, only 2015 and above are supported for use with Windows 10 but we know that older versions can / do still run though may hit problems with the new 'God Mode' desktop folder introduced with the Creators Update.

Hi Steve,

 

thanks for the feedback - it's very helpful. I will post logs if my current backup run fails again. I decided to eliminate some potential issues after reading posts elsewhere by doing the following:

1. complete removal and re-install of Acronis - in case the creators update messed with something.

2. Created a new share on my NAS and also tidied up some of the permission arrangements (I had some user group assigned permissions as well as user level.... so I removed all of the group assigned ones and just set individually for each user account).

3. created a new backup task from scratch.

 

Is there a log file somewhere with all of the info people post here? THe log in the UI seems much less informative.

 

One problem I am having that you may also be able to help with is that I used to have my desktop PC turn off my NAS after the backup was done. I used plink.exe to send an ssh command for "poweroff" however the newer versions of DSM do not allow root access by default. YOu have to use "sudo -i" in an ssh session to use root level commands.... and I don't know how to enable that via plink for a command line action.

The commands I have been using are:

C:\SSH_stuff\plink 192.168.1.2 -l root -pw XXXXXX shutdown -h now

echo n | C:\SSH_stuff\plink.exe -P 22 -ssh -pw XXXXX root@192.168.1.2 "shutdown -h now"

Using the -t option gets around TTL errors if I use sudo in the command line but I cant get it to acept a password from there.

eg:
echo n | C:\SSH_stuff\plink.exe -P 22 -t -ssh -pw XXXXX admin@192.168.1.2 "sudo -i" "shutdown -h now" 

 not sure how to enter a pw for sudo...

 

Ok after a reinstall of TI2014 and recreating the backup schedule it appears to work.

 

What I am still stuck with and may need to contact Synology about is the poweroff script I need :)

Glad to hear that the reinstall solved the immediate problem.

Sorry with regard to the Synology power off script - I do not use this with mine, just leave it to go into energy saving mode and be available 24x7 as needed.