PRIMECLUSTER Wizard for Oracle 4.2 Configuration and Administration Guide

3.2.3 Backup

This section discusses how to backup Oracle databases.

3.2.3.1 Cold backup

You can perform Oracle cold backup (offline backup) as follows. If there are Oracle-dependent resources (e.g. SAP R/3), a resource failure might occur during Oracle stop, so it is necessary to stop them manually in advance.

1. Maintenance mode / Monitoring disruption

   # hvutil -m on <userApplication> (Maintenance mode)
   # hvoradisable -a <userApplication> (Monitoring disruption)

2. Oracle stop

   # su - < Oracle user >
   $ sqlplus /nolog
   SQL> connect / as sysdba
   SQL> shutdown immediate

3. Cold backup
   Perform cold backup of the database.

4. Oracle startup

   # su - < Oracle user >
   $ sqlplus /nolog
   SQL> connect / as sysdba
   SQL> startup

5. Monitoring restart / Maintenance mode stop

   # hvoraenable -a <userApplication> (Monitoring restart)
   # hvutil -m off <userApplication> (Maintenance mode stop)

Note

If there are Oracle-dependent resources, the procedure with the monitoring disruption command might not work. When Oracle resources are stopped with the monitoring disruption command then Oracle is stopped manually, the Oracle-dependent resource might fail.

You need to check the status of the Oracle-dependent resource when you stop Oracle manually.

3.2.3.2 Hot backup

You can perform Oracle hot backup (online backup) as follows.

1. Maintenance mode / Monitoring disruption

   # hvutil -m on <userApplication> (Maintenance mode)
   # hvoradisable -a <userApplication> (Monitoring disruption)

2. Hot backup
   Perform hot backup of the database. Be sure to check that the Oracle instance and listener are properly running before going on to the next step.

3. Monitoring restart / Maintenance mode stop

   # hvoraenable -a <userApplication> (Monitoring restart)
   # hvutil -m off <userApplication> (Maintenance mode stop)