Acronis Cyber Infrastructure Cost-Efficient and Multi-Purpose Infrastructure Solution User Guide

: June 4, 2024
: Acronis

Table of Contents

Introduction
Hardware requirements
Installing Acronis Cyber Infrastructure
Creating the storage cluster
Enabling management node high availability
Deploying the compute cluster
Creating a virtual machine
References
Read User Manual Online (PDF format)
Download This Manual (PDF format)
ps1 net user

Cyber Infrastructure Cost-Efficient and Multi-Purpose Infrastructure Solution
User Guide

acronis.com
Acronis Cyber Infrastructure
5.0

Introduction

Acronis Cyber Infrastructure represents a new generation of hyper-converged infrastructures targeted at both service providers and end customers. It is a scale-out, cost-efficient, and multipurpose solution that combines universal storage and high-performance virtualization.
This guide describes how to set up a full-fledged storage cluster on three nodes, deploy a compute cluster on top of it, and create a virtual machine.

Hardware requirements

A minimum Acronis Cyber Infrastructure installation recommended for production consists of three nodes for storage and compute services with enabled high availability for the management node. This is to ensure that the cluster can survive the failure of one node without data loss. The following table lists the minimal hardware requirements for all three nodes. The recommended configurations are provided in “System requirements” in the Administrator Guide.

Type	Management node with storage and compute
CPU	64-bit x86 processors with AMD-V or Intel VT hardware virtualization

extensions enabled. 16 cores*
RAM| 32 GB
Storage| 1 disk: system + metadata, 100+ GB SATA HDD 1 disk: storage, SATA HDD, size as required
Network| 10 GbE for storage traffic and 1 GbE for other traffic

A CPU core here is a physical core in a multicore processor (hyperthreading is not taken into account).

Installing Acronis Cyber Infrastructure

Important
The time needs to be synchronized via NTP on all nodes in the same cluster. Make sure that the nodes can access the NTP server.
To install Acronis Cyber Infrastructure, do the following:

Obtain the distribution ISO image. To do that, visit the product page and submit a request for the trial version. You can also download the ISO from Acronis Cyber Cloud: a. Go to the management portal and select SETTINGS > Locations in the left menu. b. Click Add backup storage and click the Download ISO button in the open window.
Prepare the bootable media using the distribution ISO image (mount it to an IPMI virtual drive, create a bootable USB drive, or set up a PXE server).
Boot the server from the chosen media.
On the Welcome screen, choose Install Acronis Cyber Infrastructure.
In step 1, carefully read the End-User License Agreement. Accept it by selecting the I accept the End-User License Agreement check box, and then click Next.
In step 2, configure a static IP address for the network interface and provide a hostname: either a fully qualified domain name (.) or a short name (). A dynamic IP is not recommended as it might cause issues with reaching the nodes. Check that the network settings are correct.
In step 3, choose your time zone. The date and time will be set via NTP. You will need an Internet connection for synchronization to complete.
In step 4, specify what type of node you are installing. First, deploy one primary node. Then, deploy as many secondary nodes as you need.
If you chose to deploy the primary node, select two network interfaces: for internal management and configuration and for access to the admin panel. Also, create and confirm a password for the super admin account of the admin panel. This node will be the management node.
If you chose to deploy a secondary node, provide the IP address of the management node and the token. Both are obtained from the admin panel. Log in to the admin panel on port 8888. The panel’s IP address is shown in the console after deploying the primary node. Enter the default username admin and the super admin account password. In the admin panel, open Infrastructure > Nodes, and then click Connect node, to invoke a screen with the management node address and the token. The node may appear on the Infrastructure > Nodes screen with the Unassigned status as soon as the token is validated. However, you will be able to join it to the storage cluster only after the installation is complete.
On step 5, choose a disk for the operating system. This disk will have the supplementary role System, although you will still be able to set it up for data storage in the admin panel. You can also create software RAID1 for the system disk, to ensure its high performance and availability.
On step 6, enter and confirm the password for the root account, and then click Start installation.

Once the installation is complete, the node will reboot automatically. The admin panel IP address will be shown in the welcome prompt.

Creating the storage cluster

To create the storage cluster, do the following:

Open the Infrastructure > Nodes screen, and then click Create storage cluster.
[Optional] To configure the disk roles or node location, click the cogwheel icon.
Enter a name for the cluster. It may only contain Latin letters (a-z, A-Z), numbers (0-9), and hyphens (“-“).
. Enable encryption, if required.
Click Create.

You can monitor cluster creation on the Infrastructure > Nodes screen. The creation might take some time, depending on the number of disks to be configured. Once the configuration is complete, the cluster is created.
To add more nodes to the storage cluster, do the following:

On the Infrastructure > Nodes screen, click an unassigned node
On the node right pane, click Join to cluster.
Click Join to assign the roles to disks automatically and add the node to the default location.Alternatively, click the cogwheel icon to configure the disk roles or node location.

