1. Look through data for similarity New Data Stream 2. Read elements that are most similar 3. Diff reference with version will use multiple elements

Element A

Element B

Element C

4. Matches factored out - unique data added to repository
Figure 1-4 HyperFactor data deduplication
HyperFactor data deduplication uses a 4 GB Memory Resident Index to track similarities for up to 1 PB of physical disk in a single repository. Depending on the data deduplication ratio for your data, you could store much more than 1 PB of data on your disk array, for example, with a ratio of 12 to 1, you could store 12 PB on that 1 PB of disk array. With the Memory Resident Index, HyperFactor can identify potentially duplicate data quickly for large amounts of data and does this on data ingest, or inline, reducing the amount of processing required for your data. The read-back rate of the ProtecTIER native replication technology is generally faster than the write rate to the system, because there is no risk of fragmentation, and no access to the index or heavy computation is required during a restore activity. It just requires you to open metadata files and fetch the data according to the pointers that they contain.
1.3 Data deduplication processing
Data deduplication can either be performed while the data is being backed up to the storage media (inline) or after the data has been written to the storage media (post-processing).

1.3.1 Inline method

Inline data deduplication is not dependent on the type of data deduplication used. An advantage of inline data deduplication is that the data is only processed once and there is no additional processing after the backup window. Inline data deduplication requires less disk storage because the native data is not stored prior to data deduplication. Depending on the implementation, a disadvantage of inline data deduplication is that the data deduplication processing could slow down the backup data stream. Algorithms used for data deduplication can be CPU intensive and data deduplication might require additional read or write access if the index is disk based.

Set HyperFactor mode Sets HyperFactor mode on (default) or off. This must be used only at the direction of IBM Support. HyperFactor is the IBM technology
that deduplicates data inline as it is received from the backup application. Reset robot Set library type Set compression type Resets the status of the virtual medium changer. Sets library type to a supported virtual library. Sets compression on or off. Under normal circumstances when turned on, the ProtecTIER system compresses data.

Virtual drives

For virtual drives, you have these options: Unload drive Reset drive Unloads a virtual cartridge to allow the cartridge to change visibility from the virtual drive to another location Resets the status of the drive

Virtual cartridges

For virtual cartridges, these options are available: Add cartridge Move cartridge Creates additional virtual cartridges. Changes visibility of a cartridge to a virtual drive, slot, or import/export slot. This function is normally only used at the direction of IBM Support. Sets cartridge to read/write or read-only. This function is normally only used at the direction of IBM Support. Verifies the metadata for a cartridge. This function is normally only used at the direction of IBM Support. Verifies the data on the cartridge. Note that depending on the size of the cartridge and the amount of data, this can take a significant amount of time. This function is only available on the Slots view.
Read/write cartridge Cartridges metadata verification Cartridges integrity verification
ProtecTIER Manager can be run from the Management console workstation or from your personal workstation. For more information about the ProtecTIER Manager functions and windows refer to Part 3, Implementing and administering the IBM System Storage TS7650G and TS7650 on page 137.
The TS7650G and TS7650 management console workstation
The IBM System Storage TS7650 and TS7650G with ProtecTIER must have a console workstation for installation and maintenance. This workstation runs the ProtecTIER Manager application. This application is a GUI used to install, configure, and monitor the IBM System Storage TS7600 with ProtecTIER. You install the ProtecTIER Manager on a workstation running either Windows or Linux. If you are planning to run ProtecTIER Manager on a Linux system, configure your graphics card and X Window System. This is done either manually or using the Xconfigurator utility. For instructions refer to the appropriate Linux documentation. You must place the console hardware order separately from the IBM System Storage TS7600 with ProtecTIER order. The console must be capable of operating one of the following operating systems: Windows 2000, Windows XP, or Windows Server 2003 Red Hat Enterprise 3 or later

Chapter 3. ProtecTIER native replication overview and operation
result of subtracting the total number of tapes in all libraries from the total number of tapes supported in a single repository.
Visibility switch control
Visibility switch control is the means by which ProtecTIER can determine where cartridges actually exist, because from a backup application standpoint, any specific cartridge or barcode can exist in only one location at a given time. ProtecTIER native replication will provide a virtual shelf (Figure 3-3) that is visible internally only at the ProtecTIER level (after it is exported by the backup application) and will provides more flexibility in managing tapes/cartridges and where they are keptsimilar to keeping physical tapes on an actual shelf outside of the tape library.

Figure 3-3 Virtual shelf

To ensure that a given cartridge is only visible to the backup application in one location despite the fact that a replica exists, ProtecTIER offers the visibility control function that allows the user to determine in which location the cartridge should be accessible to the backup application. This is achieved by utilizing the import/export slots of the virtual libraries and exactly mimics the operation of physical tape management.
Cartridge cloning and visibility control
A common use case for ProtecTIER users is to first replicate data from the primary site to the secondary site, and then to move the data from the disk-based repository onto physical tape cartridges for long-term retention. With the visibility control function, ProtecTIER makes this operation simple for users. Once the cartridges complete replication to the secondary (DR) site, users may clone these cartridges to physical tape using their backup application tape copy function. This allows the backup application to remain in control of the end-to-end process and maintain its catalog of all cartridges, the associated data, and the location.

Policy management

Replication policies allow for flexibility in controlling replication and enable a high degree of automation. Policies consist of rules that dictate the transfer of data from one repository to another, based on events such as writing new data to an existing cartridge that belongs to a policy. By setting policies for ranges of barcodes, users may implement differing degrees of protection for different applications. Users can also assign various priority levels to replication policies, which determine the order in which the data is transferred across the network.

