Move function - unable to access NAS - authentication problems

Not sure what is going on; it may be that Acronis can only access one network share at a time whereas the operating you are tyring requires access to two.

As a work around, you could remove the existing backup task (but make sure that you only remove the task, not the backup files). Then use your preferred file manager to move the backup files from the old NAS to the new NAS. You may need to temporarily disable Active Protection to do this. Then add the backup task to ATI (you will need to reconfigure them once you have added them).

Ian

My explanation of the problem was a bit confusing - sorry.

I haven't started anything on the new NAS yet. Right now my Acronis 2019 backup is all on my Western Digital EX4100 NAS.

Can't get past the “connect” to WD NAS, for the move function to even start. – “connection failed”.

I'm wary of removing the backup task. Afraid I might loose access to all my backups.

Thanks again

GJR, like Ian, I have never had the need to do this type of move.  I only have the one Synology NAS so would be difficult to try to test.

Are you existing backup tasks to the WD NAS still working correctly without giving any connection type error messages?

I would suggest considering taking a different approach rather than using the Move function.  Move works fine for local drives in my experience but it may have some issues with your two NAS scenario!

First, setup your Synology NAS as you want to use it for your backups, i.e. setup the folders you will be backing up to and once done, then copy all your current backup files (for the tasks shown in your ATI GUI) from the WD NAS to the Synology NAS.  This may take some time depending on the size of files / data involved and will test your network connectivity etc.

Once you have all the files present on the Synology NAS, then the next step is the one that you are wary of!  Removing the task settings for the WD target tasks from the ATI GUI.

First, make a backup of the C:\ProgramData\Acronis folder structure which will include the C:\ProgramData\Acronis\TrueImageHome\Scripts folder holding the configuration (.tib.tis) files for the task you are removing.  This would allow you to recover back to the starting point if that needed to be done!

1. Select your first backup task in the ATI GUI, click on the caret (v) to the right of the task name to reveal the options menu for that task.  Take the Delete option then on the next pop-up, select to just remove the task settings (not to delete everything!).
2. Note: make notes of the settings for the task or take screen images of each panel in the settings.
3. Use the 'Add existing file' option (found behind another caret (v) to the right of 'Add backup') and navigate to the new file location for the first task on your Synology NAS, establish the credentials for the NAS and select the most recent backup file to add.
4. The added task will have the name from the selected file, so rename this to remove the extra letters following the normal name, i.e. remove _full_ or _inc_ etc.
5. Next, click on the Reconfigure button which is shown in place of 'Back up now' and put back your settings for this task as noted above.
6. Once all the above is done, then the Activity and Recovery tabs for the task should show information for the added back task and you should be able to run that task.

Repeat the above steps for each further backup task being moved to the Synology.

Your original files will remain present on the WD NAS as belt & braces during the migration process.

Thank you for the detailed step-by-step. I like the back up of the acronis scripts etc. Haven't done this before.

Backups to current WD NAS working fine.

Before I do this, I would like to have the NAS connection working properly. Any idea why the backup is working fine - thus Acronis is accessing the NAS fine. But, if I try "test the connection", it gives me an error?

Also, I did find some posts that mentioned looking at Windows credentials. I did this & it all looks fine. I wonder if I should delete the windows credentials for the WD NAS, then try testing the connection again in Acronis.  I'm not a computer expert so I'm not 100% certain if/how the Windows credentials applies to a specific program like Acronis vs the entire computer (mapped network drives, etc).

Thanks again

Which NAS is giving the error when you test the connection?

The current one that has all the backups - WD Ex4100

You need to ensure that you only have the one open connection to the NAS, i.e. not be accessing it via Explorer at the same time due to limitations imposed by Microsoft in this area.

See KB 59051: Acronis True Image 2017: Connection to NAS fails with errors "Connection failed", "Failed to check credentials", "Cannot find files and folders".

