User Guide 2.4

IBM System Storage TS7600 with ProtecTIER
User's Guide
for Enterprise Edition and Appliance Edition
GC53-1156-07
IBM System Storage TS7600 with ProtecTIER
User's Guide
for Enterprise Edition and Appliance Edition
GC53-1156-07
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.4.0.0] and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces GC53-1156-06. Copyright IBM Corporation 2008, 2009, 2010. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . vii Tables . . . . . . . . . . . . . . . ix Safety and Environmental notices . . . xi
Safety notices . . . . . . . . . . . . . . xi Power cords . . . . . . . . . . . . . . xii Environmental notices . . . . . . . . . . xiii Who should read this document . . . . . . . xxxi What's new in this edition . . . . . . . . . xxxi Getting information, help, and service . . . . . xxxi Web sites . . . . . . . . . . . . . . xxxiii Related IBM publications . . . . . . . . . xxxiii How to send your comments . . . . . . . xxxiv
Chapter 1. Introduction . . . . . . . . 1
HyperFactor . . . . . . ProtecTIER Virtual Tape (VT) . Configuration . . . . . . ProtecTIER Manager . . . . Native Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 2 5 5
Safety, danger, caution notices and labels . . . . . . . . . . . . . . . xv

D001 . . . . . . . . . . . . . . . . xvi D002 . . . . . . . . . . . . . . . . xvi D003 . . . . . . . . . . . . . . . . xvi D004 . . . . . . . . . . . . . . . . xvi D005 . . . . . . . . . . . . . . . . xvi D006 . . . . . . . . . . . . . . . . xvii D008 . . . . . . . . . . . . . . . . xvii C001 . . . . . . . . . . . . . . . . xvii C002 . . . . . . . . . . . . . . . . xviii C003 . . . . . . . . . . . . . . . . xviii C005 . . . . . . . . . . . . . . . . xviii C007 . . . . . . . . . . . . . . . . xviii C009 . . . . . . . . . . . . . . . . xix C013 . . . . . . . . . . . . . . . . xix C014 . . . . . . . . . . . . . . . . xix C018 . . . . . . . . . . . . . . . . xix C021 . . . . . . . . . . . . . . . . xix C022 . . . . . . . . . . . . . . . . xix C023. . . . . . . . . . . . . . . . . xx C026. . . . . . . . . . . . . . . . . xx C027. . . . . . . . . . . . . . . . . xx C028. . . . . . . . . . . . . . . . . xx C029. . . . . . . . . . . . . . . . . xx C030. . . . . . . . . . . . . . . . . xx C031 . . . . . . . . . . . . . . . . xxi C032 . . . . . . . . . . . . . . . . xxi C033 . . . . . . . . . . . . . . . . xxi R001 Part 1 of 2 . . . . . . . . . . . . xxii R001 Part 2 of 2 . . . . . . . . . . . . xxii R002 . . . . . . . . . . . . . . . . xxiii L001 . . . . . . . . . . . . . . . . xxiv L002 . . . . . . . . . . . . . . . . xxiv L003 . . . . . . . . . . . . . . . . xxiv L004 . . . . . . . . . . . . . . . . xxv L005 . . . . . . . . . . . . . . . . xxvi L009 . . . . . . . . . . . . . . . . xxvi L013 . . . . . . . . . . . . . . . . xxvi L015 . . . . . . . . . . . . . . . . xxvii L022 . . . . . . . . . . . . . . . . xxvii L023 . . . . . . . . . . . . . . . . xxvii
Chapter 2. Completing the ProtecTIER system setup for new installations . . . 7

Logging in to the ProtecTIER server . . . . Customizing the ProtecTIER server . . . . . Routing replication IP traffic (static routes) . . Updating replication IPs on a node . . . . Changing the system date and time . . . . Enabling SNMP compatibility . . . . . . ProtecTIER Replication Network Performance Validation Utility . . . . . . . . . . . . . . . . . . 7 . 7 . 9 . 11 . 12 . 15 . 17
Chapter 3. Upgrading and Configuring Red Hat Linux and ProtecTIER . . . . 21

Preparing for the 2.4.0.0 upgrade . . . . . . . Checking the ProtecTIER and RAS versions . . Downloading ProtecTIER v2.3.x.x . . . . . . Installing ProtecTIER v2.3.x.x . . . . . . . Upgrading and Configuring Red Hat Linux and ProtecTIER . . . . . . . . . . . . . . Upgrading Red Hat and ProtecTIER on a stand-alone server . . . . . . . . . . . . Performing post-upgrade tasks . . . . . . . Upgrading Red Hat and ProtecTIER on clustered servers . . . . . . . . . . . . . . . . Performing post-upgrade tasks . . . . . . . Configuring, verifying, and testing the RAS package Configuring the RAS package . . . . . . . 21 22 23 23 25 26 29 30 34 35 35
| | | | | |
Chapter 4. Installing ProtecTIER Manager . . . . . . . . . . . . . . 37

Prerequisites . . . . . . . . . Upgrading ProtecTIER Manager . . Uninstalling the ProtecTIER Manager. . . . . . . . . . . . . . 37 . 37 . 40
Chapter 5. Getting started with ProtecTIER Manager . . . . . . . . . 41

Logging in and out . . . . . Changing the Support System Saving and printing data . . . Refreshing ProtecTIER Manager . . . settings . . . . . . . . . . . . . . . . . . . . . . 41 41 43 43
About this document . . . . . . . . xxix

Terminology . . . . . . . . . . . . . xxix
Copyright IBM Corp. 2008, 2009, 2010
iii
Running operations in the background .
. 43
Chapter 6. Managing nodes and clusters . . . . . . . . . . . . . . 45

Adding and removing nodes from ProtecTIER Manager . . . . . . . . . . . . . . . 45
Chapter 7. Managing repositories . . . 47

Enabling replication . . . . . . . . Expanding repositories . . . . . . . Planning an expansion . . . . . . Using fsCreate to create file systems . . Expanding the repository . . . . . . Creating file systems and expanding existing Creating file systems . . . . . . . Expanding existing file systems. . . . Deleting repositories . . . . . . . . Defragmentation on a repository . . . . Reserve space for backup . . . . . . . . . . . . . . . . . ones . . . . . . . . . . . . . . . . . . . . 47 48 48 49 51 53 53 57 59 59 59
Setting the replication timeframe . . . . Setting the replication rate limit . . . . Limiting the network interface bandwidth . Creating a replication policy . . . . . Enabling and disabling a policy . . . . Running a policy . . . . . . . . . Modifying a policy . . . . . . . . Deleting a policy . . . . . . . . . Aborting replication activities . . . . . . Monitoring the replication grid . . . . .
. . . . . . . . . .
. . . . . . . . . .
115 116 117 118 119 119 120 120 120 121
Chapter 11. Disaster recovery (DR) mode operations . . . . . . . . . . 123

Working at the DR site . . . . . . . . Entering Disaster Recovery (DR) mode . . Taking over cartridge ownership . . . . Assessing cartridge status and syncing with catalog . . . . . . . . . . . . Reestablishing the production site . . . . Replacing the destroyed repository . . . The failback policy . . . . . . . . . . . . . . the . . . . . . . . 123 123 124 124 126 127 127
Chapter 8. Managing the ProtecTIER VT service. . . . . . . . . . . . . . . 61

Setting the ProtecTIER VT host connections Creating libraries . . . . . . . . . Setting the library type . . . . . . . Editing library parameters . . . . . . Reassigning devices . . . . . . . . Setting control path failover . . . . . . Managing cartridges . . . . . . . . Renaming libraries . . . . . . . . . Deleting libraries . . . . . . . . . About LUN Masking . . . . . . . . Enabling or disabling LUN Masking . . Managing host initiators . . . . . . Working with LUN Masking groups . . . Library-related Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 61 68 68 72 75 75 78 78 78 78 79 82 84
Chapter 12. Managing and monitoring ProtecTIER through the CLI . . . . . 129
Understanding the syntax diagrams . Creating a profile . . . . . . . ptcli . . . . . . . . . . . Inventory Command Options . . Server Options . . . . . . . Processing Options . . . . . Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 130 130 136 140 141 141
Chapter 13. Managing users . . . . . 143

Permission levels . . Adding user accounts . . . . . . . . . . . . . . . . . . . 143 . 143
Chapter 14. Troubleshooting . . . . . 145 Chapter 9. Monitoring ProtecTIER . . . 85

Monitoring ProtecTIER systems. . . . . . . . 85 Monitoring replication policies and activites . . 88 Monitoring the repository . . . . . . . . . 90 Monitoring nodes . . . . . . . . . . . . 94 Monitoring the ProtecTIER VT service . . . . . 95 Monitoring the shelf . . . . . . . . . . . 104 Monitoring backups from the Linux shell . . . . 105 Viewing the alerts and events log windows Wizard error messages . . . . . . . Generating a problem report for ProtecTIER Manager . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 145 . 146 . . . . . . . . 146 148 148 148 149 151 152 157
Chapter 10. Native Replication Management . . . . . . . . . . . . 107

Working with ProtecTIER Replication Manager Managing the replication grid . . . . . . Working with repositories in a replication grid Adding a repository to a grid . . . . . Removing a repository from a grid . . . Forcing a repository to leave a grid . . . Updating the IP address of a repository . Defining the role of a repository . . . . Connecting a spoke to the hub . . . . Disconnecting a spoke from the hub . . . Replication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 108 109 109 110 111 111 111 112 114 114
Chapter 15. ProtecTIER system recovery procedures . . . . . . . . 161

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 . . . . . . . . . . . . . . 161 . 162 . 166 . 167 . 170
iv
IBM System Storage TS7600 with ProtecTIER: User's Guide
DR replacing a two-node system with a single node configuration . . . . . . . . . . Activating ProtecTIER Replication Manager . . Backing up the configuration files . . . . . Analyzing and restoring the ProtecTIER Replication Manager . . . . . . . . . . Restoring the ProtecTIER Replication Manager
. 173 . 176 . 176 . 177 177
| Appendix A. Verifying and upgrading | the storage subsystem firmware, | NVSRAM, and ESM . . . . . . . . . 181
Appendix B. RSA connection

Enabling Remote Control . . . . .
. . . . 185
. . . . 188
Appendix C. TSSC network IP scheme 189 Appendix D. Worldwide time zone codes. . . . . . . . . . . . . . . 191 Accessibility . . . . . . . . . . . . 203 Notices . . . . . . . . . . . . . . 205
Trademarks . . . . . . . . . . . . . . Electronic emission notices . . . . . . . . . Federal Communications Commission statement Industry Canada compliance statement . . . . European Union Electromagnetic Compatibility Directive . . . . . . . . . . . . . . Australia and New Zealand Class A Statement Germany Electromagnetic compatibility directive . . . . . . . . . . . . . . People's Republic of China Class A Electronic Emission statement . . . . . . . . . . Taiwan Class A compliance statement . . . . Taiwan contact information. . . . . . . . Japan VCCI Council Class A statement . . . . Japan Electronics and Information Technology Industries Association (JEITA) Statement (less than or equal to 20 A per phase) . . . . . . Korean Communications Commission (KCC) Class A Statement . . . . . . . . . . . Russia Electromagnetic Interference (EMI) Class A Statement . . . . . . . . . . . . .
206 207 207 208 208 208 208 209 210 210 210
210 211 211
Index . . . . . . . . . . . . . . . 213
Contents
vi
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. Tape library emulation . . . . . . . One node system . . . . . . . . . Two node system . . . . . . . . . Cluster setup . . . . . . . . . . Updating cluster response. . . . . . ProtecTIER Manager . . . . . . . Repository meta data storage requirements window . . . . . . . . . . . . Repository resources dialog . . . . . Reserve space for backup window . . . 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. . . . . . . . . Host Initiator management window . . LUN Masking window. . . . . . . Systems monitoring screen . . . . . Storage resources window . . . . . VT tab view . . . . . . . . . . Replication Policies tab. . . . . . . Replication activities view. . . . . . Repository monitoring screen . . . . Nominal data size graph . . . . . . Utilization graph . . . . . . . . . Marginal HyperFactor graph . . . . . HyperFactor ratio over time graph . . . General tab . . . . . . . . . . Drives tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 . 3 . 4 . 5 . 12 . 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 52 60 62 63 64 65 66 66 67 68 69 70 71 71 72 73 74 74 76 77 80 83 85 86 88 89 90 91 92 93 93 94 96 98 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. Cartridges tab - backup properties . . . . Cartridges tab - origin properties . . . . Cartridges tab - replica properties. . . . Slots tab . . . . . . . . . . . . Imports/Exports tab . . . . . . . . Shelf view . . . . . . . . . . . Adding a repository to a grid . . . . . Defining the repository role . . . . . . Connecting spokes to a hub . . . . . . Replication grid map view . . . . . . View of replication policy . . . . . . Set replication time frame . . . . . . Set Replication rate limits . . . . . . Detailed view of a spoke. . . . . . . Cartridge status report (in Excel) . . . . Users Management dialog . . . . . . Add account dialog . . . . . . . . Alerts log . . . . . . . . . . . . Message area . . . . . . . . . . Create problem report window . . . . 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 . . . . . . Press F12 to select the boot device . . . Select CD as the boot device . . . . . Red Hat Enterprise Linux 5 screen . . . Verify attached disks . . . . . . . . End User License Agreement . . . . . Accept the license agreement . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 101 102 103 104 105 110 112 113 113 115 116 117 122 126 144 144 145 146 147 149 150 151 153 . 155 . 157 . 159 . 163 . 163 . 164 . 165 . 166 . 166 . 185 . 186
. 186 . 187 . 188
vii
viii
Tables
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. IBM Web sites for help, services, and information. . . . . . . . . . . . Version results and required actions . . . Default usernames and passwords . . . . Color selections for the ProtecTIER Manager GUI . . . . . . . . . . . . . . fsCreate parameters . . . . . . . . . Cluster member information . . . . . . Total utilization information . . . . . . Repository information. . . . . . . . Port attribute information . . . . . . . Network interface card information . . . Virtual robots and tape drive. . . . . . Drives tab information . . . . . . . . Cartridges backup properties. . . . . . Cartridges origin properties . . . . . . Cartridges origin properties . . . . . . Slots tab information . . . . . . . . Imports/Exports tab information . . . . Recent backup session statistics . . . . Add Cartridges command . . . . . . Add Cluster Member Command . . . . xxxii . 22 . 41 . 42 . 51 . 87 . 91 . 92 . 94 . 95 . 96 . 98 . 99 . 101 . 102 . 103 . 104 . 106 . 131 . 132 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. Add Library Command . . . . . Cartridge Info Command . . . . Create Repository Command . . . Drive Models Command . . . . . Libraries Command . . . . . . Library Information Command . . Library Types Command. . . . . Node VTL Statistics Command. . . Number of Cartridges Command . . RAID Configurations Command . . Repository Statistics Command . . Server Version Command . . . . Inventory Refresh command . . . Inventory Filter command . . . . Inventory Get Query Fields command Inventory Move File command. . . Inventory Move Filter command . . Inventory Statistics command . . . Server options . . . . . . . . Processing options . . . . . . . Grid analysis messages . . . . . TSSC IP address ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 133 134 134 134 135 135 135 136 136 136 136 137 137 138 139 140 140 141 141 178 189
ix
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, G229-9054 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.
xi
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.
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,
xii
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.
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.
Safety and Environmental notices
xiii
xiv
Safety, danger, caution notices and labels

This section contains safety, danger, caution notices and labels that are used in this guide for this product. You should read all safety notices in entirety before completing any task.
xv
D001
DANGER To prevent a possible shock from touching two surfaces with different protective ground (earth), use one hand, when possible, to connect or disconnect signal cables. (D001)
D002
DANGER Overloading a branch circuit is potentially a fire hazard and a shock hazard under certain conditions. To avoid these hazards, ensure that your system electrical requirements do not exceed branch circuit protection requirements. Refer to the information that is provided with your device or the power rating label for electrical specifications. (D002)
D003
DANGER If the receptacle has a metal shell, do not touch the shell until you have completed the voltage and grounding checks. Improper wiring or grounding could place dangerous voltage on the metal shell. If any of the conditions are not as described, STOP. Ensure the improper voltage or impedance conditions are corrected before proceeding. (D003)
D004
DANGER An electrical outlet that is not correctly wired could place hazardous voltage on the 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)
D005
DANGER When working on or around the system, observe the following precautions: Electrical voltage and current from power, telephone, and communication cables are hazardous. To avoid a shock hazard: v Connect power to this unit only with the IBM provided power cord. Do not use the IBM provided power cord for any other product. v Do not open or service any power supply assembly. v Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. v The product might be equipped with multiple power cords. To remove all
xvi
hazardous voltages, disconnect all power cords. v Connect all power cords to a properly wired and grounded electrical outlet. Ensure that the outlet supplies proper voltage and phase rotation according to the system rating plate. v Connect any equipment that will be attached to this product to properly wired outlets. v When possible, use one hand only to connect or disconnect signal cables. v Never turn on any equipment when there is evidence of fire, water, or structural damage. v Disconnect the attached power cords, telecommunications systems, networks, and modems before you open the device covers, unless instructed otherwise in the installation and configuration procedures. v Connect and disconnect cables as described in the following procedures when installing, moving, or opening covers on this product or attached devices. To disconnect: 1. Turn off everything (unless instructed otherwise). 2. 3. 4. To 1. Remove the power cords from the outlets. Remove the signal cables from the connectors. Remove all cables from the devices. connect: Turn off everything (unless instructed otherwise).
2. Attach all cables to the devices. 3. Attach the signal cables to the connectors. 4. Attach the power cords to the outlets. 5. Turn on the devices. v Sharp edges, corners and joints may be present in and around the system. Use care when handling equipment to avoid cuts, scrapes and pinching. (D005)
D006
DANGER Heavy equipmentpersonal injury or equipment damage might result if mishandled. (D006)
D008
DANGER Professional movers are to be used for all relocation activities. Serious injury or death may occur if systems are handled and moved incorrectly. (D008)
C001
CAUTION:
xvii
Energy hazard present. Shorting might result in system outage and possible physical injury. Remove all metallic jewelry before servicing. (C001)
C002
CAUTION: Only trained service personnel may replace this battery. The battery contains lithium. To avoid possible explosion, do not burn or charge the battery. Do not: v Throw or immerse into water v Heat to more than 100C (212F) v Repair or disassemble 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. (C002)
C003
CAUTION: The battery contains lithium. To avoid possible explosion, do not burn or charge the battery. Do not: v Throw or immerse into water v Heat to more than 100C (212F) v Repair or disassemble 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. (C003)
C005
CAUTION: The battery is a nickel-cadmium 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. (C005)
C007
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)
xviii
C009
CAUTION:
>18 kg (39.7 lb)
or
or
18-32 kg (39.7-70.5 lb)
The weight of this part or unit is between 18 and 32 kg (39.7 and 70.5 lb). It takes two persons to safely lift this part or unit. (C009)
C013
CAUTION: The doors and covers to the product are to be closed at all times except for service by trained service personnel. All covers must be replaced and doors locked at the conclusion of the service operation. (C013)
C014
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)
C018
CAUTION: This product is equipped with a 3-wire (two conductors and ground) power cable and plug. Use this power cable with a properly grounded electrical outlet to avoid electrical shock. (C018)
C021
CAUTION: The power distribution outlets provide 200 to 240 V ac. Use these outlets only for devices that operate within this voltage range. (C021)
C022
CAUTION: The product might be equipped with a hard-wired power cable. Ensure that a licensed electrician performs the installation per the national electrical code. (C022)
xix
C023
CAUTION: Ensure the building power circuit breakers are turned off BEFORE you connect the power cord or cords to the building power. (C023)
C026
CAUTION: This product might contain one or more of the following devices: CD-ROM drive, DVD-ROM drive, DVD-RAM drive, or laser module, which are Class 1 laser products. Note the following information: v Do not remove the covers. Removing the covers of the laser product could result in exposure to hazardous laser radiation. There are no serviceable parts inside the device. v Use of the controls or adjustments or performance of procedures other than those specified herein might result in hazardous radiation exposure. (C026)
C027
CAUTION: Data processing environments can contain equipment transmitting on system links with laser modules that operate at greater than Class 1 power levels. For this reason, never look into the end of an optical fiber cable or open receptacle. (C027)
C028
CAUTION: This product contains a Class 1M laser. Do not view directly with optical instruments. (C028)
C029
CAUTION: This product contains a Class 2 laser. Do not stare into the beam. (C029)
C030
CAUTION: Some laser products contain an embedded Class 3A or Class 3B laser diode. Note the following information: v Laser radiation when open. v Do not stare into the beam, do not view directly with optical instruments, and avoid direct exposure to the beam. (C030)
xx
C031
CAUTION: The power-control button on the device does not turn off the electrical current supplied to the device. The device might also have more than one connection to dc power. To remove all electrical current from the device, ensure that all connections to dc power are disconnected at the dc power input terminals. (C031)
C032
CAUTION: Servicing of this product or unit is to be performed by trained service personnel only. (C032)
C033
CAUTION: To reduce the risk of electric shock or energy hazards: v This equipment must be installed by trained service personnel in a restricted-access location, as defined by the NEC and IEC 60950, The Standard for Safety of Information Technology Equipment. v Connect the equipment to a reliably grounded, safety extra low voltage (SELV) source. An SELV source is a secondary circuit that is designed so that normal and single fault conditions do not cause the voltages to exceed a safe level (60 V direct current). v The branch circuit overcurrent protection must be rated per the following table. v Use copper wire conductor only, not exceeding 3 m (9.8 ft.) in length and sized according to the following table. v Torque the wiring-terminal screws to the values in the following table. v Incorporate a readily available approved and rated disconnect device in the field wiring. (C033) The following table appears in the product documentation with actual values substituted for xxx:
Circuit breaker rating Wire size Wiring-terminal screw torque Minimum: xxx amps Maximum: xxx amps xxx AWG xxx mm2 xxx inch-pounds xxx newton-meters
xxi
R001 Part 1 of 2
Use the following general safety information for all rack-mounted devices: DANGER Observe the following precautions when working on or around your IT rack system: v Heavy equipmentpersonal injury or equipment damage might result if mishandled. v Always lower the leveling pads on the rack cabinet. v Always install stabilizer brackets on the rack cabinet. v To avoid hazardous conditions due to uneven mechanical loading, always install the heaviest devices in the bottom of the rack cabinet. Always install servers and optional devices starting from the bottom of the rack cabinet. v Rack-mounted devices are not to be used as shelves or work spaces. Do not
place objects on top of rack-mounted devices. v Each rack cabinet might have more than one power cord. Be sure to disconnect all power cords in the rack cabinet when directed to disconnect power during servicing. v Connect all devices installed in a rack cabinet to power devices installed in the same rack cabinet. Do not plug a power cord from a device installed in one rack cabinet into a power device installed in a different rack cabinet. v An electrical outlet that is not correctly wired could place hazardous voltage on the 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. (R001 part 1 of 2)
R001 Part 2 of 2
CAUTION: v Do not install a unit in a rack where the internal rack ambient temperatures will exceed the manufacturer's recommended ambient temperature for all your rack-mounted devices. v Do not install a unit in a rack where the air flow is compromised. Ensure that air flow is not blocked or reduced on any side, front, or back of a unit used for air flow through the unit. v Consideration should be given to the connection of the equipment to the supply circuit so that overloading of the circuits does not compromise the supply wiring or overcurrent protection. To provide the correct power connection to a rack, refer to the rating labels located on the equipment in the rack to determine the total power requirement of the supply circuit. v (For sliding drawers): Do not pull out or install any drawer or feature if the rack stabilizer brackets are not attached to the rack. Do not pull out more than one drawer at a time. The rack might become unstable if you pull out more than one drawer at a time. v (For fixed drawers): This drawer is a fixed drawer and must not be moved for servicing unless specified by the manufacturer. Attempting to move the
xxii
drawer partially or completely out of the rack might cause the rack to become unstable or cause the drawer to fall out of the rack. (R001 part 2 of 2)
R002
CAUTION: Removing components from the upper positions in the rack cabinet improves rack stability during relocation. Follow these general guidelines whenever you relocate a populated rack cabinet within a room or building: v Reduce the weight of the rack cabinet by removing equipment starting at the top of the rack cabinet. When possible, restore the rack cabinet to the configuration of the rack cabinet as you received it. If this configuration is not known, you must observe the following precautions: Remove all devices in the 32U position and above. Ensure that the heaviest devices are installed in the bottom of the rack cabinet. Ensure that there are no empty U-levels between devices installed in the rack cabinet below the 32U level. v If the rack cabinet you are relocating is part of a suite of rack cabinets, detach the rack cabinet from the suite. v Inspect the route that you plan to take to eliminate potential hazards. v Verify that the route that you choose can support the weight of the loaded rack cabinet. Refer to the documentation that comes with your rack cabinet for the weight of a loaded rack cabinet. v Verify that all door openings are at least 760 x 230 mm (30 x 80 in.). v Ensure that all devices, shelves, drawers, doors, and cables are secure. v Ensure that the four leveling pads are raised to their highest position. v Ensure that there is no stabilizer bracket installed on the rack cabinet during movement. v Do not use a ramp inclined at more than 10 degrees. v When the rack cabinet is in the new location, complete the following steps: Lower the four leveling pads. Install stabilizer brackets on the rack cabinet. If you removed any devices from the rack cabinet, repopulate the rack cabinet from the lowest position to the highest position. v If a long-distance relocation is required, restore the rack cabinet to the configuration of the rack cabinet as you received it. Pack the rack cabinet in the original packaging material, or equivalent. Also lower the leveling pads to raise the casters off of the pallet and bolt the rack cabinet to the pallet. (R002)
xxiii
L001
DANGER Hazardous voltage, current, or energy levels are present inside any component that has this label attached. Do not open any cover or barrier that contains this label. (L001)
L002
DANGER Rack-mounted devices are not to be used as shelves or work spaces. (L002)
L003
DANGER Multiple power cords. The product might be equipped with multiple power cords. To remove all hazardous voltages, disconnect all power cords. (L003)
or
xxiv
!
1
or
3 1
L004
DANGER
4 2
Hazardous voltage present. Voltages present constitute a shock hazard, which can cause severe injury or death. (L004)
xxv
L005
CAUTION: Hazardous energy present. Voltages with hazardous energy might cause heating when shorted with metal, which might result in splattered metal, burns, or both. (L005)
>240VA
L009
CAUTION: System or part is heavy. The label is accompanied by a specific weight range. (L009)
L013
DANGER Heavy equipmentpersonal injury or equipment damage might result if mishandled. (L013)
xxvi
L015
CAUTION: Danger! Arc Flash/Arc Blast hazard when disconnected with power on. Turn off power before disconnecting. (L015)
L022
CAUTION: Class 3R visible and invisible laser radiation when open. Avoid direct eye exposure. (L022)
L023
CAUTION: Laser Aperture (L023)
xxvii
xxviii
About this document

