Hierarchical Storage Management

Concepts and Implementation

Rob BennettAsia Pacific Global Response Team

Tivoli Storage Management

AbstractThis presentation will provide an introduction to space management as implemented by Tivoli Storage Manager.The speaker will compare and contrast the recently released HSM for Windows with the established UNIX based TSM for Space Management product set.

• Included in this discussion are the issues to consider during Installation and Implementation.

Agenda

• HSM Concepts• Supported Platforms• Compare Windows HSM with UNIX HSM• Implementation Considerations• Questions

Concepts

Products

Terminology

Stub Files

Supported Platforms

Support Entitlement

To receive your full support entitlement, ALLelements of the Tivoli solution must be currently supported by the originating vendor.

HSM Elements Affecting Support

Operating SystemVxFS if neededHSM Client

Most Common Support Gotchas

• Windows 2000 is EOSImplement HSM on Windows 2003 or later

• VxFS 3.4 and VxFS 3.5 are EOS on SolarisImplement HSM using VxFS 4.1 or later.

• VxFs 3.5 is still supported on HP-UX 11.

AIX Requirements• AIX 5.2 64 bit or later• Java Runtime 1.4.0

Please review the product readme for the latest information.

The HSM client for AIX GPFS and the HSM client for AIX JFS2 cannot be installed on the same machine.

HP-UX Requirements• HP-UX 11i v1 • Veritas file systems (VxFs) 3.5 with

performance patch

Please review the product readme for the latest information.

Linux Requirements

• Red Hat Enterprise Linux 3.0• SUSE SLES 8• GPFS 2.2• Java JRE 1.4.1, or later

Please review the product readme for the latest information.

Solaris Requirements

• TSM client 5.3.2 or later• Sun Solaris 8 32bit and 64bit kernel mode• Sun Solaris 9 32 bit or 64bit kernel mode• Sun Solaris 10• Veritas VxFS 4.2

Please review the product readme for the latest information.

Windows Requirements

• Windows 2003 Server• Windows 2003 Enterprise Server (32-bit)• NTFS Version 5

Please review the product readme for the latest information.

Product Comparison

Implementation Considerations

Optimal Environment• HSM should be used in an environment, where

the migrated files, are not used regularly. • Files that are needed frequently should not be

migrated at all. • The file system needs to be large enough to

hold all regularly used files.

Differences between the UNIX clients

Migration Policy

• TSM HSM for Windows only checks at the time of last access and is not sensitive to file size.

• Files are usually not worth migrating if their size is quite small (e.g. less than 1 MB) .

• TSM HSM for UNIX enables migration to balance file size and time of lastaccess (either one or a weighted combination of the two).

Threshold Migration, Demand Migration

• TSM HSM for Windows migration is done via regularly scheduled background processes and does not automatically adjust to usage spikes.

• Active administration is required to assure that TSM HSM for Windows managed file systems do not overflow.

• TSM HSM for UNIX constantly monitors file system space usage, and automatically begins migrating files if the threshold (default 90%) is exceeded.

TSM Server Reconciliation• TSM HSM for Windows requires an

administrator to query the different versions of migrated files stored on the TSM server and to manually delete those no longer desired.

• TSM HSM for UNIX schedules periodic reconciliation processes to remove objects from the TSM server when they no longer map to files in HSM client file systems.

TSM Backup / Archive Client Integration

TSM Backup/Archive and TSM HSM for UNIX clients are tightly integrated. TSM backup recognizes TSM HSM migrated files, and will clone them on the server when making a full backup (also known as an “inline copy”).

• A full backup of a TSM HSM for Windows managed file system is not possible. TSM HSM for the Windows administrators to perform a full backup before installing TSM HSM for Windows, and subsequently, to backup files before they are qualified for migration.

Recent New Features

Partial File Recall

• Starting with TSM v5.2.2 the AIX GPFS HSM client and with TSM v5.3.0 the Linux GPFS HSM are supporting the new recall mode called partial file recall.

• Partial file recall mode recalls a portion of a migrated file. This avoids having to recall an entire, potentially large file, when only a small portion of the file is required by an application.

• An example is Digital Media-type customers.

Streaming Recall• Starting with TSM v5.2.0 some HSM clients are

capable of recalling files in the so called streaming mode. After recalling the beginning of the file, an application can read this data, while the rest of the file is still being recalled.

• Useful for video applications.

GPFS 2.3 support

• Starting with TSM v5.3.2 the AIX and Linux GPFS HSM client supports GPFS 2.3.

HSM Java GUI

• With TSM v5.3.2 the new HSM Java GUI is available for all HSM Unix platforms.

• This GUI is also available for Windows users to administer Unix HSM clients.

• The GUI can cannot connect to any HSM client without first having to login to each HSM system.

LAN-free migration/recall

• The AIX GPFS HSM (5.2.2 or later) and Linux GPFS HSM client (5.3.0 or later) support the migration and recall of files using a LAN-free path.

• Because files will be moved directly to tape, enough tape drives are available including also tapes for backups, TSM server migrations, etc.

Questions?

Thank You

Disclaimers and TrademarksNo part of this document may be reproduced or transmitted in any form without written permission from IBM Corporation.Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. IBM products are warranted according to the terms and conditions of the agreements (e.g. IBM Customer Agreement, Statement of Limited Warranty, International Program License Agreement, etc.) under which they are provided. IBM customers are responsible for ensuring their own compliance with legal requirements. It is the customer's sole responsibility to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer's business and any actions the customer may need to take to comply with such laws. The following terms are trademarks or registered trademarks of the IBM Corporation in either the United States, other countries or both: DB2, e-business logo, eServer, IBM, IBM eServer, IBM logo, Lotus, Tivoli, WebSphere, Rational, z/OS, zSeries, System z.Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States and/or other countries.Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States and/or other countries.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 and other countries.Other company, product, or service names may be trademarks or service marks of others.ITIL® is a Registered Trade Mark, and a Registered Community Trade Mark of the Office of Government Commerce, and is Registered in the U.S. Patent and Trademark Office.IT Infrastructure Library® is a Registered Trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.