Acronis Backup Gateway Quick Start Guide

Acronis Cyber Infrastructure 3.0

Backup Gateway Quick Start Guide

November 26, 2019

”Acronis” and ”Acronis Secure Zone” are registered trademarks of Acronis International GmbH.

”Acronis Compute with Conﬁdence”, ”Acronis Startup Recovery Manager”, ”Acronis Instant Restore”, and the Acronis logo are trademarks of Acronis

International GmbH.

Linux is a registered trademark of Linus Torvalds.

VMware and VMware Ready are trademarks and/or registered trademarks of VMware, Inc. in the United States and/or other jurisdictions.

Windows and MS-DOS are registered trademarks of Microsoft Corporation.

All other trademarks and copyrights referred to are the property of their respective owners.

Distribution of substantively modiﬁed versions of this document is prohibited without the explicit permission of the copyright holder.

Distribution of this work or derivative work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is

obtained from the copyright holder.

DOCUMENTATION IS PROVIDED ”AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED

WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT

SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Third party code may be provided with the Software and/or Service. The license terms for such third-parties are detailed in the license.txt ﬁle located in

the root installation directory. You can always ﬁnd the latest up-to-date list of the third party code and the associated license terms used with the

Software and/or Service at http://kb.acronis.com/content/7696.

Acronis patented technologies

Technologies, used in this product, are covered and protected by one or more U.S. Patent Numbers: 7,047,380; 7,246,211; 7,275,139; 7,281,104;

7,318,135; 7,353,355; 7,366,859; 7,383,327; 7,475,282; 7,603,533; 7,636,824; 7,650,473; 7,721,138; 7,779,221; 7,831,789; 7,836,053; 7,886,120; 7,895,403;

7,934,064; 7,937,612; 7,941,510; 7,949,635; 7,953,948; 7,979,690; 8,005,797; 8,051,044; 8,069,320; 8,073,815; 8,074,035; 8,074,276; 8,145,607; 8,180,984;

8,225,133; 8,261,035; 8,296,264; 8,312,259; 8,347,137; 8,484,427; 8,645,748; 8,732,121; 8,850,060; 8,856,927; 8,996,830; 9,213,697; 9,400,886; 9,424,678;

9,436,558; 9,471,441; 9,501,234; and patent pending applications.

Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1 About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.2 Hardware Requirements for ABGW-only Installations . . . . . . . . . . . . . . . . . . . . . . . . . 1

2. Installing Acronis Cyber Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3. Creating the Storage Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4. Connecting Acronis Backup Software to Storage Backends via Backup Gateway . . . . . . . . . . 7

4.1 Connecting to the Local Storage Cluster via Backup Gateway . . . . . . . . . . . . . . . . . . . . . 8

4.2 Connecting to External NFS Shares via Backup Gateway . . . . . . . . . . . . . . . . . . . . . . . . 10

4.3 Connecting to Public Cloud Storage via Backup Gateway . . . . . . . . . . . . . . . . . . . . . . . . 13

4.3.1 Important Requirements and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.3.2 Setting Up Backup Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5. Updating Certiﬁcate for Backup Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

6. Re-registering Backup Gateway in a New Acronis Backup Advanced . . . . . . . . . . . . . . . . . . 19

7. Migrating Backups from Older Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

7.1 Migrating Backups from Acronis Storage 1.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

7.2 Migrating Backups from Acronis Storage Gateway 1.6 and 1.7 (NFS) . . . . . . . . . . . . . . . . . 25

8. Monitoring Backup Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

9. Releasing Nodes from Backup Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

CHAPTER 1

Introduction

1.1 About This Guide

This guide describes how to deploy Acronis Cyber Infrastructure on a single node with the sole purpose of

creating Backup Gateway endpoints.

1.2 Hardware Requirements for ABGW-only Installations

Normally, Acronis Cyber Infrastructure is installed on at least ﬁve nodes to fully utilize its built-in high

availability and data redundancy capabilities. However, if you only want to use the ABGW feature, you can

deploy a very basic installation on a single virtual or physical node. Although in this case you may need to

provide data redundancy by other means or risk losing user data. You can do the following:

• Use a virtual machine (VM) with at least two virtual HDDs (three are recommended). In this case, only

one HDD will be used for data storage and you may need to make sure that the VM is made redundant

by the virtualization solution it runs on.

• Use a physical server with at least two disks (three are recommended). Have in mind that you will need

to use more disks for storage to enable data redundancy. For more details on how to plan your server

conﬁguration, see the Installation Guide.

Other minimal requirements are:

• 120 GB or higher capacity of each HDD/SSD

Chapter 1. Introduction

Note: If you plan to use Backup Gateway to store backups in the cloud, make sure the local storage

cluster has plenty of logical space for staging (keeping backups locally before sending them to the

cloud). For example, if you perform backups daily, provide enough space for at least 1.5 days’ worth of

backups. For more details, see the Administrator’s Guide.

• 4 logical CPUs*

• 4GB RAM**

