Hi Richard
I think you need to make multiple Default-Policies with different retentions
and then in the script set the NB_ORA_SCHED parameter. I am not sure is this
the exact name for RMAN, I have only used it with EBU
Regards
Michael
NBUSCRIPTS
http:/mian.homepage.dk
-----Oprindelig meddelelse-----
Fra: Richard Bannister @ Northampton <rbannister AT vartec DOT net>
Til: 'veritas-bu AT mailman.eng.auburn DOT edu' <veritas-bu AT
mailman.eng.auburn DOT edu>
Cc: Richard Bannister @ Northampton <rbannister AT vartec DOT net>
Dato: 26. juni 2002 10:39
Emne: [Veritas-bu] NetBackup - Multiple Policies within a single Backup Class..
>
>I want multiple Backup Policies in a single class - using only 1 input
>script (i use RMAN to backup databases, these are regularly restore to
>different machines).
>I no that al lthe suggested workarounds are based around having multiple
>input scripts, but as we restore very frequently, the danger of restoring to
>wrong place is not worth the hassle.
>I find multiple Netbackup classes/schedules easier to manage, but cannot see
>ehy NetBackup is so bad at dealing with Backup Policies/params passed to it
>from scripts...
>
>This is why i want different policies within the same classes -
>
>Monday thru Friday - weekly retention - stay onsite
>Saturday - weekly retention to different pool - for offsiting
>Sunday - monthly retention to different pool - for offsiting
>
>------------------------------------------------------------
>
>Well, i tested this over the weekend, and - it doesn't work properly. I
>basically changed my backup class to include 3 backup policies, with
>associated automatic schedules.
>All i want to do is have the backup run monday thru friday - with a weekly
>retention; then on a saturday - weekly retention, but different pool for
>offsiting; on sunday - monthly retention, again for offsiting - Should be
>easy with Netbackup - after all, scheduling should be a major feature for a
>backup product.
>
>------------------------------------------------------------
>
>Here's the output from 'bpsched -predict', which i long ago found to be a
>tad unreliable --->
>
>
># bpsched -predict 06/21/2002 03:00:00 | grep _e450 | grep PR
>0 vtnthe450 CL_PRODDB_D_e450 DailyFull FULL Friday 03:00:00
>
># bpsched -predict 06/22/2002 03:00:00 | grep _e450 | grep PR
>0 vtnthe450 CL_PRODDB_D_e450 WeeklyFull FULL Saturday 03:00:00
>
># bpsched -predict 06/23/2002 03:00:00 | grep _e450 | grep PR
>3 vtnthe450 CL_PRODDB_D_e450 MonthlyFull FULL Sunday 03:00:00
>
># bpsched -predict 06/24/2002 03:00:00 | grep _e450 | grep PR
>0 vtnthe450 CL_PRODDB_D_e450 DailyFull FULL Monday 03:00:00
>------------------------------------------------------------
>
>And the proof of the pudding is here -->
>See that Saturday onwards keeps using the Weekly schedule.
>
>
>MONDAY 06/24/2002 03:00:00
>
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/24/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/24/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/24/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/24/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/24/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/24/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/24/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/24/2002
>CL_PRODDB_D_e450 DailyFull 06/24/2002
>
>SUNDAY 06/23/2002 03:00:00
>
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/23/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/23/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/23/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/23/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/23/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/23/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/23/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/23/2002
>CL_PRODDB_D_e450 MonthlyFull 06/23/2002
>
>SATURDAY 06/22/2002 03:00:00
>
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/22/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/22/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/22/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/22/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/22/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/22/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/22/2002
>CL_PRODDB_D_e450 SCH_PRODDB_W 06/22/2002
>CL_PRODDB_D_e450 WeeklyFull 06/22/2002
>
>FRIDAY 06/21/2002 03:00:00
>
>CL_PRODDB_D_e450 SCH_PRODDB 06/21/2002
>CL_PRODDB_D_e450 SCH_PRODDB 06/21/2002
>CL_PRODDB_D_e450 SCH_PRODDB 06/21/2002
>CL_PRODDB_D_e450 SCH_PRODDB 06/21/2002
>CL_PRODDB_D_e450 SCH_PRODDB 06/21/2002
>CL_PRODDB_D_e450 SCH_PRODDB 06/21/2002
>CL_PRODDB_D_e450 SCH_PRODDB 06/21/2002
>CL_PRODDB_D_e450 SCH_PRODDB 06/21/2002
>CL_PRODDB_D_e450 DailyFull 06/21/2002
>
>NOW - the only thing that 'MIGHT' be wrong here - maybe each backup policy
>only NEEDS to specify the actual days that are required. I know that a
>policy has to have 24 hours (00:00:00 thru 24:00:00 set, but am not sure
>whether this should be for a whole week, or JUST the days in question)....
>I've amended policies to omit the days not needed, but have to wait 'til the
>weekend to try it out..
>
>Regards
>
>Richard Bannister
>Unix Systems Administrator
>Vartec Telecom Europe
>
>_______________________________________________
>Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
|
