377

VTL User Guide

Embed Size (px)

DESCRIPTION

VTL user guide

Citation preview

FalconStor VTL User GuideVersion 5.1

FalconStor Software, Inc. 2 Huntington Quadrangle, Suite 2S01 Melville, NY 11747 Phone: 631-777-5188 Technical Support: 631-777-3332 Fax: 631-501-7633 Web site: www.falconstor.com

Copyright 2003-2009 FalconStor Software. All Rights Reserved. FalconStor is a registered trademark of FalconStor Software, Inc. in the United States and other countries. Linux is a registered trademark of Linus Torvalds. Windows is a registered trademark of Microsoft Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners. FalconStor Software reserves the right to make changes in the information contained in this publication without prior notice. The reader should in all cases consult FalconStor Software to determine whether any such changes have been made.

12309.2030_6318

Virtual Tape Library User Guide

ContentsIntroductionFalconStor Virtual Tape Library overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 VTL components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Plan your DeploymentVTL configurations for disk-to-disk-to-tape backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 Standard VTL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Advanced VTL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Automated Tape Caching VTL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 VTL Configuration with Single Instance Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Getting StartedPre-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 Install a certified operating system on your VTL appliance . . . . . . . . . . . . . . . . . . . . . . .17 Install VTL software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 Connect your VTL appliance to your storage network . . . . . . . . . . . . . . . . . . . . . . . . . .18 Set network information for your VTL appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Install the VTL Console on an administrative computer . . . . . . . . . . . . . . . . . . . . . . . . .19 Launch the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Connect to your VTL server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Configure your VTL server using the configuration wizard . . . . . . . . . . . . . . . . . . . . . . .21 Step 1: Enter license keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Step 2: Enter encryption keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Step 3: Set up network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Step 4: Set hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Step 5: Enable Fibre Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Step 6: Switch to target mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Step 7: Prepare devices for virtual libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Step 8: Create Virtual Tape Library database . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Step 9: Assign physical libraries/drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Step 10: Create virtual libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Step 11: Add SAN clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 Step 12:Assign virtual library to clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 Enable deduplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 Add SAN Clients (backup servers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 Prepare for backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Backup server access to the VTL server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 FC backup servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 iSCSI backup servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Discover the virtual tape library from your backup server . . . . . . . . . . . . . . . . . . . .33

Virtual Tape Library User Guide

1

Contents

Create and run backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Confirm successful backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

VTL ConsoleLaunch the console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Connect to your VTL server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 VTL console user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 Understanding the objects in the tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 Multi-Node Group object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 Server object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 Virtual Tape Library System object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Virtual Tape Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Virtual Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Virtual Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Import/Export Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Physical Tape Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Physical Tape Drives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Replica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Physical Tape Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Deduplication Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 SAN Clients object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Reports object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Physical Resources object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Group Reports object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Understanding the icons in the tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Virtual tape icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Physical resource icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Console options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 System maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Set hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Set date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Restart VTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Restart network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Reboot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 Halt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 Rescan physical devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Sort the Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Filter the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Export data from the Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 Print the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 Clear the Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 Create a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 View a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Virtual Tape Library User Guide 2

Contents

Schedule a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 Export data from a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 Set report properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 Email a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Refresh report display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Delete a report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Attention Required tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 Performance statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 Server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Software patch updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Mirror the VTL database to protect your VTL configuration . . . . . . . . . . . . . . . . . . . . . .61 Check mirroring status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 Replace a failed disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 Fix a minor disk failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 Replace a disk that is part of an active mirror configuration . . . . . . . . . . . . . . . . .62 Swap the primary disk with the mirrored copy. . . . . . . . . . . . . . . . . . . . . . . . . . . .62 Replace a failed physical disk without rebooting your VTL Server . . . . . . . . . . . .63 Remove a mirror configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Mirroring and VTL Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Multi-Node GroupsCreate a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Add servers to a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Remove a server from a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Manage Tape Drives and TapesCreate virtual tape libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 Create virtual tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 How virtual tapes are allocated from multiple LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 Round Robin Logic with Tape Capacity on Demand disabled . . . . . . . . . . . . . . . . .81 Round Robin Logic with Tape Capacity on Demand enabled . . . . . . . . . . . . . . . . .81 Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 Locate and display virtual tapes in the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 Search by barcode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 Display virtual tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 Sort all tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 Filter the display of tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 Assign virtual tape libraries to backup servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 Physical tape libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 Prepare physical libraries/drives for use with VTL . . . . . . . . . . . . . . . . . . . . . . . . . .89 Assign physical libraries/drives to VTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 Inventory physical tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 Designate a physical library or drive as disabled . . . . . . . . . . . . . . . . . . . . . . . . . . .90 Reset physical tapes in a library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 Import tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91Virtual Tape Library User Guide 3

Contents

Import data from a physical tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 Import from a tape in another virtual tape library . . . . . . . . . . . . . . . . . . . . . . . . . . .93 Export data to physical tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 Export manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 Auto Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 Export with stacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 Manage jobs in the import/export queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104 Filter the display of jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 Set import/export job properties for failed jobs . . . . . . . . . . . . . . . . . . . . . . . . . . .106 Use virtual tape drive compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 Enable/disable compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 Change firmware of a virtual library or drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 Encrypt data on virtual and physical tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 Create a key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 Change a key name or password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Delete a key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Export a key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 Import a key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 Shred a virtual tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Data DeduplicationIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116 Connecting appliances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118 Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118 Determine how many zones to use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118 VTL/SIR clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119 Zoning examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119 Replication between clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122 Directly connecting VTL and SIR without a switch . . . . . . . . . . . . . . . . . . . . . . . .123 SIR installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 Set network information for your appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 Install SIR software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 Install the SIR Console on an administrative computer . . . . . . . . . . . . . . . . . . . . .125 SIR configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126 Connect to your SIR appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126 Configure each SIR server using the configuration wizard . . . . . . . . . . . . . . . . . .127 Enable Fibre Channel target mode for each SIR server . . . . . . . . . . . . . . . . . . . .129 Prepare physical storage devices for each SIR server . . . . . . . . . . . . . . . . . . . . .130 Enable deduplication on each SIR server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 Create SIR clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 Associate your VTL server with a SIR cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . .135 Deduplication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 Add deduplication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 Manage deduplication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 Failover of deduplication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 Perform deduplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 Monitor deduplication and view statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 SIR console statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142Virtual Tape Library User Guide 4

Contents

Status of running policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 Scanner history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143 Repository statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144 VTL Console information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146 Deduplication Policies object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146 Individual deduplication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147 Virtual index tape status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151 Check replication status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151 Reclaim disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152 Add SIR disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

VTL Server FailoverOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 Failover terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157 Failover requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159 IPMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161 Determine if your appliance has IPMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161 Enable IPMI for failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161 Backup server failover configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162 Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162 HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162 AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162 Configure Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163 Check Failover status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169 Make changes to the servers in your failover configuration . . . . . . . . . . . . . . . . . . . . .170 Change your failover intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170 Force a takeover by a secondary server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171 Manually initiate a recovery to your primary server . . . . . . . . . . . . . . . . . . . . . . . . . . .171 Suspend/resume failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171 Remove a failover configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 Resuming backups after failover/failback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 BakBone NetVault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 CommVault Galaxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 CA ARCserve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 HP OpenView Storage Data Protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 EMC NetWorker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 Symantec Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 Veritas NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 Fibre Channel port behavior during failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175 Sample environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175 Before failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175 When failover occurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175 After failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176 IP address behavior during failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177 Sample environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177 After failover is configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177 When failover occurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177Virtual Tape Library User Guide 5

Contents

After failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177 Port swapping for Brocade switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178 HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180 PreTakeOver script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180 PreRecovery script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181

SIR Server FailoverOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182 Failover terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182 Failover requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183 IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183 Configure Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185 Check Failover status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189 During failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

Data ReplicationAuto Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192 Remote Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193 Replication of virtual tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194 Remote Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194 Local Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194 Replication of deduplicated tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196 Replication requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198 Configure replication for virtual tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199 Configure replication for deduplicated tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205 Add a target SIR replication server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205 Replicating deduplicated tapes from a server using an alternate NIC . . . . . . . . . .207 Routing preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207 Configure replication using the alternate NIC . . . . . . . . . . . . . . . . . . . . . . . . . . . .209 Check replication status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210 Promote a replica resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212 Promote a replica resource without breaking the replication configuration . . . . . . . . . .212 Access data on a replicated VIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213 Change your replication configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213 Suspend/resume replication schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213 Stop a replication in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214 Manually start the replication process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214 Remove a replication configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214 Replication and VTL Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214 Consolidate tapes from multiple locations to a single data center . . . . . . . . . . . . . . . .215

Automated Tape CachingOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216 Tape caching policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217 Create/change a tape caching policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217Virtual Tape Library User Guide 6

Contents

Set global tape caching options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221 Disable a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221 Create a cache for your physical tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222 Create uncached virtual tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223 Manually migrate cached data to physical tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224 Force migration of an entire tape to physical tape . . . . . . . . . . . . . . . . . . . . . . . . . . . .224 Reclaim disk space manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224 Renew cache for a direct link tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224 Recover data using Automated Tape Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225

Fibre Channel ConfigurationOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226 Installation and configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227 Configure Fibre Channel hardware on server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228 Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229 Persistent binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231 QLogic HBAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232 QLogic Multi-ID HBAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234 NPIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235 FSHBA.CONF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237 Configure Fibre Channel hardware on clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239 NetWare clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239 HBA settings for Fibre Channel clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240 Windows 2000/2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240 HP-UX 10, 11, and 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241 AIX 4.3 and higher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241 Linux all versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241 Solaris 7, 8, 9, and 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242 NetWare all versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242 Verify your hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243 Set QLogic ports to target mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246 Single port QLogic HBAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246 Multi port QLogic HBAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247 Associate World Wide Port Names with clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249

iSCSI ClientsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251 Supported platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251 iSCSI users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251 Windows configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252 Prepare client initiators to access your VTL server . . . . . . . . . . . . . . . . . . . . . . . .252 Enable iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252 Add an iSCSI client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253Virtual Tape Library User Guide 7

Contents

Create targets for the iSCSI client to log onto . . . . . . . . . . . . . . . . . . . . . . . . . . . .254 Assign a virtual tape library to the iSCSI target . . . . . . . . . . . . . . . . . . . . . . . . . . .255 Log the client onto the target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255 Disable iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256 Linux client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257 Prepare the iSCSI initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257 Enable iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257 Add an iSCSI client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257 Create targets for the iSCSI client to log onto . . . . . . . . . . . . . . . . . . . . . . . . . . . .258 Assign a virtual tape library to the iSCSI target . . . . . . . . . . . . . . . . . . . . . . . . . . .258 Log the client onto the target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258

IBM 3494 ConfigurationOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260 Adding/removing tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260

IBM iSeries ConfigurationOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262 Set up the tape library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262 Import cartridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264 Export cartridges (move to vault) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264

Hosted BackupOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265 Configure Hosted Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265 Stopping VTL processes with Hosted Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267

NDMP Backup SupportOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268 Configure NDMP support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268

ACSLS and Library Station ConfigurationOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 Hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272 Configure VTL to work with ACSLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272 Set eject policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274 Filter tapes displayed in the VTL console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274 Add/remove tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274

Virtual Tape Library User Guide

8

Contents

OpenStorage OptionTerminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275 Before you install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276 Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277 Verify your configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279 Commands - detailed descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280 Add a VTL server - creatests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280 Create and assign an LSU - addlsu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280 List VTL servers - liststs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281 List LSUs - listlsu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281 List native devices - status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282 Rescan native devices - rescan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282 Remove a VTL server - deletests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282 Delete an LSU - deletelsu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283 Get/set the message logging level - loglevel . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283 Best practice guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284 Deciding how many LSUs to create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284 Deciding how many concurrent jobs to allow . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284

Email AlertsConfigure Email Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286 Modify Email Alerts properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290 Script/program trigger information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291 Customize email for a specific trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291 New script/program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291

VTL ServerStart the VTL server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294 Restart the VTL server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294 Check the VTL Server processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295 Stop the VTL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296

Command LineUsing the command line utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .297 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .297 Common arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298 Login/logout to the VTL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299 Virtual devices / Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300 Automated tape caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315Virtual Tape Library User Guide 9

Contents

System configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319 Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .321 Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328 Physical devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335 Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .341 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342 Technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350 Deduplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351

AppendixSystem security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .354 LUN migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .356

TroubleshootingGeneral Console operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .358 Physical resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360 Logical resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361 Backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .364 Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .364 Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365 Take an X-ray of your system for technical support . . . . . . . . . . . . . . . . . . . . . . . . . . .366

Index

Virtual Tape Library User Guide

10

Virtual Tape Library User Guide

IntroductionFalconStor Virtual Tape Library overviewFalconStor Virtual Tape Library (VTL) increases the speed and reliability of backups that use standard third-party backup applications by leveraging disk to emulate industry-standard tape libraries. VTL leverages your existing Fibre Channel or IP SAN to transfer data to and restore data from a disk-based virtual tape at ultra-high speeds. Since VTL uses disk to back up data, it eliminates the media and mechanical errors that can occur with physical tapes and drives. And, because VTL can emulate more tape drives than your physical tape library really has, more backup streams can run simultaneously, enabling organizations to easily complete their backups within the allotted backup window. Because you may already have physical tapes that you would like to protect, you can import data from physical tapes into your virtual tape system. If you ever need to recover files from a physical tape, you can use VTL to access those tapes for immediate recovery. For additional data protection, the data on virtual tapes can be exported to physical tapes for long-term data archiving. Data can also be copied to physical tapes using your backup applications copy function.

VTL componentsThere are several components to VTL: VTL appliance - An appliance running VTL software. VTL Console - The graphical administration tool where you configure VTL, add/configure clients, set properties, and manage the import/export of tapes. VTL Clients - The backup servers that use VTL. VTL supports Fibre Channel and iSCSI backup servers on most major platforms. If the Hosted Backup feature is available, you can install a certified backup backup application directly on the VTL appliance, eliminating the need for a dedicated backup server. (Optional) Single Instance Repository (SIR) appliance - The server that manages the SIR system. (Optional) SIR Console - The graphical administration tool where you configure SIR, monitor deduplication processes, and manage SIR storage.

Virtual Tape Library User Guide

11

Virtual Tape Library User Guide

Plan your DeploymentWhen planning your VTL deployment, you need to determine what type of configuration best suits your organization. In addition to disk-to-disk, the flexibility of FalconStor VTL supports three possible disk-to-disk-to-tape (D2D2T) configurations. In a D2D2T scenario with FalconStor VTL, you choose your preferred configuration of the various components your third party backup software, the VTL appliance, the disk storage managed by VTL for use as the virtual tape library, and one or more physical tape libraries. Regardless of which configuration you choose, VTL makes it easy for you to manage both virtual tapes and physical tapes.

VTL configurations for disk-to-disk-to-tape backup Standard Configuration - Backup software runs on a backup server or on the VTL appliance and manages all tapesvirtual and physical. Data is copied to physical tape using the backup softwares tape copy function. Advanced Configuration - Backup software runs on a backup server and manages the backup to virtual tape. VTL manages the disk storage and the export of data to the physical tape library. Automated Tape Caching Configuration - As in the Advanced Configuration, backup software runs on a backup server and transparently manages the backup to virtual tape. In addition, this configuration provides the backup application with transparent access to data regardless of whether the data is on disk or on tape. Flexible migration policies determine when data will be moved to physical tape. Single Instance Repository Configuration - One or more Single Instance Repository (SIR) appliances is used along with the VTL appliance to eliminate redundant backup data without impacting your established backup window.

Virtual Tape Library User Guide

12

Plan your Deployment

Standard VTL ConfigurationIn the Standard VTL Configuration, the backup software manages all tapesvirtual and physicalby treating the virtual tape library as though it were just another standalone tape library attached to the backup server. To copy data from virtual to physical tapes, the backup softwares Tape Copy function is utilized. In this configuration, the backup software runs on an existing backup server or on the VTL appliance itself (with the Hosted Backup Option). The Standard VTL Configuration is ideal for organizations that already have a backup process in place with which they are comfortable but which is not meeting all of their backup objectives. Adding a VTL appliance as another tape library allows you to easily increase your parallel backup streams and take advantage of VTLs rapid data recovery without having to alter your current configuration. With the backup application managing the entire backup process, virtual tapes and physical tapes are seen in the same way: a virtual tape is just another tape. With the Standard VTL Configuration, backups to virtual tapes occur quickly. Then, at a later time, the backup server can copy the data to physical tapes without impacting the production environment. Because the backup server performs the tape copying function in addition to backups additional overhead can be incurred by the backup server. Therefore, it is best to perform tape copying at off-peak hours. While VTL natively accelerates backup from the backup server to virtual tape, data transfer between application servers and the backup application can be accelerated by hosting a backup application on the VTL appliance itself. This shortens the data path between the application server and the backup application/server and therefore enhances backup performance.

Virtual Tape Library User Guide

13

Plan your Deployment

Advanced VTL ConfigurationIn the Advanced VTL Configuration, the backup software manages backups to the virtual tape library while the VTL appliance controls the export of data from virtual tapes to physical tapes. VTL dramatically accelerates backups by acting as a defacto cache to your physical tape library and enables data to be moved to physical tapes as a background process without impacting production servers. This is an innovative approach to backup that addresses the limitations of conventional tape backup. Moreover, since VTL manages the export of data from virtual to physical tapes, there is no additional overhead for the backup server. As in the Standard VTL Configuration, the backup software runs on an existing backup server or on the VTL appliance itself (with the Hosted Backup Option). With the Advanced VTL Configuration, backups to virtual tapes occur very quickly. Then, at a later time, when you are done using a given tape, you can export data to physical tape for offsite vaulting or disaster recovery without impacting the production environment. VTL can also be set up in Auto Archive mode so that after each backup to virtual tape completes, data is automatically exported to physical tape. The Advanced VTL Configuration requires you to set up the initial physical tape library emulation from within the VTL Console so that there is a 1:1 mapping, with identical barcodes, between virtual and physical tapes. This enables the backup software to keep track of backup tapes and prevents tapes from being created that would be unidentifiable by the backup software. Whenever data is written to physical tape, the virtual tape can then be deleted or the copy can be left on the virtual tape for rapid recovery. The physical tape will always have the same barcode as its virtual tape counterpart. This gives you the flexibility to easily restore from either virtual or physical tape. When it comes time to restore, the backup software identifies the barcode of the tape containing the needed data. If the data still resides on virtual tape (it was never exported or it was exported with the virtual tape left intact), it can be restored very quickly because it is being read from disk. If the data is only on physical tape, the tape must first be re-imported into VTL with a few simple keystrokes in the VTL Console so that the backup software can access it and restore in its usual manner.

Virtual Tape Library User Guide

14

Plan your Deployment

Automated Tape Caching VTL ConfigurationWith the Automated Tape caching option, tapes will always appear to be inside virtual libraries and will be visible to the backup application regardless of whether the data is actually on disk or tape. This means that the backup application will always have direct access to data regardless of whether the data is on disk or on physical tape. As in the Advanced VTL Configuration, backup software runs on a backup server and transparently manages the backup to virtual tape. In this configuration, VTL acts as a transparent cache to the physical tape library, dramatically accelerating backups while enabling the data to be written to physical tapes, as a background process without impacting production servers, based on extremely flexible migration policies (age of data, time of day, disk space, end of backup, etc.). The Automated Tape Caching Option also provides very flexible space reclamation policies (free space immediately upon migration, after specified retention period, when run out of space, etc.)

Virtual Tape Library User Guide

15

Plan your Deployment

VTL Configuration with Single Instance RepositoryThe Single Instance Repository (SIR) data deduplication solution integrates seamlessly with VTL to eliminate redundant data without impacting your established backup window. SIR offers as much as a 30:1 reduction of backup data, minimizing replication time and storage requirements. SIR can operate as a single node (one active SIR server) or as a multi-node cluster (two or four active SIR servers). If replication is configured, the attached SIR also replicates its repository and metadata, effectively performing global data deduplication. Any data duplicated across remote sites is deduplicated at the central site, enabling only globally unique data to be replicated to the disaster recovery site. A separate management console for the SIR Server appliance can be used for storage management tasks that are directly related to that appliance, such as adding additional storage capacity. The SIR Console also displays real-time and historical statistics related to deduplication.

Virtual Tape Library User Guide

16

Virtual Tape Library User Guide

Getting StartedVTL has been designed for quick setup. Your vendor will let you know whether or not your VTL appliance has been preconfigured for you. Some features may not be available for all VTL appliances. The following steps guide you through setting up and configuring your VTL appliance.

Pre-installationThe following table lists the VTL server requirements. While this information is accurate as of the date of its release, you should check the release notes or the certification matrix on the FalconStor website for any updates.CPU Memory Intel/AMD processors, 2+GHZ VTL server: 4 GB RAM is recommended. SIR server: 4 GB RAM minimum. 16 GB RAM is recommended. Red Hat Enterprise Linux 5.1 CentOS 5.1 QLogic FC HBAs. Gigabit Ethernet network cards that are supported by Linux. 40GB disk space. Fibre Channel, SCSI, or SATA hard drive. SCSI or IDE CD-Rom drive.

Operating system Fibre Channel Host Bus Adapter Network Interface Card Hard Disk CD-Rom Drive

Install a certified operating system on your VTL applianceYou must install a certified operating system on your VTL appliance before you install VTL. If you purchased VTL as a turnkey appliance, this will have been done for you.

Virtual Tape Library User Guide

17

Getting Started

Install VTL softwareIf you purchased VTL as a turnkey appliance, this will have been done for you. Otherwise, you will need to install VTL software on your appliance. 1. Log in to the VTL appliance. 2. Mount the VTL CD. The recommended way to mount the CD is as follows:# mount /mnt/ # cd /mnt/

3. At the # prompt, type ./vtlinstall. 4. Type Y to continue. 5. On the next screen, click Enter to configure the maximum number of LUNs per adapter. 6. On the next screen, click Enter to configure the maximum number of SCSI disks to scan. The installation procedure checks Fibre Channel target options. 7. On the next screen, type the number representing the target mode HBAs and click Enter. 8. On the next screen, type N to skip the step that configures Network Time Protocol on the VTL appliance. 9. Type Y to accept the configuration when you see the screen that summarizes the VTL appliance configuration. Installation continues unaided from this point. When it is complete, you will see a prompt (#).

Connect your VTL appliance to your storage networkFor Fibre Channel appliances, refer to the Fibre Channel Configuration chapter for detailed information about preparing Fibre Channel environments.

Virtual Tape Library User Guide

18

Getting Started

Set network information for your VTL appliance1. Contact your network administrator to obtain the following for your VTL appliance: IP address - You must use static IP addresses for the VTL appliances in an active-active failover configuration. Netmask Default gateway Primary name server information. 2. Power up your VTL appliance and log in. You will need to have a monitor and keyboard to access the VTL appliance. Log into your VTL appliance using the default user name and password (case sensitive). If you purchased your appliance from FalconStor, the defaults are: Default user name - root Default password - IPStor101 3. Change the IP address, netmask, default gateway, and primary name server to what your network administrator provided to you. You can type netconfig to load the utility that allows you to change them. 4. Reboot your VTL appliance by typing reboot.

Install the VTL Console on an administrative computerThe VTL Console is the graphical administration tool where you can manage your VTL server. The computer that runs the VTL Console needs connectivity to the network segment where VTL is running. This is because it communicates directly with the server and clients (backup servers). The Console may be installed on any number of machines, including the clients themselves, provided that they have a Graphical User Interface. The installation CD includes a setup program for installation on Windows XP, 2000, and 2003 computers. When the CD Browser launches, select Install Products --> Install VTL Console. (Note that you must be a Power User or Administrator to install the Console.)

Launch the ConsoleTo launch the Console, select Start --> Programs --> FalconStor --> VTL 5.10 --> VTL Console.

Virtual Tape Library User Guide

19

Getting Started

Connect to your VTL serverIf your server already appears in the tree, right-click it and select Connect. For a multi-node group, right-click the group and select Connect to connect to all of the servers in the group. If your server does not appear in the tree, do the following to add it: 1. Right-click the VTL Servers object and select Add. If you are running on a Windows machine or if you used eth0 to get a DHCP address on a FalconStor appliance, you can right-click the VTL Servers object and select Discover to detect VTL servers in a range of IP addresses. You should then specify the subnet range of your VTL server and wait for the VTL server hostname to appear in the navigation tree. For VTL appliances, the hostname has the format FSxxxxx, where xxxxx is a unique number for your VTL appliance, which is displayed on a label on your appliance. When the hostname appears in the navigation tree, right-click it and select Connect. 2. Type the VTL Server name or address (for example, 10.7.12.91) and enter a valid user name and password (both are case sensitive) to log in. If you purchased an appliance from FalconStor, log in using: User Name: root and password: IPStor101. Both are case sensitive. Once you are connected to a server, the server icon will change to show that you are connected. After connecting to the server, the configuration wizard launches.

Virtual Tape Library User Guide

20

Getting Started

Configure your VTL server using the configuration wizardNotes: If you are using VTL in a Fibre Channel environment, refer to the Fibre Channel Configuration section first before beginning the wizard. If you are setting up a failover configuration, refer to the VTL Server Failover section first before beginning the wizard.

Virtual Tape Library (VTL) provides a convenient wizard that leads you through your VTL configuration. If your VTL server has not been configured yet, the configuration wizard will be launched when you connect to it.

Press Next to begin the steps in the wizard. If you want to skip a step, press Skip.

Virtual Tape Library User Guide

21

Getting Started

Step 1: Enter license keysClick the Add button and enter the keycodes shown on your Product Keycode certificates, one at a time. Be sure to enter keycodes for any options you have purchased. Each VTL option requires that a keycode be entered before the option can be configured and used. Configuration note: After completing the configuration wizard, if you need to add license keys, you can right-click your VTL server appliance and select License.

Step 2: Enter encryption keysIndicate if you want to add encryption keys. With encryption, you can create one or more keys that can be used to encrypt data when it is exported to physical tape and decrypt it when it is imported back to virtual tapes. The data on the tape cannot be read without being decrypted using the appropriate key. 1. Click New. 2. In the Key Name text box, type a unique name for the key. 3. In the Secret Phrase text box, type the phrase that will be used to encrypt the data. Note: We recommend that you save your secret phrase somewhere because once you have created a key, you cannot change the secret phrase associated with that key. 4. In the New Password and Confirm Password text boxes, type a password for accessing the key. You will need to provide this password in order to change the key name, password, or password hint, or to delete or export the key. You do not have to provide a unique password for each key. In fact, if you use the same password for multiple keys, you have to provide the password only once when you export multiple keys that all use the same password. 5. In the Password Hint text box, type a hint that will help you remember the password. This hint appears when you type an incorrect password and request a hint. Refer to Encrypt data on virtual and physical tapes for detailed information about encryption keys. Configuration note: After completing the configuration wizard, if you need to add encryption keys, you can right-click your VTL server appliance and select Key Management.

Virtual Tape Library User Guide

22

Getting Started

Step 3: Set up networkNote: Changing the IP address is allowed only before you configure replication. To change the IP address after you configure replication, you must remove the replication target, change the IP address, and then configure replication again. 1. Enter information about your network configuration.

Domain name - Internal domain name. Append suffix to DNS lookup - If a domain name is entered, it will be appended to the machine name for name resolution. DNS - IP address of your Domain Name Server. Default gateway - IP address of your default gateway. NIC - List of Ethernet cards in the server. Enable SSH - Enable/disable the ability to use the SSH protocol. The VTL server must have openssh installed in order to use SSH. Enable FTP - Enable/disable the ability to FTP into the server. The VTL server must have vsftp installed in order to use FTP.

Virtual Tape Library User Guide

23

Getting Started

2. Click Config NIC to configure each network interface card (NIC).

If you select Static, you must click the Add button to add IP addresses and subnet masks. MTU - Set the maximum transfer unit of each IP packet. If your card supports it, set this value to 9000 for jumbo frames. Configuration note: After completing the configuration wizard, if you need to change these settings, you can right-click your VTL server appliance and select System Maintenance --> Network Configuration.

Step 4: Set hostnameEnter a valid name for your VTL appliance. Valid characters are letters, numbers, underscore, or dash. The server will automatically reboot when the hostname is changed.

Configuration note: After completing the configuration wizard, if you need to change the name again, you can right-click your VTL server appliance and select System Maintenance --> Set Hostname.Virtual Tape Library User Guide 24

Getting Started

Step 5: Enable Fibre ChannelNote: Before you enable Fibre Channel, verify that your Fibre Channel configuration is set properly. Refer to the Fibre Channel Configuration section for information. If you do not have or will not be using Fibre Channel, click Skip. Otherwise, this step takes just a few seconds and there are no additional screens to go through. An Everyone_FC client will be created under SAN Clients. This is a generic client that you can assign to all (or some) of your tape libraries/drives. It allows any WWPN not already associated with a Fibre Channel client to have read/write non-exclusive access to any tape libraries/drives assigned to Everyone_FC.

Step 6: Switch to target mode(FC edition only) Target mode allows a port to receive requests from your backup server(s). If you haven't already done so, you will need to switch any initiator zoned with a backup server to target mode so that the backup server can see the VTL server. You will then need to select the equivalent adapter on the secondary server and switch it to target mode. Note: If a port is in initiator mode and has devices attached to it, that port cannot be set for target mode. In order to identify your ports, you need to know the WWPN of each. One way to find the WWPN is through the SNS table at your Fibre Channel switch. Alternatively, for QLogic HBAs, you can find the WWPN in the BIOS (press Ctrl+Q during boot up). For VTL Failover, if you are not using multi-ID HBAs, you minimally need two ports for client connectivity (one for normal operation, one for standby) and one initiator port to connect to storage. If you are using multi-ID HBAs, you need a minimum of one port for client connectivity and one for storage. You will get a Loop Up message on your VTL server if a QLogic port has successfully been placed in target mode.

Virtual Tape Library User Guide

25

Getting Started

(Single-ID HBAs) Select which ports should be in target mode.

(Multi-ID HBAs) Add an alias WWPN for the specified port.

All targets must use either the soft or hard Alpa (Arbitrated Loop Physical Address) creation method. You cannot mix and match. Soft Alpa creation method - HBA firmware generates Alpa addresses. Hard Alpa creation method - You have to specify Alpa addresses. Configuration note: After completing the configuration wizard, if you need to switch a ports mode, you can right-click the adapter and select Enable/Disable Target Mode.

Step 7: Prepare devices for virtual librariesThis step prepares physical devices for use with VTL. Some of these devices will be used for virtual libraries/tapes/drives, while others can be reserved for deduplication resources. Depending upon your configuration, this step can take just a few seconds and there will be no additional screens to go through. Configuration note: After completing the configuration wizard, if you add new hardware that you need to prepare, you can right-click Physical Resources and select Prepare Devices. Hard drives should be set to Reserved for Virtual Device while tape libraries/drives should be set to Reserved for Direct Device.

Virtual Tape Library User Guide

26

Getting Started

Step 8: Create Virtual Tape Library databaseThe database contains the configuration information for the VTL. If your VTL appliance has been preconfigured, this step takes just a few seconds and there are no additional screens to go through. If your VTL appliance has not been preconfigured, you must have already prepared storage resources for use with VTL. 1. Select how you want to create the Virtual Tape Library database. The Virtual Tape Librarys Database Resource needs at least 6,015 MB of disk space. Custom lets you select which physical device(s) to use and lets you designate how much space to allocate from each. Express automatically creates the resource for you using an available device(s), but is not recommended unless your appliance has been preconfigured. 2. If desired, enable disk compression for VTL. This can save disk space because it compresses the data that is being written to your virtual tapes. It does not affect data that is exported to physical tapes because that is controlled by the tape drive. 3. (Tape Caching only) Set the global disk capacity threshold. When this threshold value is reached, migration from virtual tape to physical tape will be triggered for all virtual libraries using the disk capacity threshold. 4. Click Finish to create the database. If you know that you have a disk available, you can create a mirror for the VTL database in order to protect your VTL configuration. Even if you lose your VTL server, the data on your tapes will be maintained. Mirroring the database is highly recommended. Refer to Mirror the VTL database to protect your VTL configuration for more information. Configuration note: After completing the configuration wizard, if you want to enable disk compression, right-click the Virtual Tape Library System object and select Properties. To mirror the database at a later time, right-click the Database object (under the Virtual Tape Library System object) and select Mirror --> Add.

Step 9: Assign physical libraries/drivesIf you will be importing data from physical tapes into your virtual tape library or exporting virtual tapes to physical tapes, you must assign your physical tape libraries/drives to VTL. This step also inventories the physical tapes in your library/drive so that you can create virtual tapes that match your physical tapes. Configuration note: After completing the configuration wizard, if you need to assign new physical libraries/drives and inventory slots again, you can right-click Virtual Tape Library System and select Configuration wizard.Virtual Tape Library User Guide 27

Getting Started

Step 10: Create virtual librariesSelect the tape library that you are emulating.

If you have a physical tape library, you need to create a virtual tape library that resembles it. This way the virtual tapes will use the same format as those of the physical tapes. This is important for importing and exporting functions and guarantees that your backup application will accept the tapes. If you are using Automated Tape Caching, you will only see your physical tape libraries listed. Select the check box and the system will automatically match your physical library. You will have to enter information about the tape drives in your library, including: Barcode information Tape properties such as Tape Capacity On Demand and maximum tape capacity. If you are using the Single Instance Repository option (SIR), it is highly recommended that you use Tape Capacity On Demand. If you are using Automated Tape Caching, you will have to select the type of data migration triggers that you want to set and specify when the data that has been migrated to physical tape can be deleted to free up cache disk space. If you are not using Automated Tape Caching, you need to determine if you want to use auto archive or auto replication for this virtual library.

Refer to Create virtual tape libraries for detailed information about creating virtual tape libraries and Automated Tape Caching for detailed information about configuring Automated Tape Caching.

Virtual Tape Library User Guide

28

Getting Started

After you create a virtual tape library you will be prompted to create virtual tapes. Refer to Create virtual tapes for detailed information about creating them. After you create virtual tapes, you will be prompted to create more virtual libraries or to continue with the next step.

Step 11: Add SAN clientsThis step allows you to select the clients (backup servers) to which you will be assigning a tape library. Refer to Add SAN Clients (backup servers) for detailed information about adding clients. Configuration note: After completing the configuration wizard, if you need to add new clients, you can right-click Virtual Tape Library System and select Configuration wizard or you can right-click the SAN Clients object and select Add.

Step 12:Assign virtual library to clientsIf you added clients, do the following: 1. Select a client to assign. 2. Click Finish when you are done. Refer to Assign virtual tape libraries to backup servers for detailed information about assigning libraries to clients. Configuration note: After completing the configuration wizard, if you need to assign new virtual libraries, you can right-click Virtual Tape Library System and select Configuration wizard or you can click a virtual tape library or a client and select Assign.

Virtual Tape Library User Guide

29

Getting Started

Enable deduplicationIf you have a preconfigured VTL appliance, deduplication has already been enabled. If your appliance was not preconfigured, you can now enable deduplication. Refer to Data Deduplication for details.

Add SAN Clients (backup servers)You can add SAN Clients in the following two ways: Use the configuration wizard - If you have already configured your system, you can launch the wizard by right-clicking on the Virtual Tape Library System object in the console and selecting Configuration Wizard. Right-click the SAN Clients object and select Add.

After launching the wizard, follow these steps to continue: 1. Enter the client name or IP address. 2. Select the protocol(s) being used by the client.

For Fibre Channel clients, click Next and select the initiator WWPN for the client. If FC initiator ports on the backup server are already zoned with VTL's target port and are properly connected/powered up, they are listed automatically and you can select specific initiators from that zone. In addition, if there is only one initiator WWPN in the client, VTL will automatically select it for you and the dialog will not be displayed. If no WWPNs are listed, the backup server is not currently zoned with the VTL appliance. Click Next and set Fibre Channel options. Enable Volume Set Addressing may be required for particular Fibre Channel clients, such as HP-UX clients that require VSA to access storage devices.

Virtual Tape Library User Guide

30

Getting Started

Select Enable Celerra Support if you have a licensed EMC Celerra client. For iSCSI clients, click Next and select the initiator that the client uses. If the initiator does not appear, you can manually add it. For additional details on adding and managing iSCSI clients, refer to the iSCSI Clients chapter. Click Next and add/select users who can authenticate for this client. When you add users, you will have to enter a name and password for each. If you select Allow Unauthenticated Access, the VTL Server will recognize the client as long as it has an authorized initiator name. With authenticated access, an additional check is added that requires the user to type in a username and password. More than one username/password pair can be assigned to the client, but they will only be useful when coming from the machine with an authorized initiator name. 3. Click Finish when you are done.

Virtual Tape Library User Guide

31

Getting Started

Prepare for backupsBackup server access to the VTL serverThere are two access schemes that determine how backup servers access the VTL server: In the "Open Access" scheme, access is controlled purely by zoning. The pre-defined Everyone_iSCSI or Everyone_FC client represents the backup server and all or some of your virtual tape libraries/drives must be assigned to the Everyone client. In the Secured Access scheme, access is dictated by creating specific clients to represent specific backup servers instead of using the built-in Everyone_iSCSI or Everyone_FC client. In this mode, each backup server can access only its own designated virtual tape library or drives.

FC backup serversIn order for Fibre Channel backup servers to access VTL resources, you must do the following: 1. Set QLogic HBA ports to target mode. 2. Add a FC client for each backup server (Secured Access) or use the Everyone_FC client (Open Access). 3. Create and assign a virtual tape library to clients. 4. Discover the virtual tape library from your backup server. Refer to Discover the virtual tape library from your backup server for more information. Additional information about steps 1-3 can be found in the Fibre Channel Configuration chapter.

iSCSI backup serversIn order for iSCSI backup servers to access VTL resources, you must do the following: 1. Add an iSCSI client for each backup server (Secured Access) or use the Everyone_iSCSI client (Open Access). 2. Create targets for the iSCSI client to log into. 3. Create and assign a virtual tape library to the iSCSI target. 4. Register client initiators with your VTL server. 5. Log the client onto the target.Virtual Tape Library User Guide 32

Getting Started

6. Discover the virtual tape library from your backup server. Refer to Discover the virtual tape library from your backup server for more information. Additional information about steps 1-5 can be found in the iSCSI Clients chapter.

Discover the virtual tape library from your backup serverTo enable your backup server to recognize the default virtual tape library and drives, perform a device scan on your backup server at the operating system level and then use your backup software to scan for new devices as well. Use your operating system to scan for hardware changes Windows The steps to do this vary according to the backup servers operating system. For Fibre Channel environments, if your zoning has been correctly configured, and devices have been properly assigned to clients, a simple bus rescan performed on the client should show the new backup devices. Of course, this procedure varies depending on the OS. To discover a tape library on a backup server running a Windows operating system: 1. Select Control Panel --> Administrative Tools --> Computer Management. 2. In the left pane, under System Tools, select Device Manager. 3. In the right pane, right-click the backup server and select Scan for hardware changes. New devices representing the specific VTL resources will appear (the library under Medium Changers and tape drives under Tape Drives) and if the appropriate tape drive and tape library device drivers are installed on the backup server, the correct device name and type are associated and the devices will become ready for use by the backup software. If a new device is unknown, right-click it to display its Properties. Acquire and update the driver according to your Windows documentation. Your backup software may include a procedure that updates drivers. Linux To discover a tape library on a backup server running a Linux operating system: 1. Rescan your host adapter. Rescanning in Linux is host adapter-specific. For QLogic:echo "scsi-qlascan" > /proc/scsi/qla/

For Emulex:sh force_lpfc_scan.sh "lpfc"

2. Identify the detected devices.# cat /proc/scsi/scsi

Virtual Tape Library User Guide

33

Getting Started

3. For each identified device do the following:# echo "scsi add-single-device " >/proc/scsi/scsi

where is the host adapter number, is channel number is the target id and is the LUN number. HP-UX To discover a tape library on a backup server running HP-UX: 1. Rescan the devices.# ioscan -fnC

2. Generate device files.# insf -e

3. Verify the new devices.# ioscan -funC

AIX

To discover a tape library on a backup server running AIX: 1. Rescan devices.# cfgmgr -vl fcsX

where X is the number of the FC adapter. 2. Verify the new devices.# lsdev -Cc

Solaris

1. Determine the FC channels.# cfgadm -al

2. Force a rescan.cfgadm -o force_update -c configure cX

where X is the FC channel number. 3. Install device files.# devfsadm

Use backup software to detect new devices

The steps to do this vary according to your backup software. After you complete the procedure, you are ready to create and run backup jobs.

Note: For all other platforms, such as Unix and Linux, consult the appropriate reference material that came with your backup software for details on how to load drivers and how to perform discovery for hardware changes.

Virtual Tape Library User Guide

34

Getting Started

Create and run backup jobsOnce your backup server software can discover and access the virtual tape library/ drives defined in the VTL Server, you can start to use the VTL as if it were a real tape library. The preparation required to start a backup job successfully is identical whether you are using a real tape library or a virtual one. You simply configure the backup software to use the VTL just like you would a physical tape library. Generally, in order to perform a backup to a newly acquired/configured tape library, you need to: 1. Add new tape media. Real library: Buy new tapes and insert into the mail slot followed by a sequence of keys pressed on the keypad of the tape library. VTL: Virtual tapes are typically created when you create a virtual tape library. Additional virtual tapes can be created as needed. 2. Start a "tape inventory" process in your backup software. 3. Format the tapes and assign them into various "tape pools". 4. Define backup jobs and associate tapes with each job. When one or more backup jobs start to kick-off, tapes are allocated by the backup software and are loaded into the tape drives. Backup data is then sent to the tapes until the backup job is done. The backup software then sends commands to unload the tapes and return them to their assigned slot within the library. All of the above actions are emulated by VTL. When it is time to remove a tape from a physical library and to store it onto a nearby tape shelf, the administrator must physically walk over to the library, use a key pad/console to select the tape to be removed, and then catch the tape as it is physically being ejected from the "mail slot". The above can sometimes be done via commands from within the backup software. For a VTL server, obviously there is no keypad or physical mail slot for this purpose. However, the FalconStor VTL server has a Virtual Tape Vault to hold all the virtually "ejected" tapes from any virtual tape library. In the case where an "eject" is performed by the backup software, the ejected virtual tape will be automatically placed in the Virtual Tape Vault. This can be confirmed using the VTL Console (select the Virtual Tape Vault object and verify the virtual tape is indeed there). If tape removal is not done using the backup software, the equivalent of a "keypad" is to use the VTL Console and right-click the virtual tape and select Move to Vault. Typically, after the backup is complete, the backup software will automatically remove the tape from the drive and store it back in its assigned library slot. When the deduplication policy executes at the designated time, or when you click Run manually at the VTL Console for the selected policy, you can use the SIR Console to confirm that the deduplication policy is running. To do this,Virtual Tape Library User Guide 35

Getting Started

highlight the SIR server and select the Scanner processes tab in the right panel to see a list of currently running policies. Special note for NetBackup users - To prevent a backup from going to the same tape more than once, when you are configuring backup jobs for Microsoft Exchange, DO NOT span your policies across tapes.

Confirm successful backupsWhile a backup job is running, you can use the VTL Console to verify that data is being written to virtual tapes. 1. In the VTL Console, expand the Virtual Tape Library System object. 2. Expand Virtual Tape Libraries, the specific library, and then Tapes. 3. Under the Tapes object, select each tape that is included in a backup job. In the right-hand pane, you should see a value for Data Written, which updates dynamically during a backup job. After the backup job completes, use your backup software to verify that the data was written completely and can be restored.

Virtual Tape Library User Guide

36

Virtual Tape Library User Guide

VTL ConsoleThe FalconStor Management Console for VTL allows you to manage your VTL system, users, and administrators; add/configure clients; set server properties; monitor VTL activity; create deduplication policies/monitor deduplication; manage the import/export of tapes, and run/view reports.

Launch the consoleTo launch the console, select Start --> Programs --> FalconStor --> VTL 5.10 --> VTL Console.

Connect to your VTL server1. Right-click your VTL server and select Connect. If you have a multi-node group, right-click the group and select Connect to connect to all of the servers in the group. You must use a user name and password that exists for all servers in the groups. If you want to connect to a server that is not listed, right-click the VTL Servers object and select Add. If you are running on a Windows machine, you can right-click the VTL Servers object and select Discover to detect VTL servers in a range of IP addresses. 2. Enter a valid user name and password (both are case sensitive). Once you are connected to a server, the server icon will change to show that you are connected: If you connect to a server that is part of a failover configuration, you will automatically be connected to both servers. Note: Multiple administrators can access a server at the same time. Changes to the servers configuration are saved on a first-come, first-served basis. The VTL console