I don't know how I had two virtual machines in Windows Azure, one application server that was stopped and one running database server, and all of a sudden, the machines no longer exist.
I have these questions:
is there a way to restore the machines?
if not is there a way to delete the storage?
Go to Virtual Machines.
Click on Disks.
Click on any remaining disks.
Click on Delete Disk - there is an option to "retain", so make sure you choose delete.
Once all the disks are deleted, then delete the storage container.
You can delete the storage with the help of steps specified in the below post
Follow this post steps
You may have hit a billing limit for a subscription with a limit. This typically happens with MSDN and Trial accounts. Once the limit is hit, Microsoft deletes any VMs running in the subscription. For IaaS VMs the actual disks still exist in storage and the VMs can be rehydrated from there once the account has some money in it or the monthly limit is reset by a new month starting. For PaaS instances, the package and configuration file is presumably still deployed to Windows Azure so, again, the service can be rehydrated when the account is flush with money.
Related
I am testing out Azure VMs as a disaster recovery option for my organization. I'm on an Azure AD trial. My use case is this: Ideally, I'd like to have an image standing by with all the software that my users need, pre-installed, and hooked up to our Azure AD domain. Then, if we should need our DR environment, I'd like to spin up 1..n VMs from the image, send my users the RDP connection files, have them log in with their Office 365 credentials (we also subscribe to Azure AD Premium P1), and get back to work using OneDrive.
I created a VM and populated it with the settings and software I need for my users. It has a local admin, and I confirmed I could log in using my Azure AD credentials. Then I ran sysprep /generalize and created an image of the virtual workstation. So far so good. As I could no longer access the original VM, I deleted it. The original VM was of the DS3_v2 size.
Now I'm going to create a new VM from my image to test. In the Azure portal, I go to Virtual Machines -> Add. I select my image and Resource Group. However, when I go to select a Size, I get the following error message:
"4 vCPUs are needed for this configuration, but only 0 vCPUs (of 4) remain for the Standard DSv2 Family vCPUs." I cannot select any of the available options. The "Troubleshoot" link directs me to a page instructing me to request a quota increase, but that shouldn't be necessary; I de-allocated [edit: deleted] the old VM and its 4 vCPUs so I could create a new one. Why is Azure telling me I only have 0 vCPUs left in my trial subscription?
This morning when I tried again, the console allowed me to select a size. It appears that there is a very substantial delay between when you delete the VM and when Azure marks the vCPUs as available to use once again.
I am just exploring Azure and I made a Virtual Machine using the portal and I deleted that after two hours or something.
In my cost management I can see that I am still paying for that resource group that contained components of the Virtual Machine, it is been a week since I deleted it.
I am still paying for that resource group even though I can't see it in my resource groups, neither on the portal nor on Powershell.
Is this a common issue?
As per this doc, I suggest you check if all disks attached to the vm are not deleted.
For managed disk, please follow this to find and delete them.
For Unmanaged disks(the vhd files stored in azure blob storage), please follow this to find and delete them.
Delete any orphaned Network Interface Cards (NIC) and Public IPs that were associated with the VM. They are billed even when the VM is deleted.
Update:
run powershell in azure portal:
I've "Visual Studio Enterprise" azure subscription. I initially got few credits. I think it was $200 for free. Earlier it used to show static remaining credit i.e. if I built two VMs and it cost $50 it would show $150. But since few days may be just past day remaining credit is continuously reducing.
The activities I have done so far. Earlier I was unable to connect to VM as outgoing connection was not allowed from my organisation. Since I have got permission I'm able to connect. After that I installed Active Directory Services on one of the VM.
I don't think till this step my credit amount got reduced except for the VMs I built.
I was trying to start and stop the VM using powershell but I wasn't able to do so. So I installed powershell azure modules. using Connect-AzAccount to connect and then used Start-AzVM and Stop-AzVm to start and stop the VMs. Just to clarify I keep the VMs in shut down mode so I don't keep getting billed.
Still the amount is being deducted. I ran Disconnect-AzAccount on suspicion that it might be causing the issue but still it hasn't fixed the issue.
Can any one help here?
There are mainly two ways to stop VM:
Stop the Azure VM locally: When you connect to the Azure VM with remote desktop, go to the Power options within Windows and select Shutdown, this will essentially “turn off” the VM and stop it from running. However, even though the VM won’t be running you WILL still be paying for the Virtual machine hardware allocation. Doing this will cause the Azure Portal to report the status of the VM to be “Stopped”.
Another way is to click Stop in the virtual machine page on the portal(or use Azure PowerShell or Azure CLI). Instead of just shutting down the Operating System, Azure will also deallocate the hardware (CPU and Memory) allocation. Doing this will cause the Azure Portal to report the status of the VM to be “Stopped (Deallocated)”.
Overall, both methods will reduce cost but not none of cost. You do still pay for the Azure Storage account usage, which is used for storig the VM’s .vhd disk image file. As a result, you will still incur some cost for the storage, but at least you will save on the VM resources.
Ref: Properly Shutdown Azure VM to Save Money
You need to identify what resource are been billed when VM is stopped or Stopped De-allocated.
Check the Cost analysis under Cost Management to identify the resource. Note that when VM is stopped you still pay for storage and other resources depending in your setup.
I have a premium Azure Managed Disk (SSD) in the same region as a Windows VM, but when I go to attach it via the Azure portal (settings -> Disks -> + Add data disk) the drop down under name says "No managed disk available" (see below). What do I need to do?
To use Premium storage, you'll need a Premium Storage enabled VM size like the DS-series or GS-series virtual machine. You cannot use premium storage disks with VM series that are not Premium Storage-compatible. For details, see Premium Storage: High-Performance Storage for Azure Virtual Machine Workloads.
I ran into this problem after I had detached a disk from one VM and tried to attach it to another VM. Apparently those changes take some time to propagate through the system, and the solution for me was to log out of the Azure portal and then log back in again.
It's a 3 step process, once you create & attach, you need to mount it as well.
Follow the instructions presented here.
lsblk -o NAME,HCTL,SIZE,MOUNTPOINT | grep -i "sd"
This command will show you if you have the disk or not.
Before:
After:
I faced the same problem and it turned to be because I had chosen the incorrect resource group. Under Basics tab, you need to check the resource group where the Disk belongs to and make the appropriate selection. This solved the problem for me.
I faced the same problem, and I checked so many times if the vm would support premium LRS and mine did, but still not seeing the disk I just created.
I solved it by just refreshing the whole portal after creating snapshot disk, and then every disk that I can possibly attached shows up.
I faced the same problem, and I checked so many times if the vm would support premium LRS and mine did, but still not seeing the disk I just created. Also tried to refresh the whole portal but still issue didn't fixed. After that i checked my disk was not created in availability zone. And my VM was in availability zone 1. once i created the disk in availability 1. it appeared in my new VM data disk.
I have been doing some test and realized that when I stop a VM, I get a red warning saying that it still generates charges.
But on which basis ?
Furthermore, on some VM I created, the system without any reason starts fooling and reach a 98% CPU during several hours with no way to stop it or to connect with RDP. VM was totally dead and it's only after several hours that the stop command from the control panel succeeded.
Hope I will not been charged for this ? Who is able to decide if my VM is OK or fooling like a crazy horse ?
Moreover, is there any software allowing to transfer my VMs from Azure to my local system, and delete them on Azure to stop any charge ? for a simple backup with possibility to restore/restart them later ? Or to run them in my own hyper-V ?
Best regards
CS
Even if your VM is stopped, you still have resources that have been reserved for your VM (think of storage space, memory, CPU, ...) and these can't be 'sold' to anyone else. Deleting the VM will free these resoures and you'll no longer be charged.
Remember that Virtual Machines are still in preview, meaning things can go bad sometimes. And yes you'll be charged for this, but during the preview you get a 33% discount (more info here: https://www.windowsazure.com/en-us/pricing/details/).
The persistent disks of your VMs are stored in a storage account as page blobs. Using tools like Azure Storage Explorer, CloudXplorer, CloudBerry, ... you can download these VHD files and simply mount them in Hyper-V (You'll need to remember that you'll need a license if you want to run the machine on-premises).
Note that, if you simply delete the VM the disks won't be deleted (they will stay in your storage account). In that case you only pay for storage (which is very cheap).
The price of VM depends on their size and nature (prenium or not).
Also you have to pay for the storage, but a 120GB disks is not billed fully, only effectively used space is.
You can use IaaS Managament Studio to easily calculate how much your blob disk cost, and see links to pricing pages of azure.