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.
Related
I'm aware I can now do this through the portal in the storage blade however the account I need to migrate is a production account. It's just blobs, tables and queues, no VMs.
I can stomach some downtime (say an hour or 2) but am unsure how long it would take to migrate approx 750GB, does anyone have experience with the migration and an idea on the time it takes based on a similar volume size?
I also assume once migrated all my storage keys will change so I will need to update all the references in my app settings.
For anyone else wondering about this what #4c74356b41 said appears to be true.
Thanks to this post and the PowerShell command, couldn't get the ARM template to dpeloy at least not from VS, I was able to create a classic storage account. Didn't think this was still possible!
I then kicked off a 50k files container copy from another storage account in the Azure Storage Explorer container into this new classic resource and then while that was running ran the full migration including commit and the file copy carried on regardless.
Final step was to move the new resource (file copy is still ongoing at this point) from the migrated resource group back into the same resource group as the original classic storage account.
Once the move was complete the file copy was still going smoothly and all the Keys remained unchanged so this does seem to be truly seamless.
I have a storage account with over 600k blobs.
I want to move them to another storage account, in a different region.
After googling I found someone recommending "Azure storage explorer". When I tried it, it was extremely slow. It looked like it was going to take about a week to transfer them all, but then after 24 hours, it has cancelled the copy and I can see no option to restart it.
Is there a fast and convenient way of moving a large number of blobs from one storage account, in one region, to another storage account, in another region?
You are looking for the command,
azcopy
Example,
azcopy cp "https://<source-storage-account-name>.blob.core.windows.net/<container-name>/<blob-path>?<SAS-token>" "https://<destination-storage-account-name>.blob.core.windows.net/<container-name>/<blob-path>"
Read more here
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.
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.
I mistakenly created a VM without linking it to an extant storage account. When I realized my mistake I deleted the VM and then sought to delete the storage account. I found the auto created storage account and attempted to remove the container. However even 24 hours later I get told that the container contains resources in use by the (now deleted) VM and so cannot be deleted.
Clearly there is some kind of dependency which is not apparent from the management portal which needs to be removed. I am looking for some advice on a powershell approach to investigating and resolving this issue.
You have to disassociate the disk with the VM image (VHD) before you can delete the blob or container.
You can do so from the Windows Azure management portal. Go to the VMs tab. Choose 'DISKS' from the top menu and remove it. If I remember well, it will also ask you whether you'd also like to delete the blob (VHD) from the storage account.