Figure 5-1 HyperFactor

The capacity of the ProtecTIER Repository consists of the factored backup streams and the metadata that describes the factored backup streams, so it is fundamental to have the proper amount of back-end disk capacity as part of the ProtecTIER System configuration. The capacity reduction effect of deduplication is expressed as a deduplication ratio or factoring ratio. In essence, the deduplication ratio is the ratio of nominal data (the sum of all user data backup streams) to the physical storage used (including all user data, metadata, and spare capacity, that is, the total amount of disk storage for which the user pays). To figure out the factoring ratio, we recommend that you have a detailed picture of your backup/recovery environment. In this chapter, we help you identify your goals and objectives and consider all the variables, and we recommend useful best practices. This chapter covers the following topics: Sizing inputs Section 5.1.1, Sizing inputs on page 97 describes a deep analysis of your requirements, workloads, backup application, and data center topology. Capacity sizing We provide an overview of the process that is used to estimate your physical storage requirements for your current environment and your scalability needs.
Performance sizing Section 5.3.6, Performance sizing on page 133 helps you understand how many metadata and user data file systems are required, based on disk technologies and RAID configurations, to ensure proper performance in terms of backup/recovery throughput. Storage sizing Section 5.1.4, Storage sizing on page 111 describes in detail the performance and capacity tuning of your cache controller to match your actual amount of data and your future requirements. This tuning is closely related to the performance sizing. The methods described in this chapter provide the basis for assessing and understanding how the IBM System Storage TS7600 with ProtecTIER can be fully integrated in your environment. Figure 5-2 shows a flowchart of the sizing process. Although each step is described in the following sections, IBM technical personnel or Business Partner personnel will perform the sizing process before the pre-sales and pre-installation phases.
Pre-Implementation Planning: 1. Assessment of customer objectives 2. Assessment of current backup and recovery enviroment 3. Environment Interoperability Qualification Tools: Environmental Survey Data Protection Survey

RAID 6

RAID 6 (Figure 5-6) provides a striped set with dual distributed parity and fault tolerance from two drive failures. The array continues to operate with up to two failed drives. This makes larger RAID groups more practical, especially for high-availability systems. This becomes increasingly important because large-capacity drives lengthen the time needed to recover from the failure of a single drive. Single parity RAID levels are vulnerable to data loss until the failed drive is rebuilt. The larger the drive, the longer the rebuild will take. Dual parity gives time to rebuild the array without the data being at risk if one drive, but no more, fails before the rebuild is complete. RAID 6 can be used in the same workloads in which RAID 5 excels.
A B P1 = Parity One P2 = Parity Two C D E F etc

A E I M

B F J P1-M,N,O,P
C G P1-I,J,K,L P2-M,N,O,P
D P1-E,F,G,H P2-I,J,K,L N
P1-A,B,C,D P2-E,F,G,H K O

P2-A,B,C,D HH LL PP

Figure 5-6 RAID 6

Disk 6

RAID 10
RAID 10 (Figure 5-7), also known as RAID 1+0, implements block interleave data striping and mirroring. In RAID 10, data is striped across multiple disk drives, and then those drives are mirrored to another set of drives. The performance of RAID 10 is approximately the same as RAID 0 for sequential I/Os. RAID 10 provides an enhanced feature for disk mirroring that stripes data and copies the data across all the drives of the array. The first stripe is the data stripe. The second stripe is the mirror (copy) of the first data stripe, but it is shifted over one drive. Because the data is mirrored, the capacity of the logical drive is 50% of the physical capacity of the hard disk drives in the array.
Block 0 Block 1 Block 2 Block 3 Block 4 Block 5 etc

Block 0 Block 3 Block 6

Block 1 Block 4 Block 7

Block 2 Block 5 Block 8

Disk Array #1 Mirrorset

Disk Array #2 Mirrorset

Disk Array #3 Mirrorset

Stripeset

Figure 5-7 RAID 10
The recommendations for using RAID 10 are: Use RAID 10 whenever the array experiences more than 10% writes. RAID 5 does not perform as well as RAID 10 with a large number of writes. Use RAID 10 when performance is critical. Use write caching on RAID 10. Because a RAID 10 write will not be completed until both writes have been done, write performance can be improved through the use of a write cache (be sure that it is battery-backed up). When comparing RAID 10 to RAID 5: RAID 10 writes a single block through two writes. RAID 5 requires two reads (read original data and parity) and two writes. Random writes are significantly faster on RAID 10. RAID 10 rebuilds take less time than RAID 5 rebuilds. If a real disk fails, RAID 10 rebuilds it by copying all the data on the mirrored disk to a spare. RAID 5 rebuilds a failed disk by merging the contents of the surviving disks in an array and writing the result to a spare. RAID 10 is the best fault-tolerant solution in terms of protection and performance, but it comes at a cost.

Policies have three optional types of priorities: HIGH MEDIUM LOW The default is LOW for every policy. Replication policies may be enabled or disabled by the user. Policies are repository wide. There can be 254 policies on a single repository. Policies can also be set up by time frame so as to avoid contention with backups. When writing to a cartridge that is part of a policy, the ProtecTIER system checks whether it must be replicated. The priority of the replication assigned to the cartridge is also considered. The cartridge is then created at the remote shelf. Data segments are transferred from local to a remote cartridge.

Policy execution

Policies can be executed either manually or continuously. Manual execution creates replication jobs for all the valid cartridges.
5.3 Choosing a replication mode of operation: Time frame versus continuous
This section provides an operational description and a recommendation for mode of operation.

5.3.1 Operation

