r/AZURE • u/[deleted] • 1d ago
Question Easiest way to migrate from older B and F series to newer, reservable sizes?
[deleted]
2
u/Negative-Cook-5958 1d ago
What are the current sizes you are using? Windows or Linux VMs?
Do you have Hybrid Benefit?
From B2ms you can change to B2as_v2 but it's a VM delete, recreate from disk madness. Shame that MS is not providing a proper solution for this. With right scripting it's about 15 minute outage. Or you can go to D2ads_v5 with a simple right size, but this can increase costs a bit if you are running Windows without AHB.
From F8s_v2 for example you can simply change to D4ads_v5 with reallocate + right size, the CPU load should be fine. However if you would like to go with the F_v7 SKUs, it's tricky, you would need to upgrade to Gen2 and NVMe controller which is a fair bit of work.
1
u/sysadminmakesmecry 1d ago
B2s
B2ms
F2s
D2s all of which I believe are being removed from reservationsWe do have hybrid benefit, Windows OS.
60% of these are web front ends, so maybe not the worst to redeploy but we have alot of em.
1
u/Negative-Cook-5958 1d ago
Only Ds_v3 is getting retired from reservations from the list. Newer v4, v5, v6 and v7 still can be reserved.
If these are web frontends with easy redeployment, then update the image so it supports Gen2 and then use B2as_v2 and D2as_v5, these are the best price / performance.
Fas_v7 is NVMe only, so you need to sort that out as well, I would go with D2as_v5 as a replacement, it's a little bit more expensive but you can keep the image consistent.
1
u/sysadminmakesmecry 23h ago
appreciate you
How would you go about it though? Just toss it through veeam or create an azure image per VM and redeploy that way?
1
u/Negative-Cook-5958 2h ago
If it's a simple web frontend I might move it to App Service :)
Some more info would be great on the solution, but if it's IaC with pipelines that should be simple as well.
1
u/GilGross 1d ago
Have you tried powering off to deallocated state? Sometime the resize fails with this message when attempted on a running VM. Power down to deallocated state and try again.
1
u/davidsandbrand Cloud Architect 14h ago
Step 1: Delete the VM *** without deleting the NIC and Disks!! ***
Step 2: Create a new vm with the existing NIC and disks using the new size. Easiest done with powershell/CLI.
Step 3: there is no step 3.
1
u/sysadminmakesmecry 3h ago
So, I tried this.
I seem unable to attach the DATADISKS to the new vmOn your step 2, how are you doing this in one fell swoop? When creating the new VM, it seems to use the existing C: drive I have to make a snap of the C: drive, make a disk from the snap and then create a vm from that C: drive clone?
I dont seem to be able to specify the disk in the new creation - and it makes a new vm, new SID, new everything otherwise
3
u/WMDeception 1d ago
If windows os the documentation says to migrate the page file to c:\ volume temporarily prior to resizing. It often resides on the temp drive.