NBU 7.6.0.3 i created a backup policy that should repeat every hour. so what i did is schedule the new policy to start today at 1pm up to 3pm. since i chose the schedule type to be "Frequency 1 hour", i was expecting it to execute again. questions are: since the backup took only 10 minutes, i thought it would execute again 60 minutes later, ie at 2:10pm (this didn't happen) since the backup window is from 1pm to 3pm, i thought the policy would execute again an hour after 3pm (so this one i'm still waiting) are any of my above assumptions correct? appreciate any help.

1: yes - this should be normal working behaviour. Did any of the backup trys fails ? Netbackup has "Job retry delay" & "Schedule backup attempts X tris per Y hours" that can affect scheduling. You can find the setting under Host Propertries -> Master Server -> Global Attributes. 2: Backup will not start outside the defined backup window. So if backup ran 2:10, 3:10 is outside the allowed backup window. Next run time is calculated from backup end time.

how do you create repeating backup policy?

10 Replies

Nicolai
Moderator
10 years ago
1: yes - this should be normal working behaviour. Did any of the backup trys fails ?

Netbackup has "Job retry delay" & "Schedule backup attempts X tris per Y hours" that can affect scheduling.

You can find the setting under Host Propertries -> Master Server -> Global Attributes.

2: Backup will not start outside the defined backup window. So if backup ran 2:10, 3:10 is outside the allowed backup window. Next run time is calculated from backup end time.
manatee
Level 6
10 years ago
oh you mean for repeating (hourly) backups i should define a 24 hour backup window?
Michal_Mikulik1
Moderator
10 years ago
Hello,

ad 1/ it is counted against start of backup, so next run should be earlier - around 2PM. If it does not run, there must be some misconfig. Also failed job attempts can postpone next runs

ad 2/ give some extra time to backup window, lets say set end to 3:05 at least

Michal
Nicolai
Moderator
10 years ago
Yes if you want the backup to run every 2hour around the clock
Marianne
Level 6
10 years ago
Please show us the policy:

bppllist <policy-name> -U

and output of :

nbpemreq -predict -date 11/17/2015 15:00

bpimagelist -client <client-name> -hoursago 4 -U

To answer your questions:

1. Backup should've started 1 hour after the start-time of the previous backup (if schedule was created correctly).

2. If backup window closed at 3pm, then the next backup cannot start an hour later.

More questions:

What is the default number of tries every ## hour in Global Properies?

Have you kicked of anything manually since creating this hourly schedule?

Has there been any failures since you created this schedule? Or have you maybe killed a job?

My reason for the last 3 questions:

I have seen how failures with an hourly schedule gets 'upset' by a failure.
The '# tries every ## hours' kicks in when a failure occurs and will only retry when ## hours have passed.
The issue is fixed by manually starting a job that completes successfully or by changing to 1 try every 1 hour.

The above is a Global attribute and will affect retry of failed jobs for all backups while backup window is open.

manatee

Level 6

10 years ago

hi everyone,

i made the backup window 24 hours and ran the policy manually. that's the only change since my last post.

anyway, i hope i can paste here the output without losing the formatting:

# ./bppllist ruh1sfadb_trxlog -U
------------------------------------------------------------

Policy Name:       ruh1sfadb_trxlog

  Policy Type:         MS-Windows
  Active:              yes
  Effective date:      12/12/2012 12:31:10
  Backup network drvs: no
  Collect TIR info:    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:           SLP-PureDisk-to-Tape
  Volume Pool:         Daily
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       Gold
  Residence is Storage Lifecycle Policy:    yes
  Application Discovery:      no
  Discovery Lifetime:      0 seconds
  ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  yes
  Enable Metadata Indexing:  no
  Index server name:  NULL
  Use Accelerator:  no
  Optimized Backup:  no
  HW/OS/Client:  Windows-x64   Windows2008   ruh1sfadb

  Include:  D:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup\sfadbTlogs

  Schedule:              Default-Application-Backup
    Type:                User Backup
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    PFI Recovery:        0
    Maximum MPX:         1
    Retention Level:     3 (1 month)
    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

  Schedule:              Daily
    Type:                Full Backup
    Frequency:           every 1 hour
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Maximum MPX:         1
    Retention Level:     0 (1 week)
    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  -->  Saturday   23:59:00

		  
		  
		  
		  
		  