This document provides information for using the IBM System Storage TS7600 with ProtecTIER for the Appliance Edition & Enterprise Edition [ProtecTIER v2.4].
Terminology
IBM offers two virtualization solutions: TS7650 When used alone, this term signifies IBM's family of virtualization solutions that operate on the ProtecTIER platform. TS7650 Appliance or appliance These are terms for IBM's 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 for the TS7650 Appliance is an IBM Feature Code 3708: 4.8 TB Fibre Channel Disk Controller. Use this feature code for service purposes. Disk expansion unit The disk expansion unit for the TS7650 Appliance is an IBM Feature Code 3707: 7.2 TB Fibre Channel Disk Expansion Unit. Use this feature code for service purposes. TS7650G or Gateway These are terms for IBM's 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. IBM does not support more than one clustered pair of TS7650 Gateway servers in a single frame. 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.
xxix
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 customer must choose the disk controller for use with the TS7650G. A list of compatible controllers is located at the IBM Tape Systems Resource Library Web site: http://www-03.ibm.com/ systems/storage/tape/library.html#compatibility in the TS7650/TS7650G ISV and interoperability matrix document. Disk expansion unit The customer must choose the disk expansion unit for use with the TS7650G. A list of compatible expansion units is located at the IBM Tape Systems Resource Library Web site: http://www-03.ibm.com/ systems/storage/tape/library.html#compatibility in the TS7650/TS7650G ISV and interoperability matrix document. 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, that are used for replication. Replication ports are connected to the customer's WAN and are configured on two subnets as default. replication grid A set of repositories that share a common ID and can potentially transmit and receive logical objects through replication. A replication grid defines a set of ProtecTIER repositories and actions between them and is configured using the ProtecTIER Replication Manager. The ProtecTIER Replication Manager is a software component that is installed on a ProtecTIER server or a dedicated host. The ProtecTIER Replication Manager should be able to recognize all the members of the entire network the ProtecTIER Replication Manager handles on both replication subnets. The ProtecTIER Replication Manager is deployed separately from the ProtecTIER Manager on the customer's ProtecTIER server. The ProtecTIER Replication 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.
xxx
replication policy A policy made up of rules that define a set of objects (for example, VTL cartridges) from a source repository to be replicated to a target repository. repository unique ID (RID) A number that uniquely identifies the repository. The RID is created from the replication grid ID and the repository internal ID in the grid. replication timeframe A scheduled period of time for replication to take place for all policies. shelf A container of VTL cartridges within a ProtecTIER repository.
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 library's 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.
What's new in this edition

The following new functions are available in release 2.4: v Many-to-one replication v LUN masking v Red Hat upgrade to version 5.4 ProtecTIER "many-to-one" replication provides new and improved functionality. Major changes in and additions to this document since the last edition include the following: v Setting replication performance limits v Enhancements to the Replication Rate Control mechanism v v v v v v v Enhanced monitoring of repository space consumption Enhanced timeframe support Reserving space for "hub" repository local backup Additional replication information in the repository's cartridge view Disaster recovery site replacing production site operation ("takeover") Command line interface for Disaster Recovery (ptcli) Map view of the grid with a consolidated view of an entire topology group
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.
About this document
xxxi
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 Support for IBM System Storage and TotalStorage products Web address (URL) www.ibm.com http://www.ibm.com/planetwide 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. Note: If asked for an operating system, say "Storage". 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.
xxxii
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: www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss/ v Access installation and technical support information via the Web at: v v www.ibm.com/support The IBM Web site for Independent Software Vendor (ISV) support is: www.ibm.com/servers/storage/tape/resource-library.html The IBM System Storage TS7600 Interoperability Matrix Web site can be found at: www.ibm.com/storage/support/ For the latest information about SAN switches and directors, go to the following Web site: www.ibm.com/servers/storage/san 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
About this document
xxxiii
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) User's Guide, IBM part number 42C8237 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) User's 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. Click Information Centers > Systems > xSeries>. 3. Click Product information > Servers > xSeries. 4. From the Product family list, select System x3850. 5. 6. 7. 8. From the Type list, select System 7141. Click Go. On the Software and device drivers page, click the Documentation link. 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 User's Guide
How to send your comments

Your feedback is important in helping to provide the most accurate and highest quality information.
xxxiv
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
About this document
xxxv
xxxvi
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 It is scalable 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.
Storage Fabric ProtecTIER Server
Virtual Tape Drives Port 0 Server Running Backup Application Port 1 Virtual Robot Virtual Cartridges and Slots
Virtual Library
Virtual Library Repository
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:
ts760435
Backup Servers
Storage Fabric
ProtecTIER Server (Node) 1
Storage Fabric
Disk Arrays
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:
ts760432
Backup Servers
Storage Fabric
Cluster Internal Network Switch 1
Cluster Internal Network Switch 2
Storage Fabric
Disk Arrays
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 ProtecTIER's performance. The following diagram illustrates the details of the ProtecTIER cluster setup:
ts760433
Backup Server
ProtecTIER Manager Workstation
Front-End FC Port Eth 0 Node 1 Eth 1 Eth 2 Back-End FC Port Network Interfaces (NIC) Bond 0 Bond 0 Eth 0 Eth 1 Eth 2 Network Interfaces (NIC)
Front-End FC Port
Node 2
Back-End FC Port
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.
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.
ts760431
Cluster Internal Network
Disk Array
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 ProtecTIER Replication Manager is a server that remotely manages the grid's configuration (for example, grid creation/deletion, repository membership in the grid, etc.). In most cases, the ProtecTIER Replication Manager will reside on one of the ProtecTIER nodes.
Chapter 2. Completing the ProtecTIER system setup for new installations

This chapter details the prerequisites for completing the ProtecTIER system setup for new installations. If this is not a new installation and you are upgrading the ProtecTIER system, skip this chapter and go on to Upgrading and Configuring Red Hat Linux and ProtecTIER on page 25. 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.
Logging in to the ProtecTIER server

Complete this task to log in to the ProtecTIER server. Follow the steps below: 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 on any servers that are not running, 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 to Customizing the ProtecTIER server.
Customizing the ProtecTIER server

Complete this task to configure the ProtecTIER server. 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 server's command prompt, change to the /opt/dtc/install directory. To do so, enter the following command: cd /opt/dtc/install <enter> 2. Change the server's IP address, netmask, default gateway, and host name from the values that were set in manufacturing, to the values specific to the customer's 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 Customer Network IP address v Customer Network netmask v Customer Network default gateway v Customer Network hostname (This is the server's 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 customer's 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:

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 4, Installing ProtecTIER Manager, on page 37. 5. If you are in a clustered configuration, repeat the steps in this section on Server B, then go on to Chapter 4, Installing ProtecTIER Manager, on page 37.
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 subnets. This is necessary whenever traffic to any specific subnet is required to be sent through a different gateway and possibly a different network-interface than the default-gateway definition would otherwise dictate. | | Attention: Do not configure the replication ports, Eth3 and Eth4, on the same subnet as the external LAN port, Eth0. Doing so may cause replication errors. 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: 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 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> 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:
10
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. 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>
| |
Attention: Do not configure the replication ports, Eth3 and Eth4, on the same subnet as the external LAN port, Eth0. Doing so may cause replication errors. 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.
11
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 5. Updating cluster response
Changing the system date and time

The following procedure describes the steps required for changing the system's date, time and timezone. In a two-node cluster, running the command on one of the nodes will configure the system's date, time and timezone on both nodes. After configuring the ProtecTIER server, you can change the system's date, time and timezone and add timeservers to the system. 1. If you are not already connected to a node, 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. Access the /install directory by typing the command:
cd /opt/dtc/install/ ./ptconfig -setClock <Enter> <Enter>
4. Type the following command to begin the set clock configuration: As the procedure runs, the following is displayed:
Date, Time, Timezone & Timeserver(s) configuration ================================================== 1. Set date & time 2. Set Timezone 3. Set Timeserver(s) c. Commit changes and exit q. Exit without committing changes Please Choose:
5. Synchronize the date and time by typing 1 <Enter> in the Please Choose: field.
12
The following is displayed:

Please Choose:1 Please specify the date in DD/MM/YYYY format [09/11/2009]:
6. Type the date in the specified format and press <Enter>. If you do not enter a date, the default will be the date that appears within the brackets. The following is displayed:
Please specify the date in DD/MM/YYYY format [09/11/2009]: 09/11/2009 Please specify the time in HH:MM:SS format [11:56:16]:
7. Type the time in the specified format and press <Enter>. If you do not enter a time, the default will be the time that appears within the brackets. The following is displayed:
Date, Time, Timezone & Timeserver(s) configuration ================================================== 1. Set date & time 2. Set Timezone 3. Set Timeserver(s) c. Commit changes and exit * q. Exit without committing changes Please Choose:
Note: If you have typed in new information, an asterisk (*) will appear at the end of the c. Commit changes and exit menu option to show that there are modifications to be saved. At this point, you can choose either c to save the changes and exit the setClock configuration, choose q to exit the configuration without saving the changes, or continue synchronizing the local timezone (step 8) and/or adding the timeservers to the system (step 11 on page 14). 8. Synchronize the local timezone by typing 2 <Enter> in the Please Choose: field. The following is displayed:
Please Choose:2 Enter a 2 letter country code (or type m to enter the timezone manually):
9. Type, for example, US <Enter> for the United States. If you need a list of time zone codes from countries other than the United States, see Appendix D, Worldwide time zone codes, on page 191. The following is displayed:
13
Time zones under US: ==================== 1. America/New_York 2. America/Detroit 3. America/Kentucky/Louisville 4. America/Kentucky/Monticello 5. America/Indiana/Indianapolis 6. America/Indiana/Vincennes 7. America/Indiana/Knox 8. America/Indiana/Winamac 9. America/Indiana/Marengo 10. America/Indiana/Vevay 11. America/Chicago 12. America/Indiana/Tell_City 13. America/Indiana/Petersburg 14. America/Menominee 15. America/North_Dakota/Center 16. America/North_Dakota/New_Salem 17. America/Denver 18. America/Boise 19. America/Shiprock 20. America/Phoenix 21. America/Los_Angeles 22. America/Anchorage 23. America/Juneau 24. America/Yakutat 25. America/Nome 26. America/Adak 27. Pacific/Honolulu Please choose a timezone:
If you typed m to manually enter the timezone, the following is displayed:

Enter the time zone (case sensitive):
Type, for example, Italy <Enter>. 10. Type a number corresponding to the timezone you want to synchronize from the list under the country code entered. The following is displayed:
Date, Time, Timezone & Timeserver(s) configuration ================================================== 1. Set date & time 2. Set Timezone 3. Set Timeserver(s) c. Commit changes and exit * q. Exit without commiting changes Please Choose:
As previously stated, you can choose either c to save the changes and exit the setClock configuration, choose q to exit the configuration without saving the changes, or continue synchronizing the local timezone and/or adding the timeservers to the system. 11. Add timeservers to the system by typing 3 <Enter> in the Please Choose: field. The following is displayed: a. Please specify the timeserver's IP Address: Type the timeserver's IP Address. For example: 192.168.10.15 <Enter> b. Would you like to set a secondary timeserver? (yes|no) Type y <Enter> to set a secondary timeserver. c. Please specify the secondary timeserver's IP Address:
14
Type the secondary timeserver's IP address. For example: 192.168.12.15 <Enter> The following is displayed:
Date, Time, Timezone & Timeserver(s) configuration ================================================== 1. Set date & time 2. Set Timezone 3. Set Timeserver(s) c. Commit changes and exit * q. Exit without commiting changes Please Choose:
12. Confirm and save your changes to the configuration by typing c <Enter> in the Please Choose: field. A list of the configuration changes is displayed for review.
Reviewing the results

Note: If only the date was modified, and not the timezones and/or timeservers, only the date will be displayed in the contents. For example: if you modified the date, added a primary and secondary time server, and specified America/Chicago as the time zone, when you choose c to commit the changes and exit, the file contents appear as follows:
Please review the following information: ======================================== Date: Mon Nov 9 14:51:34 2009 Primary time server: 192.168.10.11 Secondary time server: 192.168.15.11 Timezone: America/Chicago Do you wish to apply those settings? (yes|no)
Type y to save and apply the changes. Note: the cluster & VTFD services on all nodes must be stopped in order to continue. Do you wish to continue? (yes|no) Type y to stop and restart the cluster and VTFD services on all the nodes.
Stopping Cluster Services Stopping NTPD Setting Time Zone Setting Timeserver Setting Date & Time Starting NTPD Starting cluster Cluster Started [ [ [ [ [ [ [ Done Done Done Done Done Done Done ] ] ] ] ] ] ]
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.
15
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 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 user's data. Recoverable errors are logged in the ProtecTIER logs and generate an SNMP warning notification trap.
16
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 inquiries, 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 utility's objective is to test maximal replication performance between two future PT repositories by emulating the network usage patterns of PT's 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.4 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. 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
17
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 [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.
18
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 300 seconds (-t 300), while the last test monitored TCP performance during that time. Test 1: Latency This test checks the nominal network link latency and packet loss. Example result:
*** Latency PING 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
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
19
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. 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.
20
Chapter 3. Upgrading and Configuring Red Hat Linux and ProtecTIER

This chapter provides instructions for upgrading Red Hat Linux and ProtecTIER on the legacy servers. If you need to configure ProtecTIER for replication, contact a trained ProtecTIER specialist. Portions of the upgrade and configuration processes vary, depending on whether data replication is being used. Notes: v The software upgrade procedure is nonconcurrent. You must complete both the Red Hat and ProtecTIER upgrades on one server, before moving on to the next one. v Upgrading Red Hat Linux can take from one to two hours per server. This time does not include upgrading ProtecTIER or configuring the server for replication, if required. You will first run the Red Hat upgrade script, and then initiate ./autorun, which performs the following tasks on each server: v Installs ProtecTIER v2.4.0.0 and the associated RPMs Red Hat Package Managers (RPMs) ProtecTIER Replication Manager, and the RAS package. v Updates server firmware components. v Checks the DS controller firmware, adds a password to it, and suggests upgrading to the required firmware, if necessary. The upgrade can be performed at a later time. (Applies to TS7650 Appliances, only). v Reboots the server. Important: If a server is already being used for replication, it is not necessary to use ./ptconfig to reconfigure replication. The server's replication settings are not be overwritten or altered as a result of the software upgrade process.
Preparing for the 2.4.0.0 upgrade

Servers that are currently running ProtecTIER v2.2.x must be upgraded to ProtecTIER 2.3.x.x before being upgraded to ProtecTIER v2.4.0.0. In addition, any servers that are currently running a version of RAS lower than 3.2.12, or on which RAS is not installed, will require that RAS configuration be performed after the servers are upgraded to ProtecTIER v2.4.0.0. Important: If all of the servers you are working on are already running ProtecTIER v2.3.x.x, you can skip this chapter and go on to Upgrading and Configuring Red Hat Linux and ProtecTIER on page 25. Otherwise, follow the procedures below to download and install ProtecTIER v2.3.x.x, as applicable. To determine the versions of ProtecTIER and RAS currently running on the server(s), refer to Checking the ProtecTIER and RAS versions on page 22, below.
21
Checking the ProtecTIER and RAS versions

Perform the procedure below on each server for which you need version information. Make note of the ProtecTIER and RAS versions for each server, and then refer to Table 2 at the end of this section, to determine how to proceed. 1. Log in to the server: 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. Notes: v During the boot cycle one or more warning or failure messages, including ones specific to Eth4 and Eth5, may display. These messages are expected and are not cause for alarm. v During the boot cycle, the ProtecTIER file systems are mounted. If the message: Running... displays, press <enter> to proceed to the login prompt. 2. At the login: prompt, log in with the ID root and the password admin. 3. Check the ProtecTIER version. Enter the command: cat /opt/dtc/app/sys/verinfo <enter> The ProtecTIER version is provided in the first line of output, in the first three digits after the colon. The version information looks similar to the following: PT version : 2.3.0 4. Check the RAS version. Enter the command: rpm -qa | grep RAS <enter> The RAS package code level (contained between the second hyphen and the underscore) displays. For example: RASpackage-4-3.2.12_mmddyy Note: If no RAS version information is returned, this indicates that the RAS package is not installed on the server. You will need to perform RAS configuration on the server, as described in Configuring the RAS package on page 35, after you have upgraded the server to ProtecTIER 2.4.0.0. 5. Refer to the table to see how to proceed:
Table 2. Version results and required actions If the ProtecTIER version is: 2.3.0 or higher And the RAS version is: 3.2.12 or higher The required action is: Skip the remaining procedures in this chapter and go on to Upgrading and Configuring Red Hat Linux and ProtecTIER on page 25. Download and install ProtecTIER v2.3.x.x. Refer to Downloading ProtecTIER v2.3.x.x on page 23.
2.2.x
3.2.12 or higher
22
Table 2. Version results and required actions (continued) If the ProtecTIER version is: 2.2x And the RAS version is: 3.2.11 or lower OR The version number is not returned. The required action is: Download and install ProtecTIER v2.3.x.x. Refer to Downloading ProtecTIER v2.3.x.x. AND Perform RAS configuration on the server after you have upgraded the server to ProtecTIER v2.4.0.0.
Downloading ProtecTIER v2.3.x.x

Note: For additional information about the ProtecTIER v2.3.x.x download (including alternate installation instructions using the TSSC), refer to the IBM System Storage TS7650G and TS7650 with ProtecTIER Software Release Notes GC53-1195-19, available on the ProtecTIER patch 2.3.x.x page of the IBM Web site. 1. Go to www.ibm.com. 2. From the Home page, click: Support & Downloads Support by Product System Storage The Support for IBM System Storage and TotalStorage products page, displays. 3. From the Product family: dropdown list, select: Tape Systems. 4. Prom the Product: dropdown list, select: TS7650 ProtecTIER Deduplication Appliances or TS7650G with ProtecTIER, as appropriate, and then click Go. The Support for TS7650G with ProtecTIER page, displays. 5. In the Support & Downloads box, click: Download. 6. In the Recommended Fix box, click: Downloadable files. The Download results page, displays. 7. From the Results list, click: ProtecTIER patch 2.3.x.x . The ProtecTIER patch 2.3.x.x page, displays. 8. Scroll to the Download package ProtecTIER patch 2.3.x.x section, then in the Download Options box, click: FTP. The Terms and Conditions page, displays. 9. Read the information and then click: I agree. The Opening PT_Linux_V2.3.x.x.x86_64.tar dialog box, opens. 10. Select Save file, then click OK. The ProtecTIER v2.3.x.x software downloads to the local hard drive. 11. Copy the PT_Linux_V2.3.x.x.x86_64.tar to a CD. 12. Go to Installing ProtecTIER v2.3.x.x.
Installing ProtecTIER v2.3.x.x

Perform the procedures below on each server that is currently running ProtecTIER v2.2.x, and being upgraded to ProtecTIER 2.4.0.0. For additional information about the v2.3.x.x update patch (including alternate installation instructions using the
23
TSSC), refer to the IBM System Storage TS7650G and TS7650 with ProtecTIER Software Release Notes GC53-1195-19, available on the ProtecTIER patch 2.3.x.x page of the IBM Web site. | | | | | | | Notes: v If you do not plan to immediately upgrade from v2.3.x.x to v2.4.0.0, you may need to update the firmware. Refer to Appendix A, Verifying and upgrading the storage subsystem firmware, NVSRAM, and ESM, on page 181 for additional information and instructions. v You cannot upgrade the servers in parallel. You must complete the upgrade on one server before moving on to the next one. 1. Log in to the server: 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. Notes: v During the boot cycle one or more warning or failure messages, including ones specific to Eth4 and Eth5, may display. These messages are expected and are not cause for alarm. v During the boot cycle, the ProtecTIER file systems are mounted. If the message: Running... displays, press <enter> to proceed to the login prompt. 2. At the login: prompt, log in with the ID root and the password admin. 3. Stop the vtfd service on the server. Enter the command: service vtfd shutdown <enter> 4. Insert the CD that contains ProtecTIER v2.3.x.x, into the server's CD-ROM drive. 5. When the drive light stops blinking, enter the commands: mkdir -p /mnt/cdrom <enter> mount /dev/cdrom /mnt/cdrom <enter> The following output displays: mount: block device /dev/cdrom is write-protected. mounting read-only 6. Copy the PT_Linux_V2.3.x.x.x86_64.tar file from the CD to the /install directory on the server's hard drive. Enter the command below: cp <filename>.tar /install <enter> Note: The file copy may take a few moments to complete. 7. Change to the /install directory. Enter the command: cd /install <enter> 8. Extract the installation files into a new directory within the /install directory. Enter the command: tar -xvf PT_Linux_V2.3.x.x.x86_64.tar <enter> The PT_Linux_V2.3.x.x.x86_64.tar directory is created. 9. Change to the PT_Linux_V2.3.x.x.x86_64.tar directory. Enter the command: cd /install/PT_Linux_V2.3.x.x.x86_64 <enter> Note: You will install ProtecTIER 2.3.x.x from this directory.
24
10. Eject the CD from the CD-ROM drive. Enter the command: eject <enter> 11. Start the Red Hat upgrade process. Enter the command: ./autorun -f <enter> 12. When asked if you want to upgrade the kernel rpm to the new one: 2.6.18-92.mm0.IT328127.el5, type: y <enter>. 13. When the process is complete, you are prompted to reboot the server. Type: y <enter>. When the reboot completes, the login: prompt displays. 14. Confirm that the new RPM kernel is loaded. Enter the command: uname -r <enter> The following output displays: 2.6.18-164.11.1.el5 Note: If the output displayed is different from what is shown above, contact your next level of support. 15. Verify the Red Hat version. Enter the command: cat /etc/redhat-release <enter> The following output displays: Red Hat Enterprise Linux Server release 5.4 (Tikanga) Note: If the output displayed is different from what is shown above, contact your next level of support. 16. Start the ProtecTIER v2.3.x.x upgrade. Enter the command: ./autorun -f <enter> 17. When the upgrade is complete, you are prompted to reboot the server. Type: y <enter>. When the reboot completes, the login: prompt displays. 18. Restart the vtfd service. Enter the command: service vtfd init <enter> 19. Verify the component versions on the server (optional). Enter the command: /opt/dtc/app/sbin/get_versions <enter> 20. If applicable, repeat steps 1 on page 24 through 19 on any other servers running ProtecTIER v2.2.x. 21. When you have finished installing the ProtecTIER v2.3.x.x upgrade, go on to Upgrading and Configuring Red Hat Linux and ProtecTIER.
Upgrading and Configuring Red Hat Linux and ProtecTIER

This section provides instructions for upgrading Red Hat Linux and ProtecTIER on the legacy servers. Portions of the upgrade and configuration processes vary, depending upon the server type(s) (3958 DD1, 3958 DD3, or 3958 AP1), the system type (stand-alone or clustered), and whether data replication is being used. Notes: v The software upgrade procedure is nonconcurrent. You must complete both the Red Hat and ProtecTIER upgrades on one server, before moving on to the next one.
25
v Upgrading Red Hat Linux can take from one to two hours per server. This time does not include upgrading ProtecTIER or configuring the server for replication, if required. You will first run the Red Hat upgrade script, and then execute ./autorun, which performs the following tasks on each server: v Installs ProtecTIER v2.4.0.0 and the associated RPMs, ProtecTIER Replication Manager, and the RAS package. v Updates server firmware components. v Checks the firmware level of the disk storage components attached to TS7650 Appliances, adds a password (ibm2serv), and suggests upgrading the storage components to the required firmware level, if necessary. (The upgrade can be performed at a later time.) The ./autorun does not check the firmware levels of the disk storage components attached to TS7650G Gateways. For information and instructions for these components, refer to the manufacturer's documentation. v Reboots the server. Important: If a server is already being used for replication, it is not necessary to use ./ptconfig to reconfigure replication. The server's replication settings will not be overwritten or altered as a result of the software upgrade process. | | | | | | | | | | | | | | | | | | | | | | | | | | |
Upgrading Red Hat and ProtecTIER on a stand-alone server

Use the procedures in this section to upgrade the versions of Red Hat and ProtecTIER running on a legacy server in a stand-alone configuration. The Red Hat Linux upgrade software is provided on the IBM System Storage ProtecTIER Maintenance and Recovery Disk, and the ProtecTIER upgrade software is provided on the IBM System Storage ProtecTIER Enterprise Edition V2.4.1.0. DVD. Important: If you are upgrading a 3958 DD1 server that is being used for replication, installation of the second dual-port Ethernet card (Feature Code 3448) must be completed before performing the Red Hat and ProtecTIER upgrades. Follow the procedure below to begin updating Red Hat and then ProtecTIER on a stand-alone server: 1. Log in to the server: 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. Notes: v During the boot cycle one or more warning or failure messages, including ones specific to Eth4 and Eth5, may display. These messages are expected and are not cause for alarm. v During the boot cycle, the ProtecTIER file systems are mounted. If the message: Running... displays, press <enter> to proceed to the login prompt. 2. At the login: prompt, log in with the ID root and the password admin. 3. Stop the vtfd and cluster services on the server. Enter the command: service vtfd stop <enter>
26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
service ptcluster stop <enter> 4. Insert the IBM System Storage ProtecTIER Maintenance and Recovery Disk into the server's CD-ROM drive. 5. When the drive light stops blinking, enter the commands: mkdir -p /mnt/cdrom <enter> mount /dev/cdrom /mnt/cdrom <enter> The following output displays: mount: block device /dev/cdrom is write-protected. mounting read-only 6. From the /root directory, execute the Red Hat update script. Enter the command: /mnt/cdrom/update-rh.pl <enter> The update-rh.pl script automatically stops the RAS package if it is running, and then starts the Red Hat upgrade on the server. Note: The Red Hat upgrade process takes approximately 70-80 minutes to complete. During this time, do not remove the DVD, or otherwise interfere with the server. The following messages display: Stopping services, please wait Stopping Cluster Services [ Done ] Services stopped Importing public keys...done Upgrading kernel...done install (2393/2393) (100%) Global_File_System-f... done Done Validating updates... 7. When the upgrade is complete, the messages below display: Validation passed!... (100%) Please eject the DVD, reboot the host, then install new PT server package. If there is an additional node which has not been updated yet, update it. 8. Eject the DVD from the CD-ROM drive. Enter the command: cd <enter> eject <enter> Remove the DVD from the CD-ROM drive. 9. Reboot the server. Enter the command: reboot <enter> The reboot will take several minutes. Upon completion, the login: prompt displays. The Red Hat upgrade is complete. Continue to the next step to upgrade ProtecTIER. 10. Insert the IBM System Storage ProtecTIER Enterprise Edition V2.4.1.0. DVD into the server's CD-ROM drive. 11. When the drive light stops blinking, enter the commands: mkdir -p /mnt/cdrom <enter> mount /dev/cdrom /mnt/cdrom <enter> The following output displays:
27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
mount: block device /dev/cdrom is write-protected. mounting read-only 12. Change to the local installation directory. Enter the command: cd /mnt/cdrom <enter> 13. List the DVD's contents to determine the name of the installation file. Enter the command: ls <enter> 14. From the list displayed, locate the file with the .tar extension and copy it to the /install directory on the server's hard drive. Enter the command: cp <filename>.tar /install <enter> Note: The file copy may take up to five minutes to complete. 15. Change to the /install directory. Enter the command: cd /install <enter> 16. Extract the installation files into a new directory within the /install directory. Enter the command: tar -xvf <tar filename>.tar <enter> The <filename> directory is created. For example: PT_Linux_V2.4.0.0.x86_64. 17. Change to the <filename> directory. Enter the command: cd /install/<filename> <enter> For example: cd /install/PT_Linux_V2.4.0.0.x86_64 Note: You will perform the remainder of the installation from this directory. 18. Eject the IBM System Storage ProtecTIER Enterprise Edition V2.4.1.0. DVD from the CD-ROM drive. Enter the command: eject <enter> Remove the DVD from the CD-ROM drive. 19. Execute the autorun utility. Enter the command: ./autorun <enter> A series of messages display as the autorun utility installs the ProtecTIER v2.4.0.0 upgrade, and performs the additional tasks outlined in Upgrading and Configuring Red Hat Linux and ProtecTIER on page 25. Execution of autorun may take up to 15 minutes. Upon completion, the following message displays: The system will now reboot! After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue... 20. Press <enter> to reboot the server. Allow vtfd to fully restart before proceeding. Notes: v While the server is rebooting, verify that the DVD was ejected in step 18. If not, press the button on the front of the disc drive to manually eject the DVD, now. v During the boot cycle one or more warning or failure messages, including ones specific to Eth4 and Eth5, may display. These messages are expected and are not cause for alarm. v During the boot cycle, the ProtecTIER file systems are mounted. If the message: Running... displays, press <enter> to proceed to the login prompt.
28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
The reboot will take several minutes. Upon completion, the login: prompt displays. The ProtecTIER upgrade is now complete. 21. Go on to Performing post-upgrade tasks.
Performing post-upgrade tasks

1. Verify that RAS restarted and is running on the server. To do so: a. Display the RAS menu. Enter the command: rasMenu <enter> The output shown below displays: +------------------------------------------+ RAS Text Based Menu running on <servername> 1) Check if RAS is running 2) Run RAS environment check 3) Start RAS 4) Stop RAS 5) Get RAS Version 6) Get PT Code Version 7) Display Firmware Levels 8) Manage Configuration (...) 9) System Health Monitoring (...) 10) Problem management (...) 11) Call Home Commands (...) 12) Collect Logs (...) 13) Enterprise Controller (...) E) Exit +------------------------------------------+ b. Select the Check if RAS is running option, by typing: 1 <enter>. v If RAS is running, the following messages display: Begin Processing Procedure RAS is running 1) Exit the RAS Menu by typing: e <enter>. 2) Go on to step 2 on page 30. v If RAS is not running, the following messages display: Begin Processing Procedure RAS is down You will need to manually start RAS on the server. To do so: 1) Select the Start RAS option, by typing: 3 <enter>. The following messages display: Begin Processing Procedure >>> You are about to start RAS. >>>Enter y or yes to continue or any other key to exit. 2) Type: y <enter>. The following messages display: StartRas ended successfully End Processing Procedure
29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Press any key to continue 3) Exit the RAS Menu by typing: e <enter>. 4) Go on to step 2. 2. Verify the server's current time, date, and time zone settings: a. Enter the command: date <enter> The server's time, date, and time zone settings, display. For example: Wed Apr 14 14:19:50 EDT 2010 b. Confirm that the settings reflect the customer's preferences. If changes are necessary, refer to Changing the system date and time on page 12 for instructions. 3. Determine whether the server needs to be configured for replication, then proceed accordingly: Note: If Replication was previously configured on the server, you do not need to configure it again. The existing replication settings are still valid. v If the server you are working on does not need to be configured for replication, go to Configuring, verifying, and testing the RAS package on page 35. v If the server you are working on does need to be configured for replication, contact a trained ProtecTIER specialist.
Upgrading Red Hat and ProtecTIER on clustered servers

