This is what i originally posted on Veritas NetBackup Newsgroup ...
- to put it simply - i want multiple Backup Policies in a single class - should be simple
- the intention is -->
Monday thru Friday - weekly retention - stay onsite
Saturday - weekly retention to different pool - for offsiting
Sunday - monthly retention to different pool - for offsiting
Previous post follows ------->
Regards
Richard Bannister
Unix Systems Administrator
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. Anyway i digress.....
I guess the tapes for all these backups are in the bloody wrong pools now also..
Here is the setup of the backup class --> (looks fine to me thus far)..
------------------------------------------------------------
Class Name: CL_PRODDB_D_e450
Class Type: Oracle
Active: yes
Mult. Data Streams: no
Client Encrypt: no
Class Priority: 2
Max Jobs/Class: 99
Disaster Recovery: 0
Residence: (specific storage unit not required)
Volume Pool: PRODDB_Daily
Keyword: (none specified)
HW/OS/Client: Solaris Solaris8 vtnthe450
Include: /home/oracle/rman-netbackup0.sh
Schedule: MonthlyFull
Type: Automatic Full Backup
Frequency: every 1 day
Maximum MPX: 1
Retention Level: 3 (1 month)
Residence: (specific storage unit not required)
Volume Pool: PRODDB_Monthly
Daily Windows:
Sunday 03:00:00 --> Sunday 13:00:00
Schedule: WeeklyFull
Type: Automatic Full Backup
Frequency: every 1 day
Maximum MPX: 1
Retention Level: 0 (1 week)
Residence: (specific storage unit not required)
Volume Pool: PRODDB_Weekly
Daily Windows:
Saturday 03:00:00 --> Saturday 13:00:00
Schedule: DailyFull
Type: Automatic Full Backup
Frequency: every 1 day
Maximum MPX: 1
Retention Level: 0 (1 week)
Residence: (specific storage unit not required)
Volume Pool: (same as class volume pool)
Daily Windows:
Monday 03:00:00 --> Monday 13:00:00
Tuesday 03:00:00 --> Tuesday 13:00:00
Wednesday 03:00:00 --> Wednesday 13:00:00
Thursday 03:00:00 --> Thursday 13:00:00
Friday 03:00:00 --> Friday 13:00:00
Schedule: SCH_PRODDB_W
Type: Backup Policy
Maximum MPX: 1
Retention Level: 0 (1 week)
Residence: (specific storage unit not required)
Volume Pool: PRODDB_Weekly
Daily Windows:
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 00:00:00 --> Friday 24:00:00
Saturday 00:00:00 --> Saturday 24:00:00
Schedule: SCH_PRODDB_M
Type: Backup Policy
Maximum MPX: 1
Retention Level: 0 (1 week)
Residence: (specific storage unit not required)
Volume Pool: PRODDB_Monthly
Daily Windows:
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 00:00:00 --> Friday 24:00:00
Saturday 00:00:00 --> Saturday 24:00:00
Schedule: SCH_PRODDB
Type: Backup Policy
Maximum MPX: 1
Retention Level: 0 (1 week)
Residence: (specific storage unit not required)
Volume Pool: (same as class volume pool)
Daily Windows:
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 00:00:00 --> Friday 24:00:00
Saturday 00:00:00 --> Saturday 24:00:00
------------------------------------------------------------
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 -->
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 where this should be for a whole week, or JUST the days in question)....
Someone please advise, i will amend the policies, but now have to wait 'til the weekend to try again..
Frustrated..
"Creaky" <rbannister@vartec.net> wrote:
>
>Hi guys, i'd be very interested to see the output of this particular class
>combo - ie can you do a bpcllist -U or whatever and cut/paste the setup
>of this class - tho i think i understand exactly how you have achieved this.
>I'm going to experiment with a test class over the weekend...
>
>Regards
>Rich
>
>
>"Wong" <goodfriday@yahoo.com> wrote:
>>
>>Hi Morgan,
>>
>>Thanks for sharing your experiences with us.
>>
>>If that is the case, how can we specify which Default policy will be used
>>by which Automatic Backup policy. Any others setting require ?
>>
>>Rdgs,
>>"C.J. Morgan" <cj.morgan@fedex.com> wrote:
>>>
>>>"wong" <goodfriday@yahoo.com> wrote:
>>>>
>>>>Thanks. I thinks this is the only solution (2 different class )right now.
>>>
>>>I have a similiar setup for my sql backups which use the Automatic backup/Default
>>>Policy combo. I have daily backups of my sql databases which I only retain
>>>for 2 weeks, then on Fridays I do a backup which is retained for 2 months.
>>> These are in the same class, but I have an Automatic Backup (called Full_2_week)
>>>which the retention is set for 2 weeks, and a matching default policy (renamed:
>>> Default-Policy_2_week) which also has a retention of 2 weeks. Then I
>created
>>>a set of Automatic backup/default policy for the 2 month retentions. The
>>>Automatic backup is what drives the actual schedule, and I have yet to
>have
>>>an issue of these running in the same class. We are using Datacenter 3.4.2
>>
>
- to put it simply - i want multiple Backup Policies in a single class - should be simple
- the intention is -->
Monday thru Friday - weekly retention - stay onsite
Saturday - weekly retention to different pool - for offsiting
Sunday - monthly retention to different pool - for offsiting
Previous post follows ------->
Regards
Richard Bannister
Unix Systems Administrator
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. Anyway i digress.....
I guess the tapes for all these backups are in the bloody wrong pools now also..
Here is the setup of the backup class --> (looks fine to me thus far)..
------------------------------------------------------------
Class Name: CL_PRODDB_D_e450
Class Type: Oracle
Active: yes
Mult. Data Streams: no
Client Encrypt: no
Class Priority: 2
Max Jobs/Class: 99
Disaster Recovery: 0
Residence: (specific storage unit not required)
Volume Pool: PRODDB_Daily
Keyword: (none specified)
HW/OS/Client: Solaris Solaris8 vtnthe450
Include: /home/oracle/rman-netbackup0.sh
Schedule: MonthlyFull
Type: Automatic Full Backup
Frequency: every 1 day
Maximum MPX: 1
Retention Level: 3 (1 month)
Residence: (specific storage unit not required)
Volume Pool: PRODDB_Monthly
Daily Windows:
Sunday 03:00:00 --> Sunday 13:00:00
Schedule: WeeklyFull
Type: Automatic Full Backup
Frequency: every 1 day
Maximum MPX: 1
Retention Level: 0 (1 week)
Residence: (specific storage unit not required)
Volume Pool: PRODDB_Weekly
Daily Windows:
Saturday 03:00:00 --> Saturday 13:00:00
Schedule: DailyFull
Type: Automatic Full Backup
Frequency: every 1 day
Maximum MPX: 1
Retention Level: 0 (1 week)
Residence: (specific storage unit not required)
Volume Pool: (same as class volume pool)
Daily Windows:
Monday 03:00:00 --> Monday 13:00:00
Tuesday 03:00:00 --> Tuesday 13:00:00
Wednesday 03:00:00 --> Wednesday 13:00:00
Thursday 03:00:00 --> Thursday 13:00:00
Friday 03:00:00 --> Friday 13:00:00
Schedule: SCH_PRODDB_W
Type: Backup Policy
Maximum MPX: 1
Retention Level: 0 (1 week)
Residence: (specific storage unit not required)
Volume Pool: PRODDB_Weekly
Daily Windows:
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 00:00:00 --> Friday 24:00:00
Saturday 00:00:00 --> Saturday 24:00:00
Schedule: SCH_PRODDB_M
Type: Backup Policy
Maximum MPX: 1
Retention Level: 0 (1 week)
Residence: (specific storage unit not required)
Volume Pool: PRODDB_Monthly
Daily Windows:
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 00:00:00 --> Friday 24:00:00
Saturday 00:00:00 --> Saturday 24:00:00
Schedule: SCH_PRODDB
Type: Backup Policy
Maximum MPX: 1
Retention Level: 0 (1 week)
Residence: (specific storage unit not required)
Volume Pool: (same as class volume pool)
Daily Windows:
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 00:00:00 --> Friday 24:00:00
Saturday 00:00:00 --> Saturday 24:00:00
------------------------------------------------------------
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 -->
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 where this should be for a whole week, or JUST the days in question)....
Someone please advise, i will amend the policies, but now have to wait 'til the weekend to try again..
Frustrated..
"Creaky" <rbannister@vartec.net> wrote:
>
>Hi guys, i'd be very interested to see the output of this particular class
>combo - ie can you do a bpcllist -U or whatever and cut/paste the setup
>of this class - tho i think i understand exactly how you have achieved this.
>I'm going to experiment with a test class over the weekend...
>
>Regards
>Rich
>
>
>"Wong" <goodfriday@yahoo.com> wrote:
>>
>>Hi Morgan,
>>
>>Thanks for sharing your experiences with us.
>>
>>If that is the case, how can we specify which Default policy will be used
>>by which Automatic Backup policy. Any others setting require ?
>>
>>Rdgs,
>>"C.J. Morgan" <cj.morgan@fedex.com> wrote:
>>>
>>>"wong" <goodfriday@yahoo.com> wrote:
>>>>
>>>>Thanks. I thinks this is the only solution (2 different class )right now.
>>>
>>>I have a similiar setup for my sql backups which use the Automatic backup/Default
>>>Policy combo. I have daily backups of my sql databases which I only retain
>>>for 2 weeks, then on Fridays I do a backup which is retained for 2 months.
>>> These are in the same class, but I have an Automatic Backup (called Full_2_week)
>>>which the retention is set for 2 weeks, and a matching default policy (renamed:
>>> Default-Policy_2_week) which also has a retention of 2 weeks. Then I
>created
>>>a set of Automatic backup/default policy for the 2 month retentions. The
>>>Automatic backup is what drives the actual schedule, and I have yet to
>have
>>>an issue of these running in the same class. We are using Datacenter 3.4.2
>>
>