Tivoli® Storage Manager
`for Windows
`Managed System for SAN
`Storage Agent User’s Guide
`Version 4 Release 2
`
`GC35-0434-02
`
`Microsoft Ex. 1014, p. 1
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`Microsoft Ex. 1014, p. 2
`Microsoft Ex. 1014, p. 2
`Microsoft v. Daedalus Blue
`Microsoft v. Daedalus Blue
`IPR2021-00831
`lPR2021-00831
`
`

`

`Tivoli® Storage Manager
`for Windows
`Managed System for SAN
`Storage Agent User’s Guide
`Version 4 Release 2
`
`GC35-0434-02
`
`Microsoft Ex. 1014, p. 3
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`Note!
`Before using this information and the product it supports, be sure to read the general information under “Notices” on page 41.
`
`Third Edition (September 2001)
`This edition applies to Version 4 Release 2.1 of Tivoli Storage Manager (product number 5698-TSM) and to any
`subsequent releases until otherwise indicated in new editions or technical newsletters.
`Changes since the June 2001 edition are marked with a vertical bar (|) in the left margin. Ensure that you are using the
`correct edition for the level of the product.
`Order publications through your sales representative or the branch office that serves your locality.
`Your feedback is important in helping to provide the most accurate and high-quality information. If you have any
`comments about this book or any other Tivoli Storage Manager documentation, please see “Contacting Customer
`Support” on page 37.
`© Copyright International Business Machines Corporation 2000, 2001. All rights reserved.
`US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
`with IBM Corp.
`
`|| ||
`
`Microsoft Ex. 1014, p. 4
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`Contents
`About This Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
`Summary of Changes for Tivoli Storage Manager. . . . . . . . . . . . . . . . . . . . . . . . vii
`Technical Changes for Version 4 Release 2.1—September 2001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
`Technical Changes for Version 4 Release 2—June 2001. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
`Chapter 1. Storage Agent Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
`LAN-free Client Data Backup Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
`Dual-session No-Query Restore for LAN-free Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
`Chapter 2. Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
`Types of Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
`Sharing Tape Storage using TSM Library Manager/Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
`Sharing Disk Storage using Tivoli SANergy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
`External Library — Sharing ACSLS-Managed Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
`System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
`Chapter 3. Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
`Summary of Tasks for Procedure 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
`Summary of Tasks for Procedure 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
`Procedure 1–Tape and File Sharing with SCSI and 349X Tape and File Devices. . . . . . . . . . . . . . . . 11
`Step 1. Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
`Establishing communications among client, storage agent, and server . . . . . . . . . . . . . . . . . . . . . . . . 11
`Step 2. Client System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
`Step 3. Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
`Configuring Devices for the Storage Agent to Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
`Step 4. Client System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
`Step 5. Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
`Step 6. Client System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
`Start the Storage Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
`Verify the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
`Procedure 2 —External Library Environment with an ACSLS-Managed Library . . . . . . . . . . . . . . . . 19
`Step 1. Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
`Establishing communications among client, storage agent, and server . . . . . . . . . . . . . . . . . . . . 20
`Configuring Devices for the Storage Agent to Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
`Step 5. Client System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
`Appendix A. Administration and Configuration Reference . . . . . . . . . . . . . . 27
`
`||
`
`||
`||
`||
`||
`||
`||
`
`||
`||
`
`||
`||
`||
`||
`||
`
`iii
`Tivoli® Storage Manager for Windows Managed System for SAN Storage Agent User’s Guide
`Microsoft Ex. 1014, p. 5
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`||
`
`||
`||
`||
`
`||
`||
`||
`||
`||
`||
`||
`||
`
`Starting and Stopping the Storage Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
`Starting and Stopping the Device Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
`Obtaining Tape Device Information on the Client System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
`Set Installation Data for the Storage Agent: DSMSTA SETSTORAGESERVER . . . . . . . . . . . . . . . . 31
`The Storage Agent Options File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
`The Device Configuration File for the Storage Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
`Appendix B. Legacy ACSLS Data Migration and Coexistence. . . . . . . . . . . 35
`Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
`Data Coexistence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
`Appendix C. Where to Look for Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
`Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
`Reporting a Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
`Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
`Tivoli Storage Manager Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
`Related IBM Hardware Products Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
`IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
`Translations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
`Appendix D. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
`Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
`Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
`Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
`
`iv
`
`Version 4 Release 2
`Microsoft Ex. 1014, p. 6
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`About This Book
`
`This user’s guide is intended for anyone who will be using the Tivoli Managed System for
`SAN product, commonly referred to as the storage agent. This document provides an
`overview of LAN-free data transfer. It also provides detailed explanations about configuring
`and using the Tivoli Storage Manager (TSM) client, storage agent, and TSM server. You
`should be familiar with TSM, SAN, and operating system administration. You may require
`additional publications during configuration of the storage agent environment. Refer to the
`listing of Tivoli Storage Manager Publications in “Where to Look for Information” on
`page 37.
`
`Note: Tivoli Managed System for SAN is only supported in US English. At the time of
`publishing this document no other language support was available.
`
`For information about Tivoli Storage Manager, see
`http://www.tivoli.com/support/storage_mgr/tivolimain.html.
`
`||||||||
`
`v
`Tivoli® Storage Manager for Windows Managed System for SAN Storage Agent User’s Guide
`Microsoft Ex. 1014, p. 7
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`vi
`
`Version 4 Release 2
`Microsoft Ex. 1014, p. 8
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`Summary of Changes for Tivoli Storage Manager
`
`This section summarizes changes made to the Storage Agent product and to this publication.
`
`Technical Changes for Version 4 Release 2.1—September 2001
`The following changes have been made to the product for this edition:
`Device support enhancements
`¶ LAN-free external library interface support allows access to LAN-free data
`transfer for TSM Servers sharing access to ACSLS-managed libraries (that is, a
`StorageTek llibrary controlled by Automated Cartridge System Library Software
`(ACSLS) software or Library Station). This publication provides additional
`information.
`¶ Tivoli Storage Manager servers can now share tape drives in a StorageTek
`library managed by ACSLS or LibraryStation software. Gresham Extended Data
`Technology DistribuTAPE (EDT-DistribuTAPE) is a middleware software
`program that takes advantage of Tivoli Storage Manager’s external library
`interface to allow tape drives in ACSLS libraries to be shared among servers.
`This support allows a storage agent to access an external library for LAN-free
`operations.
`
`Technical Changes for Version 4 Release 2—June 2001
`The following changes have been made to the product for this edition:
`Support for disk devices
`LAN-free data transfer is available for disk devices on a SAN, through shared FILE
`device class
`Support for library clients
`LAN-free data transfer is available for TSM servers that is either a library manager
`or a library client.
`Support for IBM® 3494
`LAN-free data transfer is available for IBM 3494 libraries in SAN environments.
`Support for TSM backup-archive clients
`This includes the following:
`¶ Multi-session backup
`¶ Dual session No-Query Restore
`¶ Sub-File component backup and restore enhancement
`
`| | | ||||| ||||||| |
`
`vii
`Tivoli® Storage Manager for Windows Managed System for SAN Storage Agent User’s Guide
`Microsoft Ex. 1014, p. 9
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`viii
`
`Version 4 Release 2
`Microsoft Ex. 1014, p. 10
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`1. Storage Agent
`
`Overview
`
`1
`
`Storage Agent Overview
`
`Managed System for SAN is a feature of Tivoli Storage Manager (TSM) that enables
`LAN-free TSM client data movement. The TSM client data moves directly to and from a
`storage device attached to a Storage Area Network (SAN), thereby off-loading the data
`movement from the LAN and from the Tivoli Storage Manager server. The storage agent is
`installed on the client machine and shares storage resources with the Tivoli Storage Manager
`server. The storage agent can write directly to storage media in a format that is consistent
`with that used by the server. The TSM server or servers control the storage devices and keep
`track of the data that the client has stored. TSM continues to use a LAN connection to
`exchange control information, such as policy information and data about the objects that are
`backed up. Using the SAN for client data movement decreases the load on the TSM server
`and allows the server to support a greater number of simultaneous client connections. See
`Figure 1.
`
`||||||||||||
`
`TSM Client
`Storage Agent installed
`
`Library Control
`Client Metadata
`
`LAN
`
`TSM Server
`
`Client
`Data
`
`SAN
`
`Library
`Control
`
`File Library
`
`Tape Library
`
`Figure 1. SAN Data Movement. Solid lines indicate data movement. Broken lines indicate movement of control
`information and metadata.
`To use Managed System for SAN you must install a storage agent on the client system. The
`storage agent communicates with the server to obtain and store database information and to
`coordinate device and volume access. The server determines if the client is requesting access
`
`1
`Tivoli® Storage Manager for Windows Managed System for SAN Storage Agent User’s Guide
`Microsoft Ex. 1014, p. 11
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`to storage for which the client has a SAN path defined. If a SAN path is defined, the client
`(by means of the storage agent) transfers data on that path. If a failure occurs on the SAN
`path, failover occurs and the client uses its LAN connection to the TSM server and moves
`the client data over the LAN.
`
`TSM supports SAN-attached device sharing in one of the following ways:
`¶ TSM native library management support consisting of a library manager and library
`clients or just a library manager.
`¶ Shared disk storage using a FILE library and the integration of the Tivoli SANergy™
`product.
`¶ External library support, in that tape libraries managed by StorageTek Automated
`Cartridge System Library Software (ACSLS) and middleware that enables TSM to share
`ACSLS-managed libraries. In this environment the device sharing capability is provided
`by third-party software, such as Gresham Extended Data Technology DistribuTAPE
`(EDT-DistribuTAPE) a middleware software program that takes advantage of TSM’s
`external library interface to allow tape drives in ACSLS-managed libraries to be shared
`among TSM servers.
`For additional information about these configurations, see “Types of Configurations” on
`page 3.
`
`LAN-free Client Data Backup Scenario
`The following outlines a typical backup scenario for a TSM client that uses SAN data
`movement. This scenario does not apply to External library environments.
`1. The client begins a backup operation. The client and the server exchange policy
`information over the LAN to determine the destination of the backed up data.
`For a client using LAN-free data movement, the destination is a storage pool that uses a
`device on the SAN. That device must also be mapped for the client.
`2. Because the destination is on the SAN, the client contacts the storage agent, which will
`handle the data transfer. The storage agent sends a request for a volume mount to the
`server.
`3. The server contacts the storage device and mounts the appropriate media.
`4. The server notifies the client of the location where the mounted media resides.
`5. The client, by means of the storage agent, writes the backup data directly to the device
`over the SAN.
`6. The storage agent sends file attribute information to the TSM server, and the server
`stores the information in its database.
`
`Dual-session No-Query Restore for LAN-free Path
`When performing a No-Query restore the TSM server builds a list of files to restore and
`sends data to the client while continuing to build the list. This type of restore is more
`efficient especially in a LAN-free environment. Two sessions are used for the restore when
`data for the restore resides on devices with a LAN-free path and devices with a LAN-only
`path. One session restores data from the server with a LAN-only path. The other session
`uses the storage agent to restore data over the LAN-free path. This works only with clients
`at the 4.2 level or above.
`
`Version 4 Release 2
`Microsoft Ex. 1014, p. 12
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`| || || ||||||| ||
`
`|
`
`2
`
`

