Site Recovery
30 TopicsTroubleshooting - Unable to delete Recovery Services Vault?/Can't delete Azure Backup Vault?
You may receive " Vault deletion error Vault: 'Vault name' cannot be deleted as there are existing resources within the vault. Please delete any replicated items, registered servers, Hyper-V sites (Used for Site Recovery), policy associations for System Center VMM clouds (Used for Site Recovery) and then delete the vault." when trying to remove the azure recovery services vault. Most of the Vault deletion errors that we encounter at support are due to the dependency resources exist in the vault. Please follow the steps metnioned in below articles to resolve this issue. For the site recovery resources Delete Recovery Services vault For the backup resources Delete an Azure Backup vault If you testing the product, want to rapidly delete the vault and not concerned about data loss, then you can use force delete method to remove vault and all its dependencies.Solved33KViews0likes11CommentsAzure Site Recovery now available in five new regions
To increase our service global footprint, we recently announced the expansion of Azure Site Recovery to Canada and UK regions. Apart from these two new countries, we have also deployed our service in West US2, making it available to all non-government Azure regions in the United States. With this expansion, Azure Site Recovery is now available in 27 regions worldwide including Australia East, Australia Southeast, Brazil South, Central US, East Asia, East US, East US2, Japan East, Japan West, North Europe, North Central US, Southeast Asia, South Central US, West Central US, West US2, US Gov Virginia, US Gov Iowa, West Europe, West US, North East China, East China, South India,Central India, UK South, UK West, Canada East, and Canada Central. Read about it on the Azure blog.8.8KViews2likes0CommentsASR Replication Issue - Error ID 70171
Hi. I'm new to using this forum so hopefully someone can help me I have 2 x on-premise Hyper-V Windows 2012 R2 which replicate 10 servers into an Azure Recovery Vault which is used for ASR. I have a configured ASR policy which has been working for most of the year with no issues. On Thursday last week I received notification to upgrade my Hyper-V Hosts from Azure ACS to AAD for ASR. I did this and it all went well and they're on Agent Ver 5.1.2700.0 (latest) and I updated the MARS Agents to the latest too as I had a notice about these needing updating to the latest version. When I now list my 10 servers in Azure they are all RED and Replication Health is Critical and RPO column is blank. If I open ALL the servers they correctly state the App-and Crash resistance times : so why are they RED and stated as Replication Health Critical ?? The on-premise hyper-v replications says all is working and I used this article to check the finer points that replication is indeed being sent: https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-azure-to-azure-troubleshoot-errors#outbound-connectivity-for-site-recovery-urls-or-ip-ranges-error-code-151037-or-151072). Any ideas ?6.8KViews0likes2CommentsTroubleshooting - Trusted root certificates (error code 151066)
You may receive an error message “Site Recovery configuration failed.” while configuring Azure to Azure VM replication. Most of these issues occurred due to the required trusted root certificates used for authorization and authentication aren't present on the machine. This troubleshooting article details some of the possible causes and recommended actions to resolve this issue.3.6KViews0likes1CommentTroubleshooting - Can't Enable Replication? Initial replication failing? issues
You may receive "Initial replication is stuck at 0%" when protecting your VMware virtual machines or physical servers using Azure Site Recovery. Most of the initial replication failures that we encounter at support are due to connectivity issues between source server-to-process server or process server-to-Azure. This troubleshooting article details some of the more common error messages encountered, along with troubleshooting steps to resolve them.3.3KViews0likes0CommentsTroubleshooting – Azure to Azure Site Recovery configuration failed with error code 151037 or 151072
You may receive error message “Failed to register Azure virtual machine with Site Recovery/Site Recovery configuration failed.” while configuring Azure to Azure VM replication. Most of these issues occurred due to the outbound connectivity to specific URLs or IP ranges are blocked from the VM. This troubleshooting article details some of the possible causes and recommended actions to resolve this issue.3.1KViews0likes0CommentsComprehensive monitoring for Azure Site Recovery now generally available
Azure Site Recovery is a vital part of the business continuity strategy of many Azure customers. Customers rely on Azure Site Recovery to protect their mission critical IT systems, maintain compliance, and ensure that their businesses aren’t impacted adversely in the event of a disaster. Operationalizing a business continuity plan and making sure that it meets your organization’s business continuity objectives is complex. The only way to know if the plan works is by performing periodic tests. Even with periodic tests, you can never be certain that it will work seamlessly the next time around due to variables such as configuration drift and resource availability, among others. Monitoring for something as critical should not to be so difficult. The comprehensive monitoring capabilities within Azure Site Recovery gives you full visibility into whether your business continuity objectives are being met. Not just that, with a failover readiness model that monitors resource availability and suggests configurations based on best practices, it also helps inform how prepared you are to react to a disaster today. Read about it in the Azure blog.2.7KViews0likes0CommentsAzure Site recovery clearing locks
Recently had an issue in re-protecting VM's following failover to a secondary region. Tried everything and couldn't resolve eventually after speaking with Azure support i ran the below script and resolved the issue with locks not clearing on failed over VM's cls $subscriptionId = Read-Host 'What is your Azure Subscription ID?' $rgName = Read-Host 'Specify the name of the Resource group in which your VM is located' $vmName = Read-Host 'Specify the name of the VM' # Sign-in with Azure account credentials Login-AzureRmAccount # Select Azure Subscription Select-AzureRmSubscription -SubscriptionId $subscriptionId # Remove any locks $locks = Get-AzureRmResourceLock -ResourceGroupName $rgName -ResourceName $vmName -ResourceType Microsoft.Compute/virtualMachines if ($locks -ne $null -and $locks.Count -ge 0){ $canDelete = Read-Host 'The VM has locks that could prevent cleanup of Azure Site Recovery stale links left from previous protection. Do you want the locks deleted to ensure cleanup goes smoothly? Reply with Y/N.' if ($canDelete.ToLower() -eq "y"){ Foreach ($lock in $locks) { $lockId = $lock.LockId Remove-AzureRmResourceLock -LockId $lockId -Force Write-Host "Removed Lock $lockId for $vmName" } } } $linksResourceId = 'https://management.azure.com/subscriptions/' + $subscriptionId + '/providers/Microsoft.Resources/links' $vmId = '/subscriptions/' + $subscriptionId + '/resourceGroups/' + $rgName + '/providers/Microsoft.Compute/virtualMachines/' + $vmName + '/' Write-Host $("Deleting links for $vmId using resourceId: $linksResourceId") $links = @(Get-AzureRmResource -ResourceId $linksResourceId| Where-Object {$_.Properties.sourceId -match $vmId -and $_.Properties.targetId.ToLower().Contains("microsoft.recoveryservices/vaults")}) Write-Host "Links to be deleted" $links #Delete all links which are of type Foreach ($link in $links) { Write-Host $("Deleting link " + $link.Name) Remove-AzureRmResource -ResourceId $link.ResourceId -Force } $links = @(Get-AzureRmResource -ResourceId $linksResourceId| Where-Object {$_.Properties.sourceId -match $vmId -and $_.Properties.targetId.ToLower().Contains("/protecteditemarmid/")}) Write-Host "Cross subscription Links to be deleted" $links #Delete all links which are of type Foreach ($link in $links) { Write-Host $("Deleting link " + $link.Name) Remove-AzureRmResource -ResourceId $link.ResourceId -Force } Write-Host $("Deleted all links ")2.3KViews1like0CommentsFree Microsoft webinars on Operations Management Suite
Myself and my MVP colleague Marc Kean, with the help of Microsoft, have released a series of 4 webinars which covers the basics of Azure OMS. Performance and Monitoring In Part 1 of this new webinar series, learn how to separate the signal from the noise by gaining deeper insights into applications and workloads with Log Analytics: Collect, correlate and act on log data from multiple systems in a single view. Map and understand the application dependencies, and address incidents quickly. Watch this webinar Availability and Business Continuity In Part 2 of this new webinar series, learn how to take advantage of the economies of Cloud technology to get enterprise class Back-up and DR with OMS Availability. Restore applications and services quickly with disaster recovery as a service (DRaaS). Orchestrate replication, create customised recovery plans, and easily test failover. Extend on-premises data protection tools with purpose built enterprise backup services. Remove the cost and complexity of Tape back-up. Watch this webinar Security Threat Analysis & Compliance In Part 3 of this new webinar series, learn how to prevent, detect, and respond to threats with the increased visibility that OMS Security and Compliance provides. Visualise outbound malicious IP traffic and malicious threat types. Understand the security posture of your entire environment regardless of platform. Capture all security log and event data required for a compliance audit. Save time and resources when producing a security audit with a searchable and exportable log and event data set. Watch this webinar Automation of routine tasks In Part 4 of this new webinar series, learn how to use Automation to take control of your environment by remediating operational issues & get time back to focus on work that adds business value. Consistently deploy, monitor, and automatically update your IT resources, with change management and patching solutions to enable environmental compliance. Use familiar PowerShell skills to automate complex and repetitive tasks. Extend cloud automation capabilities to your on-premises datacentre without human intervention. Watch this webinar2.2KViews4likes3CommentsAzure site recovery- replication policy for offline initial replication
Hi, I have 2 sites each site has one SCVMM configured to do Azure Site Recovery. ASR is configured to replicate the VM form one site to another. Here is the issue, my VM size is big and i want to do the initial replication offline instead of over the Network. And it just not allowing me to save the policy, saying permission issues can anyone help me to find, what could be going wrong here ?? ERROR MESSAGE Permissions couldn't be set for one or more hosts on the initial replication folder path. Provider error code: 31218 Provider error message: The VMM service couldn't provide permissions for cs\nimblenter image description hereecs1$ on \nimblecs1\f$. Error: Object reference not set to an instance of an object.. During cloud configuration, the VMM service provides permissions for Hyper-V service accounts on the import and export paths used for initial replication. Provider error possible causes: The VMM service doesn't have the required privileges to modify the permissions on the import and export paths. Provider error recommended action: Ensure that the VMM service account has the required privileges to perform this operation. POSSIBLE CAUSES Verify that the initial replication path exists and is accessible.2.1KViews0likes1Comment