EMC® AlphaStor® Release 4.0 Installation Guide · EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 EMC® AlphaStor® Release 4.0 Installation Guide

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

EMC® AlphaStor®

Release 4.0

Installation GuideP/N 300-011-889

REV A01

EMC AlphaStor Release 4.0 Installation Guide2

Copyright © 2001 - 2011 EMC Corporation. All rights reserved.

Published July 28, 2011

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

ContentsContents

Contents

Preface

Chapter 1 Introduction Terminology............................................................................................................. 12 AlphaStor features .................................................................................................. 12 Installation requirements....................................................................................... 13

AlphaStor software component requirements ............................................. 13Third-party products installed with AlphaStor software........................... 14

Chapter 2 The AlphaStor Environment Plan the AlphaStor environment.......................................................................... 16

Device Manager not required for stand-alone devices ............................... 16Device Manager not required for NDMP servers........................................ 16

The AlphaStor communications flow.................................................................. 17 AlphaStor in a SCSI environment ........................................................................ 18 AlphaStor in a SAN environment ........................................................................ 18

SAN configurations.......................................................................................... 19Mixed SAN and LAN environments ............................................................. 19Configuring AlphaStor in a SAN environment ........................................... 20

Chapter 3 Supported Library Types ACSLS library environment .................................................................................. 24

ACSLS installation requirements ................................................................... 25 IBM 3494 library environment .............................................................................. 25

IBM 3494 installation requirements ............................................................... 26 ADIC/EMASS environment ................................................................................. 26

ADIC/EMASS supported libraries and interfaces ...................................... 27ADIC/EMASS requirements .......................................................................... 27

SCSI device environment....................................................................................... 27

Chapter 4 Installing on AIX Where to install the AlphaStor components....................................................... 30 Install the AlphaStor software on AIX................................................................. 30 Verify the AlphaStor installation .......................................................................... 32

EMC AlphaStor Release 4.0 Installation Guide 3

Contents

Update the AlphaStor software............................................................................. 32Where to find patches and updates................................................................ 32Update the AlphaStor software ...................................................................... 32

Uninstall the AlphaStor software on AIX............................................................ 33Review the installed AlphaStor software ...................................................... 33Uninstall the AlphaStor software ................................................................... 33

Chapter 5 Installing on HP-UX Where to install the AlphaStor components ....................................................... 36 Install the AlphaStor software on HP-UX ........................................................... 36

Install AlphaStor software on HP-UX............................................................ 36 Verify the AlphaStor installation........................................................................... 38 Update the AlphaStor software............................................................................. 38

Where to find patches and updates................................................................ 39Update the AlphaStor software ...................................................................... 39

Uninstall the software on HP-UX ......................................................................... 40Review the installed AlphaStor software ...................................................... 40Uninstall the software ...................................................................................... 40

Chapter 6 Installing on IRIX and Tru64 UNIX Where to install the AlphaStor components ....................................................... 42 Install the AlphaStor software on IRIX and Tru64 ............................................. 42 Verify the AlphaStor installation........................................................................... 44 Update the AlphaStor software............................................................................. 45


Chapter 7 Installing on Linux Where to install the AlphaStor components ....................................................... 48 Install the AlphaStor software on Linux.............................................................. 48 Verify the AlphaStor installation........................................................................... 50 Update the AlphaStor software............................................................................. 50


Uninstall the AlphaStor software ......................................................................... 52Review the installed AlphaStor programs .................................................... 52Review the AlphaStor installation details ..................................................... 52Uninstall the software ...................................................................................... 52

Chapter 8 Installing on Solaris Where to install the AlphaStor components ....................................................... 54 Install the AlphaStor software on Solaris ............................................................ 54 Verify the AlphaStor server installation............................................................... 57 Update the AlphaStor software............................................................................. 57


Uninstall the AlphaStor software on Solaris ....................................................... 58Review the installed AlphaStor programs .................................................... 58Review the AlphaStor installation details ..................................................... 58Uninstall the software ...................................................................................... 59

Install the software in a Sun Cluster Version 3.1 or 3.2 environment.............. 59Installation requirements for Sun Cluster ..................................................... 59


Contents

Migrate an existing AlphaStor server to a Sun Cluster environment on the same host..................................................................................................... 60Install an AlphaStor virtual server................................................................. 61

Uninstall the AlphaStor Sun Cluster software ................................................... 62

Chapter 9 Installing on Microsoft Windows Where to install the AlphaStor software ............................................................. 64 Install the AlphaStor software on Windows....................................................... 64 Verify the AlphaStor server installation .............................................................. 72 Update the AlphaStor software on Windows..................................................... 73

Where to find patches and updates ............................................................... 73Update the AlphaStor software...................................................................... 74

Uninstall the AlphaStor software on Windows.................................................. 74

Chapter 10 Start and Stop the AlphaStor Services Start and stop the AlphaStor services.................................................................. 76

Start and stop AlphaStor services on Microsoft Windows......................... 76 Commands to start and stop AlphaStor services............................................... 76 Start and stop ACSLS communication servers................................................... 77

Glossary

Index


Contents


Preface

As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

If a product does not function properly or does not function as described in this document, please contact your EMC representative.

Audience This guide is part of the AlphaStor documentation set, and is intended for use by the following audiences:

◆ System administrator during installation and configuration of the AlphaStor software.

Readers of this guide are expected to be familiar with the following topics:

◆ Operation of media storage libraries and devices.◆ Configuration of NetWorker or other data mover servers and storage nodes.◆ Media lifecycle procedures.

Related documentationRelated documents include:

EMC AlphaStor Release 4.0 Administration and Operation Guide

EMC AlphaStor Release 4.0 Planning Guide

EMC AlphaStor Release 4.0 Release Notes

EMC AlphaStor Release 4.0 Command Reference Guide

EMC AlphaStor Release 4.0 Hardware Compatibility Guide

EMC NetWorker Administration Guide

EMC Information Protection Software Compatibility Guide

Conventions used in this guideEMC uses these conventions for notes, cautions, warnings, and danger notices.

Note: A note presents information that is important, but not hazard-related.


Preface

IMPORTANT

An important notice contains information essential to software or hardware operation.

Typographical conventionsEMC uses the following type style conventions in this document:

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of windows, dialog boxes, buttons,

fields, and menus)• Names of resources, attributes, pools, Boolean expressions, buttons, DQL

statements, keywords, clauses, environment variables, filenames, functions, utilities

• URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, notifications

Bold: Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs, processes, services,

applications, utilities, kernels, notifications, system call, man pages

Used in procedures for:• Names of interface elements (such as names of windows, dialog boxes, buttons,

fields, and menus)• What user specifically selects, clicks, presses, or types

Italic: Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier: Used for:• System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when shown outside of

running text

Courier bold: Used for:• Specific user input (such as commands)

Courier italic: Used in procedures for:• Variables on command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from the example


Preface

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information- For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support- For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to:

[email protected]

If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the revision (for example, A01), the page numbers, and any other details that will help us locate the subject you are addressing.


http://powerlink.emc.com

Preface


1

This chapter provides background information on the EMC AlphaStor software, and includes the following sections:

◆ Terminology ................................................................................................................... 12◆ AlphaStor features ........................................................................................................ 12◆ Installation requirements ............................................................................................. 13

Introduction

Introduction 11

Introduction

TerminologyThe following list describes some of the terminology and conventions used in this guide. For a complete list, see the “Glossary”.

◆ Application refers to a data mover application.

◆ Data mover refers to backup software, such as NetWorker server.

◆ Device refers to the mechanism, usually a tape drive, that accesses the contents of a volume. Devices appear to the host as normal drives configured under UNIX. The devices appear on the SCSI bus and have unique SCSI IDs.

◆ Library is the general term that refers to an automated media storage unit, such as an autochanger, autoloader, carousel, datawheel, jukebox, or robot.

◆ Library control module refers to the proprietary library software that receives commands from the AlphaStor® software to manipulate the arms, devices, or mailboxes. Typically, the library control module uses SCSI communication.

◆ Mailbox is the access opening through which physical media volumes are inserted into and removed from a library.

◆ Robot arm is the mechanism that moves volumes to and from the devices.

◆ Volume is a unit of removable storage media, generally a magnetic tape.

AlphaStor featuresThe AlphaStor product is a complete suite of software applications designed to automate media lifecycle, library, and SAN management. AlphaStor software provides the following features:

◆ Library sharing across multiple datazones.

• Management of tape and other removable storage media.

• Tape lifecycle management with tape location tracking and tape pool management.

• Automation and management of media devices and robotic libraries.

◆ Dynamic drive sharing.

• Coordination of device requests in a SAN, LAN, or server-attached environment.

• Support of media device, robotic library, and SAN components.

• Assignment and management of devices (resources) for configured media pools.

◆ Third-party data mover support.

• Support for backup software (data mover) products that require removable storage media for archiving.

• Tracking and reporting of media and device usage.


Introduction

Installation requirementsThe following requirements must be met:

◆ The AlphaStor server must be installed on a supported Microsoft Windows, Solaris or Linux operating system.

◆ The AlphaStor Library Manager software and AlphaStor Device Manager software must be installed on a supported Microsoft Windows, UNIX, or Linux operating system.

◆ Libraries used in the AlphaStor environment must support barcodes.

Note: On Windows, JRE version 1.6.0_03 must not be installed before installing AlphaStor. JRE version 1.6.0_03 is installed with the AlphaStor software installation.Also, on Windows, the AlphaStor database process listens on TCP/IP loopback port 2693 to support Windows Terminal Services. Ensure that this port is not used by another application. The NetWorker NMC software does not conflict with this port.

Current details on operating systems and versions are available in the EMC Information Protection Software Compatibility Guide, available on Powerlink at Home > Support > Interoperability and Product Lifecycle Information > Compatibility Guides.

Note: NetWorker jbconfig on Solaris 10i does not currently support AlphaStor.

AlphaStor software component requirements

Table 1 on page 13 lists the AlphaStor server, DCP, LCP, and CLI component system requirements. The specific operating system documentation provides complete details.

The filesystem that contains the AlphaStor server data directory (ASHOME) should have at least 2 GB available. Disk space requirements may be greater depending on the number of configured devices, hosts and volumes, as well as the frequency of AlphaStor database and event log truncations. A minimum 10 GB of additional disk space should be available when debug tracing is enabled.

Table 1 AlphaStor component system requirements

AlphaStor component Minimum system requirements Recommended

Server Minimum operating system requirements plus additional 256 MB of RAM

512 MB of RAM for AlphaStor use

Device Manager Minimum operating system requirements -

Library Manager Minimum operating system requirements -

CLI Minimum operating system requirements -

Installation requirements 13

Introduction

Third-party products installed with AlphaStor software

The following third-party products are used in the AlphaStor environment, and are provided by the AlphaStor installation:

◆ Apache Web Server — Implements the HTTP protocol.

◆ Java Runtime Environment (JRE) — Enables Java technology in AlphaStor.

◆ Sybase SQL Anywhere — Provides the database structure for media management.

◆ gethostnames — A Sun Cluster utility routine. It can only be installed on Solaris hosts that already have Sun Cluster installed.


2

This chapter provides information on the environments supported by the AlphaStor product and where to install the AlphaStor component modules. It includes the following sections:

◆ Plan the AlphaStor environment ................................................................................ 16◆ The AlphaStor communications flow ........................................................................ 17◆ AlphaStor in a SCSI environment............................................................................... 18◆ AlphaStor in a SAN environment............................................................................... 18

The AlphaStorEnvironment

The AlphaStor Environment 15

The AlphaStor Environment

Plan the AlphaStor environmentAs you plan the AlphaStor environment, consider the role of each host computer. Table 2 on page 16 provides guidelines on where to install the AlphaStor software components (modules).

Device Manager not required for stand-alone devicesThe Device Manager (DCP) software is not required on a system that is configured with only stand-alone devices. AlphaStor can track media that is used in a stand-alone device, but AlphaStor cannot help the data mover software automatically mount and unmount volumes in a device that does not have a robotic arm.