`

`2
`
`Planning
`
`2. Planning
`
`You can set up a Managed System for SAN in a number of configurations. Planning the
`system configuration provides a smooth transition through system setup and into production.
`As part of your planning, you need to identify the following:
`¶ Which configuration to implement
`¶ Devices to be used for LAN-free data movement
`¶ Clients to use LAN-free data movement
`¶ For tape libraries (except, ACSLS-managed StorageTek tape libraries), which servers,
`library manager or library client, manage which client’s data.
`
`Types of Configurations
`There are several common types of configurations that take advantage of what can be
`accomplished using a storage agent in a LAN-free environment. Your environment is
`dependent upon the type of storage device you will be using for LAN-free data storage. The
`following sections cover descriptions and planning considerations for several typical
`LAN-free environments. These environments are:
`1. SCSI and 349X Tape Library sharing using the TSM Library Manager and Client. See
`“Sharing Tape Storage using TSM Library Manager/Client”.
`2. File device sharing using SANergy. See “Sharing Disk Storage using Tivoli SANergy” on
`page 4.
`3. Sharing a library managed by ACSLS or LibraryStation software. See “External Library
`— Sharing ACSLS-Managed Libraries” on page 5.
`Sharing Tape Storage using TSM Library Manager/Client
`When TSM servers share a SCSI tape or 349X storage device using a library manager and
`library clients, one server, the library manager, owns and controls the tape library device.
`The library manager operations include checking volumes into and out of the library,
`labeling volumes, mounting and dismounting volumes, auditing volumes, and creating an
`inventory of library contents, see Figure 2 on page 4. The library manager also manages the
`storage hierarchy and performs such server functions as storage pool migrations,
`reclamation, collocation, and backup and restore of storage pools and the database. All of the
`other TSM servers sharing this library are considered. library clients. A library client
`requests shared library resources as drives or media from the TSM server acting as the
`library manager, but uses the resources independently. The library manager coordinates the
`access to these resources. Data moves over the SAN between the storage device and either
`the library manager or the library client. Either the library manager or any library client can
`manage the LAN-free movement of client data as long as the client system includes a
`storage agent.
`
`3
`Tivoli® Storage Manager for Windows Managed System for SAN Storage Agent User’s Guide
`Microsoft Ex. 1014, p. 13
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`|| ||| | | | || | ||||| || || || | ||||||||||||||
`
`