Do you have more than one than one share on the NAS, and if so, do they need different credentials?  A single Windows user can use only one set of credentials to access a NAS so cannot access multiple shares that require different credentials.

I have 2 Synology DS218 drives.  I'm fairly certain I moved some ATI backups from the old NAS to the new NAS when I was first setting it up.  

Perhaps I misinterpreted what you said.  Did you say the backup to the old NAS is working fine, but the "Test connection" fails?  If so, are you doing the test from the working backup task or are you defining a new task?  If this is from a new task, is the SMB connection still open for the old task?  (As far as I know, the old and new task should be able to share the same SMB connection if they use the same credentials.  I think Windows allows that, but maybe ATI does not.) 

Executing "Get-SMBConnection"  from an elevated Powershell prompt will show the current SMB connections.

Another possibility:  The backup runs in the background under NT AUTHORITY\SYSTEM.  I believe the connection test runs under your own Windows userid (although I could be wrong about that).  I would expect the same stored credentials to be used, but maybe not.

Don't really know what gives with my access to my current WD NAS via ATI.

Was able to test a new backup on the new Synology NAS

The connections now seem to be ok.  I'm going to try what Steve S suggested re backup of ATI settings and then reconfigure on the new Synology.  Here goes.

I was able to move the backup to the new Synology NAS but forgot to change the backup settings to be same previous setup.  Did that and it says the connection is ok, but backup won't run.

Error pops up "Ensure the folder \\,.... is accessible." - which it is according to the "test connection". 

Hit "check for a solution" but smart error reporting came up with nothing.

So now it looks like a connection issue between ATI and Synology.  

Any thoughts?

GJR

Try reselecting the Destination location for the task again to ensure it is pointing at the correct target folder.

Good idea. But, didn't work.

It starts to run & all looks ok, then it is if times out, generating the connection issue error

Are you able to setup a new backup task to the new Synology NAS without any issues?

I tested this before doing the move. Just tested it again & had no problems with a new backup.

I would suggest removing the problem task settings from the GUI again, then using Add existing backup again from the new NAS followed by using Reconfigure to set the task settngs again.

Redid the move of the backup as you suggested.

Looked ok - did a backup. 

2 Problems

It appears to have started an new backup stream - new name GJR_Main (D)_inc_b1_s10_v1.tib

Last back  to the old NAS was - GJR_Main (D)_inc_b9_s182_v1.tib

I tried to do a restore to test the backup. I generated errors saying it could not find some of the files in the backup stream. It was searching for them on the path to the old NAS drive. Seems like it isn't fully recognizing the move.

Again, your help is much appreciated. Looks like I'm close, but not yet 100% moved over.

GJR

Having any chain of incremental files with over 180 incremental files in the chain is increasing the risks inherent in this type of backup, i.e. that all files are dependent on all previous files in the chain, so if a single file is corrupted then the chain breaks at that point.

The references to old files stored on the original NAS suggests that there is still information for the task(s) that created those files stored in the internal Acronis database, which in turn suggests that the original task was not removed (settings only) from the ATI GUI before adding in the new task using the same name!

The ways of approaching this are to do a bulk rename of the files on the new NAS then add in the most recent of those files to create a new unique task in the GUI, with associated stored data in the database for the associated files for that task -- or force a rebuild of the database providing that you have actually removed the settings for the original task from the GUI?

To do the latter, see KB 60915: Acronis True Image: repairing program settings - which has the steps needed.

No answer for why your task created inc_b1_s10 instead of inc_b1_s183 you were expecting other than it is probably associated with the above comments.

So, I think I've got it as best as I can.

Did a rebuild  of the database. Then deleted the backup from the list. When I added a back, it defaulted this time to my most recent backup chain. Ran the incremental backup & it worked.

Can't thank you enough Steve. Thanks for helping a novice sort a messy little problem.

GRJ

Good to read that things are now looking good, well done for sticking with this issue & thanks for the feedback.