Azure Site Recovery Reviews

Implementation of Site Recovery let`s you one great thing, try your on-premise services, running in Azure. After we executed test failover, we were excited with speed and smoothness of Azure environment so we decided to retire outdated hardware and stayed in Azure. Solution was implemented in Hyper-V server and didn`t took long to be configured appropriately, so migration was transparent to our users. The only difference they noticed was increased speed of applications. According to documentation solution could be used with VMware and AWS virtual machines as well as with physical servers, which is also cool.

heavy network load during initial synchronization, we don`t have much bandwidth, so it was sufficient when only delta was sent to Azure, but network was very slow when we started Site Recovery for the first time

Pay attention on setting up recovery plans, if machines are started in wrong order, your environment can become unusable

Easy migration to Azure

Site Recovery provides new level of resiliency of your physical servers and virtual machines, it orchestrates replication and provides failover options in case of outage. You can chose between on-premises data center or Azure as secondary location for your workloads. solution is not so hard to implement, Microsoft also provides all required tools for capacity planning, so you can perform assessment of your infrastructure, to determine if you have enough network bandwidth to handle replication process. Support of Hyper-V and VMWare hypervisors as well as Azure virtual machines that could be replicated to another subscription. Also ASR has some support for AWS EC2 instances. Abbility to perform test failover without puttiong your actual servers down, it is also useful if you need to quickly create a copy of your production environment for testing purposes and destroy it, when testing completes. Comfortable and reasonable pricing for such kind of solutions

AWS EC2 is supported as primary location, but it will work only one-way, so you will not be able to fail back. Useful for migration from AWS but not for additional resiliency. Failing back from Azure can utilize a lot of outbound traffic, and can increase your mothly costs for Azure. VMWare configuration is complex and requires additional server to be deployed on-premises

Experienced staff can configure solution, that end users will even not see any difference after failover

Disaster Recovery and temporary testing environments for critical production systems

very easy to manage right out of the box. best choice if you have azure and want to limit downtime

the cost, it could be cheaper. also i wish i could recover to local location as an option

if you are using for DB make sure you connect with SQL studio to rename the old DB and once recovered rename the new one to the old name.

if a client changed something or a site was updated and now its not accessible. now i can just recover the site quickly and minimize outage.

It can backup online both Windows and Linux infrastructure-as-a-service (IaaS) VMs (and physical). In addition, it supports Windows Server and System Center management tools.

You need to have IT-level knowledge for all but the simplest disaster recover scenarios. Furthermore, a. System Center Virtual Machine Manager is required for multi-VM configurations.

Azure Site Recovery is a platform that helps you manage all your applications and data. Through its Ease of Use it offers an open and flexible infrastructure for users and enables them to employ Azure in order to operate all of their applications. In my opinion, it is a one of the most highly sophisticated cloud products, currently available in the market, that provides an ease-to-use set of back-up , disaster recovering (DR), and reporting features. And all these in a very good price.

It is a very good choice if you want to protect a plethora of important workloads on both VMware and Hyper-V. The price is also good offering a competitive storage, as well as a failover capability. Finally, it offers good integration with System Center, which makes Azure Site Recovery very user-friendly for Windows operations.

DRaaS model allows you to pay only for resources that you are using with Site Recovery, no need to have very expensive redundant starage on-premise. Work fantastic fow Azure recources and Hyper-V VMs in your datacenter

working with VMware is a challenge, you need to deploy additional configuration servers on-premise

Solution works perfectly if you have enough time and staff who can maintain it

Provides DR for reasonable price

Replication from on prem to azure is very simple to setup

It can be very slow, but of course depends on your network resources

as long as you configure it correctly it will work well, specially since it plays very well with vmware (vcenter)

Azure migration from onprem to azure

Orchestration of failovers between primary and secondary location, you can choose between seconary location in Azure or in on-premise datacenter

Monitoring of protected machines os not very deep, just availability check

ASR will work perfect as a DR solution

ASR controls replication between out datacenter and hoster`s location

ASR allows replication of your hypervisors to clud or secondary datacenter without a complex configuration. Configuration for Hyper-V takes just several hours, VMware is a bit more complex

Alerting system needs some work on it, but it is not a big problem

Disaster Recovery for on-premise workloads

The native integration with on-prem Microsoft products such as Windows 2012 R2 and Data Protection Manager. The Azure Site Recovery feature closes the gap for Disaster Recovery and provides new options vs. the traditional costly colocation models.

Some functions still have to be managed via Powershell vs. a GUI interface. One of the attractive draws to moving to a cloud model is reducing the need to IT expertise so adding more GUI management features would be beneficial.

Take note of the integration it provides with Active Directory and on-premise Microsoft based platforms. That is where Azure excels vs. other public cloud platforms such as AWS and Google.

Reduction of on-premise systems and on-demand disaster recovery.

My workload was relatively small so this tool worked wonderfully. It does not require a lot of Investments of time or energy.

It is expensive and I have ran across an issue with quoting clients accurately due to the cost of restoring.

How can I recover any sites that have been lost due to updates or just not accessible with very little issues.

Melhor ferramenta para contenção de desastres e manter dados seguros

Gerenciamento da Aplicação, precisa de mais recursos!

Proteção de dados de sistema e de sites!

I love using this software because it is effective at dealing with my day to day functions.

Nothing, as of yet. Everything working perfectly.

Ability to multitask within the program.