Missing files from full backup

So, the backup ended with status 0, not status 1? Were other files in the same folder backed up and just the 2 exe's skipped?

If entire folder, double-check NetBackup Client Service logon account.

The default is LocalSystem. I have seen where entire folders are skipped because LocalSystem does not have read access. No errors and/or status 1, because LocalSystem cannot 'see' into folders where it has no read access. Folder name will be backed up with no contents and report status 0.

Another reason for skipped files without error message is Windows Registry entry called FilesNotToBackup - see http://www.symantec.com/docs/TECH84013

Create bpbkar log to troubleshoot. I suggest you increase client logging level to something higher than the default level 0 - try level 3. I cannot imagine that level 5 log will be needed.

What are the names of the vital names ?

Yes they finished with status 0, which surprised me. Correct, other files backed up OK.

I've looked at registry settings and they are not listed in there.

I'll try the logging, thanks.

> What are the names of the vital names ?

Is that relavent?

turn around & say "Oh they're never backed up because ...." or "Oh, they backup ok for us, maybe it's because ...."

Sorry Nicolai, don't mean to put words in your mouth!

OK point taken:

smsexec.exe and sitecomp.exe

Both have been backed up and restored in the past successfully

Not something I've come across before, but then I've more of a *NIX background, & certainly not in relation to NB.

& you say they've backed up ok in the past, so has anything happened or changed recently that could explain this? Are there any actual issues with SCCM on the client or in general?

smsexec.exe -  System Center Configuration Manager

sitecomp.exe - System Center Configuration Manager

I do not think these two files are very important for DR restore - However I would personally be keen to know why they are skiped.

Try a full backup after applying the settings outlined in this T/N:

http://www.symantec.com/docs/TECH31513

Attach the bpbkar log from the client, and attach as a file in a post. 

Update: Too late with the SMS info

The last time the DR was tested was a few months ago I believe and that went fine. To my knowledge, nothing has changed that could explain this.

All other jobs eg SQL run without issue, all finish with 0