Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Single policy multiple schedules

Created: 30 Jul 2013 • Updated: 14 Aug 2013 | 11 comments
ashjosh's picture
This issue has been solved. See solution.

Hi Folks , 

I configured a Arch log policy under Netbackup 7.5.0.5 & set 3 Application level full backup Schedules under it.

1st backup should run at 5:30AM

2nd at 12:30 PM

3rd at 20:30.

all are calender based only.

But unfortunately only the last schudule is only running. Somehow its skipping 1st two schedules to run .

Any idea why this problem ?

Operating Systems:

Comments 11 CommentsJump to latest comment

Marianne's picture

Frequency schedule may be a better idea.

Please show us your policy:

bppllist <policy-name> -U

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

ashjosh's picture
[root@ahcbkp admincmd]# ./bppllist PRODEBS_ARCH_Daily -U
------------------------------------------------------------
 
Policy Name:       PRODEBS_ARCH_Daily
 
  Policy Type:         Oracle
  Active:              yes
  Effective date:      07/23/2013 15:25:19
  Block Incremental:   no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           ahcbkp-hcart3-robot-tld-0
  Volume Pool:         Oracle
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  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:  Linux         RedHat2.6.18  hdm01dbbkp
 
  Include:  /usr/openv/netbackup/ext/db_ext/oracle/samples/rman/database_arch_ba                                                                                                 ckup_daily.sh
 
  Schedule:              Full_Backup_01
    Type:                Automatic Full Backup
    Frequency:           every 1 day
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    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     14:59:00  -->  Sunday     15:25:00
          Monday     14:59:00  -->  Monday     15:25:00
          Tuesday    14:59:00  -->  Tuesday    15:25:00
          Wednesday  14:59:00  -->  Wednesday  15:25:00
          Thursday   14:59:00  -->  Thursday   15:25:00
          Friday     14:59:00  -->  Friday     15:25:00
          Saturday   14:59:00  -->  Saturday   15:25:00
 
  Schedule:              Full_Backup_02
    Type:                Automatic Full Backup
    Frequency:           every 1 day
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    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     15:00:00  -->  Sunday     15:30:00
          Monday     15:00:00  -->  Monday     15:30:00
          Tuesday    15:00:00  -->  Tuesday    15:30:00
          Wednesday  15:00:00  -->  Wednesday  15:30:00
          Thursday   15:00:00  -->  Thursday   15:30:00
          Friday     15:00:00  -->  Friday     15:30:00
          Saturday   15:00:00  -->  Saturday   15:30:00
 
  Schedule:              Full_Backup_03
    Type:                Automatic Full Backup
    Frequency:           every 1 day
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    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     15:03:00  -->  Sunday     15:20:00
          Monday     15:03:00  -->  Monday     15:20:00
          Tuesday    15:03:00  -->  Tuesday    15:20:00
          Wednesday  15:03:00  -->  Wednesday  15:20:00
          Thursday   15:03:00  -->  Thursday   15:20:00
          Friday     15:03:00  -->  Friday     15:20:00
          Saturday   15:03:00  -->  Saturday   15:20:00
 
  Schedule:              Default-Application-Backup
    Type:                Application Backup
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    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     00:00:00  -->  Sunday     24:00:00
          Monday     00:00:00  -->  Monday     24:00:00
          Tuesday    00:00:00  -->  Tuesday    24:00:00
          Wednesday  00:00:00  -->  Wednesday  24:00:00
          Thursday   00:00:00  -->  Thursday   24:00:00
          Friday     00:00:00  -->  Friday     24:00:00
          Saturday   00:00:00  -->  Saturday   24:00:00
 
 
I JUST CHANGED THE TIMINGS FOR MY TESTING.
Baski's picture

Hi

What type of Arch log policy is it oracle archive policy or file archive or any other policy.

If oracle archive policy, there are two types , one is Automated and second one is application. In application you can select calander or frequency but shcedule window give as per your timings.

please provide Marianne's requested information for better solution.

watsons's picture

Since your requirement is to run several backups within a day, as per Marianne's suggestion, using frequency-based will be a better option as you can specify how many hours apart you want to run.

If you use calendar-based, it might behave differently, as per the admin guide:

Calendar-based schedules run whenever the calendar schedule indicates. NetBackup assumes that an environment requires one backup on each day that is selected on the calendar schedule. Given an open schedule, backups run as soon after midnight as possible to satisfy the daily backup requirement.
Marianne's picture

Your Automatic schedules are all Frequency based and are set for once per day:

Schedule:              Full_Backup_01
    Type:                Automatic Full Backup
    Frequency:           every 1 day
 
Schedule:              Full_Backup_02
    Type:                Automatic Full Backup
    Frequency:           every 1 day
 
 Schedule:              Full_Backup_03
    Type:                Automatic Full Backup
    Frequency:           every 1 day
 
The way frequency based schedules work is that it will only run one of those schedules per day.
 
Rather have one schedule that runs every 8 hours.
You cannot use NBU schedules to kick off at a specific time. Backup window means it can start at any time during the window period.
If you need backups at a specific time, it will be better to use an external scheduler (e.g. cron) to kick off the backup.
 