Use the procedure below to upgrade the versions of Red Hat and ProtecTIER running on Servers A and B in a cluster. If you are working stand-alone servers, follow the procedures in Upgrading Red Hat and ProtecTIER on a stand-alone server on page 26, instead. Notes: v The instructions in this section apply to legacy 3958 DD1, 3958 DD3, and 3958 AP1 servers. v The Red Hat Linux upgrade software is provided on the IBM System Storage ProtecTIER Maintenance and Recovery Disk, and the ProtecTIER upgrade software is provided on the IBM System Storage ProtecTIER Enterprise Edition V2.4.1.0. DVD. Important: Perform all procedures on Server A (the bottom server) first, and then on Server B. To avoid complications, including unnecessary system reboots, you must start upgrading Red Hat and then ProtecTIER on Server A. 1. Log in to Server A: a. If not already present, connect a USB keyboard and monitor to the server. b. Verify that the server is powered on: v If it is powered on, go to step 2 on page 31. v If it is not powered on, do so now. Wait for the boot cycle to complete, then go to step 2 on page 31. Notes: v During the boot cycle one or more warning or failure messages, including ones specific to Eth4 and Eth5, might display. These messages are expected and are not cause for alarm.
30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
v During the boot cycle, the ProtecTIER file systems are mounted. If the message Running... displays, press <enter> to proceed to the login prompt. 2. At the login prompt, log in with the ID root and the password admin. 3. Verify that you are connected to Server A, and then stop the vtfd and cluster services on the server. Enter the commands: service vtfd stop <enter> service ptcluster stop <enter> 4. Insert the IBM System Storage ProtecTIER Maintenance and Recovery Disk into the server's CD-ROM drive. 5. When the drive light stops blinking, enter the commands: mkdir -p /mnt/cdrom <enter> mount /dev/cdrom /mnt/cdrom <enter> The following output displays: mount: block device /dev/cdrom is write-protected. mounting read-only 6. From the /root directory, run the Red Hat update script. Enter the command: /mnt/cdrom/update-rh.pl <enter> The update-rh.pl script automatically stops the RAS package if it is running, and then starts the Red Hat upgrade on the server. Note: The Red Hat upgrade process takes approximately 70-80 minutes to complete. During this time, do not remove the DVD or otherwise interfere with the server. The following messages display: Stopping services, please wait Stopping Cluster Services [ Done ] Services stopped Importing public keys...done Upgrading kernel...done install (2393/2393) (100%) Global_File_System-f... done Done Validating updates... 7. When the upgrade is complete, the messages below display: Validation passed!... (100%) Please eject the DVD, reboot the host, then install new PT server package. If there is an additional node which has not been updated yet, update it. 8. Eject the DVD from the CD-ROM drive. Enter the commands: cd <enter> eject <enter> Remove the DVD from the CD-ROM drive. 9. Reboot the server. Enter the command: reboot <enter> The reboot will take several minutes. Upon completion, the login prompt displays. The Red Hat upgrade is complete. 10. Continue with the next step to upgrade ProtecTIER on Server A.
31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
11. Disconnect the USB keyboard and monitor from Server A and connect them to Server B. a. Verify that Server B is powered on: v If it is powered on, go to step 12. v If it is not powered on, do so now. Wait for the boot cycle to complete, then go to step 12. Notes: v During the boot cycle one or more warning or failure messages, including ones specific to Eth4 and Eth5, might display. These messages are expected and are not cause for alarm. v During the boot cycle, the ProtecTIER file systems are mounted. If the message: Running... displays, press Enter to proceed to the login prompt. At the login prompt, log in with the ID root and the password admin. Verify that you are connected to Server B, and then shutdown the vtfd service. Enter the command: service vtfd shutdown <enter> Disconnect the USB keyboard and monitor from Server B and reconnect them to Server A.Using the KVM switch, press the PrtSc key on the TSSC keyboard. Then, select 3958 Node A from the list of devices and press Enter. Insert the IBM System Storage ProtecTIER Enterprise Edition V2.4.1.0. DVD into the server's CD-ROM drive.
12. 13.
14.
15.
16. When the drive light stops blinking, enter the commands: mkdir -p /mnt/cdrom <enter> mount /dev/cdrom /mnt/cdrom <enter> The following output displays: mount: block device /dev/cdrom is write-protected. mounting read-only 17. Change to the local installation directory. Enter the command: cd /mnt/cdrom <enter> 18. List the DVD's contents to determine the name of the installation file. Enter the command: ls <enter> 19. From the list displayed, locate the file with the .tar extension and copy it to the /install directory on the server's hard drive. Enter the command: cp <filename>.tar /install <enter> Note: The file copy might take up to five minutes to complete. 20. Change to the /install directory. Enter the command: cd /install <enter> 21. Extract the installation files into a new directory within the /install directory. Enter the command: tar -xvf <tar filename>.tar <enter> The <filename> directory is created. For example: PT_Linux_V2.4.0.0.x86_64. 22. After the files are extracted, list the /install directory's contents to get the name of the ProtecTIER directory that you will change to in the next step. Enter the command: ls <enter> 23. Change to the <ProtecTIER directory name> directory. Enter the command:
32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
cd <directory name> <enter> For example: cd PT_Linux_V2.4.0.0.x86_64 Note: You will perform the remainder of the installation from this directory. 24. Eject the IBM System Storage ProtecTIER Enterprise Edition V2.4.1.0. DVD from the CD-ROM drive. Enter the command: eject <enter> Remove the DVD from the CD-ROM drive. 25. Execute the autorun utility. Enter the command: ./autorun <enter> A series of messages display as the autorun utility installs the ProtecTIER v2.4.0.0 upgrade, and performs the additional tasks outlined in Upgrading and Configuring Red Hat Linux and ProtecTIER on page 25. Execution of autorun might take up to 15 minutes. During the autorun process, you will be prompted to upgrade the DS firmware level. This is the firmware level of the attached storage. Entering Yes instructs autorun to check the firmware level, and update it to current release levels, as necessary. Because of the varied amounts of attached storage, the firmware check could take several minutes to complete. If it is determined that the firmware requires an update, the process could take up to an hour. Upon completion, the following message displays: The system will now reboot! After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue... 26. Press Enter to reboot the server. Allow vtfd to fully restart on Server A before proceeding. Notes: v While the server is rebooting, verify that the DVD was ejected in step 24. If not, press the button on the front of the disc drive to manually eject the DVD now. v During the boot cycle one or more warning or failure messages, including ones specific to Eth4 and Eth5, might display. These messages are expected and are not cause for alarm. v During the boot cycle, the ProtecTIER file systems are mounted. If the message: Running... displays, press Enter to proceed to the login prompt. The reboot will take several minutes. Upon completion, the login prompt displays. During the reboot, RAS is automatically restarted on the server. The reboot will take several minutes. The ProtecTIER upgrade is now complete on Server A. Continue to the next step to upgrade Red Hat and ProtecTIER on Server B. Disconnect the USB keyboard and monitor from Server A and connect them to Server B.Using the KVM switch, press the PrtSc key on the TSSC keyboard. Then, select 3958 Node B from the list of devices and press Enter. At the login prompt, log in with the ID root and the password admin. Verify that you are connected to Server B, and then stop the ptcluster service on Server B. Enter the command: service ptcluster stop <enter> Repeat steps 4 on page 31 through 9 on page 31 on Server B to upgrade Red Hat on Server B.
27.
28. 29.
30.
33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
31. Repeat steps 15 on page 32 through 26 on page 33 on Server B to upgrade ProtecTIER on Server B. 32. Initialize the vtfd service on Server B. Enter the command: service vtfd init <enter> Allow vtfd to fully restart on Server B before proceeding. 33. Go on to Performing post-upgrade tasks.
Performing post-upgrade tasks

1. Verify that RAS restarted and is running on the server. To do so: a. Display the RAS menu. Enter the command: rasMenu <enter> The output shown below displays: +------------------------------------------+ RAS Text Based Menu running on <servername> 1) Check if RAS is running 2) Run RAS environment check 3) Start RAS 4) Stop RAS 5) Get RAS Version 6) Get PT Code Version 7) Display Firmware Levels 8) Manage Configuration (...) 9) System Health Monitoring (...) 10) Problem management (...) 11) Call Home Commands (...) 12) Collect Logs (...) 13) Enterprise Controller (...) E) Exit +------------------------------------------+ b. Select the Check if RAS is running option, by typing: 1 <enter>. v If RAS is running, the following messages display: Begin Processing Procedure RAS is running 1) Exit the RAS Menu by typing: e <enter>. 2) Go on to step 2 on page 35. v If RAS is not running, the following messages display: Begin Processing Procedure RAS is down You will need to manually start RAS on the server. To do so: 1) Select the Start RAS option, by typing: 3 <enter>. The following messages display: Begin Processing Procedure >>> You are about to start RAS. >>>Enter y or yes to continue or any other key to exit. 2) Type: y <enter>.
34
| | | | | | | | | | | | | | | | | | | | | |
The following messages display: StartRas ended successfully End Processing Procedure Press any key to continue 3) Exit the RAS Menu by typing: e <enter>. 4) Go on to step 2. 2. Verify the server's current time, date, and time zone settings: a. Enter the command: date <enter> The server's time, date, and time zone settings, display. For example: Wed Apr 14 14:19:50 EDT 2010 b. Confirm that the settings reflect the customer's preferences. If changes are necessary, refer to Changing the system date and time on page 12 for instructions. 3. Determine whether the server needs to be configured for replication, then proceed accordingly: Note: If Replication was previously configured on the server, you do not need to configure it again. The existing replication settings are still valid. v If the server you are working on does not need to be configured for replication, go to Configuring, verifying, and testing the RAS package. v If the server you are working on does need to be configured for replication, contact a trained ProtecTIER specialist.
Configuring, verifying, and testing the RAS package

This chapter provides instructions for configuring the RAS package performing RAS verification and validation checks, and testing Call Home.
Configuring the RAS package

Use the procedure below to configure the RAS package on all servers that were upgraded to ProtecTIER v2.4.0.0. In addition to performing configuration tasks, ./ptconfig -configRAS utility also updates system drivers, as needed. 1. Attach the USB keyboard and monitor to the stand-alone server, or to Server A in a cluster. 2. Verify that the server is powered-on: v If it is powered on, go to step 3. v If it is not powered on do so now, wait for the boot cycle to complete, then go to step 3. 3. At the login: prompt, log in with the ID root and the password admin. 4. Configure the RAS package on the server. Enter the commands: cd /opt/dtc/install and press Enter. ./ptconfig -configRAS and press Enter. The ./ptconfig -configRAS utility performs a number of system checks, then starts the RAS Interactive Tool (RIT). The RIT allows you to set (or update) the configuration parameters for the customer's environment. a. When prompted to perform changes to the RAS configuration, type: yes and press Enter.
35
Doing so will allow you to review the current settings in the properties file that displays. If changes are required, you can make them during this process. Note: It is highly likely that you will retain the same configured frame value as previously set for this server. Only change the frame setting if you are sure that you want to reassign it to a different IP value for the TSSC connection. In most cases, you will select no when prompted to change the frame value. b. When prompted to change or update the disk storage or RAS configuration, type: yes and press Enter. Doing so will allow you to confirm or make changes to the properties file. Typically, you will only need to verify the existing settings. c. When you are finished using the RIT, press Enter to exit. 5. Disconnect the USB keyboard and monitor and connect them to the next stand-alone server, or to Server B in a cluster. 6. Repeat steps 2 on page 35 through 5 on any additional upgraded servers. Following the RAS configuration, the code automatically checks and updates any drivers that are not at current release levels. 7. When RAS configuration is complete on all servers that were upgraded to ProtecTIER 2.4.0.0, proceed to the next section or contact a trained ProtecTIER specialist for further assistance.
36
Chapter 4. Installing ProtecTIER Manager

This chapter describes how to install, configure, and uninstall the ProtecTIER Manager software. The ProtecTIER system is managed using the ProtecTIER Manager software. It is recommended that you install the ProtecTIER Manager software on one or more workstations, and not directly on the ProtecTIER servers. ProtecTIER Manager enables you to: v Configure ProtecTIER 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 ProtecTIER Replication Manager software
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/64 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 of 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.
Upgrading ProtecTIER Manager

Use the procedures in this chapter to upgrade the version of ProtecTIER Manager on the ProtecTIER Manager Workstation. Important: Before starting the upgrade, make sure the currently-installed ProtecTIER Manager application is closed.
37
The ProtecTIER Manager installer is provided on your IBM System Storage ProtecTIER Manager V2.4.3.0 DVD. Different ProtecTIER Manager installers are used for Windows and Linux. Ensure that the installer that 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. v If you are installing ProtecTIER Manager on a workstation running Linux, see Installing on Linux on page 39. 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 40.
Installing on Windows
Complete this task to upgrade ProtecTIER Manager on a Windows system. Perform the following steps to upgrade ProtecTIER Manager on a Windows system: 1. Insert theIBM System Storage ProtecTIER Manager V2.4.3.0 DVD 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 server's CD-ROM drive). c. Click OK. The contents of the IBM System Storage ProtecTIER Manager V2.4.3.0 DVD displays. 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 Don't create icons - No shortcuts are created.
38
6.
7. 8.
9.
10.
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. Click Next. The Pre-Installation Summary screen displays the Install and Shortcut folder locations and the disk space information of the target for installation. Review the Summary screen, and click Install to start the installation. The Installing ProtecTIER Manager screen is displayed. When the installation is complete and ProtecTIER Manager has been successfully installed, click Done. The ProtecTIER Installation wizard closes and the upgrade process is complete. If you configured replication, you must create and configure the replication before replication is fully functional. Refer to Enabling replication on page 47 for detailed information. If you did not configure replication, you can now resume use of your ProtecTIER system.
Installing on Linux
Complete this task to upgrade ProtecTIER Manager on a Linux system. Perform the following steps to install ProtecTIER Manager on Linux: 1. Insert the IBM System Storage ProtecTIER Manager V2.4.3.0 DVD into the CD-ROM drive of the designated ProtecTIER Manager workstation. 2. Run the ProtecTIER Manager installer. Note: The following presumes that 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 that 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.
Chapter 4. Installing ProtecTIER Manager
39
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 user's files are typically stored. For example: /home/bill. 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 workstation's hard drive. v Don't create links No links are created. 8. Click Next. The Pre-Installation Summary screen is displayed. 9. 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. 10. Click Done. The ProtecTIER Manager wizard closes. When the command prompt returns in the Terminal window, type exit to close the window. The upgrade process is complete. 11. If you configured replication, you must create and configure the replication before replication is fully functional. Refer to Enabling replication on page 47 for detailed information. 12. If you did not configure replication, you can now resume use of your ProtecTIER system.
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.
40
Chapter 5. 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 143.) The default username and password for each of these accounts are as follows:
Table 3. 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 that you want to manage using the ProtecTIER Manager. 1. Click the Login button. The Login dialog box is displayed. 2. Enter your username and password. 3. Click Ok. The Login dialog box closes and you are logged into the ProtecTIER Manager. It is recommended that you change or replace these default user accounts. (For more information, see Chapter 13, Managing users, on page 143.) 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?
Clicking Yes forces the other Administrator to logout.
Changing the Support System settings

The following task illustrates how to change the support system settings. ProtecTIER Manager does not use the OS system fonts and colors by default. The support system settings can be applied, however, in the ProtecTIER Manager Preferences dialog. Note: Restart ProtecTIER Manager to apply the changes.
41
Follow the steps below to apply the support system settings: 1. Open the ProtecTIER Manager GUI interface. 2. Select Preferences from the Tools menu. The Preferences window is displayed. 3. Click the Appearances tab on the Preferences window. 4. Select Support system settings and click ok. 5. Close and reopen ProtecTIER Manager for the new settings to take place. 6. Resume working with ProtecTIER Manager.
Color selection
The following task illustrates how to change the principal color settings used by ProtecTIER Manager. Follow the steps below to modify the ProtecTIER Manager color settings: 1. Open the ProtecTIER Manager GUI interface. 2. Select Preferences from the Tools menu. The Preferences window is displayed. 3. Click the Appearances tab on the Preferences window. A color swatch is displayed next to each GUI attribute. 4. Click on the color swatch you want to modify. The Color selection window is displayed. 5. Select a new color for the GUI attribute and click Ok. 6. The table below displays the color selections and their usage in ProtecTIER Manager:
Table 4. Color selections for the ProtecTIER Manager GUI Color selection Positive/Success Negative Prohibit Warning/Hazard Information Read Write Hyperlink Plots Used Allocable Fragmented Nominal Physical Usage Shows something positive to the user Shows something negative to the user Used to display warnings to the user Used to show information that does not include the above items Mainly used in graphs to show when cartridges are being read Mainly used in graphs to show when cartridges are being written to Used for hyperlink labels Mainly used as the color of plots in graphs (repository view) Mainly used as the color of the used space in the capacity pie chart (repository view) Mainly used as the color of allocable space in the capacity pie chart (repository view) Mainly used as the color of fragmented space in the capacity pie chart (repository view) Mainly used as the color of nominal space in graphs (repository view) Mainly used as the color of physical space in graphs (repository view)
7. Close and reopen ProtecTIER Manager for the new settings to take place.
42
8. Resume working with ProtecTIER Manager.
Saving and printing data

ProtecTIER Manager data in many of the informational windows and panes can be saved or printed. 1. Select Options in the upper right-hand corner of the window. Note: The Options menu may not be available on all windows. 2. Select Save to save the information, or Print to print the information. Use 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.
Figure 6. ProtecTIER Manager
Select the Refresh navigation pane button to refresh the Navigation pane. Select the Refresh current view button to refresh the View pane.
Running operations in the background

This topic describes enabling operations to run in the background while performing another operation.
Chapter 5. Getting started with ProtecTIER Manager
ts760437
43
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.
44
Chapter 6. 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

The topics in this section describe how to add a node, a subnetwork node, and remove a node from the ProtecTIER system using the ProtecTIER Manager. Note: This section provides instructions for adding and removing nodes when using the TS7650G. Adding a node registers the node's IP address and port number with the instance of ProtecTIER Manager at your workstation. Similarly, removing a node removes the node's registration from ProtecTIER Manager at that workstation.
Adding nodes
Complete this task to add a node to your ProtecTIER system using ProtecTIER Manager. To add a node to your ProtecTIER system: 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 > 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 window 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 trained ProtecTIER specialist. 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 node's 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. For more information about repositories, see Chapter 7, Managing repositories, on page 47.
45
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 check box 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.
46
Chapter 7. Managing repositories

This chapter describes how to use the ProtecTIER Manager software 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 the ProtecTIER Manager software for the following repository management 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 v To defragment a repository v To reserve space on a repository
Enabling replication
Perform the following procedure to enable replication on systems that are being upgraded from v2.2 (and below) to v2.4. Note: It is possible that replication has already been enabled on your system. For example, if you performed the Increase Capacity operation using ProtecTIER v2.3 or above, replication was automatically enabled. By default, replication is enabled on new repositories created with ProtecTIER v2.4. Replication is disabled on repositories upgraded from v2.2 (and below) versions. When you enable replication, you must assign files systems, set the estimated factoring ratio, MD raid configuration, and disk size. The procedure allocates 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 TS7650Gs may require additional metadata, pending the actual metadata deployment on the specific repository. 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.
47
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.
Expanding repositories
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 a trained ProtecTIER specialist 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
Complete this task to plan for a repository expansion. In addition to guidance from a trained ProtecTIER specialist, 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. In the Estimated factoring ratio field, enter the updated factoring ratio estimate for the repository. In the MD Raid configuration field, select a configuration option from the drop-down list. In the Disk size field, select the physical disk size, in GB, from the drop-down list. 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.
3. 4. 5. 6.
48
Figure 7. Repository meta data storage requirements window
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 Close. 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. Note: If you need to expand an existing file system, refer to Expanding existing file systems on page 57. If not, go on to Using fsCreate to create file systems.
Using fsCreate to create file systems

Complete this task to create file systems for the repository. 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:
ts760324
49
./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
v If you are creating file systems for a two-node cluster configuration, go on to step 5. v If you are creating file systems for a stand-alone configuration, go on to step 6. 5. If you are working in a clustered configuration, shutdown the vtfd service on Server B during the file system creation to avoid any possibility of corrupting meta data on the repository's management file system and then poweroff the server. Type the following commands:
service vtfd shutdown poweroff
6. Create file systems on new available multipath devices, register them to /etc/fstab and mount them, by typing the following command on Server A:
./fsCreate -e
7. For verification, display the GFS file systems that are not part of the repository by typing the command:
./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
Go on to Expanding the repository on page 51.
fsCreate parameters
Use the following syntax and parameters to perform additional functions for expanding the physical capacity of a repository.
50
Syntax:
fsCreate Table 5. 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 devices during or detected physical 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
Expanding the repository

