Shulou(Shulou.com)06/01 Report--

This article mainly shows you "how to solve the vc upgrade failure to restore the snapshot after the data inconsistent problem", the content is easy to understand, clear, hope to help you solve the doubt, the following let the editor lead you to study and learn "how to solve the vc upgrade failure to restore the snapshot after the data inconsistent problem" this article.

The first failure phenomenon:

In the afternoon, 192.168.146.1 vc5.5 upgrade 6.0 failed and rolled back. Vcenter, DB, and SSO all take snapshots with memory. At that time, after the inspection and recovery, we were able to connect vc and web client. The vc connection was found to be interrupted that night, and it was interrupted again the next morning.

The first process:

After analysis, there is a problem with the timestamp between VC, DB and SSO when the snapshot is restored, and the data is out of sync. It is recommended to restart VC and SSO immediately after the rollback and re-establish the data connection. The second rollback the next morning restarts Vcenter and SSO.

The second failure phenomenon:

After the recovery is completed, it is found that 6 virtual machines are grayed out and displayed (isolated). There is nothing wrong with the virtual machine itself.

The second process:

Once again, after taking a snapshot yesterday and before rolling back today, these 6 virtual machines have had DRS migration. The registered host is inconsistent with the host at the time of the snapshot. Re-registration is recommended. After linking the hosts one by one with client, find the hosts that these virtual machines are now registered with. Re-link after disconnection, and the virtual machine can be displayed and accessed normally after the data is refreshed. If you can't find it, you can remove it from the list and add it back.

Recommendations:

1. Restore the VC snapshot as soon as possible. The longer the time, the more likely it is to generate new data, resulting in a long recovery time and prone to failure.

2. When taking snapshots of VC and SSO, select the snapshot without memory, and open it directly from the shutdown state when restoring, and establish a connection with the database. According to previous experience, it will not lead to the first failure.

The above is all the contents of this article entitled "how to solve the problem of data inconsistency after vc upgrade failed to restore snapshot". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, 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.