Chapter 4
Install Backup Toolkit V4.4.3

This chapter discusses the installation of Backup Toolkit V4.4.3 and SAMS:Alexandria V4.50.70 on systems running DYNIX/ptx V4.4.4 and later maintenance releases, V4.5.x, or V4.6.x.


Software Installation and Upgrade Overview

IBM approved personnel will install Backup Toolkit and SAMS:Alexandria for all first-time customers. If the host already has Backup Toolkit and SAMS:Alexandria installed, you can perform the upgrade yourself with phone assistance from IBM Customer Support, if needed. Familiarize yourself with the following two sections before installing Backup Toolkit and SAMS:Alexandria.


ATTENTION

Be sure to read through the entire installation chapter before installing 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 library. In that case, before you perform the upgrade, be sure to review 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 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 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 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.



Software Installation Process Overview

The installation process comprises the following major steps:

[  ]

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

[  ]

For existing 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.

[  ]

Install the Backup Toolkit software. For details, refer to "Install the Backup Toolkit Software" 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 the Backup Toolkit Administration Guide for SAMS:Alexandria.


[  ]

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, and configuring devices. 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. For more information, refer to the discussion of disaster preparation in the DYNIX/ptx V4.4 System Recovery and Troubleshooting Guide, the DYNIX/ptx V4.5 System Recovery and Troubleshooting Guide, or the DYNIX/ptx V4.6 System Recovery and Troubleshooting Guide, as applicable.



Installation Caveats about Backup Toolkit

The following caveats apply to the installation of Backup Toolkit on DYNIX/ptx V4.4.4 and later maintenance releases, V4.5.x, and V4.6.x:

For more information about installation procedures on DYNIX/ptx V4.4.x, V4.5.x, and V4.6.x, refer to the appropriate version of the DYNIX/ptx V4.x.x and Layered Products Software Installation Release Notes.


Prepare for the Upgrade

If this is an existing installation, prepare for the upgrade and save configuration information before you update or reinstall Backup Toolkit and SAMS:Alexandria. Perform this procedure immediately before actually installing the 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 installations, continue with "Install the Backup Toolkit Software" later in this chapter.


ATTENTION

You can upgrade to Backup Toolkit V4.4.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 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 reinstallation. 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 reinstallation. 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 pending and active 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

Once you have prepared for the upgrade, continue with the procedure "Install Backup Toolkit."


Install Backup Toolkit

IBM approved personnel will perform all new installations of Backup Toolkit. If the host already has Backup Toolkit and SAMS:Alexandria installed, you can perform the upgrade to Backup Toolkit yourself with phone assistance from IBM Customer Support, if needed. Backup Toolkit uses is installed with ptx/INSTALL and uses standard installation processes.


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 the section "Reconfigure the Disaster Recovery Environment" in Chapter 2 of the DYNIX/ptx V4.4 System Recovery and Troubleshooting Guide, the DYNIX/ptx V4.5 System Recovery and Troubleshooting Guide, or the DYNIX/ptx V4.6 System Recovery and Troubleshooting Guide,as appropriate.



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 Backup Toolkit Administration Guide for SAMS:Alexandria.


Install the Backup Toolkit Software

To install the Backup Toolkit software package, 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 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.


  3. Ensure that the required layered products for SAMS:Alexandria are already installed or are going to be installed at the same time as Backup Toolkit. Refer to "Software Requirements" in Chapter 1 of these release notes for specific versions that should be installed.

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

    # su

  5. Follow the installation procedures in the DYNIX/ptx V4.x.x and Layered Products Software Installation Release Notes to install the Backup Toolkit software package.


    ATTENTION

    Immediately after Backup Toolkit V4.4.3 is installed, hosts running DYNIX/ptx V4.6.x must also install Fastpatch 253655 for Backup Toolkit V4.4.3. This fastpatch enables Backup Toolkit to install SAMS:Alexandria on a DYNIX/ptx V4.6.x host and provides other required changes to support DYNIX/ptx V4.6.x.

    For more information on the contents of this patch and installation instructions, refer to the README file distributed with the Fastpatch.


