Introduction and Planning Guide

Transcription

1 IBM System Storage TS7650 ProtecTIER Deduplication Gateway Introduction and Planning Guide for ProtecTIER 3.1 GA

2

3 IBM System Storage TS7650 ProtecTIER Deduplication Gateway Introduction and Planning Guide for ProtecTIER 3.1 GA

4 Note Before using this information and the product it supports, be sure to read the information in the "Safety and enironmental notices" and "Notices" sections of this publication. This edition applies to the TS7650G with ProtecTIER ersion 3.1 installed and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures Tables ii Safety and Enironmental notices... ix Safety notices ix Power cords x Enironmental notices xi About this document xiii Terminology xiii Who should read this document x What's new in this release x Getting information, help, and serice..... x Getting help online xi Before you call for serice xii Getting help by telephone xii Web sites xii Related publications xiii TS7650G publications xiii Gateway serer (3958 DD4) publications... xiii Remote Superisor Adapter publications... xix System console (TSSC) publication..... xix How to send your comments xix TS7650G component dimensions Weight Operator and serice clearances Aisle and door clearances Floor requirements Floor leel requirements Weight distribution and floor loading Security considerations Operating enironment requirements Electrical power ratings for the TS7650G Acoustic declaration for the TS7650G components 22 Considering safety issues Proiding a fire-suppression system Earthquake effects Chapter 3. TS7650G components and feature codes TS7650G feature codes Feature codes for 3958 DD4 Gateway Serer XXB ProtecTIER Enterprise Edition V3.1 Base Software Chapter 4. Sizing, configuration, and usage considerations Chapter 1. Introduction TS7650G hardware components Gateway serer (3958 DD4) Software for the TS7650G ProtecTIER Manager ProtecTIER Virtual Tape (VT) OpenStorage TS7650G support and requirements Deices supported Supported operating systems Supported deice driers Supported SAN switches Supported LUNs Data management and adanced features RAID support Fencing node actie-actie support LUN masking Replication Chapter 2. Physical planning specifications for the TS7650G Site preparation Calculating space requirements Lighting considerations Upgrade considerations Accommodating cables Height requirements Dimensions and weights of models Chapter 5. Customer installation responsibilities System responsibilities ProtecTIER Manager workstation requirements 38 Hardware, cabling, and infrastructure responsibilities Cache configuration best practices Security, auditability, and control Chapter 6. IBM serice installation responsibilities Chapter 7. Planning data migration.. 45 Chapter 8. OpenStorage (OST) network configuration for the ProtecTIER Backup serer Abstract Scope and objecties Definitions and Acronyms Bonding/Teaming Bonding on linux machines Bonding on Unix machines Teaming on Microsoft-based machines LAG and similar technologies on the LAN Switches Setting up the network with ProtecTIER Load Distribution Methodology Copyright IBM Corp iii

6 LAN switch Hosts Network topologies Connectiity on a Single Site Connectiity to a Remote Site Chapter 9. IBM-proided TS7650G equipment and documents Chapter 10. Company information worksheet Chapter 11. IP address worksheet Chapter 12. Replication settings worksheet Chapter 13. ProtecTIER Replication Network Performance Validation Utility for VTL Systems Chapter 14. ProtecTIER Network Performance Validation Utility for OpenStorage Systems Chapter 15. Example cache configuration file Accessibility for publications and ProtecTIER Manager About the Windows-based accessibility features.. 93 About the Jaa-based tools Installing the Jaa Runtime Enironment Installing the Jaa Access Bridge Using a screen reader to install ProtecTIER Manager 96 Enabling the Windows High Contrast option Using the Windows high contrast scheme with ProtecTIER Manager Customizing the color palette Notices Trademarks Electronic emission notices Federal Communications Commission statement 107 Industry Canada compliance statement European Union Electromagnetic Compatibility Directie Australia and New Zealand Class A Statement 108 Germany Electromagnetic compatibility directie People's Republic of China Class A Electronic Emission statement Taiwan Class A compliance statement Taiwan contact information Japan Voluntary Control Council for Interference (VCCI) Class A Statement Japan Electronics and Information Technology Industries Association (JEITA) Statement (less than or equal to 20 A per phase) Korean Communications Commission (KCC) Class A Statement Russia Electromagnetic Interference (EMI) Class A Statement Index i IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

7 Figures 1. TS7650G serer frame components Gateway serer rear iew Gateway serer front iew Gateway serer operator information panel 7 5. Tape library emulation OpenStorage TS3000 System Console Screen Login screen Dedicated zone topology Single host with single ProtecTIER serer on the same VLAN Multiple switches High aailability configuration Host with single ProtecTIER serer on the different VLANs Connectiity in remote sites Display tab Settings for High Contrast ProtecTIER Manager window Preferences dialog box Normal contrast ersus high contrast Color selection, Swatches tab Default color ersus custom color Copyright IBM Corp. 2011

8 i IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

9 Tables 1. IBM websites for help, serices, and information xi 2. Serer rear iew: Slot assignments, ports, and connections DD4 Serer front iew Operator information panel TS7650G component dimensions TS7650G component weights Operator and Serice Clearance Requirements Temperature and humidity requirements Recommended power ratings for TS7650G 3958 per line cord Recommended power ratings for clustered TS7650G 3958 per line cord FC 3437 Cluster Connection Kit power requirements Acoustic declaration for the 3958 DD4 gateway serer Company information worksheet Country codes Factory-default serer IP addresses for a stand-alone VTL ProtecTIER serer (3958 DD4 or 3958 AP1) Factory-default serer IP addresses for a stand-alone OpenStorage ProtecTIER serer (3958 DD4 or 3958 AP1) Factory-default serer IP addresses for a clustered VTL ProtecTIER system (3958 DD4 or 3958 AP1) Factory-default serer IP addresses for a clustered OpenStorage ProtecTIER system (3958 DD4 or 3958 AP1) Customer IP addresses Customer and Replication IP addresses for VTL or OpenStorage systems Host names and DNS settings for setting up the TSSC with the TS7650G TSSC IP addresses Base Clusters and Additional Storage Component IP addresses Replication policy information Copyright IBM Corp ii

10 iii IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

11 Safety and Enironmental notices This section contains information about safety notices that are used in this guide and enironmental notices for this product. Safety notices Obsere the safety notices when using this product. These safety notices contain danger and caution notices. These notices are sometimes accompanied by symbols that represent the seerity of the safety condition. Most danger or caution notices contain a reference number (Dxxx or Cxxx). Use the reference number to check the translation in the IBM Systems Safety Notices, G manual. The sections that follow define each type of safety notice and gie examples. Danger notice A danger notice calls attention to a situation that is potentially lethal or extremely hazardous to people. A lightning bolt symbol always accompanies a danger notice to represent a dangerous electrical condition. A sample danger notice follows: DANGER: An electrical outlet that is not correctly wired could place hazardous oltage on metal parts of the system or the deices that attach to the system. It is the responsibility of the customer to ensure that the outlet is correctly wired and grounded to preent an electrical shock. (D004) Caution notice A caution notice calls attention to a situation that is potentially hazardous to people because of some existing condition, or to a potentially dangerous situation that might deelop because of some unsafe practice. A caution notice can be accompanied by one of seeral symbols: If the symbol is... It means... A generally hazardous condition not represented by other safety symbols. This product contains a Class II laser. Do not stare into the beam. (C029) Laser symbols are always accompanied by the classification of the laser as defined by the U. S. Department of Health and Human Serices (for example, Class I, Class II, and so forth). A hazardous condition due to mechanical moement in or around the product. Copyright IBM Corp ix

12 If the symbol is... It means... This part or unit is heay but has a weight smaller than 18 kg (39.7 lb). Use care when lifting, remoing, or installing this part or unit. (C008) Sample caution notices follow: Caution The battery is a lithium ion battery. To aoid possible explosion, do not burn. Exchange only with the IBM-approed part. Recycle or discard the battery as instructed by local regulations. In the United States, IBM has a process for the collection of this battery. For information, call Hae the IBM part number for the battery unit aailable when you call. (C007) Caution The system contains circuit cards, assemblies, or both that contain lead solder. To aoid the release of lead (Pb) into the enironment, do not burn. Discard the circuit card as instructed by local regulations. (C014) Caution When remoing the Modular Refrigeration Unit (MRU), immediately remoe any oil residue from the MRU support shelf, floor, and any other area to preent injuries because of slips or falls. Do not use refrigerant lines or connectors to lift, moe, or remoe the MRU. Use handholds as instructed by serice procedures. (C016) Caution Do not connect an IBM control unit directly to a public optical network. The customer must use an additional connectiity deice between an IBM control unit optical adapter (that is, fibre, ESCON, FICON ) and an external public network. Use a deice such as a patch panel, a router, or a switch. You do not need an additional connectiity deice for optical fibre connectiity that does not pass through a public network. Power cords For your safety, IBM proides a power cord with a grounded attachment plug to use with this IBM product. To aoid electrical shock, always use the power cord and plug with a properly grounded outlet. IBM power cords used in the United States and Canada are listed by Underwriter s Laboratories (UL) and certified by the Canadian Standards Association (CSA). For units intended to be operated at 115 olts: Use a UL-listed and CSA-certified cord set consisting of a minimum 18 AWG, Type SVT or SJT, three-conductor cord, a maximum of 15 feet in length and a parallel blade, grounding-type attachment plug rated 15 amperes, 125 olts. For units intended to be operated at 230 olts (U.S. use): Use a UL-listed and CSA-certified cord set consisting of a minimum 18 AWG, Type SVT or SJT, x IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

13 Enironmental notices three-conductor cord, a maximum of 15 feet in length and a tandem blade, grounding-type attachment plug rated 15 amperes, 250 olts. For units intended to be operated at 230 olts (outside the U.S.): Use a cord set with a grounding-type attachment plug. The cord set should hae the appropriate safety approals for the country in which the equipment will be installed. IBM power cords for a specific country or region are usually aailable only in that country or region. The enironmental notices that apply to this product are proided in the Enironmental Notices and User Guide, Z xx manual. A copy of this manual is located on the publications CD. Safety and Enironmental notices xi

14 xii IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

15 About this document Terminology This document proides you with introductory and planning information for the IBM System Storage TS7650G ProtecTIER Deduplication Gateway (TS7650G), with or without replication, and the 3958 DD4 gateway serer. Use this document to do the following: Gain an understanding of the basic features and capabilities of the TS7650G. Plan for the installation of the TS7650G at your site. Technical changes occurring in this edition are identified with a ertical bar ()in the left margin of the page. This section lists common terms used in this document. TS7650G or Gateway These are terms for IBM's irtualization solution from the TS7650 family that does not include a disk storage repository, allowing the customer to choose from a ariety of storage options. IBM does support two clustered pairs of TS7650 Gateway serers in a single frame. The TS7650G consists of the following: Serer There are three types of serer that hae been used in the Gateway: 3958 DD4 This is a newer, higher performance serer aailable in December This serer is based on the IBM System x3850 X5 Type 7145-AC1. When used as a serer in the TS7650G, its machine type and model are 3958 DD4. Use this machine type and model for serice purposes DD3 This is a higher performance serer aailable in March This serer is based on the IBM System x3850 M2 Type When used as a serer in the TS7650G, its machine type and model are 3958 DD3. Use this machine type and model for serice purposes DD1 This is the original serer aailable in August This serer is based on the IBM System x3850 M2 Type When used as a serer in the TS7650G, its machine type and model are 3958 DD1. Use this machine type and model for serice purposes. System console The system console is a TS3000 System Console (TSSC). This document uses the terms system console and TSSC interchangeably. Under IBM best practices, the TS7650G also contains the following: Disk controller The customer must choose the disk controller for use with the Copyright IBM Corp xiii

16 TS7650G. A list of compatible controllers is located at the IBM Tape Systems Resource Library website: systems/storage/tape/library.html#compatibility in the TS7650/TS7650G ISV and interoperability matrix document. Disk expansion unit The customer must choose the disk expansion unit for use with the TS7650G. A list of compatible expansion units is located at the IBM Tape Systems Resource Library website: systems/storage/tape/library.html#compatibility in the TS7650/TS7650G ISV and interoperability matrix document. OpenStorage OpenStorage allows ProtecTIER to be integrated with NetBackup to proide the means for backup-to-disk without using a irtual tape library (VTL) emulation. Using a plug-in that is installed on an OpenStorage-enabled media serer, ProtecTIER can implement a communication protocol that supports data transfer and control between the backup serer and the ProtecTIER serer. Therefore, to support the plug-in, ProtecTIER implements a storage serer emulation. replication A process that transfers logical objects like cartridges from one ProtecTIER repository to another. The replication function allows ProtecTIER deployment to be distributed across sites. Each site has a single or clustered ProtecTIER enironment. Each ProtecTIER enironment has at least one ProtecTIER serer. The ProtecTIER serer that is a part of the replication grid has two dedicated replication ports that are used for replication. Replication ports are connected to the customer's WAN and are configured on two subnets as default. replication grid A set of repositories that share a common ID and can potentially transmit and receie logical objects through replication. A replication grid defines a set of ProtecTIER repositories and actions between them and is configured using the ProtecTIER Replication Manager. The ProtecTIER Replication Manager is a software component that is installed on a ProtecTIER serer or a dedicated host. The ProtecTIER Replication Manager should be able to recognize all the members of the entire network the ProtecTIER Replication Manager handles on both replication subnets. The ProtecTIER Replication Manager is deployed separately from the ProtecTIER Manager on the customer's ProtecTIER serer. The ProtecTIER Replication Manager manages the configuration of multiple replication grids in an organization. An agent on eery node in each ProtecTIER serer interacts with the serer and maintains a table of its grid members. replication grid ID A number from 0 to 63 that identifies a replication grid within an organization. replication grid member A repository that is a member in a replication grid. replication pairs Two repositories within a replication grid that replicate from one to another. replication policy A policy made up of rules that define a set of objects (for example, VTL cartridges) from a source repository to be replicated to a target repository. xi IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

17 repository unique ID (RID) A number that uniquely identifies the repository. The RID is created from the replication grid ID and the repository internal ID in the grid. replication timeframe A scheduled period of time for replication to take place for all policies. shelf A container of VTL cartridges within a ProtecTIER repository. irtual tape library (VTL) The ProtecTIER irtual tape library (VTL) serice emulates traditional tape libraries. By emulating tape libraries, ProtecTIER VTL enables you to transition to disk backup without haing to replace your entire backup enironment. Your existing backup application can access irtual robots to moe irtual cartridges between irtual slots and dries. The backup application perceies that the data is being stored on cartridges while ProtecTIER actually stores data on a deduplicated disk repository. isibility switching The automated process that transfers the isibility of a VTL cartridge from its master to its replica and ice ersa. The isibility switching process is triggered by moing a cartridge to the source library Import/Export (I/E) slot. The cartridge will then disappear from the I/E slot and appear at the destination library's I/E slot. To moe the cartridge back to the source library, the cartridge must be ejected to the shelf from the destination library. The cartridge will then disappear from the destination library and reappear at the source I/E slot. Who should read this document This publication is for storage administrators, system programmers, and performance and capacity analysts. What's new in this release This document proides information on the following functions aailable in release 3.1: OpenStorage network configuration for the ProtecTIER Backup serer chapter added. Many-to-many replication information has been added. Feature codes hae been added or changed. Getting information, help, and serice If you need help, serice, technical assistance, or just want more information about IBM products, you will find a wide ariety of sources aailable from IBM to assist you. Aailable serices, telephone numbers, and web links are subject to change without notice. Information IBM maintains pages on the World Wide Web where you can get information about IBM products and serices and find the latest technical information. For more information refer to Table 1 on page xi. About this document x

18 Table 1. IBM websites for help, serices, and information Description Web address (URL) IBM home page Directory of worldwide contacts Support for IBM System Storage and TotalStorage products Note: Go to this site for information about the TS7650G and do the following: 1. Select Tape systems from the Product family list. 2. Select TS7650G with ProtecTIER from the Product list. Help and serice You can call 1 (800) IBM SERV for help and serice if you are in the U.S. or Canada. You must choose the software or hardware option when calling for assistance. Note: This product is equipped with a Software Call Home feature. When enabled, it will notify IBM Serice of software error eents. Not all countries currently support this feature, please contact your next leel of support for more information. Choose the software option if you are uncertain if the problem inoles TS7650G software or TS7650G hardware. Choose the hardware option only if you are certain the problem solely inoles the TS7650G hardware. When calling IBM for serice regarding the TS7650G: Software option Identify the TS7650G as your product and supply your customer number as proof of purchase. The customer number is a 7-digit numeric ( to ) assigned by IBM when the process ID PID is purchased and should be located on the customer information worksheet or on the inoice from the software purchase. Hardware option Proide the serial number and appropriate 4-digit Machine Type for the hardware component that displays a problem (for example, 3958 DD1, 3958 DD3, or 3958 DD4). Note: Disk modules and disk controllers are supported separately within the TS7650G Gateway. If the problem is known to be in the IBM attached storage component, select the hardware option and enter the appropriate Machine Type and Serial Number (S/N) for the component. If the attached storage is not IBM branded, contact the appropriate serice proider for the component. Getting help online Proides web addresses for getting help online. Be sure to isit the following support page for the TS7650G, complete with FAQs, parts information, technical hints and tips, technical publications, and downloadable files, if applicable: xi IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

19 Web sites For additional websites, see Web sites. Before you call for serice This section gies instructions on where to find assistance before you call for serice. Some problems can be soled without outside assistance, by using the online help, by looking in the online or printed documentation that comes with the TS7650G, or by consulting the support web page. Also, be sure to read the information in any README files and release notes that come with the TS7650G. Getting help by telephone This section describes how to get help by telephone. With the original purchase of the TS7650G software identifier, getting help by telephone is aailable. The software identifier can be either the product name (TS7650G ) components, or your proof of purchase. When calling, hae the following information aailable: Description of the problem Exact wording of any error messages Hardware and software configuration information If possible, hae access to your computer when you call. In the U.S. and Canada, these serices are aailable 24 hours a day, 7 days a week. In the U.K., these serices are aailable Monday through Friday, from 9:00 a.m. to 6:00 p.m. In all other countries, contact your IBM reseller or IBM marketing representatie. The most up-to-date information about your product, including documentation and the most recent downloads, can be found at the following Web sites: The translated publications for this product are included with the product. These documents and product specification sheets are also aailable from the following Web site: brandmain?brandind= You can order publications through the IBM Publications Ordering System at the following web site: Access installation and technical support information ia the Web at: For DS4000 information, go to the following Web site: The IBM HBA search Web site is: The IBM Web site for Independent Software Vendor (ISV) support is: About this document xii

20 Related publications To access the IBM TS7650G Interoperability Matrix Web site, go to: displayesssearchwithoutjs.wss?start_oer=yes For the latest information about SAN switches and directors, go to the following Web site: For the latest information about IBM xseries products, serices, and support, go to the following Web site: For the latest information about operating system and HBA support, clustering support, SAN fabric support, and Storage Manager feature support, see the DS4000 Interoperability Matrix at the following Web site: For product firmware and software downloads, as well as associated drier code, go to the following Web site: selectproduct?brandind= &familyind=0&oldbrand=0&oldfamily=0 &oldtype=0&taskind=1&psid=bm For accessibility information, go to the following Web site: For the latest information about product recycling programs, go to the following Web site: This section lists additional publications related to the product. The following documents proide information about the TS7650G components and related hardware. TS7650G publications The following publications proide information about the TS7650G irtualization solution. IBM System Storage TS7650G ProtecTIER Deduplication Gateway Installation Roadmap Guide, IBM form number GA IBM System Storage ProtecTIER User's Guide for Enterprise Edition and Appliance Edition, IBM form number GA IBM System Storage Problem Determination Guide for the TS7650 ProtecTIER Deduplication Appliance and TS7650G ProtecTIER Deduplication Gateway, IBM form number GA IBM System Storage Labeling Instructions for the TS7650 ProtecTIER Deduplication Appliance and TS7650G ProtecTIER Deduplication Gateway, IBM part number 95P8301 Gateway serer (3958 DD4) publications The following publications proide additional information about the gateway serer. IBM System x3850 M2 and System x3950 M2 Type 7141 and 7233 User's Guide xiii IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

21 IBM System x3850 M2 and System x3950 M2 Type 7141 and 7233 Problem Determination and Serice Guide Remote Superisor Adapter publications Remote Superisor Adapter II Slimline and Remote Superisor Adapter II Installation Guide Remote Superisor Adapter II Slimline and Remote Superisor Adapter II User's Guide System console (TSSC) publication How to send your comments The following publication proides additional information about the gateway serer: IBM System Storage TS3000 System Console (TSSC) Maintenance Information Your feedback is important in helping to proide the most accurate and highest quality information. To submit any comments about this book or any other IBM System Storage TS7600 with ProtecTIER documentation: Send your comments by to Be sure to include the following information: Exact publication title and ersion Publication form number (for example, GC ) Page, table, or illustration numbers that you are commenting on with a detailed description of any information that should be changed About this document xix

22 xx IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

23 Chapter 1. Introduction The IBM System Storage TS7650G ProtecTIER Deduplication Gateway (TS7650G) is a data deduplication and replication solution that compresses and stores backup data on your disk storage array. The replication function allows ProtecTIER (PT) deployment to be distributed across sites. To facilitate backup applications that are designed for use with tape storage, the TS7650G emulates a traditional tape library unit. The TS7650G is aailable in a stand-alone configuration, or in a clustered configuration which facilitates increased throughput and higher aailability. Note: IBM does not support more than one clustered pair of TS7650 Gateway serers in a single frame. The TS7650G uses IBM technology and software to emulate DTC VTF 0100, ATL P and TS3500 tape libraries. This emulation capability is designed to help customers achiee the following operational and throughput efficiencies: Backup window reduction Restoration time reduction Data sharing and resource irtualization optimization Operational efficiency Improed sharing of irtual tape libraries across applications and serers The disk storage array attaches to the TS7650G through Fibre Channel connections and holds the repository of factored backup data. The amount of cache aailable depends on your disk subsystem and configuration. The TS7650G supports the following disk subsystems: IBM System Storage DS8300 IBM System Storage DS8100 IBM System Storage DS5300 IBM System Storage DS5100 IBM System Storage DS4800 IBM System Storage DS4700 IBM System Storage DS4300 IBM System Storage DS4200 IBM System Storage DS3400 IBM System Storage V7000 IBM XIV 2810 IBM SAN Volume Controller and up XIV Nextra HDS AMS1000 HDS AMS2300 HP EVA 8100 HP EVA 8400 EMC CX series Copyright IBM Corp