Device Manager not required for NDMP serversThe Network Data Management Protocol (NDMP) is a standards-based, client/server protocol that allows any storage management application, such as NetWorker software, to control backup operations on a network. This same architecture is also used for the control and management of network-attached backup devices, such as tape drives.

NDMP compliant hosts can be detected by pinging the NDMP port (10000) for a response. This verification can be done either manually or during library configuration by using the auto-detect feature of the AlphaStor Library Configuration Wizard.

If it is determined that an NDMP server has access to the devices in the library, then the Device Manager (DCP) software is not required to be installed on that server because the NDMP server can manage the devices.

AlphaStor provides the ability to share a single device between NDMP and non-NDMP servers.

More information about using NDMP with NetWorker software is available in the EMC NetWorker Administration Guide.

Table 2 Where to install the AlphaStor software components

AlphaStor component Where to install

AlphaStor Server A host with sufficient memory, disk space, and communications.The AlphaStor server can be installed on Microsoft Windows, Linux or Solaris only.

AlphaStor Library Manager(Library Control Program)

A host with a control path to the robotic arm of one or more libraries.

AlphaStor Device Manager(Device Control Program)

On each NetWorker storage node and any other host that requires access to an AlphaStor-managed device.

Command Line Interface (CLI) Any system where CLI commands will be entered. The CLI component should also be installed on the AlphaStor server host.

AlphaStor Server Sun Cluster Agent

Any Sun Cluster nodes that will host the server.



The AlphaStor communications flowThe AlphaStor server is the control point for all AlphaStor activities. The following steps describe the flow of communication between each of the AlphaStor components for a read or write operation, as illustrated in Figure 1 on page 17.

Note: This same communication process is used for AlphaStor CLI commands and AlphaStor Operations Center commands.

1. The data mover (in this example, NetWorker software) contacts the AlphaStor server to request a mount operation.

2. The AlphaStor server contacts the AlphaStor Library Manager (robotd) to perform the mount operation.

3. When the volume is mounted, the AlphaStor server returns the device path to the data mover, which performs the read or write operation using the provided device path.

4. If data was written to the volume, the data mover notifies the AlphaStor server, which starts the volume's rotation cycle.

5. The data mover contacts the AlphaStor server to request an unmount operation.

6. The AlphaStor server contacts the AlphaStor Device Manager (rrobotd) to eject the volume if necessary.

7. The AlphaStor server contacts the AlphaStor Library Manager (robotd) to complete the unmount operation.

Figure 1 The AlphaStor communications flow

AlphaStor Server NetWorker Server

AlphaStor Server

NetWorkerServer

LibraryManager

DeviceManager

NetWorkerResourceDatabase

NetWorkerMedia

Database

AlphaStorMedia Manager

Database

Library

GEN-001681

robotd

rrobotd

1, 4, 5

6 6

3

2, 7 2, 7

3

The AlphaStor communications flow 17


AlphaStor in a SCSI environmentIn an environment that is configured with SCSI connections to the library, install the Device Manager and Library Manager software as follows:

◆ Install the Device Manager software on each host (typically a NetWorker storage node) that has a direct SCSI data path to one or more of the drives in the library.

◆ Install the Library Manager software on the host with the SCSI control path to the library media changer. The Library Manager issues commands for library operations, such as mount or unmount.

Figure 2 on page 18 illustrates an example of the AlphaStor software deployment in a SCSI environment.

Figure 2 AlphaStor software deployed in a SCSI environment

AlphaStor in a SAN environmentA SAN environment is a high performance, storage-dedicated, fiber-optic channel network. It provides any-to-any connectivity, where potentially any host can communicate with any storage device, such as a disk or tape drive.

Like a LAN or WAN environment, a SAN uses switches, hubs, routers, and bridges. A SAN enables storage activities to be externalized from the server in a LAN to this separate subnetwork. The SAN bypasses the usual storage activity bottlenecks and supports direct, high-speed data movement. This allows users to share storage resources and eases the task of centralized management.

DeviceManagers

Library ManagerDevice Manager

AutomatedTape Library

TCP/IPPublic Network

Data Paths

Control Path

Data Path



SAN configurations

SAN configurations can be grouped into two categories, multiplexed and switched.

Multiplexed configurationsIn multiplexed SAN configurations, drives appear to be attached to all of the hosts simultaneously. Any host may access the drives at any time. This configuration includes:

◆ Shared SCSI busses

◆ SCSI multiplexors

◆ Fiber switches

◆ Fiber-arbitrated loop hubs

Switched configurationsIn a switched configuration, drives appear to be attached to only one host at a time. The drives can be accessed by the host to which they are connected through the switch. This category includes:

◆ SCSI switches

◆ Dynamic fiber-arbitrated loop hubs

IMPORTANT

Sony AIT drives have a physical switch to identify the operating system to which they are connected. This limits their use in a heterogeneous SAN environment. AlphaStor software must be configured so that AIT drives are not shared among different types of operating systems.

Mixed SAN and LAN environmentsA SAN is not a replacement for storage attached to servers in a LAN. Enterprise environments that require backups of large databases or backups of application servers are a natural fit for a SAN implementation. However, in some cases, workstation clients and small departmental servers may not need to be directly connected to the SAN because data volumes do not necessitate a fiber channel connection. Although it is possible for these smaller clients to back up directly to SAN devices, it may be more practical to continue to back up over the LAN, without putting unnecessary strain on the LAN bandwidth.

Given these considerations, it is likely that most organizations will have a mixed environment of interconnected LAN and SAN technologies. Therefore, the storage management software product must centrally manage all servers and storage devices, whether they are physically connected to the LAN, WAN, or the SAN. AlphaStor supports both network and direct-attached storage devices. This allows organizations to use a single product to manage their current LAN environments, and as they deploy SAN technologies.

AlphaStor in a SAN environment 19


Configuring AlphaStor in a SAN environment

A SAN environment is configured by sharing library devices among multiple hosts. To configure the AlphaStor environment, you can run the Library Configuration Wizard and assign multiple host connections to a single device within a library. The wizard automatically detects the number of devices in a library and prompts you for information specific to each device. For details on assigning host connections, refer to the EMC AlphaStor Release 4.0 Administration and Operation Guide.

Additionally, to configure NetWorker software in the SAN environment, you must also run the jbconfig command and specify all hosts connected to the devices. For details on the jbconfig command, refer to the section on creating a virtual library in the EMC AlphaStor Release 4.0 Administration and Operation Guide.

Figure 3 on page 21 illustrates a mixed storage environment that includes a SAN. Although in this illustration the AlphaStor server is not connected to the SAN cabling, it communicates with the Library Manager to perform volume movement activities. The AlphaStor Library Manager and Device Manager components are deployed in the SAN environment as follows:

◆ The Library Manager component resides on any one of the hosts that participate in the SAN because they all have access to the robotic arm.

◆ A Device Manager component resides on each host that participates in the SAN because each host requires access to the drives in the library.

Note: Normally, volumes cannot be shared across multiple datazones. Volume sharing across datazones is supported only under the direction of AlphaStor Professional Services or Technical Support.



Figure 3 AlphaStor deployed in a mixed environment including a SAN

TCP/IPPublic

NetworkControl Paths

Data Paths

SAN

AlphaStor Server

Install:- AlphaStor Server

Data Zone 1NetWorker Server

Install:- Library Manager- Device Manager

Data Zone 2NetWorker Server

Install:- Device Manager

NetWorkerStorage Node

Stand-AloneDevices

Third-PartyData Mover

Install:- Library Manager- Device Manager- Command Line Interface (CLI)

Library 1

GEN-001680

Library 2

AlphaStor in a SAN environment 21



3

The AlphaStor software does not communicate directly with a non-SCSI library, but communicates indirectly through the proprietary controller software for the library.

The AlphaStor product currently supports several types of controller-based libraries, which are described in the following sections:

◆ ACSLS library environment ........................................................................................ 24◆ IBM 3494 library environment .................................................................................... 25◆ ADIC/EMASS environment........................................................................................ 26◆ SCSI device environment ............................................................................................. 27

Supported LibraryTypes

Supported Library Types 23

Supported Library Types

ACSLS library environmentFor optimal performance in an STK Automated Cartridge System Library Software (ACSLS) environment, install the AlphaStor Library Manager software on the ACSLS server. This is a co-hosted environment. The Library Configuration Wizard needs to be told that the configuration is co-hosted.

Note: If the Library Manager (LCP) software and the ACSLS server must reside on separate systems, there must not be a firewall between them.

IMPORTANT

The ACSLS mailbox should be set to manual mode instead of automatic mode. If the mailbox is set to automatic mode, then AlphaStor import operations do not succeed. The ACSLS documentation provides information on how to set the mailbox mode.

In an ACSLS environment, communication occurs as follows:

1. The AlphaStor server sends requests, such as volume mount or unmount commands, to the Library Manager host through TCP/IP communication.

2. The Library Manager host receives the requests and issues commands to the ACSLS server through RPC communication.

3. The ACSLS server software moves the robot arm and maintains its own volume database.

Figure 4 on page 24 illustrates a typical AlphaStor ACSLS configuration.

Figure 4 AlphaStor software in a co-hosted ACSLS environment

Device Manager

TCP/IP

Data Path

Control Path

AlphaStor Server

Powderhorn, WolfCreek97xx, or L Series Library GEN-001691

Library ManagerACSLS Server



Figure 5 on page 25 illustrates a typical AlphaStor non co-hosted configuration.

Figure 5 AlphaStor software in a non co-hosted environment

ACSLS installation requirementsThe following software and hardware requirements must be met before installing AlphaStor Library Manager (LCP) software for ACSLS:

◆ ACSLS 5.3 or later

◆ A supported Solaris or AIX operating system. Current information is available in the Information Protection Software Compatibility Guide.

Note: In a LibraryStation environment, the AlphaStor Library Manager software requires a Solaris operating system. The LibraryStation server runs on an IBM MVS mainframe computer. The AlphaStor Library Manager cannot be co-hosted in a LibraryStation environment.

Information on starting and stopping ACSLS services is available at “Start and stop ACSLS communication servers” on page 77.

IBM 3494 library environmentIn an IBM 3494 library environment, the AlphaStor Library Manager software must be installed on the same system as the IBM server for the library. The IBM server runs on a Microsoft Windows, Solaris, AIX, or HP-UX operating systems.

In an IBM 3494 environment, communication occurs as follows:

1. The AlphaStor server sends requests, such as tape mount or unmount commands, to the Library Manager host through TCP/IP communication.

2. The Library Manager software receives the requests and issues commands to the IBM server through RPC communication or system calls on AIX.

3. The IBM server communicates with the IBM 3494 library by using TCP/IP.

Note: All communication with the IBM 3494 library is either TCP/IP or serial-based.

TCP/IP

Device Manager

Data Path

Control Path

AlphaStor ServerLibrary Manager

Powderhorn or WolfCreek Library

LibraryStation (MVS)

GEN-001693

IBM 3494 library environment 25


4. The AlphaStor server sends requests, such as tape eject commands, to the Device Manager host through TCP/IP communication.

Figure 6 on page 26 illustrates a typical AlphaStor IBM 3494 configuration.

Figure 6 AlphaStor software in an IBM 3494 environment

IBM 3494 installation requirements

It is required that a supported Microsoft Windows, Solaris SPARC, AIX, or HP-UX PA-RISC operating system is installed before installing AlphaStor Library Manager (LCP) software in an IBM 3494 environment:

Current information is available in the EMC AlphaStor Release 4.0 Hardware Compatibility Guide.

ADIC/EMASS environmentIn an ADIC/EMASS environment, the DAS server is located inside the library as illustrated in Figure 7 on page 27.

Note: Due to RPC communications, the path between the AlphaStor Library Manager software and the DAS server cannot be configured through a firewall.

In an ADIC/EMASS environment, communication occurs as follows:

1. The AlphaStor server sends requests, such as tape mount or unmount commands, to the Library Manager host through TCP/IP communication.

2. The Library Manager software receives the requests and issues commands to the DAS server through RPC communication.

3. The DAS server software converts the Library Manager calls into Archive Management Unit (AMU) requests.

4. The AMU software moves the robot arm and maintains its own volume database.