`

`The Library Manager and Library Client configurations are represented in Figure 2 .
`
`TSM Client
`Storage Agents
`
`TSM Server
`Library Manager
`
`LAN
`
`TSM Server
`Library Client
`
`SAN
`
`Tape Library
`
`Figure 2. Library Manager/Client LAN—free Configuration
`Note: An environment can consist of just the Library Manager.
`
`The configurations represented in the previous illustration are the following:
`¶ A TSM server library manager manages a client’s data, which is stored on a tape
`library.
`¶ A TSM server library client manages a client’s data, which is stored on a tape library.
`Sharing Disk Storage using Tivoli SANergy
`When TSM servers share access to disk storage, the environment contains a FILE library
`(TSM server File device class) and utilizes the SANergy product. SANergy provides a file
`sharing accelerator. If you will be using a FILE library, you must determine where the Tivoli
`SANergy client and the Tivoli SANergy Metadata Controller (MDC) will be installed. You
`will also require a Windows® share (CIFS) or a Network File Share (NFS) on a Unix system
`to achieve file sharing. See Figure 3 on page 5 and Table 1 on page 5 for the possible Tivoli
`SANergy configurations. See the SANergy publications for additional information about
`configuring SANergy.
`
`Version 4 Release 2
`Microsoft Ex. 1014, p. 14
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`||
`
`|
`
`|||
`
`| | || | | |||||||||
`
`4
`
`

