This article describes how to troubleshoot performance issues with Acronis Backup Command line tool.
This article applies to:
- Acronis Backup (Acronis Backup & Recovery) 11.5
If you experience issues with performance of other Acronis product, please refer to article Troubleshooting Performance issues in Acronis Software.
Introduction
It is important to understand that unlike the trueimagecmd utility used in the older Acronis products, acrocmd does not contain any tools that physically execute the commands. It merely provides the command-line interface to Acronis Backup components—agents, storage nodes and the management server. The main article for troubleshooting performance issues is Acronis Backup: Troubleshooting Performance Issues.
Before starting investigation in accord with this article, make sure, the process (backup for example), is not hanged. If this is the case, please follow Troubleshooting Application Lockups.
Performance depends on many factors, but the two are mainly important: hardware limitations and product underperforming. While hardware limitations cannot be overcome without changing the hardware, underperforming has to be fixed by Acronis development. So it is important to make sure the performance bottleneck is identified correctly. This article aims to help you with it.
Solution
In general, perfomance improvements are constantly being worked on and released, so updating to the latest build is always recommened for the best perfomance of backup and other opertaions.
Please make sure the system meets system requirements listed in: Web-help: System requirements.
In Windows
1. If the backup is being created to the personal vault (local drive), the root of the issue may be caused by the Agent performance. Please collect Acronis system report and ProcMon report in this case (see below).
2. If the backup is being created to the centralized unmanaged vault, the issue may be caused by the Agent performance or network. Please collect Acronis system report, ProcMon report and PCAP report (see below).
3. If the backup is being created to the centralized managed vault, the issue may be caused by the Agent performance Acronis Storage Node performance or network. Please collect Acronis system report from machines where Agent and Acronis Storage Node are installed, ProcMon report from both machines and PCAP report (see below).
In Linux
1. If the backup is being created to the personal vault (local drive), the root of the issue may be caused by the Agent performance. Please collect Strace report during process running and Acronis system report after it finishes in this case (see below).
2. If the backup is being created to the centralized unmanaged vault, the issue may be caused by the Agent performance or network. Please collect Strace and PCAP report during process running and Acronis system report after it finishes in this case (see below).
3. If the backup is being created to the centralized managed vault, the issue may be caused by the Agent performance Acronis Storage Node performance or network. Please collect Strace from machines where Agent and Acronis Storage Node are installed and PCAP report during process running and Acronis system report from both machines after it finishes in this case (see below).
Collecting information
1. Collecting Acronis system report.
2. Collecting Process Monitor (ProcMon) log.
3. Collecting Strace log.
4. Collecting PCAP (Wireshark) log (see Linux part if collected on Linux machine).
In addition always save Acronis Backup log of the faulty operation (Right-click on the backup plan -> Logs -> Save to file) and System Report form the machine in question. See instruction for Acronis Backup & Recovery 11.5 Generating System Report, if this fails for any reason, you can use this AcronisInfo Utility. With information collected please contact Acronis Customer Central.
More information
More information availible in article: Troubleshooting Performance issues in Acronis Software