5. The AlphaStor server sends requests, such as tape eject commands, to the Device Manager host through TCP/IP communication.

TCP/IP

Device Manager

Data Path

TCP/IP or Serial


IBM Server

IBM 3494 LibraryGEN-001694



Figure 7 AlphaStor software in an ADIC/EMASS environment

ADIC/EMASS supported libraries and interfacesThere are two types of supported ADIC/EMASS libraries:

◆ The Scalar 1000 series library. The Scalar 1000 series can be controlled by either the DAS software interface or a SCSI interface.

◆ The AML series library (AML/J, AML/E, or AML/2). The AML series can be controlled only by the DAS server software interface.

ADIC/EMASS requirementsA supported AIX, HP-UX PA-RISC, or IRIX operating system must be installed before installing AlphaStor Library Manager (LCP) software for ADIC/EMASS.

Current information is available in the EMC AlphaStor Release 4.0 Hardware Compatibility Guide.

SCSI device environmentThe AlphaStor Hardware Compatibility Guide available on EMC Powerlink provides complete details on supported SCSI devices.

TCP/IP

Device Manager

Data Path

RPCs


Scalar 1000 orAML-Series Library

DAS Server and Archive Management Unit (AMU)located inside the library

GEN-001692

SCSI device environment 27



4

Use the information in this chapter to install AlphaStor software on AIX systems. This chapter contains the following sections:

◆ Where to install the AlphaStor components ............................................................. 30◆ Install the AlphaStor software on AIX ....................................................................... 30◆ Verify the AlphaStor installation................................................................................. 32◆ Update the AlphaStor software................................................................................... 32◆ Uninstall the AlphaStor software on AIX.................................................................. 33

Note: Root privileges are required to install the AlphaStor software.

Installing on AIX

Installing on AIX 29

Installing on AIX

Where to install the AlphaStor componentsTable 2 on page 16 describes where to install the AlphaStor software components.

Note: The AlphaStor server can be installed on Solaris, Linux and Microsoft Windows.

Install the AlphaStor software on AIXThe AlphaStor software filesets that can be installed on AIX are as follows:

◆ lgtoas.cli — The AlphaStor CLI client software.

◆ lgtoas.dcp — The AlphaStor Device Manager (DCP) software.

◆ lgtoas.lcp — The AlphaStor Library Manager (LCP) software.

To install the AlphaStor software on an AIX host:

1. Log in as root.

2. Launch a terminal or console window.

3. Change to the directory containing the AlphaStor software package, or if you have an installation CD-ROM, change to the software package directory on the CD-ROM.

4. Start the installation with the following command for each fileset name:

installp -a -d . fileset_name

For example, to install only the Library Manager (LCP) component:

installp -a -d . lgtoas.lcp

Note: If a previously installed version of the fileset exists, installp will perform a software update.

The package files are installed in a fixed directory /opt/as, and this location cannot be changed since AIX packages are not relocatable. However, the data file directory location (ASHOME) is maintained automatically when performing software updates. If a previously installed version of AlphaStor software does not exist, then /var/as is used as the data directory.

5. Run the configuration script for each fileset that was installed. The following configuration scripts are available:

• /opt/as/install/ascli_config - for AlphaStor CLI client software.

• /opt/as/install/asdcp_config - for AlphaStor Device Manager (DCP) software.

• /opt/as/install/aslcp_config - for AlphaStor Library Manager (LCP) software.


Installing on AIX

Respond to the prompts for each script:

a. If prompted, enter the hostname of the robot server. The robot server is the system on which you plan to install the Library Manager (LCP) software to control the library robot arm.

b. Press [Enter] to accept the default port number for the rrobotd daemon (3000), or type a different value.

c. Press [Enter] to accept the default port number for the robotd daemon (3500), or type a different value.

Note: The robotd and rrobotd port numbers are used for communication by the AlphaStor Library Manager (LCP) and the AlphaStor Device Manager (DCP), respectively.

The following is a sample installation session on an AIX operating system:

Example 1 AlphaStor installation on an AIX system

installp -a -d . lgtoas.lcp...installp progress...NOTE: To complete the configuration, please execute the following script

as root: /opt/as/install/aslcp_config...installp summary...

/opt/as/install/aslcp_config

The service rrobotd already exists in /etc/services. The entry is:

rrobotd 3000/tcp # Listen socket for clients Date=2011-02-01

Do you want to replace the entry (y/[n])? n

The service robotd already exists in /etc/services. The entry is:

robotd 3500/tcp # Listen for client requests Date=2011-02-01


Installation successful

6. Start the AlphaStor daemons as described in“Start and stop the AlphaStor services” on page 76.

If the Device and Library Manager components are installed, they will be started automatically when the system is rebooted.

The EMC AlphaStor Release 4.0 Administration and Operation Guide provides configuration instructions when the installation completes.

Install the AlphaStor software on AIX 31

Installing on AIX

Verify the AlphaStor installationTo verify the AlphaStor installation on AIX:

1. Run the following for each fileset name to verify:

lppchk -f fileset_name

2. Ensure that the /opt/as directory exists and that it contains files.

3. After the AlphaStor DCP and LCP daemons have been started, verify that the daemons are running by entering the following command:

ps -ef | grep robotd

Look for daemons such as:

• rrobotd - the DCP daemons.

• robotd - the LCP daemons.

Update the AlphaStor softwareThis section describes where to find patches and updates, and how to update the AlphaStor software.

Where to find patches and updates

Check for patches or updates that might be available for this product on Powerlink, at:


Navigate to Home > Support > Software Downloads and Licensing > Downloads A-B > AlphaStor.

Update the AlphaStor softwareTo update AlphaStor software to a newer version or patch:

1. Verify the current AlphaStor server and Library Manager versions. “Review the installed AlphaStor software” on page 33 provides details.

2. Back up the AlphaStor ASHOME directory.

3. If upgrading from AlphaStor 3.x, additional steps must be performed. Otherwise, skip to step 4 . AlphaStor 3.x packages are not in the AIX native package format. As a result, the following preparation is required to upgrade from AlphaStor 3.x:

a. Stop the AlphaStor 3.x DCP and LCP daemons manually.

b. Remove or disable any customized mechanisms that are used to start and stop the 3.x DCP and LCP daemons.

c. Remove the 3.x executable files (in the software bin directory) since they might interfere or be confused with the new package files.



Installing on AIX

4. Install the updated version of AlphaStor as described in “Install the AlphaStor software on AIX” on page 30.

5. Download applicable AlphaStor patches or hot fixes, if necessary. For each patch:

a. Read the associated readme.txt file.

b. Follow the instructions to apply the patch.

6. If the Library Manager (LCP) was upgraded from version 3.0 or earlier, reconfigure the updated library as follows:

a. On the updated AlphaStor server, run the Library Configuration Wizard.

b. Right-click the updated library and select Reconfigure Library.

Note: The library reconfiguration process can take up to ten minutes.

Uninstall the AlphaStor software on AIXReview the installed AlphaStor software components and installation details before uninstalling the AlphaStor software.

Review the installed AlphaStor software

To review all the AlphaStor filesets installed on an AIX system, enter the following command:

lslpp -l "lgtoas*"

The screen displays the installed AlphaStor filesets, for example:

lgtoas.cli.rte 4.0.0.0 COMMITTED AlphaStor Command Line Interfacelgtoas.dcp.rte 4.0.0.0 COMMITTED AlphaStor Device Managerlgtoas.lcp.rte 4.0.0.0 COMMITTED AlphaStor Library Manager

Uninstall the AlphaStor softwareTo uninstall AlphaStor software components, type the installp -u command and provide the names of AlphaStor components to uninstall as arguments to the command. For example:

◆ To remove all AlphaStor filesets, enter this command:

installp -u lgtoas

◆ To remove the AlphaStor CLI component only, enter the following command:

installp -u lgtoas.cli

Uninstall the AlphaStor software on AIX 33

Installing on AIX


5

Use the information in this chapter to install AlphaStor software on HP-UX systems. This chapter contains the following sections:

◆ Where to install the AlphaStor components ............................................................. 36◆ Install the AlphaStor software on HP-UX ................................................................. 36◆ Verify the AlphaStor installation................................................................................. 38◆ Update the AlphaStor software................................................................................... 38◆ Uninstall the software on HP-UX ............................................................................... 40


Installing on HP-UX

Installing on HP-UX 35

Installing on HP-UX


Note: The AlphaStor server can be installed on Solaris, Linux, and Microsoft Windows.

Install the AlphaStor software on HP-UXThis section describes and gives examples of how to install AlphaStor software components on HP-UX.

Install AlphaStor software on HP-UX

These are the AlphaStor software components (sub-products) that can be installed on HP-UX:

◆ AlphaStor.cli — The AlphaStor CLI client software.

◆ AlphaStor.dcp — The AlphaStor Device Manager (DCP) software.

◆ AlphaStor.lcp — The AlphaStor Library Manager (LCP) software.

To install the AlphaStor software on an HP-UX host:

1. Log in to the system as root.


3. Start the installation with the following command:

swinstall -s source -x ask=true software_selection

where:

• source is the full path to the location of the distribution depot file (AlphaStor.pkg)

• software_selection is either the product name AlphaStor, or a list of sub-products to be installed.

If a previously installed version of AlphaStor software exists, swinstall will perform a software update. The -x ask=true option can be omitted on updates. In this case, swinstall will run in non-interactive mode and automatically maintain existing AlphaStor configuration settings. The package files are installed in /opt/as by default.

4. If required, add the following to the software_selection argument to relocate the package file directory during installation:

,l=package_dir

For example:

• To install or update all AlphaStor software components:

swinstall -s /SD_CDROM/AlphaStor.pkg -x ask=true AlphaStor


Installing on HP-UX

• To install only the Library Manager (LCP) component, and relocate package files to /usr/local/as:

swinstall -s /SD_CDROM/AlphaStor.pkg -x ask=true AlphaStor.lcp,l=/usr/local/as

The data file directory location (ASHOME) is determined automatically when performing software updates, or provided explicitly during interactive installs.

If a non-interactive installation is performed when a previously installed version of AlphaStor software does not exist, then /var/as is used as the data directory, and other configuration options assume their default values.

Note: The AlphaStor software configuration options can be reconfigured at any time after the installation is complete by using swconfig. These configuration options affect all AlphaStor components. Typically, swconfig is used after a non-interactive installation, or to change the AlphaStor server and Library Manager host names. Run the swconfig command as follows: swconfig -x reconfigure=true -x ask=true AlphaStor

5. For interactive installations, respond to the prompts as follows:

a. Press Enter to accept the default data directory location (ASHOME), or type a different directory name.

b. If prompted, type the hostname of the robot server.

The robot server is the system on which you plan to install the Library Manager (LCP) software to control the library robot arm.

c. Press Enter to accept the default port number for the rrobotd daemon (3000), or type a different value.

d. Press Enter to accept the default port number for the robotd daemon (3500), or type a different value.

Note: The robotd and rrobotd port numbers are used for communication by the AlphaStor Library Manager (LCP) and the AlphaStor Device Manager (DCP), respectively.

Example 2 AlphaStor installation on an HP-UX system

The following is a sample installation session on an HP-UX operating system:

swinstall -s /SD_CDROM/AlphaStor.pkg -x ask=true AlphaStor ...swinstall informational messages... The directory entered here will have '/as' appended to it if it does not already end in '/as'. The install process will not allow /as/as, //as, etc. The data directory contains product configuration, data and log files. By default, the data directory is /var/as on new installations, and it remains unchanged on upgrades. Enter the directory for the data files: [keep current] /var/as CLI Configuration ================= By default, the command line utilities expect the AlphaStor server to be available on the local host, unless the AS_HOST setting in the asenv file specifies otherwise. Enter the host name of the AlphaStor server: [keep current] jupiter DCP Configuration ================= By default, the Device Manager (rrobotd) sends log messages to the Library Manager (robotd) on the local host, unless the

ROB_REMOTE_ROBOT

Install the AlphaStor software on HP-UX 37

Installing on HP-UX

