We are using MSP360 backup to Backblaze B2 storage on our Windows 2016 server. This is file-based backup using the new backup format with monthly synthetic full backups and incrementals in between. We're using the new format since that was the default, but looking over the forum it seems that the old format is preferable for file-based backups. (Seems to be working OK though aside from lack of search capability. Not sure if there's sufficient reason to change over to the old format, meaning starting all over again.)

Anyhow, in the near future we are going to be adding additional storage to our Windows file server, moving the shared file directory hierarchy to the new drive array. In other words, D:\SHARED will be changing to E:\SHARED, with the backup plan changed for the new location. Plan is to retain datestamps on files and directories using robocopy with appropriate command line options.

The question is, will MSP360 treat the moved files as being new/changed and upload the entire large dataset all over again? Or will it recognize that it already has the files backed up and just continue to upload actual new and changed files moving forward?

Alternately, if a symbolic link D:\SHARED is put in place pointing to E:\SHARED with the backup plan unchanged, will MSP360 follow the link and see that files as they were before the move or will it just backup the symbolic link itself and ignore the rest?

We're just trying to avoid having terabytes of data that are already backed up transferred to Backblaze B2 again if possible.