A couple of months ago our MSDN Visual Studio subscription was appeared cancelled. When contacted Microsoft, they restored our account. But all our servers running in the subscription was stopped. But I was able to start all servers except one (Ubuntu server). It was showing "internal server error". We managed to recover most of the data from our backups. But I would like to recover some other data that was not in the backup. Now, when I tried starting the server, it shows the error "A disk with nae xxxxxx-2012080707000 does not exist in the subscription". When checked, this particular disk is not listed in the "Disks" tab in Virtual Machines.
I am unable to attach or detach disks to the VM or upgrade it.
How can i troubleshoot it and start the VM
Thank you in advance
Since the VHDs are stored as page blobs in blob storage, you can start by looking for a page blob named the same as your disk. Usually you would find these blobs in vhds blob container. If you have this blob, you can create a disk using this and attach it to your VM. However if the blob is not there, then I don't think you can do anything.
Related
I can't get my VM disk restored in Azure: it is only "converted" to the Storage Account linked to my VM.
Does anyone know how to get a VM fully restored from a Recovery Service Vault backup in Azure please?
Edit :
For additional precision, I made a simple Linux VM hosting a test website in order to experience Azure's backup and restore feature.
So once the test website was online, I waited for a backup job to be done.
Then I deliberately broke the test website inside the VM, and launched a disk restore.
Unfortunately, the restore did nothing to the VM. I checked on the jobs and restore was marked as "Successful", and a VM restart did nothing.
Anyway, I can find the "vhd" in the Conainer tab of the Storage Account. But I can't find a way to attach it to the VM...
Is the disk restoration feature even supposed to work like intended ?
I tried to replicate a backed up restore of a virtual machine using Azure Site Recovery.
When you restore the virtual machine you have the option to select if you want to restore the disks or the virtual machine.
Selecting here to restore as a VM, will create the VM for you.
You can check that status of the restore by going to the jobs section of the machine in ASR.
For reference, see this page for more detailed instructions.
This likely flies in the face of what Azure thinks it can do, but have you tried to create the VM first and then just restore your data? Other possible options are:
The user you are logged in as does have the correct permissions to create a VM in that space as well as restore the data, yes?
And you did select Recovery Service vaults in the portal, correct?
check if the original VM had any special conditions, such as multiple NICs or a load balancer. Any custom VM configurations, including HUB licensing, will not be duplicated with the Create Virtual Machine option as it uses Quick Create. You will need to use PowerShell to attach the restore disks to your chosen VM configuration. You can get additional information on PowerShell and Azure backups here.
And in the link that kim provided above, scroll down to the "Create a new VM from a restore point" section and review the options and notes for creating a new VM. You can get more information on ASR at this page.
Will my files and database will be lost if I stop or restart or my VM get crashed certainly.
Can the files created at VM be stored in my computer hard disk so that I can retrieve them in future, if I need.
If your VM get crashed you will not be able to access your VM as well as your data but that doesn't mean you will loss your data. Your data will be stored there in the blob storage.
What you need to do is- attach the blob storage properly to some other vm or new vm to access it again.
As previously mentioned this was answered on another thread, the best thing to do is to download the VHD locally.
From the Windows Azure Portal you can easily download the VHD. Just navigate to STORAGE and then the storage account in which your virtual disk is created. Select CONTAINERS (at the top), open the container named "vhds". Just click the vhd you want and select DOWNLOAD (at the bottom of the page).
Have a great day
Could someone please help me understand this? I created Virtual Machine in Azure running Windows Server 2012. I noticed Azure created a storage account automatically. When I go inside that storage account, click Containers tab, and under vhds name it shows a name-name2-2014-12-05.vhd which is 127 GB and it always has recent Last modified date. What is that for? Is that my live backup image of my entire server deployment? If so where can I see how often it backs up?
When I go inside that storage account, click Containers tab, and under
vhds name it shows a name-name2-2014-12-05.vhd which is 127 GB and it
always has recent Last modified date. What is that for?
Virtual Machines in Azure are Stateful in nature. What that means is that any changes you make to the Virtual Machines like installing software, creating files etc. are persisted. The way Azure achieves this is by storing the Virtual Machine VHD as a page blob in Azure Storage. What you see as name-name2-2014-12-05.vhd is the VHD using which Azure launches your VM.
Is that my live backup image of my entire server deployment?
It is your VM and not the backup image. If by mistake you delete it (though Azure makes it real hard for you to delete it but its possible), your VM is gone. If you want, you can take a backup of this and store it in some other place. Search for Create Azure Virtual Machine Images and you will find ample resources.
If so where can I see how often it backs up?
By default Azure keeps 2 extra copies (a total of 3 including the main) of it in the data center and if you have enabled geo-redundancy, then Azure keeps additional 3 copies in a separate datacenter. However please keep in mind that it is not a backup. Any changes you make to your VM are replicated to all the copies. You would need to come up with your backup approach.
My recommendation would be to read more about Azure Virtual Machines. I'm sure if you search for it, you will get plentiful of resources.
I cannot for the life of me delete a storage account created earlier today. The error i'm getting is: Storage account portalvhds09kzndhjw5ncq has container(s) which have an active image and/or disk artifacts. Ensure those artifacts are removed from the image repository before deleting this storage account.
So I've done what all the google search results suggest, which is go to the VM's "tab", click disks and remove any disks (there aren't any), I've also looked at the images page of the storage tab and there's nothing there either. I've got no storage containers, and no blobs.
So I really can't understand why i'm getting the above error and I was hoping someone here might be able to help me.
Happy to provide more information, but I don't know what else to give at this point!
Thanks,
Simon
The container was probably used to house a virtual machine hard drive as blob storage.
If you just deleted a virtual machine then give it a few minutes for the disks to be deleted. The last time I did it, it took Azure 10-15 minutes to delete the virtual machine and remove all leases.
I had two VMs running in azure and went over my free limit for this month. I enabled the ability to charge my account and found they were gone.
The VM disks are still there but the VMs themselves have been made into hosted services. To recreate the VM I deleted the hosted service, then went to the create new VM dialog like I've seen others post previously. Under the "create from disk" option I do not see either of my OS disks as options to create a VM. Is this the right way to recreate VMs or am I missing something?
Also of note, the disks still show up as attached to the deleted VMs in the portal.
As you mentioned that your OS VHD still shows connected with deleted VM, you would need to take care that first. You can run the BreakLease.ps1 Powershell script in this forum discussion to remove the lease first and then use the Os disk VHD to create a new OS Image. Finally you can use the new OS image to create your new Virtual machine.
Alternatively if you just want to reuse the same OS disk vhd to create a new virtual machine, you can follow the blog below and look for section at the bottom "To reuse the OS VHD blob to create OS Image" to copy the blocked OS blob into a new blob and then use it:
Using OS disk VHD to create a new Virtual Machine if OS VHD is still on lease in Windows Azure Virtual Machines