I am working on a VM in Azure. Recently Azure subscription is expired(disabled) & got a new subscription(For some reasons could not renew it).
Now trying to migrate my VM to the new subscription. How can I do it.
Thanks in advance.
Tried downloading VHD(Virtual Hard Disk). Unable to create VM using this VHD.
VM Details:
Ubuntu Server 18.04 LTS
Unfortunately, you cannot move the resources from a disabled subscription. Please contact the Azure billing support (it's free)
You can refer here on how to move the VM from one subscription to another (For an Active subscription)
Related
I have a server in Classic ASM which I want to move to another subscription.
I tried using the move feature on the portal but it throws error that target subscription is not empty.
Are there any way that I can recreate the classic VM from its VHDs and also migrate its IP address to the new Subscription.
I don't want the Generalise the VM.
Thanks.
I tried using the move feature on the portal but it throws error that target subscription is not empty.
If you want to move ASM resources to a new subscription, you should note:
All classic resources in the subscription must be moved in the same operation.
The target subscription must not contain any other classic resources.
The move can only be requested through a separate REST API for classic moves. The standard Resource Manager move commands don't work when moving classic resources to a new subscription.
To move classic resources to a new subscription, use the REST operations that are specific to classic resources, refer to this link.
Besides, if it is possible, I recommend you to use ARM nowadays, Microsoft released a new management model called Azure Resource Manager (ARM) which provides many new capabilities to manage, and control Azure resources. You could migrate the VM from ASM to ARM, refer to this link. And move it to another subscription, refer to this link.
The client does not plan to migrate to ARM currently.
To migrate the VM to another subscription, I followed the below steps and it worked well.
1- Copy the VM's VHDs to the destination storage account.
2- Create VM Image (Classic) using the VHD which was copied and then create VM out of it.
3- Unfortunately, I was unable to find a way to migrate the public IP address to another subscription.
My Azure VM with Windows server 2016 stopped unexpectedly today. When I tried RDP today in my vm, it was saying 'machine unavailable'. So I logged in to Azure portal, and the VM was actually running. But when I tried to restart it, I got a notification saying
"Failed to restart virtual machine xxxxx. Error: Storage account xxxxxxxx not found. Ensure storage account is not deleted and belongs to the same location as the VM."
But, I was successfully using the vm till today. I didn't do anything in the Azure portal. The storage account with the vhd still exists (in the same resource group). I once deleted an unused storage account about 2 months ago, but the VM was running perfectly till today. I am not sure about anything that may have happened. The activity logs are empty.
Please Create a new storage account with the name – 'xxxxxxxx' in the same region as VM and then restart the VM to mitigate the failed error.
Why?
It is looking for already deleted storage account. This happens mostly for diagnostics storage accounts (I can't exactly say whether this is a diagnostics one without knowing the account name. diagnostics account names are something like xxxxxxdiag). Sometimes, disappearance of diagnostic account doesn’t cause the VM to be unreachable but the VM would just be marked as ‘failed’ over the portal.
If the virtual machine stopped unexpectedly and is not available again, we can report the issue to the Azure support team from the Azure portal. Please have a try to confirm with the Azure support team whether it can be recovered.
According to your description that the VHD file is existing in the storage. We also can recovery the machine from the VHD file. More detail steps please refer to another SO thread.
This issue may be because the diagnostics storage account for the VM is deleted. You can solve this issue by Redeploy your VM under Support + Troubleshooting tab in the VM blade. See image:
The VM Role preview in Windows Azure ends on May 31, 2013 and Microsoft urges to migrate VM Roles to "proper" Virtual Machines that are in General Availability as described here:
http://msdn.microsoft.com/library/3dae01d2-2397-47ed-a134-f9ffe58a9b52.aspx
But how do I know which of the Virtual Machines running in Azure are VM Roles and which are Windows Azure Virtual Machines?
I wrote a blog post that may help: Do I have VM Roles that I should migrate? at http://blogs.msdn.com/b/benjguin/archive/2013/04/19/do-i-have-vm-roles-that-i-should-migrate.aspx
You probably see it easily in the portal, but an easy check could be to store something on your disk and stop/delete and recreate the machine. If the file is no longer there, that means it's a VM role.
I also believe you cannot see VMRole in the new portal (and only in the old portal)
I have been reading about LocalDB and how it can not be used in Azure Roles (since they do not persist if the role stops working) and that you should move towards either Azure SQL or Azure Storage.
However, is it possible to use the LocalDB in a Windows Azure VM? Because I do not currently have access to a Azure Account I am not able to test this myself.
Kind regards
Tom
Azure VM should work fine, since it is fully persisted and largely compatible with regular Windows. Note that I'm referring to the new Azure VM feature, not the old Azure VM Role, since the VM Role was not fully persisted. Just clarifying the answer in case someone doesn't read the question too carefully.
How can we configure VM Role on Azure Emulator? Is this possible or do i need to do my testing on Windows Azure Management Portal.
Thanks,
Mrinal Jaiswal
On Azure F&Q its written that Emulator supports VM role but to much dismay it doesn't. I talked to Microsoft Tech team and got this answer.
One good thing they told me was, if i want to use VM on Azure it will be better if i use extra-small deployment it will increase my compute hours and i can host 2 extra-small VM role on azure in free trail account.