Disk roaming mechansim introduction for QSM4 #
When performing disk roaming from NAS A to NAS B, please note that as long as hard drives are inserted in slots 1 to 4, each NAS will have its own database configuration (dbconfig). The dbconfig on NAS A will be called to as config1, and the dbconfig on NAS B will be called to as config2.
Scenario 1: Direct Disk Roaming #
- If disk roaming is performed directly, NAS B’s machine will maintain config2. Failure to import config1 will result in shares created in NAS A appearing as missing in the UI. Users must click on “recreate” in the UI to restore it. Please note that all share-related configurations, such as permissions and share hosts, need to be set up again.
Scenario 2: Exporting and Importing Configuration #
- First, export the system configuration in NAS A, then perform disk roaming from A to B. Next, import config1 from NAS A into NAS B. At this point, config1 will overwrite config2.
- Consequently, the shares originally present on NAS B will appear as missing in the interface. Users must click on “recreate” in the UI to restore them.
- Again, please note that all share-related configurations need to be set up again, including permissions and share hosts.
