Forum Discussion

Rahul_Arora1's avatar
Rahul_Arora1
Level 4
15 years ago

Backup got fired without schedule

Hi All,

I am using NetBackup 6.5.3.1. I have configired the Yearly FULL Backup to run every 1st saturday of year (means 1st saturday of January). But Backup got fired in july without any schedule. Any reasons??

I checked the POLICY & it is configured correctly.
7.1.x and Earlier
Backing Up
Backup and Recovery
Best Practice
Configuring
NetBackup
Performance
  • Marianne's avatar
    Marianne
    15 years ago

    "We changed the HostName entries in Policies"

    So - there was no backup for new client name on 01/02/2010? That will most definitely initiate a backup as soon as an open window is found with 'Allow after run day' .

    Please understand that each Client Name in a policy is evaluated individually by nbpem to determine if a backup is due. The question asked by nbpem: When was the last backup run for this client in this policy for this schedule? The answer to this question is NEVER... So, a backup is due.

    This is not a problem or a bug. This is how NetBackup works.

    This topic in Admin Guide II helped me to understand how NBU scheduling works:

    How NetBackup builds a worklist

    NetBackup builds an internal worklist that contains all scheduled, active jobs. NetBackup calculates the due time for each job, then sorts all the jobs in the worklist in the order that the jobs are due:
    a.  NetBackup builds a worklist that consists of jobs for every client in every policy.
    b.  NetBackup evaluates each job and determines when it is due, based on the following factors:
    ■ When the job ran last
    ■ How often the job is scheduled to run (the frequency of the job)
    ■ How soon the next scheduled window is open for the job (if the window is not currently open)


  • Rahul_Arora1's avatar
    Rahul_Arora1
    Level 4
    15 years ago
    Hi,

    I checked the Job Details. It is showing as "Scheduled" & not "Immidiate". If someone has fired it manually, it should have "Immediate" as type.
  • Marianne's avatar
    Marianne
    Level 6
    15 years ago

    Do you have 'Allow after run date' checked?

    Please post policy output - bppllist <policy_name> -U

    Without being able to see how policy is configured, we're just guessing...
  • Rahul_Arora1's avatar
    Rahul_Arora1
    Level 4
    15 years ago
    Allowed to retry after run day


    Please find output:

      Policy Type:         Standard
      Active:              yes
      Effective date:      10/18/2009 21:36:55
      Client Compress:     no
      Follow NFS Mounts:   yes
      Cross Mount Points:  no
      Collect TIR info:    no
      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:           ******************
      Volume Pool:         NetBackup
      Server Group:        *ANY*
      Keyword:             (none specified)
      Data Classification:       -
      Residence is Storage Lifecycle Policy:    no
    Granular Restore Info:  no
      HW/OS/Client:  Solaris       Solaris10     ********
                     Solaris       Solaris10     ********
      Include:  ALL_LOCAL_DRIVES
      Schedule:          Yearly_Full
        Type:            Full Backup
        Maximum MPX:     1
        Synthetic:       0
        PFI Recovery:    0
        Retention Level: 13 (7 years) 1 (2 weeks)
        Number Copies:   2
        Fail on Error:   0 0
        Residence:       *********-hcart-robot-tld-0 *******-hcart-robot-tld-0
        Volume Pool:     XXXXXXXXX
        Server Group:    *ANY* *ANY*
        Calendar sched: Enabled
          Allowed to retry after run day
          SPECIFIC DATE 0 - 01/02/2010
          SPECIFIC DATE 1 - 01/01/2011
          SPECIFIC DATE 2 - 01/07/2012
          SPECIFIC DATE 3 - 01/05/2013
          SPECIFIC DATE 4 - 01/04/2014
          SPECIFIC DATE 5 - 01/03/2015
          SPECIFIC DATE 6 - 01/02/2016
          SPECIFIC DATE 7 - 01/07/2017
          SPECIFIC DATE 8 - 01/06/2018
          SPECIFIC DATE 9 - 01/05/2019
          SPECIFIC DATE 10 - 01/04/2020
        Residence is Storage Lifecycle Policy:     0
        Daily Windows:
              Saturday   10:00:00  -->  Monday     04:00:00Policy Name:       *********
  • Marianne's avatar
    Marianne
    Level 6
    15 years ago
    Was there a successful yearly backup for this policy on 01/02/2010? 
    If not, "Retries allowed after runday" will cause backup to run whenever it finds an open window.

    Explanation from Admin Guide:
    Enable Retries allowed after runday to have NetBackup attempt to complete this schedule until the backup is successful. With this attribute enabled, the schedule attempts to do run, even after a specified run day.
  • Rahul_Arora1's avatar
    Rahul_Arora1
    Level 4
    15 years ago

    I will check the Status of Backup on that day, but I have a query:

    1) If the Backup could have failed then I would definately have reran it.

    2) In any case, I forgot to rerun. Why the Backup started in July, it was scheduled for early January. It should have reran nearby that time.


    Please explain this feature of NetBackup, meanwhile I will check out the Status of Backup on 01/02/2010.

  • AAlmroth's avatar
    AAlmroth
    Level 6
    15 years ago

    I don't have a solution, but nbpem up until 6.5.4 was very unstable and could miss queueing backup jobs due to nbjm. There could be so many various variables to why the backup executed in July instead. If you keep the VxUL logs for PEM for a long time, then perhaps we can trace the root cause, but in most cases only 28 days is kept.

    Here are some technotes that may give you some hints as well to the functionality of nbpem;

    "Tech Alert: A potential for missed backups without notification has been discovered in NetBackup Server/Enterprise Server when calendar based schedules have a configured window spanning midnight and go Active after midnight." http://seer.entsupport.symantec.com/docs/311581.htm

    "DOCUMENTATION: The behavior of backups with a calendar schedule changes in 6.5.2 / 6.5.2A when the backup window spans midnight. Backups for a run day will always become due at midnight (the start of the run day)." http://seer.entsupport.symantec.com/docs/307649.htm

    "DOCUMENTATION: Additional information regarding frequency and calendar based scheduling. An item of particular note, calendar based schedules within the same policy are dependent on one another. " http://seer.entsupport.symantec.com/docs/274891.htm

    I would strongly recommend you to upgrade at least the master server to 6.5.6...

    /A
     

  • Rahul_Arora1's avatar
    Rahul_Arora1
    Level 4
    15 years ago
    I already mentioned that I am on a version of 6.5.3. I could not find anything in TechNote which could apply to this version. Still the TechNote is quite helpful for reference. Please provide more information if possible.
  • Rahul_Arora1's avatar
    Rahul_Arora1
    Level 4
    15 years ago
    Hi Marianne,

    I checked the 01/02/2010 backup & it was successful. Now, I come on the same page, when it was successful, why it ran again without any schedule being set, that too exactly after 26 weeks (half year).

    I am not able to understand this behaviour of NetBackup & I never came across such conditions. Is this a bug or something..