ETERNUS SF Recovery Manager for Oracle EE 13.0.1 User's Guide - Solaris(TM) Operating System -
Contents PreviousNext

Chapter 3 BACKING UP DATABASE

This chapter explains the backup function of Recovery Manager for Oracle.

3.1 Overview 

Recovery Manager for Oracle provides the following backup functions:

3.1.1 Performing Online Backup

This section explains the procedure for online backup of the database.

The function backs up files online using the "/opt/FJSVrmfo/bin/rmfobackup" command.

The command is executed as root from the target database server.

  1. Specification

    # /opt/FJSVrmfo/bin/rmfobackup -b DB_NAME


  2. Options

    Option

    Explanation

    -b

    Execute the online backup operation


  3. Operands

    Operand

    Explanation

    DB_NAME

    Specify the database name to be backed up online


  4. Completion status

    = 0: Normal ending
    > 0: Abnormal ending

  5. Example of execution

    Example: Performs backup for "database name: orcl" online

    # /opt/FJSVrmfo/bin/rmfobackup -b orcl

3.1.2 Removing Expired Archived Log File

This section explains the procedure for removing archived redo log files no longer required.

The function removes the archived redo log files that have exceeded the number of days specified in the configuration (the number of backup generation managements (BK_GEN)) using the"/opt/FJSVrmfo/bin/rmfobackup" command.
The command is executed as root from the target database server.

Ensure this procedure is followed, as the next backup operation may end in error if archived redo log files are removed using the rm command.

  1. Specification

    # /opt/FJSVrmfo/bin/rmfobackup -a DB_NAME


  2. Options

    Option

    Explanation

    -a

    Remove expired archived redo log files


  3. Operands

    Operand

    Explanation

    DB_NAME

    Specify the name of the database where the expired archived redo log files are to be removed


  4. Completion status

    = 0: Normal ending
    > 0: Abnormal ending

  5. Example of execution

    Example: Remove the expired archived redo log files of "database name: orcl"

    # /opt/FJSVrmfo/bin/rmfobackup -a orcl

3.1.3 Waiting for Completion of the OPC Physical Copy

The function is configured to wait for completion of the OPC physical copy after executing the online backup operation when OPC has been selected as the data file backup method (BK_TYPE).

To wait for completion of the OPC physical copy, execute the " /opt/FJSVrmfo/bin/rmfobackup" command.

The command is executed as root from the target database server.

  1. Specification

    # /opt/FJSVrmfo/bin/rmfobackup -w DB_NAME


  2. Options

    Option

    Explanation

    -w

    Wait for completion of the OPC physical copy


  3. Operands

    Operand

    Explanation

    DB_NAME

    Specify the database name which will wait for completion of the OPC physical copy


  4. Completion status

    = 0: Normal ending
    > 0: Abnormal ending

  5. Example of execution

    Example: Waits for completion of the OPC physical copy of "database name: orcl"

    # /opt/FJSVrmfo/bin/rmfobackup -w orcl

3.2 Checking Status Backup Operation

Confirm from the following information that the backup command has completed.

3.2.1 Return Code of Backup Command

When the backup command ends normally, the return value will be 0.

An error has been generated when a value other than 0 is returned.

3.2.2 syslog

The following message is output to syslog if the online backup operation (rmfobackup -b) has ended in error.

Example: An online backup error message (rmfobackup -b)

Mar 22 11:22:59 rmfo200 FSP_RMGRFO_backup: [ID 702911 user.error] 'Abnormal End: 00074: The backup operation of the database (ora920) ended abnormally.'

The following warning message is output in the cluster operation (RAC) if some of the nodes have been terminated.

Note: If the user.warning message is inhibited in the syslog message processing, the warning message will not be output.

Example: Warning message output from the online backup operation (rmfobackup -b)

Mar 29 15:34:41 rac001 FSP_RMGRFO_backup: [ID 702911 user.warning] 'WARNING: The instance(rac002) is not activated. Continue the process.'

3.2.3 Execution Log file 

The function outputs detailed information to a log file at the time of backup command execution.

Log files are created under the "/opt/FJSVrmfo/log/backup/DB_NAME" directory.

The log file name is as follows:

bup1_YYYYMMDDHHMISS.log

Online backup execution log and execution log for waiting for completion OPC physical copy

bup2_YYYYMMDDHHMISS.log

execution log for removing the expired archived redo log files


YYYYMMDDHHMISS : Time of execution (year/month/day/hour/minute/second)

Refer to the log file if the backup command ended in error, remove the cause of the error, and re-execute the backup operation immediately.

Command execution log files that have exceeded the backup execution log storage period (LOG_GEN) are deleted at the time of backup operation.

3.3 Example of Backup Operation 

3.3.1 General Backup Operation 

This section explains general backup operations using Recover Manager for Oracle.

[Figure 3.3.1.1 Backup operation]

