Forum Discussion

sivachandraredd's avatar
12 years ago

schedule volume pool does not override the policy volume pool(Data Store)

Hi All,

I have created oracle policy with following,

Policy attributes:

 

-bash-3.2# bpplinfo DB_RMAN_01
Policy Type:            Oracle
Active:                 yes
Effective:              07/16/2012 12:21:41
Follow NFS Mounts:      no
Cross Mount Points:     no
Client Compress:        yes
Collect TIR info:       no
Policy Priority:        0
Ext Security Info:      no
File Restore Raw:       no
Client Encrypt:         no
Residence:              xxxxxxxxxx01_nb-hcart-robot-tld-0
Volume Pool:            DataStore
Server Group:           *ANY*
Data Classification:            -
Residence is storage lifecycle policy:  no
Granular Restore:       no
Ignore Client Direct:   no
Use Accelerator:        no
Enable Metadata Indexing:       no
Application Discovery:  no
Discovery Lifetime:     0 seconds
ASC Application and attributes: (none defined)
Segmentation Fault (core dumped)
 
-bash-3.2# bpplsched DB_RMAN_01
 
Schedule:              RMAN_DB01_MONTHLY
  Type:                Automatic Full Backup
  Calendar sched: Enabled
    Sunday, Week 4
  Retention Level:     8 (7 years)
  Maximum MPX:         8
  PFI Recovery:        0
  Schedule indexing:  0
  Number Copies:       1
  Fail on Error:       0
  Residence:           xxxxxxxxxx01_nb-hcart-robot-tld-0
  Volume Pool:         DB_MONTHLY
  Server Group:        *ANY*
  Residence is Storage Lifecycle Policy:         0
  Daily Windows:
        Sunday     00:02:00  -->  Sunday     04:02:00
 
 
   here one problem i am facing
In policy attributes volume pool i mensioned as Data store,
But Schedule level override volume pool i mensioned as DB_Monthly,
 
Backup  Data does not go to DB_MONTHLY volume pool it was go to Datastore volume pool.
 
could you please help me....it's urgent..
 
 
 Thanks,
Sivachandra
 
 

 

  • The application backup schedule determines both the retention and the volume pool used

    I would suggest using Daily, Weekly and Monthly policies and set your volume pool and retention period on the application backup schedule and not the automatic schedule

    This is due to the fact that you automatic schedule kiskc off what is effectively a user backup which then uses the application schedule to determine everything else

    This crops up a lot with SQL backups which also need a policy for each retention period

    Hope this helps

6 Replies

  • The volume pool DataStore is not normal used for backup, since it's reserved by Netbackup. Try change the volume pool in the policy to "NetBackup" and re-try the operation.

    http://www.symantec.com/docs/HOWTO32903

  • If you want to use different Automatic schedules, that result in backups to different TU/Pool/Retention, then the backup script will need to use some logic to determine which Automatic schedule caused the script to run and then specify the correct Application schedule. Something like this;

    if [ "$NB_ORA_PC_SCHED" = "Auto-1" ]; then
    USE_SCHED="App-1"
    elif [ "$NB_ORA_PC_SCHED" = "Auto-2" ]; then
    USE_SCHED="App-2"

    ...continue as needed...

    fi

    Then have RMAN send the desired schedule name after allocating the channels and before the backup command.

    RMAN_CMDS="

    ...snip...

    ALLOCATE .... ;
    SEND 'NB_ORA_SCHED=$USE_SCHED';
    BACKUP ... ;
    "

    You can setup a policy for each type of application schedule you want to use, each with its own volume pool and retention. Each policy could then call its own RMAN script where the policy is set via a send command in RMAN.

    When the automatic schedule runs the RMAN script on the client, it does pass certain variables, such as the automatic schedule name (NB_ORA_PC_SCHED) and the automatic schedule type (0 or 1 settings for NB_ORA_FULL, NB_ORA_INCR, and NB_ORA_CINC). You can see how our example script uses the schedule type setting to determine what kind of Oracle backup to run.


    Here is an example of how to use NB_ORA_PC_SCHED to determine which automatic schedule is running the RMAN script, and then set which application schedule to use for the backup, which in turn can be passed via the send command in RMAN:

    if [ "$NB_ORA_FULL" = "1" ]
    then
    BACKUP_TYPE="INCREMENTAL LEVEL=0"
    if [ "$NB_ORA_PC_SCHED" = "Weekly" ]
    then
    echo "Weekly full backup requested" >> $RMAN_LOG_FILE
    SCHEDULE="Application_Backup_Weekly"
    elif [ "$NB_ORA_PC_SCHED" = "MonthEnd" ]
    then
    echo "Month-end full backup requested" >> $RMAN_LOG_FILE
    SCHEDULE="Application_Backup_MonthEnd"
    else
    echo "Full backup requested" >> $RMAN_LOG_FILE
    SCHEDULE="Application_Backup_Daily"
    fi
    elif [ "$NB_ORA_INCR" = "1" ]

     

    ...
    Keep in mind that this is just an example of what you could do. This example being provided is informational only, and not being provided as a solution.

    REFERENCE: http://www.symantec.com/docs/TECH160105

  • The application backup schedule determines both the retention and the volume pool used

    I would suggest using Daily, Weekly and Monthly policies and set your volume pool and retention period on the application backup schedule and not the automatic schedule

    This is due to the fact that you automatic schedule kiskc off what is effectively a user backup which then uses the application schedule to determine everything else

    This crops up a lot with SQL backups which also need a policy for each retention period

    Hope this helps

  • Hi All,

    Thanks for your quick reply.

    I have changed Data store Volume pool to Netbackup volume pool in policy attributes.

    But data goes to Netbackup pool volumes, It was not go to the Schedules Volume pool (DB_Monthly).

     

    Thanks ,

    Sivachandra

  • Good - We now know the behavior isn't related to the reserved DataStore pool.

    Does the Oracle backup use RMAN_DB01_MONTHLY ?. Check in the activity monitor - make a screen dump and attach it to a post. Remember a Oracle job will have one control job and one data transferring job. It's the last one that need to use schedule RMAN_DB01_MONTHLY.

    By the way - Netbackup work better if you use one volume pool for all backup. There is no gain in use different volume pools for each retention. 

    Let's assume you have backup A that go into V_volumepool and backup B_volumepool. Then you need at least two tape drives for concurrent backups. If all backup could go into the same volume pool both backup would execute at the same time. Now multiply with a factor 10 ......

  • Please have another look at Mark's post:

    The application backup schedule determines both the retention and the volume pool used

    This schedule is used for scheduling only:
    Schedule:              RMAN_DB01_MONTHLY
      Type:                Automatic Full Backup

     

     
    So, you need to override the pool in Default-Application-Backup schedule.