Video Screencast Help

Veritas Netbackup Differential backup policy backs up like full backup

Created: 19 Nov 2012 | 21 comments

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.  

 

Comments 21 CommentsJump to latest comment

Yasuhisa Ishikawa's picture

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?

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

ramkr2020's picture

 

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 picture

 

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.
 

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

Yasuhisa Ishikawa's picture

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.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

ramkr2020's picture

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>

 

Nagalla's picture

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 picture

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.

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

Yasuhisa Ishikawa's picture

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.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

ramkr2020's picture

 

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 picture

 

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
ramkr2020's picture

 

Sorry got the bpplist and bpclient working.. pls find the results.. 
C:\Program Files\VERITAS\NetBackup\bin\admincmd>bpclient -client clientname -U
Client Name: clientname
 CURRENT HOST
    APSYDFS01 0
 HOST INFO
    2 0 0 0 0 2 1 1 0 1 3
 VALID HOST INFO
11
 
C:\Program Files\VERITAS\NetBackup\bin\admincmd>bppllist file_share_clientname -U
 
------------------------------------------------------------
 
Policy Name:       file_share_clientname
 
  Policy Type:         MS-Windows-NT
  Active:              yes
  Effective date:      11/16/2012 19:36:17
  Backup network drvs: no
  Collect TIR info:    no
  Mult. Data Streams:  yes
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     9998
  Max Jobs/Policy:     4
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           apsydbu01-hcart-robot-tld-1
  Volume Pool:         NetBackup
  Keyword:             (none specified)
 
  HW/OS/Client:  PC            WindowsNET    APSYDFS01
 
  Include:  NEW_STREAM
            D:\
            NEW_STREAM
            E:\
            NEW_STREAM
            F:\
 
  Schedule:          Monthly_Archive
    Type:            Full Backup
    Maximum MPX:     4
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 9 (infinity)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Calendar sched: Enabled
      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
 
  Schedule:          Weekly_Full
    Type:            Full 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
      Allowed to retry after run day
      Friday, Week 2
      Saturday, Week 2
      Friday, Week 3
      Saturday, Week 3
      Friday, Week 4
      Saturday, Week 4
      Friday, Week 5
      Saturday, Week 5
      EXCLUDE DATE 0 - 11/16/2012
    Daily Windows:
          Friday     19:00:00  -->  Monday     07:00:00
 
  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
 
Marianne's picture

... today it showed the wrong schedule when i checked the predict list..

Please show us what you see?

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

ramkr2020's picture

Hi ,

It was showing up as monthly archive when full backup has to run as per scheduled.. but today its not showing up the particlular client which is having issues in predict list  .... whereas other clients are showing up.. .. 

*Have created new policy, modified the policy.. updated the policies with nbpemreq -updatepolicies still this particular policy is not showing up in predict list.. any inputs will be helpful. . 

Nagalla's picture

hi,

you have excluded the date 11/16/2012

and enabled the retries allowed after runday.

 

Retries allowed after runday   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.
 
as you excluded the date 11/16 it did not run the job, but as you selected to have retires allowed, its trying to run the job untill it got succesfull. that is the reason its triggering full backup i guess..16 
 
why dont you create  new policy with no exclude dates(because your exclude date 11/16 is already passwd) and dont select retry option ... and see how it works...
 
 
good luck..
 
 
 
Marianne's picture

I have personally not experienced any joy with nbpemreq -updatepolicies.

I had to wait for nbpem to automatically refresh (every 10 minutes) or either close the GUI and restart NBU.

I hope you have followed advice to only create new policy or change existing before a Full is due to prevent Incrementals from running as full.

Please show us what you see - post output of following:

bppllist <policy-name> -U

nbpemreq -predict -date <mm/dd/yyyy HH:MM:SS>

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

ramkr2020's picture

yes, now incremental is running as incremental after running manual full backup but issue is the policy not starting as per schedule.. 

tried restarting nbu but it didn't help..  please find the outputs to analyze the issue.. 

nbpemreq -predict -date <mm/dd/yyyy HH:MM:SS> - gives all other policies scheduled but not showing up the policy which is having issue.. 

