5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
My migration team is doing a good job trying to push as many VM’s through Move to stage reboots after-hours. I’ve noticed that replication slows way down when we have about 15-20 VM’s waiting for cutover. I have checked the load on the Move VM and increased the amount of CPUs. Replication goes well (25Gbit network), but now we only have 2 seed streams going with 19 waiting to cutover. I have 4 other VM’s that are in the “seeding data” phase, but haven’t started their copies. Is this a bottleneck within the Move postgres database? Any ideas on how I can get more VM’s copying in parallel? Thanks,
We are planning our AHV migration and would like to migrate about 75% of our VM’s (~400) during their negotiated patch outage windows to minimize how many app teams get to set our schedule for us. Most of these outage windows are in the 3AM time frame. We would like to find an automated/scripted way to do the cutover so that we can set a job to run that script overnight during that window. I’ve seen some REST calls that look like they could do it. Has anyone actually done it? If so, would they mind sharing a sanitized snippet of their Powershell/REST code? Thanks in advance!
I hope this is an easy question. Am I allowed to increase the VCPU and memory resources on the Move VM/Docker without issues? I know hot-plug is disabled, so it’s in the reboot-world. I found that we are pegging the CPUs out when we are queueing migrations, so I want to try to get some more throughput on it to take advantage of our 25Gb infrastructure. Thanks
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.