Expand the repository using the information generated during the repository expansion planning process. Note: Before running the Increase capacity wizard, if you are working on a clustered configuration, make sure that the vtfd service has been shutdown on Server B and that Server B has been powered off. Access the ProtecTIER Manager GUI interface 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.
51
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 dropdown list. 7. Select the Disk size, in GB, from the options in the dropdown 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.
Figure 8. 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. When the system comes back online, you can resume use of your ProtecTIER system. 14. If you are working in a clustered configuration, go on to Restarting the vtfd service in a clustered configuration.
Restarting the vtfd service in a clustered configuration

If you are working in a clustered configuration, continue working with the fsCreate tool to register the new file systems and initialize the vtfd service on Server B. 1. Once the file systems are created and the repository's capacity has been increased, power on Server B.
52
ts760326
Note: Server B was initially powered off in step 5 on page 50 of Using fsCreate to create file systems on page 49. 2. Open a Secured Shell (SSH) session to Server B and log in using the user ID: root and password: admin. 3. Type the following command:
cd /opt/dtc/app/sbin
4. Register the new file systems to /etc/fstab, create the mount points and mount them by typing the following commands:
./fsCreate -t
5. Verify that all the repository file systems are available, including the new ones, by typing the following command:
./fsCreate -r
6. Initialize the vtfd service on Server B. Type the command:

service vtfd init
Allow vtfd to fully start before proceeding. When the system comes back online, you can resume use of your ProtecTIER system.
Creating file systems and expanding existing ones

This section defines how to create a ProtecTIER file system when you want to increase the physical capacity of your repository. | | | | | | | Note: If you are working on a clustered system, the following procedures should be performed while all the services (vtfd, gfs, clvmd, and cman) on Server B are down. Before you begin, stop the vtfd and cluster services on Server B. Enter the commands:
service vtfd stop service ptcluster stop
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 wizard.
Creating file systems

Perform the following steps, in the order that they appear, for each file system that you want to create: v v v v v v v Creating partitions on page 54 Creating physical volumes on page 55 Creating volume groups on page 55 Creating logical volumes on page 56 Creating a Global File System (GFS) on page 56 Creating mount points on page 56 Adding file systems to fstab and mounting file systems on page 56
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
53
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 in to 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] \_ 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
FAStT
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. | | Note: Some mpaths may already exist on the repository. The Parted Partition Manipulation procedure should be run on new mpaths only. 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).
54
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 Partition Manipulation utility. 8. Enter the following command to present the new partition to the operating system:
kpartx -a /dev/mapper/mpathN
9. Repeat steps 3 on page 54 through 7 to create additional partitions until you have created one partition on each device.
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:
55
# 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.
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.
56
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 automatically runs 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 existing file systems

The topics in this section define how to expand the existing file systems used for ProtecTIER. Each task must be performed in the order in which it appears. Note: Before you begin expanding file systems, enter the command service vtfd stop on the node that you are working on. Perform the following steps, in the order they appear, for each file system that you want to expand: v Creating a partition v Unmounting a file system v Deactivating the logical volume v Creating a physical volume on page 58 v Adding the physical volume to a volume group on page 58 v Expanding the logical volume on page 58 v Reactivating the logical volume on page 58 v Mounting the file system on page 58 v Expanding the GFS file system on page 59
Creating a partition
Create a partition for each file system that you want to expand. For more information, see Creating partitions on page 54.
Unmounting a file system

Complete this task to unmount the file system or file systems as part of expanding your file system. Unmount the file system that you want to expand by performing the following step: Type umount /dev/<file system name> .
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:
57
| | |
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 55.
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. 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.
58
Expanding the GFS file system

Complete this task to allow for the expansion of the Global File System (GFS) file system. Type gfs_grow /dev/<volume group name>/<logical volume name> to allow for expansion of the GFS file system.
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 a trained ProtecTIER specialist. For more information, see Removing and adding cluster members on page 149. Attention: Deleting the repository results in the loss of all the data contained in the repository. 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. 6. When the system comes back online, you can resume use of your ProtecTIER system.
Defragmentation on a repository
Defragmentation is the process to allocate fragmented space on a repository as defragmented so that this space can be used to write new data. Important: Contact a trained ProtecTIER specialist before performing this operation. A ProtecTIER repository becomes fragmented over time. The Defragmentation control operation gathers the fragmented (i.e. free, but unusable) space together in order to improve the speed of reading and writing new data to the repository.
Reserve space for backup

This topic describes the Reserve space for backup feature which provides the ability to exclusively assign a portion of a hub repository's capacity for local backups.
59
In large deployments with many backup target repositories (that is, "spokes") replicating to the replication and backup target (that is, the "hub"), the replication process may fill, or nearly fill, all the space in the hub repository, leaving insufficient space for backup data. Since the assumption is that backup has precedence over replication, this feature ensures that the designated capacity is reserved only for local backup during replication, so that replication cannot be written to the reserved portion of the storage capacity. Error notifications will appear in the event that the capacity reserved on the repository hub is running out of space for the local backup, or for replication. v If there is no replication, backup data can stream into the repository and fill the entire storage capacity. v If there is replication going on, backup data can stream into the repository and fill the entire reserved space for backup, while replication data streams into the repository and fills the remainder of the storage capacity. Keep in mind that replication and backup data compete for this space. To reserve space for backup on a hub repository: 1. From the System's Management view, choose hub repository from the navigation pane. 2. Select Reserve space for backup from the Repository menu. The Reserve space for backup window displays the minimum amount of nominal space that is currently reserved for backup.
Figure 9. Reserve space for backup window
3. Enter the new minimum nominal space size and click Ok. The operation is complete and space for backup is reserved on the repository. Go on to the next section.
60
ts760423
Chapter 8. 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).
Creating libraries
Complete this task to create a library for your ProtecTIER system. Ensure that the following items are performed before proceeding with this task: v Check with your administrator about the number of drives and cartridges supported by your application. v Use the Scan button of the Port attributes pane to verify that the ports of the ProtecTIER server (to which the virtual devices of the library are to be assigned) are connected to the correct host. 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.
TS7610 Appliance Maximum number of 4 libraries Maximum number of 256 virtual drives TS7650G 16 256 (dual-node 512) TS7650 Appliance 12 256 (dual-node 512)
61
Note: Use the Scan button of the Port attributes pane to verify if the ports of the ProtecTIER 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 94. 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 by selecting the Flat addressing mode function from the Host Initiators Management screen. For more information, see Managing host initiators on page 79 and Manually adding host initiators on page 79. 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.
Figure 10. Library type screen
6. Select IBM TS3500 0100 as 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
62
ts760404
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.
Figure 11. 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.
ts760405
63
Figure 12. 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.
64
ts760406
Figure 13. Port assignment screen
12. Select or deselect the check boxes next to each port to define which of the node's 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, ProtecTIER 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.
ts760407
65
Figure 14. Assignment (2) screen
16. Repeat steps 12 on page 65 and 13 on page 65 for the Assignment (2) screen. 17. Click Next. The Cartridges screen is displayed.
Figure 15. 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
66
ts760409
ts760408
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.
Figure 16. 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.
ts760410
67
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 that the backup application that you are using supports the type of library model that you select for a virtual tape system. When you set the library type, you can 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 If you chose the TS3500 (or P3000) during the creation of the library and your backup application does not support that library model type as a virtual tape system, the Set library type dialog window 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 window is displayed and you can specify the library type accordingly:
Figure 17. Set library type dialog
Editing library parameters

Complete this task to change the parameters of an existing library. 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.
68
ts760317
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 72. 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.
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.
ts760379
69
Figure 19. Assignment screen
6. Select or deselect the check boxes next to each port to define which of the node's 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, ProtecTIER 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.
70
ts760380
11. Repeat steps 6 on page 70 through 9 on page 70 for the Assignment (2) screen. 12. Click Next. The Slots screen is displayed.
Figure 21. Slots screen
13. In the Number of slots field, enter the number of slots that you want in the library.
ts760382
ts760381
71
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
Complete this task to reassign the virtual robot and cartridge drives within the ProtecTIER system. 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.
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.
72
ts760393
Figure 23. Assignment screen
5. Select or deselect the check boxes next to each port to define which of the node's 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, ProtecTIER 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.
ts760394
73
10. Repeat steps 5 on page 73 through 8 on page 73 for the Assignment (2) screen. 11. Click Next. The Summary report is displayed.
Figure 25. Summary report screen
12. Click Finish. The Re-assign devices wizard closes and the ProtecTIER system temporarily goes offline to reassign the devices.
74
ts760396
ts760395
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.
Adding cartridges
Complete this task to add cartridges to your ProtecTIER system. 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.
75
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. 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. When the system returns online, the cartridges are added to the library. 6. Continue working with the ProtecTIER system.
Deleting cartridges
Deleting a cartridge results in the loss of all data contained in the cartridge. Perform the following steps to delete a cartridge:
76
ts760375
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 you want to delete. The VT window is displayed. 2. Click the Cartridges tab. The Cartridges window is displayed.
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 from the list.
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.
77
ts760332
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 library's name is changed.
Deleting libraries
Attention: Deleting a library results in the loss of all data contained in that library. Only a person with administrator authority can perform this task. Perform the following steps to delete a ProtecTIER 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.
About LUN Masking

LUN Masking is used to monitor device visibility by allowing specific devices (e.g. tape drives or robots) to be seen only by a selected group of host initiators. LUN Masking allows you to assign specific devices to a specific host running backup application modules. It enables multiple initiators to share the same target FC port without having conflicts on the devices being emulated. The LUN Masking setup can be monitored and modified at all times during system operation. LUN Masking in ProtecTIER influences the visibility of the devices by the hosts systems. Keep in mind that every modification in the LUN Masking in ProtecTIER may affect the host configuration and may require re-scanning by the hosts.
Enabling or disabling LUN Masking

The LUN Masking settings are disabled, by default, but can be either enabled or disabled. Configuration operations can be done in either mode, but the relevant changes will only be applied when LUN Masking is enabled. If LUN Masking is enabled, devices are seen only by the hosts that are defined with them in the same LUN Masking group. If LUN Masking is disabled, all devices are seen by all hosts. Follow the steps below to enable or disable LUN Masking: 1. Select VT > LUN Masking > Set LUN Masking enablement.
78
2. Select Enable LUN masking to turn LUN Masking on, or Disable LUN masking to turn LUN Masking off. 3. Click Ok. Once you have enabled or disabled the LUN Masking option, rescan the devices from the host systems. This is strongly recommended so that the host will have the most up-to-date information on the list of visible devices and their associated LUN numbers. Go on to Managing host initiators.
Managing host initiators

The Host Initiators Management option is used to add, modify, or delete host initiators from the list of host initiators known to ProtecTIER. Note: A host initiator must first be defined before it can be a part of a LUN Masking group and up to 1024 host initiators can be defined on a system. See Working with LUN Masking groups on page 82. To add, modify or delete host initiators, select VT > Host Initiators Management to access the Host Initiators Management functions. The Host Initiators Management screen displays the following details of the host initiator: v WWN v Alias a name that is defined other than the WWN v Group associated the LUN Masking group to which the host initiator belongs v Flat addressing mode - a technique used by HP-UX to work around certain SCSI addressing limitations when accessing a large amount of devices over a fibre channel v Link up displays whether or not there is an active link between ProtecTIER and the host initiator From this screen, go on to adding or scanning host initiators, modifying host initiator configurations, or deleting host initiators.
Adding Host Initiators

This section describes how to add host initiators using the Host Initiators Management window. Host initiators can be added to the host initiators list either manually, or by scanning the system for new host initiators. Follow either of the procedures listed below for adding host initiators: v Manually adding host initiators v Scanning host initiators on page 80 Manually adding host initiators: Host initiators can be added manually by entering the host's WWN, alias and addressing mode. A host initiator can be added either by accessing the Host Initiator Management window from the VT menu, or from the LUN Masking group configuration window. Manually adding host initiators is primarily done when hosts are not yet connected to ProtecTIER.
79
Note: A host initiator must first be defined before it can be a part of a LUN Masking group. To add a new host initiator: 1. Select VT > Host initiators management. The Host initiators management window is displayed.
Figure 28. Host Initiator management window
2. 3. 4. 5.
Click Add. The Add host initiator screen is displayed. Select a WWN from the WWN dropdown box or type in a new WWN. Enter an alternative name to the WWN in the Alias field. Select the Flat addressing mode checkbox if the flat addressing technique is to be used. 6. Click Ok. The new host initiator is listed on the Host initiators management screen. Go on to add more new host initiators or to modify or delete existing host initiators. Once you have defined a host initiator, you can create LUN Masking groups. See Working with LUN Masking groups on page 82. Scanning host initiators: Host initiators can be added to the configured host initiators list after scanning the system. Scanning for new host initiators is recommended when the host initiators are already physically connected, but you have not yet added them to the Host Initiators list. Follow the steps below to scan for new host initiators:
80
ts760421
1. Select VT > Host initiators management. The Host initiators management screen is displayed. 2. Click Re-scan for new initiators to scan for new host initiators. If new host initiators are found that are not already configured in the Host Initiators list, a dialog with the available host initiators appears. 3. Select the Host Initiators you want to add. 4. Click Yes to add the new host initiators to the list, or click Cancel to exit without adding. Go on to Working with LUN Masking groups on page 82.
Modifying Host Initiators

You can change the alias and/or the addressing mode of a host initiator. Follow the steps below to change the alias and/or the addressing mode of a host initiator: 1. Select Host initiators management from the VT menu. The Host initiators management screen is displayed. 2. Select a host initiator from the list and click Modify. The Modify host initiator dialog is displayed. 3. Change the host initiator alias by typing a new name in the Alias field. 4. Change the addressing mode by selecting or deselecting the Flat addressing mode checkbox. 5. Click Ok to save and close the Modify host initiator dialog, or select a different host initiator to modify from the dropdown list in the WWN field. Continue working with the options available from the Host Initiators Management screen to add, remove, modify or re-scan for new initiators. If you have finished working with the Host Initiators Management screen, click Save Changes to save your changes and exit, or click Cancel to exit without saving your changes.
Removing Host Initiators

Configured host initiators can not be deleted if they act as members of a LUN Masking group. See Removing a LUN Masking group for more information. Follow the steps below to remove a host initiator that is not a member of a LUN Masking group: 1. Select Host initiators management from the VT menu. The Host initiators management screen is displayed. 2. Select a host initiator from the list and click Remove. The Remove host initiator dialog is displayed. 3. Click Yes to remove. Continue working with the options available from the Host Initiators Management screen to add, remove, modify or re-scan for new initiators. If you have finished working with the Host Initiators Management screen, click Save Changes to save your changes and exit, or click Cancel to exit without saving your changes.
81
Working with LUN Masking groups

LUN Masking groups define the connection between the host initiators and the VT library devices (e.g. robots or tape drives). Devices which belong to a certain group can be seen by the host initiators of the group. A device can belong to multiple LUN Masking groups, but a host initiator can only belong to one LUN Masking group. Select the Configure LUN Masking groups option from the VT > LUN Masking menu to begin configuring LUN Masking groups. You can add LUN Masking groups, or if a group already exists, you can configure it by adding Host Initiators, adding or modifying libraries, and adding or modifying the devices within the libraries. Note: Keep in mind that changes you make in the LUN Masking configuration requires scanning by the host and by the back up application.
Creating LUN Masking groups

Begin working with LUN Masking groups by adding a group via the LUN Masking window. A maximum of 512 groups can be configured per system and a maximum of 512 drives can be configured per group. (A maximum of 1024 host initiators can be defined on a system.) Each group needs to contain at least one host initiator and one device (i.e. drive or robot). Robots can be added as required. To add a LUN Masking group: 1. On the left side of the LUN Masking window, click Add at the bottom of the LUN Masking Groups pane. The group details appear to the right of the window.
82
Figure 29. LUN Masking window
2. Type a new name for the group in the Group name field. 3. Add host initiators by clicking Add in the Selected Host Initiators pane. The Add Host Initiators dialog is displayed. 4. Select the Host Initiators to add to the LUN Masking group from the list displayed and click Ok. 5. Continue adding more host initiators, or go on to add the library devices. From the Library Mappings pane, you can add the library devices you want to be visible to the host initiators in the group. 1. To define the devices, click Add at the bottom of the Library Mappings pane in the LUN Masking group details view. A list of libraries in the system is displayed. 2. Select the relevant libraries from the list and click Ok Continue selecting the library devices to be viewed by the host initiators in the group.
Modifying a LUN Masking group

From the Selected Devices pane you can modify the libraries and devices defined in the LUN Masking group. Once you have finished, click Save changes to save your modifications and exit the LUN Masking configuration. After modifying a LUN Masking group, undesired holes may occur within the LUN numbering sequence. For example, removing a device from an existing group will cause holes in the LUN numbering if this device doesn't have the highest LUN number and, therefore, the backup application may have trouble scanning the
ts760422
83
devices. If your backup application does have trouble scanning the devices, it is recommended that you re-enumerate the LUN. Reassign the LUNs by clicking Reassign All LUNs at the bottom of the Selected Devices pane. The Reassign LUNs dialog is displayed stating that you are about to renumber all the LUN values of the available devices in the group and the connected hosts will be rescanned. Click Yes to renumber. The LUN values will be renumbered and all the devices in the Selected Devices pane will be assigned new LUN numbers, sequentially, starting with 0 (zero). Continue to the next section.
Removing a LUN Masking group

If a LUN Masking group is removed while LUN Masking is enabled, the host initiators of the respective group will be unable to "see" any devices on this system. The host initiators must be reassigned to a different group to be reconnected. To remove a LUN Masking group, click Remove at the bottom of the LUN Masking groups pane. The LUN Masking group is removed from the list. Continue configuring the LUN Masking groups as desired. Click Save changes to save your modifications and exit the LUN Masking configuration.
Library-related Operations
Some library configuration operations may affect the LUN masking groups. Most of these changes will be blocked by the system. The only exception to this is the Delete library operation and reducing the number of drives through the Change library dimensions operations where the removal of the devices may directly affect the relevant LUN Masking group.
Deleting a library
If devices from a deleted library are members of LUN Masking groups, a warning is issued to the log file and to the user (via the GUI). If the user chooses to proceed with the operation, the relevant devices are removed from the relevant LUN Masking groups, and the configuration file data is updated accordingly. Removing a library can cause "holes" in the LUN Masking numbering and, therefore, the backup application may have trouble scanning the devices. In this case, you must reassign the LUN.
Modifying the dimensions or reassigning devices of a library

When you modify the dimensions of a library or reassign the library devices, if a device already belongs to a LUN Masking group, the following rules apply: v The device cannot be deleted or reassigned to another FE port. To reassign the device to a different port, you must remove the device from all of its related groupings. v The number of drives in the library cannot be reduced. Continue to the next chapter.
84
Chapter 9. Monitoring ProtecTIER

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

The topics in this section explain how to monitor ProtecTIER systems. In the Systems Management view, select a system from the Systems tab. The Systems monitoring screen is displayed:
Figure 30. Systems monitoring screen
The Systems screen consists of the following main tabs: v General on page 86 v VT on page 87 v Replication Policies tab on page 88 v Replication activites tab on page 89 In addition, the ProtecTIER Manager status bar displays icons for the total read and write replication and backup throughput rates for the selected system and the system time. 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 system. (For more information, see Viewing the alerts and events log windows on page 145.)
85
ts760349
General
This topic explains monitoring general information about a ProtecTIER system. The General tab consists of the following panes: v v v v Capacity Cluster members on page 87 Replication information on page 87 Fibre channel ports throughput on page 95
Capacity
This topic defines how to monitor the disk space capacity on a ProtecTIER system. The Capacity pane displays the amount of disk space that is used, allocable, or fragmented, in the selected system's repository. The information is displayed 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 ProtecTIER's defragmentation operation Click View resources to open the Storage resources window.
Figure 31. Storage resources window
The Storage resources window displays the list of metadata and user data file systems for the selected system's repository.
86
ts760329
Note: You can open the Storage resources dialog at any time by clicking the View resources button on the Toolbar.
Cluster members
This topic defines how to monitor the cluster members on a ProtecTIER system. The Cluster members pane displays the following information about each node in the cluster:
Table 6. 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 Management service is online or offline. Indicates whether the VT service for that node is online or offline.
Status Management service VT
Replication information
This topic defines how to monitor the replication information on a ProtecTIER system. The Replication information pane displays the replication properties of the ProtecTIERsystem: v Spoke repositories that are configured on the system v ProtecTIER Replication Manager information: Repository replication IP address Replication Manager management IP address is the IP address used by the ProtecTIER Manager GUI to connect to the Replication manager. Grid name Grid ID
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.
VT
This topic defines how to monitor VT (Virtual Tape) libraries using ProtecTIER. Open the IBM ProtecTIER Manager, click System and select the cluster that you want to view. At the bottom of the Systems Management window, click the VT tab. The VT tab displays information about the VT service libraries associated with the
87
cluster.
Figure 32. VT tab view
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 97. v Libraries performance - Displays the total performance of the libraries in the cluster. For more information, see ProtecTIER VT overview on page 97. 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 97.
Monitoring replication policies and activites

You can monitor replication policies and activities of a repository via the Systems Management view. Click on a system 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 policy's details.
88
ts760352
Figure 33. Replication Policies tab
When you select a policy, you can see the policy's 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 Policy's 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.
89
ts760351
Figure 34. 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 policy's 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
Monitoring the repository

In the Repositories pane, select the repository. The Repository monitoring screen is displayed.
90
ts760350
Figure 35. Repository monitoring screen
The Repository monitoring screen consists of the following panes: v Capacity v v v v Total utilization Repository configuration on page 92 Storage on page 92 HyperFactor on page 93
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 86.
Total utilization
The Total utilization pane displays the following information in both graphical and numerical format:
Table 7. 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.
ts760346
91
Repository configuration
The Repository configuration pane features the following information:
Table 8. 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 on page 93 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 36. Nominal data size graph
The Nominal data size graph displays the amounts of data contained in the repository over time.
92
ts760390
Utilization graph
Figure 37. Utilization graph
The Utilization graph displays the amounts of actual repository space used over time.
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 38. 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
ts760388
ts760413
93
Figure 39. HyperFactor ratio over time graph
The HyperFactor ratio over time graph displays the cumulative HyperFactor ratio as it changes over time.
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 Port attributes v Version information on page 95 v Fibre channel ports throughput on page 95 v Network configuration on page 95
Port attributes
The Port attributes pane displays the following information for each port in the node:
Table 9. 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.
94
ts760386
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 87.
Network configuration
The Network configuration pane displays information about the setup of the network interface cards (NIC) for the node.
Table 10. 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 tab on page 96 v Drives tab on page 97 v Cartridges tab on page 99
95
v Slots tab on page 102 v Imports/Exports tab on page 103
General tab
The VT service monitoring screen displays the General tab by default. The General tab displays information about the selected library.
Figure 40. General tab
The General tab consists of the following panes: v Library front-end v ProtecTIER VT overview on page 97 v Configuration on page 97 v Library type on page 97
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 11. Virtual robots and tape drive Column Node Port Definition The node on which the virtual device is assigned. The port within the node on which the virtual device is assigned.
96
ts760314
Table 11. Virtual robots and tape drive (continued) Column Top. Definition 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 Device Throughput The Worldwide Name of the port. The logical unit number of the robot or tape drive relative to the port. 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 72.)
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 Status of each tape drive v Rate of data transfer in Mbps v Number of I/O operations per second v 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 68.)
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 tab
The Drives tab displays detailed information about the virtual tape drives in the selected library.
97
Figure 41. Drives tab
The Drives tab displays the following information:

Table 12. 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, Vendor Name Product Revision Node Port LUN Serial Address Barcode is displayed.
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 drive's logical unit number relative to the port The drive's serial number The drive's address within the library If the drive is loaded with a cartridge, this column displays the cartridge's barcode
98
ts760313
Cartridges tab
This topic defines the cartridges information provided by ProtecTIER Manager when it is used for monitoring Virtual Tape (VT) services. Go to the Systems Management view of ProtecTIER Manager to see detailed information about the virtual tape cartridges in a selected library: 1. Select the Systems tab in the navigation pane and choose a library from the Services category. 2. Click the Cartridges tab to view detailed information about the virtual tape cartridges in the chosen VT library. You can filter the configuration properties view of the cartridges displayed by selecting one of the following options from the Configuration dropdown field: v Backup properties v Origin properties on page 100 v Replica properties on page 101
Backup properties
This topic illustrates the backup properties of a cartridge. The Backup properties filter displays the general properties of the cartridge's configuration (not related to replication).
Figure 42. Cartridges tab - backup properties
The following general information is provided for the cartridges of the library you have chosen:
Table 13. Cartridges backup properties Column Barcode Definition The cartridge's barcode.
99
ts760332
Table 13. Cartridges backup properties (continued) Column R/W Definition Whether the cartridge is write enabled. If the cartridge is write enabled, a green checkmark is displayed. The cartridge's 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. The maximum amount of nominal data, in megabytes, the cartridge can contain. Indicates whether the cartridge has reached Early Warning. If so, the cartridge is regarded as full and a green checkmark is displayed. The repository on which the cartridge was created and backed up. (See Taking over cartridge ownership on page 124 for more information on "principality".)
Capacity (MB)
Data Size (MB) Max Size (MB) Full
Principal
Go on to the next section.
Origin properties
This topic illustrates the origin properties of a cartridge. The Origin properties of a cartridge are typically useful when viewed from a spoke repository. The origin properties are used to understand the status of replicating the cartridges to the hub. Using this view, you can understand if cartridges are still pending replication (e.g. backlog > 0) and to what repository the cartridge was replicated. Note: The Origin properties view from the hub repository is useful for situations when the hub has failed back cartridges. See The failback policy on page 127.
100
Figure 43. Cartridges tab - origin properties
The following information about the cartridges' origin is provided for the cartridges of the library you have chosen:
Table 14. Cartridges origin properties Column Barcode Data Size (MB) Hub Replicated data size Backlog Last sync time Definition The cartridge's barcode. The amount of nominal data, in megabytes, currently stored on the cartridge. The name of the hub repository to which the cartridges will be replicated. The amount of nominal data that has already been replicated. The data on the cartridge that still needs to be replicated. The most updated date and time when the backup data on the cartridge was last synchronized with the hub. The percentage of the cartridge that has been replicated.
% Replicated
Replica properties
This topic illustrates the replica properties of a cartridge. The Replica properties are used to analyze cartridges that were replicated into this repository. The replica properties are typically useful from the hub repository. The most useful property of this view is the In-Sync column that displays whether or
101
ts760333
not the cartridge is synchronized with the most up-to-date data from the spoke.
Figure 44. Cartridges tab - replica properties
The following information about cartridge replication is displayed for the cartridges of the library you have chosen:
Table 15. Cartridges origin properties Column Barcode Data Size (MB) Spoke Last sync local time Definition The cartridge's barcode. The amount of nominal data, in megabytes, currently stored on the cartridge. The name of the spoke repository from which the cartridges are being replicated. The most updated date and time on the hub when the backup data on the cartridge was last synchronized with the hub. The most updated date and time on the spoke when the backup data on the cartridge was last synchronized with the hub. Shows whether or not the cartridge has been replicated and is synchronized with the spoke.
Last sync remote time
In-Sync
Slots tab
The Slots tab displays detailed information about the slots in the selected library.
102
ts760335
Figure 45. Slots tab
The Slots tab displays the following information:

