You are on page 1of 204

IBM System Storage TS7600 with ProtecTIER

Users Guide
for Enterprise Edition and Appliance Edition

GC53-1156-03

IBM System Storage TS7600 with ProtecTIER

Users Guide
for Enterprise Edition and Appliance Edition

GC53-1156-03

Note:
Before using this information and the product it supports, be sure to read the information in the Safety and environmental notices and Notices sections of this publication.

Edition notices This edition applies to IBM System Storage TS7600 with ProtecTIER for Enterprise Edition and Appliance Edition [ProtecTIER v2.3] and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces GC53-1156-02 Copyright International Business Machines Corporation 2008, 2009. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
Figures . . . . . . . . . . . . . . . v Tables . . . . . . . . . . . . . . . vii Safety and Environmental notices . . . ix
Safety notices . . . . . . . . . . . . . . ix Environmental notices . . . . . . . . . . . x

Chapter 5. Managing nodes and clusters . . . . . . . . . . . . . . 35


Adding and removing nodes from ProtecTIER Manager . . . . . . . . . . . . . . . 35

Chapter 6. Managing repositories . . . 37


Expanding repositories . . . . Deleting repositories . . . . . Replication policies . . . . . . Setting the replication timeframe Creating a replication policy . . Enabling and disabling a policy Running a policy . . . . . Modifying a policy . . . . . Deleting a policy . . . . . Aborting replication activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 42 43 44 45 46 46 47 47 48

About this document . . . . . . . . . xi


Terminology . . . . . . . . . Who should read this document . . Whats new in this edition . . . . Getting information, help, and service Web sites . . . . . . . . . . Related IBM publications . . . . . How to send your comments . . . . . . . . xi xiii xiii xiii xiv . . . . . xv . . . . . xvi . . . . . . . . . . . . . . . . . . . .

Chapter 1. Introduction . . . . . . . . 1
HyperFactor . . . . . . ProtecTIER Virtual Tape (VT) . Configuration . . . . . . ProtecTIER Manager . . . . Native Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 2 6 6

Chapter 7. Managing the ProtecTIER VT service. . . . . . . . . . . . . . . 49


Setting the ProtecTIER VT host connections . . Configuring node ports for hosts running HP-UX Creating libraries . . . . . . . . . . . Setting the library type . . . . . . . . . Editing library parameters . . . . . . . . Reassigning devices . . . . . . . . . . Setting control path failover . . . . . . . . Managing cartridges . . . . . . . . . . Renaming libraries . . . . . . . . . . . Deleting libraries . . . . . . . . . . . . . . . . . . . . . 49 49 50 57 58 62 66 66 70 70

Chapter 2. Setting up ProtecTIER . . . . 7


Completing the ProtecTIER setup . . . . . Logging in to the server . . . . . . . . Upgrading ProtecTIER on a single node . . . Upgrading ProtecTIER on a two-node cluster . Upgrading the first node . . . . . . . Upgrading the second node . . . . . . Adding replication on a node . . . . . . Routing replication IP traffic (static routes) . . Updating replication IPs on a node . . . . Enabling SNMP compatibility . . . . . . ProtecTIER Replication Network Performance Validation Utility . . . . . . . . . . Changing the system date and time . . . . . . . . . . . . . . . . . 7 . 7 . 9 . 11 . 11 . 12 . 14 . 15 . 17 . 19 . 20 . 24

Chapter 8. Native Replication Management . . . . . . . . . . . . 71 Chapter 9. Monitoring ProtecTIER . . . 77


Monitoring clusters . . . . . . . . . Monitoring the repository . . . . . . Monitoring replication policies and activites Monitoring nodes . . . . . . . . . Monitoring the ProtecTIER VT service . . Monitoring the shelf . . . . . . . Monitoring backups from the Linux shell . . . . . . . . . . . . . . . . . . . . . . 77 80 83 86 87 93 94

Chapter 3. Installing ProtecTIER Manager . . . . . . . . . . . . . . 27


Prerequisites . . . . . . . . . Installing ProtecTIER Manager . . . Uninstalling the ProtecTIER Manager. . . . . . . . . . . . . . 27 . 27 . 30

Chapter 10. Managing and monitoring ProtecTIER through the CLI. . . . . . 97


ptmon . . . . . . . . . . . . . . . . 97 ptcli . . . . . . . . . . . . . . . . 103 ptcli responses . . . . . . . . . . . . 106

Chapter 4. Getting started with ProtecTIER Manager . . . . . . . . . 31


Logging in and out . . . . . . . Enabling replication . . . . . . Saving and printing data . . . . . Refreshing ProtecTIER Manager . . Running operations in the background . . . . . . . . . . . . . . . . . . . . . . . . . 31 31 32 32 33

Chapter 11. Managing users . . . . . 113


Permission levels . . Adding user accounts . . . . . . . . . . . . . . . . . . . 113 . 113

Chapter 12. Troubleshooting . . . . . 117


Copyright IBM Corp. 2008, 2009

iii

Viewing the alerts and events log windows Wizard error messages . . . . . . . Generating a problem report . . . . . Creating a long-term statistics report . . Turning on the WTI power switch outlets . Modifying port attributes . . . . . . Removing and adding cluster members . Changing World Wide Names for a node . Common troubleshooting tasks . . . . Checking and repairing errors . . . . .

. . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

117 118 119 119 119 120 121 123 124 128

Chapter 13. Disaster recovery operations. . . . . . . . . . . . . 133


Assessing cartridge status and syncing with the catalog . . . . . . . . . . . . . . . 136

Adding file systems to fstab and mounting file systems . . . . . . . . . . . . . . Expanding file systems . . . . . . . . . . Creating a partition . . . . . . . . . . Unmounting a file system . . . . . . . . Deactivating the logical volume . . . . . . Creating a physical volume. . . . . . . . Adding the physical volume to a volume group Expanding the logical volume . . . . . . . Reactivating the logical volume . . . . . . Mounting the file system . . . . . . . . Expanding the GFS file system . . . . . .

164 164 165 165 165 165 165 166 166 166 166

Appendix C. RSA connection


Enabling Remote Control . . . . .

. . . . 167
. . . . 170

Appendix A. Recovery procedures


Preparing to reload a node . . . . . . . . Installing the Red Hat Enterprise Linux Advanced Platform operating system . . . . . . . . RAS package installation . . . . . . . . Installing ProtecTIER for use with the TS7650G . Installing ProtecTIER for use with the TS7650 Appliance . . . . . . . . . . . . . DR replacing a two-node system with a single node configuration . . . . . . . . . . Installing Grid Manager . . . . . . . . . Backing up the configuration files . . . . . Analyzing and restoring the Grid Manager . . Restoring the Grid Manager . . . . . .

139
. 139 . 139 . 146 . 146 . 149 . . . . . 152 154 156 157 157

Appendix D. TSSC network IP scheme 171 Accessibility . . . . . . . . . . . . 173 Notices . . . . . . . . . . . . . . 175


Trademarks . . . . . . . . . . . . . Electronic emission notices . . . . . . . . Federal Communications Commission (FCC) statement. . . . . . . . . . . . . Industry Canada compliance statement . . . European Union (EU) Electromagnetic Compatibility Directive . . . . . . . . Peoples Republic of China Class A Electronic Emission statement . . . . . . . . . Taiwan Class A compliance statement . . . Taiwan contact information. . . . . . . Japan VCCI Class A ITE Electronics Emission statement. . . . . . . . . . . . . Korean Class A Electronic Emission statement Power cords . . . . . . . . . . . . . . 176 . 177 . 177 . 178 . 178 . 179 . 179 . 179 . 180 180 . 180

Appendix B. Creating file systems and expanding existing ones . . . . . . 161


Creating file systems . . . . Creating partitions . . . Creating physical volumes . Creating volume groups . . Creating logical volumes . Creating a Global File System Creating mount points . . . . . . . . . . . . . . . . . (GFS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 161 163 163 163 164 164

Index . . . . . . . . . . . . . . . 181

iv

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figures
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. Tape library emulation . . . . . . . One node system . . . . . . . . . Two node system . . . . . . . . . Cluster setup . . . . . . . . . . Starting cluster response . . . . . . Updating cluster response. . . . . . ProtecTIER Manager . . . . . . . Repository meta data storage requirements dialog . . . . . . . . . . . . Repository resources dialog . . . . . View of replication policy . . . . . . Set replication time frame . . . . . . Library type screen . . . . . . . . Tape model screen . . . . . . . . Tape drives screen . . . . . . . . Port assignment screen . . . . . . . Assignment (2) screen . . . . . . . Cartridges screen. . . . . . . . . Slots screen . . . . . . . . . . Set library type dialog . . . . . . . Tape drives screen . . . . . . . . Assignment screen . . . . . . . . Assignment (2) screen . . . . . . . Slots screen . . . . . . . . . . Tape drives screen . . . . . . . . Assignment screen . . . . . . . . Assignment (2) screen . . . . . . . Summary report screen . . . . . . Cartridges screen. . . . . . . . . Cartridges screen. . . . . . . . . Create replication pair . . . . . . . Delete replication pair . . . . . . . View of grid member details via Grids Management mode . . . . . . . . Systems monitoring screen . . . . . Storage resources dialog . . . . . . VT tab . . . . . . . . . . . . Repository monitoring screen . . . . Nominal data size graph . . . . . . Utilization graph . . . . . . . . . Marginal HyperFactor graph . . . . . HyperFactor ratio over time graph . . . Replication policies tab. . . . . . . Replication activities view. . . . . . General tab . . . . . . . . . . Drives tab . . . . . . . . . . . Cartridges tab. . . . . . . . . . Slots tab . . . . . . . . . . . Imports/Exports tab . . . . . . . Shelf view . . . . . . . . . . . ptmon on success response output . . . ptmon on error output . . . . . . . ptmon -repository output . . . . . . ptmon -libs output . . . . . . . . ptmon -libinfo -libid <library id> output ptmon -ncarts -libid <library id> output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 . 3 . 4 . 5 . 15 . 18 . 33 . . . . . . . . . . . . . . . . . . . . . . . . 38 42 44 45 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 69 73 74 55. ptmon -cartsinfo -libid <library id> -from <first cartridge index> -count <number of cartridges> outputf . . . . . . . . ptmon -node_vtl_statistics -hours <hours> output . . . . . . . . . . . . . ptmon -version output . . . . . . . Failed Response for Calling to DriveModels without --libtype . . . . . . . . . Failed Response for Calling to DriveModels without --libtype . . . . . . . . . Successful Response for Configuration Operations . . . . . . . . . . . Successful Response for RepositoryStatistics Successful Response for Libraries . . . . Successful Response for LibraryInfo without Active Drive . . . . . . . . . . . Successful Response for LibraryInfo with Active Drives . . . . . . . . . . Successful Response for NumberofCartridges Successful Response for CartridgeInfo Successful Response for NodeVtlStatistics Successful Response for ServerVersion Successful Response for LibraryTypes Successful Response for DriveModels Successful Response for RaidConfigurations Users Management dialog . . . . . . Add account dialog . . . . . . . . Alerts log . . . . . . . . . . . . Message area. . . . . . . . . . . Port Details screen . . . . . . . . . Node Selection screen. . . . . . . . Node Selection screen. . . . . . . . ProtecTIER VT HyperFactor mode dialog Set trace levels dialog . . . . . . . . Move cartridge dialog . . . . . . . Check and recover dialog . . . . . . Cartridge validation results . . . . . . Repository takeover . . . . . . . . Cartridge status report (in Excel) . . . . Press F12 to select the boot device . . . Select CD as the boot device . . . . . Red Hat Enterprise Linux 5 screen . . . Verify attached disks . . . . . . . . Review end user license agreement . . . End User License Agreement . . . . . Accept the license agreement . . . . . Grid analysis. . . . . . . . . . . Previewing the grid layout . . . . . . Laptop or PC to RSA connection . . . . Local Area Connection Properties . . . . Local Area Connection Properties: Internet Protocol (TCP/IP) . . . . . . . . . Remote Supervisor Adapter II Refresh 1 Welcome window . . . . . . . . . Remote Supervisor Adapter II Refresh 1 window: Remote Control link . . . . . . 101 . 102 . 102 . 106 . 106 . 106 107 . 107 . 107 . 108 108 109 110 110 110 110 111 . 114 . 114 . 117 . 118 . 120 . 122 . 123 125 . 126 . 128 . 130 . 135 . 136 . 138 . 141 . 142 . 143 . 144 . 144 . 145 . 145 . 158 . 160 . 167 . 168 . 168 . 169 . 170

56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. 81. 82. 83. 84. 85. 86. 87. 88. 89. 90. 91. 92. 93. 94. 95. 96. 97. 98. 99.

. 75 . 77 . 78 . 80 . 81 . 82 . 82 . 83 . 83 . 84 . 85 . 88 . 90 . 91 . 92 . 93 . 94 . 98 . 98 . 99 . 99 100 100

Copyright IBM Corp. 2008, 2009

vi

IBM System Storage TS7600 with ProtecTIER: Users Guide

Tables
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. IBM Web sites for help, services, and information . . . . . . . . . . . . xiii Default usernames and passwords . . . . . 31 fsCreate parameters . . . . . . . . . . 40 Cluster member information . . . . . . . 79 Total utilization information . . . . . . . 81 Repository information. . . . . . . . . 82 Port attribute information . . . . . . . . 86 Network interface card information . . . . 87 Virtual robots and tape drive. . . . . . . 88 Drives tab information . . . . . . . . . 90 Cartridges tab information . . . . . . . 91 Slots tab information . . . . . . . . . 92 13. 14. 15. 16. 17. 18. 19. 20. 21. Imports/Exports tab information . . . . . 93 Recent backup session statistics . . . . . . 95 Repository command statistics . . . . . . 98 Statistics on the configured tape drives of a specific library . . . . . . . . . . . 99 Statistics on the number of configured cartridges of a specific library . . . . . . 100 Statistics of the cartridges in a specified range 100 Statistics history on the local host for the last hours . . . . . . . . . . . . . . 101 Grid analysis messages . . . . . . . . 159 TSSC IP address ranges . . . . . . . . 171

Copyright IBM Corp. 2008, 2009

vii

viii

IBM System Storage TS7600 with ProtecTIER: Users Guide

Safety and Environmental notices


This section contains information about safety notices that are used in this guide and environmental notices for this product.

Safety notices
Observe 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 severity 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, G2299054 manual. The sections that follow define each type of safety notice and give 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 voltage on metal parts of the system or the devices that attach to the system. It is the responsibility of the customer to ensure that the outlet is correctly wired and grounded to prevent 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 develop because of some unsafe practice. A caution notice can be accompanied by one of several 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 Services (for example, Class I, Class II, and so forth). A hazardous condition due to mechanical movement in or around the product.

Copyright IBM Corp. 2008, 2009

ix

If the symbol is...

It means... This part or unit is heavy but has a weight smaller than 18 kg (39.7 lb). Use care when lifting, removing, or installing this part or unit. (C008)

Sample caution notices follow: Caution The battery is a lithium ion battery. To avoid possible explosion, do not burn. Exchange only with the IBM-approved 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 1-800-426-4333. Have the IBM part number for the battery unit available when you call. (C007) Caution The system contains circuit cards, assemblies, or both that contain lead solder. To avoid the release of lead (Pb) into the environment, do not burn. Discard the circuit card as instructed by local regulations. (C014) Caution When removing the Modular Refrigeration Unit (MRU), immediately remove any oil residue from the MRU support shelf, floor, and any other area to prevent injuries because of slips or falls. Do not use refrigerant lines or connectors to lift, move, or remove the MRU. Use handholds as instructed by service procedures. (C016) Caution Do not connect an IBM control unit directly to a public optical network. The customer must use an additional connectivity device between an IBM control unit optical adapter (that is, fibre, ESCON, FICON) and an external public network . Use a device such as a patch panel, a router, or a switch. You do not need an additional connectivity device for optical fibre connectivity that does not pass through a public network.

Environmental notices
The environmental notices that apply to this product are provided in the Environmental Notices and User Guide, Z125-5823-xx manual. A copy of this manual is located on the publications CD.

IBM System Storage TS7600 with ProtecTIER: Users Guide

About this document


This document provides information for using the IBM System Storage TS7600 with ProtecTIER for the Appliance Edition & Enterprise Edition [ProtecTIER v2.3].

Terminology
IBM offers two virtualization solutions: TS7650 When used alone, this term signifies IBMs family of virtualization solutions that operate on the ProtecTIER platform. TS7650 Appliance or appliance These are terms for IBMs self-contained virtualization solution from the TS7650 family that includes a disk storage repository. The TS7650 Appliance consists of the following: Server The 3958 AP1 server is based on an IBM System x3850 M2 Type 7233. When used as a server in the TS7650 Appliance, its machine type and model are 3958 AP1. Use this machine type and model for service purposes. System console The system console is a TS3000 System Console (TSSC). This document uses the terms system console and TSSC interchangeably. Disk controller The disk controller is an IBM System Storage DS4700 Express. When used as a disk controller in the TS7650 Appliance, its machine type and model are 1814 70H. Use this machine type and model for service purposes. Disk expansion module The disk expansion module is an IBM System Storage DS4000 EXP810 Storage Expansion Unit. When used as a disk expansion module in the TS7650 Appliance, its machine type and model are 1812 81H. Use this machine type and model for service purposes. TS7650G or Gateway These are terms for IBMs virtualization solution from the TS7650 family that does not include a disk storage repository, allowing the customer to choose from a variety of storage options. The TS7650G consists of the following: Server There are two types of server used in the gateway: 3958 DD3 This is a newer, higher performance server available in March 2009. This server is based on the IBM System x3850 M2 Type 7233. When used as a server in the TS7650G, its machine type and model are 3958 DD3. Use this machine type and model for service purposes. 3958 DD1 This is the original server available in August 2008. This server is based on the IBM System x3850 M2 Type 7141.
Copyright IBM Corp. 2008, 2009

xi

When used as a server in the TS7650G, its machine type and model are 3958 DD1. Use this machine type and model for service 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 IBM disk controller is an IBM System Storage DS4700 Express. When used as a disk controller in the TS7650G, its machine type and model are 1814 70H. Use this machine type and model for service purposes. Disk expansion module The IBM disk expansion module is an IBM System Storage DS4000 EXP810 Storage Expansion Unit. When used as a disk expansion module in the TS7650G, its machine type and model are 1812 81H. Use this machine type and model for service purposes. 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 environment. Each ProtecTIER environment has at least one ProtecTIER server. The ProtecTIER server that is a part of the replication grid has two dedicated replication ports, Eth3 and Eth4 are use for replication. Replication ports are connected to the customers 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 receive logical objects through replication. A replication grid defines a set of ProtecTIER repositories and actions between them and is configured using the Grid Manager. The Grid Manager is a software component that is installed on a ProtecTIER server or a dedicated host. The Grid Manager should be able to recognize all the members of the entire network the Grid Manager handles on both replication subnets. The Grid Manager is deployed separately from the ProtecTIER Manager on the customers ProtecTIER server. The Grid Manager manages the configuration of multiple replication grids in an organization. An agent on every node in each ProtecTIER server interacts with the server 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 (e.g. VTL cartridges) from a source repository to be replicated to a target repository.

xii

IBM System Storage TS7600 with ProtecTIER: Users Guide

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 (virtual tape library) cartridges within a ProtecTIER repository.

visibility switching The automated process that transfers the visibility of a VTL cartridge from its master to its replica and vice versa. The visibility switching process is triggered by moving 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 librarys I/E slot. To move 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 intended for storage administrators, system programmers, and performance capacity analysts.

Whats new in this edition


Major changes in and additions to this document since the last edition include the following: v ProtecTIER replication function. v Introduction of instructions for configuring ProtecTIER for replication. v Introduction of Grid Manager installation instructions. v Introduction of new ProtecTIER Replication Network Performance Validation Utility, used to test maximal replication performance between two future PT repositories.

Getting information, help, and service


If you need help, service, technical assistance, or just want more information about IBM products, you will find a wide variety of sources available from IBM to assist you. Available services, 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 services and find the latest technical information. For more information refer to Table 1.
Table 1. IBM Web sites for help, services, and information Description IBM home page Directory of worldwide contacts Web address (URL) www.ibm.com http://www.ibm.com/planetwide

About this document

xiii

Table 1. IBM Web sites for help, services, and information (continued) Description Support for IBM System Storage and TotalStorage products Web address (URL) http://www.ibm.com/storage/support Note: Go to this site for information about the TS7650 and do the following: 1. Select Tape systems from the Product family list 2. Select TS7650 with ProtecTIER from the Product list

Help and service


You can call 1 (800) IBM SERV (1-800-426-7378) for help and service if you are in the U.S. or Canada. You must choose the software or hardware option when calling for assistance. Choose the software option if you are uncertain if the problem involves TS7650 software or TS7650 hardware. Choose the hardware option only if you are certain the problem solely involves the TS7650 hardware. When calling IBM for service regarding the TS7650, follow these guidelines for the software and hardware options: Software option Identify the TS7650 as your product and supply your customer number as proof of purchase. The customer number is a 7-digit numeric (0000000 to 9999999) assigned by IBM when the PID is purchased and should be located on the customer information worksheet or on the invoice from the software purchase. Hardware option Provide 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). Note: Cache modules and cache controllers are supported separately within the TS7650G. If the problem is known to be in the IBM attached storage component, select the hardware option and enter the appropriate Machine Type and S/N (serial number) for the component. If the attached storage is not IBM branded, contact the appropriate service provider for the component. For the TS7650 Appliance, all components inside the frame are supported under the 3958 AP1 MTM.

Web sites
The most up-to-date information about your product, including documentation and the most recent downloads, can be found at the following Web sites: v The translated publications for this product are included with the product. These documents and product specification sheets are also available from the following Web site: www.ibm.com/storage/support/ v You can order publications through the IBM Publications Ordering System at the following Web site:

xiv

IBM System Storage TS7600 with ProtecTIER: Users Guide

www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss/ v Access installation and technical support information via the Web at: www.ibm.com/support v The IBM Web site for Independent Software Vendor (ISV) support is: www.ibm.com/servers/storage/tape/resource-library.html v The IBM System Storage TS7600 Interoperability Matrix Web site can be found at: www.ibm.com/storage/support/ v For the latest information about SAN switches and directors, go to the following Web site: www.ibm.com/servers/storage/san v For the latest information about IBM xSeries products, services, and support, go to the following Web site: www.ibm.com/eserver/xseries v 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: www.ibm.com/servers/storage/disk/ds4000/interop-matrix.html v For product firmware and software downloads, as well as associated driver code, go to the following Web site: www.ibm.com/storage/support/ v For accessibility information, go to the following Web site: www.ibm.com/able/product_accessibility/index.html v For the latest information about product recycling programs, go to the following Web site: www.ibm.com/ibm/environment/products/prp.shtml

Related IBM publications


The following documents provide information about the IBM System Storage TS7600 with ProtecTIER gateway and appliance server(s) and recommended additional hardware components.

IBM System Storage TS7600 with ProtecTIER publications


v IBM System Storage TS7600 with ProtecTIER Introduction and Planning Guide for the TS7650G (DD1 & DD3), IBM form number GC53-1152-03 v IBM System Storage TS7600 with ProtecTIER Introduction and Planning Guide for the TS7650 (3958 AP1-Appliance), IBM form number GC53-1193-00 v Statement of Limited Warranty

TS7650 (3958 AP1) publications


The following publications provide additional documentation about the appliance server: v IBM System x3850 M2 (Type 7233), System x3950 M2 (Type 7233) Installation Guide, IBM part number 40M2377 v IBM System x3850 M2 (Type 7233, 7144), System x3950 M2 (Type 7233) Users Guide, IBM part number 42C8237

About this document

xv

v IBM System x3850 M2 (Type 7233), System x3950 M2 (Type 7233) Problem Determination and Service Guide, IBM part number 44R5214

TS7650G Server (x3958 DD1/DD3) publications


The following publications provide additional documentation about the TS7650G Server: v IBM System x3850 M2 (Type 7141, 7144), System x3950 M2 (Type 7141) Users Guide v IBM Safety Information The server might have features that are not described in the documentation that you received with the server. The documentation might be updated occasionally to include information about those features, or technical updates might be available to provide additional information that is not included in the server documentation. These updates are available from the IBM Web site. Complete the following steps to check for updated documentation and technical updates: 1. In a Web browser, navigate to http://www.ibm.com/support/publications/us/ library/. 2. 3. 4. 5. 6. 7. Click Information Centers > Systems > xSeries>. Click Product information > Servers > xSeries. From the Product family list, select System x3850. From the Type list, select System 7141. Click Go. On the Software and device drivers page, click the Documentation link.

8. On the Support for System x3850 page, click the link for the document you want to view.

Remote Supervisor Adapter (RSA) publications


The following publications provide additional documentation about the RSA: v Remote Supervisor Adapter II Slimline and Remote Supervisor Adapter II Installation Guide v Remote Supervisor Adapter II Slimline and Remote Supervisor Adapter II Users Guide

How to send your comments


Your feedback is important in helping to provide the most accurate and highest quality information. To submit any comments about this book or any other IBM System Storage TS7600 with ProtecTIER documentation: v Send your comments by e-mail to starpubs@us.ibm.com. Be sure to include the following information: Exact publication title and version Publication form number (for example, GC53-1196-03) Page, table, or illustration numbers that you are commenting on with a detailed description of any information that should be changed

xvi

IBM System Storage TS7600 with ProtecTIER: Users Guide

Chapter 1. Introduction
ProtecTIER is a disk-based data storage system. It uses data de-duplication technology to store data to disk arrays. The ProtecTIER VT service emulates traditional automated tape libraries. Before you begin using ProtecTIER and following the procedures described in this document, be sure you have completed the planning, preparation, and installation tasks described in the IBM System Storage TS7600 with ProtecTIER Introduction and Planning Guide, IBM publication number: GC53-1153, and installed IBM ProtecTIER Manager.

HyperFactor
ProtecTIER is the first virtual tape product to contain patented data factoring technology that IBM calls HyperFactor. This technology detects recurring data in multiple backups. The common data is merged into a single instance store, saving disk space needed to store multiple backups without sacrificing performance or the availability of backups for restore. HyperFactor is a breakthrough on several fronts: v Scales up to 1024 TB v The algorithm used to find the common data between backups does not affect the backup performance of the virtual tape engine v Data integrity is not compromised, not even statistically v Merged data is stored in a format that preserves restore performance HyperFactor saves space by taking advantage of the fact that only a very small percentage of data actually changes from backup to backup. Incremental backups include all files whose modification dates have changed since the last full or incremental backup; and full backups backup all data, changed or not. The amount of space saved is a function of many factors, but mostly of the backup policies and retention periods and the variance of the data between them. The more full backups retained on ProtecTIER, and the more intervening incremental backups, the more space that will be saved overall.

ProtecTIER Virtual Tape (VT)


The ProtecTIER Virtual Tape (VT) service emulates traditional tape libraries. By emulating tape libraries, ProtecTIER VT enables you to transition to disk backup without having to replace your entire backup environment. Your existing backup application can access virtual robots to move virtual cartridges between virtual slots and drives. The backup application perceives that the data is being stored on cartridges while ProtecTIER actually stores data on a deduplicated disk repository on the storage fabric.

Copyright IBM Corp. 2008, 2009

Figure 1. Tape library emulation

Configuration
ProtecTIER systems can be set up with either one node or two nodes arranged in a cluster. Each cluster operates independently, but you can manage them all from ProtecTIER Manager. A one node system uses one server to transfer data from the backup server to the storage fabric, as illustrated in the following figure:

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 2. One node system

A two node system uses two servers in an active-active cluster and enables you to build a more sophisticated system, as illustrated in the following figure:

Chapter 1. Introduction

Figure 3. Two node system

Using a two node system provides the following benefits: v Higher-Availability clustered configuration available to provide hardware redundancy in the event of a node failure. v Increased Performance provided that there are sufficient disk resources, the two servers can share the backup load and increase ProtecTIERs performance.

IBM System Storage TS7600 with ProtecTIER: Users Guide

The following diagram illustrates the details of the ProtecTIER cluster setup:

Figure 4. Cluster setup

Each node connects through front-end fibre channel ports to the backup server, and through back-end fibre channel ports to disk arrays. The network interface cards enable the nodes to connect to each other and to the ProtecTIER Manager workstation. Eth0 connects to the ProtecTIER Manager workstation. Eth1 and Eth2 are used for the Cluster Internal Network.

Chapter 1. Introduction

ProtecTIER Manager
The ProtecTIER Manager application can be installed on one or more workstations, enabling you to monitor the status of nodes and clusters in your ProtecTIER system, along with the accompanying repositories and services. ProtecTIER Manager is used to initially configure your ProtecTIER system, and can be used to change the configuration of the system.

Native Replication
Native Replication lets you replicate between repositories connected to a WAN network using TCP/IP protocol. Replication enables you to set rules (depending on your required replication needs) for replicating data objects across ProtecTIER repositories. The ProtecTIER repositories can be different in size, as well as physical layout. And since ProtecTIER deduplicates data before storing it, only the changes of the data are transferred to the remote site. These rules for replicating data objects are defined in replication policies on a repository. A replication grid is a logical set of repositories that can replicate from one to another. The Grid Manager is a server that remotely manages the grids configuration (for example, grid creation/deletion, repository membership in the grid, etc.). In most cases, the Grid Manager will reside on one of the ProtecTIER nodes.

IBM System Storage TS7600 with ProtecTIER: Users Guide

Chapter 2. Setting up ProtecTIER


This section provides instructions for completing the ProtecTIER system setup for use with the TS7650 Appliance and the TS7650G.

Completing the ProtecTIER setup


Use the ptconfig utility to complete the ProtecTIER configuration process that was started in manufacturing. Note: Throughout this chapter the terms server and node are used interchangeably, depending upon the task being performed.

Prerequisites
Before executing ptconfig, verify that the following tasks have been completed: v Cabling and physical connections (including those to the customers local area network (LAN) using assigned IP addresses) are complete. v You have collected the following server information: External IP address External, fully-qualified, host name (hostname.domain.com) External gateway address External network subnet mask Note: The cluster name and host name are case-sensitive. Be aware of the use of upper- and lower-case characters when gathering the information and when entering it into the system.

Logging in to the server


Follow the steps below to log in to the ProtecTIER server: 1. If you are in a standalone configuration, connect the USB keyboard and graphics-capable monitor to the server. 2. Verify that the server is running: v If it is, go on to step 4. v If it is not running: power it on now, wait for the boot cycle to complete, and then go on to step 4. 3. If you are in a clustered configuration, verify that Servers A and B are running: v If they are, go on to step 4. v If they are not running: power them both on now, wait for the boot cycle to complete, and then go on to step 4. 4. At the localhost login: prompt, log in with the ID root and the password admin. 5. Go on to Configuring the server.

