I have a azure VM. I setup the Backup in the Recovery Service vaults. Installed Windows Azure Guest Agent on VM (WindowsAzureVmAgent.2.7.1198.778.rd_art_stable.160617-1120.fre.msi), update GuestAgentStatus based on https://blogs.msdn.microsoft.com/mast/2014/04/07/install-the-vm-agent-on-an-existing-azure-vm/ . Now if I check GuestAgentStatus, I can see ProvisionGuestAgent has value.
However, once I setup backup, run it, it always failed. The error message is:
The VM Agent is not in Running State.
The recommended action is:
This is mostly because of older version of VM agent. Please update the VM agent as mentioned in the troubleshooting guide at http://go.microsoft.com/fwlink/?LinkId=800034
It also has another link: https://azure.microsoft.com/en-us/documentation/articles/backup-azure-vms-troubleshoot/
However, they do not provide solution for the same error. There is a similar error:
Could not communicate with the VM agent for snapshot status. - Ensure that VM has internet access. Also, update the VM agent as mentioned in the troubleshooting guide at http://go.microsoft.com/fwlink/?LinkId=800034
The VM agent is the latest, also, I can use its DNS RDP to the VM, there is no problem to browser website like google, etc., and no Network Security Group.
Anyone has any ideas why the backup failed? How do I check whether the VM agent is running?
Thanks
See if restarting the VM post updating the agent is solving the issue. VM agent will be listed under services running inside a Windows machine.
Related
I use Azure- windows VM for running some services, the services are very stable(after testing).
The server run one day and after that he has fallen and i get this message.
**
Diagnose and solve problems
In Activity log
Resource health
Solved
The problem was in 'Auto-shutdown' it was enabled to 'Scheduled shutdown'. you can find it under - HOME --> VM --> Auto-shutdown(under the title Operations).
From the Activity Log, we can see the Azure Lab Service initiated the VM deallocation.
When you create a Lab Service in Azure, there is an option for you to automatically shut down virtual machines when users disconnect. It's probably the reason. This could help save costs.
It's the same Lab policy when you create template VMs in the lab Account or change it later.
Does Azure deallocate end user's VM's at its own discretion?
I was using an Azure VM for a clean build and then the remote connection was dropped, I tried to reconnect by RDP and found out the machine was deallocated.
The info from Microsoft was:
Connect is disabled because this virtual machine is deallocated.
I did not know that Azure took machines away like that?
I would be hesitant to use Azure VM's in the future for build work.
Azure does not de-allocate your VM. There are numerous reasons you VM might be de-allocated while you are using it, below are a few;
Like #david mentioned in comment, you ran out of credit
Shared subscription, someone that also has access to you subscription shutdown VM
Automation, VM is set to shutdown at a certain time
These a just a few reason why you vm might have de-allocated while you are using it. If you can't determine on your own why it shutdown you can file a support ticket with Azure support.
Hope this helps.
Check if your appropriate resource group is enabled:
Open Azure portal.
Navigate to the Subscriptions.
Search for the necessary subscription group. enable it.
By default, there is a scheduled shutdown on Azure. If you go to operations settings in the left panel of the Azure VM portal, there is an auto-shutdown. You need to disable it so that your VM won't shutdown at the scheduled time.
Azure VM machine might be in stopped mode so it is saying that error message, please check the Azure VM list and see the status, accordingly start the VM, it will work
normally when you create your VM, you will see that there is a parameter that it will stop at 7pm or something like that. So After 7pm it will stop you VM. Which is good I think, because we tend to forget our VMs and then we pay for nothing. So no worries, just start your vm and you are all good to go :)
I cannot currently rdp to my Azure server. After checking the RDP endpoints were open I looked at the Boot Diagnostics and a Settings window was displayed.
Is this significant, if so how do I correct it.
Note: I created another VM based on a previous image of the problematic server and the same thing happened.
Thanks
Phil
According to your description, I had test in my lab, follow this article I had create image, and it works. Maybe there are some points need to consider:
1.run sysprep.exe, in Shutdown Options, select Shutdown. After sysprep.exe was running, we will disconnect this VM, but it does not mean this VM was stopped.
We should confirm the status of this VM, we can via portal to check the status:
2.After this VM's status is stopped, then we can click the VM and select the virtual machine you want to capture.
3.Then we can use this image to create a new VM.
You should re-capture this image.
Note:Prior to caputuring an image of an Azure virtual machine, it is recommended the target virtual machine be backed up
We have a requirement to Migrate EC2 instance of AWS to Azure as VM, have been trying to implement the same from this source,
unable to complete the process. Tried and stuck on Protection Group.
I'm looking in these other links
Migrating a VM from EC2 to Azure at 300 Mbps For this I'm able to create VM in Classis portal but unable connect to it only port 80 is active all other ports are not working
Migrate virtual machines in Amazon Web Services (AWS) to Azure with Azure Site Recovery
https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-vmware-to-azure
https://aws.amazon.com/ec2/vm-import/ on trying this I'm getting this unresolved EC2 API export to S3 ACL issue
Can anyone suggest me a workflow on how to implement this?
I achieved this by downloading AWS EC2 VHD to an Hyper-V enabled machine on-premises.
Following are the steps.
Create VM from VHD and Remove AWS related software.
Open Hyper-V manager and create VM from the downloaded VHD.
Log in to the VM and uninstalled AWS related services from control panel (AWS Drivers, EC2configService, AWS Tools for Windows, AWS SSM Agent)
All these changes were affected on the VHD.
Upload the converted VHD to Azure Storage (using the Azure PowerShell cmdlets)
Create av Azure VM-Image from that VHD in Classic Azure Portal
Create an Azure VM using the new Image.
Created a classic VM in Azure portal.
For creating a VM under Resource manager, created VHD of newly migrated VM and using that created a new VM in azure portal.
Mention any workflow other than this.
There are multiple ways to migrate machines.
Azure Migrate: Server Migration is one tool that lets you do that and is the recommended way to rehost x86 machines to Azure. You can treat the EC2 instance (AWS VM) as though it were a Physical machine and migrate it to Azure as long as the Operating System on the machine is supported by the Physical Server Migration flow (also check the kernel version to ensure it is supported) https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-physical-virtual-machines
That being said, EC2 VMs may have some changes that you’ll need to make before migrating them, or it may cause issues once in Azure. For example if they are using cloudinit for VM provisioning, you may want to disable cloudinit on the VM before replicating it because the provisioning steps performed by cloudinit on the VM maybe AWS specific and wont be valid after the migration to Azure.
The other thing to note is if the VM is a PV VM (para-virtualized) and not a HVM VM you may not be able to run it as is because paravirtualized VMs use a custom boot sequence in AWS (you may be able to get over this challenge by installing GRUB 2 on the VM and building grub)
The recommendation, if you are using this approach, is to always perform a test migration first to test the process.
I configured Windows Azure Backup on my VM hosted on Azure. I did manage to create and upload a certificate following this tutorial and this tutorial.
I downloaded the server agent to the VM and configured it, I then managed to perform a manual backup and it worked fine.
However I scheduled it to run every day at 3am using the wizard provided and it's not running. I check every day, and the last backup that is listed is the one I did manually. The dashboard in the Backup Server Agent shows it's scheduled, but it's not running.
I tried leaving the agent open overnight, and it didn't help.
Any insight on the situation will be helpful.
Thanks,
After checking my VM's event log, I figured out that the backup wasn't running as expected due to limited space in the HD. After I cleared some space it started running as expected.