No, but VMs need access to Site Recovery URLs and IP ranges.

In reality, you are transferring the data across the Internet into Azure Site Recovery. But in many organisations, they don’t even allow Internet access on the servers, and they block it for security reasons. Because of that, there are certain URLs from Microsoft, so as long as we have access to those URL and they are whitelisted, then yes we can run the Azure Site Recovery and the service doesn’t need a separate Internet.  

The first recovery point that's generated has the complete copy. Successive recovery points have delta changes.

Azure Backup is also very secure, the data is encrypted with 256 bit encryption key during transfer to Azure and also is encrypted at rest by default in the Azure vault.

Access can be granted to specific admin identities, enforced with MFA for an added layer of security, and comes with full audit log of what has been access by whom and when.

You can't keep the public IP address for a production app after a failover. When you bring up a workload as part of the failover process, you need to assign an Azure public IP address resource to it. The resource must be available in the target region. You can assign the Azure public IP address resource manually, or you can automate it with a recovery plan.

By default, when you enable disaster recovery for Azure VMs, Site Recovery creates target resources based on source resource settings. For Azure VMs configured with static IP addresses, Site Recovery tries to provision the same IP address for the target VM, if it's not in use.

You can add as little as $30/month (AUD) to your existing Azure subscription to protect your data and apps against disasters and cyber threats, avoid costly disruption, and recover your data quickly when needed.

It doesn’t matter what type of data, virtual machine, or application you want to backup, Azure can cover it, and Professional Advantage can implement it for you. Contact us to learn more.

Assess your risk of IT downtime by using this 7-point questionnaire.

1. How long will it take to restore your production systems (RTO)?
2. How much data do you risk losing (RPO)?
3. What is the impact on client trust if downtime occurs?
4. Do you rely on sourcing hardware to recover production systems?
5. How many users are on your network at any given time?
6. Are you compliant if running on your “Recovered” system?
7. What are your Cloud strategies / considerations for the future?

Download a copy of the checklist here. For further guidance, please connect with our experts here. 

Protect to Azure is the strategy for workloads that run on-premises. Protect in Azure is the strategy for workloads that run in Azure.

Register to watch this on-demand webinar for more information.