setting in the asenv file specifies otherwise. Enter the host name of the robotd server: [keep current] [enter] If robotd and rrobotd port numbers are not already configured in /etc/services, then, by default, they are set to 3500 and 3000, respectively. If the ports are already configured, then they are not modified by default. If non-default port numbers are used, then the same port numbers must be used on all hosts. Enter the port number for robotd [keep current]: [enter] Enter the port number for rrobotd [keep current]: [enter] LCP Configuration ================= If robotd and rrobotd port numbers are not already configured in /etc/services, then, by default, they are set to 3500 and 3000, respectively. If the ports are already configured, then they are not modified by default. If non-default port numbers are used, then the same port numbers must be used on all hosts. Enter the port number for robotd [keep current]: [enter] Enter the port number for rrobotd [keep current]: [enter] ...swinstall informational messages...

6. Restart the AlphaStor daemons as described in“Start and stop the AlphaStor services” on page 76. If the Device and Library Manager components are installed, they will start automatically when the system reboots.

The EMC AlphaStor Release 4.0 Administration and Operation Guide provides configuration instructions when the installation completes.

Verify the AlphaStor installationTo verify the AlphaStor installation on HP-UX:

1. Use swverify to verify the package integrity:

swverify AlphaStor




• rrobotd - the DCP daemons

• robotd - the LCP daemons



Installing on HP-UX

Where to find patches and updates

Check for patches or updates that might be available for this product on Powerlink, at:



Update the AlphaStor software

To update the AlphaStor software:

1. Verify the current AlphaStor server and Library Manager versions as described in “Review the installed AlphaStor software” on page 40.

2. Back up the AlphaStor directory.

3. If upgrading from AlphaStor 3.x, additional steps must be performed. Otherwise, skip to step 4. AlphaStor 3.x package files are not managed by the HP-UX package manager. As a result, the following preparation is required to upgrade from AlphaStor 3.x:



c. Remove the 3.x executable files in the software bin directory. They can interfere or be confused with the new package files.

Note: You can relocate the new AlphaStor package directory to match the location of the existing AlphaStor 3.x installation. However, the default /opt/as location is recommended. In either case, the data directory location (ASHOME) will be preserved during the software update.

4. Install the updated version of AlphaStor as described in “Install the AlphaStor software on HP-UX” on page 36.

5. Download applicable AlphaStor patches or hot fixes, if necessary. For each patch:

a. Read the associated readme.txt file.

b. Follow the instructions to apply the patch.




Note: The library reconfiguration process can take up to ten minutes.

Update the AlphaStor software 39


Installing on HP-UX

Uninstall the software on HP-UXReview the installed AlphaStor software components and installation details before uninstalling the AlphaStor software.

Review the installed AlphaStor softwareTo review all the AlphaStor components installed on an HP-UX system, enter the following command:

swlist AlphaStor

The installed AlphaStor packages are displayed, for example:

# AlphaStor 4.0 AlphaStor AlphaStor.CLI 4.0 AlphaStor Command Line Interface AlphaStor.DCP 4.0 AlphaStor Device Manager AlphaStor.LCP 4.0 AlphaStor Library Manager

Uninstall the softwareTo uninstall AlphaStor software components:

1. Type the swremove command and provide the names of AlphaStor components to uninstall as arguments to the command. For example:

• To remove all AlphaStor packages, type this command:

swremove AlphaStor

• To remove the AlphaStor CLI component only, type this command:

swremove AlphaStor.cli

2. Reconfigure remaining AlphaStor components, not removed with swremove:

swconfig -x reconfigure=true AlphaStor


6

Use the information in this chapter to install AlphaStor software on IRIX and Tru64 UNIX systems. This chapter contains the following sections:

◆ Where to install the AlphaStor components ............................................................. 42◆ Install the AlphaStor software on IRIX and Tru64 ................................................... 42◆ Verify the AlphaStor installation................................................................................. 44◆ Update the AlphaStor software................................................................................... 45


Installing on IRIX andTru64 UNIX

Installing on IRIX and Tru64 UNIX 41

Installing on IRIX and Tru64 UNIX



Install the AlphaStor software on IRIX and Tru64This section describes and gives examples of how to install AlphaStor software components on IRIX and Tru64.

◆ Library Module

◆ Device Module

◆ AlphaStor Command Line Interface

IMPORTANT

If using a SCSI-connected library on UNIX, install a SCSI device driver to enable communication with the library.

To install the AlphaStor software:

1. Create an installation directory to contain the installation files, for example:

mkdir /usr/local/ASinstall

2. Change to the newly created installation directory:

cd /usr/local/ASinstall

3. Untar the distribution file into the installation directory:

tar xvf <distribution directory>/AS_4.0_platform.tar

where platform is sgi for IRIX, and dec4 for Tru64.

4. To start the installation, enter the following command:

./as_install

5. Respond to the prompts as follows:

a. Select the modules to install. Details are available in Table 2 on page 16.

b. If a previously installed version of AlphaStor already exists, proceed to step c. Otherwise, choose the installation (package home) directory.

c. Confirm the location of the environment file (asenv). When upgrading from AlphaStor versions prior to 4.0, the asenv file will be automatically migrated to the package home directory.

d. Type the port number for the robotd daemon. The default is 3500.

e. Type the port number for the rrobotd daemon. The default is 3000.



6. To ensure that the proper daemons are active for AlphaStor sessions, add the rrobotd and robotd commands to the system startup directories. The commands may be added at any time when TCP/IP is running, either before or after the AlphaStor software installation. Enter the commands as follows:

package_directory/bin/rrobotdpackage_directory/bin/robotd

where package_directory is the location in which the AlphaStor software is installed.

IMPORTANT

If the rrobotd and robotd commands are not added to the startup files, the AlphaStor software must be manually started before using the devices attached to the system.

The EMC Release 4.0 AlphaStor Administration and Operation Guide provides configuration instructions when the installation completes.

Example 3 AlphaStor installation on an IRIX or Tru64 system

The following is a sample installation session on an IRIX or Tru64 operating system:

./as_install

There are 3 modules that can be installed:

Library Control Module Device Control Module AlphaStor Command Line Interface

If the system is connected to the robot's control path, to one or more of the robot's tape drives, and the AlphStor Command Line Interface is required then select the "all" option.

Install the Library Module (l) Device Module (d) Library and Device Modules (b) AlphaStor Command Line Interface (t) All software (a) (l/d/b/t/[a]) : aEnter the package home directory: (/usr/local/alphastor) [enter]

The location of the AlphaStor configuration file is stored in /etc/asenv.loc.

Please update /etc/asenv.loc if you elect to relocate the configuration file.

Alternatively, the variable $ASENV must specify the configuration filelocation whenever any command is executed.

The variable ASENV is not set. Using the default: /usr/local/alphastor/asenv

Is this correct file name? ([y]/n) yEnter the host name for the AlphaStor Server []: jupiterEnter the host name for the Library Manager Server [mars]: [enter]

Install the AlphaStor software on IRIX and Tru64 43


An entry must be made in your /etc/services file to allow robot clients to talk to the robot server software on a well known socket number. This entry must match the entry made on the robot client systems. The default name for this service is robotd. The default value is 3500. If these values do not match the value configured on the robot client systems, they will not be able to communicate with the server.

Enter the socket number for robotd: [3500] [enter]

If any of the robots tape drives are connected to this system a second entry must be added to the /etc/services file. This service allows the server and client access to the tape drives that are connected to this system.

The service name is fixed and created by robot. The socket numberdefaults to 3000. This number must also match the number defined for

robot clients on the robot server system. If you used 3456 for robot clients on the robot server you must use 3456 on all of the robot clients.

Enter the socket number for rrobotd: [3000] [enter]

Begin installation...list of installed files... Starting the robot client daemon rrobotd. Starting the robot server daemon robotd.

Installation Complete.

Verify the AlphaStor installationTo verify the AlphaStor installation on IRIX and Tru64 UNIX:

1. Ensure that the package directory (/usr/local/alphastor by default) exists and that it contains files.




• rrobotd - the DCP daemons.

• robotd - the LCP daemons.




Where to find patches and updatesCheck for patches or updates that might be available for this product on Powerlink, at:



Update the AlphaStor softwareTo update AlphaStor software to a newer version or patch:

1. Verify the current AlphaStor server and Library Manager versions.


3. Install the updated version of AlphaStor according to the instructions in “Install the AlphaStor software on IRIX and Tru64” on page 42.

4. Download the AlphaStor patch or hot fix, if necessary.

a. Read the patch readme.txt file.

b. Copy the correct patch to the AlphaStor installation directory.

5. If the Library Manager (LCP) is upgraded from version 3.0 or earlier, reconfigure the updated library as follows:



Note: The library reconfiguration process may take some time, possibly up to ten minutes.





7

Use the information in this chapter to install AlphaStor software on Linux systems. This chapter contains the following sections:

◆ Where to install the AlphaStor components ............................................................. 48◆ Install the AlphaStor software on Linux.................................................................... 48◆ Verify the AlphaStor installation................................................................................. 50◆ Update the AlphaStor software................................................................................... 50◆ Uninstall the AlphaStor software ............................................................................... 52


Installing on Linux

Installing on Linux 47

Installing on Linux



Install the AlphaStor software on LinuxThe AlphaStor software packages that can be installed on Linux are as follows:

◆ lgtoas — The AlphaStor server software.

◆ lgtoascli — The AlphaStor CLI client software.

◆ lgtoasdcp — The AlphaStor Device Manager (DCP) software.

◆ lgtoaslcp — The AlphaStor Library Manager (LCP) software.

To install the AlphaStor software on a Linux host:

1. Log in to the system as root.


3. Change to the directory containing the AlphaStor software packages, or if you have an installation CD-ROM, change to the software packages directory on the CD-ROM.

4. Start the installation with one of the following commands:

• If a previously installed version of AlphaStor does not exist, enter the following command for each package name:

rpm -i package_file_path

For example: rpm -i lgtoaslcp-4.0-1.i686.rpm

• If a previously installed version of AlphaStor does exist, enter the following command for each package name:

rpm -U package_file_path

For example: rpm -U lgtoaslcp-4.0-1.i686.rpm

By default, the package files are installed in the directory /usr/local/as, and the data files in /var/as. To install these files in a non-default directory, provide the following parameter to the rpm command:

--relocate default_install_directory=new_directory

For example:

--relocate /usr/local/as=/usr/local/alphastor


Installing on Linux

5. Run the configuration script for each package that was installed. The following configuration scripts are available:

• /usr/local/as/install/as_config - for AlphaStor server software.

• /usr/local/as/install/ascli_config - for AlphaStor CLI client software.

• /usr/local/as/install/asdcp_config - for AlphaStor Device Manager (DCP) software.

• /usr/local/as/install/aslcp_config - for AlphaStor Library Manager (LCP) software.

Respond to the prompts as follows for each script:

a. If prompted, enter the hostname of the robot server. The robot server is the system where you plan to install the Library Manager (LCP) software to control the library robot arm.

b. Press Return to accept the default port number for the rrobotd daemon (3000), or enter a different value.

c. Press Return to accept the default port number for the robotd daemon (3500), or enter a different value.

Note: The robotd and rrobotd port numbers are used for communication by the AlphaStor Library Manager (LCP) and the AlphaStor Device Manager (DCP).

The following is a sample installation session on a Linux operating system:

Example 4 AlphaStor installation on a Linux system

rpm -i ./lgtoas-4.0-1.i686.rpm

NOTE: To complete the configuration, please execute the following script as root: /usr/local/as/install/as_config

/usr/local/as/install/as_config

The EMC, Sun JRE, and Apache EULAs will now be displayed.Press return to continue.PLEASE READ THE FOLLOWING TERMS AND CONDITIONS

...License Agreement...

Do you accept the terms of this agreement? (y/n): y

Enter the host name of the robot server: [keep current] robothost

The service rrobotd already exists in /etc/services. The entry is:rrobotd 3000/tcp # Listen socket for clients

Date=2009-04-16


The service robotd already exists in /etc/services. The entry is:robotd 3500/tcp # Listen for client requests

Date=2009-04-16


Installation successful.

Install the AlphaStor software on Linux 49

