11-19-2012 04:03 PM
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.
11-19-2012 05:59 PM
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?
11-19-2012 08:40 PM
11-19-2012 09:08 PM
C:\Program Files\VERITAS\NetBackup\bin\admincmd>bppllist File_Share_APSDYFS01 -Uthe specified policy does not exist in the configuration database (230)
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.
11-19-2012 09:27 PM
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.
11-19-2012 10:26 PM
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
11-19-2012 10:46 PM
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
11-19-2012 10:53 PM
11-19-2012 11:22 PM
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.
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.
11-22-2012 05:36 PM
bpclient -client <corrent client name inthe question > -U -- - doesn't give any results..
11-22-2012 05:48 PM
11-22-2012 05:58 PM
11-22-2012 07:33 PM
... today it showed the wrong schedule when i checked the predict list..
Please show us what you see?
11-22-2012 09:23 PM
hi,
you have excluded the date 11/16/2012
and enabled the retries allowed after runday.
11-25-2012 03:18 PM
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. .
11-25-2012 08:16 PM
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>
11-26-2012 09:45 PM
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
11-26-2012 10:14 PM
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...
11-27-2012 05:46 PM
*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?
11-27-2012 09:23 PM
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/netbackup-frequency-based-scheduling
Seems like a good idea to create a new policy on Friday, deactivate this one, and see what happens.