Recommended Configurations for 6.x Series Storage Systems for Taking Over Data from Other Huawei Storage Systems When the Host Uses the OS Native Multipathing Software
When data is migrated from other Huawei storage systems (including Dorado V3, OceanStor V3, and OceanStor V5) to 6.x series storage systems, the old storage system and 6.x series storage systems will connect to the host concurrently. You must select a proper migration and configuration method based on the configurations of the old storage and host to ensure proper running. The following provides recommended configurations.
1. Configuration method for 6.x series storage systems working in load balancing mode |
||||||||
Host OS |
Current Configuration on the Customer's Live Network |
Configuration Before Migration (Both the Old Storage and 6.x Storage Exist) |
Configuration After Migration (Old Storage Offline) |
|||||
Old Storage Scenario |
Old Storage Configuration |
Current Host Configuration |
Old Storage Configuration |
6.x Storage Configuration |
Host Configuration |
6.x Storage Configuration |
Host Configuration |
|
Linux |
Non-HyperMetro |
ALUA |
ALUA |
Unchanged |
Set the host access mode to asymmetric. |
Unchanged |
Change the host access mode to load balancing. Note 1 |
Change the host configuration to AA. Note 1 |
Change the initiator mode to not using ALUA. Note 1 |
Use the default host access mode, that is, load balancing. |
Change the host configuration to AA. Note 1 |
Unchanged |
Unchanged |
||||
ALUA not used |
AA |
Unchanged |
Use the default host access mode, that is, load balancing. |
Unchanged |
Unchanged |
Unchanged |
||
HyperMetro |
ALUA |
ALUA |
Unchanged |
Set the host access mode to asymmetric. |
Unchanged |
Change the host access mode to load balancing. |
Change the host configuration to AA. |
|
Note 1: If LUNs have been mapped to the host, you must restart the host for the configuration to take effect after changing the initiator mode or host access mode on the storage systems. It is recommended that you restart the host after you have finished the configurations on both the storage systems and host. |
||||||||
2. Configuration method for 6.x series storage systems working in asymmetric mode |
||||||||
Host OS |
Current Configuration on the Customer's Live Network |
Configuration Before Migration (Both the Old Storage and 6.x Storage Exist) |
Configuration After Migration (Old Storage Offline) |
|||||
Old Storage Scenario |
Old Storage Configuration |
Current Host Configuration |
Old Storage Configuration |
6.x Storage Configuration |
Host Configuration |
6.x Storage Configuration |
Host Configuration |
|
Linux |
Non-HyperMetro |
ALUA |
ALUA |
Unchanged |
Set the host access mode to asymmetric. |
Unchanged |
Unchanged |
Unchanged |
ALUA not used |
AA |
Change the initiator mode to ALUA. Note 1 |
Set the host access mode to asymmetric. |
Change the host configuration to ALUA. Note 1 |
Unchanged |
Unchanged |
||
Unchanged |
Use the default host access mode, that is, load balancing. |
Unchanged |
Change the host access mode to asymmetric. Note 1 |
Change the host access mode to asymmetric. Note 1 |
||||
HyperMetro |
ALUA |
ALUA |
Unchanged |
Set the host access mode to asymmetric. |
Unchanged |
Unchanged |
Unchanged |
|
Note 1: If LUNs have been mapped to the host, you must restart the host for the configuration to take effect after changing the initiator mode or host access mode on the storage systems. It is recommended that you restart the host after you have finished the configurations on both the storage systems and host. |
||||||||