Perform the backup operation as follows:

  1. Perform online backup

    Backup online the target database disk to another disk, as directed in Performing Online Backup.

  2. Wait for completion of the OPC physical copy

    Execute as directed in Waiting for Completion of the OPC Physical Copy if the OPC backup method has been selected, and files are to be backed up to a tape, after completion of the OPC physical copy.

  3. Backup to a tape

    Recovery Manager for Oracle does not provide a function that backs up data to a tape.

    It is recommended that data stored on a backup volume be backed up to a tape using backup software.

    By backing up data to tapes, risks may be dispersed.

    To backup data in file system images from a server other than the target database server, always unmount the backup volume after completing the backup operation. If mounted in duplication, the file system will be destroyed.

    To backup to a tape from a server other than the target database server, backing up in raw images is recommended.

    The following volumes require tape backup:

    1. Data file (tablespace) backup
    2. Control file backup
    3. Archived redo log backup
    4. Recovery catalog database backup

    For details on these volumes, refer to the examples of disk resource arrangement in Disk Resources Allocation.

  4. Removing an expired archived redo log file

    After completing the tape backup, remove archived redo log files that have exceeded the number of generations being managed in the target database as directed in the section, Removing Expired Archived Log File

3.3.2 Example of Configuration File 

Examples of the Configuration file are shown below.:

3.3.2.1 Single Server Operation 

An example of a configuration file is below.:

Conditions:

  1. Basic information file (rmfo_system.ini)

    DB_NAME=orcl
    ORA_VL=1
    ORA_E=2
    ORACLE_HOME= /ora920/app/oracle/product/920
    CON_STR=orcl
    DB_TYPE=1
    NODE_CNT=1
    ORA_OWN=ora920
    ORA_GRP=dba
    HOST=dbsvr001
    ORACLE_SID=orcl


  2. sys password file (rmfo_syspw.ini)

    change_on_install


  3. Node list file (rmfo_node.ini)

    Not required

  4. Backup basic information file (rmfo_bkcom.ini)

    BK_TYPE=1
    DBF_TYPE=1
    BK_GEN=1
    LOG_GEN=7
    ALT_ROWS=100
    TRC_LVL=1


  5. Data file backup definition file (rmfo_bkdbf.ini)

    /orcl/bk_dbf1|/dev/dsk/c5t16d20s0|1|
    /orcl/bk_dbf2|/dev/dsk/c5t16d21s0|1|


  6. Control file backup definition file (rmfo_bkctl.ini)

    /orcl/bk_ctl|/dev/dsk/c5t16d22s0|1|


  7. Archived redo log information file (rmfo_arch.ini)

    Not required

  8. Archived redo log backup definition file (rmfo_bkarch.ini)

    |/orcl/bk_arch|/dev/dsk/c5t16d23s0|1|


  9. Recovery catalog database definition file (rmfo_catalog.ini)

    R_DB_NAME=r_orcl
    LSNR_NAME=LISTENER_R_ORCL
    PORT=1525
    R_TAR_MP=/orcl/r_orcl
    R_TAR_DEV=/dev/dsk/c5t16d24s0
    R_BK_TYPE=1
    R_BK_MP=NONE
    R_BK_DEV=/dev/dsk/c5t16d25s0

3.3.2.2 Cluster Operation (HA) 

An example of cluster operation (HA) is shown as follows:

Conditions:

  1. Basic information file (rmfo_system.ini)

    DB_NAME=ha10g
    ORA_VL=2
    ORA_E=2
    ORACLE_HOME=/ora101/app/oracle/product/10.1.0/db
    CON_STR=ha10g
    DB_TYPE=2
    NODE_CNT=2
    ORA_OWN=ora101
    ORA_GRP=dba
    HOST=dbvip
    ORACLE_SID=


  2. sys password file (rmfo_syspw.ini)

    change_on_install


  3. Node list file (rmfo_node.ini)

    hasvr001|ha10g|ha10g_app1|
    hasvr002|ha10g|ha10g_app1|


  4. Backup basic information file (rmfo_bkcom.ini)

    BK_TYPE=2
    DBF_TYPE=1
    BK_GEN=2
    LOG_GEN=7
    ALT_ROWS=100
    TRC_LVL=1


  5. Data file backup definition file (rmfo_bkdbf.ini)

    /ha10g/dbf1|/dev/sfdsk/ha10g/dsk/dbf1:c2t16d133|/dev/dsk/c2t16d172s0|/dev/dsk/c2t16d173s0||
    /ha10g/dbf2|/dev/sfdsk/ha10g/dsk/dbf2:c2t16d133|/dev/dsk/c2t16d172s1|/dev/dsk/c2t16d173s1||


  6. Control file backup definition file (rmfo_bkctl.ini)

    /ha10g_bk/ctl|/dev/dsk/c2t16d172s4|1|


  7. Archived redo log information file (rmfo_arch.ini)

    Not required

  8. Archived redo log backup definition file (rmfo_bkarch.ini)

    |/ha10g_bk/arch|/dev/dsk/c2t16d174s7|1|


  9. Recovery catalog database definition file (rmfo_catalog.ini)
    R_DB_NAME=r_ha10g
    LSNR_NAME=LISTENER_R_HA10G
    PORT=1526
    R_TAR_MP=/ha10g/r_ha10g
    R_TAR_DEV=/dev/dsk/c2t16d172s7
    R_BK_TYPE=2
    R_BK_MP=NONE
    R_BK_DEV=/dev/dsk/c2t16d173s7

