Backup, Folders on Synology DS216Play - More than I expected
I am at at loss why I select a small (3mb) folder on the Synology DS216Play and Acronis backs up over 1TB (which I stopped after goodness know how many hours) to a USB disk in a 2 bay dock.
Please comment.
Thank you for your help.
I can't explain why, but the next day the 3mb file was backed up.
So, I went back to my original plan to backup a NAS share to a USB disk.
Attached is a screenshot of the share I want to backup. Note: I have to enter \\192.168.1.11 in order for Acronis to accept my credentials, because DS216PLAY will not accept my credentials (even though the Synology Assistant for logging onto the NAS will).
What I failed to see was the front screen (attachment 2) which shows that it going to backup all Shares.
Finally the log file (attached) shows that it was going backup up all the Shares.
So why is it backing up all Shares when I only want 1 Share (first attachment)?
allsam,
Looking at attachement "Files to Backup.png" I note that in the directory structure below the expanded folders under your IP address there appears another branch entitled DS216PLAY. If you expand that branch do you see the same folders there as is seen with the IP address expanded?
If yes to the above question, what happens if you select the same Windows 10 folder for backup when creating a new task to that location? Will the backup run? Does it backup only the Windows 10 folder?
Your log file clearly shows the task as originally created included all of the folders under the IP address. I can only suspect that when you first created the task only your IP address was selected as the source location for data to backup rather than that of just the Windows 10 folder. Possibly when you discovered the backup not performing as you expected and you investigated unknowingly you ended up having the only Windows 10 folder selected which is now why the backujp is performing as you expected in the first place. A bit unlikely yes but I have no other explanation as to why you have had this experience based on what information we have here.
allsam,
Looking at attachement "Files to Backup.png" I note that in the directory structure below the expanded folders under your IP address there appears another branch entitled DS216PLAY. If you expand that branch do you see the same folders there as is seen with the IP address expanded?
If yes to the above question, what happens if you select the same Windows 10 folder for backup when creating a new task to that location? Will the backup run? Does it backup only the Windows 10 folder?
Your log file clearly shows the task as originally created included all of the folders under the IP address. I can only suspect that when you first created the task only your IP address was selected as the source location for data to backup rather than that of just the Windows 10 folder. Possibly when you discovered the backup not performing as you expected and you investigated unknowingly you ended up having the only Windows 10 folder selected which is now why the backujp is performing as you expected in the first place. A bit unlikely yes but I have no other explanation as to why you have had this experience based on what information we have here.
Looking at attachement "Files to Backup.png" I note that in the directory structure below the expanded folders under your IP address there appears another branch entitled DS216PLAY. If you expand that branch do you see the same folders there as is seen with the IP address expanded?
As per my last reply 'Note: I have to enter \\192.168.1.11 in order for Acronis to automatically log onto the NAS, because DS216PLAY will not accept my credentials (even though the Synology Assistant for logging onto the NAS will).'
To recap:
1) Enter \\192.168.1.11 in the Backup Source top bar and press Enter (windows 10). I am automatically logged in to the NAS
2) Click on DS216PLAY and it shows \\DS216PLAY in the Backup Source top bar. Press Enter. It asks me for User name and Password. I paste in the password and click Test Connection and get 'Connection failed' in red. I have done this many times.
3) In Windows Explorer, I can enter \\DS216PLAY and I can see all the Shares with no asking for Credentials.
I'll try setting up the Backup task again from scratch.
Thank you.
Alisam, as Bob pointed out in his updates above, the log file clearly shows you are selecting a lot more than just the Windows 10 folder / share on your NAS.
id=26; level=2; module=11; code=1008; date/time=12/12/2016 07:18:05
message=Create Backup Archive
From:
\\192.168.1.11\File History\
\\192.168.1.11\home\
\\192.168.1.11\homes\
\\192.168.1.11\Media\
\\192.168.1.11\photo\
\\192.168.1.11\Time Machine\
\\192.168.1.11\video\
\\192.168.1.11\Video - Original\
\\192.168.1.11\Windows 10\
\\192.168.1.11\Windows 10\
\\192.168.1.11\Windows 10\
\\192.168.1.11\Windows 10\
\\192.168.1.11\Windows 10\
\\192.168.1.11\Windows 10\Sovereign\
\\192.168.1.11\Windows 10\
To file: Weekly - NAS W - Windows 10 - Thursday 6-30pm_full_b1_s1_v1.tib
Compression: Normal
Exclude: System files
I suspect that the issues with connecting to DS216PLAY versus 192.168.1.11 is a matter of your stored credentials held by Windows, especially as you say that are accessing the former via Windows Explorer.
Please see KB document: 58004: Acronis True Image 2016: Troubleshooting Issues Related to NAS Credentials which will show you how to clear the stored credentials used by Acronis for your NAS.
As noted when attempting to access the NAS via \\DS216PLAY\ you are prompted for credentials. You provide the proper credentials but the connection test fails. What occurs if you choose to not enter any credentials leaving the username and password blank? Will the application proceed with the backup or does it abort complaining that credentials test failed or similar error message?
It is possible that the application is displaying the credentials prompt window in error thinking that the share authentication has not been performed. I have witnessed similar behavior on my systems and have found that to get around the credentials error it is best to approach the situation in the following manner.
1. From a restart of your computer, note I say restart not start as in computer being in shutdown or asleep, without accessing your NAS shares via Windows File Explorer or other means such as a web browser, open the True Image application and setup a backup task to an NAS share.
2. Browse to the desired folder using the name\folder method rather than the IP address method. At some point during that process the applicaiton should ask for credentials. The credentials necessary are that of the credentials that are in place for the NAS and not your Windows account credentials unless both of those are the same.
3. When this credentials prompt window displays enter the appropriate username and password and click Test Connection. I have found that this method works and credentials would be accepted.
If you begin with your computer being started from shutdown, sleep, or already running and you have at any point accessed your NAS shares via web browser or File Explorer and you configure a backup task to your NAS share proceed as follows:
1. When selecting the NAS share location if credentials prompt screen is displayed close that screen and continue with the configuration. In most cases the backup configuration will continue and run once selecting Backup now.
2. If the credentials prompt reappears during task configuration or after selecting Backup now do not enter credentials, instead close the credentials prompt window and attempt the continuation of task configuration or press the Backup now button again. This sometimes works and sometimes does not. If this step fails then it is necessary to clear the Connection SMB registry key for the NAS device as described in the KB article linked below:
https://kb.acronis.com/content/58004
I believe that there is a bug in the network credentials aspect of the application in that it asks for credentials when in fact they are not needed. This would be true if in fact you have already gained access to the NAS share via another method such as web browser or File Explorer. Reason being that you have already authenticated the current Windows sessions connection to the NAS share and since Windows only allows one authenticated connection during any one session any attempt by the user to authenticate another connection fails because it is not allowed. So I believe that the credentials connection failed message displayed in the True Image application as discussed here is in fact triggered by what is not allowed by Windows.