Migrate vCenter Server 6. 5 to VCSA 6. 7

Step 1, use a browser to view the source vCenter Server version 6.5, as shown in figure 3-5-34.

Step 2, run the VCSA 6.7installer, as shown in figure 3-5-35, and click migrate.

Step 3, the migration is divided into two phases. First, enter the first phase, as shown in figure 3-5-36. Click next.

Step 4, check "I accept the terms of the license agreement" to accept the end user license agreement, as shown in figure 3-5-37, and click "next".

Step 5, connect to the source server and enter information about the source server, as shown in figure 3-5-38. Note that the ISO that the migration is running does not operate on the source vCenter Server server.

Step 6, run the VMware-Migration-Assistant program on the source vCenter Server server, as shown in figure 3-5-39, in the VCSA 6.7 installation ISO file.

Step 7, verify the migration program with the VMware-Migration-Assistant program on the source vCenter Server, as shown in figure 3-5-8, click Yes.

Step 8, set up the ESXi host or vCenter Server for the device deployment. If there is only one vCenter Server in the production environment, fill in the information about the ESXi host here, as shown in figure 3-5-41, and click next.

Step 9, the system appears with a certificate warning prompt, as shown in figure 3-5-42. Click Yes to accept and continue.

Step 10, set the information about the target virtual machine, as shown in figure 3-5-43, and click next.

Step 11, select the VCSA virtual machine deployment size. Different deployment sizes have different requirements for virtual machine hardware resources. Please select them according to the actual situation of the production environment, as shown in figure 3-5-44, and click "next".

Step 12, select the data store used by the target virtual machine, as shown in figure 3-5-45, and click next.

Step 13, set up the temporary network of virtual machines, as shown in figure 3-5-46. Note that the temporary network must be able to access the source VCSA virtual machine, and click next.

Step 14, complete the relevant parameter configuration of the first phase, as shown in figure 3-5-47, and click finish.

Step 15, start the first phase of the migration operation, as shown in figure 3-5-48.

Step 18, complete the first phase of the migration operation, as shown in figure 3-5-49, and click continue to proceed to the second phase. It should be noted that if there is a problem with the first phase of the operation, the second stage will not operate.

Step 17, enter the second phase of the migration, as shown in figure 3-5-50, and click next.

In step 18, the system conducts a pre-migration check and prompts the results, as shown in figure 3-5-51, click close.

Step 21, select the data to be replicated, as shown in figure 3-5-52. The production environment strongly recommends keeping all historical data, and click next.

Step 20, decide whether to join the VMware customer experience enhancement program as appropriate, as shown in figure 3-5-53, and click next.

Step 21, verify that the migration parameters are configured correctly, check "I have backed up all the necessary data in the source vCenter Server and database", as shown in figure 3-5-54, and click finish.

Step 22, the source vCenter Server virtual machine is closed during the migration process, which requires special attention, as shown in figure 3-5-55, click OK.

Step 23, there are three steps in data transfer, each of which must not report an error. Figure 3-5-56 copies the data from the source vCenter Server to the destination VCSA.

Step 24, set the target VCSA and start the service, as shown in figure 3-5-57.

Step 25, import the replicated data into the target VCSA, as shown in figure 3-5-58.

Step 26, the process of importing data will give you some message prompts, as shown in figure 3-5-59.

Step 27, complete the second phase, as shown in figure 3-5-60, and click close.

Step 28, look at the VCSA version, which has been migrated to version 6.7, as shown in figure 3-5-61.

Step 29, open the VCSA virtual machine console and see that the version information is version 6.7, as shown in figure 3-5-62.

At this point, the cross-platform migration of vCenter Server 6.5 to VCSA 6.7 has been completed. As long as the preparatory work is done in advance, there will be no problems in the migration process. Again, the VCSA 6.7 installer cannot run on the source vCenter Server server, and the source vCenter Server server needs to run the VMware-Migration-Assistant program.

Welcome to www.bdnetlab.com for more original documents of Mr. he.