Status 200 message "scheduler found no backups due to run

Question

Hello,
&nbsp;We are&nbsp; updating are clients to a calendar base schedule, I updated a Solaris client policy the other day and the FULL backup failed with a status code 200 "scheduler found no backups due to run . I setup the same policy again yesterday and last night the backup received the same STATUS CODE 200.
&nbsp;I have done numerous clients and they have run without issue.
&nbsp;I read the the technote below this seems to not&nbsp; apply to our situation
&nbsp;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;Solaris10 client
Here is the bbpplist -l output
Policy Name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; testwater01
	Options:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x0
	template:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FALSE
	audit_reason:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?
	Names:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (none)
	Policy Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Standard (0)
	Active:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; yes
	Effective date:&nbsp;&nbsp;&nbsp; 06/25/2012 23:59:59
	Client Compress:&nbsp;&nbsp; no
	Follow NFS Mnts:&nbsp;&nbsp; no
	Cross Mnt Points:&nbsp; no
	Collect TIR info:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; yes, with move detection
	Block Incremental: no
	Mult. Data Stream: yes
	Perform Snapshot Backup:&nbsp;&nbsp; no
	Snapshot Method:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (none)
	Snapshot Method Arguments: (none)
	Perform Offhost Backup:&nbsp;&nbsp;&nbsp; no
	Backup Copy:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	Use Data Mover:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	Data Mover Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2
	Use Alternate Client:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	Alternate Client Name:&nbsp;&nbsp;&nbsp;&nbsp; (none)
	Use Virtual Machine:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	Hyper-V Server Name:&nbsp;&nbsp;&nbsp;&nbsp; (none)
	Enable Instant Recovery:&nbsp;&nbsp; no
	Policy Priority:&nbsp;&nbsp; 0
	Max Jobs/Policy:&nbsp;&nbsp; 6
	Disaster Recovery: 0
	Collect BMR Info:&nbsp; yes
	Keyword:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (none specified)
	Data Classification:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp; no
	Client Encrypt:&nbsp;&nbsp;&nbsp; no
	Checkpoint:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	Volume Pool:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NetBackup
	Server Group:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *ANY*
	Granular Restore Info:&nbsp; no
	Exchange Source attributes:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	Exchange 2010 Preferred Server: (none defined)
	Application Discovery:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	Discovery Lifetime:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 seconds
	Generation:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8
	Ignore Client Direct:&nbsp; no
	Client/HW/OS/Pri:&nbsp; testwater01-bkup Solaris Solaris10 0 0 0 0 ?
	Include:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ALL_LOCAL_DRIVES
	Schedule:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; full
	&nbsp; Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FULL (0)
	&nbsp; Calendar sched: Enabled
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 0 - 06/26/2012
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 1 - 09/18/2012
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 2 - 12/11/2012
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 3 - 03/05/2013
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 4 - 05/28/2013
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 5 - 08/20/2013
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 6 - 11/12/2013
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 7 - 02/04/2014
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 8 - 04/29/2014
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 9 - 07/22/2014
	&nbsp; Maximum MPX:&nbsp;&nbsp;&nbsp;&nbsp; 1
	&nbsp; Synthetic:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; PFI Recovery:&nbsp;&nbsp;&nbsp; 0
	&nbsp; Retention Level: 11 (56 days)
	&nbsp; u-wind/o/d:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 0
	&nbsp; Incr Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DELTA (0)
	&nbsp; Alt Read Host:&nbsp;&nbsp; (none defined)
	&nbsp; Max Frag Size:&nbsp;&nbsp; 0 MB
	&nbsp; Number Copies:&nbsp;&nbsp; 1
	&nbsp; Fail on Error:&nbsp;&nbsp; 0
	&nbsp; Residence:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (specific storage unit not required)
	&nbsp; Volume Pool:&nbsp;&nbsp;&nbsp;&nbsp; (same as policy volume pool)
	&nbsp; Server Group:&nbsp;&nbsp;&nbsp; (same as specified for policy)
	&nbsp; Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; Daily Windows:
	&nbsp;&nbsp; Day&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Open&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Close&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; W-Open&nbsp;&nbsp;&nbsp;&nbsp; W-Close
	&nbsp;&nbsp; Sunday&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00
	&nbsp;&nbsp; Monday&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 024:00:00&nbsp; 031:00:00
	&nbsp;&nbsp; Tuesday&nbsp;&nbsp;&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 048:00:00&nbsp; 055:00:00
	&nbsp;&nbsp; Wednesday&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 072:00:00&nbsp; 079:00:00
	&nbsp;&nbsp; Thursday&nbsp;&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 096:00:00&nbsp; 103:00:00
	&nbsp;&nbsp; Friday&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 120:00:00&nbsp; 127:00:00
	&nbsp;&nbsp; Saturday&nbsp;&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 144:00:00&nbsp; 151:00:00
	Schedule:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; synthetic
	&nbsp; Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FULL (0)
	&nbsp; Calendar sched: Enabled
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 0 - 07/24/2012
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 1 - 08/21/2012
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 2 - 10/16/2012
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 3 - 11/13/2012
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 4 - 01/08/2013
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 5 - 02/05/2013
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 6 - 04/02/2013
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 7 - 04/30/2013
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 8 - 06/25/2013
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 9 - 07/23/2013
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 10 - 09/17/2013
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 11 - 10/15/2013
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 12 - 12/10/2013
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 13 - 01/07/2014
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 14 - 03/04/2014
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 15 - 04/01/2014
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 16 - 05/27/2014
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 17 - 06/24/2014
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 18 - 08/19/2014
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 19 - 09/16/2014
	&nbsp; Maximum MPX:&nbsp;&nbsp;&nbsp;&nbsp; 1
	&nbsp; Synthetic:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1
	&nbsp; PFI Recovery:&nbsp;&nbsp;&nbsp; 0
	&nbsp; Retention Level: 11 (56 days)
	&nbsp; u-wind/o/d:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 0
	&nbsp; Incr Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DELTA (0)
	&nbsp; Alt Read Host:&nbsp;&nbsp; (none defined)
	&nbsp; Max Frag Size:&nbsp;&nbsp; 0 MB
	&nbsp; Number Copies:&nbsp;&nbsp; 1
	&nbsp; Fail on Error:&nbsp;&nbsp; 0
	&nbsp; Residence:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (specific storage unit not required)
	&nbsp; Volume Pool:&nbsp;&nbsp;&nbsp;&nbsp; (same as policy volume pool)
	&nbsp; Server Group:&nbsp;&nbsp;&nbsp; (same as specified for policy)
	&nbsp; Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; Daily Windows:
	&nbsp;&nbsp; Day&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Open&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Close&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; W-Open&nbsp;&nbsp;&nbsp;&nbsp; W-Close
	&nbsp;&nbsp; Sunday&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 008:00:00&nbsp; 016:00:00&nbsp;&nbsp; 008:00:00&nbsp; 016:00:00
	&nbsp;&nbsp; Monday&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 008:00:00&nbsp; 016:00:00&nbsp;&nbsp; 032:00:00&nbsp; 040:00:00
	&nbsp;&nbsp; Tuesday&nbsp;&nbsp;&nbsp;&nbsp; 008:00:00&nbsp; 016:00:00&nbsp;&nbsp; 056:00:00&nbsp; 064:00:00
	&nbsp;&nbsp; Wednesday&nbsp;&nbsp; 008:00:00&nbsp; 016:00:00&nbsp;&nbsp; 080:00:00&nbsp; 088:00:00
	&nbsp;&nbsp; Thursday&nbsp;&nbsp;&nbsp; 008:00:00&nbsp; 016:00:00&nbsp;&nbsp; 104:00:00&nbsp; 112:00:00
	&nbsp;&nbsp; Friday&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 008:00:00&nbsp; 016:00:00&nbsp;&nbsp; 128:00:00&nbsp; 136:00:00
	&nbsp;&nbsp; Saturday&nbsp;&nbsp;&nbsp; 008:00:00&nbsp; 016:00:00&nbsp;&nbsp; 152:00:00&nbsp; 160:00:00
	Schedule:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; incremental
	&nbsp; Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; INCR (1)
	&nbsp; Frequency:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 day(s) (86400 seconds)
	&nbsp;&nbsp;&nbsp; EXCLUDE DATE 0 - 06/26/2012
	&nbsp;&nbsp;&nbsp; EXCLUDE DATE 1 - 09/18/2012
	&nbsp;&nbsp;&nbsp; EXCLUDE DATE 2 - 12/11/2012
	&nbsp;&nbsp;&nbsp; EXCLUDE DATE 3 - 03/05/2013
	&nbsp;&nbsp;&nbsp; EXCLUDE DATE 4 - 05/28/2013
	&nbsp;&nbsp;&nbsp; EXCLUDE DATE 5 - 08/20/2013
	&nbsp;&nbsp;&nbsp; EXCLUDE DATE 6 - 11/12/2013
	&nbsp;&nbsp;&nbsp; EXCLUDE DATE 7 - 02/04/2014
	&nbsp;&nbsp;&nbsp; EXCLUDE DATE 8 - 04/29/2014
	&nbsp;&nbsp;&nbsp; EXCLUDE DATE 9 - 07/22/2014
	&nbsp; Maximum MPX:&nbsp;&nbsp;&nbsp;&nbsp; 1
	&nbsp; Synthetic:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; PFI Recovery:&nbsp;&nbsp;&nbsp; 0
	&nbsp; Retention Level: 11 (56 days)
	&nbsp; u-wind/o/d:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 0
	&nbsp; Incr Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DELTA (0)
	&nbsp; Alt Read Host:&nbsp;&nbsp; (none defined)
	&nbsp; Max Frag Size:&nbsp;&nbsp; 0 MB
	&nbsp; Number Copies:&nbsp;&nbsp; 1
	&nbsp; Fail on Error:&nbsp;&nbsp; 0
	&nbsp; Residence:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (specific storage unit not required)
	&nbsp; Volume Pool:&nbsp;&nbsp;&nbsp;&nbsp; (same as policy volume pool)
	&nbsp; Server Group:&nbsp;&nbsp;&nbsp; (same as specified for policy)
	&nbsp; Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; Daily Windows:
	&nbsp;&nbsp; Day&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Open&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Close&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; W-Open&nbsp;&nbsp;&nbsp;&nbsp; W-Close
	&nbsp;&nbsp; Sunday&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00
	&nbsp;&nbsp; Monday&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 024:00:00&nbsp; 031:00:00
	&nbsp;&nbsp; Tuesday&nbsp;&nbsp;&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 048:00:00&nbsp; 055:00:00
	&nbsp;&nbsp; Wednesday&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 072:00:00&nbsp; 079:00:00
	&nbsp;&nbsp; Thursday&nbsp;&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 096:00:00&nbsp; 103:00:00
	&nbsp;&nbsp; Friday&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 120:00:00&nbsp; 127:00:00
	&nbsp;&nbsp; Saturday&nbsp;&nbsp;&nbsp; 000:00:00&nbsp; 007:00:00&nbsp;&nbsp; 144:00:00&nbsp; 151:00:00
	&nbsp;
