4 Starting and Stopping DIVArchive

This chapter describes the steps required to start and stop DIVArchive. See the Linux installation instructions in the Oracle DIVArchive Installation and Configuration Guide in the Oracle DIVArchive 7.5 Core documentation library for Linux-specific directions associated with running DIVArchive components as services in a Linux environment.

All Windows batch files (.bat) have corresponding shell scripts (.sh) in Linux. You must substitute Windows paths with Linux paths when operating on Linux. For example, the Windows path C:\DIVA\Program is /home/diva/DIVA/Program when running under Linux. Linux commands, paths and file names are case-sensitive.

This chapter includes the following information:

Starting DIVArchive

To start the DIVArchive system you must first start the hardware, and then the software in the sequence as described in the following sections.

Starting DIVArchive Hardware

Perform the following steps in sequence to start all of the DIVArchive hardware components. Wait for initialization of each hardware component to complete before moving to the following step.

  1. Confirm that all required devices are installed. If they are not installed, you must install them before proceeding any further.

    See Appendix A for Oracle DIVArchive options and licensing information.

    • Libraries and Drives

    • SAN RAID Arrays

    • Fibre Channel Switches

    • Networking Devices

    • Terminal Concentrator

    • Graphical Front End Hosts

    • Library Manager Host

    • External Direct Attached Devices

    • Manager Hosts

    • Actor Hosts

  2. Power on the Libraries and Drives.

  3. Power on the SAN RAID Arrays.

  4. Power on the Fibre Channel Switches (if installed).

  5. Power on the Networking Devices.

  6. Power on the Terminal Concentrator (if installed).

  7. Power on the Graphical Front End Hosts (if installed).

  8. Power on the Library Manager Host (if installed).

  9. Power on External Direct Attached Devices.

  10. Power on Manager Hosts.

    In installations where two Manager Hosts are installed, it may be required to always start the Main manager first, and then the Alternate (or Backup) Manager at a later time. Consult with your Oracle Installer to determine if this is applicable to your installation.

  11. Power on the Actor Hosts.

Hardware start is complete if everything powered on successfully.

Starting DIVArchive Software

The following steps describe the required order that the software components of a DIVArchive system must be launched. Some software components may be set to launch automatically when the host is started (for example, the Actor Service).

The management of each DIVArchive software component, whether manually or automatically initiated, is covered in Software Components. Perform the following steps in sequence to start all of the DIVArchive software components:

  1. Confirm that all required components are installed. If they are not installed, you must install them before proceeding any further.

    1. Library Manager

    2. Library

    3. DIVArchive Manager

    4. DIVArchive Backup Service

    5. Complex Objects (if in use)

    6. DIVAnet

    7. DIVArchive VACP Converter

    8. DIVArchive Storage Plan Manager (SPM)

    9. DIVArchive Drop Folder Monitor (DFM)

  2. Launch the Library Control software.

    1. ACSLS

    2. PCS

    3. SDLC

  3. Launch the DIVArchive Robot Managers.

  4. Launch the DIVArchive Actors.

  5. Launch the DIVArchive Manager.

  6. Launch DIVAnet.

  7. Launch the DIVArchive VACP Converter.

  8. Launch the DIVArchive Naming Service.

  9. Launch the DIVArchive Storage Plan Manager (SPM).

  10. Launch the DIVArchive Drop Folder Monitor (DFM).

Software start is complete if everything powered on successfully.

Stopping DIVArchive

You stop DIVArchive in the reverse order from starting the system. You shut down the software first and then the hardware. The following sections describe the required procedure to fully shut down DIVArchive.

Shutting Down the Software

To ensure that requests currently still in progress are not prematurely aborted by shutting down the DIVArchive system, it is recommended the DIVArchive Manager be stopped first, because any requests currently active will be completed before the Manager will complete the shut down.

See the DIVArchive Manager section for DIVArchive Manager shut down procedures. When the DIVArchive Manager is shut down all archive operations are ceased. It is not necessary to stop other DIVArchive software components before shutting down the host computer where they are installed.

Shutting Down the Hardware

Use the following procedure (in sequence) to shut down all DIVArchive related equipment and devices:

  1. Shut down the Manager Host.

  2. Shut down the Actor Hosts.

  3. Power off all External Direct Attached Devices.

  4. Power off Graphical Front End Hosts (if installed).

  5. Power off Terminal Concentrator (if installed).

  6. Shut down the Library Manager Host (if installed)

  7. Power off Network Devices.

  8. Power off Fibre Channel Switches (if installed).

  9. Power off SAN RAID Arrays (if installed).

  10. Power off Library and Drives.

Hardware shut down is complete if everything powered off successfully.

Manager Failover Procedures

Caution:

These procedures are critical and sensitive. They should only be performed under the control of an Oracle Support Technician.

Use the following procedures to switch to a Backup Manager (if possible) if a Manager fails:

The following procedures are performed on the Main Manager computer:

  1. Attempt to stop the DIVArchive Manager if it is still running.

  2. Run the DIVA DB Full Backup scheduled task.

  3. Run the DIVA DB Backup Sync scheduled task.

  4. Shutdown the DIVArchive Manager server as cleanly as possible.

The following procedures are performed on the Backup Manager computer:

  1. Change the IP address to the Main Manager computer's IP address and restart the computer.

  2. Use the following steps to recover the database:

    1. Run %DIVA_HOME%\Program\DBBackup\rman\bin\restore_lib5_from_mgr1_to_mgr2.bat.

    2. Choose 0 for Automatic Restore and wait for completion.

    3. Choose 0 for Full Backup.

    4. Choose q to quit.

  3. Start the DIVArchive Services (Manager, RobotManager, Storage Plan Manager, DFM, and so on depending on the configuration).

The system is now running from the new (originally the Backup Manager computer) Main DIVArchive Manager computer, enabling repair of the original Main Manager computer.