Creating a primary server for Acronis Disaster Recovery

Overview

This article describes how to create your primary servers for Acronis Disaster Recovery Cloud.

Prerequisites

  • One of the connectivity types to the cloud site must be set.

To create a primary server

  1. Go to Disaster Recovery > Servers > Primary servers tab.
  2. Click Create.
  3. Select a template for the new virtual machine.
  4. Select the flavor of the configuration (number of virtual cores and the size of RAM). The following table shows the maximum total amount of disk space (GB) for each flavor.
TypevCPURAM (GB)Maximum total amount of disk space (GB)
F112500
F2141000
F3282000
F44164000
F58328000
F6166416000
F71612832000
F81625664000
Note

You can see the compute points for every option. The number of compute points reflects the cost of running the primary server per hour. For more information, see Compute points.

  1. (Optional)Change the virtual disk size. If you need more than one hard disk, click Add disk, and then specify the new disk size. Currently, you can add no more than 10 disks for a primary server.
  2. Specify the cloud network in which the primary server will be included.
  3. Select the DHCP option.
DHCP optionDescription
Provided by cloud siteDefault setting. The IP address of the server will be provided by an automatically configured DHCP server in the cloud.
CustomThe IP address of the server will be provided by your own DHCP server in the cloud.
  1. (Optional) Specify the MAC address.
    The MAC address is a unique identifier that is assigned to the network adapter of the server. If you use custom DHCP, you can configure it to always assign a specific IP address to a specific MAC address. This ensures that the primary server always gets the same IP address. You can run applications that have licenses that are registered with the MAC address.
  2. Specify the IP address that the server will have in the production network. By default, the first free IP address from your production network is set.
    Note

    If you use a DHCP server, add this IP address to the server exclusion list in order to avoid IP address conflicts.
    If you use a custom DHCP server, you must specify the same IP address in IP address in production network as the one configured in the DHCP server. Otherwise, test failover will not work properly, and the server will not be reachable via a public IP address.

  3. (Optional)Select the Internet access check box.
    This will enable the primary server to access the Internet. By default, TCP port 25 is open for outbound connections to public IP addresses.
  4. (Optional)Select the Use public IP address check box.
    Having a public IP address makes the primary server available from the Internet. If you leave the check box cleared, the server will be available only in your production network.
    The public IP address will be shown after you complete the configuration. By default, TCP port 443 is open for inbound connections to public IP addresses.
    Note

    If you clear the Use Public IP address check box or delete the recovery server, its public IP address will not be reserved.

  5. (Optional)Select Set RPO threshold.
    RPO threshold defines the maximum allowable time interval between the last recovery point and the current time. The value can be set within 15 – 60 minutes, 1 – 24 hours, 1 – 14 days.
  6. Define the primary server name.
  7. (Optional)Specify a description for the primary server.
  8. (Optional)Click the Cloud firewall rules tab to edit the default firewall rules. For more information, see Setting firewall rules for cloud servers.
  9. Click Create.

The primary server becomes available in the production network. You can manage the server by using its console, RDP, SSH, or TeamViewer.

Share this:
FacebookTwitterWhatsAppViberCopy LinkTelegramLinkedIn
Updated on July 6, 2023
Was this article helpful?

Related Articles

Need Support?
Can't find the answer you're looking for?
Contact Support