How to add a Public IP address to Azure VM (for VM failed over using ASR)

If your Connect button is grayed out and you are not connected to Azure via an Express Route or Site-to-Site VPN connection, then for ARM (based deployment model) add a Public IP on the Network interface of the virtual machine as shown below: If the deployment model is Classic, then add an endpoint on public port…

0

Unable to connect/RDP/SSH to the failed-over VM (using Azure Site Recovery)

Unable to connect/RDP/SSH to the failed over virtual machine Is Connect button grayed out on the virtual machine? If your Connect button is grayed out and you are not connected to Azure via an Express Route or Site-to-Site VPN connection then for ARM (Resource Manager deployment model) add a Public IP on the Network interface of…

0

[Limited Preview] Troubleshooting Backup/Restore failures when using Azure Files Backup

Azure File Backup (for backing up Azure Files Share) is currently in Limited Preview release. To sign up for this limited preview, send mail to askazurebackupteam AT microsoft DOT com with your Subscription Id. To troubleshoot common issues related to Azure File Backup refer to the symptoms and recommendations listed below.  If your issue is…

0

Updating Azure Backup agents

This article describes how you can use the Azure portal to identify servers with older versions of Azure Backup agent that rely on the soon-to-be-retired ACS authentication mechanisms to connect with Azure, and further update them. The article has two sections that would help you achieve the following tasks: Identify servers with earlier versions of…

0

Troubleshooting Backup failures when using Microsoft Azure Recovery Services Agent

This article describes the top Symptoms, Cause and Resolution that occur during Backup Operation when using Microsoft Azure Recovery Services Agent (MARS Agent) for taking Files and Folders backup (or backups using Microsoft Azure Backup Server).  The following article covers these top symptoms and its resolutions: Scheduled backup not working The Microsoft Azure Recovery Service…

0

Troubleshooting ‘No latest App Consistent Snapshot’ issues for Hyper-V to Azure when using Azure Site Recovery

An app-consistent snapshot is a point-in-time snapshot of the application data inside the VM. Volume Shadow Copy Service (VSS) ensures that app on the VM are in a consistent state when the snapshot is taken.  This article details some of the common causes for No latest App Consistent Snapshot issue for Hyper-V to Azure when…

0

The backup could not be started because of an unexpected error in virtual disk service (0x80070057) (0x086C6)

This article describes the symptoms, cause and resolution for an issue that occurs on MARS Agent installations within Azure Virtual Machines. Symptoms Scheduled or adhoc backups on the MARS Agent installed in Azure Virtual Machines fail with the following error: The backup could not be started because of an unexpected error in the virtual disk…

0

Troubleshooting Hyper-V to Azure Replication Issues when using Azure Site Recovery

This article details some of the more common error messages encountered when replicating on-premises Hyper-V virtual machines using Azure Site Recovery and explains in detail the troubleshooting steps to resolve them. Enable protection failed Ensure your configuration adheres to support matrix (supported/not-supported configurations) and prerequisites recommended for Hyper-v to Azure. Ensure Hyper-V host prerequisites are…

0

Troubleshooting ‘No latest App Consistent Snapshot’ issues for VMWare to Azure when using Azure Site Recovery

An app-consistent snapshot is a point-in-time snapshot of the application data inside the VM. Volume Shadow Copy Service (VSS) ensures that app on the VM are in a consistent state when the snapshot is taken.  This article details some of the common causes for No latest App Consistent Snapshot issue for VMWare to Azure when…

0

Replication Stuck? Replication not Progressing?

Check the following on SOURCE MACHINE: Check connectivity between Source Server-to-Configuration/Process server. Check port 443 on Source machine for outbound connectivity to Config server and port 9443 on Source machine for outbound connectivity to Process Server. From Source machine, use telnet (instead of PING) to connect to a config Server and Process server IP address using port…

0