Debugging The Disaster Recovery Session - HP Data Protector A.06.11 Recovery Manual

them are relevant to you and indicate that an error has occurred. These error messages
are usually logged at the end of the log file with a traceback appended.
There are four types (levels) of messages in the autodr.log (note that they do not
correspond to the same report levels for messages that are reported at the end of a
backup session in the Data Protector GUI):
• Critical error: The error is so serious that the backup of the object can not
continue and will be aborted.
• Error: The error may be critical, but it depends on different factors.
For example, autodr.log reports an error that some driver has not been included
in the disaster recovery operating system. The missing driver may be the reason
for the recovered system not to be operational after the recovery or only for some
non-critical service not to be running after the boot of the operating system. It
depends on which driver has not been backed up.
• Warning and Info: These are not error messages and usually do not mean that
anything is wrong.
Some of the most common messages stated in the autodr.log file are:
• unsupported location: Data Protector notices that a certain file that is
required by a service or a driver that will be included in the disaster recovery
operating system (DR OS), is not located under the %SystemRoot% directory.
Such drivers are often used by the antivirus and remote control software (for
example pcAnywhere). This message is important, because it can mean that the
service/driver that requires the missing file, will not be operational after the boot.
It depends on which service or driver was affected, if the disaster recovery will
fail or succeed. A possible solution for this problem is copying the missing file
into the %SystemRoot% directory and changing its path in the Windows Registry.
Note that incorrect editing of the Windows Registry may severely damage your
system.

Debugging the disaster recovery session

You can instruct Data Protector to create and save debug logs during a disaster
recovery session. This option is available only for EADR and OBDR.
To enable debugging:
134 Troubleshooting disaster recovery