Configuring the server


Once you have finished logging in to the server, you are now ready to configure the server.

Copyright IBM Corp. 2008, 2009

If you have a code-level update package, execute the ptconfig that is resident on the server first, then apply the update from the CD. Perform the steps below on the single server in a standalone configuration, or on Server A and Server B in a clustered configuration. To configure the server: 1. At the servers command prompt, change to the /opt/dtc/install directory. To do so, enter the following command: cd /opt/dtc/install <enter> 2. Change the servers IP address, netmask, default gateway, and host name from the values that were set in manufacturing, to the values specific to the customers environment. To do so: a. Enter the following command: ./ptconfig -updateNetwork <enter> The following status messages display:
Starting Cluster, please wait Starting cluster [ Done ] Cluster Started

b. If asked if you would like to stop the vtfd service, type: yes <Enter>. The following status message displays as the system initiates shutdown:
Stopping VTFD [/] The shutdown process may take a few minutes to complete.

When shutdown completes, the following status message displays:


Stopping VTFD [ Done ]

c. You are then prompted, one at a time, to enter the values listed below. At each prompt, type the new value and then press <Enter>: v v v v Customer Network IP address Customer Network netmask Customer Network default gateway Customer Network hostname (This is the servers fully-qualified hostname. For example: hostname.domain.com)

Note: The values that were assigned to the server during manufacturing appear in brackets after each prompt. For example: Customer Network netmask:
[255.255.255.0]

After you enter the hostname, the system automatically starts the network configuration process. The following status messages display:
Configuring network [ Done ] Updated network configuration successfully update updateNetwork ended successfully

The system automatically restarts the vtfd service, and you are returned to the command prompt. 3. Change the system name from the one assigned during manufacturing to one specific to the customers environment. In a clustered configuration, this command only needs to be run from one of the nodes as it affects the shared name of the system. To do so: a. Enter the following command:
./ptconfig -updateSystemName <Enter>

The following status messages display:

IBM System Storage TS7600 with ProtecTIER: Users Guide

Starting Cluster, please wait Starting Cluster [ Done ] Cluster Started

b. When prompted, type the new system name of the server and press <Enter>. Note: The system name that was assigned to the server in manufacturing appears in brackets after the prompt. For example: [PORTLAND]. After you enter the system name, the system automatically starts the Update System Name process. The following status message displays:
Change system name [ Done ] Updated system name successfully update updateSystemName ended successfully

You are returned to the command prompt. 4. If you are in a standalone configuration, go on to Chapter 3, Installing ProtecTIER Manager, on page 27. 5. If you are in a clustered configuration, repeat the steps in this section on Server B, then go on to Chapter 3, Installing ProtecTIER Manager, on page 27. Creating the repository on the node results in a functional one-node ProtecTIER cluster system. If you are using a one-node system, create a library on the one node. (For more information, see Creating libraries on page 50.) If you are using a two-node system, upgrade the system to a two-node cluster. Then create one or more libraries on the nodes of the two-node cluster.

Upgrading ProtecTIER on a single node


The following procedure describes how to upgrade ProtecTIER on a single node. A repository must be configured on the node before upgrading ProtecTIER to version 2.3. To update ProtecTIER on a node, stop the ProtecTIER service on that node before you begin the following procedure. 1. Log in as root and stop vtfd, using the following steps: a. Connect or verify a USB keyboard and display are connected to the TS7650 or the TS7650G. b. If the server is not already powered on, power it on and allow the boot cycle to complete. c. When the localhost login: prompt appears, login as root and type the password: admin. d. From the command line, enter in the following command to monitor the status of the vtfd service: service vtfd status <Enter> e. If the vtfd does not report as stopped, enter the following command to stop the process: service vtfd stop <Enter> The process will discontinue and return you to a command prompt. 2. Mount and copy the code to the installation directory, using the following steps: a. Insert the IBM System Storage ProtecTIER Enterprise Edition V2.3 CD and wait for the CD to stop blinking. b. Create the /mnt/cdrom directory by typing the following command:
Chapter 2. Setting up ProtecTIER

mkdir /mnt/cdrom

<Enter>

Note: If the /mnt/cdrom directory already exists, the following message will be displayed:
mkdir: cannot create directory '/mnt/cdrom': File exists

If this message appears, ignore it and proceed to the next step. c. Mount the CD-ROM drive:
mount /dev/cdrom /mnt/cdrom <Enter>

The following output is displayed: mount: block device /dev/cdrom is write-protected. mounting read-only d. Type the following command to change the current directory to the local installation directory:
cd /mnt/cdrom

e. From the CD, locate the following tar file, where <filename> indicates the version number and date: v List the files on the CD from the command line: ls <Enter> v Locate the .tar file and copy it to the /install directory on the hard drive. Type the following command to copy the file:
cp <filename>.tar /install <Enter>

f. Access the directory to which you copied the tar file (for example, type cd /install). g. Type the following command to extract the installation files in the /install directory:
tar -xvf <tar filename>.tar <Enter>

The <filename> directory is created. h. Type the following command to change to the <tar filename> directory. Perform the rest of the installation from this directory:
cd /install/<filename> <Enter>

Example: <filename>=PT_Linux_V2.3.0.0.x86_64 i. Type the following command to unmount the CD-ROM drive:
umount /dev/cdrom <Enter>

j. Type the following command to eject the ProtecTIER installation CD from the CD-ROM drive:
eject /dev/cdrom

k. Type the following command:


./autorun <Enter>

l. Enter y if you are prompted to stop the vtfd service. m. The autorun utility will install the ProtecTIER application. The following message is displayed at the end of the installation:
The system will now reboot!\

Note: After the reboot, the vtfd will be ready only after the service vtfd status command reports that vtfd is running, not that the service is not finished running yet. Press <Enter> at the prompt to reboot the system. The following message is displayed:
After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue...

10

IBM System Storage TS7600 with ProtecTIER: Users Guide

Upgrading ProtecTIER on a two-node cluster


The following procedure describes how to upgrade ProtecTIER on a two-node cluster. In a two-node cluster, each node must be upgraded separately. A repository must be configured on a node before upgrading ProtecTIER to version 2.3. If the TS7650 or the TS7650G is not already powered on, power it on on both nodes and stop the ProtecTIER service on both nodes before beginning the upgrade.

Upgrading the first node


To upgrade the first node: 1. Log in as root and stop the vtfd using the following steps: a. Connect or verify a USB keyboard and display are connected to Server B (the second server). b. When the localhost login: prompt appears, login as root and type the password: admin. c. Monitor the vtfd service on Node B by typing the following command:
service vtfd status <Enter>

d. If the vtfd does not report as stopped, enter the following command to stop the process:
service vtfd stop <Enter>

The process will discontinue and return you to a command prompt. e. Connect or verify a USB keyboard and display are connected to Server A (the first server). f. When the localhost login: prompt appears, login as root and type the password: admin. 2. Mount and copy the code to the installation directory, using the following steps: a. Insert the IBM System Storage ProtecTIER Enterprise Edition V2.3 CD and wait for the CD to stop blinking. b. Create the /mnt/cdrom directory by typing the following command:
mkdir /mnt/cdrom <Enter>

Note: If the /mnt/cdrom directory already exists, the following message will be displayed:
mkdir: cannot create directory '/mnt/cdrom': File exists

If this message appears, ignore it and proceed to the next step. c. Mount the CD-ROM drive:
mount /dev/cdrom /mnt/cdrom <Enter>

The following output is displayed:


mount: block device /dev/cdrom is write-protected. mounting read-only

d. Type the following command to change the current directory to the local installation directory:
cd /mnt/cdrom

e. From the CD, locate the following tar file, where <filename> indicates the version number and date:
Chapter 2. Setting up ProtecTIER

11

v List the files on the CD from the command line: ls <Enter> v Locate the .tar file and copy it to the /install directory on the hard drive. Type the following command to copy the file:
cp <filename>.tar /install <Enter>

f. Access the directory to which you copied the tar file (for example, type cd /install). g. Type the following command to extract the installation files in the /install directory:
tar -xvf <tar filename>.tar <Enter>

The <filename> directory is created. h. Type the following command to change to the < tar filename> directory. Perform the rest of the installation from this directory:
cd /install/<filename> <Enter>

Example: <filename>=PT_Linux_V2.3.0.0.x86_64 i. Type the following command to unmount the CD-ROM drive:
umount /dev/cdrom <Enter>

j. Type the following command to eject the ProtecTIER installation CD from the CD-ROM drive:
eject /dev/cdrom

k. Type the following command:


./autorun <Enter>

l. Enter y if you are prompted to stop the vtfd service. m. The autorun utility will install the ProtecTIER application. The following message is displayed at the end of the installation:
The system will now reboot!\

Note: After the reboot, the vtfd will be ready only after the service vtfd status command reports that vtfd is running, not that the service is not finished running yet. Press <Enter> at the prompt to reboot the system. The following message is displayed:
After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue...

Upgrading the second node


To upgrade the second node: 1. Log in as root and stop the vtfd using the following steps: a. Connect or verify a USB keyboard and display are connected to Server A (the first server). b. When the localhost login: prompt appears, login as root and type the password: admin. c. From the command line, enter in the following command to stop vtfd:
service vtfd stop <Enter>

d. Connect or verify a USB keyboard and display are connected to Server B (the second server). e. When the localhost login: prompt appears, login as root and type the password: admin. 2. Mount and copy the code to the installation directory, using the following steps:

12

IBM System Storage TS7600 with ProtecTIER: Users Guide

a. Insert the IBM System Storage ProtecTIER Enterprise Edition V2.3 CD and wait for the CD to stop blinking. b. Create the /mnt/cdrom directory by typing the following command:
mkdir /mnt/cdrom <Enter>

Note: If the /mnt/cdrom directory already exists, the following message will be displayed:
mkdir: cannot create directory '/mnt/cdrom': File exists

If this message appears, ignore it and proceed to the next step. c. Mount the CD-ROM drive:
mount /dev/cdrom /mnt/cdrom <Enter>

The following output is displayed:


mount: block device /dev/cdrom is write-protected. mounting read-only

d. Type the following command to change the current directory to the local installation directory:
cd /mnt/cdrom

e. From the CD, locate the following tar file, where <filename> indicates the version number and date: v List the files on the CD from the command line: ls <Enter> v Locate the .tar file and copy it to the /install directory on the hard drive. Type the following command to copy the file:
cp <filename>.tar /install <Enter>

f. Access the directory to which you copied the tar file (for example, type cd /install). g. Type the following command to extract the installation files in the /install directory:
tar -xvf <tar filename>.tar <Enter>

The <filename> directory is created. h. Type the following command to change to the < tar filename> directory. Perform the rest of the installation from this directory:
cd /install/<filename> <Enter>

Example: <filename>=PT_Linux_V2.3.0.0.x86_64 i. Type the following command to unmount the CD-ROM drive:
umount /dev/cdrom <Enter>

j. Type the following command to eject the ProtecTIER installation CD from the CD-ROM drive:
eject /dev/cdrom

Attention: Run the autorun command only after the service on Server A has completed its startup (after the reboot). k. Type the following command:
./autorun <Enter>

l. Enter y if you are prompted to stop the vtfd service m. The autorun utility will install the ProtecTIER application. The following message is displayed at the end of the installation:
The system will now reboot!\

Press <Enter> at the prompt to reboot the system. The following message is displayed:
Chapter 2. Setting up ProtecTIER

13

After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue... <Enter>

Adding replication on a node


To add replication on a node that is part of a two-node cluster, the following procedure must be run on each node, one after the other. Note: This procedure is applicable to both the TS7650 Appliance and TS7650G servers. If the server is not already powered on, power it on on both nodes and stop the vtfd service on both nodes. To add replication on a node: 1. Connect or verify a USB keyboard and display are connected to the server. 2. When the localhost login: prompt appears, login as root and type the password: admin. 3. Set the user to ptadmin by typing the command su - ptadmin (the default password is ptadmin). 4. Change the directories to the /opt/dtc/install directory. From the command line, run the following command:
cd /opt/dtc/install

5. Run the following command to change the Ethernet port assignments of the server. You should see eth3 and eth4 identified as the Ethernet ports to be used for replication:
./ptconfig -addReplication <enter>

6. At the prompt, type yes <enter> to continue. 7. When prompted, enter the IP address, netmask, and hostname for the first replication port. 8. When prompted, enter the IP address, netmask, and hostname for the second replication port. The vtfd service is restarted and the procedure ends. 9. If you are working with a two-node cluster , repeat the entire procedure on the second node.

14

IBM System Storage TS7600 with ProtecTIER: Users Guide

Example
[root@kovna install]# ./ptconfig -addReplication Starting Cluster, please wait Starting cluster [ Done ] Cluster Started Would you like to stop the VTFD service on both nodes? (yes|no) yes Stopping VTFD locally [ Done ] Stopping VTFD remotely [ Done ] Checking configuration [ Done ] ---------------------------------------Found the following available Network Interface(s): eth3 eth4 These Interface(s) are going to be configured for Replication Do you wish to continue? (yes|no) yes Modifying configuration Verifying configuration Please provide the following information: ----------------------------------------Replication Port 1, IP Address: 192.168.170.2 Replication Port 1, Netmask: 255.255.255.0 Replication Port 1, Hostname: replicationNode2_1 Replication Port 2, IP Address: 192.168.171.2 Replication Port 2, Netmask: 255.255.255.0 Replication Port 2, Hostname: replicationNode2_2 Configuring Replication Port 1 Configuring Replication Port 2 Saving configuration Starting VTFD locally Starting VTFD remotely AddReplication ended successfully [ Done ] [ Done ]

[ Done ] [ Done ] [ Done ] [ Done ] [ Done ]

Figure 5. Starting cluster response

Routing replication IP traffic (static routes)


Static routes are a simple and effective way of instructing the ProtecTIER IP stack how to route replication IP traffic destined for specific sub-nets. This is necessary whenever traffic to any specific sub-net is required to be sent through a different gateway and possibly a different network-interface than the default-gateway definition would otherwise dictate. Static routes are comprised of two parameters: v the subnet that should be specially handled (defined by its network-address and network-mask) v the gateway through which IP traffic to this network should be sent (defined by its IP address) The gateway specified (sometimes referred to as the next hop) must reside on a network directly connected to one of the network-interfaces of ProtecTIER, and the traffic will be sent to it through this interface. Note: If static routing is needed/used, it must be implemented on all nodes at all sites. To define the static routes used for replication:
Chapter 2. Setting up ProtecTIER

15

1. At the command prompt, enter the command: ./ptconfig -staticRoutes <enter> The message below displays: Gathering System information [ Done ] The auto-detected system information displays. For example:
ID 1 2 Target Network Address 10.11.194.0 10.11.196.0 Target Netmask 255.255.255.0 255.255.255.0 Local Gateway Address 168.159.151.111 168.159.151.110

Followed by the Available Options prompt: Available Options: ================== (a)dd a new record (e)dit a record (d)elete a record (c)ommit changes (q)uit Please Choose (a,e,d,c,q): 2. Type: a <enter> You are prompted to enter information for the first destination (target) server and the local network. 3. At each prompt, type the requested information and then press <enter>: Please provide the following information: Target Network Address: (for example: 10.11.194.0) Target Network Netmask: (for example: 255.255.255.0) Local Gateway Address: (for example: 10.11.195.1) A summary displays:
ID 1 Target Network Address 10.11.194.0 Target Netmask 255.255.255.0 Local Gateway Address 10.11.195.1

Note: The addresses in the summary above are examples. Actual values will vary. The Available Options prompt displays a second time: Available Options: ================== (a)dd a new record (e)dit a record (d)elete a record (c)ommit changes (q)uit Please Choose (a,e,d,c,q): 4. Type: a <enter>

16

IBM System Storage TS7600 with ProtecTIER: Users Guide

You are prompted for the information for the second destination (target) server and the local network. 5. At each prompt, type the requested information and then press <enter>: Please provide the following information: Target Network Address: (for example: 10.11.196.0) Target Network Netmask: (for example: 255.255.255.0) Local Gateway Address: (for example: 10.11.197.1) An updated summary displays:
ID 1 2 Target Network Address 10.11.194.0 10.11.196.0 Target Netmask 255.255.255.0 255.255.255.0 Local Gateway Address 10.11.195.1 10.11.197.1

Note: The addresses in the summary above are examples. Actual values will vary. For reference, write actual values from the summary screen in the blank spaces below:
ID 1 2 Target Network Address Target Netmask Local Gateway Address

The Available Options prompt displays a third time: Available Options: ================== (a)dd a new record (e)dit a record (d)elete a record (c)ommit changes (q)uit Please Choose (a,e,d,c,q): 6. Type: q <enter> The message below displays: Would you like to commit the changes performed to the routing table now? (yes|no) 7. Type: yes <enter> The Successfully committed changes! message displays, and you are returned to the command prompt.

Updating replication IPs on a node


If you want to update the replication IPs on a node and the node is part of a two-node cluster, the following procedure must be run on each node. Note: This procedure is applicable to both the TS7650 Appliance and TS7650G servers.

Chapter 2. Setting up ProtecTIER

17

Before updating the replication IPs, check to see if the static routing needs to be updated as well. To update replication IPs on a node: 1. If the server is not already powered on, power it on on both nodes and stop the vtfd service on both nodes. 2. Connect or verify a USB keyboard and display are connected to the server. 3. When the localhost login: prompt appears, login as root and type the password: admin. 4. Set the user to ptadmin by typing the command su - ptadmin (the default password is ptadmin). 5. Change the directories to the /opt/dtc/install directory. From the command line, run the following command:
cd /opt/dtc/install

6. Run the following command to change the Ethernet port assignments of the DD1:
./ptconfig -updateReplicationIp <enter>

7. At the prompt, type yes <enter> to continue. 8. When prompted, enter the IP address, netmask, and hostname for the first replication port. 9. When prompted, enter the IP address, netmask, and hostname for the second replication port. The vtfd service is restarted and the procedure ends.

Example
[root@kovna install]# ./ptconfig -updateReplicationIp Starting Cluster, please wait Starting cluster [ Done ] Cluster Started Would you like to stop the VTFD service on both nodes? (yes|no) yes Stopping VTFD locally Stopping VTFD remotely [ Done ] [ Done ]

Verifying configuration [ Done ] Please provide the following information: ----------------------------------------Replication Port 1, IP Address [192.168.170.2]: 10.0.13.56 Replication Port 1, Netmask [255.255.255.0]: 255.255.255.192 Replication Port 1, Hostname [replicationNode2_1]: Replication Port 2, IP Address [192.168.171.2]: 10.1.14.1 Replication Port 2, Netmask [255.255.255.0]: 255.255.255.224 Replication Port 2, Hostname [replicationNode2_2]: Configuring Replication Port 1 [ Done ] Configuring Replication Port 2 Saving configuration Starting VTFD locally Starting VTFD remotely UpdateReplicationIp ended successfully [ Done ] [ Done ] [ Done ] [ Done ]

Figure 6. Updating cluster response

18

IBM System Storage TS7600 with ProtecTIER: Users Guide

Enabling SNMP compatibility


ProtecTIER responds to SNMP, implementing MIB-2 and generating the appropriate traps. The server responds to SNMP discovery and queries, and to the standard MIB requests.

Enabling ProtecTIER SNMP support


When the server is installed at the user site, the IP address of the SNMP management station, i.e. the TotalStorage Service Console (TSSC), must be made available to the ProtecTIER code. To enable SNMP support: 1. Edit the configuration file. From the command line, use the vi editor:
vi /etc/snmp/snmpd.conf trapsink localhost <Enter>