ProtecTIER offers two modes of operation for the replication activity: Time frame (scheduled replication) with a predefined time window Continuous replication, which runs concurrently with the backup operation The mode of operation is configured at the source system, and all replication policies defined operate in one of these modes. In almost all cases, scheduled replication is the recommended approach, as it enables the user to accurately plan for performance and better ensure that SLAs are met. There are several variables, such as payload, available bandwidth, network utilization, time windows, and required SLAs, that might influence the final decision about which mode to choose. Given this mix and understanding the importance to the user of any one of these relative to others, the choice of approaches becomes clearer. We discuss the two choices in the following sections.
Dedicated Replication Timeframe window
There is no backup precedence in the ProtecTIER Manager. The window initiates the
procedure used with physical tapes that are being transported to a DR site after backup is completed. This method allows users to keep complete sets of backup data together with the matching backup catalog/DB for every 24-hour period. This is the best practice recommended mode. In the dedicated mode, the user defines a time slot during which replication operations will execute throughout the day. After this daily period is exhausted, all replication activities are halted at a consistent state and queued until the following day's window is resumed. 128

Figure 6-61 ProtecTIER Replication Manager view with both repositories
6.7.4 Setting up the replication policies
Before creating a replication policy you must create a replication pair. 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 disaster recovery (DR) site. A replication policy defines a set of cartridges from a local repository that must be replicated to a remote repository and establishes the rules for when and how that replication will take
place. When an event matching a replication policy rule occurs, such as data on a cartridge changing or the user ejecting a cartridge into an I/E slot, a trigger is created for replication activity to take place. 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 grid's pair and the policy only applies to the repository on which it is defined. When creating a replication policy, the following parameters are defined: User object (that is, cartridges) Time frame in which the policy will take place (the replication window) Replication destination, with visibility change (specific library) or without visibility change (virtual shelf) at the remote location The priority: Each policy can be set with three priority levels: Low Medium High Users can set one policy with low priority and another with medium or high. The system default is low. By default the destination of the replication is the virtual shelf at the remote repository. If the visibility control switch is enabled, the destination is defined as a specified target library. This means that if you eject a cartridge that belongs to a policy with the enabled visibility switch, the cartridge is moved to the shelf of the local repository, and at the destination repository, once replicated, the cartridge is placed in the import/export slots of the specified destination library. Create a single policy or a small number of them for any single library for ease of management. It might be easier to manage one policy per library rather than many policies to reduce maintenance burden and to prevent human errors. One shelf is configured for each repository in the grid and when the cartridges are in the shelf and cannot be seen by the backup application. The cartridges are outside the library. ProtecTIER GUI has access to cartridges in the shelf in a special view. When the cartridges are in the shelf the following actions can be done: Relocate to a librarys import slot with the ProtecTIER GUI or by visibility switching. Be replicated to another repository. The cartridges can be deleted.

Example 8-1 Configuration and recognition of virtual tape drives in AIX
freeway> cfgmgr freeway> lsdev -Cc tape rmt0 Available 04-08-02 rmt1 Available 04-08-02 rmt2 Available 0B-08-02 rmt3 Available 0B-08-02 rmt4 Available 0B-08-02

IBM IBM IBM IBM IBM

Ultrium Ultrium Ultrium Ultrium Ultrium
rmt5 rmt6 rmt7 rmt8 rmt9 rmt10 rmt11 rmt12 rmt13 smc0 smc1 smc2
Available Available Available Available Available Available Available Available Available Available Available Available
0B-08-02 0B-08-02 0B-08-02 0B-08-02 0B-08-02 0B-08-02 0B-08-02 0B-08-02 0B-08-02 04-08-02 0B-08-02-PRI 0B-08-02
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
Ultrium Ultrium Ultrium Ultrium Ultrium Ultrium Ultrium Ultrium Ultrium Library Library Library
Tape Drive (FCP) Tape Drive (FCP) Tape Drive (FCP) Tape Drive (FCP) Tape Drive (FCP) Tape Drive (FCP) Tape Drive (FCP) Tape Drive (FCP) Tape Drive (FCP) Medium Changer (FCP) Medium Changer (FCP) Medium Changer (FCP)
3. Obtain information about the tape devices. In our environment, we have four tape drives and one robot created and assigned. We must ensure that each device of rmtx and smc search the new drives by issuing the lscfg command in AIX. See Example 8-2.
Example 8-2 Obtain information about each device in AIX
freeway> lscfg -vpl rmt10 rmt10 U787A.001.DPM04K9-P1-C6-T1-W10000000C97C69CB-LA000000000000 IBM 3580 Ultrium Tape Drive (FCP) Manufacturer.IBM Machine Type and Model.ULT3580-TD3 Serial Number..7127285000 Device Specific.(FW).5AT0 freeway> lscfg -vpl rmt11 rmt11 U787A.001.DPM04K9-P1-C6-T1-W10000000C97C69CB-LB000000000000 IBM 3580 Ultrium Tape Drive (FCP) Manufacturer.IBM Machine Type and Model.ULT3580-TD3 Serial Number..7127285001 Device Specific.(FW).5AT0 freeway> lscfg -vpl rmt12 rmt12 U787A.001.DPM04K9-P1-C6-T1-W10000000C97C69CB-LC000000000000 IBM 3580 Ultrium Tape Drive (FCP) Manufacturer.IBM Machine Type and Model.ULT3580-TD3 Serial Number..7127285002 Device Specific.(FW).5AT0 freeway> lscfg -vpl rmt13 rmt13 U787A.001.DPM04K9-P1-C6-T1-W10000000C97C69CB-LD000000000000 IBM 3580 Ultrium Tape Drive (FCP) Manufacturer.IBM Machine Type and Model.ULT3580-TD3 Serial Number..7127285003 Device Specific.(FW).5AT0

