This is not a guided procedure for migrating to vCenter 6. Just a simple collection of doubts. It’s important to bear in mind some ‘apparently’ minor considerations we read everyday about vSphere 6.0. Truth is, you have to assess your own scenario in terms of scalability and choose the future vSphere 6 model that best fit your needs.
Following and reading this VMware Best Practices is a must, prior to perform any changes.
Keep in mind the final update model you are upgrading to depends entirely on what your current 5.x schema currently is.
I guess our current vCenter server is running now but, is the current vCenter state good enough to guarantee the upgrade?. And if so, where to upgrade to ? 🙂 .
I’d like to summarize some relevant points to consider at the time you decide going to windows vCenter 6 using the Embedded Deployment Model.
- You’ll need a Windows Server (Virtual or Physical) with at least 8 GB of RAM
- The earliest Windows Server version that vCenter Server 6 supports is x64 Windows Server 2008 SP2. Check the supported Host OS list. (Same as 5.5, I must say)
- Also 15 GB free space on installation disk is required. Sounds silly but I’ve seen vCenter servers with less than that.
- SQL Express: Migrate your Database to a SQL Server following this KB1028601 or it will be automatically migrated to Postgres.
- Once on a Postgres vCenter 6.0, if you decide to uninstall it, keep in mind that Postgres database will be erased, so backup your data is mandatory as described on KB2108547
These are just a few remarks and links to read carefully when I first faced the upgrade and stared wondering how the process might be. Now that I read those KBs , Guess what? it really leaves an opened door to use VCSA 6.0 instead. With version 6, VCSA is now capable of use linked mode, external Database and not anymore limited to just a few ESXi. I’ll think about it for next post.