24 TS7650G hardware components The TS7650G is aailable in stand-alone and clustered configurations. For a stand-alone configuration, one IBM machine type and model 3958 DD4 serer is required. For a clustered configuration, two 3958 DD4 serers are required, along with an FC 3437 Cluster Connection Kit, which consists of: two 1 Gb (gigabit) Ethernet switches, SMC model 8126L2 one network power switch, Western Telematic, Inc. (WTI) model VMR-8HD20-2 power cables Ethernet cables mounting hardware Notes: Existing stand-alone 3958 DD1 serers may be upgraded to a clustered configuration by clustering a 3958 DD1 serer and a 3958 DD3 serer. In all cases, the clustered serers must be installed in the same frame. IBM does not support more than one clustered pair of TS7650 Gateway serers in a single frame. Red Hat Enterprise Linux 5.4 Adanced Platform is required to run on the gateway serer. For more information, see TS7650G feature codes on page 25. An IBM Total Storage System Console (TSSC) and the accompanying Keyboard/Video/Monitor (KVM kit) (purchased separately) are also required for installation, serice, and maintenance of the TS7650G. IBM recommends that the TSSC be installed in the same rack as the gateway serer. Howeer, an existing TSSC may be used, proided it is within 100 feet of the gateway serer. For the TS7650G to be fully functional, additional hardware components (purchased separately) are required. These components include frame(s), disk controller(s), and disk expansion modules. The lists below outline the additional hardware purchases recommended for each deployment option of the TS7650G: Stand-alone Gateway One customer-supplied serer frame One customer-supplied disk storage frame Clustered Gateway One customer-supplied serer frame One or more customer-supplied disk storage frames Replication Gateway Two customer-supplied serer frames One or more customer-supplied disk storage frames per serer frame Each customer-supplied frame must contain two 220V power distribution units, and proide sufficient rack space in order to accommodate: In a stand-alone configuration, the serer frame must proide either 4u or 6u of rack space. 4u of rack space for one gateway serer. 2 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

25 2u of rack space for one TSSC, or no additional rack space if an existing TSSC is used. In a clustered configuration, the serer frame must proide 11u or 13u of rack space. 8u of rack space for two gateway serers. 2u of rack space for one TSSC, or no additional rack space if an existing TSSC is used. 2u of rack space for two Ethernet switches. 1u of rack space for one Network Power Switch. In a replication configuration, the serer frames required depend on the planned hardware configuration of the source and destination serer(s). If stand-alone to stand-alone, duplicate the stand-alone configuration listed aboe for the second frame. If the source and destination frames are clustered, duplicate the clustered configuration listed aboe for the second site. Possible existing gateway upgrade scenarios: Existing TS7650G installation with DD3 serers, adding new DD4 serers for replication. Existing TS7650G installation with DD4 serers, adding new DD4 serers for replication. Existing TS7650G installation with DD3 or DD4 serers, adding replication functionality, no new hardware required for DD4, for DD1 or DD3, a second ethernet adapter is needed (Feature Code 3448). Existing DD3 clustered with a new DD4 VTL system. DD4 VTL system clustered with another DD4 VTL system. DD4 OpenStorage system clustered with another 3958 DD4 OpenStorage system. Possible new gateway installation scenarios: New TS7650G installation, clustered or stand-alone, with replication (VTL or OpenStorage). New TS7650G installation, clustered or stand-alone, without replication (VTL or OpenStorage). Figure 1 on page 4 identifies the serer components present in a fully configured, clustered TS7650G. Chapter 1. Introduction 3

26 EIA EIA Holes Unit Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) Empty (1u) TSSC (1u) KVM Tray + TSSC sw (1u) Empty (1u) 1 Gb Network Switch (1u) 1 Gb Network Switch (1u) ProtecTIER Serer (4u) Empty (1u) ProtecTIER Serer (4u) WTI Power Switch (1u) Power Distribution Unit (1u) Power Distribution Unit (1u) Empty (1u) EIA EIA Unit Holes ts Figure 1. TS7650G serer frame components For the disk storage frame(s), the amount of rack space and the number of frames required aries depending on the type of disk storage that is being used. For example, one IBM System Storage DS4700 disk controller and six IBM System Storage DS4000 EXP810 disk expansion modules require 21u of rack space in the frame. In a clustered configuration with two controllers and 12 expansion modules, an additional disk storage frame may be required. Gateway serer (3958 DD4) The gateway serer proides the connections to the TSSC and the customer SAN network (for connection to the client hosts and irtual tape libraries). Figure 2 on page 5 shows the LEDs and connectors on the rear of the gateway serer. 4 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

27 3958-DD4 Serer P1 P A1 A2 B V S E1 E3 E2 E4 9 ts Figure 2. Gateway serer rear iew Table 2. Serer rear iew: Slot assignments, ports, and connections Slot, Port or Connection VTL use OpenStorage use 1 Slot 1: Emulex fibre channel Host Blank Bus Adapter (HBA) 2 Slot 2: Emulex fibre channel HBA Blank 3 Slot 3: Blank Intel Pro Quad-port gigabit Ethernet adapter (Port 1 = Eth8, Port 2 = Eth9, Port 3 = Eth10, Port 4 = Eth11) 4 Slot 4: Blank Intel Pro Quad-port gigabit Ethernet adapter (Port 1 = Eth4, Port 2 = Eth5, Port 3 = Eth6, Port 4 = Eth7) 5 Slot 5: Intel Pro Quad-port gigabit Ethernet adapter (Port 1 = Eth0, Port 2 = Eth1, Port 3 = Eth2, Port 4 = Eth3) Quad-port gigabit Ethernet adapter (Port 1 = Eth0, Port 2 = Eth1, Port 3 = Eth2, Port 4 = Eth3) 6 Slot 6: Qlogic HBA Qlogic HBA 7 Slot 7: Qlogic HBA Qlogic HBA 8 QPI Slot 1 Not used Not used 9 QPI Slot 2 Not used Not used A1 Integrated Ethernet 1 (Eth4) (Eth12) port A2 Integrated Ethernet 2 (Eth5) (Eth13) port B Integrated Ethernet 3 (Eth6) (Eth14) port V RSA Video port S Serial Attached SCSI (SAS) port E1 Uniersal Serial Bus (USB) port 1 E2 Uniersal Serial Bus (USB) port 2 E3 Uniersal Serial Bus (USB) port 3 E4 Uniersal Serial Bus (USB) port 4 Chapter 1. Introduction 5

28 Table 2. Serer rear iew: Slot assignments, ports, and connections (continued) P1 Power connection P2 Power connection Gigabit Ethernet LED 1: When this LED is lit, it indicates that the gateway serer is transmitting to or receiing signals from the Ethernet LAN connected to the Ethernet port. Gigabit Ethernet 1 connector: Use this connector to connect the gateway serer to a network. Gigabit Ethernet LED 2: When this LED is lit, it indicates that the gateway serer is transmitting to or receiing signals from the Ethernet LAN connected to the Ethernet port. Gigabit Ethernet 2 connector: Use this connector to connect the gateway serer to a network. Integrated Management Module (IMM): Use this connector to connect the gateway serer to a network for systems-management information control.. The ac and dc power LEDs: Each hot-swap power supply has an ac power LED and a dc power LED. During typical operation, both the ac and dc power LEDs are lit. For additional information about the gateway serer ports, see Hardware, cabling, and infrastructure responsibilities on page 38. The following illustration shows the controls, LEDs, and connectors on the front of the serer ts Figure 3. Gateway serer front iew Table 3. DD4 Serer front iew Callout 1 2 Description Electrostatic discharge connector DVD-eject button: Press this button to release a CD or DVD from the DVD drie. 6 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

29 Table 3. DD4 Serer front iew (continued) DVD drie actiity LED: When this LED is lit, it indicates that the DVD drie is in use. USB connectors: Connect USB deices to these connectors. Scalability LED Operator information panel: This panel contains controls and LEDs. Hard disk drie actiity LED: On some serer models, each hot-swap hard disk drie has an actiity LED. When this LED is flashing, it indicates that the drie is in use. Hard disk drie status LED: On some serer models, each hot-swap hard disk drie has a status LED. When this LED is lit continuously, that indiidual drie is faulty. When the drie is connected to the integrated SAS controller with RAID capabilities, a flashing status LED indicates that the drie is a secondary drie in a mirrored pair and the drie is being synchronized. The following illustration shows the controls and LEDs on the operator information panel ts Figure 4. Gateway serer operator information panel Table 4. Operator information panel Callout Description Power control button coer: Slide this coer oer the power-control button to preent the serer from being turned off accidentally. Power control button/power-on LED: Press this button to turn the serer on and off manually. Ethernet icon LED: This LED lights the Ethernet icon. Ethernet port actiity LEDs: When these LEDs flash, they indicate that there is actiity between the serer and the network on the indicated port. Chapter 1. Introduction 7

30 Table 4. Operator information panel (continued) 5 Locator button/locator LED: Press this button to turn the locator LED on and off manually. In multi-node configurations, press this button to turn the locator LED on and off in all nodes in the configuration. 6 Information LED: When this LED is lit, it indicates that there is a suboptimal condition in the serer and that light path diagnostics will light an additional LED to help isolate the condition. This LED and LEDs on the light path diagnostics panel remain lit until you resole the condition or you press the remind button. 7 System-error LED: When this LED is lit, it indicates that a system error has occurred. An LED on the light path diagnostics panel is also lit to help isolate the error. Software for the TS7650G This section briefly describes the software used with the TS7650G. ProtecTIER is a disk-based data storage system. It uses data de-duplication technology to store data to disk arrays. Before you begin using ProtecTIER and following the procedures described in this document, be sure you hae completed the planning, preparation, and installation tasks described in the IBM System Storage TS7600 with ProtecTIER Introduction and Planning Guide, IBM publication number: GC , and installed IBM ProtecTIER Manager. Note: Only install one of the backup solutions, either ProtecTIER Virtual Tape (VT) or OpenStorage. ProtecTIER Manager The ProtecTIER Manager workstation is a customer-supplied workstation that runs the ProtecTIER Manager software. The ProtecTIER Manager software proides the management GUI interface to the TS7650G. System requirements for the workstation are proided in this document in ProtecTIER Manager workstation requirements on page 38. Complete information about installing and using the ProtecTIER Manager console is proided in the IBM System Storage ProtecTIER User's Guide for Enterprise Edition and Appliance Edition, IBM form number GA Note: ProtecTIER Manager will not be optimal on all resolutions. 1280x1024 should be the optimal resolution. ProtecTIER Virtual Tape (VT) The ProtecTIER Virtual Tape (VT) serice emulates traditional tape libraries. By emulating tape libraries, ProtecTIER VT enables you to transition to disk backup without haing to replace your entire backup enironment. Your existing backup application can access irtual robots to moe irtual cartridges between irtual 8 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

31 slots and dries. The backup application perceies that the data is being stored on cartridges while ProtecTIER actually stores data on a deduplicated disk repository on the storage fabric. Storage Fabric ProtecTIER Serer Serer Running Backup Application Port 0 Port 1 Virtual Tape Dries Virtual Robot Virtual Cartridges and Slots Virtual Library Virtual Library Figure 5. Tape library emulation Repository OpenStorage With OpenStorage, ProtecTIER can be integrated with NetBackup to proide the means for backup-to-disk without haing to emulate tape. Using a plug-in that is installed on an OpenStorage-enabled media serer, ProtecTIER can implement a communication protocol that supports data transfer and control between the backup serer and the ProtecTIER serer. Therefore, to support the plug-in, ProtecTIER implements a storage serer emulation. Note: OpenStorage supports 12 many-to-many bidirectional replication. ts PT Repository Serer Running Backup Application IBM ProtecTIER plug-in Comm Client Figure 6. OpenStorage TCP/IP 0 M Comm Serer ProtecTIER Serer Storage Serer ProtecTIER Core LSU1 TSSC microcode If you hae an existing TSSC, the TSSC microcode must be at ersion or later before upgrading ProtecTIER. To check the ersion, go to the TS3000 System Console Screen Login screen as shown in Figure 7 on page 10. LSU2 STS ts Chapter 1. Introduction 9

32 Figure 7. TS3000 System Console Screen Login screen If an update is required, contact IBM Serice. ts TS7650G support and requirements This section proides support information for the TS7650G in the following areas: Deices supported Supported operating systems on page 11 Supported deice driers on page 11 Supported SAN switches on page 11 Deices supported The following irtual tape libraries and dries are supported: DTC VTF 0100 irtual tape libraries ATL P irtual tape libraries IBM TS3500 irtual tape libraries Quantum DLT 7000 dries IBM LTO-2 dries The latest firmware and drier code requirements for connection to these deices are posted on the following IBM website: Select Tape Systems from the Product family menu and select TS7650G from the Product menu. Click the Plan or Upgrade tab, and under Product Considerations, click TS7650G product information. 10 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

33 Supported operating systems The TS7650G is supported by a wide ariety of serers, operating systems, and adapters. These attachments can change throughout the life cycle of the product. To determine the latest attachments, or to get a comprehensie list of compatible software, perform one of the following: For a list of compatible software, operating systems, and serers for the TS7650G, isit the following website: Select Tape & optical from the Product family menu and select TS7650G from the Product menu. Contact your IBM Sales Representatie. Note: If you attach your TS7650G to a non-ibm platform with non-ibm software, IBM recommends that you contact your software endor to obtain a matrix of compatible hardware, software, firmware reisions, and adapter cards. Supported deice driers This section identifies ways to determine the latest deice driers for the dries of the TS7650G. IBM proides deice drier support for the TS7650G. IBM maintains the latest leels of deice driers and drier documentation. IBM Serice proides deice drier support as needed. Supported SAN switches The TS7650G supports a wide ariety of switches in the SAN enironment. All switches attached directly to the TS7650G must be loop protocol capable. These attachments can change throughout the product's life cycle. For information on supported switches and required code leels for the switches, do one of the following: For a list of compatible switches for the TS7650G, isit the web at: Select Tape & optical from the Product family menu and select TS7650G from the Product menu. Contact your IBM Sales Representatie. Notes: If you attach your TS7650G to a non-ibm platform with non-ibm software, IBM recommends that you contact your software endor to obtain a matrix of compatible hardware, software, firmware reisions, and adapter cards. The customer must use an additional connectiity deice between the optical Fibre directly connected to RMSS optical adapters (for example, Fibre, ESCON, or FICON) and an external public network. It can be a patch panel, router, switch, or other suitable deice. Optical Fibre connectiity that does not go oer a public network does not require an additional connectiity deice. Supported LUNs This section lists the LUN limits for a system setup. The maximum LUN size supported for the ProtecTIER Gateway is 8 Terabytes. This includes both MetaData and UserData. Chapter 1. Introduction 11

34 The minimum LUN size supported for the ProtecTIER Gateway is 20 GB. (This minimum is not recommended due to limited repository space.) The maximum number of LUNs supported for the Gateway is The minimum number of LUNs supported for a ProtecTIER Gateway is three: one for UserData, and two for MetaData. Data management and adanced features The TS7650G is designed with the following data management and adanced features that allow you to securely process and access your data according to your business needs een if it is 24 hours a day and 7 days a week. RAID support Redundant array of independent disks (RAID) is a method of configuring multiple disk dries in a storage subsystem for high aailability and high performance. The collection of two or more disk dries presents the image of a single disk drie to the system. In the eent of a single deice failure, data can be read or regenerated from the other disk dries in the array. The gateway supports the following RAID configurations: RAID 1 for the gateway serer's internal hard disk dries RAID 5 for user data on attached disk storage RAID 6 for user data on attached disk storage RAID 10 for metadata on attached disk storage Configure other items such as block size, channel protection, etc., in accordance with your disk storage manufacturer's instructions. Fencing The TS7650G's fencing option proides higher aailability for TS7650G operations by eliminating the down time that can occur should a gateway serer (software or hardware) fail. In the TS7650G fencing design, two gateway serers are installed in the same frame and configured to monitor each other. In the eent that one gateway serer fails to fulfill its responsibilities to the SAN clients it is sering, the other serer will take oer the failed gateway serer's resources. Fencing requirements Fencing is aailable only in a clustered TS7650G configuration. Follow these requirements when setting up a fencing configuration: You must hae two 3958 DD3s, two 3958 DD1 gateway serers, or one 3958 DD3 and one 3958 DD1 gateway serer in a single frame. One gateway serer is located at the bottom of the frame (node A, the lower serer in the rack) and the other gateway serer is located at the top of the frame (node B, the upper serer in the rack). Note: 3958 DD1 and 3958 DD4 cannot be clustered. Fencing with two gateway serers in different frames is not possible, because both gateway serers must be connected to the same Network Power Switch. 12 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

35 Static IP addresses must be used. Ethernet adapter 2 (eth1) on Node A (the lower serer in the rack) and Node B (the upper serer in the rack) must use different IP addresses. For more information, see Chapter 11, IP address worksheet, on page node actie-actie support 2 node actie-actie support permits the sharing of all disk storage between two gateway serers in a clustered configuration. LUN masking LUN masking is used to control deice isibility by allowing specific deices (for example, tape dries or robots) to be seen only by a selected group of host initiators. A host initiator is the WWN, or the physical address of a port of a fiber card of the host (that is, the serer that the backup application is installed on). LUN masking allows you to assign specific deices to a specific host running backup application modules. It enables multiple initiators to share the same target FC port without haing conflicts on the deices being emulated. The LUN masking setup can be monitored and modified at all times during system operation. LUN masking in ProtecTIER influences the isibility of the deices by the hosts systems. Keep in mind that eery modification to LUN Masking in ProtecTIER may affect the host configuration and may require rescanning by the hosts. Replication Replication proides complete system backup across sites. The replication function allows ProtecTIER (PT) deployment to be distributed across sites. Each site has a single or clustered PT enironment. Each PT enironment has at least one PT serer. The PT serer which is a part of the replication grid has two dedicated replication ports, Eth3 and Eth4, which are used for replication. Replication ports are connected to the customer's WAN and are configured on two subnets by default. Use the pt_net_perf_util utility in Chapter 13, ProtecTIER Replication Network Performance Validation Utility for VTL Systems, on page 79 to test maximal replication performance between two future PT repositories by emulating the network usage patterns of PT's Natie Replication component. This utility will not predict replication performance, but it may discoer performance bottlenecks. Many-to-one replication ProtecTIER many-to-one replication supports both single node and clustered ProtecTIER configurations. Many-to-one replication proides the following functionality and support: Setting replication performance limits - This feature allows the user to set system-wide physical and/or nominal limits in order to indicate to the replication engine the maximal replication transfer rate allowed in the network for a specific repository. The performance limits refer to oerall resource consumption of the system, and is reflected on to the network transfer rate. Performance limits are based on the Replication Rate Control mechanism, which has been enhanced. Current Replication Rate Control (RRC) is used when a user does not proide a time frame and the system replicates continuously. The Chapter 1. Introduction 13

36 enhancement is in the rate calculation. The rate calculation uses performance limits to understand the maximum rate possible in both leels of system usage (IDLE, BUSY) and then it normalizes the rate accordingly. Resering space for hub repository - This feature proides the ability to exclusiely assign a fragment of a hub repository's capacity for local backups. In large deployments with many spokes replicating, capacity management done by the user might cause a situation where replication is trying to occupy all the space in hub repository. Since the assumption is that backup has precedence oer replication, this feature has been added to ensure that capacity is resered only for local backup, so that replication cannot be written to this storage fragment. Error notifications appear in the eent the capacity resered for the local backup or the capacity resered for replication on the repository hub is running out of space. Enhanced monitoring of repository space consumption - This enhancement is displayed in the GUI as a nominal data pie, where a user can get at-a-glance the proportion of the nominal data out of the repository and the internal capacity distribution of replication data s. local backup data and free space. Additional Replication information in Repository's cartridge iew - This feature adds cartridge replication properties such as: last update time, destination, etc. to a new replication iew that adds replication properties for cartridges which are also displayed in the regular cartridge iew. This feature allows the user to see replication properties for a batch of cartridges each in a single row. Sorting capability for the new replication fields was added, to stay on par with the sorting capabilities for the rest of the cartridge fields. Disaster Recoery site replaces production site operation - This feature supports a scenario where a disaster recoery site (the hub) is chosen to replace one of its spokes permanently. The feature allows the user to take oer the responsibility for the cartridges of the old spoke after running the replace repository wizard from the Replication Manager. Enhanced Timeframe support - This feature enhances the repository timeframe attribute to be a weekly scheduler on a repository leel. The timeframe is a set of 30 minute time interals across a full week. The user chooses at which time interal the replication should run during a single week. The new timeframe also uses the performance limits feature for limiting the replication rate when in timeframe. Command Line Interface for Disaster Recoery - This feature adds a Command Line Interface (CLI) that allows a user to run complex queries on cartridges and proides cartridge batch moe operation during a manual DR procedure. The feature allows the user to query ProtecTIER in order to obtain a list of cartridges that falls under specific criteria. The query criteria are cartridge replication properties and cartridge location properties. Replication grid The replication grid is defined as an entity that supports replication between its members. The replication grid members are PT repositories and are configured using a Replication Manager (RM). The RM is a software component that may be installed on a dedicated host or on a PT machine. The RM should be able to see all of the members of the whole network the RM handles on both replication subnets. A replication grid defines a set of PT repositories and actions between them. The RM is serer software that is separately deployed on the customer's WAN or on a PT machine. The RM can manage the configuration of multiple replication grids in an organization. An agent on each PT system (specifically on eery node) interacts with the serer and maintains a table of its grid's members. 14 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

