Manage cloud recovery sites

This article describes how to manage cloud recovery sites including pre-requirements, resources, cost implications, and lifecycle.

Pre-requirements

Cloud recovery site consists of resources such as virtual machines or file storage. These resources are created within the selected cloud service provider, such as Azure or AWS.

Depending on your cloud provider subscription, you might be charged for resources created in the cloud.

To create resources in Azure an Entra ID subscription is required. You can use your existing subscription or consider purchasing a new one.

To create resources in AWS, an AWS account is required. Learn more about AWS pricing.

Azure recovery site

Connection account for Azure

An account with a Contributor role in the resource group is required in case you plan to create a resource group manually and only allow Cayosoft Guardian to create the resources.

A Contributor role for the subscription is required for Cayosoft Guardian to create a resource group with all resources.

Resources in Azure recovery site

Cayosoft Guardian automatically creates a virtual machine and related resources such as a Network Interface, Disk for each domain controller to be recovered, and additional resources such as a Storage account, Virtual network, Relay, and Network Security Group. If you select to configure remote access to VMs in the Azure Recovery Site, additional Azure resources will be provisioned during the creation of the Azure Recovery Site.

NOTE: Starting from 6.1.0, you can configure recovery plans to use a Relay VM instead of the Azure Relay service. This option is available for both new and existing recovery plans and helps reduce dependency on Azure Relay service availability. Switching to a Relay VM may provide improved resilience and control over remote access components.
 

You will be charged for these resources depending on the type of agreement entered with Microsoft, the date of purchase, and the currency exchange rate. Sign in to the Azure pricing calculator to see pricing based on your current offer with Microsoft.

Deploy Azure recovery site

You can deploy an Azure recovery site from a forest or standby forest recovery plan. To deploy an Azure recovery site from a forest recovery plan:

1. Open Cayosoft Guardian web portal.
2. Expand the Forest Recovery node.
3. Select the Recovery plans node.
4. Click Add and select Forest Recovery plan.
5. Click Deploy recovery site in the forest recovery plan and select Deploy to Azure.
6. Review settings and click Deploy.

Delete Azure recovery site

Consider deleting a recovery site in case it is no longer required.

1. Expand theForest Recovery node.
2. Click on Recovery Sites.
3. Select the recovery site and click Delete.
4. Keep theDelete linked Azure resources option enabled to delete resources in Azure.

Deployment schema for Azure

AWS recovery site

Connection account for AWS

Account credentials with necessary permissions are required to connect to Gssuardian. For the detailed list of requirements on the Guardian side, see software requirements. To create an account in AWS with the required permissions, see Forest Recovery: How to create AWS access keys.

Deploy an AWS recovery site

You can deploy an AWS recovery site from a forest or standby forest recovery plan. To deploy an AWS recovery site from a forest recovery plan:

1. Open the Cayosoft Guardian web portal.

1. Expand the Forest Recovery node.
2. Select the Recovery plans node.
3. Press Add and select Forest Recovery plan.
4. Click Deploy recovery site in the forest recovery plan and select Deploy to AWS.
5. Review settings and click Deploy.

Delete an AWS recovery site

Consider deleting a recovery site in case it is no longer required.

1. Expand the Forest Recovery node.
2. Click on Recovery Sites.
3. Select the recovery site and click Delete.

Deployment schema for AWS