Chapter 3
Install Backup Toolkit V4.2.3

This chapter discusses the installation of Backup Toolkit V4.2.3 and SAMS:Alexandria on a IBM NUMA-Q host running DYNIX/ptx V4.2.x.


Software Installation and Upgrade Overview

Personnel approved by IBM NUMA-Q will install Backup Toolkit, ptx/SLPT, and SAMS:Alexandria for all first-time customers. If you are an existing Backup Toolkit and SAMS:Alexandria user, you can upgrade these products yourself with phone assistance from IBM Customer Support.


ATTENTION

Be sure to read through the entire installation chapter before installing or upgrading ptx/SLPT, Backup Toolkit, and SAMS:Alexandria. You should also read through the Backup Toolkit Administration Guide for SAMS:Alexandria.

You may be upgrading a SAMS:Alexandria server host that is using an ACSLS-connected STK library. In that case, before you perform the upgrade, be sure to review Chapter 3, "Configure and Use an ACSLS-Connected Library with SAMS:Alexandria," in the Backup Toolkit Administration Guide for SAMS:Alexandria for applicable configuration information.

If you are installing SAMS:Alexandria on the nodes of a clustered system, refer to Chapter 4, "Use SAMS:Alexandria with ptx/SVM and ptx/CLUSTERS," in the Backup Toolkit Administration Guide for SAMS:Alexandria. You might need to contact IBM Customer Support for assistance in planning your SAMS:Alexandria environment on your clustered system.


On new installations of ptx/SLPT, Backup Toolkit, and SAMS:Alexandria, install these products on the server host and configure the server host for client use before you install these products on a client host. Configuring the server host for client use includes configuration of the server activation key, which includes client host support and configuration of security and the Remote Home Node option for each client host that will use this server. Additionally, ensure that SAMS:Alexandria is running on the server host during the client host installation.

On upgrade installations, upgrade Backup Toolkit and SAMS:Alexandria on the client host before you upgrade ptx/SLPT, Backup Toolkit, and SAMS:Alexandria on the server host.


ATTENTION

The only network configurations that are supported are those between server and client hosts running SAMS:Alexandria V4.50.53 and later patch releases. Network configurations are not supported between hosts running SAMS:Alexandria V4.50.53 or later patch releases and hosts running versions of SAMS:Alexandria prior to V4.50.53 or running any version of ptx/ESBM.


The installation and upgrade process comprises the following major tasks:

[  ]

For new installations, prepare for the installation. You should try to complete these pre-installation tasks before having a IBM representative at your site. For details, refer to Chapter, "Hardware Installation and First-Time Installations," earlier in these release notes.

[  ]

On SAMS:Alexandria server hosts, configure the DYNIX/ptx kernel. For details, refer to "Configure the DYNIX/ptx Kernel for SAMS:Alexandria" later in this chapter.


ATTENTION

The installation or upgrade automatically sets or adjusts the values of most of the kernel parameters required by SAMS:Alexandria. For more information on these kernel parameters, refer to "Kernel Parameters Set by Backup Toolkit" in Chapter 1 of the Backup Toolkit Administration Guide for SAMS:Alexandria.


[  ]

For existing SAMS:Alexandria users, prepare for the upgrade and ensure that you have a good backup of the SAMS:Alexandria database. For details, refer to "Prepare for the Upgrade" later in this chapter.

[  ]

On hosts that will be SAMS:Alexandria servers, install or upgrade ptx/SLPT by using the layered product installation procedures in ptx/ADMIN. The installation of ptx/SLPT requires a kernel build and a system reboot. ptx/SLPT is not required for client installations.


ATTENTION

Do not perform the ptx/SLPT installation steps in the ptx/SLPT Release Notes when SAMS:Alexandria is also being used. Instead, refer to "Install or Upgrade ptx/SLPT" later in this chapter.


[  ]

Install the Backup Toolkit software. For details, refer to "Install the Backup Toolkit Software" later in this chapter.

[  ]

Install SAMS:Alexandria using the Backup Toolkit installalex script. For details, refer to "Install SAMS:Alexandria" later in this chapter.

[  ]

Complete the installation of SAMS:Alexandria. This step involves configuring any activation keys, configuring SAMS:Alexandria to print critical system information, configuring devices, and reenabling backups and SAMS:Alexandria daily housekeeping. For more information, refer to "Complete the Installation of SAMS:Alexandria" later in this chapter.


ATTENTION

After installation, prepare for disaster recovery by saving critical system information and creating a custom miniroot tape for that host. Otherwise you might be unable to recover the root, /usr, or SAMS:Alexandria filesystems in the event of a disk crash. Refer to the discussion of disaster preparation in the Backup Toolkit Administration Guide for SAMS:Alexandria for more information.



Configure the DYNIX/ptx Kernel for SAMS:Alexandria

Complete the following steps to adjust the DYNIX/ptx kernel configuration for SAMS:Alexandria server hosts. Be sure to review this section even if you are an existing SAMS:Alexandria customer. For more information about configuring the kernel, refer to the DYNIX/ptx System Configuration and Performance Guide.


ATTENTION