• 1GbE network interface with a static IP address. You can also use the same network interface for both

internal and external traﬃc (but you are advised to conﬁgure secure networking later).

* A logical CPU is a core (thread) in a multicore (multithreading) processor.

** Each chunk server (CS), e.g., storage disk, requires 1 GB of RAM (0.5 GB anonymous memory + 0.5 GB

page cache). The total page cache limit is 12 GB. In addition, each metadata server (MDS) requires 0.2 GB of

RAM + 0.1 GB per 100TB of physical storage space.

CHAPTER 2

Installing Acronis Cyber Infrastructure

To install Acronis Cyber Infrastructure, do the following:

1. Prepare 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).

2. Boot the server from the chosen media.

3. On the welcome screen, choose Install Acronis Cyber Infrastructure.

4. On step 1, please carefully read the End-User License Agreement. Accept it by ticking the I accept the

End-User License Agreement checkbox and click Next.

5. On step 2, conﬁgure a static IP address for the NIC and provide a hostname: either a fully qualiﬁed

domain name (hostname, domainname) or a short name (hostname).

6. On step 3, choose your time zone. Date and time will be set via NTP. You will need an Internet

connection for synchronization to complete.

7. On 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 conﬁguration and for access to the admin panel. Also create and conﬁrm a password for the

superadmin account of the admin panel.

• 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. Panel’s IP

address is shown in the console after deploying the primary node. Use the default user name

Chapter 2. Installing Acronis Cyber Infrastructure

shown on the login screen and the primary node’s root password. In the admin panel, open

INFRASTRUCTURE > Nodes and click ADD NODE to invoke a screen with the management node

address and the token.

The node may appear on the INFRASTRUCTURE > Nodes screen in the UNASSIGNED list as soon

as token is validated. However, you will be able to join it to the storage cluster only after the

installation is complete.

8. 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.

9. On step 6, enter and conﬁrm the password for the root account and 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.

CHAPTER 3

Creating the Storage Cluster

To create the storage cluster, do the following:

1. Open the INFRASTRUCTURE > Nodes screen and click a node in the UNASSIGNED list.

2. On the node overview screen, click Create cluster.

3. In the Cluster ﬁeld, type a name for the cluster. The name may only contain Latin letters (a-z, A-Z),

numbers (0-9), underscores (“_”) and hyphens (“-“).

4. Click New cluster.

You can monitor cluster creation in the HEALTHY list of the INFRASTRUCTURE > Nodes screen. The creation

Chapter 3. Creating the Storage Cluster

might take some time depending on the number of disks to be conﬁgured. Once the automatic conﬁguration

is complete, the cluster is created.

CHAPTER 4

Connecting Acronis Backup Software to Storage Backends via Backup Gateway

Note: If you are going to migrate your Acronis Storage Gateway, skip the steps described in this chapter and

proceed to Migrating Backups from Older Solutions (page 20).

The Backup Gateway storage access point (also called “gateway”) is intended for service providers who use

Acronis Backup Cloud and/or Acronis Backup Advanced and want to organize an on-premise storage for their

clients’ backed-up data.

Backup Gateway enables a service provider to easily conﬁgure storage for the proprietary

deduplication-friendly data format used by Acronis.

Backup Gateway supports the following storage backends:

• storage clusters with software redundancy by means of erasure coding

• NFS shares

• public clouds, including a number of S3 solutions as well as Microsoft Azure, OpenStack Swift, and

Google Cloud Platform

While your choice should depend on scenario and requirements, it is recommended to keep Acronis backup

data in the local storage cluster. In this case, you can have the best performance due to WAN optimizations

and data locality. Keeping backups in an NFS share or a public cloud implies the unavoidable data transfer

Chapter 4. Connecting Acronis Backup Software to Storage Backends via Backup Gateway

and other overhead, which reduces overall performance.

Take note of the following:

• When conﬁguring Backup Gateway, you will need to provide the credentials of your administrator

account in the Acronis backup software.

• In cases when not local but external storage (e.g., NFS) is used with Backup Gateway, redundancy has to

be provided by the said external storage. Backup Gateway does not provide data redundancy or

perform data deduplication itself.

4.1 Connecting to the Local Storage Cluster via Backup Gateway

Before you proceed, make sure that the destination storage has enough space for both existing and new

backups.

To set up Backup Gateway, do the following:

1. On the INFRASTRUCTURE > Networks screen, make sure that the ABGW private and ABGW public

traﬃc types are added to your networks.

2. In the left menu, click STORAGE SERVICES > Backup storage.

3. Select the node(s) to run the gateway services on and click Create gateway in the right menu.

4. Select This Acronis cluster as storage type.

5. Make sure the correct network interface is selected in the drop-down list. Click NEXT.

If necessary, click the cogwheel icon and conﬁgure node’s network interfaces on the Network

Conﬁguration screen.

6. On the Volume Parameters tab, select the desired tier, failure domain, and data redundancy mode.

+ 24 hidden pages