Table 16. Slots tab information Column Slot No. Address Barcode Capacity Definition Indicates the slot's number in the library. Indicates the slot's address number. If the slot contains a cartridge, this column displays the cartridge's 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 tab
TheImports/Exports tab displays detailed information about the import/export slots in the selected library.
103
ts760316
Figure 46. Imports/Exports tab
The Imports/Exports tab displays the following information:

Table 17. Imports/Exports tab information Column Imp/Exp No. Address Barcode Definition The number of the import/export slot. The import/export slot's address number. If the import/export slot contains a cartridge, this column displays the cartridge's barcode. If the import/export slot contains a cartridge, this column displays the estimated cartridge's 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

This topic details 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 library's 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. ProtecTIER Manager displays a view of the shelf and allows access to the cartridges in the shelf.
104
ts760315
From the shelf, cartridges can be moved to a library's import slot, replicated to another repository, or be deleted. Cartridges can also be automatically moved to a library's import slot through the visibility switching process. A cartridge that is moved to an export slot is automatically displaced to the shelf.
Figure 47. 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 system's backup sessions using the analyze_sessions utility. Complete this task to initiate a backup of the ProtecTIER information from within the Linux Shell. Invoke a backup from the /opt/dtc/app/utils/ directory. 1. Change to the /opt/dtc/app/utils/ directory.
105
ts760355
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 18. 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
106
Chapter 10. Native Replication Management

This chapter provides the information needed to manage Native Replication configuration and monitoring. Native Replication lets you replicate data objects between ProtecTIER repositories. In order for a logical set of repositories to replicate from one to another, you must create a replication grid. The replication grid is remotely created and managed by the Replication Manager. The ProtecTIER Replication Manager is a server that remotely manages the replication grids within an organization. The ProtecTIER Manager connects to the ProtecTIER Replication Manager using the IP address of the ProtecTIER Replication Manager server. The ProtecTIER Replication Manager can be installed on a dedicated host (which requires an RPQ), or on a ProtecTIER node If the ProtecTIER Replication Manager is installed on a ProtecTIER node, it can manage up to one grid with 24 repositories. If ProtecTIER Replication Manager is installed on a dedicated server, it can manage up to 64 grids with 256 repositories in each grid. Each ProtecTIER Replication Manager has a unique identity. A repository, once it has joined a replication manager cannot join a replication grid managed by a different replication manager, even if it has left the grid. This is to prevent data collision. In this release, multiple source repositories (i.e., "spokes") can replicate to a single target (i.e., "hub"), which may in turn act as a Disaster Recovery site for any number of the spokes while still allowing local backups, as well as replication, from the active spokes.
Working with ProtecTIER Replication Manager

This section describes how to manage Native Replication by working with a ProtecTIER Replication Manager. The ProtecTIER Replication Manager's tasks include: v Managing the repositories in the replication grid that can be replicated to v Maintaining the IP addresses of all repositories v Updating of repositories leaving and joining the grid v High-level monitoring and statistics of traffic in the replication grids To begin adding and working with a ProtecTIER Replication Manager, click the Grids Management button at the bottom of the navigation pane of ProtecTIER Manager.
Connecting to a ProtecTIER Replication Manager

Connect to a new ProtecTIER Replication Manager from the ProtecTIER Replication Manager by following the steps below: 1. Select Replication Manager > Add Replication Manager. The Add ProtecTIER Replication Manager dialog is displayed. 2. Enter the IP address of the ProtecTIER Replication Manager you want to add and click Ok. The ProtecTIER Replication Manager Login is displayed.
107
Logging in to a ProtecTIER Replication Manager

To 1. 2. 3. log in to a ProtecTIER Replication Manager: Select Replication Manager > Login. The login screen is displayed. Enter the Username: gmadmin and Password: gmadmin. Click Ok. The Replication Manager view is displayed.
Removing a ProtecTIER Replication Manager

Before you remove a ProtecTIER Replication Manager, you must first log out of the Replication Manager you want to remove. 1. Select the Replication Manager for removal from the Grids Management navigation pane. 2. Select Replication Manager > Logout. You are now logged out. 3. Select Replication Manager > Remove Replication Manager. The Remove Replication Manager dialog is displayed asking if you want to remove the connection to the Replication Manager you selected. 4. Click Yes. The Replication Manager is removed from the list in the Grids Management navigation pane. Go on to Managing the replication grid.
Managing the replication grid

Management and configuration of a replication grid is done via the ProtecTIER Replication Manager through the Grids Management view of ProtecTIER Manager. A replication grid is comprised of a set of repositories that share a common ID and can potentially transmit and receive logical objects through replication. A single replication grid may include up to 8 hubs and, therefore, up to 8 "topology groups". A "topology group" is a group of one hub with up to 12 spokes connected to it. Keep in mind that if ProtecTIER Replication Manager is installed on a ProtecTIER node, it can manage up to one grid with a total of 24 repositories. Note: Spokes do not need physical connections between them. However, all repositories do need a network connection to the ProtecTIER Replication Manager server.
Creating a replication grid

Follow the steps below to create a replication grid: 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. 2. Complete the fields to define a grid. Type a unique Grid ID or select a unique Grid ID number (0 to 63) from the dropdown list and enter a name in the Name field. Note: ProtecTIER will not allow you to choose an ID that has already been used.
108
3. Click Ok. The new grid is added to the Grids list in the navigation pane of the Grids Management view.
Deleting a replication grid

Deleting a grid is only allowed if the grid is empty. In addition, once you have deleted a grid, the Grid ID cannot be reused. Being that there are only 64 grid numbers (i.e. 0 to 63), deleting a grid means that you 'lose' one grid ID.
Taking over a repository

If the repository at the production site (spoke) has been destroyed and cannot be repaired, you can replace it with a new repository. See Replacing the destroyed repository on page 127.
Displaying removed repositories

To display a list of removed and/or unrecoverable repositories and their replacements, click Grid > Show removed repositories. A table is displayed showing the list of repositories and their replacements according to their ID numbers and names. Go on to Working with repositories in a replication grid.
Working with repositories in a replication grid

This section explains how to manage and work with repositories in a replication grid. Note: Repositories can only replicate to each other if they are part of the same grid. In addition, a repository cannot be a member of more than one grid. The following tasks can be accessed from the Repository menu of the Grids Management view of ProtecTIER Manager (except for Forcing a repository to leave a grid on page 111 which is done from the Systems Management view): v Adding a repository to a grid v v v v v Removing a repository from a grid on page 110 Updating the IP address of a repository on page 111 Defining the role of a repository on page 111 Connecting a spoke to the hub on page 112 Disconnecting a spoke from the hub on page 114
Adding a repository to a grid

This task explains how to add a repository to a grid. When you add a repository to a replication grid, the repository can be defined as a hub or a spoke. To add a repository to a replication grid: 1. Select Repository > Add repository to grid. The Add repository to grid window is displayed.
109
Figure 48. Adding a repository to a grid
Note: A repository cannot be a grid member of more than one grid. 2. Type the network replication IP address of the repository in the Replication IP address field. 3. Enter the username and password of the repository (e.g. User name: ptadmin and Password: ptadmin). Click Ok. 4. If you would like this repository to be designated as the hub, select the Define as hub checkbox. Designating a repository as a hub can be done at a later time. See Defining the role of a repository on page 111.
Removing a repository from a grid

This task explains how to remove a repository from a grid. A repository can be removed from a grid via the ProtecTIER Replication Manager. Note: Before removing a repository from a grid, carefully consider the potential effects on the system configuation. Once the repository is removed from the grid, all the bandwidth reduction and replication deduplication information is deleted. Therefore, if the repository rejoins the grid at some time, it must send or receive each data segment at least once before bandwidth reduction and replication deduplication will work for that data segment. A repository can only be removed from a grid if it is a stand-alone repository. See Disconnecting a spoke from the hub on page 114. To remove a repository from a grid: 1. From the Grids Management view, click on the repository you want to remove. 2. Select Repository > Remove repository from grid. The Remove repository from grid window is displayed.
110
ts760339
3. Complete the login information by typing the User name and Password of the repository. 4. Click Ok. The repository is removed from the grid. Note: Removing a repository from a grid, without coordination with the Replication Manager, should be done only if the ProtecTIER Replication Manager thinks that the repository is not a part of the grid already, or the Replication Manager was destroyed and is not meant to be restored. To remove a repository from a grid without coordination, see Forcing a repository to leave a grid.
Forcing a repository to leave a grid

This task explains how to force a repository to leave a grid. A repository can be removed from a grid without the repository's 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. A temporary network disconnection between the replication manager and the repository is not enough of a reason for forcing a repository from a grid. If the repository thinks it is part of the grid, but ProtecTIER Replication Manager does not recognize the repository as part of the grid, via the Systems Management view, the repository can be persuaded to believe that it is not a part of the grid. Note: This situation can happen in a case where the Replication Manager was permanently destroyed, or if the repository was removed from the grid without coordination due to temporary network disconnection. To force a repository from a grid, from the Systems Management view, select Replication > Disaster Recovery > Uncoordinated repository removal from grid.
Updating the IP address of a repository

If the replication IP address of the repository is changed , the ProtecTIER Replication Manager needs to be updated as well with the correct IP address To update the IP address of a repository, select Repository > Update repository address. The Update repository address screen is displayed. Enter the updated IP address and click Ok.
Defining the role of a repository

This task explains how to define the role of a repository in a replication grid. When you add a repository to a replication grid, you can define the acting role of that repository. A repository can be defined as a hub or a spoke. To define the role of a repository: 1. Select Repository > Define repository role. The Define repository role window is displayed.
111
Figure 49. Defining the repository role
2. Select the Define as Hub checkbox if you want to define the repository as a hub, or leave the selection blank to leave the repository as a spoke. 3. Click Ok. The repository will change color in the grid view according to its role definition (e.g. hub or non-hub) as indicated by the color-coded legend at the bottom of the view pane. Go on to Connecting a spoke to the hub.
Connecting a spoke to the hub

This task explains how to connect a spoke to the hub in a replication grid. Before defining any replication policy, you must create a physical connection between the spoke(s) and the hub. Note: When defining a connection, you also define the direction of the replication from the source repository (spoke) to the destination repository (hub). Typically, the spoke is the primary site and the hub is the disaster recovery site. The maximum number of spokes that can be connected to a hub at any given time is 12. To connect a spoke to the hub: 1. Click on the hub to which you want to add spokes. 2. Select Repository > Connect Spoke to Hub. The Connect Spoke to Hub window is displayed. If spokes have been previously connected to the hub, a message will appear stating how many spokes are already connected to the hub.
112
ts760343
Figure 50. Connecting spokes to a hub
3. Choose the repositories from the Spoke repositories list that you want to connect as spokes to the selected hub. 4. Click Ok. The connections are displayed in the grid view map.
Figure 51. Replication grid map view
113
ts760340
ts760336
Disconnecting a spoke from the hub

This task explains how to disconnect a spoke repository to the hub repository in a replication grid. Disconnecting the connection between a spoke and hub is done from the spoke repository. If you try to run this operation from the hub repository, an error message will display. To delete a spoke from the hub: 1. Click on the spoke you want to disconnect from the hub. 2. Select Repository > Disconnect Spoke from Hub. The Disconnect Spoke to Hub window is displayed. 3. Confirm the action by clicking Ok. The spoke appears as a stand-alone 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 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 and managed via the Systems Management view of ProtecTIER Manager. A policy can only be created on a repository that is a spoke in a grid and the policy only applies to the repository on which it's defined. Click on a system in the navigation pane to view the policies defined. Select a policy from the list to view the policy details and replication statistics.
114
Figure 52. View of replication policy
The following sections describe how to create and work with replication policies: v Setting the replication timeframe v v v v v Setting the replication rate limit on page 116 Limiting the network interface bandwidth on page 117 Creating a replication policy on page 118 Enabling and disabling a policy on page 119 Running a policy on page 119
v Modifying a policy on page 120 v Deleting a policy on page 120
Setting the replication timeframe

Scheduling a timeframe for replication to take place for all policies allows you to maximize your system's resources and prioritize between backups and replication. Defining a replication timeframe gives replication the highest priority with the maximum system resources used to complete the replication during the replication window. You can define a replication timeframe using the Set Replication Timeframe dialog. Outside of the set timeframe replication is off and does not run. If you choose backup as the priority, or no replication timeframe is defined, replication runs continuously all day, but on low priority, thereby consuming minimal resources from the system. You can also limit the replication throughput through the Replication Rate Limits window (see Setting the replication rate limit on page 116).
115
ts760351
Note: If you define a timeframe both in the hub and in the spoke, you need to adjust both to the same time. To set the replication timeframe: 1. Select Replication > Set replication timeframe. The Set replication timeframe dialog box is displayed.
Figure 53. Set replication time frame
2. Select an option: v Prioritized backup Replication is active, but is of low priority. v No backup priority Replication is off and only activated during defined timeframe. 3. Select the replication window in daily half-hour intervals. 4. Click OK. The replication timeframe is set. Go on to the next section.
Setting the replication rate limit

Setting the replication rate control allows you to limit the nominal and physical throughput (data flow rate) of replication. The values set for the physical and nominal limits have no explicit influence on one another. That is, the values set in the physical throughput may, but do not necessarily impact those values set in the nominal throughput, and vice versa. The physical throughput limit restrains the amount of I/O and resources replication consumes on the local repository. Implicitly, this reduces the total load on the replication networks used by the repository (you can have 2 networks) and the amount of resources needed on the peer repository, as well. The nominal throughput directly affects the load on the destination repository. On the source repositories, the replication nominal rate does not necessarily compete with the backup. Setting the limit on a source repository guarantees that the backup will get the total possible throughput minus the nominal limit, but in many cases this is not needed.
116
ts760348
The Replication Rate Limits dialog is divided into separate areas for physical and nominal throughput. These areas are divided further into various scenarios where you can limit the rate of replication; for example, replication rates for physical throughput during backup or restore, replication rates when there is no backup or restore, with no replication timeframe defined and with a replication timeframe defined. The same options appear for nominal throughput.
Figure 54. Set Replication rate limits
To define the replication rate limits for these various scenarios of backup or restore, complete the following steps: 1. Select the checkbox next to the desired option and enter a value (in MB/Sec). If a checkbox is not selected, the value will revert to an unlimited replication rate. 2. To return to the original replication rate limits that were defined during installation for the physical and/or nominal throughputs, click Restore defaults at the bottom of either or both areas. The values will default to their original settings at setup. Go on to the next section.
Limiting the network interface bandwidth

Complete the task in this topic to limit the bandwidth or throughput of a network interface, such as a port, on a node that is running replication. Note: This task should be performed only if it is important to limit each one of the interfaces separately. If you want to limit the total throughput over the networks, refer to Setting the replication rate limit on page 116 and set the physical replication rate limit of the repository. Select a node from the navigation pane to view its network configuration and follow the steps below: 1. Highlight a device that is being used for replication and click Limit bandwidth at the bottom-right side of the Network configuration pane, or select Replication > Limit network interface bandwidth. A window with the Device, IP Address, Usage, and Speed properties of the selected device is displayed. 2. Select the Limit network bandwidth checkbox to redefine the bandwidth speed (in Mbit/Sec). The bandwidth limit value can range from 1 to 1000. Other
ts760347
117
values will not be accepted. If the checkbox is not selected, the value will default to an unlimited bandwidth speed. 3. Click Ok. The defined limit is displayed in the Limit (Mbit) column of the Network configuration display of the device. Note: If the bandwidth limitation is changed during replication, the change does not take effect immediately. If replication begins after the bandwidth limitation change, the effect is immediate. Go on to the next section.
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 complete the following steps: 1. Choose Replication > Policy > Create policy. The Welcome screen of the Create policy wizard is displayed. 2. Click Next. The Properties screen is displayed: 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 policy's 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. 3. 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.
118
4.
5. 6.
7. 8.
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.
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 policy's 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). 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.
119
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. Complete the following steps 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 policy's Priority according to the importanceand/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 policy's 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. Complete the following steps 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
120
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 policies 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.
Monitoring the replication 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 ProtecTIER Replication Manager periodically updates the status of the grid members and ProtecTIER Manager receives the status updates from the ProtecTIER Replication 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. The grid map feature provides a consolidated view of the entire replication grid with the actual topology groups deployment. The map provides indications for local backups, replication rates and allows panning and zooming capabilities.
121
Select a grid from the navigation pane and click on one of the spokes. The grid member details are displayed to the right. The details displayed are: v Capacity - physical and nominal v Replication activities - running, pending and backlog v Backup 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 90.
Figure 55. Detailed view of a spoke
122
ts760309
Chapter 11. Disaster recovery (DR) mode operations

