---
title: "Connect disaster recovery via Cloud Availability"
sidebar_label: "Connect disaster recovery via Cloud Availability"
sidebar_position: 1
description: "How to connect disaster recovery from a VMware Public Cloud, On-Premises, or private cloud to the Selectel cloud"
---

import Formbricks from '@theme/MDXComponents/Formbricks'
import Tabs from '@theme/Tabs'
import TabItem from '@theme/TabItem'
import {TabItemLabel} from '@selectel/docux/components'

# Connect disaster recovery via Cloud Availability

You can connect disaster recovery to the Selectel cloud from a VMware Public Cloud at another provider, from an On-Premises infrastructure, or from a private cloud at another provider.

To connect disaster recovery in the Selectel Control Panel, you must have [an organization](/public-cloud/manage-public-cloud/create-organization.mdx) created for a VMware-based public cloud.

If disaster recovery is connected, in the event of an emergency, [perform a failover](/draas/manage/failover.mdx).

1. [Connect disaster recovery](#connect-disaster-recovery).
2. [Connect to Cloud Availability in Selectel](#connect-to-selectel).
3. [Create a replication job](#create-replication-job).
4. Optional: [create a disaster recovery plan](#create-recovery-plan).
5. Optional: [test the failover](#test-failover).

## 1. Connect disaster recovery \{#connect-disaster-recovery}

<Tabs queryString="source">
  <TabItem value="from-public-cloud-at-another-provider" default>
    <TabItemLabel>
      From a public cloud at another provider
    </TabItemLabel>

    1. From the public cloud provider for which you are setting up disaster recovery, request the following data:

       * Local site name;
       * Service endpoint address.
    2. [Create a ticket](https://my.selectel.ru/tickets/create) to configure connectivity on the Selectel side. Include the data received from the provider in the ticket.
    3. Provide the equivalent Selectel cloud data to your provider so they can configure connectivity on the public cloud side. Specify the following Service endpoint address:

       * Saint Petersburg — `https://vcav-spb-1.vmw.selectel.ru`
       * Moscow — `https://vcav-msk-1.vmw.selectel.ru`
  </TabItem>

  <TabItem value="from-on-premises-or-private-cloud">
    <TabItemLabel>
      From On-Premises or a private cloud
    </TabItemLabel>

    1. Check compatibility of VMware Cloud Director Availability™ and VMware vCenter Server® versions in the [VMware compatibility matrix](https://interopmatrix.vmware.com/Interoperability).

    2. Download the virtual machine template from the [VMware website](https://customerconnect.vmware.com/en/downloads/details?downloadGroup=VCDAT_43\&productId=1223).

    3. Select one of the following entities as a container for the virtual machine:

       * data center;
       * folder;
       * cluster;
       * or resource pool.

    4. Right-click the container and select **Deploy OVF Template**.

    5. Optional: create an A-record on your local DNS server for the virtual machine being deployed.

    6. Select the template file in `.ova format`.

    7. Enter the virtual machine name.

    8. Accept the license agreement.

    9. Set the network parameters.

    10. Enter a new password for accessing Cloud Availability and the address of the NTP server.

    11. Synchronize the time on the virtual machine with VMware vCenter Server®, Platform Services Controller™, and VMware ESXi™. Use a common NTP server.

    12. Open the Cloud Availability administration page at `https://<vcda_ip_address>/ui/admin`. Specify `<vcda_ip_address>` — the IP address you specified when deploying the virtual machine from the `.ovf template`.

    13. Optional: change the password upon your first login.

    14. Go to the **Getting Started** → **Run initial setup wizard**.

    15. Enter the local site name.

    16. In the **Lookup Service** section, enter the Lookup service address of your vCenter. If the installation uses a separate PSC, the Lookup service is located on it.

    17. Enter the vCenter administrator name and password (use local SSO credentials for vCenter Server).

    18. Accept the certificate.

    19. In the **Cloud Details** section, in the **Public IP Endpoint** field, enter the address of the remote Cloud Availability site:

        * Saint Petersburg — `https://vcav-spb-1.vmw.selectel.ru`
        * Moscow — `https://vcav-msk-1.vmw.selectel.ru`

    20. In the **Organization Admin** field, enter the Cloud Director organization administrator name in the format `administrator-<s-xxxx>@<s-xxxx>`, where `<s-xxxx>` is the organization name, which you can find in the Cloud Director address bar or in the [Control Panel](https://my.selectel.ru/vmware/) in the **VMware-based cloud** section in the list of organizations.

    21. In the **Organization Password** field, enter the administrator password.

    22. Optional: to enable access to the On-Premises site from Cloud Director, turn on the **Allow access from cloud**.

    23. Accept the certificate.

    24. Optional: to configure placement settings for virtual machines migrated from the cloud to the local vCenter, turn on the **Configure local placement**.

    25. Click **Finish**.
  </TabItem>
</Tabs>

## 2. Connect to Cloud Availability in Selectel \{#connect-to-selectel}

Use the instructions for [Connecting to Cloud Availability in Selectel](/draas/manage/connect-to-selectel.mdx).

## 3. Create a replication job \{#create-replication-job}

Use the [Creating a replication job subsection](/draas/manage/manage-tasks.mdx#create-replication-job).

## 4. Optional: create a disaster recovery plan \{#create-recovery-plan}

Use the [Recovery Plans](https://docs.vmware.com/en/VMware-Cloud-Director-Availability/4.5/VMware-Cloud-Director-Availability-User-Guide/GUID-30387927-096F-4F1B-91AD-4BEA00B75DE2.html) reference in the VMware documentation.

## 5. Optional: test the failover \{#test-failover}

Use the [Test Failover](https://docs.vmware.com/en/VMware-vCloud-Availability/3.0/com.vmware.vcav.user.guide.doc/GUID-A760E8AA-7CAF-4B2D-A24B-0B812986FEF9.html) reference in the VMware documentation.

<Formbricks />
