[Yandex Cloud documentation](../../index.md) > [Yandex Compute Cloud](../index.md) > [Tutorials](index.md) > Backing up a VM with Hystax Acura # Backing up a VM with Hystax Acura Backup You can automatically create VM backups and recover them in your cloud infrastructure using [Hystax Acura Backup in Yandex Cloud](https://yandex.cloud/en/marketplace/products/hystax/hystax-acura-backup). A VM with Hystax Acura Backup manages backup and recovery. VM backups are saved to an Object Storage [bucket](../../storage/concepts/bucket.md). Recovery involves an auxiliary Hystax Cloud Agent VM, which creates a new VM with a certain recovery point objective (RPO) at a random point of time in the past. The backup recovery time objective (RTO) depends on the amount of source data. To back up and recover a VM using Hystax Acura Backup: 1. [Get your cloud ready](#before-begin). 1. [Create a service account](#create-sa). 1. [Configure the network traffic permissions](#network-settings). 1. [Create a bucket](#create-bucket). 1. [Create a VM with Hystax Acura Backup](#create-acura-vm). 1. [Convert the VM IP address to static](#static-ip). 1. [Configure Hystax Acura Backup](#setup-hystax-acura). 1. [Prepare and install an agent on the VM](#prepare-agent). 1. [Create a VM backup](#start-protection). 1. [Create a disaster recovery plan](#create-recovery-plan). 1. [Run recovery](#run-recover). If you no longer need the resources you created, [delete them](#clear-out). ## Get your cloud ready {#before-begin} Sign up for Yandex Cloud and create a [billing account](../../billing/concepts/billing-account.md): 1. Navigate to the [management console](https://console.yandex.cloud) and log in to Yandex Cloud or create a new account. 1. On the **[Yandex Cloud Billing](https://center.yandex.cloud/billing/accounts)** page, make sure you have a billing account linked and it has the `ACTIVE` or `TRIAL_ACTIVE` [status](../../billing/concepts/billing-account-statuses.md). If you do not have a billing account, [create one](../../billing/quickstart/index.md) and [link](../../billing/operations/pin-cloud.md) a cloud to it. If you have an active billing account, you can create or select a [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) for your infrastructure on the [cloud page](https://console.yandex.cloud/cloud). [Learn more about clouds and folders here](../../resource-manager/concepts/resources-hierarchy.md). ### Required paid resources {#paid-resources} {% note info %} Note that both the Hystax Acura Backup infrastructure and all recovered VMs will be charged and counted against the [quotas](https://console.yandex.cloud/cloud?section=quotas). * A Hystax Acura Backup VM uses 8 vCPUs, 16 GB of RAM, and a 200-GB disk. * Auxiliary Hystax Cloud Agent VMs use 2 vCPUs, 4 GB of RAM, and a 10-GB disk. A single Hystax Cloud Agent VM can serve up to six replicated disks at a time. If there are more than six disks, the system will automatically create additional Hystax Cloud Agent VMs. For detailed system requirements, see the [Hystax deployment reference](https://xn--q1ach.xn--p1ai/cdn/TechDocs/Deployment-requirements.pdf). {% endnote %} The cost of resources for Hystax Acura Backup includes: * Fee for VM computing resources (see [Yandex Compute Cloud pricing](../pricing.md#prices-instance-resources)). * Fee for VM disks (see [Yandex Compute Cloud pricing](../pricing.md#prices-storage)). * Fee for using a dynamic or static external IP address (see [Yandex Virtual Private Cloud pricing](../../vpc/pricing.md#prices-public-ip)). * Fee for data storage in a bucket and data operations (see [Yandex Object Storage pricing](../../storage/pricing.md)). * Fee for using Hystax Acura Backup (see the [product description](https://yandex.cloud/en/marketplace/products/hystax/hystax-acura-backup) in Cloud Marketplace). ### Create a service account and access keys {#create-sa} Hystax Acura Backup will run under a [service account](../../iam/concepts/users/service-accounts.md). 1. [Create](../../iam/operations/sa/create.md) a service account named `hystax-acura-account` with the `editor` and `marketplace.meteringAgent` roles. Save the service account ID. You will need it later. 1. [Create](../../iam/operations/authentication/manage-authorized-keys.md#create-authorized-key) an authorized key for the service account. You need an authorized key to perform operations in Yandex Cloud under a service account. Save the ID and private key. You will need these later. 1. [Create](../../iam/operations/authentication/manage-access-keys.md#create-access-key) a static access key. A static key is required to access a bucket as a service account. Save the ID and secret key. You will need these later. ### Configure the network traffic permissions {#network-settings} Configure the network traffic permissions in the [default security group](../../vpc/concepts/security-groups.md#default-security-group). [Add](../../vpc/operations/security-group-update.md#add-rule) the following rules to it: Traffic
direction | Description | Port range | Protocol | Destination name /
Source | CIDR blocks --- | --- | --- | --- | --- | --- Inbound | `http` | `80` | `TCP` | `CIDR` | `0.0.0.0/0` Inbound | `https` | `443` | `TCP` | `CIDR` | `0.0.0.0/0` Inbound | `https` | `4443` | `TCP` | `CIDR` | `0.0.0.0/0` Inbound | `vmware` | `902` | `TCP` | `CIDR` | `0.0.0.0/0` Inbound | `vmware` | `902` | `UDP` | `CIDR` | `0.0.0.0/0` Inbound | `iSCSI` | `3260` | `TCP` | `CIDR` | `0.0.0.0/0` Inbound | `udp` | `12201` | `UDP` | `CIDR` | `0.0.0.0/0` Inbound | `tcp` | `15000` | `TCP` | `CIDR` | `0.0.0.0/0` Outbound | `http` | `80` | `TCP` | `CIDR` | `0.0.0.0/0` Outbound | `https` | `443` | `TCP` | `CIDR` | `0.0.0.0/0` Outbound | `vmware` | `902` | `TCP` | `CIDR` | `0.0.0.0/0` Outbound | `vmware` | `902` | `UDP` | `CIDR` | `0.0.0.0/0` Outbound | `iSCSI` | `3260` | `TCP` | `CIDR` | `0.0.0.0/0` Outbound | `udp` | `12201` | `UDP` | `CIDR` | `0.0.0.0/0` Save the security group ID. You will need it later. {% note info %} Auxiliary Hystax Cloud Agent VMs are created automatically in the default security group. If you created a dedicated group for the Hystax Acura Backup VM, [move](../operations/vm-control/vm-update.md) the auxiliary Hystax Cloud Agent VMs to this group after their creation. {% endnote %} ## Create a bucket {#create-bucket} {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the folder where you want to create a bucket. 1. Navigate to **Object Storage**. 1. Click **Create bucket**. 1. On the bucket creation page: 1. Enter a name for the bucket by following the [naming conventions](../../storage/concepts/bucket.md#naming). 1. Limit the maximum bucket size, if required. If the value is `0`, the size is not limited. It is similar to the enabled **No limit** option. 1. Select the [access](../../storage/concepts/bucket.md#bucket-access) type: * **Read objects**: `With authorization`. * **Read object list**: `With authorization`. * **Read settings**: `With authorization`. 1. Select the [storage class](../../storage/concepts/storage-class.md): `Standard`. 1. Click **Create bucket** to complete the operation. 1. Save the bucket name. You will need it later. - API {#api} Use the [create](../../storage/api-ref/Bucket/create.md) REST API method for the [Bucket](../../storage/api-ref/Bucket/index.md) resource or the [BucketService/Create](../../storage/api-ref/grpc/Bucket/create.md) gRPC API call. {% endlist %} ## Create a VM with Hystax Acura Backup {#create-acura-vm} To create a VM with a recommended configuration and a boot disk from the Hystax Acura Backup image: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) where you want to create your VM. 1. Navigate to **Compute Cloud**. 1. In the left-hand panel, select ![image](../../_assets/console-icons/server.svg) **Virtual machines**. 1. Click **Create virtual machine**. 1. Under **Boot disk image**: * Navigate to the **Marketplace** tab. * Click **Show all Marketplace products**. * In the list of public images, select [Hystax Acura Backup in Yandex Cloud](https://yandex.cloud/en/marketplace/products/hystax/hystax-acura-backup) and click **Use**. 1. Under **Location**, select an [availability zone](../../overview/concepts/geo-scope.md) where your VM will reside. Save the availability zone ID. You will need it later. 1. Under **Disks and file storages**, enter `200 GB` as the boot [disk](../concepts/disk.md) size. 1. Under **Computing resources**, select the `8 vCPU` and `16 GB` configuration. 1. Under **Network settings**: * In the **Subnet** field, enter the ID of a subnet in the new VM’s availability zone. Alternatively, select a [cloud network](../../vpc/concepts/network.md#network) from the list. * Each network must have at least one [subnet](../../vpc/concepts/network.md#subnet). If there is no subnet, create one by selecting **Create subnet**. * If there are no networks in the list, click **Create network** to create one: * In the window that opens, specify the network name and select the folder where it will be created. * Optionally, enable the **Create subnets** setting to automatically create subnets in all availability zones. * Click **Create network**. * If the list of **Security groups** is available, select the [security group](../../vpc/concepts/security-groups.md#default-security-group) whose network traffic permissions you previously configured. If this list is not there, the system will allow all inbound and outbound traffic for the VM. 1. Under **Access**, select **SSH key** and specify the VM access credentials: * In the **Login** field, enter a username, e.g., `yc-user`. * In the **SSH key** field, select the SSH key saved in your [organization user](../../organization/concepts/membership.md) profile. If there are no SSH keys in your profile or you want to add a new key: 1. Click **Add key**. 1. Enter a name for the SSH key. 1. Select one of the following: * `Enter manually`: Paste the contents of the public SSH key. You need to [create](../operations/vm-connect/ssh.md#creating-ssh-keys) an SSH key pair on your own. * `Load from file`: Upload the public part of the SSH key. You need to create an SSH key pair on your own. * `Generate key`: Automatically create an SSH key pair. When adding a new SSH key, an archive containing the key pair will be created and downloaded. In Linux or macOS-based operating systems, unpack the archive to the `/home//.ssh` directory. In Windows, unpack the archive to the `C:\Users\/.ssh` directory. You do not need additionally enter the public key in the management console. 1. Click **Add**. The system will add the SSH key to your organization user profile. If the organization has [disabled](../../organization/operations/os-login-access.md) the ability for users to add SSH keys to their profiles, the added public SSH key will only be saved in the user profile inside the newly created resource. 1. Under **General information**, specify the VM name: `hystax-acura-vm`. 1. Under **Additional**, select `hystax-acura-account`, the service account you created earlier. 1. Click **Create VM**. - CLI {#cli} If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install). The folder used by default is the one specified when [creating](../../cli/operations/profile/profile-create.md) the CLI profile. To change the default folder, use the `yc config set folder-id ` command. You can also specify a different folder for any command using `--folder-name` or `--folder-id`. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions. Run this command: ```bash yc compute instance create \ --name hystax-acura-vm \ --zone \ --cores 8 \ --memory 16 \ --network-interface subnet-id=,nat-ip-version=ipv4,security-group-ids= \ --create-boot-disk name=hystax-acura-disk,size=200,image-id= \ --service-account-id \ --ssh-key ``` Where: * `--name`: VM name, e.g., `hystax-acura-vm`. * `--zone`: [Availability zone](../../overview/concepts/geo-scope.md), e.g., `ru-central1-a`. Save the availability zone ID, as you will need it later. * `--cores`: [Number of vCPUs](../concepts/vm.md) the VM has. * `--memory`: VM [RAM size](../concepts/vm.md). * `--network-interface`: VM network interface description: * `subnet-id`: ID of the subnet to connect your VM to. You can get the list of subnets using the `yc vpc subnet list` CLI command. Save the subnet ID. You will need it later. * `nat-ip-version=ipv4`: Connect a public IP address. * `security-group-ids`: Security group. Use this parameter in case you configured this group previously. You can get the list of groups using the `yc vpc security-group list` CLI command. If you skip this parameter, the system will assign the [default security group](../../vpc/concepts/security-groups.md#default-security-group) to the VM. * `--create-boot-disk`: Create a new disk for the VM: * `name`: Disk name, e.g., `hystax-acura-disk`. * `size`: Disk size. * `image-id`: Disk image ID. Use `image_id` from the [product description](https://yandex.cloud/en/marketplace/products/hystax/hystax-acura-backup) in Cloud Marketplace. * `--service-account-id`: ID of the service account you [created previously](#create-sa). You can get the list of accounts using the `yc iam service-account list` command. * `--ssh-key`: Path to the public SSH key file. The default username for SSH access is `yc-user`. - API {#api} Use the [create](../api-ref/Instance/create.md) REST API method for the [Instance](../api-ref/Instance/index.md) resource or the [InstanceService/Create](../api-ref/grpc/Instance/create.md) gRPC API call. {% endlist %} ## Convert the VM IP address to static {#static-ip} VMs get a public dynamic IP address when created. Since a VM with Hystax Acura Backup may reboot, convert its IP address to static: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), open the dashboard of the folder you are using. 1. Navigate to **Virtual Private Cloud**. 1. Navigate to the **Public IP addresses** tab. 1. Click ![image](../../_assets/console-icons/ellipsis.svg) in the row with the address of your Hystax Acura Backup VM. 1. In the menu that opens, select **Make static**. 1. In the window that opens, click **Change**. 1. Save the IP address, as you will need it later. - CLI {#cli} If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install). The folder used by default is the one specified when [creating](../../cli/operations/profile/profile-create.md) the CLI profile. To change the default folder, use the `yc config set folder-id ` command. You can also specify a different folder for any command using `--folder-name` or `--folder-id`. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions. 1. See the description of the CLI commands for updating the address attributes: ```bash yc vpc address update --help ``` 1. Get a list of available addresses: ```bash yc vpc address list ``` Result: ```text +----------------------+------+-----------------+----------+------+ | ID | NAME | ADDRESS | RESERVED | USED | +----------------------+------+-----------------+----------+------+ | e2l46k8conff******** | | 84.201.155.117 | false | true | +----------------------+------+-----------------+----------+------+ ``` The `false` value of the `RESERVED` parameter means the IP address with the `e2l46k8conff********` `ID` is dynamic. 1. Convert the address to static by using the `--reserved=true` parameter and the IP address `ID`: ```bash yc vpc address update --reserved=true ``` Result: ```text id: e2l46k8conff******** folder_id: b1g7gvsi89m3******** created_at: "2023-05-23T09:36:46Z" external_ipv4_address: address: 84.201.155.117 zone_id: ru-central1-b requirements: {} reserved: true used: true ``` Now that `reserved` is `true`, the IP address is static. 1. Save the IP address, as you will need it later. - API {#api} Use the [update](../../vpc/api-ref/Address/update.md) REST API method for the [Address](../../vpc/api-ref/Address/index.md) resource or the [AddressService/Update](../../vpc/api-ref/grpc/Address/update.md) gRPC API call. {% endlist %} ## Configure Hystax Acura Backup {#setup-hystax-acura} 1. In the [management console](https://console.yandex.cloud), open the page of the Hystax Acura Backup VM and find its public IP address. 1. Enter the VM’s public IP address in your browser. This will open the initial setup screen. {% note info %} Booting the Hystax Acura Backup VM for the first time will trigger an installation process which may take over 20 minutes. {% endnote %} By default, a Hystax Acura VM has a self-signed certificate. 1. On the page that opens, fill out these fields: * **Organization**: Name of your organization. * **Admin user login**: Administrator username. * **Password**: Administrator password. * **Confirm password**: Re-enter the administrator password. 1. Click **Next**. 1. Specify the Yandex Cloud connection settings: * **Service account ID**: ID you got when [creating a service account](#create-sa). * **Key ID**: Service account authorized key ID you got when [creating a service account](#create-sa). * **Private key**: Service account private key you got when [creating a service account](#create-sa). {% note info %} If you obtained the ID and private key in a JSON file, e.g., when creating an authorized key via the CLI, remove the line break characters (`\n`) from the ID and the private key. {% endnote %} * **Default folder ID**: [ID](../../resource-manager/operations/folder/get-id.md) of your folder. * **Availability zone**: Availability zone hosting the Hystax Acura Backup VM (the one you got when [creating a VM with Hystax Acura Backup](#create-acura-vm)). * **Hystax Service Subnet**: ID of the subnet the Hystax Acura Backup VM is connected to (the one you got when [creating a VM with Hystax Acura Backup](#create-acura-vm)). * **S3 Host**: `storage.yandexcloud.net`. * **S3 Port**: `443`. * **Enable HTTPS**: Enable HTTPS connections. * **S3 Access Key ID**: ID you got when [creating a service account](#create-sa). * **S3 Secret Access Key**: Secret key you got when [creating a service account](#create-sa). * **S3 Bucket**: Name of the bucket that stores the VM backups, the one you got when [creating a bucket](#create-bucket). * **Hystax Acura Control Panel Public IP**: Replace the value with the public IP address of the Hystax Acura Backup VM (the one you got when [creating a VM with Hystax Acura Backup](#create-acura-vm)). * **Additional parameters**: Advanced settings. Do not edit this field. 1. Click **Next**. Hystax Acura Backup will automatically check whether it can access your cloud. If the configuration is correct, you can log in to the control panel using the previously set username and password. ## Prepare and install an agent on your VMs {#prepare-agent} To install an agent on the VMs you need to back up: 1. Open the Hystax Acura Backup control panel. Click the Hystax logo. 1. On the left-hand panel, click **Download agents**. 1. Select the agent type for the your OS: * VMware. * Windows. * Linux. 1. Click **Next**. 1. Download and install an agent on the VMs you need to back up: {% list tabs group=operating_system %} - VMware {#vmware} 1. From the drop-down list, select an instance group you want to prepare agents for, e.g., `Default`. 1. Select **New VMware vSphere** and fill out these fields: * **Platform Name**. * **Endpoint**: Public IP address of the ESXi host where the replication agent will be deployed. * **Login**: User login (the user must have administrator permissions). * **Password**. Click **Next**. 1. Click **Download Agent** and wait until the download is complete. 1. Deploy the downloaded OVA agent file in your cluster on the VMs you need to back up. 1. Start the VMs with the agent. - Windows {#windows} 1. From the drop-down list, select an instance group to prepare agents for, e.g., `Default`. 1. Click **Next**. 1. Click **Download Agent** and wait until the download is complete. 1. Unpack the archive and install the agent from the `hwragent.msi` file on the VMs you need to back up. - Linux {#linux} 1. From the drop-down list, select an instance group to prepare agents for, e.g., `Default`. 1. Select Linux distribution: * **CentOS/RHEL (.rpm package)**: CentOS or Red Hat-based. * **Debian/Ubuntu (.deb package)**. 1. Select the driver installation method: * **Pre-built**: Install a driver binary. * **DKMS**: Compile as you install. 1. Click **Next**. 1. You will get commands for installing the agent on the VM. Run these commands following the instructions for your distribution and installation method. {% endlist %} A few minutes after the agent is installed, the VMs will appear in the target group of the Hystax Acura Backup control panel. ## Create a VM backup {#start-protection} After the agent is installed on the VMs under protection, they will appear in the list as `Unprotected`. To enable VM protection: 1. Open the Hystax Acura Backup control panel. Click the Hystax logo. 1. Under **Machines Groups**, deploy an instance group, e.g., `Default`. 1. In the VM list on the right, click ![image](../../_assets/console-icons/ellipsis.svg). 1. In the** Edit replication settings** menu, set up a replication schedule for the instance group by hour, day, or week, or select continuous protection. Under **Volume type**, specify the drive type for VM recovery: `network-hdd`, `network-ssd`, or `network-ssd-nonreplicated`. 1. In the **Edit retention settings** menu, set the backup retention period. For more information, see the [Hystax tutorials](https://xn--q1ach.xn--p1ai/documentation/disaster-recovery-and-cloud-backup/dr_overview.html#edit-replication-schedule). 1. Select **Start Protection**. This will start VM replication. A VM replica will include all the data of the original VM. Therefore, replication can take a while (depending on the original VM disk size). The replication status will be displayed in the **Status** column under **Machines Groups**. After the replication is complete, the VMs will switch their status to `Protected`. ## Create a disaster recovery plan {#create-recovery-plan} The disaster recovery (DR) plan includes a VM description and the network settings. The plan defines which VMs will be recovered to your cloud and specifies the VM configuration, subnet, and IP address. You can have a plan generated automatically or create one manually: {% list tabs group=instructions %} - Automatically {#auto} 1. Open the Hystax Acura Backup control panel. Click the Hystax logo. 1. Check the VMs you need in the list, click **Bulk actions**, and select **Generate DR plan**. You can also generate a plan for an instance group by clicking ![image](../../_assets/console-icons/ellipsis.svg) in the group title. 1. In the **Name** field, enter `Plan-1`. 1. In the right-hand **Subnets** section, set the properties of the subnet where the recovered VMs will start: * In the **Subnet ID** field, enter the subnet ID. * In the **CIDR** field, specify the subnet [CIDR](../../vpc/concepts/network.md#subnet). 1. Expand the VM description and edit the **Flavor name** field containing the settings of the VM being restored as follows: `---`, e.g., `3-8-16-100`. Where: * `platform`: VM [platform](../concepts/vm-platforms.md#standard-platforms), such as `1`, `2`, or `3`. * `cpu`: Number of vCPUs. * `ram`: Amount of RAM. * `core_fraction`: vCPU performance level. 1. In the **Port ip** field, enter a new IP address for the VM from the selected subnet. 1. Click **Save**. - Manually {#manual} 1. Open the Hystax Acura Backup control panel. Click the Hystax logo. 1. Click **Add DR Plan**. 1. In the **Name** field, enter `Plan-1`. 1. Under **Devices & Ranks**, click ![image](../../_assets/console-icons/ellipsis.svg). In the menu that opens, click **Add machine**. Select a VM group, e.g., `Default`. Select the VM to add to the DR plan. Repeat the steps for all VMs you need recovered. 1. In the right-hand **Subnets** section, set the properties of the subnet where the recovered VMs will start: * In the **Subnet ID** field, enter the subnet ID. * In the **CIDR** field, specify the subnet [CIDR](../../vpc/concepts/network.md#subnet). 1. Expand the VM description and edit the **Flavor name** field containing the settings of the VM being restored as follows: `---`, e.g., `3-8-16-100`. Where: * `platform`: VM [platform](../concepts/vm-platforms.md#standard-platforms), such as `1`, `2`, or `3`. * `cpu`: Number of vCPUs. * `ram`: Amount of RAM. * `core_fraction`: vCPU performance level. 1. In the **Port ip** field, enter a new IP address for the VM from the selected subnet. 1. Click **Save**. {% endlist %} {% note warning %} Make sure you specified a valid IP address for each VM. {% endnote %} ## Run recovery {#run-recover} To recover a VM from a backup, Hystax Acura Backup will create a new VM with Hystax Acura Cloud Agent in your cloud. This VM will perform all operations in the cloud. To recover a VM from a backup: 1. Open the Hystax Acura Backup control panel. Click the Hystax logo. 1. Under **DR plans**, select the plan you created previously. Expand and edit the plan, if required. 1. Click **Run Recover**. 1. In the **Cloud Site Name** field, enter a name, such as `Cloud-Site-from-Plan-1`. 1. Make sure all the required resources are there in the **Final DR plan** list and click **Run Recover**. You will see the **Cloud Sites** section in the Hystax Acura Backup control panel. The VM recovery may take a while. The recovery status will be displayed in the **Status** column under **Machines**. Wait until it switches to `Running`. 1. Open the [management console](https://console.yandex.cloud) and make sure this restored all required resources. ## How to delete the resources you created {#clear-out} To stop paying for the resources you created: 1. [Delete](../operations/vm-control/vm-delete.md) the Hystax Acura Backup VM. 1. [Delete](../operations/vm-control/vm-delete.md) the auxiliary Hystax Cloud Agent VMs. 1. [Delete](../operations/vm-control/vm-delete.md) the recovered VMs. 1. [Delete](../../storage/operations/buckets/delete.md) the bucket. 1. [Delete](../../iam/operations/sa/delete.md) the service account for Hystax Acura Backup. 1. [Delete](../../vpc/operations/address-delete.md) the public static IP address you reserved.