- 37
- 1
- NAS
- DSM 1621+
- Operating system
- Linux
- Mobile operating system
- 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.
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.