Administrator’s Command Line Guide
Table Of Contents
- Introduction
- Accessing Acronis Storage Clusters via iSCSI
- Preparing to Work with Acronis Storage iSCSI Targets
- Creating and Running Acronis Storage iSCSI Targets
- Listing Acronis Storage iSCSI Targets
- Transferring Acronis Storage iSCSI Targets Between Acronis Storage Nodes
- Stopping Acronis Storage iSCSI Targets
- Deleting Acronis Storage iSCSI Targets
- Configuring Multipath I/O for Acronis Storage iSCSI Targets
- Managing CHAP Accounts for Acronis Storage iSCSI Targets
- Managing LUN Snapshots
- Accessing Acronis Storage Clusters via S3 Protocol
- Monitoring Acronis Storage Clusters
- Managing Cluster Security
- Maximizing Cluster Performance
Chapter 4. Monitoring Acronis Storage Clusters
Status Description
degraded Percentage of chunks with the number of active replicas lower than normal but
equal to or higher than the set minimum. Such chunks can be read from and
written to. However, in the latter case a degraded chunk becomes urgent.
urgent Percentage of chunks which are degraded and have non-identical replicas. Repli-
cas of a degraded chunk may become non-identical if some of them are not ac-
cessible during a write operation. As a result, some replicas happen to have the
new data while some still have the old data. The latter are dropped by the cluster
as fast as possible. Urgent chunks do not affect information integrity as the actual
data is stored in at least the set minimum amount of replicas.
standby Percentage of chunks that have one or more replicas in the standby state. A replica
is marked standby if it has been inactive for no more than 5 minutes.
overcommitted Percentage of chunks that have more replicas than normal. Usually these chunks
appear after the normal number of replicas has been lowered or a lot of data has
been deleted. Extra replicas are eventually dropped, however, this process may
slow down during replication.
4.4 Monitoring Clients
By monitoring clients, you can check the status and health of servers that you use to access virtual machines
and Containers. To monitor clients, use the vstorage -c <cluster_name> top command, for example:
50










