Hello,
i found an upgrade instruction from VCSA 6.5 to 6.7.https://www.wojcieh.net/upgrade-vcenter-server-appliance-6-5-to-6-7/
Are the steps to upgrade from VCSA 6.0 to 6.7 identical?
Is it possible to keep the old VCSA name from my appliance?
Some other questions:
1. How many cluster can i create in a datacenter?
2. How many clusters can a vCenter manage?
If i have a 6.7 vCenter with 2 clusters….
In one cluster 6.7 ESXi, in the other cluster 6.5 ESXi.
Do i have any limitations about the features if i have diffenrent ESXi versions?
Regards
Dennis
Correct!
I always rename the source VM (existing VCSA) befor i start the migration. For the target VM i select a different Datastore because i would like to see the right folder and *.vmdk name. I dont like the /vmname_1/ naming scheme which ESXi choose when a folder with the choosen name already exists. Also not every of my customer have svMotion license so i cant correct a wrong naming scheme in a easy way.
Regards,
Joerg
Hello
Yes, the upgrade procedure is the same. You can upgrade directly from VCSA 6.0 to 6.7 (from 5.5. you need an intermediate step to 6.0 or 6.5 and you cannot upgrade directly to 6.7)
The VCSA name will be the same as it was on your old VCSA. Probably you have to change the VM label in the inventory to the same name as the old VCSA had and rename the old one to "VCSAName_old" or something like this
You can manage both clusters with ESXi in 6.5 and 6.7. Of course if version 6.7 has a new feature, you won't have it available on the 6.5 ESXi...
For configuration maximums see https://configmax.vmware.com/guest and http://sdebbeche.com/wp-content/uploads/2016/11/vsphere-65-configuration-maximums.pdf , the latter is vSphere 6.5. In vSphere 6.7 the numbers changed slightly, see http://vsphere-land.com/news/configuration-maximum-changes-in-vsphere-6-7.html for the differences.
best regards
The VCSA name will be the same as it was on your old VCSA. Probably you have to change the VM label in the inventory to the same name as the old VCSA had and rename the old one to "VCSAName_old" or something like this
OK. Means before the migration i can rename my old VCSA in my vSphere webclient and then i do the migration with the original name of my old VSCA?
Correct!
I always rename the source VM (existing VCSA) befor i start the migration. For the target VM i select a different Datastore because i would like to see the right folder and *.vmdk name. I dont like the /vmname_1/ naming scheme which ESXi choose when a folder with the choosen name already exists. Also not every of my customer have svMotion license so i cant correct a wrong naming scheme in a easy way.
Regards,
Joerg