8.2.7 Reclamation considerations
Another important consideration when using ProtecTIER IP Replication in a TSM environment is the effect that reclamation will have. Reclamation is the TSM process that moves expired data off of tapes and moves any unexpired data to other tapes, thus freeing up space and returning empty tapes to the scratch pool. All reclamation tape movement is recorded in the TSM database and it must be replicated to reflect an accurate tape environment in the event of a disaster. If the disaster strikes while reclamation is running and the database backup available for restore does not reflect the data on tape movements, an audit/fix of the volumes might be required. 295
The effect of reclamation can be delayed by using the REUSEDELAY parameter. When the user defines or updates a sequential access storage pool, the user can use the REUSEDELAY parameter. This parameter specifies the number of days that must elapse before a volume can be reused or returned to scratch status after all files have been expired, deleted, or moved from the volume. When the user delays reuse of such volumes and they no longer contain any files, they enter the pending state. Volumes remain in the pending state for as long as specified with the REUSEDELAY parameter for the storage pool to which the volume belongs. Delaying reuse of volumes can be helpful under certain conditions for disaster recovery. When files are expired, deleted, or moved from a volume, they are not actually erased from the volumes. The database references to these files are removed. Thus, the file data might still exist on sequential volumes if the volumes are not immediately reused. This prevents a situation where reclamation has run after the last TSM database backup to virtual tape, and reclaimed tapes have been replicated. If the disaster occurs at a point after the reclamation ran and these tapes fully replicated, but this is not reflected in the TSM database, the user could get a mismatch. A disaster might force the user to restore the database using a database backup that is not the most recent backup. In this case, some files might not be recoverable because the server cannot find them on current volumes. However, the files might exist on volumes that are in the pending state. The user might be able to use the volumes in the pending state to recover data by performing the following steps: 1. Restore the database to a point-in-time prior to file expiration. 2. Use a primary or copy storage pool volume that has not been rewritten and contains the expired file at the time of the database backup. If the user backs up the primary storage pools, set the REUSEDELAY parameter for the primary storage pools to 0 to efficiently reuse primary scratch volumes. For their copy storage pools, the user should delay reuse of volumes for as long as they keep their oldest database backup. Users can also disable the reclamation by changing the reclaim parameter of the update stgpool command: update stgpool <stg pool name> reclaim=100

Do these steps to add cartridges: 1. From the menu bar, select VT VT Add cartridges. The Add cartridges wizard Welcome window is displayed (Figure 9-32).
Figure 9-32 Add cartridges: Welcome window
Click Next. Then system will validate the barcode seed.
Figure 9-33 Validating barcode seed window
Then cartridges window is displayed (Figure 9-34).
Figure 9-34 Add cartridges window
2. In the No. of cartridges field enter the number of cartridges that you want to have in the library. The Virtual size field automatically displays the maximum possible size for virtual cartridges for your system, 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. growth check box. 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. 3. 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.
Click Next. The Report window will displayed (Figure 9-35).
Figure 9-35 Add cartridges: Report window
4. Click Finish. The Add cartridges wizard closes and the cartridges are added to the library (Figure 9-36).
Figure 9-36 Add cartridges: Adding cartridges to existing library window
If the necessary number of slots are not already available, the ProtecTIER system temporarily goes offline to create slots and then create the cartridges.
Figure 9-37 Confirm operation

Click Yes to continue.

Figure 9-38 Add cartridges: System goes offline for a while
The slots and cartridges both are created.
Figure 9-39 Add cartridges: Slots and cartridges both are created
9.3.4 Deleting cartridges
You can delete virtual cartridges, and the results are the same as when you discard a physical tape. If the virtual volume was not in scratch status, you will loose all data on that virtual cartridge and cannot recover it anymore. If you plan to delete cartridges, we strongly recommend that you check the status of the cartridges and make sure that you do not delete any cartridges that contain valid data.
Attention: Deleting a cartridge results in the loss of all data contained on that cartridge. To delete a virtual cartridge, follow these steps: 1. From the Services pane, select the library that contains the cartridge that you want to delete. The VT service monitoring window is displayed. 2. Click the Cartridges tab. The cartridges window is displayed (Figure 9-40).

2. Click Next. The Properties window opens. Type a unique name for the failback policy in the Policy name field (Figure 10-7).
Figure 10-7 Create failback policy properties window
In our example, we entered Fail back test.
3. Click Next. The Barcode ranges window opens (Figure 10-8). Enter the barcode range of the cartridges that you want to fail back to the old or replaced primary repository.
Figure 10-8 Create failback policy properties window
Figure 10-9 Create failback policy barcode ranges window
In our example we used the barcode range AU0060AU0085. Click Add to validate and submit the defined barcode range. If the barcode range is invalid, an error message is displayed and you must change the barcode range. Click Next. The Validation Results window opens (Figure 10-10).
Figure 10-10 Create failback policy validation window
In our example we selected 26 cartridges for the fail back scenario. Click Save reports as if you want to save the validation summary report.
4. Click Next to view the validation summary report (Figure 10-11). Click Finish to create the fail back policy.
Figure 10-11 Create failback policy summary report
5. No message is displayed after you create the fail back policy. On the ProtecTIER view pane, click the DR repository, then replication policies. Here you see your newly created policy (Figure 10-12).
Figure 10-12 Failback policy
6. Double-click your policy and click Execute. The failback policy starts. Depending on the number of many cartridges and the amount of data, it can take some time for the failback procedure to finish. You can observe the progress of replication when you click Replication activities in your ProtecTIER view pane (Figure 10-13).
Figure 10-13 Replication progress
10.3 Completing failback and leaving DR mode
Once you have finished creating a failback policy, manually execute the policy and wait for it to complete. Do not run any backup activities on the restored repository until the operation is complete. You cannot run the failback policy, twice so you can delete the failback policy from ProtecTIER Manager and exit the DR mode by selecting Replication Disaster Recovery Leave DR mode. You can now start working again with the restored repository. See Figure 10-14.
Figure 10-14 Leaving DR mode

10.4 Principality

11.1 ProtecTIER Manager user management
ProtecTIER Manager has three default user accounts that come with predefined default passwords. They are shown in Table 11-1.
Table 11-1 Default user names and passwords in ProtecTIER Manager Permission level Administrator Operator Monitor Default user name ptadmin ptoper ptuser Default password ptadmin ptoper ptuser
We recommend that you change the passwords or replace and delete these default user accounts to secure the system against unauthorized access through knowledge of the default passwords. The three permission levels have different abilities within ProtecTIER Manager. Once you are logged in, depending on your user IDs permission level, only certain options from menus and toolbar buttons are available to you. This is indicated by the color of the options text. If the option is available to you, the text appears in black and is selectable. If it is not available to you, the text appears in blue and is not selectable. For example, in Figure 11-1, from the Repository menu, only the View Resources option is available to this user account.
Figure 11-1 Example of available and unavailable options for a user account in ProtecTIER Manager
The ProtecTIER Manager application supports the permission levels shown in Table 11-2.
Table 11-2 Permission levels Permission level Administrator Operator Authority Has full access to ProtecTIER Manager. Has restricted access to ProtecTIER Manager: Toggle cartridges between read/write and read-only modes. For more information see 9.3.5, Switching cartridges to read-only mode on page 357. Set the HyperFactor mode for libraries. For more information see 9.8.5, Changing the HyperFactor mode on page 394. Reset virtual tape drives and robots. For more information see 9.8.8, Resetting robot on page 398. Unload and changing visibility of cartridges from virtual tape drives. For more information see 9.8.9, Unloading and moving cartridges on page 398.

Permission level Monitor

Authority Can only access ProtecTIER Manager monitoring windows.
To make changes to ProtecTIER Manager user accounts, after you have successfully logged in to ProtecTIER Manager as an administrator, from the System menu choose the User Management option (Figure 11-2).
Figure 11-2 The User Management option on the System menu in ProtecTIER Manager
The window shown in Figure 11-3 is displayed. From here you may add, remove, or change user accounts.
Figure 11-3 User Management window in ProtecTIER Manager
Chapter 11. Monitoring and reporting of the IBM System Storage TS7600 with ProtecTIER
From here you can choose an action and, if required, an existing user ID on which to perform the operation. As an example, click Add to create a new user account. The dialog box shown in Figure 11-4 is displayed, where you must specify a user name and password. You must also select a permission level from the drop-down menu. You may also click Close if you want to exit the window.

Example 11-12 ptmon -repository output
<?xml version="1.0" encoding="UTF-8" standalone="no ?> <response status="success"> <repository-statistics current-factoring-ratio="1.00" host-name="beast" repositoryallocablephysicalstorage-mb="49152" repository-free-physical-storage-mb="49152" repositorytotalnominalstorage-mb="0" repository-total-physical-storage-mb="49152" repository-usedphysicalstoragemb="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 (Example 11-13). This library unique ID can be used later for receiving detailed information about each of the configured libraries.
Example 11-13 ptmon -libs output
<?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>
ptmon -libinfo -libid <library id>
This command displays statistics about the configured tape drives of a specific library (Example 11-14). Table 11-10 provides descriptions of the fields.
Table 11-10 Field num-total-drives library-name libid Statistics about the configured tape drives of a specific library Description Amount of configured tape drives Name of the library Unique ID for the library
Example 11-14 ptmon -libinfo -libid <library id> output
<?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>
ptmon -ncarts -libid <library id>
When -ncarts and -libid are used together they display the statistics for the number of configured cartridges of a specific library (Table 11-11 and Example 11-15): http://publib.boulder.ibm.com/infocenter/ts7680/cust/index.jsp

IBM System Storage TS7650 ProtecTIER Deduplication Business Partner Sales Kit

Dear Business Partner

These are certainly very interesting and demanding times that we are experiencing. With the economy in turmoil, many of your valued customers and prospects are desperate to find ways that will enable them to reduce their costs. I am pleased to let you know that IBM has an answer for you to offer to your existing mid-range customers and prospects and that answer is the recently released IBM TS7650 ProtecTIER Deduplication Appliance. As you will see, when you review the materials in this Business Partner Sales Kit, enabling your customer/prospect base to deduplicate their backup data will provide them the means to achieve the following benefits: Reduce their storage Total Cost of Ownership by reducing the amount of backup storage by a factor of up to 25:1. Enhance their ability to make well informed and timely business decisions by utilizing disk as the media for backup and recovery operations. Enhance their backup and recovery operations without changing existing backup processes, procedures, and/or policies. Shorten their backup window to ensure their nightly/weekly backups are completed on time. Utilize remote disk for disaster recovery enabling rapid data restore with a high degree of integrity while significantly reducing manpower costs.
I encourage you to: Review the contents of this Sales Kit and make this information immediately available to your sales and pre-sales teams. Reach out to your IBM Business Partner Managers to schedule additional training sessions for your sales and pre-sales teams. Identify your top five (5) existing customers and arrange to take the benefits message to them immediately.
In summary, this is an exciting enhancement to IBMs existing ProtecTIER deduplication product line that IBM announced in September 2008. With the advent of the TS7650 Appliance product we have extended the benefits that hundreds of Enterprise customers have been enjoying for the past three(3) years plus, to your Mid-range customer base. You now have the tools necessary to enable your sales teams to take full advantage of the Data Deduplication market growth and market demands. Please feel free to contact me with any questions you might have. Best regards and good selling!!
Mike Doran WW Sales Director for ProtecTIER Deduplication Solutions
February 2009 For IBM and IBM Business Partners Use Only

Table of Contents

7650 Overview Buyers Profile Messaging & Value Props Product Description Competitive Information IBM Product Compatibility Additional Information

TS7650 Overview

Whats new?
The IBM System Storage TS7650 ProtecTIER Deduplication Appliance is a complete integrated solution of IBM storage, IBM server and ProtecTIER data deduplication software. This is an integrated solution that makes it easy for IBM Business Partners to sell and makes it significantly easier for our customers or a Business Partners professional services consultants to deploy. These solutions were designed to meet the disk-based data protection needs of a wide variety of organizations from mid-sized IT environments to enterprise data centers.
What is the 7650 ProtecTIER Deduplication Appliance?
The TS7650 ProtecTIER Deduplication Appliance is the industrys first enterprise-class data protection solution that reduces the required backup disk capacity by up to 25 times or more without disrupting the existing backup infrastructure. Powered by a revolutionary patented algorithm called HyperFactor, ProtecTIER appliances eliminate redundant data while improving the performance and reliability of backup operations. The TS7650 ProtecTIER Deduplication Appliance is an integrated solution of IBM servers, IBM storage and IBM ProtecTIER data deduplication software that is easy to deploy and integrate into existing backup environments. These three elements combine to offer a high capacity, high performance and highly scalable target for backup, archive and compliance data.
What are the top 3 messages for your prospects to remember?
ProtecTIER, with its revolutionary and patented HyperFactor data deduplication technology, is the only proven data deduplication solution on the market that can provide high levels of performance, scalability and data integrity. IBM is now delivering this enterprise-class technology to mid-sized customers that are challenged with protecting rapidly growing amounts of data within their existing tape-based data protection environment. IBM delivers data deduplication solutions that enable customers to address their backup and recovery challenges without changing their existing backup policies, practices or procedures with a lower TCO than competitive or conventional technology products.

What are the top five challenges addressed by this solution?
1. Protecting and cost effectively managing rapidly increasing amounts of data. 2. Inability to complete backup operations in a given backup window. 3. Cost effectively introducing disk into the backup environment. 4. Inability to recover files in a cost effective and timely manner. 5. Difficulty in achieving new compliance standards.
What are the main benefits provided by this solution?
Reduced Storage Total Cost of Ownership. Enhanced backup and recovery performance, data protection & reliability. Backup window shortened. Enhanced control of decentralized open systems data. Data management simplified. Enhanced Disaster Recovery through use of remote disk.

Buyers Profile

Business problems addressed by this solution
Organizations of all sizes are striving to improve their backup and recovery operations. Rapidly growing data volumes, shrinking backup windows, and increasing demands for data availability are driving the demand for enhanced solutions. Utilizing disk technology (D2D) in the backup and recovery operation is an increasingly attractive method of improving reliability, reducing backup windows, and ensuring rapid recoveries. However, introducing the use of disk into backup and recovery operations is a non-trivial effort. Customers need a solution that allows them to capture the performance and reliability benefits of disk without disrupting existing policies, practices and procedures. Virtual Tape Libraries (VTLs) deliver the speed, reliability and availability benefits of disk to the backup operations. By utilizing disk, customers achieve much greater data throughput performance, high availability, data protection (RAID, mirroring, replication), reduced mechanical and human errors, and rapid recoverability. Because VTLs exactly emulate tape libraries, customers do not need to change existing backup policies, practices or procedures. Disk is the answer but data deduplication is the key. Using more disk improves backup and recovery operations, but is prohibitively expensive to deploy without data deduplication technology. Data deduplication enables customers to store up to 25 times more data on a storage array making the cost of backing up to fast disks less than then conventional methods. The TS7650 ProtecTIER Deduplication Appliance provides improvements to existing data protection infrastructures as follows: Operational Resilience Complete backup operations in given backup window. Recover files and systems quicker. RPO and RTO improvements.

Operational Efficiency Greatly improved SLAs. Reduced cost of backup infrastructure (TCO). Improved reliability. Simplification/consolidation. Enhanced serviceability. Reduced management requirements.
Regulatory compliance Data loss mitigation and avoidance. Operational resiliency and efficiency.

Target Customers

In the past, the TS7650G ProtecTIER Deduplication Gateway has enabled IBM to secure storage footprints in existing enterprise accounts and generate significant storage and services revenue drag. IBM is introducing the TS7650 Appliance to enable our IBM Business Partners to replicate this previous success in smaller enterprise and mid-sized accounts. This will enable IBM Business Partners to secure backup to disk storage footprints and enable follow-on storage sales in this fast growing market segment. Enterprise-class customers with the following characteristics: Large organizations. Petabytes of data. Many mission-critical applications. Very experienced with backup technology. Experienced or familiar with replication, clustering. Tend to be multi-vendor storage and server structures. Large IT staff. Significant internal and external SLAs. Significant backup window issues. Hard to manage or unacceptable recovery windows. Current RTO/RPO characteristics are no longer acceptable. Looking for risk mitigation through improved data protection. Excessive operational costs.
Mid-sized customers that with the following characteristics: 1-12 Terabytes of backup data per night. Somewhat experienced with backup technology. Interested in reducing backup & recovery costs. Interested in deploying some amount of disk in their backup environments.
By enabling customers to get 25 times the capacity from a given amount of physical disk capacity, ProtecTIER greatly changes the economics of data protection. Analysis shows that both on an acquisition cost basis and a total cost of ownership (TCO) basis, a ProtecTIER solution is significantly less expensive than competitive and conventional backup alternatives, while offering higher levels of data protection. Thus, customers may greatly expand the use of disk in their data protection infrastructure, while significantly lowering costs.
Messaging & Value Props