37 Important: Be sure to coordinate between the source and destination sites to ensure that the serers at both locations are fully configured before the you use the ProtecTIER Replication Manager GUI to create the replication grid. Consult with Solutions Assurance and your IBM Representatie for assistance and information. Many-to-one replication defines the following two roles in a replication grid: Spoke - A backup target that can only replicate to a single hub, may not be a target for replication. Hub - A replication and backup target, may receie replication from up to 12 spokes, may not replicate (besides failback). A group of one hub and 1-12 spokes is referred to as a topology group. A single grid may include up to eight hubs and therefore up to eight topology groups. Spokes do not need physical connections between them. All repositories need a network connection to the replication manager serer (a PT or dedicated host ia RPQ approal). Note: When upgrading from one-to-one replication to many-to-one replication, the Replication Manager serer automatically upgrades the grid's database; therefore all replication pairs will be set as hub and spoke accordingly. The GUI behaes as its multiple many-to-one pairs. The GUI behaes as its multiple many-to-one pairs. OpenStorage also supports a group of 12 repositories replicating in many-to-many bidirectional topology. Supported replication configurations This list shows all of the supported replication configurations: DD1 (source serer) + DD1 (destination serer) - (s+s), (c+c), (c+s), (s+c) DD1 (source serer) + DD3 (destination serer) - (s+s), (c+c), (c+s), (s+c) DD3 (source serer) + DD3 (destination serer) - (s+s), (c+c), (c+s), (s+c) DD1 (source serer) + AP1 (destination serer) - (s+s), (c+c), (c+s), (s+c) DD3 (source serer) + AP1 (destination serer) - (s+s), (c+c), (c+s), (s+c) AP1 (source serer) + AP1 (destination serer) - (s+s), (c+c), (c+s), (s+c) Legend: s = stand-alone c = cluster Chapter 1. Introduction 15

38 16 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

39 Chapter 2. Physical planning specifications for the TS7650G Site preparation This section proides physical planning and site specifications for the TS7650G. Before the TS7650G is installed at your site, erify that the planned installation site meets these requirements, or prepare the site so that it does meet these requirements. Preparations might inole meeting area requirements, enironmental requirements, and electrical requirements for TS7650G installation, serice, and operation. Use the information in this section to prepare a location for installation of the system's components. Prepare a floor plan that includes the following information: Power outlet locations, types, and ratings Frame locations Operator and serice clearances Dimensions of the area containing all system components Before hardware installation can begin, the local installation planning representatie must erify that all installation planning and preparation is complete. Additional user responsibilities include planning for the following: Cabling and wiring for connections to the host Cooling and heating Telephone serice Safety and security Fire detection and suppression Floors (both raised and non-raised) that meet the operational and structural requirements necessary for the system components Important: For replication to be enabled, the serers at both source and destination locations must be fully installed and configured before any other steps are taken. Use this information for planning at both sites as needed. Consult with Solutions Assurance and your IBM Representatie for assistance and information. Calculating space requirements Lighting considerations When you plan the installation location, first calculate the total amount of space that is needed for the TS7650G units, including all serice clearances and weight distribution areas. The TS7650G is designed for lights-out operation. No special lighting considerations apply. Copyright IBM Corp

40 Upgrade considerations Accommodating cables Height requirements When planning for system installation, consider any potential future growth such as the addition of expansion frames. Consult your IBM representatie for current planning information regarding upgrades to the TS7650G. Reiew the following considerations when planning for cabling accommodations: Electrical power cabling should be planned in adance of deliery of the TS7650G. This planning includes cabling for a second source if the dual power option has been ordered and if independent sources are intended to be used. Fibre Channel cabling from the TS7650G adapters to the attaching customer serers or customer switch fabric should be included in the planning, as well as Fibre Channel cabling to any attached physical disk storage. In addition, customers should plan for the Fibre Channel cabling from the serer frame to the disk storage frame. Cat-5e Ethernet cabling is required for attachment of the TS7650G to the TSSC, operator console or consoles, and to the network for replication and for call-home reporting. Clustered configurations require a network connection for the corresponding Ethernet ports on the two gateway serers for mutual operational state monitoring. An analog phone line is required for remote access to the TSSC for TS7650G support. The minimum floor-to-ceiling clearance required for installation as well as the required operating and serice clearances are determined by the dimensions of the customer-supplied frames. IBM recommends that serer components be installed in a separate frame from disk storage components. For more information, refer to TS7650G hardware components on page 2. Dimensions and weights of models When you are planning the floor and space requirements for your storage units, consider the dimensions and weights of your configuration components. TS7650G component dimensions Table 5 lists the TS7650G component dimensions. Table 5. TS7650G component dimensions Component Height Width Depth 3958 DD mm (7.0 in) mm (19.0 in) mm (28.0 in) Weight The total weight of the TS7650G depends on the number of components installed. Table 6 on page 19 lists the weight of each component. 18 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

41 Table 6. TS7650G component weights Unit TS7650G 3958 DD4 Weight 43.2 kg (95.25 lb) Operator and serice clearances Clearances are required around system components for the operator and the serice representatie to perform certain tasks. See Table 7 for specific clearance requirements. Table 7. Operator and Serice Clearance Requirements Component Customer-Supplied Frame (see note 2 below) Area Size (Width Depth) (see note 1 below) Notes: 1. Size is defined by the depth from the outside of the frame and either the width of a stand-alone frame or the length along any frames installed side-by-side. The width is on a frame-to-frame basis; space required in front or behind each frame is additie. The access space for indiidual frames oerlaps. 2. Required clearance around the frame is listed below: Front: 690 mm (27.2 in.) Back: 660 mm (26.0 in.) Side: 0 mm (0 in.) Unlike weight distribution areas that are required to handle floor loading, keep in mind that serice clearances of adjacent unrelated storage units can oerlap. Note: The terms serice clearance and weight distribution area are often confused with each other. The serice clearance is the area required to open the serice coers and to pull out components for sericing. The weight distribution area is the area required to distribute the weight of the storage unit. Aisle and door clearances Two persons should be aailable to moe system components between locations. The following are the minimum aisle and door dimensions for moing components from one location to another: Roof Height 1830 mm (72 in.) Aisle and Door Width 736 mm (29 in.) Corner Radius 2237 mm (88 in.) Ramp Inclination 15 Chapter 2. Physical planning specifications 19

42 Floor requirements A customer-supplied frame can be installed on a raised or solid floor meeting the minimum leeling and floor-loading capacity requirements. Floor leel requirements The customer-supplied frame should proide leeling pads that can be adjusted to compensate for an uneen floor where the frame is to be installed. The maximum out-of-leel condition is 25.4 mm (1 in.) oer the frame's length and width. Weight distribution and floor loading If the customer-supplied frame is installed on a raised floor, the raised floor should be stabilized to preent a horizontal shift of the raised floor structure. Security considerations IBM recommends a floor load rating of at least 341 kg/m 2 (70 lb./ft. 2 ). These ratings do not include additional loading by personnel and equipment traffic. Controlling access to the TS7650G is the customer's responsibility. The system should be installed in a controlled-access area to preent unauthorized access to the system's internal components, the TSSC, and ProtecTIER Manager console. For troubleshooting purposes, an IBM serice representatie may need to use the TSSC to open an SSH session on the gateway serer. To do so, the IBM serice representatie will need the ptadmin account password. If the customer has changed the default password, the customer must make the new password aailable to the IBM serice representatie upon request. Operating enironment requirements You must meet specific operating enironment requirements at all the air intake locations of your models. The operating points ary depending on the state of the model. The models can be in the following states: Operating Powered off In storage In transit Table 8 on page 21 lists the acceptable temperature and humidity ranges in which the TS7650 Appliance is designed to operate. 20 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

43 Table 8. Temperature and humidity requirements Condition Parameter Requirement Temperature 1 Operating range [Altitude: 0 to 914 meters (0 to 3,000 feet)] C (50-95 F) Relatie humidity (no condensation) Wet bulb temperature (maximum) Operating range [Altitude: 900 to 2133 meters (3,000 to 7,000 feet)] C (50-90 F) Note: Aboe 900 m, decrease maximum operating temperature by 1 C. Recommended operating C ( F) range Power off range C (50-95 F) Storage range 0-60 C ( F) Transit range -40 C to 60 C (-40 F to 140 F) Operating range 8% to 80% Recommended operating 40% to 55% range Power off range 8% to 80% Storage range 5% to 80% Transit range 5% to 100% Operating range 23 C (73 F) Power off range 27 C (80 F) Storage range 29 C (84 F) Transit range 29 C (84 F) Notes: 1. The non-operating enironment must not exceed the operating enironment limits for longer than 60 days. 2. The storage enironment must not exceed the operating enironment limits for longer than one year. 3. Substantial deiations from the suggested operating range, in either direction, if sustained for extended periods of time, exposes the unit to greater risk of failure from external causes. Electrical power ratings for the TS7650G This section includes tables with the electrical power ratings for the TS7650G. The customer must supply two 220V power distribution units in the customer-supplied frame. Table 9. Recommended power ratings for TS7650G 3958 per line cord Product Input oltage Input frequency Current Inrush current Power Apparent power 3958 DD V ac Hz 7 A 250 A 1620 W 1.65 kva 5.5 KBtu/hr Chapter 2. Physical planning specifications 21

44 Table 10. Recommended power ratings for clustered TS7650G 3958 per line cord Product Input oltage Input frequency Current Inrush current Power Apparent power 3958 DD V ac Hz 14 A 250 A 3240 W 3.24 kva 11.0 KBtu/hr Note: The clustered TS7650G is connected through an included remote network power switch. These figures refer to the requirements for that configuration. Table 11. FC 3437 Cluster Connection Kit power requirements Unit WTI Network Power Switch, Model VMR-8HD20-2 SMC Networks Ethernet switch, Model 8126L2 Input oltage Input frequency Maximum load per outlet Maximum load per bus Vac 50-60Hz 10A 16A 32A Maximum load per unit Power Vac 50-60Hz 38W Acoustic declaration for the TS7650G components This section includes a table with the acoustic declaration for the TS7650G components. Table 12 describes the acoustical noise emissions for the 3958 DD4 gateway serer. Table 12. Acoustic declaration for the 3958 DD4 gateway serer Sound power Operating Idling 6.6 bel declared 6.6 bel declared Note: 10 db (decibel) = 1 B(bel) Considering safety issues You must consider arious safety issues when you plan your TS7650G location. The following list identifies some of the safety issues that you must consider: Fire suppression Earthquake safety Proiding a fire-suppression system You are responsible for proiding a fire suppression system for your TS7650G. IBM designs and manufactures equipment to internal and external standards that require certain enironments for reliable operation. Because IBM does not test any equipment for compatibility with fire-suppression systems, IBM does not make compatibility claims of any kind. IBM does not proide recommendations on fire-suppression systems. 22 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

45 Consult your insurance underwriter, local fire marshal, or local building inspector about selecting a fire-suppression system that proides the proper leel of coerage and protection. Earthquake effects There is no guarantee against equipment damage as a result of an earthquake. Many factors influence the stress imposed on system equipment, including: Intensity and duration of the earthquake Equipment structural strength and durability Equipment location within a structure Equipment installation method Building type Soil conditions Guarantees of equipment reliability cannot be made for all earthquakes and conditions. The damaging effects of an earthquake are minimized by appropriate installation and planning techniques. Significant sliding and rocking of equipment during an earthquake might directly or indirectly result in damage. The following steps can help minimize damage: Position equipment far enough from walls to preent or minimize collision. Ensure that power and accessory cables are long enough to accommodate sliding and flexing during an earthquake. Ensure that cable clamps or other strain reliefs are secured properly to equipment. Secure seeral tall units together to form a more stable structure. Use a flexible restraint that allows a limited amount of moement, approximately 75 mm to 150 mm (3 in. to 6 in.), to dissipate energy imparted by the earthquake. Chapter 2. Physical planning specifications 23

46 24 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

47 Chapter 3. TS7650G components and feature codes TS7650G feature codes This section describes the TS7650G components and lists the required and optional feature codes for each component. Note: In addition to the components and feature codes listed in the following sections, the customer must also purchase Red Hat Enterprise Linux 5.4 Adanced Platform, which is required to run on the gateway serer. One Red Hat license is required for each gateway serer. The appropriate number of licenses must be purchased from IBM, along with one-year or three-year Red Hat support subscriptions that match the maintenance period purchased for the TS7650G. Use PID 5639-RHL with feature 0017 (1 year support) or feature 0019 (3 year support) to purchase the appropriate number of Red Hat licenses and support. Red Hat Linux 5.4 Adanced Platform is shipped on a recoery disk which can be used to restore the operating system on the gateway serer in the eent of a hardware failure. This section discusses in detail the required and optional features for the TS7650G. Feature codes are proided for the following components: Feature codes for 3958 DD4 Gateway Serer 5639-XXB ProtecTIER Enterprise Edition V3.1 Base Software on page 32 Attention: The license keys required for TS7650G feature enablement require that the TS7650G VE console software be installed and functional before any IBM System Storage TS7650G ProtecTIER Deduplication Gateway features can be enabled. Feature codes for 3958 DD4 Gateway Serer This section lists the feature codes to use when you order the required and optional features for the gateway serer. The TS3000 System Console is required for sericing the TS7650G Gateway. FC 2714 and FC 2715 proide connectiity to an existing TS3000 System Console. FC 2722 proides the first TS3000 System Console. The connection to a working TSSC is required for the 3958 DD4. The TSSC is the serice console and supports remote access and call home functions. The 3958 DD4 gathers logs and sends them to the TSSC as part of a call home packet sent to RETAIN. In cases where external connection for the TSSC is not allowed, the TSSC is the repository of the logs and is still a requirement. FC 2722 is the TSSC feature code. FC 2714 and FC 2715 proide connectiity to an existing TSSC. Copyright IBM Corp

48 Feature Code Feature name Description Corequisites or requirements 3958 DD4 TS7650G Serer Gateway serer x3850x5 (MT 7145) Seen 5.0 Gb PCIE I/O (one x16, fie x8, one x4) sockets. Four 8 core Xeon processors 2.26 GHz 64 GB memory Console Expansion This feature proides an attachment cable for connection of a unit using the TS3000 System Console (TSSC), and an Ethernet hub for expanding the number of FC 2721, FC 2722, FC 2730, or FC Up to 14 additional connections are proided by this feature for connection of FC 2715 or another FC Feature Type: Chargeable Required Feature: One of FC 2714, FC 2715 or FC 2722 is required. Maximum Number of Features: One of FC 2714, FC 2715 or FC A maximum of one other console expansion (FC 2714) may be connected to the Ethernet hub proided by this feature FC A maximum of two of feature FC 2714 may be included in a single TSSC facility (proiding a total maximum of 43 unit connections). Minimum Number of Features: One of feature FC 2714, FC 2715 or FC 2722 is required. Installation: Plant or Field 2715 Console Attachment This feature proides a cable to attach to the Ethernet hub proided by an existing TS3000 System Console (features FC 2720, FC 2721, FC 2722, FC 2730, or FC 2732), IBM TotalStorage Master Console for Serice (feature FC 2718), or Console Expansion (FC 2714). A maximum of 40 of feature FC 2715 may be included in a single console facility. Remoable: Yes Feature Type: Chargeable Required Feature: One of FC 2714, FC 2715 or FC 2722 is required. Maximum Number of Features: One of FC 2714, FC 2715 or FC 2722 is required. Minimum Number of Features:One of FC 2714, FC 2715 or FC 2722 is required. Installation: Plant or Field Remoable: Yes 26 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

49 Feature Code Feature name Description Corequisites or requirements 2722 TS3000 System Console 2733 TS3000 Internal Modem This feature proides the enhanced rack-mountable TS3000 System Console, an Ethernet switch, and a cable and connectors for connection of one machine to an IBM supplied modem to enable remote enhanced serice. This feature is an enhanced replacement of the IBM TS3000 System Console for Serice (FC 2721). Includes console upgrade preiously proided as FC 2719 (Memory upgrade to 2 GB total RAM and a second Ethernet card for the Serice Console to allow redundant connections into the serice network.) This feature proides an internal modem installed in the 1U serer. Feature Type: Chargeable. Required Feature: Yes. Maximum Number of Features: One of FC 2714, FC 2715 or FC 2722 is required. Minimum Number of Features: One of FC 2714, FC 2715 or FC 2722 is required. Installation: Plant or field Remoable: Yes Corequisite: FC 2733 FC 5510 and FC 5512 Feature Type: Chargeable. Required Feature: No. Maximum Number of Features: 1 Minimum Number of Features: 0 Installation: Plant or field. Remoable: Yes Corequisite: One of #2722 is required. Chapter 3. Components and feature codes 27

50 Feature Code Feature name Description Corequisites or requirements 3437 Cluster Connection Kit Gb quad port Ethernet adapter This feature proides a network power control, two Ethernet switches, associated cables and mounting hardware to create a clustered configuration between two TS7650 serers. The network power switch is used to automatically control the power to a failed node. Note: Only one Cluster Connection Kit is required for each pair of clustered nodes. Both clustered serers must be installed in the same rack. This feature delieries the required power cords and Ethernet cables to attach the two serers with the network power switch and Ethernet switches. The Cluster Connection Kit must be installed in the same rack as the serers. This feature proides a quad port 1-Gbps 10/100/1000Base-TX PCIe Ethernet adapter. This adapter has an RJ-45 connector for attaching Cat6 cables. This adapter conforms to the IEEE 802.3ab 1000Base-T standard. It supports distances of up to 100 meters using four pairs of Cat6 balanced copper cabling. Feature Type: Chargeable Required Feature: No Maximum Number of Features: 1 Minimum Number of Features: 0 Installation: Plant only Remoable: No Prerequisite: None Feature Type: Chargeable Required Feature: No Maximum Number of Features: 2 Minimum Number of Features: 0 Installation: Plant only Remoable: No Prerequisite: Two of FC 3456 or FC 3457 required with FC IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

51 Feature Code Feature name Description Corequisites or requirements Gb dual port Ethernet adapter Gb FC Dual Port HBA - Host This feature proides a dual port 10-Gbps Ethernet longwae adapter. This adapter has an SC Duplex connector for attaching 9 micron single mode fibre cable. It is a standard longwae (1,310 nm) adapter conforming to the IEEE 802.3ae standards. It supports distances up to 10 km. Note: When operating in a clustered OpenStorage configuration, both ProtecTIER nodes must run either 10 Gb OpenStorage or 1 Gb OpenStorage. Running an intermix of 1 Gb (copper or optical) and 10Gb OpenStorage in a cluster is not supported. This 8 Gb FC dual-port PCIe HBA proides the connections to the host serers or switches. Feature Type: Chargeable Required Feature: No Maximum Number of Features: 2 Minimum Number of Features: 0 Installation: Plant only Remoable: No Prerequisite: Two of FC 3456 or FC 3457 required with FC Feature Type: Chargeable Required Feature: No Maximum Number of Features: 2 Minimum Number of Features: 0 Installation: Plant only Remoable: No 5510 Plant install KVM Switch This feature proides the KVM switch, cables, and mounting hardware to be plant installed in the frame or deliered for installation in a rack. Prerequisite: FC Feature Type: Chargeable Required Feature: No Maximum Number of Features: 1 Minimum Number of Features: 0 Installation: Plant or field Remoable: Yes Corequisite: FC2722, FC 5512 Chapter 3. Components and feature codes 29

52 Feature Code Feature name Description Corequisites or requirements 5512 KVM Display, Keyboard, Mouse This feature proides the KVM display, keyboard, mouse and mounting hardware to be plant installed in the frame or deliered for installation in a rack. Feature Type: Chargeable Required Feature: No Maximum Number of Features: 1 Minimum Number of Features: 0 Installation: Plant or field Remoable: Yes Prerequisite: FC KVM adjacent frame connection nd serer in adjacent frame This feature proides a cable to connect one or two appliances or gateways to the KVM switch in an adjacent unit with feature FC 5510 and FC 5512 installed. This will allow the keyboard, mouse, and ideo display installed with FC 5512 to be used by this ProtecTIER system. A maximum of four FC 5513S may be attached to a single FC This feature designates the second appliance or gateway which will use the FC 5513 cable to share the keyboard, mouse and ideo display from an adjacent frame with FC 5512 installed. Corequisite: FC 5510 Feature Type: Chargeable Required Feature: No Maximum Number of Features: 1 Minimum Number of Features: 0 Installation: Plant or field Remoable: Yes Prerequisite: FC 2714 or FC 2715 FC 5510 and FC 5512 must exist in an adjacent frame or rack. Feature Type: Chargeable Required Feature: No Maximum Number of Features: 1 Minimum Number of Features: 0 Installation: Plant or field Remoable: Yes Prerequisite: FC 2714 or FC 2715 FC 5513 on another ProtecTIER serer in the same rack or frame. 30 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

53 Feature Code Feature name Description Corequisites or requirements Meter LC/LC Fibre Channel Cable 9022 ProtecTIER Virtual Tape Library (VTL) This feature proides a 25 meter (82 ft.) 50.0/125 micrometer short waelength multimode fiber-optic cable with LC duplex connectors on both ends. Note: This cable is for attaching a TS7600 serer (that has an LC duplex connector) to switches, disk subsystem or hosts with LC duplex fibre channel connectors. (Host cables only.) This feature designates that this ProctecTIER system will be configured for use as a irtual tape library management system. Feature Type: Chargeable Required Feature: No Maximum Number of Features: 4 (Maximum of 8 with cluster support.) Minimum Number of Features: 0 Installation: Plant or field Remoable: No Prerequisite: One of FC 9700 or at least four of FC 6025s are required. Feature Type: Chargeable Required Feature: No Maximum Number of Features: 1 Minimum Number of Features: 0 Installation: Plant only Remoable: No 9023 Open Storage This feature designates that this ProctecTIER system will be configured for use with Open Storage. Prerequisite: Two of FC 3458 required. Mutually exclusie with FC 3456, FC 3457 and FC Feature Type: Chargeable Required Feature: No Maximum Number of Features: 1 Minimum Number of Features: 0 Installation: Plant only Remoable: No Prerequisite: Two of FC 3456 or FC 3457 required. Mutually exclusie with FC 3458 and FC Chapter 3. Components and feature codes 31

54 Feature Code Feature name Description Corequisites or requirements 9306 ProtecTIER EE preload This feature instructs IBM manufacturing to load ProtecTIER Enterprise Edition software (PID 5639 XXB) on the TS7650G. A separate order for the software is required. Feature Type: No Charge Required Feature: Yes Maximum Number of Features: 1 Minimum Number of Features: 1 Installation: Plant only 9340 Rack Mount This specify code indicates this TS7650G Serer will be mounted in a customer proided industry standard, 19 rack. Remoable: Yes Feature Type: No Charge Required Feature: Yes Maximum Number of Features: 1 Minimum Number of Features: 1 Installation: Plant only Remoable: No 9700 No Factory Cables This feature should be specified if you do not want the factory to ship any Fibre Channel cable features with the new machine. These Fibre Channel cables are for attachment to switches or host serers. Prerequisite: None Feature Type: No Charge Required Feature: No Maximum Number of Features: 1 Minimum Number of Features: 0 Installation: Plant only Remoable: Yes Prerequisite: One of FC 9700 or at least four of FC 6025s are required XXB ProtecTIER Enterprise Edition V3.1 Base Software This software proides the base functionality for ProtecTIER EE. The software supports any capacity of FC or SATA disk dries in its disk storage pool. It is ordered on a per serer' basis. Capacity support This is the base functionality for ProtecTIER EE. It supports any capacity of either FC and SATA disk dries in its disk storage pool. It is ordered on a per terabyte' basis for usable capacity of the whole configuration, using the capacity tiers shown below: 32 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

