When I try to register the Azure Backup Agent from my Windows 7 machine, the following error appear:
The Microsoft Azure Recovery Services Agent cannot connect to the OBEngine service. (ID: 100052)
Verify that the OBEngine service is present in the Services Control Panel and that the port 6049 is available.
I've checked that the service is running and the port is available.
Any suggestions?
I run into this error many times when my DPM online recovery points attempt to run. I believe they fail because other backup jobs (like disk-to-disk jobs) are still running on the same protected data sources. So the online recovery points start while another backup is already running and it fails. This causes the OBENGINE service to falter and get stuck. I have had good luck with spreading out my backup job schedules within my protection groups. For instance, my disk-to-disk backups run in the latePM/earlyAM. My Online Recovery Points run during the work day, lateAM/earlyPM.
If I find some online backups failed with error:
The Microsoft Azure Recovery Services Agent cannot connect to the OBEngine service. (ID: 100052)
...I first look to see if any backups are running. If not, I restart the OBENGINE service. When you look in services, this is the "Microsoft Azure Recovery Services Agent" which is running obengine.exe. Here is a good command to restart this service, which you can run on your DPM server in a command prompt or in PowerShell:
net stop obengine && net stop obengine
After restarting the service, restart the online recovery point jobs that failed. However it is likely your jobs may fail again tomorrow, so get those schedules spread out.
Related
Background:
Now I use an Azure Automation to shutdown the Azure Vms,
but I met a problem last time when one VM had been shutdown form the Azure portal
when it was restarting after the applied patch and the result was the VM could not start again.
I want to find if there has a script that can check if the VM is restart/start/shutdown when I shut down the VM from Azure Portal.
Thanks in ad
You can use Azure Automation to schedule all your Start/Stop/Restart jobs. If ever, you need to check when and how your VMs have been restarted and by whom, you could check the Log history from the portal, inside your VM's sections. To automate the display of this using a script, you could use a simple runbook that queries the tables from the access logs of your VM, and triggers an action of your choice...
I hope this could help you resolve your issue :)
Rougly what im trying to do is:
Start VM automaticly(already doing this with Azure Automation)
Have the VM run an application(it already auto runs on startup) This is where the problem is, since the app runs fine when the VM is started manually with RDP, but is not run when the VM is started automaticly with Azure automation.
Stop VM (already doing this with Azure Automation)
All this must happend automaticly in the cloud so i dont have to do it manually trough the RDP sever application
i have an Azure VM that auto runs a console application on startup, this app do some work and then upload some files to my Azure storage. This console application needs to be run once a day, so im thinking that ill use the Azure Automation Account to auto start/stop it once every day, which i did and its working fine, atleast i can see the VM change status on the Azure portal at the specified times, however the files are not being pushed from my console application to my Azure storage when.
First question question is, do the Automation Account auto start of VM just make the VM avalible for use, and doesnt infact turn the OS on?
This would explain why the console application which should run auto on startup arent being run and therefor not pushing files.
Second question. If this is the case, how do i run my Azure VM without running the RDP manually aka somewhere in the cloud?
Normally it wouldnt be that big an issue for me to run the RDP myself once a day, but if i could automate it that would be ideal. Also when im traveling its not allways possible for me to get good enough internet access, and the VMs console application file pushing is vital for a website and a Xamarin Android app im managing, so its not something i can allow to "skip" sometimes whenever inconvenient.
There is so much wrong in this question that I don't even know where to start.
First of all, if you need to run something once a day, why not use Azure Automation, Azure Functions, etc?
Second, you cannot turn on VM but not turn on OS. how do you even suppose this might happen.
My thoughts - you configured your app to run on user login, not on startup, or the scheduled task doesn't run when the user is not logged in.
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.
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.
I have a program that I run only 1-2 hours a day. Is there a way to suspend the Azure server so I don't pay for it, then resume it later? How fast is it to suspend and then resume?
To clarify here, Azure no longer charges for stopped VMs. The billing change was announced in 2013 on Scott Guthrie's blog: No Charge for Stopped VMs.
This means you can use the portal or APIs to stop a VM without deallocating the resource - and avoid charges at the same time.
Not sure if you are asking for Window Azure Cloud Services or for Windows Azure Virtual Machines but you sure can stop/start these Azure Virtual Machines directly on Windows Portal or using Powershell or REST based Service Management API. The Windows Azure Portal does not provide a way to schedule stop/restart so you will have to manually do it by yourself or use some 3rd party service i.e. AzureWatch etc to do it.
Note: Even if you shutdown the Virtual Machine or Cloud Service, you will still pay for if you want to do it for cost saving, then you would need to delete the service or VM. Reboot/Restart does not take long as VM is already configured and ready to run so it is just the time to turn on a pre-configured VM.
If you want to use REST API in your own application to stop/start here is some help:
Virtual Machines: http://msdn.microsoft.com/en-us/library/windowsazure/jj157206.aspx
Cloud Service: http://msdn.microsoft.com/en-us/library/windowsazure/gg441298.aspx
If you want to use Powershell to stop/Start Azure VM look for "Start-AzureVM" and "Stop-AzureVM" cmdlet below:
http://msdn.microsoft.com/en-us/library/windowsazure/jj152841.aspx
To save money, I did Remote Desktop to my Azure Windows VM, and clicked shutdown.
Then, at my Azure dashboard (https://manage.windowsazure.com) > VIRTUAL MACHINES > STATUS it changed from Running to Stopped.
But then I read this doesn't stop the billing.
So I went to Microsoft Azure > Virtual machines (classic) >
and saw the status was Stopped. But this doesn't mean billing stopped.
I clicked the "stop" command, and it changed to Stopped (deallocated) which means no (or near 0) billing.
The screenshot says it all... so only a "deallocated" VM won't be billed!
One more thing to add. As opposed to a deleted VM, a deallocated VM still has virtual disks attached to it which consume storage space and therefor creates costs.
If you mean the "suspended" state you can achieve with your computer I don't think is available today on Azure.
Google Cloud for example has just released that feature on beta https://cloud.google.com/compute/docs/instances/suspending-an-instance