Single policy multiple schedules

Question

Hi Folks ,&nbsp;
I configured a Arch log policy under Netbackup 7.5.0.5 &amp; 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 .
&nbsp;
Any idea why this problem ?

watsons · Accepted Answer

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.&nbsp;
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&nbsp;, 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 &nbsp;1 23:59:59 2013
rl client &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; policy &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; schedule &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; type &nbsp; &nbsp; &nbsp; due time
-- -------------------- -------------------- -------------------- ---------- ------------------
00 msxxxx &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Wins &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Incr &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Thu Aug &nbsp;1 09:04:37 2013
&nbsp;

marianne · Answer

Frequency schedule may be a better idea.
Please show us your policy:
bppllist &lt;policy-name&gt; -U

baski · Answer

Hi
What type of Arch log policy is it oracle archive policy or file archive or any other policy.
&nbsp;
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.
&nbsp;
&nbsp;

ashjosh · Answer

[root@ahcbkp admincmd]# ./bppllist PRODEBS_ARCH_Daily -U
------------------------------------------------------------
&nbsp;
Policy Name: &nbsp; &nbsp; &nbsp; PRODEBS_ARCH_Daily
&nbsp;
&nbsp; Policy Type: &nbsp; &nbsp; &nbsp; &nbsp; Oracle
&nbsp; Active: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;yes
&nbsp; Effective date: &nbsp; &nbsp; &nbsp;07/23/2013 15:25:19
&nbsp; Block Incremental: &nbsp; no
&nbsp; Mult. Data Streams: &nbsp;no
&nbsp; Client Encrypt: &nbsp; &nbsp; &nbsp;no
&nbsp; Checkpoint: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;no
&nbsp; Policy Priority: &nbsp; &nbsp; 0
&nbsp; Max Jobs/Policy: &nbsp; &nbsp; Unlimited
&nbsp; Disaster Recovery: &nbsp; 0
&nbsp; Collect BMR info: &nbsp; &nbsp;no
&nbsp; Residence: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ahcbkp-hcart3-robot-tld-0
&nbsp; Volume Pool: &nbsp; &nbsp; &nbsp; &nbsp; Oracle
&nbsp; Server Group: &nbsp; &nbsp; &nbsp; &nbsp;*ANY*
&nbsp; Keyword: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (none specified)
&nbsp; Data Classification: &nbsp; &nbsp; &nbsp; -
&nbsp; Residence is Storage Lifecycle Policy: &nbsp; &nbsp;no
&nbsp; Application Discovery: &nbsp; &nbsp; &nbsp;no
&nbsp; Discovery Lifetime: &nbsp; &nbsp; &nbsp;0 seconds
ASC Application and attributes: (none defined)
&nbsp;
&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;Linux &nbsp; &nbsp; &nbsp; &nbsp; RedHat2.6.18 &nbsp;hdm01dbbkp
&nbsp;
&nbsp; Include: &nbsp;/usr/openv/netbackup/ext/db_ext/oracle/samples/rman/database_arch_ba &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ckup_daily.sh
&nbsp;
&nbsp; Schedule: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Full_Backup_01
&nbsp; &nbsp; Type: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Automatic Full Backup
&nbsp; &nbsp; Frequency: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; every 1 day
&nbsp; &nbsp; Maximum MPX: &nbsp; &nbsp; &nbsp; &nbsp; 1
&nbsp; &nbsp; Synthetic: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0
&nbsp; &nbsp; Checksum Change Detection: 0
&nbsp; &nbsp; PFI Recovery: &nbsp; &nbsp; &nbsp; &nbsp;0
&nbsp; &nbsp; Retention Level: &nbsp; &nbsp; 1 (2 weeks)
&nbsp; &nbsp; Number Copies: &nbsp; &nbsp; &nbsp; 1
&nbsp; &nbsp; Fail on Error: &nbsp; &nbsp; &nbsp; 0
&nbsp; &nbsp; Residence: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (specific storage unit not required)
&nbsp; &nbsp; Volume Pool: &nbsp; &nbsp; &nbsp; &nbsp; (same as policy volume pool)
&nbsp; &nbsp; Server Group: &nbsp; &nbsp; &nbsp; &nbsp;(same as specified for policy)
&nbsp; &nbsp; Residence is Storage Lifecycle Policy: &nbsp; &nbsp; &nbsp; &nbsp; 0
&nbsp; &nbsp; Schedule indexing: &nbsp; &nbsp; 0
&nbsp; &nbsp; Daily Windows:
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Sunday &nbsp; &nbsp; 14:59:00 &nbsp;--&gt; &nbsp;Sunday &nbsp; &nbsp; 15:25:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Monday &nbsp; &nbsp; 14:59:00 &nbsp;--&gt; &nbsp;Monday &nbsp; &nbsp; 15:25:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Tuesday &nbsp; &nbsp;14:59:00 &nbsp;--&gt; &nbsp;Tuesday &nbsp; &nbsp;15:25:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Wednesday &nbsp;14:59:00 &nbsp;--&gt; &nbsp;Wednesday &nbsp;15:25:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Thursday &nbsp; 14:59:00 &nbsp;--&gt; &nbsp;Thursday &nbsp; 15:25:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Friday &nbsp; &nbsp; 14:59:00 &nbsp;--&gt; &nbsp;Friday &nbsp; &nbsp; 15:25:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Saturday &nbsp; 14:59:00 &nbsp;--&gt; &nbsp;Saturday &nbsp; 15:25:00
&nbsp;
&nbsp; Schedule: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Full_Backup_02
&nbsp; &nbsp; Type: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Automatic Full Backup
&nbsp; &nbsp; Frequency: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; every 1 day
&nbsp; &nbsp; Maximum MPX: &nbsp; &nbsp; &nbsp; &nbsp; 1
&nbsp; &nbsp; Synthetic: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0
&nbsp; &nbsp; Checksum Change Detection: 0
&nbsp; &nbsp; PFI Recovery: &nbsp; &nbsp; &nbsp; &nbsp;0
&nbsp; &nbsp; Retention Level: &nbsp; &nbsp; 1 (2 weeks)
&nbsp; &nbsp; Number Copies: &nbsp; &nbsp; &nbsp; 1
&nbsp; &nbsp; Fail on Error: &nbsp; &nbsp; &nbsp; 0
&nbsp; &nbsp; Residence: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (specific storage unit not required)
&nbsp; &nbsp; Volume Pool: &nbsp; &nbsp; &nbsp; &nbsp; (same as policy volume pool)
&nbsp; &nbsp; Server Group: &nbsp; &nbsp; &nbsp; &nbsp;(same as specified for policy)
&nbsp; &nbsp; Residence is Storage Lifecycle Policy: &nbsp; &nbsp; &nbsp; &nbsp; 0
&nbsp; &nbsp; Schedule indexing: &nbsp; &nbsp; 0
&nbsp; &nbsp; Daily Windows:
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Sunday &nbsp; &nbsp; 15:00:00 &nbsp;--&gt; &nbsp;Sunday &nbsp; &nbsp; 15:30:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Monday &nbsp; &nbsp; 15:00:00 &nbsp;--&gt; &nbsp;Monday &nbsp; &nbsp; 15:30:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Tuesday &nbsp; &nbsp;15:00:00 &nbsp;--&gt; &nbsp;Tuesday &nbsp; &nbsp;15:30:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Wednesday &nbsp;15:00:00 &nbsp;--&gt; &nbsp;Wednesday &nbsp;15:30:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Thursday &nbsp; 15:00:00 &nbsp;--&gt; &nbsp;Thursday &nbsp; 15:30:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Friday &nbsp; &nbsp; 15:00:00 &nbsp;--&gt; &nbsp;Friday &nbsp; &nbsp; 15:30:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Saturday &nbsp; 15:00:00 &nbsp;--&gt; &nbsp;Saturday &nbsp; 15:30:00
&nbsp;
&nbsp; Schedule: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Full_Backup_03
&nbsp; &nbsp; Type: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Automatic Full Backup
&nbsp; &nbsp; Frequency: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; every 1 day
&nbsp; &nbsp; Maximum MPX: &nbsp; &nbsp; &nbsp; &nbsp; 1
&nbsp; &nbsp; Synthetic: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0
&nbsp; &nbsp; Checksum Change Detection: 0
&nbsp; &nbsp; PFI Recovery: &nbsp; &nbsp; &nbsp; &nbsp;0
&nbsp; &nbsp; Retention Level: &nbsp; &nbsp; 1 (2 weeks)
&nbsp; &nbsp; Number Copies: &nbsp; &nbsp; &nbsp; 1
&nbsp; &nbsp; Fail on Error: &nbsp; &nbsp; &nbsp; 0
&nbsp; &nbsp; Residence: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (specific storage unit not required)
&nbsp; &nbsp; Volume Pool: &nbsp; &nbsp; &nbsp; &nbsp; (same as policy volume pool)
&nbsp; &nbsp; Server Group: &nbsp; &nbsp; &nbsp; &nbsp;(same as specified for policy)
&nbsp; &nbsp; Residence is Storage Lifecycle Policy: &nbsp; &nbsp; &nbsp; &nbsp; 0
&nbsp; &nbsp; Schedule indexing: &nbsp; &nbsp; 0
&nbsp; &nbsp; Daily Windows:
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Sunday &nbsp; &nbsp; 15:03:00 &nbsp;--&gt; &nbsp;Sunday &nbsp; &nbsp; 15:20:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Monday &nbsp; &nbsp; 15:03:00 &nbsp;--&gt; &nbsp;Monday &nbsp; &nbsp; 15:20:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Tuesday &nbsp; &nbsp;15:03:00 &nbsp;--&gt; &nbsp;Tuesday &nbsp; &nbsp;15:20:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Wednesday &nbsp;15:03:00 &nbsp;--&gt; &nbsp;Wednesday &nbsp;15:20:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Thursday &nbsp; 15:03:00 &nbsp;--&gt; &nbsp;Thursday &nbsp; 15:20:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Friday &nbsp; &nbsp; 15:03:00 &nbsp;--&gt; &nbsp;Friday &nbsp; &nbsp; 15:20:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Saturday &nbsp; 15:03:00 &nbsp;--&gt; &nbsp;Saturday &nbsp; 15:20:00
&nbsp;
&nbsp; Schedule: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Default-Application-Backup
&nbsp; &nbsp; Type: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Application Backup
&nbsp; &nbsp; Maximum MPX: &nbsp; &nbsp; &nbsp; &nbsp; 1
&nbsp; &nbsp; Synthetic: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0
&nbsp; &nbsp; Checksum Change Detection: 0
&nbsp; &nbsp; PFI Recovery: &nbsp; &nbsp; &nbsp; &nbsp;0
&nbsp; &nbsp; Retention Level: &nbsp; &nbsp; 1 (2 weeks)
&nbsp; &nbsp; Number Copies: &nbsp; &nbsp; &nbsp; 1
&nbsp; &nbsp; Fail on Error: &nbsp; &nbsp; &nbsp; 0
&nbsp; &nbsp; Residence: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (specific storage unit not required)
&nbsp; &nbsp; Volume Pool: &nbsp; &nbsp; &nbsp; &nbsp; (same as policy volume pool)
&nbsp; &nbsp; Server Group: &nbsp; &nbsp; &nbsp; &nbsp;(same as specified for policy)
&nbsp; &nbsp; Residence is Storage Lifecycle Policy: &nbsp; &nbsp; &nbsp; &nbsp; 0
&nbsp; &nbsp; Schedule indexing: &nbsp; &nbsp; 0
&nbsp; &nbsp; Daily Windows:
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Sunday &nbsp; &nbsp; 00:00:00 &nbsp;--&gt; &nbsp;Sunday &nbsp; &nbsp; 24:00:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Monday &nbsp; &nbsp; 00:00:00 &nbsp;--&gt; &nbsp;Monday &nbsp; &nbsp; 24:00:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Tuesday &nbsp; &nbsp;00:00:00 &nbsp;--&gt; &nbsp;Tuesday &nbsp; &nbsp;24:00:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Wednesday &nbsp;00:00:00 &nbsp;--&gt; &nbsp;Wednesday &nbsp;24:00:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Thursday &nbsp; 00:00:00 &nbsp;--&gt; &nbsp;Thursday &nbsp; 24:00:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Friday &nbsp; &nbsp; 00:00:00 &nbsp;--&gt; &nbsp;Friday &nbsp; &nbsp; 24:00:00
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Saturday &nbsp; 00:00:00 &nbsp;--&gt; &nbsp;Saturday &nbsp; 24:00:00
&nbsp;
&nbsp;
I JUST CHANGED THE TIMINGS FOR MY TESTING.

