The key opinion that we all know you'll disagree with is one policy per server, which Bob apparently doesn't like and we know that you.  "The man in the suit" vs "the man in the yellow shirt" discussion, for those of who were at the customer forum in Roseville in October.  :-)

Personally, I agree with Bob on frequency-based schedules for fulls.  Calendar-based schedules only make sense if you have a strict business requirement for say, an end-of-quarter backup after the books close.

The key thing to always remember is to keep things as absolutely simple as possible.  Make it easy for other people (new employees, support folks, contractors) to see what the heck you've done a year or more after you set it up.  The more complicated you make it, the harder it is to support.  The more you deviate from a "normal" configuration, the more likely it is you'll trigger bugs in future NetBackup releases.   Simple is good.