I sold my client a 5 host ESX 6.0 u2 with vSAN 6.0 in early 2016. Late last year we upgraded to ESX 6.5 u2...but since VMware technical support had no idea how long a block-by-block vSAN 6.0 to vSAN 6.6 upgrade would take my client has left it running vSAN 6.0. I certainly can’t blame them...and I would never sell hybrid vSAN again even if my life depended on it. It complicates EVERYTHING. Want to put a host running hybrid vSAN in miantenance mode? You’d better carefully plan that out and expect it to take 4+ hours.
Anyway, enough venting. I want to create the (2) L3 VPNs between thier production cluster and a new on-demand 3-host VMware Cloud then live migrate their workloads over to AWS. Then run the (long overdue) vSAN 6.6 on-disk upgrade on their production cluster. My question is
1. Am I forgetting something.
2. They don’t have NSX on their production cluster but I’m planning on selling them NSX Entrrprise Plus SPLA licenses (~$20/month/per protected VM) Prior to the live migration since NSX is running on AWS. Any advice?
3. Windows licensing & Trend Micro Deep Security licensing & Veeam licensing. I sold this client Windows datacenter licensing with Software Assurance, trend ds licensing and you guessed it Veeam licenseing. Since I don’t intend to instantiate new Windows guests while in the AWS environment I’m betting/hoping it is kosher to run these properly licensed Windows workloads in AWS. I’m not even going to try to migrate the Trend licenses - we‘ll have to roll the dice on viruses. Which leaves Veeam...which again cant migrate the licenses. So my plan is to create AWS snapshots regularly and then a fresh full Veeam backup the minute a server is live migrated back. Please don’t be shy in telling my plan sucks.
4. Uhm...did I mention that my client has a mission critical ~12TB VM fileserver? Well they do. If I could devote a 500Mbps circuit to it alone that would take 50 hours. They have ESX 6.5 which the FAQ said is all that is required for live migration. Question: has anyone live migrated such an enormous VM? Can anyone confirm that it would be available on-prem after triggering the vMotion to AWS but before the vMotion completed and vice verse be available in AWS after triggering the return vMotion? Anyone think this part of my plan sucks? If so, what would you do?