When a disaster occurs, or a situation arises where the production site (also known as primary or spoke) has gone offline, enter Disaster Recovery (DR) mode so that the disaster recovery site (also known as remote or hub) can take the place of the production site until the primary site comes back online or a new primary site is created. If a situation arises where you must stop using the primary repository (for example, 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 it as the primary site. Once you enter DR mode, all incoming replication 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. Replicated or newly created tapes can then be moved back to the main production site using the failback process.
Working at the DR site

Begin working at the DR site by entering the DR mode. 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 on cartridges originating from the production site so that the cartridges can be used for backup. Cartridges at the DR site can be restored for recovery at any time. If you want to work with the DR site as the new backup target, instead of the primary site, you can either: v Create new cartridges at the DR site and work with them v Run the Cartridge ownership takeover procedure to take control of the cartridges belonging to a down repository in order to have R/W (read/write) permission at the DR site (see Taking over cartridge ownership on page 124.)
Entering Disaster Recovery (DR) mode

Entering DR mode on the DR site repository (i.e. the hub) "declares" that the primary site is now down and DR operations are enabled on the DR site. Note: You can enter DR mode only on a repository that is defined as the hub in the grid. See Chapter 10, Native Replication Management, on page 107. To 1. 2. 3. enter DR mode on the hub: From the Systems Management view, click on the hub repository. Select Replication > Disaster Recovery > Enter DR mode. Choose the spoke repository you want to enter to DR mode.
4. Type yes to confirm that you want to enter DR mode. An automatic procedure is executed that blocks incoming replication to the DR site. Note: If replication is not blocked, the safety of the data at the DR site cannot be guaranteed.
123
Once you have entered DR mode, you can begin working with the various Disaster Recovery operations.
Taking over cartridge ownership

Cartridge ownership, or principality, is the privilege to write to a cartridge (i.e. to 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. Cartridge ownership takeover is used to allow the local repository, or hub, to take control of cartridges belonging to a destroyed repository. The repository can only take ownership of a cartridge if the repository is defined on the Replication Manager as the replacement of the destroyed repository. Run the Repository takeover command before performing the task below. Taking ownership of the cartridges on a destroyed repository will allow you to write on the cartridges previously belonging to the replaced repository. Follow the steps below to take over cartridge ownership: 1. Select Cartridge ownership takeover from the VT > VT Cartridge menu. The Cartridge ownership takeover window is displayed. 2. Choose a repository from the dropdown list that was replaced by the current repository. Note: Make sure that the replaced repository is inactive and unrecoverable to prevent conflict with the data on the cartridges. 3. Click Ok. The principality of the cartridges now belongs to the current repository. Go on to the next section for assessing the cartridge status and synchronize the cartridge data with the backup application catalog.
Assessing cartridge status and syncing with the catalog

The following section explains the process for assessing cartridge status on the DR site and synchronizing the backup application catalog with the cartridges. Before running a restore for disaster recovery, you must verify that the list of associated cartridges are marked as "In-Sync" with the primary site, otherwise an earlier full backup image must be used for recovery. The easiest way to determine 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
124
If the catalog is backed up to a virtual cartridge, check on the DR site that this cartridge appears as In-Sync with the primary site. If the cartridge is not In-Sync, you will need to compare the cartridge's last sync time with the time of the last full backup. To recover the backup application catalog from a backup on a virtual cartridge, you must work with the replicated cartridges on the hub to get an updated copy of the catalog back to the remote site. From the Systems Management window, select the Replication properties view on the Cartridges tab and use the following guidelines for each cartridge before running the procedure for recovering the catalog: Note: The procedure for recovering the selected catalog backup depends on the backup application and is documented in the backup application official documentation. v If the cartridge has been replicated, either a red `X` or a green checkmark will appear in the In-Sync column. If the In-Sync property has a green checkmark, then nothing further needs to be verified and this cartridge is valid for recovery. v If the cartridge is not marked In-Sync, refer to the Last sync time column. This column displays the last time each cartridge's data was fully replicated to the DR site. The cartridge marked with the most recent Last sync time date should be used to recover the backup application catalog. Note: The sync time is updated during replication, and not only when replication for this cartridge is finished.
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. Use the PTCLI inventory filter command to filter the cartridges according to the following properties (see Table 34 on page 137 for more information on running the command): v In-Sync v Last update time v Last sync time All the cartridges marked as In-Sync are valid for recovery. For those cartridges not marked as In-Sync, 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 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.
125
Figure 56. 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.
Reestablishing the production site

In order for the production site to come back online, or for a new site to be established to replace the original production site, some actions are required to reestablish and update the site with the most recent and up-to-date data. Follow these procedures for reestablishing and updating the production site: v Replacing the destroyed repository v Creating a failback policy
126
ts760303
Replacing the destroyed repository

If the repository at the production site (spoke) has been destroyed and cannot be repaired, you can replace it with a new repository. The replacing repository must be part of the grid. Note: Be careful when replacing a repository that you do not accidentally replace a good repository. Follow the steps below in the order in which they appear: 1. Enter DR mode as described in Entering Disaster Recovery (DR) mode on page 123. 2. Run the Repository takeover wizard by selecting Grid Repository takeover. 3. Run the Repository takeover wizard. From the Grids Management view, select Grid > Repository takeover. 4. Select the Unrecoverable repository from the dropdown list. 5. From the Replacing repository dropdown list, select the new repository that you want to replace the unrecoverable repository (the new repository should appear in the dropdown list). Note: This operation is not reversible. 6. Click Ok to begin running the Repository takeover wizard. When you run the Repository takeover wizard, the ProtecTIER Replication Manager will internally do the following actions: v Delete the current grid pair, if a pair exists, between the unrecoverable primary site and remote site (if you have not done this previously on your own). v Remove the unrecoverable repository from the grid. v Create a connection between the replacing repository at the new primary site and the remote site. Go on to The failback policy section for more information on failback policies and how to create them.
The failback policy

Failback is the procedure for replicating back new or old updated cartridges from a DR site to their original restored production site (in order to bring it up-to-date in case it was down), or to a new production site. If the primary repository was down and has been restored, you can return to working with the primary site as the production site and use the DR site as the secondary site. In order to replicate back new or old updated cartridges from the DR site, create a failback policy. 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. Note: The failback policy, in addition to copying the cartridges, also takes care of transferring the principality, or ownership, of all the cartridges that belonged to the temporary primary repository at the DR site to the restored primary repository at the production site.
127
Creating a failback policy

This section describes how to create a failback policy. Important: Only cartridges on the shelf are valid for failback. Follow the steps below 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. Select a spoke repository on which to create the failback policy. 4. Click Next. The Barcode ranges screen is displayed. 5. Enter the barcode range of the cartridges that you want to fail back to the old or replaced primary repository. 6. Click Add to validate and submit the defined barcode range. If the barcode range is invalid, an error message is displayed. 7. Click Next. The Validation Results window displays the validation results of the cartridges in range, the cartridges valid for failback, and those that are invalid for failback. Click the Save report as... button if you want to save the validation summary report. Click Next to view the validation summary report and exit the Failback wizard.
Completing failback and leaving DR mode

Once the primary site is rebuilt or replaced, create the failback policy and wait for it to complete. When the data is returned to the primary site, you can exit DR mode and continue with backups and replication as usual. The failback policy is a one-time policy. When failback is complete, the policy still remains in the Replication policies list. Running and/or modifying this policy is not allowed, and on trying to do so, an error message is displayed. Note: Do not run any backup activities on the restored repository until the failback operation is complete. When the failback operation is complete, follow the steps below to exit DR mode: 1. Select Replication > Disaster Recovery > Leave DR mode. The Leave DR mode window is displayed. 2. From the dropdown menu, select the spoke repository from which you want to exit DR mode. 3. Click Ok. Once the repository is out of DR mode, any replication policy defined on the spoke repository can modify the cartridge data. You can now begin working again with the restored repository.
128
Chapter 12. 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. 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.
Understanding the syntax diagrams

A syntax diagram uses symbols to represent the elements of a command and to specify the rules for using these elements.
Syntax diagrams
Main path line
Begins on the left with double arrowheads (>>) and ends on the right with two arrowheads facing each other (><). If a diagram is longer than one line, each line to be continued ends with a single arrowhead (>) and the next line begins with a single arrowhead. Read the diagrams from left-to-right, top-to-bottom, following the main path line. Keyword
dscli
Represents the name of a command, flag, parameter, or argument. A keyword is not in italics. Spell a keyword exactly as it is shown in the syntax diagram. Required keywords
mkuser -pw password -group group_name [ . . . ] User Name " - "
Indicate the parameters or arguments you must specify for the command. Required keywords appear on the main path line. Mutually exclusive required keywords are stacked vertically. Optional keywords
-h
-help
-?
Indicate the parameters or arguments you can choose to specify for the command. Optional keywords appear below the main path line. Mutually exclusive optional keywords are stacked vertically. Variable
129
variable
Represents the value you need to supply for a parameter or argument, such as a file name, user name, or password. Variables are in italics.
Special characters
- (minus) or / (slash) sign Flags are prefixed with a - (minus) sign. Flags define the action of a command or modify the operation of a command. You can use multiple flags, followed by parameters, when you issue a command. [ ] square brackets Optional values are enclosed in square brackets. { } braces Required or expected values are enclosed in braces. | vertical bar A vertical bar indicates that you have a choice between two or more options or arguments. For example, [ a | b ] indicates that you can choose a, b, or nothing. Similarly, { a | b } indicates that you must choose either a or b. ... ellipsis An ellipsis signifies the values that can be repeated on the command line or multiple values or arguments. dash A dash indicates that, as an alternative to entering the parameter, a value or values are supplied from stdin. Depending on your settings, stdin varies and is available when you are using single-shot or script mode. This option is not available when using interactive mode.
Creating a profile
This topic describes how to create a profile in order to query the ProtecTIER server through the command line interface (CLI) using ptcli. Creating a profile is a necessary task that must be completed prior to accessing ptcli. For more information on using ptcli, see ptcli. 1. Activate ptcli with -p followed by a file name with full path. 2. Once prompted, enter the desired user name and password. This step creates the user-specified file with the user name and password that is needed for login.
ptcli -p h:\ptcli\ptuser User name: ptuser Password: <?xml version="1.0" encoding="UTF-8"? <response command="createprofile" status="success"/>
ptcli
This topic describes how to configure and monitor the ProtecTIER (PT) server through the command line interface (CLI) using ptcli. The ptcli is loaded during the installation of PT software and PT Manager software.
130
Usage
ptcli can be used to do the following: v Configure ProtecTIER (including configuration of a PT repository and configuration of PT VT (virtual tape) libraries). v Monitor ProtecTIER (including statistics of PT VT and statistics about PT repository). v Snapshot and filter PT VT cartridges (mostly used for DR (disaster recovery) scenerios) For more information, see Inventory Command Options on page 136. To run ptcli on a PT node, move into the following directory: /opt/dtc/PTManager. To run the ptcli on a host running PT Manager, move into the PT Manager directory (in Windows, C:\Program Files\IBM\ProtecTIER Manager). The ptcli command is issued from the command line as follows: ptcli
./ptcli <processing options> <command name> <--server options> <--command specific options>
For more information, see the following: v Command Options v Inventory Command Options on page 136 v Server Options on page 140 v Processing Options on page 141
Command Options
The following tables contain lists of commands to invoke on the management server. For information on Inventory commands, see Inventory Command Options on page 136.
Table 19. Add Cartridges command Command AddCartridges Explanation Add Cartridges Command Specific Options Name --name <NAME> --cartridges <NUM> [--maxcartsize <NUM>] Explanation Library name (taken from "Libraries" output) Number of cartridges Maximum cartridge growth in MB. If not specified, the size is not limited. Bar code seed
--seed <SEED>
131
Table 19. Add Cartridges command (continued) Command Example: Explanation Command Specific Options
Add Cartridges
./ptcli AddCartridges --ip 9.148.220.45 --login h:\ptcli\ptadmin Command Specific Options
Command Specific Options:

--name Lib --cartridges 200 --seed TS0000
Table 20. Add Cluster Member Command Command AddClusterMember Explanation Add cluster member Command Specific Options Name --addip <IP> Example: Explanation External IP of the node to add to the cluster
Add Cluster Member

./ptcli AddClusterMember --ip 9.148.220.102 --login h:\ptcli\ptadmin --addip 9.148.220.101
Table 21. Add Library Command Command AddLibrary Explanation Create a new library Command Specific Options Name --name <NAME> [--slots <NUM>] --impexp <NUM> --libtype <NAME> --robot X,Y Explanation Library name (taken from "Libraries" output) Number of slots (defaults to 0) Number of import/export (defaults to 8) Library type (taken from "LibraryTypes" output List of robot assignments in the form of [X,Y] where (X = Node external IP), ( Y = Port) Tape drive model (taken from "DriveModels" output) List of drive assignments in the form of [X,Y,Z] where (X = Number of drives), (Y = Node external IP), and (Z = Port)
--drivemodel <NAME> [--drives X,Y,Z]
132
Table 21. Add Library Command (continued) Command Example: Explanation Command Specific Options
Add Library
./ptcli AddLibrary --ip 9.148.220.45 --login h:\ptcli\ptadmin Command Specific Options

--name Lib1 [--slots] 30
--robot 9.148.220.45,0 --robot 9.148.220.45,1 [--drives] 5,9.148.220.45,0 [--drives] 7,168.159.150.33,0
--impexp
--libtype
TS3500
--drivemodel
ULT3580-TD3
Table 22. Cartridge Info Command Command CartridgeInfo Explanation Print information about specific cartridges in the library Note: The list is sorted by barcode. Command Specific Options Name --name <NAME> --from <NUM> Explanation Library name (taken from "Libraries" output) The number of cartridges before the first printed cartridge in the list of cartridges (the number of cartridges can be taken from "NumberOfCartridges" ouput) The maximum number of cartridges in the output
--count <NUM> Example:
Cartridge Info
./ptcli CartridgeInfo --ip 9.148.220.45 --login h:\ptcli\ptadmin Command Specific Options

--name Lib --from 0 --count 400
133
Table 23. Create Repository Command Command CreateRepository Explanation Create a repository Command Specific Options Name --name <NAME> --system <NAME> --size <SIZE> --peak <NUM> --ratio <NUM> --raid <X,Y,Z> Explanation Repository name System name Repository physical maximum size in TB Peak throughput in MB Deduplication ratio Metadata raid configuration in the form of [X,Y,Z] where (X = Type), (Y = Members) and (Z = Disk size in GB) taken from "RaidConfiguations" output List of GFS (global file system) mounted file systems that will be used to store ProtecTIER repository metadata List of GFS mounted file systems that will be used to store ProtecTIER repository user's data
[--metadata <MOUNT_POINTS>]
[--userdata <MOUNT_POINTS>]
Example:
Create Repository
./ptcli CreateRepository --ip 9.148.220.101 --login h:\ptcli\ptadmin Command Specific Options

--name PTCLI_REP --system PTCLI_SYS --size 2 --peak 300 --ratio 13 --raid FC-10K,4+4,120
Table 24. Drive Models Command Command DriveModels Explanation Prints information about the supported tape drive models Command Specific Options Name --libtype <NAME> Explanation Library type (taken from "LibraryTypes" output
Example:
Drive Models
./ptcli DriveModels --ip 9.148.220.101 --login h:\ptcli\ptadmin --libtype TS3500
Table 25. Libraries Command Command Libraries Explanation Prints the list of libraries on the repository
134
Table 25. Libraries Command (continued) Command Example: Explanation
Libraries
./ptcli Libraries --ip 9.148.220.101 --login h:\ptcli\ptadmin
Table 26. Library Information Command Command LibraryInfo Explanation Prints information about a specific library in the repository Command Specific Options Name --name <NAME> Explanation Library name (taken from "Libraries" output
Example:
Library Info
./ptcli LibraryInfo --ip 9.148.220.101 --login h:\ptcli\ptadmin --name Lib
Table 27. Library Types Command Command LibraryTypes Example: Explanation Prints information about a specific library in the repository
Library Types
./ptcli LibraryTypes --ip 9.148.220.101 --login h:\ptcli\ptadmin
Table 28. Node VTL Statistics Command Command NodeVtlStatistics Explanation Prints the statistics history on the local host Command Specific Options Name --hours <NUM> Explanation The number of statistics hours included in the output. By default, the output should include four chronicles (statistic records) per hour (if uptime >= hours).
Example:
Node Vtl Statistics

./ptcli NodeVtlStatistics --ip 9.148.220.101 --login h:\ptcli\ptadmin --hours 1
135
Table 29. Number of Cartridges Command Command NumberOfCartridges Explanation Prints the number of cartridges in the library Command Specific Options Name --name <NAME> Explanation Library name (taken from "Libraries" output
Example:
Number Of Cartridges
./ptcli NumberOfCartridges --ip 9.148.220.101 --login h:\ptcli\ptadmin --name Lib
Table 30. RAID Configurations Command Command RaidConfigurations Example: Explanation Prints information about the supported raid configurations
Raid Configurations
./ptcli RaidConfigurations --ip 9.148.220.101 --login h:\ptcli\ptadmin
Table 31. Repository Statistics Command Command RepositoryStatistics Example: Explanation Prints the repository statistics
Repository Statistics
./ptcli RepositoryStatistics --ip 9.148.220.101 --login h:\ptcli\ptadmin
Table 32. Server Version Command Command ServerVersion Example: Explanation Prints the server version
Server Version
./ptcli ServerVersion --ip 9.148.220.101 --login h:\ptcli\ptadmin
Inventory Command Options

This topic describes how to query the ProtecTIER server through the command line interface (CLI) using Inventory commands.
Usage
The Inventory command options are used to filter cartridges in a ProtecTIER repository using a variety of criteria. Also, these options can be used to move
136
cartridges that match a certain criteria. Before beginning to filter the cartridges, and/or moving cartridges using the CLI, you must first create a snapshot of the cartridges using the InventoryRefresh command. (See Table 33.) The snapshot will include the most updated properties of the cartridges at the time it is created. Note: Any filter/move operation is executed using the snapshot's contents. Running such a command without a previous refresh is considered an error. Also, for larger repositories, a refresh operation may take considerable time and reduce ProtecTIER's performance during that time. Moving a cartridge using the CLI may fail if the snapshot is not up to date for the cartridge (for instance, if the cartridge is moved or deleted after a snapshot is taken). Operations on libraries for which the snapshot is not up to date may have undesirable consequences.
Table 33. Inventory Refresh command Command InventoryRefresh Example: Explanation Refresh the cartridges inventory snapshot on the server.
Inventory Refresh
./ptcli InventoryRefresh --ip 9.148.220.101 --login h:\ptcli\ptadmin
Table 34. Inventory Filter command Command InventoryFilter Explanation Queries the cartridges inventory snapshot created by the InventoryRefresh command. Command Specific Options Name --querytype <QUERYTYPE> Explanation Type of query to be used by the command: v All - All cartridges in the ProtecTIER repository. v Replica - All cartridges that were replicated into this repository. v Origin - All cartridges that were replicated from this repository. --query <QUERY> Query to be used by the filter command. See Queries on page 141 for more information. The output file path for the query results. The limit for the maximal number of cartridges the query may return.
[--output <PATH>] [--limit <NUM>]
137
Table 34. Inventory Filter command (continued) Command Example: Explanation Command Specific Options
Inventory Filter
./ptcli InventoryFilter --ip 9.148.220.101 --login h:\ptcli\ptadmin Command Specific Options

--querytype replica --query "in_sync = true"
Table 35. Inventory Get Query Fields command Command InventoryGetQueryFields Explanation Command Specific Options
Returns the fields Name Explanation available for the specified --querytype <QUERYTYPE> Type of query to be used query type by the command: v All - All cartridges in the ProtecTIER repository. v Replica - All cartridges that were replicated into this repository. v Origin - All cartridges that were replicated from this repository. See Queries on page 141 for more information.
Example:
Inventory Get Query Fields

./ptcli InventoryGetQueryFields --ip 9.148.220.101 --login h:\ptcli\ptadmin --querytype all
138
Table 36. Inventory Move File command Command InventoryMoveFile Explanation Move a group of cartridges expressed as a file (created manually or using the InventoryFilter command). Command Specific Options Name --filetype <PATH> Explanation The type of the file to be used by the command: v All - All cartridges in the ProtecTIER repository. v Replica - All cartridges that were replicated into this repository. v Origin - All cartridges that were replicated from this repository. v Errors v Barcode --file <PATH> The path to a file containing a list of cartridges to be moved The destination library (or shelf) of the move command A manually created file, listing the barcodes of cartridges in the repository to be moved
--destination <NAME>
--Barcode
Example:
Inventory Move File

./ptcli InventoryMoveFile --ip 9.148.220.45 --login h:\ptcli\ptadmin Command Specific Options

--filetype replica --file "in_synch = true" --destination shelf
139
Table 37. Inventory Move Filter command Command InventoryMoveFilter Explanation Move a group of cartridges (that match a given query) Command Specific Options Name --querytype <QUERYTYPE> Explanation The type of the query to be used by the command: v All - All cartridges in the ProtecTIER repository. v Replica - All cartridges that were replicated into this repository. v Origin - All cartridges that were replicated from this repository. --query <QUERY> The query to be used by the filter command See Queries on page 141 for more information. The destination library of the move command.
--destination <NAME> Example:
Inventory Move Filter

./ptcli InventoryMoveFilter --ip 9.148.220.45 --login h:\ptcli\ptadmin Command Specific Options

--querytype replica --query "in_synch = true" --destination shelf
Table 38. Inventory Statistics command Command InventoryStatistics Example: Explanation Display the latest information about the cartridges inventory snapshot
Inventory Statistics
./ptcli InventoryStatistics --ip 9.148.220.101 --login h:\ptcli\ptadmin
Server Options
This topic describes the server options to use when querying the ProtecTIER server through the command line interface (CLI). Server options are used for connection to the management server. They should appear with each query/action - except for the arguments -h or -v.
Usage
Note: Administrator privileges are required for configuration operations. You can specify the following server options at the beginning of the command string:
140
Table 39. Server options Server options --ip <IP> [--port <PORT>] Explanation Specify the IP address of the management server. Specify the port of the management server. The default is: 3501. Note: This is optional. Force the login if another administrator is already logged in. Note: This is optional.
[--force]
Processing Options
This topic describes how to use the processing options to query the ProtecTIER server through the command line interface (CLI).
Usage
You can specify the following processing options at the beginning of the command string:
Table 40. Processing options Processing options --debug <debug level> Explanation Specify the debug level to print log messages to the console. Choices for the debug level are as follows: v SEVERE v WARNING v ALL --logfile <logfile> --help --version --login <FILE> Specify the name (with full path) to use for the log file name. The default directory is the user home directory. Prints the Help message to the consul and exits. Prints the version information and exits. Log in
Queries
This topic describes what a query is and how to use it in the ProtecTIER server command line interface (CLI).
Usage
A query is a statement in which the user can put one of the following: v White spaces v Numbers v Tokens: and/or/not/is/in/between v String literals (within single quotes): 'AB0000' v Boolean: TRUE/FALSE/true/false v Column names as defined by the column names of the query type v Date: the date format in a query is as follows: datetime('2009-12-27' 08:23:00) Results can be saved in a .csv file using the --output command switch.
141
The .csv file can be used as an input to a CLI move command. This .csv file can be partially edited by the user by removing lines (each line represents a cartridge). User can also create his own barcodes file, and to use this as an input to a move command.
Cartridges set and query type

A filter is always working on the specified set of cartridges: v All: All cartridges in the ProtecTIER repository. v Replica: All cartridges that were replicated into this repository. v Origin: All cartridges that were replicated from this repository. The set of cartridges is stated in the CLI command as querytype'. So the query type can be: all', replica', origin'.
142
Chapter 13. 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 77. Set the HyperFactor mode for libraries. For more information, see Changing the HyperFactor mode on page 153. Reset virtual tape drives and robots. For more information, see Resetting devices on page 155. Unload and moving cartridges from virtual tape drives. For more information, see Unloading and moving cartridges on page 156. v Monitor can only access ProtecTIER Manager monitoring screens. For more information, see Chapter 9, Monitoring ProtecTIER, on page 85.
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.
143
Figure 57. Users Management dialog
2. Click Add. The Add account dialog is displayed.
Figure 58. 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. 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.
144
ts760374
ts760412
Chapter 14. 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 a trained ProtecTIER specialist. A trained ProtecTIER specialist 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 59. Alerts log
Click Events Log on the bottom-right of the View pane to view all the events occurring in the ProtecTIER system. 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.
145
ts760377
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 60. 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.
Generating a problem report for ProtecTIER Manager

Complete this task to generate a status report on your ProtecTIER system for use by IBM Service.
146
ts760414
ts760384
ts760415
A trained ProtecTIER specialist 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 a trained ProtecTIER specialist. Service reports can only be generated for one node at a time. 1. Select a node from the Nodes pane. 2. Choose Node > Create problem report. The Create problem report dialog box is displayed.
Figure 61. Create problem report window
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.
ts760319
147
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 a trained ProtecTIER specialist.
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.
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.
148
Figure 62. 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 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

Complete this task to remove 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
149
ts760436
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 72. 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.
Figure 63. 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.
150
ts760397
Adding a cluster member

Complete this task to add a cluster member back into a two-node cluster. The need for this action becomes necessary when you are asked to remove a ProtecTIER repository. When this occurs you generally have to remove one of the nodes from a two-node cluster, and later add it back. Perform the following steps to add a cluster member into a two-node cluster. 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.
Figure 64. 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
151
ts760376
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. 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. 7. 8. 9. Type Type Type Type a port name. m to return to the wwnutil main menu. 4 and then c to accept the name change. The WWN is changed. 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 a trained ProtecTIER specialist 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 153. v Changing the HyperFactor mode - Enables you to stop the HyperFactoring process. For more information, see Changing the HyperFactor mode on page 153. 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 154. v Resetting devices - Enables you to reset a robot or tape drive in a virtual library. For more information, see Resetting devices on page 155. 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 156.
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.
152
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.
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

Complete this task to change the HyperFactor mode for a specified library. 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. Perform the following steps to change the HyperFactor mode on a specified VT library. 1. Choose VT > VT Library > Set HyperFactor mode. The ProtecTIER VT HyperFactor mode dialog is displayed.
Figure 65. ProtecTIER VT HyperFactor mode dialog
2. Select one of the following options, as directed by a trained ProtecTIER specialist: 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.
ts760385
153
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. A trained ProtecTIER specialist 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.
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 a trained ProtecTIER specialist. 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

Complete this task to change the trace levels for a specified node. 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. Perform the following steps to set the trace levels for a specified node. 1. In the Nodes pane, select a node. 2. Choose Node > Set trace levels. The Set trace levels dialog is displayed.
154
Figure 66. Set trace levels dialog
3. Change the trace level settings, as directed by a trained ProtecTIER specialist. 4. Click Ok. The Set trace levels dialog box closes and the new trace levels are set.
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 a trained ProtecTIER specialist.
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.
155
ts760403
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 a trained ProtecTIER specialist.
Unloading cartridges
Complete this task to unload a cartridge by using ProtecTIER Manager. You must unload a cartridge from its drive to move it to a slot. Perform the following steps to disconnect (unload) a cartridge from a drive: 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.
ts760411
Note: Unloaded drives are indicated with
Moving cartridges
Complete this task to move a cartridge after it has been disconnected (unloaded) from a virtual tape drive. 1. In the Services pane, select a library. 2. Click the Drives tab. 3. 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.
156
Figure 67. 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 Manager's check and recovery wizard on top of inconsistent file systems can harm the consistency of the repository.
Checking for errors requiring fsck

Complete this task to check for file system consistency. The purpose of this task is to discover all error messages that indicate the need to run fsck. Perform the following steps to check for file system consistency errors: 1. Open the /var/log/messages file. 2. Search for error messages of the following types: v GFS: fsid=<cluster name>:<file system name>: fatal filesystem consistency error v GFS: fsid=<cluster name>:<file system name>: about to withdraw from the cluster
ts760389
157
v v v v
GFS: fsid=<cluster name>:<file system name>: telling LM to withdraw GFS: fsid=<cluster name>:<file system name>: withdrawn kernel: [<ffffffff887e8094>] :gfs:gfs_lm_withdraw+0xc4/0xd3 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
Complete this task to run fsck to check the file systems' consistency before you run ProtecTIER Manager to check and repair any ProtecTIER system errors. 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 -n <logical volume name> > vgxx_fsck.out ; for each of the problematic file systems. 6. Type service gfs start. 7. Type service vtfd start.
158
8. Restart the inactive node. 9. Send the fsck output to trained ProtecTIER specialist to determine the next step.
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

Perform the following steps to use ProtecTIER Manager to check for errors: 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 68. 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 a trained ProtecTIER specialist. In the Category sub-pane, filter the list contents by selecting individual categories.
159
ts760383
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 a trained ProtecTIER specialist.
160
Chapter 15. ProtecTIER system recovery procedures

The topics in this section provide tips, guidelines, and tasks for recovering a ProtecTIER server. The and 1. 2. 3. 4. recovery process described in these topics define the customer responsibilities include the following procedures: Preparing to reload a node Installing the Red Hat Enterprise Linux Advanced Platform operating system Reloading the node Installing the RAS package
5. Recovering a server for use with the TS7650G 6. Recovering a server for use with the TS7650 Appliance 7. Recovering a server that was part of a two-node system and configuring it as a single stand-alone node 8. Activating ProtecTIER Replication Manager 9. Backing up the configuration files 10. Analyzing and restoring the replication manager
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 on page 162. If this is a clustered system, and there is currently an operational running node, you must stop all of the functioning node's 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, type the following command: service vtfd stop Stopping this activity will avoid any possibility of corrupting meta data on the repository's management file system, in case the recognition procedure encounters unexpected issues. 4. Verify that the ptconfigd service is running by typing the command: service ptconfigd status 5. If the ptconfigd service is not running, type the following command: service ptconfigd start
161
6. Proceed to Installing the Red Hat Enterprise Linux Advanced Platform operating system.
Installing the Red Hat Enterprise Linux Advanced Platform operating system
This section provides instructions for installing Red Hat Enterprise Linux Advanced Platform 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 <PrtSc> and select the system from the list that is to be recovered. If the KVM is attached, proceed to Installing Red Hat Enterprise Linux, 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 B, RSA connection, on page 185. 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 Red Hat Enterprise Linux.
Installing Red Hat Enterprise Linux

Complete this task to install the Red Hat Enterprise Linux Advanced Platform operating system (RHL) on the server that you are reloading as part of the recovery process. | | | | Attention: Label and disconnect the fibre connections to the adapters in slots 6 and 7 of the server prior to reloading Red Hat. You will reconnect them during the ProtecTIER installation, following the autorun process, and before running ptconfig. You will be prompted to reboot the system. 1. Power on the server if it is not already powered on. 2. Insert the IBM System Storage ProtecTIER Maintenance and Recovery Disk into the server's CD-ROM drive. 3. If the server is already powered on, press Ctrl+Alt+Del to reboot the server.
162
Figure 69. 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. 4. When the Press F12 to Select Boot Device option appears on the screen, press F12.
Figure 70. Select CD as the boot device
5. From the Select Boot Device menu, highlight CD and press Enter.
163
ts760402
ts760392
Note: You may be prompted to Select Boot Device more than once. If so, select CD again and press Enter. 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
Figure 71. Red Hat Enterprise Linux 5 screen
Note: Be sure to enter the command exactly as shown. If the command is entered incorrectly, Red Hat will not be properly configured to work with ProtecTIER and you will need to restart the installation process. | | | | Note: If you encounter a long delay before reaching the screen displayed in Figure 72 on page 165, after entering linux ks=cdrom, the backend storage is being evaluated by the Red Hat installation routines. Please be patient as this may take up to an hour to complete. 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>.
164
ts760401
Figure 72. Verify attached disks
8. Follow the next flow of screens to review the End User License Agreement. Press <Enter> to proceed to the next screen: 9. Review end user license agreement. 10. Continue pressing <Enter> to read the next page:
165
ts760387
Figure 73. 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 74. Accept the license agreement
12. When the installation is complete, the system will restart. During this time, remove the IBM System Storage ProtecTIER Maintenance and Recovery Disk from the server's 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: Can't 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. Proceed to RAS package installation.
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 is automatically reloaded once the ./ptconfig -replace command is run during the server recovery procedure. See Installing ProtecTIER for use with the TS7650G on page 167 or Installing ProtecTIER for use with the TS7650 Appliance on page 170.
166
ts760400
ts760399
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

Complete this task to install the ProtecTIER package on the ProtecTIER server as part of the recovery process. 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 162, 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

Complete this task to establish the installation directory and install the ProtecTIER package. 1. Insert the IBM System Storage ProtecTIER Enterprise Edition V2.4.1.0. DVD and wait for the CD-ROM drive to stop blinking. 2. Type the following commands to create and mount the CD-ROM drive:
mkdir -p /mnt/cdrom 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>
5. Type cd /install. 6. 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. 7. 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>
167
Example: <tar filename>=PT_TS7650G_V2.4.0.0.x86_64 8. Type the following commands to unmount and eject the CD from the CD-ROM drive:
eject <Enter>
9. Remove the CD from the CD-ROM drive. 10. Type the following command:
./autorun <Enter>
The autorun utility will install the ProtecTIER application. The following message is displayed at the end of the installation:
The system will now reboot!
| | | | | | |
Attention: Reconnect the fibre connections to the adapters in slots 6 and 7 of the server that were disconnected prior to reloading Red Hat. Note: Ignore I/O errors that are presented on-screen when the connections are reestablished prior to the reboot. This is due to the recognition of the disk arrays to the server and they will recover when the reboot discovers the connected storage. Although errors will scroll on-screen, you can still press the Enter key to reboot. 11. 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=TS7650G
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.
168
[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 clusters 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 6, Managing nodes and clusters, on page 45 to ensure the node is displayed on the ProtecTIER Manager interface.
169
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

Complete this task to establish the installation directory and install the ProtecTIER package. 1. Insert the IBM System Storage ProtecTIER Appliance Edition V2.4.1.0. DVD and wait for the CD-ROM drive to stop blinking. 2. Type the following commands to mount the CD-ROM drive:
mkdir -p /mnt/cdrom <Enter>
mount /dev/cdrom /mnt/cdrom <Enter> The following output is displayed:

The <filename> directory is created. 7. 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_TS7650_V2.4.0.0.x86_64 8. Type the following command to eject the ProtecTIER installation DVD from the CD-ROM drive:
eject <Enter>
./autorun <Enter>
170
| | | | | | |
Attention: Reconnect the fibre connections to the adapters in slots 6 and 7 of the server that were disconnected prior to reloading Red Hat. Note: Ignore I/O errors that are presented on-screen when the connections are reestablished prior to the reboot. This is due to the recognition of the disk arrays to the server and they will recover when the reboot discovers the connected storage. Although errors will scroll on-screen, you can still press the Enter key to reboot. 11. Press Enter at the prompt to reboot the system. The following message is displayed:
12. When the localhost login: prompt appears, login as root and type the password: admin 13. Set the user to ptadmin by typing the command su - ptadmin (the default password is ptadmin). 14. Change the directories to the /opt/dtc/install directory. From the command line, run the following command:
cd /opt/dtc/install <Enter>
15. 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:
v If you are replacing the server on a 128 spindle appliance model, type the following command:
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.
171
[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 clusters 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. 16. Once the information has been provided, proceed to Chapter 6, Managing nodes and clusters, on page 45 to ensure the node is displayed on the ProtecTIER Manager interface.
172
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 command's 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.4.1.0. DVD and wait for the CD drive to stop blinking. 5. Type the following commands to create and mount the CD-ROM drive:
mkdir -p /mnt/cdrom
mount /dev/cdrom /mnt/cdrom The following output is displayed:

The <tar filename> directory is created. 10. 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_TS7650G_V2.4.0.0.x86_64

173
11. Type the following commands to unmount and eject the CD from the CD-ROM drive:
eject <Enter>
./autorun <Enter>
Press Enter at the prompt to reboot the system. The following message is displayed:
14. After the system boots up, set the user to ptadmin by typing the command su - ptadmin (the default password is ptadmin). 15. Change the directories to the /opt/dtc/install directory. From the command line, run the following command:
cd /opt/dtc/install <Enter> <Enter>
16. Type the following command:

./ptconfig -replace -model=TS7650G -dualBySingle
The following output is displayed.
174
[root@localhost install]# ./ptconfig -replace -model=TS7650G -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 TS7650G 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. Go on to Upgrading ProtecTIER Manager on page 37.
175
Activating ProtecTIER Replication Manager

The ProtecTIER Replication Manager application is installed on a customer-designated ProtecTIER server. IBM recommends installing ProtecTIER Replication Manager at the replication destination site, so that the ProtecTIER Replication Manager will remain available in a disaster recovery situation. Note: If you are not enabling replication, you do not need to install ProtecTIER Replication Manager. Instead, go to Chapter 4, Installing ProtecTIER Manager, on page 37. Important: ProtecTIER Replication Manager requires access to TCP port 6202. Before installing the ProtecTIER Replication Manager application, ensure that TCP port 6202 is open in the customer's firewall. If port 6202 is behind the firewall, data replication will fail. 1. Log in to the ProtecTIER v2.4 server on which the ProtecTIER Replication 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. To activate the ProtecTIER Replication Manager enter the following commands: cd /opt/dtc/install <enter> ./ptconfig -activatePTRepMan <enter> Note: If in the future you should need to deactivate the ProtecTIER Replication Manager, use the following command: ./ptconfig -deactivatePTRepMan <enter> 4. The following ProtecTIER Replication Manager messages are displayed: Are you sure you want to activate the ProtecTIER Replication Manager on this node? (yes|no) Enter yes to activate the ProtecTIER Replication Manager or no if not activating the ProtecTIER Replication Manager. 5. The following ProtecTIER Replication Manager messages are displayed after selecting yes : Gathering information activatePTReplicationManager ended successfully 6. Go to Chapter 4, Installing ProtecTIER Manager, on page 37.
Backing up the configuration files

The ProtecTIER Replication Manager configuration files are automatically backed up and saved by default. However, you can choose to cancel the automatic configuration file backups and perform the operation manually. The following task explains how to manually back up the Replication Manager configuration files. Backups of the configuration files from ProtecTIER Replication Manager are saved as a .zip file. The .zip file contains the /gm_work directory with all its subdirectories: configuration, data, and history, without the log files. When
176
restoring ProtecTIER Replication 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 checkbox found on the Backup tab under the Tools > Preferences window in the Grids Management view. From the Preferences window, 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 Replication Manager > Backup configuration files. The Backup configuration files dialog is displayed. 2. Enter the customer name in the Customer name field for which to provide backup information and click Ok. A message is displayed that the backup .zip file was saved on the ProtecTIER Replication 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 ProtecTIER Replication Manager

This section describes the procedure for analyzing and restoring an inactive or "lost" ProtecTIER Replication Manager server using ProtecTIER Manager. Note: Once the ProtecTIER Replication 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 ProtecTIER Replication Manager restore procedure is done grid by grid and can be done in either of the following ways: v Using an existing backup file: PtReplicationManager_<hostName>_<customerName>_time_ConfigurationBackup.zip v Using an accessible repository that was once a member of a grid. Important: Use the most updated file determined by the newest time value. Access the Restore grid procedure from the Grids Management view of ProtecTIER Manager.
Restoring the ProtecTIER Replication Manager

The following tasks describe the different methods for restoring the processed grid using the Restore grid procedure. The ProtecTIER Replication Manager server automatically handles grid analysis. Grid analysis validates and checks the integrity of the grid in relation to its grid
177
members. To begin restoring a grid, import a grid for analysis by selecting one of the following tabs appearing on the Restore grid window: v Default backup (see The Default backup tab) v File (see The File tab on page 179) v IP Address (see The IP Address tab on page 179)
The Default backup tab

The following task describes how to restore the Replication Manager from the Default backup tab. If ProtecTIER Replication Manager is installed on a ProtecTIER server, the entire Replication Manager is automatically analyzed and restored. Follow the steps below to import a grid for analysis and restore: 1. Select the Restore grid option from the Replication Manager menu. The Restore grid dialog is displayed. 2. Select the Default backup tab. 3. Click Read file. The grids are automatically retrieved from the backup configuration file that was found on the server and displayed. Before restoring a grid, you can preview the grid layout by clicking on the Grid preview tab. If all the repositories are accessible and validated successfully, go on to the next step. 4. Click Restore. The current grid is restored and the next grid for analysis is displayed. 5. Continue restoring, grid by grid, until the entire Replication Manager is restored. The following messages might be displayed during the grid analysis:
Table 41. Grid analysis messages Message The repository was not accessible Meaning The ProtecTIER Replication Manager failed to communicate with the specific repository and could not get the configuration ID. 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 ProtecTIER Replication Manager during a new configuration layout. 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. Restoration is not recommended.
Inconsistent grid member
Old configuration ID was found
None. The new ProtecTIER Replication Manager will update the repository with the new configuration layout.
178
Table 41. Grid analysis messages (continued) Message Empty message Meaning Comparison and validation was successful. Recommended action
Once you have finished restoring the ProtecTIER Replication Manager, return to Chapter 10, Native Replication Management, on page 107 to begin working again with ProtecTIER Replication Manager.
The File tab

The following task describes how to restore the Replication Manager from the File tab. If you are restoring a grid from a backup .zip file, locate the grid data files in the /gm_work/data/grid.<x>.xml where <x> represents the grid ID number. Follow the steps below to import a grid for analysis and restore: 1. Select the Restore grid option from the Replication Manager menu. The Restore grid dialog is displayed. 2. Select the File tab. 3. Browse to the backup filename from which you want to analyze and restore the grid, or enter a filename in the Backup .ZIP file name field. Note: If you are restoring a grid from a backup .zip file that has been extracted, browse to the grid.<x>.xml file. Click Read file. Select a grid to analyze from the dropdown list. The grid analysis is displayed. Click Restore. The current grid is restored and removed from the grid analysis list. Select the next grid for analysis from the dropdown list. Continue restoring, grid by grid, until the entire Replication Manager is restored.
4. 5. 6. 7.
Once you have finished restoring the ProtecTIER Replication Manager, return to Chapter 10, Native Replication Management, on page 107 to begin working again with ProtecTIER Replication Manager.
The IP Address tab

The following task describes how to restore a grid from the Replication IP address of a repository from the IP Address tab. If you search for a backup file and cannot find one, then you can restore a grid on which the repository was previously a member. With a given replication IP address, the analysis phase is done with the respective repository's grid data in relation to the other grid members. Follow the steps below to import a grid for analysis and restore: 1. Select the Restore grid option from the Replication Manager menu. The Restore grid dialog is displayed. 2. Select the IP Address tab. 3. Enter the Replication IP address , the Port number, and the Ping port number of the accessible repository that was previously a member of the grid. 4. Click Analyze grid. The grid analysis is displayed.
179
5. Click Restore. The current grid is restored. Once you have finished restoring the ProtecTIER Replication Manager, return to Chapter 10, Native Replication Management, on page 107 to begin working again with ProtecTIER Replication Manager.
180
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Appendix A. Verifying and upgrading the storage subsystem firmware, NVSRAM, and ESM
The firmware on your storage subsystem must be upgraded to 7.50.13.00 or higher prior to upgrading to ProtecTIER code level 2.4.0.0. Complete the following steps to verify the firmware level and update the firmware if it is not at the correct level. 1. Verify that the firmware is at the correct code level. a. If you are not already logged in to the TSSC, log in with user ID service and password service. b. Right-click on the blue desktop, and from the IBM TS3000 System Console menu, select Browser Functions SM GUI Functions Launch GUI. Note: If you receive a message that the DS Storage Manager GUI is not installed, you need to install it using the supplied TS3000 System Console Graphical User Interface CD version 10.60.x5.16 Use step 3 on page 182 below to perform the installation, and return to this step after DS Storage Manager is installed. If the DS Storage Manager GUI is already installed, verify the version by selecting Help About. If the DS Storage Manager version is below 10.60.x5.16 use step 3 on page 182 below to install the new version of DS Storage Manager and return to this step. The new version of DS Storage Manager will replace the previous version. c. If multiple storage systems are listed, you will need to identify the storage system you are updating. Click on a storage system in the left navigation pane. When the subsystem list appears in the right pane, click to highlight the storage system, right-click on it, and select Locate Storage Subsystem from the drop-down menu. The indicator lights on the storage subsystem will flash in blue until you click OK. If the storage system you want to update is not listed, or you are using DS Storage Manager for the first time and no systems are displayed, select Edit Add Storage Subsystem. When prompted in the Add New Storage Subsystem menu, enter the In-Band IP address of the storage subsystem, and click Add. The DS Storage Manager will attempt to locate the subsystem. If it is successful, it will be added to the storage list, if it is not, verify the IP addresses entered. d. Once the correct subsystem has been identified, in the right pane, the storage subsystem should display as Optimal. If it does not, resolve any failure indictions before proceeding with the firmware upgrade. If you cannot resolve a failure condition and return the system to optimal status, contact your next level of IBM support. e. If the storage displays as optimal status, double-click to open the array. At the Synchronize window, click Cancel. If prompted for a cache subsystem password, enter ibm2serv. Click No when prompted to change the password. Attention: Do not change the password when prompted. This password must not change to preserve access for service. f. Click the tab for Logical/Physical. Controller A and B should be displayed. g. Right-click on Controller A in the Storage Subsystem window. h. Select Properties. Verify and record the levels displayed for the DS4700 Firmware and NVSRAM:
181
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
v Firmware Version at the minimum level of 07.50.13.00 or the recommended level of 7.60.28.00 v NVSRAM Version at the minimum level of N1814D47R1050V07 or the recommended level of N1814D47R1060V04 i. Close the Properties window. From the title bar, select Advanced Maintenance Download ESM Configuration Settings. Verify that Card A and Card B firmware are at the minimum level of 98C5 or the recommended level of 98D0. j. Click on Close to close the window. k. If the storage firmware level is lower than 7.50.13.00 (for example: 7.15.10.6 or 7.36.17.0), it will need to be updated to minimum supported levels with ProtecTIER v. 2.4 microcode. Go to 2 to copy the latest storage firmware from the IBM System Storage ProtecTIER Manager V2.4.3.0 DVD to the TSSC. If the storage firmware levels are 7.50.13.00 or higher (recommended level is 7.60.28.00), proceed to the ProtecTIER v. 2.4 upgrade. 2. Insert the IBM System Storage ProtecTIER Manager V2.4.3.0 DVD into the TSSC drive. a. If you are not already logged in to the TSSC, log in with user ID service and password service. b. Right-click on the blue desktop of the TSSC, and from the System Console menu select System Console Actions CD copy to console. c. On the CD copy to console screen, select option 3, /home/service/offload. d. Follow the instructions on the screen to copy the code. e. After the code has been copied, the disk will eject. f. Verify the /home/service/offload/DS4k Storage Manager v10.60.x5.17 for Windows 32-bit/DS4700 directory contents: v esm98D0.esm v FW_DS4700_07602800.dlp v IBM_EXP810_CFG_v0150.DL v N1814D47R1060V04.dlp v ST3450856FC_B989.LOD Right click on the TSSC's blue desktop, from the System Console menu, select Terminal.
cd ls /home/service/offload/DS4k Storage Manager v10.60.x5.17 for Windows 32-bit/DS4700 [enter] [enter]
Note: The storage system firmware is located on the IBM System Storage ProtecTIER Manager V2.4.3.0 DVD under a 10.60.x5.17 for Windows 32-bit directory. It is used on the TSSC's Linux version as well, and the files are the same. 3. Upgrade the DS Storage Manager application to version 10.60.x5.16 on the TSSC. a. Right-click on the blue desktop of the TSSC and select Browser Functions DS4000 Install GUI. b. The TSSC's CD tray will open automatically. Insert the TS3000 System Console Storage Manager CD, version 10.60.x5.16 (located in the TSSC ship group) into the TSSC and follow the instructions on the screen to complete the installation.
4. Locate the firmware and NVSRAM files using the DS Storage Manager GUI.
182
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
a. Launch the DS Storage Manager from the TSSC by right-clicking on the TSSC and selecting Browser Functions Storage Manager GUI Functions Launch GUI. b. Select the Storage Subsystem that will be upgraded (identified in step 1 on page 181 above) by right-clicking on the storage and selecting Manage Storage Subsystem. If prompted to enter a password, enter: ibm2serv. If prompted to change or set a password, click No. If prompted with a Synchronize Controller Clocks window, click Cancel. c. In the Manage Storage Subsystem window, select the Advanced button in the top menu bar. d. Select Maintenance Download Controller Firmware. The Download Controller Firmware window will appear. The DS Storage Manager will check the health of the storage subsystem. This might take several minutes. If there is a problem associated with the storage, it will be identified, and you will not be able to continue with the upgrade until the problem is resolved. If you cannot isolate or resolve the error condition, contact your next level of support. e. In the Controller Firmware panel, press the Select File button. A new window will appear. f. Enter the path of the controller firmware and press Enter. The path might be similar to the following: /home/service/offload/DS4k Storage Manager v10.60.x5.17 for Windows 32-bit/DS4700. In the same window, click to highlight the FW.DS4700_07602800.dlp file from the Files section. Note: The storage system firmware is located on the IBM System Storage ProtecTIER Manager V2.4.3.0 DVD under a 10.60.x5.17 for Windows 32-bit directory, DS4k Storage Manager v10.60.x5.17 for Windows 32-bit. It is used on the TSSC's Linux version as well, and the files are the same. g. Press the OK button at the bottom of the window. You will return to the Download Controller Firmware window. h. In the Download Controller Firmware window select the Transfer the NVSRAM file with controller firmware button. i. Press the Select File button in the NVSRAM section. A new window will appear. Enter the path of the NVSRAM and press Enter. The path might be similar to the following: /home/service/offload/DS4k Storage Manager v10.60.x5.17 for Windows 32-bit/DS4700. In the same window click to highlight the N1814D47R1060V04.dlp file from the Files section. Note: The storage system firmware is located on the IBM System Storage ProtecTIER Manager V2.4.3.0 DVD under a 10.60.x5.17 for Windows 32-bit directory, DS4k Storage Manager v10.60.x5.17 for Windows 32-bit. It is used on the TSSC's Linux version as well, and the files are the same. j. Press the OK button at the bottom of the window. You will return to the Download Controller Firmware window. 5. Upgrade the firmware and NVSRAM using the DS Storage Manager . In the Download Controller Firmware window, select the Transfer button. When you are prompted with a version compatibility window to confirm the download and you are asked, "Do you want to continue?" click Yes. The transfer and activation process should take 15-20 minutes to complete. Note: During this activation, both A and B controllers will be upgraded. When the activation is completed, a New Firmware Detected window will appear. Click OK.
Appendix A. Verifying and upgrading the storage subsystem firmware, NVSRAM, and ESM
183
| | | | | | | | | | | | | | | | | | | | | | | | | | | |
6. Upgrade the ESM level. a. In the Manage Storage Subsystem window, select Advanced button in the top menu bar. b. Select Maintenance Download ESM Firmware. The Download Environmental (ESM) Card Firmware window will appear. c. In the Drive Enclosure section, click to highlight the enclosure that will be upgraded. d. In the ESM Firmware section, press the Select File button. A new window will appear. Enter the path of the ESM and press Enter. The path might be similar to the following: /home/service/offload/DS4k Storage Manager v10.60.x5.17 for Windows 32-bit/DS4700. In the same window click to highlight the esm98D0.esm file from the Files section. Note: The storage system firmware is located on the IBM System Storage ProtecTIER Manager V2.4.3.0 DVD under a 10.60.x5.17 for Windows 32-bit directory, DS4k Storage Manager v10.60.x5.17 for Windows 32-bit. It is used on the TSSC's Linux version as well, and the files are the same. e. Press the OK button at the bottom of the window. You will return to the Download Environmental (ESM) Card Firmware window. f. Press the Start button in the Download Environmental Card Firmware window to start the ESM download process. You will be prompted with a Confirm Download window. Type yes and click OK to continue. This process should take 5-7 minutes for each enclosure. The Status column will display Transferring until the process is complete. The enclosures can only be updated one at a time. g. Repeat substep 6c. through substep 6f. for each enclosure. 7. The upgrade process of the firmware and NVSRAM is now complete. Close any open DS Storage Manager windows and right click on the blue desktop of the TSSC and select Logout.
184

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.22 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 187 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 187. 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 75.
Figure 75. 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.
185
6. Right-click Local Area Connections->Properties. See Figure 76.
Figure 76. Local Area Connection Properties
7. From the list, select Internet Protocol (TCP/IP), then click Properties. See Figure 77.
Figure 77. Local Area Connection Properties: Internet Protocol (TCP/IP)
186
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 78.
Figure 78. Remote Supervisor Adapter II Refresh 1 Welcome window
You are now logged into the server's RSA. 16. Go on to Enabling Remote Control on page 188.
187
Enabling Remote Control

Once you are connected to the server's 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 79.
Figure 79. 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 79. 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.
188
Appendix C. 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 42. TSSC IP address ranges IP addresses: Component Server Server Port eth5 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
189
190
Appendix D. Worldwide time zone codes

Use the information in the following table to help you set the system's time zone.
Time zone codes

The following table lists all of the worldwide time zone codes and the associated time zone descriptions. Additional information about the time zone is located in the Comments column.
Code AD AE AF AG AI AL AM AN AO AQ AQ AQ AQ AQ AQ AQ AQ AQ AQ AR AR AR AR AR AR AR AR AR AR AS Time zone Europe/Andorra Asia/Dubai Asia/Kabul America/Antigua America/Anguilla Europe/Tirane Asia/Yerevan America/Curacao Africa/Luanda Antarctica/McMurdo Antarctica/South_Pole Antarctica/Rothera Antarctica/Palmer Antarctica/Mawson Antarctica/Davis Antarctica/Casey Antarctica/Vostok Antarctica/DumontDUrville Antarctica/Syowa America/Argentina/Buenos_Aires America/Argentina/Cordoba America/Argentina/Jujuy America/Argentina/Tucuman America/Argentina/Catamarca America/Argentina/La_Rioja America/Argentina/San_Juan America/Argentina/Mendoza America/Argentina/Rio_Gallegos America/Argentina/Ushuaia Pacific/Pago_Pago McMurdo Station, Ross Island Amundsen-Scott Station, South Pole Rothera Station, Adelaide Island Palmer Station, Anvers Island Mawson Station, Holme Bay Davis Station, Vestfold Hills Casey Station, Bailey Peninsula Vostok Station, S Magnetic Pole Dumont-d'Urville Station, Terre Adelie Syowa Station, E Ongul I Buenos Aires (BA, CF) most locations (CB, CC, CN, ER, FM, LP, MN, NQ, RN, SA, SE, SF, SL) Jujuy (JY) Tucuman (TM) Catamarca (CT), Chubut (CH) La Rioja (LR) San Juan (SJ) Mendoza (MZ) Santa Cruz (SC) Tierra del Fuego (TF) Comments
191
Code AT AU AU AU AU AU AU AU AU AU AU AU AU AW AX AZ BA BB BD BE BF BG BH BI BJ BL BM BN BO BR BR BR BR BR BR BR BR BR BR BR BR
Time zone Europe/Vienna Australia/Lord_Howe Australia/Hobart Australia/Currie Australia/Melbourne Australia/Sydney Australia/Broken_Hill Australia/Brisbane Australia/Lindeman Australia/Adelaide Australia/Darwin Australia/Perth Australia/Eucla America/Aruba Europe/Mariehamn Asia/Baku Europe/Sarajevo America/Barbados Asia/Dhaka Europe/Brussels Africa/Ouagadougou Europe/Sofia Asia/Bahrain Africa/Bujumbura Africa/Porto-Novo America/St_Barthelemy Atlantic/Bermuda Asia/Brunei America/La_Paz America/Noronha America/Belem America/Fortaleza America/Recife America/Araguaina America/Maceio America/Bahia America/Sao_Paulo America/Campo_Grande America/Cuiaba America/Porto_Velho America/Boa_Vista
Comments
Lord Howe Island Tasmania - most locations Tasmania - King Island Victoria New South Wales - most locations New South Wales - Yancowinna Queensland - most locations Queensland - Holiday Islands South Australia Northern Territory Western Australia - most locations Western Australia - Eucla area
Atlantic islands Amapa, E Para NE Brazil (MA, PI, CE, RN, PB) Pernambuco Tocantins Alagoas, Sergipe Bahia S & SE Brazil (GO, DF, MG, ES, RJ, SP, PR, SC, RS) Mato Grosso do Sul Mato Grosso W Para, Rondonia Roraima
192
Code BR BR BR BS BT BW BY BZ CA CA CA CA CA CA CA CA CA CA CA CA CA CA CA CA CA CA CA CA CA CA CA CA CA CA CA CC
Time zone America/Manaus America/Eirunepe America/Rio_Branco America/Nassau Asia/Thimphu Africa/Gaborone Europe/Minsk America/Belize America/St_Johns America/Halifax America/Glace_Bay America/Moncton America/Goose_Bay America/Blanc-Sablon America/Montreal America/Toronto America/Nipigon America/Thunder_Bay America/Iqaluit America/Pangnirtung America/Resolute America/Atikokan America/Rankin_Inlet America/Winnipeg America/Rainy_River America/Regina America/Swift_Current America/Edmonton America/Cambridge_Bay America/Yellowknife America/Inuvik America/Dawson_Creek America/Vancouver America/Whitehorse America/Dawson Indian/Cocos
Comments E Amazonas W Amazonas Acre
Newfoundland Time, including SE Labrador Atlantic Time - Nova Scotia (most places), PEI Atlantic Time - Nova Scotia - places that did not observe DST 1966-1971 Atlantic Time - New Brunswick Atlantic Time - Labrador - most locations Atlantic Standard Time - Quebec - Lower North Shore Eastern Time - Quebec - most locations Eastern Time - Ontario - most locations Eastern Time - Ontario & Quebec - places that did not observe DST 1967-1973 Eastern Time - Thunder Bay, Ontario Eastern Time - east Nunavut - most locations Eastern Time - Pangnirtung, Nunavut Eastern Time - Resolute, Nunavut Eastern Standard Time - Atikokan, Ontario and Southampton I, Nunavut Central Time - central Nunavut Central Time - Manitoba & west Ontario Central Time - Rainy River & Fort Frances, Ontario Central Standard Time - Saskatchewan - most locations Central Standard Time - Saskatchewan - midwest Mountain Time - Alberta, east British Columbia & west Saskatchewan Mountain Time - west Nunavut Mountain Time - central Northwest Territories Mountain Time - west Northwest Territories Mountain Standard Time - Dawson Creek & Fort Saint John, British Columbia Pacific Time - west British Columbia Pacific Time - south Yukon Pacific Time - north Yukon
193
Code CD CD CF CG CH CI CK CL CL CM CN CN CN CN CN CO CR CU CV CX CY CZ DE DJ DK DM DO DZ EC EC EE EG EH ER ES ES ES ET FI FJ
Time zone Africa/Kinshasa Africa/Lubumbashi Africa/Bangui Africa/Brazzaville Europe/Zurich Africa/Abidjan Pacific/Rarotonga America/Santiago Pacific/Easter Africa/Douala Asia/Shanghai Asia/Harbin Asia/Chongqing Asia/Urumqi Asia/Kashgar America/Bogota America/Costa_Rica America/Havana Atlantic/Cape_Verde Indian/Christmas Asia/Nicosia Europe/Prague Europe/Berlin Africa/Djibouti Europe/Copenhagen America/Dominica America/Santo_Domingo Africa/Algiers America/Guayaquil Pacific/Galapagos Europe/Tallinn Africa/Cairo Africa/El_Aaiun Africa/Asmara Europe/Madrid Africa/Ceuta Atlantic/Canary Africa/Addis_Ababa Europe/Helsinki Pacific/Fiji
Comments west Dem. Rep. of Congo east Dem. Rep. of Congo
most locations Easter Island & Sala y Gomez
east China - Beijing, Guangdong, Shanghai, etc. Heilongjiang (except Mohe), Jilin central China - Sichuan, Yunnan, Guangxi, Shaanxi, Guizhou, etc. most of Tibet & Xinjiang west Tibet & Xinjiang
mainland Galapagos Islands
mainland Ceuta & Melilla Canary Islands
194
Code FK FM FM FM FO FR GA GB GD GE GF GG GH GI GL GL GL GL GM GN GP GQ GR GS GT GU GW GY HK HN HR HT HU ID ID ID ID IE IL IM
Time zone Atlantic/Stanley Pacific/Truk Pacific/Ponape Pacific/Kosrae Atlantic/Faroe Europe/Paris Africa/Libreville Europe/London America/Grenada Asia/Tbilisi America/Cayenne Europe/Guernsey Africa/Accra Europe/Gibraltar America/Godthab America/Danmarkshavn America/Scoresbysund America/Thule Africa/Banjul Africa/Conakry America/Guadeloupe Africa/Malabo Europe/Athens Atlantic/South_Georgia America/Guatemala Pacific/Guam Africa/Bissau America/Guyana Asia/Hong_Kong America/Tegucigalpa Europe/Zagreb America/Port-au-Prince Europe/Budapest Asia/Jakarta Asia/Pontianak Asia/Makassar Asia/Jayapura Europe/Dublin Asia/Jerusalem Europe/Isle_of_Man
Comments
Truk (Chuuk) and Yap Ponape (Pohnpei) Kosrae
most locations east coast, north of Scoresbysund Scoresbysund / Ittoqqortoormiit Thule / Pituffik
Java & Sumatra west & central Borneo east & south Borneo, Celebes, Bali, Nusa Tengarra, west Timor Irian Jaya & the Moluccas
195
Code IN IO IQ IR IS IT JE JM JO JP KE KG KH KI KI KI KM KN KP KR KW KY KZ KZ KZ KZ KZ LA LB LC LI LK LR LS LT LU LV LY MA MC MD
Time zone Asia/Calcutta Indian/Chagos Asia/Baghdad Asia/Tehran Atlantic/Reykjavik Europe/Rome Europe/Jersey America/Jamaica Asia/Amman Asia/Tokyo Africa/Nairobi Asia/Bishkek Asia/Phnom_Penh Pacific/Tarawa Pacific/Enderbury Pacific/Kiritimati Indian/Comoro America/St_Kitts Asia/Pyongyang Asia/Seoul Asia/Kuwait America/Cayman Asia/Almaty Asia/Qyzylorda Asia/Aqtobe Asia/Aqtau Asia/Oral Asia/Vientiane Asia/Beirut America/St_Lucia Europe/Vaduz Asia/Colombo Africa/Monrovia Africa/Maseru Europe/Vilnius Europe/Luxembourg Europe/Riga Africa/Tripoli Africa/Casablanca Europe/Monaco Europe/Chisinau
Comments
Gilbert Islands Phoenix Islands Line Islands
most locations Qyzylorda (Kyzylorda, Kzyl-Orda) Aqtobe (Aktobe) Atyrau (Atirau, Gur'yev), Mangghystau (Mankistau) West Kazakhstan
196
Code ME MF MG MH MH MK ML MM MN MN MN MO MP MQ MR MS MT MU MV MW MX MX MX MX MX MX MX MX MY MY MZ NA NC NE NF NG NI NL NO NP
Time zone Europe/Podgorica America/Marigot Indian/Antananarivo Pacific/Majuro Pacific/Kwajalein Europe/Skopje Africa/Bamako Asia/Rangoon Asia/Ulaanbaatar Asia/Hovd Asia/Choibalsan Asia/Macau Pacific/Saipan America/Martinique Africa/Nouakchott America/Montserrat Europe/Malta Indian/Mauritius Indian/Maldives Africa/Blantyre America/Mexico_City America/Cancun America/Merida America/Monterrey America/Mazatlan America/Chihuahua America/Hermosillo America/Tijuana Asia/Kuala_Lumpur Asia/Kuching Africa/Maputo Africa/Windhoek Pacific/Noumea Africa/Niamey Pacific/Norfolk Africa/Lagos America/Managua Europe/Amsterdam Europe/Oslo Asia/Katmandu
Comments
most locations Kwajalein
most locations Bayan-Olgiy, Govi-Altai, Hovd, Uvs, Zavkhan Dornod, Sukhbaatar
Central Time - most locations Central Time - Quintana Roo Central Time - Campeche, Yucatan Central Time - Coahuila, Durango, Nuevo Leon, Tamaulipas Mountain Time - S Baja, Nayarit, Sinaloa Mountain Time - Chihuahua Mountain Standard Time - Sonora Pacific Time peninsular Malaysia Sabah & Sarawak
197
Code NR NU NZ NZ OM PA PE PF PF PF PG PH PK PL PM PN PR PS PT PT PT PW PY QA RE RO RS RU RU RU RU RU RU RU RU RU RU RU RU RU RU
Time zone Pacific/Nauru Pacific/Niue Pacific/Auckland Pacific/Chatham Asia/Muscat America/Panama America/Lima Pacific/Tahiti Pacific/Marquesas Pacific/Gambier Pacific/Port_Moresby Asia/Manila Asia/Karachi Europe/Warsaw America/Miquelon Pacific/Pitcairn America/Puerto_Rico Asia/Gaza Europe/Lisbon Atlantic/Madeira Atlantic/Azores Pacific/Palau America/Asuncion Asia/Qatar Indian/Reunion Europe/Bucharest Europe/Belgrade Europe/Kaliningrad Europe/Moscow Europe/Volgograd Europe/Samara Asia/Yekaterinburg Asia/Omsk Asia/Novosibirsk Asia/Krasnoyarsk Asia/Irkutsk Asia/Yakutsk Asia/Vladivostok Asia/Sakhalin Asia/Magadan Asia/Kamchatka
Comments
most locations Chatham Islands
Society Islands Marquesas Islands Gambier Islands
mainland Madeira Islands Azores
Moscow-01 - Kaliningrad Moscow+00 - west Russia Moscow+00 - Caspian Sea Moscow+01 - Samara, Udmurtia Moscow+02 - Urals Moscow+03 - west Siberia Moscow+03 - Novosibirsk Moscow+04 - Yenisei River Moscow+05 - Lake Baikal Moscow+06 - Lena River Moscow+07 - Amur River Moscow+07 - Sakhalin Island Moscow+08 - Magadan Moscow+09 - Kamchatka
198
Code RU RW SA SB SC SD SE SG SH SI SJ SK SL SM SN SO SR ST SV SY SZ TC TD TF TG TH TJ TK TL TM TN TO TR TT TV TW TZ UA UA UA UA
Time zone Asia/Anadyr Africa/Kigali Asia/Riyadh Pacific/Guadalcanal Indian/Mahe Africa/Khartoum Europe/Stockholm Asia/Singapore Atlantic/St_Helena Europe/Ljubljana Arctic/Longyearbyen Europe/Bratislava Africa/Freetown Europe/San_Marino Africa/Dakar Africa/Mogadishu America/Paramaribo Africa/Sao_Tome America/El_Salvador Asia/Damascus Africa/Mbabane America/Grand_Turk Africa/Ndjamena Indian/Kerguelen Africa/Lome Asia/Bangkok Asia/Dushanbe Pacific/Fakaofo Asia/Dili Asia/Ashgabat Africa/Tunis Pacific/Tongatapu Europe/Istanbul America/Port_of_Spain Pacific/Funafuti Asia/Taipei Africa/Dar_es_Salaam Europe/Kiev Europe/Uzhgorod Europe/Zaporozhye Europe/Simferopol
Comments Moscow+10 - Bering Sea
most locations Ruthenia Zaporozh'ye, E Lugansk / Zaporizhia, E Luhansk central Crimea

199
Code UG UM UM UM US US US US US US US US US US US US US US US US US US US US US US US US US US US UY UZ UZ VA VC VE VG VI
Time zone Africa/Kampala Pacific/Johnston Pacific/Midway Pacific/Wake America/New_York America/Detroit America/Kentucky/Louisville America/Kentucky/Monticello America/Indiana/Indianapolis America/Indiana/Vincennes America/Indiana/Knox America/Indiana/Winamac America/Indiana/Marengo America/Indiana/Vevay America/Chicago America/Indiana/Tell_City America/Indiana/Petersburg America/Menominee America/North_Dakota/Center America/North_Dakota/New_Salem America/Denver America/Boise America/Shiprock America/Phoenix America/Los_Angeles America/Anchorage America/Juneau America/Yakutat America/Nome America/Adak Pacific/Honolulu America/Montevideo Asia/Samarkand Asia/Tashkent Europe/Vatican America/St_Vincent America/Caracas America/Tortola America/St_Thomas
Comments
Johnston Atoll Midway Islands Wake Island Eastern Time Eastern Time - Michigan - most locations Eastern Time - Kentucky - Louisville area Eastern Time - Kentucky - Wayne County Eastern Time - Indiana - most locations Eastern Time - Indiana - Daviess, Dubois, Knox & Martin Counties Eastern Time - Indiana - Starke County Eastern Time - Indiana - Pulaski County Eastern Time - Indiana - Crawford County Eastern Time - Indiana - Switzerland County Central Time Central Time - Indiana - Perry County Central Time - Indiana - Pike County Central Time - Michigan - Dickinson, Gogebic, Iron & Menominee Counties Central Time - North Dakota - Oliver County Central Time - North Dakota - Morton County (except Mandan area) Mountain Time Mountain Time - south Idaho & east Oregon Mountain Time - Navajo Mountain Standard Time - Arizona Pacific Time Alaska Time Alaska Time - Alaska panhandle Alaska Time - Alaska panhandle neck Alaska Time - west Alaska Aleutian Islands Hawaii
west Uzbekistan east Uzbekistan
200
Code VN VU WF WS YE YT ZA ZM ZW
Time zone Asia/Saigon Pacific/Efate Pacific/Wallis Pacific/Apia Asia/Aden Indian/Mayotte Africa/Johannesburg Africa/Lusaka Africa/Harare
Comments
201
202
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.
203
204
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 user's 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
205
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 IBM's 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 AIX DS4000 Enterprise Storage Server ESCON FICON i5/OS iSeries IBM ProtecTIER pSeries S/390 ServeRAID System x System Storage TotalStorage Wake on LAN
v z/OS v 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
206
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 statement

This explains the Federal Communications Commission's (FCC) statement. This equipment has been tested and found to comply with the limits for a Class A digital 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 user's authority to operate the equipment.
Notices
207
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.
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 Electromagnetic Compatibility Directive

This product is in conformity with the protection requirements of European Union (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. Attention: This is an EN 55022 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. Responsible Manufacturer: International Business Machines Corp. New Orchard Road Armonk, New York 10504 914-499-1900 European community contact: IBM Technical Regulations, Department M456 IBM-Allee 1, 71137 Ehningen, Germany Tel: +49 7032 15-2937 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 compatibility 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
208
die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der 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 Einhaltung der EMV Vorschriften ist der Hersteller:
International Business Machines Corp. New Orchard Road Armonk,New York 10504 Tel: 914-499-1900
Der verantwortliche Ansprechpartner des Herstellers in der EU ist: IBM Deutschland Technical Regulations, Department M456 IBM-Allee 1, 71137 Ehningen, Germany Tel: +49 7032 15-2937 e-mail: tjahn@de.ibm.com Generelle Informationen: Das Gert erfllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A.
People's Republic of China Class A Electronic Emission statement
Notices
209
Taiwan Class A compliance statement
Taiwan contact information

This topic contains the product service contact information for Taiwan.
IBM Taiwan Product Service Contact Information: IBM Taiwan Corporation 3F, No 7, Song Ren Rd., Taipei Taiwan Tel: 0800-016-888
Japan VCCI Council Class A statement
Japan Electronics and Information Technology Industries Association (JEITA) Statement (less than or equal to 20 A per phase)
210
jjieta1
f2c00790
Korean Communications Commission (KCC) Class A Statement
Russia Electromagnetic Interference (EMI) Class A Statement
rusemi
Notices
211
212
Index A
about this document xxix sending comments xxxv accessibility 203 adding cartridges 75 cluster members 151 nodes 45 nodes to a subnetwork 46 physical volumes to volume groups 58 user accounts 143 administrator default password 41 role 143 alerts SNMP 16 alerts log 145 comments, sending xxxv completing ProtecTIER system setup 7 compression disabling 153 configuration cluster setup 2 one node system 2 two node system 2 Configuration file backups 176 configuring ProtecTIER server 7 configuring ProtecTIER 21, 25 Configuring the ProtecTIER server 7 creating file systems 49, 53 libraries 61 partitions 54 zones 61 creating file systems fsCreate 49 emulation tape library 1 enabling SNMP compatibility 15 SNMP support 16 error checking 159 repairing 160 error check fsck 157 overview 157 ProtecTIER Manager 159 running 159 error message wizards 146 error trap SNMP 16 errors recoverable errors 16 unrecoverable errors 16 ESM 181 establishing installation directory 167 events log 145 expanding file systems 53 logical volumes 58 repositories 51 expanding the repository 48
B
Backup Reserve space on a repository backup catalog 124 backup monitoring 105 60
D
danger notices xv data deduplication 1 deactivating logical volumes 57 deduplication 1 defragmentation disabling 152 Defragmentation control on a repository 59 deleting cartridges 76 libraries 78 repositories 59 user accounts 143 device reassigning 72 resetting 155 disabling compression 153 defragmentation 152 Disaster recovery operations 123 replace dual node by single 173 Disaster Recovery Entering DR mode 123 documentation improvement xxxv DR mode Entering DR mode 123 DS4700 firmware 181 dumping trace buffer 154
C
cartridge adding 75 deleting 76 managing 75 moving 156 read-only mode 77 read/write mode 77 switching modes 77 unloading 156 cartridge drive reassigning 72 Cartridge ownership takeover Principality 124 caution notices xv changing HyperFactor mode 153 worldwide names 151 Changing support system settings 41 checking errors 159 cluster cluster member monitoring, see cluster member 87 disk space monitoring 86 fibre channel port throughput monitoring 87 overview 45 VT service monitoring 87 cluster member adding 151 monitoring 87 removing 149 Copyright IBM Corp. 2008, 2009, 2010
F
Failback policy 127 creating 128 fields implemented SNMP 16 file system creating 49, 53 expanding 53 unmounting 57 volume name 158 firmware upgrades 181 fsck error check 157 running 158 fsCreate creating file systems 49 fsCreate parameters 50
G
generating long-term statistics reports 148 problem reports 147 Grid Adding a repository 109 Connecting a spoke to the hub 112 Defining the role of a repository 111 Disconnecting a spoke from the hub 114
E
editing libraries 68
213
Grid (continued) Forcing a repository to leave Removing a repository 110
111
H
Hub Connecting a spoke 112 Disconnecting a spoke 114 HyperFactor 1 HyperFactor mode changing 153 HyperFactor ratio over time graph
LUN Masking (continued) Adding host initiators Manually adding host initiators 79 Scanning host initiators 79 Disabling 78 Enabling 78 Library-related operations 84 Managing host initiators 79 Modifying host initiators 81 Working with groups 82
93
M
machine types xxix management tools SNMP 16 managing cartridges 75 clusters 45 nodes 45 repositories 47 user accounts 143 marginal HyperFactor ratio graph 93 message area 146 MIB definition file 16 MIB-2 SNMP 15 model numbers xxix modifying port attributes 148 trace buffer 154 monitor default password 41 role 143 monitoring backup operations 105 cartridges 99 backup properties 99 origin properties 100 replica properties 101 cluster disk space 86 cluster members 87 cluster VT service 87 drives 97 fibre channel port throughput 87 HyperFactor 93 imports/exports slots 103 library configuration 97 network configuration 95 nodes 94 port attributes 94 ProtecTIER 85 repositories 90 repository configuration 92 repository disk space 91 repository factoring ratio 92 repository HyperFactor 93 repository IOPS 92 repository nominal data size 91 repository storage 92 repository used space 91 robots 96 slots 102 systems 85 tape drives 96 VT service 96
monitoring (continued) VT service for clusters 87 VT service libraries 97 Monitoring ProtecTIER general tab 86 replication grid 121 replication policies and activities shelf 104 Monitoring ProtecTIER systems replication information 87 moving cartridges 156
88
I
implementing SNMP compatibility 16 installation directory, establishing 167 installing ProtecTIER Manager 37 Installing RAS package 166 Installing Red Hat Enterprise Linux 162 introduction 1 IP address Updating a repository 111
N
Native Replication network interface bandwidth limiting 117 replication rate limit setting 116 Navigation pane refreshing 43 node adding 45 adding to a subnetwork 46 changing worldwide names 151 general monitoring 94 network configuration monitoring 95 overview 45 port monitoring 94 port scanning 94 removing 46 scanning ports 94 updating ProtecTIER 26 version information 95 node configuration one node 2 two nodes 2 nominal data size graph 92 notices caution xv danger xv NVSRAM 181
K
keyboards accessibility features 203
L
library creating 61 deleting 78 editing 68 overview 61 renaming 78 Library library type setting 68 library type information 97 Limiting the network interface bandwidth 117 Linux shell backup monitoring 105 log alerts 145 events 145 log in as root 167 logging in 41 Logging in to the ProtecTIER server logging out 41 logical volume deactivating 57 expanding 58 reactivating 58 long-term statistics report generating 148 LUN Masking About LUN Masking 78
O
operating system installing Red Hat Enterprise Linux 162 operator default password 41 role 143 overview checking errors 157 ProtecTIER Manager 5 repository expansion 48 troubleshooting 145
P
partition creating 54 password default 41
214
permission levels default accounts 41 overview 143 physical volume adding to volume groups 58 planning repository expansion 48 Policy creating 118 disable 119 enable 119 modifying 120 running 119 port attributes, modifying 148 attributes, monitoring 94 Preferences ProtecTIER Manager changing support system settings 41 prerequisites ProtecTIER Manager 37 printing data 43 problem report generating 147 ProtecTIER configuring 21, 25 monitoring 85 package, unpacking 167 updating 26 upgrading 21, 25 upgrading clustered servers 30 ProtecTIER Manager installing 37 overview 5 Preferences changing support system settings 41 prerequisites 37 refreshing 43 running operation in the background 44 uninstalling 40 upgrading 37 ProtecTIER Replication Manager 176 backing up configuration files 176 installing 176 restoring 177 ProtecTIER server customizing 7 ProtecTIER servers preparing for v2.4.0.0 upgrade 21 ProtecTIER system setup completing 7 ProtecTIER v2.3.x.x applying 23 downloading from IBM Web site 23 installing 23
R
RAS installation 166 RAS package configuration, verification and validation 35 configuring 35
reactivating logical volumes 58 reader feedback, sending xxxv reassigning cartridge drives 72 devices 72 robots 72 reboot error 16 Recovering a server TS7650G 167 recovery cartridge status 124 recovery procedures 161 Red Hat Enterprise Linux installing Red Hat operating system 162 Red Hat Linux upgrading 21, 25 upgrading clustered servers 30 refreshing 43 reloading a node 161 removing cluster members 149 nodes 46 renaming libraries 78 repairing errors 160 Replace, dual node by single Disaster recovery 173 Replication about policies 114 creating a policy 118 disabling a policy 119 enabling a policy 119 modifying a policy 120 ProtecTIER Replication Manager 107 Replication Manager Working with 107 Replication policies tab 114 running a policy 119 timeframe setting 115 Replication activities monitoring 88 Replication grid monitoring 121 Replication information monitoring ProtecTIER systems 87 replication IPs updating 11 Replication policies monitoring 88 replication timeframe setting 115 Repositories Replication grid Working with repositories 109 Working with repositories in a replication grid 109 repository configuration monitoring 92 deleting 59 disk space monitoring 91 expanding 51 expansion overview 48 expansion planning 48
repository (continued) factoring ratio monitoring 92 general monitoring 90 HyperFactor monitoring 93 HyperFactor ratio over time graph 93 IOPS monitoring 92 managing 47 marginal HyperFactor ratio graph 93 nominal data size graph 92 nominal data size monitoring 91 planning an expansion 48 replacing a destroyed repository 127 storage monitoring 92 used space monitoring 91 utilization graph 93 Repository Adding a repository to a grid 109 Defining the role in a grid 111 Defragmentation control 59 Forcing a repository to leave a grid 111 Removing a repository from a grid 110 Reserve space for backup 60 Updating the IP address 111 resetting devices 155 robots 155 tape drives 155 trace buffer 155 restart error 16 restoring ProtecTIER Replication Manager 177 Restoring ProtecTIER Replication Manager Default backup tab 178 File tab 179 IP Address tab 179 robot monitoring 96 reassigning 72 resetting 155 RSA connection 185 running error checks 159 fsck 158 running operations in the background 44
S
saving data 43 sending comments xxxv setting trace buffer levels 154 Setting the replication rate limit 116 Shelf monitoring the shelf 104 SNMP alerts 16 compatibility, enabling 15 compatibility, implementing 16 error trap 16 fields implemented 16 Index
215
SNMP (continued) management tools 16 MIB-2 15 support, enabling 16 traps 16 warning notification trap 16 Spoke Connecting to a hub 112 Disconnecting from a hub 114 static routes routing, replication 9 subnetworks 46 switching modes cartridges 77 Syntax understanding diagrams 129 systems general monitoring 85
user account (continued) deleting 143 overview 143 username default 41 utilization graph 93
V
version information 95 View pane refreshing 43 Virtual Tape service, see VT service 1 volume group adding physical volumes 58 volume name of file systems 158 VT service 1 cartridge view 99 backup properties 99 origin properties 100 replica properties 101 clusters monitoring 87 drives monitoring 97 general monitoring 96 imports/exports slots monitoring 103 library configuration monitoring 97 library monitoring 97 library type information 97 overview 61 robot monitoring 96 slots monitoring 102 tape drive monitoring 96
T
tape drive monitoring 96 resetting 155 tape library 1 TCP/IP network 46 terminology xxix timeserver updating 12 trace buffer dumping 154 modifying 154 resetting 155 setting levels 154 Trademarks 206 traps SNMP 16 troubleshooting overview 145 tasks 152 TSSC network IP scheme 189
W
warning notification trap SNMP 16 Wizard error messages 146 Wizard message area 146 worldwide name changing 151
U
Understanding syntax diagrams 129 uninstalling ProtecTIER Manager 40 unloading cartridges 156 unmounting file systems 57 unpacking ProtecTIER package 167 updating nodes 26 ProtecTIER 26 updating replication IPs 11 upgrading ProtecTIER Manager 37 upgrading ProtecTIER 21, 25 clustered servers 30 upgrading Red Hat Linux 21, 25 clustered servers 30 user account adding 143
216
Printed in USA
GC53-1156-07

User Guide 2.4

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

User Guide 2.4

Загружено:

Авторское право:

Доступные форматы

IBM System Storage TS7600 with ProtecTIER

IBM System Storage TS7600 with ProtecTIER

Safety, danger, caution notices and labels . . . . . . . . . . . . . . . xv

Chapter 2. Completing the ProtecTIER system setup for new installations . . . 7

Chapter 3. Upgrading and Configuring Red Hat Linux and ProtecTIER . . . . 21

Chapter 4. Installing ProtecTIER Manager . . . . . . . . . . . . . . 37

Chapter 5. Getting started with ProtecTIER Manager . . . . . . . . . 41

About this document . . . . . . . . xxix

Copyright IBM Corp. 2008, 2009, 2010

Running operations in the background .

Chapter 6. Managing nodes and clusters . . . . . . . . . . . . . . 45

Chapter 7. Managing repositories . . . 47

Chapter 11. Disaster recovery (DR) mode operations . . . . . . . . . . 123

Chapter 8. Managing the ProtecTIER VT service. . . . . . . . . . . . . . . 61

Chapter 13. Managing users . . . . . 143

Chapter 14. Troubleshooting . . . . . 145 Chapter 9. Monitoring ProtecTIER . . . 85

Chapter 10. Native Replication Management . . . . . . . . . . . . 107

Chapter 15. ProtecTIER system recovery procedures . . . . . . . . 161

IBM System Storage TS7600 with ProtecTIER: User's Guide

. 173 . 176 . 176 . 177 177

Appendix B. RSA connection

210 211 211

IBM System Storage TS7600 with ProtecTIER: User's Guide

. 186 . 187 . 188

Copyright IBM Corp. 2008, 2009, 2010

IBM System Storage TS7600 with ProtecTIER: User's Guide

Copyright IBM Corp. 2008, 2009, 2010

IBM System Storage TS7600 with ProtecTIER: User's Guide

Safety and Environmental notices

Copyright IBM Corp. 2008, 2009, 2010

If the symbol is...

IBM System Storage TS7600 with ProtecTIER: User's Guide

Safety and Environmental notices

IBM System Storage TS7600 with ProtecTIER: User's Guide

Safety, danger, caution notices and labels

Copyright IBM Corp. 2008, 2009, 2010

IBM System Storage TS7600 with ProtecTIER: User's Guide

IBM System Storage TS7600 with ProtecTIER: User's Guide

>18 kg (39.7 lb)

18-32 kg (39.7-70.5 lb)

Safety, danger, caution notices and labels

IBM System Storage TS7600 with ProtecTIER: User's Guide

Safety, danger, caution notices and labels

IBM System Storage TS7600 with ProtecTIER: User's Guide

Safety, danger, caution notices and labels

IBM System Storage TS7600 with ProtecTIER: User's Guide

Safety, danger, caution notices and labels

IBM System Storage TS7600 with ProtecTIER: User's Guide

Safety, danger, caution notices and labels

IBM System Storage TS7600 with ProtecTIER: User's Guide

About this document

Copyright IBM Corp. 2008, 2009, 2010

IBM System Storage TS7600 with ProtecTIER: User's Guide

Who should read this document

What's new in this edition

Getting information, help, and service

Help and service

IBM System Storage TS7600 with ProtecTIER: User's Guide

Related IBM publications

IBM System Storage TS7600 with ProtecTIER publications

v Statement of Limited Warranty

TS7650 (3958 AP1) publications

TS7650G Server (x3958 DD1/DD3) publications