Powering On and Off a Recovery Appliance Rack

This section includes the following topics:

Emergency Power-Off Procedure

In an emergency, halt power to Recovery Appliance immediately. The following emergencies might require powering off Recovery Appliance:

  • Natural disasters, such as earthquake, flood, hurricane, tornado, or cyclone

  • Abnormal noise, smell, or smoke coming from the system

  • Threat to human safety

Powering Off in an Emergency

In an emergency, do one of the following:

  • Turn off power at the circuit breaker.

  • Pull the emergency power-off switch in the computer room.

After the emergency, contact Oracle Support Services about restoring power to the system.

About the Emergency Power-Off Switch

You can use the emergency power-off (EPO) switch to remove power from Recovery Appliance.

EPO switches are required when computer equipment contains batteries capable of supplying more than 750 volt-amperes for more than five minutes. Systems that have these batteries include internal EPO hardware for connecting to a site EPO switch or relay.

Shutting Down Recovery Appliance

Under normal, nonemergency conditions, you can power down the software services and hardware gracefully.

Stop all software services before shutting down the rack components.

Stopping Recovery Appliance Services

You must stop the Recovery Appliance services, Oracle Database File System, Oracle Database, and the cluster services. This operation has been simplified with the implementation of racli stop appliance, which elminates several manual steps involving the keystore and calling various API commands.

To stop the Recovery Appliance services:

  1. To shut down the Recovery Appliance, run the following command as an admin user. 

    [root@myhost ~]# racli stop appliance

    Among the operations this performs:

    • Shuts down the keystore.

    • Opens a connection to Oracle Database.

    • Checks the status of the services.

    • Runs the API for shutting down the Recovery Appliance services.

    • Disconnects from the Oracle Database.

    • Stops Oracle Secure Backup, if it is involved.

    • Stops the Oracle Database.

  2. Switch to the root user.

  3. Stop the Oracle Clusterware stack on all nodes in the cluster:

    # $GRID_HOME/bin/crsctl stop cluster -all
CRS-2673: Attempting to stop 'ora.crsd' on 'zdlradb07'
CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on
'zdlradb07'
CRS-2673: Attempting to stop 'ora.LISTENER_SCAN2.lsnr' on 'zdlradb07'
CRS-2673: Attempting to stop 'ora.LISTENER_SCAN1.lsnr' on 'zdlradb07'
     .
     .
     .
#

    If the command fails, reenter it with the -f option.

  4. On each compute server, run the following command to stop the Oracle Cluster Ready Services (CRS):

    # $GRID_HOME/bin/crsctl stop crs
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'radb08'
CRS-2673: Attempting to stop 'ora.crf' on 'radb08'
CRS-2673: Attempting to stop 'ora.mdnsd' on 'radb08'
     .
     .
     .
CRS-2677: Stop of 'ora.crf' on 'radb08' succeeded
CRS-2677: Stop of 'ora.mdnsd' on 'radb08' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'radb08' has completed
CRS-4133: Oracle High Availability Services has been stopped.

  5. Shut down or reboot the hardware as required, in the following order:

    1. Compute servers

    2. Storage servers

    3. Rack and switches

Powering Down the Servers

Before powering down a server, stop the services running on it, as described in "Shutting Down Recovery Appliance".

To shut down a compute server or a storage server:

  1. Log in to the server as root.
  2. Stop the operating system:
    # shutdown -h -y now

    Or restart the operating system:

    # shutdown -r -y now

Example 13-1 Powering Off Recovery Appliance Using the dcli Utility

  1. Stop Oracle Clusterware on all compute servers:

    # GRID_HOME/grid/bin/crsctl stop cluster -all

  2. Shut down the other compute server in the rack:

    # dcli -l root -g ra-adm02 shutdown -h -y now

    In the preceding command, ra01adm02 is the name of the second compute server.

  3. Shut down all storage servers:

    # dcli -l root -g cell_group shutdown -h -y now

    In the preceding command, cell_group is a file that lists all storage servers.

  4. Shut down the local compute server:

    shutdown -h -y now

  5. Power off the rack.

Use the dcli utility to run the shutdown command on multiple servers simultaneously. Do not run dcli from a server that will be powered off by the command.

The following example shuts down a group of storage servers listed in a file named cell_group: 

# dcli -l root -g cell_group shutdown -h -y now

Example 13-1 shows the power off procedure for the rack when using the dcli utility to shut down multiple servers simultaneously. The commands run from a compute server.

Powering the Network Switches

The gateway and spine switches do not have power controls. They power off when power is removed, by turning off a PDU or a breaker in the data center.

Starting Up Recovery Appliance

Turn on the rack components first, then start the software services.

Starting Up Recovery Appliance Components

To power on the rack components, use one of the following methods:

  • Press the power button on the front of the component.

  • Log in to Oracle ILOM and apply power to the system. See "Powering On Servers Remotely".

Startup Sequence

Power on the rack components in this sequence:

  1. Rack and switches

    Allow the switches a few minutes to initialize, before you start the storage servers.

  2. Storage servers

    Allow five to 10 minutes for the storage servers to start all services. Ensure that they finish initializing before you start the compute servers.

  3. Compute servers

    When a compute server is powered on, the operating system and Oracle Clusterware start automatically. Oracle Clusterware then starts all resources that are configured to start automatically.

Powering On Servers Remotely

You can use the Oracle ILOM interface to power on the Recovery Appliance servers remotely. To access Oracle ILOM, use the web console, the command-line interface (CLI), intelligent platform management interface (IPMI), or simple network management protocol (SNMP).

For example, to apply power to server ra01cel01 using IPMI, you use its Oracle ILOM with a command like the following: 

# ipmitool -H ra01cel01-ilom -U root chassis power on

IPMItool must be installed on the server where you use the command.

See Also:

Oracle Integrated Lights Out Manager (ILOM) 3.0 documentation for additional information about using Oracle ILOM to power on the servers:

http://docs.oracle.com/cd/E19860-01/index.html

Starting the Recovery Appliance Software

  1. Log in as root to a Recovery Appliance compute server.

  2. Confirm that Oracle Cluster Ready Services (CRS) is running:

    	# $GRID_HOME/bin/crsctl status server
	  NAME=radb07
	  STATE=ONLINE
	
	  NAME=radb08
	  STATE=ONLINE

  3. If CRS is not running, then start it:

    # $GRID_HOME/bin/crsctl start cluster -all
CRS-2672: Attempting to start 'ora.evmd' on 'radb07'
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'radb07'
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'radb08'
     .
     .
     .
#

  4. Switch to the oracle user.

  5. Start up the Recovery Appliance.

    [root@myhost ~]# racli start appliance

    Among the operations this performs:

    • Starts the Oracle Database

    • If Oracle Secure Backup is enabled, this service is started.

    • Connects to the Oracle Database.

    • Checks the status of the Recovery Appliance.

    • If services are off, it starts them.

    • It enables the keystore.