watsons · Answer

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&nbsp;schedule indicates. NetBackup assumes that an environment&nbsp;requires one backup on each day that is selected on the&nbsp;calendar schedule. Given an open schedule, backups run as&nbsp;soon after midnight as possible to satisfy the daily backup&nbsp;requirement.

marianne · Answer

Your Automatic schedules are all Frequency based and are set for once per day:
Schedule: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Full_Backup_01
&nbsp; &nbsp; Type: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Automatic Full Backup
&nbsp; &nbsp; Frequency: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; every 1 day
&nbsp;

Schedule: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Full_Backup_02
	&nbsp; &nbsp; Type: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Automatic Full Backup
	&nbsp; &nbsp; Frequency: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; every 1 day
	&nbsp;
	
		&nbsp;Schedule: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Full_Backup_03
		&nbsp; &nbsp; Type: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Automatic Full Backup
		&nbsp; &nbsp; Frequency: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; every 1 day
		&nbsp;
		The way frequency based schedules work is that it will only run one of those schedules per day.
		&nbsp;
		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.
		&nbsp;
		Please see this article about Frequency Based schedules:&nbsp;
			https://www-secure.symantec.com/connect/articles/netbackup-frequency-based-scheduling-1
		&nbsp;

&nbsp;

Forum Discussion

Single policy multiple schedules

11 Replies

Related Content

Saving a Report Schedule - Cron

NBU IT Analytics 11.2 - send out multiple reports in one scheduled email

Replication to multiple domains

Multiple schedule config for SAP HANA DB backup from single policy

Create Same schedule in multiple policies

Recent Discussions

"failed, status 6" error after increasing datastore (LUN) capacity

command: bperror

MS-SharePoint policy restore error (2804) .

How to restore a backup

How to configure RBAC