ATIH - Backup

Introduction

This article describes how to run existing Acronis True Image backup tasks from command line.

Prerequisites

You need to have a configured backup job in True Image graphical user interface (GUI) before you can run it from command line. It is not possible to configure a new backup job from scratch from command line or modify settings of already set up tasks.

Acronis Scheduler is a tool which is responsible for scheduled Acronis operations. If scheduled backups or other activities do not work as configured in backup plan or task, proceed with this article in order to identify the root cause and solve the issue if possible.

Follow these steps to troubleshoot Acronis Scheduler issues:

Backup may fail due to a variety of reasons. This article contains instructions on how to localize the root cause of the issue and how to troubleshoot it as well as links to other troubleshooting articles.

About backup process

Backup process can be divided into several stages:

How to solve e-mail notifications issues.

Always make sure you have the latest build of the product.

Symptoms

  1. In Acronis True Image you set up E-Mail notifications on operation results;
  2. E-Mail notifications fail with the following error message: Cannot send e-mail. The possible reason might be incorrect e-mail settings.

Known issues

Possible reasons for e-mail notifications issues can be:

Follow these steps to troubleshoot Consolidation Issue

Product may hang under specific circumstances.

There are 2 types of hanging:

  • Actual hanging. That is a state similar to a crash. That means that software halts and is doing nothing inside.
  • Infinite loop. This means that on the outside the software looks hanging but inside it is doing some actions over and over again.

Usually when a software hangs its process uses either 100% of CPU (especially when it is infinite loop) or does not use CPU and does not change RAM usage at all (Actual hanging). Still it is difficult to make sure if the software hangs or not. The above means that usually 1 dump is not enough because if that is Infinite Loop – the developers will see that software is working and there is no problem inside. So in order to troubleshoot application lockups you need about 5 dumps collected one after another. A Process Monitor Log will also be useful especially if it actually turns out to be an Infinite Loop.

Please note that an application lockup does not necessarily mean the software is completely unresponsive. A process can hang (e.g. service_process.exe hangs and a backup is stuck), but you can still browse vaults, create new plans etc.

Define the hanging process using Windows Task Manager. In some cases multiple processes are involved in an operation. In this case the hang of 1 process can be caused by some operations in another process. In this case you need  to collect memory dumps of all processes involved in the operation. E.g. if a backup to Acronis Storage Node hangs, you need to collect a dump of service_process of the agent as well as StorageServer.exe process on ASN machine.

Instructions on how to troubleshoot and resolve issues with corrupt backups