55 Per Terabytes (1-12) Per Terabytes (13-32) Per Terabytes (33-64) Per Terabytes (65-100) Per Terabytes ( ) Per Terabytes (251+) Per 250 Terabytes (251+) Clustering This feature allows the serer running this software to share a common disk storage pool with a second serer running ProtecTIER EE with the clustering feature. This feature is ordered on a per terabyte' basis using the same capacity tiers as Capacity support aboe. Replication This feature allows the serer running this software to replicate data to a second system running ProtecTIER EE with the replication feature. This feature is ordered on a per terabyte' basis using the same capacity tiers as Capacity support aboe. DATs and Chargeable Components for the base software PID# 5639-XXB ProtecTIER Enterprise Edition V3.1 CC#1 ProtecTIER (IPLA178V1, IASP387V1, IASP390V1, IASP388V1, IASP389V1, IASP391V1) Per Serer with 1yr SW Maintenance Media Delierable CC#2 Capacity Support (IPLA480V1, IASP480V1, IASP481V1, IASP482V1, IASP483V1, IASP484V1) Per Terabytes (1-12) with 1yr SW Maintenance Per Terabytes (13-32) with 1yr SW Maintenance Per Terabytes (33-64) with 1yr SW Maintenance Per Terabytes (65-100) with 1yr SW Maintenance Per Terabytes ( ) with 1yr SW Maintenance Per Terabytes (251+) with 1yr SW Maintenance Per 250 Terabytes (251+) with 1yr SW Maintenance Media delierable (code shipped ia CC#1) CC#3 Clustering Support (IPLA480V1, IASP480V1, IASP481V1, IASP482V1, IASP483V1, IASP484V1 Per Terabytes (1-12) with 1yr SW Maintenance Per Terabytes (13-32) with 1yr SW Maintenance Per Terabytes (33-64) with 1yr SW Maintenance Per Terabytes (65-100) with 1yr SW Maintenance Per Terabytes ( ) with 1yr SW Maintenance Per Terabytes (251+) with 1yr SW Maintenance Per 250 Terabytes (251+) with 1yr SW Maintenance Media delierable (code shipped ia CC#1) CC#4 Replication Support (IPLA480V2) Per Terabytes (1-12) with 1yr SW Maintenance Chapter 3. Components and feature codes 33

