Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Recovery Services Backup Policies / Site Recovery #1007

Closed
philipstreet-hiscox opened this issue Mar 20, 2018 · 8 comments
Closed

Comments

@philipstreet-hiscox
Copy link

We would like to automate the configuration of Backup and Site Recovery for VMs, a la https://docs.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-enable-replication.

This should include the configuration of Resource Group, Network, Storage and Availability Sets.

@JamesDLD
Copy link

JamesDLD commented Apr 9, 2018

I will be very interested too on this feature, we currently use the not recommended solution "azurerm_template_deployment"

@JamesDLD
Copy link

For info, if it can help I published here how I create a recovery vault through the Terraform resource "azurerm_template_deployment" : https://github.com/JamesDLD/terraform
I will add soon how to enable backup for a VM.

@tombuildsstuff
Copy link
Contributor

hi @philipstreet-hiscox @JamesDLD

Thanks for opening this issue :)

Support for provisioning Recovery Services has been added in #995 which will ship as part of the next release of the Azure Provider. There's a separate issue tracking adding Virtual Machines to a Recovery Vault - which I'm going to close this in favour of: #1143

Thanks!

@tombuildsstuff tombuildsstuff changed the title Feature Request: Support for "Backup and Site Recovery" capability Feature Request: Recovery Services Backup Policies / Site Recovery May 23, 2018
@tombuildsstuff
Copy link
Contributor

Adding some additional context after a little investigation: it appears this'd need to be a resource per "Type" - we should be able to start with IaaS VM's and add additional types based on demand? This is available in the SDK: https://github.com/Azure/azure-sdk-for-go/blob/4de511fba6f4c9d4266d37a7b0d142abb976fa8e/services/recoveryservices/mgmt/2017-07-01/backup/models.go#L3572

@philipstreet-hiscox
Copy link
Author

My specific scenario is configuring Replicated items (https://docs.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-enable-replication#enable-replication).

What I've done so far is Terraform the additional resources required to configure Azure-to-Azure VM replication, i.e. Availability Sets, NSGs, Recovery Services Vault & Storage Accounts, and then manually configure (via the Portal) the VM Replication (as described in the above link).

So, what I would like to be able to do in Terraform is (depending on what is supported):

  • Configure replication settings for a VM, specifying target Resource Group, Availability Set, Virtual Network, Replica Managed Disks, and Cache Storage
  • Configure Replication policy, including using an existing Replication policy or configuring a new one (Name, recovery point, app consistency snapshot frequency), multi-VM consistency with Replication group details (name, machines)
  • Extension settings (Update settings)

@tombuildsstuff
Copy link
Contributor

👋

Support for Recovery Services Policies and Recovery Services Protected VM's shipped in v1.17 of the AzureRM Provider. You can upgrade to this by updating the version number specified in the Provider block (as shown below) then by running terraform init -upgrade:

provider "azurerm" {
  version = "=1.18.0"
}

Thanks!

@silvesterc
Copy link

Hi There, can this be used to set up replication rather than backups? From the documentation, it seems only backups are possible.

@ghost
Copy link

ghost commented Mar 5, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants