For example, if the size of the hole is 1024 bytes, but hole_gfactor is 2k (i.e. 2028 ), that hole of 1024 will get backed up as its smaller than the hole_gfactor. But if the hole_gfactor is set to a too large number, it may happen that bpbkar will end up backing up only the data.
Investigation into the ...\netbackup\logs\bpdbjobs\ log file shows this command being executed every 35 minutes, and lining up exactly with the timing of the fault in the Application Event Log: 10:06:11.812 [7688. 2028 ] 4 main: NetBackup 6.5: 0000.2147483643.4375352 10:06:11.812 [7688.2028] 4 main: VERBOSE = 5
5/20/2013 11:31:59 AM - restoring image exchange2010_1369020288 5/20/2013 11:32:00 AM - Info bprd(pid= 2028 ) Restoring from copy 1 of image created 05/20/13 11:24:48 5/20/2013 11:32:04 AM - Info bpbrm(pid=4864) exchange2010 is the host to restore to