To clarify - I am running 6.5.2A on unix master and media servers, with MSSQL 
on a 6.5.2 windows server.

Update from my DBA - these are transaction log backups, and he added a new 
database - since the TL will fail if there is not a backup, that is what caused 
the issue. Why would NetBackup not see this? He claims his SQL scripts ran 
through and finished, but the parent jobs never acknowledged this. 

I have received a recommendation to get a patch for the bpbrm, but that was 
based on 5.1 mp6. Shouldn't 6.5.2A have any patches from 5.1?


NetBackup support response is that this is not their problem. Any ideas?


David McMullin


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu