(200) scheduler found no backups due to run

Question

Master/Media server&nbsp; 7.5.0.7

RedHat Linux 2.6

Exchange Backup policy

For the life of me I can not figure out what is causing this to happen, and it's only one policy.&nbsp; None of the other exchange policies are doing this.&nbsp; I've made sure my frequencies and backups windows are all configured correctly.&nbsp; In fact I lowered the Frequency to be just longer then the window in case someone was running the job manually earlier in the day.&nbsp; This did not help.&nbsp; I do see one thing that looks out of place.&nbsp; Even though the clients are configured in lowercase letters in both the exchange and filesystem backups, I'm seeing the client name in all uppercase for some of the jobs running and getting the error 200..&nbsp; I've checked cron on the NetBackup server and nothing is running from there.&nbsp; The only thing I can think of is something is running from the client side to kick off the exchange jobs for this policy.&nbsp; I've asked the exchange admin to check and they said there is nothing running.&nbsp; I don't have access to that server to do any investigation myself.

Any ideas where to look to try and track it down?&nbsp; My customer understands this is not an error we need to worry about, but I would like to clear it up anyway.

john_snodgrass · Accepted Answer

I finally found the problem by accident.&nbsp; One of the Exchange databases was in the backup selection twice.&nbsp; When it was trying to run it the 2nd time it was saying it was not due to run.&nbsp; As soon as I found that and removed it, the error 200 stopped.

will_restore · Answer

A rather old technote, may still apply to your case

http://www.symantec.com/business/support/index?page=content&amp;id=TECH44763

STATUS CODE 200: A client backup receives a Status 200 message "scheduler found no backups due to run" when multiple backups of the same type are scheduled on the same day, for the same policy, with calendar-based scheduling.

&nbsp;

Please attach your policy details, output from this command:&nbsp; bppllist -U&nbsp; policyname

nicolai · Answer

Another Connect thread about status code 200 troubles.

https://www-secure.symantec.com/connect/forums/status-200-message-scheduler-found-no-backups-due-run

michael_g_ander · Answer

The upper case client name is probably&nbsp;a part of&nbsp;the problem, try to change either the policy client to upper case or the client name on the exchange client to lower case.

john_snodgrass · Answer

Sorry for the delay in getting this information, had some issues with real broken stuff, rather then just an anoyance.&nbsp; 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:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxx_MAN_2K8_DBW_EXE_1

&nbsp; Policy Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MS-Exchange-Server
	&nbsp; Active:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; yes
	&nbsp; Effective date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 07/23/2013 07:14:42
	&nbsp; Mult. Data Streams:&nbsp; yes
	&nbsp; Client Encrypt:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	&nbsp; Checkpoint:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	&nbsp; Policy Priority:&nbsp;&nbsp;&nbsp;&nbsp; 99900
	&nbsp; Max Jobs/Policy:&nbsp;&nbsp;&nbsp;&nbsp; Unlimited
	&nbsp; Disaster Recovery:&nbsp;&nbsp; 0
	&nbsp; Collect BMR info:&nbsp;&nbsp;&nbsp; no
	&nbsp; Residence:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxx-hcart2-robot-tld-0
	&nbsp; Volume Pool:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxx
	&nbsp; Server Group:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *ANY*
	&nbsp; Keyword:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CATII
	&nbsp; Data Classification:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	&nbsp; Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp; no
	&nbsp; Exchange Source passive db if available: yes
	&nbsp; Exchange DAG Preferred Server: (none defined)
	&nbsp; Application Discovery:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	&nbsp; Discovery Lifetime:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 seconds
	ASC Application and attributes: (none defined)

&nbsp; Granular Restore Info:&nbsp; no
	&nbsp; Ignore Client Direct:&nbsp; no
	Enable Metadata Indexing:&nbsp; no
	Index server name:&nbsp; NULL
	&nbsp; Use Accelerator:&nbsp; no
	&nbsp; HW/OS/Client:&nbsp; Windows-x64&nbsp;&nbsp; Windows2008&nbsp;&nbsp; xxx

&nbsp; Include:&nbsp; Microsoft Exchange Database Availability Groups:\a
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NEW_STREAM
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Microsoft Exchange Database Availability Groups:\b
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NEW_STREAM
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Microsoft Exchange Database Availability Groups:\c
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NEW_STREAM
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Microsoft Exchange Database Availability Groups:\d
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NEW_STREAM
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Microsoft Exchange Database Availability Groups:\e
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NEW_STREAM
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Microsoft Exchange Database Availability Groups:\f
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NEW_STREAM
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Microsoft Exchange Database Availability Groups:\g
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NEW_STREAM
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Microsoft Exchange Database Availability Groups:\h
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NEW_STREAM
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Microsoft Exchange Database Availability Groups:\i
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NEW_STREAM
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Microsoft Exchange Database Availability Groups:\j
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NEW_STREAM
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Microsoft Exchange Database Availability Groups:\k