Solution Messaging

For both mid-sized and enterprise customers who are challenged with the rapid growth of data and shrinking backup windows: the TS7650 ProtecTIER Deduplication Appliance leverages unique data deduplication technology to help customers: Increase backup performance by complimenting tape environments with the addition of high speed disk. Speed up recovery operations improving RPO and RTO. Optimizes their storage infrastructure and drastically reduces TCO. Achieve their business resilience objectives without changing their existing backup policies, procedures and practices.
TS7650 ProtecTIER Appliance Key Messages & Value Statements
ProtecTIER Next Generation data deduplication technology Reduce storage needs by a factor of 25, radically reducing costs Greatly improve backup success rates (close to 100%) Dramatically improve backup and recovery operations Only virtual tape system that includes data reduction technology Requires minimal changes to existing policies, practices and procedures Involves no client or host agents Qualified with leading enterprise backup applications Architecture enables smooth scaling of both performance and capacity Capacity scales to 1 PB of physical storage Sustained throughput rates greater than 500 MBPS with a single TS7650 ProtecTIER appliance in real customer environments Over 1000 MBPS sustained performance with a TS7650G ProtecTIER cluster configuration Acquisition cost 50-80% lower than standard VTL solutions across a range of environments Total Cost of Ownership dramatically lower than standard VTL solutions across all customer scenarios and use profiles Unlike hash-based deduplication products, HyperFactor performs byte level differential comparisons to detect duplication to avoid the risks of data lass associated with hash collisions TCO reduction, increased reliability, improved service levels

Ease of Implementation

Transparent and non-invasive

Scalability

No cost surprises as you grow

Performance

Improved backup performance, reduction of backup window

Changed Economics

Unprecedented TCO savings
Enterprise level Data Integrity

Reduced risk

Product Description
The TS7650 ProtecTIER Deduplication Appliance combines a highly reliable IBM Systems storage system, IBMs revolutionary and patented ProtecTIER data deduplication software, and a high performance multi-core IBM server to meet the performance and capacity needs of a wide variety of environments. The IBM System Storage TS7650 ProtecTIER Deduplication Appliance features: IBM ProtecTIER software with patented HyperFactor data deduplication technology. IBM System X server with 18 2.66GHz processor cores, 24 GB RAM and 4GB HBAs. IBM Storage Controller with 450GB Fibre Channel drives. IBM TS3000 System Console. Rack, cables, and other components needed to provide a complete solution and the IBM System Storage TS7650 ProtecTIER Deduplication Appliance provides: Up to 500MB/sec or more inline data deduplication. Up to 25 times or more storage capacity reduction. Emulation of up to 12 virtual libraries, 256 virtual drives and 128,000 virtual cartridges. Simplified configuration and deployment.
TS7650 ProtecTIER Deduplication Appliance 7TB Configuration Performance: Useable Capacity: 100MB/sec inline data deduplication 7TB
A value based configuration that delivers fast inline data deduplication performance and scalability. TS7650 ProtecTIER Deduplication Appliance 18TB Configuration Performance: Useable Capacity: 250MB/sec inline data deduplication 18TB
A flexible solution that delivers fast inline deduplication performance and future capacity scalability. TS7650 ProtecTIER Deduplication Appliance 36TB Configuration Performance: Useable Capacity: 500MB/sec inline data deduplication 36TB
Delivers the industrys fastest single-node data deduplication performance and large capacity for enterprise-class IT organization with significant backup and recovery work loads. TS7650 ProtecTIER Deduplication Appliance 36TB Dual-node Cluster Configuration Performance: Useable Capacity: 500MB/sec inline data deduplication* 36TB
A dual-node high-availability cluster configuration that delivers the industrys fastest inline data deduplication performance, high availability, and large useable capacity for demanding high-volume backup environments.

Competitive

What is our positioning relative to the competition?

