Microsoft Azure Backup job failing to backup the C: drive with on-premise Windows Server 2019

Thomas Beck 1

Hello,

I am having trouble setting up the Azure Backup of a on-premise Windows Server 2019. While the D: drive can be backed-up without any trouble, the C: drive fails backing-up correctly with a "Job Failed." error (on the on-premise server side); the error being "Microsoft Azure Recovery Services Agent has detected inconsistencies while verifying the latest backup. A new recovery point could not be created." on the Azure portal.

The MARS agent version on the Windows Server 2019 is 2.0.9190.0, Windows Server is up-to-date with latest updates, it has .NET 4.8, Windows Powershell, MMC 3.0.

Up to now, the C: drive backup failed twice initially, then succeeded once for a complete backup; and kept failing ever since.

Some log files are present in the C:\Program Files\Microsoft Azure Recovery Services Agent\Temp indicating some files are causing problems with the "DATA FAILURE 0x80070002" error code. So, I excluded these files (mainly C:\Windows\WinSxS and Avast anti-virus installation path); but the job is still failing.

Would you have any suggestion as to why the job is failing on the C: drive?
Thanks and regards,
Thomas.

SadiqhAhmed-MSFT 44,591 Reputation points Microsoft Employee

2020-09-04T14:26:05.207+00:00

@Thomas Beck Sorry for the painful experience.

Please exclude the following folders from anti-virus software:

Cbengine process -C:\Program Files\Microsoft Azure Recovery Services Agent\bin\cbengine.exe"

Exclude MARS folder - C:\Program Files\Microsoft Azure Recovery Services Agent

Scratch folder - C:\Program Files\Microsoft Azure Recovery Services Agent

Also, change the backup schedule to see if that works.
SadiqhAhmed-MSFT 44,591 Reputation points Microsoft Employee

2020-09-07T06:30:55.27+00:00

@Thomas Beck Have you had a chance to see the previous response? If the suggestions were helpful, click “Accept Answer” and Up-Vote. Feel free to reach out to us if you've additional questions in this regard.
Thomas Beck 1 Reputation point

2020-09-07T08:17:56.053+00:00

Hi @SadiqhAhmed-MSFT and thank you for your prompt response.

I was waiting for the backup to complete in order to see if it worked. Unfortunately, excluding these folders from the antivirus did not help and the job is still failing.

Would you have any other suggestion?
Thanks in advance.
SadiqhAhmed-MSFT 44,591 Reputation points Microsoft Employee

2020-09-07T10:04:35.557+00:00

@Thomas Beck Thanks for the reply. IMO, the next step that I would think of, is to re-register the server. Uninstall backup agent, then start fresh installation just like a new server, if possible. If 'Not' I would recommend you reach out to Azure technical support team by raising a support request. The support professionals will work with you directly and investigate the issue and help fix it.

Let me know if you have any limitations on your support plan for raising a technical support ticket.
SadiqhAhmed-MSFT 44,591 Reputation points Microsoft Employee

2020-09-08T12:06:14.717+00:00

@Thomas Beck Any progress on this issue?
Thomas Beck 1 Reputation point

2020-09-08T15:03:24.583+00:00

@SadiqhAhmed-MSFT thanks for your answer.

I currently do not have a paid Azure account (using the free trial) so it seems I cannot open an Azure technical support ticket (which is unfortunate, as I can't try this service out if it is not working...). I just remarked that my C: drive was getting a little crowded and there was a bit more than 3Gb left on it. I am currently trying to resize the C: drive partition to make it bigger and see if that solves the problem.
SadiqhAhmed-MSFT 44,591 Reputation points Microsoft Employee

2020-09-08T15:51:36.587+00:00

@Thomas Beck Let me know if resizing C: drive helps resolving this issue. If not, send mail to AzCommunity [at] microsoft dot com with subject: "ATTN: Sadiqh Ahmed" include your Azure subscription ID and a link to this forum thread (for context).
Thomas Beck 1 Reputation point

2020-09-09T07:14:12.897+00:00

@SadiqhAhmed-MSFT Thank you, I will let you know and do what you suggested otherwise.
Ben Weston 1 Reputation point

2020-09-21T16:25:51.433+00:00

Interestingly, we've been having issues with the following -

DPM could not create online recovery point for some of the required files for this data source. This could be because of intermittent failures or if the file type is unsupported.
Number of files that failed during online recovery point creation: 0
Next online recovery point creation job will try to backup these files again. (ID 33415)

Only since updating to Mars Agent 2.0.9190.0 on DPM 2019 Windows 2016.

Could there be some issues with this Mars Agent I wonder?
Ben Weston 1 Reputation point

2020-09-21T16:44:39.947+00:00

Just noticed there is now a 2.0.9195.0 - time to try that and hope its the fix
Ben Weston 1 Reputation point

2020-10-19T07:51:08.707+00:00

Forgot to come back and say - the new agent version solved our problem.

1 answer

SadiqhAhmed-MSFT 44,591 Reputation points Microsoft Employee

2020-10-16T20:16:54.617+00:00
Sharing workaround that fixed the issue for now.

Removed the C: drive from the Azure backup, and just selected one folder from C: drive (the inetpub folder ) => this backup works on Azure

Created a local backup schedule from the Windows Server Backup tool from drive C: on drive D:

The drive D: is fully backed up using the Azure Backup tool. => this is working fine with the Azure backup.

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.
Please sign in to rate this answer.
Ben Weston 1 Reputation point

2020-10-19T07:50:14.623+00:00

Updating to the 2.0.9195.0 agent was the fix for us. There was clearly an issue with 2.0.9190.0.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Microsoft Azure Backup job failing to backup the C: drive with on-premise Windows Server 2019

1 answer

Your answer