Enabling management node high availability

To make your infrastructure more resilient and redundant, you can create a high availability (HA) configuration of three nodes.
Management node HA and compute cluster are tightly coupled, so changing nodes in one usually affects the other.
Take note of the following:

All nodes in the HA configuration will be added to the compute cluster.
Single nodes cannot be removed from the compute cluster as they are included in the HA configuration. In such a case, the compute cluster can be destroyed completely, but the HA configuration will remain. This is also true and vice versa, the HA configuration can be deleted, but the compute cluster will continue working.

To enable high availability for the management node and admin panel, do the following:

On the Settings > Management node screen, open the Management high availability tab.
Select three nodes, and then click Create HA. The management node is automatically selected.
On Configure network, verify that the correct network interfaces are selected on each node. Otherwise, click the cogwheel icon for a node and assign networks with the Internal management and Admin panel traffic types to its network interfaces. Click Proceed.
On Configure network, provide one or more unique static IP addresses for the highly available admin panel, compute API endpoint, and interservice messaging. Click Done.

Once the high availability of the management node is enabled, you can log in to the admin panel at the specified static IP address (on the same port 8888).

Deploying the compute cluster

Before creating a compute cluster, make sure the following requirements are met:

The traffic types VM private, VM public, Compute API, and VM backups are assigned to networks. The full recommended network configuration is described in “Setting up networks for the compute cluster” in the Administrator Guide.
The nodes to be added to the compute cluster are connected to these networks and to the same network with the VM public traffic type.
The nodes to be added to the compute cluster have the same CPU model (refer to “Setting virtual machine CPU model” in the Administrator Guide).
(Recommended) High availability for the management node is enabled (refer to “Enabling management node high availability” (p. 8)).

To create the compute cluster, do the following:

Open the Compute screen, and then click Create compute cluster.
On the Nodes step, add nodes to the compute cluster:
a. Select the nodes to add to the compute cluster. You can only select nodes with the Configured network state. Nodes in the management node high availability cluster are automatically selected to join the compute cluster.
b. If the node network interfaces are not configured, click the cogwheel icon, select the networks as required, and then click Apply.
c. Click Next.
On the Physical network step, do the following:
a. Enable or disable IP address management: l With IP address management enabled, VMs connected to the network will automatically be assigned IP addresses from allocation pools by the built-in DHCP server and use custom DNS servers. Additionally, spoofing protection will be enabled for all VM network ports by default. Each VM network interface will be able to accept and send IP packets only if it has IP and MAC addresses assigned. You can disable spoofing protection manually for a VM interface, if required. l With IP address management disabled, VMs connected to the network will obtain IP addresses from the DHCP servers in that network, if any. Also, spoofing protection will be disabled for all VM network ports, and you cannot enable it manually. This means that each VM network interface, with or without assigned IP and MAC addresses, will be able to accept and send IP packets. In any case, you will be able to manually assign static IP addresses from inside the VMs.
b. Provide the required details for the physical network:
i. Select an infrastructure network to connect the physical network to.
ii. Select the physical network type: select VLAN and specify a VLAN ID to create a VLAN-based network, or select Untagged to create a flat physical network.
iii. If you enabled IP address management, the subnet IP range in the CIDR format will be filled in automatically. Optionally, specify a gateway. If you leave the Gateway field blank, the gateway will be omitted from network settings.
c. Click Next.
The selected physical network will appear in the list of computing networks on computing cluster’s Network tab. By default, it will be shared between all future projects. You can disable the network access on the network right pane later.
If you enabled IP address management, you will move on to the DHCP and DNS step, where you can configure the network settings for IP address management:
a. Enable or disable the built-in DHCP server:
• With the DHCP server enabled, VM network interfaces will automatically be assigned IP addresses: either from allocation pools or, if there are no pools, from the network’s entire IP range. The DHCP server will receive the first two IP addresses from the IP pool. For example:
o In a subnet with CIDR 192.168.128.0/24 and without a gateway, the DHCP server will be assigned the IP addresses 192.168.128.1 and 192.168.128.2.
o In a subnet with CIDR 192.168.128.0/24 and the gateway IP address set to 192.168.128.1, the DHCP server will be assigned the IP addresses 192.168.128.2 and 192.168.128.3.
• With the DHCP server disabled, VM network interfaces will still get IP addresses, but you will have to manually assign them inside VMs.
The virtual DHCP service will work only within the current network and will not be exposed to other networks.
b. Specify one or more allocation pools (ranges of IP addresses that will be automatically assigned to VMs).
c. Specify DNS servers that will be used by virtual machines. These servers can be delivered to VMs via the built-in DHCP server or by using the cloud- init network configuration (if cloud-init is installed in the VM).
d. Click Add.
On the Add-on services step, enable the additional services that will be installed during the compute cluster deployment. You can also install these services later. Then, click Next.
Note Installing Kubernetes automatically installs the load balancer service as well.
On the Summary step, review the configuration, and then click Create cluster. You can monitor compute cluster deployment on the Compute screen.

