この記事の対象:
This article describes how to troubleshoot issues related to Application malfunction in Replica VM while using Acronis Backup for VMware (Acronis vmProtect).
This article applies to:
AVMP - Replication
This article describes how to troubleshoot issues related to Exchange Malfunction in Replica VM while using Acronis Backup for VMware (Acronis vmProtect).
This article applies to:
This article describes how to troubleshoot issues related to AD malfunction after the replication of VM while using Acronis Backup for VMware (Acronis vmProtect).
This article applies to:
This article describes how to troubleshoot issues related to VM replication failure while using Acronis Backup for VMware (Acronis vmProtect).
This article applies to:
Acronis Cyber Backup 製品で vSphereのスナップショットに関する問題が発生した場合のトラブルシューティングおよび問題解決の手順。
OSのクラッシュ（異常終了）をトラブルシュートする方法
本記事の対象製品：
- Acronis ソフトウェア
はじめに
Acronis 製品はオペレーティングシステムのストレージシステムを非常に低レベルで扱いますから、このレベルでの様々な競合によってバックアップ（または、他の操作）中にオペレーティングシステムがクラッシュする僅かなリスクがあります。クラッシュをトラブルシュートするには、使用するOSによって以下の手順のいずれかに従ってください。
ソリューション
これらのクラッシュはいつも低レベルのシステム競合によって発生するので、一般的なソリューションがありません。各クラッシュは、個別に調べる必要があります。クラッシュをトラブルシュートするには、以下の手順に従ってください。使用するシステムによって手順が異なりますので、まずは適切なセクションを選んでください：
Instructions on how to troubleshoot and resolve vSphere snapshot issues in Acronis Cyber Backup products
This article applies to:
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..
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.