Installing on Linux

6. Start the AlphaStor processes as described in “Start and stop the AlphaStor services” on page 76.

If the AlphaStor server, Device Manager, and Library Manager components are installed, they will start automatically when the system reboots.

After completing the installation, refer to the AlphaStor Release 4.0 Administration and Operation Guide for configuration instructions.

Verify the AlphaStor installationTo verify the AlphaStor server installation on Linux:

1. Run the following for each package name you want to verify:

rpm -V package_name

Note: Installation of the AlphaStor server package changes configuration files automatically to update settings. rpm -V will report these files, and this is perfectly normal, not a package installation error.

2. Ensure that the installation directory (.../as) exists and that it contains files.

3. After the AlphaStor server has been started, verify that the daemons are running by entering the following command:

ps -ef | grep as

These are some of the daemons that will be running:

• asa_apid — Interface to AlphaStor database.

• java — Handles communication with the web interface.

• asagent — AlphaStor Agent daemon.

For a complete list of AlphaStor daemons, refer to the AlphaStor Release 4.0 Administration and Operation Guide .

4. Launch a web browser, and enter the AlphaStor server hostname as the URL.







Installing on Linux


To update AlphaStor software to a newer version or patch:

1. Verify the current AlphaStor server and Library Manager versions (see “Review the AlphaStor installation details” on page 52).


3. If upgrading from AlphaStor 3.x, additional steps must be performed. Otherwise, skip to step 4. AlphaStor 3.x packages are not in the RPM format. As a result, the following preparation is required to upgrade from AlphaStor 3.x:



c. Remove the 3.x executable files (in the software bin directory) as they might interfere or be confused with the new package files.

d. To preserve the existing settings when installing the RPM packages, relocate the data directory (/var/as) to the existing 3.x data directory.

4. Install the updated version of AlphaStor according to the instructions in “Install the AlphaStor software on Linux” on page 48:




6. Start the AlphaStor server and monitor the messages generated by the start script (lgtoas.d) to ensure that the database conversion was successful. Details on how to start the AlphaStor server is available in “Start and stop the AlphaStor services” on page 76.




Note: The library reconfiguration process may take some time, up to ten minutes.


Installing on Linux

Uninstall the AlphaStor softwareReview the installed AlphaStor software components and installation details before uninstalling the AlphaStor software.

Review the installed AlphaStor programsTo review all the AlphaStor modules installed on a Linux system, type the following command:

rpm -qa "lgtoas*"

The programs that are installed are displayed, for example:

lgtoas-4.0-1lgtoascli-4.0-1lgtoasdcp-4.0-1lgtoaslcp-4.0-1

Review the AlphaStor installation detailsTo review detailed information about a specific AlphaStor package, type the following command:

rpm -qi lgtoas

The screen displays the installation details.

Uninstall the softwareTo uninstall AlphaStor software components, enter the rpm -e command and provide the names of AlphaStor components to uninstall as arguments to the command.

For example, to remove the AlphaStor server and the CLI module, type the following command:

rpm -e lgtoas lgtoascli


8

Use the information in this chapter to install AlphaStor software on Solaris systems. This chapter contains the following sections:

◆ Where to install the AlphaStor components ............................................................. 54◆ Install the AlphaStor software on Solaris .................................................................. 54◆ Verify the AlphaStor server installation..................................................................... 57◆ Update the AlphaStor software................................................................................... 57◆ Uninstall the AlphaStor software on Solaris ............................................................. 58◆ Install the software in a Sun Cluster Version 3.1 or 3.2 environment.................... 59◆ Uninstall the AlphaStor Sun Cluster software.......................................................... 62


Installing on Solaris

Installing on Solaris 53




Install the AlphaStor software on Solaris

IMPORTANT

Install all the proper Solaris patches before beginning the installation procedure. Solaris patches are available from Oracle.

The AlphaStor software packages that can be installed on Solaris are as follows:

◆ LGTOAs — The AlphaStor server software.

◆ LGTOAscli — The AlphaStor CLI client software.

◆ LGTOAsdcp — The AlphaStor Device Manager (DCP) software.

◆ LGTOAslcp — The AlphaStor Library Manager (LCP) software.

◆ LGTOAssc — The AlphaStor Sun Cluster agent.

Note: The LGTOAssc package should only be installed if deploying in a Sun Cluster environment. More information on configuring and/or migrating to a Sun Cluster environment after installation is provided later in this chapter.

IMPORTANT

If updating from AlphaStor version 3.0 or earlier, remove the NetWorker Server Agent. This component no longer exists. Install that the Device Manager (DCP) component on the system instead.

To install the AlphaStor software on a Solaris host:

1. Log in as root user.


3. Change to the directory containing the AlphaStor software packages, or if you have an installation CD-ROM, change to the software packages directory on the CD-ROM.

4. Start the installation with one of these commands:

• If a previously installed version of AlphaStor does not exist, type the following command:

/usr/sbin/pkgadd -d .

• If a previously installed version of AlphaStor does exist, type the following command:

/usr/sbin/pkgadd -a admin -d .

The -a admin option allows an update of AlphaStor components from an existing version of the product.



5. Respond to the prompts as follows:

a. Type the package numbers for the modules to install as listed in Table 2 on page 16.

b. Enter y to proceed with the installation.

If you are performing an update of the AlphaStor software, proceed to step 8.

6. When prompted for a location to install the files, and a location for the AlphaStor home directory:

a. Press [Enter] to accept the default AlphaStor Home directory path, or type a different path. If installing in a Sun Cluster environment, specify a path on a cluster global file system for the AlphaStor home directory.

b. Type a location in which to install the AlphaStor software files.

c. If prompted, type the hostname of the robot server. The robot server is the system where you plan to install the Library Manager (LCP) software to control the library robot arm.

d. Press [Enter] to accept the default socket number for the robotd daemon (3500), or type a different value.

e. Press [Enter] to accept the default socket number for the rrobotd daemon (3000), or type a different value.

Note: The robotd and rrobotd port numbers are used for communication by the AlphaStor Library Manager (LCP) and the AlphaStor Device Manager (DCP).

f. Press [Enter] to create the base directory.

g. Type y to install the software package files.

The installation program installs the AlphaStor package files, and indicates when the installation succeeds.

h. If prompted, repeat the steps to install other AlphaStor modules, depending on the modules specified in step 5a.

7. If installating on a Solaris version previous to Solaris 10, set the AlphaStor server system parameters, found in /etc/system directory, to the required minimum values as follows:

Note: These values can be set either before or after the AlphaStor server software is installed.

set max_nprocs=5000set shmsys:shminfo_shmmax=0x20000000set semsys:seminfo_semmap=500set semsys:seminfo_semmni=1000set semsys:seminfo_semmns=1600set semsys:seminfo_semmsl=1000set semsys:seminfo_semmnu=1000set semsys:seminfo_semume=900set shmsys:shminfo_shmmni=400set shmsys:shminfo_shmseg=400set pt_cnt=1024set slowscan=100set autoup=300set tune_t_fsflushr = 5

Install the AlphaStor software on Solaris 55


set rlim_fd_cur = 1024set rlim_fd_max = 1024set maxphys = 8388608

Reboot the system to enable the parameters.

If installing on Solaris 10 or later, proceed to step 8.

8. Start the AlphaStor processes as described in“Start and stop the AlphaStor services” on page 76.

If the AlphaStor server, Device Manager, and Library Manager components are installed, they will start automatically when the system reboots.

After completing the installation, obtain configuration instructions in the EMC AlphaStor Release 4.0 Administration and Operation Guide.

Example 5 AlphaStor installation on a Solaris system

A sample installation session on Solaris is as follows:

/usr/sbin/pkgadd -d .

The following packages are available: 1 LGTOAs AlphaStor (sparc) 4.0,REV=67 2 LGTOAscli AlphaStor Command Line Interface (sparc) 4.0,REV=67 3 LGTOAsdcp AlphaStor Device Manager (sparc) 4.0,REV=67 4 LGTOAslcp AlphaStor Library Manager (sparc) 4.0,REV=67 5 LGTOAssc AlphaStor Sun Cluster Agent (sparc) 4.0,REV=67

Select package(s) you wish to process (or 'all' to processall packages). (default: all) [?,??,q]: 1Processing package instance <LGTOAs> from </pkgs/as_4.0>AlphaStor(sparc) 4.0,REV=67## Software contents file initialized...license agreement...

Each directory entered here will have '/as' appended to itif it does not already end in '/as'.The install process will not allow /as/as, //as, etc.

Enter the installation target directory: /opt/as [?] [enter]

Enter the directory for the server data files: /var/as [?] [enter]The directory /var/as will be used for the AlphaStor Home environment

Enter the host name of the robot server: [keep current] [enter]Enter the socket number for robotd [3500]: [enter]

The port number 3500 will be assigned to robotd

Enter the socket number for rrobotd [3000]: [enter]

The port number 3000 will be assigned to rrobotd

## Executing checkinstall script.

The selected base directory </opt/as> must exist beforeinstallation is attempted.



Do you want this directory created now [y,n,?,q] yUsing </opt/as> as the package base directory.

This package contains scripts which will be executed with super-userpermission during the process of installing this package.

Do you want to continue with the installation of <LGTOAs> [y,n,?] y

Installing AlphaStor as LGTOAs

## Executing preinstall script.## Installing part 1 of 1....<listing of files>...## Executing postinstall script.Installation of <LGTOAs> was successful.#

Verify the AlphaStor server installationTo verify the AlphaStor server installation on Solaris:

1. Run the following for each package name to verify:

pkgchk -n package_name

2. Ensure that the .../as directory exists and that it contains files.

3. After the AlphaStor server has been started, verify that the daemons are running by using this command:

ps -ef | grep as


• asa_apid — Interface to AlphaStor database.

• java — Handles communication with the web interface.

• asagent — AlphaStor Agent daemon.

The EMC AlphaStor Release 4.0 Administration and Operation Guide provides a complete list of AlphaStor daemons.

4. Launch a web browser, and enter the AlphaStor server hostname as the URL.





Verify the AlphaStor server installation 57




To update AlphaStor software to a newer version or patch:

1. Verify the current AlphaStor server and Library Manager versions (see “Review the AlphaStor installation details” on page 58). For example:

pkginfo -x package_name


3. Install the updated version of AlphaStor according to the instructions in “Install the AlphaStor software on Solaris” on page 54:




5. Start the AlphaStor server and monitor the messages generated by the start script (lgtoas.d) to ensure that the database conversion was successful. Details on how to start the AlphaStor server are available in“Start and stop the AlphaStor services” on page 76.





Uninstall the AlphaStor software on SolarisReview the installed AlphaStor software components and installation details before uninstalling the AlphaStor software.

Review the installed AlphaStor programs

To review all the AlphaStor modules installed on a Solaris system, type the following command:

pkginfo | grep AlphaStor

The screen displays the AlphaStor programs that are installed, for example:

application LGTOAs AlphaStorapplication LGTOAscli AlphaStor Clientapplication LGTOAsdcp AlphaStor Device Managerapplication LGTOAslcp AlphaStor Library Manager

Review the AlphaStor installation detailsTo review detailed information about a particular AlphaStor package (such as the base install directory or version), type the following command:

pkginfo –l LGTOAs

The screen displays the installation details.



Uninstall the software

To uninstall AlphaStor software components, type the pkgrm command along with the specific names of the AlphaStor programs to uninstall as options for the command. The possible AlphaStor program names are as follows:

◆ LGTOAs for the AlphaStor server

◆ LGTOAscli for the CLI module

◆ LGTOAsdcp for the Device Manager

◆ LGTOAslcp for the Library Manager

◆ LGTOAssc for the AlphaStor Sun Cluster agent

For example, to remove the AlphaStor server and the CLI module, type the following command:

pkgrm LGTOAs LGTOAscli

After each component is uninstalled, a message states that the removal was successful.

Install the software in a Sun Cluster Version 3.1 or 3.2 environmentThe following section provides details on the installation of Sun Cluster Version 3.1 or 3.2.

The following tasks are a roadmap to follow when installing the AlphaStor software:

1. Review “Installation requirements for Sun Cluster” on page 59 and note the default directory location.

2. Install the required AlphaStor software:

• “Install the AlphaStor software on Solaris” on page 54

• “Install an AlphaStor virtual server” on page 61

Installation requirements for Sun Cluster

This section specifies the software and hardware required for installing and setting up the AlphaStor server or client software within a Sun Cluster environment:

The EMC Information Protection Software Compatibility Guide provides the most up-to-date information about software and hardware requirements.

Software requirementsThe following software must be installed on each node in the cluster:

◆ Solaris 8 or 9 operating environment and Sun Cluster version 3.1

◆ Solaris 10 operating environment and Sun Cluster version 3.2

◆ Volume Manager software (Solstice DiskSuite/Solaris Volume Manager)

Hardware requirements Ensure that a multihosted disk is used as a mount point for the global file systems. These contain the shared AlphaStor data (ASHOME) directory.

Install the software in a Sun Cluster Version 3.1 or 3.2 environment 59


System information requirementsTable 3 on page 60 lists, and Figure 8 on page 60 displays the system information needed to install highly available AlphaStor software in a Sun Cluster environment.

Figure 8 Sample cluster configuration

Migrate an existing AlphaStor server to a Sun Cluster environment on the same hostSun Cluster support is new to AlphaStor version 4.0. Therefore, it is not possible to perform a direct update from a 3.x release. AlphaStor 3.x does not have separate data and package directories, so the LGTOAssc package, which provides Sun Cluster support, cannot simply be added to an upgraded 3.x installation.

Migrate to a Sun Cluster installation on the same host as follows:

1. Ensure that the AlphaStor server is not being used during the upgrade process and that no mount or unmount operations will be requested.

2. Run AlphaStor_DR_Backup.sh with the AlphaStor server running to create a backup of the AlphaStor data files.

3. Copy the <ASHOME>/ASBackup directory to a location that is outside the ASHOME directory structure so that the backed up data does not get removed during uninstallation.

Table 3 System information

Information Required Example

AlphaStor virtual hostname with an IP address in the same subnet as the cluster nodes

clus_vir1192.168.1.10

AlphaStor globally mounted data directory (ASHOME) /global/as

Node 1 clus_phys1

Node 2 clus_phys2

Private Network

Local Disk Local Diskclus_vir1

If Node1fails,clus_vir1 fails

over to Node2

Public Network

Volume-managed Shared Disks

Terminal Concentrator

Administrative Workstation

Logical Host (Virtual Server)



4. Uninstall all AlphaStor 3.x packages.

5. Install the new AlphaStor packages. Instructions are vailable in “Task 1: Install the AlphaStor software” on page 61.

6. Copy all files contained in ASBackup/data into <ASHOME>/data on the global filesystem, over-writing files as required.

IMPORTANT

This step must be done before the AlphaStor server resource group is brought into the managed state for the first time.

7. Create the AlphaStor server resource group. Instructions are available in “Task 2: Create an Instance of the AlphaStor server resource group” on page 61.

Install an AlphaStor virtual server

To install and configure the AlphaStor software as a highly available service in a cluster, perform these tasks:

◆ “Task 1: Install the AlphaStor software” on page 61

◆ “Task 2: Create an Instance of the AlphaStor server resource group” on page 61

Task 1: Install the AlphaStor softwareThe AlphaStor software must be installed on all nodes in the cluster that are required to run the AlphaStor resource group.

Note: Ensure that Solaris 8, 9, or 10 operating environment and Sun Cluster 3.1 or 3.2 software are already installed on all nodes in the cluster and that those nodes boot in cluster mode.

To install the AlphaStor software on nodes that will be running the AlphaStor resource group:

1. Access the AlphaStor software from the distribution media.

2. Follow the package installation procedures outlined in “Install the AlphaStor software on Solaris” on page 54.

When performing the installation, the following requirements must be met:

◆ At a minimum, the packages LGTOAs, LGTOAscli, and LGTOAssc must be installed.

◆ The AlphaStor data directory must be located in the globally mounted area.

◆ The AlphaStor package directory must be located in a locally mounted area.

Task 2: Create an Instance of the AlphaStor server resource groupA resource group must be created for the highly available AlphaStor server. It must contain these resources:

◆ Logical hostname

◆ Globally mounted file system for the ASHOME directory

◆ LGTO.as resource

Install the software in a Sun Cluster Version 3.1 or 3.2 environment 61


To create an instance of the AlphaStor Server resource group, perform these steps on one node in the cluster:

1. Register the AlphaStor server (LGTO.as) resource type:

scrgadm -a -t LGTO.as

2. Create a resource group:

scrgadm -a -g alphastor

3. Add the logical host resource:

scrgadm -a -L -g alphastor -l logical_server_name

4. Create an instance of the LGTO.as resource type:

scrgadm -a -j server -t LGTO.as -g alphastor

5. Start the AlphaStor resource group:

scswitch -Z -g alphastor

Example 6 A highly available AlphaStor server

In this example, a highly available AlphaStor server uses the logical hostname as_server. The highly available AlphaStor server uses /global/as (globally mounted file system) as its data directory ASHOME.

1. Create a resource group with the name AlphaStorRG:

scrgadm -a -g AlphaStorRG

2. Add the logical hostname resource type to the resource group created in the previous step:

scrgadm -a -L -g AlphaStorRG -l as_server

3. Create an instance of the LGTO.as resource type with the name asserv. This resource belongs to the resource group AlphaStorRG and has a dependency on the logical host created in the previous step.

scrgadm -a -j asserv -t LGTO.as -g AlphaStorRG

4. Start the highly available service associated with the resource group AlphaStorRG.

scswitch -Z -g AlphaStorRG

Uninstall the AlphaStor Sun Cluster softwareTo uninstall the AlphaStor software from a cluster environment:

1. On one node in the cluster, disable and remove all instances of the LGTO.as resource type in the cluster.

For information, refer to the scswitch(1m) and scrgadm(1m) man pages.

2. On each node in the cluster, type the following command to remove all packages:

pkgrm LGTOAssc LGTOAs LGTOAscli


9

Use the information in this chapter to install AlphaStor software on Microsoft Windows systems. This chapter contains the following sections.

◆ Where to install the AlphaStor software.................................................................... 64◆ Install the AlphaStor software on Windows ............................................................. 64◆ Verify the AlphaStor server installation..................................................................... 72◆ Update the AlphaStor software on Windows ........................................................... 73◆ Uninstall the AlphaStor software on Windows........................................................ 74

Note: Administrator privileges are required to install the AlphaStor software.

Installing onMicrosoft Windows

Installing on Microsoft Windows 63

Installing on Microsoft Windows

Where to install the AlphaStor softwareTable 2 on page 16 describes where to install the AlphaStor software components.


Install the AlphaStor software on WindowsThis section describes how to install the AlphaStor software on Windows.

IMPORTANT

If Microsoft Windows is the operating system for the AlphaStor server, then the server must be a dedicated system, reserved for AlphaStor use only. The server must not have any pre installed Internet Information Services (IIS) or Apache Web Server software.

An installation wizard guides you through each step as you install the AlphaStor server or other supporting software.

Note: If updating from AlphaStor version 3.0 or earlier, remove the NetWorker Server Agent from the system. This component no longer exists. Ensure that the Device Manager (DCP) component is installed on the system instead.

To install the AlphaStor server or other software components:

1. Close any open applications and navigate to the location of the AlphaStor files.

2. To run the installation wizard, double-click the appropriate file:

• If installing from a CD-ROM, double-click the Setup.exe file in the root folder on the CD.

• If installing from a web download, double-click the downloaded executable file. The file may have a different name than the CD file.

3. In the Welcome screen of the installation wizard, illustrated in Figure 9 on page 65, verify the AlphaStor version and click Next. If upgrading an existing installation, skip to step 11.



Figure 9 AlphaStor installation welcome window

4. In the License screen, read the License Notice. Click Accept to proceed, or Decline to quit as illustrated in Figure 10 on page 66.

Install the AlphaStor software on Windows 65


Figure 10 License Notice window

5. Choose the installation directory, as illustrated in Figure 11 on page 67, and Figure 12 on page 67.

Note: Install the AlphaStor product in a directory or partition set aside exclusively for its use. This allows the AlphaStor product to be completely deleted from the system upon removal of the package, for example, by running the uninstall process in Windows. Do not install the AlphaStor software in a root or system folder.



Figure 11 Select installation folder window

Figure 12 Destination folder directory creation



6. Click Next to accept the default location for the program, or select a different location from the dropdown list and then click Next. Figure 13 on page 68 illustrates the icon location window.

Figure 13 AlphaStor icon location window



7. In the Component Selection screen, illustrated in Figure 14 on page 69, select the AlphaStor components to be installed. Table 2 on page 16 lists the components.

Figure 14 AlphaStor component selection window

8. Depending on the components chosen to install, enter the required information as follows:

a. For the Library Control Program (LCP), accept the default (3500) or enter a new port number.

b. For the Device Control Program (DCP), accept the default (3000) or enter a new port number.

c. For the Library Manager host, enter the fully qualified hostname of the local or remote host that controls the library.

Figure 15 on page 70 illustrates the LCP and DCP port window.



Figure 15 AlphaStor LCP and DCP port number window



9. Click Next, and review the current settings, including third-party installation components as illustrated in Figure 16 on page 71.

Figure 16 Review or change settings window

10. Perform one of the following:

• Click Back to make any necessary changes.

• Click Next to accept the current settings, then click Finish to continue.

11. Wait for the installation to complete. When prompted, restart the computer to enable the AlphaStor parameters, as illustrated in Figure 17 on page 72.



Figure 17 Completed installation window

The EMC AlphaStor Release 4.0 Administration and Operation Guide provides considerations and instructions for firewall configuration after the installation is complete.

Verify the AlphaStor server installationTo verify the AlphaStor server installation:

1. Ensure that the AlphaStor installation directory (...\AS) exists and that it contains files.

2. Verify that the PATH environment variable includes the AlphaStor binary directory. For example C:\AS\bin.

3. Verify that the AlphaStor services are running. From the Start menu, select Settings > Control Panel > Administrative Tools > Services. Table 4 on page 72 lists the required services that should be running.

Table 4 AlphaStor services (page 1 of 2)

Service Description

AlphaStor Agent Service • Starts the data mover interface and the AlphaStor logs.• Handles all requests from the Operations Center.• Automatically starts and stops the Apache service.



4. Verify that AlphaStor processes are running.

a. Press [Ctrl]+[Alt]+[Delete].

b. Click Task Manager.

c. Select the Processes tab.

The Image Name column should list the following:

– asagent.exe if the server component is installed– robotd.exe if the Library Manager component is installed– rrobotd.exe if the Device Manager component is installed

5. Verify the AlphaStor system parameters.

a. From the Start menu, select Settings > ControlPanel > System.

b. On the Advanced tab, click Environment Variables.

The AlphaStor installation process adds the following environment parameters to the system: ASENV, ASHOME and SCHTRACE. An additional variable, ROBOT, is added when the Library Manager or Device Manager products are installed.

6. Double-click the AlphaStor desktop icon to launch the AlphaStor login prompt.

Update the AlphaStor software on WindowsThis section describes where to find patches and updates, and how to update the AlphaStor software.




AlphaStor Device Manager Starts the Device Control Program (DCP).

AlphaStor Library Manager Starts the Library Control Program (LCP).

Apache2 • Handles the web server interface.• Included as part of the AlphaStor server installation.

Table 4 AlphaStor services (page 2 of 2)

Service Description

Update the AlphaStor software on Windows 73




To update AlphaStor software to a newer version:

1. Use Windows Explorer to navigate to the %ASHOME%\bin directory.

2. To verify the existing version, right-click one of the executables, such as sm.exe, and select Properties from the context menu. In the Properties window, view the Version tab.


4. Install the updated version of AlphaStor according to the instructions in “Install the AlphaStor software on Windows” on page 64.

5. Download any AlphaStor patches or hot fixes, if necessary.


b. Copy the correct patch to the AlphaStor directory.