`

`2. Planning
`
`1
`TSM Client
`Storage Agent
`
`3
`Another Node
`
`2
`TSM Server
`
`LAN
`
`SAN
`
`FILE Library
`
`Figure 3. Tivoli SANergy Configurations
`In the following table, the numbers refer to those numbers in Figure 3. For example, one
`possible configuration is for the Tivoli SANergy client to be installed on the TSM client
`machine (򍦠1򐂰) and the Tivoli SANergy MDC to be installed on the TSM server (򍦠2򐂰). These
`configurations can also consist of multiple platforms. For example, an environment can
`consist of a SUN MDC working with a NT and AIX client.
`Table 1. Tivoli SANergy Configurations
`Tivoli SANergy
`Component
`Tivoli SANergy Client
`Tivoli SANergy MDC
`
`򍦠1򐂰
`򍦠2򐂰
`
`򍦠2򐂰
`򍦠1򐂰
`
`Where Installed
`
`򍦠1򐂰 and 򍦠2򐂰
`򍦠3򐂰
`
`External Library — Sharing ACSLS-Managed Libraries
`When TSM servers share access to ACSLS-managed libraries, the sharing is enabled by
`middleware (such as, Gresham EDT-DistribuTAPE) between the data storage manager
`(TSM) and a media manager (StorageTek ACSLS). See Figure 4 on page 6. The ACSLS
`Server (or Library Station) manages the physical aspects of tape cartridge storage and
`retrieval. The external library manager, in this discussion Gresham EDT, communicates with
`the ACSLS Server or LibraryStation to access tape cartridges in an automated StorageTek
`library. The storage agent installed on a machine containing Gresham EDT and a TSM client
`(such as, Tivoli Data Protection (TDP) for Exchange or TDP for SQL) provides access to
`SAN-attached storage devices resulting in LAN-free data movement. The continued
`connection to the LAN provides a meta data (control information) path. If the storage agent
`is not available, the LAN provides a failover path for data backup and recovery.
`
`5
`Tivoli® Storage Manager for Windows Managed System for SAN Storage Agent User’s Guide
`Microsoft Ex. 1014, p. 15
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`|
`
`|||||||| || ||| |||| ||||| | ||||||||||||
`
`

`