3.3.2.3 Cluster Operation (RAC) 

An example of cluster operation (RAC) is shown as follows:

Conditions:

  1. Basic information file (rmfo_system.ini)

    DB_NAME=rmfo
    ORA_VL=2
    ORA_E=2
    ORACLE_HOME=/ora101/app/oracle/product/10.1.0/db
    CON_STR=rmfo
    DB_TYPE=3
    NODE_CNT=4
    ORA_OWN=ora101
    ORA_GRP=dba
    HOST=racvip
    ORACLE_SID=


  2. sys password file (rmfo_syspw.ini)

    change_on_install


  3. Node list file (rmfo_node.ini)

    rac001|rmfo01|app_rmfo01|
    rac002|rmfo02|app_rmfo02|
    rac003|rmfo03|app_rmfo03|
    rac004|rmfo04|app_rmfo04|


  4. Backup basic information file (rmfo_bkcom.ini)

    BK_TYPE=3
    DBF_TYPE=2
    BK_GEN=3
    LOG_GEN=7
    ALT_ROWS=100
    TRC_LVL=1


  5. Data file backup definition file (rmfo_bkdbf.ini)

    SYSTEM|/dev/sfdsk/rac10g/dsk/system:c3t16d3|/dev/dsk/c3t16d13s0|/dev/dsk/c3t16d15s0|/dev/dsk/c3t16d17s0|
    SYSAUX|/dev/sfdsk/rac01g/dsk/sysaux:c3t16d3|/dev/dsk/c3t16d13s1|/dev/dsk/c3t16d15s1|/dev/dsk/c3t16d17s1|
    UNDOTBS1|/dev/sfdsk/rac01g/dsk/undotbs01:c3t16d4|/dev/dsk/c3t16d13s3|/dev/dsk/c3t16d15s3|/dev/dsk/c3t16d17s3|
    UNDOTBS2|/dev/sfdsk/rac01g/dsk/undotbs02:c3t16d4|/dev/dsk/c3t16d13s4|/dev/dsk/c3t16d15s4|/dev/dsk/c3t16d17s4|
    UNDOTBS3|/dev/sfdsk/rac01g/dsk/undotbs03:c3t16d5|/dev/dsk/c3t16d13s5|/dev/dsk/c3t16d15s5|/dev/dsk/c3t16d17s5|
    UNDOTBS4|/dev/sfdsk/rac01g/dsk/undotbs04:c3t16d5|/dev/dsk/c3t16d13s6|/dev/dsk/c3t16d15s6|/dev/dsk/c3t16d17s6|
    USERS1|/dev/sfdsk/rac01g/dsk/users01:c3t16d6|/dev/dsk/c3t16d14s0|/dev/dsk/c3t16d16s0|/dev/dsk/c3t16d18s0|
    USERS2|/dev/sfdsk/rac01g/dsk/users02:c3t16d6|/dev/dsk/c3t16d14s1|/dev/dsk/c3t16d16s1|/dev/dsk/c3t16d18s1|
    USERS3|/dev/sfdsk/rac01g/dsk/users03:c3t16d7|/dev/dsk/c3t16d14s3|/dev/dsk/c3t16d16s3|/dev/dsk/c3t16d18s3|
    TOOLS|/dev/sfdsk/rac01g/dsk/tools:c3t16d7|/dev/dsk/c3t16d14s4|/dev/dsk/c3t16d16s4|/dev/dsk/c3t16d18s4|


  6. Control file backup definition file (rmfo_bkctl.ini)

    /rmfo_bk/ctl|/dev/dsk/c3t16d24s3|1|


  7. Archived redo log information file (rmfo_arch.ini)

    fjh001|/rac10g/arch1|/dev/sfdsk/rac10g/dsk/arch1|4|
    fjh002|/rac10g/arch2|/dev/sfdsk/rac10g/dsk/arch2|4|
    fjh003|/rac10g/arch3|/dev/sfdsk/rac10g/dsk/arch3|4|
    fjh004|/rac10g/arch4|/dev/sfdsk/rac10g/dsk/arch4|4|


  8. Archived redo log backup definition file (rmfo_bkarch.ini)

    rac001|/rmfo_bk/arch1|/dev/dsk/c3t16d19s0|1|
    rac002|/rmfo_bk/arch2|/dev/dsk/c3t16d19s1|1|
    rac003|/rmfo_bk/arch3|/dev/dsk/c3t16d20s0|1|
    rac004|/rmfo_bk/arch4|/dev/dsk/c3t16d20s1|1|


  9. Recovery catalog database definition file (rmfo_catalog.ini)

    R_DB_NAME=r_rac10g
    LSNR_NAME=listener_r_rac10g
    PORT=1531
    R_TAR_MP=/rac10g/r_rac10g
    R_TAR_DEV=/dev/dsk/c3t16d24s0
    R_BK_TYPE=2
    R_BK_MP=NONE
    R_BK_DEV=/dev/dsk/c3t16d25s0
Contents PreviousNext
All Rights Reserved, Copyright(C) FUJITSU LIMITED 2006