56 Per Terabytes (13-32) with 1yr SW Maintenance Per Terabytes (33-64) with 1yr SW Maintenance Per Terabytes (65-100) with 1yr SW Maintenance Per Terabytes ( ) with 1yr SW Maintenance Per Terabytes (251+) with 1yr SW Maintenance Per 250 Terabytes (251+) with 1yr SW Maintenance Media delierable (code shipped ia CC#1) ProtecTIER EE SWMA PIDs for Enterprise Edition are: 5639-XXC 1 Yr Registration & Renewal 5639-XXD 1 Yr After License 5639-XXE 3 Yr Registration 5639-XXF 3 Yr Renewal 5639-XXG 3 Yr After License 5639-XXJ 2 Yr Registration 5639-XXK 4 Yr Registration 5639-XXL 5 Yr Registration CC#4 Replication Support (IASP480V2, IASP481V2, IASP482V2, IASP483V2, IASP484V2, IASP737V1, IASP738V1, IASP739V1) Per Terabytes (1-12) with 1yr SW Maintenance Per Terabytes (13-32) with 1yr SW Maintenance Per Terabytes (33-64) with 1yr SW Maintenance Per Terabytes (65-100) with 1yr SW Maintenance Per Terabytes ( ) with 1yr SW Maintenance Per Terabytes (251+) with 1yr SW Maintenance Per 250 Terabytes (251+) with 1yr SW Maintenance Media delierable (code shipped ia CC#1) 34 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

57 Chapter 4. Sizing, configuration, and usage considerations This section discusses sizing, configuration, and usage considerations. The performance of customer-supplied components, such as backup serers and disk storage arrays, can greatly effect TS7650G performance. Understanding other factors, such as the amount of time allotted for backups, the type of data being stored, and the rate at which the data changes, will help you to make decisions about the design for your TS7650G solution. Your IBM representatie will discuss these factors with you to help you design a solution that meets your needs. Backup serers Understanding the recommended method for connecting the backup serers to the gateway serer and configuring the backup serer applications for optimal performance with the TS7650G. SAN connectiity Understanding how the TS7650G can be installed in your existing SAN enironment. Storage arrays Understanding the performance benefits of Fibre channel dries ersus SATA dries, comparisons of different RAID leels, and recommendations for configuring LUNs. Data types Understanding how the compressibility of different data types affects the amount of storage required for your TS7650G solution. Copyright IBM Corp

58 36 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

59 Chapter 5. Customer installation responsibilities This section discusses customer installation responsibilities. Customers are responsible for preparing the installation site, as described in Chapter 2, Physical planning specifications for the TS7650G, on page 17, prior to the installation of the TS7650G. All physical planning for the TS7650G is a customer's responsibility. In summary, customers are responsible for proiding network connections (cables and switches), SNMP catcher, serers, host clients, and serices for call home and IMM alerts. Customers must proide IBM with all necessary IP addresses for the installation of the TS7650G, which includes two IP addresses per 3958 DD4 and one IP address for the TSSC. The customer must supply an analog telephone line for the TSSC. The customer must supply a USB keyboard and SVGA monitor for use during the installation process. Customer-supplied frames, disk controllers, and disk expansion modules must be fully installed and operational before the installation of the TS7650G can begin. Customers are required to hae an approed disk subsystem aailable and configured according to the guidelines in the Cache configuration best practices on page 39 prior to the installation of the TS7650G. The customer must also supply the appropriate Fibre Channel cables, which an IBM serice representatie will use to attach the TS7650G to the customer-supplied disk subsystem. It is also necessary for the customer to order the appropriate feature code for the selected disk subsystem. Refer to TS7650G TS7650G feature codes on page 25 for more information. Important: The systems at both the source and destination sites must be completely installed and configured for replication before the installation of the replication functionality of thets7650g can begin. Consult with Solutions Assurance and your IBM Representatie for assistance and information. Use the pt_net_perf_util utility in Chapter 13, ProtecTIER Replication Network Performance Validation Utility for VTL Systems, on page 79 to test maximal replication performance between two future PT repositories by emulating the network usage patterns of PT's Natie Replication component. This utility will not predict replication performance, but it may discoer performance bottlenecks. Note: All aspects of the backend disk repository, including configuration, monitoring, code updates, and repair actions are the responsibility of the customer in conjunction with their disk supplier. Customers are responsible for obtaining a ProtecTIER Manager workstation and for obtaining the appropriate adapters and cables. Fibre channel cables are required to attach the TS7650G to arious serer adapters. Cat-5e Ethernet cables are required to attach the TS7650G to iscsi hosts. Refer to TS7650G feature codes on page 25 for a list of cables for the attachment of the TS7650G. In addition, customers are also responsible for proiding client machines and required fibre channel and Ethernet switches as described in the following sections. Copyright IBM Corp

60 System responsibilities This section discusses the hardware and system responsibilities of the customer. In addition to meeting the requirements set out in Chapter 2, Physical planning specifications for the TS7650G, on page 17, the customer must proide the following hardware and systems. ProtecTIER Manager workstation requirements This section discusses workstation requirements. The customer uses the ProtecTIER Manager software to configure, manage, and monitor the operation of the TS7650G. The customer is responsible for obtaining the workstation where the ProtecTIER Manager software is installed. The customer can install the software from the supplied ProtecTIER Manager application CD. Complete information about installing and using the ProtecTIER Manager workstation is proided in the IBM System Storage TS7650G ProtecTIER Deduplication Gateway Installation Roadmap Guide, IBM form number GA and the IBM System Storage ProtecTIER User's Guide for Enterprise Edition and Appliance Edition, IBM form number GA The following are hardware and operating enironment requirements for the ProtecTIER Manager workstation. Hardware requirements: x86 (Pentium or higher) microprocessor 256 MB memory 1.2 GB of disk space Access to the ProtecTIER serice node's IP address (Port 3501 is open on the firewall.) Keyboard, mouse, and CD-ROM drie Resolution of 1024x768 pixels or higher. (This is the minimum resolution supported, howeer, we recommend 1280x1024.) 24 bit color or higher Operating enironments supported: Windows 32 bit (2003/XP) Linux Red Hat 32/64 bit (Red Hat Enterprise 4 or 5) Hardware, cabling, and infrastructure responsibilities In general, the customer is responsible for proiding the appropriate infrastructure resources, such as frames and power distribution units, as well as the cables and switches required to support TS7650G connections to the ProtecTIER Manager console, disk controller(s), and disk expansion modules. Note: The customer must use an additional connectiity deice between the optical Fibre directly connected to RMSS optical adapters (for example, Fibre, ESCON, or FICON) and an external public network. It can be a patch panel, router, switch, or other suitable deice. Optical Fibre connectiity that does not go oer a public network does not require an additional connectiity deice. 38 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

61 The customer must proide the following hardware and cabling resources prior to the installation of the TS7650G: One serer frame with two 220V power distribution units. One or two disk storage frames, as required, based on the amount of rack space needed for the disk storage components. Each frame must hae two 220V power distribution units. Cat-5e Ethernet cables for connecting to the TS7650G and TSSC. Note: Cat-5 cables do not proide sufficient data-transfer rates for the TS7650G. You must use Cat-5e or aboe.. Fibre channel cables for connecting the disk controller(s) to the disk expansion modules. ProtecTIER Manager workstation, as described in ProtecTIER Manager workstation requirements on page 38. SVGA monitor and USB keyboard for use during TS7650G installation. Note: All customer-supplied hardware components, including frames, switches, client host platforms, and media must be installed and erified as operational by the customer prior to the installation of the TS7650G. Cache configuration best practices The disk storage array that connects to the TS7650G is a critical element of the TS7650G enironment. This section lists the key factors and common configuration requirements of the back end disk storage array that must be set appropriately in order to establish a proper enironment for ProtecTIER. Use RAID for data protection and performance. It is recommended that you use RAID 5 with at least fie disk members (4+1) per group for Fibre-Channel user data LUNs (5+1 or 7+1 for SATA disks) and RAID 10 groups for meta data LUNs (with layout per planning requirements). Een if you use SATA dries for user data LUNs, we recommend that you use Fibre-channel disks for meta data LUNs. For SATA configurations, use RAID 6 instead of RAID 5 for user data LUNs, and enable dual-parity to sustain dual disk failure. Create at least 24 user data RAID groups for best performance optimization. The number of meta data RAID groups will be dictated by the planning session/wizard, and can range from 2 to 10 or more RAID groups. The number of RAID groups needed is based on repository size, factoring ratio, and performance needs. Only create one LUN per RAID group, that is, one LUN that spans the entire RAID group. The only exception is the single 1 GB meta data LUN. The 1 GB meta data LUN can be created on any of the meta data RAID groups, but ideally should be placed on the first. Tune the ProtecTIER serer host type in the host connectiity settings for a Linux deice-mapper-multipath client. It may be generally denoted as a Linux host. A repository requires a minimum of four LUNs, one for the cluster database, one for user data and two for meta data. At least 27 LUNs (one cluster, two meta data and 24 user data) gie best performance. The size of the required meta data LUNs/filesystems is a function of the nominal capacity of the repository (physical space and expected factoring ratio) and should be determined prior to the system installation by trained ProtecTIER specialist (FTSS) and/or your IBM System Serice Representatie (SSR). Chapter 5. Customer installation responsibilities 39

62 The size of user data RAID groups and LUNs should be consistent. For example, don't mix 7+1 SATA user data LUNs with 3+1 SATA LUNs. Smaller disk groups will hold back the performance of the larger groups and will degrade the oerall system throughput. Follow this policy for meta data. When expanding the repository, it is important to use the same tier of RAID groups (spindle type & quantity) for meta data or user data as the existing meta and user data groups. For example, if the original two meta data LUNs were built on RAID 4+4 Groups, new meta data RAID groups added must be at least 4+4 to maintain the same leel of performance. Using storage from 2+2 or 4+1 RAID Groups for the expansion could result in performance degradation due to IOPS bottlenecks. In storage arrays with actie-actie controller support (that is, a LUN can be accessed from both controllers simultaneously) map LUNs to both controllers for best load-balancing and redundancy. In arrays with only actie-passie support (that is, a LUN can only be accessed by one controller at once) LUN mapping should be interleaed between controllers (that is, LUN 0 on controller A, LUN 1 on B, 2 on A, and so on) in order to establish load-balancing to a similarly effectie degree. Each ProtecTIER node should hae at least one Fibre Channel link/path to each disk array controller. With low SAN switching speeds (for example, 1 GB or 2 GB), two paths per controllers are recommended. When using only two backend Fibre Channel links, use separate HBA ports on the TS7650G to protect against HBA hardware failure. If possible, use patch cords and loop topology between the TS7650G and the disk storage array. This saes expensie fabric ports and reduces the risk of SAN failure. If using SAN P2P topology to connect the TS7650G to the disk array, create a dedicated zone for ProtecTIER backend ports. Do not mix the backend ports (Qlogic) with the frontend ProtecTIER ports (Emulex) or any other SAN deices in the same zone. 40 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

63 FRONT END (FE) PORTS BACK END (BE) PORTS ZONE A ZONE B ZONE C PROTECTIER SERVER ZONE D BACKUP SERVERS PROTECTIER APPLICATION FABRIC STORAGE ARRAYS ts Figure 8. Dedicated zone topology If possible, dedicate the disk storage array to the TS7650G. If not possible, use zoning and LUN masking to isolate the TS7650G from other applications. The TS7650G should neer share RAID groups or LUNs with other applications. ProtecTIER is a random read oriented application. 80 to 90 percent of I/O in a typical TS7650G enironment is random reads at 60 Kb block size. Implement the performance optimizations and tuning recommended by the disk endor for this I/O profile. The disk storage array firmware ersion leel should be equal to or greater than the firmware ersion leel listed in the ProtecTIER Interoperability Matrix. Make sure that the ISL links between SAN switches connected to TS7650G ports and disk storage arrays are not oersubscribed. See Chapter 15, Example cache configuration file, on page 87 for a sample configuration file for a TS7650G with an IBM System Storage DS4000 disk storage array. Security, auditability, and control This product uses the security and auditability features of host hardware, host software, and/or application software to which it is attached. The customer is responsible for ealuation, selection, and implementation of security features, administratie procedures, and appropriate controls in application systems and communications facilities. For troubleshooting purposes, an IBM serice representatie may need to use the TSSC to open an SSH session on the gateway serer. To do so, the IBM serice representatie will need the ptadmin account password. If the customer has changed the default password, the customer must make the new password aailable to the IBM serice representatie upon request. Chapter 5. Customer installation responsibilities 41

64 42 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

65 Chapter 6. IBM serice installation responsibilities This section lists IBM serice installation responsibilities. The IBM installation team is responsible for performing the followings tasks during the installation of the TS7650G: Connect the network cables (proided by the customer) to the network switches (proided by the customer) in the customer configuration. Set IP addresses according to customer-proided network assignments. Configure the operating system on the gateway serer(s). Configure the RAS package. Configure the ProtecTIER software. Verify that the TS7650G hardware is functioning properly. Install and set up the TSSC, which includes connecting the customer-supplied analog phone line and network cable. Note: The supplied analog phone line must be a minimum of a 26 AWG type wire and comply with one of the following standards: CSA NO. 233 UL 1863 Verify communications between TS7650G, TSSC and ProtecTIER Manager console. Install and configure replication, if applicable. Install any clustering hardware and software, if applicable. Verify fencing functionality, if applicable. (This is a function that is resered for clustered systems only.) Copyright IBM Corp

66 44 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

67 Chapter 7. Planning data migration Use data migration considerations to formulate your data migration plan. There are three leels of considerations to keep in mind when selecting the best method for your enironment. At the first leel, you consider broad questions about your enironment to create a generic profile of your needs. At the second leel you compare which migration methods fit into your generic profile. The third leel is to reiew a set of hints and other guidelines that apply to specific enironments or that may help you take adantage of a migration to optimize your enironment. The following are some key questions to use to define your generic migration enironment: Why is the data migrating? How much data is migrating? How quickly must the migration be performed? What duration of serice outage can be tolerated? Is the data migration to/from the same type storage? What resources are aailable for the migration? After determining general answers to the considerations listed aboe, a better understanding of some of the migration options along with their adantages and disadantages will help frame your generic profile into a subset of acceptable migration options. Copyright IBM Corp

68 46 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

69 Chapter 8. OpenStorage (OST) network configuration for the ProtecTIER Backup serer Abstract This section proides information on OpenStorage (OST) network configuration for the ProtecTIER Backup serer including the scopes and objecties, definitions and acronyms, information on Teaming/Bonding and procedures for setting up the network with ProtecTIER. The goal of this information is to describe the networking technologies that are used in order to set up the connectiity of the ProtecTIER front end interfaces to the network. This chapter describes OpenStorage (OST) network configuration best practices to support different IP configurations. It will proide the scope and objecties, along with the basic acronyms that will be used in the subsequent sections. The goal is to describe the networking technologies that are used in order to set up the connectiity of the ProtecTIER front end interfaces to the network. This chapter describes the technologies in use such as teaming or bonding on the network serers, 802.3ad Link Aggregation and similar technologies on the LAN switches, along with network topologies for stand-alone and redundant architectures. This chapter describes the technology, topologies and setups for achieing the best performance and suriability oer the network. Scope and objecties The purpose of this topic is to establish a connectiity method for connecting the ProtecTIER serer front end interfaces to the network, and achieing the optimal performance using it. In an OpenStorage enironment, the ProtecTIER serer connects to the network with multiple Ethernet adapters, and supports a total throughput of hundreds of mega bytes per second oer the network per node. The next sections will focus on the following issues: Network connectiity and load balancing method of the ProtecTIER serer. Network connectiity and load balancing method of the hosts connected to the network. Network configuration and load balancing method of the LAN switches to which the ProtecTIER serer and the hosts are connected. Definitions and Acronyms This section describes definitions and acronyms that are releant to OST network configuration. Link Aggregation A method for grouping seeral interfaces into a single irtual interface, for the purpose of load sharing between the interfaces. IEEE 802.3ad IEEE standard for Link Aggregation for LAN connectiity. Copyright IBM Corp

70 Gigabit Ethernet Ethernet that runs in a Gigabit per second bandwidth. VLAN Virtual LAN is a software-defined LAN that groups network elements in the same broadcast domain. Teaming A method for grouping seeral physical adapters into a single irtual adapter for the purpose of load sharing and throughput enhancement. Teaming is a common term used in Microsoft Operating Systems. Bonding This term means the same as teaming and is usually used in Linux/Unix Operating System. Host Bonding/Teaming A network element connected to the network. In the OpenStorage enironment, the NetBackup media serers are referred to as hosts. The connectiity is based on a mechanism called Teaming (usually in Microsoft platforms) or Bonding (usually on Linux/Unix platforms) in serers, and Link aggregation (802.3ad) or Cisco Etherchannel in LAN switches. The purpose of these mechanisms is to achiee higher bandwidth on the connection, as close as possible to the multiplication of the port's bandwidth, along with redundancy between the ports. Principles of teaming/bonding mechanisms The teaming is a mechanism that groups interfaces in layer 2 (on the Ethernet layer), while the whole team gets a single IP address. This mechanism can work in seeral common ways, among which are the following: Redundant mode - usually two interfaces: one for carrying the traffic, and one for backup. This is usually called Actie-Backup mode. Transmit and/or Receie load balancing - receie and/or transmit load is distributed independently of the LAN switches to which they are connected ad Mode - the serers and the switches they are connected to must support the standard and load distribution is according to this standard. The first two methods are topologies that are "switch-less", which means that the switch does not hae to support any specific standard. In the last method, the switches in the topology must support the 802.3ad standard, or in some cases the Cisco Etherchannel implementation. Redundant mode In redundant mode, one of the adapters is actie, and one is passie. When the actie adapter fails, the passie takes its place. Note: This mode does not perform load balancing. Transmit and receie load balancing In transmit mode, the serer adapters usually works in the following way: 48 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

71 In transmit load balancing, the traffic is usually sent in a round-robin manner, while the team (or bond) sends out packets with a single MAC address. The load is balanced on the way out from the serer, while all traffic comes in on a single interface. In receie load balancing, the question is how to tell the receier of the packets, to send the packets back to the same interface that it came from. The problem occurs because there are multiple MAC addresses going out with a single IP address. Therefore, when the receier starts to send data, it will send an ARP request, and then will send all packets back to the interface that his address came back in the ARP response. The method that is usually used to sole this problem is to send the receier multiple ARP responses, with all the MAC addresses of the team, so the receier will "beliee" that the IP address is coming from different MACs, and therefore we will get also receie load balancing. Actie Load Balancing (ALB) is a receie load balancing technique ad Topologies This standard does not mandate any particular distribution algorithm(s). Howeer, any distribution algorithm shall ensure that the algorithm will not cause the following: Misorder of frames that are part of any gien conersation Duplication of frames The standard suggests, but does not mandate, that the algorithm may assign one or more conersations to the same port; howeer, it must not allocate some of the frames of a gien conersation to one port and the remainder to different ports. The information used to assign conersations to ports could include the following: Source MAC address Destination MAC address Source IP address Destination IP address The reception port The type of destination address (indiidual or group MAC address) Ethernet Length/Type alue (i.e., protocol identification) Higher layer protocol information (e.g., addressing and protocol identification information from the LLC sub layer or aboe) Combinations of the aboe The policy according to which the bond decides how to distribute the frames across the ports is referred to as "hash algorithm" or "hash policy". The hash policy decides according to what parameters, or combination of parameters, the frames will be distributed. For example, when we hae a serer exchanging information with seeral hosts on the same subnet, configuring a source/destination MAC hash will usually gie a reasonable load distribution. On the other hand, if we want to use load balancing oer a router, then a layer-3 hash will not help, since the serer sees only one IP Address (of the router), and therefore all traffic will be sent oer the same interface. In this case, layer-4 hash must be used. Bonding on linux machines This section describes bonding types on linux machines. In linux machines, the following bonding types exist: Chapter 8. OpenStorage (OST) network configuration 49

72 Mode 0 - sets a round-robin policy for fault tolerance and load balancing. Mode 1 - sets an actie-backup policy for fault tolerance. Mode 2 - sets an XOR (exclusie-or) policy for fault tolerance and load balancing. Mode 3 - sets a broadcast policy for fault tolerance. All transmissions are sent on all slae interfaces. Mode 4 - sets an IEEE 802.3ad dynamic link aggregation policy. Mode 5 - sets a Transmit Load Balancing (TLB) policy for fault tolerance and load balancing. Mode 6 - sets an Actie Load Balancing (ALB) policy for fault tolerance and load balancing. Includes transmit and receie load balancing for IPV4 traffic. Receie load balancing is achieed through ARP negotiation. Modes 2 and 4 use a default transmit hash policy of layer 2 (source MAC destination MAC)%N (number of slaes). The hash policy can be modified to layer3+4 where both source and destination IP and port are taken into consideration. Bonding on Unix machines This section describes bonding types on Unix machines. These are the modes supported in IBM-AIX: Standard or 802.3ad Default hash mode - The traditional AIX behaior. The adapter selection algorithm uses the last byte of the destination IP address (for TCP/IP traffic) or MAC address (for ARP and other non-ip traffic). Standard or 8023ad src_dst_port hash mode - The outgoing adapter path is selected by an algorithm using the combined source and destination TCP or UDP port alues. Standard or 8023ad src_port - The adapter selection algorithm uses the source TCP or UDP port alue Standard or 8023ad dst_port The outgoing adapter path is selected by the algorithm using the destination system port alue. Round-robin Outgoing traffic is spread eenly across all of the adapter ports in the EtherChannel. Teaming on Microsoft-based machines On Microsoft-based machines, the teaming methods are entirely defined by the NIC endor. This section describes the teaming modes for Broadcom and Intel NICs. The teaming modes described are only those used for load sharing. Broadcom NICs Broadcom supports the following balancing modes: 50 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

73 SLB Smart Load Balancing In this method both transmit and receie load balancing are enabled, based on source and destination L3/L4 IP addresses and TCP/UDP port numbers. Generic Trunking In this switch-assisted teaming mode, the LAN switch that the serer is attached to, must be also configures for one of the aggregation methods. As is the case for Smart Load Balancing, the IP/TCP/UDP source and destination addresses to load balance the transmit traffic from the serer Link Aggregation (IEEE 802.3ad LACP) Link Aggregation is similar to Generic Trunking except that it uses the Link Aggregation Control Protocol to negotiate the ports that will make up the team. Intel NICs Intel supports the following balancing modes: Adaptie Load Balancing (ALB) This method allows transmission oer 2-8 ports to multiple destination addresses, along with Fault Tolerance. In this method, transmit is done through 2-8 adapters in load balancing, while the team receies packets only through the main adapter. This method works on L3/4 basis. Receie Load Balancing (RLB) This method, than can be configures only with ALB, adds the receie load balancing feature to it, and is also based on L3/4. This is a switch-less method. Virtual Machine Load Balancing (VMLB) Proides transmit and receie traffic load balancing across Virtual Machines bound to the team interface, as well as fault tolerance in the eent of switch port, cable, or adapter failure. This teaming type is switch-less method IEEE 802.3ad In this method, the standard supports static and dynamic modes. Intel supports both modes, and must be configured with a LAN switch the supports the 802.3ad standard, or Cisco Etherchannel technology. LAG and similar technologies on the LAN Switches For LAN switches, configurations are proided for Cisco switches. Some of the features are present in Cisco IOS Release 12.2(33)SB and higher. The 802.3ad is a market-wide standard, supported by all common endors. In Cisco switches, both L2 and L3, two methods are aailable: 1. Etherchannel GEC/FEC (Giga/Fast Ethernet ports), and PaGP ad Link Aggregations and LACP control Protocol In switches from other endor's (Aaya, Juniper, 3Com, HP and others), only 802.3ad is used. Etherchannel is a Cisco proprietary technology. In Cisco IOS ersions up to Release 15.0(1)S, mechanisms for load balancing Ethernet serice instances oer member links in a port channel do not account for the serice instances traffic loads, which can lead to unequal distribution of traffic oer member links. Chapter 8. OpenStorage (OST) network configuration 51

74 In IOS Release 15.0(1)S, a new feature was presented, that is 802.3ad Link Aggregation with Weighted Load Balancing feature (802.3ad LAG with WLB) that allows you to assign weights to serice instances to efficiently distribute traffic flow across actie member links in a port channel. The LAG with WLB feature supports both LACP (actie or passie mode) and manual (mode on) EtherChannel bundling. A weighted load balancing configuration does not affect the selection of actie member links in the EtherChannel. As member links become actie or inactie, a load-balancing algorithm adjusts the distribution of Ethernet serice instances to use the currently actie member links. Setting up the network with ProtecTIER This section describes the set up procedures using the ProtecTIER serer. ProtecTIER serer Configuration The backup application creates a backup or restore stream for each backup set copied to or from the IBM ProtecTIER serer. In an OpenStorage enironment, the ProtecTIER plug-in on the media serer opens by default up to 8 TCP connections for each stream. The best practice for the ProtecTIER serer is to connect it in one of the following configurations: Indiidual IPs (layer 3) configuration In this configuration each interface gets its own IP address. This configuration maximizes the performance but does not offer high aailability of the interfaces. It also requires multiple IPs and subnets. No teaming or bonding is used in this configuration. This configuration is recommended in case no switch support for the other options is aailable. This is currently the only configuration supported for serers using the 10Gb NICs. Single team/bond (Layer 2) configuration In this configuration, all front end interfaces on a ProtecTIER node are grouped into one team. This configuration maximizes the high aailability and ease of use, as a single IP and subnet is used for the entire team. This configuration is recommended if using 2 or 4 interfaces on the ProtecTIER side. If a different interfaces number is used (e.g. all 6 interfaces in the case of 1Gb NICs), this method might not maximize the performance, and option (3) is recommended. Dual/Three teams (Layer 2+3) configuration In this configuration, 2 or 3 teams are configured. This configuration balances the high aailability, ease of use and performance. This configuration is recommended in the case that the number of interfaces used on the ProtecTIER side is different than 2 or 4. In testing with Cisco 6500 switch configured with Etherchannel, 3 teams containing 2 interfaces each, maximized the performance similarly to option 1. If configuring teams, for each one of the teams, an IP address should be configured on the team, and the team should be configured with load balancing method as described in Load Distribution Methodology on page IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

75 Load Distribution Methodology This section describes the Load Distribution Methodology. The bonding methods which are supported by the ProtecTIER serer are: Mode 0 (Round-Robin): outgoing traffic is spread eenly across all of the adapter ports in the team/bond. Mode 4 (Dynamic IEEE 802.3ad, switch-assist): L2 : outgoing traffic is spread using a default transmit hash policy of layer 2 (source MAC destination MAC)%N (number of slaes). L2/L3: outgoing traffic is spread using a transmit hash policy of MAC addresses and IP addresses of the source and the destination. L3/L4: outgoing traffic is spread using a transmit hash policy of IP addresses and ports of the source and the destination. LAN switch This section describes the LAN switch. In LAN switches, there are arious technologies that are supported by arious endors, for example Cisco Fast EtherChannel (FEC) and Gigabit EtherChannel (GEC), Nortel's Multilink Trunking (MLT), Extreme Network Load Sharing and others. Most of the endor's supports also 802.3ad. Teams Configuration In the LAN switch, configure as follows: 1. When configured with switch-less topology, no configuration is required. 2. When configured with Etherchannel or 802.3ad, use Layer-3/4 hash mechanism. See Configuration instructions and examples for instructions how to configure Cisco Etherchannel for this mode. Configuration instructions and examples This section describes OpenStorage (OST) network configuration instructions and examples. Configuring IP addresses Whether or not bonds/teams are being configured, you will hae to configure unique IP addresses on the hosts and on the ProtecTIER serers. If you are configuring bonds/teams, each bond/team will hae to be assigned with a single IP address. Otherwise, each physical interface will hae to be assigned with a unique IP address. On each system, host or ProtecTIER, each IP address which is configured has to be on a different subnet. Additional hosts and ProtecTIER nodes can share the same subnet. For example, on the first ProtecTIER node, you can configure the following IP addresses: / / / / / /24 In this case, the second ProtecTIER node can use the following addresses: Chapter 8. OpenStorage (OST) network configuration 53

76 / / / / / /24 In this example, the first network is , and 255 subnet addresses can be defined. Therefore, the first node is using an address in this subnet ( ) and the second node can use a different address on the same subnet ( ). Configuring the network interfaces on the ProtecTIER serer By default, upon installation of the ProtecTIER software, each front end physical interface on a ProtecTIER node is configured with a corresponding irtual interface with a unique default IP address. During the system configuration, it is necessary to proide a new IP address to eery irtual interface, each of the IPs on a different subnet. This command line interface proides the option to: Assign new IP addresses for each irtual interface. Reassign physical interfaces into irtual interface (this is the way to group the interfaces into a bond). Define the load balancing method to be used within a bond. Configuring the network interfaces on the host (media serer) On the hosts, similarly to the ProtecTIER nodes, each physical interface should be assigned with its own IP address or will be grouped within a team/bond that will hae a single IP address. Each interface or bond/team on the host side will need to hae its IP address on a separate subnet. As in the ProtecTIER case, different hosts may share the same subnet. Routing the IP traffic Static routes are a simple and effectie way of instructing the host IP stack how to route IP traffic destined for specific subnets. This is necessary wheneer traffic to any specific subnet is required to be sent through a different gateway and possibly a different network-interface than the default-gateway definition would otherwise dictate. If required, configure your static routes such that each port on the host can reach one irtual port on each ProtecTIER node to which it is connected. If possible, configure all IP addresses on the media serers on the same subnets that you hae defined on the ProtecTIER nodes. Configuring Etherchannel load balancing on Cisco switches This example shows how to configure EtherChannel to use source and destination IP addresses and port numbers as parameters for load balancing (L3/L4): 1. Configure the load balancing Router# configure terminal Router(config)# port-channel load-balance src-dst-mixed-ip-port Router(config)# exit Router(config)# 2. Verify the configuration 54 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

77 Router# show etherchannel load-balance EtherChannel Load-Balancing Configuration: src-dst-mixed-ip-port enhanced mpls label-ip Configuring bonds, load balancing and IP addresses on AIX hosts 1. Create the bond: a. Go todeices > Communication > EtherChannel/IEEE 802.3ad Link Aggregation > Add An EtherChannel / Link Aggregation. b. Choose the network interfaces (ports) you would like to bond together and click OK. c. Change the parameter "Hash Mode" from default to src_dst_port Note: By doing this, a new en#"/"et# deice has been created on the machine and assigned to it the ports selected from the list. 2. Assign IP address to the newly created bond: a. Go to Communications Applications and Serices > TCP/IP > Minimum Configuration & Startup. b. Choose the newly created en# deice (not the et#, that is the "Standard Ethernet Network Interface") and update it's IP and Network mask as needed. Configuring teams, load balancing and IP addresses on Windows hosts In order to configure teams in Windows platforms, use the NIC endor network utility. This example is using BACS which is Broadcom's network utility. 1. Create the team: a. In the Explorer View of BACS, under Team Management, right-click the Teams at the top of the tree, and choose Create Team. Gie a meaningful name to the team (the irtual deice created), the Team Type parameter should be Link Aggregation (802.3ad). b. Check the "members" of this team (the ports to be assigned to the deice), and click Apply / Exit. 2. Configure the IP address to the newly created team: a. Open Network Connections, right-click the new deice (appears under what was defined as "Team Name") Properties > Internal Protocol (TCP/IP) > Propertiesbutton. b. Choose Use the following IP address, and change the IP address and the Subnet mask. Configuring teams, load balancing and IP addresses on Solaris hosts In order to configure teams in Solaris platforms, do the following: 1. Verify ports aailability. # diadm show-de This command shows information for all Ethernet deices (status, speed, duplex, etc.). If any of the required ports are down, check the physical cables and ports before continuing with configuration. 2. Check for preious link Aggregation setting. # diadm show-aggr Chapter 8. OpenStorage (OST) network configuration 55

78 If no link aggregation settings hae been configured on the machine, expect no output. # diadm delete-aggr <aggregation key number> Use this command to delete a link aggregation. Some Solaris systems require you to take the port down and unplumb it prior to deletion. It is highly recommended to do so to the physical ports to be used by the link aggregation to be created, as problems might be encountered later. a. # ifconfig <aggregation name> down b. # ifconfig <aggregation name> unplumb c. # ifconfig <deice / physical port name> down d. # ifconfig <deice / physical port name> unplumb 3. Create Link Aggregation a. # dladm create-aggr l <LACP mode> P <Policy Mode> d <deice / physical port name> <aggregation key number> For example, to create a link aggregation oer three ports (e1000g1, e1000g2, e1000g3). The policy will be L4; LACP enabled. b. # dladm create-aggr l actie P L4 d e1000g1 d e1000g2 d e1000g3 1 c. # dladm show-aggr Verify the link aggregation creation using this command. 4. Actiate and set IP address to the Link Aggregation a. # ifconfig <aggregation name> plumb b. # ifconfig <aggregation name> up c. # ifconfig <aggregation name> set <IP address> netmask <netmask> Example: a. # ifconfig aggr1 plumb b. # ifconfig aggr1 up c. # ifconfig aggr1 set netmask Configuring teams, load balancing and IP addresses on Linux hosts 1. Create the irtual interface: a. Create a file in /etc/sysconfig/network-scripts/ named ifcfg-irt# (# represent the ID number of the irtual deice) and fill it with the following data: LINKDELAY=30 BOOTPROTO=none BONDING_OPTS="miimon=100 mode=4 xmit_hash_policy=layer3+4" DEVICE=irt1 NETMASK=xxx.xxx.xxx.xxx BROADCAST= xxx.xxx.xxx.xxx IPADDR= xxx.xxx.xxx.xxx NETWORK= xxx.xxx.xxx.xxx ONBOOT=yes USERCTL=no b. Fill the IP addresses according to your enironment allocation. 2. Assign physical ports to the irtual port: 56 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

79 Hosts Change the /etc/sysconfig/network-scripts/ifcfg-eth# file of the physical ports you want to bond to the newly created irtual one. It should look like this: BOOTPROTO=none MASTER=irt# HWADDR=xx:xx:xx:xx:xx:xx ONBOOT=yes SLAVE=yes DEVICE=eth# 3. In order for the changes to take effect you need to add the following line to the /etc/modprobe.conf file: alias irt# bonding. 4. Restart the network serice (serice network restart). The hosts can be serers of arious types, operating systems, and hardware profiles. This section describes the configurations of the following deices Broadcom and NICs on Windows platforms and IBM AIX serer Broadcom NICs with Microsoft Platforms If configuring teams, the Broadcom NICs should be configured with the Broadcom network utility. Choose team type of Link Aggregation (802.3ad). Note: See Configuration instructions and examples on page 53. IBM AIX Platforms If configuring bond, use the AIX configuration tools to create a new link aggregation of type 802.3ad. Set the hash mode to src_dst_port parameter. Note: See Configuration instructions and examples on page 53. Solaris Platforms If configuring bond, use the dladm configuration command to create a new link aggregation. LACP mode should be actie and policy should be L4. Network topologies Note: See Configuration instructions and examples on page 53. Connectiity on a Single Site When connecting the ProtecTIER on a single site with the hosts, it will be connected on the same VLAN with the hosts, or on separate VLANs. Connectiity on a single VLAN, with a single IP subnet In a single switch topology, the ProtecTIER serers and the hosts are connected to the same VLAN, with the same IP subnet, on a same physical switch. Chapter 8. OpenStorage (OST) network configuration 57

80 HOST Host Backup To the IBM ProtecTIER Serer Team VLAN X IP NET A VLAN Y IP NET B LAN Switch Team PT Serer IBM ProtecTIER Serer Figure 9. Single host with single ProtecTIER serer on the same VLAN Connectiity on different Switches When connecting the hosts and the ProtecTIER serers on multiple LAN switches, the connectiity between the switches must hae the capability of transferring the data rate required for the backup. Therefore, we recommend using a 10Gb Ethernet connectiity between the switches. Another option would be to define another link aggregation between the switches such that they will be capable of transferring the required bandwidth. ts IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

81 Host Backup To the IBM ProtecTIER Serer HOST Team VLAN X IP NET A VLAN Y IP NET B VLAN X IP NET A VLAN Y IP NET B PT Serer Team IBM ProtecTIER Serer LAN Switch 10Giga Ethernet Trunk LAN Switch Figure 10. Multiple switches The dual switch configuration can be used for high-aailability with switch redundancy. ts HOST HOST Host Backup to the IBM ProtecTIER Serer HOST HOST Team Team Team Team LAN Switch LAN Switch Team1 Team2 Team1 Team2 PT Serer Figure 11. High aailability configuration 2 IBM ProtecTIER Serer PT Serer ts Chapter 8. OpenStorage (OST) network configuration 59

82 Connectiity on different VLANs, with different IP subnets In this topology, the host and the ProtecTIER serer are connected on separate VLANs and subnets. The switch has L3 support. Routing is performed between the VLANs. Host Backup To the IBM ProtecTIER Serer HOST Team VLAN X IP NET A VLAN Y IP NET B LAN Switch Team PT Serer IBM ProtecTIER Serer Figure 12. Host with single ProtecTIER serer on the different VLANs Connectiity to a Remote Site When connecting the ProtecTIER serer on a site which is remotely connected to the sites where the hosts are located, all backup traffic will be transmitted through a router (or routers) that connects between the sites. ts The routers (or routers) can be connected to the network ia a single interface, or multiple interfaces in a teaming configuration. 60 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

83 HOST Host Backup To the IBM ProtecTIER Serer Single or Multiple NIC/NICs Single or Multiple NIC/NICs Team L2 Switch L2 Switch Team PT Serer Figure 13. Connectiity in remote sites ts Chapter 8. OpenStorage (OST) network configuration 61

84 62 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

85 Chapter 9. IBM-proided TS7650G equipment and documents The TS7650G shipment includes the following components. Please note that part numbers are subject to change. Ship group 45E DD3 Ship Group MFI 45E6829 ISO bom (1x) 42R6959 Perchlorite Flyer (1x) 95P2031 Hotline Card Recoery Disk (1x) IBM System Storage ProtecTIER Maintenance and Recoery Disk ProtecTIER Software (1x) IBM(r) System Storage(tm) ProtecTIER Enterprise Edition V3.1 DVD (1x) IBM(r) System Storage(tm) ProtecTIER Manager V3.1 DVD Mcode (1x) 45E6129 CD-ROM 3958 DD4 Cache Config script (1x) 45E1456 License Agreement for Machine Code Z Labels (1x) 45E5260 Fibre Label set (1x) 45E8062 Fibre Label set (1x) 45E5262 Power Label set (1x) 45E5261 Ethernet Label set Miscellaneous (RR) 45E6228 IBM System Storage ProtecTIER Source Code (as requested) (2x) 95P ' Ethernet Cable (2x) 95P M Ethernet Cable Publications (1x) 45E8334 Start Here (1x) 45E8335 Statement of Limited Warranty (1x) 45E8332 IBM System Storage TS7650 with ProtecTIER Publications CD (contains): IBM System Storage TS7650G ProtecTIER Deduplication Gateway Introduction and Planning Guide, IBM form number GA IBM System Storage TS7650G ProtecTIER Deduplication Gateway Installation Roadmap Guide, IBM form number GA IBM System Storage ProtecTIER User's Guide for Enterprise Edition and Appliance Edition, IBM form number GA IBM System Storage Problem Determination Guide for the TS7650 ProtecTIER Deduplication Appliance and TS7650G ProtecTIER Deduplication Gateway, IBM form number GA Copyright IBM Corp

86 IBM System Storage Labeling Instructions for the TS7650 ProtecTIER Deduplication Appliance and TS7650G ProtecTIER Deduplication Gateway, IBM part number 95P8301 TSSC Code and Publications (Supplied ia TSSC Features) 46X4112 (1x) TSSC Version or higher microcode 46X4114 (1x) TSSC Documentation CD 46X4115 (1x) TSSC MI 46X4457 (1x) DS4000 GUI CD 64 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

87 Chapter 10. Company information worksheet IBM serice representaties use the information that is proided on the company information worksheet to customize your IBM storage complex. When you use any of the remote support features, the TSSC sends this information to IBM so an IBM serice representatie can contact you. Table 13. Company information worksheet Required information Description Your information Business company name The full name of your company. IBM serice representaties use this information to identify your company when they receie Call Home reports from your IBM storage system. Ensure that the company name proided is consistent with all other machines that correspond to your IBM customer account. Customer number The IBM-assigned customer number for your company. This is proided by the customer. Country code The two-digit number that must be used in order to reach your country by phone or fax, from another country. This is not the three-digit RETAIN country code. Frame range number See Table 14 on page 67. This alue is specific for setting the IP address range for a TSSC connection ( xxx). These ranges are set in units of 10 for standalone serers. For example: standalone serer 1 would be frame range 10, standalone serer 2 (connected to the same TSSC) would be frame range 20, etc. When clustering a second serer, the frame range number entered should be the same number used for the first frame. For example: 10 for the original serer's frame number ( ), and when prompted, enter 10 for the second node. The system will automatically assign the frame range to 15 and the IP of the second node (in this case: ). SMTP Serer ID / IP address To check the original serer's IP address, iew the Attached System list on the TSSC, where the last octet of the IP address is the frame number ( = 10). Copyright IBM Corp

88 Table 13. Company information worksheet (continued) Required information Description Your information SMTP address The address of the administrator who receies failure alerts for the serer. This may or may not be the administrator listed below. System administrator information Proide information about your storage system administrator in the following section. Administrator name The name of the indiidual at your site who IBM serice representaties should contact about IBM storage system serice matters. Administrator address The storage system administrator's address. Voice phone number The primary telephone number that IBM serice representaties should use to contact the storage system administrator. Include the area code and the country code, if appropriate. Fax number The primary fax number that IBM serice representaties should use to fax documents to the storage system administrator. Include the area code and the country code, if appropriate. Alternate fax number An alternate fax number that IBM serice representaties can use to fax documents to the storage system administrator. Include the area code and the country code, if appropriate. Administrator mailing address The postal mailing address for the storage system administrator. proide the full street address, building (if appropriate), city or locality, state or proince, and postal or zip code. Storage system information Proide basic information about your storage system and the TSSC in the following section. Machine type and model number The machine type and model number for the ProtecTIER TS7650 serers Gateway = 3958-DD Gateway = 3958-DD Gateway = 3958-DD Appliance = 3958 AP Appliance = 3958 AP1 Machine location Call back phone number The address of the facility where the TS7650 serer(s) reside. If different from the administrator mailing address aboe, proide the full street address, building (if appropriate), city or locality, state or proince, and postal or zip code. The phone number of the modem being used for Call Home. Include the area code and the country code, if appropriate. 66 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

89 Table 13. Company information worksheet (continued) Required information Description Your information Disk array machine type(s) and model number(s) Disk array serial number(s) The machine type(s) and model number(s) for the attached disk array storage subsystem(s). For non-ibm equipment, also proide endor name(s). Use an additional sheet if necessary. The serial number(s) for the attached disk array storage subsystem(s). Table 14. Country codes Use the information in the following table to conert a country to a code, and use that code as an entry in the Country code field of the Table 13 on page 65. Country Code Country Code Country Code Country Code Country Code Afghanistan af Cook Islands ck Iceland is Nauru nr Solomon Islands sb Albania al Costa Rica cr India in Nepal np Somalia so Algeria dz Croatia hr Indonesia id Netherlands nl South Africa za American Samoa as Cuba cu Iran ir Netherlands Antilles an South Korea kr Andorra ad Cyprus cy Iraq iq Neutral Zone nt Spain es Angola ao Czech Republic cz Ireland ie New Caledonia (French) nc Sri Lanka lk Anguilla ai Denmark dk Israel il New Zealand nz Sudan sd Antarctica aq Djibouti dj Italy it Nicaragua ni Suriname sr Antigua and Barbuda ag Dominica dm Iory Coast (Cote D'Ioire) Argentina ar Dominican Republic ci Niger ne Salbard and Jan Mayen Islands do Jamaica jm Nigeria ng Swaziland sz Armenia am East Timor tp Japan jp Niue nu Sweden se Aruba aw Ecuador ec Jordan jo Norfolk Island nf Switzerland ch Australia au Egypt eg Kazakhstan kz North Korea kp Syria sy Austria at El Salador s Kenya ke Northern Mariana Islands mp Tadjikistan tj Azerbaidjan az Equatorial Guinea gq Kiribati ki Norway no Taiwan tw Bahamas bs Eritrea er Kuwait kw Oman om Tanzania tz Bahrain bh Estonia ee Kyrgyzstan kg Pakistan pk Thailand th Bangladesh bd Ethiopia et Laos la Palau pw Togo tg Barbados bb Falkland Islands fk Latia l Panama pa Tokelau tk Belarus by Faroe Islands fo Lebanon lb Papua New Guinea pg Tonga to Belgium be Fiji fj Lesotho ls Paraguay py Trinidad and Tobago Belize bz Finland fi Liberia lr Peru pe Tunisia tn Benin bj Former cs Libya ly Philippines ph Turkey tr Czechosloakia sj tt Chapter 10. Company information worksheet 67

90 Table 14. Country codes (continued) Country Code Country Code Country Code Country Code Country Code Bermuda bm Former USSR su Liechtenstein li Pitcairn Island pn Turkmenistan tm Bhutan bt France fr Lithuania lt Poland pl Turks and Caicos Islands tc Boliia bo France (European Territory) Bosnia- Herzegoina fx Luxembourg lu Polynesia (French) pf Tualu t ba French Guyana gf Macau mo Portugal pt Uganda ug Botswana bw French Southern Territories Bouet Island tf Macedonia mk Puerto Rico pr Ukraine ua b Gabon ga Madagascar mg Qatar qa United Arab Emirates Brazil br Gambia gm Malawi mw Reunion (French) British Indian Ocean Territory Brunei Darussalam ae re United Kingdom uk io Georgia ge Malaysia my Romania ro United States of America bn Germany de Maldies m Russian Federation us ru Uruguay uy Bulgaria bg Ghana gh Mali ml Rwanda rw USA Minor Outlying Islands Burkina Faso bf Gibraltar gi Malta mt S. Georgia & S. Sandwich Isls. Burundi bi Great Britain gb Marshall Islands Cambodia kh Greece gr Martinique (French) um gs Uzbekistan uz mh Saint Helena sh Vanuatu u mq Saint Kitts & Neis Anguilla kn Vatican City State a Cameroon cm Greenland gl Mauritania mr Saint Lucia lc Venezuela e Canada ca Grenada gd Mauritius mu Saint Pierre pm Vietnam n and Miquelon Cape Verde c Guadeloupe (French) Cayman Islands Central African Republic gp Mayotte yt Saint Tome (Sao Tome) and Principe ky Guam (USA) gu Mexico mx Saint Vincent & Grenadines st c Virgin Islands (British) Virgin Islands (USA) cf Guatemala gt Micronesia fm Samoa ws Wallis and Futuna Islands Chad td Guinea gn Moldaia md San Marino sm Western Sahara eh Chile cl Guinea Bissau gw Monaco mc Saudi Arabia sa Yemen ye China cn Guyana gy Mongoliar mn Senegal sn Yugoslaia yu Christmas Island cx Haiti ht Montserrat ms Seychelles sc Zaire zr Cocos (Keeling) Islands cc Heard and McDonald Islands hm Morocco ma Sierra Leon sl Zambia zm Colombia co Honduras hn Mozambique mz Singapore sg Zimbabwe zw Comoros km Hong Kong hk Myanmar mm Sloak sk Republic Congo cg Hungary hy Namibia na Sloenia si g i wf 68 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

91 Chapter 11. IP address worksheet Use this worksheet to specify the IP addresses assigned to the TS7650G or TS7650 Appliance components. IBM serice representaties use the information proided to define the IP addresses of components supported by the TSSC. When the TSSC sends Call Home information to IBM through VPN or modem, or sends you notices about sericeable eents, these settings will be included in the information to identify and proide important information about the TSSC that sent a serice request. Table 15 on page 70 and Table 17 on page 71 show the default IP addresses for the TS7650G and TS7650 Appliance serers with VTL configurations. Table 16 on page 70 and Table 18 on page 72 show the default IP addresses for the TS7650G and TS7650 Appliance serers with OpenStorage configurations. Table 20 on page 73 shows the IP address, network mask, DNS and VLAN settings for the source and destination serers for replication. This information is needed to configure the indiidual ports to communicate and transfer data oer the replication network. Write this information in the spaces proided for future reference. Table 21 on page 74 shows the host names and other settings needed for replication. Write the appropriate information in the spaces proided for future reference. Table 22 on page 75 shows the default IP addresses for the TSSC. Table 23 on page 76 shows the IP address ranges for the gateway or appliance components once they are configured to be on the TSSC's xx network. In the spaces proided in Table 23 on page 76, write the IP addresses that you assign for each component, so that the IP address information is aailable for future reference. Copyright IBM Corp

92 Attention: 1. All components use subnet mask Do not configure the replication ports on the same subnet as the external LAN port Eth0. Doing so may cause replication errors. Factory-default IP addresses for a stand-alone VTL configuration for a TS7650G 3958 DD4 or TS7650 Appliance Table 15. Factory-default serer IP addresses for a stand-alone VTL ProtecTIER serer (3958 DD4 or 3958 AP1) Stand-alone TS7650 VTL configuration Component Port Function Node A (the serer located in the lower part of the rack) Factory Default IP Address Serer A eth0 Customer local LAN Serer A eth1 Cluster network 1 N/A Serer A eth2 Replication network Serer A eth3 RAS xx Serer A eth4 Cluster network 2 N/A Serer A eth5 Replication network Factory-default IP addresses for a stand-alone OpenStorage configuration for a TS7650G 3958 DD4 or TS7650 Appliance Table 16. Factory-default serer IP addresses for a stand-alone OpenStorage ProtecTIER serer (3958 DD4 or 3958 AP1) Stand-alone TS7650 OpenStorage configuration Component Port Function Factory Default IP Address Node A (the serer located in the lower part of the rack) Serer A eth0 Customer local LAN Serer A eth1 Cluster network 1 N/A Serer A eth2 Free N/A Serer A eth3 RAS xx Serer A eth4 OpenStorage Serer A eth5 OpenStorage Serer A eth6 OpenStorage Serer A eth7 Replication Serer A eth8 OpenStorage Serer A eth9 OpenStorage Serer A eth10 OpenStorage Serer A eth11 Replication network Serer A eth12 Cluster network 2 N/A Serer A eth13 Free N/A 70 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

93 Factory-default serer IP addresses for a clustered VTL TS7650G 3958 DD4 or TS7650 Appliance Table 17. Factory-default serer IP addresses for a clustered VTL ProtecTIER system (3958 DD4 or 3958 AP1) TS7650 clustered VTL system Component Port Function Node A (the serer located in the lower part of the rack) Factory Default IP Address Serer A eth0 Customer local LAN Note: By default, the TS7650 serers use the IP address range through for the power control network. The serer IP addresses do not change from frame to frame. Serer A eth1 Cluster network 1 Serer A eth2 Replication network 1 Serer A eth3 RAS xx Serer A eth4 Cluster network 2 Serer A eth5 Replication network 2 Network Power Switch N/A Node B (the serer located in the upper part of the rack) Serer B eth0 Customer local LAN Note: By default, the TS7650 serers use the IP address range through , for the power control network. The serer IP addresses do not change from frame to frame. Serer B eth1 Cluster network 1 Serer B eth2 Replication network 1 Serer B eth3 RAS xx Serer B eth4 Cluster network 2 Serer B eth5 Replication network 2 Network Power Switch N/A Chapter 11. IP address worksheet 71

94 Factory-default serer IP addresses for a clustered OpenStorage TS7650G 3958 DD4 or TS7650 Appliance Table 18. Factory-default serer IP addresses for a clustered OpenStorage ProtecTIER system (3958 DD4 or 3958 AP1) TS7650 clustered VTL system Component Port Function Node A (the serer located in the lower part of the rack) Factory Default IP Address Serer A eth0 Customer local LAN Note: By default, the TS7650 serers use the IP address range through for the power control network. The serer IP addresses do not change from frame to frame. Serer A eth1 Cluster network Serer A eth2 Free Serer A eth3 RAS xx Serer A eth4 OpenStorage Serer A eth5 OpenStorage Serer A eth6 OpenStorage Serer A eth7 Replication network Serer A eth8 OpenStorage Serer A eth9 OpenStorage Serer A eth10 OpenStorage Serer A eth11 Replication network Serer A eth12 Cluster network Serer A eth13 Free Network Power Switch N/A Node B (the serer located in the upper part of the rack) Serer B eth0 Customer local LAN Note: By default, the TS7650 serers use the IP address range through , for the power control network. The serer IP addresses do not change from frame to frame. Serer B eth1 Cluster network Serer B eth2 Free Serer B eth3 RAS xx Serer B eth4 OpenStorage Serer B eth5 OpenStorage Serer B eth6 OpenStorage Serer B eth7 Replication network Serer B eth8 OpenStorage Serer B eth9 OpenStorage Serer B eth10 OpenStorage Serer B eth11 Replication network Serer B eth12 Cluster network Serer B eth13 Free Network Power Switch N/A IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

95 Customer IP addresses Table 19. Customer IP addresses Node A (the serer located in Port Host Name IP Address Network Mask Default Gateway the lower part of the rack) eth0 Node B (the serer located in Port IP Address Network Mask Default Gateway the upper part of the rack) eth0 Customer and Replication IP addresses Table 20. Customer and Replication IP addresses for VTL or OpenStorage systems Default gateways for eth2 and eth5 for VTL systems or eth5 or eth13 for OpenStorage systems should be different, otherwise the lans are meaningless. For VTL systems, proide a routing path from the IP address on eth2-serer1 to the IP address of eth2-serer2, and a routing path from the IP address on eth5-serer1 to the IP address of eth5-serer2. For OpenStorage systems, proide a routing path from the IP address on eth5-serer1 to the IP address of eth5-serer2, and a routing path from the IP address on eth13-serer1 to the IP address of eth13-serer2. Source Site Node A (the serer located in the lower part of the rack) Port IP Address Network Mask Default Gateway Dedicated VLAN eth2 for VTL systems or eth5 for OpenStorage systems eth5 for VTL systems or eth13 for OpenStorage systems Node B (the serer located in the upper part of the rack) Port IP Address Network Mask Default Gateway Dedicated VLAN eth2 for VTL systems or eth5 for OpenStorage systems eth5 for VTL systems or eth13 for OpenStorage systems Node A (the serer located in the lower part of the rack) Destination or Target Site Port IP Address Network Mask Default Gateway Dedicated VLAN eth2 for VTL systems or eth5 for OpenStorage systems eth5 for VTL systems or eth13 for OpenStorage systems Chapter 11. IP address worksheet 73

96 Table 20. Customer and Replication IP addresses for VTL or OpenStorage systems (continued) Node B (the serer located in the upper part of the rack) Port IP Address Network Mask Default Gateway Dedicated VLAN eth2 for VTL systems or eth5 for OpenStorage systems eth5 for VTL systems or eth13 for OpenStorage systems Host names and DNS settings for setting up the TSSC with the TS7650G Table 21. Host names and DNS settings for setting up the TSSC with the TS7650G Item or setting Instructions eth0 eth1 (if applicable) Source host name Record the console or host name that you want to assign to the management console workstation (for example, dse1). The console name and the domain are used to identify the TS7650G to the network. IP address (client) #1: IP address #2 (serice): IP address #1 (client): IP address #2 (serice): Domain name Proide the domain name that you are assigning to the TSSC (for example, medina.xyz.it). Ethernet settings Complete the LAN Adapter Details section when the TSSC connects to your LAN. Media speed (Ethernet) TCP/IP interface network mask Check Autodetection or the media speed of the Ethernet adapter. Record the dotted decimal network mask that you want to apply to the TCP/IP address (for example, ). _ Autodetection _ 10Mpbs Half Duplex _ 10Mpbs Full Duplex _ 100Mpbs Half Duplx _ 100Mpbs Full Duplx _ 1000Mpbs Half Duplx _ 1000Mpbs Full Duplx _ Autodetection _ 10Mpbs Half Duplex _ 10Mpbs Full Duplex _ 100Mpbs Half Duplx _ 100Mpbs Full Duplx _ 1000Mpbs Half Duplx _ 1000Mpbs Full Duplx DNS settings: Complete this section if you plan to use a domain name serer (DNS) to resole network names. Name serer (DNS) internet address 1 Name serer domain name 1 Proide the dotted decimal address of the name serer that the TSSC will access (for example, ). Proide the domain name of the name serer (for example, medina.xyz.it). 74 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

97 Table 21. Host names and DNS settings for setting up the TSSC with the TS7650G (continued) Item or setting Instructions eth0 eth1 (if applicable) Name serer (DNS) internet address 2 (Optional) Name serer domain name 2 Proide the dotted decimal address of the second name serer that this workstation can access (for example, ). Although this is optional, you can specify a second name serer when you configure a backup or secondary serer. If you hae a second name serer, proide the domain name of the second name serer (for example, medina2.xyz.it). Routing settings: Complete the following section if you want to specify a default gateway for routing. Gateway address Confirm and record the dotted decimal or symbolic name address of the gateway (for example, or londongate). Table 22. TSSC IP addresses TSSC IP addresses TSSC Ethernet Port Default IP Address TSSC External N/A TSSC Internal (fixed, do not change) Customer Assigned IP Address N/A TSSC IP addresses from frame-to-frame A single frame is ten IP addresses, and each node within a frame requires its own set of ten IP addresses from 0 to 9. If there are no attached deices/systems, the first usable frame would be 10. For example: would be considered frame would be considered frame would be considered frame would be considered frame 240 Chapter 11. IP address worksheet 75

98 Table 23. Base Clusters and Additional Storage Component IP addresses The TSSC IP address range changes from frame to frame, and each new frame increments by a multiple of 10. For example, the first stand-alone frame range would be 10, and the second frame range would be 20. If this is a clustered set of serers, the entry for the first serer (A) will most likely be 10. For the entry for the second serer (B), you will also enter 10 for the frame number. The code will make the adjustment automatically based on the answer you proide during the RAS package installation process that asks you if you are setting up the second node. If you reply "Yes", the code will set the IP range for node 2 at 5 octets higher than what is set for node 1 (serer A). For example, if serer A is set for then serer B will be set for Note: Depending upon the address ranges aailable on the TSSC, the IBM Serice representatie may hae to use ranges other than those shown here. Component Serer Serer Port eth3 RSA or IMM IP Addresses: Stand-alone serer -or- Node A in a cluster (the serer located in the lower part of the rack) Examples: For eth3, x0 For RSA or IMM, x1 IP Addresses: Node B in a cluster (the serer located in the upper part of the rack) Examples: For eth3, x5 For RSA or IMM, x6 76 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

99 Chapter 12. Replication settings worksheet Use this worksheet to determine and record the information you need to implement replication on your TS7650G or TS7650 Appliance. Replication policy and Grid management information Table 24. Replication policy information Replication policy information Policy name Policy priority leel Low Medium High Policy enabled: Y/N Destination repository name Destination target Shelf Library Library name Barcodes for range of cartridges to be replicated Replication meta-data resered space Grid Management information Copyright IBM Corp

100 78 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

101 Chapter 13. ProtecTIER Replication Network Performance Validation Utility for VTL Systems The VTL pt_net_perf_util utility's objectie is to test maximal replication performance between two future ProtecTIER VTL repositories by emulating the network usage patterns of ProtecTIER's Natie Replication component. This utility will not predict replication performance, but it may discoer performance bottlenecks. Before you begin The requirements of this utility are as follows: Red Hat Enterprise Linux 5.4 Standard external utilities expected to be in the current path: ping, netstat, getopt, echo. The pt_net_perf_util utility and the iperf tool it uses are installed as part of the ProtecTIER software installation. To test the replication performance, use the following tool: iperf /usr/local/bin/iperf This utility has two modes of operation, client and serer. The serer has to be started before the client. Before running the utility, shut down all other programs on both the client and serer ProtecTIER systems. The client is the ProtecTIER system that transmits the test data and the serer is the ProtecTIER system that receies the data (also known as the target serer). Based on the data sent by the client and receied by the serer, the script outputs key network parameter alues which indicate certain attributes of the network. The goal of these tests is to benchmark the throughput of the network. The most important benchmark is the direction that replication will actually take place, i.e. the target should be tested as the serer since the flow of data will be to that serer from the client. Howeer, it is also important to also test the reerse direction to measure the bandwidth performance during disaster recoery failback. Network bandwidth is not always the same in both directions. About this task In the following procedure, the goal is to test network performance between two machines on a WAN, serer1 and serer2. Each test will run for fie minutes. Since there are fie tests, the process will take a total of 25 minutes. Procedure 1. Start the serer mode of the utility on serer1 by entering the following commands on the command line: cd /opt/dtc/app/sbin./pt_net_perf_util -s 2. Start the client mode of the utility on serer2 by entering the following command on the command line:./pt_net_perf_util -c serer1 -t 300 Copyright IBM Corp

102 3. The utility will automatically perform the tests in sequence. The client output (serer2 in the example below) will look similar to the following: Note: In the sample output below the test ran for only 5 seconds instead of 300. *** Latency PING ( ) 56(84) bytes of data ping statistics packets transmitted, 5 receied, 0% packet loss, time 4001ms rtt min/ag/max/mde = 0.257/0.406/0.484/0.079 ms *** Throughput - Default TCP [ 3] sec 56.6 MBytes 94.8 Mbits/sec *** Throughput - 1 TCP stream(s), 1MB send buffer [ 3] sec 57.0 MBytes 95.0 Mbits/sec *** Throughput - 16 TCP stream(s), 1MB send buffer [SUM] sec 65.0 MBytes 94.3 Mbits/sec *** Throughput TCP stream(s), 1MB send buffer [SUM] sec 127 MBytes 94.1 Mbits/sec Number of TCP segments sent: Number of TCP retransmissions detected: 21 (0%) Done. See the next section for information about interpreting the results of the tests. Interpreting the results The utility performs fie foreground tests (Tests 1-5 below), and one background test (Test 6 below). The example outputs below are from the client side. Each of the first fie tests below ran for 300 seconds (-t 300), while the last test monitored TCP performance during that time. Test 1: Latency This test checks the nominal network link latency and packet loss. Example result: *** Latency PING ( ) 56(84) bytes of data ping statistics packets transmitted, 120 receied, 0% packet loss, time ms rtt min/ag/max/mde = /78.491/ /9.872 ms Interpreting the results: The aerage round-trip-time (rtt) was 78.4ms and there was 0% packet loss. The latency in WAN topologies may ary, but should neer exceed 200ms. Contact your network administrator if latency reports more than 200ms, as it may significantly decrease replication throughput. Higher latency alues will cause a major deterioration in replication throughput. Packet loss should be 0%. Any other alue indicates a major network problem. Test 2: Throughput - default settings 80 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

103 This test checks maximal TCP throughput using a single data stream with default TCP settings. Example result: *** Throughput - Default TCP [ 3] sec 2.41 GBytes 173 Mbits/sec Interpreting the results: The test ran for seconds, transferred 2.41 GB (2.24 GiB), with an aerage throughput of 173 Mbits/sec. Note: 1 MByte = 1,048,576 bytes. 1 Mbit/sec = 1,000,000 bits/sec. Test 3: Throughput - single stream, 1MB send buffer This test checks maximal TCP throughput using a single data stream with a 1MB (0.95 MiB) send buffer. Example result: *** Throughput - 1 TCP stream(s), 1MB send buffer [ 3] sec 2.51 GBytes 180 Mbits/sec Interpreting the results: The test ran for seconds, transferred 2.51 GB (2.34 GiB), with an aerage throughput of 180 Mbits/sec. There may be an improement here on high-latency links. Test 4: Throughput - 16 streams, 1MB send buffer Example result: *** Throughput - 16 TCP stream(s), 1MB send buffer [SUM] sec 5.91 GBytes 418 Mbits/sec Interpreting the results: The test ran for seconds, transferred 5.91 GB (5.5 GiB), with an aerage throughput of 418 Mbits/sec. The extra streams yielded higher utilization of the connection. The Mbits/sec reported in this test is the maximum replication performance your system will achiee if your backup enironment is using up to 2-3 cartridges in parallel. Test 5: Throughput streams, 1MB send buffer Example result: *** Throughput TCP stream(s), 1MB send buffer [SUM] sec 8.08 GBytes 550 Mbits/sec Interpreting the results: The test ran for seconds, transferred 8.08 GB (7.53 Gb), with an aerage throughput of 550 Mbits/sec. TCP takes a while to reach its maximal throughput. Longer testing times, 300 seconds or more, will produce more accurate results. The throughput alue gien by this test is the potential physical replication throughput for this system. It is directly affected by the aailable bandwidth, latency, packet loss and retransmission rate. Chapter 13. ProtecTIER Replication Network Performance Validation Utility for VTL Systems 81

104 The Mbits/sec reported in this test is the maximum replication performance your system may achiee. If this number is lower than anticipated, contact your network administrator. Test 6: TCP Retransmissions s. Total TCP segments sent Example result: Number of TCP segments sent: Number of TCP retransmissions detected: (12%) Interpreting the results: A total of TCP segments were sent during the fie tests, out of which, were lost and retransmitted. The retransmission rate imposes a direct penalty on the throughput, as the retransmission of these packets take up bandwidth. The retransmission can be caused by the underlying network (e.g. packet dropping by an oerflowed router) or by the TCP layer itself (e.g. retransmission due to packet reordering). Segment loss can be caused by each of the network layers. TCP retransmission larger than 2% may cause performance degradation and unstable network connectiity. Contact your network administrator to resole this issue and reduce it to approximately 0%. What to do next You may want to run these tests again to test the reerse throughput in the network. To run the tests in reerse, change serer1 to the client and serer2 to the serer and repeat the procedures. 82 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

105 Chapter 14. ProtecTIER Network Performance Validation Utility for OpenStorage Systems The OpenStorage pt_net_perf_util utility's objectie is to test network performance between an OpenStorage host and a ProtecTIER serer. This utility will not predict backup and restore performance, but it may discoer performance bottlenecks. Before you begin The requirements of this utility are as follows: Red Hat Enterprise Linux 5.4 or any other platform officially supported by the OpenStorage plug-in Standard external utilities expected to be in the current path such as ping and netstat About this task The pt_net_perf_util utility and the iperf tool it uses are installed as part of the ProtecTIER software installation. The location of the utility aries according to the platform: Windows plug-in: %PROGRAMFILES%\IBM\ost_plugin_tools AIX plug-in: /opt/ibm/ost_plugin_tools ProtecTIER serer: /opp/dtc/app/sbin This utility has two modes of operation, client and serer. The serer has to be started before the client. Before running the utility, shut down all other programs on both the client and serer systems. The client is the system that transmits the test data and the serer is the system that receies the data (also known as the target serer). Based on the data sent by the client and receied by the serer, the script outputs key network parameter alues which indicate certain attributes of the network. The goal of these tests is to benchmark the throughput of the network. It is important to test both OpenStorage host-to-protectier serer and ProtecTIER serer-to-openstorage host directions to measure the bandwidth performance during both backup and restore actiities. Network bandwidth is not always the same in both directions. In addition, if an OpenStorage host or a ProtecTIER serer uses more than one IP address for OpenStorage operation, it is essential to test each IP address separately. In the following procedure, the goal is to test network performance between two machines serer1 and serer2. Each test will run for fie minutes. Since there are fie tests, the process will take a total of 25 minutes. Procedure 1. Start the serer mode of the utility on serer1 by entering the following commands on the command line:./pt_net_perf_util -s 2. Start the client mode of the utility on serer2 by entering the following command on the command line:./pt_net_perf_util -c serer1_ip_address -t 300 Copyright IBM Corp

106 where serer1_ip_address is one of the IP addresses to be tested for serer1. The default size of a buffer used for sending data is 1024KB. To oerride this size to another alue, for example 256KB, use the -l parameter as follows:./pt_net_perf_util -c serer1_ip_address -t 300 -l 256 Note: If serer1 is a Windows system, use following command: pt_net_perf_util.bat -c serer1_ip_address -t win-serer where serer1_ip_address is one of the IP addresses to be tested for serer1. The same buffer oerride command can also be used to change the size of the buffer. 3. The utility will automatically perform the tests in sequence. The client output (serer2 in the example below) will look similar to the following: Note: In the sample output below the test ran for only 5 seconds instead of 300. *** Latency PING ( ) 56(84) bytes of data ping statistics packets transmitted, 5 receied, 0% packet loss, time 4001ms rtt min/ag/max/mde = 0.257/0.406/0.484/0.079 ms *** Throughput - Default TCP [ 3] sec 56.6 MBytes 94.8 Mbits/sec *** Throughput - 1 TCP stream(s), 1MB send buffer [ 3] sec 57.0 MBytes 95.0 Mbits/sec *** Throughput - 16 TCP stream(s), 1MB send buffer [SUM] sec 65.0 MBytes 94.3 Mbits/sec *** Throughput TCP stream(s), 1MB send buffer [SUM] sec 127 MBytes 94.1 Mbits/sec Number of TCP segments sent: Number of TCP retransmissions detected: 21 (0%) Done. 4. See the next section for information about interpreting the results of the tests. Interpreting the results The utility performs fie foreground tests (Tests 1-5 below), and one background test (Test 6 below). The example outputs below are from the client side. Each of the first fie tests below ran for 300 seconds (-t 300), while the last test monitored TCP performance during that time. Test 1: Latency This test checks the nominal network link latency and packet loss. Example result: *** Latency PING ( ) 56(84) bytes of data ping statistics packets transmitted, 120 receied, 0% packet loss, time ms rtt min/ag/max/mde = /78.491/ /9.872 ms Interpreting the results: The aerage round-trip-time (rtt) was 78.4ms and there was 0% packet loss. The round-trip-time in network topologies may ary, but should neer exceed 200ms on WAN. Contact your network administrator if round-trip-time reports more than 200ms on WAN or 6ms on LAN, as it may significantly decrease throughput. 84 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

107 Higher latency alues will cause a major deterioration in throughput. Packet loss should be 0%. Any other alue indicates a major network problem. Test 2: Throughput - default settings This test checks maximal TCP throughput using a single data stream with default TCP settings. Example result: *** Throughput - Default TCP [ 3] sec 2.41 GBytes 173 Mbits/sec Interpreting the results: The test ran for seconds, transferred 2.41 GB (2.24 Gb), with an aerage throughput of 173 Mbits/sec. Note: 1 MByte = 1,048,576 bytes. 1 Mbit/sec = 1,000,000 bits/sec. Test 3: Throughput - single stream, 1MB send buffer This test checks maximal TCP throughput using a single data stream with a 1MB (0.95 MiB) send buffer. Example result: *** Throughput - 1 TCP stream(s), 1MB send buffer [ 3] sec 2.51 GBytes 180 Mbits/sec Interpreting the results: The test ran for seconds, transferred 2.51 GB (2.34 GiB), with an aerage throughput of 180 Mbits/sec. There may be an improement here on high-latency links. Test 4: Throughput - 16 streams, 1MB send buffer Example result: *** Throughput - 16 TCP stream(s), 1MB send buffer [SUM] sec 5.91 GBytes 418 Mbits/sec Interpreting the results: The test ran for seconds, transferred 5.91 GB (5.5 Gb), with an aerage throughput of 418 Mbits/sec. The extra streams yielded higher utilization of the connection. Test 5: Throughput streams, 1MB send buffer Example result: *** Throughput TCP stream(s), 1MB send buffer [SUM] sec 8.08 GBytes 550 Mbits/sec Interpreting the results: The test ran for seconds, transferred 8.08 GB (7.53 Gb), with an aerage throughput of 550 Mbits/sec. TCP takes a while to reach its maximal throughput. Longer testing times, 300 seconds or more, will produce more accurate results. The throughput alue gien by this test is the potential physical throughput for this system. It is directly affected by the aailable bandwidth, latency, packet loss and retransmission rate. Chapter 14. ProtecTIER Network Performance Validation Utility for OpenStorage Systems 85

108 The Mbits/sec reported in this test is the maximum throughput your system may achiee. If this number is lower than anticipated, contact your network administrator. Test 6: TCP Retransmissions s. Total TCP segments sent Example result: Number of TCP segments sent: Number of TCP retransmissions detected: (12%) Interpreting the results: A total of TCP segments were sent during the fie tests, out of which, were lost and retransmitted. The retransmission rate imposes a direct penalty on the throughput, as the retransmission of these packets take up bandwidth. The retransmission can be caused by the underlying network (e.g. packet dropping by an oerflowed router) or by the TCP layer itself (e.g. retransmission due to packet reordering). Segment loss can be caused by each of the network layers. TCP retransmission larger than 2% may cause performance degradation and unstable network connectiity. Contact your network administrator to resole this issue and reduce it to approximately 0%. What to do next You may want to run these tests again to test the reerse throughput in the network. To run the tests in reerse, change serer1 to the client and serer2 to the serer and repeat the procedures. 86 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

109 Chapter 15. Example cache configuration file This is an example configuration file for a TS7650G using a DS4000 disk storage array. Note: This code has been formatted to fit on the page, and is an example only. Consult with Solutions Assurance and your IBM representatie to deelop a configuration file specific to your needs. // Logical configuration information from Storage Subsystem DS_Cache_Subsystem. // Saed on May 28, 2009 // Firmware package ersion for Storage Subsystem DS_Cache_Subsystem = // NVSRAM package ersion for Storage Subsystem DS_Cache_Subsystem = A1814D470R923V08 //on error stop; // Uncomment the two lines below to delete the existing configuration. //show "Deleting the existing configuration."; //set storagesubsystem resetconfiguration = true; // Storage Subsystem global logical configuration script commands show "Setting the Storage Subsystem user label to DS_Cache_Subsystem."; set storagesubsystem userlabel="ds_cache_subsystem"; show "Setting the Storage Subsystem media scan rate to 30."; set storagesubsystem mediascanrate=30; // Uncomment the three lines below to remoe default logical drie, if exists, script command. //NOTE: Default logical drie name is always = "" (blank). //on error continue; //show "Deleting the default logical drie created during the remoal of the existing configuration."; //delete logicaldrie[""]; //on error stop; // Copies the hot spare settings // NOTE: These statements are wrapped in on-error continue and on-error stop statements to // account for minor differences in capacity from the drie of the Storage Subsystem on which the // configuration was saed to that of the dries on which the configuration will be copied. //on error continue; show "Creating hot spare at Enclosure 85 Slot 16."; set drie[85,16] hotspare=true; show "Creating hot spare at Enclosure 1 Slot 16."; set drie[1,16] hotspare=true; show "Creating hot spare at Enclosure 0 Slot 16."; set drie[0,16] hotspare=true; show "Creating hot spare at Enclosure 2 Slot 16."; set drie[2,16] hotspare=true; //on error stop; show "Setting the Storage Subsystem cache block size to 16."; set storagesubsystem cacheblocksize=16; show "Setting the Storage Subsystem to begin cache flush at 80% full."; set storagesubsystem cacheflushstart=80; show "Setting the Storage Subsystem to end cache flush at 80% full."; set storagesubsystem cacheflushstop=80; // Creating Host Topology show "Creating RAID 1 Logical Drie accessa on new Array 1."; Copyright IBM Corp

110 // This command creates the Array and the initial Logical Drie on that array. // NOTE: For Arrays that use all aailable capacity, the last Logical Drie on this array is // created using all remaining capacity by omitting the capacity= logical drie creation parameter. create logicaldrie dries[85,1 85,2 85,3 85,4 85,5 85,6 85,7 85,8 85,9 85,10] raidleel=1 userlabel="accessa" owner=a segmentsize=32 capacity= Bytes; show "Setting additional attributes for Logical Drie accessa."; // Configuration settings that can not be set during Logical Drie creation. set logicaldrie["accessa"] cacheflushmodifier=10; set logicaldrie["accessa"] cachewithoutbatteryenabled=false; set logicaldrie["accessa"] mirrorenabled=true; set logicaldrie["accessa"] readcacheenabled=true; set logicaldrie["accessa"] writecacheenabled=true; set logicaldrie["accessa"] mediascanenabled=true; set logicaldrie["accessa"] redundancycheckenabled=false; set logicaldrie["accessa"] readaheadmultiplier=1; set logicaldrie["accessa"] modificationpriority=high; show "Creating Logical Drie-to-LUN Mapping for Logical Drie accessa to LUN 0."; set logicaldrie ["accessa"] logicalunitnumber=0 hostgroup=defaultgroup; show "Creating RAID 1 Logical Drie metadata0 on existing Array 1."; // Create Logical Drie on the Array created by the create logical drie dries command. // NOTE: For Arrays that use all aailable capacity, the last Logical Drie on this array is // created using all remaining capacity by omitting the capacity= logical drie creation parameter. create logicaldrie array[1] raidleel=1 userlabel="metadata0" owner=a segmentsize=32 capacity= Bytes; show "Setting additional attributes for Logical Drie metadata0."; // Configuration settings that can not be set during Logical Drie creation. set logicaldrie["metadata0"] cacheflushmodifier=10; set logicaldrie["metadata0"] cachewithoutbatteryenabled=false; set logicaldrie["metadata0"] mirrorenabled=true; set logicaldrie["metadata0"] readcacheenabled=true; set logicaldrie["metadata0"] writecacheenabled=true; set logicaldrie["metadata0"] mediascanenabled=true; set logicaldrie["metadata0"] redundancycheckenabled=false; set logicaldrie["metadata0"] readaheadmultiplier=1; set logicaldrie["metadata0"] modificationpriority=high; show "Creating Logical Drie-to-LUN Mapping for Logical Drie metadata0 to LUN 7."; set logicaldrie ["metadata0"] logicalunitnumber=7 hostgroup=defaultgroup; show "Creating RAID 5 Logical Drie userdata0 on new Array 2."; // This command creates the Array and the initial Logical Drie on that array. // NOTE: For Arrays that use all aailable capacity, the last Logical Drie on this array is // created using all remaining capacity by omitting the capacity= logical drie creation parameter. create logicaldrie dries[85,11 85,12 85,13 85,14 85,15] raidleel=5 userlabel="userdata0" owner=a segmentsize=32; show "Setting additional attributes for Logical Drie userdata0."; // Configuration settings that can not be set during Logical Drie creation. set logicaldrie["userdata0"] cacheflushmodifier=10; set logicaldrie["userdata0"] cachewithoutbatteryenabled=false; set logicaldrie["userdata0"] mirrorenabled=true; set logicaldrie["userdata0"] readcacheenabled=true; set logicaldrie["userdata0"] writecacheenabled=true; set logicaldrie["userdata0"] mediascanenabled=true; set logicaldrie["userdata0"] redundancycheckenabled=false; set logicaldrie["userdata0"] readaheadmultiplier=1; set logicaldrie["userdata0"] modificationpriority=high; show "Creating Logical Drie-to-LUN Mapping for Logical Drie userdata0 to LUN 8."; set logicaldrie ["userdata0"] logicalunitnumber=8 hostgroup=defaultgroup; show "Creating RAID 5 Logical Drie userdata1 on new Array 3."; // This command creates the Array and the initial Logical Drie on that array. // NOTE: For Arrays that use all aailable capacity, the last Logical Drie on this array is // created using all remaining capacity by omitting the capacity= logical drie creation parameter. create logicaldrie dries[0,1 0,2 0,3 0,4 0,5] raidleel=5 userlabel="userdata1" owner=b segmentsize=32; show "Setting additional attributes for Logical Drie userdata1."; 88 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

111 // Configuration settings that can not be set during Logical Drie creation. set logicaldrie["userdata1"] cacheflushmodifier=10; set logicaldrie["userdata1"] cachewithoutbatteryenabled=false; set logicaldrie["userdata1"] mirrorenabled=true; set logicaldrie["userdata1"] readcacheenabled=true; set logicaldrie["userdata1"] writecacheenabled=true; set logicaldrie["userdata1"] mediascanenabled=true; set logicaldrie["userdata1"] redundancycheckenabled=false; set logicaldrie["userdata1"] readaheadmultiplier=1; set logicaldrie["userdata1"] modificationpriority=high; show "Creating Logical Drie-to-LUN Mapping for Logical Drie userdata1 to LUN 9."; set logicaldrie ["userdata1"] logicalunitnumber=9 hostgroup=defaultgroup; show "Creating RAID 5 Logical Drie userdata2 on new Array 4."; // This command creates the Array and the initial Logical Drie on that array. // NOTE: For Arrays that use all aailable capacity, the last Logical Drie on this array is // created using all remaining capacity by omitting the capacity= logical drie creation parameter. create logicaldrie dries[0,6 0,7 0,8 0,9 0,10] raidleel=5 userlabel="userdata2" owner=a segmentsize=32; show "Setting additional attributes for Logical Drie userdata2."; // Configuration settings that can not be set during Logical Drie creation. set logicaldrie["userdata2"] cacheflushmodifier=10; set logicaldrie["userdata2"] cachewithoutbatteryenabled=false; set logicaldrie["userdata2"] mirrorenabled=true; set logicaldrie["userdata2"] readcacheenabled=true; set logicaldrie["userdata2"] writecacheenabled=true; set logicaldrie["userdata2"] mediascanenabled=true; set logicaldrie["userdata2"] redundancycheckenabled=false; set logicaldrie["userdata2"] readaheadmultiplier=1; set logicaldrie["userdata2"] modificationpriority=high; show "Creating Logical Drie-to-LUN Mapping for Logical Drie userdata2 to LUN 10."; set logicaldrie ["userdata2"] logicalunitnumber=10 hostgroup=defaultgroup; show "Creating RAID 5 Logical Drie userdata3 on new Array 5."; // This command creates the Array and the initial Logical Drie on that array. // NOTE: For Arrays that use all aailable capacity, the last Logical Drie on this array is // created using all remaining capacity by omitting the capacity= logical drie creation parameter. create logicaldrie dries[0,11 0,12 0,13 0,14 0,15] raidleel=5 userlabel="userdata3" owner=b segmentsize=32; show "Setting additional attributes for Logical Drie userdata3."; // Configuration settings that can not be set during Logical Drie creation. set logicaldrie["userdata3"] cacheflushmodifier=10; set logicaldrie["userdata3"] cachewithoutbatteryenabled=false; set logicaldrie["userdata3"] mirrorenabled=true; set logicaldrie["userdata3"] readcacheenabled=true; set logicaldrie["userdata3"] writecacheenabled=true; set logicaldrie["userdata3"] mediascanenabled=true; set logicaldrie["userdata3"] redundancycheckenabled=false; set logicaldrie["userdata3"] readaheadmultiplier=1; set logicaldrie["userdata3"] modificationpriority=high; show "Creating Logical Drie-to-LUN Mapping for Logical Drie userdata3 to LUN 11."; set logicaldrie ["userdata3"] logicalunitnumber=11 hostgroup=defaultgroup; show "Creating RAID 5 Logical Drie userdata4 on new Array 6."; // This command creates the Array and the initial Logical Drie on that array. // NOTE: For Arrays that use all aailable capacity, the last Logical Drie on this array is // created using all remaining capacity by omitting the capacity= logical drie creation parameter. create logicaldrie dries[1,1 1,2 1,3 1,4 1,5] raidleel=5 userlabel="userdata4" owner=a segmentsize=32; show "Setting additional attributes for Logical Drie userdata4."; // Configuration settings that can not be set during Logical Drie creation. set logicaldrie["userdata4"] cacheflushmodifier=10; set logicaldrie["userdata4"] cachewithoutbatteryenabled=false; set logicaldrie["userdata4"] mirrorenabled=true; set logicaldrie["userdata4"] readcacheenabled=true; set logicaldrie["userdata4"] writecacheenabled=true; set logicaldrie["userdata4"] mediascanenabled=true; Chapter 15. Example cache configuration file 89

112 set logicaldrie["userdata4"] redundancycheckenabled=false; set logicaldrie["userdata4"] readaheadmultiplier=1; set logicaldrie["userdata4"] modificationpriority=high; show "Creating Logical Drie-to-LUN Mapping for Logical Drie userdata4 to LUN 12."; set logicaldrie ["userdata4"] logicalunitnumber=12 hostgroup=defaultgroup; show "Creating RAID 5 Logical Drie userdata5 on new Array 7."; // This command creates the Array and the initial Logical Drie on that array. // NOTE: For Arrays that use all aailable capacity, the last Logical Drie on this array is // created using all remaining capacity by omitting the capacity= logical drie creation parameter. create logicaldrie dries[1,6 1,7 1,8 1,9 1,10] raidleel=5 userlabel="userdata5" owner=b segmentsize=32; show "Setting additional attributes for Logical Drie userdata5."; // Configuration settings that can not be set during Logical Drie creation. set logicaldrie["userdata5"] cacheflushmodifier=10; set logicaldrie["userdata5"] cachewithoutbatteryenabled=false; set logicaldrie["userdata5"] mirrorenabled=true; set logicaldrie["userdata5"] readcacheenabled=true; set logicaldrie["userdata5"] writecacheenabled=true; set logicaldrie["userdata5"] mediascanenabled=true; set logicaldrie["userdata5"] redundancycheckenabled=false; set logicaldrie["userdata5"] readaheadmultiplier=1; set logicaldrie["userdata5"] modificationpriority=high; show "Creating Logical Drie-to-LUN Mapping for Logical Drie userdata5 to LUN 13."; set logicaldrie ["userdata5"] logicalunitnumber=13 hostgroup=defaultgroup; show "Creating RAID 5 Logical Drie userdata6 on new Array 8."; // This command creates the Array and the initial Logical Drie on that array. // NOTE: For Arrays that use all aailable capacity, the last Logical Drie on this array is // created using all remaining capacity by omitting the capacity= logical drie creation parameter. create logicaldrie dries[1,11 1,12 1,13 1,14 1,15] raidleel=5 userlabel="userdata6" owner=a segmentsize=32; show "Setting additional attributes for Logical Drie userdata6."; // Configuration settings that can not be set during Logical Drie creation. set logicaldrie["userdata6"] cacheflushmodifier=10; set logicaldrie["userdata6"] cachewithoutbatteryenabled=false; set logicaldrie["userdata6"] mirrorenabled=true; set logicaldrie["userdata6"] readcacheenabled=true; set logicaldrie["userdata6"] writecacheenabled=true; set logicaldrie["userdata6"] mediascanenabled=true; set logicaldrie["userdata6"] redundancycheckenabled=false; set logicaldrie["userdata6"] readaheadmultiplier=1; set logicaldrie["userdata6"] modificationpriority=high; show "Creating Logical Drie-to-LUN Mapping for Logical Drie userdata6 to LUN 14."; set logicaldrie ["userdata6"] logicalunitnumber=14 hostgroup=defaultgroup; show "Creating RAID 5 Logical Drie userdata7 on new Array 9."; // This command creates the Array and the initial Logical Drie on that array. // NOTE: For Arrays that use all aailable capacity, the last Logical Drie on this array is // created using all remaining capacity by omitting the capacity= logical drie creation parameter. create logicaldrie dries[2,1 2,2 2,3 2,4 2,5] raidleel=5 userlabel="userdata7" owner=b segmentsize=32; show "Setting additional attributes for Logical Drie userdata7."; // Configuration settings that can not be set during Logical Drie creation. set logicaldrie["userdata7"] cacheflushmodifier=10; set logicaldrie["userdata7"] cachewithoutbatteryenabled=false; set logicaldrie["userdata7"] mirrorenabled=true; set logicaldrie["userdata7"] readcacheenabled=true; set logicaldrie["userdata7"] writecacheenabled=true; set logicaldrie["userdata7"] mediascanenabled=true; set logicaldrie["userdata7"] redundancycheckenabled=false; set logicaldrie["userdata7"] readaheadmultiplier=1; set logicaldrie["userdata7"] modificationpriority=high; show "Creating Logical Drie-to-LUN Mapping for Logical Drie userdata7 to LUN 15."; set logicaldrie ["userdata7"] logicalunitnumber=15 hostgroup=defaultgroup; show "Creating RAID 5 Logical Drie userdata8 on new Array 10."; 90 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

113 // This command creates the Array and the initial Logical Drie on that array. // NOTE: For Arrays that use all aailable capacity, the last Logical Drie on this array is // created using all remaining capacity by omitting the capacity= logical drie creation parameter. create logicaldrie dries[2,6 2,7 2,8 2,9 2,10] raidleel=5 userlabel="userdata8" owner=a segmentsize=32; show "Setting additional attributes for Logical Drie userdata8."; // Configuration settings that can not be set during Logical Drie creation. set logicaldrie["userdata8"] cacheflushmodifier=10; set logicaldrie["userdata8"] cachewithoutbatteryenabled=false; set logicaldrie["userdata8"] mirrorenabled=true; set logicaldrie["userdata8"] readcacheenabled=true; set logicaldrie["userdata8"] writecacheenabled=true; set logicaldrie["userdata8"] mediascanenabled=true; set logicaldrie["userdata8"] redundancycheckenabled=false; set logicaldrie["userdata8"] readaheadmultiplier=1; set logicaldrie["userdata8"] modificationpriority=high; show "Creating Logical Drie-to-LUN Mapping for Logical Drie userdata8 to LUN 16."; set logicaldrie ["userdata8"] logicalunitnumber=16 hostgroup=defaultgroup; show "Creating RAID 5 Logical Drie userdata9 on new Array 11."; // This command creates the Array and the initial Logical Drie on that array. // NOTE: For Arrays that use all aailable capacity, the last Logical Drie on this array is // created using all remaining capacity by omitting the capacity= logical drie creation parameter. create logicaldrie dries[2,11 2,12 2,13 2,14 2,15] raidleel=5 userlabel="userdata9" owner=b segmentsize=32; show "Setting additional attributes for Logical Drie userdata9."; // Configuration settings that can not be set during Logical Drie creation. set logicaldrie["userdata9"] cacheflushmodifier=10; set logicaldrie["userdata9"] cachewithoutbatteryenabled=false; set logicaldrie["userdata9"] mirrorenabled=true; set logicaldrie["userdata9"] readcacheenabled=true; set logicaldrie["userdata9"] writecacheenabled=true; set logicaldrie["userdata9"] mediascanenabled=true; set logicaldrie["userdata9"] redundancycheckenabled=false; set logicaldrie["userdata9"] readaheadmultiplier=1; set logicaldrie["userdata9"] modificationpriority=high; show "Creating Logical Drie-to-LUN Mapping for Logical Drie userdata9 to LUN 17."; set logicaldrie ["userdata9"] logicalunitnumber=17 hostgroup=defaultgroup; Chapter 15. Example cache configuration file 91

114 92 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

115 Accessibility for publications and ProtecTIER Manager The publications for this product are in Adobe Portable Document Format (PDF) and should be compliant with accessibility standards. Use these procedures to enable screen-reader compatibility, change the Windows contrast setting, and customize the color palette used in ProtecTIER Manager. About this task If you experience difficulties when you use the PDF files and want to request a Web-based format for a publication, send your request to the following address: International Business Machines Corporation Information Deelopment Department GZW 9000 South Rita Road Tucson, Arizona U.S.A In the request, be sure to include the publication number and title. When you send information to IBM, you grant IBM a nonexclusie right to use or distribute the information in any way it beliees appropriate without incurring any obligation to you. About the Windows-based accessibility features About this task The accessibility features in ProtecTIER Manager help persons with limited ision use the ProtecTIER Manager installation wizard and software. After preparing the ProtecTIER Manager workstation for accessibility, you can use Windows-based screen-reader software and a digital oice synthesizer to hear what is displayed on the screen. The installation, configuration, and instructional screens in the Windows ersions of the ProtecTIER Manager installation wizard and the ProtecTIER Manager software hae been tested with JAWS. Howeer, the associated diagrams and graphs in ProtecTIER Manager and ProtecTIER Replication Manager, do not currently support keyboard naigation or screen-reader use. You can obtain full system statistics (typically proided in the diagrams and graphs) by going to the ProtecTIER Manager toolbar and clicking: Reports > Create long term statistics report, and downloading the results. To enable screen-reader compatibility, you must prepare the ProtecTIER Manager workstation by completing these tasks. Instructions are proided in the topics that follow: Before you install ProtecTIER Manager: Download and install the Jaa Runtime Enironment (JRE). Download and install the Jaa Access Bridge (JAB). After you install ProtecTIER Manager: Copyright IBM Corp

116 About the Jaa-based tools Change the ProtecTIER Manager preferences to enable support of the Windows system settings (required) Select a high-contrast color scheme in Windows (optional) Customize the color palette used in the ProtecTIER Manager display (optional) About this task Complete the following the procedures to download and install the Jaa-based tools that are required to enable full screen-reader compatibility on the ProtecTIER Manager workstation. Install the Jaa Runtime Enironment (JRE) first, and then install the Jaa Access Bridge (JAB). Both of these tools must be installed before you install the ProtecTIER Manager software. For simplicity, download the Jaa-based tools by using the ProtecTIER Manager workstation on which you are installing the JRE and JAB. If this is not possible, try to use another computer that is running Windows. Installing the Jaa Runtime Enironment About this task The JRE includes the Jaa Virtual Machine (JVM). These tools are necessary for your computer to run Jaa-based applications. Procedure 1. Go to The Jaa website opens. The jaa.com website auto-detects the operating system and Internet browser of the computer you use when you access the site. 2. Click Free Jaa Download, and proceed as appropriate: If the Download Jaa for Windows page opens, go on to step 3 If the Download Jaa for... page title contains the name of an operating system other than Windows, do the following: a. Click the See all downloads here link. The list of aailable downloads, categorized by operating system, displays. b. In the Windows section, click Windows 7/XP/Vista/2000/2003/2008 Online. 3. Reiew the information proided, and then click Agree and Start Free Download. The download dialog box opens. 4. Follow the on-screen instructions to sae the executable (.exe) installer file to the hard disk drie. 5. After the download is complete, find the installer file on the hard disk drie and write down the full path to the location of the file. For example: C:\Program Files\Jaa\jre6\bin\jaa.exe. This path is needed during ProtecTIER Manager installation. 6. Proceed as appropriate: 94 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

117 If you downloaded the installer on the ProtecTIER Manager workstation on which you are installing the JRE, go on to step 7. If you downloaded the installer on a PC other than the applicable ProtecTIER Manager workstation, do the following: a. Copy the installer file onto a CD, flash memory drie, or other form of remoable media. b. Copy the installer file from the remoable media to the hard disk drie of the ProtecTIER Manager workstation. c. Go on to step Double-click the installer file to start the Jaa installation wizard. The Jaa Setup Welcome window opens. 8. Click Install and follow the on-screen instructions to complete the installation process. 9. When you hae successfully installed the JRE, go on to Installing the Jaa Access Bridge. Installing the Jaa Access Bridge About this task The Jaa Access Bridge (JAB) makes it possible for you to use Jaa-based screen readers with the ProtecTIER Manager installation wizard and software. Procedure 1. Go to: The Jaa SE Desktop Accessibility page of the Oracle website opens. 2. Read the information proided, then click Access Bridge. 3. Scroll down to the Jaa Access Bridge for Microsoft Windows Operating System x.x.x (where x.x.x is the most recent ersion listed) section. Click the Download Jaa Access Bridge x.x.x link. The Software License Agreement page opens. 4. Read the license agreement, and then select the I agree to the Software License Agreement check box. The Download Jaa Access Bridge for Windows Operating System x.x.x page opens. 5. In the Required Files list, click the link to download the Access Bridge x.x.x, accessbridge-x.x.x.exe file. The download dialog box opens. 6. Follow the on-screen instructions to sae the executable (.exe) installer file to the hard disk drie. 7. When the download is complete, locate the installer file on the hard disk drie and proceed as appropriate: If you downloaded the installer by using the ProtecTIER Manager workstation on which you are installing the JAB, go on to step 8 on page 96. If you downloaded the installer by using a PC other than the applicable ProtecTIER Manager workstation, do the following: a. Copy the installer file onto a CD, flash memory drie, or other remoable media deice. b. Copy the installer file from the remoable media deice to the hard disk drie of the ProtecTIER Manager workstation. Accessibility for publications and ProtecTIER Manager 95

118 c. Go on to step On the ProtecTIER Manager workstation, double-click the accessbridge-x.x.x.exe installer file. A security warning dialog box displays. 9. Click Run. The Jaa Access Bridge InstallShield Wizard opens. 10. Read the welcome information, then click Next and follow the on-screen instructions to complete the installation. 11. When the installation is complete, restart the workstation as directed. You now hae the necessary Jaa tools for compatibility between the ProtecTIER Manager installation wizard and screen reader software. 12. Follow the instructions in Using a screen reader to install ProtecTIER Manager to start the ProtecTIER Manager installation wizard by using a screen reader. Using a screen reader to install ProtecTIER Manager About this task Install ProtecTIER Manager according to the following command line-based instructions. When entering the commands, type them exactly as shown, including any spaces or quotation marks. Any deiation in the procedure can cause the installation to start in the non-accessible mode, or fail completely. Procedure 1. If your workstation is configured to automatically open DVDs, temporarily disable the Windows AutoPlay feature for the CD/DVD deice. Use the Windows Help or other Windows documentation for instructions, and then go on to step Insert the IBM System Storage ProtecTIER Manager V3.1 DVD into the CD/DVD drie of the ProtecTIER Manager workstation. 3. Access the command prompt on the ProtecTIER Manager workstation: a. Click Start > Run... The Run dialog box opens. 4. In the Open field, type: cmd and click Ok. The command window opens. 5. Browse to the ProtecTIER Manager installation directory on the DVD. To do so: a. At the command prompt, type: D: (where D: is the letter assigned to the CD/DVD drie of the workstation) and press <enter>. b. At the command prompt, list the contents of the DVD. Type: dir and press <enter>. c. Locate the name of the ProtecTIER Manager directory on the DVD. For example: PT_Manager_V d. At the command prompt, change to the ProtecTIER Manager directory. Type: cd <directory name> and press <enter>. For example: cd PT_Manager_V <enter>. e. At the command prompt, change to the Windows directory. Type: cd windows and press <enter>. 96 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

119 f. At the command prompt, type: Install.exe LAX_VM "C:\Program Files\ Jaa60\jre\bin\jaa.exe" and press <enter>, where the path contained within the quotation marks is the same as the path that you noted in step 5 on page 94. The screen-reader-enabled ProtecTIER Manager installation wizard starts. g. Follow the spoken prompts to compete the installation. 6. When the installation completes, proceed as appropriate: If you do not want to enable the Windows High Contrast option or customize the color palette, resume your regular use of ProtecTIER Manager. To change the contrast mode for ProtecTIER Manager, go to Enabling the Windows High Contrast option. To customize the color palette, go to Customizing the color palette on page 102. Enabling the Windows High Contrast option About this task To make it possible for ProtecTIER Manager display in high contrast, you must first enable the Use High Contrast option in Windows. Procedure 1. On the ProtecTIER Manager workstation, go to Windows > Control Panel > Accessibility Options. The Accessibility Options dialog box opens. 2. Select the Display tab. 3. In the High Contrast area of the Display tab, select the Use High Contrast check box, as shown in Figure 14 on page 98: Accessibility for publications and ProtecTIER Manager 97

120 ts Figure 14. Display tab 4. Click Settings. The Settings for High Contrast dialog box displays, as shown in Figure 15 on page 99: 98 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

121 ts Figure 15. Settings for High Contrast By default, the High Contrast Black (large) scheme is selected. 5. Do one of the following: To use the default, High Contrast Black (large), scheme: a. Click Ok to close the Settings for High Contrast dialog box. b. Click Ok to close the Accessibility Options dialog box. After a few moments, the display changes to the new color scheme. c. Go on to Using the Windows high contrast scheme with ProtecTIER Manager. To use a different high contrast scheme: a. Click the arrow to show the list of aailable color schemes. b. Select the high contrast scheme that you want to use. c. Click Ok to close the Settings for High Contrast dialog box. d. Click Ok to close the Accessibility Options dialog box. After a few moments, the display changes to the new color scheme. e. Go on to Using the Windows high contrast scheme with ProtecTIER Manager. Using the Windows high contrast scheme with ProtecTIER Manager About this task Now that you hae changed the contrast scheme in Windows, you must enable the Support system settings option in ProtecTIER Manager. Procedure 1. Launch ProtecTIER Manager: Accessibility for publications and ProtecTIER Manager 99

122 a. Click: Start > All Programs > IBM > ProtecTIER Manager > IBM ProtecTIER Manager. The ProtecTIER Manager window opens, as shown in: Figure 16. ts Figure 16. ProtecTIER Manager window 2. On the toolbar, click: Tools > Preferences. The Preferences dialog box opens with the Appearance tab selected, as shown in Figure 17 on page 101: 100 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

123 ts Figure 17. Preferences dialog box 3. On the Appearance tab, select the Support system settings check box. You are returned to the ProtecTIER Manager window. 4. Exit and restart ProtecTIER Manager so the contrast settings take effect: a. On the ProtecTIER Manager toolbar, click: File > Exit. The ProtecTIER Manager window closes. b. Click: Start > All Programs > IBM > ProtecTIER Manager > IBM ProtecTIER Manager. When the ProtecTIER Manager window opens, the display reflects the contrast change, as shown in: Figure 18. ts Figure 18. Normal contrast ersus high contrast 5. Proceed as appropriate: If you want to change one or more of the colors used in the ProtecTIER Manager display, continue to Customizing the color palette on page 102. If you do not want to customize the color palette, resume your regular use of ProtecTIER Manager. Accessibility for publications and ProtecTIER Manager 101

124 Customizing the color palette About this task Use this procedure to customize the color palette for ProtecTIER Manager to improe isibility in the display, or to suit your personal preferences. Procedure 1. If necessary, start ProtecTIER Manager as described in step 1 on page Open the Preferences dialog box, as described in 2 on page Scroll down (if necessary) to see the entire Color selection list, and then select the color you want to change. The Color selection dialog box opens, with the Swatches tab selected, as shown in Figure 19: ts Figure 19. Color selection, Swatches tab The color that is currently defined for your selection is shown in the Preiew pane. 4. Select a new color from the color palette. You can also specify a new color by using the Hue/Saturation/Brightness (HSB) or Red/Green/Blue (RGB) color models. To do so, click the tab for the model you want to use and enter the required alues. 5. When you hae finished selecting or specifying the new color, click Ok. You are returned to the Appearance tab. 6. To change another color, repeat steps 3 through IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

125 7. When you are finished making changes in the Appearance tab, click Ok. You are returned to the ProtecTIER Manager window. 8. Exit and restart ProtecTIER Manager (as described in step 4 on page 101) so the color palette changes take effect. After you log in to ProtecTIER Manager and add a node, the display reflects your custom color selections. An example of the default color ersus a custom color for Allocable resources, is shown in: Figure 20 ts Figure 20. Default color ersus custom color 9. Proceed as appropriate. Return to the task from which you were sent to these instructions or resume your regular use of ProtecTIER Manager. Accessibility for publications and ProtecTIER Manager 103

126 104 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

127 Notices This information was deeloped for products and serices offered in the U.S.A. IBM may not offer the products, serices, or features discussed in this document in other countries. Consult your local IBM representatie for information on the products and serices currently aailable in your area. Any reference to an IBM product, program, or serice is not intended to state or imply that only that IBM product, program, or serice may be used. Any functionally equialent product, program, or serice that does not infringe any IBM intellectual property right may be used instead. Howeer, it is the user's responsibility to ealuate and erify the operation of any non-ibm product, program, or serice. IBM may hae patents or pending patent applications coering subject matter described in this document. The furnishing of this document does not gie you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drie Armonk, NY U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such proisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATIONS "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are proided for conenience only and do not in any manner sere as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it beliees appropriate without incurring any obligation to you. Any performance data contained herein was determined in a controlled enironment. Therefore, the results obtained in other operating enironments may ary significantly. Some measurements may hae been made on deelopment-leel systems and there is no guarantee that these measurements will be the same on generally aailable systems. Furthermore, some measurement may hae been Copyright IBM Corp

128 estimated through extrapolation. Actual results may ary. Users of this document should erify the applicable data for their specific enironment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly aailable sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objecties only. This information is for planning purposes only. The information herein is subject to change before the products described become aailable. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of indiiduals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. Trademarks The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: AIX DS4000 Enterprise Storage Serer ESCON FICON i5/os iseries IBM ProtecTIER pseries S/390 SereRAID System x System Storage TotalStorage Wake on LAN z/os zseries IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ((R) or (TM)), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or 106 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

129 Electronic emission notices common law trademarks in other countries. A current list of IBM trademarks is aailable on the Web at "Copyright and trademark information" at Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Jaa and all Jaa-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Toralds in the United States, other countries, or both. Other company, product, and serice names may be trademarks or serice marks of others. This section contains the electronic emission notices or statements for the United States and other countries. Federal Communications Commission statement This explains the Federal Communications Commission's (FCC) statement. This equipment has been tested and found to comply with the limits for a Class A digital deice, pursuant to Part 15 of the FCC Rules. These limits are designed to proide reasonable protection against harmful interference when the equipment is operated in a commercial enironment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, might cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense. Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. IBM is not responsible for any radio or teleision interference caused by using other than recommended cables and connectors, or by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could oid the user's authority to operate the equipment. Notices 107

130 This deice complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this deice might not cause harmful interference, and (2) this deice must accept any interference receied, including interference that might cause undesired operation. Industry Canada compliance statement This Class A digital apparatus complies with Canadian ICES-003. Cet appareil numérique de la classe A est conform à la norme NMB-003 du Canada. European Union Electromagnetic Compatibility Directie This product is in conformity with the protection requirements of European Union (EU) Council Directie 2004/108/EC on the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the fitting of non-ibm option cards. Attention: This is an EN Class A product. In a domestic enironment this product might cause radio interference in which case the user might be required to take adequate measures. Responsible Manufacturer: International Business Machines Corp. New Orchard Road Armonk, New York European community contact: IBM Deutschland GmbH IBM Technical Regulations, Department M456 IBM-Allee 1, Ehningen, Germany Australia and New Zealand Class A Statement Attention: This is a Class A product. In a domestic enironment this product might cause radio interference in which case the user might be required to take adequate measures. Germany Electromagnetic compatibility directie Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie zur Elektromagnetischen Verträglichkeit Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 2004/108/EG zur Angleichung der Rechtsorschriften über die elektromagnetische Verträglichkeit in den EU-Mitgliedsstaaten und hält die Grenzwerte der EN Klasse A ein. Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu betreiben. Des Weiteren dürfen auch nur on der IBM empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der 108 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

131 IBM erändert bzw. wenn Erweiterungskomponenten on Fremdherstellern ohne Empfehlung der IBM gesteckt/eingebaut werden. EN Klasse A Geräte müssen mit folgendem Warnhinweis ersehen werden: "Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbereich Funk-Störungen erursachen; in diesem Fall kann om Betreiber erlangt werden, angemessene Mabnahmen zu ergreifen und dafür aufzukommen." Deutschland: Einhaltung des Gesetzes über die elektromagnetische Verträglichkeit on Geräten Dieses Produkt entspricht dem "Gesetz über die elektromagnetische Verträglichkeit on Geräten (EMVG)." Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in der Bundesrepublik Deutschland. Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagnetische Verträglichkeit on Geräten (EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) für Geräte der Klasse A Dieses Gerät ist berechtigt, in übereinstimmung mit dem Deutschen EMVG das EG-Konformitätszeichen - CE - zu führen. Verantwortlich für die Einhaltung der EMV Vorschriften ist der Hersteller: International Business Machines Corp. New Orchard Road Armonk,New York Tel: Der erantwortliche Ansprechpartner des Herstellers in der EU ist: IBM Deutschland GmbH Technical Regulations, Abteilung M456 IBM-Allee 1, Ehningen, Germany Generelle Informationen: Das Gerät erfüllt die Schutzanforderungen nach EN und EN Klasse A. People's Republic of China Class A Electronic Emission statement Notices 109

132 Taiwan Class A compliance statement Taiwan contact information This topic contains the product serice contact information for Taiwan. IBM Taiwan Product Serice Contact Information: IBM Taiwan Corporation 3F, No 7, Song Ren Rd., Taipei Taiwan Tel: f2c00790 Japan Voluntary Control Council for Interference (VCCI) Class A Statement Japan Electronics and Information Technology Industries Association (JEITA) Statement (less than or equal to 20 A per phase) jjieta1 110 IBM System Storage TS7650 ProtecTIER Deduplication Gateway: Introduction and Planning Guide

133 Korean Communications Commission (KCC) Class A Statement Russia Electromagnetic Interference (EMI) Class A Statement rusemi Notices 111