VMware VCSA 6.0 to 6.5 upgrade: data copy – pt.2

vcsa60to65datacopy01

Deployed the VCSA 6.5, the upgrade process continues with Stage 2 where data are copied from source to target vCenter Server Appliance.

With the result of the upgrade procedure, the new vCenter Server will have same hostname and IP address of the source VCSA avoiding services interruption.

 

Blog Series

VMware VCSA 6.0 to 6.5 upgrade: deploy VCSA – pt.1
VMware VCSA 6.0 to 6.5 upgrade: data copy – pt.2

 

Stage 2 data copy

Completed Stage 1, Stage 2 can be finalized in two ways:

  • using the vCenter Server Appliance Installer
  • accessing the vCenter Server Appliance Management Interface typing in your preferred browser the address https://IPAddress_VCSA:5480

In the example, the vCenter Server Appliance Installer is used to proceed with Stage 2. Click Next to begin.

vcsa60to65datacopy02

The system performs some pre-upgrade checks.

vcsa60to65datacopy03

A warning reminds you that the cluster where the ESXi host that manages the new VCSA resides has not to be set as Fully Automated. Check out part 1 of the procedure for additional details. Other extensions installed in the source VCSA (PernixData FVP in the example) should be double checked for compatibility with the new VCSA. Click Close to continue.

vcsa60to65datacopy04

The window shows the credentials inserted in Stage 1. Click Next.

vcsa60to65datacopy05

Select what data should be copied to the target VCSA then click Next.

vcsa60to65datacopy06

Optionally you can join the CEIP program. Click Next.

vcsa60to65datacopy07

Thick I have backed up the source vCenter Server and all the required data from the database option then click Finish to start the data copy process.

vcsa60to65datacopy08

Click OK to confirm.

vcsa60to65datacopy09

The system starts copying the data from source VCSA.

vcsa60to65datacopy10

Looking at the Migration Assistant installed in the VUM server, the export process is in progress.

vcsa60to65datacopy11

 

VMware Identity Manager Service error

During the copy process you may experience this error related to the vmidentity-firstboot.py.

vcsa60to65datacopy12

The procedure stops at 5% of step 2 while the system tries starting the VMware Identity Manager Service. Clicking on Retry button, the problem is not solved and same error occurs again. Click Close to exit the wizard.

vcsa60to65datacopy13

This error doesn’t give any chance to continue the upgrade and you have to start the entire procedure from the beginning.

vcsa60to65datacopy14

To fix this matter, you have to add localhost.localdom localhost in the /etc/hosts file of the new VCSA as suggested by the KB2147908 article before Stage 2 takes place. When Stage 1 has completed, from the vSphere Web Client of the source VCSA right click the target VCSA and select Open Console.

vcsa60to65datacopy15

Press Alt+F1 and log in with root credentials. Run this command to enable SSH:

# ssh.set –enabled true

and this command to verify SSH is enabled:

# ssh.get

vcsa60to65datacopy16

Connect to the VCSA with an SSH session and root credentials using the temporary IP Address specified during Stage 1 .

vcsa60to65datacopy17

Enable the shell and run the following command to add localhost.localdom localhost to the /etc/hosts file:

Command> shell
# echo “::1 localhost.localdom localhost” >> /etc/hosts

vcsa60to65datacopy18

Type the following command to verify if the parameter has been entered.

# cat /etc/hosts

vcsa60to65datacopy19

Continuing with Stage 2 of the deployment, I figure out the Applying network configuration step erased the entry causing the same error again.

vcsa60to65datacopy20

Adding the localhost.localdom localhost to the /etc/hosts as soon as Stage 2 starts step 2 fixed the issue.

# echo “::1 localhost.localdom localhost” >> /etc/hosts

vcsa60to65datacopy21

Resume the data copy

After using the suggested fix, the installation continues.

vcsa60to65datacopy22

 

Importing VMware vSphere Update Manager error

Another issue you may experience occurs in Stage 2 during the Importing VMware vSphere Update Manager data step. Also this error requires to start the overall upgrade procedure from the beginning.

vcsa60to65datacopy23

To fix this problem, make sure the VMware vSphere Update Manager Service in the VUM server runs with a dedicated account and not as Local System.

vcsa60to65datacopy24

Start the upgrade once again and if no issues occur, after some minutes Stage 2 completes successfully. Click Close to exit the wizard.

vcsa60to65datacopy25

The new VCSA offers two ways to access vSphere:

  • Using the classic Flash-based vSphere Web Client
  • Using the new HTML5-based vSphere Web Client but with limited functionality

vcsa60to65datacopy26

 

Access the new VCSA

Since the upgrade process copies the configuration from source to the target VCSA, the new vCenter Server will have same hostname and IP address of the source VCSA.

vcsa60to65datacopy27

To access the classic Flash-based vSphere Web Client, from your favorite browser type the address https://IPAddress_VCSA/vsphere-client.

vcsa60to65datacopy28

To access the HTML5-based vSphere Web Client, type the address https://IPAddress_VCSA/ui. Keep in mind that this client has limited functionality.

vcsa60to65datacopy29

The upgrade procedure is now complete. For a fresh installation of the VCSA, check out this post.

signature

No Responses

Leave a Reply