These instructions apply to VMware Infrastructure VDDK version 6.x or later.
Creating a VDDK Support Request
Here is a summary of the steps to file a VDDK Support Request:
Here is a summary of the steps to file a VDDK Support Request:
- Ensure that the error was captured in the log files.
- Note the approximate time (and time zone especially) of the error.
- Provide the backup target VM name and backup proxy VM name (if any)
- Collect the required diagnostic files and information
Three sets of data are needed to properly diagnose your VMware Infrastructure VDDK issue:
-
- VDDK related information β Complete the VDDK support form. For more information, please check the document "
1006186_VMware_VDDK_Support_Form.doc
" which is attached to this article.
- ESX related information β Collect ESX files. For more information, please check Collecting diagnostic information for VMware products.
- vCenter Server related information β Collect the vCenter Server files. For more information, please check Collecting diagnostic information for VMware products
- Create and submit a Support Request
- Submit the Support Request with its associated information
- Upload the diagnostic files to the VMware SFTP/FTP site
Collecting VDDK related data
All the VDDK related information needed to evaluate your Support Request and to help diagnose your problem is listed in the VMware VDDK Support Form.
- Download and save the VMware VDDK Support Form, "
1006186_VMware_VDDK_Support_Form.doc
" attached to this article.
- Complete the form, providing as much detail about your computing environment as possible. Include any log files and code snippets you feel might be helpful.
Note: To collect VDDK logs from backup software, it usually needs help from a backup vendor as log functionality is provided by backup software.
- Upload the completed form with your Support Request.
Note:
- Collect VDDK logs with Verbose level to troubleshoot. VDDK log level needs to be set accordingly.
-
vixDiskLib.transport.LogLevel=6
vixDiskLib.nfc.LogLevel = 4
Note: This is only needed when nbd/nbdssl transports are utilized.
- In case of VDDK crash/hung, collect core dump file of VDDK along with collect windows event logs (applies for windows proxies only).
Collecting ESX related data
ESX includes a script called vm-support, which collects information that VMware Technical Support might request and packages that information into one file.
- For information about collecting ESX related data, please check:
-
- Collecting diagnostic information for VMware ESX/ESXi
- Collecting diagnostic information for VMware ESX/ESXi using the "vm-support" command
- Send the script-generated log files with your Support Request.
Note: Collect the vm-support bundles for ESXi hosts where the backup target VMs and proxy VMs are registered
Collecting vCenter Server related data
vCenter Server provides an option that collects log information useful to VMware Technical Support.
- See the appropriate Knowledge Base article for your version of vCenter Server . For more information, please check Collecting diagnostic information for VMware products
- When itβs requested by engineering, set the logging option to Trivia to ensure that all information is collected and that it includes time stamps.
- Send the script-collected files with your Support Request.
Uploading files to the SFTP/FTP site
If you have an existing Support Request and you need to attach additional files to your Support Request, upload them via SFTP/FTP.
Fore more information, please check Uploading Diagnostic information for VMware through the Secure FTP & Broadcom portal
Debugging tips
Here are some best practices for debugging code when using VMware Infrastructure APIs:
- Generate complete logs with as much detail as possible including timestamps. Provide case samples of successful completions and failures with time stamps.
- Submit code samples that are as self-contained as possible and reproduce the problems.
- Use the VMware Infrastructure Perl Toolkit to reproduce problems found when you use VM Perl.