&nbsp;
Thanks for any help!
&nbsp;

nbustarter380 · Accepted Answer

Marianne,
Thanks for the Information and for all your respsones, we found the issue someone or somehow the etc/hosts file was changed on our Master Netbackup server. Netbackp uses the host name as the key to its database.
The full backup was run and completed successfully once that was fixed.
&nbsp;
Again thanks for your help!
&nbsp;

marianne · Answer

Why the mix of Calendar and Frequency schedules ?

nbustarter380 · Answer

Marianne, Thanks for your response
We are switiching from Frequency to calender based,&nbsp; We use a script to created the new calendar based&nbsp; schedule. In the&nbsp;script that was created it asks if we want to deactivate the&nbsp; "OLD" policy (frequency schedule) we reply yes. then the script asks to create a new policy not sure if that answers your question?
All polices will be Calendar based now
&nbsp;
Thanks
&nbsp;
&nbsp;
&nbsp;

&nbsp;
&nbsp;
&nbsp;
&nbsp;
&nbsp;

marianne · Answer

I would trust what bppllist tells us rather than a script.... You should be able to confirm the following by looking at the policy in the GUI.
I see the following schedules in policy testwater01:
Schedule:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; full
	&nbsp; Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FULL (0)
	&nbsp; Calendar sched: Enabled
Schedule:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; synthetic
	&nbsp; Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FULL (0)
	&nbsp; Calendar sched: Enabled
Schedule:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; incremental
	&nbsp; Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; INCR (1)
	&nbsp; Frequency:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 day(s) (86400 seconds)
&nbsp;
Which of these schedules failed with 200?
&nbsp;
&nbsp;

nbustarter380 · Answer

Hi Marianne thanks!
Sorry for the late response, I was away for a couple of days the&nbsp;"Schedule&nbsp;full" is failing.&nbsp;&nbsp;Since we are re-doing the policy&nbsp;schedule we start off with Full backups first.
&nbsp;
Thanks again&nbsp;

marianne · Answer

You have 2 Full schedules of type Calendar:
	full
	synthetic
full starts with these SPECIFIC days:
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 0 - 06/26/2012
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 1 - 09/18/2012
synthetic:
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 0 - 07/24/2012
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 1 - 08/21/2012
	&nbsp;&nbsp;&nbsp; SPECIFIC DATE 2 - 10/16/2012
and then a Frequency based INCR schedule with frequency of every 1 day.
	&nbsp;
So, the one and only time so far that the initial full schedule was supposed to run was on 26 June @ 00:00 with&nbsp; Effective date:&nbsp;&nbsp;&nbsp; 06/25/2012 23:59:59. (Cutting things very fine??)
	Is this when the backup failed?
	Have you tried to run a manual backup of this schedule in the meantime?
It is almost a week later.... What has been tried as a fix in the last week?
Without a full backup, what has happened to the daily Incrementals since the 26th?
	&nbsp;

Forum Discussion

Status 200 message "scheduler found no backups due to run

11 Replies

Related Content

Error message 0xe000fe0b when backup up systemstate

Exchange Archive Task "scheduled" reports not there...

Scheduled Job stuck on "To be scheduled" job status

Error with Scheduled backup "Please insert overwriteable media..."

Re: Job status

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