6. If upgrading the Library Manager (LCP) from version 3.0, after the LCP software is updated to the new version, reconfigure the updated library as follows:




The AlphaStor Release 4.0 Administration and Operation Guide provides complete details on the Library Configuration Wizard.

Uninstall the AlphaStor software on WindowsThe following instructions apply to any Windows host where AlphaStor components are installed.

To uninstall the AlphaStor software components:

1. Launch the Microsoft Windows Control Panel.

2. In the Control Panel, select Add/Remove Programs.

3. Select the AlphaStor Agent, and click Add/Remove.

4. Click Yes to uninstall the AlphaStor software or click No to retain the software.

5. When the uninstall completes, restart the computer when prompted.


10

This chapter explains how to start and stop the AlphaStor services:

◆ Start and stop the AlphaStor services ........................................................................ 76◆ Commands to start and stop AlphaStor services ..................................................... 76◆ Start and stop ACSLS communication servers ......................................................... 77

Start and Stop theAlphaStor Services

Start and Stop the AlphaStor Services 75

Start and Stop the AlphaStor Services

Start and stop the AlphaStor servicesThis section describes how to start and stop the AlphaStor services.

Start and stop AlphaStor services on Microsoft WindowsAlphaStor software provides the following services on Microsoft Windows:

◆ AlphaStor Agent Service (AlphaStor server)

◆ AlphaStor Library Manager

◆ AlphaStor Device Manager

Note: The Apache2 service is managed automatically by the AlphaStor Agent service.

Use the Microsoft Windows Services manager to start and stop the services. By default, the services are configured to start automatically. The services can also be started and stopped from a command prompt.

Commands to start and stop AlphaStor servicesTable 5 on page 76 lists the commands to start and stop the AlphaStor services on all supported operating systems.

Table 5 AlphaStor commands to start and stop services

Operating system AlphaStor component Start command Stop command

AIX LCP startsrc -s lgtoaslcp stopsrc -s lgtoaslcp

DCP startsrc -s lgtoasdcp stopsrc -s lgtoasdcp

All startsrc -g alphastor stopsrc -g alphastor

HP-UX LCP /sbin/init.d/lgtorobotlcp.d start /sbin/init.d/lgtorobotlcp.d stop

DCP /sbin/init.d/lgtorobotdcp.d start /sbin/init.d/lgtorobotdcp.d stop

IRIX and Tru64 UNIXa LCP <package_dir>/bin/robotd <package_dir>/bin/robotd -k

DCP <package_dir>/bin/rrobotd <package_dir>/bin/rrobotd -k

Solaris and Linuxb Server /etc/init.d/lgtoas.d start /etc/init.d/lgtoas.d stop

LCP /etc/init.d/lgtorobotlcp.d start /etc/init.d/lgtorobotlcp.d stop

DCP /etc/init.d/lgtorobotdcp.d start /etc/init.d/lgtorobotdcp.d stop

Sun Cluster Server scswitch -Z -g <resource_group> scswitch -F -g <resource_group>

Microsoft Windows Server net start "AlphaStor Agent Service" net stop "AlphaStor Agent Service"

LCP net start "AlphaStor Library Manager" net stop "AlphaStor Library Manager"

DCP net start "AlphaStor Device Manager" net stop "AlphaStor Device Manager"

a.On IRIX and Tru64, the package directory is /usr/local/alphastor by default, but it is relocatable on installations.

b.On Red Hat Linux, the init.d scripts are installed in the /etc/rc.d/init.d directory.



Start and stop ACSLS communication serversStarting and stopping ACSLS library communication servers is independent of the primary ACSLS server.

Note: Before starting or stopping an ACSLS library server, ensure that all Automated Cartridge System (ACS) and Library Storage Module (LSM) modules are online and the ACSLS server is in run mode. The secondary logging server, mini_el, is not started because the normal ACSLS logging mechanism is used.

1. To start an ACSLS library communication server, type the following command:

robot_acslsstart [-c] hostname

where:

• -c (co-hosted) means the Library Manager (LCP) software is installed on the same host as the ACSLS server and uses a different socket number, 64004 instead of 50004.

• hostname is the name of the ACSLS server host.

2. To stop the communication servers, type the following command:

robot_acslsstop

Start and stop ACSLS communication servers 77



This glossary provides descriptions of terminology used in this guide.

Aaccess path The interface of the operating system to a device. For example, the default access path

on a Solaris computer could be /dev/rmt/0cbn.

ACSLS Automated Cartridge System Library Software, which is a third-party server that manages STK libraries through a database and integrated interface. It also shares tape drives and media between multiple backup servers.

AdministrationConsole

A component of the web user interface that provides the administrator a method of performing configuration tasks. An administrator login and password are required to use the Administration Console.

administrator A person who adds users, defines user privileges, configures third-party applications, manages resources (locations, libraries, and devices), and performs other setup and configuration tasks in the AlphaStor environment. An administrator has privileges that other users do not have.

allocate The process that designates the volume for use by an application. Data mover applications can use only the volumes that are allocated by them. See also unallocated and deallocated.

AlphaStor A software application that handles media lifecycle management, and library and device administration. AlphaStor enables device sharing between multiple servers and applications.

AlphaStor API AlphaStor Application Program Interface. The API allows a single AlphaStor instance to simultaneously service requests from multiple, different data mover applications. See also Data Mover Interface (DMI) and CAPI.

AlphaStor media pool A collection of volumes (tapes) that are used by the same application (such as NetWorker) and have the same AlphaStor rotation policy. AlphaStor media pools should correspond to application media pools. See also media pool and NetWorker media pool.

AlphaStor server The part of the AlphaStor system that translates library management requests from NetWorker and third-party applications and then passes the requests to the appropriate library, device, or software component. It contains a media database, which manages all media and media movement within the environment.

Glossary


Glossary

AlphaStor ServerAgent

The service name on Windows for the AlphaStor server, which does the following:

◆ Supports communication between the AlphaStor server and the NetWorker server or other data mover server.

◆ Communicates device requests to the Media Manager.

◆ Provides the web interface for the Administration Console and Operations Center

The AlphaStor installation includes the Apache Web Server.

ASCLI See Command Line Interface (ASCLI).

autochanger See library.

Bbackup job See queue job.

backup server The NetWorker server, storage node, or third-party server that sends backup jobs or mount requests to an AlphaStor server.

backup volume Backup media, such as magnetic tape.

barcode The horizontal strip of vertical bars of varying widths that represent symbols referred to as "characters." Barcodes are used as volume labels and are read by devices with read capability.

browse policy A NetWorker policy that specifies the time period during which backup entries are stored in a client file index and the associated backup files are readily accessible to desktop users.

CCAP Cartridge Access Port, a type of mailbox.

CAPI Client Applications Program Interface. The interface used in the communication between AlphaStor software and NetWorker release 7.2 and earlier.

carousel A tray or tape cartridge that holds multiple backup volumes. A type of library.

cartridge See volume.

Command LineInterface (ASCLI)

An AlphaStor software component that provides a scriptable commands for administration and manipulation of the AlphaStor environment. The ASCLI also serves as a functional interface for third-party backup applications on remote systems. It enables backup applications other than NetWorker to utilize AlphaStor for media management.

Ddata mover (DM) A backup software program that accesses the media and devices managed by

AlphaStor. The NetWorker software is a data mover. Can also refer to the backup server.

Data Mover Interface(DMI)

Data Mover Interface. The interface used in the communication between AlphaStor software and NetWorker release 7.3 and later.


Glossary

data retention The length of time, specified by NetWorker or other data mover applications, that data is retained on a volume, so that it can access the data for recovery. Data retention is configured in the browse and retention policies.

datazone The NetWorker terminology for the functional space defined by a server, storage node, and client connections.

DCP See Device Control Program (DCP).

DDS See Digital Data Storage (DDS), or dynamic drive sharing (DDS).

deallocated The operation that relinquishes ownership of an allocated volume. Media that has been deallocated can be reallocated (recycled) or purged from the AlphaStor server catalog database. See also allocate.

device The mechanism that is used to access the contents of volumes. Generally, a device is a tape drive, but can also be a magneto-optical drive, or a CD-ROM drive.

Device ControlProgram (DCP)

Also Device Control Program (DCP). A control program that manages the configuration of devices and performs the device control tasks associated with mount and unmount requests. A DCP is installed on each computer that controls a physically connected device. For example, a NetWorker storage node.

Device List The list of devices known to the AlphaStor software.

Device Manager A component that controls the devices in a library. It resides on a host that has a control path to the device or devices.

Digital Data Storage(DDS)

A storage standard used with medium-cost tape media and tape drives. DDS is the industry standard for digital audio tape (DAT) formats.

digital linear tape(DLT)

A high-capacity tape storage format.

DMI See Data Mover Interface (DMI).

drive See device.

dynamic drive sharing(DDS)

A feature that makes it possible for NetWorker software to recognize shared devices (drives). DDS enables the NetWorker software to skip the shared drives that are in use and route the backups or recoveries to other available shared devices.

Eeject The process by which you remove, or eject, a volume (tape) from a library. Removing

a volume does not, however, remove the entry from the Media Manager database. A record of the volume is saved and remains intact.

export The act of removing one or more tapes from a library. See also import.

Fforeign volume A volume created by a third-party (non NetWorker) data mover application.

frozen The state assigned to a volume when it is arrested in its normal lifecycle.


Glossary

Hhome location The location to which a volume will be recalled when @Home is used in a rotation

policy.

host A computer on the network. Data mover applications or the AlphaStor server and its components are installed on hosts.

Host List List of hosts configured to a selected device.

hostname The name of either a physical or virtual host.

import The process of inserting one or more scratch volumes into a library. See also recall and export.

inside location A location within a media library that is used by the AlphaStor software.

JJava Runtime

Environment (JRE)A virtual machine environment kit that enables web-based Java technology in AlphaStor.

job See queue job.

jukebox See library.

Llabel (noun) An electronic header on a volume used for identification by the data mover.

(verb) The process that applies an electronic header on a volume.

library A storage unit for media volumes that a device can access. A library can be automated (accessible by robotic arm) or manual (accessible by a human operator).

An automated library uses a robotic arm to move the volumes among various components located within it, including storage slots, media devices (drives), media access ports (mailboxes), and transports.

The term library can refer to a variety of robotic units, including autochanger, autoloader, carousel, datawheel, jukebox, and near-line storage.

library control module The proprietary library software that receives commands from the AlphaStor software to manipulate the arms, devices, or mailboxes. Typically, the control module uses SCSI communication. It can exist on the same cable as the library devices or it may use a separate control path.

library controlprogram (LCP)

A control program that manages the configuration, control procedures, and low-level details for a library. Each AlphaStor-controlled library has at least one LCP (Library Manager) associated with it.

library inventory An operation that updates the Media Manager database based on the current contents of the library. Newly discovered volumes are automatically added to the database and the location of existing volumes is updated accordingly.

Library Manager An AlphaStor software component, which is installed on the computer that manages the library through a physical connection, such as an SCSI interface. The Library Manager communicates with the Media Manager during library or device requests.


Glossary

library server See Library Manager.

library sharing The control and usage of individual devices within a library by different hosts within a datazone.

libraryname The name assigned to the library.

listener port The TCP/IP listener socket port number of the AlphaStor server. Sockets are part of the TCP/IP networking system that enable processes to communicate with each other.

location The physical place where a volume resides. AlphaStor automatically creates a location for inside a library, inside<libraryname>. Locations determine whether a volume is onsite or offsite. See also recall location, and inside location.

log file A file to which AlphaStor logs all messages pertaining to the Library Manager and Media Manager.

logical device A NetWorker resource that points to a device in a virtual library. Logical devices are defined by the jbconfig command entry.

LTO Linear Tape Open. An open tape storage standard designed for fast access speed and high capacity.

Mmailbox The access opening through which physical media are inserted into and removed

from a library.

media The physical storage medium, such as magnetic tape or optical disks, to which backup data is written.

media database A database that contains indexed entries about the storage volume locations and the lifecycle status of all data.

media lifecycle The series of stages in which media can be categorized related to usage. In terms of the AlphaStor software, the media lifecycle consists of four stages:

◆ New tape

◆ Ready for use in library

◆ Saved for data recovery

◆ Recycled for reuse

media manager A program, such as AlphaStor, that manages the location, status, and purpose of a variety of media.

media pool 1. The AlphaStor feature that enables the sorting of volumes, and linking of user-defined pools to AlphaStor rotation policies and resource queues.

2. A sorted and labeled collection of media volumes to which an application writes data according to specification.

mount The action within a library of retrieving a volume (such as a tape) from a slot, and placing it in a device (such as a tape drive) for reading or writing.


Glossary

mount class A user-defined value in both AlphaStor and NetWorker software that is associated with a resource queue. When NetWorker sends AlphaStor a request containing a mount class attribute, the request is automatically linked to the resource queue that is associated to the mount class.

The mount class attribute for NetWorker is found in the Pool resource.

mount priority An attribute that accompanies a mount request (from NetWorker release 6.1.3 and later) which positions a job in the resource queue to allow higher priority jobs to be processed before lower priority jobs. The following lists these operations and the priority:

◆ Backup (priority 2)

◆ Label (priority 2)

◆ Restore (priority 1)

◆ Default (priority 2)

AlphaStor does not stop a job in progress to process another incoming job, regardless of priority.

mount request A request from a data mover or other application to mount a volume on a device for reading or writing.

multipath rotationpolicy

The ability to move a volume to several different locations within a rotation policy.

NNetwork Attached

Storage (NAS)Generally, a disk array that connects directly to the messaging network or LAN interfaces that uses common communication protocols (TCP/IP or NDMP).

Network DataManagement

Protocol (NDMP)

An open standard client/server protocol that allows any storage management application, such as NetWorker, to control backup operations on a network.

networked backupserver

The combination of all networked clients and storage nodes that report to a particular networked server. It is the backup server that sends the backup requests to the AlphaStor server.

NetWorker An EMC network-based software product that is used to back up and recover file systems.

NetWorker client A computer that can access the backup and recover services from a NetWorker server.

NetWorker client fileindex

A database of information the NetWorker server maintains that tracks every database object, file, or file system backed up. The NetWorker server maintains a single client index file for each client computer.

NetWorker clone The NetWorker process used to make an exact copy of saved data (save sets), which are indexed and tracked.

NetWorker group A NetWorker attribute that specifies a client or group of clients that starts backing up its files at a designated time.

NetWorker mediapool

A feature in NetWorker software that enables you to sort data to selected volumes. You can link NetWorker pools to AlphaStor rotation policies and assign them to a specific resource queue.


Glossary

Jobs with no specified pool use the NetWorker Default pool and are sent to the resource queue that is configured for the AlphaStor Default pool.

NetWorker mountclass

A value that accompanies a mount request from the backup server and identifies the resource queue that the AlphaStor server should use to process a job. The value must be defined in both the backup server and AlphaStor environments.

NetWorker server The computer on a network that runs the NetWorker software, contains the online indexes, and provides backup and recover services to the clients on the same network.

Ooffsite The AlphaStor location for a volume that is physically located outside the library or

data center. Offsite durations in a rotation policy should match the NetWorker retention policy.

onsite The AlphaStor location for a volume that is physically located inside the library or data center. Onsite durations in a rotation policy should match the NetWorker browse policy.

Operations Center A component of the web user interface that provides the AlphaStor operator with methods of performing day-to-day tasks. An operator login and password are required to use the Operations Center.

operator The person who performs the following:

◆ Monitors volume locations and movements.

◆ Checks the success or failure of backups.

◆ Manages libraries, labels volumes

◆ Executes day-to-day tasks that use the AlphaStor software.

outside location A location that is outside of the library.

over-subscription A scenario where mount requests exceed available physical devices.

Pphysical cartridge

label (PCL)An identifier, usually a barcode, but can also be read without a barcode reader or other machine.

pool See media pool.

Qqueue See resource queue.

queue job A request from a backup server to AlphaStor to mount a volume for reading or writing. Jobs are ordered in a resource queue based on mount priority.

Rrecall The process of returning an offsite volume to its library for the purpose of data

recovery.


Glossary

recall location The location specified in the first step in the rotation policy. When a volume is recalled from an offsite location, it moves to the recall location. Also, a volume is returned to the recall location at the end of its rotation cycle. See also home location.

recyclable The NetWorker status of a volume whose data has exceeded both its browse and retention policies and is available for relabeling.

resource A device, location, or library specified in AlphaStor.

resource queue A user-defined feature that groups one or more devices. AlphaStor software assigns jobs to resource queues based on the mount class or pool assigned to the job.

AlphaStor automatically creates a default resource queue when the library is configured. The default queue contains all of the devices in the library and is named by appending the library name to the word queue.

resource queueviewer

A window accessible in the Device Resource Manager or Operations Center that displays the jobs sent to the resource queues. The viewer enables you to change the processing order by moving a job up or down in the queue.

retention policy A NetWorker policy that specifies how long data on a volume is retained for data recovery before it is recycled. Any volume that has one or more protected files cannot be recycled.

retrieval The process of locating and copying files and directories that an application has archived.

robot 1. A library.

2. The robotic arm within a library.

robotd The process name of the LCP.

rrobotd The process name of the DCP.

rotation The act of moving volumes from one location to another.

rotation policy A configurable AlphaStor policy that schedules volume rotation from one location to another.

SSAN Storage area network. An AlphaStor SAN environment is configured by assigning

multiple hosts to single devices within a library.

save set A set of files, or a file system, that is backed up onto backup media.

scratch A new or recycled volume (tape) that has not been imported or labeled.

SCSI Small Computer Systems Interface. A parallel interface standard used to attach peripheral devices to computers for transmission of data. The AlphaStor software can use SCSI connections to communicate with device managers, library managers, and libraries.

SCSI address A numeric value that uniquely identifies a device on the SCSI bus. The SCSI address of 7 is generally reserved for the SCSI interface board in the computer.


Glossary

SDLT Super Digital Linear Tape. A backwards-compatible improvement on the DLT format. It features increased capacity and better performance.

silo A library repository for holding hundreds or thousands of volumes. Silo volumes are identified by barcodes, not slot numbers. They are controlled by silo management software on a server computer that might, or might not be, the server for the application that accesses it.

slot A position in a library where a volume (tape) resides when it is not mounted for reading or writing. The slot may be free (unoccupied) or occupied. The library control path (LCP) tracks the location of media within a library and detects whether or not a slot contains a volume.

SmartMedia An EMC software application that manages media resources within a distributed environment. The jbconfig program recognizes a SmartMedia-controlled jukebox, which is also an AlphaStor-controlled library.

stand-alone device A backup device that contains a single drive for backing up data. Stand-alone devices cannot store or automatically load backup volumes.

step A location in a multipath rotation policy.

storage area network(SAN)

A high-speed subnetwork of shared storage devices that establishes a direct connection between the storage devices and servers or clients. The subnetwork is separate from a LAN or WAN.

storage device See device.

storage media See media.

Ttape A type of removable media, referenced in AlphaStor as a volume, that contains

magnetic tape as its medium.

tape library A library that uses tapes as the storage media.

TCP/IP The standard transport and network protocols on the Internet. The AlphaStor software can use TCP/IP to communicate between entities on the network, including the clients, servers, device managers, library managers, and libraries.

third-partyapplication

A non NetWorker data mover program that is designated to access the media and devices managed by AlphaStor. Examples include large enterprise storage management applications, a backup script, or utilities, such as tar.

Uunallocated Specifies the status of media that have not been allocated to an application and are

free and available. See also allocate.

Vvirtual jukebox See virtual library.


Glossary

virtual library An AlphaStor resource that manages the allocation of media to a physical library, thereby bypassing the NetWorker server or storage node. A virtual library may have more or fewer volumes, slots, or drives than the physical library.

volume 1. A unit of a partition that is allocated to a client application. The term volume refers to an application’s view of a partition on a cartridge.

2. A unit of removable storage media, such as a magnetic tape. A storage device reads from and writes to volumes.

volume movement A change in the location of a volume.

volume rotation The cycle of a volume when it rotates from one location to another. Volume rotation is defined as a rotation policy.

Wweb user interface An AlphaStor software component that provides a method of performing AlphaStor

tasks with a web interface. A login and password are required to use it.


Index

AACSLS

environment 24server 77

ADIC/EMASS environment 26, 27AlphaStor

componentsAlphaStor Server 16AlphaStor Server Agent 16Command Line Interface 16Device Manager 16Library Manager 16where to install 16

environment 16installation requirements 13installing

on Solaris 48, 54, 56on UNIX 36, 37, 42, 43, 49on Windows 64

library wizard 16, 20software features 12uninstalling

on Solaris 58, 59on Windows 74

verifying the installon Solaris 50, 57on Windows 72

Apache service 73Apache Web Server 14, 64application 12arm, robot 12, 16, 49, 55as_install command 42asa_apid daemon 50, 57automatic mount and unmount 16

Bbarcode support 13

Ccommand

AlphaStor CLI 17AlphaStor Operations Center 17

as_install 42grep 50, 57, 58jbconfig 20mount 24, 25, 26pkgadd 48, 54pkginfo 58pkgrm 59ps 50, 57robot_acslsstart 77robot_acslsstop 77robotd 43rrobotd 43unmount 24, 25, 26

Command Line Interface (CLI) 16communication flow 17components

AlphaStor Server 16AlphaStor Server Agent 16Command Line Interface 16Device Manager 16Library Manager 16where to install 16

configurationmultiplexed 19switched 19

Ddaemon

asa_apid 50, 57java 50, 57

data mover 12dedicated system 64device 12

stand-alone 16Device Manager 16, 18, 20dynamic drive sharing (DDS) 12

Eenvironment

ACSLS 24ADIC/EMASS 26, 27IBM 3494 25


Index

mixed LAN and SAN 19planning 16SAN 18, 19, 20, 21SCSI 18

Ffeatures, AlphaStor 12fiber channel 18flow, communication 17

Ggrep command 50, 57, 58

IIBM 3494 environment 25installation

AlphaStor on Solaris 48, 54, 56AlphaStor on UNIX 36, 37, 42, 43, 49AlphaStor on Windows 64requirements 13verifying on Solaris 50, 57verifying on Windows 72where to install AlphaStor components 16wizard on Windows 64

Jjava daemon 50, 57Java Runtime Environment (JRE) 14jbconfig command 20

LLCP 73Legato Application Availability Manager

requirementssoftware 59

library 12control module 12

Library Control Path (LCP) 73Library Manager 16, 17, 18, 20library server 49, 55

Mmailbox 12, 24mixed LAN and SAN environment 19mount command 24, 25, 26mount, automatic 16

NNDMP port 16Network Data Management Protocol (NDMP) 16

Ooperating system support 13

Ppkgadd command 48, 54pkginfo command 58pkgrm command 59port

NDMP 16robotd 49, 55rrobotd 49, 55

product features 12program

Device Manager 16, 18, 20Library Manager 16, 17, 18, 20robotd 17, 42, 49, 55rrobotd 42, 49, 55

ps command 50, 57

Rrequirements

Legato Application Availability Managersoftware 59

robortd port 49, 55robot arm 12, 16, 49, 55robot_acslsstart command 77robot_acslsstop command 77robotd command 43robotd program 17, 42, 49, 55rrobotd command 43rrobotd port 49, 55rrobotd program 42, 49, 55

SSAN environment 18, 19, 20, 21SCSI environment 18secondary logging server 77server

ACSLS 77AlphaStor 16library 49, 55secondary logging 77

software features 12stand-alone device 16Sybase SQL Anywhere 14system startup 43

Tterminology 12third-party products supported 14

Uuninstalling AlphaStor


unmount command 24, 25, 26unmount, automatic 16untar files on UNIX 42updating AlphaStor

on UNIX 32, 45, 51, 58on Windows 74


Index

Vverifying the install


volume 12

Wwizard

AlphaStor library 16, 20installation on Windows 64


Index


Documents

EMC® AlphaStor® Release 4.0 Installation Guide · EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 EMC® AlphaStor® Release 4.0 Installation Guide