pchettri
asked on
VUM on windows and VDP appliance
Is there a recommended steps to remove VUM installed on Windows on my existing vSphere 6.1 environment. Also, needed to reinstall VDP appliance, as the exiting one is not connecting with plugin after recent power failure. I was thinking about new appliance and provisioning storage again on VDP, once I upgrade vcenter and ESX to 6.5. For now I need to find an article to unregister existing VDP appliance.
Thirdly, Is it recommended to take Vcenter appliance snapshot before upgrading existing vcenter? Does the snapshot really help, if I already upgraded ESX after vCenter upgrade and already register to new vCenter?
Thirdly, Is it recommended to take Vcenter appliance snapshot before upgrading existing vcenter? Does the snapshot really help, if I already upgraded ESX after vCenter upgrade and already register to new vCenter?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is how I would approach my upgrade -
remove VDP
install new vCenter 6.5
add all ESX host to new one - or one at a time
when it is greyed from OLD VCSA remove all host
Create baselines for host upgrade
check compatibility over cluster
remediate one host at a time. Move all VMs before remediation and bring main mode
Keep old VCSA shutdown for few weeks and delete from disk after 2 weeks
This way I don't have need for snapshot of VCSA. Also, I do have couple of critical health alert with this VCSA on services health like "The data service container process is running low on heap memory " and "
Filesystem holding VMware Postgres service error logs is running low on available space. Available: 123 MB. Total: 10071 MB.
", which I presume should all go away with new VSCA 6.5.
Also, I will log ticket with netapps for compatibility of Ontap version with ESX 6.5
remove VDP
install new vCenter 6.5
add all ESX host to new one - or one at a time
when it is greyed from OLD VCSA remove all host
Create baselines for host upgrade
check compatibility over cluster
remediate one host at a time. Move all VMs before remediation and bring main mode
Keep old VCSA shutdown for few weeks and delete from disk after 2 weeks
This way I don't have need for snapshot of VCSA. Also, I do have couple of critical health alert with this VCSA on services health like "The data service container process is running low on heap memory " and "
Filesystem holding VMware Postgres service error logs is running low on available space. Available: 123 MB. Total: 10071 MB.
", which I presume should all go away with new VSCA 6.5.
Also, I will log ticket with netapps for compatibility of Ontap version with ESX 6.5
ASKER
This is how I would approach my upgrade -
remove VDP
install new vCenter 6.5
add all ESX host to new one - or one at a time
when it is greyed from OLD VCSA remove all host
Create baselines for host upgrade
check compatibility over cluster
remediate one host at a time. Move all VMs before remediation and bring main mode
Keep old VCSA shutdown for few weeks and delete from disk after 2 weeks
This way I don't have need for snapshot of VCSA. Also, I do have couple of critical health alert with this VCSA on services health like "The data service container process is running low on heap memory " and "
Filesystem holding VMware Postgres service error logs is running low on available space. Available: 123 MB. Total: 10071 MB.
", which I presume should all go away with new VSCA 6.5.
Also, I will log ticket with netapps for compatibility of Ontap version with ESX 6.5
remove VDP
install new vCenter 6.5
add all ESX host to new one - or one at a time
when it is greyed from OLD VCSA remove all host
Create baselines for host upgrade
check compatibility over cluster
remediate one host at a time. Move all VMs before remediation and bring main mode
Keep old VCSA shutdown for few weeks and delete from disk after 2 weeks
This way I don't have need for snapshot of VCSA. Also, I do have couple of critical health alert with this VCSA on services health like "The data service container process is running low on heap memory " and "
Filesystem holding VMware Postgres service error logs is running low on available space. Available: 123 MB. Total: 10071 MB.
", which I presume should all go away with new VSCA 6.5.
Also, I will log ticket with netapps for compatibility of Ontap version with ESX 6.5
VASA is not snapshot acceleration.
You need VAAI driver on ESXi-s for that( and VMX-09 or better for iSCSI or VMX-10 or better on NFS)
Still disk is written twice when snapshot is active
You need VAAI driver on ESXi-s for that( and VMX-09 or better for iSCSI or VMX-10 or better on NFS)
Still disk is written twice when snapshot is active
ASKER
However, one thing I would like be sure is the migration of VM between ESX 6 host after the vcenter upgrade to 6.5, to allow host update without brining VMs down. Hopefully, HA and manual vmotion would continue work on host with lower version using higher version of management appliance. In the past, I have upgraded host first before appliance clean installation.