Once the Backup Toolkit software and Fastpatch 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 for installing or upgrading SAMS:Alexandria on DYNIX/ptx hosts. 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.

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. Change directories to /usr/backup_toolkit/alexandria. (You must run the script from within this directory.)

    # cd /usr/backup_toolkit/alexandria
  2. 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.

  3. 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.

  4. At the following prompt, enter 2 to designate that the host is running DYNIX/ptx V4.4.4 or later maintenance releases, DYNIX/ptx V4.5.x, or DYNIX/ptx V4.6.x. The hardware platform choice DYNIX/ptx V4.4 applies to all of these operating system versions.

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

    Would you like to run ./Install now (Y/N) ?
    
  6. 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.

  7. 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 for 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.

  8. 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 a line similar to the following to indicate this fact:

Tue May  2 16:23:29 PDT 2000 - Backup Toolkit V4.4.3 PN: 1003-75184-04_A00
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 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 that is appropriate for the version of DYNIX/ptx on your host.

  2. 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 hostname of the ACSLS server that controls the robotics for the STK library you plan to use.

  3. If this is a new installation on DYNIX/ptx V4.4.x or V4.5.x and you have not already done so, you must recompile the kernel and reboot the system. Otherwise, the kernel parameter changes made by Backup Toolkit will not be available.

    If this is a new installation on DYNIX/ptx V4.6.x, you should recompile the kernel before the next scheduled system reboot. You do not have to recompile and reboot immediately because the alex startup script dynamically makes the kernel parameter changes. These changes are not permanent across system boots, which is why you must eventually recompile the kernel.

  4. If you are installing on a server host and the system was not rebooted during the software installation or if you changed the 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.)

    # 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 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 either ST-9710, ST-9730, or ST-L700 for directly-connected STK 9710/9730/L700 libraries or ACSLS for ACSLS-connected STK 9710/9740/L700 libraries.

    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 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.

    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, enter the following command. The -d option runs SetupHD.Seq non-interactively.

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


    ATTENTION

    Do not use SetupHD.Seq -d to configure libraries for a SAMS:Alexandria server host in a clustered system unless all other nodes of the cluster are SAMS:Alexandria client hosts. SetupHD.Seq -d configures all libraries that can be seen from the host. If more than one node in the cluster is installed as a SAMS:Alexandria server, run SetupHD.Seq interactively or use the Xalex graphical interface to manually designate the libraries that will be exclusive to each server host.



    ATTENTION

    The SetupHD.Seq command does not configure ACSLS-connected libraries; you can only use Xalex to do so. For more information, refer to 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 on device configuration, refer to 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 device configuration 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 DYNIX/ptx V4.4 System Recovery and Troubleshooting Guide, the DYNIX/ptx V4.5 System Recovery and Troubleshooting Guide, or the DYNIX/ptx V4.6 System Recovery and Troubleshooting Guide,as appropriate.

  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 buildmini. Otherwise, you might be unable to recover the root, /usr, or SAMS:Alexandria filesystems in the event of a disk crash. Refer to the DYNIX/ptx V4.4 System Recovery and Troubleshooting Guide, the DYNIX/ptx V4.5 System Recovery and Troubleshooting Guide, or the DYNIX/ptx V4.6 System Recovery and Troubleshooting Guide, as appropriate, 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 this chapter.

  16. If you changed the start time for SAMS:Alexandria daily housekeeping before you reinstalled 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 option 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 have 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.


Upgrade Operation Card Template Files From COBRA v4.00 to COBRA v4.50

If you exported COBRA v4.00 store operation cards to files for use as templates or used the Backup Toolkit V4.2.0/4.4.0 cobra_cold or cobra_hot operation card template files to create customized template files, manually migrate these template files for COBRA v4.50. When you upgrade, any COBRA operation cards in the SAMS:Alexandria database are updated for SAMS:Alexandria v4.50. However, site-specific template files are not updated by the SAMS:Alexandria installation. The template files cobra_cold and cobra_hot have already been updated to COBRA V4.50.

If you use site-specific template files that were based on COBRA v4.00 to create operation cards without updating them for COBRA v4.50, store operations can fail or have unexpected results.

After SAMS:Alexandria 4.50.70 is installed, update site-specific template files as follows:

  1. Use the alex-xfer command to export any COBRA store operation cards that were created from site-specific template files. For more information on using the alex-xfer command to export COBRA operation cards, refer to the COBRA System Administration Guide.

  2. Compare the definitions of these exported operation cards to the original template files on which they were based.

  3. As appropriate, edit the newly exported operation card files to create new site-specific template files.

The following COBRA v4.00 keywords are not supported and are no longer needed by COBRA v4.50: