Professional Documents
Culture Documents
Users Guide
for Enterprise Edition and Appliance Edition
GC53-1156-03
Users Guide
for Enterprise Edition and Appliance Edition
GC53-1156-03
Note:
Before using this information and the product it supports, be sure to read the information in the Safety and environmental notices and Notices sections of this publication.
Edition notices This edition applies to IBM System Storage TS7600 with ProtecTIER for Enterprise Edition and Appliance Edition [ProtecTIER v2.3] and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces GC53-1156-02 Copyright International Business Machines Corporation 2008, 2009. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . v Tables . . . . . . . . . . . . . . . vii Safety and Environmental notices . . . ix
Safety notices . . . . . . . . . . . . . . ix Environmental notices . . . . . . . . . . . x
Chapter 1. Introduction . . . . . . . . 1
HyperFactor . . . . . . ProtecTIER Virtual Tape (VT) . Configuration . . . . . . ProtecTIER Manager . . . . Native Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 2 6 6
iii
Viewing the alerts and events log windows Wizard error messages . . . . . . . Generating a problem report . . . . . Creating a long-term statistics report . . Turning on the WTI power switch outlets . Modifying port attributes . . . . . . Removing and adding cluster members . Changing World Wide Names for a node . Common troubleshooting tasks . . . . Checking and repairing errors . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
117 118 119 119 119 120 121 123 124 128
Adding file systems to fstab and mounting file systems . . . . . . . . . . . . . . Expanding file systems . . . . . . . . . . Creating a partition . . . . . . . . . . Unmounting a file system . . . . . . . . Deactivating the logical volume . . . . . . Creating a physical volume. . . . . . . . Adding the physical volume to a volume group Expanding the logical volume . . . . . . . Reactivating the logical volume . . . . . . Mounting the file system . . . . . . . . Expanding the GFS file system . . . . . .
164 164 165 165 165 165 165 166 166 166 166
. . . . 167
. . . . 170
139
. 139 . 139 . 146 . 146 . 149 . . . . . 152 154 156 157 157
Index . . . . . . . . . . . . . . . 181
iv
Figures
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. Tape library emulation . . . . . . . One node system . . . . . . . . . Two node system . . . . . . . . . Cluster setup . . . . . . . . . . Starting cluster response . . . . . . Updating cluster response. . . . . . ProtecTIER Manager . . . . . . . Repository meta data storage requirements dialog . . . . . . . . . . . . Repository resources dialog . . . . . View of replication policy . . . . . . Set replication time frame . . . . . . Library type screen . . . . . . . . Tape model screen . . . . . . . . Tape drives screen . . . . . . . . Port assignment screen . . . . . . . Assignment (2) screen . . . . . . . Cartridges screen. . . . . . . . . Slots screen . . . . . . . . . . Set library type dialog . . . . . . . Tape drives screen . . . . . . . . Assignment screen . . . . . . . . Assignment (2) screen . . . . . . . Slots screen . . . . . . . . . . Tape drives screen . . . . . . . . Assignment screen . . . . . . . . Assignment (2) screen . . . . . . . Summary report screen . . . . . . Cartridges screen. . . . . . . . . Cartridges screen. . . . . . . . . Create replication pair . . . . . . . Delete replication pair . . . . . . . View of grid member details via Grids Management mode . . . . . . . . Systems monitoring screen . . . . . Storage resources dialog . . . . . . VT tab . . . . . . . . . . . . Repository monitoring screen . . . . Nominal data size graph . . . . . . Utilization graph . . . . . . . . . Marginal HyperFactor graph . . . . . HyperFactor ratio over time graph . . . Replication policies tab. . . . . . . Replication activities view. . . . . . General tab . . . . . . . . . . Drives tab . . . . . . . . . . . Cartridges tab. . . . . . . . . . Slots tab . . . . . . . . . . . Imports/Exports tab . . . . . . . Shelf view . . . . . . . . . . . ptmon on success response output . . . ptmon on error output . . . . . . . ptmon -repository output . . . . . . ptmon -libs output . . . . . . . . ptmon -libinfo -libid <library id> output ptmon -ncarts -libid <library id> output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 . 3 . 4 . 5 . 15 . 18 . 33 . . . . . . . . . . . . . . . . . . . . . . . . 38 42 44 45 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 69 73 74 55. ptmon -cartsinfo -libid <library id> -from <first cartridge index> -count <number of cartridges> outputf . . . . . . . . ptmon -node_vtl_statistics -hours <hours> output . . . . . . . . . . . . . ptmon -version output . . . . . . . Failed Response for Calling to DriveModels without --libtype . . . . . . . . . Failed Response for Calling to DriveModels without --libtype . . . . . . . . . Successful Response for Configuration Operations . . . . . . . . . . . Successful Response for RepositoryStatistics Successful Response for Libraries . . . . Successful Response for LibraryInfo without Active Drive . . . . . . . . . . . Successful Response for LibraryInfo with Active Drives . . . . . . . . . . Successful Response for NumberofCartridges Successful Response for CartridgeInfo Successful Response for NodeVtlStatistics Successful Response for ServerVersion Successful Response for LibraryTypes Successful Response for DriveModels Successful Response for RaidConfigurations Users Management dialog . . . . . . Add account dialog . . . . . . . . Alerts log . . . . . . . . . . . . Message area. . . . . . . . . . . Port Details screen . . . . . . . . . Node Selection screen. . . . . . . . Node Selection screen. . . . . . . . ProtecTIER VT HyperFactor mode dialog Set trace levels dialog . . . . . . . . Move cartridge dialog . . . . . . . Check and recover dialog . . . . . . Cartridge validation results . . . . . . Repository takeover . . . . . . . . Cartridge status report (in Excel) . . . . Press F12 to select the boot device . . . Select CD as the boot device . . . . . Red Hat Enterprise Linux 5 screen . . . Verify attached disks . . . . . . . . Review end user license agreement . . . End User License Agreement . . . . . Accept the license agreement . . . . . Grid analysis. . . . . . . . . . . Previewing the grid layout . . . . . . Laptop or PC to RSA connection . . . . Local Area Connection Properties . . . . Local Area Connection Properties: Internet Protocol (TCP/IP) . . . . . . . . . Remote Supervisor Adapter II Refresh 1 Welcome window . . . . . . . . . Remote Supervisor Adapter II Refresh 1 window: Remote Control link . . . . . . 101 . 102 . 102 . 106 . 106 . 106 107 . 107 . 107 . 108 108 109 110 110 110 110 111 . 114 . 114 . 117 . 118 . 120 . 122 . 123 125 . 126 . 128 . 130 . 135 . 136 . 138 . 141 . 142 . 143 . 144 . 144 . 145 . 145 . 158 . 160 . 167 . 168 . 168 . 169 . 170
56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. 81. 82. 83. 84. 85. 86. 87. 88. 89. 90. 91. 92. 93. 94. 95. 96. 97. 98. 99.
. 75 . 77 . 78 . 80 . 81 . 82 . 82 . 83 . 83 . 84 . 85 . 88 . 90 . 91 . 92 . 93 . 94 . 98 . 98 . 99 . 99 100 100
vi
Tables
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. IBM Web sites for help, services, and information . . . . . . . . . . . . xiii Default usernames and passwords . . . . . 31 fsCreate parameters . . . . . . . . . . 40 Cluster member information . . . . . . . 79 Total utilization information . . . . . . . 81 Repository information. . . . . . . . . 82 Port attribute information . . . . . . . . 86 Network interface card information . . . . 87 Virtual robots and tape drive. . . . . . . 88 Drives tab information . . . . . . . . . 90 Cartridges tab information . . . . . . . 91 Slots tab information . . . . . . . . . 92 13. 14. 15. 16. 17. 18. 19. 20. 21. Imports/Exports tab information . . . . . 93 Recent backup session statistics . . . . . . 95 Repository command statistics . . . . . . 98 Statistics on the configured tape drives of a specific library . . . . . . . . . . . 99 Statistics on the number of configured cartridges of a specific library . . . . . . 100 Statistics of the cartridges in a specified range 100 Statistics history on the local host for the last hours . . . . . . . . . . . . . . 101 Grid analysis messages . . . . . . . . 159 TSSC IP address ranges . . . . . . . . 171
vii
viii
Safety notices
Observe the safety notices when using this product. These safety notices contain danger and caution notices. These notices are sometimes accompanied by symbols that represent the severity of the safety condition. Most danger or caution notices contain a reference number (Dxxx or Cxxx). Use the reference number to check the translation in the IBM Systems Safety Notices, G2299054 manual. The sections that follow define each type of safety notice and give examples.
Danger notice
A danger notice calls attention to a situation that is potentially lethal or extremely hazardous to people. A lightning bolt symbol always accompanies a danger notice to represent a dangerous electrical condition. A sample danger notice follows:
DANGER: An electrical outlet that is not correctly wired could place hazardous voltage on metal parts of the system or the devices that attach to the system. It is the responsibility of the customer to ensure that the outlet is correctly wired and grounded to prevent an electrical shock. (D004)
Caution notice
A caution notice calls attention to a situation that is potentially hazardous to people because of some existing condition, or to a potentially dangerous situation that might develop because of some unsafe practice. A caution notice can be accompanied by one of several symbols:
If the symbol is... It means... A generally hazardous condition not represented by other safety symbols.
This product contains a Class II laser. Do not stare into the beam. (C029) Laser symbols are always accompanied by the classification of the laser as defined by the U. S. Department of Health and Human Services (for example, Class I, Class II, and so forth). A hazardous condition due to mechanical movement in or around the product.
ix
It means... This part or unit is heavy but has a weight smaller than 18 kg (39.7 lb). Use care when lifting, removing, or installing this part or unit. (C008)
Sample caution notices follow: Caution The battery is a lithium ion battery. To avoid possible explosion, do not burn. Exchange only with the IBM-approved part. Recycle or discard the battery as instructed by local regulations. In the United States, IBM has a process for the collection of this battery. For information, call 1-800-426-4333. Have the IBM part number for the battery unit available when you call. (C007) Caution The system contains circuit cards, assemblies, or both that contain lead solder. To avoid the release of lead (Pb) into the environment, do not burn. Discard the circuit card as instructed by local regulations. (C014) Caution When removing the Modular Refrigeration Unit (MRU), immediately remove any oil residue from the MRU support shelf, floor, and any other area to prevent injuries because of slips or falls. Do not use refrigerant lines or connectors to lift, move, or remove the MRU. Use handholds as instructed by service procedures. (C016) Caution Do not connect an IBM control unit directly to a public optical network. The customer must use an additional connectivity device between an IBM control unit optical adapter (that is, fibre, ESCON, FICON) and an external public network . Use a device such as a patch panel, a router, or a switch. You do not need an additional connectivity device for optical fibre connectivity that does not pass through a public network.
Environmental notices
The environmental notices that apply to this product are provided in the Environmental Notices and User Guide, Z125-5823-xx manual. A copy of this manual is located on the publications CD.
Terminology
IBM offers two virtualization solutions: TS7650 When used alone, this term signifies IBMs family of virtualization solutions that operate on the ProtecTIER platform. TS7650 Appliance or appliance These are terms for IBMs self-contained virtualization solution from the TS7650 family that includes a disk storage repository. The TS7650 Appliance consists of the following: Server The 3958 AP1 server is based on an IBM System x3850 M2 Type 7233. When used as a server in the TS7650 Appliance, its machine type and model are 3958 AP1. Use this machine type and model for service purposes. System console The system console is a TS3000 System Console (TSSC). This document uses the terms system console and TSSC interchangeably. Disk controller The disk controller is an IBM System Storage DS4700 Express. When used as a disk controller in the TS7650 Appliance, its machine type and model are 1814 70H. Use this machine type and model for service purposes. Disk expansion module The disk expansion module is an IBM System Storage DS4000 EXP810 Storage Expansion Unit. When used as a disk expansion module in the TS7650 Appliance, its machine type and model are 1812 81H. Use this machine type and model for service purposes. TS7650G or Gateway These are terms for IBMs virtualization solution from the TS7650 family that does not include a disk storage repository, allowing the customer to choose from a variety of storage options. The TS7650G consists of the following: Server There are two types of server used in the gateway: 3958 DD3 This is a newer, higher performance server available in March 2009. This server is based on the IBM System x3850 M2 Type 7233. When used as a server in the TS7650G, its machine type and model are 3958 DD3. Use this machine type and model for service purposes. 3958 DD1 This is the original server available in August 2008. This server is based on the IBM System x3850 M2 Type 7141.
Copyright IBM Corp. 2008, 2009
xi
When used as a server in the TS7650G, its machine type and model are 3958 DD1. Use this machine type and model for service purposes. System console The system console is a TS3000 System Console (TSSC). This document uses the terms system console and TSSC interchangeably. Under IBM best practices, the TS7650G also contains the following: Disk controller The IBM disk controller is an IBM System Storage DS4700 Express. When used as a disk controller in the TS7650G, its machine type and model are 1814 70H. Use this machine type and model for service purposes. Disk expansion module The IBM disk expansion module is an IBM System Storage DS4000 EXP810 Storage Expansion Unit. When used as a disk expansion module in the TS7650G, its machine type and model are 1812 81H. Use this machine type and model for service purposes. replication A process that transfers logical objects like cartridges from one ProtecTIER repository to another. The replication function allows ProtecTIER deployment to be distributed across sites. Each site has a single or clustered ProtecTIER environment. Each ProtecTIER environment has at least one ProtecTIER server. The ProtecTIER server that is a part of the replication grid has two dedicated replication ports, Eth3 and Eth4 are use for replication. Replication ports are connected to the customers WAN and are configured on two subnets as default. replication grid A set of repositories that share a common ID and can potentially transmit and receive logical objects through replication. A replication grid defines a set of ProtecTIER repositories and actions between them and is configured using the Grid Manager. The Grid Manager is a software component that is installed on a ProtecTIER server or a dedicated host. The Grid Manager should be able to recognize all the members of the entire network the Grid Manager handles on both replication subnets. The Grid Manager is deployed separately from the ProtecTIER Manager on the customers ProtecTIER server. The Grid Manager manages the configuration of multiple replication grids in an organization. An agent on every node in each ProtecTIER server interacts with the server and maintains a table of its grid members. replication grid ID A number from 0 to 63 that identifies a replication grid within an organization. replication grid member A repository that is a member in a replication grid. replication pairs Two repositories within a replication grid that replicate from one to another. replication policy A policy made up of rules that define a set of objects (e.g. VTL cartridges) from a source repository to be replicated to a target repository.
xii
repository unique ID (RID) A number that uniquely identifies the repository. The RID is created from the replication grid ID and the repository internal ID in the grid. replication timeframe A scheduled period of time for replication to take place for all policies. shelf A container of VTL (virtual tape library) cartridges within a ProtecTIER repository.
visibility switching The automated process that transfers the visibility of a VTL cartridge from its master to its replica and vice versa. The visibility switching process is triggered by moving a cartridge to the source library Import/Export (I/E) slot. The cartridge will then disappear from the I/E slot and appear at the destination librarys I/E slot. To move the cartridge back to the source library, the cartridge must be ejected to the shelf from the destination library. The cartridge will then disappear from the destination library and reappear at the source I/E slot.
Information
IBM maintains pages on the World Wide Web where you can get information about IBM products and services and find the latest technical information. For more information refer to Table 1.
Table 1. IBM Web sites for help, services, and information Description IBM home page Directory of worldwide contacts Web address (URL) www.ibm.com http://www.ibm.com/planetwide
xiii
Table 1. IBM Web sites for help, services, and information (continued) Description Support for IBM System Storage and TotalStorage products Web address (URL) http://www.ibm.com/storage/support Note: Go to this site for information about the TS7650 and do the following: 1. Select Tape systems from the Product family list 2. Select TS7650 with ProtecTIER from the Product list
Web sites
The most up-to-date information about your product, including documentation and the most recent downloads, can be found at the following Web sites: v The translated publications for this product are included with the product. These documents and product specification sheets are also available from the following Web site: www.ibm.com/storage/support/ v You can order publications through the IBM Publications Ordering System at the following Web site:
xiv
www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss/ v Access installation and technical support information via the Web at: www.ibm.com/support v The IBM Web site for Independent Software Vendor (ISV) support is: www.ibm.com/servers/storage/tape/resource-library.html v The IBM System Storage TS7600 Interoperability Matrix Web site can be found at: www.ibm.com/storage/support/ v For the latest information about SAN switches and directors, go to the following Web site: www.ibm.com/servers/storage/san v For the latest information about IBM xSeries products, services, and support, go to the following Web site: www.ibm.com/eserver/xseries v For the latest information about operating system and HBA support, clustering support, SAN fabric support, and Storage Manager feature support, see the DS4000 Interoperability Matrix at the following Web site: www.ibm.com/servers/storage/disk/ds4000/interop-matrix.html v For product firmware and software downloads, as well as associated driver code, go to the following Web site: www.ibm.com/storage/support/ v For accessibility information, go to the following Web site: www.ibm.com/able/product_accessibility/index.html v For the latest information about product recycling programs, go to the following Web site: www.ibm.com/ibm/environment/products/prp.shtml
xv
v IBM System x3850 M2 (Type 7233), System x3950 M2 (Type 7233) Problem Determination and Service Guide, IBM part number 44R5214
8. On the Support for System x3850 page, click the link for the document you want to view.
xvi
Chapter 1. Introduction
ProtecTIER is a disk-based data storage system. It uses data de-duplication technology to store data to disk arrays. The ProtecTIER VT service emulates traditional automated tape libraries. Before you begin using ProtecTIER and following the procedures described in this document, be sure you have completed the planning, preparation, and installation tasks described in the IBM System Storage TS7600 with ProtecTIER Introduction and Planning Guide, IBM publication number: GC53-1153, and installed IBM ProtecTIER Manager.
HyperFactor
ProtecTIER is the first virtual tape product to contain patented data factoring technology that IBM calls HyperFactor. This technology detects recurring data in multiple backups. The common data is merged into a single instance store, saving disk space needed to store multiple backups without sacrificing performance or the availability of backups for restore. HyperFactor is a breakthrough on several fronts: v Scales up to 1024 TB v The algorithm used to find the common data between backups does not affect the backup performance of the virtual tape engine v Data integrity is not compromised, not even statistically v Merged data is stored in a format that preserves restore performance HyperFactor saves space by taking advantage of the fact that only a very small percentage of data actually changes from backup to backup. Incremental backups include all files whose modification dates have changed since the last full or incremental backup; and full backups backup all data, changed or not. The amount of space saved is a function of many factors, but mostly of the backup policies and retention periods and the variance of the data between them. The more full backups retained on ProtecTIER, and the more intervening incremental backups, the more space that will be saved overall.
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:
A two node system uses two servers in an active-active cluster and enables you to build a more sophisticated system, as illustrated in the following figure:
Chapter 1. Introduction
Using a two node system provides the following benefits: v Higher-Availability clustered configuration available to provide hardware redundancy in the event of a node failure. v Increased Performance provided that there are sufficient disk resources, the two servers can share the backup load and increase ProtecTIERs performance.
The following diagram illustrates the details of the ProtecTIER cluster setup:
Each node connects through front-end fibre channel ports to the backup server, and through back-end fibre channel ports to disk arrays. The network interface cards enable the nodes to connect to each other and to the ProtecTIER Manager workstation. Eth0 connects to the ProtecTIER Manager workstation. Eth1 and Eth2 are used for the Cluster Internal Network.
Chapter 1. Introduction
ProtecTIER Manager
The ProtecTIER Manager application can be installed on one or more workstations, enabling you to monitor the status of nodes and clusters in your ProtecTIER system, along with the accompanying repositories and services. ProtecTIER Manager is used to initially configure your ProtecTIER system, and can be used to change the configuration of the system.
Native Replication
Native Replication lets you replicate between repositories connected to a WAN network using TCP/IP protocol. Replication enables you to set rules (depending on your required replication needs) for replicating data objects across ProtecTIER repositories. The ProtecTIER repositories can be different in size, as well as physical layout. And since ProtecTIER deduplicates data before storing it, only the changes of the data are transferred to the remote site. These rules for replicating data objects are defined in replication policies on a repository. A replication grid is a logical set of repositories that can replicate from one to another. The Grid Manager is a server that remotely manages the grids configuration (for example, grid creation/deletion, repository membership in the grid, etc.). In most cases, the Grid Manager will reside on one of the ProtecTIER nodes.
Prerequisites
Before executing ptconfig, verify that the following tasks have been completed: v Cabling and physical connections (including those to the customers local area network (LAN) using assigned IP addresses) are complete. v You have collected the following server information: External IP address External, fully-qualified, host name (hostname.domain.com) External gateway address External network subnet mask Note: The cluster name and host name are case-sensitive. Be aware of the use of upper- and lower-case characters when gathering the information and when entering it into the system.
If you have a code-level update package, execute the ptconfig that is resident on the server first, then apply the update from the CD. Perform the steps below on the single server in a standalone configuration, or on Server A and Server B in a clustered configuration. To configure the server: 1. At the servers command prompt, change to the /opt/dtc/install directory. To do so, enter the following command: cd /opt/dtc/install <enter> 2. Change the servers IP address, netmask, default gateway, and host name from the values that were set in manufacturing, to the values specific to the customers environment. To do so: a. Enter the following command: ./ptconfig -updateNetwork <enter> The following status messages display:
Starting Cluster, please wait Starting cluster [ Done ] Cluster Started
b. If asked if you would like to stop the vtfd service, type: yes <Enter>. The following status message displays as the system initiates shutdown:
Stopping VTFD [/] The shutdown process may take a few minutes to complete.
c. You are then prompted, one at a time, to enter the values listed below. At each prompt, type the new value and then press <Enter>: v v v v Customer Network IP address Customer Network netmask Customer Network default gateway Customer Network hostname (This is the servers fully-qualified hostname. For example: hostname.domain.com)
Note: The values that were assigned to the server during manufacturing appear in brackets after each prompt. For example: Customer Network netmask:
[255.255.255.0]
After you enter the hostname, the system automatically starts the network configuration process. The following status messages display:
Configuring network [ Done ] Updated network configuration successfully update updateNetwork ended successfully
The system automatically restarts the vtfd service, and you are returned to the command prompt. 3. Change the system name from the one assigned during manufacturing to one specific to the customers environment. In a clustered configuration, this command only needs to be run from one of the nodes as it affects the shared name of the system. To do so: a. Enter the following command:
./ptconfig -updateSystemName <Enter>
b. When prompted, type the new system name of the server and press <Enter>. Note: The system name that was assigned to the server in manufacturing appears in brackets after the prompt. For example: [PORTLAND]. After you enter the system name, the system automatically starts the Update System Name process. The following status message displays:
Change system name [ Done ] Updated system name successfully update updateSystemName ended successfully
You are returned to the command prompt. 4. If you are in a standalone configuration, go on to Chapter 3, Installing ProtecTIER Manager, on page 27. 5. If you are in a clustered configuration, repeat the steps in this section on Server B, then go on to Chapter 3, Installing ProtecTIER Manager, on page 27. Creating the repository on the node results in a functional one-node ProtecTIER cluster system. If you are using a one-node system, create a library on the one node. (For more information, see Creating libraries on page 50.) If you are using a two-node system, upgrade the system to a two-node cluster. Then create one or more libraries on the nodes of the two-node cluster.
mkdir /mnt/cdrom
<Enter>
Note: If the /mnt/cdrom directory already exists, the following message will be displayed:
mkdir: cannot create directory '/mnt/cdrom': File exists
If this message appears, ignore it and proceed to the next step. c. Mount the CD-ROM drive:
mount /dev/cdrom /mnt/cdrom <Enter>
The following output is displayed: mount: block device /dev/cdrom is write-protected. mounting read-only d. Type the following command to change the current directory to the local installation directory:
cd /mnt/cdrom
e. From the CD, locate the following tar file, where <filename> indicates the version number and date: v List the files on the CD from the command line: ls <Enter> v Locate the .tar file and copy it to the /install directory on the hard drive. Type the following command to copy the file:
cp <filename>.tar /install <Enter>
f. Access the directory to which you copied the tar file (for example, type cd /install). g. Type the following command to extract the installation files in the /install directory:
tar -xvf <tar filename>.tar <Enter>
The <filename> directory is created. h. Type the following command to change to the <tar filename> directory. Perform the rest of the installation from this directory:
cd /install/<filename> <Enter>
Example: <filename>=PT_Linux_V2.3.0.0.x86_64 i. Type the following command to unmount the CD-ROM drive:
umount /dev/cdrom <Enter>
j. Type the following command to eject the ProtecTIER installation CD from the CD-ROM drive:
eject /dev/cdrom
l. Enter y if you are prompted to stop the vtfd service. m. The autorun utility will install the ProtecTIER application. The following message is displayed at the end of the installation:
The system will now reboot!\
Note: After the reboot, the vtfd will be ready only after the service vtfd status command reports that vtfd is running, not that the service is not finished running yet. Press <Enter> at the prompt to reboot the system. The following message is displayed:
After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue...
10
d. If the vtfd does not report as stopped, enter the following command to stop the process:
service vtfd stop <Enter>
The process will discontinue and return you to a command prompt. e. Connect or verify a USB keyboard and display are connected to Server A (the first server). f. When the localhost login: prompt appears, login as root and type the password: admin. 2. Mount and copy the code to the installation directory, using the following steps: a. Insert the IBM System Storage ProtecTIER Enterprise Edition V2.3 CD and wait for the CD to stop blinking. b. Create the /mnt/cdrom directory by typing the following command:
mkdir /mnt/cdrom <Enter>
Note: If the /mnt/cdrom directory already exists, the following message will be displayed:
mkdir: cannot create directory '/mnt/cdrom': File exists
If this message appears, ignore it and proceed to the next step. c. Mount the CD-ROM drive:
mount /dev/cdrom /mnt/cdrom <Enter>
d. Type the following command to change the current directory to the local installation directory:
cd /mnt/cdrom
e. From the CD, locate the following tar file, where <filename> indicates the version number and date:
Chapter 2. Setting up ProtecTIER
11
v List the files on the CD from the command line: ls <Enter> v Locate the .tar file and copy it to the /install directory on the hard drive. Type the following command to copy the file:
cp <filename>.tar /install <Enter>
f. Access the directory to which you copied the tar file (for example, type cd /install). g. Type the following command to extract the installation files in the /install directory:
tar -xvf <tar filename>.tar <Enter>
The <filename> directory is created. h. Type the following command to change to the < tar filename> directory. Perform the rest of the installation from this directory:
cd /install/<filename> <Enter>
Example: <filename>=PT_Linux_V2.3.0.0.x86_64 i. Type the following command to unmount the CD-ROM drive:
umount /dev/cdrom <Enter>
j. Type the following command to eject the ProtecTIER installation CD from the CD-ROM drive:
eject /dev/cdrom
l. Enter y if you are prompted to stop the vtfd service. m. The autorun utility will install the ProtecTIER application. The following message is displayed at the end of the installation:
The system will now reboot!\
Note: After the reboot, the vtfd will be ready only after the service vtfd status command reports that vtfd is running, not that the service is not finished running yet. Press <Enter> at the prompt to reboot the system. The following message is displayed:
After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue...
d. Connect or verify a USB keyboard and display are connected to Server B (the second server). e. When the localhost login: prompt appears, login as root and type the password: admin. 2. Mount and copy the code to the installation directory, using the following steps:
12
a. Insert the IBM System Storage ProtecTIER Enterprise Edition V2.3 CD and wait for the CD to stop blinking. b. Create the /mnt/cdrom directory by typing the following command:
mkdir /mnt/cdrom <Enter>
Note: If the /mnt/cdrom directory already exists, the following message will be displayed:
mkdir: cannot create directory '/mnt/cdrom': File exists
If this message appears, ignore it and proceed to the next step. c. Mount the CD-ROM drive:
mount /dev/cdrom /mnt/cdrom <Enter>
d. Type the following command to change the current directory to the local installation directory:
cd /mnt/cdrom
e. From the CD, locate the following tar file, where <filename> indicates the version number and date: v List the files on the CD from the command line: ls <Enter> v Locate the .tar file and copy it to the /install directory on the hard drive. Type the following command to copy the file:
cp <filename>.tar /install <Enter>
f. Access the directory to which you copied the tar file (for example, type cd /install). g. Type the following command to extract the installation files in the /install directory:
tar -xvf <tar filename>.tar <Enter>
The <filename> directory is created. h. Type the following command to change to the < tar filename> directory. Perform the rest of the installation from this directory:
cd /install/<filename> <Enter>
Example: <filename>=PT_Linux_V2.3.0.0.x86_64 i. Type the following command to unmount the CD-ROM drive:
umount /dev/cdrom <Enter>
j. Type the following command to eject the ProtecTIER installation CD from the CD-ROM drive:
eject /dev/cdrom
Attention: Run the autorun command only after the service on Server A has completed its startup (after the reboot). k. Type the following command:
./autorun <Enter>
l. Enter y if you are prompted to stop the vtfd service m. The autorun utility will install the ProtecTIER application. The following message is displayed at the end of the installation:
The system will now reboot!\
Press <Enter> at the prompt to reboot the system. The following message is displayed:
Chapter 2. Setting up ProtecTIER
13
After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue... <Enter>
5. Run the following command to change the Ethernet port assignments of the server. You should see eth3 and eth4 identified as the Ethernet ports to be used for replication:
./ptconfig -addReplication <enter>
6. At the prompt, type yes <enter> to continue. 7. When prompted, enter the IP address, netmask, and hostname for the first replication port. 8. When prompted, enter the IP address, netmask, and hostname for the second replication port. The vtfd service is restarted and the procedure ends. 9. If you are working with a two-node cluster , repeat the entire procedure on the second node.
14
Example
[root@kovna install]# ./ptconfig -addReplication Starting Cluster, please wait Starting cluster [ Done ] Cluster Started Would you like to stop the VTFD service on both nodes? (yes|no) yes Stopping VTFD locally [ Done ] Stopping VTFD remotely [ Done ] Checking configuration [ Done ] ---------------------------------------Found the following available Network Interface(s): eth3 eth4 These Interface(s) are going to be configured for Replication Do you wish to continue? (yes|no) yes Modifying configuration Verifying configuration Please provide the following information: ----------------------------------------Replication Port 1, IP Address: 192.168.170.2 Replication Port 1, Netmask: 255.255.255.0 Replication Port 1, Hostname: replicationNode2_1 Replication Port 2, IP Address: 192.168.171.2 Replication Port 2, Netmask: 255.255.255.0 Replication Port 2, Hostname: replicationNode2_2 Configuring Replication Port 1 Configuring Replication Port 2 Saving configuration Starting VTFD locally Starting VTFD remotely AddReplication ended successfully [ Done ] [ Done ]
15
1. At the command prompt, enter the command: ./ptconfig -staticRoutes <enter> The message below displays: Gathering System information [ Done ] The auto-detected system information displays. For example:
ID 1 2 Target Network Address 10.11.194.0 10.11.196.0 Target Netmask 255.255.255.0 255.255.255.0 Local Gateway Address 168.159.151.111 168.159.151.110
Followed by the Available Options prompt: Available Options: ================== (a)dd a new record (e)dit a record (d)elete a record (c)ommit changes (q)uit Please Choose (a,e,d,c,q): 2. Type: a <enter> You are prompted to enter information for the first destination (target) server and the local network. 3. At each prompt, type the requested information and then press <enter>: Please provide the following information: Target Network Address: (for example: 10.11.194.0) Target Network Netmask: (for example: 255.255.255.0) Local Gateway Address: (for example: 10.11.195.1) A summary displays:
ID 1 Target Network Address 10.11.194.0 Target Netmask 255.255.255.0 Local Gateway Address 10.11.195.1
Note: The addresses in the summary above are examples. Actual values will vary. The Available Options prompt displays a second time: Available Options: ================== (a)dd a new record (e)dit a record (d)elete a record (c)ommit changes (q)uit Please Choose (a,e,d,c,q): 4. Type: a <enter>
16
You are prompted for the information for the second destination (target) server and the local network. 5. At each prompt, type the requested information and then press <enter>: Please provide the following information: Target Network Address: (for example: 10.11.196.0) Target Network Netmask: (for example: 255.255.255.0) Local Gateway Address: (for example: 10.11.197.1) An updated summary displays:
ID 1 2 Target Network Address 10.11.194.0 10.11.196.0 Target Netmask 255.255.255.0 255.255.255.0 Local Gateway Address 10.11.195.1 10.11.197.1
Note: The addresses in the summary above are examples. Actual values will vary. For reference, write actual values from the summary screen in the blank spaces below:
ID 1 2 Target Network Address Target Netmask Local Gateway Address
The Available Options prompt displays a third time: Available Options: ================== (a)dd a new record (e)dit a record (d)elete a record (c)ommit changes (q)uit Please Choose (a,e,d,c,q): 6. Type: q <enter> The message below displays: Would you like to commit the changes performed to the routing table now? (yes|no) 7. Type: yes <enter> The Successfully committed changes! message displays, and you are returned to the command prompt.
17
Before updating the replication IPs, check to see if the static routing needs to be updated as well. To update replication IPs on a node: 1. If the server is not already powered on, power it on on both nodes and stop the vtfd service on both nodes. 2. Connect or verify a USB keyboard and display are connected to the server. 3. When the localhost login: prompt appears, login as root and type the password: admin. 4. Set the user to ptadmin by typing the command su - ptadmin (the default password is ptadmin). 5. Change the directories to the /opt/dtc/install directory. From the command line, run the following command:
cd /opt/dtc/install
6. Run the following command to change the Ethernet port assignments of the DD1:
./ptconfig -updateReplicationIp <enter>
7. At the prompt, type yes <enter> to continue. 8. When prompted, enter the IP address, netmask, and hostname for the first replication port. 9. When prompted, enter the IP address, netmask, and hostname for the second replication port. The vtfd service is restarted and the procedure ends.
Example
[root@kovna install]# ./ptconfig -updateReplicationIp Starting Cluster, please wait Starting cluster [ Done ] Cluster Started Would you like to stop the VTFD service on both nodes? (yes|no) yes Stopping VTFD locally Stopping VTFD remotely [ Done ] [ Done ]
Verifying configuration [ Done ] Please provide the following information: ----------------------------------------Replication Port 1, IP Address [192.168.170.2]: 10.0.13.56 Replication Port 1, Netmask [255.255.255.0]: 255.255.255.192 Replication Port 1, Hostname [replicationNode2_1]: Replication Port 2, IP Address [192.168.171.2]: 10.1.14.1 Replication Port 2, Netmask [255.255.255.0]: 255.255.255.224 Replication Port 2, Hostname [replicationNode2_2]: Configuring Replication Port 1 [ Done ] Configuring Replication Port 2 Saving configuration Starting VTFD locally Starting VTFD remotely UpdateReplicationIp ended successfully [ Done ] [ Done ] [ Done ] [ Done ]
18
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.
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
19
Test (POST) procedure, in order to verify that the application can run. Initialization files are checked for consistency. Resource allocation specifically memory - is checked. Errors encountered may be recoverable or unrecoverable. Recoverable errors A recoverable error is an error from which the ProtecTIER server can recover without losing the users data. Recoverable errors are logged in the ProtecTIER logs and generate an SNMP warning notification trap. Unrecoverable errors An unrecoverable error is an error that prevents the platform from booting correctly, an unrecoverable consistency check error during ProtecTIER startup, or any other error that could cause or has caused loss of user data. The server is left in offline state (booted, responding to TCP/IP SNMP enquiries, and responding to console, telnet and modem logins). Unrecoverable errors are logged in the ProtecTIER logs and generate an SNMP error trap. Restarting on error If ProtecTIER detects an error at runtime, it recovers by rebooting and restarting the ProtecTIER process. If multiple restarts are detected within a short time period, ProtecTIER declares an unrecoverable error. Alerts The server generates SNMP traps to higher level management frameworks. In particular, whenever the system enters the online state, it generates a coldStart trap if the platform has rebooted, and a warmStart trap if the system only returned to online state from the offline state. A recoverable error generates a recoverableErrorNotification trap. An unrecoverable error generates an operatorInterventionRequired trap.
v nuttcp 6.1.2
/usr/local/bin/nuttcp-6.1.2
Note: Use iperf or nuttcp for the procedures below. The utilities cannot be used together.
20
This utility has two modes of operation, client and server. The server has to be started before the client. Before running the utility, shut down all other programs on both the client and server ProtecTIER systems. The client is the ProtecTIER system that transmits the test data and the server is the ProtecTIER system that receives the data (also known as the target server). Based on the data sent by the client and received by the server, the script outputs key network parameter values which indicate certain attributes of the network. The goal of these tests is to benchmark the throughput of the network. The most important benchmark is the direction that replication will actually take place, i.e. the target should be tested as the server since the flow of data will be to that server from the client. However, it is also important to also test the reverse direction to measure the bandwidth performance during disaster recovery failback. Network bandwidth is not always the same in both directions. In the following procedure, the goal is to test network performance between two machines on a WAN, server1 and server2. Each test will run for five minutes. Since there are five tests, the process will take a total of 25 minutes. 1. Start the server mode of the utility on server1 by entering the following commands on the command line:
cd /opt/dtc/app/sbin ./pt_net_perf_util -s
Note: The above command uses the iperf tool. To use nuttcp tool instead, add -n to the command. Enter one of the following series of commands to use nuttcp:
cd /opt/dtc/app/sbin ./pt_net_perf_util -sn or cd /opt/dtc/app/sbin ./pt_net_perf_util -s -n
2. Start the client mode of the utility on server2 by entering the following command on the command line: ./pt_net_perf_util -c server1 -t 300 Note: This step uses the iperf external utility. To use nuttcp instead, add -n to the command. Enter the following command to use nuttcp:
./pt_net_perf_util -c server1 -t 300 -n
3. The utility will automatically perform the tests in sequence. The client output (server2 in the example below) will look similar to the following: Note: In the sample output below the test ran for only 5 seconds instead of 300.
*** Latency PING 9.5.53.33 (9.5.53.33) 56(84) bytes of data. --- 9.5.53.33 ping statistics --5 packets transmitted, 5 received, 0% packet loss, time 4001ms rtt min/avg/max/mdev = 0.257/0.406/0.484/0.079 ms *** Throughput - Default TCP [ 3] 0.0- 5.0 sec 56.6 MBytes 94.8 Mbits/sec
*** Throughput - 1 TCP stream(s), 1MB send buffer [ 3] 0.0- 5.0 sec 57.0 MBytes 95.0 Mbits/sec *** Throughput - 16 TCP stream(s), 1MB send buffer
Chapter 2. Setting up ProtecTIER
21
[SUM]
65.0 MBytes
94.3 Mbits/sec
*** Throughput - 127 TCP stream(s), 1MB send buffer [SUM] 0.0-11.3 sec 127 MBytes 94.1 Mbits/sec Number of TCP segments sent: 230536 Number of TCP retransmissions detected: 21 (0%) Done.
See the next section for information about interpreting the results of the tests.
Interpreting the results: v The average round-trip-time (rtt) was 78.4ms and there was 0% packet loss. v The latency in WAN topologies may vary, but should never exceed 200ms. Contact your network administrator if latency reports more than 200ms, as it may significantly decrease replication throughput. v Higher latency values will cause a major deterioration in replication throughput. v Packet loss should be 0%. Any other value implicates a major network problem. Test 2: Throughput - default settings This test checks maximal TCP throughput using a single data stream with default TCP settings. Example result:
*** Throughput - Default TCP [ 3] 0.0-120.1 sec 2.41 GBytes 173 Mbits/sec
Interpreting the results: v The test ran for 120.1 seconds, transferred 2.41 GB, with an average throughput of 173 Mbits/sec. Note: 1 MByte = 1,048,576 bytes. 1 Mbit/sec = 1,000,000 bits/sec. Test 3: Throughput - single stream, 1MB send buffer This test checks maximal TCP throughput using a single data stream with a 1MB send buffer. Example result:
[ *** Throughput - 1 TCP stream(s), 1MB send buffer 3] 0.0-120.0 sec 2.51 GBytes 180 Mbits/sec
22
Interpreting the results: v The test ran for 120.0 seconds, transferred 2.51 GBs, with an average throughput of 180 Mbits/sec. v There may be an improvement here on high-latency links. Test 4: Throughput - 16 streams, 1MB send buffer Example result:
*** Throughput - 16 TCP stream(s), 1MB send buffer [SUM] 0.0-121.4 sec 5.91 GBytes 418 Mbits/sec
Interpreting the results: v The test ran for 121.4 seconds, transferred 5.91 GB, with an average throughput of 418 Mbits/sec. v The extra streams yielded higher utilization of the connection. v The Mbits/sec reported in this test is the maximum replication performance your system will achieve if your backup environment is using up to 2-3 cartridges in parallel. Test 5: Throughput - 127 streams, 1MB send buffer Example result:
*** Throughput - 127 TCP stream(s), 1MB send buffer [SUM] 0.0-126.1 sec 8.08 GBytes 550 Mbits/sec
Interpreting the results: v The test ran for 126.1 seconds, transferred 8.08 GB, with an average throughput of 550 Mbits/sec. v TCP takes a while to reach its maximal throughput. Longer testing times, 300 seconds or more, will produce more accurate results. v The throughput value given by this test is the potential physical replication throughput for this system. It is directly affected by the available bandwidth, latency, packet loss and retransmission rate. v The Mbits/sec reported in this test is the maximum replication performance your system may achieve. If this number islower than anticipated, contact your network administrator. Test 6: TCP Retransmissions vs. Total TCP segments sent Example result:
Number of TCP segments sent: 1619061 Number of TCP retransmissions detected: 201038 (12%)
Interpreting the results: v A total of 1619061 TCP segments were sent during the five tests, out of which, 201038 were lost and retransmitted. v The retransmission rate imposes a direct penalty on the throughput, as the retransmission of these packets take up bandwidth. The retransmission can be caused by the underlying network (e.g. packet dropping by an overflowed router) or by the TCP layer itself (e.g. retransmission due to packet reordering). v Segment loss can be caused by each of the network layers.
23
v TCP retransmission larger than 2% may cause performance degradation and unstable network connectivity. Contact your network administrator to resolve this issue and reduce it to approximately 0%. You may want to run these tests again to test the reverse throughput in the network. To run the tests in reverse, change server1 to the client and server2 to the server and repeat the procedures.
4. 5. 6. 7.
Example: US/Eastern a. Display the list of countries. Enter the command: ls <enter> b. Change to the directory of the desired country. Enter the command: cd [country] <enter> For example: cd america <enter> c. From the country directory, display the list of cities. Enter the command: ls <enter> d. From the list of cities, find the city that is closest to the time zone in which you are located, and write the name of the city on the blank line below: _____________________________________ 8. Set the local time zone on Node 1 using one of the formats (Continent/City or GMT/EST standard time zones), below: Continent/City format Enter the commands: mv /etc/localtime /etc/localtime.ORIG <enter>
24
ln -sf /usr/share/zoneinfo/[continent]/[city] /etc/localtime <enter> For example: ln -sf /usr/share/zoneinfo/america/phoenix /etc/localtime <enter> OR GMT/EST standard time zones format Enter the command: ln -sf /usr/share/zoneinfo/[standard time zone]/etc/localtime <enter> For example: ln -sf /usr/share/zoneinfo/GMT /etc/localtime <enter> 9. Set the time zone field to the chosen time zone. Enter the command: vi /etc/sysconfig/clock <enter> Note: Use the Insert and Delete keys to alter the default location. The contents of the time zone file display. For example: if you specified america/phoenix, the time zone file appears as follows: ZONE=America/Phoenix UTC=false ARC=false 10. Save the changes you made to the time zone file. Enter the command: (Esc key) wq! <enter> Note: To execute the above command, you will press the Esc key, then type wq!, and then press <enter>. 11. You may need to set the time explicitly. To do this, run the command:
date MMDDhhmm
where: MM is the two-digit month of the year DD is the two-digit day of the month hh is the two-digit hour of the day in a 24-hour format (00 - 23) mm is the two-digit minutes after the hour For example, 1:45 pm on September 1, would be entered as: 09011345. 12. Synchronize the servers hardware clock by running the command:
hwclock --systohc service ntpd start <Enter> <Enter>
13. Restart the ntp service on Node 1. Enter the command: As the ntpd service restarts, status messages similar to the ones shown below, display: [root@Austin America]# hwclock --systohc [root@Austin America]# service ntpd start ntpd: Synchronizing with time server: [FAILED] Starting ntpd: [ OK ] Note: The [FAILED] message above may display if the customer is not using an external time server. If this is the case, and the ntpd service returns a status of [OK], ignore the failure and proceed to the next step.
25
14. Disconnect the keyboard and monitor from Node 1 and reconnect them to Node 2. 15. If necessary, log in to Node 2 with the username root and password admin. 16. Run steps 8 on page 24 through 11 on page 25 on Node 2. 17. Synchronize the exact time from Node 1 by running the command:
rdate -s internal_node1
As the ntpd service restarts, status messages similar to the ones shown below, display: [root@Austin America]# hwclock --systohc [root@Austin America]# service ntpd start ntpd: Synchronizing with time server: [FAILED] Starting ntpd: [ OK ] Note: The [FAILED] message above may display if the customer is not using an external time server. If this is the case, and the ntpd service returns a status of [OK], ignore the failure and proceed to the next step. 20. Run the following commands to view the updated time:
date <Enter> ntpq -p
21. Complete the services startup on Node 1 (this will fence Node 2 which should restart with the correct time): service ptcluster start <enter> service vtfd start <enter> Note: Starting the cman service will initiate fencing. This causes Node 2 to reboot. However, you can continue starting the services on Node 1 while Node 2 is rebooting. When Node 2 reboots during fencing, the time on Node 2 synchronizes with the time on Node 1. 22. When both nodes have finished rebooting, use PT Manager to verify that fencing completed successfully and both nodes are online. To do so: a. On the PT Manager workstation or TSSC, open PT Manager. b. Confirm that both nodes display as Online. If one (or both) nodes displays as offline, contact your next level of support.
26
Prerequisites
The ProtecTIER Manager workstation must meet the following prerequisites in order to install and run ProtecTIER Manager effectively: v One of the following operating systems: Windows 32 bit (2003/XP) Linux Red Hat 32/64 bit (Red Hat Enterprise 4 or 5) v At least 1.2 GB of available disk space v At least 256 MB or RAM v The workstation can access the ProtecTIER service nodes IP address (ports 3501 and 3503 are open on the firewall). In addition, it is recommended that the monitor for ProtecTIER Manager be configured to the following settings: v Resolution of 1024 x 768 pixels or higher (this is the minimum resolution supported, however, 1280 x 1024 is recommended). v 24 bit color or higher Note: If you are planning to run ProtecTIER Manager on a UNIX system, configure your graphics card and X windows system. This is done either manually or using the Xconfigurator utility. For instructions, refer to the appropriate Linux documentation.
27
If you are installing ProtecTIER Manager on a workstation on which an older version of ProtecTIER Manager is already installed, uninstall the older version first. For more information, see Uninstalling the ProtecTIER Manager on page 30.
Installing on Windows
Perform the following steps to install ProtecTIER Manager on Windows. To install ProtecTIER Manager on Windows: 1. Insert the IBM System Storage ProtecTIER Manager v2.3 CD into the CD-ROM drive of the designated ProtecTIER Manager workstation. v If the ProtecTIER Manager autorun launches and starts the installation, go on to step 2. v If the ProtecTIER Manager autorun process does not launch automatically, do the following: a. On the Windows task bar, click: Start > Run. The Run dialog box opens. b. In the Open box, type: D: (where D: is the servers CD-ROM drive). c. Click OK. The contents of the IBM System Storage ProtecTIER Manager v2.3 CD display. d. From the list of files, locate the ProtecTIER Manager for Windows installation file and double-click the file to start the installation. 2. Read the Introduction screen, and then click Next. 3. Read and accept the license agreement provided, and click Next. The Choose Install Folder screen is displayed. 4. Specify the folder where the ProtecTIER Manager program files will be installed, and click Next. The Choose Shortcut Folder screen is displayed. 5. Select the location where the program icons will be created: v In a new Program Group - Creates a new program group in the Program list of the Start menu. v In an existing Program Group - Adds the shortcut to an existing program group in the Program list of the Start menu. v In the Start Menu v On the Desktop v In the Quick Launch Bar v Other - Enables you to enter a path location for the shortcut, or to browse for a location by clicking Choose. v Dont create icons - No shortcuts are created. Note: When relevant, you can select Create Icons for All Users to create a shortcut in the defined location for all user accounts on the workstation. 6. Click Next. The Pre-Installation Summary screen displays the Install and Shortcut folder locations and the disk space information of the target for installation. 7. Review the Summary screen, and click Install to start the installation. The Installing ProtecTIER Manager screen is displayed. 8. When the installation is complete and ProtecTIER Manager has been successfully installed, click Done.
28
The Install Complete screen is displayed. The ProtecTIER Installation wizard closes. 9. Go to Adding nodes on page 35.
Installing on Linux
Perform the following steps to install ProtecTIER Manager on Linux. To install ProtecTIER Manager on Linux: 1. Insert the IBM System Storage ProtecTIER Manager v2.3 CD into the CD-ROM drive of the designated ProtecTIER Manager workstation. 2. Run the ProtecTIER Manager installer: Note: This assumes the workstation has a Linux graphical interface which is required for ProtecTIER Manager. a. From the Linux Desktop, select and open the CD drive icon. b. Select and open the folder for your Linux version: Linux for version 64 or Linux32 for version 32. c. When the folder opens, drag the InstallLinuxXX.bin file from the folder to the Desktop. (XX=either 32 or 64, depending on the Linux folder you selected.) d. Close the open windows. e. Right-click on an open area of the Desktop, and from the menu options displayed, select Open Terminal. f. At the Terminal command prompt, change to the Desktop directory using the following command (Note: Desktop is case sensitive. Type it using a capital D.):
cd Desktop <Enter>
g. From the Desktop directory in the Terminal window, run the ProtecTIER Manager installer:
./InstallLinuxXX.bin <Enter>
(XX= either 32 or 64, as noted above) If the message: Permission Denied displays, enter the following commands:
chmod +x InstallLinuxXX.bin <Enter> ./InstallLinuxXX.bin <Enter)
The IBM ProtecTIER Manager wizard Introduction screen is displayed. 3. Click Next. Two separate Software License Agreement screens display. 4. Read the terms for each license agreement, select I accept both the IBM and non-IBM terms of the License Agreement and click Next. The Choose Install Folder screen is displayed. 5. Enter the path to the location where the ProtecTIER Manager program files will be installed. Click Choose to browse for a location. Note: Click Restore Default Folder to revert to the default installation path. 6. Click Next. The Choose Link Folder screen is displayed. 7. Select the location where the program links will be created: v In your Home folder Creates the links in the directory where the users files are typically stored. For example: /home/bill.
29
v Other Creates the links in the default location (/opt/IBM/PTManager). To specify a different location, click Choose and select a directory on the workstations hard drive. 8. 9. v Dont create links No links are created. Click Next. The Pre-Installation Summary screen is displayed. Click Install. The Installing ProtecTIER Manager screen is displayed and ProtecTIER Manager is installed on your computer. When the installation is complete, the Install Complete screen is displayed. Click Done. The ProtecTIER Manager wizard closes. When the command prompt returns in the Terminal window, type exit to close the window. Go to Adding nodes on page 35.
10. 11.
30
Log in to each ProtecTIER cluster you want to manage using ProtecTIER Manager. 1. Click the Login button. The Login dialog is displayed. 2. Enter your username and password. 3. Click Ok. The Login dialog closes and you are logged into ProtecTIER Manager. It is recommended that you change or replace these default user accounts. (For more information, see Chapter 11, Managing users, on page 113.) Note: Only one Administrator can be logged into a ProtecTIER cluster at a time. It is, therefore, recommended that you log out at the end of each session by clicking the Logout button. If you log in with Administrator level permission while another Administrator is already logged in, a message box is displayed with the following message:
Administrator is already logged in from host <host name>, at IP address: <IP address>. Would you like to login anyway?
Enabling replication
Perform the following procedure to enable replication on systems that are being upgraded from v2.x to v2.3. By default, replication is enabled on new repositories created with ProtecTIER v2.3. Replication is disabled on repositories upgraded from previous versions. When you enable replication, you must assign files systems, set the estimated factoring ratio, MD raid configuration, and disk size. The procedure allocates
31
metadata for replication and then you can add file systems to the repository as needed. If more storage is required, you can select additional file systems (if they exist) to add to the metadata. Enabling replication on the TS7650 Appliance should not require any additional metadata space, as the required metadata has already been allocated during the v2.2 repository creation. Enabling replication on the TS7650G may require additional metadata, pending the actual metadata deployment on the specific repository. Note: Before you begin, make sure that the code has been upgraded to v2.3 and that replication has been added during the ProtecTIER configuration process. To enable replication: 1. From the Systems management view, select Replication > Enable replication. The Enable replication wizard welcome screen is displayed. 2. Click Next. The Properties dialog is displayed. 3. Select the Estimated factoring ratio, the MD raid configuration, and the Disk size (in GB) of the metadata disks. Note: The size of the repository cannot be changed when enabling replication. 4. Click Next. The Repository resources dialog displays the total amount of metadata and user data (in GB) allocated for the repository. 5. If more storage is required, click Advanced. The Repository resources window is displayed with a list of available file systems (if they exist). 6. Select what file systems will be used for metadata or user data. Click Ok, the resources window closes. 7. Click Finish. The summary report is displayed and replication is enabled on ProtecTIER Manager.
32
Select the Refresh navigation pane button to refresh the Navigation pane. Select Refresh current view button to refresh the View pane.
33
34
Adding nodes
To add a node to ProtecTIER 1. Run the ProtecTIER Manager application: v For a Windows based ProtecTIER Manager workstation, run the ProtecTIER Manager application: Click Start > Programs > IBM > ProtecTIER Manager 2.3.x > IBM ProtecTIER Manager. v For a Linux based ProtecTIER Manager workstation, click the icon for ProtecTIER Manager on the Desktop or from the location of the shortcut that you selected during the installation. The ProtecTIER Manager screen is displayed. 2. Click the Add node button. The Add node dialog box is displayed, prompting you for the IP address and Port number of the node that you want to add. 3. Enter the IP address of the node and click Ok. The node is displayed in the Nodes pane and the Login button is displayed in the View pane. Note: Do not change the port number of the node unless directed to do so by IBM Support. 4. Click Login. You are prompted for your username and password. 5. Enter your username and password and click Ok. ProtecTIER Manager displays the information for that node. If the node has a repository, the nodes cluster is displayed in the Systems tab of the Navigation pane. If that cluster already contains a second node, the second node is also displayed in the Nodes pane. Note: For more information about repositories, see Chapter 6, Managing repositories, on page 37.
35
Removing nodes
Removing a node stops the instance of ProtecTIER Manager at your workstation from registering the node and being able to manage it. The node itself, and the cluster with which the node is associated, is unaffected by removing a node in this way. Note: If you remove a node that is associated with a two-node cluster, the second node will also be removed. Perform the following steps to remove a node: 1. In the Node pane, select the node that you want to remove. 2. Click the Remove node button. A confirmation message box is displayed. 3. Click Yes. The node is removed.
36
Expanding repositories
Complete the tasks in this topic to increase the capacity of a repository. Attention: This section provides instructions for increasing the capacity of a repository when using the TS7650G. After the repository is created, the ProtecTIER system enables you to increase the capacity of the repository. Much like creating the repository, expanding the repository requires the guidance of IBM Support and use of a wizard for planning repository expansions. You might need to expand the repository if: v Your factoring ratio is higher than originally expected and you are running out of meta data space v Your repository needs have expanded beyond the original growth projections and you are running out of user data space
Planning an expansion
In addition to guidance from IBM Support, run the Plan repository increase wizard to determine the optimum repository size and meta data file system arrangement for your expanded repository. To plan a repository expansion: 1. Choose Repository > Increase capacity planning. The Increase capacity planning window opens. 2. In the Repository size field, select the total physical size, in TB, for the repository. Note: If you are expanding the repository only to increase the amount of meta data space, increase the estimated factoring ratio value, but leave the repository physical size value unchanged.
Copyright IBM Corp. 2008, 2009
37
3. In the Estimated factoring ratio field, enter the updated factoring ratio estimate for the repository. 4. In the MD Raid configuration field, select a configuration option from the drop-down list. 5. In the Disk size field, select the physical disk size, in GB, from the drop-down list. 6. Click Ok. The Increase capacity planning dialog closes and the Repository meta data storage requirements window is displayed listing the minimum meta data file system expansion options that are suitable for your expansion needs.
7. Click Options to print or save as a .csv file the information in the Repository meta data storage requirements dialog using the standard procedures for your operating system. 8. Click Plan again to go back to the Increase capacity planning window and change the configuration options, or click Ok. The Repository meta data storage requirements dialog closes. The information from the Repository meta data storage dialog indicates whether you need to create more file systems and/or expand the existing file systems for the increased repository.
38
3. To display the list of file systems that are already a part of the repository, type the command:
./fsCreate -r
Example
[root@nodeA sbin]# ./fsCreate -r [INFO] [09/02/17-16:18:36] Repository file systems are: [INFO] [09/02/17-16:18:36] /dev/mapper/vg0-lv_vg0 /mnt/vg0-lv_vg0 [INFO] [09/02/17-16:18:36] /dev/mapper/vg1-lv_vg1 /mnt/vg1-lv_vg1 [INFO] [09/02/17-16:18:36] /dev/mapper/vg2-lv_vg2 /mnt/vg2-lv_vg2
4. To display the list of available new multipath devices, type the command:
./fsCreate -u
Example
[root@nodeA ~]# /opt/dtc/app/sbin/fsCreate -u [INFO] [09/02/17-16:35:24] New devices are: [INFO] [09/02/17-16:35:24] /dev/mapper/mpath7 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath6 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath12 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath5 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath11 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath4 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath10 [INFO] [09/02/17-16:35:24] /dev/mapper/mpath3
5. To create file systems on new available multipath devices, register them to /etc/fstab and mount them, type the command:
./fsCreate -e
If you are creating file systems for a two-node cluster, stop the cluster services on the second node during the file system creation to avoid any possibility of corrupting meta data on the repositorys management file system. Type the following commands to stop service on the second node:
service vtfd stop service ptcluster stop
6. Once the file systems are created, start the services on the node. Register the new file systems to /etc/fstab, create the mount points and mount them by typing the command:
./fsCreate -t
7. To verify, display the GFS file systems that are not part of the repository by typing the command:
Chapter 6. Managing repositories
39
./fsCreate - g
Example
[root@nodeA ~]# /opt/dtc/app/sbin/fsCreate -g [INFO] [09/02/17-16:35:13] Non-repository file systems are: [INFO] [09/02/17-16:35:13] /dev/mapper/vg0-lv_vg0 /mnt/vg0-lv_vg0 [INFO] [09/02/17-16:35:13] /dev/mapper/vg1-lv_vg1 /mnt/vg1-lv_vg1 [INFO] [09/02/17-16:35:13] /dev/mapper/vg2-lv_vg2 /mnt/vg2-lv_vg2 [INFO] [09/02/17-16:35:13] /dev/mapper/vg3-lv_vg3 /mnt/vg3-lv_vg3
fsCreate parameters
Use the following syntax and parameters to perform additional functions for expanding the physical capacity of a repository. Syntax:
fsCreate Table 3. fsCreate parameters Parameter -n Description Return Code (rc=0) Return Code (rc=1)
Create GFS file All file systems built. Error encountered systems for all mpath building file systems or detected physical devices during first-time installation. volumes created from mpath devices. Create GFS file systems for new mpath devices during capacity upgrade. Create mount points and register GFS file systems to /etc/fstab. All new file systems built. Error encountered building file systems or detected physical volumes created from mpath devices. Error encountered creating and registering mount points to /etc/fstab or detected physical volumes created from mpath devices. Failed to determine status of an existing file system or detected physical volumes created from mpath devices. Detected physical volumes created from mpath devices. Failed to determine status of an existing file system or detected physical volumes created from mpath devices.
-e
-t
-r
Display all repository Call completed GFS file systems. without error.
-u
-g
40
41
10. Select file systems from the Available file systems list and click the arrows to the left and right of the column to add available file systems to either the meta data column or the user data column. 11. Click Ok. The Repository resources dialog closes. 12. Click Next. A summary report is displayed with the new configuration. 13. Click Finish. The Increase capacity wizard closes and the ProtecTIER system temporarily goes offline to increase the repository capacity.
Deleting repositories
Complete this task to delete a repository. In a two-node cluster where the repository was created on one of the nodes, you must remove the second node before you delete the repository. In general, it is not necessary to delete a repository. However, you might have to delete a repository in certain troubleshooting scenarios. For more information, contact IBM Support. For more information, see Removing and adding cluster members on page 121. Attention: Deleting the repository results in the loss of all the data contained in the repository.
42
Perform the following steps to delete a repository: 1. In the Repositories pane, select the repository. 2. Choose Repository > Delete repository. A confirmation message box is displayed. 3. Click Yes. The Data Loss Confirmation dialog box is displayed. 4. In the field, type data loss and click Ok. A confirmation message box is displayed. 5. Click Yes. The ProtecTIER system temporarily goes offline to delete the repository.
Replication policies
A replication policy defines a set of objects (for example, cartridges) from a repository that need to be replicated to a remote repository. A replication policy is the only means to transfer deduplicated data from a source repository to a destination repository. A replication policy is made up of rules. An event occurs, for example, which indicates that the data segment on a cartridge has changed and that replication may be needed for the specific cartridge. Once the event matches with a policy, a trigger is created for replication activity and a job occurs. Replication policies are defined via the Systems Management view of ProtecTIER Manager. A policy can only be created on a repository that is the source in a grids pair and the policy only applies to the repository on which its defined. Click on a repository in the navigation pane to view the policies defined for that repository. Select a policy from the list to view the policy details and replication statistics.
43
The following sections describe how to create and work with replication policies: v Setting the replication timeframe v Creating a replication policy on page 45 v Enabling and disabling a policy on page 46 v Running a policy on page 46 v Modifying a policy on page 47 v Deleting a policy on page 47
44
2. Select an option. You can either set a precedency for backup where the replication policy will take precedence in the order of other policies to be replicated, or you can set a given timeframe by setting the Start time, Duration and End time. 3. Click OK.
45
a. Type a unique policy name in the Policy name field. You cannot have the same policy name twice. If you do define the same policy name, an error message is displayed. b. Policies have 3 options of priority: High, Medium, Low. Define the policys Priority according to the importance and/or urgency of the data that needs to be transferred. For example, a policy with a high priority is transferred first, then a policy with medium priority, followed by low priority. The default is Low for every policy. c. Selecting Policy enabled automatically runs the policy within the timeframe defined. If Policy enabled is not selected, no activities will take place. Click Next, the Replication Destination screen is displayed: The Destination repository option controls the visibility of replicated cartridges at the destination repository. Destination replica cartridges can be invisible (if you choose shelf) or visible (if you choose a library). The Target is the destination of the cartridge. The target is either the shelf or a library: v If you choose shelf, the visibility switching feature is not activated. v If the target is a library, the visibility switching feature is activated. Upon ejecting a cartridge, it is first moved to the shelf on the local repository. On the remote repository, the cartridge is moved to the import/export slot of a library so that the backup application on the remote site can see it. Click Next. The Barcode ranges screen is displayed. The policy objects, i.e. cartridges, are defined as barcode ranges. There can be up to 256 ranges in a single policy. Type the From and To barcodes for a range of cartridges to be replicated. Click Add to view the range in the Ranges table. If a barcode number or barcode range appears more than once, an error message is displayed with the conflict. To delete the barcode ranges from the table, click Select all and Remove, or click Select none to deselect. Click Next. The Summary report is displayed with the policy name and the number of ranges that were defined.
3.
4.
5. 6.
7. 8.
Enabling a policy
Upon successfully creating a policy, by default, the policy is enabled. This means that all incoming replication events will look to apply their rules to the policys definition. If a policy is disabled, you can enable it from ProtecTIER Manager. This does not affect current running activities.
Disabling a policy
A policy can be disabled at any time from ProtecTIER Manager. If a policy is disabled, all incoming replication events will ignore the policy from the moment it is disabled. This does not affect current running and pending activities.
Running a policy
Policies can be run either manually or automatically (i.e., continuously).
46
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.
Modifying a policy
You can modify a policy to change the parameters originally defined during policy creation. To modify a policy: 1. Select Replication > Policy > Modify policy. The Modify policy welcome screen is displayed. 2. Click Next. The Properties screen is displayed: a. Define the policys Priority according to the importance and/or urgency of the data that needs to be transferred. Policies have 3 options of priority: High, Normal, Low. The default is Normal for every policy. b. Select Policy enabled to automatically run the policy within the timeframe defined. If Policy enabled is not selected, no activities will take place. 3. Click Next, the Replication Destination screen is displayed. Select the remote target location in the destination repository to which the cartridge with the replicated data is to be placed. 4. Click Next. The Barcode ranges screen is displayed with the ranges defined during creation of the policy. a. To delete the barcode ranges from the table, click Select all and Remove. b. To deselect your choice, click Select none. c. Type the From and To barcodes for a range of cartridges to be replicated. 5. Click Add to view the range in the Ranges table. If a barcode number or barcode range appears more than once, an error message is displayed with the conflict. 6. Click Next. The modified policys Summary report is displayed.
Deleting a policy
Deleting a policy removes the policy in its entirety from the repository. All running and pending activities are aborted.
Chapter 6. Managing repositories
47
To delete a policy: Select Replication > Policy > Delete policy. A dialog will appear to confirm the action and a message that all running and pending activities will be aborted. For more information on aborting replication activities, see Aborting replication activities.
48
49
Note: If you no longer want a port to have an HP WWN, delete the line identifying the HP WWN from /etc/pt/ports_conf.xml, for example:
<hp-wwn wwn=50060b000000f0b0/>
Creating libraries
A library can be created on a ProtecTIER system of either one node or two nodes. Note: Check with your backup application administrator to ensure the number of drives and cartridges supported by your application.
7650G Maximum number of libraries Maximum number of virtual drives 16 256 (dual-node 512) 7650 Appliance 12 256 (dual-node 512)
Note: Use the Scan button of the Port attributes pane to verify if the ports of the ProtecTEIR server to which the virtual devices of the library are to be assigned are connected to the correct host. For more information, see Port attributes on page 86. If your ProtecTIER node has ports connected to a host that is running HP-UX, verify that the ports are configured as HP-UX ports. For more information, see Configuring node ports for hosts running HP-UX on page 49. If these conditions are not met, the host may not be able to detect all of the virtual tape drives. Perform the following steps to create the library: 1. In the Systems pane, select a cluster on which to add a library. 2. From the Toolbar, click the Create new library button. The Create new library wizard Welcome screen is displayed. 3. Click Next. The Library details screen is displayed. 4. In the VT name field, enter a name for the library. 5. Click Next. The Library type screen is displayed.
50
6. Select the type of physical library model that you want the virtual library to emulate: v ATL P3000 0100 v IBM TS3500 0100 You can also configure the virtual library models: v DTC VTF 0100 v IBM V-TS3500 0100 Note: Verify that the backup application that you are using supports the type of library model that you select. 7. Click Next. The Tape model screen is displayed.
51
8. Select the type of tape drive model that you want the virtual library to emulate. The type of tape drive depends on the library type chosen: v IBM ULT3580-TD3 (IBM LTO3) Note: All tape drives in the library are of this type after your selection, including tape drives added at a later time. 9. Click Next. The Tape drives screen is displayed.
52
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.
53
12. Select or deselect the check boxes next to each port to define which of the nodes ports are assigned virtual devices. Note: If you have chosen an IBM library model, all the robots are selected and enabled. You can deselect the robots and choose at least one. If you have chosen a library model other than IBM, the robots are not checked and only one must be chosen. 13. In the Drives fields corresponding to each selected port, select the number of virtual tape drives that are assigned to each port. Note: Optionally, click Select All to automatically select both ports. Click Equally divide to evenly divide the number of drives between the ports. 14. Check the Robot checkbox if you want the library virtual robot to be accessible through this port. Note: For high-availability purposes, TS7650 supports the assignment of the virtual robot to multiple ports. 15. Click Next. If a second node exists in the cluster, the Assignment (2) screen is displayed.
54
16. Repeat steps 12 on page 54 and 13 on page 54 for the Assignment (2) screen. 17. Click Next. The Cartridges screen is displayed.
55
18. In the No. of cartridges field, enter the number of cartridges that you want to have in the library. The Virtual cartridge size field automatically displays the maximum possible size for virtual cartridges for your system. This is based on the number of cartridges entered, the total amount of available storage space in your repository, and the current HyperFactor ratio. Note: Optionally, select the Max. cartridge growth checkbox. When selected, you can limit the maximum amount of nominal data that a cartridge can contain. The value of the maximum number of cartridges possible on a system depends on the amount of storage space available on your system. 19. In the Barcode seed field, enter a value for the barcode seed. The barcode seed is the barcode that is assigned to the first cartridge created. Every cartridge added after the first cartridge is assigned a barcode following the initial barcode seed. Note: The barcode seed must contain only numbers and capital letters. 20. Click Next. The Slots screen is displayed.
56
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.
57
When you set the library type, you can select the type of physical library model you want the virtual library to emulate: v ATL P3000 0100 v IBM TS3500 0100 You can also configure the virtual library models: v DTC VTF 0100 v IBM V-TS3500 0100 If you chose the TS3500 (or P3000) during creating a library and your backup application does not support that library model type as a virtual tape system, the Set library type dialog allows you to change the library type to V-TS3500 (or VTF). Conversely, if you chose the V-TS3500 (or VTF) during library creation, and your backup application supports the TS3500 library, use Set library type to change the library type. (i.e. You can interchange between the TS3500 and V-TS3500 library models and between the P3000 and VTF library models.)
Example
To set the library type, select VT > VT Library > Set library type. The Set library type dialog is displayed and you can specify the library type accordingly:
58
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.
59
6. Select or deselect the check boxes next to each port to define which of the nodes ports are assigned virtual tape drives. 7. In the Drives fields corresponding to each selected port, select the number of virtual tape drives that are assigned to each port. Note: Optionally, click Select All to automatically select both ports. Click Equally divide to evenly divide the number of drives between the ports. 8. Optionally, click Track Changes to display the modifications that the ProtecTIER system might need to make in response to the changes you defined. Then, click Re-assign ports to return to the Assignment screen and continue assigning virtual tape drives. 9. Check the Robot checkbox if you want the library virtual robot to be accessible through this port. Note: For high-availability purposes, TS7650 supports the assignment of the virtual robot to multiple ports. 10. Click Next. If a second node exists in the cluster, the Assignment (2) screen is displayed.
60
11. Repeat steps 6 on page 60 through 9 on page 60 for the Assignment (2) screen. 12. Click Next. The Slots screen is displayed.
61
13. In the Number of slots field, enter the number of slots that you want in the library. Note: The number of slots must be at least equal to the number of cartridges in the library. 14. In the Number of import/export slots field, enter the number of import/export slots that you want in the library. 15. Click Next and Finish. The Change dimensions wizard closes and the ProtecTIER system temporarily goes offline to update the library.
Reassigning devices
The ProtecTIER system enables you to relocate the virtual robot and cartridge drives between nodes or node ports. Perform the following steps to reassign the virtual robot or cartridge drives: 1. Choose VT > VT Library > Re-assign devices. The Re-assign devices wizard Welcome screen is displayed. 2. Click Next. The Tape drives screen is displayed.
62
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.
63
5. Select or deselect the check boxes next to each port to define which of the nodes ports are assigned virtual tape drives. 6. In the Drives fields corresponding to each selected port, select the number of virtual tape drives that are assigned to each port. Note: Optionally, click Select All to automatically select both ports. Click Equally divide to evenly divide the number of drives between the ports. 7. Optionally, click Track Changes to display the modifications that the ProtecTIER system might need to make in response to the changes that you defined. Then, click Re-assign ports to return to the Assignment screen and continue assigning virtual tape drives. 8. Check the Robot checkbox if you want the library virtual robot to be accessible through this port. Note: For high-availability purposes, TS7650 supports the assignment of the virtual robot to multiple ports. 9. Click Next. If a second node exists in the cluster, the Assignment (2) screen is displayed.
64
10. Repeat steps 5 on page 64 through 8 on page 64 for the Assignment (2) screen. 11. Click Next. The Summary report is displayed.
65
12. Click Finish. The Re-assign devices wizard closes and the ProtecTIER system temporarily goes offline to reassign the devices.
Managing cartridges
The ProtecTIER system has a function that enables you to add and remove cartridges from your libraries.
66
Adding cartridges
If your virtual library has enough empty slots to accommodate the additional cartridges, the adding cartridges process occurs online without disrupting backup. If the virtual library does not have enough empty slots, adding cartridges causes the ProtecTIER system to temporarily go offline to create more slots for the cartridges. Perform the following steps to add cartridges: 1. Click the Add cartridges button. The Add cartridges wizard Welcome screen is displayed. 2. Click Next. The Cartridges screen is displayed.
3. In the No. of cartridges field, enter the number of cartridges that you want to have in the library. The Virtual cartridge size field automatically displays the maximum possible size for virtual cartridges for your system. This number is based on the number of cartridges entered, the total amount of available storage space in your repository, and the current HyperFactor ratio. Note: Optionally select the Max. cartridge growth checkbox. When selected, you can limit the maximum amount of nominal data that a cartridge can contain.
Chapter 7. Managing the ProtecTIER VT service
67
The value of the maximum number of cartridges possible on a system depends on the amount of storage space available on your system. 4. In the Barcode seed field, enter a value for the barcode seed. The default barcode seed is the continuation of the initial barcode seed assigned when the library was created. Note: The barcode seed must contain only numbers and capital letters. 5. Click Next and Finish. The Add cartridges wizard closes and the cartridges are added to the library. If the necessary number of cartridge slots are not already available, the ProtecTIER system temporarily goes offline to create them.
Deleting cartridges
Deleting a cartridge results in the loss of all data contained in the cartridge. Perform the following steps to delete a cartridge: Note: Alternatively, you can delete a cartridge from the shelf. Deleting a cartridge from the shelf is a nondisruptive operation (i.e. the VTL stays online). Thus, it is recommended that you eject the cartridges you want to delete to the local shelf on the repository, and then delete the cartridge. 1. From the Systems tab, select the library from the Services pane that contains the cartridge that you want to delete. The VT screen is displayed. 2. Click the Cartridges tab. The Cartridges screen is displayed.
68
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.
69
Renaming libraries
The ProtecTIER system enables you to rename libraries after they have been created. Perform the following steps to rename an existing library: 1. In the Services pane, select a library. 2. Choose VT > VT Library > Rename library. The Rename library dialog is displayed. 3. Enter a new name for the selected library and click Ok. The Rename library dialog closes and the librarys name is changed.
Deleting libraries
Attention: Deleting a library results in the loss of all data contained in that library. Perform the following steps to delete a library: 1. In the Services pane, select a library. 2. Choose VT > VT Library > Delete library. A confirmation message box is displayed. 3. Click Yes. The Data Loss Confirmation dialog is displayed. 4. In the field, type data loss and click Ok. A confirmation message box is displayed. 5. Click Yes. The ProtecTIER system temporarily goes offline to delete the library.
70
Managing a grid
Managing a grid is done via the Grids Management view of ProtecTIER Manager. Note: Grid IDs and repository IDs are numbers that are never recycled. Even if a repository leaves the grid and re-enters the grid, it will not receive the same ID. Thus, actions like leaving a grid are expected to be rare and should not be planned as part of the normal flow of work.
Creating a grid
Managing a grid is done via the Grids Management view of ProtecTIER Manager. Note: Grid IDs and repository IDs are numbers that are never recycled. Even if a repository leaves the grid and re-enters the grid, it will not receive the same ID. Thus, actions like leaving a grid are expected to be rare and should not be planned as part of the normal flow of work. 1. Click Create new grid. The Create new grid dialog is displayed. Note: A maximum of 63 grids can exist in an organization. 2. Complete the fields to define a grid. Select a unique Grid ID number (1 to 63) from the dropdown list and enter a name in the Name field. Click Ok.
71
Note: ProtecTIER will not allow you to choose an ID that has already been used.
72
Creating pairs
Before defining any policy, you must define repository pairs. Note: When defining a replication pair, you also define the direction of the replication from the source repository to the destination repository. Typically, the source is the primary repository and the destination is the DR site. To create a replication pair: 1. Select Grid > Create replication pair. The Create replication pair dialog is displayed:
2. Select the Source repository ID and Destination repository ID from the drop-down listboxes. Click Ok. Note: The source and destination repository ids in a pair cannot be the same.
Deleting pairs
To delete a replication pair:
Chapter 8. Native Replication Management
73
1. Select Grid > Delete replication pair. The Delete replication pair dialog is displayed:
2. Select a replication pair to delete from the drop-down listbox. Click Ok. The repositories are listed separately.
74
Figure 32. View of grid member details via Grids Management mode
75
76
Monitoring clusters
In the Systems Management pane, select a cluster. The Systems monitoring screen is displayed:
The Systems screen consists of the following main tabs: v General v VT on page 79 and In addition, the ProtecTIER Manager status bar displays the total read throughput rates for the selected cluster and the time on the cluster. write Note: The status bar also displays the Alerts and Event log buttons which enable you to view alert and event information for the nodes of the selected cluster. (For more information, see Viewing the alerts and events log windows on page 117.)
General
The General tab displays information about the cluster and consists of the following panes:
Copyright IBM Corp. 2008, 2009
77
Capacity
The Capacity pane displays the amounts of the disk space that are used , allocable, or fragmented in the selected clusters repository, in both graphical and numerical format. The amount of total disk space is also displayed. v Total capacity refers to the total amount of physical disk space in the system v Used refers to the amount of physical space that currently contains data v Allocable refers to the amount of free physical space that is available to hold data v Fragmented refers to the amount of free physical space that cannot hold data until it is defragmented by ProtecTIERs defragmentation operation You can click View resources to open the Storage resources dialog.
The Storage resources dialog displays the list of meta data and user data file systems for the selected clusters repository.
78
Note: Open the Storage resources dialog at any time by clicking View resources button in the Toolbar.
Cluster members
The Cluster members pane displays the following information about each node in the cluster:
Table 4. Cluster member information Column IP Address DNS GUI proxy Definition IP address of the node. Name of the node. Indicates which node is currently being used by ProtecTIER Manager to monitor the cluster. Indicates whether ProtecTIER is online or offline on the node. Indicates whether the VT service for that node is online or offline.
Status VT
VT
The VT tab displays information about the VT service libraries associated with the cluster.
79
The VT tab consists of the following panes: v Library front-end - Displays information about all library devices assigned to nodes in the cluster. For more information, see Library type on page 89. v Libraries performance - Displays the total performance of the libraries in the cluster. For more information, see ProtecTIER VT overview on page 89. v Libraries configuration - Displays the total number of drives, slots, import/export slots, and cartridges for all the libraries in the cluster. For more information, see Configuration on page 89.
80
The Repository monitoring screen consists of the following panes: v Capacity v Total utilization v Repository configuration v Storage on page 82 v HyperFactor on page 83
Capacity
The Capacity pane of the Repository monitoring screen is identical to that of the Cluster monitoring screen. For more information, see Capacity on page 78.
Total utilization
The Total utilization pane displays the following information in both graphical and numerical format:
Table 5. Total utilization information Item Used space Nominal data size Definition The amount of used physical repository space that currently contains data. The total amount of data which is stored in the used space using HyperFactor.
Repository configuration
The Repository configuration pane features the following information:
Chapter 9. Monitoring ProtecTIER
81
Table 6. Repository information Field Configured size Configured factoring ratio Calculated factoring ratio Configured peak throughput Configured IOPS Function The physical repository size in terabytes. The estimated HyperFactor factoring ratio that was used to create the repository. The actual current HyperFactor factoring ratio. The expected maximum peak throughput specified when the repository was created. The configured number of I/O operations per second supported by the meta data file systems specified during the repository creation.
Storage
The Storage pane displays the following graphs: v Nominal data size graph v Utilization graph You can alternate between the graphs using the tabs located below the Storage pane. Note: Set the scale of the Storage pane graphs to either hours or days.
The Nominal data size graph displays the amounts of data contained in the repository over time.
Utilization graph
The Utilization graph displays the amounts of actual repository space used over time.
82
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.
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.
The HyperFactor ratio over time graph displays the cumulative HyperFactor ratio as it changes over time.
83
When you select a policy, you can see the policys details as defined by the Create policy wizard. In addition, you can see the number of active and pending replication activities related to this policy. Policy name The name that you define for the policy. Mode Cartridges are either copied or moved. (Note: In this release, copy is the only mode of operation.) Priority Policys level of importance: high, normal, or low. Enabled Policy can be enabled or disabled for execution.
84
Note: The replication activities view is adhoc. As such, if new data is written to a cartridge while it is being replicated, the progress of the displayed data details will appear as if it has been restarted. Object ID the barcode of the cartridge Policy the name of the policy that contains the respective cartridge in its definition Throughput the nominal throughput of replicating data in MB/sec Dedup displays the savings in the bandwidth needed for replicating this cartridge Priority the replication policys priority in the queue Progress the progress of replicating the latest changes to their destination Time left the amount of time remaining for the replication process to complete
85
Monitoring nodes
In the Nodes pane, select a node. The Node monitoring screen is displayed. The Node monitoring screen consists of the following panes: v v v v Port attributes Version information Fibre channel ports throughput Network configuration on page 87
Port attributes
The Port attributes pane displays the following information for each port in the node:
Table 7. Port attribute information Column Port Definition Port number and port mode. All ports in the ProtecTIER system are front-end ports that connect the node with the backup server(s). This mode is labeled FE. Worldwide Name of the port. Transmission speed of the port. Fiber Channel topology of the port. The possible values are as follows: v Point-to-point (P2P) v Fiber channel-arbitrated loop v Down There is no fiber channel connection User setup User-assigned link speed and topology.
In addition, for each port you can click the Scan button to open the Scan Port dialog box. The Scan Port dialog box displays a numbered list of the Worldwide Names of the remote ports detected by the port.
Version information
The Version information pane displays the version numbers for the versions of ProtecTIER, the PT Linux RPM, and the DTC Emulex RPM installed and running on the node. In addition, click Show fixes to display the list of temporary fixes featured in the installed ProtecTIER version.
86
Network configuration
The Network configuration pane displays information about the setup of the network interface cards (NIC) for the node.
Table 8. Network interface card information Column Device Definition The devices in the NIC. v Eth0 is the node port that communicates with the ProtecTIER Manager workstation v Eth1 and Eth2 are the node ports used in the cluster-internal network v Bond0 is the virtual bond master device to which Eth1 and Eth2 are enslaved Bond devices are defined as part of the installation process. IP Address Usage IP address of the device. Indicates whether the device is used for the cluster-internal network or to communicate with the ProtecTIER Manager workstation and the external network. The master device or bond device, if any, to which the device is enslaved. Indicates whether the device is functioning properly. The supported speed of data transfer across the device in Megabits per second. Configured maximum transmission unit for the device.
General
The VT service monitoring screen displays the General tab by default. The General tab displays information about the selected library.
87
The General tab consists of the following panes: v Library front-end v ProtecTIER VT overview on page 89 v Configuration on page 89 v Library type on page 89
Library front-end
The Library front-end pane displays the virtual robots and tape drives assigned to each port of each node in your ProtecTIER system.
Table 9. Virtual robots and tape drive Column Node Port Top. Definition The node on which the virtual device is assigned. The port within the node on which the virtual device is assigned. The Fiber Channel topology of the port. Possible values: v Point-to-point (P2P) v Fiber channel-arbitrated loop v Down There is no fiber channel connection WWN LUN The Worldwide Name of the port. The logical unit number of the robot or tape drive relative to the port.
88
Table 9. Virtual robots and tape drive (continued) Column Device Throughput Definition The name of the robot or tape drive. The rate of data transfer across the device.
Note: Change the device assignments for your libraries by clicking Re-assign devices. (For more information, see Reassigning devices on page 62.)
ProtecTIER VT overview
The ProtecTIER VT overview pane displays general information about the performance of the selected library for Read and Write operations, including the following: v v v v Status of each tape drive Rate of data transfer in Mbps Number of I/O operations per second Number of active tape drives
Each tape drive in the library is graphically represented. If the drive is currently writing, an orange square is displayed on the graphic. If the drive is currently reading, a blue icon is displayed. Hovering your cursor over the graphic displays the drive number, the current read/write rate of the drive in Mbps, and the percentage of time that the tape drive is idle during backup operations due to low backup application data transfer rates.
Configuration
The Configuration pane displays the current number of drives, slots, import/export slots, and cartridges in the selected library. Note: Change the number of devices in the library by clicking Edit to open the Change dimensions wizard. (For more information, see Editing library parameters on page 58.)
Library type
The Library type pane displays the definition for the emulated virtual library type, including the vendor name, product name, and revision number.
Drives
The Drives tab displays detailed information about the virtual tape drives in the selected library.
89
is displayed. Vendor Name Product Revision Node Port LUN Serial Address Barcode The vendor whose product the virtual drive emulates The product name for the product that the virtual drive emulates. The revision number for the product that the virtual drive emulates The node to which the drive is assigned The port on the node to which the drive is assigned The drives logical unit number relative to the port The drives serial number The drives address within the library If the drive is loaded with a cartridge, this column displays the cartridges barcode
90
Capacity
91
Data Size
Imports/Exports
TheImports/Exports tab displays detailed information about the import/export slots in the selected library.
92
Capacity
Data Size
93
From the shelf, cartridges can be moved to a librarys import slot, replicated to another repository, or be deleted. Cartridges can also be automatically moved to a librarys import slot through the visibility switching process. A cartridge that is moved to an export slot is automatically displaced to the shelf.
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
94
2. Type ./analyze_sessions. An output file containing statistics for the recent backup sessions is generated at the following location: /ptwork/<server name>-<date>-<time>.csv The following statistical information is included.
Table 14. Recent backup session statistics Statistic Total data (TB) Total data (KB) System change rate Description Total amount of data backed-up during the session, in terabytes. Total amount of data backed-up during the session, in kilobytes. Percentage of data in the backup session recognized as changed relative to the previous backup session. The ratio of the quantity of actual backed-up data over the total amount of physical data. Start time of the backup session. End time of the backup session.
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
95
96
ptmon
The following section describes how to query the ProtecTIER server through the CLI using ptmon. The ptmon is loaded during the installation of ProtecTIER software and is located in the / opt/dtc/app/sbin/ directory. Make sure you are in this directory when running ptmon commands from the command prompt.
Usage
Use the ptmon command to query the system via the command line interface (CLI), and to receive various statistics about the ProtecTIER system. This information can provide valuable insight to the administrator on the performance, capacity, configuration and operation of the system, and can be accessed by other management applications. You can print the usage information message by running ptmon with no arguments. The usage information message will also be printed when the arguments list is malformed. The ptmon command is issued from the command line as follows: ./ptmon <-parameter> <variable>
Parameters
-repository Displays repository statistics. -libs Displays information about the unique ID of all configured libraries on the repository. -libinfo -libid library id Displays statistics on the configured tape drives of a specific library. -ncarts -libid library id Displays statistics on the number of configured cartridges of a specific library. -cartsinfo -libid library id -from first cartridge index -count number of cartridges Displays statistics for each of the cartridges in a specified range. -node_vtl_statistics -hours hours Displays the statistics history on the local host for the last <hours> hours.
97
-version Displays the version of the build of the local ProtecTIER installation. pt-version is the major version release.
PTmon responses
PTmon responses always appear in a well structured XML document printed. The XML always has the same root element: response with attribute status which may have the values success or failed. The response element displays the reply as a child element on success and, in this case, returns an exit code of zero to the shell. If status is failed the response element has a single child element: error with attributes description (a human readable string) and a non-zero code value. The same value is returned to the shell. The code value is also returned as the PTmon exit code and enables grouping of errors to general types (RPC error, argument error, etc.)
Example - on success
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <libraries-list host-name="somehostname" time="1235485682" time-string="24-Feb-2009 16:28"> <library name="somehostname_vt" unique-id="2199023256193"/> </libraries-list> </response>
Example - on error
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="failed"> <error code="2" description="Error: failed to execute GetStatisticsSamples"/> </response>
ptmon -repository
This command generates the following repository statistics:
Table 15. Repository command statistics Field current-factoring-ratio Description Current factoring ratio in the repository which is the nominal data divided by the physical data. Amount of unused space in the repository in MB. Amount of nominal data that in the repository in MB. Amount of physical storage configured for the repository in MB.
98
Table 15. Repository command statistics (continued) Field repository-used-physical-storage-mb repository-allocable-physical-storage-mb Description Amount of physical storage used by the repository in MB. Amount of physical storage available for the repository in MB.
Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <repository-statistics current-factoring-ratio="1.00" host-name="beast" repositoryallocablephysical-storage-mb="49152" repository-free-physical-storage-mb="49152" repositorytotalnominal-storage-mb="0" repository-total-physical-storage-mb="49152" repository-usedphysicalstorage-mb="0" time="1236210447" time-string="04-Mar-2009 18:47"/> </response>
ptmon -libs
This command displays information about the unique ID of all configured libraries on the repository. This library unique ID can be later used for receiving detailed information about each of the configured libraries.
Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <libraries-list host-name="beast" time="1236210637" time-string="04-Mar-2009 18:50"> <library name="2" unique-id="2199023255719"/> <library name="20" unique-id="2199023255824"/> </libraries-list> </response>
99
Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <library-info host-name="beast" library-name="2" library-unique-id="2199023255719" numtotaldrives="12" time="1236210783" time-string="04-Mar-2009 18:53"> <active-drives/> </library-info> </response>
Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <library host-name="beast" num-configured-cartridges="5" time="1236210795" time-string="04Mar-2009 18:53" unique-id="2199023255719"/> </response>
ptmon -cartsinfo -libid <library id> -from <first cartridge index> -count <number of cartridges>
This command displays statistics for each of the cartridges in a specified range: v Cartridge barcode v Indication of whether the cartridge is full v Total amount of nominal data currently on the cartridge
Table 18. Statistics of the cartridges in a specified range Field libid from Description Library unique ID taken from -libs output. Number of cartridges before the first printed cartridges in the sorted list of cartridges (by barcode). Maximum number of cartridges in the output. This list may be shorter if the sorted list of cartridges is exhausted before printing <number of cartridges> cartridges.
count
100
Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <cartridges-information host-name="beast" library-unique-id="2199023255719" time="1236210879" time-string="04-Mar-2009 18:54"> <cartridge barcode="000000" early-warning-reported="false" nominal-size-mb="0"/> <cartridge barcode="000001" early-warning-reported="false" nominal-size-mb="0"/> <cartridge barcode="000002" early-warning-reported="false" nominal-size-mb="0"/> <cartridge barcode="000003" early-warning-reported="false" nominal-size-mb="0"/> <cartridge barcode="000004" early-warning-reported="false" nominal-size-mb="0"/> </cartridges-information> </response>
Figure 55. ptmon -cartsinfo -libid <library id> -from <first cartridge index> -count <number of cartridges> outputf
101
Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <statistics num-returned="4"> <chronicle n-samples-per-poll="30" sample-date="04-03-2009 18:00:32" sample-timeseconds=" 30"> <vtl-overall num-active-tapes="0" num-reading-tapes="0" num-writing-tapes="0" readio. average-bytes="0" read-io.max-bytes="0" read-io.min-bytes="0" valid="true" writeio. average-bytes="0" write-io.max-bytes="0" write-io.min-bytes="0"/> </chronicle> <chronicle n-samples-per-poll="30" sample-date="04-03-2009 18:15:33" sample-timeseconds=" 30"> <vtl-overall num-active-tapes="0" num-reading-tapes="0" num-writing-tapes="0" readio. average-bytes="0" read-io.max-bytes="0" read-io.min-bytes="0" valid="true" writeio. average-bytes="0" write-io.max-bytes="0" write-io.min-bytes="0"/> </chronicle> <chronicle n-samples-per-poll="30" sample-date="04-03-2009 18:30:34" sample-timeseconds=" 30"> <vtl-overall num-active-tapes="0" num-reading-tapes="0" num-writing-tapes="0" readio. average-bytes="0" read-io.max-bytes="0" read-io.min-bytes="0" valid="true" writeio. average-bytes="0" write-io.max-bytes="0" write-io.min-bytes="0"/> </chronicle> <chronicle n-samples-per-poll="30" sample-date="04-03-2009 18:45:35" sample-timeseconds=" 30"> <vtl-overall num-active-tapes="0" num-reading-tapes="0" num-writing-tapes="0" readio. average-bytes="0" read-io.max-bytes="0" read-io.min-bytes="0" valid="true" writeio. average-bytes="0" write-io.max-bytes="0" write-io.min-bytes="0"/> </chronicle> </statistics> </response>
ptmon -version
This command displays the version of the build of the local ProtecTIER installation. pt-version is the major version release
Example
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <response status="success"> <version-info> <version build="0.0.0" pt-version="2.2.0.TEST1"/> </version-info> </response>
102
ptcli
The following section describes how to query the ProtecTIER server through the CLI using ptcli. The ptcli is loaded during the installation of ProtecTIER software. Make sure you are in this directory when running ptcli commands from the command prompt.
Usage
Use the ptcli command to query the system via the command line interface (CLI), receive various statistics about the ProtecTIER system, and issue commands as available in the interface. This information can provide valuable insight to the administrator on the performance, capacity, configuration and operation of the system, and can be accessed by other management applications. The ptcli command is issued from the command line as follows: ./ptcli <--parameter> <--server options> <--parameter options> <variables> <-processing options>
103
robot <X, Y> Specify a list of robot assignments in the form of X, Y (for example, X=node external IP address and Y=port). drivemodel <NAME> Specify the tape drive model (taken from the DriveModels output). drives <X, Y, Z> Specify a list of drive assignments in the form of X, Y, Z (for example, X=number of drives, Y=node external IP address, Z=port). Cartridgeinfo Prints information about specific cartridges in the library. The list is sorted by barcode. name <NAME> Specify the library name (taken from the Libraries output). from <NUM> Specify the number of cartridges before the first printed cartridge in the list of cartridges (taken from the NumberofCartridges output). count <NUM> Specify the maximum number of cartridges in the output. CreateRepository Creates a new repository on a node. name <NAME> Specify the repository name. system <NAME> Specify the system name. peak <NUM> Specify the maximum number of cartridges in the output. ratio <NUM> Specify the deduplication ratio. raid <X, Y, Z> Specify the meta-data raid configuration in the form of X, Y, Z (for example, X=Type, Y=Members, Z=Disk size in gigabytes take from the RaidConfigurations output). metadata <MOUNT_POINTS> Specify a list of GFS mounted file systems that will be used to store ProtecTIER repository meta-data. This is optional. userdata <MOUNT_POINTS> Specify a list of GFS mounted file systems that will be used to store ProtecTIER repository users data. This is optional. DriveModels Prints information about the supported tape drive models. libtype <NAME> Specify the library type. Libraries Prints the list of libraries on the repository. LibraryInfo Prints information about a specific library in the repository.
104
name <NAME> Specify the library name (take from the Libraries output). Librarytypes Prints information about the supported library types. NodeVtlStatistics Prints the statistics history about the local host. hours <NUM> Specify the number of statistics hours included in the output. By default, the output should include four chronicles (statistics records) per hour (if uptime is greater than or equal to hours). NumberofCartridges Prints the number of cartridges in a library. name <NAME> Specify the library name (taken from Libraries output). RaidConfigurations Prints information about the supported raid configurations. Rpositorystatistics Prints the repository statistics. ServerVersion Prints the server version.
Server options
Server options are used for connection to the management server. Note: Administrator privileges are required for configuration operations. ip <IP> Specify the IP address of the management server. port <PORT> Specify the port of the management server. This is optional. The default is: 3501. username <NAME> Specify the username for the login. password <PASSWORD> Specify the password for the login. force Force the login if another administrator is already logged in. This is optional.
Processing options
You can specify the following processing options at the end of the command string: d <debug level> Specify the debug level to print log messages to the console. Choices for the debug level are as follows: v SEVERE v WARNING
Chapter 10. Managing and monitoring ProtecTIER through the CLI
105
v ALL f <logfile> Specify the name (with full path) to use for the log file name. The default is: c:\Documents and Settings\hanoch\cli0.log . h v Prints this message and exits. Prints the version information and exits.
ptcli responses
ptcli responses always appear in a well structured XML document printed. The XML always has the same root element: response with attribute status which may have the values success or failed. The response element displays the reply as a child element on success and, in this case, returns an exit code of zero to the shell. If status is failed the response element has a single child element: error with attributes description (a human readable string) and a non-zero code value. The same value is returned to the shell. The code value is also returned as the PTmon exit code and enables grouping of errors to general types (RPC error, argument error, etc.)
Examples - on failure
Calling to DriveModels without --libtype
<?xml version="1.0" encoding="UTF-8" ?> <response status="failed"> <error code="3" description="Missing required option --libtype" /> </response>
Examples - on success
Success of Configuration Operations The XML for all configuration operation is the same, the only different is the name.
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <command host-name="beast" host-time="1243147115" host-time-string="24-May-2009 09:38" local-time="1243146789" local-time-string="24-May-2009 09:33" name="AddLibrary" /> </response>
106
--password ptoper
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <repository-statistics current-factoring-ratio="1.00" host-name="mir" repository-allocable-physical-storage-mb="724992" repository-free-physical-storage-mb="724992" repository-total-nominal-storage-mb="0" repository-total-physical-storage-mb="724992" repository-used-physical-storage-mb="0" host-time="1243147611" host-time-string="24-May-2009 09:46" local-time="1243147285" local-time-string="24-May-2009 09:41"/> </response>
./ptcli LibraryInfo --ip 168.159.151.62 --username ptoper --password ptoper --name Pisa_Parma_24X7 without active drives
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <library-info host-name="parma" library-name="Pisa_Parma_24X7" library-unique-id="2199023265953" num-total-drives="30" host-time="1243147611" host-time-string="24-May-2009 09:46" local-time="1243147285" local-time-string="24-May-2009 09:41"> <active-drives num-returned="0" /> </library-info> </response>
./ptcli LibraryInfo --ip 168.159.151.62 --username ptoper --password ptoper --name Pisa_Parma_24X7 with active drives
107
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <library-info host-name="parma" library-name="Pisa_Parma_24X7" library-unique-id="2199023265953" num-total-drives="30" host-time="1243147611" host-time-string="24-May-2009 09:46" local-time="1243147285" local-time-string="24-May-2009 09:41"> <active-drives num-returned="12"> <drive lea="0" loaded-cartridge-barcode="001025" node-id="1" read-rate-mb-per-second="0" write-rate-mb-per-second="4" /> <drive lea="2" loaded-cartridge-barcode="001024" node-id="1" read-rate-mb-per-second="0" write-rate-mb-per-second="5" /> <drive lea="8" loaded-cartridge-barcode="001028" node-id="1" read-rate-mb-per-second="0" write-rate-mb-per-second="3" /> <drive lea="10" loaded-cartridge-barcode="001027" node-id="1" read-rate-mb-per-second="0" write-rate-mb-per-second="2" /> <drive lea="14" loaded-cartridge-barcode="001022" node-id="1" read-rate-mb-per-second="0" write-rate-mb-per-second="5" /> <drive lea="18" loaded-cartridge-barcode="001021" node-id="1" read-rate-mb-per-second="0" write-rate-mb-per-second="8" /> <drive lea="7" loaded-cartridge-barcode="001018" node-id="2" read-rate-mb-per-second="0" write-rate-mb-per-second="6" /> <drive lea="17" loaded-cartridge-barcode="001019" node-id="2" read-rate-mb-per-second="0" write-rate-mb-per-second="6" /> <drive lea="19" loaded-cartridge-barcode="001026" node-id="2" read-rate-mb-per-second="0" write-rate-mb-per-second="4" /> <drive lea="21" loaded-cartridge-barcode="001020" node-id="2" read-rate-mb-per-second="0" write-rate-mb-per-second="5" /> <drive lea="25" loaded-cartridge-barcode="001030" node-id="2" read-rate-mb-per-second="0" write-rate-mb-per-second="0" /> <drive lea="27" loaded-cartridge-barcode="001029" node-id="2" read-rate-mb-per-second="0" write-rate-mb-per-second="4" /> </active-drives> </library-info> </response>
./ptcli NumberOfCartridges --ip 168.159.150.60 --username ptadmin --password ptadmin --force --name Lib1
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <library host-name="mir" name="Lib1" num-configured-cartridges="20" host-time="1243147611" host-time-string="24-May-2009 09:46" local-time="1243147285" local-time-string="24-May-2009 09:41" unique-id="2199023256354" /> </response>
./ptcli CartridgeInfo --ip 168.159.150.60 --username ptadmin --password ptadmin --force --name Lib1 --from 0 --count 200
108
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <cartridges-information host-name="mir" library-name="Lib1" library-unique-id="2199023256354" num-returned="20" host-time="1243147853" host-time-string="24-May-2009 09:50" local-time="1243147527" local-time-string="24-May-2009 09:45"> <cartridge barcode="000000" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000001" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000002" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000003" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000004" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000005" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000006" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000007" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000008" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000009" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000010" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000011" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000012" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000013" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000014" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000015" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000016" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000017" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000018" early-warning-reported="false" nominal-size-mb="0" /> <cartridge barcode="000019" early-warning-reported="false" nominal-size-mb="0" /> </cartridges-information> </response>
./ptcli NodeVtlStatistics --ip 168.159.150.60 --username ptadmin --password ptadmin --force --hours 1
109
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <statistics host-name="mir" num-returned="1" host-time="1243147853" host-time-string="24-May-2009 09:50" local-time="1243147527" local-time-string="24-May-2009 09:45"> <chronicle n-samples-per-poll="30" sample-date="06-05-2009 15:08:15" sample-time-seconds="30"> <vtl-overall num-active-tapes="0" num-reading-tapes="0" num-writing-tapes="0" read-io.average-bytes="0" read-io.max-bytes="0" read-io.min-bytes="0" valid="true" write-io.average-bytes="0" write-io.max-bytes="0" write-io.min-bytes="0" /> </chronicle> </statistics> </response>
./ptcli DriveModels --ip 168.159.150.60 --username ptoper --password ptoper --libtype TS3500
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <drive-models host-name="beast" host-time="1243147853" host-time-string="24-May-2009 09:50" local-time="1243147527" local-time-string="24-May-2009 09:45" num-returned="1"> <drive-model name="ULT3580-TD3" /> </drive-models> </response>
./ptcli RaidConfigurations--ip 168.159.150.60 --username ptadmin --password ptadmin (Requires administrator priviliges)
110
<?xml version="1.0" encoding="UTF-8" ?> <response status="success"> <raid-configurations host-name="beast" host-time="1243148247" host-time-string="24-May-2009 09:57" local-time="1243147921" local-time-string="24-May-2009 09:52" num-returned="18"> <raid-configuration members="2+2" type="FC-10K" /> <raid-configuration members="3+3" type="FC-10K" /> <raid-configuration members="4+4" type="FC-10K" /> <raid-configuration members="5+5" type="FC-10K" /> <raid-configuration members="6+6" type="FC-10K" /> <raid-configuration members="8+8" type="FC-10K" /> <raid-configuration members="2+2" type="FC-15K" /> <raid-configuration members="3+3" type="FC-15K" /> <raid-configuration members="4+4" type="FC-15K" /> <raid-configuration members="5+5" type="FC-15K" /> <raid-configuration members="6+6" type="FC-15K" /> <raid-configuration members="8+8" type="FC-15K" /> <raid-configuration members="2+2" type="SATA-7.2K" /> <raid-configuration members="3+3" type="SATA-7.2K" /> <raid-configuration members="4+4" type="SATA-7.2K" /> <raid-configuration members="5+5" type="SATA-7.2K" /> <raid-configuration members="6+6" type="SATA-7.2K" /> <raid-configuration members="8+8" type="SATA-7.2K" /> </raid-configurations> </response>
111
112
Permission levels
The ProtecTIER system supports the following permission levels: v Administrator has full access to the ProtecTIER system. Note: Only one Administrator can be logged into the ProtecTIER system at a time. If you log in as an Administrator while another Administrator is already logged in, a notification pane is displayed informing you who is logged in and offering to force that Administrator to log out. v Operator can access ProtecTIER Manager monitoring screens and perform the following tasks: Toggle cartridges between read/write and read-only modes. For more information, see Switching cartridges to read-only mode on page 69. Set the HyperFactor mode for libraries. For more information, see Changing the HyperFactor mode on page 125. Reset virtual tape drives and robots. For more information, see Resetting devices on page 127. Unload and moving cartridges from virtual tape drives. For more information, see Unloading and moving cartridges on page 127. v Monitor can only access ProtecTIER Manager monitoring screens. For more information, see Chapter 9, Monitoring ProtecTIER, on page 77.
113
3. In the User name field, enter a username for the account. 4. In the New password field, enter a password for the account. 5. In the Verify password field, reenter the password that you entered in the New password field. 6. In the Permission field, select a permission level.
114
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.
115
116
Click Events Log on the bottom-right of the View pane to view all the events occurring in the ProtecTIER system.
117
The Alerts Log and Events Log dialogs only display information for one node at a time. In addition, the Alerts Log and Events Log dialogs only display up to 200 alert events at one time. Navigate to a previous set of 200 alert events by clicking Previous lines. Navigate to a later set of 200 alert events by clicking Next lines. Note: View the error log directly on a ProtecTIER server by opening the /pt_work/log/vtf_event.log file. View the alerts log by opening the /pt_work/log/vtf_error.log file.
You can continue the wizard without resolving this issue, but it is not recommended.
118
119
4. In Link speed column, click the down-arrow to select a link speed from the dropdown list. The options are as follows: v Auto v 1 GB v 2 GB v 4 GB 5. In the Topology column, click the down-arrow to select a network topology from the dropdown list. The options are as follows: v LOOP - Fibre channel-arbitrated loop v P2P - Point-to-point
120
6. Click Next and Finish. The new port attributes are set.
121
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.
122
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.
123
Note: You must have root permission to use the wwnutil utility. 1. From the node server working directory, type service vtfd stop to stop the ProtecTIER service on the node. 2. Type /opt/dtc/app/util/wwnutil. 3. Type 2 to edit a WWN by port number. 4. Type a port number. 5. Type a node name. 6. Type a port name. 7. Type m to return to the wwnutil main menu. 8. Type 4 and then c to accept the name change. The WWN is changed. 9. Type service vtfd start to restart the node server. After the name change has been confirmed, the list of WWNs reflects the new name, and the name change is no longer registered as a change to the system.
Disabling defragmentation
The ProtecTIER system automatically defragments fragmented repository disk space as a background task at a rate that does not cause the system to slow down. Stop defragmentation to free the resources used by the defragmentation process. 1. Choose Repository > Defragmentation control. The Defragmentation control dialog is displayed. 2. Select Disable defragmentation and click Ok. The Defragmentation control pane closes and defragmentation is disabled. Note: Selecting Enable defragmentation in the Defragmentation control pane resumes system defragmentation.
124
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.
2. Select one of the following options, as directed by IBM Support: v Hyperfactor enabled - HyperFactor operates as normal. v HyperFactor disabled - HyperFactor stops. When you restart HyperFactor, the HyperFactor process proceeds as normal based on the data stored from before HyperFactor stopped. v Baseline - HyperFactor stops factoring incoming data and uses the newly stored non-factored data as the reference for factoring new data after Hyperfactor is resumed. 3. Click Ok. The ProtecTIER VT HyperFactor mode dialog closes and HyperFactor stops.
125
3. Change the trace level settings, as directed by IBM Support. 4. Click Ok. The Set trace levels dialog box closes and the new trace levels are set.
126
Resetting devices
If a virtual robot or tape drive is locked, reset the device to break any existing SCSI reservations on the device. Attention: Resetting a robot or tape drive while the backup application is accessing the library can harm the backup operations. Do not reset a device unless directed to do so by IBM Support.
Resetting robots
1. In the Services pane, select a library. 2. Choose VT > VT Library > Reset robot. A confirmation message box is displayed. 3. Click Yes. The robot is reset.
Unloading cartridges
You must unload a cartridge from its drive to move it to a slot. 1. In the Services pane, select a library. 2. Click the Drives tab. 3. Select a drive that contains a loaded cartridge. . Note: Loaded drives are indicated with 4. Choose VT > VT Drive > Unload drive. A confirmation message box is displayed. 5. Click Ok. The drive is unloaded. Note: Unloaded drives are indicated with .
127
Moving cartridges
To 1. 2. 3. move a cartridge: In the Services pane, select a library. Click the Drives tab. Select a drive that contains an unloaded cartridge. Note: When moving cartridges from a slot, select the Slot tab and select a slot that contains a cartridge. 4. Choose VT > VT Cartridge > Move cartridge. The Move cartridge dialog is displayed.
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.
128
v GFS: fsid=<cluster name>:<file system name>: fatal filesystem consistency error v gfs_controlId[2905]: <file system name> finish: needs recovery jjd 0 nodeid 2 status 1 If any error messages of these types are found, run fsck on the file systems referenced by the error messages using the file systems volume names.
3. Open etc/fstab. 4. Locate the mount points determined using gfs_tool df, and determine the corresponding logical volume names. The following is an example of the fstab entry format:
/dev/<volume group name>/<logical volume name> name> gfs defaults,noatime,nodiratime,noquota /mnt/<mount point 0 0
Running fsck
1. On one of the ProtecTIER nodes, type service vtfd stop to stop the ProtecTIER service. 2. Shut down the stopped node. 3. On the active node, type service vtfd stop. 4. Type service gfs stop to stop the GFS service. 5. Run gfs_fsck <logical volume name> for each of the problematic file systems. 6. Type service gfs start. 7. Type service vtfd start. 8. Restart the inactive node.
129
The Diagnostic results pane displays each element of the ProtecTIER system in one of the following lists: v Positive checks - no errors. v ProtecTIER recoverable errors - has errors that the ProtecTIER system may be able to repair. v Support required errors - has errors that cannot be repaired by the ProtecTIER system without the assistance of IBM Support.
130
In the Category sub-pane, filter the list contents by selecting individual categories. Categories that contain errors of the type ProtecTIER recoverable errors feature an empty checkbox.
131
132
133
Failback policy
Failback is the procedure for replicating back updated cartridges, new or old, from a DR site to the original (restored) production site to bring it up-to-date in case it was down, or to a new production system. If the primary repository was down and has been restored, you can return to working with the production site as the primary site and use the DR site as the remote, or secondary site. Define a failback policy on the remote repository and select all the cartridges that were used for backup during the time the primary repository was down. Note: The cartridges that originally came from the primary site do not need to be replicated because they were not changed at the DR site. The failback policy will transfer the principality of all the cartridges that belonged to the temporary primary repository at the DR site to the restored primary repository at the production site.
134
Click the Save report as... button if you want to save the validation summary report. Click Next to view the validation summary report.
135
2. Enter DR mode as described in Entering disaster recovery (DR) mode on page 133. 3. Run the Repository takeover wizard. Via the Grids Management view, select Grid > Repository takeover. Select the Unrecoverable repository from the drop-down list and select the new repository that you added to the grid as the Replacing repository (the new repository should appear in the drop-down list). Click Ok. Note: This operation is not reversible.
When you run the Repository takeover wizard, the Grid Manager will internally do the following: a. Delete the current grid pair between the unrecoverable primary site and remote site (if you have not done this previously on your own). b. Remove the unrecoverable repository from the grid. c. Create a pair between the replacing repository at the new primary site and the remote site. d. Define a failback policy on the remote repository and add all the cartridges to the policy that you would like to be at the new primary site. For more information, see Creating a failback policy on page 134. Since you have replaced the primary repository with a new one, the failback policy will change the principality of the failed back cartridges to the new repository, even if the corrupted primary site was the owner, as opposed to the DR site being the owner. e. Complete the procedure as describe in Completing failback and leaving DR mode on page 135.
136
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.
137
backup image end time. This will indicate that the cartridge contains all the required data for this recovery operation. Otherwise, you will have to use a previous full backup image for recovery.
You may have a case where the cartridge sync point is after the backup start time, but before the end of the backup. This may happen in cases where replication is working in parallel to the backup. If the backup has many cartridges, the first cartridges may finish replicating before the backup ends and they get a sync point earlier than the backup end time. As such, if the last sync time flag on one (or more) of the cartridges indicates a time later than the backup start time, but earlier than the backup complete time, those cartridges need further inspection. Scan the backup application catalog for each of those cartridges and get the backup start time and the backup complete time. If the last sync time flag on all the cartridges indicates a time later than the backup complete time, your backup image was fully replicated. Remember: When processing the cartridge list to find a complete set of DR tapes, you must keep track of the date/time discrepancies. Compare the date/time values of the source master backup server and the source ProtecTIER system. The destination environment may be in a different time zone or may be set to the incorrect date/time and as such, unreliable. Thus, use the source date/time, rather than the destination sync time when comparing cartridge states to the backup catalog/database. The destination sync time should only be used to determine which cartridges are whole. In addition, there could be a time difference between the source backup server and the source ProtecTIER server. Your Administrator should be aware of the discrepancy, measure it regularly and communicate the delta to the DR Administrator or operator(s). For instance, if the backup server is 2 hours behind, a cartridge may have a sync time that precedes its backup complete time, i.e. it will appear as a previous, old backup. If there is uncertainty regarding the time differences, compare the nominal size of the cartridge to the Catalog/DB value as an additional (not a substitute) layer of verification.
138
Installing the Red Hat Enterprise Linux Advanced Platform operating system
This section provides instructions for installing Red Hat Enterprise Linux Advanced Platform (version x86_64) on the TS7650 Appliance and TS7650G servers for the purpose of disaster recovery.
139
<PrtSc> and select the system from the list that is to be recovered. If the KVM is attached, proceed to Installing RHL, otherwise proceed to Attaching an external keyboard and monitor to the server.
Installing RHL
1. If not already powered on, power on the server. 2. Insert the Recovery DVD into the servers CD-ROM drive. 3. If the server is already powered on, press Ctrl+Alt+Del to reboot the server. Note: When the installation begins, a list of accessible disks is displayed. If any external devices appear in the list, disconnect them before continuing with the installation. (This includes the fibre connections to the QLogic adapters in slots 6 and 7. Label their locations and disconnect them from the server.) 4. When the Press F12 to Select Boot Device option appears on the screen, press F12. (See Figure 86 on page 141.)
140
When the boot sequence finishes, the Select Boot Device window opens and allows you to specify the CD-ROM drive as the first boot device. 5. From the Select Boot Device menu, highlight CD and press Enter. See Figure 87 on page 142. Note: You may be prompted to Select Boot Device more than once. If so, select CD again and press Enter.
141
The server reboots from the CD-ROM drive. 6. On the Red Hat Enterprise Linux 5 install options screen, type the following at the command line boot: prompt and then press Enter: linux ks=cdrom Note: Be sure to enter the command exactly as shown. If the command is entered incorrectly, RHL will not be properly configured to work with ProtecTIER and you will need to restart this procedure at Step 3. See Figure 88 on page 143.
142
7. When prompted, verify that the installation process has not detected any external, backend disks. Disk /dev/sda is the internal disk. If this is the only disk displayed, type YES and press <Enter>. See Figure 89 on page 144. Note: If external disks are detected, label and disconnect the fibre channel cables that are attached to the disks (the fibre connections to the adapters in slots 6 and 7), then type YES and press <Enter>.
143
Note: The Red Hat Linux operating system should only be installed on internal disks. 8. Follow the next flow of screens to review the End User License Agreement. Press <Enter> to proceed to the next screen:
9. Review end user license agreement. 10. Continue pressing <Enter> to read the next page:
144
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:
12. When the installation is complete, the system will restart. During this time, remove the RHL installation DVD from the servers CD-ROM drive. Note: After the reboot completes, a message similar to the one below may display. If so, ignore the message. Memory for crash kernel (0x0 to 0x0) not within permissible range i8042.c: Cant read CTR while initializing i8042 Red Hat Nash version 5.1.19.6 starting. When the system reboot is complete, you should be at the localhost login prompt.
145
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.
Note: If the following message is displayed, the directory already exists and you can continue to the next command: mkdir: cannot create directory /mnt/cdrom: File exists mount /dev/cdrom /mnt/cdrom The following output is displayed:
mount: block device /dev/cdrom is write-protected. mounting read-only
3. Type the following command to change the current directory to the local installation directory:
cd /mnt/cdrom <Enter>
4. From the CD, locate the following tar file, where <filename> indicates the version number and date: v List the files on the CD from command line: ls <Enter> v Locate the .tar file and copy it to the /install directory on the hard drive. Type the following command to copy the file:
cp <filename>.tar /install <Enter>
146
5. Copy the cman-2.0.85-2.el5.x86_64.rpm file to the /install directory on the hard drive. Type the following command to copy the file:
cp cman-2.0.85-2.el5.x86_64.rpm /install <Enter>
6. Access the /install directory to update the RPM file. Type the following command to change the directory:
cd /install rpm -Uvh <Enter> <Enter>
7. Access the directory to which you copied the tar file (for example, type cd /install). 8. Type the following command to extract the installation files in the /install directory:
tar -xvf <tar filename>.tar <Enter>
The <tar filename> directory is created. 9. Type the following command to change to the <tar filename> directory. Perform the rest of the installation from this directory:
cd /install/<tar filename> <Enter>
Example: <tar filename>=PT_Linux_V2.3.0.0.x86_64 10. Type the following commands to unmount and eject the CD-ROM drive:
umount /dev/cdrom eject /dev/cdrom ./autorun <Enter> <Enter> <Enter>
11. Type the following command: The autorun utility will install the ProtecTIER application. The following message is displayed at the end of the installation:
The system will now reboot!
Press Enter at the prompt to reboot the system. The following message is displayed:
After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue...
12. After the system boots up, set the user to ptadmin by typing the command su - ptadmin (the default password is ptadmin). 13. Change the directories to the /opt/dtc/install directory. From the command line, run the following command:
cd /opt/dtc/install <Enter> <Enter>
The following output is displayed. Note: If you are prompted, enter yes to stop the vtfd service. When prompted to select the node to be replaced, enter the proper node option number. This is especially important when replacing a 2-node system when both nodes are down. Only the valid options for replacement are displayed, i.e. if one of the nodes is running and accessible, only the option of replacing the node that is not running is displayed. In addition, if you are working with a 2-node system, all GFS and vtfd services must be stopped on the second node in order to continue replacing
Appendix A. Recovery procedures
147
the selected node. To stop the GFS and vtfd services on the second node, run the service vtfd stop and service gfs stop commands, respectively.
[root@localhost install]# ./ptconfig -replace -model=TS7650G Gateway Would you like to stop the VTFD service? (yes|no) yes Stopping services, please wait Stopping Cluster Services [ Done ] Services stopped Checking conditions... Checking BOM [ Done ] Checking for existing nodes [ Done ] Comparing mapped devices [ Done ] Checking NICs for Replication [ Done ] In order to continue the GFS & VTFD services on the remote node MUST be stopped. Are the GFS & VTFD services stopped on the remote node? (yes|no) yes Checking repository [ Done ] Checking local raid [ Done ] Checking conditions done Checking live nodes Model <TS7650G> [ Done ]
Option 1 ************************************************** node id : 2 hostname : bilbao ip : 168.159.151.145 Select option: 1 Recoverable static routes configuration found, would you like to restore it? (yes|no) yes Recovering Static Routes [ Done ] Configuring network [ Done ] Configuring Replication Network [ Done ] Restarting Network Service [ Done ] Stopping Remote VTFD [ Done ] Stopping cluster [ Done ] Configuring cluster [ Done ] Starting cluster [ Done ] Installing NTP [ Done ] Mounting file systems [ Done ] Restoring node ID [ Done ] Starting VTFD locally [ Done ] Starting VTFD remotely [ Done ] validation will start in 10 seconds Testing customer network connectivity [ Done ] Testing connectivity to the Default Gateway [ Done ] Getting number of nodes [ Done ] Testing NTP configuration [ Done ] Testing cluster's network speed [ Done ] Testing connectivity to other node in the cluster [ Done ] Testing fence ports [ Done ] Validation is about to execute a fence on 1 node in the cluster, the node will be forcefully shutdown and rebooted To Continue please type "fence test", or "q" to quit: q User aborted validation ended replace ended successfully
Note: Once the configuration is complete, a validation procedure runs automatically. Even if, for some reason, the validation fails, the procedure is not rolled back since the configuration completed successfully. 15. Once the information has been provided, proceed to Chapter 5, Managing nodes and clusters, on page 35 to ensure the node is displayed on the ProtecTIER Manager interface.
148
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.
Note: If the following message is displayed, the directory already exists and you can continue to the next command:
mkdir: cannot create directory '/mnt/cdrom': File exists
3. Type the following command to change the current directory to the local installation directory:
cd /mnt/cdrom <Enter>
4. From the CD, locate the following tar file, where <filename> indicates the version number and date: v List the files on the CD from command line: ls <Enter> v Locate the .tar file and copy it to the /install directory on the hard drive. Type the following command to copy the file:
cp <filename>.tar /install <Enter>
5. Copy the cman-2.0.85-2.el5.x86_64.rpm file to the /install directory on the hard drive. Type the following command to copy the file:
cp cman-2.0.85-2.el5.x86_64.rpm /install <Enter>
6. Access the /install directory to update the RPM file. Type the following command to change the directory:
cd /install <Enter> <Enter>
8. Access the directory to which you copied the tar file (for example, type cd /install). 9. Type the following command to extract the installation files in the /install directory:
tar -xvf <tar filename>.tar <Enter>
149
10. Type the following command to change to the < tar filename> directory. Perform the rest of the installation from this directory:
cd /install/<filename> <Enter>
Example: <filename>=PT_Linux_V2.3.0.0.x86_64 11. Type the following command to unmount the CD-ROM drive:
umount /dev/cdrom <Enter>
12. Type the following command to eject the ProtecTIER installation CD from the CDROM drive:
eject ./autorun <Enter> <Enter>
13. Type the following command: 14. The autorun utility will install the ProtecTIER application. The following message is displayed at the end of the installation:
The system will now reboot!
Press <Enter> at the prompt to reboot the system. The following message is displayed:
After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue...
15. When the localhost login: prompt appears, login as root and type the password: admin 16. Set the user to ptadmin by typing the command su - ptadmin (the default password is ptadmin). 17. Change the directories to the /opt/dtc/install directory. From the command line, run the following command:
cd /opt/dtc/install <Enter>
18. The ProtecTIER configuration command set that is entered next is dependant on the amount of cache that is connected to the server. Use the guidelines below to determine the command to use: v If you are replacing the server on a 32 spindle appliance model, type the following command:
./ptconfig -replace -model=TS7650_DS4700_32_450 <Enter>
v If you are replacing the server on a 64 spindle appliance model, type the following command:
./ptconfig -replace -model=TS7650_DS4700_64_450 <Enter>
v If you are replacing the server on a 128 spindle appliance model, type the following command:
./ptconfig -replace -model=TS7650_DS4700_128_450 <Enter>
The following output is displayed. Note: If you are prompted, enter yes to stop the vtfd service. When prompted to select the node to be replaced, enter the proper node option number. This is especially important when replacing a 2-node system when both nodes are down. Only the valid options for replacement are displayed, i.e. if one of the nodes is running and accessible, only the option of replacing the node that is not running is displayed. In addition, if you are working with a 2-node system, all GFS and vtfd services must be stopped on the second node in order to continue replacing the selected node. To stop the GFS and vtfd services on the second node, run the service vtfd stop and service gfs stop commands, respectively.
150
[root@localhost install]# ./ptconfig -replace -model=TS7650_DS4700_128_450 Would you like to stop the VTFD service? (yes|no) yes Stopping services, please wait Stopping Cluster Services [ Done ] Services stopped Checking conditions... Checking BOM [ Done ] Checking for existing nodes [ Done ] Comparing mapped devices [ Done ] Checking NICs for Replication [ Done ] In order to continue the GFS & VTFD services on the remote node MUST be stopped. Are the GFS & VTFD services stopped on the remote node? (yes|no) yes Checking repository [ Done ] Checking local raid [ Done ] Checking conditions done Checking live nodes Model <TS7650G> [ Done ]
Option 1 ************************************************** node id : 2 hostname : bilbao ip : 168.159.151.145 Select option: 1 Recoverable static routes configuration found, would you like to restore it? (yes|no) yes Recovering Static Routes [ Done ] Configuring network [ Done ] Configuring Replication Network [ Done ] Restarting Network Service [ Done ] Stopping Remote VTFD [ Done ] Stopping cluster [ Done ] Configuring cluster [ Done ] Starting cluster [ Done ] Installing NTP [ Done ] Mounting file systems [ Done ] Restoring node ID [ Done ] Starting VTFD locally [ Done ] Starting VTFD remotely [ Done ] validation will start in 10 seconds Testing customer network connectivity [ Done ] Testing connectivity to the Default Gateway [ Done ] Getting number of nodes [ Done ] Testing NTP configuration [ Done ] Testing cluster's network speed [ Done ] Testing connectivity to other node in the cluster [ Done ] Testing fence ports [ Done ] Validation is about to execute a fence on 1 node in the cluster, the node will be forcefully shutdown and rebooted To Continue please type "fence test", or "q" to quit: q User aborted validation ended replace ended successfully
Note: Once the configuration is complete, a validation procedure runs automatically. Even if, for some reason, the validation fails, the procedure is not rolled back since the configuration completed successfully. 19. Once the information has been provided, proceed to Chapter 5, Managing nodes and clusters, on page 35 to ensure the node is displayed on the ProtecTIER Manager interface.
151
To replace a two-node system by a single node when using disk-based replication: 1. Connect or verify a USB keyboard and display are connected to the ProtecTIER server. 2. If the server is not already powered on, power it on and allow the boot cycle to complete. 3. When the localhost login: prompt appears, login as root and type the password: admin. 4. Insert the IBM System Storage ProtecTIER Enterprise Edition v2.3 CD and wait for the CD drive to stop blinking. 5. Type the following commands to create and mount the CD-ROM drive:
mkdir /mnt/cdrom
Note: If the following message is displayed, the directory already exists and you can continue to the next command: mkdir: cannot create directory /mnt/cdrom: File exists mount /dev/cdrom /mnt/cdrom The following output is displayed:
mount: block device /dev/cdrom is write-protected. mounting read-only
6. Type the following command to change the current directory to the local installation directory:
cd /mnt/cdrom <Enter>
7. From the CD, locate the following tar file, where <filename> indicates the version number and date: v List the files on the CD from command line: ls <Enter> v Locate the .tar file and copy it to the /install directory on the hard drive. Type the following command to copy the file:
cp <filename>.tar /install <Enter>
8. Copy the cman-2.0.85-2.el5.x86_64.rpm file to the /install directory on the hard drive. Type the following command to copy the file:
cp cman-2.0.85-2.el5.x86_64.rpm /install <Enter>
9. Access the /install directory to update the RPM file. Type the following command to change the directory:
cd /install <Enter>
152
10. Access the directory to which you copied the tar file (for example, type cd /install). 11. Type the following command to extract the installation files in the /install directory:
tar -xvf <tar filename>.tar <Enter>
The <tar filename> directory is created. 12. Type the following command to change to the <tar filename> directory. Perform the rest of the installation from this directory:
cd /install/<tar filename> <Enter>
Example: <tar filename>=PT_Linux_V2.3.0.0.x86_64 13. Type the following commands to unmount and eject the CD-ROM drive:
umount /dev/cdrom eject /dev/cdrom ./autorun <Enter> <Enter> <Enter>
14. Type the following command: The autorun utility will install the ProtecTIER application. The following message is displayed at the end of the installation:
The system will now reboot!
Press Enter at the prompt to reboot the system. The following message is displayed:
After boot, please set user to ptadmin by invoking 'su - ptadmin' (default password is ptadmin). Press <CR> to continue...
15. After the system boots up, set the user to ptadmin by typing the command su - ptadmin (the default password is ptadmin). 16. Change the directories to the /opt/dtc/install directory. From the command line, run the following command:
cd /opt/dtc/install <Enter> <Enter>
153
[root@localhost install]# ./ptconfig -replace -model=<model> -dualBySingle *** NOTICE *** By selecting the dualBySingle option you are converting this node. Once this action is complete this installed node must NEVER be a part of a 2 node Cluster. Converting to dual by single [ Done ] Stopping services, please wait Stopping Cluster Services [ Done ] Services stopped Checking conditions... Checking BOM [ Done ] Checking for existing nodes [ Done ] Checking NICs for Replication [ Done ] Checking repository [ Done ] Checking conditions done Checking live nodes Model <Generic> Option 1 ************************************************** node id : 1 hostname : compy ip : 168.159.150.107 [ Done ]
Option 2 ************************************************** node id : 2 hostname : bunny ip : 168.159.150.135 Select option: 2 Recoverable static routes configuration found, would you like to restore it? (yes|no) yes Recovering Static Routes [ Done ] Configuring network [ Done ] Configuring Replication Network [ Done ] Restarting Network Service [ Done ] Stopping cluster [ Done ] Configuring cluster [ Done ] Starting cluster [ Done ] Installing NTP [ Done ] Mounting file systems [ Done ] Restoring node ID [ Done ] Starting VTFD [ Done ] validation will start in 10 seconds Testing customer network connectivity [ Done ] Testing connectivity to the Default Gateway [ Done ] Getting number of nodes [ Done ] This is a 1 node cluster, will not test fencing validation ended replace ended successfully
Note: Once the configuration is complete, a validation procedure runs automatically. Even if, for some reason, the validation fails, the procedure is not rolled back since the configuration completed successfully.
154
Note: If you are not enabling replication, you do not need to install Grid Manager. Instead, go to Chapter 3, Installing ProtecTIER Manager, on page 27. 1. Log in to the ProtecTIER v2.3 server on which the Grid Manager application will reside: a. Connect a USB keyboard and monitor (if not already present) to the server. b. Verify that the server is powered-on: v If it is powered-on, go to step 2. v If it is not powered-on do so now, wait for the boot cycle to complete, then go to step 2. 2. At the login: prompt, log in with the ID root and the password admin. 3. Insert the IBM System Storage Replication Manager v2.3.0 CD into the servers CD-ROM drive. 4. When the CD-ROM drive light stops blinking, enter the command: mount /dev/cdrom /mnt/cdrom <enter> Note: If you receive the error message: No such file or directory, enter both of the commands below: mkdir /mnt/cdrom <enter> mount /dev/cdrom /mnt/cdrom <enter> The following output displays: mount: block device /dev/cdrom is write-protected. mounting read-only 5. Enter the command: cd /mnt/cdrom 6. Change to the installation directory. Enter the command: cd /Replication_Manager_V2.3.0.0/Linux <enter> 7. Start Grid Manager installation. Enter the following command: ./gm_installLinux64.bin <enter> The following messages display: Preparing to install... Extracting the JRE from the installer archive... Unpacking the JRE... Extracting the installation resources from the installer archive... Configuring the installer for this systems environment... Launching installer... Preparing CONSOLE Mode Installation... The Introduction screen displays. 8. Read the information on the screen, then press <enter> to continue. The Grid Manager Platform menu displays: Please define the type of platform the Grid Manager will run 1- ProtecTIER Node 2- Dedicated Linux server ENTER THE NUMBER OF THE DESIRED CHOICE: 9. Select option 1 and press <enter>. 10. When prompted for the first IP address of the GridManager, type the servers first replication IP address (Eth3) and press <enter>. 11. When prompted for the second IP address of the GridManager, type the servers second replication IP address (Eth4) and press <enter>.
Appendix A. Recovery procedures
155
The Pre-Installation Summary screen displays: Please Review the Following Before Continuing: Product Name: PTGridManager Install Folder: /opt/dtc/PTGridManager Link Folder: /opt/dtc Replication Manager first IP: x.xx.xxx.xxx (The IP address for Eth3) Replication Manager second IP: x.xx.xxx.xxx (The IP address for Eth4) Disk Space Information (for Installation Target): Required: 139,495,067 bytes Available: xxx,xxx,xxx bytes 12. Review the information, then press <enter> to continue. The Ready To Install screen displays: InstallAnywhere is now ready to install PTGridManager onto your system at the following location: /opt/dtc/PTGridManager 13. Press <enter> to start the installation. The Installing message displays. When the installation finishes the Installation Complete screen displays: Congratulations. PTGridManager has been successfully installed to: /opt/dtc/PTGridManager 14. Press <enter> to exit the installer. 15. Eject the CD-ROM from the servers CD-ROM drive. Enter the commands: cd / <enter> eject /dev/cdrom <enter> 16. Go to Chapter 3, Installing ProtecTIER Manager, on page 27.
156
2. Enter the customer name in the Customer name field to provide backup information and click Ok. A message is displayed that the backup .zip file was saved on the Grid Manager server in the /tmp directory. 3. Click Yes if you want to download the backup file to a specific directory or No to close the window. 4. If Yes, browse to the directory in which you want to save the backup configuration file and click Save. The file is saved to the respective directory and the Save window closes.
157
1. Select Grid Manager > Restore grid. The Restore grid dialog is displayed. 2. Choose from one of the options listed to import the grid for analysis: v Import from file browse to the grid.<x>.xml file, if you are restoring a grid from a backup .zip file that has been extracted. v Import from repository enter the Replication IP address of the accessible repository that was previously a member of the grid. 3. Click Analyze grid. The Grid Manager attempts to communicate with the grids members (i.e. repositories). Note: If the running Grid Manager already contains a number of grids, and the restored grid does not match the Grid Manager unique ID, the analyze phase fails and an error is displayed that the imported grid does not belong to the respective Grid Manager.
158
Table 20. Grid analysis messages Message The repository was not accessible Meaning The Grid Manager failed to communicate with the specific repository and could not get the configuration ID. Recommended action Make sure the server status in the repository is up and running and all ports are well configured. Then, analyze the grid again.
Restoration is not recommended. Communication was successful, invalid configuration ID. Additional message follows the configuration is higher or different than expected. This could be caused by a old restored grid data file, an old backup, or a repository that does not belong to this grid. Communication was successful. This could be caused when the specific repository does not communicate with the restored Grid Manager during a new configuration layout. Comparison and validation was successful. None. The new Grid Manager will update the repository with the new configuration layout.
Empty message
Before restoring a grid, you can preview the grid layout by clicking on the Grid preview tab.
159
If all the repositories are accessible and validated successfully, click Restore. Continue restoring the remaining grids, if available.
160
Creating partitions
Create one partition on each device on the storage disk. Note: Your storage disk must be configured with the number of devices equal to the number of file systems you must create. 1. Log into a ProtecTIER node server. Open a Secured Shell (SSH) session to the node and log in using the user ID: root and password: admin. 2. From the command line, enter multipath -l. You receive a list of multipath devices in a format similar to the following:
# multipath -l mpath2 (3600a0b8000422e7200000536482c7a90) dm-10 IBM,1814 [size=4.1T][features=0][hwhandler=1 rdac] \_ round-robin 0 [prio=0][active] \_ 2:0:0:7 sdt 65:48 [active][undef] \_ round-robin 0 [prio=0][enabled] \_ 4:0:0:7 sdak 66:64 [active][undef] mpath23 (3600a0b8000421b2800000558483d8d4b) dm-15 IBM,1814 [size=1.0G][features=0][hwhandler=1 rdac] \_ round-robin 0 [prio=0][active] \_ 1:0:0:1 sdb 8:16 [active][undef] \_ round-robin 0 [prio=0][enabled] \_ 3:0:0:1 sdh 8:112 [active][undef] mpath1 (3600a0b8000422e7200000541482c7ae3) dm-13 IBM,1814 [size=4.1T][features=0][hwhandler=1 rdac]
Copyright IBM Corp. 2008, 2009
FAStT
FAStT
FAStT
161
\_ round-robin 0 [prio=0][active] \_ round-robin 0 [prio=0][active] \_ 2:0:0:9 sdy 65:128 [active][undef] \_ round-robin 0 [prio=0][enabled] \_ 4:0:0:9 sdao 66:128 [active][undef] mpath22 (3600a0b8000421b2800000556483d8d0f) dm-8 IBM,1814 [size=835G][features=0][hwhandler=1 rdac] \_ round-robin 0 [prio=0][active] \_ 1:0:0:11 sdaq 66:160 [active][undef] \_ round-robin 0 [prio=0][enabled] \_ 3:0:0:11 sdai 66:32 [active][undef] mpath0 (3600a0b8000421b6400000597482c9341) dm-21 IBM,1814 [size=4.1T][features=0][hwhandler=1 rdac] \_ round-robin 0 [prio=0][active] \_ 1:0:0:4 sdp 8:240 [active][undef] \_ round-robin 0 [prio=0][enabled] \_ 3:0:0:4 sdo 8:224 [active][undef]
FAStT
FAStT
Each device is named mpathN, where N is a number and can be found on the system as /dev/mapper/mpathN. 3. Enter parted /dev/mapper/<mpath device name> to start the Parted Partition Manipulation utility on the selected device. The following is displayed:
# parted /dev/mapper/mpath2 GNU Parted 1.8.1 Using /dev/mapper/mpath2 Welcome to GNU Parted! Type 'help' to view a list of commands. (parted)
4. Enter mklabel gpt to create a new disk label (partition table). Note: Always answer Yes when you receive the prompt Do you want to continue? 5. Enter print to display the partition table. The following device attributes are displayed:
(parted) mklabel gpt (parted) print Model: Linux device-mapper (dm) Disk /dev/mapper/mpath2: 1000MB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags
(parted)
6. Enter mkpart primary <start> <end> to create a primary partition beginning at <start> and ending in <end>, in megabytes. If the previous print command showed a size in GB, specify <end> with a GB suffix for a size in gigabytes. A primary partition and a device named /dev/mapper/mpathNp1 are created. 7. Enter quit to exit the Parted utility. 8. Enter the following command to present the new partition to the operating system:
kpartx -a /dev/mapper/mpathN
9. Repeat steps 3 through 7 to create additional partitions until you have created one partition on each device.
162
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
2. Type vgscan to view the list of volume groups. The volume group that you created is displayed in the list:
# vgscan Reading all physical volumes. This may take a while... Found volume group VG1 using metadata type lvm2
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.
163
Attention: You must set the last file system parameter to zero. Setting the last parameter to another value will automatically run fsck at GFS file system startup which can result in corruption of the file system. 2. Type mount -a to mount all the file systems listed in /etc/fstab.
164
v v v v v
Adding the physical volume to a volume group Expanding the logical volume on page 166 Reactivating the logical volume on page 166 Mounting the file system on page 166 Expanding the GFS file system on page 166
Creating a partition
Create a partition for each file system that you want to expand. For more information, see Creating partitions on page 161.
165
2. Type pvscan to view the list of physical volumes. The physical volume path should include /dev/<device name>.
166
3. In a cluster, disconnect the Ethernet cable from the RSA port on Server A. 4. On the laptop, click Start->Control Panel. 5. Double-click Network Connections.
Copyright IBM Corp. 2008, 2009
167
7. From the list, select Internet Protocol (TCP/IP), then click Properties. See Figure 97.
168
8. Select Use the following IP address. 9. In the IP Address field, type: 172.31.1.14, and in the Subnet mask field, type: 255.255.255.0. 10. Click OK, then click Close to exit the Local Area Connections Properties window. 11. In a cluster, reconnect the Ethernet cable to the RSA port on Server A. 12. On the TSSC or service laptop, open an Internet Explorer window. 13. In the Address Bar area of the browser window, type the default RSA port IP address: 172.31.1.254 and then press <Enter>. 14. In the Login window, enter USERID as the username and PASSW0RD (with a zero) as the password, and then click OK. Note: The username and password are case sensitive and must be entered in all uppercase. The Remote Supervisor Adapter II Refresh 1 Welcome window opens. 15. In the Remote Supervisor Adapter II Refresh 1 Welcome window: a. Use the Inactive session timeout value drop-down list to specify a reasonable amount of time which will keep your session active until you can complete your task. Do not select No Timeout, as this will prevent anyone else from logging into the RSA until you have logged out. b. Click Continue. See Figure 98.
You are now logged into the servers RSA. 16. Go on to Enabling Remote Control on page 170.
169
Figure 99. Remote Supervisor Adapter II Refresh 1 window: Remote Control link
2. In the Remote Control window, click Start Remote Control in Single User Mode. See Figure 99. The ASM Remote Control window opens. Note: If your laptop is configured to block pop-ups, temporarily disable this function. Accept any Java versions that may appear on the screen, as well as any Windows security prompts displayed as a result of trying to open this window.
170
171
172
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.
173
174
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATIONS AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been
175
estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBMs future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: v v v v v v v v v v v v v v v v v v AIX DS4000 Enterprise Storage Server ESCON FICON i5/OS iSeries IBM ProtecTIER pSeries S/390 ServeRAID System x System Storage TotalStorage Wake on LAN z/OS zSeries
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ((R) or (TM)), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or
176
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.
Notices
177
178
IBM verndert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne Empfehlung der IBM gesteckt/eingebaut werden. EN 55022 Klasse A Gerte mssen mit folgendem Warnhinweis versehen werden: Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbereich Funk-Strungen verursachen; in diesem Fall kann vom Betreiber verlangt werden, angemessene Mabnahmen zu ergreifen und dafr aufzukommen. Deutschland: Einhaltung des Gesetzes ber die elektromagnetische Vertrglichkeit von Gerten Dieses Produkt entspricht dem Gesetz ber die elektromagnetische Vertrglichkeit von Gerten (EMVG). Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in der Bundesrepublik Deutschland. Zulassungsbescheinigung laut dem Deutschen Gesetz ber die elektromagnetische Vertrglichkeit von Gerten (EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) fr Gerte der Klasse A Dieses Gert ist berechtigt, in bereinstimmung mit dem Deutschen EMVG das EG-Konformittszeichen - CE - zu fhren. Verantwortlich fr die Konformittserklrung des EMVG ist die IBM Deutschland GmbH, 70548 Stuttgart. Generelle Informationen: Das Gert erfllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A.
179
IBM Taiwan Product Service Contact Information: IBM Taiwan Corporation 3F, No 7, Song Ren Rd., Taipei Taiwan Tel: 0800-016-888
Power cords
For your safety, IBM provides a power cord with a grounded attachment plug to use with this IBM product. To avoid electrical shock, always use the power cord and plug with a properly grounded outlet. IBM power cords used in the United States and Canada are listed by Underwriters Laboratories (UL) and certified by the Canadian Standards Association (CSA). For units intended to be operated at 115 volts: Use a UL-listed and CSA-certified cord set consisting of a minimum 18 AWG, Type SVT or SJT, three-conductor cord, a maximum of 15 feet in length and a parallel blade, grounding-type attachment plug rated 15 amperes, 125 volts. For units intended to be operated at 230 volts (U.S. use): Use a UL-listed and CSA-certified cord set consisting of a minimum 18 AWG, Type SVT or SJT, three-conductor cord, a maximum of 15 feet in length and a tandem blade, grounding-type attachment plug rated 15 amperes, 250 volts. For units intended to be operated at 230 volts (outside the U.S.): Use a cord set with a grounding-type attachment plug. The cord set should have the appropriate safety approvals for the country in which the equipment will be installed. IBM power cords for a specific country or region are usually available only in that country or region.
180
f2c00790
Index A
about this document xi sending comments xvi accessibility 173 adding cartridges 67 cluster members 122 nodes 35 nodes to a subnetwork 36 physical volumes to volume groups 165 user accounts 113 administrator default password 31 role 113 alerts SNMP 19 alerts log 117 configuration cluster setup 2 one node system 2 two node system 2 creating file systems 39, 161 libraries 50 partitions 161 zones 49 creating file systems fsCreate 39 errors recoverable errors 19 unrecoverable errors 19 establishing installation directory 146 events log 117 expanding file systems 161 logical volumes 166 repositories 41
D
data de-duplication 1 de-duplication 1 deactivating logical volumes 165 defragmentation disabling 124 deleting cartridges 68 libraries 70 repositories 42 user accounts 113 device reassigning 62 resetting 127 disabling compression 125 defragmentation 124 Disaster recovery replace dual node by single documentation improvement xvi dumping trace buffer 126
F
fields implemented SNMP 19 file system creating 39, 161 expanding 161 unmounting 165 volume name 129 fsck error check 128 running 129 fsCreate creating file systems 39 fsCreate parameters 40
B
backup catalog 136 backup monitoring 94
C
cartridge adding 67 deleting 68 managing 66 moving 128 read-only mode 69 read/write mode 69 switching modes 69 unloading 127 cartridge drive reassigning 62 changing HyperFactor mode 125 worldwide names 123 checking errors 130 cluster cluster member monitoring, see cluster member 79 disk space monitoring 78 fibre channel port throughput monitoring 79 general monitoring 77 overview 35 VT service monitoring 79 cluster member adding 122 monitoring 79 removing 121 comments, sending xvi completing ProtecTIER setup 7 compression disabling 125
G
152 generating long-term statistics reports problem reports 119 Grid Manager 154 installing 154 119
H
HP-UX host configuring node ports 49 HyperFactor 1 HyperFactor mode changing 125 HyperFactor ratio over time graph 83
E
editing libraries 58 emulation tape library 1 enabling SNMP compatibility 19 SNMP support 19 error checking 130 repairing 131 error check fsck 128 overview 128 ProtecTIER Manager 130 running 130 error message wizards 118 error trap SNMP 19
I
implementing SNMP compatibility 19 installation directory, establishing 146 installing ProtecTIER Manager 27 Installing RAS package 146 introduction 1
K
keyboards accessibility features 173
181
L
library creating 50 deleting 70 editing 58 overview 49 renaming 70 Library library type setting 57 library type information 89 Linux shell backup monitoring 94 log alerts 117 events 117 log in as root 146 logging in 31 logging out 31 logical volume deactivating 165 expanding 166 reactivating 166 long-term statistics report generating 119
monitoring (continued) repository configuration 81 repository disk space 81 repository factoring ratio 81 repository HyperFactor 83 repository IOPS 81 repository nominal data size 81 repository storage 82 repository used space 81 robots 88 slots 92 tape drives 88 VT service 87 VT service for clusters 79 VT service libraries 89 moving cartridges 128
N
Navigation pane refreshing 32 node adding 35 adding replication 14 adding to a subnetwork 36 changing worldwide names 123 configuring ports for HP-UX hosts 49 general monitoring 86 network configuration monitoring 87 overview 35 port monitoring 86 port scanning 86 removing 36 scanning ports 86 updating ProtecTIER 9, 11 version information 86 node configuration one node 2 two nodes 2 nominal data size graph 82
M
machine types xi management tools SNMP 19 managing cartridges 66 clusters 35 nodes 35 repositories 37 user accounts 113 marginal HyperFactor ratio graph 83 message area 118 MIB definition file 19 MIB-2 SNMP 19 model numbers xi modifying port attributes 120 trace buffer 125 monitor default password 31 role 113 monitoring backup operations 94 cartridges 91 cluster disk space 78 cluster members 79 cluster VT service 79 clusters 77 drives 89 fibre channel port throughput 79 HyperFactor 83 imports/exports slots 92 library configuration 89 network configuration 87 nodes 86 port attributes 86 ProtecTIER 77 repositories 80
planning repository expansion 37 Policy creating 45 disable 46 enable 46 modifying 47 running 47 port attributes, modifying 120 attributes, monitoring 86 configuring for HP-UX hosts prerequisites ProtecTIER Manager 27 printing data 32 problem report generating 119 ProtecTIER monitoring 77 package, unpacking 146 updating 9, 11 ProtecTIER Manager installing 27 overview 6 prerequisites 27 refreshing 32 uninstalling 30 ProtecTIER setup completing 7
49
R
RAS installation 146 reactivating logical volumes 166 reader feedback, sending xvi reassigning cartridge drives 62 devices 62 robots 62 reboot error 19 recovery cartridge status 136 Recovery Procedures 139 refreshing 32 reloading a node 139 removing cluster members 121 nodes 36 renaming libraries 70 repairing errors 131 Replace, dual node by single Disaster recovery 152 Replication adding 14 creating a policy 45 disabling a policy 46 enabling a policy 46 modifying a policy 47 policies 43 running a policy 47 timeframe setting 44
O
operator default password 31 role 113 overview checking errors 128 ProtecTIER Manager 6 repository expansion 37 troubleshooting 117
P
partition creating 161 password default 31 permission levels default accounts 31 overview 113 physical volume adding to volume groups
165
182
replication timeframe setting 44 repository configuration monitoring 81 deleting 42 disk space monitoring 81 expanding 41 expansion overview 37 expansion planning 37 factoring ratio monitoring 81 general monitoring 80 HyperFactor monitoring 83 HyperFactor ratio over time graph 83 IOPS monitoring 81 managing 37 marginal HyperFactor ratio graph 83 nominal data size graph 82 nominal data size monitoring 81 planning an expansion 37 storage monitoring 82 used space monitoring 81 utilization graph 82 resetting devices 127 robots 127 tape drives 127 trace buffer 127 restart error 19 restoring grid manager analysis 157 robot monitoring 88 reassigning 62 resetting 127 RSA connection 167 running error checks 130 fsck 129
T
tape drive monitoring 88 resetting 127 tape library 1 TCP/IP network 36 terminology xi timeserver updating 24 trace buffer dumping 126 modifying 125 resetting 127 setting levels 126 Trademarks 176 traps SNMP 19 troubleshooting overview 117 tasks 124
W
warning notification trap SNMP 19 Wizard error messages 118 Wizard message area 118 worldwide name changing 123
U
uninstalling ProtecTIER Manager 30 unloading cartridges 127 unmounting file systems 165 unpacking ProtecTIER package 146 updating nodes 9, 11 ProtecTIER 9, 11 user account adding 113 deleting 113 overview 113 username default 31 utilization graph 82
S
saving data 32 sending comments xvi setting trace buffer levels 126 SNMP alerts 19 compatibility, enabling 19 compatibility, implementing 19 error trap 19 fields implemented 19 management tools 19 MIB-2 19 support, enabling 19 traps 19 warning notification trap 19 static routes routing, replication 15 subnetworks 36 switching modes cartridges 69
V
version information 86 View pane refreshing 32 Virtual Tape service, see VT service 1 volume group adding physical volumes 165 volume name of file systems 129 VT service 1 cartridge monitoring 91 clusters monitoring 79 drives monitoring 89 general monitoring 87 imports/exports slots monitoring 92 library configuration monitoring 89 library monitoring 89 library type information 89 overview 49 robot monitoring 88 slots monitoring 92 tape drive monitoring 88
Index
183
184
Printed in USA
GC53-1156-03