The installation or upgrade automatically sets or adjusts the values of most of the kernel parameters required by SAMS:Alexandria. For more information on the kernel parameters used by SAMS:Alexandria, refer to Chapter 1 of the Backup Toolkit Administration Guide for SAMS:Alexandria.


  1. On SAMS:Alexandria server hosts that are using DDS-2 libraries or DDS-3 libraries, edit the /etc/conf/uts/symmetry/sb8000/unix_sb8000.std system configuration file to contain the correct number of DDS-2 tape drives and DDS-3 tape drives and to bind each of these devices to a specific channel and unit number (SCSI ID of tape drive). By default, the system configuration file only contains four entries for DDS-2/DDS-3 tape drives connected to QCIC-based SCSI buses, and these devices are wild-carded:

    td      on      qcic_scsi ?     unit    ? segsize 135168 nsegs 1
    td on qcic_scsi ? unit ? segsize 135168 nsegs 1
    td on qcic_scsi ? unit ? segsize 135168 nsegs 1
    td on qcic_scsi ? unit ? segsize 135168 nsegs 1

    Edit the system configuration file so that it contains one entry for each DDS-2 tape drive and DDS-3 tape drive you plan to use.


    ATTENTION

    If a DDS-2 library or DDS-3 library is moved to a different SCSI bus at some later time, update the entries for the affected devices in the system configuration file with the appropriate channel and unit numbers, build a new kernel, and reboot the system. Wild-carding causes the kernel to assign device numbers in the order in which the devices are found at system boot time. If a device is not found, the unit number normally associated with that device will be assigned to another device, which can cause the device to be associated with an unexpected device name. For more information about binding devices, refer to the DYNIX/ptx System Configuration and Performance Guide.


    The DDS-2 libraries and DDS-3 libraries (ms devices) cannot be configured until ptx/SLPT is installed.

  2. On SAMS:Alexandria server hosts that are using HP DLT4000 libraries, an ACSLS-connected library, or a directly-connected STK library ensure that the /etc/conf/uts/symmetry/spd.std system configuration file has bound the HP DLT4000 libraries (ml device) and directly-connected STK library (mw device) and ACSLS-connected library tape devices (tl devices) to specific channels and unit numbers (SCSI ID of library or tape drive). The installation of ptx/SPDRIVERS does not require you to bind these devices so you must do so now.


    ATTENTION

    If a bound device is moved to a different SCSI bus at some later time, update the entries for the affected devices in the spd.std configuration file with the appropriate channel and unit numbers, build a new kernel, and reboot the system. Wild-carding causes the kernel to assign device numbers in the order in which the devices are found at system boot time. If a device is not found, the unit number normally associated with that device will be assigned to another device, which can cause the device to be associated with an unexpected device name. For more information about binding devices, refer to the DYNIX/ptx System Configuration and Performance Guide.

    Some wild-carded devices need to be available in the spd.std configuration file in case you ever perform a system recovery of this host on an alternate host. The alternate host will be unable to find bound devices unless the devices are located on the exact same address, bus, QCIC card, and slot in the back plane. Also, the custom miniroot does not enable you to build a new kernel. Do not configure any of these wild-carded devices into SAMS:Alexandria.


  3. If you will be performing RPF restore operations with multiple files, you should examine the setting of the SEMMSL kernel parameter. This kernel parameter designates the maximum semaphores needed. SAMS:Alexandria requires three times the number of files being restored with RPF plus three. For example, if you are restoring 10 files, SAMS:Alexandria requires 33 semaphores. (That is, three times 10, which is 30, plus three, a total of 33.)


ATTENTION

You do not need to recompile or reboot the operating system at this time. Instead, wait until after ptx/SLPT is installed. Because ptx/SLPT contains kernel components, recompile and reboot the operating system after ptx/SLPT is installed. The kernel adjustments you just made can be picked up during this later recompile and reboot.



Prepare for the Upgrade

If this is an existing installation, prepare for the upgrade and save configuration information before you install or reinstall Backup Toolkit and SAMS:Alexandria. Perform this procedure immediately before actually installing the ptx/SLPT, Backup Toolkit, or SAMS:Alexandria software. Do not perform this procedure ahead of time. If this is the first installation of Backup Toolkit and SAMS:Alexandria, skip this procedure. For new server installations, continue with "Install or Upgrade ptx/SLPT" later in this chapter; for new client installations, continue with "Install Backup Toolkit" later in this chapter.


ATTENTION

You can upgrade to Backup Toolkit V4.2.3 and SAMS:Alexandria V4.50.70 only from the following earlier versions:


Complete the following steps to prepare for the upgrade:

  1. If you will be installing SAMS:Alexandria as a server or using the COBRA, ON-Bar, RMAN, or the AlexClient/NT personalities, contact IBM Customer Support to obtain new activation keys. New activation keys are required for existing customers because the version number of SAMS:Alexandria has changed. For more information about activation keys, refer to the section "Obtain Activation Keys for SAMS:Alexandria" in Chapter 2 of these release notes.

  2. If you are upgrading a server host that will use directly-connected STK libraries or ACSLS-connected libraries, contact IBM Customer Support to obtain a new library personality activation key for the STK library you will be using. You need a new library activation key because the ST-9710, ST-9730, ST-L700, and ACSLS library personalities required by the STK libraries are protected and because the version number of SAMS:Alexandria has changed.

  3. Log in as user root:

    # su

  4. Copy the systeminfo script to a secure location. Doing so preserves any customizations you might have made to the systeminfo script on your host. Otherwise, any customizations will be lost as the installation overwrites the current systeminfo script with the default systeminfo script from the distribution media. For example:

    # mkdir /usr/alexbkup/upgrade
    # cp /usr/alexbkup/disaster_recovery/systeminfo
  5. Save information about the current settings for all SAMS:Alexandria configuration options. For example:

    # alex-option -Lc > /usr/alexbkup/upgrade/option.out
  6. Ensure that you have a recent, good backup of the SAMS:Alexandria database. Normally, this backup occurs during daily SAMS:Alexandria housekeeping. If you use the backup from the most recent SAMS:Alexandria housekeeping, be sure to verify that the backup was successful.

    If you want to perform an unscheduled housekeeping operation, you can use the following command:

    # alex-sched -c

    This operation can take up to 30 minutes or more to complete for sites with large SAMS:Alexandria databases. Once the backup has completed successfully, remove the tapes that contain this backup from the library and write-protect the tapes.

  7. Ensure that SAMS:Alexandria daily housekeeping is not scheduled to run during the upgrade. If it is scheduled to run at that time, change the House-Keeping-Time configuration option to a time that does not overlap the time scheduled for the upgrade. For example, to change the housekeeping start time to 4:00 am, enter the following command:

    # alex-option -u House-Keeping-Time 04:00

  8. Unmanage (unschedule) any operation cards that are scheduled to run during the installation time. For example, to unmanage the operation card Root-Full, enter the following command with a 0 (zero) at the end of the syntax:

    # alex-opcard -Um Root-Full 0

  9. Ensure that no SAMS:Alexandria store or restore operations are in progress or pending. These processes are called alex-store and alex-restore in the ps output. To display all running SAMS:Alexandria processes, enter the following command:

    # alex-sched -lq -la

    If you see any pending or active SAMS:Alexandria operations, you should wait until the operations have been completed before you proceed with the installation. If you do not want to complete these operations, then perform the remaining steps of this procedure. These pending and active operations will be terminated when the SAMS:Alexandria daemons are stopped in a later step.

  10. Ensure that all vaultable media, including SAMS:Alexandria DATABASE tapes, are ejected from each library. For example, to eject all vaultable media from library Host1-DDS2-1, use the alex-cntrl command with the +l option (l as in 'library'):

    # alex-cntrl +l Host1-DDS2-1 -E

  11. Stop the SAMS:Alexandria daemons:

    # sh /etc/init.d/alex stop

    You can verify that the daemons are stopped if the following command shows no SAMS:Alexandria processes:

    # ps -ef | grep alex

  12. If you are upgrading DYNIX/ptx to a later version, do so now. Refer to the appropriate DYNIX/ptx Release Notes for installation information.


    ATTENTION

    Do not use SAMS:Alexandria until the entire upgrade process is complete. If Backup Toolkit is already installed, SAMS:Alexandria will be automatically started when the system is booted. In this case, stop it with the /etc/init.d/alex stop command after the system boots.


Once you have prepared for the upgrade, continue with the procedure "Install or Upgrade ptx/SLPT."


Install or Upgrade ptx/SLPT

Install or upgrade to ptx/SLPT V2.0.2 before you install or upgrade a SAMS:Alexandria server. ptx/SLPT is not required for SAMS:Alexandria client installations.

The following instructions assume that you are familiar with the DYNIX/ptx installation procedure and with the ptx/ADMIN menu system, which is used to install the ptx/SLPT software. For more information about the installation procedure and the menu system, refer to the Installing Software with ptx/ADMIN, which is part of the DYNIX/ptx Software Installation Guide.


ATTENTION

ptx/SLPT does not support alternate disk installation.


