acronis.com Acronis Cyber Infrastructure 5.
Table of contents Introduction 3 Hardware requirements 4 Installing Acronis Cyber Infrastructure 5 Creating the storage cluster 7 Enabling management node high availability 8 Deploying the compute cluster 9 Creating a virtual machine 2 14 © Acronis International GmbH, 2003-2023
Introduction Acronis Cyber Infrastructure represents a new generation of hyperconverged 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 failure of one node without data loss. The following table lists the minimal hardware requirements for all the three nodes. The recommended configurations are provided in "System requirements" in the Administrator Guide.
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: 1. 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 Protect Cloud: a. Go to the management portal and select SETTINGS > Locations in the left menu. b.
10. 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: 1. Open the Infrastructure > Nodes screen, and then click Create storage cluster. 2. In the Create storage cluster window, enter a name for the cluster. The cluster name may only contain Latin letters (a-z, A-Z), numbers (0-9), and hyphens ("-"). It must start with a letter and end with a letter or number. 3. [Optional] Enable disk encryption for tiers. You can also enable it later. 4.
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: l All nodes in the HA configuration will be added to the compute cluster. l Single nodes cannot be removed from the compute cluster as they are included in the HA configuration.
Deploying the compute cluster Before creating a compute cluster, make sure the following requirements are met: l 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. l 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.
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.
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. l With the DHCP server disabled, VM network interfaces will still get IP addresses, but you will have to manually assign them inside VMs.
7. On the Storage policy step, select a redundancy mode, storage tier, and failure domain for the default policy, which will be applied to uploaded images and base volumes created from these images. Alternatively, enable Use the default storage policy parameters, to define these parameters automatically.
8. 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. 1. On the Virtual machines screen, click Create virtual machine. A window will open where you will need to specify the VM parameters. 2. Specify a name for the new VM. 3. 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.
After selecting the boot media, volumes required for this media to boot will be automatically added to the Volumes section. 4. 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.
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 one, will not be automatically assigned to the network interface inside the virtual machine guest OS. You should assign them manually. l 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.
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. 7.
l 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 8. [Optional] Enable CPU and RAM hot plug for the VM in Advanced options, to be able to change its flavor when the VM is running. You can also enable hot plug after the VM is created. Note If you do not see this option, CPU and RAM hot plug is disabled in your project.
