Acronis vmProtect: Troubleshooting Application Malfunction after Recovery

 Complete all steps before proceeding to error troubleshooting step.

1. Check if the application works fine on the original virtual machine. If there are problems with application before the virtual machine is backed up then these problems will also appear when the virtual machine is restored.
2. The snapshot that is used to create a backup is created using the VMware API. It also uses the VMware Tools to create a snapshot inside the virtual machine to back up the VSS-aware applications. The user should check that the latest VMware tools are installed inside the virtual machine. 

Complete all steps before proceeding to collect information step.

1. Check all the partitions inside the recovered virtual machine for errors using chkdsk utility: go to command prompt (Start -> run -> cmd) and enter the following command: "chkdsk VOLUME /f" where VOLUME is the volume letter you need to check. Please note, that checking the C: drive may require you to reboot the machine.
2. Check that the environment where the application should be used has not been changed after the backup was created. There are applications that depend on the environment that were used. So if the environment is changed and they cannot access the data then the application may fail to work properly. For example recovering the virtual machine with the application that depends on the resources stored on network machines. This application may fail to start properly if the required resources are not available after restore operation is finished and virtual machine is started. 

If all steps above have been executed and issue still persists, go to collect information step.

Collect the following information and contact Acronis Customer Central.

1. The debug log of recovery operation that can be captured using the Acronis vmProtect: Collecting Debug Logs for Virtual Appliance and Windows Agent article.
2. Acronis System Reports from original VM and from the recovered VM that can be captured using AcronisInfo utility.
   
3. The screenshot of the error message that appeared during the attempt to start the application.
4. The detailed information about application (full name, version, build, where the configuration data and databases should be stored and other details that can help to localize the problem)
5. In order to increase the speed of resolution and be able to reproduce the problem in our environment we also need the full backup that has been used to recover if possible.