To install ptx/SLPT, complete these steps:

  1. Log in as user root, if not already done:

    # su

  2. Enter the menu command to start the ptx/ADMIN menu system; then select the System Administration option.

  3. From the System Administration menu, choose the Software Management option.

  4. If needed, use the Change Installation Device option on the Software Management menu to change the installation device to the appropriate device (tape or CD-ROM).

  5. Insert the distribution media and run the preview phase by choosing Preview Software Package from the Software Management menu.

    For the installation procedure, the name of this tape is slpt. The Bill of Materials (BOM) and other installation files for this tape are loaded into the /usr/options/slpt directory. The preview log created during the preview phase is named /usr/options/slpt/preview.log. The preview phase reports the amount of space needed in / and /usr to install ptx/SLPT.

  6. When the preview phase is complete, use the View/Edit Preview Log menu option to examine the preview log.

  7. Run the install phase by choosing Install Software Package from the Software Management menu. The name of the package to be installed is slpt.


    ATTENTION

    The /usr/options/slpt/oldfiles directory is the default location for saving locally modified files that are in conflict with files on the installation tape. If the oldfiles directory currently contains files from an earlier version of this package, be sure to move or delete this directory before you start the install phase.


  8. When the software is installed, you will be asked whether you want to build the man-page databases:

    Do it now?

    It can take up to an hour to build the man-page databases. If you want to complete the installation of ptx/SLPT, which requires you to reboot the operating system in a later step, you should enter n at this prompt. If you enter n, you can build the man-page databases at a later time by entering both the makealiases and makewhatis commands. If you answer y at this prompt, the man pages will be built in the background.

  9. After you enter y or n at the prompt shown in step 8, the install phase of ptx/ADMIN ends. Complete the remaining steps of this procedure to finish the installation of ptx/SLPT.

  10. If you plan to use DDS-2 libraries or DDS-3 libraries with SAMS:Alexandria, edit the system configuration file for DDS-2/DDS-3 libraries, which by default is /etc/conf/uts/symmetry/ms.std, to bind the DDS-2/DDS-3 library devices to a specific channel and unit number (SCSI ID of library). By default, these devices are wild-carded:

    ms      on      qcic_scsi ?     unit    ? segsize 135168 nsegs 1

    ATTENTION

    If a DDS-2 library or DDS-3 library is moved to a different SCSI bus at some later time, update the entries for the affected library in the ms.std file with the appropriate channel and unit number, build a new kernel, and reboot the system.

    Be sure to comment out lines for those ms devices you do not plan to use.

    The DDS-2 tape drives and DDS-3 tape drives should have already been properly configured during the preinstallation tasks. If not refer to "Configure the DYNIX/ptx Kernel for SAMS:Alexandria" earlier in this chapter.


  11. Compile the kernel with the configuration updates from the preinstallation task "Configure the DYNIX/ptx Kernel for SAMS:Alexandria" and from step 10 of this procedure.

    The Kernel Configuration option, accessed from the ptx/ADMIN System Administration menu, can be used to compile the appropriate kernel. This new kernel will include the kernel adjustments made during preinstallation and the kernel components in ptx/SLPT. The ptx/SLPT kernel components do not need modification. They are configured by default for the maximum supported SAMS:Alexandria usage. Even if this host has previously used ptx/SLPT, compile a new kernel after ptx/SLPT V2.0.2 is installed.

  12. Shut down the operating system by entering the init 0 command. Then power down the system.


    ATTENTION

    If you do not need to attach DDS-2 libraries, DDS-3 libraries, HP DLT4000 libraries, or STK libraries, you do not have to power down the system. However, you must reboot the operating system with the newly compiled kernel since ptx/SLPT has kernel components.


  13. If all the libraries are not already installed on your system, install them now while the system is powered down. For information about installing libraries supported by IBM NUMA-Q, refer to the following manuals as appropriate: DDS-2 Library Operator's Guide, DDS-3 Library Operator's Guide, NUMA-Q Supplement to the DLT Tape Library User's Guide, and the NUMA-Q Supplement to the StorageTek Hardware Operator's Guides.

  14. Power up all libraries connected to the system.


    ATTENTION

    The libraries must be powered up and ready before the operating system is booted.


  15. Power up the system and boot the operating system with the newly compiled kernel.

Once ptx/SLPT is installed and the system is rebooted, continue with the procedure "Install Backup Toolkit."


Install Backup Toolkit

Personnel approved by IBM NUMA-Q will perform all new installations of Backup Toolkit. If you are an existing SAMS:Alexandria user, you can perform the upgrade to Backup Toolkit yourself with phone assistance from IBM Customer Support. Backup Toolkit uses IBM NUMA-Q standard installation processes (ptx/ADMIN, which invokes ptxmd).


ATTENTION

If the SAMS:Alexandria database is corrupted or removed and you re-create the database, the default disaster-recovery operation cards will not exist in the re-created database. In this scenario, you must re-create the default disaster-recovery operation cards and configure the House-Keeping-Begin-Command to run the systeminfo script. For more information, refer to "Reconfigure the Disaster Recovery Environment" in Chapter 5 of the Backup Toolkit Administration Guide for SAMS:Alexandria.


Install Backup Toolkit and SAMS:Alexandria on the server host and configure the server host for client use before you install SAMS:Alexandria on a client host. (Backup Toolkit can be installed on a client host before the server host is configured.) Configuring the server host for client use includes configuration of the server activation key, which includes client host support and configuration of security and the Remote Home Node option for each client host that will use this server. Additionally, ensure that SAMS:Alexandria is running on the server host during the client host installation.


ATTENTION

Backup Toolkit does not support alternate disk installation.


Backup Toolkit is installed in the /usr/backup_toolkit directory. Under this directory are two subdirectories, alexandria and disaster_recovery. The alexandria subdirectory contains the installalex script, which is used during installation. The disaster_recovery subdirectory contains disaster preparation and recovery scripts.

Backup Toolkit also installs miscellaneous scripts and template files under the /usr/alexbkup/local/bin directory. For more information, refer to the section "Backup Toolkit Miscellaneous Scripts and Templates" in Chapter 1 of the Backup Toolkit Administration Guide for SAMS:Alexandria.


Install the Backup Toolkit Software

The following instructions assume that you are familiar with the DYNIX/ptx installation procedure and with the ptx/ADMIN menu system, which is used to install the Backup Toolkit software. For more information about the installation procedure and the menu system, refer to the Installing Software with ptx/ADMIN, which is part of the DYNIX/ptx Software Installation Guide.