# ./nbpemreq -predict -date 11/17/2015
Predicted work assuming no job run between now and Tue 17 Nov 2015 11:59:59 PM AST
rl client               policy               schedule             type
-- -------------------- -------------------- -------------------- ----------
00 ruh1abcdb            ruh1abcdb_trxlog     Daily                0
00 ruh1abcstg           ruh1abcstg_trxlog    Daily                0
00 ruh1sfadb            ruh1sfadb_trxlog     Daily                0
00 ruh1sfastg           ruh1sfastg_trxlog    Daily                0
00 ruh1dag01            MS_Exchange2013_DAG  Full                 0
00 ruh1fs01             RUH1FS01_STD_FILE    Daily                1
00 ruh1lms01            RUH1LMS01_STD_FILE   Daily                1
00 ruh1dc03             Windows_Domain_Controller Daily                1        
00 dev                  dev_std_file         Daily                1
00 ruh1cam              ruh1cam_std          Daily                1
00 uci-svr              uci-svr_diff         Diff                 0
00 prodr12              ascpdb_ora_hot       Daily                0
00 avs0021f6000009      auditVault_full      Daily                0
00 ruh1obidb1           obidb_ora_hot        Daily                0
00 ruh1erpdb2           ruh1erpdb2_ora_hot   Daily                0
00 ruh1fs01             ruh1fs01_file        Daily                1


# ./bpimagelist -client ruh1sfadb -hoursago 4 -U
Backed Up         Expires       Files       KB  C  Sched Type      On Hold Index Status Policy
----------------  ---------- -------- --------  -  --------------- ------- ------------ ------------
11/17/2015 16:26  12/18/2015       91  2938947  N  Full Backup     0       0            ruh1sfadb_trxlog
11/17/2015 15:10  12/18/2015        7 57322272  N  User Backup     0       0            ruh1sfadb_diff
11/17/2015 15:10  12/18/2015        5     5024  N  User Backup     0       0            ruh1sfadb_diff
11/17/2015 15:10  12/18/2015        0        0  N  Full Backup     0       0            ruh1sfadb_diff
11/17/2015 14:55  12/18/2015        5    66336  N  User Backup     0       0            ruh1sfadb_full
11/17/2015 14:55  12/18/2015        5     4832  N  User Backup     0       0            ruh1sfadb_full
11/17/2015 14:19  12/18/2015        7 105071776  N  User Backup    0       0            ruh1sfadb_full
11/17/2015 14:19  12/18/2015        5   390048  N  User Backup     0       0            ruh1sfadb_full
11/17/2015 14:18  12/18/2015        0        0  N  Full Backup     0       0            ruh1sfadb_full
11/17/2015 14:10  12/18/2015       89  2293859  N  Full Backup     0       0            ruh1sfadb_trxlog
11/17/2015 13:39  12/18/2015        5    66400  N  User Backup     0       0            ruh1sfadb
11/17/2015 13:39  12/18/2015        5     4832  N  User Backup     0       0            ruh1sfadb
11/17/2015 13:01  12/18/2015        7 103521056  N  User Backup    0       0            ruh1sfadb
11/17/2015 13:00  12/18/2015        5   390048  N  User Backup     0       0            ruh1sfadb
11/17/2015 13:00  12/18/2015        0        0  N  Full Backup     0       0            ruh1sfadb

manatee
Level 6
10 years ago
the number of tries is 2 every 12 hours.

yes i manually started them.

no failures. yet.

no jobs killed.
Marianne
Level 6
10 years ago
I was hoping for nbpemreq with hh:mm within the next hour. Without that it defaults to midnight.

Did the job that started at 16:26 kick off automatically or did you start it manually?

The logic behind 1 hour frequency is that the next job will be submitted 1 hour after the start of previous successful job.
If no resources are available, the job will queue.
When the job goes active, we need to wait for successful flag to start the calculation from the beginning of the job.
manatee
Level 6
10 years ago
the job i started manually. the first one is at 16:14 and now at 17:14 it started by itself. which is what i am expecting.
manatee
Level 6
10 years ago
it's working fine now.

so for repeating policies backup window should be 24 hours and let the "Frequency" handle when the next job will occur. but calculations start from a successful job only.

thanks for all replies.

Forum Discussion

how do you create repeating backup policy?

10 Replies

Related Content

Create Oracle Policy Using Script

Creating a backup policy from cli

Create Same schedule in multiple policies

Can't create a VMWare Policy

Creating a new Desktop Policy