I finally found the problem by accident. One of the Exchange databases was in the backup selection twice. When it was trying to run it the 2nd time it was saying it was not due to run. As soon as I found that and removed it, the error 200 stopped.
Sorry for the delay in getting this information, had some issues with real broken stuff, rather then just an anoyance. I removed any identifying information from the policy so as not to show any customer information.
[johnsnod@xxx ~]$ sudo /usr/openv/netbackup/bin/admincmd/bppllist xxx_MAN_2K8_DBW_EXE_1 -U
------------------------------------------------------------
Policy Name: xxx_MAN_2K8_DBW_EXE_1
Policy Type: MS-Exchange-Server
Active: yes
Effective date: 07/23/2013 07:14:42
Mult. Data Streams: yes
Client Encrypt: no
Checkpoint: no
Policy Priority: 99900
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Residence: xxx-hcart2-robot-tld-0
Volume Pool: xxx
Server Group: *ANY*
Keyword: CATII
Data Classification: -
Residence is Storage Lifecycle Policy: no
Exchange Source passive db if available: yes
Exchange DAG Preferred Server: (none defined)
Application Discovery: no
Discovery Lifetime: 0 seconds
ASC Application and attributes: (none defined)
Granular Restore Info: no
Ignore Client Direct: no
Enable Metadata Indexing: no
Index server name: NULL
Use Accelerator: no
HW/OS/Client: Windows-x64 Windows2008 xxx
Include: Microsoft Exchange Database Availability Groups:\a
NEW_STREAM
Microsoft Exchange Database Availability Groups:\b
NEW_STREAM
Microsoft Exchange Database Availability Groups:\c
NEW_STREAM
Microsoft Exchange Database Availability Groups:\d
NEW_STREAM
Microsoft Exchange Database Availability Groups:\e
NEW_STREAM
Microsoft Exchange Database Availability Groups:\f
NEW_STREAM
Microsoft Exchange Database Availability Groups:\g
NEW_STREAM
Microsoft Exchange Database Availability Groups:\h
NEW_STREAM
Microsoft Exchange Database Availability Groups:\i
NEW_STREAM
Microsoft Exchange Database Availability Groups:\j
NEW_STREAM
Microsoft Exchange Database Availability Groups:\k
Schedule: Offsite_3Y
Type: Automatic Backup
Maximum MPX: 4
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 10 (36 months)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: xxx
Server Group: (same as specified for policy)
Calendar sched: Enabled
Saturday, Week 1
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Saturday 18:30:00 --> Sunday 05:00:00
Schedule: Weekly_full
Type: Automatic Backup
Maximum MPX: 4
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 3 (1 month)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Saturday, Week 1
Saturday, Week 2
Saturday, Week 3
Saturday, Week 4
Saturday, Week 5
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Saturday 18:30:00 --> Sunday 05:00:00
Schedule: Daily_Incremental
Type: Differential Incremental Backup
Frequency: every 8 hours
Maximum MPX: 4
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 3 (1 month)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Sunday 21:30:00 --> Monday 05:00:00
Monday 21:30:00 --> Tuesday 05:00:00
Tuesday 21:30:00 --> Wednesday 05:00:00
Wednesday 21:30:00 --> Thursday 05:00:00
Thursday 21:30:00 --> Friday 05:00:00
Friday 21:30:00 --> Saturday 05:00:00
