To the original machine
- Log in to Cyber Protection console and click Recover:
- Click Recover machine:
- Specify recovery options if you need them, otherwise skip this step
Linux
This article describes how to get asamba verbose logs of Acronis services in Linux and macOS
Acronis Snap Deploy 5 licensing is based on the number of deployed and/or managed computers. License types are different in terms of the operating system to deploy and in terms of number of allowed deployments.
In terms of the operating system you can deploy, you can have a workstation or server license:
Instructions on how to troubleshoot and resolve issues with disk/partition backup failures
Introduction
Backup of drives or partitions may fail due to a variety of reasons, but not all reasons are specific to this type of backup. Generally the problem can be treated as a partition backup failure only when you also tried to run a file backup
This article applies to:
- Oracle Linux Server 6.5 Kernel 3.8.13-44.1.3.el6uek.x86_64
- Oracle Linux Server 6.6 Kernel 3.8.13-44.1.3.el6uek.x86_64
- Oracle Linux Server 6.8 Kernel 3.8.13-118.14.2.el6uek.x86_64
Other kernel versions of Oracle Linux Server 6.x may be affected as well. The list above contains the kernel versions that produced the issue in Acronis test lab.
Disk/Volume backup fails with:
The SnapAPI kernel module is not loaded for the kernel currently running on the system.
Installation of Acronis Agent for Linux fails with "Segmentation Fault". To fix this issue, transfer the installation files with WinSCP or via Samba share
Symptoms
You want to installed Acronis Agent on a machine. During installation, you are notified that R1Soft backup software is already installed on the machine and installation cannot proceed.
Cause
Acronis Agent and R1Soft backup software cannot be installed on one machine because of Acronis snapAPI and hcpdriver conflict.
Solution
R1Soft backup software needs to be uninstalled before installing Acronis Agent.
This article details aspects of LVM backup and recovery with Acronis Cyber Protect, Acronis Cyber Backup and Acronis Backup 11.7/11.5
Instructions on how to troubleshoot problems after recovery
This article applies to:
- Acronis Backup (Acronis Backup & Recovery)
Introduction
Sometimes a recovery process seems to work without any visible problems, but the resulting files after recovery are not complete and/or are corrupted. This article will explain the process to troubleshoot this issue.
Solution
Depending on what was being recovered, please choose the correct section:
Errors during recovery can happen for a number of different reasons and this article will help troubleshoot and resolve such issues.
Prerequisites
If you are having any sort of issue during recovery, always validate the archive as the first step. If validation find a problem with your archive please follow the instructions in this article.
Will work better in 8.0 (from A.Berezin)
Machine already has been backed up several times. To check the recovery points, you go to All devices, select the machine, and click Recovery.
You click Refresh (in the upper right corner of the list) to refresh the list of recovery points. In a minute, recovery points appear, but you notice that some or all of the recovery points are now missing from the list.
You might see this message:
There are no backups of the selected devices in the known locations.
You have a machine with a local DNS server (such as unbound or named) in a network with DHCP.
Recovery (entire machine or disk-level that requires reboot) fails with this error:
Error:
{"domain":"Access","code":"InvalidGrant","debug":{"msg":"couldn't get upstream token, Post https://jp-cloud.acronis.com/bc/idp/token: dial tcp: lookup jp-cloud.acronis.com on 127.0.0.1:53: read udp 127.0.0.1:55705-\u003e127.0.0.1:53: read: connection refused"},"error":"invalid_grant","error_description":"couldn't get upstream token, Post https://jp-cloud.acronis.com/bc/idp/token: dial tcp: lookup jp-cloud.acronis.com on 127.0.0.1:53: read udp 127.0.0.1:55705-\u003e127.0.0.1:53: read: connection refused"}
Because Acronis products work with the storage system of an operating system on a very low level, there is a small risk that different conflicts on this level can lead to an operating system crash during backup or other operations. Please follow the instructions below to troubleshoot these issues, depending on what operating system is being used..
This article describes how to troubleshoot performance issues with Acronis Backup Command line tool.
Use a pre-backup command to run inventory before backup
You faced an issue with the registration of the Agent during the automatic installation and try to use the instruction from the article 55244:Acronis Backup Cloud: Registering Backup Client Manually
The RegisterAgent tool gives you an error:
| error 0x2260007: couldn't connect to host at localhost:43234
| line: 0xcbd08862963188d1
| file: e:/271/enterprise/common/http/curl_transport.cpp:284
| function: PerformRequest
| $module: register_agent_lxa64_10790
OR in Linux
The registration failed due to a problem on the Management Server. Either the backup service on this machine could not access the Management Server or the server returned an error response. Please make sure that the Management Server is accessible through the network and try again.
This article looks at troubleshooting GUI performance issues with Acronis products.
In general, performance is constantly being optimized, so updating to the latest build is always recommended for the best performance
You need to use Acronis Universal Restore to recover the system backup of one machine to another one with dissimilar hardware.
Acronis Software is not always able to detect storage hardware correctly in the backup source selection or Disk Management components. This is often caused by a conflict with hardware, its drivers or third-party software. There is a huge number of possible storage configurations, and we cannot test every single one beforehand.
This issue can also be caused by an incorrect or unfinished installation of the product.
You install Acronis Agent on a Linux machine. Installation completes with this error:
Failed to build the SnapAPI kernel module. Operations with disk-level backups will not be available.
Symptoms
- You have upgraded your system from Acronis Cyber Backup 12.5 to Acronis Cyber Protect 15.
- After the upgrade, you created new protection plans. When you try to edit a newly created protection plan, there is a spinning loading circle with Reconnecting... message.
Symptoms
Backup of a Linux system with kernel 4.18 fails with the following error:
Failed to create a snapshot
Acronis True Image restores LVM volumes as non-LVM partitions. You will need to take extra steps to make the restored system bootable. You can also restore LVM volumes to prepared LVMs
This article describes how to get strace output of Acronis services in Linux
Symptoms:
1) Basic error message stack in Backup Console:
Status:Error
Common I/O error.
2) Details of error message in Backup Console (click on the Details button):
How to update the SnapAPI module in Linux
Symptoms
Symptoms depend on the product version:
- Acronis Cyber Backup 12.5 builds 16180, 16318, 16327, 16342, 16343 contain build 0.7.127 – SnapAPI module will not compile on kernel 5.8 and later
- Acronis Cyber Protect 15 builds 24426, 24508, 24515 and later contain SnapAPI build 0.7.133 which imminently leads to kernel crash and the following error:
cannot execute binary file: Exec format error
when trying to execute any binary file.
Introduction
Almost always, the recommended and sufficient way to completely uninstall an Acronis Cyber Backup Cloud Agent for Linux is to follow Acronis Cyber Protect Cloud: manual uninstallation and execute (as root):
/usr/lib/Acronis/BackupAndRecovery/uninstall/uninstall -a