Do I need to buy instances of VMs to access the site recovery benefit

Hi,

If I have a number of physical servers and would like to protect these using Azure site recovery do I need to create instances of these servers in the cloud and pay for them in addition to $54 which MS charges for the site recovery feature ?

//Misha

August 21st, 2015 10:05am

It depends what you mean by create.  Recovery is replication. If you have not read the article below it will walk you through it.

http://blogs.technet.com/b/systemcenter/archive/2014/07/01/microsoft-azure-site-recovery-your-dr-site-in-microsoft-azure.aspx

Azure Site Recovery is billed in units of the average daily number of instances you are protecting over a monthly period. For example, if you consistently protected 20 instances for the first half of the month and none for the second half of the month, the average daily number of protected instances would be 10 for that month.

If your question is really just about pricing then you can go here and get more info on pricing http://azure.microsoft.com/en-us/pricing/details/site-recovery/

Free Windows Admin Tool Kit Click here and download it now
August 21st, 2015 2:17pm

It depends what you mean by create.  Recovery is replication. If you have not read the article below it will walk you through it.

http://blogs.technet.com/b/systemcenter/archive/2014/07/01/microsoft-azure-site-recovery-your-dr-site-in-microsoft-azure.aspx

Azure Site Recovery is billed in units of the average daily number of instances you are protecting over a monthly period. For example, if you consistently protected 20 instances for the first half of the month and none for the second half of the month, the average daily number of protected instances would be 10 for that month.

If your question is really just about pricing then you can go here and get more info on pricing http://azure.microsoft.com/en-us/pricing/details/site-recovery/

August 21st, 2015 6:14pm

It depends what you mean by create.  Recovery is replication. If you have not read the article below it will walk you through it.

http://blogs.technet.com/b/systemcenter/archive/2014/07/01/microsoft-azure-site-recovery-your-dr-site-in-microsoft-azure.aspx

Azure Site Recovery is billed in units of the average daily number of instances you are protecting over a monthly period. For example, if you consistently protected 20 instances for the first half of the month and none for the second half of the month, the average daily number of protected instances would be 10 for that month.

If your question is really just about pricing then you can go here and get more info on pricing http://azure.microsoft.com/en-us/pricing/details/site-recovery/

Free Windows Admin Tool Kit Click here and download it now
August 21st, 2015 6:14pm

It depends what you mean by create.  Recovery is replication. If you have not read the article below it will walk you through it.

http://blogs.technet.com/b/systemcenter/archive/2014/07/01/microsoft-azure-site-recovery-your-dr-site-in-microsoft-azure.aspx

Azure Site Recovery is billed in units of the average daily number of instances you are protecting over a monthly period. For example, if you consistently protected 20 instances for the first half of the month and none for the second half of the month, the average daily number of protected instances would be 10 for that month.

If your question is really just about pricing then you can go here and get more info on pricing http://azure.microsoft.com/en-us/pricing/details/site-recovery/

August 21st, 2015 6:14pm

It depends what you mean by create.  Recovery is replication. If you have not read the article below it will walk you through it.

http://blogs.technet.com/b/systemcenter/archive/2014/07/01/microsoft-azure-site-recovery-your-dr-site-in-microsoft-azure.aspx

Azure Site Recovery is billed in units of the average daily number of instances you are protecting over a monthly period. For example, if you consistently protected 20 instances for the first half of the month and none for the second half of the month, the average daily number of protected instances would be 10 for that month.

If your question is really just about pricing then you can go here and get more info on pricing http://azure.microsoft.com/en-us/pricing/details/site-recovery/

Free Windows Admin Tool Kit Click here and download it now
August 21st, 2015 6:14pm

It depends what you mean by create.  Recovery is replication. If you have not read the article below it will walk you through it.

http://blogs.technet.com/b/systemcenter/archive/2014/07/01/microsoft-azure-site-recovery-your-dr-site-in-microsoft-azure.aspx

Azure Site Recovery is billed in units of the average daily number of instances you are protecting over a monthly period. For example, if you consistently protected 20 instances for the first half of the month and none for the second half of the month, the average daily number of protected instances would be 10 for that month.

