Logs for troubleshooting NetBackup for Hyper-V
|Article:TECH183159|||||Created: 2012-03-07|||||Updated: 2012-03-08|||||Article URL http://www.symantec.com/docs/TECH183159|
The following information describes logs that contain valuable information for Hyper-V logs for troubleshooting.
Enabling VxMS and vhd logging
1. On the Windows desktop of the Hyper-V server where the NetBackup client is installed, click Start > Run and enter regedit.
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
2. To be on the safe side, make a backup of the current registry (File > Export).
3. Go to HKEY_LOCAL_MACHINE > SOFTWARE > VERITAS > VxMS.
4. Change the Logging DWORD value.
- To enable vhd logging, set the value of VHDLog to 0x01.
- To disable vhd logging, set the value of VHDLog to 0x00.
The name of the vhd log is vhd_vm.txt. Only one vhd_vm.txt log file is created; new log entries are written to the existing log file.
Enabling VxFI logging
By default, VxFI logging occurs at the error level. You can increase the logging verbosity by changing the log configuration file for the appropriate provider.
To increase the VxFI logging level
On the Windows desktop of the Hyper-V server where the NetBackup client is installed, go to the following location:
\Program Files\Common Files\Symantec Shared\VxFI\4\ConfigFiles\
This folder contains a configuration file for each provider, such as vss.conf and emcclariionfi.conf. These files are generated after a successful load of VxFI providers, usually during NetBackup policy validation.
Edit the .conf file for the appropriate provider, as follows:
Change the TRACELEVEL entry to the following:
The default TRACELEVEL value is 00000001.
Note that VSS and WMI provider logs are relevant to Hyper-V.
Article URL http://www.symantec.com/docs/TECH183159