Video Screencast Help

Archive log backups not getting executed as scheduled

Created: 28 Feb 2013 • Updated: 02 Mar 2013 | 8 comments
This issue has been solved. See solution.

Hello All,

We are using NBU version - 7.1 in a Windows 2003 OS.  We have a DB server for which the archive log backup has been configured with the frequency set as 1 hour.  However, we see that the backup is not getting executed on an hourly basis.  What could be the root cause of this problem?  Please help with your valuable suggestion.

Thanks in advance.

Regards,

Jecintha

Operating Systems:

Comments 8 CommentsJump to latest comment

Marianne's picture

Please show us your policy config:
bppllist <policy-name> -U

When did last backup run?
Has there been any failures recently of this policy?

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

Jecintha's picture

Hello Marianne,

 

Thanks for your post.  There were no recent failures, however, the backup stopped getting executed after 10th Feb, 2013.

Before posting this comment, I had trigered a manual backup and after that I see that the backups are getting executed every one hour as per the schedule.

Though the backups are running fine now, I would like to know why the backup stopped getting executed.

Thanks for your help.

Regards,

Jecintha

Nicolai's picture

Sorry - Based on the information provided its impossible to say.

Best Rgards

Nicoai

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

jim dalton's picture

Policy type ie what flavour of DB? Does it fail or does it never even get triggered?

Jim

Jecintha's picture

This archivelog backup used to run as per the schedule, but it was temporarily disabled for some activity on the client server.  After the server was brought up, we had enabled the policy and triggered a manual backup.  This manual backup had got completed successfully.  But after that we have noticed that the backup did not get triggered as per the schedule - but if a manual backup was trigerred, that would get completed successfully.  Fortunately, after the last manual backup trigerred, we see that the policy is getting executed as per the schedule. I am just curious as to why the backups did not get triggered as per the schedule for around 2 weeks.

The output for bppllist <policy-name> -U is as under:

E:\Program Files\Veritas\NetBackup\bin\admincmd>bppllist NT_DB_hpdsscror03-dblog

s -U
------------------------------------------------------------
 
Policy Name:       NT_DB_hpdsscror03-dblogs
 
  Policy Type:         Oracle
  Active:              yes
  Effective date:      08/26/2011 15:52:29
  Block Incremental:   no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     9999
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           crhesb5500-hcart-group-tld-0n1
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      28800 seconds
 
  Granular Restore Info:  no
  Ignore Client Direct:  no
  HW/OS/Client:  Windows-x86   Windows2003   hpdsscror03
 
  Include:  C:\oracle\ORADATA\PITME\RMAN\rman_backup_archlogs.cmd
 
  Schedule:          Monthly_Full
    Type:            Automatic Full Backup
    Maximum MPX:     6
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 10 (5 years)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     Monthly
    Server Group:    (same as specified for policy)
    Calendar sched: Enabled
      Friday, Week 1
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Friday     19:00:00  -->  Monday     00:00:00
 
  Schedule:          Default-Application-Backup
    Type:            Application Backup
    Maximum MPX:     6
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 10 (5 years)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     Monthly
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     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_Full
    Type:            Automatic Full Backup
    Frequency:       every 1 hour
    Maximum MPX:     6
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 3 (1 month)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     Daily
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Sunday     00:00:00  -->  Sunday     23:50:00
          Monday     00:00:00  -->  Monday     23:50:00
          Tuesday    00:00:00  -->  Tuesday    23:50:00
          Wednesday  00:00:00  -->  Wednesday  23:50:00
          Thursday   00:00:00  -->  Thursday   23:50:00
          Friday     00:00:00  -->  Friday     23:50:00
          Saturday   00:00:00  -->  Saturday   23:50:00
 
  Schedule:          Weekly_Full
    Type:            Automatic Full Backup
    Maximum MPX:     6
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 3 (1 month)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     Weekly
    Server Group:    (same as specified for policy)
    Calendar sched: Enabled
      Friday, Week 2
      Friday, Week 3
      Friday, Week 4
      Friday, Week 5
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Friday     19:00:00  -->  Monday     00:00:00
 
Regards,
Jecintha
 
Vickie's picture

Please find the attached pdf doc about frequency based schedule.Hope this will help you,

As you stated a manual backup has been run.

So NBU has update that next hour's backup has completed already, and it will not run backup for coming schedule.

And once that one hour passed, on the second hour the backup starts working fine as per schedule.

You can check below article as well,

https://www-secure.symantec.com/connect/articles/netbackup-frequency-based-scheduling-1

 

Industry expert David Chapa has written an article explaining how to best use Frequency based schedules. David has kindly shared his article to be published on Connect.

AttachmentSize
Frequency Based Backups.pdf 75 KB
Marianne's picture

You should NEVER include Daily, Weekly, Monthly schedules in the same Oracle policy.

The reason is because there is only one  Default-Application-Backup. 
Actual data is backed up with this schedule and will get retention level specified for this schedule.

I have seen that hourly backups stop after one backup has failed.
For some or other reason, NBU applies the master server global setting of 2 tries per 12 hours (or whatever you have changed this setting to) after a failure.
The workaround is to kick-start the schedule again with a manual backup or to change the 'x tries per x' hours to smaller frequency, e.g. 1 try every 2 hours.
 

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

SOLUTION
Jecintha's picture

thanks Marianne, This was a very useful information.  thanks again