AB - Recovery
Acronis Universal RestoreまたはAcronis Universal Deployに関する問題をトラブルシュートし、解決する方法
本記事の対象製品：
- Acronis Cyber Backup (Acronis Cyber Backup & Recovery)
- Acronis True Image
- Acronis Snap Deploy
はじめに
Universal Restore と Universal Deploy について
Universal Restore 技術は、異なるハードウェアに移行してもオペレーティングシステムを起動できるためのものです。この技術に関する最も一般的な問題は、Universal Restoreを使ってリカバリしてからオペレーティングシステムが起動しなくなることです。
リカバリ中のエラーの原因は様々です。この記事において、エラーの原因を見つけ出して、問題を解決する方法を紹介しています。
異なるハードウェアへリカバリする場合は、リカバリ元とリカバリ先のディスクが同じ論理セクタサイズであることを確認してください。詳細については、Advanced Format（4K セクタ）ハード ディスクのサポートを参照してください。
前提条件
リカバリ中、問題が発生した場合、まずは必ずアーカイブをベリファイしてください。ベリファイのとき、アーカイブに何か問題が見つかった場合、この記事の説明に従ってください。
This article provides instruction for troubleshooting recovery and conversion to virtual machine failures in Acronis Backup (Acronis Backup & Recovery).
Follow these steps to troubleshoot the recovery and conversion to virtual machine:
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.
During Exchange data recovery with Acronis Backup Advanced you may encounter one of the following problems:
Collect information for investigation of Linux operating system lockups.
Operating system may hang under specific circumstances. To identify the exact cause, it is necessary to analyze Acronis System Report and a kernel dump.
Always make sure you have the latest build of the product (if it's possible).
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.