If your question is really just about pricing then you can go here and get more info on pricing http://azure.microsoft.com/en-us/pricing/details/site-recovery/

August 21st, 2015 6:14pm

It depends what you mean by create.  Recovery is replication. If you have not read the article below it will walk you through it.

http://blogs.technet.com/b/systemcenter/archive/2014/07/01/microsoft-azure-site-recovery-your-dr-site-in-microsoft-azure.aspx

Azure Site Recovery is billed in units of the average daily number of instances you are protecting over a monthly period. For example, if you consistently protected 20 instances for the first half of the month and none for the second half of the month, the average daily number of protected instances would be 10 for that month.

If your question is really just about pricing then you can go here and get more info on pricing http://azure.microsoft.com/en-us/pricing/details/site-recovery/

Free Windows Admin Tool Kit Click here and download it now
August 21st, 2015 6:14pm

It depends what you mean by create.  Recovery is replication. If you have not read the article below it will walk you through it.

http://blogs.technet.com/b/systemcenter/archive/2014/07/01/microsoft-azure-site-recovery-your-dr-site-in-microsoft-azure.aspx

Azure Site Recovery is billed in units of the average daily number of instances you are protecting over a monthly period. For example, if you consistently protected 20 instances for the first half of the month and none for the second half of the month, the average daily number of protected instances would be 10 for that month.

If your question is really just about pricing then you can go here and get more info on pricing http://azure.microsoft.com/en-us/pricing/details/site-recovery/

August 21st, 2015 6:14pm

It depends what you mean by create.  Recovery is replication. If you have not read the article below it will walk you through it.

http://blogs.technet.com/b/systemcenter/archive/2014/07/01/microsoft-azure-site-recovery-your-dr-site-in-microsoft-azure.aspx

Azure Site Recovery is billed in units of the average daily number of instances you are protecting over a monthly period. For example, if you consistently protected 20 instances for the first half of the month and none for the second half of the month, the average daily number of protected instances would be 10 for that month.

If your question is really just about pricing then you can go here and get more info on pricing http://azure.microsoft.com/en-us/pricing/details/site-recovery/

Free Windows Admin Tool Kit Click here and download it now
August 21st, 2015 6:14pm

I would like to consider the following option:

  • You can replicate virtual machines from your primary site directly to Azure, instead of your own secondary site. In the event of an outage at the primary site, the service orchestrates the recovery of virtual machines in Azure.

In this scenario, if I have 20 servers in my data center which I want to protect, do I pay $54*20=$1080 per month total, or in addition to this I pay extra money for each DR instance in the cloud, so I pay + $229*20 = $4580 for 20 A3 basic tier instances?

In other words, how much will it cost me a month in this example - $1080 or $5660? Or you are saying that I don't pay anything for a DR VM in the cloud unless I boot it? Can you gime some example for me to understand the price?


August 24th, 2015 5:37am

Hello,

In ASR the recovery side is always passive till a Failover is triggered. This means that you ongoing cost per month is $1080 as you have correctly calculated.

In the event of a disaster at your on-premises site, you can trigger the failover of all your protected instances to Azure. Once the VMs start running in Azure from then on you will have to start paying the IAAS VM cost. So lets say to test your DR stack you do a Planned Failover for say 1 week (7 days)  every 6 months then your yearly cost will be

             Cost = (20VMs * $54  * 12 months) + (20 VMS * 14 days * $7.7)

where $7.4 = cost of running a A3 VM for 1 day ($0.30/hour)

Hope the clears the math.

Regards,

Anoop

  • Marked as answer by MihaMih 9 minutes ago
Free Windows Admin Tool Kit Click here and download it now
August 26th, 2015 1:28am

Hello,

In ASR the recovery side is always passive till a Failover is triggered. This means that you ongoing cost per month is $1080 as you have correctly calculated.

In the event of a disaster at your on-premises site, you can trigger the failover of all your protected instances to Azure. Once the VMs start running in Azure from then on you will have to start paying the IAAS VM cost. So lets say to test your DR stack you do a Planned Failover for say 1 week (7 days)  every 6 months then your yearly cost will be

             Cost = (20VMs * $54  * 12 months) + (20 VMS * 14 days * $7.7)

