Managing Updates

You can update your Acronis Storage infrastructure using the management panel.

Important

To check for and download updates, the cluster must be healthy and each node in the infrastructure must be able to open outgoing Internet connections.

To update Acronis Storage, do the following:

  1. Open the SETTINGS > Updates screen and click CHECK FOR UPDATES. The script will run yum update on each node. If updates are available for a node, said node’s status will change to Update available.

    If you are running the latest version of Acronis Storage, you should see a notification about upgrading to Acronis Software-Defined Infrastructure 2.5. See the following subsection for more details.

  2. To apply all available updates, click UPDATE NOW.

While updates are being applied, some of the Acronis Storage services might be unavailable for a short period of time.

Upgrading to Acronis Software-Defined Infrastructure 2.5

You can upgrade your Acronis Storage installation to Acronis Software-Defined Infrastructure 2.5 in-place from the management panel. The procedure is similar to updating.

The following conditions must be met in order to upgrade:

  • All nodes in the storage cluster are updated to the latest version, which is Acronis Storage 2.4 Update 2.

  • All cluster nodes have unique hostnames.

    Make sure that all cluster nodes have unique hostnames. Note that in Acronis Software-Defined Infrastructure 2.5 hostname management via /etc/hostname is deprecated.

  • All nodes have the storage agent installed and running.

    Cluster nodes deployed as management-only do not have the storage agent service installed and running. To proceed with the upgrade, do the following on each such node:

    1. Install and enable the agent service by running

      # yum install vstorage-ui-agent
# systemctl start vstorage-ui-agent
# systemctl enable vstorage-ui-agent

    2. Register the agent on the management node by running

      /usr/libexec/vstorage-ui-agent/bin/register-storage-node.sh -m MN_ADDRESS -t TOKEN

      where MN_ADDRESS is the management node IP address and TOKEN is the token from the Add node screen.

  • LDAP is not configured.

    Acronis Software-Defined Infrastructure 2.5 implements a new user model that does not support configuring LDAP/AD via the management panel anymore. As a result, LDAP/AD users will not be able to log in to the management panel after the upgrade. Make sure that you can access the cluster in ways other than via LDAP/AD. If you need LDAP/AD in Acronis Software-Defined Infrastructure 2.5, please create a support ticket. The technical support team will help you configure it manually.

  • Management node high availability is disabled.

    The WebCP database structure and backend management protocol will be changed during upgrade. Because of this, you need to disable management node HA before upgrading.

  • No tasks are running.

    Make sure there are no running tasks like adding or removing cluster nodes, reconfiguring network adapters, or similar.

If the storage cluster does not meet any of these requirements, you will see corresponding alerts when attempting to upgrade.

Nodes will be upgraded one at a time. Each node will reboot to finalize the procedure, so you may expect some downtime. Highly available storage services, however, should continue working.

During upgrade, iSCSI targets will be migrated to iSCSI target groups, because Acronis Software-Defined Infrastructure 2.5 provides a completely new high-performance iSCSI target subsystem with ALUA support, a new high availability mechanism, and other features. After the upgrade, you will still be able to run older iSCSI targets created on version 2.4 alongside new targets. For each older target, a target group will be automatically created and iSCSI LUNs will be moved to iSCSI volumes. Nevertheless, it is recommended to plan maintenance for iSCSI targets after the upgrade to create new targets and move LUNs to them (detach volumes and attach them to new target groups).

Upgrading with Minimal Downtime of iSCSI Targets

Before you proceed, find out which node is the management node (MN), i.e. hosts the management panel. It will be the last to upgrade.

Do the following on each node in succession, excluding the MN:

  1. Get a list of iSCSI targets running on the node. For example:

    # vstorage-iscsi list
IQN STATUS LUNs HOST PORTAL(s) METADATA
iqn.2014-06.com.vstorage:t1 running 0 257ef7411e48466c 192.168.15.200 tgtd iscsi
...

  2. Stop all listed targets. For example:

    # vstorage-iscsi stop -t iqn.2014-06.com.vstorage:t1 --force
...

  3. Move all targets on the node to the MN. Log in to the MN via SSH, and run these two commands for each target. For example:

    # vstorage-iscsi register -t iqn.2014-06.com.vstorage:t1 --force
# vstorage-iscsi start -t iqn.2014-06.com.vstorage:t1

  4. Upgrade the node to version 2.5 as as described in Upgrading to Acronis Software-Defined Infrastructure 2.5.

Now that you have upgraded all the nodes except the MN, upgrade the MN. Now you can move the iSCSI targets back by connecting to their original nodes via SSH and using the vstorage-iscsi register and vstorage-iscsi start commands.

Jun 18, 2019
Edit Raw Print