Windows Azure VM disappeared after trial limit reached
Recently I set up SharePoint farm in my customer's Windows Azure trial subscription. In a few days he received e-mail saying that the subscription reached allowed limit. So he decided to move to pay-as-you-go subscription. But (as you may know) all the Virtual machines and virtual networks were deleted. Instead empty Cloud Services named exactly as you VMs appeared. The problem and possible solutions described in many posts like:http://blogs.msdn.com/b/narahari/archive/2012/10/18/windows-azure-virtual-machine-disappeared-or-gone-how-do-i-recover.aspxhttp://social.msdn.microsoft.com/Forums/en-US/WAVirtualMachinesforWindows/thread/94b52c79-5487-453d-81b7-016baec62d28/
Generally, folks suggest 2 possible recovery approaches:
- Create new VMs using existing disks as templates.
- If (1) don't work (as was for me because of "A lease conflict occurred with the blob" error), download CloudXplorer and copy VHDs into different place.
I found alternative solution that worked for me.
- First you need to delete all the Cloud Services that are named after your VMs. Otherwise you will not be able to create VMs with the same DNS names.
- Go to Virtual Machines and select Disks. You will see all you disks that are not attached to any VM. You should delete them, but be careful: DON'T delete associated VHD (you will be prompted for that option).
- Now you will be able to create Images from VHDs. Go to Images and create new images from the VHDs.
- Recreate your virtual networks with the same settings (hope you remember them).
- Recreate your VMs using Images you already created and their original DNS names. If you set up DNS server IP in you virtual networks you need to create the DNS server VM first.
Wait a bit while your VM is creating. Because you didn't run sysprep before image creation, the VM will stuck in "Running (Provisioning)". Don't worry - the VM is ready to use and seems to be operational anyway.