The TS7650 ProtecTIER Deduplication Appliance is being positioned in the data deduplication market segment to compete with offerings from the other major storage vendors and third party applications providers. ProtecTIER, with its patented HyperFactor data deduplication technology is the only data deduplication solution on the market that can provide enterprise-class performance, scalability, and data integrity. IBM is now delivering this enterprise-class technology to mid-sized customers that are challenged with protecting rapidly growing amounts of data with their existing tape-based data protection environment.
Differentiators (rich sense of besting the competition)
ProtecTIER is the only proven enterprise-class data deduplication solution on the market today. With a unique commonality factoring technology called HyperFactor, IBM delivers disk-based data protection solutions that enable customers to effectively increase the capacity of disk systems by up to 25 times or more without the risk of data loss or corruption, radically reducing the amount and cost of physical storage required. Competitors make similar claims for their products using 10 year old hashing algorithms, such as MD-5 and or SHA-1. In addition to their claims being overly optimistic, they fail to mention the fact that there is a possibility, though remote but still a possibility, that hashing algorithms may store the incorrect data causing data corruption issues that will not be discovered until a data recovery is required. ProtecTIER provides industry leading data deduplication performance at over 500MB/sec per server. The next fastest competitor tops out at 220MB/sec per server and most other competitors struggle to provide 100-150MB/sec per server performance. To make up for their performance shortcomings, competitors must propose multiple servers or propose a risky two phase approach called Post Processing to reach the same performance or capacity provided by a single TS7650 ProtecTIER Deduplication Appliance. This eliminates the cost saving opportunity of reducing the amount of disk required to store backup data and raises the total cost of ownership of their solutions in terms of acquisition and ongoing maintenance and support costs. Below is an overview of the competitive data deduplication offerings. Data Domain Small deduplication appliances for small and medium business (SMB). Low performance <222MB/sec. Limited scalability up to 28TBs useable.
Quantum Unproven hash-based deduplication technology. Late to the game with very few systems in production.
FalconStor Major provider of standard (non-deduplication) VTL to OEM partners. Most OEM partners evaluated and rejected their deduplication technology. Unproven hash-based post-process-only deduplication technology.

EMC, Sun, HP, Copan and others OEMing other vendors product. No commitment to deduplication technology. In general, data deduplication technology is not generally available or not capable of handling enterprise-class performance or large capacities.
Sepaton Only supported in NetBackup environments. TSM support promised but not GA. ContentAware post processing approach requires much more storage and many more servers to meet requirements.
NetApp A-SIS is hash-based post-process deduplication technology. Initially designed for small capacity, low performance NAS environments.

Compatibility

Compatibility with other IBM solutions
The TS7650 ProtecTIER Deduplication Appliance fits neatly into IBMs storage and tape strategy product portfolio. The impact on the current portfolio is simply another solution in a growing market to enable more storage, software and services sales to customers in existing and new accounts. It broadens our reach and there is no overlap or negative impact on current IBM portfolio. TS7650 ProtecTIER Deduplication Appliance integrates with and is complementary to many other hardware and software product offerings from IBM. The following is just a partial list: IBM Tivoli Storage Manager is fully compatible with the TS7650 ProtecTIER Deduplication Appliance and can take advantage of a TS7650 ProtecTIER Deduplication Appliance as a target to increase backup performance and reliability. IBM Tape Systems such as the TS3500 Tape Library can be used in conjunction with the TS7650 ProtecTIER Deduplication Appliance to provide a comprehensive end-to-end backup and recovery environment that takes advantage of the strengths of both disk and tape. IBM Fibre Channel Disk Systems such as the IBM System Storage DS4700, DS4800 or DS5000 can be used with the TS7650G ProtecTIER Deduplication Gateway to provide high performance solutions that can provide up to 500 MB/sec or more inline data deduplication. IBM SATA Disk Systems such as the IBM System Storage DS4200 or XIV Storage System can be used with the TS7650G ProtecTIER Deduplication Gateway to provide a cost effective solution with a TCO less than a magnetic tape library. IBM Data Mobility Solutions such as the advanced copy services; IBM FlashCopy, Metro Mirror and Global Mirror can be used with the TS7650 ProtecTIER Deduplication Appliance to create a high performance backup and recovery environment that also provides disaster recovery capabilities unlike any other solution available.

Additional Resources

For more information visit the IBM ProtecTIER Sales Kit on PartnerWorld: http://www.ibm.com/partnerworld/wps/servlet/ContentHandler/ProtecTIER SalesKit IBM has sales and technical experts dedicated to helping you configure and sell ProtecTIER solutions Americas: USA West Michael Lehrer mlehrer@us.ibm.com USA South Dave Stilley dstilley@us.ibm.com USA NorthEast Nathan Rosen nrosen@us.ibm.com USA Federal Walker Smith smithwa@us.ibm.com Canada John Perring perring@ca.ibm.com Latin America Jeff Roy groy@us.ibm.com EMEA: Jasper Gundry-White gundryw@uk.ibm.com APAC: Justin Hildebrandt justin_hildebrandt@au1.ibm.com
Copyright IBM Corporation 2009 All Rights Reserved References in this document to IBM products or services do not imply that IBM intends to make them available in every country. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. IBM, the IBM logo, AIX and System Storage are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries or both. FlexClone, LockVault, SecureAdmin and Snapshot are trademarks of Network Appliance, Inc., and Data ONTAP, DataFabric, FilerView, FlexVol, MultiStore, SnapDrive, SnapLock, SnapManager, SnapMirror, SnapRestore, SnapValidator, SyncMirror and SnapVault are registered trademarks of Network Appliance, Inc. in the U.S. and other countries. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. Other company, product, or service names may be trademarks or service marks of others. Information is provided "AS IS" without warranty of any kind. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Information concerning non-IBM products was obtained from a supplier of these products, published announcement material, or other publicly available sources and does not constitute an endorsement of such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly available information, including vendor announcements and vendor worldwide homepages. IBM has not tested these products and cannot confirm the accuracy of performance, capability, or any other claims related to non-IBM products. Questions on the capability of non-IBM products should be addressed to the supplier of those products. All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Contact your local IBM office or IBM authorized reseller for the full text of the specific Statement of Direction. Some information addresses anticipated future capabilities. Such information is not intended as a definitive statement of a commitment to specific levels of performance, function or delivery schedules with respect to any future products. Such commitments are only made in IBM product announcements. The information is presented here to communicate IBM's current investment and development activities as a good faith effort to help with our customers' future planning. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here. Photographs shown are of engineering prototypes. Changes may be incorporated in production models. 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.