For offline database backup / restore, the operations and requirements are the same as File System Backup and Restore (You can use the ’Pre/Post’ function to Stop/Start Oracle Server before/after backup and restore.).

 

The following requirements must be met in order to perform online backup / restore of Oracle Database Servers.


 

General Requirements


  • The user who performs Oracle Backup / Restore should have knowledge about the Oracle database file structure and instance management.
  • The DB Administrator / Backup Operator must know the name of the Service when creating a new backup set. (You cannot browse the database(s) for names, therefore you must know the exact name in advance.)
  • The credentials used for backup / restore of the Oracle database must have the sysdba privilege.



DS-Client Computer Requirements


  • DS-Client must be running on a supported Linux platform listed in the Oracle Database Server Support Matrix.
  • Oracle Client must be installed on the machine running the DS-Client (this must be a full installation created from the Oracle Installer). It must be the same version as the Oracle Server to backup.
  • You must configure the ‘Net service Name’ for this Oracle Client to connect to each Oracle Server you want to backup or restore.
  • If the Oracle Instance is a shared server, set the Connection Type as "Dedicated Server" using Net Manager (Oracle 9).
  • Recovery Manager (RMAN) utility must be installed.
  • To backup / restore Oracle 9, you must manually copy recover.bsq to $ORACLE_HOME/rdbms/admin directory on DS-Client computer. Please see Oracle bug #2421470. You can find recover.bsq on the Oracle 9 Server.
  • The remote Oracle database server hostname must be configured in /etc/hosts file on the Linux DS-Client computer.



Oracle Server Requirements


  • Oracle Instance should be running in "ARCHIVELOG MODE" (this allows online backup of the database).
  • Set the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter to slightly longer than the period (in days) between backups of the whole Oracle database (all tablespaces, control files, and archive logs).
  • RMAN has a limitation of how many archived logs can be backed up at one time. Increase the "redo log file" size to reduce the number of archived logs.
  • Oracle Server should be a certified product. For example, Oracle 10.2 for Red Hat Enterprise Linux AS/ES 4, SuSE SLES 10, or Solaris 10 (64-bit).
  • To use DS-PIPE for backup and restore, a library file must be copied to $ORACLE_HOME/lib on the Oracle server. This file must correspond to the Oracle server’s platform. The files are found in the DS-Client installation directory in the sub-folder /Misc/Oracle_Classical_Library:


libobk.so     [for Linux 32-bit Oracle database]

Copy to $ORACLE_HOME/lib on 32-bit Linux Oracle Server.


libobk-64.so  [for Linux 64-bit Oracle database]

Copy to $ORACLE_HOME/lib on 64-bit Linux Oracle Server and make a soft link "ln -s libobk-64.so libobk.so".

 

libobk.a      [for AIX Oracle database]

Copy to $ORACLE_HOME/lib on AIX Oracle server.


libobk_ia64.sl [for HPUX Itanium oracle database]

Copy to $ORACLE_HOME/lib on HPUX Itanium Oracle Server and make a soft link "ln -s libobk_ia64.sl libobk.so"


libsbt64.so   [for Solaris 64-bit Oracle database]

Copy to $ORACLE_HOME/lib on Solaris 64-bit Oracle server and make a soft link "ln -s libsbt64.so libobk.so".


libsbt32.so   [for Solaris 32-bit Oracle database]

Copy to $ORACLE_HOME/lib on Solaris 32-bit Oracle server and make a soft link "ln -s libsbt32.so libobk.so".



Backup Requirements


  • The Oracle database should be in Open state when you perform the online backup.
  • In order to perform full or alternate restore of an Oracle database, the backup must be a full Oracle database backup (all tablespaces, archived log files, and control file). In addition, you must have a backup of the password file and the init file.
  • The init file (e.g. admin/<instance>/pfile/init<instance>.ora) and password file (e.g. $ORACLE_HOME/dbs/orapw<instance>) should be backed up in a File System backup set. A backup of the password file is necessary for any full or alternate restore of the Oracle database.
  • You do not need to place online tablespaces in backup mode when performing backups.
  • For Oracle backup using NFS protocol, you must supply the user account of ’root’ for the network credentials.



Restore Requirements


There are the following requirements and limitations:

  • To restore the Control File, you must start the database in nomount (started) state.
  • To restore Tablespaces without the Control File, you must start the database in mount state. Otherwise, you must change the tablespaces offline.
  • Tablespaces can be restored, however the logs will be applied to the present (unless DBPITR is performed). This means they will not be "as when backed up".
  • The control file should only be restored when performing DBPITR (Database Point In Time Recovery). After restoring, the database will be opened with the "RESETLOGS" option. By doing this, you will not be able to restore any tablespaces backed up after that point in time (unless you restore the control file).
  • When performing a DBPITR, all the files backed up in that particular session must be restored.
  • For full restore to the original location, the requirements are the same as for Alternate Location Restore, except the ‘target computer’ is the original computer.
  • [Oracle 10g only] Before performing a DBPITR, if the backup and flash_recovery_area have different reset log times, you must rename the flash_recovery_area directory. After performing the restore, you must shutdown and manually restart the Oracle database (see Oracle Note: 286964.1).



Alternate Location Restore Requirements


The Oracle Server (target restore server) must satisfy the requirements listed in the sections above.

 

In addition, the following apply for Alternate Restore:

  1. The backup must be a full Oracle database backup. You must also have a backup of the password file and the init file (this will be in a File System backup set).
  2. The target restore computer must have an Oracle database service Instance of the same name.
    This is to simplify the process of recovery. You must modify the initial file manually if you use a different Instance name.
  3. The target restore computer must have the same tablespace path as the original backup (this can be created when setting up the database).
    This is because of Oracle limitations and specifications. All information about file structure is recorded in the Control File and the Oracle Database as a whole.
  4. Restore the (File System) backup of the password file and the init file to the alternate computer. This is a separate backup set of the password file and the init file from the original backup computer.
  5. Restore the full Oracle database backup.
  6. If you choose a different dump path, only dump files are restored to that path. You must use RMAN to restore your Oracle database manually.