In bpbkar VERBOSE logging has little meaning.
To increase logging set General Debug Level = 2.
In Backup Archive and Restore GUI, go to Troubleshooting Tab:
Debug Levels: General = 2.
From the registry set Debug_Level:
HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config\Debug_Level
Then in bpbkar you'll see this:
GENERAL Log Level: 2
However for this you don't need verbose logging.
The easiest way to test an exclude is to use backup to NUL.
Example:
Exclude list in the registry:
D:\Program Files\Veritas\NetBackup\bin\*.lock
D:\Program Files\Veritas\NetBackup\bin\bprd.d\*.lock
D:\Program Files\Veritas\NetBackup\bin\bpsched.d\*.lock
D:\Program Files\Veritas\NetBackupDB\data\*
D:\Program Files\Veritas\Volmgr\misc\*
J:\
(I didn't have a Y:\ drive so I used J:\)
From a cmd line execute:
bpbkar32.exe -nocont J:\ 1> NUL 2> NUL
Monitor the task manager for the bpbkar process and note the bpbkar32 PID.
Now look for the backup PID in bpbkar log.
If the backup was too quick to open the task manager and get the PID, look for the 'nocont' in the bpbkar log. Then grep out the PID.
Example:
9:45:03.781 AM: [4356.5656] <4> ov_log::OVInit: GENERAL Log Level: 0
9:45:03.781 AM: [4356.5656] <2> WinMain: DAT - lpCmdLine = '-nocont J:\ '
9:45:03.890 AM: [4356.5656] <2> tar_backup_tfi::setupFileDirectives: TAR - backup filename = J:\
9:45:06.046 AM: [4356.5656] <2> tar_base::V_vTarMsgW: INF - Excluded: J:
9:45:06.046 AM: [4356.5656] <2> tar_base::backup_finish: TAR - backup: 0 files
Using bpbkar to NUL to test a backup is quick and easy and doesn't require a policy or a tape or disk storage and doesn't interferre with scheduled backups or creating test policies.
Note:
1> NUL - This is used so that bpbkar does not write a backup file.
2> NUL - This is used so that bpbkar does not write an output file.
If you want to see what bpbkar is writing outside of the bpbkar log set 2> NUL to a file.
Example:
2> C:\temp\output.txt
Example of C:\output.txt
INF - Inform when done
INF - BACKUP START
INF - Open File Backup license is not installed on the server. Open File Backup usage will be disabled.
INF - Estimate:-1 -1
Dfi - 0 0 0 -1 23 292 user other 0 0 0 0 /VRTS_IMAGE_SIZE_RECORD
INF - Total Size:0
INF - EXIT STATUS 0: the requested operation was successfully completed
Note: Be careful with 1> NUL
If this is not NUL then bpbkar isn't writing to the 'bit' bucket and it will generate a backup file. If the file list Y:\ for example is 4TB, then bpbkar will write a 4TB file.
