• Art Vandelay
    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.
  • Steve Putnam
    See the knowledge base article in the link below. Yes you can change the drive letter, and as long as the folder structure remains the same it will not backup everything again.
  • David Gugick
    The new format has many advantages. The determining factor will be if you need the new features and are using a supported cloud for synthetic full backups. You are, with B2. But if you prefer the incremental-forever, version-based retention with the legacy format, then you can use it.

    Those directions that Steve posted only apply to the legacy backup format. I am waiting on direction from the team about how (or if) this is possible with the new backup format since there is more involved, like the deduplication database.
  • Art Vandelay
    Thanks, please let me know what you find out about dealing with the drive letter change. Since directory structure and date stamps will be retained, hopefully we can get this to work with the new format without having to upload everything again.
  • David Gugick
    If you are not moving computers and are just moving data, then the new backup format supports deduplication, so it should see those bytes already in storage and avoid uploading them again. You're in B2 and will benefit from synthetic full backups when the next full backup runs. I would recommend you open a support case for best assistance.
  • Art Vandelay
    Sounds good, will verify with support. Thanks!
  • Alexander Negrash
    Here is an article on how to continue backup on another computer with the new backup format https://help.msp360.com/cloudberry-backup/miscellaneous/continue-backup
  • Art Vandelay
    Thanks, that looks basically the same as the link that was previously posted which apparently only applies to "old format" backups.

    We contacted MSP360 Support yesterday as David Gugick had suggested and they quickly responded. They conducted a test, backing up some files then moving them to another drive letter, editing the backup plan with the new drive letter, and continuing the backup. The pre-existing files were not uploaded again. This confirmed the de-duplication feature of the software where data is backed up at the block level and previously-seen blocks are not uploaded again.

    Thanks to all who responded here, and kudos to the MSP360 support team for a very fast response and actually testing the feature to verify that it works.
  • David Gugick
    That article has been updated by the team to include references to the new backup format.
Add a Comment