Several retentions levels for the same client requires several policies
Updated: 04 Nov 2010 | 4 comments
If using NetBackup agents options and for the same client we have several schedules with different retention levels, NBU requires one policy for each retention level.
This could be avoid if variable with the name of the autimatic schedule was sent to the client, the same way the name of the policy is sent.
For example, in the Oracle agent, there is the variable ORA_SCHEDULE, but is blank. If this variable as the value of the automatic schedule that initiated the backup, in the client rman script we could then choose the value to the ORA_SCHED variable and then the correct application-schedule with the correct retention level will be used.
Idea Filed Under:
Comments
oh yes
Wanted this function since NBU 3.1.1
Assumption is the mother of all mess ups.
If this post solved you’re questions please send a gratitude by marking it as a solution.
The variable is NB_ORA_SCHED
The variable is NB_ORA_SCHED and declares which application schedule the oracle db should use.
You can use different app-schedules ( with different retentions) according to the backup type (Full, incremental) or with a little scripting you can set this value (every day full with 1 week retention, every week full backup with 1 month retention etc)
Also you could use different time window in order to use different schedules :
1. Daily schedule, 1 week retention, open window Mon-Fri 01:00-06:00
1. Weekly schedule, 1 month retention, open window Sat 01:00-06:00
With one policy, you have 2 schedules and different retentions.
Know all that
I know all the workarounds since I've worked with NBU from version 2, still in motif and only in Unix :-). But those aren't feasible in some enviroments. Guess we have to wait a little longer.
Hope, will see this
Hope, will see this implemented in the upcoming versions.
My Blogs : Handy BE Links
Would you like to reply?
Login or Register to post your comment.