`Figure 4. External Library Environment
`For detailed installation, configuration, and system administration of ACSLS, refer to the
`appropriate StorageTek documentation. For detailed installation, configuration, data
`migration, and system administration of Gresham EDT-DistribuTAPE, refer to the Gresham
`EDT User’s Manual.
`
`Version 4 Release 2
`Microsoft Ex. 1014, p. 16
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`|
`
`||
`
`6
`
`

`

`2. Planning
`
`Data Migration and Coexistence
`If you currently have data associated with the TSM ACSLS library type and want to take
`advantage of LAN-free, you will need to consider coexistence and migration issues, see
`“Legacy ACSLS Data Migration and Coexistence” on page 35.
`
`System Requirements
`To use the Managed System for SAN feature configure the following components at the
`latest available software levels. See
`http://www.tivoli.com/support/storage_mgr/tivolimain.html
`¶ Your SAN configuration must meet the applicable hardware and software requirements
`(see http://www.tivoli.com/support/storage_mgr/san/overview.html).
`¶ TCP/IP is required for communication among the TSM server, the client, and the storage
`agent.
`¶ The storage agent machine must have Microsoft® Internet Explorer Version 5 or higher
`installed.
`¶ A Tivoli Storage Manager server with this feature (version 4.2.1 or higher). The TSM
`servers available for the Windows, AIX®, and Sun Solaris operating systems support the
`Managed System for SAN feature.
`¶ A Tivoli Storage Management client (for example, Tivoli Data Protection application
`client). Client software must be installed on a client system (check
`http://www.tivoli.com/support/storage_mgr/tivolimain.html for the clients that are
`currently supporting the Managed System for SAN feature).
`
`Note: An API version 4.2 or higher is required.
`¶ A Tivoli Storage Manager storage agent. The storage agent must be installed on the
`same system as the client software. Also, the storage agent must be at the same level as
`the server with which it communicates (including program temporary fix (PTF) level).
`You can download the latest PTF from the Tivoli Web site at
`http://www.tivoli.com/support/storage_mgr/tivolimain.html.
`¶ The TSM application program interface (API) software must be at the version 4.2 or
`higher level. You can obtain the API by downloading the latest version of the
`backup-archive client for Windows from the Web site.
`¶ If you are sharing disk storage, Tivoli SANergy Version 2.2 or higher must be installed.
`
`Note: If you are sharing only tape devices, Tivoli SANergy is not required.
`¶ If you are using External library support in conjunction with the Gresham product,
`Gresham EDT DistribuTAPE 6.2.2.0 or higher must be installed. For additional
`information and product download, see
`http:www.greshamstorage.com/products/download/distributape.html.
`
`||||
`
`7
`Tivoli® Storage Manager for Windows Managed System for SAN Storage Agent User’s Guide
`Microsoft Ex. 1014, p. 17
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`8
`
`Version 4 Release 2
`Microsoft Ex. 1014, p. 18
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`3
`
`3. Installation and
`
`Configuration
`
`Installation and Configuration
`
`|
`
`The set up procedures are different for disk devices, tape devices and External Library
`(ACSLS) devices. There are two procedure descriptions in this section. The type of
`environment you implement determines which procedure you should follow. The types of
`environments described are:
`1. SCSI and 349X Tape Library sharing using the TSM Library Manager and Client.
`2. File device sharing using SANergy.
`3. External Library support for ACSLS Libraries.
`For descriptions of these environments, see “Storage Agent Overview” on page 1 and “Types
`of Configurations” on page 3.
`
`The first procedure covers environments that are using either Library Manager/Client or
`SANergy, see “Procedure 1–Tape and File Sharing with SCSI and 349X Tape and File
`Devices” on page 11. The second procedure specifically describes External Library support
`for ACSLS library environment configuration, see “Procedure 2 —External Library
`Environment with an ACSLS-Managed Library” on page 19.
`
`Read the summary and continue by performing the tasks in the appropriate procedure using
`the details that follow.
`
`||
`
`Summary of Tasks for Procedure 1
`You must complete the following tasks:
`1. Network: Ensure that your system meets the prerequisites for the SAN configuration.
`See “Step 1. Network” on page 11.
`
`Note: If you will be using Tivoli Storage Agent with disk media, you must have
`installed Tivoli SANergy Version 2.2 on the applicable machines. See Figure 3 on
`page 5 for possible Tivoli SANergy configurations. See the Tivoli SANergy
`Administrator’s Guide for details.
`
`Establishing communications among client, storage agent, and server
`2. Client system:
`a.
`Install the client and the latest level of the TSM API. Specify the LAN-free option
`for the API. See “Install or Upgrade the Client and API Software” on page 12.
`Install and set up the storage agent. See “Install and Configure the Storage Agent” on
`page 13.
`3. Server:
`
`b.
`
`9
`Tivoli® Storage Manager for Windows Managed System for SAN Storage Agent User’s Guide
`Microsoft Ex. 1014, p. 19
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`a. Configure the library and drives on the SAN
`b. Define the storage agent as a server
`
`Tape Devices
`a. Configure the library and drives on the SAN
`b. Define the storage agent as a server
`
`Disk Devices
`a. Define the FILE device class
`b. Define the storage agent as a server
`See “Step 3. Server” on page 14.
`
`Configuring devices for the storage agent to access
`4. Client system: For the tape devices to be used:
`a. Start the device drivers
`b. Obtain device information
`See “Step 4. Client System” on page 16.
`5. Server:
`Set up drive mapping for the storage agents on the server. See “Step 5. Server” on
`page 17.
`6. Client system:
`a. Start the storage agent.
`b. Verify the configuration.
`See “Step 6. Client System” on page 18.
`
`Summary of Tasks for Procedure 2
`You must complete the following tasks:
`1. Network: Ensure that your system meets the prerequisites for the SAN configuration.
`See “Step 1. Network” on page 20.
`
`Note: If you will be using Tivoli Storage Agent with ACSLS-managed libraries, you
`must have the ACSLS software and the third-party external library software (such
`as, Gresham EDT-DistribuTAPE) installed and configured. See Figure 4 on page 6
`for an example of a Storage Agent in an ACSLS-managed library environment.
`See the StorageTek ACSLS and the Gresham EDT documentation for installation
`instructions.
`
`Establishing communications among client, storage agent, and server
`2. Client system:
`a.
`Install the client and the latest level of the TSM API. Specify the LAN-free option
`for the API. See “Install or Upgrade the Client and API Software” on page 21.
`
`| | || |||||| | | ||
`
`10
`
`Version 4 Release 2
`Microsoft Ex. 1014, p. 20
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`3. Installation and
`
`Configuration
`
`b.
`
`Install and set up the storage agent. See “Install and Configure the Storage Agent” on
`page 21 .
`3. Server:
`a. Configure the library on the SAN
`b. Define the storage agent as a server
`
`Tape Devices
`a. Configure the library on the SAN
`b. Define the storage agent as a server
`See “Step 3. Server” on page 14.
`
`Configuring devices for the storage agent to access
`4. Client system: For the tape devices to be used, start the device drivers. See “Step 4.
`Client System” on page 24.
`5. Client system:
`a. Start the storage agent.
`b. Verify the configuration.
`See “Step 5. Client System” on page 25.
`
`Procedure 1–Tape and File Sharing with SCSI and 349X Tape and
`File Devices
`The following steps describe configuring a storage agent environment consisting of either
`shared libraries or shared disk, or both. If you are configuring an external library, that is, an
`ACSLS-managed library environment, see “Procedure 2 —External Library Environment
`with an ACSLS-Managed Library” on page 19.
`
`Step 1. Network
`The server system and the client systems must be attached to the SAN along with
`appropriate storage devices. The server system and the client systems must also be
`connected by means of a LAN.
`
`The Managed System for SAN feature requires specific levels and models of hardware and
`software. Ensure that your system configuration meets the hardware and software
`requirements for the SAN setup. See the Web site,
`http://www.tivoli.com/support/storage_mgr/san/overview.html, for details.
`
`Establishing communications among client, storage agent, and
`server
`
`Figure 5 on page 12 shows the results of completing “Step 2. Client System” on page 12 and
`“Step 3. Server” on page 14.
`
`Note: This figure does not include all the required options. Steps 2 and 3 provide more
`details.
`
`|| | | | | | | | | || | | | | | | ||||
`
`11
`Tivoli® Storage Manager for Windows Managed System for SAN Storage Agent User’s Guide
`Microsoft Ex. 1014, p. 21
`Microsoft v. Daedalus Blue
`IPR2021-00831
`
`

`

`TSM Client Workstation
`
`Client - MANTIA
`
`dsm.opt file
`
`enablelanfree yes
`tcpserveraddress
`
`
`
`.tucson.tivoli.comgarden
`
`Storage Agent - IRIS
`
`dsmsta.opt file
`
`servername=garden
`
`devconfig
`devconfig
`
`devconfig file
`set staname iris
`set stapassword xxxxxxx
`set stahladdress arbor.tucson.tivoli.com
`define server
`garden
`serverpassword=xxxxxxxx
`hladdress=garden.tucson.tivoli.com
`lladdress=1500
`
`TSM Server - GARDEN
`
`serverpassword=jonquil
`define server
`iris
`hladdress=sanclient.tucson.tivoli.com
`lladdress=1500
`
`register node
`
`mantia
`
`crocus domain=sandomain
`
`Figure 5. Communications information. Results of Steps 2 and 3. The passwords are shown as ″xxxxxxx″ because
`they are encrypted in the file.
`
`Step 2. Client System
`Do the following on the client system:
`1.
`Install or upgra