To install the Backup Toolkit software, complete these steps:

  1. If this is a new Backup Toolkit and SAMS:Alexandria installation and not already done, complete the tasks described in Chapter 2, "Hardware Installation and First-Time Installations," under the section "Prepare for First-Time Installations."

  2. If not already done for SAMS:Alexandria server hosts, configure the DYNIX/ptx kernel as described under "Configure the DYNIX/ptx Kernel for SAMS:Alexandria" earlier in this chapter.

  3. If the host already contains SAMS:Alexandria, complete the tasks described under "Prepare for the Upgrade" earlier in this chapter.


    ATTENTION

    Be sure to perform these preparation tasks before upgrading the host to Backup Toolkit and SAMS:Alexandria. These steps include saving site-specific information and ensuring that you have a good backup of the SAMS:Alexandria database.

    Be sure to have a custom miniroot tape that reflects the current configuration of the host. If you do not have a custom miniroot tape, refer to the disaster preparation procedures applicable to the current version of Backup Toolkit and SAMS:Alexandria. If you do not take these precautions, you might be unable to recover the data on the host as it existed before the upgrade occurred.


  4. If you have not already installed ptx/SLPT, do so now. For more information, refer to "Install or Upgrade ptx/SLPT" earlier in this chapter.

  5. If not already done, log in as user root:

    # su

  6. Enter the menu command to start the ptx/ADMIN menu system; then select the System Administration option.

  7. From the System Administration menu, choose the Software Management option.

  8. If needed, use the Change Installation Device option on the Software Management menu to change the installation device to the appropriate distribution media (CD-ROM).

  9. Insert the distribution media and run the preview phase by choosing Preview Software Package from the Software Management menu.

    For the installation procedure, the name of this tape is bktk. The Bill of Materials (BOM) and other installation files for this tape are loaded into the /usr/options/bktk directory. The preview log created during the preview phase is named /usr/options/bktk/preview.log. The preview phase reports the amount of space needed in the root and /usr directories to install Backup Toolkit.

  10. When the preview phase is complete, use the View/Edit Preview Log menu option to examine the preview log.

    If there are any files in conflict, carefully examine them to determine if they have been customized for your site or if they are just updated binaries. If they have been customized, save them to a secure location so that you can manually apply these customizations after the installation is complete. Then, before continuing the installation, ensure that the conflicts in the preview log file are set to CONFLICT-REPLACE. Do not set the entries to CONFLICT-SKIP.

  11. Run the install phase by choosing Install Software Package from the Software Management menu. The name of the package to be installed is bktk.


    ATTENTION

    The /usr/options/bktk/oldfiles directory is the default location for saving locally modified files that are in conflict with files on the installation tape. If the oldfiles directory currently contains files from an earlier version of this package, be sure to move or delete the directory before you start the install phase.


Once the Backup Toolkit software is installed, continue with the section "Install SAMS:Alexandria" later in this chapter. If you would like more information on what is installed with Backup Toolkit, refer to the next section "Understand the Backup Toolkit Directory."


Understand the Backup Toolkit Directory

Backup Toolkit is installed in the /usr/backup_toolkit directory. The files and subdirectories in this directory are as follows:

alexandria
Contains the installalex installation script. Also contains the LOG file, which captures messages from the installalex script.
alexandria/alex/
Contains Backup Toolkit files used by the installalex installation script. Also contains example operation card templates and unsupported tools and scripts for use with SAMS:Alexandria. These files are copied to /usr/alexbkup/local/bin by the installalex script after SAMS:Alexandria has been installed.
disaster_recovery/
Contains disaster preparation and recovery scripts. The files in this directory are copied to /usr/alexbkup/disaster_recovery by the installalex script after SAMS:Alexandria has been installed.
htmldocs/
Contains an HTML file for the Backup Toolkit Administration Guide for SAMS:Alexandria. For more information, refer to the section "Backup Toolkit and SAMS:Alexandria Documentation" in Chapter 1 of these release notes.

Install SAMS:Alexandria

SAMS:Alexandria is installed and configured on each system in your backup environment as either a server or client installation:


ATTENTION

On new installations, install SAMS:Alexandria on the server host and configure the server host for client use before you install SAMS:Alexandria on a client host. Additionally, ensure that SAMS:Alexandria is running on the server host during the client host installation.

On upgrade installations, upgrade SAMS:Alexandria on the client host before you do so on the server host.

The only network configurations that are supported are those between server and client hosts running SAMS:Alexandria V4.50.53 and later patch releases. Network configurations are not supported between hosts running SAMS:Alexandria V4.50.53 or later patch releases and hosts running versions of SAMS:Alexandria prior to V4.50.53 or running any version of ptx/ESBM.


