Backup / Restore of Oracle Database Servers
Creation Date: March 12, 2003
Revision Date: December 01, 2015
Product: DS‑Client
Oracle Backup Set Overview
This following summarizes the DS-Client capabilities to back up and restore online Oracle databases.
Functionality |
On a scheduled or an on-demand basis, the DS-Client will instruct the Oracle’s Recovery Manager (RMAN) to access the Oracle Server via IP (LAN, WAN, etc) and use the Oracle-supplied functions to perform a database backup (through Pipe or using dump files). The data is then compressed, encrypted and transmitted to the DS-System. The first time this action is performed, the entire database is dumped and transmitted (creating a “master”). During subsequent backups, only the changes are transmitted (creating a “delta”). DS-Client never accesses the Oracle database data files directly and therefore, there is never an issue with open and locked database files. The database does NOT have to be taken off-line to perform the backup. |
Security |
During the Oracle server backup (as with all backups), the database credentials (sysdba username and password) are entered and stored in the DS-Client database, using AES128 encryption. The backup data is encrypted with a security algorithm that is secure up to AES-256 (256-bit) with a private key known only by you (the customer). Your service provider will never have access to this information. The DS-System uses a one-way hash to validate encryption keys, however the hash cannot be used to recover the encryption keys. |
Items available for backup/restore |
• individual tablespaces • control file • archived logs | Whole database backup: • Backup all items (individual tablespaces, control file, and archived logs) in one oracle database backup set. • Create a File system backup set to back up only init<sid>.ora and pwd<sid>.ora. |
Options for backup |
• Logical Corruption Check • Backup Only Current Archived Logs • Truncate Transaction Logs |
Possible items to restore |
Original restore (restore to the original Oracle server) | Alternate restore (restore to another Oracle server) |
• individual tablespaces • control file + tablespaces + archived logs • Whole database (including files init.ora & pwd.ora) | • All possible options in Original restore • Restore only the dump files |
Options for restore |
• Restore only dump files • Create temp tablespace |
NOTE: You must install the full Oracle client on the DS-Client that performs backup / restore of the target Oracle Express server. Do not install the Oracle Express client on the DS-Client.
Backup / Restore of Oracle Database Servers using Windows DS-Client
For off-line 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. (If your database is in NOARCHIVE mode, then you must perform off-line backup of the database.)
The following requirements must be met 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. • You can not use an IP address to specify a computer for backup / restore. Only the computer name is allowed. |
DS-Client Computer Requirements |
• Oracle Client must be installed. It must be the same version as the Oracle Server you want to backup. If you want to backup different versions of Oracle servers, you must install each corresponding version of Oracle client on the DS-Client computer. • 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. This is the TNS alias that is specified in the “tnsnames.ora” file on your Oracle client. • For Oracle 12c, you must configure a separate ‘Net service Name’ to access the Oracle Server at CDB-level or PDB-level. CDB-level will give access to the entire container database (Root and all pluggable databases). PDB-level will give access to only the specific pluggable database named. • Recovery Manager (RMAN) utility must be installed. |
Oracle Server Requirements |
• [32-Bit Windows Platforms] orasbt.dll must be copied to the target Oracle Server's computer. Place it in the path \%SYSTEMROOT%\SYSTEM32 (System Root path). You can find this file in the DS-Client installation directory. • [64-Bit Windows Platforms] orasbt_x64.dll must be copied to the target Oracle Server's computer. Rename it to orasbt.dll, then place it in the path \%SYSTEMROOT%\SYSTEM32 (System Root path). You can find this file in the DS-Client installation directory. • Oracle Instance must 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. • If you are using DS-Client Buffer or DS-Client Pipe as the dump path for backup, make sure both the "OracleServiceXXXX" and "Oracle TNSListener" services use the "administrator" account. [For Oracle 12c, the Oracle Installation User (Oracle owner) must be a member of the Windows operating system’s “Administrators” Group.] |
Backup Requirements |
• The Oracle database should be in Open state when you perform the online backup. • 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 password file (e.g.c:\oracle\ora92\database\pwd<instance>.ora) and the init file (e.g. c:\oracle\admin\<instance>\pfile\init.ora) should be backed up in a File system backup set. • You do not need to place online tablespaces in backup mode when performing backups. |
Restore Requirements |
There are the following requirements and limitations: • To restore the Control File, start the database in nomount (started) state. • To restore Tablespaces without the Control File, start the database in mount state. Otherwise, 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. • 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, 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: • The backup should be a full Oracle database backup. You should also have a backup of the password file and the init file (this will be in a File system backup set). • The target restore computer should have an Oracle database service Instance of the same name. • The target restore computer should 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 the information about file structure is recorded in the Control File and the Oracle Database as a whole. • 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. • Restore the full Oracle database backup. • 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. |
Backup / Restore of Oracle Database Servers using Linux DS-Client
For off-line 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 to perform online backup / restore of Oracle Database Servers.
General Requirements
• The user who performs Oracle Backup / Restore should have knowledge of 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 Installation and Support Matrix.This can be found on the Installation DVD in the following path: \Documentation\Release_Information
• 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. This is the TNS alias that is specified in the “tnsnames.ora” file on your Oracle client.
• For Oracle 12c, you must configure a separate ‘Net service Name’ to access the Oracle Server at CDB-level or PDB-level. CDB-level will give access to the entire container database (Root and all pluggable databases). PDB-level will give access to only the specific pluggable database named.
• If the Oracle Instance is a shared server, set the Connection Type as "Dedicated Server" using Net Manager.
• Recovery Manager (RMAN) utility must be installed.
• 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.
• 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_Classic_Library:
• libobk.so
This file is for Linux 32-bit Oracle database. Copy this file to $ORACLE_HOME/lib on 32-bit Linux Oracle Server.
• libobk-64.so
This file is for Linux 64-bit Oracle database. Copy this file to $ORACLE_HOME/lib on 64-bit Linux Oracle Server and make a soft link ln -s libobk-64.so libobk.so.
NOTE: If you upgrade from DS-Client v13 or lower, you must copy this file libobk-64.so again because a newer version has been built to support Oracle 12c.
• libobk.a
This file is for AIX Oracle database. Copy this file to $ORACLE_HOME/lib on AIX Oracle server.
• libobk_ia64.sl
This file is for HPUX Itanium oracle database. Copy this file to $ORACLE_HOME/lib on HPUX Itanium Oracle Server and make a soft link ln -s libobk_ia64.sl libobk.so
• libsbt64.so
This file is for Solaris (9 & 10) 64-bit Oracle database. Copy this file to $ORACLE_HOME/lib on Solaris 64-bit Oracle server and make a soft link ln -s libsbt64.so libobk.so
NOTE: For Solaris 11 Oracle servers, you must take the libsbt64.so file found in the /Misc/Oracle_Classic_Library/Solaris11 sub-folder.
• libsbt32.so
This file is for Solaris 32-bit Oracle database. Copy this file 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.
• 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 enter the user account of ’root’ for the network credentials.
• For Oracle 12c: By default, threaded execution is OFF on the Oracle server. If threaded execution is enabled, DS-Client using DS-PIPE will fail to back up the controlfile.
Restore Requirements
There are the following requirements and limitations:
• To restore the Control File, 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.
• 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, 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:
• 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).
• 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.
• 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.
• 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.
• Restore the full Oracle database backup.
• 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.