I have setup Azure on W Server 2008 r2 sp1 and have configured vault etc. I am trying to do our initial upload to the cloud storage. It got to @ 96 gb and stopped. The only error I can find is 0x007E3. I have fully patched the server so don't think this is the issue. If I look on the portal storage it says there is @96 gb of data.
Any help would be appreciated.
Thanks
Bill
“The activation did not complete successfully. The Microsoft Azure Recovery Services Agent could not authenticate this server with the backup service. You must register the server again to establish the server
identity.”
Hello,
I was wondering which server workload backups are supported in Azure Backup.
Thanks!
Hi,
My azure backup was running fine until last week when I upgraded/updated the backup agent with latest. As of Saturday, backups started failing for whatever reason but I didn't notice until our Exchange Server stopped receiving emails due to low disk space. Only then I noticed that azure had four failed backup attempts and consumed drive space without ever releasing it. Cancelling the backup jobs did exactly nothing. Restart server didn't help either and re-installing the agent made it even worse as now I have no disk space and no trace of it being taken by the failed partial backups. The normal disk usage is about 30GB and the failed backups took over 70GB of the 120GB drive ( RAID1) yet I cannot locate these partial files anywhere even among system/hidden files. Even if I completely uninstall the Azure agent and remove its directory in Program Files. Now I am left with no backup and no disk space. Lovely. How do I cleanup this mess?
Thank you,
RR
I have a problem with the Vault backup since a while now (started around 22-10). The snap in reports the following error when I try to run a job manually:
"Error details: The Microsoft Azure Recovery Services Agent cannot connect to the OBEngine service. Verify that the OBEngine service is present in the Services Control Panel and that the port 6049 is available."
I read a few articles online and I noticed something has changed regarding the connection method between the server and the vault. I downloaded and installed the newest Azure client 2.0.8694.0 and downloaded a Vault Credential file. When I do the ‘register server’ I receive an error at the end stating:
"Failed to set the encryption key for secure backups. The encryption passphrase provided does not match with passphrase associated with the following server: Server.Domain.local Ensure that the encryption passphrase is configured properly."
And I am still receiving the first error when I try to manually start a back-up job. I have also deinstalled the Azure client and installed it again. I have turned off the firewall and virus scanner. I checked if the service was running, it is. I also rebooted the server. Is there anyone who can help me out? It did work fine before it just got ‘broken’ somewhere along the line.
I'm not seeing the expected behavior of Azure Backup regarding retention. Since Azure Backup is charged by the amount of data stored, we intend to keep the cost as low as possible by only storing the most recent backup. That is, we expect to only pay for the storage costs of one day's worth of recover points, which in our case will be one because we do only one backup per day. We are still performing onsite backup, and there we keep many days worth of backup recovery points.
On the Microsoft Azure Backup application's main screen, under "Destination usage" it shows "Retention: 1 days". However, I see under "Available Recovery Points" it shows "Total backups: 15", "Latest copy: 12/29/2014 4:30 AM", "Oldest copy: 12/19/2014 12:35 PM". When I visit the Recovery Services "PROTECTED ITEMS" onhttps://manage.windowsazure.com/, I see the number of "RECOVERY POINT", "NEWEST RECOVERY POINT", and "OLDEST RECOVERY POINT" shown match the same values displayed on the Microsoft Azure Backup application's main screen.
Why is Azure Backup retaining more recovery points than expected? Why is it retaining recovery points for more days than requested?
Trilon, Inc.
I'm using the latest version (2.0.8694.0) of the Microsoft Azure Backup Agent on my Windows 8.1 64-bit machine.
Backup completes with warnings and viewing the error list shows several files with CATALOG FAILURE 0x80131500. All files are on the same local USB harddrive. I cannot see any difference between files backed up succesfully and files habing issues
How to troubleshoot this issue?
Hi,
I cant seem to find much information on this.
I've been using azure backup for a little over a month now and have been adding additional data due to the volume that we want backed up.
The last few days after I added some new folders I keep getting the below error for thousands of files. I've de selected and reselected the data, I've alse restarted the service as I've seen mentioned elsewhere.
the recovery services agent I have is version 2.0.8692.0
CATALOG FAILURE 0x80131500 "x:\Location\file.xls"
Any help is appreciated.
We have installed and are using Azure Backup on a Windows Server 2008 R2 Standard and a Windows Small Business Server 2011 Standard (which is based upon the Windows Server 2008 R2 Standard kernel). Both servers complete scheduled Azure Backup jobs, but every job lists thousands upon thousands of failed files. The failed file list reports each failed file as a CATALOG FAILURE 0x80131500. Both servers have the Microsoft Azure Recovery Services Agent version 2.0.8692.0 installed.
I have attempted to install the update https://support.microsoft.com/kb/2854994, but the update fails stating "The program being upgraded may be missing or the upgrade patch updates a different version of the program."
I have installed the update http://support.microsoft.com/kb/2997692, which after running the update states "Microsoft Azure Recover Services Agent is installed and registered".
I have attempted to install the update http://support.microsoft.com/kb/2816671, but after launching the downloaded Upgrade.exe, it simple exits without any confirmation that the update succeeded or failed.
After the three updates attempts listed above, the problem is unchanged. I'm happy to share any log files; just tell me what you need to diagnose and correct this problem.
In the mean time, I've requested that Azure billing be aware we don't want to pay for a service that doesn't work, yet we need to keep using it to resolve this problem. I've been told I'll need Microsoft Technical Support to provide documentation that there was a problem, and if it turns out to be something that Microsoft had to fix. That way, we can get credit for the cost to use the Azure Backup service while it doesn't work properly.
Trilon, Inc.
Hello!
We are trying to schedule full backups of our azure VMs (i.e. System Image).
Volumes "backup & restore" system natively provided by Microsoft Azure Backup is not enough for our needs.
Assuming we don't want to set up a DPM Server to use with Azure Recovery Services, I tried the following workaround:
Backup
- Attach a new empty volume to the VM I've to backup (I'll call it F:)
- Use Windows Server Backup to create a system image, stored in F:
- Use Windows Azure Backup to backup F: contents with Azure Recovery Services
Restore
- Create a new VM
- Recover F: contents from Azure Recovery Services and...
I'm stuck right here. Any way to restore an Azure VM From a System Image?
Of course, any other simple solution to our simple need (schedule full backups of Azure VMs) is welcome.
Thank you everyone!
Riccardo Di Stefano
Hi,
My client has a requirement for us to backup files on their IaaS VMs using multiple policies/schedules.
As far as I can tell, Azure Backup only allows you to create 1 backup policy which will leave us with a gap if we only implement one of the schedules above.
Is there any way to backup to an azure backup vault (or azure files which seems cheaper, even after it comes out of preview) with multiple schedules as shown above? Our solution needs to use free (preferably micrososft) software.
Hi,
I am running Microsoft Azure Recovery Services Agent 2.0.8694.0 on a Windows Server 2008 R2 x64 Standard SP1.
The Retention Range was initially setup with 2 days. However, the Total amount of recovery points are more than the retention range. So now it's using 29GB when I only expected it to use around 14GB.
I have now changed the Retention Range to 1 day, however, it's still over on the Recovery Points I want it to have.
When will it delete the old data in the vault? Luckily I am on the Free Trial at the moment.
Thanks,
James
Bug Report:
Microsoft Azure Recovery Services Agent 2.0.8694.0
"Available Recovery Points" > View Details > "Latest Available" and "Oldest Available" are mixed up.
HI,
I am using SCDPM 2012 R2 UR4 to backup some files on premise. I created a backup vault - installed the Azure Agent on DPM (registered it), I downloaded the Azure Backup Vault credential file and provided it during registration process (it showed the correct subscription and region) and configured online backup.
The backup to azure fails with Windows Azure Backup Agent cannot connect to the OBEngine service.
I already re-started the service - no problem. No firewall locally - not sure what ports are required on outgoing company firewalls (didn't see anything in the documentation). I also created a new backup vault in azure and did the same procedure again. But the result is the same. Please does someone have any other ideas?
Hi,
I have windows 2012 R2 and DPM 2012 R2 RU 4. I configure FREE TRIAL Azure account and configured the recovery services vault. In the portal I can see my DPM server, in the DPM I can see the azure vault. When I try to add online backup to existing protection group I get the error that "Azure Backup only supports up to 0 recovery points for each data sources. The azure backup schedule you have specified exceeds the limit ( ID:33422)"
My schedule is 7 days retention period, daily backup. No matter what settings I change in the backup schedule I cannot make the online backup. Is this some limitation in the free trial or I am missing something.
I want to test my online backup solution before purchasing the service.
Please help me
Ivaylo
Hi,
I was hoping to use our windows azure account to make cloud backup of some of our PC's, they're all running Windows 7, 8 or 8.1.
I read that now azure backup support windows 7, 8 and 8.1 : https://support.microsoft.com/kb/3015072?wa=wsignin1.0
So I installed this updated package, configured a backup and tried to run it but I can't have it works it always fails: 0x1d4c2 error. I looked into the log and here is the first error that appear on the log
0B001EF0 01/0700:51:33.62270nativeutils.hpp(41)170BDAAE-9565-4632-84BA-A48F18F64C81 WARNINGFailed: Hr: = [0x80070002] : Encountered Failure: : lVal : r.Open((( HKEY ) (ULONG_PTR)((LONG)0x80000002) ), pszPath)0B002130
01/0700:51:33.67203miscellaneousutils.cpp(692)170BDAAE-9565-4632-84BA-A48F18F64C81
NORMALHr: = [0x80070002] Could not get the value of registry key name CopyBackupEnabled under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Azure Backup
Hope someone can help me figured it out ....
Thank you!
Chris
Hello,
We are using the Azure Recovery Service to backup data from our server (Windows Server 2012).
This has been done since almost 1 year now.
Since last October we experience problems in backuping data, jobs keep failing without any additional details.
I have totally reinstalled the Azure Agent on the server yesterday to see if it would change, but we still have issues.
It is quite hard to identify the issue and I would need help i that. Moreover, the backups are still billed as if data was consumed but our last recovery points is from 09.10.2014!
Thank you in advance for your help and support.