Preferred procedure for seamless migration of all data to new share

Currently reading
Preferred procedure for seamless migration of all data to new share

37
1
NAS
DSM 1621+
Operating system
  1. Linux
Mobile operating system
  1. Android
I operate a DiskStation device, on which I have a share that functions adequately, except that it was originally provisioned with a weak encryption key, due to lack of understanding that the passphrase entered on initial provisioning of a share is the one used directly as the master encryption key, rather than as a wrapper to encrypt the master key.

Therefore, I wish to migrate the share to a new one using a stronger key. Otherwise, I wish for the new share to behave identically to the current, without any breakage of user applications or use cases. I would understand that I may create a new share with a temporary name, migrate the data, change the names such that the new share will carry the name previously held by the original, and finally, I may delete the old share.

However, I would like to understand the preferred method, based on a sound basis in the design of DSM, for ensuring that all metadata is properly transferred, including ACLs, and any other that may affect functionality.
 
for ensuring that all metadata is properly transferred, including ACLs, and any other that may affect functionality.
If I may suggest using Hyper Backup for this case.

Create a new, temp folder, and then a HB (single file) task. This will transfer the data and maintain the folder structure as it is without the use of HB's proprietary format. Also, this process (if checked) will maintain all the metadata needed.

Screenshot 2023-08-24 at 20.09.18.png
 
If I may suggest using Hyper Backup for this case.

If I were to copy files directly to a new share, then the process would be most natural if the amount of free space on the volume exceeded the size of the old share. The restriction may be relaxed, by copying the share in batches, separating major components of the file tree.

If I were to use HyperBackup, then either I would need external media to store the backup, or I would use some internal storage. May I use as an internal target location, for a backup, any directory within an existing share, or only an entire share? May I restore a backup to a directory within an existing share, or only to an entire share?

It would seem that for using HyperBackup, I would require additional capacity to store the intermediary targets, that is, the backup, compared to the case of directly copying files, unless I were willing to risk removing the original source filles before restoring the backup to the new share.

Which metadata would be lost if I were simply to copy a file tree using the builtin file manager for DSM, FileStation?
 
May I use as an internal target location, for a backup, any directory within an existing share, or only an entire share?
Target can only be a new root share.

May I restore a backup to a directory within an existing share, or only to an entire share?
by default, restore will go to the original (source) location or any other that you choose. So it will be up to you.

Which metadata would be lost if I were simply to copy a file tree using the builtin file manager for DSM, FileStation?
All of them, apart from ofc size, type and those that define the file.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Old thread notice: There have been no replies in this thread for quite some time. The last reply was on .
The content in this thread may no longer be relevant. It might be better to open a new thread instead.

Similar threads

  • Question
While I don't know your competency... there is a good introductory NAS setup series on YouTube nu...
Replies
8
Views
14,937

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Back
Top