So I jumped into a remote support session with Macrium and while we were troubleshooting an idea popped into my head to try creating a new user on the NAS.
So far that seems to be working.

I'm still truly baffled as the other account I was using had no changes made to it prior to all the scheduled backups failing.

However, if this solution sticks, I don't really have a problem having an account on my NAS strictly for backups.

Glad it’s resolved, although I know the frustration of fixing a problem without realizing why the problem is fixed. But a dedicated NAS user isn’t a bad idea. As a security precaution, I recommend creating a dedicated SHARE for your Reflect backups, separate from all other data, and then granting access to two user accounts. One has read-only access and one has read/write. The read/write credentials to go Reflect, and the read-only credentials are used whenever you want to access the share within Windows for the purpose of restoring backups or extracting data from them.

That's a great idea! I'll set that up to ensure everything runs smoothly in the event of having to restore from a backup. Thanks for the suggestion!

Glad you like it!  It’s a nice additional safeguard against malware. If network connections within Windows Explorer practically always use read-only credentials, then malware wouldn’t be able to piggyback on that connection to perpetrate destruction of your backups. The chances of the malware looking for the read/write credential info stored by Reflect are much slimmer than malware just taking advantage of whatever network connections are already open.

So a couple days go by and the same thing starts happening again.
Now I'm really at a loss.

Don't really have anything new to add, just thought I would update the thread in case anyone else can chime in.

Just enabled these in case they have any affect.
They weren't enabled when it ran on this account before and it worked but the logs do say that the user I created is accessing the folder through SMB3.



It's almost like Macrium piggy backs off a connection if I have accessed the NAS in anyway.
I made sure to restart the computer and schedule the backup to run after a couple minutes and it succeeded.
We'll see if that sticks or not.

Still no idea what's going on with your system given the parameters of this behavior, but Reflect relies on Windows for file share connections, Windows uses SMB, and SMB 3.0 specifically has been available since Windows 8 / Server 2012.  If that wasn't enabled before, then I'm not sure how it worked at all beforehand unless the default state is to allow anything unless you specifically choose to set per-protocol policies.

Yep still failing.
I'm about ready to just write to the local disk and let Synology Drive Sync the files.

Scheduled backup failed same as usual, but ran manually from the scheduled backups tab, it worked.
Another anomaly I'm noticing is that the scheduled backup used a different user (the one I was originally using but removed from Macrium)
When I manually ran it, it used the other user.

I'm still going at it trying to figure this out. And I'm leaning towards this having something to do with the Windows Credentials Manager.

Still a bit confused on how it works, but from what I understand, you can't have two different connections/credentials to the same network location in order for Macrium to work correctly?

Windows is using the UNC name for the network location in file explorer but I'm also using the IP for network folders (it was having issues using the UNC path)


So basically, UNC path is used if accessing the network through file explorer (unless I access the drives directly where it uses the IP address). I need this functionality to read/write files to the NAS.
Is there any way to configure this so that Macrium will be able to connect? Do I need to utilize this section in Macrium?:


Still don't understand how it was able to work before upgrading to v8, my mind is spinning.

It’s true that Windows can’t use multiple credentials to connect to the same remote system at the same time within the same user context. Using an IP in one area and a hostname in another does not sidestep this restriction, to my recollection. But scheduled backups don’t exist in the same user context as your Windows Explorer session, and it IS possible for two different Windows user session to have connections open to the same network target using separate credentials for that target at the same time, because User A’s network connection would not be available for use by User B, and vice versa.