![]() If you cannot restore from backup then that backup is not very useful. ![]() Remember, your backup is only as good as your restoration. Aside from having that all important backup, I would also execute a restore operation as a test. Verify your environment is backed up and ready to go.Great point in time here to create your run-book if you have not already. Review the documentation associated with upgrading.Verify the upgrade path for the solution(s) you plan on upgrading.Upgrading your environment will likely involve the following. Always review the documentation (multiple iterations) prior executing any tasks. Great way to remain organized and review everything thoroughly before proceeding with your upgrade. ![]() It is a very good practice and habit to get into. Regardless of which version you are currently running, I highly recommend creating an upgrade run-book (spreadsheet) to track the tasks associated with your upgrade. vSphere ESXi 6.5 U3 – Build 13932383 (single 3-node HA/DRS cluster).As you can see, very basic lab setup that I am going with with and upgrade both my vCenter Server and ESXi hosts basically a ‘naked vSphere’ deployment. ![]() I felt the need to start here to help provide some guidelines for those still using 6.5.Īs I do in my previous step-by-step articles I provide a brief summary of the software versions that I am starting with in my lab environment. There are going to be a lot of great articles out there for upgrading 6.7 to 7.0 so keep an eye out for those. This blog article is intended for that specific audience. There are some organizations out there that didn’t make the jump to vSphere 6.7 and are running vSphere 6.5.
0 Comments
Leave a Reply. |