Need help with recovering my Azure system state to a new server

Escalate the existing Azure case to the highest severity allowed by your support plan, request Phone contact, and state that production is completely unavailable and that an interactive troubleshooting session is required.

Escalate the existing ticket

1. In the Azure portal, open Help + support → All support requests, then select the existing request.
2. Select Change severity:
   • If no engineer is assigned, choose the highest severity available and select Change.
   • If an engineer is assigned, select OK, then use New message to request the severity change.
   • If the assigned engineer is unavailable and the change is urgent, Microsoft documents that customer service is available at all hours to request a severity change. The maximum severity available depends on your support plan.^1^
3. In New message, send a concise escalation such as:

   Production outage: the office cannot operate. System State recovery to an alternate Windows Server is failing. Please raise this case to the highest eligible severity and assign an Azure Backup/MARS recovery engineer. Phone contact is required at [availability/time zone]. Please arrange an interactive screen-sharing session if available. Errors, timestamps, recovery-point details, source/target OS versions, and logs are attached.

4. Verify that the case’s preferred contact method is Phone, your telephone number and time zone are correct, and your availability reflects whether you can work continuously. Azure support cases allow phone as the preferred contact method; response time and maximum severity depend on the support plan and region.^2^
5. Select Advanced diagnostic information → Yes if organizational policy permits it. Then select Upload file and attach:
   • Exact error messages and codes
   • Screenshots
   • MARS/Windows Server Backup logs
   • Source and target Windows Server versions
   • Recovery point selected
   • Time of each failed attempt, including time zone
   Existing cases accept up to five uploaded files; package additional material into a ZIP and exclude confidential data.^1^

Phone contact can be requested, but the documentation does not guarantee that every case will include screen sharing. Ask the assigned engineer explicitly when contact is established.

If the portal does not offer an appropriate technical severity or phone option, the likely constraint is the selected support plan. Technical support requires an eligible plan, and managing the request requires Owner, Contributor, or Support Request Contributor at subscription scope.^2^

Confirm that this is Azure Backup, not Azure Site Recovery

“System State” recovery from a Recovery Services vault is an Azure Backup/MARS agent operation. Azure Site Recovery is a different service used for replicated-machine failover. In the ticket, select Azure Backup and identify MARS agent/System State recovery if that is how the backup was created; selecting Azure Site Recovery could route the case to the wrong team.

Supported alternate-server System State recovery

If this is a MARS System State backup, Microsoft’s documented process has two phases: recover System State as files, then apply those files using Windows Server Backup.^3^

On the target server:

1. Install the latest MARS agent.
2. Register the target and confirm that both source and target are registered with the same Recovery Services vault.
3. Open Microsoft Azure Backup → Recover Data → Another server.
4. Supply a current vault credentials file. If it is expired or invalid, download a new one from that vault.
5. Select the unavailable source server.
6. Select System State, then choose the recovery date and recovery point.
7. Choose a destination and start Recover.
8. Copy the resulting WindowsImageBackup directory to the root of a non-system volume, for example:

      D:\WindowsImageBackup
   

9. Open Windows Server Backup → Local Backup → Recover.
10. Select A backup stored in another location:
    • Choose Local drives for D:\WindowsImageBackup.
    • Choose Remote shared folder if the recovered directory remains on another server.
11. Select and apply the recovered System State.

The target cannot run an earlier Windows Server version than the source backup—for example, a Server 2016 backup cannot be restored to Server 2012 R2.^3^

Do not repeatedly apply System State while the failure remains unidentified. Preserve the current recovered files and provide the exact error code and the stage that fails—MARS file recovery or Windows Server Backup application—to the assigned engineer.

References

1. Manage an Azure support request
2. Create an Azure support request
3. Restore System State to Windows Server