With the release of NetBackup 7.

0, NetBackup now uses the vSphere vStorage api t

o perform backups and restore directly to the ESX or Virtual Center server. Wit
h this new method comes some changes in our troubleshooting procedure which will
be seen below.
Here are the logs to review and the event to review them in:
Browsing for Virtual Machine:
VMWare Backup Host logs:
C:\Program Files\Veritas\NetBackup\logs\bpVMutil\<date>.log
C:\Program Files\Veritas\NetBackup\logs\bpcd\ <date>.log
Master Server logs:
C:\Program Files\Veritas\NetBackup\logs\bprd\ <date>.log
C:\Program Files\Veritas\NetBackup\logs\nbproxy\ <date>.log
Backup Time:
Parent Job: (Snapshot Job)
VMWare Backup Host logs:
C:\Program Files\Veritas\NetBackup\logs\bpfis\<date>.log
C:\Program Files\Veritas\NetBackup\logs\bpcd\ <date>.log
Media Server side logs:
C:\Program Files\Veritas\NetBackup\logs\bpbrm\ <date>.log
ESX Server side logs:
/var/log/vmware/hostd.log

Virtual Center:
Check for Snapshot Errors from the Virtual Machine.
Child Job: (Backup Job)
VMWare Backup Host:
C:\Program Files\Veritas\NetBackup\logs\bpfis\<date>.log
C:\Program Files\Veritas\NetBackup\logs\bpbkar\<date>.log
C:\Program Files\Common Files\Veritas\VxMS\logs\
C:\Program Files\Veritas\NetBackup\logs\bpcd\ <date>.log
Server side logs:
C:\Program Files\Veritas\NetBackup\logs\bpbrm\<date>.log
C:\Program Files\Veritas\NetBackup\logs\bptm\ <date>.log
ESX Server side logs:
/var/log/vmware/hostd.log
Restore Time:
VMWare Backup Host logs:
C:\Program Files\Veritas\NetBackup\logs\tar\ <date>.log
C:\Program Files\Veritas\NetBackup\logs\bpcd\ <date>.log
C:\Program Files\Veritas\NetBackup\logs\bpVMutil\ <date>.log
C:\Program Files\Common Files\Veritas\VxMS\logs\
Media Server logs:
C:\Program Files\Veritas\NetBackup\logs\bpbrm\ <date>.log
C:\Program Files\Veritas\NetBackup\logs\bptm\ <date>.log
Master Server logs:
C:\Program Files\Veritas\NetBackup\logs\bprd\ <date>.log
C:\Program Files\Veritas\NetBackup\logs\nbproxy\ <date>.log
Machine where Backup Archive and Restore(nbwin) is running from:
C:\Program Files\Veritas\NetBackup\logs\bpvmreq\<date>.log
In the previous versions of NetBackup for VMWare, when a VMWare component fails
our logs would capture the VMWare logs. In NetBackup 7.0, it will be necessary
to increase the vmcloglevel to capture additional information from the VMWare To
ols.
Modify the following registry on the VMware Backup Host to gather additional inf
ormation in the NetBackup log perform the VMWare task.

Location: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config\BA
CKUP
Value: vmcloglevel
Value type: DWORD

Unit: second
Input range: 1 to 6 (default = 0)

Using vmcloglevel 3 will show API errors and 6 is used for debugging the API cod
e. Level 3 should be sufficient for technical support.

Additional information on configuring VxMS logging:

Delete the contents of:
C:\Program Files\Common Files\VERITAS\VxMS\Logs
To enable VxMS log, run regedit and set the value of following registry value to
7580 hexadecimal
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxMS\Logging
Also create the following for Backup jobs that fails to mapped the disk:
DWORD registry value "VIXLog" under the registry key
"HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxMS\" and set the value of VIXLog to 1
Assuming C: to be the root drive, the VxMS logs will be collected at: C:\Program
Files\Common Files\VERITAS\VxMS\Logs
Change the logging level back to 0 after testing is completed.
New NetBackup 7.1 Logs:
VMware Intelligent Policy query will be logged in the following unified log:
ncfnbcs - OID 366
ncfvmwarepi - OID 386
The following command will return the last 5 minutes of the above logs:
# vxlogview -p NB -i ncfnbcs -t 00:05:00
NBDISCOVERY will also be logged in the following Unified Log:
ncfnbdiscover - OID 377
The following example will return the last 5 minutes of a nbdiscovery command:
# vxlogview -i 377 -t 00:05:00 > c:\temp\discovery.txt
New to NetBackup 7.5 logs:
By default VDDK logs are embedded into VxMS logs. To collect VDDK logs separate
ly, then add the following registry entry:
Add "createVDDKlog" DWORD entry under "HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxMS\
" and set its value to 1. This will generate VDDK-*.log files in the VxMS log f
older.
New to NetBackup 7.6 logs:
To configure VxMS logging on a Windows backup host
Create the VxMS log directory:
install_path\NetBackup\logs\vxms
Note: For logging to occur, the VxMS folder must exist.
In the Windows registry, create the DWORD registry entry VXMS_VERBOSE in the fol
lowing location:
HKEY_LOCAL_MACHINE>SOFTWARE>Veritas>NetBackup>CurrentVersion>Config
For Mapping during the VMware Backup, use:
VXMS_VERBOSE = 8
For possible VDDK issues:
VXMS_VERBOSE = 5
NOTE: VXMS_VERBOSE = 8 will slow down backups and restore operations.
To change the log location:
Open regedit and go to the following location:
HKEY_LOCAL_MACHINE>SOFTWARE>Veritas>NetBackup>CurrentVersion
Create the registry entry vxmslogdir with a string value (REG_SZ). For the strin
g value, specify the full path to an existing folder.
Note: You can use NTFS compression on VxMS log folders to compress the log size.
The new logs are written in compressed form only.
For Instant Recovery Logging
Configure bprd on the Master
They are 3 main steps performed during Instant Recovery:
- Export a backup image
- Mount a backup image
- Activate VM
If any of these steps failed Activate Instant Recovery job logs will have details
about the failure and error code.
If Export a backup image fails look at nbfsd.log on media server.
Mount backup image fails look at nbfsd.log on VM Proxy host and also the Virtual
Center Task and Events.
Activate VM fails look at bpVMutil.log on VM Proxy host and also the Virtual Cen
ter Task and Events.