Forum Discussion

ramkr2020's avatar
ramkr2020
Level 5
13 years ago

Veritas Netbackup Differential backup policy backs up like full backup

Hi All,

Got an issue on one particular netbackup policy. I have configured a policy with Daily differential backup &Weekly full backup on a file server but it runs Full backup daily, This server was configured earlier with different policy name. Now i created a new policy and named a different policy name for this server. Problems which i am facing with this particular policy are.

*It's not starting as per schedule, have to manually start this policy

*Configured as Daily Differential but it runs full backup

*And at times the policy getting confused with earlier policies configured on same server and backing up only particular drive and folders which were configured earlier. does veritas netbackup stores the old policies configuration some where which makes this contradiction.

Appreciate if any one can help me on this issue. Thanks in Advance.  

 

7.1.x and Earlier
Backup and Recovery
NetBackup
Troubleshooting
  • Yasuhisa_Ishika's avatar
    Yasuhisa_Ishika
    Level 6
    13 years ago

    Have you already run full backup with this new policy? NetBackup does not inherit backup history accross policies. To incremental backup work as it is, full backup on this policy must be run first.

    For scheduling issue, please post output of "bppllist policy_name -U" and "nbpemreq -predict -dateu 2147483647 -policy_filter policy_name".

    I could not cleary figure out your last issue. Please tell us more detail?

  • ramkr2020's avatar
    ramkr2020
    Level 5
    13 years ago

     

    please see the outputs:
     
    C:\Program Files\VERITAS\NetBackup\bin\admincmd>bppllist File_Share_APSDYFS01 -U
     
    the specified policy does not exist in the configuration database (230)
     
    couldn't get the other command working: 
    C:\Program Files\VERITAS\NetBackup\bin\admincmd>nbpemreq -predict -dateu 2147483
    647 -policy_filter File_Share_APSYDFS01
    Invalid input-usage:
    usage: nbpemreq -updatepolicies
    usage: nbpemreq -predict -date <mm/dd/yyyy HH:MM:SS>
    usage: nbpemreq -predict -dateu <unixtime>
     
    *Last issue is this particular server is configured with different policy names to make it work by creating new policies. i am thinking is netbackup storing the old policy names anywhere to cause this issue. 

     

  • Marianne's avatar
    Marianne
    Level 6
    13 years ago

     

    C:\Program Files\VERITAS\NetBackup\bin\admincmd>bppllist File_Share_APSDYFS01 -U
     
    the specified policy does not exist in the configuration database (230)
    Please double-check policy name. NBU is case sensitive. If policy name is correct, the command will output full policy config.
     
    Is the old policy still active? Ensure it is deactivated or else delete it.
     
    Did you see Yasuhisa's question in his opening post?
    Have you already run full backup with this new policy? NetBackup does not inherit backup history accross policies. To incremental backup work as it is, full backup on this policy must be run first.
     
  • Yasuhisa_Ishika's avatar
    Yasuhisa_Ishika
    Level 6
    13 years ago

    Which version of NetBackup are you using? If you got error with "nbpemreq -predict -dateu 2147483647 -policy_filter policy_name", use "nbpemreq -predict 2147483647" instead.

    BTW, I checked policy information in your private message now, and wonder if you understand calendar schedule well.

    For example, backup window opens from Friday 19:00:00 to Monday 07:00:00 although you specified only Friday as run day. With this configuration, NetBackup can only start backup from Friday 19:00:00 to Friday 24:00:00.

    Schedule: Monthly_Archive
    Type: Full Backup
    Allowed to retry after run day
    Friday, Week 1
    EXCLUDE DATE 0 - 11/16/2012
    Daily Windows:
    Friday 19:00:00 --> Monday 07:00:00

    Weekly full is as below. Weekly full backup can start from Friday 19:00:00 to Friday 24:00:00. But you have excluded last Friday. This schedule does not take effect across Friday midnight. If you want, you need to add Saturday and Monday as run day.

    Schedule: Weekly_Full
    Type: Full Backup
    Allowed to retry after run day
    Friday, Week 2
    Friday, Week 3
    Friday, Week 4
    Friday, Week 5
    EXCLUDE DATE 0 - 11/16/2012
    Daily Windows:
    Friday 19:00:00 --> Monday 07:00:00

    This policy go active on last Friday, but full backup in this policy have never run so far. So daily differential incremental backup run on this Monday worked like full.

  • ramkr2020's avatar
    ramkr2020
    Level 5
    13 years ago

    I want Monthly archive to start and run only on first Friday and then it can continue to run on sat&sun, since first sat&fri differs in each month, not selecting sat on the policy. but daily differential have to run from mon to thursday. 

    policy is not showing up in the predict list that its goint to start. . other policies are showing up. 

     have excluded the weekly full since  i have manually ran the full back on that server for the new policy. 

    Pls let me know how to get this policy start as per schedule now.. 

    Schedule:          Daily_Differential

     

      Type:            Differential Incremental Backup
      Maximum MPX:     4
      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:     (same as policy volume pool)
      Calendar sched: Enabled
        Monday, Week 1
        Tuesday, Week 1
        Wednesday, Week 1
        Thursday, Week 1
        Monday, Week 2
        Tuesday, Week 2
        Wednesday, Week 2
        Thursday, Week 2
        Monday, Week 3
        Tuesday, Week 3
        Wednesday, Week 3
        Thursday, Week 3
        Monday, Week 4
        Tuesday, Week 4
        Wednesday, Week 4
        Thursday, Week 4
        Monday, Week 5
        Tuesday, Week 5
        Wednesday, Week 5
        Thursday, Week 5
        EXCLUDE DATE 0 - 11/16/2012
      Daily Windows:
            Monday     18:00:00  -->  Tuesday    06:10:00
            Tuesday    19:00:00  -->  Wednesday  07:00:00
            Wednesday  19:00:00  -->  Thursday   07:00:00
            Thursday   19:00:00  -->  Friday     07:00:00
     
     
    C:\Program Files\VERITAS\NetBackup\bin\admincmd>nbpemreq -predict 2147483647 -po
    licy_filter File_share_APSYDFS01
    Invalid input-usage:
    usage: nbpemreq -updatepolicies
    usage: nbpemreq -predict -date <mm/dd/yyyy HH:MM:SS>
    usage: nbpemreq -predict -dateu <unixtime>

     

  • RamNagalla's avatar
    RamNagalla
    Moderator
    13 years ago

    hey,

    1) what is the correct policy name in this question File_Share_APSDYFS01 or File_Share_APSYDFS01

     

    when you say its not starting as per the schudle , ther is something wrong with the policy schedule or with the nbpem timer.

    please porvide the below info

    bpplinfo -policy <correct policy name inthe question > -U

    bpclient -client <corrent client name inthe question > -U

  • Marianne's avatar
    Marianne
    Level 6
    13 years ago
    Run the weekly full backup manually tonight. Kick it off before the Incr is due. In future, make policy changes just before a full is due to prevent the issue that you are currently experiencing. This is normal behaviour in NBU but unfortunately not very well documented.
  • Yasuhisa_Ishika's avatar
    Yasuhisa_Ishika
    Level 6
    13 years ago

    Plese run "nbpemreq -predict 2147483647" in stead of "nbpemreq -predict 2147483647 -policy_filter File_share_APSYDFS01".

    NetBackup can start backup while start window is open *AND* the day is specified as run day.
    With your current configuration, NetBackup will work as below.

    • Monthly full backup can start from 19:00:00 to 24:00:00 on 1st Friday.
    • Weekly full backup can start from 19:00:00 to 24:00:00 on Friday except 1st Friday of the month.
    • Daily differential incremental backup can start on  following time table.
      - Monday 18:00:00 --> Tuesday 06:10:00
      - Tuesday 19:00:00 --> Wednesday 07:00:00
      - Wednesday 19:00:00 --> Thursday 07:00:00
      - Thursday 19:00:00 --> Thursday 24:00:00

    Once jobs go active, jobs keep running although start window become closed.
    NetBackup does not kill backup when start window is passed. If you configured your start window based on elapsed backup time, please reconsider.

    I think current configuration almost follow your intention: full backup must start Friday night, and NetBackup process backup as so. If you really want to allow full backup to start on Saturday, Sunday, and Monday moring, add them as run day.

    Anyway, you have to run full backup first to prevent diff from taking all the files. Run full backup manually.

  • ramkr2020's avatar
    ramkr2020
    Level 5
    13 years ago

     

    Thanks Marianne&Yasuhisa... now the policy runs fine .. only problem now its not starting as per schedule. have to manually run the full or differential ..not sure why its not starting as per schedule.. today it showed the wrong schedule when i checked the predict list.. pls advice.. 
     
    Thanks nagala - bpplinfo -policy <correct policy name inthe question > -U

    bpclient -client <corrent client name inthe question > -U -- - doesn't give any results.. 

     
     
     
  • ramkr2020's avatar
    ramkr2020
    Level 5
    13 years ago

     

    Not sure this helps to check why this policy is not starting up as per schedule.. 
     
    C:\Program Files\VERITAS\NetBackup\bin\admincmd>bppllist policy -l
     
    CLASS policy *NULL* 0 600000 0 *NULL*
    NAMES
    INFO 13 0 0 9998 *NULL* 0 0 4 0 0 0 0 0 0 0 1 0 0 1353054977 282347071F194A73BC9
    47BE710ADA97B 1 0 0 0 0 0 0 0 0 0
    KEY *NULL*
    BCMD *NULL*
    RCMD *NULL*
    RES apsydbu01-hcart-robot-tld-1 *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
     *NULL* *NULL*
    POOL NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup NetBa
    ckup NetBackup NetBackup
    FOE 0 0 0 0 0 0 0 0 0 0
    CLIENT  PC WindowsNET 0 0 0 0 *NULL*
    INCLUDE NEW_STREAM
    INCLUDE D:\
    INCLUDE NEW_STREAM
    INCLUDE E:\
    INCLUDE NEW_STREAM
    INCLUDE F:\
    SCHED Monthly_Archive 0 4 604800 9 0 0 0 *NULL* 0 2 0 0 0 0 -1
    SCHEDCALENDAR RETRIES
    SCHEDCALDAYOWEEK 6,1
    SCHEDCALEDATES 1352984400
    SCHEDWIN 0 0 0 0 0 0 0 0 0 0 68400 216000 0 0
    SCHEDRES *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
    SCHEDPOOL *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
    SCHEDRL 9 0 0 0 0 0 0 0 0 0
    SCHEDFOE 0 0 0 0 0 0 0 0 0 0
    SCHED Weekly_Full 0 4 604800 3 0 0 0 *NULL* 0 2 0 0 0 0 -1
    SCHEDCALENDAR RETRIES
    SCHEDCALDAYOWEEK 6,2;7,2;6,3;7,3;6,4;7,4;6,5;7,5
    SCHEDCALEDATES 1352984400
    SCHEDWIN 0 0 0 0 0 0 0 0 0 0 68400 216000 0 0
    SCHEDRES *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
    SCHEDPOOL *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
    SCHEDRL 3 1 1 1 1 1 1 1 1 1
    SCHEDFOE 0 0 0 0 0 0 0 0 0 0
    SCHED Daily_Differential 1 4 86400 3 0 0 0 *NULL* 0 1 0 0 0 0 -1
    SCHEDCALENDAR
    SCHEDCALDAYOWEEK 2,1;3,1;4,1;5,1;2,2;3,2;4,2;5,2;2,3;3,3;4,3;5,3;2,4;3,4;4,4;5,4
    ;2,5;3,5;4,5;5,5
    SCHEDCALEDATES 1352984400
    SCHEDWIN 0 0 64800 43800 68400 43200 68400 43200 68400 43200 0 0 0 0
    SCHEDRES *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
    SCHEDPOOL *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
    SCHEDRL 3 1 1 1 1 1 1 1 1 1
    SCHEDFOE 0 0 0 0 0 0 0 0 0 0