Here, for example, you can check out the possible upgrade paths for VMware vCenter Server:
On the same resource, there’s a tab Upgrade Path to verify whether the currently installed versions of your products have a direct upgrade path to the new version of vSphere. You have to make sure it will remain working after the upgrade, so find a time to go through the manufacturer’s documentation. That way, you can see how this version of the product is compatible with the other solutions in your virtual data center.įor example, if you were to pick, say, VMware vCenter 6.7 Update 2, you can see it plainly that it is compatible with VMware ESXi 6.5 Update 2 and 6.0 Update 3, but not with ESXi 5.5 Update 3:Īside from VMware products, in particular, it won’t hurt if you also check for third party software, backup tools, active scripts, various frameworks, API, etc.
What if they will work differently, or worse, aren’t supported at all? So, to avoid all the headaches, you’ll need to check for Interoperability with VMware Product Interoperability Matrices. I will assume that the first thing every admin wants to know before upgrading the system is whether the other products will continue to work as they used to, and that is a good question indeed. Also, a lot of those aspects work with the other VMware products as well. So, here comes the purpose of this text: covering key things that you need to take care of before upgrading your VMware vSphere.
Therefore, they miss the part to review how other VMware products are compatible with the new vSphere version or determining which Upgrade Paths are supported. Still, many admins tend to forget that with every upgrade comes proper planning, collecting requirements, and understanding compatibility and prerequisites. VMware vSphere upgrade? That doesn’t really sound scary, and it generally isn’t. StarWind Virtual Tape Library (VTL) OEM.Software as a Service (SaaS) & Financing.StarWind Virtual Tape Library Appliance (VTLA).
0 kommentar(er)
