Professional Documents
Culture Documents
ibm.com/redbooks
Application Server
Application Server
Application Server
SAN
SAN
SAN Volume Controller installed and old storage mapped as virtual volume to the server
SAN
Movement of data from old volume to new disk and reduction of old volume space from virtual volume
Volume
Virtual Volume
Virtual Volume
New Disk
Volume
Volume
Data
Figure 1 Migrating SAN disk volume data to SAN Volume Controller storage
Data migration from the original volume to the virtual volume using additional disks can be accomplished without interrupting data availability. The application server can continue to read, write, and process data as it is migrated. Transparency of these operations to the application server makes the IBM TotalStorage SAN Volume Controller a very effective tool in managing SAN-attached storage.
could possibly be physically unavailable if an archived tape or other media is kept off site for data retrieval. Don't take the risk that a specific tape drive you sent off site last week will be available in ten years. You should have a plan to perform a technical refresh of your media and drive technologies after a specified number of years to either move the data to new media, or migrate it to newer, higher capacity media using newer drive technologies. Data within IBM Tivoli Storage Manager is stored on a per client basis, and each of these clients' data resides in a storage pool hierarchy. Each storage pool, in turn, consists of allocated media volumes (such as, tapes, disks, or optical volumes). Storage pools are associated with particular technologies based on the media volumes that comprise them, and a storage management administrator can move or migrate this data across storage pools within IBM Tivoli Storage Manager. This makes the transition to a different form of media transparent to the clients to whom the data belongs and without interruption in data availability. There are two methods used to perform data migration: Migrating individual nodes Migrating complete storage pools to a new tape technology
Node1 Node2
Node3
Node4
Old Library
Database
LAN or SAN
Node1
Node2
Node3
Node4
Figure 2 Using move nodedata command to migrate data across tape technologies
data resides to a storage pool value comprised of the new technology, the migration threshold parameter of the older storage pool(s) can be set to 0. Over the course of the next few hours, or days if necessary, the data will safely migrate to the new storage pools during background processing.
ARCH3494
ARCH3584
TLIB3584
Figure 3 Migrating storage pool data using migration destination and thresholds
Once data begins to populate the storage pools on the new media, it will be necessary to run a backup storage pool process on these if you have created a new off-site pool based on the new media. The move data and move nodedata commands cannot be used on copy pool data; however, the internal IBM Tivoli Storage Manager database will be updated to reflect the new location of the data that is associated with the pre-existing copy pool. In the event of a media failure or loss of data in the new media storage pool, the database will still reference the backup copy of the pool data and the missing data can be restored from there. Once the storage pools on the new media have been successfully populated, a new copy pool can be created on the new media and backup storage pool commands can be run to reproduce the data on the new media. This will totally remove your dependence on the older media technology.
Tape consolidation
Tape consolidation has become an important topic since the quantity of data used in open systems environments started to reach mainframe proportions. This subchapter explains the technological move from dedicated to shared libraries and later to logical partitioned libraries. A removable media manager combines the advantages of library sharing with the advantages of logical partitioning. It can be seen as an initial step to tape virtualization.
Drive
Drive
As the control information goes through the TCP/IP network, this type of library is sometimes called an IP library. In Figure 4 the functionality of an IP library with open attachment is depicted in a very basic way. Open systems servers have fibre channel or SCSI connections to tape drives. The Library Control System handles the robotics of the libraries by sending commands over the TCP/IP network. In cases of fibre channels, it is common to use a switched fabric environment. We chose not to use this type of environment in our scenarios to keep them simple and comparable. In the open systems environment, smaller libraries designed for affordable solutions are widely used. These libraries dont have a dedicated management computer attached, so the control of the robotics has to be done via SCSI commands from the attached server. Even if the attachment is connected via the fibre channel, this type of library is often called an SCSI library and sometimes called a jukebox. The content of SCSI libraries has to be managed by software
solutions, usually network backup applications. To prevent confusion and loss of data, only one server may have control over the tape volumes and the robotics of the library. The classic way to use an SCSI library is to connect it to a backup server like the IBM Tivoli Storage Manager and to do backups from clients over the TCP/IP network. Network backup is an established and approved method.
Drive
inactive
Drive
inactive
Tape library sharing works in a heterogeneous hardware environment but requires a homogeneous software solution. With the IBM Tivoli Storage Manager, it is possible to share an SCSI library between backup servers running under AIX, Windows, Linux, HP-UX and Solaris. If a single IBM Tivoli Storage Manager is not able to perform the backups in a reasonable time frame due to a heavy workload, tape library sharing is a good way to share tape resources. Incidentally, tape library sharing was a precursor to the LAN (local area network) backup method. For more details on storage management concepts please refer to the following IBM Redbook: IBM Tivoli Storage Management Concepts, SG24-4877-03. Note: Keep in mind that every backup server needs administration.
10
Drive
Drive
Drive
Drive
inactive
The IBM 3584 UltraScalable tape library was IBMs first SCSI library that could be divided into many logical partitions. These partitions share robotics and appear to be connected to the server as a separate smaller library would be. In principle each drive within an IBM 3584, in conjunction with an array of slots, can build a separate partition. In reality two or more drives are used in logical
11
partitions. In the IBM Tivoli Storage Manager, for example, it is recommended that you use a least three drives per backup server. Figure 7 shows how a physical library can be shared between different open systems and midrange platforms like iSeries, xSeries and pSeries. Its also possible to implement software-based tape library sharing within a logical partition such as the one depicted in Figure 7 as Zone 3.
Library Controller
DRIVE 1
Logical Library 1
DRIVE 2
DRIVE 3
SAN
(with Zoning) xSeries App B Zone 2
Logical Library 2
DRIVE 4
DRIVE 5
Zone 3
Logical Library 3
DRIVE 6
pSeries App C
Linux App C
Its common to have some logical libraries in an IBM 3584 tape library. The slots of a logical library have to be in consecutive order. If a logical library has to be enlarged or reduced, the other logical libraries may also have to be changed. This is a critical step, because the administrator has to move the cartridges and take care that none of the tapes are overwritten by other applications. This approach may be practical in a two frame library, but imagine trying to do this for a fully equipped IBM 3584 library with 16 frames and more than 6000 tape cartridge slots.
12
13
ol Contr
TSM Servers
Other Apps
Tape Virtualization
Data
RMM Server
SAN
SCSI/FC Streaming Devices (Drives) SCSI/FC Media Changer Devices SCSI/FC Prop. Interface Library Mgmt. Streaming Devices (Drives) Media Changer Devices
A removable media manager is middleware that allows heterogeneous sharing of tape libraries with respect to applications, operating systems and library vendors without the need to implement static partitioning and dedicated drives. Without a tape resource management solution, different applications could access the tape resources in an uncoordinated manner. On the other hand, with a removable media manager, administration, access control and reporting are centralized in one solution. The management and tracking of off-site media pools, as shown in Figure 9, are integrated inside the removable media manager.
14
DB2 Database
A removable media manager combines the benefits of tape library sharing and logical partitioning. A single pool of tape drives and a pool of scratch cartridges can dynamically be shared between different backup applications, as shown in Figure 10. The backup applications may access virtual tape libraries that appear altogether larger than the actual hardware really is. Physical resources will be allocated on demand. Mount requests of different applications can be queued and prioritized between the applications in case of over allocation. A cartridge life cycle management policy is also included, complete with vaulting and tape quality management.
15
Backup Application A
Backup Application B
Backup Application X
TCP/IP Network
SAN
Drive s Slots
Database
Tape Library
16
Consolidation
Network
Network
Tivoli Storage Manager Clients Tivoli Storage Manager Server Tivoli Storage Manager Server
Network
Network
17
Restore Data
Backup Data
Network
dsmc -servername=old_tsm dsmc -servername=new_tsm
dsm.sys (UNIX)
servername old_tsm commethod tcpip tcpserveraddress 10.1.1.1 . . servername new_tsm commethod tcpip tcpserveraddress 10.1.1.3 . .
18
Administrator
Server
Export
Node
Import
Policy
Figure 13 Exporting data from server 1, using volumes to import data to server 2
The export commands create an operating-system-independent, self-describing copy of the specified server information. The original database is not required to recover data from this volume. IBM Tivoli Storage Manager does not keep track of file expiration, so the information contained can be recovered onto any server at any time. This is not a substitute for disaster recovery. Export and import is a relatively time-consuming process, so it is designed primarily for one-time data movement. IBM Tivoli Storage Manager offers two ways of exporting data: Export to sequential media. Export directly to another IBM Tivoli Storage Manager server in the network. The target server can be on the same platform or a different one. If you choose the first option, to export to sequential media, the target server must support the same tape media that the source server does. Restrictions: Export from an IBM Tivoli Storage Manager server cannot be imported by earlier versions. Nodes of type NAS cannot be exported.
19
Export/import administration
These commands move administrative data such as name, password, privilege classes, and administrator lock/unlocking information for server access.
Export/import node
These commands move client node definitions. Each client node definition includes the user ID, password, name of the policy domain to which the client is assigned, file compression status, backup/archive delete authority, and client node lock / unlocking data for server access. Client data can be exported in the same process. The following groupings of files are supported: Active and inactive versions of backup files, archive copies of files, and space-managed files Active versions of backup files, archive copies of files, and space-managed files Active and inactive versions of backup files Active versions of backup files Archive copies of files Space-managed files An incremental export can limit the amount of data being exported. In this case, the export command specifies the date (FROMDATE) and time (FROMTIME) the data was stored on the server. All data stored on the server before that specified date and time will not be exported.
20
If the exported client node already exists on the target server, IBM Tivoli Storage Manager can merge the client file data during import. During this process, backup objects are inserted as new active or inactive versions depending on their insertion date and time. Double archive and space management objects will be skipped. If merging is not used, IBM Tivoli Storage Manager will create a new renamed file space for the imported client.
Export/import policy
These commands move policy information from one or more policy domains. They include data such as policy domain and set definitions, management class definitions, backup, copy group, and archive group definitions, schedule definitions for each policy domain, and client node associations.
Export/import server
These commands move all or part of the server control information and client file data (if specified). These include definitions for administrator, client node, policy and schedule for each policy domain. They can optionally include: file space definitions, access authorization information, and backup, archived, and space-managed files. You can import client file data using the previously described procedures.
21
export... toserver=NEW_SERVER
LAN
OLD Database
NEW Database
22
OLD Database
NEW Database
Intermediate Volume(s)
23
Figure 16 illustrates the VMware architecture. As noted in the illustration, the Tivoli Storage Manager backup client can be installed on both the operating system that manages the physical hardware as well as the operating system that is within the virtual machine. Each installation method provides distinct benefits. Installing a backup client within the operating system of the virtual machine allows access to the individual files within the file systems, allowing multiple versions of each file within the virtual instances to be retained. Note: If an application has certain files open, these files cannot be reliably backed up. Close all open files before beginning the transports. All rules on open files in relation to a backup strategy still apply with this scenario.
Backup client on physical machine allows virtual disks to be backed up as individual files, providing an image backup capability
24
Installing a backup client on the host machine where the VMware Workstation application is installed (and where the virtual machines are running) allows for entire drives or volumes of the virtual machines to be backed up as individual files when the virtual machines are paused or shut down. This is shown in Figure 17. On enterprise-class implementations of VMware, such as the VMware ESX Server product, the drives can be released for backup as individual files by utilizing scripts and the built-in API of VMware. This provides functionality comparable to an image backup of a raw logical volume. In the event of data loss resulting from human error, it is usually sufficient to restore individual files using the backup/archive client within the virtual machine. For a more catastrophic loss, such as a virus infection, the flat file that represents the virtual drive can be restored to the directory where it resides on the host machine. If this is insufficient, once the flat file is restored, the virtual machines backup/archive client installation function can then be used to restore files to a more current version than the existing backup copy.
25
/usr
/filesystem1
/home
C:\
/filesystem2
C:\
vm2/disk1.dsk vm3/disk1.dsk
D:\
Virtual Machines
Figure 17 Mapping virtual volumes as physical files on a host machine
Physical Machine
When implementing a backup/recovery solution for a VMware installation, it is important to back up the configuration files for each virtual machine. These contain information such as the amount of RAM that is allocated, the virtual networking configuration, and other important details.
26
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "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. 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. 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. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.
27
This document created or updated on September 16, 2004. Send us your comments in one of the following ways: Use the online Contact us review redbook form found at: ibm.com/redbooks Send your comments in an Internet note to: redbook@us.ibm.com Mail your comments to: IBM Corporation, International Technical Support Organization Dept. QXXE Building 80-E2, 650 Harry Road San Jose, California 95120-6099 U.S.A.
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: AIX ibm.com Tivoli ESCON IBM TotalStorage Eserver iSeries xSeries Eserver pSeries FICON Redbooks (logo) The following terms are trademarks of other companies: Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. 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.
28