where $7.4 = cost of running a A3 VM for 1 day ($0.30/hour)

Hope the clears the math.

Regards,

Anoop

  • Marked as answer by MihaMih 13 minutes ago
August 26th, 2015 1:28am

Thank you, I was unable to get this information from Russian Azure support - they told me to sign up for Azure to open a ticket with them. Having to sign up for a service and open a ticket to get a price is crazy in my opinion.

At which point do I select an instance which will be used for the failover VM - at the time when I set up the DR or at the time when I failover?

What about VMWare scenario? The case when I want to protect my local vCenter's VMs in Azure. As far as I understand I would need to pay for one instance in the cloud permanetly and then does the same pricing rule apply - I pay only for the period of time I start the failed over VM in the cloud?

Free Windows Admin Tool Kit Click here and download it now
August 26th, 2015 3:13am

Hello,

In ASR the recovery side is always passive till a Failover is triggered. This means that you ongoing cost per month is $1080 as you have correctly calculated.

In the event of a disaster at your on-premises site, you can trigger the failover of all your protected instances to Azure. Once the VMs start running in Azure from then on you will have to start paying the IAAS VM cost. So lets say to test your DR stack you do a Planned Failover for say 1 week (7 days)  every 6 months then your yearly cost will be

             Cost = (20VMs * $54  * 12 months) + (20 VMS * 14 days * $7.7)

where $7.4 = cost of running a A3 VM for 1 day ($0.30/hour)

Hope the clears the math.

Regards,

Anoop

  • Marked as answer by MihaMih Wednesday, August 26, 2015 7:06 AM
August 26th, 2015 5:27am

Hello,

In ASR the recovery side is always passive till a Failover is triggered. This means that you ongoing cost per month is $1080 as you have correctly calculated.

In the event of a disaster at your on-premises site, you can trigger the failover of all your protected instances to Azure. Once the VMs start running in Azure from then on you will have to start paying the IAAS VM cost. So lets say to test your DR stack you do a Planned Failover for say 1 week (7 days)  every 6 months then your yearly cost will be

             Cost = (20VMs * $54  * 12 months) + (20 VMS * 14 days * $7.7)

where $7.4 = cost of running a A3 VM for 1 day ($0.30/hour)

Hope the clears the math.

Regards,

Anoop

  • Marked as answer by MihaMih Wednesday, August 26, 2015 7:06 AM
Free Windows Admin Tool Kit Click here and download it now
August 26th, 2015 5:27am

Hello,

In ASR the recovery side is always passive till a Failover is triggered. This means that you ongoing cost per month is $1080 as you have correctly calculated.

In the event of a disaster at your on-premises site, you can trigger the failover of all your protected instances to Azure. Once the VMs start running in Azure from then on you will have to start paying the IAAS VM cost. So lets say to test your DR stack you do a Planned Failover for say 1 week (7 days)  every 6 months then your yearly cost will be

             Cost = (20VMs * $54  * 12 months) + (20 VMS * 14 days * $7.7)

where $7.4 = cost of running a A3 VM for 1 day ($0.30/hour)

Hope the clears the math.

Regards,

Anoop

  • Marked as answer by MihaMih Wednesday, August 26, 2015 7:06 AM
August 26th, 2015 5:27am

Hello,

In ASR the recovery side is always passive till a Failover is triggered. This means that you ongoing cost per month is $1080 as you have correctly calculated.

In the event of a disaster at your on-premises site, you can trigger the failover of all your protected instances to Azure. Once the VMs start running in Azure from then on you will have to start paying the IAAS VM cost. So lets say to test your DR stack you do a Planned Failover for say 1 week (7 days)  every 6 months then your yearly cost will be

             Cost = (20VMs * $54  * 12 months) + (20 VMS * 14 days * $7.7)

where $7.4 = cost of running a A3 VM for 1 day ($0.30/hour)

Hope the clears the math.

Regards,

Anoop

  • Marked as answer by MihaMih Wednesday, August 26, 2015 7:06 AM
Free Windows Admin Tool Kit Click here and download it now
August 26th, 2015 5:27am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics