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