Schedule for oracle job

[Ahmed_ELHalwagy]

my case is

i have a an oracledatabase and i am using daily schedule with backup and i am trying to take each daily backup on sparate tape

the scenario is

• creating 7 pool for the seven days of the week
• assign one tape for eah pool
• creating 7 seven schedule and in each schdule i assigned the desired pool according to the day

all of that on one policy :

the default pool of the policy is for example is (ERP) and the default application backup schedule pool is (ERP)

when i run the backup it used only the time of the schedule but use the pool of the application backup schedule

why it didn't use the pool i assigned in each schedule and how can i make this scenario in one policy

[mrinal_sarkar62]

Hi,

First of all...please provide the NBU details ..Platform details and the Oracle details(version, OS,, etc)..

Is that error says that it is looking for next tape nad error code 96..then...

As u have scheduled each Vol pool for each backup.for and the image is expire in week(default)..I guess the images were not getting expeired as it should be...

Use a customized expire in days...e.g. use 5 days to expire the images in the tapes...

Also u can expire the tape manually using ..

bpexpdate -m mediaID -d 0

Thanks.

[Marianne]

Please post your policy config : bppllist <policy-name> -U
as well as the script used for backup.

If you want to micro-manage to this extent, you might have to modify your script to specify different NB_ORA_SCHED for each day. If this variable is NOT set in the script, NBU will 'grab' the first available Default Application Schedule in an Oracle policy for this client... Or different scripts and policies for each day...

The other option is to either suspend the media used at the end of the backup or eject from the robot on a daily basis.

[Nicolai]

Netbackup isn't really built for this kind of "super tape control". Are you sure you wan't to do all that manual work ?. Is it a business requirement ?

You can to some extend archive what you wan't if each day schedule overwrite the volume volume pool. But after a week Netbackup will re-use the partial full tapes in the volume pool unless you eject the tape from the robot.

[Ahmed_ELHalwagy]

[Ahmed_ELHalwagy]

each daily schedule uses different volume pool

[Marianne]

ANOTHER request for the following info (a screenshot does not display all details):

Please post your policy config  (run this command from cmd on the master, command is in .../netbackup/bin/admincmd) : bppllist <policy-name> -U
as well as the script used for backup.

[Ahmed_ELHalwagy]

------------------------------------------------------------

Policy Name:       oracletkt

  Policy Type:         Oracle
  Active:              no
  Effective date:      08/01/2011 04:30:00
  Block Incremental:   no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           enr-synb-01-hcart-robot-tld-2
  Volume Pool:         ERP
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no

Granular Restore Info:  no
Ignore Client Direct:  no
  HW/OS/Client:  HP-UX-IA64    HP-UX11.31    db1vip

  Include:  oracletkttmp.tpl

  Schedule:          Default-Application-Backup
    Type:            Application Backup
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 3 (1 month)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    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:          Ticketing_Fri
    Type:            Automatic Full Backup
    Frequency:       every 1 day
    Maximum MPX:     25
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 0 (1 week)
    Number Copies:   1
    Fail on Error:   0
    Residence:       enr-synb-01-hcart-robot-tld-2
    Volume Pool:     Ticketing_Fri
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Friday     04:30:00  -->  Friday     07:30:00

  Schedule:          Ticketing_Mon
    Type:            Automatic Full Backup
    Frequency:       every 1 day
    Maximum MPX:     25
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 0 (1 week)
    Number Copies:   1
    Fail on Error:   0
    Residence:       enr-synb-01-hcart-robot-tld-2
    Volume Pool:     Ticketing_Mon
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Monday     04:30:00  -->  Monday     07:30:00

  Schedule:          Ticketing_Sat
    Type:            Automatic Full Backup
    Frequency:       every 1 day
    Maximum MPX:     25
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 0 (1 week)
    Number Copies:   1
    Fail on Error:   0
    Residence:       enr-synb-01-hcart-robot-tld-2
    Volume Pool:     Ticketing_Sat
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Saturday   04:30:00  -->  Saturday   07:30:00

  Schedule:          Ticketing_Sun
    Type:            Automatic Full Backup
    Frequency:       every 1 day
    Maximum MPX:     25
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 0 (1 week)
    Number Copies:   1
    Fail on Error:   0
    Residence:       enr-synb-01-hcart-robot-tld-2
    Volume Pool:     Ticketing_Sun
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Sunday     04:30:00  -->  Sunday     07:30:00

  Schedule:          Ticketing_Thu
    Type:            Automatic Full Backup
    Frequency:       every 1 day
    Maximum MPX:     25
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 0 (1 week)
    Number Copies:   1
    Fail on Error:   0
    Residence:       enr-synb-01-hcart-robot-tld-2
    Volume Pool:     Ticketing_Thu
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Thursday   04:30:00  -->  Thursday   07:30:00

  Schedule:          Ticketing_Tue
    Type:            Automatic Full Backup
    Frequency:       every 1 day
    Maximum MPX:     25
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 0 (1 week)
    Number Copies:   1
    Fail on Error:   0
    Residence:       enr-synb-01-hcart-robot-tld-2
    Volume Pool:     Ticketing_Tue
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Tuesday    04:30:00  -->  Tuesday    07:30:00

  Schedule:          Ticketing_Wen
    Type:            Automatic Full Backup
    Frequency:       every 1 day
    Maximum MPX:     25
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 0 (1 week)
    Number Copies:   1
    Fail on Error:   0
    Residence:       enr-synb-01-hcart-robot-tld-2
    Volume Pool:     Ticketing_Wen
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Wednesday  04:30:00  -->  Wednesday  07:30:00

[Marianne]

The actual schedule that is used for the Oracle backup is the Default-Application-Backup.

The automatic schedules only determines when they must be kicked off.

Schedule:          Default-Application-Backup
Type:                 Application Backup
.......
Residence:       (specific storage unit not required)
Volume Pool:   (same as policy volume pool)

The Volume Pool specified in Policy attributes:
Volume Pool:         ERP

This means that all backups in this policy will be sent to volume pool ERP.

Please see advice given by myself and Nicolai in our previous posts.....