C:\Program Files\VERITAS\NetBackup\bin\admincmd>bppllist file_share_server -U

------------------------------------------------------------
 
Policy Name:       file_share_apsydfs01
 
  Policy Type:         MS-Windows-NT
  Active:              yes
  Effective date:      11/16/2012 19:36:17
  Backup network drvs: no
  Collect TIR info:    no
  Mult. Data Streams:  yes
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     9998
  Max Jobs/Policy:     4
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:         file_share_apsydfs01
  Volume Pool:         NetBackup
  Keyword:             (none specified)
 
  HW/OS/Client:  PC            WindowsNET    APSYDFS01
 
  Include:  NEW_STREAM
            D:\
            NEW_STREAM
            E:\
            NEW_STREAM
            F:\
 
  Schedule:          Monthly_Archive
    Type:            Full Backup
    Maximum MPX:     4
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 9 (infinity)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Calendar sched: Enabled
      Allowed to retry after run day
      Friday, Week 1
      EXCLUDE DATE 0 - 11/16/2012
      EXCLUDE DATE 1 - 11/23/2012
    Daily Windows:
          Friday     19:00:00  -->  Monday     07:00:00
 
  Schedule:          Weekly_Full
    Type:            Full 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
      Allowed to retry after run day
      Friday, Week 2
      Saturday, Week 2
      Friday, Week 3
      Saturday, Week 3
      Friday, Week 4
      Saturday, Week 4
      Friday, Week 5
      Saturday, Week 5
      EXCLUDE DATE 0 - 11/16/2012
    Daily Windows:
          Friday     19:00:00  -->  Monday     07:00:00
 
  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

 

 

Marianne's picture

Whate value did you use for '-date <mm/dd/yyyy HH:MM:SS>' ?

Did you follow advice to only create or modify policy before Full backup is due (i.e. last Friday)?

When last did a backup run for this policy/client combination? This will affect when next backup can be expected.

'NEW' policy seems to have exactly same settings as previous policy, e.g.
 Effective date:      11/16/2012 19:36:17

Does this mean that you have copied the previous policy? 
If there is some sort of corruption in the previous policy, it will be copied to new policy as well...
 

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

ramkr2020's picture

*16th i created this policy - haven't copied from old policy.. ran a manual full backup on the same day, full backup got completed... since then if i trigger increm backup.. it runs as incr backup and last frid 23rd full backup was triggered since its not starting as per schedule.. even yesterday night the incremental backup ran successfully after triggering it manually.. .. 

Whate value did you use for '-date <mm/dd/yyyy HH:MM:SS>' ? i have tried11/27/2012 21:00:00 and 11/28/2012 21:00:00 or any future dates like 11/29 or 12/03 doesnt show this policy schedule....

Every day the backups are triggered manually, does this affect the policy to start as per schedule.. do you suggest to create a new policy again for this client?

 

 

Marianne's picture

The time that you kick off the manual backup will affect automatic schedule. 

If a backup ran during the day, it will not kick off that night. I do expect it to run the next day as per schedule. I have no explanation of why it does not show in predict list. 
I also have a personal preference for Frequency scheduling over Calendar for daily and weekly schedules. See David Chapa's article about Frequency based scheduling:
https://www-secure.symantec.com/connect/articles/n...

Seems like a good idea to create a new policy on Friday, deactivate this one, and see what happens.

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

ramkr2020's picture

Unfortunately the link https://www-secure.symantec.com/connect/articles/n... not opening for me - The requested page could not be found.

 

Ok, i will deactivate the existing policy and create a new policy on friday, then i will run a manual full backup on the same day.. Will it start the normal schedule for the new policy from Monday onwards. 

ramkr2020's picture

Unfortunately the above link https://www-secure.symantec.com/connect/articles/n... gives error: The requested page could not be found.

Unfortunately Will deactivate the existing policy and i will create a new one this friday.. will start manual full backup on the same day.. once when its finished. Will monitor this policy on mond and tuesday to see whether it starts as per schedule..will update how the new policy works.. thanks Marianne.