Creating a virtual machine

Note
For supported guest operating systems and other information, refer to “Managing virtual machines” in the Administrator Guide.

On the Virtual machine’s screen, click Create a virtual machine. A window will open where you will need to specify the VM parameters.
Specify a name for the new VM.
Select the VM boot media:
l If you have an ISO image or a template
a. Select Image in the Deploy from section, and then click Specify in the Image section.
b. In the Images window, select the ISO image or template and then click Done.
• If you have a compute boot volume
a. Select Volume in the Deploy from section, and then click Specify in the Volumes section.
b. In the Volumes window, click Attach.
c. In the Attach volume window, find and select the volume, and then click Attach.
If you attach more than one volume, the first attached volume becomes the boot volume, by default. To select another volume as bootable, place it first in the list by clicking the up arrow button next to it.
Note
If you select an image or volume with an assigned placement, the created VM will also inherit this placement.
After selecting the boot media, volumes required for this media to boot will be automatically added to the Volumes section.
Configure the VM disks:
a. In the Volumes window, make sure the default boot volume is large enough to accommodate the guest OS. Otherwise, click the ellipsis icon next to it, and then Edit. Change the volume size and click Save.
b. [Optional] Add more disks to the VM by creating or attaching volumes. To do this, click the pencil icon in the Volumes section, and then Add or Attach in the Volumes window.
c. Select volumes that will be removed during the VM deletion. To do this, click the pencil icon in the Volumes section, click the ellipsis icon next to the needed volume, and then Edit. Enable Delete on termination and click Save.
d. When you finish configuring the VM disks, click Done.
Choose the amount of RAM and CPU resources that will be allocated to the VM in the Flavor section. In the Flavor window, select a flavor, and then click Done.
Important When choosing a flavor for a VM, ensure it satisfies the hardware requirements of the guest OS.
Note To select a flavor with an assigned placement, you can filter flavors by placement. The VM created from such a flavor will also inherit this placement.
Add network interfaces to the VM in the Networks section:
a. In the Network interfaces window, click Add to attach a network interface.
b. In the Add network interface window, select a compute network to connect to, and then specify MAC address, IPv4 and/or IPv6 addresses, and security groups. By default, MAC and primary IP addresses are assigned automatically. To specify them manually, clear the Assign automatically checkboxes, and enter the desired addresses. Optionally, assign additional IP addresses to the network interface in the Secondary IP addresses section. Note that a secondary IPv6 address is not available for an IPv6 subnet that works in the SLAAC or DHCPv6 stateless mode.
Note Secondary IP addresses, unlike the primary ones, will not be automatically assigned to the network interface inside the virtual machine guest OS. You should assign them manually.
• If you selected a virtual network with enabled IP address management, In this case, spoofing protection is enabled and the default security group is selected by default. This security group allows all incoming and outgoing traffic on all the VM ports. If required, you can select another security group or multiple security groups. To disable spoofing protection, clear all of the checkboxes and turn off the toggle switch. Security groups cannot be configured with disabled spoofing protection.
• If you selected a virtual network with disabled IP address management, In this case, spoofing protection is disabled by default and cannot be enabled. Security groups cannot be configured for such a network.
• If you selected a shared physical network In this case, spoofing protection cannot be configured by a self-service user. If you want to enable or disable spoofing protection, contact your system administrator.
After specifying the network interface parameters, click Add. The network interface will appear in the Network interfaces list.
c. [Optional] If required, edit IP addresses and security groups of newly added network interfaces. To do this, click the ellipsis icon, click Edit, and then set the parameters. d. When you finish configuring the VM network interfaces, click Done.
[Optional] If you have chosen to boot from a template or volume, which has cloud-init and OpenSSH installed:
Important
As cloud images have no default password, you can access VMs deployed from them only by using the key authentication method with SSH.
• Add an SSH key to the VM, to be able to access it via SSH without a password. In the Select an SSH key window, select an SSH key and then click Done.
• Add user data to customize the VM after launch, for example, change a user password. Write a cloud-config or shell script in the Customization script field or browse a file on your local server to load the script from.
To inject a script in a Windows VM, refer to the Cloudbase-Init documentation. For example, you can set a new password for the account using the following script:

ps1 net user
[Optional] Enable CPU and RAM hot plug for the VM in the Advanced options, to be able to change its flavor when the VM is running. You can also enable hotplug after the VM is created.
Note If you do not see this option, the CPU and RAM hot plug is disabled in your project. To enable it, contact your system administrator.
After configuring all of the VM parameters, click Deploy to create and boot the VM. If you are deploying the VM from an ISO image, you need to install the guest OS inside the VM by using the built-in VNC console. Virtual machines created from a template or a boot volume already have a preinstalled guest OS.