&nbsp; Schedule:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Offsite_3Y
	&nbsp;&nbsp;&nbsp; Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Automatic Backup
	&nbsp;&nbsp;&nbsp; Maximum MPX:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4
	&nbsp;&nbsp;&nbsp; Synthetic:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Checksum Change Detection: 0
	&nbsp;&nbsp;&nbsp; PFI Recovery:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Retention Level:&nbsp;&nbsp;&nbsp;&nbsp; 10 (36 months)
	&nbsp;&nbsp;&nbsp; Number Copies:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1
	&nbsp;&nbsp;&nbsp; Fail on Error:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Residence:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (specific storage unit not required)
	&nbsp;&nbsp;&nbsp; Volume Pool:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xxx
	&nbsp;&nbsp;&nbsp; Server Group:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (same as specified for policy)
	&nbsp;&nbsp;&nbsp; Calendar sched: Enabled
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Saturday, Week 1
	&nbsp;&nbsp;&nbsp; Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Schedule indexing:&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Daily Windows:
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Saturday&nbsp;&nbsp; 18:30:00&nbsp; --&gt;&nbsp; Sunday&nbsp;&nbsp;&nbsp;&nbsp; 05:00:00

&nbsp; Schedule:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Weekly_full
	&nbsp;&nbsp;&nbsp; Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Automatic Backup
	&nbsp;&nbsp;&nbsp; Maximum MPX:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4
	&nbsp;&nbsp;&nbsp; Synthetic:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Checksum Change Detection: 0
	&nbsp;&nbsp;&nbsp; PFI Recovery:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Retention Level:&nbsp;&nbsp;&nbsp;&nbsp; 3 (1 month)
	&nbsp;&nbsp;&nbsp; Number Copies:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1
	&nbsp;&nbsp;&nbsp; Fail on Error:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Residence:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (specific storage unit not required)
	&nbsp;&nbsp;&nbsp; Volume Pool:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (same as policy volume pool)
	&nbsp;&nbsp;&nbsp; Server Group:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (same as specified for policy)
	&nbsp;&nbsp;&nbsp; Calendar sched: Enabled
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Saturday, Week 1
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Saturday, Week 2
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Saturday, Week 3
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Saturday, Week 4
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Saturday, Week 5
	&nbsp;&nbsp;&nbsp; Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Schedule indexing:&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Daily Windows:
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Saturday&nbsp;&nbsp; 18:30:00&nbsp; --&gt;&nbsp; Sunday&nbsp;&nbsp;&nbsp;&nbsp; 05:00:00

&nbsp; Schedule:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Daily_Incremental
	&nbsp;&nbsp;&nbsp; Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Differential Incremental Backup
	&nbsp;&nbsp;&nbsp; Frequency:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; every 8 hours
	&nbsp;&nbsp;&nbsp; Maximum MPX:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4
	&nbsp;&nbsp;&nbsp; Synthetic:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Checksum Change Detection: 0
	&nbsp;&nbsp;&nbsp; PFI Recovery:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Retention Level:&nbsp;&nbsp;&nbsp;&nbsp; 3 (1 month)
	&nbsp;&nbsp;&nbsp; Number Copies:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1
	&nbsp;&nbsp;&nbsp; Fail on Error:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Residence:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (specific storage unit not required)
	&nbsp;&nbsp;&nbsp; Volume Pool:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (same as policy volume pool)
	&nbsp;&nbsp;&nbsp; Server Group:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (same as specified for policy)
	&nbsp;&nbsp;&nbsp; Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Schedule indexing:&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp;&nbsp;&nbsp; Daily Windows:
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sunday&nbsp;&nbsp;&nbsp;&nbsp; 21:30:00&nbsp; --&gt;&nbsp; Monday&nbsp;&nbsp;&nbsp;&nbsp; 05:00:00
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Monday&nbsp;&nbsp;&nbsp;&nbsp; 21:30:00&nbsp; --&gt;&nbsp; Tuesday&nbsp;&nbsp;&nbsp; 05:00:00
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tuesday&nbsp;&nbsp;&nbsp; 21:30:00&nbsp; --&gt;&nbsp; Wednesday&nbsp; 05:00:00
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Wednesday&nbsp; 21:30:00&nbsp; --&gt;&nbsp; Thursday&nbsp;&nbsp; 05:00:00
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thursday&nbsp;&nbsp; 21:30:00&nbsp; --&gt;&nbsp; Friday&nbsp;&nbsp;&nbsp;&nbsp; 05:00:00
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Friday&nbsp;&nbsp;&nbsp;&nbsp; 21:30:00&nbsp; --&gt;&nbsp; Saturday&nbsp;&nbsp; 05:00:00

&nbsp;

marianne · Answer

I only saw your last post today...

This policy does not allow client-initiated backups.

You have masked the client name in the policy. Is that a DAG member name or the virtual hostname?

The client names that you see in Activity Monitor - is that Virtual or node name?
	Can you post all text in Details tab of failed jobs?

Do you have bpresolver log folder on all DAG members?
	If not, please create this log folder as it may help to understand how hostnames are resolved.

Something else that I am wondering about:
	The&nbsp;Automatic Backup schedules.

My understanding is that only Full, Diff, Cumm Inc and User schedules are available for Exchange Backups.
	Why would these schedules be of type 'Automatic Backup'?
	&nbsp;

Forum Discussion

(200) scheduler found no backups due to run

6 Replies

Related Content

NDMP backup failing with EC 200

Saving a Report Schedule - Cron

VMWare backups - scheduler found no backups due to run(200)

Status 200 message "scheduler found no backups due to run

Re: Automatic Backup and Default Application backup.

Recent Discussions

command: bperror

MS-SharePoint policy restore error (2804) .

How to restore a backup

How to configure RBAC

10 years old netbackup appliance database service down, ssl certification out date