Full volume restore using MARS console stuck at Estimating size of Backup items...

Question

Full volume restore using MARS console stuck at Estimating size of Backup items...

FCQ 0

Hi, I've been attempting to start a full volume recovery from MARS, however it has been stuck at "Estimating size of Backup items..." for 24 hours and I believe there is nothing currently in progress.

Stuck cancelling

Additionally, on the Backup jobs blade in portal.azure.com it appears as the restore is still running:

Running jobs

For context, the full backup is around 2.68TB, and about 600k files.

There are no logs on the Windows Event Viewer computer where MARS is running.

Could someone please point me to the right direction to further troubleshoot this?

FCQ 0 Reputation points

2026-05-05T00:11:42.39+00:00

Hi, once again I'm stuck after trying to mount a snapshot:

However this never ends, G: drive is mounted but inaccessible:

A corruption was discovered in the file system structure on volume G:.

A file system index structure contains entries that violate ordering rules. The file reference number is 0x5000000000005. The name of the file is "<unable to determine file name>". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".

It has been like this for more than 12 hours.

Please assist this is urgent.

2 answers

Your answer

FCQ 0 Reputation points

2026-05-05T00:11:42.39+00:00

Hi, once again I'm stuck after trying to mount a snapshot:

However this never ends, G: drive is mounted but inaccessible:

A corruption was discovered in the file system structure on volume G:.

A file system index structure contains entries that violate ordering rules. The file reference number is 0x5000000000005. The name of the file is "<unable to determine file name>". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".

It has been like this for more than 12 hours.

Please assist this is urgent.

Answer 1

Hi, once again I'm stuck after trying to mount a snapshot:
User's image

However this never ends, G: drive is mounted but inaccessible:

A corruption was discovered in the file system structure on volume G:.

A file system index structure contains entries that violate ordering rules. The file reference number is 0x5000000000005. The name of the file is "<unable to determine file name>". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".

It has been like this for more than 12 hours.

Please assist this is urgent.

Answer 2

Sadiqh Ahmed 49,566 Microsoft External Staff Moderator

Hello @FCQ Thank you for contacting us through Microsoft Q&A platform. Sorry for the inconvenience caused to you!

It sounds like you're encountering some challenges with your Azure Backup recovery process. Please follow the suggestions below and see if this helps:

First thing, please ensure that you are running the latest version of MARS agent [Version. 2.0.929] - download it from here or from the Azure portal as mentioned in this section.

User's image

If you are already using the latest version of MARS agent, there are a few things you can try to resolve the issue:

Since you mentioned that the restore job still appears to be running in the Azure portal, try cancelling the job from there if possible. Sometimes, jobs can get stuck on the MARS agent side but still appear as running in the portal. Cancelling the job from the portal might help to resolve the issue.
If cancelling the job doesn't work or if you're unable to cancel it from the portal, try restarting the Microsoft Azure Recovery Services (MARS) agent service on the machine where it's installed. This might help to reset the agent and allow you to start a new recovery job.
Check the status of the Azure Backup Agent service:

Open the Services console on the server where the Azure Backup Agent is installed.
Verify that the service is running and set to start automatically.
- If the service is not running, start it and try the backup again

Check the status of the Volume Shadow Copy service:

Open the Services console on the server where the backup is being taken.
Verify that the Volume Shadow Copy service is running and set to start automatically.
- If the service is not running, start it and try the backup again.

If none of the above steps resolve the issue, try restarting the backup.

If the issue persists after trying these steps, you may need to contact Azure technical support for further assistance.

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

FCQ 0 Reputation points

2024-05-21T14:48:43.4866667+00:00
Hi @Sadiqh Ahmed thanks for your thorough guide, below my comments:

I'm using lates version of MARS

The cancel button is greyed out and can't be clicked on the Azure Portal

I've closed and reopened the MARS client the problem persist, I also tried restarting the computer where I'm attempting to recover the volume backup.

Please note that I see this error on the MARS console, although I don't know which logs to look at, there are no errors on the Recovery Service Vault.

4-5 the backup was already taken, the problem is when I try to recover it, and according to the Backup agent on the source system the backup snapshot was successful:

Do you have any other suggestions of what could I try, or should I contact Azure Technical support?
Sadiqh Ahmed 49,566 Reputation points Microsoft External Staff Moderator

2024-05-21T20:52:10.96+00:00
@FCQ Although you mentioned there are no logs in the Windows Event Viewer, MARS typically generates its own logs which can provide more insight into what might be causing the issue. Look for logs in the following locations:

C:\Program Files\Microsoft Azure Recovery Services Agent\Temp: Check for any log files generated by the MARS agent in this directory.

C:\Windows\Logs\Microsoft Azure Recovery Services Agent: Look for additional log files here.

If this doesn't help, then the best option would be contact Azure technical support team by raising a support request.
FCQ 0 Reputation points

2024-05-23T14:33:11.7866667+00:00

@Sadiqh Ahmed There is no Microsoft Recovery Services Agent folder on C:\Windows\Logs

However on the C:\Program Files\Microsoft Azure Recovery Services Agent\Temp I found some files:

after quickly skimming through them I didn't find any Exception or meaningful errors.

Please note I just went back to the Backup jobs blade in Azure portal and the jobs are still running

Looks like the next course of action is to log a ticket with Azure Support, however it seems I can't do that because I don't have a paid support subscription.

Any other ideas of what could I try on my own?
Sadiqh Ahmed 49,566 Reputation points Microsoft External Staff Moderator

2024-05-23T18:43:26.4566667+00:00

@FCQ The query needs deep dive technically. So, the best I recommend would be to contact Azure technical support team by raising a support ticket. The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.

Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.
FCQ 0 Reputation points

2024-05-25T00:21:14.1633333+00:00

Thanks @Sadiqh Ahmed I've sent the email with the details requested

This is crazy, the MARS agent was stopped on the 20th in the afternoon, yet the Jobs blade still says the recovery is in progress:
Sadiqh Ahmed 49,566 Reputation points Microsoft External Staff Moderator

2024-05-31T14:47:14.43+00:00

@FCQ As per support request:

File and folder recovery is successful, but the full volume recovery is failing. This is currently being investigated internally.

Share via

Full volume restore using MARS console stuck at Estimating size of Backup items...

2 answers

Your answer