Hi! Nice video guide. Some question to clarify 1) At 6:18 of the video, you had change the Hostname of the VM to a different hostname as compared to your source, is it a must? I think by putting the same hostname should not be having any issues as the source VM will be shutdown right after the upgrade. Am I right? 2) 6:47 of the video, is it a need to enable the Thin Disk Mode for the upgrade? Thanks!
1] At 6:18 I have given a different VM name to target VM, but I have not changed the hostname. At 13:17 you can refer hostname of the target VM is same. Giving a different hostname is also not necessary, you can keep the same. 2] At 6:47, enabling Thin Disk mode is not compulsory. You can leave that option unchecked.
I just subscribed to your channel. Good job done. I have two questions 1. Once upgraded to VCSA7 , Can we delete the old VCSA 6.7 appliance from Datastore. 2. Can we upgrade VCSA appliance from Update manager, importing VCSA 7 appliance ISO image.
1--Yes, You can delete the old VCSA from Datastore. 2--I think you cannot upgrade VCSA from Update Manager, because Update Manager is for patching or upgrading the ESXi.
Suppose we have 2 host, both managed by vcenter 6.7 - Host 1 has vcenter, My idea is to move vcenter from host 1 to host 2 during upgrading from 6.7 to 8 directly. so can i give the target host as host 2? Will it upgrade? Will it have any effect?
suppose in a cluster 4 hosts are present, by this process one host wll upgrade ........my question is what about remaining 3 hosts?? how to upgrade ......... ?????
Can't get out of this error would you have any idea what the problem would be? "No networks on the host. Cannot proceed with the installation. Configure network settings for this vCenter Server"
It creates a new VM with a similar IP to the old VM. In the end, it shut down the source VM but doesn't delete it. If the upgrade fails you can shut down the new VM and start the old VM. You can also take the backup/OVF of the source VM before starting. You can also take a snapshot of the source VM for safety purposes.
![Summer Walker - Heart Of A Woman [Official Lyric Video]](http://i.ytimg.com/vi/SFddctbZzw8/mqdefault.jpg)
Good explanation on upgrade. thank you
You're Welcome.
Hi! Nice video guide. Some question to clarify
1) At 6:18 of the video, you had change the Hostname of the VM to a different hostname as compared to your source, is it a must? I think by putting the same hostname should not be having any issues as the source VM will be shutdown right after the upgrade. Am I right?
2) 6:47 of the video, is it a need to enable the Thin Disk Mode for the upgrade?
Thanks!
1] At 6:18 I have given a different VM name to target VM, but I have not changed the hostname.
At 13:17 you can refer hostname of the target VM is same.
Giving a different hostname is also not necessary, you can keep the same.
2] At 6:47, enabling Thin Disk mode is not compulsory. You can leave that option unchecked.
Nice video..... Keep going
I just subscribed to your channel. Good job done. I have two questions 1. Once upgraded to VCSA7 , Can we delete the old VCSA 6.7 appliance from Datastore. 2. Can we upgrade VCSA appliance from Update manager, importing VCSA 7 appliance ISO image.
1--Yes, You can delete the old VCSA from Datastore.
2--I think you cannot upgrade VCSA from Update Manager, because Update Manager is for patching or upgrading the ESXi.
Hi, great video thanks. Do you need to upgrade your licenses to Version 7 before the upgrade ?
After the upgrade, you will have to apply license for version 7.
Can you delete the old vcenter shown? Any issues with that?
Once new vCenter has been upgraded successfully and working fine, you can delete the old vCenter.
Hi! Do the PC and vCenter used when upgrading have the same network address?
No, but should be in same network/subnet.
After completing the upgrade, can I change the FQDN and Hostname of the new vm to be the same as the old vm?
Yes, you can. Just do the new hostname entry to your domain controller also, so that new fqdn will resolve in your network.
Good explanation.
Glad you think so!
Suppose we have 2 host, both managed by vcenter 6.7
- Host 1 has vcenter,
My idea is to move vcenter from host 1 to host 2 during upgrading from 6.7 to 8 directly.
so can i give the target host as host 2?
Will it upgrade? Will it have any effect?
Yes, you can.
@@VirtualTechBox so this do not require any migration? It automatically get install on host 2? Without the shared resource?
@@pradnyapadaki6594 Yes.
good video bro keep going and thanks for the simple explaination
Glad it helped.
suppose in a cluster 4 hosts are present, by this process one host wll upgrade ........my question is what about remaining 3 hosts?? how to upgrade ......... ?????
This procedure is about upgrading the vCenter not the host. If vCenters are in a cluster, you need to upgrade each vCenter individually.
Can't get out of this error would you have any idea what the problem would be? "No networks on the host. Cannot proceed with the installation.
Configure network settings for this vCenter Server"
Are you able to access Host through IP?
how come the name still had a 7 in it, it didn't look like it used the original name
Yes, it uses the same IP address and hostname. At the end of the migration temporary IP gets released and the source VM is powered off.
why u gave temporary ip address is thir any rule to give that...?
I gave temporary IP because after the upgrade it will have my old IP which was there in my VCSA 6.7. There is no such rule.
can we do upgrade from vCenter 6.7 to 7.0 directly ?
Directly means? I have upgraded 6.7 to 7.0 in this video.
Do i need to do something different if one of my instances is in Linked Mode?
I'm doing 3 upgrade in total. 1 is its by itself and the 2 are in linked mode. just to clarify
Seems the procedure would be the same in linked mode also.
@@VirtualTechBox okay thank u!
How can I roll back if the upgrade fails ?
It creates a new VM with a similar IP to the old VM. In the end, it shut down the source VM but doesn't delete it. If the upgrade fails you can shut down the new VM and start the old VM. You can also take the backup/OVF of the source VM before starting. You can also take a snapshot of the source VM for safety purposes.
Can I delete the other VM?
Yes. Once the upgrade completed successfully, you can delete the older VM.