PRIMECLUSTER Wizard for Oracle 4.6 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 database cold backup (offline backup) as follows. If there are Oracle database -dependent resources (e.g. SAP R/3), a resource failure might occur during Oracle database stop, so it is necessary to stop them manually in advance.

1. Maintenance mode / Monitoring disruption

   # /opt/SMAW/SMAWRrms/bin/hvutil -m on <userApplication> (Maintenance mode)
   # /opt/FJSVclora/sbin/hvoradisable -a <userApplication>(Monitoring disruption)

2. Confirmation of maintenance mode and stop of monitoring

   Confirm that changing into maintenance mode and stop of monitoring have been successfully done.

   (Refer to note of "4.1 hvoradisable - Discontinue Monitoring Resources".)

3. Enable Oracle Restart settings

   Enable Oracle Restart settings if necessary.
   (Refer to "3.2 Oracle database Maintenance".)

4. Oracle database stop

   # su - <Oracle user>
   $ sqlplus /nolog
   SQL> CONNECT / AS SYSDBA
   SQL> SHUTDOWN IMMEDIATE

5. Cold backup

   Perform cold backup of the database.

6. Oracle database startup

   # su - <Oracle user>
   $ sqlplus /nolog
   SQL> CONNECT / AS SYSDBA
   SQL> STARTUP

7. PDB startup(for the database using the multitenant architecture)

   # su - <Oracle user>
   $ sqlplus /nolog
   SQL> CONNECT / AS SYSDBA
   SQL> ALTER PLUGGABLE DATABASE ALL OPEN;

8. Disable Oracle Restart settings

   If "3. Enable Oracle Restart settings" is executed, disable Oracle Restart settings.
   (Refer to "3.2 Oracle database Maintenance".)

9. Monitoring restart / Maintenance mode stop

   # /opt/FJSVclora/sbin/hvoraenable -a <userApplication> (Monitoring restart)
   # /opt/SMAW/SMAWRrms/bin/hvutil -m off <userApplication> (Maintenance mode stop)

10. Confirmation of restart of monitoring and maintenance mode

    Confirm that restart of monitoring and changing out of maintenance mode has been successfully done.

    (Refer to note of "4.2 hvoraenable - Restart Monitoring Resources".)

11. Restart userApplication

    When the Oracle instance, listener, or ASM is stopped and started manually, restart the userApplication including Oracle resources.

    # hvutil -f <userApplication>
    # hvswitch <userApplication> <SysNode>

3.2.3.2 Hot backup

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

1. Maintenance mode / Monitoring disruption

   # /opt/SMAW/SMAWRrms/bin/hvutil -m on <userApplication> (Maintenance mode)
   # /opt/FJSVclora/sbin/hvoradisable -a <userApplication> (Monitoring disruption)

2. Confirmation of maintenance mode and stop of monitoring

   Confirm that changing into maintenance mode and stop of monitoring have been successfully done.

   (Refer to note of "4.1 hvoradisable - Discontinue Monitoring Resources".)

3. 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. Be sure to check that the PDBs are properly running for the database using the multitenant architecture.

4. Monitoring restart / Maintenance mode stop

   # /opt/FJSVclora/sbin/hvoraenable -a <userApplication> (Monitoring restart)
   # /opt/SMAW/SMAWRrms/bin/hvutil -m off <userApplication> (Maintenance mode stop)

5. Confirmation of restart of monitoring and maintenance mode

   Confirm that restart of monitoring and changing out of maintenance mode has been successfully done.

   (Refer to note of "4.2 hvoraenable - Restart Monitoring Resources".)