Migrate data on the system

In E0780 and later versions, the management platform uses the NingOS operating system. To upgrade

the management platform to a version that uses the NingOS operating system, perform this task to migrate data to the management platform that uses the NingOS operating system. After data migration, the management platform that uses the NingOS operating system will connect to all the hosts managed by the source management platform. However, the new features in the management platform that uses the NingOS operating system are not available on those hosts. After data migration, the source management platform is unavailable.

Restrictions and guidelines

• Before data migration, verify the following information:

○ No host pool, cluster, host, or VM data exists on the management platform that uses the NingOS operating system.

○ The size of the database partition on the source management platform is not larger than the size of the database partition on the management platform that uses the NingOS operating system.

○ No frozen VMs exist on the source management platform.

○ The enabling status of stateful failover for the management platform using the NingOS operating system must be the same as that for the management platform using a non-NingOS operating system.

○ Hosts in the same cluster use the same software version and the shared file systems is used by only one cluster.

○ In the stateful failover scenario, enter the IP address of the primary node when you configure the management platform information.

○ When RBAC is disabled, use system administrator admin for data migration. When RBAC is enabled, use system administrator sysadmin for data migration and make sure RBAC is enabled for both NingOS and non-NingOS versions.

• When you migrate the management platform data, first identify whether the source vSwitch (management, storage, migration, and backup types) has port mirroring with the destination type as VMs enabled. If it is enabled, remove the configuration before proceeding with the management platform data migration.

• To avoid data synchronization failure, do not configure host firewalls on the management platform that uses the NingOS operating system before data migration.

• The backup policies on the source management platform are available on the NingOS management platform. However, you must manually add backup policy pools.

• After data migration, the backup history data of the original management platform in the database will be cleared.

• After data migration, you must manually restart the iSCSI template pool.

• As a best practice, do not use VM templates created in a higher-version system to deploy VMs in a CVK host that uses a lower software version.

• After data migration, to use the IP address of the source management platform, make sure the following conditions are met:

○ In a standalone environment:

▪ The source management platform and the management platform that uses the NingOS operating system must use the same gateway.

▪ The IP addresses of the source management platform and the management platform that uses the NingOS operating system must reside on the same network segment.

▪ Before editing the IP address of the management platform that uses the NingOS operating system, you must first shut down the source management platform. If you do not shut down the source management platform, you cannot use its IP address. If the source management platform serves as a CVK host, you must first remove the host and then shut down the source management platform.

○ In a stateful failover environment (only the virtual IP address is edited and the actual host IP address is not edited):

▪ The source management platform and the management platform that uses the NingOS operating system must use the same gateway.

▪ The virtual IP addresses of the source management platform and the management platform that uses the NingOS operating system must reside on the same network segment.

▪ Before editing the IP address of the management platform that uses the NingOS operating system, you must first shut down the source management platform.

• To edit the route settings of the management platform that uses the NingOS operating system after data migration, manually reconfigure the route settings.

Procedure

1. On the top navigation bar, click System.

2. From the left navigation pane, select CVM Data Migration.

3. Click Migrate.

4. In the dialog box that opens, configure parameters for logging in to the OS of the management platform, compatibility check, data migration, re-enabling cluster HA, and connecting hosts as described in "Parameters."

5. Click Finish Migration.

6. Click OK.

Parameters

• Set the management node access info

○ IP Address: Specify the IP address of the non-NingOS management platform. Only E0730P06 and E0730 versions later than E0730P06 and E076X non-NingOS management platforms support data migration.

○ Username: Specify the root username used for logging in to the OS of the non-NingOS management platform.

○ Password: Specify the root password used for logging in to the OS of the non-NingOS management platform.

• Re-enable Cluster HA

○ Cluster Name: Name of the cluster on the non-NingOS management platform.

○ Result: Result for re-enabling cluster HA.

• Connect All Hosts

○ Host Name: Name of the host.

○ Connection State: Whether the host is connected successfully.

• Verify management platform address

○ Management Platform Address: Used to specify the address for accessing the management platform after migration is completed. Users can select one of the following addresses:

○ Current: When this option is selected for the management platform access address method, the system will automatically fill in the address of the current management platform, which users cannot modify.