Please see this article about Frequency Based schedules: 
https://www-secure.symantec.com/connect/articles/netbackup-frequency-based-scheduling-1
 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

ashjosh's picture

Hi ,

I changed it to frequency based , but still its not running as desired.

I wanted it to start at 7:00AM & should run upto next day 1:00AM every 6 hours.

Still policy is not starting at scheduled time.

& netbackup is predicting it to start at 00:50AM only once.

Pls suggest.

[root@ahcbkp admincmd]# ./bppllist  PRODEBS_ARCH_Daily -U
------------------------------------------------------------
 
Policy Name:       PRODEBS_ARCH_Daily
 
  Policy Type:         Oracle
  Active:              yes
  Effective date:      07/30/2013 16:45:55
  Block Incremental:   no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           ahcbkp-hcart3-robot-tld-0
  Volume Pool:         Oracle
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  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:  Linux         RedHat2.6.18  hdm01dbbkp
 
  Include:  /usr/openv/netbackup/ext/db_ext/oracle/samples/rman/database_arch_backup_daily.sh
 
  Schedule:              Full_Daily
    Type:                Automatic Full Backup
    Frequency:           every 6 hours
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    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     07:00:00  -->  Monday     01:00:00
          Monday     07:00:00  -->  Tuesday    01:00:00
          Tuesday    07:00:00  -->  Wednesday  01:00:00
          Wednesday  07:00:00  -->  Thursday   01:00:00
          Thursday   07:00:00  -->  Friday     01:00:00
          Friday     07:00:00  -->  Saturday   01:00:00
          Saturday   07:00:00  -->  Sunday     01:00:00
 
  Schedule:              Default-Application-Backup
    Type:                Application Backup
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    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     00:00:00  -->  Sunday     24:00:00
          Monday     00:00:00  -->  Monday     24:00:00
          Tuesday    00:00:00  -->  Tuesday    24:00:00
          Wednesday  00:00:00  -->  Wednesday  24:00:00
          Thursday   00:00:00  -->  Thursday   24:00:00
          Friday     00:00:00  -->  Friday     24:00:00
          Saturday   00:00:00  -->  Saturday   24:00:00
 
 
[root@ahcbkp admincmd]# ./nbpemreq -predict_all -date 08/10/2013
Predicted worklist including all jobs due to run between now and Sat 10 Aug 2013 12:59:59 AM AST
rl client               policy               schedule             type       due time
-- -------------------- -------------------- -------------------- ---------- ------------------
 
01 hdm01dbbkp           PRODEBS_ARCH_Daily   Full_Daily           0          Thu Aug  1 00:50:16 2013
 
Marianne's picture

Did you do a 'nbpemreq  -updatepolicies' after changing the schedules?

When last did the backup run?

Please show us output of:

bpimagelist -client hdm01dbbkp -pt Oracle  -hoursago 24 -U

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

ashjosh's picture

Hi ,

I did ./bprdreq -rereadconfig as well as ./nbpemreq -updatepolicies after the changes.

backup never happened as its not running on required timelines.

Its new implementation so i am not worried about backup imgaes as of now  , but policy should be run at regular time interval , so as soon as system went live we can start backup.

[root@ahcbkp admincmd]# ./bpimagelist -client hdm01dbbkp -pt Oracle  -hoursago 24 -U
no entity was found
Marianne's picture

How many hours is ' Thu Aug  1 00:50:16 2013' away? 

nbpemreq will only ever list the 'next' backup.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

ashjosh's picture

But Thu Aug  1 00:50:16 2013'  is not in schedule.

From where this value is coming?

& why its nt running after 6 hours.

Daily Windows:

          Sunday     07:00:00  -->  Monday     01:00:00
          Monday     07:00:00  -->  Tuesday    01:00:00
          Tuesday    07:00:00  -->  Wednesday  01:00:00
          Wednesday  07:00:00  -->  Thursday   01:00:00
          Thursday   07:00:00  -->  Friday     01:00:00
          Friday     07:00:00  -->  Saturday   01:00:00
          Saturday   07:00:00  -->  Sunday     01:00:00
watsons's picture

When you change a schedule to frequency-based, it does not go by the time you set. The next backup would be calculated from your last backup. 

If your last backup was run on Jul 31 18:50:16 2013, the next would be 6 hours away, which is Aug 1 00:50:16 2013.

If you want backup to run on certain time say at 13:00 (1PM), then prepare to run a manual backup right before 7:00 AM in the morning , this way once it completes the next schedule will be 13:00 (1PM).

Here is an example of my schedule runs every 2 hours. My manual backup happens on 7:04AM, and when I checked my nbpemreq predict, it shows:

# nbpemreq -predict_all -date 8/1/2013
Predicted worklist including all jobs due to run between now and Thu Aug  1 23:59:59 2013
rl client               policy               schedule             type       due time
-- -------------------- -------------------- -------------------- ---------- ------------------
00 msxxxx             Wins                 Incr                 1          Thu Aug  1 09:04:37 2013
 
SOLUTION