Microsoft Azure Recovery Services Agent has detected inconsistencies while verifying the latest backup.

Kobbi 0 Reputation points

I have this one machine running Win10 that gets this error every time it tries to do a backup:

	Microsoft Azure Recovery Services Agent has detected inconsistencies while verifying the latest backup. A new recovery point could not be created.

Recommended action(s)
	The next backup will attempt to transfer the data again. If the issue persists, contact Microsoft support

Win 10 is fully updated.

Newest version of the MARSA agent.

list of directories trying to backup:

  • C:\Users\Brynjar\Contacts\
  • C:\Users\Brynjar\Desktop\
  • C:\Users\Brynjar\Documents\
  • C:\Users\Brynjar\Downloads\
  • C:\Users\Brynjar\Favorites\
  • C:\Users\Brynjar\Pictures\
  • C:\Users\Brynjar\Videos\

I have tried deleting it from Azure and setting it up again but get the same problem.

This is working fine on other machines at the same location.

Do you have any ideas to solve this?

Azure Backup
Azure Backup
An Azure backup service that provides built-in management at scale.
1,140 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. SadiqhAhmed-MSFT 38,891 Reputation points Microsoft Employee

    @Kobbi Thank you for reaching out to us!

    This error message indicates that the latest backup has inconsistencies and cannot be verified. To resolve this issue, you can try the following steps:

    1. Check if the latest version of the Backup agent is installed<sup>.</sup>
    2. Check if the cache folder (also referred to as scratch folder) is correctly configured, has the necessary prerequisites, and has unrestricted access<sup>.</sup>
    3. Increase the shadow copy storage space on the protected volume using vssadmin<sup>.</sup>

    If tis is Mabs server follow below steps:

    1. Verify that the automatic consistency check option in the Protection Group Wizard is turned on
    2. Check for space-related issues in the DPM storage pool on the DPM/Microsoft Azure Backup Server, and allocate storage as required<sup>.</sup>
    3. Check the state of the Volume Shadow Copy Service on the protected server. If it's in a disabled state, set it to start manually. Start the service on the server. Then go back to the DPM/Microsoft Azure Backup Server console, and start the sync with the consistency check job<sup>.</sup> Let us know If the issue persists!

    If the response helped, do "Accept Answer" and up-vote it