Complete the following steps to install SAMS:Alexandria with the Backup Toolkit installalex script. The following procedure does not describe all messages and prompts that are actually output during the installation. For information on any message or prompt that is not described in this procedure, refer to the SAMS:Alexandria Installation Guide, Chapter 11, "Server: Install and Configure SAMS:Alexandria."

  1. If not already done, install the required layered products for SAMS:Alexandria. If these products are not installed, the installation of SAMS:Alexandria will fail. Refer to "Software Requirements" in Chapter 1 of these release notes for specific versions that should be installed.

  2. Change directories to /usr/backup_toolkit/alexandria. (You must run the script from within this directory.)

    # cd /usr/backup_toolkit/alexandria
  3. Run the Backup Toolkit installalex script to begin the SAMS:Alexandria installation process:

    # ./installalex

    The messages from this script are sent to the screen as well as saved to the /usr/backup_toolkit/alexandria/LOG file.

  4. At the following prompt, insert the SAMS:Alexandria CD into the CD-ROM drive and then press any key when ready to continue:

    What device should we mount [/dev/dsk/cd1]?

    At this point, the installalex script invokes the installation script provided by SAMS:Alexandria. Prompts about which platform you are installing, which type of files to install, and whether you want to run the SAMS:Alexandria Install script are displayed.

  5. At the following prompt, enter 1 to designate that the host is running DYNIX/ptx V4.2.3 or later maintenance releases.

    <<  Please select your hardware platform  >> 
    
    1)    DYNIX/ptx 4.2
    2)    DYNIX/ptx 4.4
    
    Please select a platform ( 1 - 2, Q ) :
    
  6. When the following prompt is displayed, enter Y to start the SAMS:Alexandria Install script.

    Would you like to run ./Install now (Y/N) ?
    
  7. At the following prompt, enter Y to accept all the default installation options:

    Would you like to use all the default installation options? [N]:
    

    Several lines of text are displayed about the options that the installation is configuring.

  8. For new installations, answer the following prompts as described:

    1. At the following prompt, enter N so that a FAX sheet is not generated:

      Do you want to generate the FAX sheet in order to
      obtain the software key (Y/N)?
      

      The FAX sheet is not applicable to IBM NUMA-Q customers. (Activation keys for DYNIX/ptx hosts are obtained from IBM Customer Support.)

    2. At the following prompt, enter N.

      Would you like to enter your software key now [Y/N]?
      

      The activation keys will be configured later in these installation procedures.

    3. At the following prompt, enter N to prevent the SetupHD script from running:

      Would you like to run SetupHD now (Y/N) ?
      

      The SetupHD script does not apply to DYNIX/ptx hosts. Instead, use the SetupHD.Seq script as described later in these procedures to configure devices in SAMS:Alexandria on a DYNIX/ptx host.

    4. At the following prompt, enter N to prevent SAMS:Alexandria from creating a Store operation card at this time:

      Would you like to setup your first Op-card now? [Y]:
      

      You will set up your operation cards later in these installation procedures.

  9. Once the SAMS:Alexandria Install script completes the installation of SAMS:Alexandria, the installalex script begins its post-installation processes required for DYNIX/ptx hosts. The tasks performed include:

Once Backup Toolkit and SAMS:Alexandria are installed, the /etc/versionlog file contains lines similar to the following to indicate this fact:

Tue May  2 16:23:29 PDT 2000 - Backup Toolkit V4.2.3 PN: 1003-75183-08
Tue May  2 16:28:30 PDT 2000 - Alexandria V4.50.70 PN: BKTK-ALEXANDRIA (insta
ll complete)

Continue with the section "Complete the Installation of SAMS:Alexandria" later in this chapter.


Install Software Patch for COBRA 4.50.70

If the host will be using COBRA, you must install the patch from the "SAMS:Alexandria 4.50.70 Software Patch" CD. This patch addresses a problem in COBRA 4.50.70 where a cold backup of an Oracle database would core dump when that backup did not include the archived redo logs (problem report 253587). Hosts that are not using COBRA do not require this patch.

Installation instructions for this patch CD are provided on the label of the CD.


Complete the Installation of SAMS:Alexandria