2. Scroll down the list to the bottom of the file and locate this line: 3. Use the arrow key on the keyboard to place the cursor under the letter l in the word localhost. Press the Delete key until localhost is removed. Press the a key (this is for add or insert mode). Enter the IP address with the TSSC SNMP management station (Service Console) IP address. Example: Remove `localhost and insert 172.31.1.1. 172.31.1.1 is the standard TSSC IP address. After the IP address has been entered, press the <Esc> key, then <shift+colon (:)> keys and type: wq! (write-quit) <Enter>. This will save the file.

IBM MIB definition file


IBM supplies an MIB definition file called DILIGENT-MIB.txt that can be found in the/usr/share/snmp/mibs directory. This file describes each of the supported traps and should be imported to the SNMP application used at the customer site.

SNMP compatibility
ProtecTIER implements SNMP as follows: MIB-2 implementation In the MIB-2 System Group, the following fields are implemented: sysDescr, sysObjectID, sysUpTime, sysContact, sysName, sysLocation, sysServices. All other parts of the MIB-2 responds in such a way that management tools understand that they are not implemented. Traps The traps generated are: coldStart, warmStart, authenticationFailure, operatorInterventionRequired (proprietary), recoverableErrorNotification (proprietary). If authentication of a user fails more than five times in a row, an SNMP authenticationFailure trap is generated. Startup consistency checks ProtecTIER checks its persistent data on startup, using a Power On Self

Chapter 2. Setting up ProtecTIER

19

Test (POST) procedure, in order to verify that the application can run. Initialization files are checked for consistency. Resource allocation specifically memory - is checked. Errors encountered may be recoverable or unrecoverable. Recoverable errors A recoverable error is an error from which the ProtecTIER server can recover without losing the users data. Recoverable errors are logged in the ProtecTIER logs and generate an SNMP warning notification trap. Unrecoverable errors An unrecoverable error is an error that prevents the platform from booting correctly, an unrecoverable consistency check error during ProtecTIER startup, or any other error that could cause or has caused loss of user data. The server is left in offline state (booted, responding to TCP/IP SNMP enquiries, and responding to console, telnet and modem logins). Unrecoverable errors are logged in the ProtecTIER logs and generate an SNMP error trap. Restarting on error If ProtecTIER detects an error at runtime, it recovers by rebooting and restarting the ProtecTIER process. If multiple restarts are detected within a short time period, ProtecTIER declares an unrecoverable error. Alerts The server generates SNMP traps to higher level management frameworks. In particular, whenever the system enters the online state, it generates a coldStart trap if the platform has rebooted, and a warmStart trap if the system only returned to online state from the offline state. A recoverable error generates a recoverableErrorNotification trap. An unrecoverable error generates an operatorInterventionRequired trap.

ProtecTIER Replication Network Performance Validation Utility


The pt_net_perf_util utilitys objective is to test maximal replication performance between two future PT repositories by emulating the network usage patterns of PTs Native Replication component. This utility will not predict replication performance, but it may discover performance bottlenecks. The requirements of this utility are as follows: v Red Hat Enterprise Linux 5.2 v Standard external utilities expected to be in the current path: ping, netstat, getopt, echo. The pt_net_perf_util utility and the iperf and nuttcp tools it uses are installed as part of the ProtecTIER software installation. To test the replication performance, use one of the following tools: v iperf 2.0.4
/usr/local/bin/iperf

v nuttcp 6.1.2
/usr/local/bin/nuttcp-6.1.2

Note: Use iperf or nuttcp for the procedures below. The utilities cannot be used together.

20

IBM System Storage TS7600 with ProtecTIER: Users Guide

This utility has two modes of operation, client and server. The server has to be started before the client. Before running the utility, shut down all other programs on both the client and server ProtecTIER systems. The client is the ProtecTIER system that transmits the test data and the server is the ProtecTIER system that receives the data (also known as the target server). Based on the data sent by the client and received by the server, the script outputs key network parameter values 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 server since the flow of data will be to that server from the client. However, it is also important to also test the reverse direction to measure the bandwidth performance during disaster recovery failback. Network bandwidth is not always the same in both directions. In the following procedure, the goal is to test network performance between two machines on a WAN, server1 and server2. Each test will run for five minutes. Since there are five tests, the process will take a total of 25 minutes. 1. Start the server mode of the utility on server1 by entering the following commands on the command line:
cd /opt/dtc/app/sbin ./pt_net_perf_util -s

Note: The above command uses the iperf tool. To use nuttcp tool instead, add -n to the command. Enter one of the following series of commands to use nuttcp:
cd /opt/dtc/app/sbin ./pt_net_perf_util -sn or cd /opt/dtc/app/sbin ./pt_net_perf_util -s -n

2. Start the client mode of the utility on server2 by entering the following command on the command line: ./pt_net_perf_util -c server1 -t 300 Note: This step uses the iperf external utility. To use nuttcp instead, add -n to the command. Enter the following command to use nuttcp:
./pt_net_perf_util -c server1 -t 300 -n

3. The utility will automatically perform the tests in sequence. The client output (server2 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 9.5.53.33 (9.5.53.33) 56(84) bytes of data. --- 9.5.53.33 ping statistics --5 packets transmitted, 5 received, 0% packet loss, time 4001ms rtt min/avg/max/mdev = 0.257/0.406/0.484/0.079 ms *** Throughput - Default TCP [ 3] 0.0- 5.0 sec 56.6 MBytes 94.8 Mbits/sec

*** Throughput - 1 TCP stream(s), 1MB send buffer [ 3] 0.0- 5.0 sec 57.0 MBytes 95.0 Mbits/sec *** Throughput - 16 TCP stream(s), 1MB send buffer
Chapter 2. Setting up ProtecTIER

21

[SUM]

0.0- 5.8 sec

65.0 MBytes

94.3 Mbits/sec

*** Throughput - 127 TCP stream(s), 1MB send buffer [SUM] 0.0-11.3 sec 127 MBytes 94.1 Mbits/sec Number of TCP segments sent: 230536 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 five foreground tests (Tests 1-5 below), and one background test (Test 6 below). The example outputs below are from the client side, with the script using iperf (not nuttcp) in tests 2-5. Each of the first five tests below ran for 30 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 10.0.13.194 (10.0.13.194) 56(84) bytes of data. --- 10.0.13.194 ping statistics --120 packets transmitted, 120 received, 0% packet loss, time 119060ms rtt min/avg/max/mdev = 57.403/78.491/104.451/9.872 ms

Interpreting the results: v The average round-trip-time (rtt) was 78.4ms and there was 0% packet loss. v The latency in WAN topologies may vary, but should never exceed 200ms. Contact your network administrator if latency reports more than 200ms, as it may significantly decrease replication throughput. v Higher latency values will cause a major deterioration in replication throughput. v Packet loss should be 0%. Any other value implicates 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] 0.0-120.1 sec 2.41 GBytes 173 Mbits/sec

Interpreting the results: v The test ran for 120.1 seconds, transferred 2.41 GB, with an average 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 send buffer. Example result:
[ *** Throughput - 1 TCP stream(s), 1MB send buffer 3] 0.0-120.0 sec 2.51 GBytes 180 Mbits/sec

22

IBM System Storage TS7600 with ProtecTIER: Users Guide

Interpreting the results: v The test ran for 120.0 seconds, transferred 2.51 GBs, with an average throughput of 180 Mbits/sec. v There may be an improvement here on high-latency links. Test 4: Throughput - 16 streams, 1MB send buffer Example result:
*** Throughput - 16 TCP stream(s), 1MB send buffer [SUM] 0.0-121.4 sec 5.91 GBytes 418 Mbits/sec

Interpreting the results: v The test ran for 121.4 seconds, transferred 5.91 GB, with an average throughput of 418 Mbits/sec. v The extra streams yielded higher utilization of the connection. v The Mbits/sec reported in this test is the maximum replication performance your system will achieve if your backup environment is using up to 2-3 cartridges in parallel. Test 5: Throughput - 127 streams, 1MB send buffer Example result:
*** Throughput - 127 TCP stream(s), 1MB send buffer [SUM] 0.0-126.1 sec 8.08 GBytes 550 Mbits/sec

Interpreting the results: v The test ran for 126.1 seconds, transferred 8.08 GB, with an average throughput of 550 Mbits/sec. v TCP takes a while to reach its maximal throughput. Longer testing times, 300 seconds or more, will produce more accurate results. v The throughput value given by this test is the potential physical replication throughput for this system. It is directly affected by the available bandwidth, latency, packet loss and retransmission rate. v The Mbits/sec reported in this test is the maximum replication performance your system may achieve. If this number islower than anticipated, contact your network administrator. Test 6: TCP Retransmissions vs. Total TCP segments sent Example result:
Number of TCP segments sent: 1619061 Number of TCP retransmissions detected: 201038 (12%)

Interpreting the results: v A total of 1619061 TCP segments were sent during the five tests, out of which, 201038 were lost and retransmitted. v 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 overflowed router) or by the TCP layer itself (e.g. retransmission due to packet reordering). v Segment loss can be caused by each of the network layers.

Chapter 2. Setting up ProtecTIER

23

v TCP retransmission larger than 2% may cause performance degradation and unstable network connectivity. Contact your network administrator to resolve this issue and reduce it to approximately 0%. You may want to run these tests again to test the reverse throughput in the network. To run the tests in reverse, change server1 to the client and server2 to the server and repeat the procedures.

Changing the system date and time


The following procedure describes the steps required for changing the systems date, time and time zone. In a two-node cluster, each node must be changed separately. After configuring the ProtecTIER server, you can change the systems date, time and time zone. Perform the procedure below on both nodes in the cluster, starting with Node 1 (the bottom server). 1. If you are not already connected to Node 1, plug a USB keyboard and monitor into the back of the server. 2. Log in to the server with the username root and password admin. 3. Enter each of the commands listed below to shut down the services currently running on the server: service vtfd stop <enter> service ptcluster stop <enter> service ntpd stop <enter> Disconnect the keyboard and monitor from Node 1 and connect them to Node 2 (the top server). Repeat steps 2and 3 on Node 2. Disconnect the keyboard and monitor from Node 2 and reconnect them to Node 1. Change the directory to locate the time zone you wish to use by typing the command:
cd /usr/share/zoneinfo <Enter>

4. 5. 6. 7.

Example: US/Eastern a. Display the list of countries. Enter the command: ls <enter> b. Change to the directory of the desired country. Enter the command: cd [country] <enter> For example: cd america <enter> c. From the country directory, display the list of cities. Enter the command: ls <enter> d. From the list of cities, find the city that is closest to the time zone in which you are located, and write the name of the city on the blank line below: _____________________________________ 8. Set the local time zone on Node 1 using one of the formats (Continent/City or GMT/EST standard time zones), below: Continent/City format Enter the commands: mv /etc/localtime /etc/localtime.ORIG <enter>

24

IBM System Storage TS7600 with ProtecTIER: Users Guide

ln -sf /usr/share/zoneinfo/[continent]/[city] /etc/localtime <enter> For example: ln -sf /usr/share/zoneinfo/america/phoenix /etc/localtime <enter> OR GMT/EST standard time zones format Enter the command: ln -sf /usr/share/zoneinfo/[standard time zone]/etc/localtime <enter> For example: ln -sf /usr/share/zoneinfo/GMT /etc/localtime <enter> 9. Set the time zone field to the chosen time zone. Enter the command: vi /etc/sysconfig/clock <enter> Note: Use the Insert and Delete keys to alter the default location. The contents of the time zone file display. For example: if you specified america/phoenix, the time zone file appears as follows: ZONE=America/Phoenix UTC=false ARC=false 10. Save the changes you made to the time zone file. Enter the command: (Esc key) wq! <enter> Note: To execute the above command, you will press the Esc key, then type wq!, and then press <enter>. 11. You may need to set the time explicitly. To do this, run the command:
date MMDDhhmm

where: MM is the two-digit month of the year DD is the two-digit day of the month hh is the two-digit hour of the day in a 24-hour format (00 - 23) mm is the two-digit minutes after the hour For example, 1:45 pm on September 1, would be entered as: 09011345. 12. Synchronize the servers hardware clock by running the command:
hwclock --systohc service ntpd start <Enter> <Enter>

13. Restart the ntp service on Node 1. Enter the command: As the ntpd service restarts, status messages similar to the ones shown below, display: [root@Austin America]# hwclock --systohc [root@Austin America]# service ntpd start ntpd: Synchronizing with time server: [FAILED] Starting ntpd: [ OK ] Note: The [FAILED] message above may display if the customer is not using an external time server. If this is the case, and the ntpd service returns a status of [OK], ignore the failure and proceed to the next step.

Chapter 2. Setting up ProtecTIER

25

14. Disconnect the keyboard and monitor from Node 1 and reconnect them to Node 2. 15. If necessary, log in to Node 2 with the username root and password admin. 16. Run steps 8 on page 24 through 11 on page 25 on Node 2. 17. Synchronize the exact time from Node 1 by running the command:
rdate -s internal_node1

18. Synchronize the servers hardware clock by running the command:


hwclock --systohc

19. Restart the ntp service on Node 2:


service ntpd start

As the ntpd service restarts, status messages similar to the ones shown below, display: [root@Austin America]# hwclock --systohc [root@Austin America]# service ntpd start ntpd: Synchronizing with time server: [FAILED] Starting ntpd: [ OK ] Note: The [FAILED] message above may display if the customer is not using an external time server. If this is the case, and the ntpd service returns a status of [OK], ignore the failure and proceed to the next step. 20. Run the following commands to view the updated time:
date <Enter> ntpq -p

21. Complete the services startup on Node 1 (this will fence Node 2 which should restart with the correct time): service ptcluster start <enter> service vtfd start <enter> Note: Starting the cman service will initiate fencing. This causes Node 2 to reboot. However, you can continue starting the services on Node 1 while Node 2 is rebooting. When Node 2 reboots during fencing, the time on Node 2 synchronizes with the time on Node 1. 22. When both nodes have finished rebooting, use PT Manager to verify that fencing completed successfully and both nodes are online. To do so: a. On the PT Manager workstation or TSSC, open PT Manager. b. Confirm that both nodes display as Online. If one (or both) nodes displays as offline, contact your next level of support.

26

IBM System Storage TS7600 with ProtecTIER: Users Guide

Chapter 3. Installing ProtecTIER Manager


The ProtecTIER system is managed using ProtecTIER Manager. It is recommended that you install ProtecTIER Manager on one or more workstations, and not directly on the ProtecTIER servers. ProtecTIER Manager enables you to: v Configure ProtecTIER for use with the TS7650 Appliance and TS7650G v Monitor the status of nodes and clusters v Manage file systems, repositories, and services v Change the system configuration v Manage Native Replication activities using the Grid Manager

Prerequisites
The ProtecTIER Manager workstation must meet the following prerequisites in order to install and run ProtecTIER Manager effectively: v One of the following operating systems: Windows 32 bit (2003/XP) Linux Red Hat 32/64 bit (Red Hat Enterprise 4 or 5) v At least 1.2 GB of available disk space v At least 256 MB or RAM v The workstation can access the ProtecTIER service nodes IP address (ports 3501 and 3503 are open on the firewall). In addition, it is recommended that the monitor for ProtecTIER Manager be configured to the following settings: v Resolution of 1024 x 768 pixels or higher (this is the minimum resolution supported, however, 1280 x 1024 is recommended). v 24 bit color or higher Note: If you are planning to run ProtecTIER Manager on a UNIX system, configure your graphics card and X windows system. This is done either manually or using the Xconfigurator utility. For instructions, refer to the appropriate Linux documentation.

Installing ProtecTIER Manager


The ProtecTIER Manager installer is provided on your IBM System Storage ProtecTIER Manager v2.3 CD. Different ProtecTIER Manager installers are used for Windows and Linux. Make sure that the installer you are using is correct for the operating system running on your workstation. v If you are installing ProtecTIER Manager on a workstation running Windows, see Installing on Windows on page 28. v If you are installing ProtecTIER Manager on a workstation running Linux, see Installing on Linux on page 29.

Copyright IBM Corp. 2008, 2009

27

If you are installing ProtecTIER Manager on a workstation on which an older version of ProtecTIER Manager is already installed, uninstall the older version first. For more information, see Uninstalling the ProtecTIER Manager on page 30.

Installing on Windows
Perform the following steps to install ProtecTIER Manager on Windows. To install ProtecTIER Manager on Windows: 1. Insert the IBM System Storage ProtecTIER Manager v2.3 CD into the CD-ROM drive of the designated ProtecTIER Manager workstation. v If the ProtecTIER Manager autorun launches and starts the installation, go on to step 2. v If the ProtecTIER Manager autorun process does not launch automatically, do the following: a. On the Windows task bar, click: Start > Run. The Run dialog box opens. b. In the Open box, type: D: (where D: is the servers CD-ROM drive). c. Click OK. The contents of the IBM System Storage ProtecTIER Manager v2.3 CD display. d. From the list of files, locate the ProtecTIER Manager for Windows installation file and double-click the file to start the installation. 2. Read the Introduction screen, and then click Next. 3. Read and accept the license agreement provided, and click Next. The Choose Install Folder screen is displayed. 4. Specify the folder where the ProtecTIER Manager program files will be installed, and click Next. The Choose Shortcut Folder screen is displayed. 5. Select the location where the program icons will be created: v In a new Program Group - Creates a new program group in the Program list of the Start menu. v In an existing Program Group - Adds the shortcut to an existing program group in the Program list of the Start menu. v In the Start Menu v On the Desktop v In the Quick Launch Bar v Other - Enables you to enter a path location for the shortcut, or to browse for a location by clicking Choose. v Dont create icons - No shortcuts are created. Note: When relevant, you can select Create Icons for All Users to create a shortcut in the defined location for all user accounts on the workstation. 6. Click Next. The Pre-Installation Summary screen displays the Install and Shortcut folder locations and the disk space information of the target for installation. 7. Review the Summary screen, and click Install to start the installation. The Installing ProtecTIER Manager screen is displayed. 8. When the installation is complete and ProtecTIER Manager has been successfully installed, click Done.

28

IBM System Storage TS7600 with ProtecTIER: Users Guide

The Install Complete screen is displayed. The ProtecTIER Installation wizard closes. 9. Go to Adding nodes on page 35.

Installing on Linux
Perform the following steps to install ProtecTIER Manager on Linux. To install ProtecTIER Manager on Linux: 1. Insert the IBM System Storage ProtecTIER Manager v2.3 CD into the CD-ROM drive of the designated ProtecTIER Manager workstation. 2. Run the ProtecTIER Manager installer: Note: This assumes the workstation has a Linux graphical interface which is required for ProtecTIER Manager. a. From the Linux Desktop, select and open the CD drive icon. b. Select and open the folder for your Linux version: Linux for version 64 or Linux32 for version 32. c. When the folder opens, drag the InstallLinuxXX.bin file from the folder to the Desktop. (XX=either 32 or 64, depending on the Linux folder you selected.) d. Close the open windows. e. Right-click on an open area of the Desktop, and from the menu options displayed, select Open Terminal. f. At the Terminal command prompt, change to the Desktop directory using the following command (Note: Desktop is case sensitive. Type it using a capital D.):
cd Desktop <Enter>

g. From the Desktop directory in the Terminal window, run the ProtecTIER Manager installer:
./InstallLinuxXX.bin <Enter>

(XX= either 32 or 64, as noted above) If the message: Permission Denied displays, enter the following commands:
chmod +x InstallLinuxXX.bin <Enter> ./InstallLinuxXX.bin <Enter)

The IBM ProtecTIER Manager wizard Introduction screen is displayed. 3. Click Next. Two separate Software License Agreement screens display. 4. Read the terms for each license agreement, select I accept both the IBM and non-IBM terms of the License Agreement and click Next. The Choose Install Folder screen is displayed. 5. Enter the path to the location where the ProtecTIER Manager program files will be installed. Click Choose to browse for a location. Note: Click Restore Default Folder to revert to the default installation path. 6. Click Next. The Choose Link Folder screen is displayed. 7. Select the location where the program links will be created: v In your Home folder Creates the links in the directory where the users files are typically stored. For example: /home/bill.

Chapter 3. Installing ProtecTIER Manager

29

v Other Creates the links in the default location (/opt/IBM/PTManager). To specify a different location, click Choose and select a directory on the workstations hard drive. 8. 9. v Dont create links No links are created. Click Next. The Pre-Installation Summary screen is displayed. Click Install. The Installing ProtecTIER Manager screen is displayed and ProtecTIER Manager is installed on your computer. When the installation is complete, the Install Complete screen is displayed. Click Done. The ProtecTIER Manager wizard closes. When the command prompt returns in the Terminal window, type exit to close the window. Go to Adding nodes on page 35.

10. 11.

Uninstalling the ProtecTIER Manager


Perform the following steps to uninstall the ProtecTIER Manager: 1. From the ProtecTIER Manager directory, run the ProtecTIER Manager uninstaller. The Uninstall ProtecTIER Manager wizard Introduction screen is displayed. 2. Click Uninstall. The Uninstalling screen is displayed and ProtecTIER Manager is removed from your computer. The Uninstall Complete screen is displayed. 3. Click Done. The Uninstall ProtecTIER Manager wizard closes.

30

IBM System Storage TS7600 with ProtecTIER: Users Guide

Chapter 4. Getting started with ProtecTIER Manager


After ProtecTIER Manager has been installed, familiarize yourself with various common tasks that apply throughout ProtecTIER Manager.

Logging in and out


ProtecTIER Manager has default user accounts corresponding to three user permission levels: Administrator, Operator, and Monitor. (For more information, see Permission levels on page 113.) The default username and password for each of these accounts are as follows:
Table 2. Default usernames and passwords Permission Level Administrator Operator Monitor Default Username ptadmin ptoper ptuser Default Password ptadmin ptoper ptuser

Log in to each ProtecTIER cluster you want to manage using ProtecTIER Manager. 1. Click the Login button. The Login dialog is displayed. 2. Enter your username and password. 3. Click Ok. The Login dialog closes and you are logged into ProtecTIER Manager. It is recommended that you change or replace these default user accounts. (For more information, see Chapter 11, Managing users, on page 113.) Note: Only one Administrator can be logged into a ProtecTIER cluster at a time. It is, therefore, recommended that you log out at the end of each session by clicking the Logout button. If you log in with Administrator level permission while another Administrator is already logged in, a message box is displayed with the following message:
Administrator is already logged in from host <host name>, at IP address: <IP address>. Would you like to login anyway?

Click Yes to force the other Administrator to logout.

Enabling replication
Perform the following procedure to enable replication on systems that are being upgraded from v2.x to v2.3. By default, replication is enabled on new repositories created with ProtecTIER v2.3. Replication is disabled on repositories upgraded from previous versions. When you enable replication, you must assign files systems, set the estimated factoring ratio, MD raid configuration, and disk size. The procedure allocates

Copyright IBM Corp. 2008, 2009

31

metadata for replication and then you can add file systems to the repository as needed. If more storage is required, you can select additional file systems (if they exist) to add to the metadata. Enabling replication on the TS7650 Appliance should not require any additional metadata space, as the required metadata has already been allocated during the v2.2 repository creation. Enabling replication on the TS7650G may require additional metadata, pending the actual metadata deployment on the specific repository. Note: Before you begin, make sure that the code has been upgraded to v2.3 and that replication has been added during the ProtecTIER configuration process. To enable replication: 1. From the Systems management view, select Replication > Enable replication. The Enable replication wizard welcome screen is displayed. 2. Click Next. The Properties dialog is displayed. 3. Select the Estimated factoring ratio, the MD raid configuration, and the Disk size (in GB) of the metadata disks. Note: The size of the repository cannot be changed when enabling replication. 4. Click Next. The Repository resources dialog displays the total amount of metadata and user data (in GB) allocated for the repository. 5. If more storage is required, click Advanced. The Repository resources window is displayed with a list of available file systems (if they exist). 6. Select what file systems will be used for metadata or user data. Click Ok, the resources window closes. 7. Click Finish. The summary report is displayed and replication is enabled on ProtecTIER Manager.

Saving and printing data


ProtecTIER Manager data in many of the informational windows and panes can be saved or printed. Select Options in the upper right-hand corner of a window, if the option appears. The Save and Print options appear. Select Save or Print to save the information or print it using the standard saving or printing procedures for your operating system.

Refreshing ProtecTIER Manager


Many windows, screens, and panes of ProtecTIER Manager automatically refresh to display the most current information. Some, however, must be refreshed manually. In addition, because you can set up multiple ProtecTIER Manager workstations on the same system, changes can be made on another workstation that are not automatically reflected on your workstation. It is, therefore, recommended that you periodically refresh the Navigation pane and View pane of ProtecTIER Manager.

32

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 7. ProtecTIER Manager

Select the Refresh navigation pane button to refresh the Navigation pane. Select Refresh current view button to refresh the View pane.

Running operations in the background


You can use the same instance of ProtecTIER Manager to work with multiple ProtecTIER systems while a specific ProtecTIER Manager operation runs in the background. You cannot, however, run multiple operations in the same ProtecTIER system. For instance, if you are running a Delete library operation, the wizard will prompt you to wait while the system goes offline and performs the required operation. That system will be busy until it completes, thereby not allowing further administration of other operations. By clicking Run in background, control is returned to the user. If additional systems are configured in ProtecTIER Manager, those systems are accessible and can be worked on, even while the required operation is running.

Chapter 4. Getting started with ProtecTIER Manager

33

34

IBM System Storage TS7600 with ProtecTIER: Users Guide

Chapter 5. Managing nodes and clusters


The ProtecTIER system supports both one-node systems and two-node active-active clusters. Using two nodes in a cluster enables higher throughput and provides higher-availability in the event of node failure.

Adding and removing nodes from ProtecTIER Manager


Note: This section provides instructions for adding and removing nodes when using the TS7650G. Adding a node registers the nodes IP address and port number with the instance of ProtecTIER Manager at your workstation. Similarly, removing a node removes the nodes registration from ProtecTIER Manager at that workstation.

Adding nodes
To add a node to ProtecTIER 1. Run the ProtecTIER Manager application: v For a Windows based ProtecTIER Manager workstation, run the ProtecTIER Manager application: Click Start > Programs > IBM > ProtecTIER Manager 2.3.x > IBM ProtecTIER Manager. v For a Linux based ProtecTIER Manager workstation, click the icon for ProtecTIER Manager on the Desktop or from the location of the shortcut that you selected during the installation. The ProtecTIER Manager screen is displayed. 2. Click the Add node button. The Add node dialog box is displayed, prompting you for the IP address and Port number of the node that you want to add. 3. Enter the IP address of the node and click Ok. The node is displayed in the Nodes pane and the Login button is displayed in the View pane. Note: Do not change the port number of the node unless directed to do so by IBM Support. 4. Click Login. You are prompted for your username and password. 5. Enter your username and password and click Ok. ProtecTIER Manager displays the information for that node. If the node has a repository, the nodes cluster is displayed in the Systems tab of the Navigation pane. If that cluster already contains a second node, the second node is also displayed in the Nodes pane. Note: For more information about repositories, see Chapter 6, Managing repositories, on page 37.

Copyright IBM Corp. 2008, 2009

35

Adding node subnetworks


In addition to adding individual nodes to ProtecTIER Manager, you can add addresses for subnetworks to which nodes are connected. When ProtecTIER Manager restarts, it automatically detects all nodes on the added subnetworks of the TCP/IP network. 1. Select Tools > Preferences from the toolbar. A confirmation message box is displayed. 2. Click Yes. The Preferences dialog box is displayed. 3. For each subnetwork you want to add, click a Sub network checkbox and enter the subnetwork address in the corresponding field. 4. Click Ok. The Preferences dialog box closes and the subnetwork address is added to the ProtecTIER Manager. When you restart the ProtecTIER Manager, all nodes on the defined subnetwork addresses are automatically added to the ProtecTIER Manager.

Removing nodes
Removing a node stops the instance of ProtecTIER Manager at your workstation from registering the node and being able to manage it. The node itself, and the cluster with which the node is associated, is unaffected by removing a node in this way. Note: If you remove a node that is associated with a two-node cluster, the second node will also be removed. Perform the following steps to remove a node: 1. In the Node pane, select the node that you want to remove. 2. Click the Remove node button. A confirmation message box is displayed. 3. Click Yes. The node is removed.

36

IBM System Storage TS7600 with ProtecTIER: Users Guide

Chapter 6. Managing repositories


This chapter describes how to use ProtecTIER Manager to manage repositories on a ProtecTIER node. Each ProtecTIER cluster has one repository on which data is stored. In systems enabled for two-node clusters, a repository for common use is a prerequisite for adding a second cluster member. Note: If you have installed the IBM ProtecTIER Appliance Edition software (TS7650), IBM ProtecTIER software that is not used with a gateway configuration, the repository comes preconfigured. Use ProtecTIER Manager for the following tasks: v To configure the virtual libraries on the ProtecTIER server v To connect the user host servers to the ProtecTIER server using the provided FC cards on the Enterprise Controllers v To define Replication policies

Expanding repositories
Complete the tasks in this topic to increase the capacity of a repository. Attention: This section provides instructions for increasing the capacity of a repository when using the TS7650G. After the repository is created, the ProtecTIER system enables you to increase the capacity of the repository. Much like creating the repository, expanding the repository requires the guidance of IBM Support and use of a wizard for planning repository expansions. You might need to expand the repository if: v Your factoring ratio is higher than originally expected and you are running out of meta data space v Your repository needs have expanded beyond the original growth projections and you are running out of user data space

Planning an expansion
In addition to guidance from IBM Support, run the Plan repository increase wizard to determine the optimum repository size and meta data file system arrangement for your expanded repository. To plan a repository expansion: 1. Choose Repository > Increase capacity planning. The Increase capacity planning window opens. 2. In the Repository size field, select the total physical size, in TB, for the repository. Note: If you are expanding the repository only to increase the amount of meta data space, increase the estimated factoring ratio value, but leave the repository physical size value unchanged.
Copyright IBM Corp. 2008, 2009

37

3. In the Estimated factoring ratio field, enter the updated factoring ratio estimate for the repository. 4. In the MD Raid configuration field, select a configuration option from the drop-down list. 5. In the Disk size field, select the physical disk size, in GB, from the drop-down list. 6. Click Ok. The Increase capacity planning dialog closes and the Repository meta data storage requirements window is displayed listing the minimum meta data file system expansion options that are suitable for your expansion needs.

Figure 8. Repository meta data storage requirements dialog

7. Click Options to print or save as a .csv file the information in the Repository meta data storage requirements dialog using the standard procedures for your operating system. 8. Click Plan again to go back to the Increase capacity planning window and change the configuration options, or click Ok. The Repository meta data storage requirements dialog closes. The information from the Repository meta data storage dialog indicates whether you need to create more file systems and/or expand the existing file systems for the increased repository.

38

IBM System Storage TS7600 with ProtecTIER: Users Guide

Using fsCreate to create file systems


The fsCreate tool can be used to automatically create files systems for repositories. Note: You only need to create the set of file systems once. Even if you later delete the repository, you can recreate the repository using the existing file systems. To use the fsCreate tool: 1. Log into a ProtecTIER node server. Open a Secured Shell (SSH) session to the node and log in using the user ID: root and password: admin. 2. Type the following command:
cd /opt/dtc/app/sbin

3. To display the list of file systems that are already a part of the repository, type the command:
./fsCreate -r

Example
[root@nodeA sbin]# ./fsCreate -r [INFO] [09/02/17-16:18:36] Repository file systems are: [INFO] [09/02/17-16:18:36] /dev/mapper/vg0-lv_vg0 /mnt/vg0-lv_vg0 [INFO] [09/02/17-16:18:36] /dev/mapper/vg1-lv_vg1 /mnt/vg1-lv_vg1 [INFO] [09/02/17-16:18:36] /dev/mapper/vg2-lv_vg2 /mnt/vg2-lv_vg2

4. To display the list of available new multipath devices, type the command:
./fsCreate -u

Example
[root@nodeA ~]# /opt/dtc/app/sbin/fsCreate -u [INFO] [09/02/17-16:35:24] New devices are: [INFO] [09/02/17-16:35:24] /dev/mapper/mpath7 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath6 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath12 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath5 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath11 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath4 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath10 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath3

5. To create file systems on new available multipath devices, register them to /etc/fstab and mount them, type the command:
./fsCreate -e

If you are creating file systems for a two-node cluster, stop the cluster services on the second node during the file system creation to avoid any possibility of corrupting meta data on the repositorys management file system. Type the following commands to stop service on the second node:
service vtfd stop service ptcluster stop

6. Once the file systems are created, start the services on the node. Register the new file systems to /etc/fstab, create the mount points and mount them by typing the command:
./fsCreate -t

7. To verify, display the GFS file systems that are not part of the repository by typing the command:
Chapter 6. Managing repositories

39

./fsCreate - g

Example
[root@nodeA ~]# /opt/dtc/app/sbin/fsCreate -g [INFO] [09/02/17-16:35:13] Non-repository file systems are: [INFO] [09/02/17-16:35:13] /dev/mapper/vg0-lv_vg0 /mnt/vg0-lv_vg0 [INFO] [09/02/17-16:35:13] /dev/mapper/vg1-lv_vg1 /mnt/vg1-lv_vg1 [INFO] [09/02/17-16:35:13] /dev/mapper/vg2-lv_vg2 /mnt/vg2-lv_vg2 [INFO] [09/02/17-16:35:13] /dev/mapper/vg3-lv_vg3 /mnt/vg3-lv_vg3

fsCreate parameters
Use the following syntax and parameters to perform additional functions for expanding the physical capacity of a repository. Syntax:
fsCreate Table 3. fsCreate parameters Parameter -n Description Return Code (rc=0) Return Code (rc=1)

Create GFS file All file systems built. Error encountered systems for all mpath building file systems or detected physical devices during first-time installation. volumes created from mpath devices. Create GFS file systems for new mpath devices during capacity upgrade. Create mount points and register GFS file systems to /etc/fstab. All new file systems built. Error encountered building file systems or detected physical volumes created from mpath devices. Error encountered creating and registering mount points to /etc/fstab or detected physical volumes created from mpath devices. Failed to determine status of an existing file system or detected physical volumes created from mpath devices. Detected physical volumes created from mpath devices. Failed to determine status of an existing file system or detected physical volumes created from mpath devices.

-e

-t

All mount points created and registered to /etc/fstab.

-r

Display all repository Call completed GFS file systems. without error.

-u

Display unused devices. Display all non-repository GFS file systems.

Call completed without error. Call completed without error.

-g

40

IBM System Storage TS7600 with ProtecTIER: Users Guide

Expanding the repository


Expand the repository using the information generated during the repository expansion planning process. Note: Before running the Increase capacity wizard, it is recommended that you bring down the vtfd service on one of the cluster members to reduce the operations downtime. To expand the repository: 1. In the Repositories pane, select the repository that you want to expand. 2. Select Repository > Increase capacity. The Increase capacity wizard Welcome screen is displayed. 3. Click Next. The Repository size properties screen is displayed. 4. In the Repository size field, enter the physical size, in terabytes, to which you want the repository expanded. 5. In the Estimated factoring ratio field, enter the factoring ratio value that you estimate for the expanded repository. 6. Select the MD Raid configuration from the options in the drop-down list. 7. Select the Disk size, in GB, from the options in the drop-down list. 8. Click Next. The Repository resources screen is displayed. The Allocated meta data size field value and the Allocated user data size field value are automatically generated based on the values entered in the Repository size properties screen. 9. From the Repository resources dialog, click Advanced. The Repository resources window is displayed with a list of available file systems for meta data and user data.

Chapter 6. Managing repositories

41

Figure 9. Repository resources dialog

10. Select file systems from the Available file systems list and click the arrows to the left and right of the column to add available file systems to either the meta data column or the user data column. 11. Click Ok. The Repository resources dialog closes. 12. Click Next. A summary report is displayed with the new configuration. 13. Click Finish. The Increase capacity wizard closes and the ProtecTIER system temporarily goes offline to increase the repository capacity.

Deleting repositories
Complete this task to delete a repository. In a two-node cluster where the repository was created on one of the nodes, you must remove the second node before you delete the repository. In general, it is not necessary to delete a repository. However, you might have to delete a repository in certain troubleshooting scenarios. For more information, contact IBM Support. For more information, see Removing and adding cluster members on page 121. Attention: Deleting the repository results in the loss of all the data contained in the repository.

42

IBM System Storage TS7600 with ProtecTIER: Users Guide

Perform the following steps to delete a repository: 1. In the Repositories pane, select the repository. 2. Choose Repository > Delete repository. A confirmation message box is displayed. 3. Click Yes. The Data Loss Confirmation dialog box is displayed. 4. In the field, type data loss and click Ok. A confirmation message box is displayed. 5. Click Yes. The ProtecTIER system temporarily goes offline to delete the repository.

Replication policies
A replication policy defines a set of objects (for example, cartridges) from a repository that need to be replicated to a remote repository. A replication policy is the only means to transfer deduplicated data from a source repository to a destination repository. A replication policy is made up of rules. An event occurs, for example, which indicates that the data segment on a cartridge has changed and that replication may be needed for the specific cartridge. Once the event matches with a policy, a trigger is created for replication activity and a job occurs. Replication policies are defined via the Systems Management view of ProtecTIER Manager. A policy can only be created on a repository that is the source in a grids pair and the policy only applies to the repository on which its defined. Click on a repository in the navigation pane to view the policies defined for that repository. Select a policy from the list to view the policy details and replication statistics.

Chapter 6. Managing repositories

43

Figure 10. View of replication policy

The following sections describe how to create and work with replication policies: v Setting the replication timeframe v Creating a replication policy on page 45 v Enabling and disabling a policy on page 46 v Running a policy on page 46 v Modifying a policy on page 47 v Deleting a policy on page 47

Setting the replication timeframe


You can schedule a timeframe (for example, a replication window) for replication to take place for all policies. To set the replication timeframe: 1. Select Replication > Set replication timeframe. The Set replication timeframe dialog box is displayed:

44

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 11. Set replication time frame

2. Select an option. You can either set a precedency for backup where the replication policy will take precedence in the order of other policies to be replicated, or you can set a given timeframe by setting the Start time, Duration and End time. 3. Click OK.

Creating a replication policy


When creating a replication policy, the following parameters are defined : v User object type (for example, cartridges) v User object (for example, barcodes) v Replication destination (for example, visibility change) If the destination is defined as a target library, visibility switching is enabled. This means that if you eject a cartridge that belongs to the respective policy, the cartridge is moved to the shelf of the local repository and on the destination repository, the cartridge is placed in the import/export slots of the destination library. Note: Visibility control is the means by which you can determine where cartridges actually exist. From a backup application standpoint, a specific cartridge or barcode can exist in only one location at a given time. Once exported by the backup application, cartridges can be placed on a virtual shelf that is visible via ProtecTIER, providing more flexibility in managing tapes/cartridges and where they are kept similar to keeping physical tapes on an actual shelf outside of the tape library. To create a replication policy: 1. Choose Replication > Policy > Create policy. The Welcome screen of the Create policy wizard is displayed. 2. Click Next. The Properties screen is displayed:

Chapter 6. Managing repositories

45

a. Type a unique policy name in the Policy name field. You cannot have the same policy name twice. If you do define the same policy name, an error message is displayed. b. Policies have 3 options of priority: High, Medium, Low. Define the policys Priority according to the importance and/or urgency of the data that needs to be transferred. For example, a policy with a high priority is transferred first, then a policy with medium priority, followed by low priority. The default is Low for every policy. c. Selecting Policy enabled automatically runs the policy within the timeframe defined. If Policy enabled is not selected, no activities will take place. Click Next, the Replication Destination screen is displayed: The Destination repository option controls the visibility of replicated cartridges at the destination repository. Destination replica cartridges can be invisible (if you choose shelf) or visible (if you choose a library). The Target is the destination of the cartridge. The target is either the shelf or a library: v If you choose shelf, the visibility switching feature is not activated. v If the target is a library, the visibility switching feature is activated. Upon ejecting a cartridge, it is first moved to the shelf on the local repository. On the remote repository, the cartridge is moved to the import/export slot of a library so that the backup application on the remote site can see it. Click Next. The Barcode ranges screen is displayed. The policy objects, i.e. cartridges, are defined as barcode ranges. There can be up to 256 ranges in a single policy. Type the From and To barcodes for a range of cartridges to be replicated. Click Add to view the range in the Ranges table. If a barcode number or barcode range appears more than once, an error message is displayed with the conflict. To delete the barcode ranges from the table, click Select all and Remove, or click Select none to deselect. Click Next. The Summary report is displayed with the policy name and the number of ranges that were defined.

3.

4.

5. 6.

7. 8.

Enabling and disabling a policy


You can enable or disable a policy from ProtecTIER Manager.

Enabling a policy
Upon successfully creating a policy, by default, the policy is enabled. This means that all incoming replication events will look to apply their rules to the policys definition. If a policy is disabled, you can enable it from ProtecTIER Manager. This does not affect current running activities.

Disabling a policy
A policy can be disabled at any time from ProtecTIER Manager. If a policy is disabled, all incoming replication events will ignore the policy from the moment it is disabled. This does not affect current running and pending activities.

Running a policy
Policies can be run either manually or automatically (i.e., continuously).

46

IBM System Storage TS7600 with ProtecTIER: Users Guide

Whenever replication events are received, policies are continuously run. The most common types of triggers for automatic replication are: v backup v eject v unload cartridge Manually run policies create replication jobs for all the valid cartridges in their list, whether or not they need to be replicated. Running a policy leads to lining up replication jobs in their respective priority queues where they wait for resources and the replication timeframe to start replicating. To run a policy: Select Replication > Policy > Execute policy.

Running a policy on a cartridge


You can also replicate a specific cartridge that is within the range of cartridges in a specific policy. To manually run the policy on the specific cartridge, select the Cartridges tab view of the library. Right-click on the cartridge and choose Cartridge replication.

Modifying a policy
You can modify a policy to change the parameters originally defined during policy creation. To modify a policy: 1. Select Replication > Policy > Modify policy. The Modify policy welcome screen is displayed. 2. Click Next. The Properties screen is displayed: a. Define the policys Priority according to the importance and/or urgency of the data that needs to be transferred. Policies have 3 options of priority: High, Normal, Low. The default is Normal for every policy. b. Select Policy enabled to automatically run the policy within the timeframe defined. If Policy enabled is not selected, no activities will take place. 3. Click Next, the Replication Destination screen is displayed. Select the remote target location in the destination repository to which the cartridge with the replicated data is to be placed. 4. Click Next. The Barcode ranges screen is displayed with the ranges defined during creation of the policy. a. To delete the barcode ranges from the table, click Select all and Remove. b. To deselect your choice, click Select none. c. Type the From and To barcodes for a range of cartridges to be replicated. 5. Click Add to view the range in the Ranges table. If a barcode number or barcode range appears more than once, an error message is displayed with the conflict. 6. Click Next. The modified policys Summary report is displayed.

Deleting a policy
Deleting a policy removes the policy in its entirety from the repository. All running and pending activities are aborted.
Chapter 6. Managing repositories

47

To delete a policy: Select Replication > Policy > Delete policy. A dialog will appear to confirm the action and a message that all running and pending activities will be aborted. For more information on aborting replication activities, see Aborting replication activities.

Aborting replication activities


This topic describes how to abort cartridge replication activities on a repository. When monitoring a repository, there are two ways to abort replication activities: v Selecting running replication activities from the Replication activities tab and aborting them v Selecting a policy from the Replication Policies tab and aborting the running and pending replication activities

Aborting running activities


You can abort running activities from the Replication activities tab in the following ways: v Right-click on the cartridge on which you want to abort activities and choose Abort activity v Highlight all the cartridges on which you want to abort activities and select Replication > Policy > Abort activities v Highlight all the cartridges on which you want to abort activities and click the Abort activity button This cancels all the running replication activities on a cartridge without affecting any pending activities, thereby not causing any backlog issues.

Aborting replication policys running and pending activities


You can abort running and pending activities of a policy from the Replication Policies tab in the following ways: v Select the policy on which you want to abort all replication activities and click the Abort activities button v Select the policy on which you want to abort all replication activities and select Replication > Policy > Abort activities v Right-click on the policy and choose Delete policy Aborting replication activities of a policy cancels any running and pending activities that are generated from the selected policy. This has an immediate effect on the running activities, however, the pending activities are backlogged and are aborted over time. This is due to the background nature of cancelling pending triggers. The backlog is reduced due to the cancellation of the pending activities, which is done one by one in the background, but the effect is not immediate. In the case of deleting a policy, the selected policy is deleted in its entirety and all running and pending activities are deleted.

48

IBM System Storage TS7600 with ProtecTIER: Users Guide

Chapter 7. Managing the ProtecTIER VT service


The ProtecTIER system has a rich set of library management functions that are described in this chapter. A virtual tape library emulates a physical tape library. The ProtecTIER system emulates the library installation, library expansion, cartridge management, drive addition, and drive allocation.

Setting the ProtecTIER VT host connections


Connect the ProtecTIER front-end ports to your backup environment. ProtecTIER front-end ports can be connected either in FC loop topology or through fibre channel switches. If fibre channel switches are used, you must create zones to set up the appropriate fibre channel connectivity between the ProtecTIER front-end ports and the fibre channel ports in your backup environment. Attention: The switch should be installed and correctly cabled before beginning the configuration. For details, see the documentation provided with the switch.

Creating the zones


A ProtecTIER server front-end port should share zones only with backup server FC ports. Each zone should contain only one ProtecTIER front-end port. Zoning can be defined by switch ports or by World Wide Names (WWNs).

Configuring node ports for hosts running HP-UX


If one or more front-end ports on one of your nodes is connected to a host running HP-UX, configure the WWNs of those ports as HP-UX WWNs using the vtlutil utility from Linux shell. 1. Log into a ProtecTIER node server. 2. Change to the /opt/dtc/app/utils/ directory. 3. Type vtlutil -hp <HP WWN> -port <ProtecTIER front-end port number> to define an HP WWN for the port. An entry is automatically added to the file /etc/pt/ports_conf.xml. For example:
<?xml version 1.0 encoding=UTF-16 standalone=no?> <ports- configuration> <fc_ports> <fc_port_info configured-mode=FE configured-speed=AUTO configured-topology=P2P current-speed=1GB currenttopology=P2P instance=1 wwn=10000000c942711f> <speed-option value=AUTO/> <speed-option value=1GB/> <speed-option value=2GB/> <speed-option value=4GB/> <topology-option value=LOOP/> <topology-option value=P2P/> <mode-option value=FE/> <mode-option value=BE/>

Copyright IBM Corp. 2008, 2009

49

<hp-wwn wwn=50060b000000f0b0/> </fc_port_info> </fc_ports>

Note: If you no longer want a port to have an HP WWN, delete the line identifying the HP WWN from /etc/pt/ports_conf.xml, for example:
<hp-wwn wwn=50060b000000f0b0/>

Creating libraries
A library can be created on a ProtecTIER system of either one node or two nodes. Note: Check with your backup application administrator to ensure the number of drives and cartridges supported by your application.
7650G Maximum number of libraries Maximum number of virtual drives 16 256 (dual-node 512) 7650 Appliance 12 256 (dual-node 512)

Note: Use the Scan button of the Port attributes pane to verify if the ports of the ProtecTEIR server to which the virtual devices of the library are to be assigned are connected to the correct host. For more information, see Port attributes on page 86. If your ProtecTIER node has ports connected to a host that is running HP-UX, verify that the ports are configured as HP-UX ports. For more information, see Configuring node ports for hosts running HP-UX on page 49. If these conditions are not met, the host may not be able to detect all of the virtual tape drives. Perform the following steps to create the library: 1. In the Systems pane, select a cluster on which to add a library. 2. From the Toolbar, click the Create new library button. The Create new library wizard Welcome screen is displayed. 3. Click Next. The Library details screen is displayed. 4. In the VT name field, enter a name for the library. 5. Click Next. The Library type screen is displayed.

50

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 12. Library type screen

6. Select the type of physical library model that you want the virtual library to emulate: v ATL P3000 0100 v IBM TS3500 0100 You can also configure the virtual library models: v DTC VTF 0100 v IBM V-TS3500 0100 Note: Verify that the backup application that you are using supports the type of library model that you select. 7. Click Next. The Tape model screen is displayed.

Chapter 7. Managing the ProtecTIER VT service

51

Figure 13. Tape model screen

8. Select the type of tape drive model that you want the virtual library to emulate. The type of tape drive depends on the library type chosen: v IBM ULT3580-TD3 (IBM LTO3) Note: All tape drives in the library are of this type after your selection, including tape drives added at a later time. 9. Click Next. The Tape drives screen is displayed.

52

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 14. Tape drives screen

10. In the Number of tape drives field for each node, enter the number of tape drives to assign to the node. To maximize load balancing, it is recommended that you distribute tape drives across the nodes in a cluster based on the relative power of the node servers. Note: The value of the maximum number of tape drives possible on a node depends on the amount of storage space available on your system. 11. Click Next. The Assignment screen is displayed.

Chapter 7. Managing the ProtecTIER VT service

53

Figure 15. Port assignment screen

12. Select or deselect the check boxes next to each port to define which of the nodes ports are assigned virtual devices. Note: If you have chosen an IBM library model, all the robots are selected and enabled. You can deselect the robots and choose at least one. If you have chosen a library model other than IBM, the robots are not checked and only one must be chosen. 13. In the Drives fields corresponding to each selected port, select the number of virtual tape drives that are assigned to each port. Note: Optionally, click Select All to automatically select both ports. Click Equally divide to evenly divide the number of drives between the ports. 14. Check the Robot checkbox if you want the library virtual robot to be accessible through this port. Note: For high-availability purposes, TS7650 supports the assignment of the virtual robot to multiple ports. 15. Click Next. If a second node exists in the cluster, the Assignment (2) screen is displayed.

54

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 16. Assignment (2) screen

16. Repeat steps 12 on page 54 and 13 on page 54 for the Assignment (2) screen. 17. Click Next. The Cartridges screen is displayed.

Chapter 7. Managing the ProtecTIER VT service

55

Figure 17. Cartridges screen

18. In the No. of cartridges field, enter the number of cartridges that you want to have in the library. The Virtual cartridge size field automatically displays the maximum possible size for virtual cartridges for your system. This is based on the number of cartridges entered, the total amount of available storage space in your repository, and the current HyperFactor ratio. Note: Optionally, select the Max. cartridge growth checkbox. When selected, you can limit the maximum amount of nominal data that a cartridge can contain. The value of the maximum number of cartridges possible on a system depends on the amount of storage space available on your system. 19. In the Barcode seed field, enter a value for the barcode seed. The barcode seed is the barcode that is assigned to the first cartridge created. Every cartridge added after the first cartridge is assigned a barcode following the initial barcode seed. Note: The barcode seed must contain only numbers and capital letters. 20. Click Next. The Slots screen is displayed.

56

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 18. Slots screen

21. In the Number of slots field, enter the number of cartridge slots that you want to have in the library. Note: The number of cartridge slots must not be less than the number of cartridges that you are creating. If you expect to increase the number of cartridges at a later time, it is recommended that you create additional slots. 22. In the Number of import/export slots field, enter the number of import/export slots that you want to have in the library. The maximum number of import/export slots that can be defined in the entire system is 1022. 23. Click Next and Finish. The Create new library wizard closes and the ProtecTIER system temporarily goes offline to create the library. The library is displayed in the Services pane and the VT monitoring screen is displayed.

Setting the library type


After creating a library, you can change the library type that was originally defined in the Create library wizard. Note: Verify the backup application you are using supports the type of library model you select for a virtual tape system.

Chapter 7. Managing the ProtecTIER VT service

57

When you set the library type, you can select the type of physical library model you want the virtual library to emulate: v ATL P3000 0100 v IBM TS3500 0100 You can also configure the virtual library models: v DTC VTF 0100 v IBM V-TS3500 0100 If you chose the TS3500 (or P3000) during creating a library and your backup application does not support that library model type as a virtual tape system, the Set library type dialog allows you to change the library type to V-TS3500 (or VTF). Conversely, if you chose the V-TS3500 (or VTF) during library creation, and your backup application supports the TS3500 library, use Set library type to change the library type. (i.e. You can interchange between the TS3500 and V-TS3500 library models and between the P3000 and VTF library models.)

Example
To set the library type, select VT > VT Library > Set library type. The Set library type dialog is displayed and you can specify the library type accordingly:

Figure 19. Set library type dialog

Editing library parameters


The ProtecTIER system enables you to change the parameters of existing libraries, including changing the assignment of virtual devices, adding virtual tape drives, and increasing the library capacity. Note: The Change dimensions wizard does not enable you to assign existing unassigned tape drives. Use the Re-assign devices wizard to assign unassigned tape drives. For more information, see Reassigning devices on page 62. Perform the following steps to change the parameters of an existing library: 1. In the Services pane, select a library. 2. Choose VT > VT Library > Change dimensions. The Change dimensions wizard Welcome screen is displayed. 3. Click Next. The Tape drives screen is displayed.

58

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 20. Tape drives screen

4. In the Number of tape drives field for each node, enter the number of tape drives that you want to have in the node. 5. Click Next. The Assignment screen is displayed for the first node in the cluster.

Chapter 7. Managing the ProtecTIER VT service

59

Figure 21. Assignment screen

6. Select or deselect the check boxes next to each port to define which of the nodes ports are assigned virtual tape drives. 7. In the Drives fields corresponding to each selected port, select the number of virtual tape drives that are assigned to each port. Note: Optionally, click Select All to automatically select both ports. Click Equally divide to evenly divide the number of drives between the ports. 8. Optionally, click Track Changes to display the modifications that the ProtecTIER system might need to make in response to the changes you defined. Then, click Re-assign ports to return to the Assignment screen and continue assigning virtual tape drives. 9. Check the Robot checkbox if you want the library virtual robot to be accessible through this port. Note: For high-availability purposes, TS7650 supports the assignment of the virtual robot to multiple ports. 10. Click Next. If a second node exists in the cluster, the Assignment (2) screen is displayed.

60

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 22. Assignment (2) screen

11. Repeat steps 6 on page 60 through 9 on page 60 for the Assignment (2) screen. 12. Click Next. The Slots screen is displayed.

Chapter 7. Managing the ProtecTIER VT service

61

Figure 23. Slots screen

13. In the Number of slots field, enter the number of slots that you want in the library. Note: The number of slots must be at least equal to the number of cartridges in the library. 14. In the Number of import/export slots field, enter the number of import/export slots that you want in the library. 15. Click Next and Finish. The Change dimensions wizard closes and the ProtecTIER system temporarily goes offline to update the library.

Reassigning devices
The ProtecTIER system enables you to relocate the virtual robot and cartridge drives between nodes or node ports. Perform the following steps to reassign the virtual robot or cartridge drives: 1. Choose VT > VT Library > Re-assign devices. The Re-assign devices wizard Welcome screen is displayed. 2. Click Next. The Tape drives screen is displayed.

62

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 24. Tape drives screen

3. In the Number of tape drives field, select the number of tape drives to assign to the node. Note: If a node is currently down, you can only remove drives from that node. 4. Click Next. The Assignment screen is displayed.

Chapter 7. Managing the ProtecTIER VT service

63

Figure 25. Assignment screen

5. Select or deselect the check boxes next to each port to define which of the nodes ports are assigned virtual tape drives. 6. In the Drives fields corresponding to each selected port, select the number of virtual tape drives that are assigned to each port. Note: Optionally, click Select All to automatically select both ports. Click Equally divide to evenly divide the number of drives between the ports. 7. Optionally, click Track Changes to display the modifications that the ProtecTIER system might need to make in response to the changes that you defined. Then, click Re-assign ports to return to the Assignment screen and continue assigning virtual tape drives. 8. Check the Robot checkbox if you want the library virtual robot to be accessible through this port. Note: For high-availability purposes, TS7650 supports the assignment of the virtual robot to multiple ports. 9. Click Next. If a second node exists in the cluster, the Assignment (2) screen is displayed.

64

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 26. Assignment (2) screen

10. Repeat steps 5 on page 64 through 8 on page 64 for the Assignment (2) screen. 11. Click Next. The Summary report is displayed.

Chapter 7. Managing the ProtecTIER VT service

65

Figure 27. Summary report screen

12. Click Finish. The Re-assign devices wizard closes and the ProtecTIER system temporarily goes offline to reassign the devices.

Setting control path failover


Control Path Failover (CPF) is supported by the emulated IBM library models. By default, CPF is enabled on the emulated IBM library models. When troubleshooting host connectivity issues, you might be asked to disable CPF. To disable CPF, click on a library from the Services window in the navigation pane. 1. Select VT > VT Library > Set control path failover mode. The Set control path failover mode dialog is displayed. 2. Set the CPF mode to Control path failover disabled.

Managing cartridges
The ProtecTIER system has a function that enables you to add and remove cartridges from your libraries.

66

IBM System Storage TS7600 with ProtecTIER: Users Guide

Adding cartridges
If your virtual library has enough empty slots to accommodate the additional cartridges, the adding cartridges process occurs online without disrupting backup. If the virtual library does not have enough empty slots, adding cartridges causes the ProtecTIER system to temporarily go offline to create more slots for the cartridges. Perform the following steps to add cartridges: 1. Click the Add cartridges button. The Add cartridges wizard Welcome screen is displayed. 2. Click Next. The Cartridges screen is displayed.

Figure 28. Cartridges screen

3. In the No. of cartridges field, enter the number of cartridges that you want to have in the library. The Virtual cartridge size field automatically displays the maximum possible size for virtual cartridges for your system. This number is based on the number of cartridges entered, the total amount of available storage space in your repository, and the current HyperFactor ratio. Note: Optionally select the Max. cartridge growth checkbox. When selected, you can limit the maximum amount of nominal data that a cartridge can contain.
Chapter 7. Managing the ProtecTIER VT service

67

The value of the maximum number of cartridges possible on a system depends on the amount of storage space available on your system. 4. In the Barcode seed field, enter a value for the barcode seed. The default barcode seed is the continuation of the initial barcode seed assigned when the library was created. Note: The barcode seed must contain only numbers and capital letters. 5. Click Next and Finish. The Add cartridges wizard closes and the cartridges are added to the library. If the necessary number of cartridge slots are not already available, the ProtecTIER system temporarily goes offline to create them.

Deleting cartridges
Deleting a cartridge results in the loss of all data contained in the cartridge. Perform the following steps to delete a cartridge: Note: Alternatively, you can delete a cartridge from the shelf. Deleting a cartridge from the shelf is a nondisruptive operation (i.e. the VTL stays online). Thus, it is recommended that you eject the cartridges you want to delete to the local shelf on the repository, and then delete the cartridge. 1. From the Systems tab, select the library from the Services pane that contains the cartridge that you want to delete. The VT screen is displayed. 2. Click the Cartridges tab. The Cartridges screen is displayed.

68

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 29. Cartridges screen

3. Select a cartridge. 4. Choose VT > VT Cartridge > Delete Cartridge. A confirmation message box is displayed. 5. Click Yes. The Data Loss Confirmation dialog is displayed. 6. In the field, type data loss and click Ok. A confirmation message box is displayed. 7. Click Yes. The cartridge is deleted.

Switching cartridges to read-only mode


Perform the following steps to change the cartridge mode to read-only: 1. Select a cartridge. 2. Choose VT > VT Cartridge > Read/Write cartridge. A confirmation message box is displayed. 3. Click Yes. The cartridge switches to read-only mode. Note: Clicking Read/Write cartridge for a read-only cartridge switches the cartridge to the read/write mode.

Chapter 7. Managing the ProtecTIER VT service

69

Renaming libraries
The ProtecTIER system enables you to rename libraries after they have been created. Perform the following steps to rename an existing library: 1. In the Services pane, select a library. 2. Choose VT > VT Library > Rename library. The Rename library dialog is displayed. 3. Enter a new name for the selected library and click Ok. The Rename library dialog closes and the librarys name is changed.

Deleting libraries
Attention: Deleting a library results in the loss of all data contained in that library. Perform the following steps to delete a library: 1. In the Services pane, select a library. 2. Choose VT > VT Library > Delete library. A confirmation message box is displayed. 3. Click Yes. The Data Loss Confirmation dialog is displayed. 4. In the field, type data loss and click Ok. A confirmation message box is displayed. 5. Click Yes. The ProtecTIER system temporarily goes offline to delete the library.

70

IBM System Storage TS7600 with ProtecTIER: Users Guide

Chapter 8. Native Replication Management


This chapter provides the information needed to manage native replication activities.

Grids Management view


The Grid Manager manages the replication grids within an organization. The Grid Managers responsibilities include: v Managing the repositories in the replication grid that can be replicated to v Maintain the IP addresses of all repositories v Update of repositories leaving and joining the grid v High-level monitoring and statistics of traffic in the replication grids. ProtecTIER Manager connects to the grid manager using the IP address of the grid manager. Click the Grids Management button at the bottom of the navigation pane of ProtecTIER Manager to view the Grid Manager.

Adding and connecting to a grid manager


To connect to a new grid manager: 1. Click the Add grid manager button. The Add grid manager dialog is displayed. 2. Enter the IP address of the grid manager you want to add and click Ok. The grid manager login dialog is displayed. 3. Enter the User name: gmadmin and Password: gmadmin and click Ok. 4. The login screen is displayed.

Managing a grid
Managing a grid is done via the Grids Management view of ProtecTIER Manager. Note: Grid IDs and repository IDs are numbers that are never recycled. Even if a repository leaves the grid and re-enters the grid, it will not receive the same ID. Thus, actions like leaving a grid are expected to be rare and should not be planned as part of the normal flow of work.

Creating a grid
Managing a grid is done via the Grids Management view of ProtecTIER Manager. Note: Grid IDs and repository IDs are numbers that are never recycled. Even if a repository leaves the grid and re-enters the grid, it will not receive the same ID. Thus, actions like leaving a grid are expected to be rare and should not be planned as part of the normal flow of work. 1. Click Create new grid. The Create new grid dialog is displayed. Note: A maximum of 63 grids can exist in an organization. 2. Complete the fields to define a grid. Select a unique Grid ID number (1 to 63) from the dropdown list and enter a name in the Name field. Click Ok.

Copyright IBM Corp. 2008, 2009

71

Note: ProtecTIER will not allow you to choose an ID that has already been used.

Adding a repository to a grid


To add a repository to a grid: 1. Select Grid > Add repository to grid. The Add repository to grid dialog is displayed. Note: A maximum of 256 repositories can exist in a grid. A repository cannot be a grid member of more than one grid. 2. Type the network replication IP address of the repository in the IP address field. 3. Enter the User name: ptadmin and Password: ptadmin. Click Ok.

Deleting a repository from a grid


A repository can be removed from a grid in coordination with the grid. To remove a repository from a grid: 1. Select Grid > Remove repository from grid. The Remove repository from grid screen is displayed: 2. Select the repository to remove from the Repository name drop-down list. If the repository is part of a pair, the replication pair must be deleted first before you can remove the repository from the grid. See Deleting pairs on page 73. 3. Complete the login information by typing the user name and password of the repository. Click Ok. Note: Removing a repository from a grid, without coordination with the grid, should be done only if the Grid Manager is temporarily down, or if there is a good reason for the lack of communication between the grid manager and the repository. From the Grids Management view, select Grid > Disaster recovery > Uncoordinated repository removal.

Forcing a repository to leave a grid


A repository can be removed from a grid without its cooperation. Note: Forcing a repository to leave a grid should be done only if the repository has been destroyed and is not supposed to be a part of the grid. It is preferable to remove a repository from a grid with coordination between the two. If the Grid Manager does not recognize a repository as part of the grid, but the repository thinks it is part of the grid, then the repository must be removed (for example, convinced) that it is not a part of the grid. Only then should a repository should be forced to leave a grid. Once a repository has been removed from a grid without its cooperation, it cannot be added to a new grid in the usual manner. To force a repository from a grid, from the Systems Management mode, select Replication > Disaster recovery > Uncoordinated repository removal from grid.

72

IBM System Storage TS7600 with ProtecTIER: Users Guide

Updating the IP address of a repository


If the replication IP address of the repository is changed , the grid manager needs to be updated as well with the correct IP address. To update the IP address of a repository, select Grid > Update repository address. The Update repository address screen is displayed. Enter the updated IP address and click Ok.

Displaying removed repositories


All of the repository statistics that are or were once part of the grid are saved in the Grid Manager database. The statistics are returned to the user interface upon request. To display the list of unrecoverable repositories and their replacements, click Grid > Show removed repositories. A table is displayed showing the list of unrecoverable repositories and their replacements.

Creating pairs
Before defining any policy, you must define repository pairs. Note: When defining a replication pair, you also define the direction of the replication from the source repository to the destination repository. Typically, the source is the primary repository and the destination is the DR site. To create a replication pair: 1. Select Grid > Create replication pair. The Create replication pair dialog is displayed:

Figure 30. Create replication pair

2. Select the Source repository ID and Destination repository ID from the drop-down listboxes. Click Ok. Note: The source and destination repository ids in a pair cannot be the same.

Deleting pairs
To delete a replication pair:
Chapter 8. Native Replication Management

73

1. Select Grid > Delete replication pair. The Delete replication pair dialog is displayed:

Figure 31. Delete replication pair

2. Select a replication pair to delete from the drop-down listbox. Click Ok. The repositories are listed separately.

Monitoring the grid


ProtecTIER Manager is used to monitor a replication grid. It is possible to see current grid members and their status, the relationship between the grid members and the actual throughput of replication data between the grid members. The Grid Manager periodically updates the status of the grid members and ProtecTIER Manager receives the status updates from the Grid Manager. The status includes whether or not the grid member is online, if the grid member reports any errors related to replication, and statistics regarding replication activity currently being run on the grid member. Select a grid pair from the navigation pane and click on one of the grid members. The grid member details are displayed to the right. The details displayed are: v Capacity v Backup and replication activities v Grid member replication configuration The details displayed are a partial view of the full repository view. For more information, see Monitoring the repository on page 80.

74

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 32. View of grid member details via Grids Management mode

Chapter 8. Native Replication Management

75

76

IBM System Storage TS7600 with ProtecTIER: Users Guide

Chapter 9. Monitoring ProtecTIER


The topics in this section describe how to use ProtecTIER Manager to monitor the status and performance of the elements of the ProtecTIER system.

Monitoring clusters
In the Systems Management pane, select a cluster. The Systems monitoring screen is displayed:

Figure 33. Systems monitoring screen

The Systems screen consists of the following main tabs: v General v VT on page 79 and In addition, the ProtecTIER Manager status bar displays the total read throughput rates for the selected cluster and the time on the cluster. write Note: The status bar also displays the Alerts and Event log buttons which enable you to view alert and event information for the nodes of the selected cluster. (For more information, see Viewing the alerts and events log windows on page 117.)

General
The General tab displays information about the cluster and consists of the following panes:
Copyright IBM Corp. 2008, 2009

77

v Capacity v Fibre channel ports throughput on page 86 v Cluster members on page 79

Capacity
The Capacity pane displays the amounts of the disk space that are used , allocable, or fragmented in the selected clusters repository, in both graphical and numerical format. The amount of total disk space is also displayed. v Total capacity refers to the total amount of physical disk space in the system v Used refers to the amount of physical space that currently contains data v Allocable refers to the amount of free physical space that is available to hold data v Fragmented refers to the amount of free physical space that cannot hold data until it is defragmented by ProtecTIERs defragmentation operation You can click View resources to open the Storage resources dialog.

Figure 34. Storage resources dialog

The Storage resources dialog displays the list of meta data and user data file systems for the selected clusters repository.

78

IBM System Storage TS7600 with ProtecTIER: Users Guide

Note: Open the Storage resources dialog at any time by clicking View resources button in the Toolbar.

Fibre channel ports throughput


An instance of the Fibre channel ports throughput pane is displayed for each node in the cluster. The Fibre channel ports throughput pane displays the rate of data movement and I/O operations for both reading and writing operations for the node. The data movement rate is also displayed graphically for each front-end Fibre Channel port on the node. You can change the scale of the graph by editing the value in the Scale graph field.

Cluster members
The Cluster members pane displays the following information about each node in the cluster:
Table 4. Cluster member information Column IP Address DNS GUI proxy Definition IP address of the node. Name of the node. Indicates which node is currently being used by ProtecTIER Manager to monitor the cluster. Indicates whether ProtecTIER is online or offline on the node. Indicates whether the VT service for that node is online or offline.

Status VT

VT
The VT tab displays information about the VT service libraries associated with the cluster.

Chapter 9. Monitoring ProtecTIER

79

Figure 35. VT tab

The VT tab consists of the following panes: v Library front-end - Displays information about all library devices assigned to nodes in the cluster. For more information, see Library type on page 89. v Libraries performance - Displays the total performance of the libraries in the cluster. For more information, see ProtecTIER VT overview on page 89. v Libraries configuration - Displays the total number of drives, slots, import/export slots, and cartridges for all the libraries in the cluster. For more information, see Configuration on page 89.

Monitoring the repository


In the Repositories pane, select the repository. The Repository monitoring screen is displayed.

80

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 36. Repository monitoring screen

The Repository monitoring screen consists of the following panes: v Capacity v Total utilization v Repository configuration v Storage on page 82 v HyperFactor on page 83

Capacity
The Capacity pane of the Repository monitoring screen is identical to that of the Cluster monitoring screen. For more information, see Capacity on page 78.

Total utilization
The Total utilization pane displays the following information in both graphical and numerical format:
Table 5. Total utilization information Item Used space Nominal data size Definition The amount of used physical repository space that currently contains data. The total amount of data which is stored in the used space using HyperFactor.

Repository configuration
The Repository configuration pane features the following information:
Chapter 9. Monitoring ProtecTIER

81

Table 6. Repository information Field Configured size Configured factoring ratio Calculated factoring ratio Configured peak throughput Configured IOPS Function The physical repository size in terabytes. The estimated HyperFactor factoring ratio that was used to create the repository. The actual current HyperFactor factoring ratio. The expected maximum peak throughput specified when the repository was created. The configured number of I/O operations per second supported by the meta data file systems specified during the repository creation.

Storage
The Storage pane displays the following graphs: v Nominal data size graph v Utilization graph You can alternate between the graphs using the tabs located below the Storage pane. Note: Set the scale of the Storage pane graphs to either hours or days.

Nominal data size graph

Figure 37. Nominal data size graph

The Nominal data size graph displays the amounts of data contained in the repository over time.

Utilization graph

Figure 38. Utilization graph

The Utilization graph displays the amounts of actual repository space used over time.

82

IBM System Storage TS7600 with ProtecTIER: Users Guide

HyperFactor
The HyperFactor pane displays one of the following graphs: v Marginal HyperFactor ratio graph v HyperFactor ratio over time graph You can alternate between the graphs using the tabs located below the HyperFactor pane. Note: Set the scale of the HyperFactor pane graphs to either hours or days.

Marginal HyperFactor ratio graph

Figure 39. Marginal HyperFactor graph

The Marginal HyperFactor ratio graph displays the amount of data written to the repository, and the physical space it occupies, at each point in time. Comparing these two values enables you to evaluate the effect of HyperFactor on the data written.

HyperFactor ratio over time graph

Figure 40. HyperFactor ratio over time graph

The HyperFactor ratio over time graph displays the cumulative HyperFactor ratio as it changes over time.

Monitoring replication policies and activites


You can monitor replication policies and activities of a repository via the Systems Management view. Click on the repository appearing in the navigation pane.

Replication Policies tab


Click on the Replication Policies tab at the bottom of the work pane to see the replication policies that are defined on the repository. Select a policy from the list to view the policys details.

Chapter 9. Monitoring ProtecTIER

83

Figure 41. Replication policies tab

When you select a policy, you can see the policys details as defined by the Create policy wizard. In addition, you can see the number of active and pending replication activities related to this policy. Policy name The name that you define for the policy. Mode Cartridges are either copied or moved. (Note: In this release, copy is the only mode of operation.) Priority Policys level of importance: high, normal, or low. Enabled Policy can be enabled or disabled for execution.

Replication activites tab


Click on the Replication activities tab at the bottom of the work pane. The list of cartridges undergoing replication activity is displayed. Select a cartridge from the list to view the cartridge details.

84

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 42. Replication activities view

Note: The replication activities view is adhoc. As such, if new data is written to a cartridge while it is being replicated, the progress of the displayed data details will appear as if it has been restarted. Object ID the barcode of the cartridge Policy the name of the policy that contains the respective cartridge in its definition Throughput the nominal throughput of replicating data in MB/sec Dedup displays the savings in the bandwidth needed for replicating this cartridge Priority the replication policys priority in the queue Progress the progress of replicating the latest changes to their destination Time left the amount of time remaining for the replication process to complete

Chapter 9. Monitoring ProtecTIER

85

Monitoring nodes
In the Nodes pane, select a node. The Node monitoring screen is displayed. The Node monitoring screen consists of the following panes: v v v v Port attributes Version information Fibre channel ports throughput Network configuration on page 87

Port attributes
The Port attributes pane displays the following information for each port in the node:
Table 7. Port attribute information Column Port Definition Port number and port mode. All ports in the ProtecTIER system are front-end ports that connect the node with the backup server(s). This mode is labeled FE. Worldwide Name of the port. Transmission speed of the port. Fiber Channel topology of the port. The possible values are as follows: v Point-to-point (P2P) v Fiber channel-arbitrated loop v Down There is no fiber channel connection User setup User-assigned link speed and topology.

WWN Link Speed Topology

In addition, for each port you can click the Scan button to open the Scan Port dialog box. The Scan Port dialog box displays a numbered list of the Worldwide Names of the remote ports detected by the port.

Version information
The Version information pane displays the version numbers for the versions of ProtecTIER, the PT Linux RPM, and the DTC Emulex RPM installed and running on the node. In addition, click Show fixes to display the list of temporary fixes featured in the installed ProtecTIER version.

Fibre channel ports throughput


The elements of the Fibre channel ports throughput pane of the Node monitoring screen are identical to the elements of the Fibre channel ports throughput pane of the Cluster monitoring screen. For more information, see Fibre channel ports throughput on page 79.

86

IBM System Storage TS7600 with ProtecTIER: Users Guide

Network configuration
The Network configuration pane displays information about the setup of the network interface cards (NIC) for the node.
Table 8. Network interface card information Column Device Definition The devices in the NIC. v Eth0 is the node port that communicates with the ProtecTIER Manager workstation v Eth1 and Eth2 are the node ports used in the cluster-internal network v Bond0 is the virtual bond master device to which Eth1 and Eth2 are enslaved Bond devices are defined as part of the installation process. IP Address Usage IP address of the device. Indicates whether the device is used for the cluster-internal network or to communicate with the ProtecTIER Manager workstation and the external network. The master device or bond device, if any, to which the device is enslaved. Indicates whether the device is functioning properly. The supported speed of data transfer across the device in Megabits per second. Configured maximum transmission unit for the device.

Master device Status Speed MTU

Monitoring the ProtecTIER VT service


In the Services pane, select a library. The VT service monitoring screen is displayed with the General tab displayed. The VT service monitoring screen consists of the following tabs: v General v Drives on page 89 v Monitoring VT Service - Cartridges tab on page 91 v Monitoring Virtual Tape service - Slots tab on page 92 v Imports/Exports on page 92

General
The VT service monitoring screen displays the General tab by default. The General tab displays information about the selected library.

Chapter 9. Monitoring ProtecTIER

87

Figure 43. General tab

The General tab consists of the following panes: v Library front-end v ProtecTIER VT overview on page 89 v Configuration on page 89 v Library type on page 89

Library front-end
The Library front-end pane displays the virtual robots and tape drives assigned to each port of each node in your ProtecTIER system.
Table 9. Virtual robots and tape drive Column Node Port Top. Definition The node on which the virtual device is assigned. The port within the node on which the virtual device is assigned. The Fiber Channel topology of the port. Possible values: v Point-to-point (P2P) v Fiber channel-arbitrated loop v Down There is no fiber channel connection WWN LUN The Worldwide Name of the port. The logical unit number of the robot or tape drive relative to the port.

88

IBM System Storage TS7600 with ProtecTIER: Users Guide

Table 9. Virtual robots and tape drive (continued) Column Device Throughput Definition The name of the robot or tape drive. The rate of data transfer across the device.

Note: Change the device assignments for your libraries by clicking Re-assign devices. (For more information, see Reassigning devices on page 62.)

ProtecTIER VT overview
The ProtecTIER VT overview pane displays general information about the performance of the selected library for Read and Write operations, including the following: v v v v Status of each tape drive Rate of data transfer in Mbps Number of I/O operations per second Number of active tape drives

Each tape drive in the library is graphically represented. If the drive is currently writing, an orange square is displayed on the graphic. If the drive is currently reading, a blue icon is displayed. Hovering your cursor over the graphic displays the drive number, the current read/write rate of the drive in Mbps, and the percentage of time that the tape drive is idle during backup operations due to low backup application data transfer rates.

Configuration
The Configuration pane displays the current number of drives, slots, import/export slots, and cartridges in the selected library. Note: Change the number of devices in the library by clicking Edit to open the Change dimensions wizard. (For more information, see Editing library parameters on page 58.)

Library type
The Library type pane displays the definition for the emulated virtual library type, including the vendor name, product name, and revision number.

Drives
The Drives tab displays detailed information about the virtual tape drives in the selected library.

Chapter 9. Monitoring ProtecTIER

89

Figure 44. Drives tab

The Drives tab displays the following information:


Table 10. Drives tab information Column Drive No. Loaded Definition The drive number Indicates whether the drive is loaded with a virtual cartridge. If the drive is loaded with a virtual cartridge,

is displayed. Vendor Name Product Revision Node Port LUN Serial Address Barcode The vendor whose product the virtual drive emulates The product name for the product that the virtual drive emulates. The revision number for the product that the virtual drive emulates The node to which the drive is assigned The port on the node to which the drive is assigned The drives logical unit number relative to the port The drives serial number The drives address within the library If the drive is loaded with a cartridge, this column displays the cartridges barcode

90

IBM System Storage TS7600 with ProtecTIER: Users Guide

Monitoring VT Service - Cartridges tab


The Cartridges tab displays detailed information about the cartridges in the selected library.

Figure 45. Cartridges tab

The Cartridges tab displays the following information:


Table 11. Cartridges tab information Column Barcode Write enabled Definition The cartridges barcode. Whether the cartridge is write enabled. If the cartridge is write enabled, a green checkmark is displayed. The cartridges estimated data capacity in megabytes. This value varies over time depending on the HyperFactor ratio and the number of cartridges configured in the system. The amount of nominal data, in megabytes, currently stored on the cartridge. Indicates whether the cartridge has reached Early Warning. If so, the cartridge is regarded as full and a green checkmark is displayed.

Capacity

Data Size Full

Chapter 9. Monitoring ProtecTIER

91

Monitoring Virtual Tape service - Slots tab


The Slots tab displays detailed information about the slots in the selected library.

Figure 46. Slots tab

The Slots tab displays the following information:


Table 12. Slots tab information Column Slot No. Address Barcode Capacity Definition Indicates the slots number in the library. Indicates the slots address number. If the slot contains a cartridge, this column displays the cartridges barcode. If the slot contains a cartridge, this column displays the estimated cartridge capacity in megabytes. If the slot contains a cartridge, this column displays, in megabytes, the amount of nominal data currently stored on the cartridge.

Data Size

Imports/Exports
TheImports/Exports tab displays detailed information about the import/export slots in the selected library.

92

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 47. Imports/Exports tab

The Imports/Exports tab displays the following information:


Table 13. Imports/Exports tab information Column Imp/Exp No. Address Barcode Definition The number of the import/export slot. The import/export slots address number. If the import/export slot contains a cartridge, this column displays the cartridges barcode. If the import/export slot contains a cartridge, this column displays the estimated cartridges data capacity in megabytes. If the import/export slot contains a cartridge, this column displays, in megabytes, the amount of nominal data currently stored on the cartridge.

Capacity

Data Size

Monitoring the shelf


The shelf is a container for cartridges that do not belong to any library. Each repository contains only one shelf and whenever a cartridge in a library is moved to the librarys export slot, it is automatically displaced to the shelf. The cartridges in the shelf cannot be seen by backup applications and this facilitates the concept of being out of the library. Via ProtecTIER Manager, a view of the shelf can be displayed and you can access the cartridges in the shelf.

Chapter 9. Monitoring ProtecTIER

93

From the shelf, cartridges can be moved to a librarys import slot, replicated to another repository, or be deleted. Cartridges can also be automatically moved to a librarys import slot through the visibility switching process. A cartridge that is moved to an export slot is automatically displaced to the shelf.

Figure 48. Shelf view

Barcode the barcode of the cartridge R/W displays if the cartridge can be modified

Principal repository on which repository the cartridge can be modified Data size (MB) the nominal size (in MB) of the cartridge

Monitoring backups from the Linux shell


Monitor the statistics for your ProtecTIER systems backup sessions using the analyze_sessions utility. 1. Change to the /opt/dtc/app/utils/ directory.

94

IBM System Storage TS7600 with ProtecTIER: Users Guide

2. Type ./analyze_sessions. An output file containing statistics for the recent backup sessions is generated at the following location: /ptwork/<server name>-<date>-<time>.csv The following statistical information is included.
Table 14. Recent backup session statistics Statistic Total data (TB) Total data (KB) System change rate Description Total amount of data backed-up during the session, in terabytes. Total amount of data backed-up during the session, in kilobytes. Percentage of data in the backup session recognized as changed relative to the previous backup session. The ratio of the quantity of actual backed-up data over the total amount of physical data. Start time of the backup session. End time of the backup session.

Factoring ratio start time end time

The following is an example of the output of the analyze_sessions utility.


Total data (TB) Total data (KB) System change rate Factoring ratio

Name

start time

end time

Grand totals all 0.0604314 64887700 48.82% 2.05 2/13/2008 11:47 2/26/2008 21:24

By session (summary) 2008-2-13 11:47:41 to 2008-2-13 11:52:08 2008-2-26 18:00:49 to 2008-2-26 18:08:25 2008-2-26 21:24:52 to 2008-2-26 21:24:52 2008-2-13 12:13:25 to 2008-2-13 12:13:25 2008-2-13 14:23:34 to 2008-2-13 15:11:50 2008-2-13 19:06:10 to 2008-2-13 19:06:10 2008-2-13 20:15:29 to 2008-2-13 20:15:29 2008-2-26 17:34:45 to 2008-2-26 17:34:58 0.00683594 0.0038147 0.000204086 0.000748962 0.0185547 0.000331342 0.000331342 0.00115609 7340030 4096000 219136 804192 19922900 355776 355776 1241340 94.63 2.94 1.64 93.68 0.01 0.00 0.01 85.49 1.06 33.97 61.01 1.07 7342.59 64004.70 7637.78 1.17 2/13/2008 11:47 2/26/2008 18:00 2/26/2008 21:24 2/13/2008 12:13 2/13/2008 14:23 2/13/2008 19:06 2/13/2008 20:15 2/26/2008 17:34 2/13/2008 11:52 2/26/2008 18:08 2/26/2008 21:24 2/13/2008 12:13 2/13/2008 15:11 2/13/2008 19:06 2/13/2008 20:15 2/26/2008 17:34

Chapter 9. Monitoring ProtecTIER

95

96

IBM System Storage TS7600 with ProtecTIER: Users Guide

Chapter 10. Managing and monitoring ProtecTIER through the CLI


This chapter describes how to query the system via the command line interface (CLI), and to receive various statistics about the ProtecTIER system. Information in this section provides valuable insight to the administrator on the performance, capacity, configuration and operation of the system, and can be accessed by other management applications.

ptmon
The following section describes how to query the ProtecTIER server through the CLI using ptmon. The ptmon is loaded during the installation of ProtecTIER software and is located in the / opt/dtc/app/sbin/ directory. Make sure you are in this directory when running ptmon commands from the command prompt.

Usage
Use the ptmon command to query the system via the command line interface (CLI), and to receive various statistics about the ProtecTIER system. This information can provide valuable insight to the administrator on the performance, capacity, configuration and operation of the system, and can be accessed by other management applications. You can print the usage information message by running ptmon with no arguments. The usage information message will also be printed when the arguments list is malformed. The ptmon command is issued from the command line as follows: ./ptmon <-parameter> <variable>

Parameters
-repository Displays repository statistics. -libs Displays information about the unique ID of all configured libraries on the repository. -libinfo -libid library id Displays statistics on the configured tape drives of a specific library. -ncarts -libid library id Displays statistics on the number of configured cartridges of a specific library. -cartsinfo -libid library id -from first cartridge index -count number of cartridges Displays statistics for each of the cartridges in a specified range. -node_vtl_statistics -hours hours Displays the statistics history on the local host for the last <hours> hours.

Copyright IBM Corp. 2008, 2009

97

-version Displays the version of the build of the local ProtecTIER installation. pt-version is the major version release.

PTmon responses
PTmon responses always appear in a well structured XML document printed. The XML always has the same root element: response with attribute status which may have the values success or failed. The response element displays the reply as a child element on success and, in this case, returns an exit code of zero to the shell. If status is failed the response element has a single child element: error with attributes description (a human readable string) and a non-zero code value. The same value is returned to the shell. The code value is also returned as the PTmon exit code and enables grouping of errors to general types (RPC error, argument error, etc.)

Example - on success

<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <libraries-list host-name="somehostname" time="1235485682" time-string="24-Feb-2009 16:28"> <library name="somehostname_vt" unique-id="2199023256193"/> </libraries-list> </response>

Figure 49. ptmon on success response output

Example - on error

<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="failed"> <error code="2" description="Error: failed to execute GetStatisticsSamples"/> </response>

Figure 50. ptmon on error output

ptmon -repository
This command generates the following repository statistics:
Table 15. Repository command statistics Field current-factoring-ratio Description Current factoring ratio in the repository which is the nominal data divided by the physical data. Amount of unused space in the repository in MB. Amount of nominal data that in the repository in MB. Amount of physical storage configured for the repository in MB.

repository-free-physical-storage-mb repository-total-nominal-storage-mb repository-total-physical-storage-mb

98

IBM System Storage TS7600 with ProtecTIER: Users Guide

Table 15. Repository command statistics (continued) Field repository-used-physical-storage-mb repository-allocable-physical-storage-mb Description Amount of physical storage used by the repository in MB. Amount of physical storage available for the repository in MB.

Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <repository-statistics current-factoring-ratio="1.00" host-name="beast" repositoryallocablephysical-storage-mb="49152" repository-free-physical-storage-mb="49152" repositorytotalnominal-storage-mb="0" repository-total-physical-storage-mb="49152" repository-usedphysicalstorage-mb="0" time="1236210447" time-string="04-Mar-2009 18:47"/> </response>

Figure 51. ptmon -repository output

ptmon -libs
This command displays information about the unique ID of all configured libraries on the repository. This library unique ID can be later used for receiving detailed information about each of the configured libraries.

Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <libraries-list host-name="beast" time="1236210637" time-string="04-Mar-2009 18:50"> <library name="2" unique-id="2199023255719"/> <library name="20" unique-id="2199023255824"/> </libraries-list> </response>

Figure 52. ptmon -libs output

ptmon -libinfo -libid <library id>


This command displays statistics on the configured tape drives of a specific library:
Table 16. Statistics on the configured tape drives of a specific library Field num-total-drives library-name libid Descritpion Amount of configured tape drives Name of the library Unique ID for the library

Chapter 10. Managing and monitoring ProtecTIER through the CLI

99

Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <library-info host-name="beast" library-name="2" library-unique-id="2199023255719" numtotaldrives="12" time="1236210783" time-string="04-Mar-2009 18:53"> <active-drives/> </library-info> </response>

Figure 53. ptmon -libinfo -libid <library id> output

ptmon -ncarts -libid <library id>


This command displays statistics on the number of configured cartridges of a specific library:
Table 17. Statistics on the number of configured cartridges of a specific library Header libid Header Library unique ID taken from ptmon -libs output.

Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <library host-name="beast" num-configured-cartridges="5" time="1236210795" time-string="04Mar-2009 18:53" unique-id="2199023255719"/> </response>

Figure 54. ptmon -ncarts -libid <library id> output

ptmon -cartsinfo -libid <library id> -from <first cartridge index> -count <number of cartridges>
This command displays statistics for each of the cartridges in a specified range: v Cartridge barcode v Indication of whether the cartridge is full v Total amount of nominal data currently on the cartridge
Table 18. Statistics of the cartridges in a specified range Field libid from Description Library unique ID taken from -libs output. Number of cartridges before the first printed cartridges in the sorted list of cartridges (by barcode). Maximum number of cartridges in the output. This list may be shorter if the sorted list of cartridges is exhausted before printing <number of cartridges> cartridges.

count

100

IBM System Storage TS7600 with ProtecTIER: Users Guide

Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <cartridges-information host-name="beast" library-unique-id="2199023255719" time="1236210879" time-string="04-Mar-2009 18:54"> <cartridge barcode="000000" early-warning-reported="false" nominal-size-mb="0"/> <cartridge barcode="000001" early-warning-reported="false" nominal-size-mb="0"/> <cartridge barcode="000002" early-warning-reported="false" nominal-size-mb="0"/> <cartridge barcode="000003" early-warning-reported="false" nominal-size-mb="0"/> <cartridge barcode="000004" early-warning-reported="false" nominal-size-mb="0"/> </cartridges-information> </response>

Figure 55. ptmon -cartsinfo -libid <library id> -from <first cartridge index> -count <number of cartridges> outputf

ptmon -node_vtl_statistics -hours <hours>


This command displays the statistics history on the local host for the last <hours> hours:
Table 19. Statistics history on the local host for the last hours Field hours Description Number of hours of statistics to be included in the output. By default, the output includes 4 chronicles (fore example, statistic records) per hour (if the uptime is greater than or equal to the number of hours).

Chapter 10. Managing and monitoring ProtecTIER through the CLI

101

Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <statistics num-returned="4"> <chronicle n-samples-per-poll="30" sample-date="04-03-2009 18:00:32" sample-timeseconds=" 30"> <vtl-overall num-active-tapes="0" num-reading-tapes="0" num-writing-tapes="0" readio. average-bytes="0" read-io.max-bytes="0" read-io.min-bytes="0" valid="true" writeio. average-bytes="0" write-io.max-bytes="0" write-io.min-bytes="0"/> </chronicle> <chronicle n-samples-per-poll="30" sample-date="04-03-2009 18:15:33" sample-timeseconds=" 30"> <vtl-overall num-active-tapes="0" num-reading-tapes="0" num-writing-tapes="0" readio. average-bytes="0" read-io.max-bytes="0" read-io.min-bytes="0" valid="true" writeio. average-bytes="0" write-io.max-bytes="0" write-io.min-bytes="0"/> </chronicle> <chronicle n-samples-per-poll="30" sample-date="04-03-2009 18:30:34" sample-timeseconds=" 30"> <vtl-overall num-active-tapes="0" num-reading-tapes="0" num-writing-tapes="0" readio. average-bytes="0" read-io.max-bytes="0" read-io.min-bytes="0" valid="true" writeio. average-bytes="0" write-io.max-bytes="0" write-io.min-bytes="0"/> </chronicle> <chronicle n-samples-per-poll="30" sample-date="04-03-2009 18:45:35" sample-timeseconds=" 30"> <vtl-overall num-active-tapes="0" num-reading-tapes="0" num-writing-tapes="0" readio. average-bytes="0" read-io.max-bytes="0" read-io.min-bytes="0" valid="true" writeio. average-bytes="0" write-io.max-bytes="0" write-io.min-bytes="0"/> </chronicle> </statistics> </response>

Figure 56. ptmon -node_vtl_statistics -hours <hours> output

ptmon -version
This command displays the version of the build of the local ProtecTIER installation. pt-version is the major version release

Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <version-info> <version build="0.0.0" pt-version="2.2.0.TEST1"/> </version-info> </response>

Figure 57. ptmon -version output

102

IBM System Storage TS7600 with ProtecTIER: Users Guide

ptcli
The following section describes how to query the ProtecTIER server through the CLI using ptcli. The ptcli is loaded during the installation of ProtecTIER software. Make sure you are in this directory when running ptcli commands from the command prompt.

Usage
Use the ptcli command to query the system via the command line interface (CLI), receive various statistics about the ProtecTIER system, and issue commands as available in the interface. This information can provide valuable insight to the administrator on the performance, capacity, configuration and operation of the system, and can be accessed by other management applications. The ptcli command is issued from the command line as follows: ./ptcli <--parameter> <--server options> <--parameter options> <variables> <-processing options>

Parameters and options


AddCartridges Adds cartridges to the library. name <NAME> Specify the library name (taken from the Libraries output). cartridges <NUM> Specify the number of cartridges. maxcartsize <NUM> Specify the maximum cartridge growth size in megabytes. This is optional. The default is no limit. seed <SEED> Specify the barcode seed. AddClustermember Adds a node to the cluster. addip <IP> Specify the external IP address of the node to add to the cluster. AddLibrary Creates a new library. name <NAME> Specify the library name (taken from the Libraries output). slots <NUM> Specify the number of slots. This is optional. The default is: 0 imexp <NUM> Specify the number of import and export. This is optional. The default is: 8 libtype <NAME> Specify the library type (taken from the LibrariesTypes output).

Chapter 10. Managing and monitoring ProtecTIER through the CLI

103

robot <X, Y> Specify a list of robot assignments in the form of X, Y (for example, X=node external IP address and Y=port). drivemodel <NAME> Specify the tape drive model (taken from the DriveModels output). drives <X, Y, Z> Specify a list of drive assignments in the form of X, Y, Z (for example, X=number of drives, Y=node external IP address, Z=port). Cartridgeinfo Prints information about specific cartridges in the library. The list is sorted by barcode. name <NAME> Specify the library name (taken from the Libraries output). from <NUM> Specify the number of cartridges before the first printed cartridge in the list of cartridges (taken from the NumberofCartridges output). count <NUM> Specify the maximum number of cartridges in the output. CreateRepository Creates a new repository on a node. name <NAME> Specify the repository name. system <NAME> Specify the system name. peak <NUM> Specify the maximum number of cartridges in the output. ratio <NUM> Specify the deduplication ratio. raid <X, Y, Z> Specify the meta-data raid configuration in the form of X, Y, Z (for example, X=Type, Y=Members, Z=Disk size in gigabytes take from the RaidConfigurations output). metadata <MOUNT_POINTS> Specify a list of GFS mounted file systems that will be used to store ProtecTIER repository meta-data. This is optional. userdata <MOUNT_POINTS> Specify a list of GFS mounted file systems that will be used to store ProtecTIER repository users data. This is optional. DriveModels Prints information about the supported tape drive models. libtype <NAME> Specify the library type. Libraries Prints the list of libraries on the repository. LibraryInfo Prints information about a specific library in the repository.

104

IBM System Storage TS7600 with ProtecTIER: Users Guide

name <NAME> Specify the library name (take from the Libraries output). Librarytypes Prints information about the supported library types. NodeVtlStatistics Prints the statistics history about the local host. hours <NUM> Specify the number of statistics hours included in the output. By default, the output should include four chronicles (statistics records) per hour (if uptime is greater than or equal to hours). NumberofCartridges Prints the number of cartridges in a library. name <NAME> Specify the library name (taken from Libraries output). RaidConfigurations Prints information about the supported raid configurations. Rpositorystatistics Prints the repository statistics. ServerVersion Prints the server version.

Server options
Server options are used for connection to the management server. Note: Administrator privileges are required for configuration operations. ip <IP> Specify the IP address of the management server. port <PORT> Specify the port of the management server. This is optional. The default is: 3501. username <NAME> Specify the username for the login. password <PASSWORD> Specify the password for the login. force Force the login if another administrator is already logged in. This is optional.

Processing options
You can specify the following processing options at the end of the command string: d <debug level> Specify the debug level to print log messages to the console. Choices for the debug level are as follows: v SEVERE v WARNING
Chapter 10. Managing and monitoring ProtecTIER through the CLI

105

v ALL f <logfile> Specify the name (with full path) to use for the log file name. The default is: c:\Documents and Settings\hanoch\cli0.log . h v Prints this message and exits. Prints the version information and exits.

ptcli responses
ptcli responses always appear in a well structured XML document printed. The XML always has the same root element: response with attribute status which may have the values success or failed. The response element displays the reply as a child element on success and, in this case, returns an exit code of zero to the shell. If status is failed the response element has a single child element: error with attributes description (a human readable string) and a non-zero code value. The same value is returned to the shell. The code value is also returned as the PTmon exit code and enables grouping of errors to general types (RPC error, argument error, etc.)

Examples - on failure
Calling to DriveModels without --libtype
<?xml version="1.0" encoding="UTF-8" ?> <response status="failed"> <error code="3" description="Missing required option --libtype" /> </response>

Figure 58. Failed Response for Calling to DriveModels without --libtype

Calling to a server without running VTFD


<?xml version="1.0" encoding="UTF-8" ?> <response status="failed"> <error code="3" description="Management server 168.159.150.60 is not responding." /> </response>

Figure 59. Failed Response for Calling to DriveModels without --libtype

Examples - on success
Success of Configuration Operations The XML for all configuration operation is the same, the only different is the name.
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <command host-name="beast" host-time="1243147115" host-time-string="24-May-2009 09:38" local-time="1243146789" local-time-string="24-May-2009 09:33" name="AddLibrary" /> </response>

Figure 60. Successful Response for Configuration Operations

Success of Monitoring Operations ./ptcli RepositoryStatistics --ip 168.159.151.62 --username ptoper

106

IBM System Storage TS7600 with ProtecTIER: Users Guide

--password ptoper
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <repository-statistics current-factoring-ratio="1.00" host-name="mir" repository-allocable-physical-storage-mb="724992" repository-free-physical-storage-mb="724992" repository-total-nominal-storage-mb="0" repository-total-physical-storage-mb="724992" repository-used-physical-storage-mb="0" host-time="1243147611" host-time-string="24-May-2009 09:46" local-time="1243147285" local-time-string="24-May-2009 09:41"/> </response>

Figure 61. Successful Response for RepositoryStatistics

./ptcli Libraries --ip 168.159.150.60 --username ptoper --password ptoper


<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <libraries-list host-name="mir" num-returned="2" host-time="1243147611" host-time-string="24-May-2009 09:46" local-time="1243147285" local-time-string="24-May-2009 09:41"> <library name="Lib1" unique-id="2199023256354" /> <library name="Lib2" unique-id="2199023256454" /> </libraries-list> </response>

Figure 62. Successful Response for Libraries

./ptcli LibraryInfo --ip 168.159.151.62 --username ptoper --password ptoper --name Pisa_Parma_24X7 without active drives
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <library-info host-name="parma" library-name="Pisa_Parma_24X7" library-unique-id="2199023265953" num-total-drives="30" host-time="1243147611" host-time-string="24-May-2009 09:46" local-time="1243147285" local-time-string="24-May-2009 09:41"> <active-drives num-returned="0" /> </library-info> </response>

Figure 63. Successful Response for LibraryInfo without Active Drive

./ptcli LibraryInfo --ip 168.159.151.62 --username ptoper --password ptoper --name Pisa_Parma_24X7 with active drives

Chapter 10. Managing and monitoring ProtecTIER through the CLI

107

<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <library-info host-name="parma" library-name="Pisa_Parma_24X7" library-unique-id="2199023265953" num-total-drives="30" host-time="1243147611" host-time-string="24-May-2009 09:46" local-time="1243147285" local-time-string="24-May-2009 09:41"> <active-drives num-returned="12"> <drive lea="0" loaded-cartridge-barcode="001025" node-id="1" read-rate-mb-per-second="0" write-rate-mb-per-second="4" /> <drive lea="2" loaded-cartridge-barcode="001024" node-id="1" read-rate-mb-per-second="0" write-rate-mb-per-second="5" /> <drive lea="8" loaded-cartridge-barcode="001028" node-id="1" read-rate-mb-per-second="0" write-rate-mb-per-second="3" /> <drive lea="10" loaded-cartridge-barcode="001027" node-id="1" read-rate-mb-per-second="0" write-rate-mb-per-second="2" /> <drive lea="14" loaded-cartridge-barcode="001022" node-id="1" read-rate-mb-per-second="0" write-rate-mb-per-second="5" /> <drive lea="18" loaded-cartridge-barcode="001021" node-id="1" read-rate-mb-per-second="0" write-rate-mb-per-second="8" /> <drive lea="7" loaded-cartridge-barcode="001018" node-id="2" read-rate-mb-per-second="0" write-rate-mb-per-second="6" /> <drive lea="17" loaded-cartridge-barcode="001019" node-id="2" read-rate-mb-per-second="0" write-rate-mb-per-second="6" /> <drive lea="19" loaded-cartridge-barcode="001026" node-id="2" read-rate-mb-per-second="0" write-rate-mb-per-second="4" /> <drive lea="21" loaded-cartridge-barcode="001020" node-id="2" read-rate-mb-per-second="0" write-rate-mb-per-second="5" /> <drive lea="25" loaded-cartridge-barcode="001030" node-id="2" read-rate-mb-per-second="0" write-rate-mb-per-second="0" /> <drive lea="27" loaded-cartridge-barcode="001029" node-id="2" read-rate-mb-per-second="0" write-rate-mb-per-second="4" /> </active-drives> </library-info> </response>

Figure 64. Successful Response for LibraryInfo with Active Drives

./ptcli NumberOfCartridges --ip 168.159.150.60 --username ptadmin --password ptadmin --force --name Lib1
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <library host-name="mir" name="Lib1" num-configured-cartridges="20" host-time="1243147611" host-time-string="24-May-2009 09:46" local-time="1243147285" local-time-string="24-May-2009 09:41" unique-id="2199023256354" /> </response>

Figure 65. Successful Response for NumberofCartridges

./ptcli CartridgeInfo --ip 168.159.150.60 --username ptadmin --password ptadmin --force --name Lib1 --from 0 --count 200

108

IBM System Storage TS7600 with ProtecTIER: Users Guide

<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <cartridges-information host-name="mir" library-name="Lib1" library-unique-id="2199023256354" num-returned="20" host-time="1243147853" host-time-string="24-May-2009 09:50" local-time="1243147527" local-time-string="24-May-2009 09:45"> <cartridge barcode="000000" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000001" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000002" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000003" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000004" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000005" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000006" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000007" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000008" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000009" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000010" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000011" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000012" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000013" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000014" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000015" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000016" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000017" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000018" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000019" early-warning-reported="false" nominal-size-mb="0" /> </cartridges-information> </response>

Figure 66. Successful Response for CartridgeInfo

./ptcli NodeVtlStatistics --ip 168.159.150.60 --username ptadmin --password ptadmin --force --hours 1

Chapter 10. Managing and monitoring ProtecTIER through the CLI

109

<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <statistics host-name="mir" num-returned="1" host-time="1243147853" host-time-string="24-May-2009 09:50" local-time="1243147527" local-time-string="24-May-2009 09:45"> <chronicle n-samples-per-poll="30" sample-date="06-05-2009 15:08:15" sample-time-seconds="30"> <vtl-overall num-active-tapes="0" num-reading-tapes="0" num-writing-tapes="0" read-io.average-bytes="0" read-io.max-bytes="0" read-io.min-bytes="0" valid="true" write-io.average-bytes="0" write-io.max-bytes="0" write-io.min-bytes="0" /> </chronicle> </statistics> </response>

Figure 67. Successful Response for NodeVtlStatistics

./ptcli ServerVersion --ip 168.159.150.60 --username ptoper --password ptoper


<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <version-info host-name="mir" host-time="1243147853" host-time-string="24-May-2009 09:50" local-time="1243147527" local-time-string="24-May-2009 09:45"> <version build="7.113.2" pt-version="2.2.0.TESTING10013" /> </version-info> </response>

Figure 68. Successful Response for ServerVersion

./ptcli LibraryTypes --ip 168.159.150.60 --username ptoper --password ptoper


<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <version-info host-name="mir" host-time="1243147853" host-time-string="24-May-2009 09:50" local-time="1243147527" local-time-string="24-May-2009 09:45"> <version build="7.113.2" pt-version="2.2.0.TESTING10013" /> </version-info> </response>

Figure 69. Successful Response for LibraryTypes

./ptcli DriveModels --ip 168.159.150.60 --username ptoper --password ptoper --libtype TS3500
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <drive-models host-name="beast" host-time="1243147853" host-time-string="24-May-2009 09:50" local-time="1243147527" local-time-string="24-May-2009 09:45" num-returned="1"> <drive-model name="ULT3580-TD3" /> </drive-models> </response>

Figure 70. Successful Response for DriveModels

./ptcli RaidConfigurations--ip 168.159.150.60 --username ptadmin --password ptadmin (Requires administrator priviliges)

110

IBM System Storage TS7600 with ProtecTIER: Users Guide

<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <raid-configurations host-name="beast" host-time="1243148247" host-time-string="24-May-2009 09:57" local-time="1243147921" local-time-string="24-May-2009 09:52" num-returned="18"> <raid-configuration members="2+2" type="FC-10K" /> <raid-configuration members="3+3" type="FC-10K" /> <raid-configuration members="4+4" type="FC-10K" /> <raid-configuration members="5+5" type="FC-10K" /> <raid-configuration members="6+6" type="FC-10K" /> <raid-configuration members="8+8" type="FC-10K" /> <raid-configuration members="2+2" type="FC-15K" /> <raid-configuration members="3+3" type="FC-15K" /> <raid-configuration members="4+4" type="FC-15K" /> <raid-configuration members="5+5" type="FC-15K" /> <raid-configuration members="6+6" type="FC-15K" /> <raid-configuration members="8+8" type="FC-15K" /> <raid-configuration members="2+2" type="SATA-7.2K" /> <raid-configuration members="3+3" type="SATA-7.2K" /> <raid-configuration members="4+4" type="SATA-7.2K" /> <raid-configuration members="5+5" type="SATA-7.2K" /> <raid-configuration members="6+6" type="SATA-7.2K" /> <raid-configuration members="8+8" type="SATA-7.2K" /> </raid-configurations> </response>

Figure 71. Successful Response for RaidConfigurations

Note: Responses may vary based on your installation.

Chapter 10. Managing and monitoring ProtecTIER through the CLI

111

112

IBM System Storage TS7600 with ProtecTIER: Users Guide

Chapter 11. Managing users


ProtecTIER Manager enables you to create user accounts with different permission levels for accessing and configuring your ProtecTIER system.

Permission levels
The ProtecTIER system supports the following permission levels: v Administrator has full access to the ProtecTIER system. Note: Only one Administrator can be logged into the ProtecTIER system at a time. If you log in as an Administrator while another Administrator is already logged in, a notification pane is displayed informing you who is logged in and offering to force that Administrator to log out. v Operator can access ProtecTIER Manager monitoring screens and perform the following tasks: Toggle cartridges between read/write and read-only modes. For more information, see Switching cartridges to read-only mode on page 69. Set the HyperFactor mode for libraries. For more information, see Changing the HyperFactor mode on page 125. Reset virtual tape drives and robots. For more information, see Resetting devices on page 127. Unload and moving cartridges from virtual tape drives. For more information, see Unloading and moving cartridges on page 127. v Monitor can only access ProtecTIER Manager monitoring screens. For more information, see Chapter 9, Monitoring ProtecTIER, on page 77.

Adding user accounts


ProtecTIER Manager enables you to add user accounts, which are each assigned a permission level. 1. Choose System > Users management. The Users Management dialog is displayed.

Copyright IBM Corp. 2008, 2009

113

Figure 72. Users Management dialog

2. Click Add. The Add account dialog is displayed.

Figure 73. Add account dialog

3. In the User name field, enter a username for the account. 4. In the New password field, enter a password for the account. 5. In the Verify password field, reenter the password that you entered in the New password field. 6. In the Permission field, select a permission level.

114

IBM System Storage TS7600 with ProtecTIER: Users Guide

7. Click Ok. The Add account dialog closes and the account is added to the ProtecTIER system. Note: Delete a user account by selecting the user account from the User Account list and clicking Remove.

Chapter 11. Managing users

115

116

IBM System Storage TS7600 with ProtecTIER: Users Guide

Chapter 12. Troubleshooting


Errors that occur in your ProtecTIER system can be monitored using the Alerts dialog and the Event Log dialog. All errors within the ProtecTIER system should be reported to IBM Support. IBM Support can guide you in determining the cause of the error and finding a solution. In addition, the Check and recover wizard, included in ProtecTIER Manager, can find and repair some errors.

Viewing the alerts and events log windows


If an error occurs, the Alerts button on the bottom-right of the View pane turns red and features a blinking exclamation mark. Click Alerts to view the list of error events in the Alerts Log dialog.

Figure 74. Alerts log

Click Events Log on the bottom-right of the View pane to view all the events occurring in the ProtecTIER system.

Copyright IBM Corp. 2008, 2009

117

The Alerts Log and Events Log dialogs only display information for one node at a time. In addition, the Alerts Log and Events Log dialogs only display up to 200 alert events at one time. Navigate to a previous set of 200 alert events by clicking Previous lines. Navigate to a later set of 200 alert events by clicking Next lines. Note: View the error log directly on a ProtecTIER server by opening the /pt_work/log/vtf_event.log file. View the alerts log by opening the /pt_work/log/vtf_error.log file.

Wizard error messages


ProtecTIER Manager wizards feature a Message area to inform you of issues that relate to each wizard screen.

Figure 75. Message area

Messages can be of the following types:

You cannot continue the wizard until this problem is resolved.

You can continue the wizard without resolving this issue, but it is not recommended.

118

IBM System Storage TS7600 with ProtecTIER: Users Guide

Generating a problem report


IBM Support may request that you generate a service report detailing the status of your ProtecTIER system. Service report files can be attached to a support ticket and sent to IBM Support. Service reports can only be generated for one node at a time. 1. In the Nodes pane, select a node. 2. Choose Node > Create problem report. The Create problem report dialog box is displayed. 3. Enter the appropriate information in each of the fields and click Ok. A confirmation message box is displayed. 4. Click Yes. The ProtecTIER system downloads the report files from the ProtecTIER server to the ProtecTIER Manager workstation and the Create problem report wizard Add report files pane is displayed. Note: Optionally click Add to browse for additional files to add to the report. 5. Click Ok. A standard save dialog box is displayed, enabling you to save the report .zip file. 6. Click Save. The report file is saved to the selected location. 7. If the cluster contains a second node, repeat steps 1 though 6 for the second node in the cluster. Note: a. Generate a service report directly on a ProtecTIER server by typing the /opt/dtc/app/sbin/report_problem command. b. Perform a system check on the server by typing sosreport. The sosreport operation is time-consuming and should only be used when you are directed to do so by IBM Support.

Creating a long-term statistics report


If you want IBM to analyze your system throughput over time, create a long-term statistics report to attach to a support ticket. Note: You can only create a long-term statistics report for one node at a time. 1. In the Nodes pane, select a node. 2. Choose Node > Create and download long term statistics. A confirmation message box is displayed. 3. Click Yes. The long-term statistics report file is created on the ProtecTIER server and a standard save dialog box is displayed. 4. Save the file on the ProtecTIER Manager workstation.

Turning on the WTI power switch outlets


If both cluster nodes have been powered off and their power switch outlets are off, bring the ports back to on by pressing and holding down the Default button for three seconds. All IPS power outlets will be toggled On or Off.

Chapter 12. Troubleshooting

119

Modifying port attributes


If one of your front-end fibre channel links is down, it may be because the attributes of that port do not fit the setup of the backup environment. Modify the port attributes from ProtecTIER Manager. 1. In the Nodes pane, select a node. 2. Choose Nodes > Port attributes. The Port attributes wizard Welcome screen is displayed. 3. Click Next. The Port Details screen is displayed.

Figure 76. Port Details screen

4. In Link speed column, click the down-arrow to select a link speed from the dropdown list. The options are as follows: v Auto v 1 GB v 2 GB v 4 GB 5. In the Topology column, click the down-arrow to select a network topology from the dropdown list. The options are as follows: v LOOP - Fibre channel-arbitrated loop v P2P - Point-to-point

120

IBM System Storage TS7600 with ProtecTIER: Users Guide

6. Click Next and Finish. The new port attributes are set.

Removing and adding cluster members


In some troubleshooting scenarios, such as deleting a ProtecTIER repository, you may be asked to remove one of the nodes from a two-node cluster, and later add it back. If you have a two-node cluster, you first need to remove one of the cluster members before deleting the repository. After you delete the repository and create a new repository in its place, add the cluster member back.

Removing a cluster member


You can only remove a node from a cluster if the ProtecTIER service on the node is down. If there is only one node in the cluster, that node cannot be removed from the cluster. If you remove a node on which VT service devices are assigned, the devices remain offline and unassigned until they are assigned to an active cluster member node. If there are cartridges loaded into drives on that node, the cartridges are automatically unloaded. Attention: If you want to remove a cluster member to which tape drives are assigned, it is recommended that you first reassign the tape drives. Nodes that have robots assigned to them cannot be removed from a cluster until the robot is reassigned. For more information, see Reassigning devices on page 62. 1. In the Nodes pane, select the node that you want to remove from its cluster. 2. Choose Node > Stop ProtecTIER service. You are prompted to enter your username and password. 3. Enter your username and password and click Ok. The ProtecTIER service stops for the selected node and you are automatically logged out. 4. In the Systems tab of the Navigation pane, select a cluster. 5. Click Login. You are prompted for your username and password. 6. Enter your username and password and click Ok. You are logged in. 7. Verify that the selected node is offline. 8. Choose Cluster Management > Remove cluster member. The Remove cluster member wizard Welcome screen is displayed. 9. Click Next. The Node selection screen is displayed.

Chapter 12. Troubleshooting

121

Figure 77. Node Selection screen

10. In the Node IP field, select the node that you want to remove from the cluster. 11. Read the instructions and select the I read the warnings above and I agree to continue checkbox. 12. Click Next and Finish. The Remove cluster member wizard closes and the selected node is removed from the cluster.

Adding a cluster member


1. In the Systems tab of the Navigation pane, select a cluster. 2. Choose Cluster Management > Add Cluster member. The Add cluster member wizard Welcome screen is displayed. 3. Click Next. The Node Selection screen is displayed.

122

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 78. Node Selection screen

4. In the Node IP field, enter the IP address of the node you want to associate with the cluster or select the IP address from the dropdown list. 5. Click Next and Finish. The Add cluster member wizard closes and the node is added to the selected cluster.

Changing World Wide Names for a node


After replacing HBAs on a node, or replacing a whole node, you may want to change the World Wide Names (WWN) for the HBAs to match the names from the previous hardware. This minimizes the disruption to the backup application. ProtecTIER enables you to do this using the wwnutil utility from within the Linux shell environment. The wwnutil utility: v Only works with Emulex HBAs v Does not perform a duplication check for name changes v Does not maintain a record of the changes made once the changes have been confirmed It is therefore recommended that you maintain records of the WWNs in order to make sure that WWNs are not duplicated when they are changed.
Chapter 12. Troubleshooting

123

Note: You must have root permission to use the wwnutil utility. 1. From the node server working directory, type service vtfd stop to stop the ProtecTIER service on the node. 2. Type /opt/dtc/app/util/wwnutil. 3. Type 2 to edit a WWN by port number. 4. Type a port number. 5. Type a node name. 6. Type a port name. 7. Type m to return to the wwnutil main menu. 8. Type 4 and then c to accept the name change. The WWN is changed. 9. Type service vtfd start to restart the node server. After the name change has been confirmed, the list of WWNs reflects the new name, and the name change is no longer registered as a change to the system.

Common troubleshooting tasks


The following is a list of miscellaneous tasks that IBM Support may ask you to perform during the troubleshooting process. Attention: These tasks should not be performed unless you are directed to do so by IBM Support. v Disabling defragmentation - Enables you to stop the defragmentation process. For more information, see Disabling defragmentation. v Disabling compression - Enables you to stop the data compression process. For more information, see Disabling compression on page 125. v Changing the HyperFactor mode - Enables you to stop the HyperFactoring process. For more information, see Changing the HyperFactor mode on page 125. v Modifying the trace buffer - Enables you to dump or reset the trace buffer, or to change the trace settings. For more information, see Modifying the trace buffer on page 125. v Resetting devices - Enables you to reset a robot or tape drive in a virtual library. For more information, see Resetting devices on page 127. v Unloading and moving cartridges - Enables you to manually move virtual cartridges between slots and tape drives. For more information, see Unloading and moving cartridges on page 127.

Disabling defragmentation
The ProtecTIER system automatically defragments fragmented repository disk space as a background task at a rate that does not cause the system to slow down. Stop defragmentation to free the resources used by the defragmentation process. 1. Choose Repository > Defragmentation control. The Defragmentation control dialog is displayed. 2. Select Disable defragmentation and click Ok. The Defragmentation control pane closes and defragmentation is disabled. Note: Selecting Enable defragmentation in the Defragmentation control pane resumes system defragmentation.

124

IBM System Storage TS7600 with ProtecTIER: Users Guide

Disabling compression
Under normal circumstances, the ProtecTIER system compresses data. Stop compression on a specific virtual library to free the resources usually demanded by the compression process. 1. Choose ProtecTIER VT > ProtecTIER VT Library > Set compression type. The ProtecTIER compression mode dialog is displayed. 2. Select Disable compression and click Ok. The ProtecTIER compression mode dialog closes and compression is stopped. Note: Selecting Enable compression in the ProtecTIER compression mode dialog box resumes data compression.

Changing the HyperFactor mode


By default, ProtecTIER factors all new incoming data, detecting recurring data and storing only the data segments that have not previously been written to the repository. You can change the default HyperFactor mode for each library. 1. Choose VT > VT Library > Set HyperFactor mode. The ProtecTIER VT HyperFactor mode dialog is displayed.

Figure 79. ProtecTIER VT HyperFactor mode dialog

2. Select one of the following options, as directed by IBM Support: v Hyperfactor enabled - HyperFactor operates as normal. v HyperFactor disabled - HyperFactor stops. When you restart HyperFactor, the HyperFactor process proceeds as normal based on the data stored from before HyperFactor stopped. v Baseline - HyperFactor stops factoring incoming data and uses the newly stored non-factored data as the reference for factoring new data after Hyperfactor is resumed. 3. Click Ok. The ProtecTIER VT HyperFactor mode dialog closes and HyperFactor stops.

Modifying the trace buffer


The ProtecTIER system stores run-time information in a cyclic memory buffer. IBM Support may direct you to dump the trace buffer for analysis, set the trace recording levels, or reset the trace buffer. Note: You can only manage the trace buffer for one node at a time.
Chapter 12. Troubleshooting

125

Dumping the trace buffer


Dumping the trace buffer saves a file of the trace buffer contents to the ProtecTIER server. Attach this file to a support ticket to send to IBM Support. 1. In the Nodes pane, select a node. 2. Choose Node > Dump trace. A confirmation message box is displayed. 3. Click Yes. The trace buffer information is saved to the ProtecTIER server.

Setting the trace levels


The ProtecTIER system traces and records many types of operation information at various levels of detail. These trace levels are initially set in manufacturing. IBM Support might direct you to reduce the level of detail traced for certain components. This request is made so that system resources are freed up or to increase the level of detail for system components that are suspected to be problematic. 1. In the Nodes pane, select a node. 2. Choose Node > Set trace levels. The Set trace levels dialog is displayed.

Figure 80. Set trace levels dialog

3. Change the trace level settings, as directed by IBM Support. 4. Click Ok. The Set trace levels dialog box closes and the new trace levels are set.

126

IBM System Storage TS7600 with ProtecTIER: Users Guide

Resetting the trace buffer


Resetting the trace buffer empties the buffer. 1. In the Nodes pane, select a node. 2. Choose Node > Reset trace. A confirmation message box is displayed. 3. Click Yes. The trace buffer is reset.

Resetting devices
If a virtual robot or tape drive is locked, reset the device to break any existing SCSI reservations on the device. Attention: Resetting a robot or tape drive while the backup application is accessing the library can harm the backup operations. Do not reset a device unless directed to do so by IBM Support.

Resetting robots
1. In the Services pane, select a library. 2. Choose VT > VT Library > Reset robot. A confirmation message box is displayed. 3. Click Yes. The robot is reset.

Resetting tape drives


1. In the Services pane, select a library. 2. Click the Drives tab. 3. Select a drive. 4. Choose VT > VT Drive > Reset drive. A confirmation message box is displayed. 5. Click Yes. The tape drive is reset.

Unloading and moving cartridges


Attention: Manual unloading and moving of cartridges is not detected by your backup application and can result in the loss of synchronization between your backup application and ProtecTIER. Furthermore, unloading or moving cartridges while the backup application is using the library can harm the backup operations. Do not unload or move a cartridge manually unless directed by IBM Support.

Unloading cartridges
You must unload a cartridge from its drive to move it to a slot. 1. In the Services pane, select a library. 2. Click the Drives tab. 3. Select a drive that contains a loaded cartridge. . Note: Loaded drives are indicated with 4. Choose VT > VT Drive > Unload drive. A confirmation message box is displayed. 5. Click Ok. The drive is unloaded. Note: Unloaded drives are indicated with .

Chapter 12. Troubleshooting

127

Moving cartridges
To 1. 2. 3. move a cartridge: In the Services pane, select a library. Click the Drives tab. Select a drive that contains an unloaded cartridge. Note: When moving cartridges from a slot, select the Slot tab and select a slot that contains a cartridge. 4. Choose VT > VT Cartridge > Move cartridge. The Move cartridge dialog is displayed.

Figure 81. Move cartridge dialog

5. In the Destination Type field, select one of the following destinations: v Drive v Slot v Import / Export 6. In the Destination area, select one of the following options: v Next Available - The cartridge is placed in the next available location of the selected type. v Slot/Drive No. - The cartridge is placed in the slot or drive with the number specified in the field. The name of this field depends on your selection in the Destination Type field. 7. Click Ok. The cartridge is moved to the specified location.

Checking and repairing errors


Before attempting to check and recover errors using ProtecTIER Manager, make sure that the file systems are in a consistent state and do not report errors that require running fsck. Running ProtecTIER Managers check and recovery wizard on top of inconsistent file systems can harm the consistency of the repository.

Checking for errors requiring fsck


1. Open the /var/log/messages file. 2. Search for error messages of the following types:

128

IBM System Storage TS7600 with ProtecTIER: Users Guide

v GFS: fsid=<cluster name>:<file system name>: fatal filesystem consistency error v gfs_controlId[2905]: <file system name> finish: needs recovery jjd 0 nodeid 2 status 1 If any error messages of these types are found, run fsck on the file systems referenced by the error messages using the file systems volume names.

Determining a file systems volume name


1. Run gfs_tool df. Summary information for all GFS file systems in your repository is displayed. 2. Locate the desired file system names and determine their mount points. The following is an example output from gfs_tool df with the file system name in bold and mount point name italicized:
/mnt/fs_4 SB lock proto = "lock_dlm" SB lock table = "romeo_juliet:gfs_sda4_new" SB ondisk format = 1309 SB multihost format = 1401 Block size = 4096 Journals = 3 Resource Groups = 720 Mounted lock proto = "lock_dlm" Mounted lock table == "romeo_juliet:gfs_sda4_new" Mounted host data = "jid=0:id=589825:first=1" Journal number = 0 Lock module flags = 0 Local flocks = FALSE Local caching = FALSE Oopses OK = FALSE Type Total Used Free use% -----------------------------------------------------------------inodes 6 6 0 100% metadata 1296 17 1279 1% data 47081258 0 47081258 0%

3. Open etc/fstab. 4. Locate the mount points determined using gfs_tool df, and determine the corresponding logical volume names. The following is an example of the fstab entry format:
/dev/<volume group name>/<logical volume name> name> gfs defaults,noatime,nodiratime,noquota /mnt/<mount point 0 0

Running fsck
1. On one of the ProtecTIER nodes, type service vtfd stop to stop the ProtecTIER service. 2. Shut down the stopped node. 3. On the active node, type service vtfd stop. 4. Type service gfs stop to stop the GFS service. 5. Run gfs_fsck <logical volume name> for each of the problematic file systems. 6. Type service gfs start. 7. Type service vtfd start. 8. Restart the inactive node.

Chapter 12. Troubleshooting

129

Checking and repairing using ProtecTIER Manager


After any problematic file systems have been repaired, scan the ProtecTIER system for errors, and attempt to repair them, using the Check and recover wizard. Note: The check and recovery process is time-consuming and the ProtecTIER system goes offline for the duration of the process. It is therefore recommended that the Check and recover wizard only be used for severe problems.

Checking the system


1. Choose System > Check and recover. A confirmation message box is displayed. 2. Click Yes. The ProtecTIER system goes offline and scans itself. The Check and recover dialog is displayed with the results of the scan.

Figure 82. Check and recover dialog

The Diagnostic results pane displays each element of the ProtecTIER system in one of the following lists: v Positive checks - no errors. v ProtecTIER recoverable errors - has errors that the ProtecTIER system may be able to repair. v Support required errors - has errors that cannot be repaired by the ProtecTIER system without the assistance of IBM Support.

130

IBM System Storage TS7600 with ProtecTIER: Users Guide

In the Category sub-pane, filter the list contents by selecting individual categories. Categories that contain errors of the type ProtecTIER recoverable errors feature an empty checkbox.

Repairing the system


If the checking process discovers errors of the type ProtecTIER recoverable errors, attempt to repair the errors using ProtecTIER Manager. Attention: Make sure to allot sufficient down-time for system recovery. The recovery process is time-consuming and the ProtecTIER system goes offline for the duration of that process. 1. In the Categories sub-pane, select the checkbox for each category for which you want to repair errors. All list items of the type ProtecTIER recoverable errors in each selected category appear in the Selected errors to recover pane and are labeled with a red X. 2. Click Recover. ProtecTIER Manager attempts to repair the errors. Errors that are successfully repaired are labeled with a green checkmark. Errors that cannot be repaired remain labeled with a red X. Note: For assistance with errors that cannot be repaired, contact IBM Support.

Chapter 12. Troubleshooting

131

132

IBM System Storage TS7600 with ProtecTIER: Users Guide

Chapter 13. Disaster recovery operations


Disaster recovery is the process of recovering production site data in a remote location. In case of a disaster or a situation where the production (or primary) site has gone offline, the disaster recovery site can take the place of the production site until the primary site comes back online. When the primary site comes back online, replicated or newly created tapes can be moved back to the main production site using the failback process. Once you enter Disaster Recovery (DR) mode, all incoming replication and visibility switching activities from the production site to the disaster recovery site are blocked. When the primary site is rebuilt or replaced, you can then return the data to the primary site and continue backups and replication. If you have a situation where you must stop using the primary repository, i.e. the repository is down or has been destroyed, and you want to use the remote repository as your backup target, you must enter DR mode on the remote repository to start working with the remote site as the primary site.

Entering disaster recovery (DR) mode


To enter DR mode: 1. Via the Systems Management view, click on the repository of the disaster recovery site, i.e. the remote site. The repository must be defined as a destination in a grids pair, if not, an error message is displayed. 2. Select Replication > Disaster Recovery > Enter DR mode. 3. Type yes to confirm that you want to enter DR mode. An automatic procedure is executed that blocks incoming replication to the DR site. In addition, visibility switching is blocked. Note: If replication is not blocked, the safety of the data at the DR site cannot be guaranteed.

Working at the DR site


The cartridges that were created at the production site are in read only mode at the DR site. To work with the DR site as the new backup target, the backup application must have R/W permission. Thus, cartridges need to be locally created or must have gained ownership of the cartridges sometime in the past (see Principality). Principality is the privilege to write to a cartridge (i.e. set it to R/W mode). The principality of each cartridge belongs only to one repository in the grid, and, by default, principality belongs to the repository in which the cartridge was created. When the principality of a cartridge belongs to a repository that is down or has been destroyed, principality can be transferred by running a fail back policy at the DR site (see Failback policy on page 134). For further details, see Replacing the primary repository on page 135.

Copyright IBM Corp. 2008, 2009

133

Failback policy
Failback is the procedure for replicating back updated cartridges, new or old, from a DR site to the original (restored) production site to bring it up-to-date in case it was down, or to a new production system. If the primary repository was down and has been restored, you can return to working with the production site as the primary site and use the DR site as the remote, or secondary site. Define a failback policy on the remote repository and select all the cartridges that were used for backup during the time the primary repository was down. Note: The cartridges that originally came from the primary site do not need to be replicated because they were not changed at the DR site. The failback policy will transfer the principality of all the cartridges that belonged to the temporary primary repository at the DR site to the restored primary repository at the production site.

Creating a failback policy


Important: You must eject the cartridges from the library to the Shelf before creating a failback policy for these cartridges. If you do not eject the cartridges, they will not be valid for failback. To create a failback policy: 1. Select Replication > Disaster recovery > Fail back. The Fail back wizard welcome screen is displayed. 2. Click Next. The Properties screen is displayed. Type a unique name for the failback policy in the Policy name field. 3. Click Next. The Barcode ranges screen is displayed. 4. Enter the barcode range of the cartridges that you want to fail back to the old or replaced primary repository. 5. Click Add to validate and submit the defined barcode range. If the barcode range is invalid, an error message is displayed. 6. Click Next. The Validation Results screen is displayed:

134

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 83. Cartridge validation results

Click the Save report as... button if you want to save the validation summary report. Click Next to view the validation summary report.

Completing failback and leaving DR mode


Once you have finished creating a failback policy, manually execute the policy and wait for it to complete. Note: Do not run any backup activities on the restored repository until the operation is complete. Delete the failback policy from ProtecTIER Manager and exit the DR mode by selecting Replication > Disaster Recovery > Leave DR mode. You can now start working again with the restored repository.

Replacing the primary repository


Note: Be careful when replacing a repository that you do not replace a good repository. If the repository at the production site has been destroyed and cannot be repaired, you can replace it with a new repository. Follow the steps below in the order in which they appear: 1. Add a new repository to the grid if it does not already exist and is not a part of any other grid pair. See Adding a repository to a grid on page 72.
Chapter 13. Disaster recovery operations

135

2. Enter DR mode as described in Entering disaster recovery (DR) mode on page 133. 3. Run the Repository takeover wizard. Via the Grids Management view, select Grid > Repository takeover. Select the Unrecoverable repository from the drop-down list and select the new repository that you added to the grid as the Replacing repository (the new repository should appear in the drop-down list). Click Ok. Note: This operation is not reversible.

Figure 84. Repository takeover

When you run the Repository takeover wizard, the Grid Manager will internally do the following: a. Delete the current grid pair between the unrecoverable primary site and remote site (if you have not done this previously on your own). b. Remove the unrecoverable repository from the grid. c. Create a pair between the replacing repository at the new primary site and the remote site. d. Define a failback policy on the remote repository and add all the cartridges to the policy that you would like to be at the new primary site. For more information, see Creating a failback policy on page 134. Since you have replaced the primary repository with a new one, the failback policy will change the principality of the failed back cartridges to the new repository, even if the corrupted primary site was the owner, as opposed to the DR site being the owner. e. Complete the procedure as describe in Completing failback and leaving DR mode on page 135.

Assessing cartridge status and syncing with the catalog


The following section explains the process for assessing cartridge status and synchronizing the backup application catalog with the cartridges for disaster recovery. Before running a restore for disaster recovery, you must verify that the list of associated cartridges are completely replicated to the remote site, otherwise an earlier full backup image must be used for recovery. The easiest way to determine

136

IBM System Storage TS7600 with ProtecTIER: Users Guide

the time of the last full backup is if you have a specific time each day where your replication backlog is zero (i.e. there is no pending data to replicate and backups are not running). If this is not the case, you can assess the cartridges by recovering the backup application catalog and scanning it to find the last full backup where its associated cartridges completed replication.

Recovering the backup application catalog


There are several ways to obtain a copy of the catalog at the remote site: v From a catalog backup on a virtual cartridge that will be replicated to the remote site v From disk-based replication, or by other means If the catalog is backed up to a virtual cartridge, through the cartridge view of the library in ProtecTIER Manager, query each of the cartridges used for catalog backup to find the most recent sync dates marked on the cartridges. Assuming that there are multiple backup copies, you need to find the latest backup that finished replication. To recover the backup application catalog from a backup on a virtual cartridge, you must work with the replicated cartridges to get an updated copy of the catalog to the remote site: v Each cartridge has a Last sync time that displays the last time the cartridges data was fully replicated to the remote site. (The sync time will be updated during the replication, not only when the replication for this cartridge is finished.) v The cartridge marked with the most recent Last sync time date should be used to recover the backup application catalog. The procedure for recovering the selected catalog backup depends on the backup application and is documented in the backup application official documentation.

Recovering the data


Once recovered, scan the backup application catalog and search for the full backup image you want to recover: v Get the start and end backup time of the full backup image. v View the list of cartridges associated with this full backup. Via ProtecTIER Manager, generate the cartridges .csv file report by selecting Replication > Create and download statistics. The .csv file is created in the /pt_work directory and a popup message is displayed to download the file to your workstation. You can open the file with any spreadsheet application you desire (the default is Excel). The report which includes statistics for all the cartridges at the remote site, indicates whether or not the replica cartridge data is consistent with the associated sync timestamp (i.e. the current data on the tape represents what it was at the specified sync time). Compare between the last update time, which represents the last time the replica was updated, and the last sync point destination time. If the last update time is less than or equal to the last sync point destination time, the replica cartridge has consistent point in time. Otherwise, the cartridge is incomplete, or in-transit. If the cartridge has consistent point in time, ensure this time stamp is larger than the full
Chapter 13. Disaster recovery operations

137

backup image end time. This will indicate that the cartridge contains all the required data for this recovery operation. Otherwise, you will have to use a previous full backup image for recovery.

Figure 85. Cartridge status report (in Excel)

You may have a case where the cartridge sync point is after the backup start time, but before the end of the backup. This may happen in cases where replication is working in parallel to the backup. If the backup has many cartridges, the first cartridges may finish replicating before the backup ends and they get a sync point earlier than the backup end time. As such, if the last sync time flag on one (or more) of the cartridges indicates a time later than the backup start time, but earlier than the backup complete time, those cartridges need further inspection. Scan the backup application catalog for each of those cartridges and get the backup start time and the backup complete time. If the last sync time flag on all the cartridges indicates a time later than the backup complete time, your backup image was fully replicated. Remember: When processing the cartridge list to find a complete set of DR tapes, you must keep track of the date/time discrepancies. Compare the date/time values of the source master backup server and the source ProtecTIER system. The destination environment may be in a different time zone or may be set to the incorrect date/time and as such, unreliable. Thus, use the source date/time, rather than the destination sync time when comparing cartridge states to the backup catalog/database. The destination sync time should only be used to determine which cartridges are whole. In addition, there could be a time difference between the source backup server and the source ProtecTIER server. Your Administrator should be aware of the discrepancy, measure it regularly and communicate the delta to the DR Administrator or operator(s). For instance, if the backup server is 2 hours behind, a cartridge may have a sync time that precedes its backup complete time, i.e. it will appear as a previous, old backup. If there is uncertainty regarding the time differences, compare the nominal size of the cartridge to the Catalog/DB value as an additional (not a substitute) layer of verification.

138

IBM System Storage TS7600 with ProtecTIER: Users Guide

Appendix A. Recovery procedures


Recovery procedures for the TS7650G and TS7650 Appliance consist of the following steps: 1. Preparing to reload a node 2. Installing the Red Hat Enterprise Linux Advanced Platform operating system 3. Installing the RAS package 4. Recovering a server for use with the TS7650G 5. Recovering a server for use with the TS7650 Appliance

Preparing to reload a node


To reload a node, it must first be installed with the appropriate Red Hat operating system (5.2). If this is a standalone server that is being recovered, proceed to Installing the Red Hat Enterprise Linux Advanced Platform operating system. If this is a clustered system, and there is currently an operational running node, you must stop all of the functioning nodes activities before attempting to reload the node you are recovering. 1. Attach a graphics capable monitor and a USB keyboard to the working server, or use the KVM and TSSC console (if attached). If the feature code 2730 is installed in a TS7650 frame, then a KVM switch is present. Press the <PrtSc> key and select the system from the list. 2. From the login prompt, login with user ID root and password admin. If the root user ID is not available, use user ID ptadmin and password ptadmin. If the ptadmin password fails to work, get the correct password for user ID ptadmin from the customer. 3. From the command line, enter the following commands: v service vtfd stop Stopping this activity will avoid any possibility of corrupting meta data on the repositorys management file system, in case the recognition procedure encounters unexpected issues. 4. Verify that the ptconfigd service is running by issuing the command: service ptconfigd status

Installing the Red Hat Enterprise Linux Advanced Platform operating system
This section provides instructions for installing Red Hat Enterprise Linux Advanced Platform (version x86_64) on the TS7650 Appliance and TS7650G servers for the purpose of disaster recovery.

Establishing a server connection


Before installing Red Hat Linux (RHL), you must first establish a connection to the server by attaching a USB keyboard and a monitor directly to the server. If feature code 2730 is installed in a TS7650 frame, then a KVM switch is present. Press
Copyright IBM Corp. 2008, 2009

139

<PrtSc> and select the system from the list that is to be recovered. If the KVM is attached, proceed to Installing RHL, otherwise proceed to Attaching an external keyboard and monitor to the server.

Attaching an external keyboard and monitor to the server


Note: If the customer cannot supply a keyboard and monitor for configuration usage, see Appendix C, RSA connection, on page 167. 1. Plug a USB keyboard into one of the unused USB ports on the back of the server. 2. Plug a monitor into the video port on the back of the server. 3. Go on to Installing RHL.

Installing RHL
1. If not already powered on, power on the server. 2. Insert the Recovery DVD into the servers CD-ROM drive. 3. If the server is already powered on, press Ctrl+Alt+Del to reboot the server. Note: When the installation begins, a list of accessible disks is displayed. If any external devices appear in the list, disconnect them before continuing with the installation. (This includes the fibre connections to the QLogic adapters in slots 6 and 7. Label their locations and disconnect them from the server.) 4. When the Press F12 to Select Boot Device option appears on the screen, press F12. (See Figure 86 on page 141.)

140

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 86. Press F12 to select the boot device

When the boot sequence finishes, the Select Boot Device window opens and allows you to specify the CD-ROM drive as the first boot device. 5. From the Select Boot Device menu, highlight CD and press Enter. See Figure 87 on page 142. Note: You may be prompted to Select Boot Device more than once. If so, select CD again and press Enter.

Appendix A. Recovery procedures

141

Figure 87. Select CD as the boot device

The server reboots from the CD-ROM drive. 6. On the Red Hat Enterprise Linux 5 install options screen, type the following at the command line boot: prompt and then press Enter: linux ks=cdrom Note: Be sure to enter the command exactly as shown. If the command is entered incorrectly, RHL will not be properly configured to work with ProtecTIER and you will need to restart this procedure at Step 3. See Figure 88 on page 143.

142

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 88. Red Hat Enterprise Linux 5 screen

7. When prompted, verify that the installation process has not detected any external, backend disks. Disk /dev/sda is the internal disk. If this is the only disk displayed, type YES and press <Enter>. See Figure 89 on page 144. Note: If external disks are detected, label and disconnect the fibre channel cables that are attached to the disks (the fibre connections to the adapters in slots 6 and 7), then type YES and press <Enter>.

Appendix A. Recovery procedures

143

Figure 89. Verify attached disks

Note: The Red Hat Linux operating system should only be installed on internal disks. 8. Follow the next flow of screens to review the End User License Agreement. Press <Enter> to proceed to the next screen:

Figure 90. Review end user license agreement

9. Review end user license agreement. 10. Continue pressing <Enter> to read the next page:

144

IBM System Storage TS7600 with ProtecTIER: Users Guide

Figure 91. End User License Agreement

11. Once you have reached the end of the license agreement, type YES and press <Enter> to accept the terms of the license agreement or type NO to exit:

Figure 92. Accept the license agreement

12. When the installation is complete, the system will restart. During this time, remove the RHL installation DVD from the servers CD-ROM drive. Note: After the reboot completes, a message similar to the one below may display. If so, ignore the message. Memory for crash kernel (0x0 to 0x0) not within permissible range i8042.c: Cant read CTR while initializing i8042 Red Hat Nash version 5.1.19.6 starting. When the system reboot is complete, you should be at the localhost login prompt.

Appendix A. Recovery procedures

145

RAS package installation


The loading of the Red Hat Linux operating system overlays all the RAS, BIOS, and firmware scripts and utility rpms. The RAS package must be reloaded by an IBM Service Representative after reloading the Red Hat LINUX operating system. Contact your IBM Service Representative for assistance with this procedure. Important: TS7600 products depend on the RAS package to gather logs at the time of the failure and send a call home packet. When the RAS package is not installed, contact your local hardware support: http://www.ibm.com/planetwide.

Installing ProtecTIER for use with the TS7650G


The following section explains how to recover a server for use with the TS7650G.

Unpacking the ProtecTIER package


Log in and access the installation files to invoke the installation procedure. Before installing the ProtecTIER package, you must first establish a connection to the server by attaching a USB keyboard and monitor directly to the server. See Attaching an external keyboard and monitor to the server on page 140, or by using the KVM switch at the TSSC (if available).

Log in as root
1. If the TS7650G is not already powered on, power it on and allow the boot cycle to complete. 2. When the localhost login: prompt appears, login as root and type the password: admin.

Establish the installation directory


1. Insert the IBM System Storage ProtecTIER Enterprise Edition v2.3 CD and wait for the CD drive to stop blinking. 2. Type the following commands to create and mount the CD-ROM drive:
mkdir /mnt/cdrom

Note: If the following message is displayed, the directory already exists and you can continue to the next command: mkdir: cannot create directory /mnt/cdrom: File exists mount /dev/cdrom /mnt/cdrom The following output is displayed:
mount: block device /dev/cdrom is write-protected. mounting read-only

3. Type the following command to change the current directory to the local installation directory:
cd /mnt/cdrom <Enter>

4. From the CD, locate the following tar file, where <filename> indicates the version number and date: v List the files on the CD from command line: ls <Enter> v Locate the .tar file and copy it to the /install directory on the hard drive. Type the following command to copy the file:
cp <filename>.tar /install <Enter>

146

IBM System Storage TS7600 with ProtecTIER: Users Guide

5. Copy the cman-2.0.85-2.el5.x86_64.rpm file to the /install directory on the hard drive. Type the following command to copy the file:
cp cman-2.0.85-2.el5.x86_64.rpm /install <Enter>

6. Access the /install directory to update the RPM file. Type the following command to change the directory:
cd /install rpm -Uvh <Enter> <Enter>

Then type the command to apply the cman RPM:


cman-2.085-2.el5.x86_64rpm

7. Access the directory to which you copied the tar file (for example, type cd /install). 8. Type the following command to extract the installation files in the /install directory:
tar -xvf <tar filename>.tar <Enter>

The <tar filename> directory is created. 9. Type the following command to change to the <tar filename> directory. Perform the rest of the installation from this directory:
cd /install/<tar filename> <Enter>

Example: <tar filename>=PT_Linux_V2.3.0.0.x86_64 10. Type the following commands to unmount and eject the CD-ROM drive:
umount /dev/cdrom eject /dev/cdrom ./autorun <Enter> <Enter> <Enter>

11. Type the following command: The autorun utility will install the ProtecTIER application. The following message is displayed at the end of the installation:
The system will now reboot!

Press Enter at the prompt to reboot the system. The following message is displayed:
After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue...

12. After the system boots up, set the user to ptadmin by typing the command su - ptadmin (the default password is ptadmin). 13. Change the directories to the /opt/dtc/install directory. From the command line, run the following command:
cd /opt/dtc/install <Enter> <Enter>

14. Type the following command:


./ptconfig -replace -model=TS7560G

The following output is displayed. Note: If you are prompted, enter yes to stop the vtfd service. When prompted to select the node to be replaced, enter the proper node option number. This is especially important when replacing a 2-node system when both nodes are down. Only the valid options for replacement are displayed, i.e. if one of the nodes is running and accessible, only the option of replacing the node that is not running is displayed. In addition, if you are working with a 2-node system, all GFS and vtfd services must be stopped on the second node in order to continue replacing
Appendix A. Recovery procedures

147

the selected node. To stop the GFS and vtfd services on the second node, run the service vtfd stop and service gfs stop commands, respectively.
[root@localhost install]# ./ptconfig -replace -model=TS7650G Gateway Would you like to stop the VTFD service? (yes|no) yes Stopping services, please wait Stopping Cluster Services [ Done ] Services stopped Checking conditions... Checking BOM [ Done ] Checking for existing nodes [ Done ] Comparing mapped devices [ Done ] Checking NICs for Replication [ Done ] In order to continue the GFS & VTFD services on the remote node MUST be stopped. Are the GFS & VTFD services stopped on the remote node? (yes|no) yes Checking repository [ Done ] Checking local raid [ Done ] Checking conditions done Checking live nodes Model <TS7650G> [ Done ]

Option 1 ************************************************** node id : 2 hostname : bilbao ip : 168.159.151.145 Select option: 1 Recoverable static routes configuration found, would you like to restore it? (yes|no) yes Recovering Static Routes [ Done ] Configuring network [ Done ] Configuring Replication Network [ Done ] Restarting Network Service [ Done ] Stopping Remote VTFD [ Done ] Stopping cluster [ Done ] Configuring cluster [ Done ] Starting cluster [ Done ] Installing NTP [ Done ] Mounting file systems [ Done ] Restoring node ID [ Done ] Starting VTFD locally [ Done ] Starting VTFD remotely [ Done ] validation will start in 10 seconds Testing customer network connectivity [ Done ] Testing connectivity to the Default Gateway [ Done ] Getting number of nodes [ Done ] Testing NTP configuration [ Done ] Testing cluster's network speed [ Done ] Testing connectivity to other node in the cluster [ Done ] Testing fence ports [ Done ] Validation is about to execute a fence on 1 node in the cluster, the node will be forcefully shutdown and rebooted To Continue please type "fence test", or "q" to quit: q User aborted validation ended replace ended successfully

Note: Once the configuration is complete, a validation procedure runs automatically. Even if, for some reason, the validation fails, the procedure is not rolled back since the configuration completed successfully. 15. Once the information has been provided, proceed to Chapter 5, Managing nodes and clusters, on page 35 to ensure the node is displayed on the ProtecTIER Manager interface.

148

IBM System Storage TS7600 with ProtecTIER: Users Guide

Installing ProtecTIER for use with the TS7650 Appliance


The following section explains how to recover a server for use with the TS7650. Log in and access the installation files to invoke the installation procedure.

Log in as root
1. Connect or verify a USB keyboard and display are connected to the TS7650. 2. If the TS7650 is not already powered on, power it on and allow the boot cycle to complete. 3. When the localhost login: prompt appears, login as root and type the password: admin.

Establish the installation directory


1. Insert the IBM System Storage ProtecTIER Appliance Edition V2.3 CD and wait for the CD drive to stop blinking. 2. Type the following commands to mount the CD-ROM drive:
mkdir /mnt/cdrom <Enter>

Note: If the following message is displayed, the directory already exists and you can continue to the next command:
mkdir: cannot create directory '/mnt/cdrom': File exists

mount /dev/cdrom /mnt/cdrom <Enter> The following output is displayed:


mount: block device /dev/cdrom is write-protected. mounting read-only

3. Type the following command to change the current directory to the local installation directory:
cd /mnt/cdrom <Enter>

4. From the CD, locate the following tar file, where <filename> indicates the version number and date: v List the files on the CD from command line: ls <Enter> v Locate the .tar file and copy it to the /install directory on the hard drive. Type the following command to copy the file:
cp <filename>.tar /install <Enter>

5. Copy the cman-2.0.85-2.el5.x86_64.rpm file to the /install directory on the hard drive. Type the following command to copy the file:
cp cman-2.0.85-2.el5.x86_64.rpm /install <Enter>

6. Access the /install directory to update the RPM file. Type the following command to change the directory:
cd /install <Enter> <Enter>

7. Then type the command to apply the cman RPM:


rpm -Uvh cman-2.0.85-2.el5.x86_64.rpm

8. Access the directory to which you copied the tar file (for example, type cd /install). 9. Type the following command to extract the installation files in the /install directory:
tar -xvf <tar filename>.tar <Enter>

The <filename> directory is created.

Appendix A. Recovery procedures

149

10. Type the following command to change to the < tar filename> directory. Perform the rest of the installation from this directory:
cd /install/<filename> <Enter>

Example: <filename>=PT_Linux_V2.3.0.0.x86_64 11. Type the following command to unmount the CD-ROM drive:
umount /dev/cdrom <Enter>

12. Type the following command to eject the ProtecTIER installation CD from the CDROM drive:
eject ./autorun <Enter> <Enter>

13. Type the following command: 14. The autorun utility will install the ProtecTIER application. The following message is displayed at the end of the installation:
The system will now reboot!

Press <Enter> at the prompt to reboot the system. The following message is displayed:
After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue...

15. When the localhost login: prompt appears, login as root and type the password: admin 16. Set the user to ptadmin by typing the command su - ptadmin (the default password is ptadmin). 17. Change the directories to the /opt/dtc/install directory. From the command line, run the following command:
cd /opt/dtc/install <Enter>

18. The ProtecTIER configuration command set that is entered next is dependant on the amount of cache that is connected to the server. Use the guidelines below to determine the command to use: v If you are replacing the server on a 32 spindle appliance model, type the following command:
./ptconfig -replace -model=TS7650_DS4700_32_450 <Enter>

v If you are replacing the server on a 64 spindle appliance model, type the following command:
./ptconfig -replace -model=TS7650_DS4700_64_450 <Enter>

v If you are replacing the server on a 128 spindle appliance model, type the following command:
./ptconfig -replace -model=TS7650_DS4700_128_450 <Enter>

The following output is displayed. Note: If you are prompted, enter yes to stop the vtfd service. When prompted to select the node to be replaced, enter the proper node option number. This is especially important when replacing a 2-node system when both nodes are down. Only the valid options for replacement are displayed, i.e. if one of the nodes is running and accessible, only the option of replacing the node that is not running is displayed. In addition, if you are working with a 2-node system, all GFS and vtfd services must be stopped on the second node in order to continue replacing the selected node. To stop the GFS and vtfd services on the second node, run the service vtfd stop and service gfs stop commands, respectively.

150

IBM System Storage TS7600 with ProtecTIER: Users Guide

[root@localhost install]# ./ptconfig -replace -model=TS7650_DS4700_128_450 Would you like to stop the VTFD service? (yes|no) yes Stopping services, please wait Stopping Cluster Services [ Done ] Services stopped Checking conditions... Checking BOM [ Done ] Checking for existing nodes [ Done ] Comparing mapped devices [ Done ] Checking NICs for Replication [ Done ] In order to continue the GFS & VTFD services on the remote node MUST be stopped. Are the GFS & VTFD services stopped on the remote node? (yes|no) yes Checking repository [ Done ] Checking local raid [ Done ] Checking conditions done Checking live nodes Model <TS7650G> [ Done ]

Option 1 ************************************************** node id : 2 hostname : bilbao ip : 168.159.151.145 Select option: 1 Recoverable static routes configuration found, would you like to restore it? (yes|no) yes Recovering Static Routes [ Done ] Configuring network [ Done ] Configuring Replication Network [ Done ] Restarting Network Service [ Done ] Stopping Remote VTFD [ Done ] Stopping cluster [ Done ] Configuring cluster [ Done ] Starting cluster [ Done ] Installing NTP [ Done ] Mounting file systems [ Done ] Restoring node ID [ Done ] Starting VTFD locally [ Done ] Starting VTFD remotely [ Done ] validation will start in 10 seconds Testing customer network connectivity [ Done ] Testing connectivity to the Default Gateway [ Done ] Getting number of nodes [ Done ] Testing NTP configuration [ Done ] Testing cluster's network speed [ Done ] Testing connectivity to other node in the cluster [ Done ] Testing fence ports [ Done ] Validation is about to execute a fence on 1 node in the cluster, the node will be forcefully shutdown and rebooted To Continue please type "fence test", or "q" to quit: q User aborted validation ended replace ended successfully

Note: Once the configuration is complete, a validation procedure runs automatically. Even if, for some reason, the validation fails, the procedure is not rolled back since the configuration completed successfully. 19. Once the information has been provided, proceed to Chapter 5, Managing nodes and clusters, on page 35 to ensure the node is displayed on the ProtecTIER Manager interface.

Appendix A. Recovery procedures

151

DR replacing a two-node system with a single node configuration


The following section explains how to recover a server that was part of a two-node system and configure it as a single standalone node when you are using disk-based replication. This is done when you have a cluster at the local site with a single node system at the remote site. Note: This command should only be used when you are replacing a two-node system with a single node system that will not be upgraded to a two-node cluster. In such a scenario, the single node will fail to start after the replacement, since there is no connection to a WTI fence device. Adding a second node to this single node system may cause data corruption, as the fence device will not be used. Ensure that the WTI fence device is disconnected from the network. The commands syntax is:
./ptconfig -replace -model=<model> -dualBySingle

To replace a two-node system by a single node when using disk-based replication: 1. Connect or verify a USB keyboard and display are connected to the ProtecTIER server. 2. If the server is not already powered on, power it on and allow the boot cycle to complete. 3. When the localhost login: prompt appears, login as root and type the password: admin. 4. Insert the IBM System Storage ProtecTIER Enterprise Edition v2.3 CD and wait for the CD drive to stop blinking. 5. Type the following commands to create and mount the CD-ROM drive:
mkdir /mnt/cdrom

Note: If the following message is displayed, the directory already exists and you can continue to the next command: mkdir: cannot create directory /mnt/cdrom: File exists mount /dev/cdrom /mnt/cdrom The following output is displayed:
mount: block device /dev/cdrom is write-protected. mounting read-only

6. Type the following command to change the current directory to the local installation directory:
cd /mnt/cdrom <Enter>

7. From the CD, locate the following tar file, where <filename> indicates the version number and date: v List the files on the CD from command line: ls <Enter> v Locate the .tar file and copy it to the /install directory on the hard drive. Type the following command to copy the file:
cp <filename>.tar /install <Enter>

8. Copy the cman-2.0.85-2.el5.x86_64.rpm file to the /install directory on the hard drive. Type the following command to copy the file:
cp cman-2.0.85-2.el5.x86_64.rpm /install <Enter>

9. Access the /install directory to update the RPM file. Type the following command to change the directory:
cd /install <Enter>

152

IBM System Storage TS7600 with ProtecTIER: Users Guide

Then type the command to apply the cman RPM:


rpm -Uvh cman-2.085-2.el5.x86_64rpm <Enter>

10. Access the directory to which you copied the tar file (for example, type cd /install). 11. Type the following command to extract the installation files in the /install directory:
tar -xvf <tar filename>.tar <Enter>

The <tar filename> directory is created. 12. Type the following command to change to the <tar filename> directory. Perform the rest of the installation from this directory:
cd /install/<tar filename> <Enter>

Example: <tar filename>=PT_Linux_V2.3.0.0.x86_64 13. Type the following commands to unmount and eject the CD-ROM drive:
umount /dev/cdrom eject /dev/cdrom ./autorun <Enter> <Enter> <Enter>

14. Type the following command: The autorun utility will install the ProtecTIER application. The following message is displayed at the end of the installation:
The system will now reboot!

Press Enter at the prompt to reboot the system. The following message is displayed:
After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue...

15. After the system boots up, set the user to ptadmin by typing the command su - ptadmin (the default password is ptadmin). 16. Change the directories to the /opt/dtc/install directory. From the command line, run the following command:
cd /opt/dtc/install <Enter> <Enter>

17. Type the following command:


./ptconfig -replace -model=Generic -dualBySingle

The following output is displayed.

Appendix A. Recovery procedures

153

[root@localhost install]# ./ptconfig -replace -model=<model> -dualBySingle *** NOTICE *** By selecting the dualBySingle option you are converting this node. Once this action is complete this installed node must NEVER be a part of a 2 node Cluster. Converting to dual by single [ Done ] Stopping services, please wait Stopping Cluster Services [ Done ] Services stopped Checking conditions... Checking BOM [ Done ] Checking for existing nodes [ Done ] Checking NICs for Replication [ Done ] Checking repository [ Done ] Checking conditions done Checking live nodes Model <Generic> Option 1 ************************************************** node id : 1 hostname : compy ip : 168.159.150.107 [ Done ]

Option 2 ************************************************** node id : 2 hostname : bunny ip : 168.159.150.135 Select option: 2 Recoverable static routes configuration found, would you like to restore it? (yes|no) yes Recovering Static Routes [ Done ] Configuring network [ Done ] Configuring Replication Network [ Done ] Restarting Network Service [ Done ] Stopping cluster [ Done ] Configuring cluster [ Done ] Starting cluster [ Done ] Installing NTP [ Done ] Mounting file systems [ Done ] Restoring node ID [ Done ] Starting VTFD [ Done ] validation will start in 10 seconds Testing customer network connectivity [ Done ] Testing connectivity to the Default Gateway [ Done ] Getting number of nodes [ Done ] This is a 1 node cluster, will not test fencing validation ended replace ended successfully

Note: Once the configuration is complete, a validation procedure runs automatically. Even if, for some reason, the validation fails, the procedure is not rolled back since the configuration completed successfully.

Installing Grid Manager


The Grid Manager application is installed on a customer-designated ProtecTIER v2.3 server. IBM recommends installing Grid Manager at the replication destination site, so that the Grid Manager will remain available in a disaster recovery situation.

154

IBM System Storage TS7600 with ProtecTIER: Users Guide

Note: If you are not enabling replication, you do not need to install Grid Manager. Instead, go to Chapter 3, Installing ProtecTIER Manager, on page 27. 1. Log in to the ProtecTIER v2.3 server on which the Grid Manager application will reside: a. Connect a USB keyboard and monitor (if not already present) to the server. b. Verify that the server is powered-on: v If it is powered-on, go to step 2. v If it is not powered-on do so now, wait for the boot cycle to complete, then go to step 2. 2. At the login: prompt, log in with the ID root and the password admin. 3. Insert the IBM System Storage Replication Manager v2.3.0 CD into the servers CD-ROM drive. 4. When the CD-ROM drive light stops blinking, enter the command: mount /dev/cdrom /mnt/cdrom <enter> Note: If you receive the error message: No such file or directory, enter both of the commands below: mkdir /mnt/cdrom <enter> mount /dev/cdrom /mnt/cdrom <enter> The following output displays: mount: block device /dev/cdrom is write-protected. mounting read-only 5. Enter the command: cd /mnt/cdrom 6. Change to the installation directory. Enter the command: cd /Replication_Manager_V2.3.0.0/Linux <enter> 7. Start Grid Manager installation. Enter the following command: ./gm_installLinux64.bin <enter> The following messages display: Preparing to install... Extracting the JRE from the installer archive... Unpacking the JRE... Extracting the installation resources from the installer archive... Configuring the installer for this systems environment... Launching installer... Preparing CONSOLE Mode Installation... The Introduction screen displays. 8. Read the information on the screen, then press <enter> to continue. The Grid Manager Platform menu displays: Please define the type of platform the Grid Manager will run 1- ProtecTIER Node 2- Dedicated Linux server ENTER THE NUMBER OF THE DESIRED CHOICE: 9. Select option 1 and press <enter>. 10. When prompted for the first IP address of the GridManager, type the servers first replication IP address (Eth3) and press <enter>. 11. When prompted for the second IP address of the GridManager, type the servers second replication IP address (Eth4) and press <enter>.
Appendix A. Recovery procedures

155

The Pre-Installation Summary screen displays: Please Review the Following Before Continuing: Product Name: PTGridManager Install Folder: /opt/dtc/PTGridManager Link Folder: /opt/dtc Replication Manager first IP: x.xx.xxx.xxx (The IP address for Eth3) Replication Manager second IP: x.xx.xxx.xxx (The IP address for Eth4) Disk Space Information (for Installation Target): Required: 139,495,067 bytes Available: xxx,xxx,xxx bytes 12. Review the information, then press <enter> to continue. The Ready To Install screen displays: InstallAnywhere is now ready to install PTGridManager onto your system at the following location: /opt/dtc/PTGridManager 13. Press <enter> to start the installation. The Installing message displays. When the installation finishes the Installation Complete screen displays: Congratulations. PTGridManager has been successfully installed to: /opt/dtc/PTGridManager 14. Press <enter> to exit the installer. 15. Eject the CD-ROM from the servers CD-ROM drive. Enter the commands: cd / <enter> eject /dev/cdrom <enter> 16. Go to Chapter 3, Installing ProtecTIER Manager, on page 27.

Backing up the configuration files


Configuration files from the Grid Manager are automatically backed up and saved. Backups of the configuration files from Grid Manager are saved as a .zip file. The .zip file contains the /gm_work directory with all its sub-directories: configuration, data, and history, without the log files. When restoring Grid Manager, extract the .zip file and locate the grid data files grid.<x>.xml (where <x> represents the grid ID number) in the /gm_work/data directory. Automatic backups can be cancelled by deselecting the Backup configuration files option found on the Backup tab dialog under the Tools > Preferences menu. From the Preferences dialog, you can also specify the number of backup files to save (the default is 20). The backup is done by rotation on the saved files. For instance, the backup files are named consecutively from gm_backup.0 to gm_backup.20. When a new backup is generated, gm_backup.0 is renamed to gm_backup.1 and the new backup is saved as gm_backup.0. This continues until the backups reach the total number saved and the old backups are deleted. To manually back up the configuration files: 1. From the Grids Management view, select Grids Manager > Backup configuration files. The Backup configuration files dialog is displayed:

156

IBM System Storage TS7600 with ProtecTIER: Users Guide

2. Enter the customer name in the Customer name field to provide backup information and click Ok. A message is displayed that the backup .zip file was saved on the Grid Manager server in the /tmp directory. 3. Click Yes if you want to download the backup file to a specific directory or No to close the window. 4. If Yes, browse to the directory in which you want to save the backup configuration file and click Save. The file is saved to the respective directory and the Save window closes.

Analyzing and restoring the Grid Manager


This section describes the procedure for analyzing and restoring an inactive or lost Grid Manager server using ProtecTIER Manager. Note: Once the Grid Manager server is restored, you must make sure that the lost or inactive server is never reactivated. Reactivating a lost or inactive server may cause inconsistencies and may conflict with the restored server. The Grid Manager restore procedure is done grid by grid and can be done in either of the following ways: v Using an existing backup file: PtGridManager_<hostName>_<customerName>_time_ConfigurationBackup.zip Important: Use the most updated file determined by the newest time value. v Using an accessible repository that was once a member of a grid. Each Grid Manager has a unique signature ID which distinguishes it from all other servers. In addition, each grid has a unique configuration ID that determines the current layout of the grid, i.e. the repositories in the grid, the grid pairs, the DR sites, etc. Both the Grid Manager unique ID and the grid configuration ID are saved in the servers directory (/gm_work/...) and in the repositories. Prior to grid restoration, in the case of a given grid data file, the Grid Manager unique ID must be validated by the running Grid Manager and each repositorys configuration ID must be compared with the given grid data file. This validation and comparison steps are called the analysis phase, which is automatically done by the Grid Manager server. With a given replication IP address, the analysis phase is done with the respective repositorys grid data and all the other grid members. Once the analysis phase is done, a detailed table is displayed with the repository configuration ID comparison results. The final step is to restore the grid where the Grid Manager accepts the restored grid and starts communicating with the repositories.

Restoring the Grid Manager


The following steps describe the procedure for restoring the processed grid. Install a new Grid Manager server. If you are restoring a grid from a backup .zip file, extract the file and locate the grid data files in the /gm_work/data/ grid.<x>.xml where <x> represents the grid ID number. To restore a grid, log in to the new Grid Manager server.
Appendix A. Recovery procedures

157

1. Select Grid Manager > Restore grid. The Restore grid dialog is displayed. 2. Choose from one of the options listed to import the grid for analysis: v Import from file browse to the grid.<x>.xml file, if you are restoring a grid from a backup .zip file that has been extracted. v Import from repository enter the Replication IP address of the accessible repository that was previously a member of the grid. 3. Click Analyze grid. The Grid Manager attempts to communicate with the grids members (i.e. repositories). Note: If the running Grid Manager already contains a number of grids, and the restored grid does not match the Grid Manager unique ID, the analyze phase fails and an error is displayed that the imported grid does not belong to the respective Grid Manager.

Figure 93. Grid analysis

The following messages might be displayed during the grid analysis:

158

IBM System Storage TS7600 with ProtecTIER: Users Guide

Table 20. Grid analysis messages Message The repository was not accessible Meaning The Grid Manager failed to communicate with the specific repository and could not get the configuration ID. Recommended action Make sure the server status in the repository is up and running and all ports are well configured. Then, analyze the grid again.

Inconsistent grid member

Restoration is not recommended. Communication was successful, invalid configuration ID. Additional message follows the configuration is higher or different than expected. This could be caused by a old restored grid data file, an old backup, or a repository that does not belong to this grid. Communication was successful. This could be caused when the specific repository does not communicate with the restored Grid Manager during a new configuration layout. Comparison and validation was successful. None. The new Grid Manager will update the repository with the new configuration layout.

Old configuration ID was found

Empty message

Before restoring a grid, you can preview the grid layout by clicking on the Grid preview tab.

Appendix A. Recovery procedures

159

Figure 94. Previewing the grid layout

If all the repositories are accessible and validated successfully, click Restore. Continue restoring the remaining grids, if available.

160

IBM System Storage TS7600 with ProtecTIER: Users Guide

Appendix B. Creating file systems and expanding existing ones


If you are expanding the physical capacity of your repository, you may need to manually create file systems for the new physical capacity. In addition, you might need to create additional file systems, or extend existing file systems for repository meta data storage based on the output of the Plan repository increase.

Creating file systems


Perform the following steps, in the order that they appear, for each file system that you want to create: v Creating partitions v Creating physical volumes on page 163 v Creating volume groups on page 163 v Creating logical volumes on page 163 v Creating a Global File System (GFS) on page 164 v Creating mount points on page 164 v Adding file systems to fstab and mounting file systems on page 164 Note: You only need to create the set of file systems once. Even if you later delete the repository, you can recreate the repository using the existing file systems. You may, however, need to create additional file systems for expanding the repository, or you may need to expand the existing file systems.

Creating partitions
Create one partition on each device on the storage disk. Note: Your storage disk must be configured with the number of devices equal to the number of file systems you must create. 1. Log into a ProtecTIER node server. Open a Secured Shell (SSH) session to the node and log in using the user ID: root and password: admin. 2. From the command line, enter multipath -l. You receive a list of multipath devices in a format similar to the following:
# multipath -l mpath2 (3600a0b8000422e7200000536482c7a90) dm-10 IBM,1814 [size=4.1T][features=0][hwhandler=1 rdac] \_ round-robin 0 [prio=0][active] \_ 2:0:0:7 sdt 65:48 [active][undef] \_ round-robin 0 [prio=0][enabled] \_ 4:0:0:7 sdak 66:64 [active][undef] mpath23 (3600a0b8000421b2800000558483d8d4b) dm-15 IBM,1814 [size=1.0G][features=0][hwhandler=1 rdac] \_ round-robin 0 [prio=0][active] \_ 1:0:0:1 sdb 8:16 [active][undef] \_ round-robin 0 [prio=0][enabled] \_ 3:0:0:1 sdh 8:112 [active][undef] mpath1 (3600a0b8000422e7200000541482c7ae3) dm-13 IBM,1814 [size=4.1T][features=0][hwhandler=1 rdac]
Copyright IBM Corp. 2008, 2009

FAStT

FAStT

FAStT

161

\_ round-robin 0 [prio=0][active] \_ round-robin 0 [prio=0][active] \_ 2:0:0:9 sdy 65:128 [active][undef] \_ round-robin 0 [prio=0][enabled] \_ 4:0:0:9 sdao 66:128 [active][undef] mpath22 (3600a0b8000421b2800000556483d8d0f) dm-8 IBM,1814 [size=835G][features=0][hwhandler=1 rdac] \_ round-robin 0 [prio=0][active] \_ 1:0:0:11 sdaq 66:160 [active][undef] \_ round-robin 0 [prio=0][enabled] \_ 3:0:0:11 sdai 66:32 [active][undef] mpath0 (3600a0b8000421b6400000597482c9341) dm-21 IBM,1814 [size=4.1T][features=0][hwhandler=1 rdac] \_ round-robin 0 [prio=0][active] \_ 1:0:0:4 sdp 8:240 [active][undef] \_ round-robin 0 [prio=0][enabled] \_ 3:0:0:4 sdo 8:224 [active][undef]

FAStT

FAStT

Each device is named mpathN, where N is a number and can be found on the system as /dev/mapper/mpathN. 3. Enter parted /dev/mapper/<mpath device name> to start the Parted Partition Manipulation utility on the selected device. The following is displayed:
# parted /dev/mapper/mpath2 GNU Parted 1.8.1 Using /dev/mapper/mpath2 Welcome to GNU Parted! Type 'help' to view a list of commands. (parted)

4. Enter mklabel gpt to create a new disk label (partition table). Note: Always answer Yes when you receive the prompt Do you want to continue? 5. Enter print to display the partition table. The following device attributes are displayed:
(parted) mklabel gpt (parted) print Model: Linux device-mapper (dm) Disk /dev/mapper/mpath2: 1000MB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags

(parted)

6. Enter mkpart primary <start> <end> to create a primary partition beginning at <start> and ending in <end>, in megabytes. If the previous print command showed a size in GB, specify <end> with a GB suffix for a size in gigabytes. A primary partition and a device named /dev/mapper/mpathNp1 are created. 7. Enter quit to exit the Parted utility. 8. Enter the following command to present the new partition to the operating system:
kpartx -a /dev/mapper/mpathN

9. Repeat steps 3 through 7 to create additional partitions until you have created one partition on each device.

162

IBM System Storage TS7600 with ProtecTIER: Users Guide

Creating physical volumes


For each partition created, create a physical volume. Perform the following steps to create the physical volumes that are needed: 1. Type pvcreate /dev/mapper/<partition name> to create the physical volume. Example:
# pvcreate /dev/mapper/mpath2p1 Physical volume /dev/mapper/mpath2p1 successfully created

2. Type pvscan to view the list of physical volumes. The physical volume or volumes that you created is displayed in the list:
# pvscan PV /dev/mapper/mpath2p1 lvm2 [953.97 MB] Total: 1 [953.97 MB] / in use: 0 [0

] / in no VG: 1 [953.97 MB]

Creating volume groups


For each physical volume created, create a volume group. Perform the following steps to create the volume group: 1. Type vgcreate <volume group name> /dev/mapper/mpathNp1 to create the volume group. Example:
# vgcreate VG1 /dev/mapper/mpath2p1 Volume group VG1 successfully created

2. Type vgscan to view the list of volume groups. The volume group that you created is displayed in the list:
# vgscan Reading all physical volumes. This may take a while... Found volume group VG1 using metadata type lvm2

Creating logical volumes


A logical volume must be created for each volume group that you have created. Perform the following steps to create a logical volume: 1. Type lvcreate -l 100%VG -n <logical volume name> <volume group name> to create the logical volume. Example:
# lvcreate -l 100%VG -n lvol1 VG1 Logical volume lvol1 created

2. Type lvscan to view the list of logical volumes. The logical volume that you created is displayed in the list:
# lvscan ACTIVE '/dev/VG1/lvol1' [952.00 MB] inherit

3. Type pvscan to view the complete path of the logical volumes with their associated partitions, physical volumes, and volume groups.
# pvscan PV /dev/mapper/mpath2p1 VG VG1 lvm2 [952.00 MB / 0 free] Total: 1 [952.00 MB] / in use: 1 [952.00 MB] / in no VG: 0 [0 ]

4. Ensure that all the layers of the logical volumes are correct.

Appendix B. Creating file systems and expanding existing ones

163

Creating a Global File System (GFS)


For each logical volume that you create, you must create a global file system. The GFS is the file system type necessary for the ProtecTIER repository. The GFS creation command includes the predefined cluster name on which the repository is created. Cluster names are defined in the Red Hat Cluster Suite configuration process. Perform the following step to create a GFS: Type gfs_mkfs -p lock_dlm -t <cluster name>:<gfs file system name> -j 3 <logical volume path>

Creating mount points


Once the file systems have been created, create a mount point for each file system. Attention: If you are creating file systems for a two-node cluster, create mount points on both nodes. Use the same mount point names on both nodes. Perform the following step to create a mount point: Type mkdir -p <mount point name>. Your command looks like the following:
#mkdir -p /mnt/fs1

Adding file systems to fstab and mounting file systems


Each file system you create must be listed in the /etc/fstab file, so that it is mounted automatically each time the system boots. Perform the following steps to list and mount your file system in the /etc/fstab file: 1. Add the following line to the /etc/fstab file for each file system that you have created.
/dev/mapper/<volume group name>-<logical volume name> <mount point name> gfs defaults,noatime,nodiratime,noquota 0 0

A completed line looks like the following:


/dev/mapper/VG1-lvol1 /mnt/fs1 gfs defaults,noatime,nodirtime,noquota 0 0

Attention: You must set the last file system parameter to zero. Setting the last parameter to another value will automatically run fsck at GFS file system startup which can result in corruption of the file system. 2. Type mount -a to mount all the file systems listed in /etc/fstab.

Expanding file systems


Perform the following steps, in the order they appear, for each file system that you want to expand: v Creating a partition on page 165 v Unmounting a file system on page 165 v Deactivating the logical volume on page 165 v Creating a physical volume on page 165

164

IBM System Storage TS7600 with ProtecTIER: Users Guide

v v v v v

Adding the physical volume to a volume group Expanding the logical volume on page 166 Reactivating the logical volume on page 166 Mounting the file system on page 166 Expanding the GFS file system on page 166

Creating a partition
Create a partition for each file system that you want to expand. For more information, see Creating partitions on page 161.

Unmounting a file system


Unmount the file system that you want to expand. Note: If you are working with a two node system, unmount the file system on both nodes. Type umount /dev/<file system name> to unmount the file system. Type umount /dev/<file system name> to unmount the file system.

Deactivating the logical volume


Deactivate the logical volume corresponding to the file system that you want to expand. Perform the following steps to deactivate the logical volume: 1. Type lvchange -an/dev/<volume group name>/<logical volume name>, where <volume group name> is the volume group corresponding to the file system that you want to expand. 2. Type lvscan to view the list of logical volumes. The logical volume is displayed as deactivated.

Creating a physical volume


Complete this task to create a new physical volume when expanding your file system. For each new partition created, create a physical volume. The steps used for creating a physical volume when creating a file system are the same as when expanding your file system. For more information, see Creating physical volumes on page 163.

Adding the physical volume to a volume group


Each new physical volume must be added to an existing volume group corresponding to the file system that you want to expand. Perform the following steps to add a new physical volume to an existing volume group: 1. Type vgextend <volume group name>/dev/<device name> to add the physical volume to an existing volume group.

Appendix B. Creating file systems and expanding existing ones

165

2. Type pvscan to view the list of physical volumes. The physical volume path should include /dev/<device name>.

Expanding the logical volume


Expand the logical volume corresponding to the file system that you want to expand. Perform the following step to expand the logical volume: Type lvextend -L +<size in Gigabytes>G /dev/<volume group name>/<logical volume name> /dev/<device name> to expand the logical volume.

Reactivating the logical volume


Perform the following step to reactivate the expanded logical volume: Type lvchange -ay /dev/<volume group name>/<logical volume name> to reactivate the expanded logical volume.

Mounting the file system


When the process of expanding the file system began, you unmounted the file system. After expanding the file system, you must remount it. Note: If you are working with a two node system, remount the file system on both nodes. Perform the following step to mount the file system that you expanded: Type mount -a to mount the file systems.

Expanding the GFS file system


Complete this task to allow for the expansion of the GFS file system. Type gfs_grow /dev/<volume group name>/<logical volume name> to allow for expansion of the GFS file system.

166

IBM System Storage TS7600 with ProtecTIER: Users Guide

Appendix C. RSA connection


This appendix provides an alternative method for establishing a connection to a server during RAS package configuration, using the remote supervisor adapter (RSA) port. This method should be used only if the server connection cannot be made using a USB keyboard and graphics-capable monitor. In order to use the RSA to connect to the servers, you will need to use the TSSC (code-level 5.5.x or higher required), or your IBM service laptop. If you use your laptop, you may also need an extension cord to reach a standard power outlet, or a 240v to 110v step-down voltage converter to allow the service laptop to run off of the PDU. Important: By default, the RSA ports on both servers in a cluster have the same IP address. This will cause a conflict when the servers attempt to communicate with the TSSC network switch via the RSA ports, and will result in abnormal system behavior. To avoid the conflict, you must change the IP address on one of the RSA ports so that its IP address is unique. To do so, perform steps 2 through 11 on page 169 below to change the RSA port IP address on Server B in the cluster. Do not change the default RSA port IP address on Server A. On the server on which you are installing the RAS package, complete the following steps: 1. If you are using the TSSC, skip ahead to step 12 on page 169. Otherwise, continue with step 2. 2. Connect an Ethernet cable from the Ethernet port on your laptop to the SYS MGMT (RSA port) on a stand-alone server, or on Server B in a cluster. See Figure 95.

Figure 95. Laptop or PC to RSA connection

3. In a cluster, disconnect the Ethernet cable from the RSA port on Server A. 4. On the laptop, click Start->Control Panel. 5. Double-click Network Connections.
Copyright IBM Corp. 2008, 2009

167

6. Right-click Local Area Connections->Properties. See Figure 96.

Figure 96. Local Area Connection Properties

7. From the list, select Internet Protocol (TCP/IP), then click Properties. See Figure 97.

Figure 97. Local Area Connection Properties: Internet Protocol (TCP/IP)

168

IBM System Storage TS7600 with ProtecTIER: Users Guide

8. Select Use the following IP address. 9. In the IP Address field, type: 172.31.1.14, and in the Subnet mask field, type: 255.255.255.0. 10. Click OK, then click Close to exit the Local Area Connections Properties window. 11. In a cluster, reconnect the Ethernet cable to the RSA port on Server A. 12. On the TSSC or service laptop, open an Internet Explorer window. 13. In the Address Bar area of the browser window, type the default RSA port IP address: 172.31.1.254 and then press <Enter>. 14. In the Login window, enter USERID as the username and PASSW0RD (with a zero) as the password, and then click OK. Note: The username and password are case sensitive and must be entered in all uppercase. The Remote Supervisor Adapter II Refresh 1 Welcome window opens. 15. In the Remote Supervisor Adapter II Refresh 1 Welcome window: a. Use the Inactive session timeout value drop-down list to specify a reasonable amount of time which will keep your session active until you can complete your task. Do not select No Timeout, as this will prevent anyone else from logging into the RSA until you have logged out. b. Click Continue. See Figure 98.

Figure 98. Remote Supervisor Adapter II Refresh 1 Welcome window

You are now logged into the servers RSA. 16. Go on to Enabling Remote Control on page 170.

Appendix C. RSA connection

169

Enabling Remote Control


Once you are connected to the servers RSA, you can perform configuration, setup, service, and maintenance functions on the server, either locally or remotely. 1. In the Remote Supervisor Adapter II Refresh 1 window, click Remote Control found in the left-hand menu under the IBM logo. See Figure 99.

Figure 99. Remote Supervisor Adapter II Refresh 1 window: Remote Control link

2. In the Remote Control window, click Start Remote Control in Single User Mode. See Figure 99. The ASM Remote Control window opens. Note: If your laptop is configured to block pop-ups, temporarily disable this function. Accept any Java versions that may appear on the screen, as well as any Windows security prompts displayed as a result of trying to open this window.

170

IBM System Storage TS7600 with ProtecTIER: Users Guide

Appendix D. TSSC network IP scheme


The TSSC IP address range changes from frame to frame, and each new frame increments by a multiple of 10. For example, the first standalone frame range would be 10, and the first cluster frame range would be 20. By default the first standalone or cluster uses IP address range 172.31.1.10. The next standalone or cluster uses address range 172.31.1.20, and so on. Note: Depending upon the address ranges available on the TSSC, the IBM Service representative may have to use ranges other than those shown here.
Table 21. TSSC IP address ranges IP addresses: Component Server Server Port eth3 RSA IP addresses: Standalone server or Server A in a cluster Server B in a cluster 172.31.1.x0 172.31.1.x1 172.31.1.x5 172.31.1.x6

Copyright IBM Corp. 2008, 2009

171

172

IBM System Storage TS7600 with ProtecTIER: Users Guide

Accessibility
The publications for this product are in Adobe Portable Document Format (PDF) and should be compliant with accessibility standards. 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 Development Department GZW 9000 South Rita Road Tucson, Arizona 85744-001 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 nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

Copyright IBM Corp. 2008, 2009

173

174

IBM System Storage TS7600 with ProtecTIER: Users Guide

Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions 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 improvements 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 provided for convenience only and do not in any manner serve 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 believes appropriate without incurring any obligation to you. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been

Copyright IBM Corp. 2008, 2009

175

estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available 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 IBMs future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. 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 individuals, 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: v v v v v v v v v v v v v v v v v v AIX DS4000 Enterprise Storage Server ESCON FICON i5/OS iSeries IBM ProtecTIER pSeries S/390 ServeRAID 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

176

IBM System Storage TS7600 with ProtecTIER: Users Guide

common law trademarks in other countries. A current list of IBM trademarks is available on the Web at Copyright and trademark information at http://www.ibm.com/legal/copytrade.shtml. 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. Java and all Java-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 Torvalds in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others.

Electronic emission notices


This section contains the electronic emission notices or statements for the United States and other countries.

Federal Communications Commission (FCC) statement


This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. 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 television interference caused by using other than recommended cables and connectors, or by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could void the users authority to operate the equipment. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device might not cause harmful interference, and (2) this device must accept any interference received, including interference that might cause undesired operation.

Notices

177

Industry Canada compliance statement


This Class A digital apparatus complies with Canadian ICES-003. Cet appareil numrique de la classe A est conform la norme NMB-003 du Canada.

European Union (EU) Electromagnetic Compatibility Directive


This product is in conformity with the protection requirements of EU Council Directive 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. This product has been tested and found to comply with the limits for Class A Information Technology Equipment according to European Standard EN 55022. The limits for Class A equipment were derived for commercial and industrial environments to provide reasonable protection against interference with licensed communication equipment. Attention: This is a Class A product. In a domestic environment this product might cause radio interference in which case the user might be required to take adequate measures. Properly shielded and grounded cables and connectors must be used in order to reduce the potential for causing interference to radio and TV communications and to other electrical or electronic equipment. Such cables and connectors are available from IBM authorized dealers. IBM cannot accept responsibility for any interference caused by using other than recommended cables and connectors. European community contact: IBM Technical Regulations Pascalstr. 100, Stuttgart, Germany 70569 Telephone: 0049 (0)711 785 1176 Fax: 0049 (0)711 785 1283 E-mail: tjahn@de.ibm.com

Australia and New Zealand Class A Statement


Attention: This is a Class A product. In a domestic environment this product might cause radio interference in which case the user might be required to take adequate measures.

Germany Electromagnetic compatibilty directive


Deutschsprachiger EU Hinweis: Hinweis fr Gerte der Klasse A EU-Richtlinie zur Elektromagnetischen Vertrglichkeit Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 2004/108/EG zur Angleichung der Rechtsvorschriften ber die elektromagnetische Vertrglichkeit in den EU-Mitgliedsstaaten und hlt die Grenzwerte der EN 55022 Klasse A ein. Um dieses sicherzustellen, sind die Gerte wie in den Handbchern beschrieben zu installieren und zu betreiben. Des Weiteren drfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM bernimmt keine Verantwortung fr die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der

178

IBM System Storage TS7600 with ProtecTIER: Users Guide

IBM verndert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne Empfehlung der IBM gesteckt/eingebaut werden. EN 55022 Klasse A Gerte mssen mit folgendem Warnhinweis versehen werden: Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbereich Funk-Strungen verursachen; in diesem Fall kann vom Betreiber verlangt werden, angemessene Mabnahmen zu ergreifen und dafr aufzukommen. Deutschland: Einhaltung des Gesetzes ber die elektromagnetische Vertrglichkeit von Gerten Dieses Produkt entspricht dem Gesetz ber die elektromagnetische Vertrglichkeit von Gerten (EMVG). Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in der Bundesrepublik Deutschland. Zulassungsbescheinigung laut dem Deutschen Gesetz ber die elektromagnetische Vertrglichkeit von Gerten (EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) fr Gerte der Klasse A Dieses Gert ist berechtigt, in bereinstimmung mit dem Deutschen EMVG das EG-Konformittszeichen - CE - zu fhren. Verantwortlich fr die Konformittserklrung des EMVG ist die IBM Deutschland GmbH, 70548 Stuttgart. Generelle Informationen: Das Gert erfllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A.

Peoples Republic of China Class A Electronic Emission statement

Taiwan Class A compliance statement

Taiwan contact information


This topic contains the product service contact information for Taiwan.
Notices

179

IBM Taiwan Product Service Contact Information: IBM Taiwan Corporation 3F, No 7, Song Ren Rd., Taipei Taiwan Tel: 0800-016-888

Japan VCCI Class A ITE Electronics Emission statement

Korean Class A Electronic Emission statement

Power cords
For your safety, IBM provides a power cord with a grounded attachment plug to use with this IBM product. To avoid 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 Underwriters Laboratories (UL) and certified by the Canadian Standards Association (CSA). For units intended to be operated at 115 volts: 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 volts. For units intended to be operated at 230 volts (U.S. use): 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 tandem blade, grounding-type attachment plug rated 15 amperes, 250 volts. For units intended to be operated at 230 volts (outside the U.S.): Use a cord set with a grounding-type attachment plug. The cord set should have the appropriate safety approvals for the country in which the equipment will be installed. IBM power cords for a specific country or region are usually available only in that country or region.

180

IBM System Storage TS7600 with ProtecTIER: Users Guide

f2c00790

Index A
about this document xi sending comments xvi accessibility 173 adding cartridges 67 cluster members 122 nodes 35 nodes to a subnetwork 36 physical volumes to volume groups 165 user accounts 113 administrator default password 31 role 113 alerts SNMP 19 alerts log 117 configuration cluster setup 2 one node system 2 two node system 2 creating file systems 39, 161 libraries 50 partitions 161 zones 49 creating file systems fsCreate 39 errors recoverable errors 19 unrecoverable errors 19 establishing installation directory 146 events log 117 expanding file systems 161 logical volumes 166 repositories 41

D
data de-duplication 1 de-duplication 1 deactivating logical volumes 165 defragmentation disabling 124 deleting cartridges 68 libraries 70 repositories 42 user accounts 113 device reassigning 62 resetting 127 disabling compression 125 defragmentation 124 Disaster recovery replace dual node by single documentation improvement xvi dumping trace buffer 126

F
fields implemented SNMP 19 file system creating 39, 161 expanding 161 unmounting 165 volume name 129 fsck error check 128 running 129 fsCreate creating file systems 39 fsCreate parameters 40

B
backup catalog 136 backup monitoring 94

C
cartridge adding 67 deleting 68 managing 66 moving 128 read-only mode 69 read/write mode 69 switching modes 69 unloading 127 cartridge drive reassigning 62 changing HyperFactor mode 125 worldwide names 123 checking errors 130 cluster cluster member monitoring, see cluster member 79 disk space monitoring 78 fibre channel port throughput monitoring 79 general monitoring 77 overview 35 VT service monitoring 79 cluster member adding 122 monitoring 79 removing 121 comments, sending xvi completing ProtecTIER setup 7 compression disabling 125

G
152 generating long-term statistics reports problem reports 119 Grid Manager 154 installing 154 119

H
HP-UX host configuring node ports 49 HyperFactor 1 HyperFactor mode changing 125 HyperFactor ratio over time graph 83

E
editing libraries 58 emulation tape library 1 enabling SNMP compatibility 19 SNMP support 19 error checking 130 repairing 131 error check fsck 128 overview 128 ProtecTIER Manager 130 running 130 error message wizards 118 error trap SNMP 19

I
implementing SNMP compatibility 19 installation directory, establishing 146 installing ProtecTIER Manager 27 Installing RAS package 146 introduction 1

K
keyboards accessibility features 173

Copyright IBM Corp. 2008, 2009

181

L
library creating 50 deleting 70 editing 58 overview 49 renaming 70 Library library type setting 57 library type information 89 Linux shell backup monitoring 94 log alerts 117 events 117 log in as root 146 logging in 31 logging out 31 logical volume deactivating 165 expanding 166 reactivating 166 long-term statistics report generating 119

monitoring (continued) repository configuration 81 repository disk space 81 repository factoring ratio 81 repository HyperFactor 83 repository IOPS 81 repository nominal data size 81 repository storage 82 repository used space 81 robots 88 slots 92 tape drives 88 VT service 87 VT service for clusters 79 VT service libraries 89 moving cartridges 128

N
Navigation pane refreshing 32 node adding 35 adding replication 14 adding to a subnetwork 36 changing worldwide names 123 configuring ports for HP-UX hosts 49 general monitoring 86 network configuration monitoring 87 overview 35 port monitoring 86 port scanning 86 removing 36 scanning ports 86 updating ProtecTIER 9, 11 version information 86 node configuration one node 2 two nodes 2 nominal data size graph 82

M
machine types xi management tools SNMP 19 managing cartridges 66 clusters 35 nodes 35 repositories 37 user accounts 113 marginal HyperFactor ratio graph 83 message area 118 MIB definition file 19 MIB-2 SNMP 19 model numbers xi modifying port attributes 120 trace buffer 125 monitor default password 31 role 113 monitoring backup operations 94 cartridges 91 cluster disk space 78 cluster members 79 cluster VT service 79 clusters 77 drives 89 fibre channel port throughput 79 HyperFactor 83 imports/exports slots 92 library configuration 89 network configuration 87 nodes 86 port attributes 86 ProtecTIER 77 repositories 80

planning repository expansion 37 Policy creating 45 disable 46 enable 46 modifying 47 running 47 port attributes, modifying 120 attributes, monitoring 86 configuring for HP-UX hosts prerequisites ProtecTIER Manager 27 printing data 32 problem report generating 119 ProtecTIER monitoring 77 package, unpacking 146 updating 9, 11 ProtecTIER Manager installing 27 overview 6 prerequisites 27 refreshing 32 uninstalling 30 ProtecTIER setup completing 7

49

R
RAS installation 146 reactivating logical volumes 166 reader feedback, sending xvi reassigning cartridge drives 62 devices 62 robots 62 reboot error 19 recovery cartridge status 136 Recovery Procedures 139 refreshing 32 reloading a node 139 removing cluster members 121 nodes 36 renaming libraries 70 repairing errors 131 Replace, dual node by single Disaster recovery 152 Replication adding 14 creating a policy 45 disabling a policy 46 enabling a policy 46 modifying a policy 47 policies 43 running a policy 47 timeframe setting 44

O
operator default password 31 role 113 overview checking errors 128 ProtecTIER Manager 6 repository expansion 37 troubleshooting 117

P
partition creating 161 password default 31 permission levels default accounts 31 overview 113 physical volume adding to volume groups

165

182

IBM System Storage TS7600 with ProtecTIER: Users Guide

replication timeframe setting 44 repository configuration monitoring 81 deleting 42 disk space monitoring 81 expanding 41 expansion overview 37 expansion planning 37 factoring ratio monitoring 81 general monitoring 80 HyperFactor monitoring 83 HyperFactor ratio over time graph 83 IOPS monitoring 81 managing 37 marginal HyperFactor ratio graph 83 nominal data size graph 82 nominal data size monitoring 81 planning an expansion 37 storage monitoring 82 used space monitoring 81 utilization graph 82 resetting devices 127 robots 127 tape drives 127 trace buffer 127 restart error 19 restoring grid manager analysis 157 robot monitoring 88 reassigning 62 resetting 127 RSA connection 167 running error checks 130 fsck 129

T
tape drive monitoring 88 resetting 127 tape library 1 TCP/IP network 36 terminology xi timeserver updating 24 trace buffer dumping 126 modifying 125 resetting 127 setting levels 126 Trademarks 176 traps SNMP 19 troubleshooting overview 117 tasks 124

W
warning notification trap SNMP 19 Wizard error messages 118 Wizard message area 118 worldwide name changing 123

U
uninstalling ProtecTIER Manager 30 unloading cartridges 127 unmounting file systems 165 unpacking ProtecTIER package 146 updating nodes 9, 11 ProtecTIER 9, 11 user account adding 113 deleting 113 overview 113 username default 31 utilization graph 82

S
saving data 32 sending comments xvi setting trace buffer levels 126 SNMP alerts 19 compatibility, enabling 19 compatibility, implementing 19 error trap 19 fields implemented 19 management tools 19 MIB-2 19 support, enabling 19 traps 19 warning notification trap 19 static routes routing, replication 15 subnetworks 36 switching modes cartridges 69

V
version information 86 View pane refreshing 32 Virtual Tape service, see VT service 1 volume group adding physical volumes 165 volume name of file systems 129 VT service 1 cartridge monitoring 91 clusters monitoring 79 drives monitoring 89 general monitoring 87 imports/exports slots monitoring 92 library configuration monitoring 89 library monitoring 89 library type information 89 overview 49 robot monitoring 88 slots monitoring 92 tape drive monitoring 88

Index

183

184

IBM System Storage TS7600 with ProtecTIER: Users Guide

Printed in USA

GC53-1156-03

You might also like