How to collect VDDK trace when diagnosing VMware backup or restore problems
Date: FEB 2011
Product & Version: VMware 2.0
OS Version: all
Symptoms:
When diagnosing VMware backups and restores we can obtain useful information from the VDDK trace that does not appear in the binary log or VMware plugin trace.
How to generate and collect the data follows:
1/ Edit .../netvault/config/vmware.cfg as follows:
[Custom:GenerateVddkLogsOnDisk]
Value=True
2/ To increase debug level we need to do the following:
Create file config.vddk in .../netvault/config/ folder the file should contain the following
# log level 0 to 6 for quiet ranging to verbose
vixDiskLib.transport.LogLevel=6
# nfc.LogLevel (0 = Quiet, 1 = Error, 2 = Warning, 3 = Info, 4 = Debug)
vixDiskLib.nfc.LogLevel= 4
3/ Collecting the data:
On linux system the log file are created /tmp/vmware-root and the file name is vixDiskLib-xxxxx.log
On windows system the log files are found C:\WINDOWS\Temp\vmware-SYSTEM
4/ to stop trace / Edit .../netvault/config/vmware.cfg as follows:
[Custom:GenerateVddkLogsOnDisk]
Value=False
5/ Delete file config.vddk in .../netvault/config/ folder
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center