Collect required logs when vCenter upgrade is failed

Products

• VMware vCenter Server 7.0
• VMware vCenter Server 6.0

Issue/Introduction

^{When a vCenter Server upgrade fails, we need to collect the required information in order to investigate the root cause of the issue.}

Environment

^{VMware vCenter Server 6.5}

^{VMware vCenter Server 6.7}

^{VMware vCenter Server 7.x}

Resolution

 ^{Prior to reverting to the snapshot:}

1. ^{Please capture a screenshot of the error}

2. ^{Navigate to the windows machine where the vCenter Server upgrade was attempted. Locate the following directory:}

^{C:\ProgramData\VMware\vCenterServer\logs} 

3. ^{If stage 1 completed successfully, proceed to newly deployed vCenter Server VM.}

4. ^{Initiate a Putty session and execute ‘vm-support’ command.}

^{Important: Please revert to the snapshot taken prior to the vCenter Server upgrade attempt to recover the vCenter Server.}

<sup>When using multiple vCenters in the same Single Sign on Domain (Enhanced Linked Mode), there is high potential of corruption of the domain if no offline snapshots are taken of all nodes before the changes. 

If a change must be reverted, all nodes of the Enhanced Linked Mode domain have to be restored back to this offline/consistent snapshot. All nodes must be reverted to the snapshots first, before powering any on.</sup> 

^{For more information please refer to KB article: https://knowledge.broadcom.com/external/article/313886/vmware-vcenter-in-enhanced-linked-mode-p.html}

^{After reverting to the snapshot:} 

1. ^{Initiate a Putty session to source vCenter Server and execute ‘vm-support’ command.}

2. ^{Please submit a support case by following the steps outlined in the KB article: https://knowledge.broadcom.com/external/article/142884/creating-and-managing-broadcom-support-c.html}

Additional Information

^{Please upload the logs to support case by following the steps outlined in the KB article https://knowledge.broadcom.com/external/article/344754/uploading-diagnostic-information-for-vmw.html}