NBU 7.1Retention Report shows 2038 Expairy year
Hi,
We have implemented NBU 7.1 in our datacenter. Today I have seen the successful backup job reports, it is showing wrong expairy date for all media in GUI. We set custom 1 month retention period for "xyz" backup policy but when backup complete it shows 01/18/2038 expairy date. When we ran "bpimagelist -client "xyz" -d 10/29/2012 -e 11/02/2012 -U from command prompt. It gives following result report
11/01/2012 22:01 INFINITY 7766 2091864 N Differential "xyz"
11/01/2012 22:00 INFINITY 20293 8711914 N Differential "xyz"
10/31/2012 22:01 INFINITY 9608 2676372 N Differential "xyz"
10/31/2012 22:01 INFINITY 3146 15627 N Differential "xyz"
10/31/2012 10:04 INFINITY 62096 85764478 N Differential "xyz"
10/30/2012 22:01 INFINITY 10789 2089835 N Differential "xyz"
10/29/2012 23:29 INFINITY 10743 2072530 N Differential "xyz"
10/29/2012 04:05 INFINITY 10759 2072181 N Differential "xyz"
Why this is showing wrong expiry date in report as we set custom?
Any body suggest solution on above query.....
Regards,
Arvind
This will probably be correct
This will probably be correct then.
With SLP, when you make a backup copy, it gets the retention of infinity.
Only when the copy is made successfully does the backup copy revert to the value you have set.
This is normal behavior and is the whole point of SLP.
Martin
Comments
Are you using SLP ? Can you
Are you using SLP ?
Can you post up
Output of these commands
bppllist <policy name> -U
bpretlevel
Can you confirm what the
Can you confirm what the retention level is set to in the policy/schedule? Is it correct?
Can you confirm that your 'custom expiry date' for one month is exactly that? Why a custom expiry date as there is a default one (ret level 3)
Has someone used bpexdate to *manually* change the retention period for these images (or media even) to "INFINITY" (ret level 9)?
Regards Andy
"Have you still got the box it came in?"
Hi, Thanks for you
Hi,
Thanks for you Response!!!!!
Yes, we are using SLP for this policy. After executing "bppllist <policy name> -U", We got following output on Master server.
Policy Name: xyz
Policy Type: MS-Windows
Active: yes
Effective date: 01/06/2012 14:08:47
Backup network drvs: no
Collect TIR info: yes, with move detection
Mult. Data Streams: no
Client Encrypt: no
Checkpoint: yes
Interval: 30
Policy Priority: 0
Max Jobs/Policy: 10
Disaster Recovery: 0
Collect BMR info: yes
Residence: tape-loadbalance
Volume Pool: sg-shared
Server Group: *ANY*
Keyword: abc
Data Classification: -
Residence is Storage Lifecycle Policy: no
Application Discovery: no
Discovery Lifetime: 0 seconds
Granular Restore Info: no
Ignore Client Direct: no
HW/OS/Client: Windows-x64 Windows2008 xyz
Include: ALL_LOCAL_DRIVES
Schedule: Weekly-Full
Type: Full Backup
Frequency: every 7 days
Maximum MPX: 15
Synthetic: 0
PFI Recovery: 0
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: abc
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 1
Daily Windows:
Saturday 22:00:00 --> Sunday 06:00:00
Schedule: Daily-Inc
Type: Differential Incremental Backup
Frequency: every 1 day
Maximum MPX: 15
Synthetic: 0
PFI Recovery: 0
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: abc
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 1
Daily Windows:
Sunday 22:00:00 --> Monday 07:00:00
Monday 22:00:00 --> Tuesday 07:00:00
Tuesday 22:00:00 --> Wednesday 07:00:00
Wednesday 22:00:00 --> Thursday 07:00:00
Thursday 22:00:00 --> Friday 07:00:00
Friday 22:00:00 --> Saturday 07:00:00
#########################################################
And output for "bpretlevel"
Retention Retention Equivalent
Level Period Days
--------- ----------- ----------
0 1 week 7
1 2 weeks 14
2 3 weeks 21
3 1 month 31
4 2 months 62
5 3 months 93
6 6 months 186
7 9 months 279
8 1 year 365
9 infinity
10 5 years 1825
11 infinity
12 infinity
13 35 days 35
14 infinity
15 infinity
16 infinity
17 infinity
18 infinity
19 infinity
20 infinity
21 infinity
22 infinity
23 infinity
24 infinity
Regards,
Arvind
Thanks & Best Regards,
Arvind Yadav.
Hi Andy, Yes, I
Hi Andy,
Yes, I am confirm the custom expiry level set for 3 for perticular policy.
We are using SLP and in SLP configuration we set level 3 retention.
No one has a access to that server except me so I know "bpexdate" command not executed manually.
Arvind
Thanks & Best Regards,
Arvind Yadav.
This will probably be correct
This will probably be correct then.
With SLP, when you make a backup copy, it gets the retention of infinity.
Only when the copy is made successfully does the backup copy revert to the value you have set.
This is normal behavior and is the whole point of SLP.
Martin
Best practice
Best practice guide
http://www.symantec.com/docs/TECH75047
White paper on SLP
https://www-secure.symantec.com/connect/sites/default/files/ent-whitepaper_veritas_netBackup_6.5_slp_nov_2007.pdf
TECH153154 Best practices for using Storage Lifecycle Policies and Auto Image Replication in NetBackup 7.1 is for 7.1 and 7.5.
Hi Andy, Sorry.... I
Hi Andy,
Sorry.... I understand what you want to ask.
We are using default 3 level expiry ratio in SLP setting.
Arvind
Thanks & Best Regards,
Arvind Yadav.
Arvind - Martin is
Arvind - Martin is correct.
Netbackup has a security feature when you use SLP. When a backup has been created the SLP will set a infinity retention. After the SLP has been processed the original expiration time will be applied. This is to ensure images are not expired prematurely. I find this behavior a little odd but that how it works.
Image this:
Backup to disk using SLP : retention level infinity (event thru you uses 3 week)
Stage to tape: Retention level 3 week (because SLP has finished processing).
Assumption is the mother of all mess ups.
If this post answered your'e qustion - Please mark as a soloution.
Thanks!!!!!
Thanks!!!!!
Thanks & Best Regards,
Arvind Yadav.
Thanks for provided
Thanks for provided solution!!!!
Thanks & Best Regards,
Arvind Yadav.
Would you like to reply?
Login or Register to post your comment.