Once you have installed the SAMS:Alexandria software, complete the following steps to finish the installation of SAMS:Alexandria:

  1. If you are installing a server host, ensure that the file slpt_conf in the bits subdirectory of the SAMS:Alexandria home directory (typically /usr/alexbkup) includes the names of the device files for only those libraries and tape drives that you want to use with SAMS:Alexandria. (By default, for new installations or when this file does not exist, this file is created with the device filenames for all available libraries and tape drives supported by DYNIX/ptx for use with SAMS:Alexandria.)

    The device filenames in the slpt_conf file are used by the alex script to create the layered device files for use with SAMS:Alexandria.


    ATTENTION

    Be sure to configure only those libraries supported by DYNIX/ptx for use with SAMS:Alexandria. For information on supported libraries and maximum configurations, refer to "Backup Device Requirements" in Chapter 1 of these release notes.


    The device filenames for the libraries supported by DYNIX/ptx can be found in theptx/SPDRIVERS Release Notes or in Chapter 2, "Configure Backup Devices," of the Backup Toolkit Administration Guide for SAMS:Alexandria. For more information about the alex script, refer to the Backup Toolkit Administration Guide for SAMS:Alexandria.

    If you change your library configuration after the software is installed, edit the file /usr/alexbkup/bits/slpt_conf to designate the libraries you want to use with SAMS:Alexandria.

  2. If you will be performing RPF restore operations with multiple files, you should examine the setting of the SEMMSL kernel parameter. This kernel parameter designates the maximum semaphores needed. SAMS:Alexandria requires three times the number of files being restored with RPF plus three. For example, if you are restoring 10 files, SAMS:Alexandria requires 33 semaphores. (That is, three times 10, which is 30, plus three, a total of 33.) If you adjust this kernel parameter, recompile the kernel and reboot the system for the new value to take effect. For more information on kernel configuration, refer to the DYNIX/ptx System Configuration and Performance Guide.

  3. On server hosts that will be using an ACSLS-connected library, create the acsls_conf file in the bits subdirectory in the SAMS:Alexandria home directory, typically /usr/alexbkup. This file must contain the name of the ACSLS server that controls the robotics for the ACSLS-connected library you plan to use.

  4. If you are installing on a server host and the system was not rebooted during the software installation or if you changed the slpt_conf file or acsls_conf file, start or restart the SAMS:Alexandria daemons on the server host by running the alex script. (The alex script is automatically run during a system reboot.) On a server host, the alex script also creates the layered device files needed by SAMS:Alexandria. If the layered device files are not created, you will be unable to configure devices as described in a later step.

    # sh /etc/init.d/alex start

  5. If you want to use the transaction database logging feature of SAMS:Alexandria, configure the database on a raw partition, as described in the SAMS:Alexandria Reference Guide. The raw partition must belong to the owner alexbkup and the group alexbkup. If you plan to create a ptx/SVM volume on the partition, the disk containing the partition must belong to the rootdg disk group. For more information, refer to "Set Aside a Raw Partition for the Transaction Database Log" in Chapter 2 of these release notes.

  6. Configure activation keys on the host as appropriate:

    Alexandria clients do not need activation keys for the SAMS:Alexandria software or the AlexClient/NT personality; these licenses are granted through the server host. (For this reason, client hosts do not have to configure the Client-Nodes-Per-Server configuration option.)

    Use the alex-option command to configure or update these activation keys in their respective configuration options in SAMS:Alexandria. Use the -c option to configure the key for the first time on a new SAMS:Alexandria installation. Use the -u option to update an existing key on an existing SAMS:Alexandria installation. The syntax is as follows:

    # alex-option [ -u | -c ] configuration_option activationkey

    For example, the following commands update the activation keys for the SAMS:Alexandria server and the COBRA personality and initially configure the activation keys for the ON-Bar, RMAN, and AlexClient/NT personalities:

    # alex-option -u Server-Key SER0001FF07,AJFOCDGIKNGHMNVWTS 
    # alex-option -u COBRA-Personality-Key ejfnfmjnenflnovuqs
    # alex-option -c ONBAR-Personality-Key fhemenkprdremnqxwtr
    # alex-option -c Recovery-Manager-Personality-Key gifofplosesfnoryzt
    # alex-option -u NT-Nodes-Per-Server NT6,chemfmeijsflqnorus

    More information is provided about activation keys in the Chapter 1, "Getting Started," of the Backup Toolkit Administration Guide for SAMS:Alexandria.

  7. If you are installing a server host that will be using a directly-connected STK library or an ACSLS-connected library, configure the library personality activation keys that you obtained from IBM Customer Support for the appropriate library personality. These will be for either ST-9710,ST-9730, or ST-L700 for directly-connected STK 9710/9730/L700 libraries or ACSLS for an ACSLS-connected STK 9710/9740/L700 library.

    You can use the alex-person command to enter or update the activation key for the necessary library personality. For example, to enter the activation key for the ST-9730 library personality for the first time, use a command similar to the following:

    # alex-person -C ST-9730 diiqjqkohqgmnpqtss

    To confirm that the activation key is properly configured, enter the alex-person -Ls ST-9730 command to display the configured activation key.


    ATTENTION

    Your site may have already configured an ACSLS activation key. If so, first delete the old ACSLS activation key (alex-person -D ACSLS) and then enter the new ACSLS activation key (alex-person -C ACSLS).


  8. Configure library and tape devices in SAMS:Alexandria. If you are upgrading, you only need to complete this step if you changed the hardware configuration for the libraries or changed slpt_conf during the installation. Be sure you are familiar with the information about device configuration in the Backup Toolkit Administration Guide for SAMS:Alexandria before configuring devices. The following text only briefly describes device configuration.

    On a server host, this step involves using SetupHD.Seq or the Xalex graphical interface to configure devices for use by SAMS:Alexandria. For example, to automatically configure all directly-connected libraries (DDS-2, DDS-3, HP DLT4000, STK 9710/9730/L700), but not ACSLS-connected STK 9710/9740/L700 libraries in SAMS:Alexandria on a server host, enter the following command. The -d option runs SetupHD.Seq non-interactively.

    # /usr/alexbkup/bits/SetupHD.Seq -d


    ATTENTION

    The SetupHD.Seq command does not configure ACSLS-connected STK libraries; you can only use Xalex to do so. For more information, refer to Chapter 3, "Configure and Use ACSLS-Connected STK Libraries with SAMS:Alexandria," in the Backup Toolkit Administration Guide for SAMS:Alexandria.


    You might also want to use the -p option to define the library name prefix you want to use or use the -t option to designate the density type when using DLT tape drives. For details, refer to Chapter 2, "Configure Backup Devices," in the Backup Toolkit Administration Guide for SAMS:Alexandria.

    On a client host, configuring devices in SAMS:Alexandria involves using ClientHD or the Xalex graphical interface. For example, to configure devices interactively on a client host, enter the following command:

    # /usr/alexbkup/bits/ClientHD Host1

    On a client host, you might want to configure specific network interfaces for each network library. For details, refer to Chapter 2, "Configure Backup Devices," in the Backup Toolkit Administration Guide for SAMS:Alexandria.

  9. If this is a new installation on a server host, configure security and enable the Remote Home Node security option for each of the client hosts you plan to use.


    ATTENTION

    When configuring security for a client host, designate the TCP/IP network protocol.


    On the server host, complete this task as follows:

  10. If this is a new installation on a client host, configure security for the server host on the client host.


    ATTENTION

    When configuring security for a server host, designate the TCP/IP network protocol.


    On the client host, complete this task as follows:

  11. If you are installing on a client host and the system was not rebooted during the software installation, start the SAMS:Alexandria daemons on the client host by running the alex script. (The alex script is automatically run during a system reboot.)

    # sh /etc/init.d/alex start

  12. On new installations, configure SAMS:Alexandria daily housekeeping to print the drinfo.out file that is created by the systeminfo script. (The drinfo.out file contains critical system information that is required during a disaster recovery). The Backup Toolkit installalex script puts the systeminfo -B command in the House-Keeping-Begin-Command configuration option and the systeminfo -E command in the House-Keeping-End-Command configuration option.

    By default, the error messages and drinfo.out file are mailed to the users listed in the Mail-Default configuration option and the drinfo.out file is not printed. To print the drinfo.out file or mail this file to other users, change the systeminfo command that is in the House-Keeping-End-Command configuration option to include the -p or -m options. (The configuration of the Mail-Default option is described in the SAMS:Alexandria X Interface Guide.)

    For example, to configure housekeeping to print the drinfo.out file to the printer qms17 and mail it to root, alexbkup, and jones, use the following syntax in the House-Keeping-End-Command option:

    systeminfo -E -p qms17 -m root,alexbkup,jones

    If you are upgrading, the Backup Toolkit installalex script verifies that the House-Keeping-Begin-Command and House-Keeping-End-Command configuration options call the systeminfo script. If these options do not function, installalex configures them as described earlier. If these options are already configured to call systeminfo, then the installalex script does not change the configuration or the systeminfo options that are used.

    For more information about the systeminfo script, refer to the systeminfo(1M) man page or the discussion of disaster preparation in the Backup Toolkit Administration Guide for SAMS:Alexandria.

  13. On a new installation of SAMS:Alexandria, the installation is complete and you can test operations and begin configuring operation cards for backups. For more information, refer to the SAMS:Alexandria X Interface Guide or the SAMS:Alexandria Reference Guide.

    On an existing installation, complete the remaining steps in this procedure.


    ATTENTION

    After installation, prepare for a disaster recovery by creating a custom miniroot tape for that host with bktkbuildmini. Otherwise, you might be unable to recover the root, /usr, or SAMS:Alexandria filesystems in the event of a disk crash. Refer to the Backup Toolkit Administration Guide for SAMS:Alexandria for more information on disaster preparation.


  14. If there were any local site-specific customizations made to the systeminfo script, compare the newly installed systeminfo script with the previous systeminfo script that you saved to a secure location when preparing for the upgrade, for example, /usr/alexbkup/upgrade. Manually merge any customizations found in the previous script into the new systeminfo script.


    ATTENTION

    Do not overwrite the new systeminfo script with the previous systeminfo script. Changes have occurred to systeminfo that will not be reflected in previous versions. Instead, edit the new systeminfo script to contain any customizations your site requires.


  15. If you are upgrading from COBRA v4.00 to COBRA v4.50, manually migrate any store operation card template files to COBRA v4.50. When you upgrade SAMS:Alexandria, any COBRA operation cards in the SAMS:Alexandria database are updated for SAMS:Alexandria v4.50. However, template files are not updated by the SAMS:Alexandria installation. For more information, refer to "Upgrade Operation Card Template Files From COBRA v4.00 to COBRA v4.50" at the end of Chapter 4.

  16. If you changed the start time for SAMS:Alexandria daily housekeeping before you installed the software, restore the start time to its original time. You can determine the original housekeeping start time by examining the /usr/alexbkup/upgrade/option.out file that you created before the upgrade when you saved the configuration information. For example, to change the housekeeping start time back to 12:00 am, enter the following command:

    # alex-option -u House-Keeping-Time 00:00

  17. If you unmanaged (unscheduled) any operation cards that were scheduled to run during the installation time, manage (schedule) those operation cards. For example, to manage the operation card Root-Full, enter the following command with a 1 (one) at the end of the syntax:

    # alex-opcard -Um Root-Full 1

  18. On upgrade installations of SAMS:Alexandria, the directory HTTP in /usr/alexbkup is no longer needed and can be removed.

The upgrade installation of SAMS:Alexandria is now complete and you can test operations and begin configuring operation cards for backups. For more information, refer to the SAMS:Alexandria X Interface Guide or the SAMS:Alexandria Reference Guide.