Shulou(Shulou.com)05/31 Report--

In this issue, the editor will bring you about how to upgrade from vCenter 5.5to vCenter 6.0.The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

The process of upgrading from vCenter 5.5to vCenter 6.0is convenient, just follow the on-screen wizard and complete it step by step. However, there is a small episode, how to change VC's stand-alone disk mode, it is a little bit of a hassle. All right, let's take a look at the whole upgrade process.

First, upgrade SSO first

First of all, what is vCenter SSO?

SSO is an optional authentication system for VMware user management, service management and authentication, which allows different infrastructure such as vCenter and Web Client to be installed on different virtual machines, while SSO is a communication channel so that administrators do not have to install all the infrastructure on vCenter Server, so vCenter SSO is another vCenter authentication method other than AD infrastructure.

Users who perform a simple installation of vCenter do not need to worry about deploying SSO, because the current AD configuration will be listed and the corresponding configuration will be added when the correct certificate is given, to ensure that the installation image is logged in as a domain administrator instead of a local administrator, otherwise there will be problems adding domain users to vCenter.

In the new version of vCenter, SSO is more important than before. If you are interested in SSO, you can check the relevant manuals and documentation on the official VMware website.

Generally speaking, VCENTER and SS0 as well as ESXI are best released in the same version, so that they can give full play to their functions and features. So before upgrading VCETNER, let's upgrade SSO online.

The upgrade method is relatively simple: mount the ALL version of VMWARE6.0 iso, and upgrade it step by step.

Second, upgrade VCENTER

Let's focus on this upgrade process. Pay attention to two points:

If the original vCenter is a virtual machine, perform a snapshot, backup, and backup the vc database before performing the upgrade operation to facilitate recovery if necessary. Upgrade is risky, you need to be careful! If a problem occurs after the upgrade, you can search VMware KB for a solution.

Another problem is that if VC used to be a stand-alone disk, it cannot be snapped, cloned or NBU backed up. After we upgrade, we can modify the format of the independent disk to facilitate future backups.

First mount the iso of the ALL version of VMWARE6.0 on the host where VCENTER is located, and then execute the installation program (note that there is no upgrade button, the upgrade script will be automatically extracted)

Click install

The following will detect the original version and enter the necessary verification information.

Enter the password of the VCENTER administrator

Note that the authentication login password of the original VC is entered here.

The following is to configure the network and the corresponding ports, which are generally fine by default. These ports need to be released on the firewall.

Then confirm the installation and data, export the directory, and confirm that the VC and database have been backed up

Wait for the progress bar to be upgraded until it is successful.

Third, how to deal with stand-alone disk format

If VC used to be a stand-alone disk, we cannot take snapshots, clones or NBU backups. After upgrading, we need to modify the format of separate disks to facilitate future backups.

To modify the stand-alone disk, you need to close VC. Then we can think of going to the ESXI where VC is located to modify it, but will prompt that only VC has permission to modify it.

So what should we do? We can close the upgraded VC in ESXI and export it to OVA or OVF format. Then open the upgraded VC (because it is not cloned, so you need to configure the same IP address as the original VC and then start VC-related services to be normal), import the newly exported VC, then modify its independent disk format without booting the system, and finally close the previous VC and open the modified independent disk VC, and then see that the snapshot clone and NBU backup are normal.

IV. The evaluation model after upgrading

When VC is upgraded from 5.5 to 6.0, it becomes an evaluation mode, and you need to re-enter the authorized 6. 0 lisence for long-term use.

Note: if you use vSphere Web Client to manage vCenter Server, after upgrading to vCenter Server 6.0, upgrade the browser version used by the client (vSphere Web Client for managing vCenter Server or ESXi) to IE 10 or later. Using earlier versions of IE browsers will not be able to use vSphere Web Client 6.

Another thing to note is the difference between persistent and non-persistent on stand-alone disks.

In fact, persistence and non-persistence have been clearly stated in the settings. Persistent, that is, your data is not affected by the snapshot, whether you restore the system state or restore the snapshot, it will not affect the data of this persistent hard disk, so this independent hard disk generally stores the developed source code and important documents. in this way, if you restore the snapshot will not cause data loss, but not persistent is that when you restore the snapshot, your hard disk data will also be restored, and the data previously stored at the origin point will be lost.

This is how the vCenter 5.5 upgraded to vCenter 6.0.If you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.