Virtual Tape Library VTL User Guide Sun Microsystems, Inc. www.sun.com Part No. 96267 May 2008, Revision G Submit comments about this document at: glsfs@sun.
Copyright 2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
Revision History Short Name Part # VTL User Guide 96267 96267 • G Revision Date Comments Nov 2006 Base document supplied by the vendor. A Jan 2007 Major revision. B Mar 2007 Published. EC 131376. C Aug 2007 Major revision. D Nov 2007 Minor revision. E Feb 2008 Major revision to cover VTL Plus 2.0 F Mar 2008 Major revision to the commandline appendix G May 2008 Revised for VTL Plus 2.0 Update 1.
iv VTL User Guide • May 2008 G • 96267
Contents About this book 1.
2. 3. 4.
Copying tapes 104 Moving tapes between virtual and physical libraries 107 Managing tape caching 120 Creating and viewing reports 123 Encrypting and shredding data 127 Working with the Event Log 135 Using the Attention Required tab Managing VTL servers 140 5. Installing the VTL console 143 6. Recovery following a system failure 147 Failback 147 Resuming backups following a failover/failback 157 7. Configuring email alerts 159 8. Updating VTL software 165 A.
Get client properties 175 Assign virtual device 175 Unassign virtual device 176 Create virtual device 177 Delete virtual device 177 Get supported virtual libraries 178 Get supported virtual drives 179 Create virtual tape library 179 Add virtual tape drive 181 Create standalone tape drive 182 Create virtual tape 183 Move virtual tape 184 Tape copy 186 Set tape duplication 186 Set tape properties 187 Automated tape caching 189 Set tape caching 189 Sync physical tapes 191 Mi
Get import/export job status 198 Resume import/export jobs 199 Delete import/export jobs 200 Suspend import/export jobs 200 Cancel import/export jobs 200 Replication Create a replica 201 Promote a replica 203 Remove replication 203 Suspend replication 204 Resume replication 205 Set replication properties 205 Get replication properties 206 Get replication status 207 Start replication 207 Stop replication 208 Physical devices 208 Inventory physical tape library 208 Get physic
Server throughput report 215 SCSI channel throughput report 216 Device throughput report 217 Physical resources configuration report 218 Disk usage report 218 Physical resources allocation report 219 Specific physical resource allocation report 219 Fibre Channel adapter configuration report 220 Replication status report 220 Virtual library information report 221 Virtual tape information report 222 Create job report 223 Event Log x 224 Get Event Log 224 Technical support 225 Ge
About this book This book introduces tape virtualization and guides you through the administration of Sun StorageTek Virtual Tape Library (VTL) solutions, including VTL Plus 2.0 and VTL Value systems. It starts with a high‐level explanation of VTL technology, common deployment architectures, and special features.
When the setup process branches, the task ends with conditional alternatives: Next task: ■ If the customer does not plan to run the management console from a host on the local area network (LAN), press Skip, and go to the next task. ■ Otherwise, carry out the procedure “Configuring the Ethernet LAN” on page 57. When you have finished a sequence of tasks, this is clearly noted: Stop here.
Understanding the conventions used in this book The table below illustrates the conventions that represent literal and variable values, commands, and property names in this book. Convention Meaning Examples AaBbCc123 Fixed‐width text is used for literal values, including names of commands, files, directories, literal computer inputs/outputs, and Uniform Resource Locators (URLs) Edit your.login file. Use ls -a to list files. % You have mail.
xiv VTL User Guide • May 2008 G • 96267
CHAPTER 1 Introduction: VTL appliances and enterprise data‐protection Sun StorageTek VirtualTape Library (VTL) technology makes the benefits of disk‐to‐ disk‐to‐tape architecture available to complex backup environments that cannot readily accommodate the disruptions and administrative burdens that often accompany major changes to information‐management environments and processes. VTL solutions make disk media available to applications that are configured to work with tape.
Features Features The Sun StorageTek VTL solution has the following features: ■ Emulation of most widely used tape libraries, drives, and media types, including the latest Sun StorageTek T10000‐series drives and media ■ Dynamic allocation of disk capacity VTL software can allocate disk space to virtual tapes in 5‐GB increments, up to the full, rated capacity of the emulated media. This minimizes wasted space, provides natural load balancing, and optimizes the performance of the disk array.
Features The Shred feature insures military standard, secure data destruction by overwriting virtual tape with random bit patterns. Data destruction jobs are queued so that the shred process does not have an excessive impact upon performance. ■ Data compression Sun VTL Plus 2.0 supports both software‐based and hardware‐based data compression. Both data‐compression technologies offer similar functionality. Both are based on the LZO algorithm.
Advantages of VTL tape virtualization Advantages of VTL tape virtualization Adding Sun StorageTek VirtualTape Library appliances to an existing tape‐based backup architecture can thus realize the following advantages: ■ “Shorter runtimes and reduced dependency on backup windows” on page 4 ■ “Shorter run times for non‐sequential backup jobs” on page 5 ■ “Improved reliability” on page 5 ■ “Better utilization of tape subsystems” on page 5 ■ “Larger, more flexible libraries” on page 6 ■ “Compatibili
Advantages of VTL tape virtualization Shorter run times for non‐sequential backup jobs Disk‐based VTL systems reduce run time when storage operations are poorly matched to the operational characteristics of tape backup systems. Properly configured, streaming tape backups achieve transfer rates that are as high as or higher than those attainable by disk technology. But many common jobs—such as incrementals and full backups of workstations—produce semi‐random I/O.
Advantages of VTL tape virtualization that produce intermittent or non‐sequential I/O, such as incrementals and backups of work stations, are copied to tape only after they have been backed up to disk and incorporated into large, sequential backup sets. This approach uses tape drives continuously, at close to their maximum throughput. The drives spend less time idle, since they mount and reposition less often. Fewer drives and tapes are needed for a given workload.
Advantages of VTL tape virtualization Operating systems and backup applications that currently interact with a physical library via ACSLS continue to use ACSLS when accessing VTL virtual libraries. ACSLS further hides the particulars of disk‐based tape virtualization behind a standard, well‐known interface. This ability to mask the library implementation from client applications and operating systems lets ACSLS make disk‐based tape‐virtualization available to platforms that could not otherwise support it.
Key VTL features and options Key VTL features and options ■ “NDMP migration” on page 8 ■ “VTL high‐availability option” on page 9 ■ “Automated Tape Caching” on page 12 ■ “Virtual tape replication” on page 12 ■ “VTL Secure Tape encryption option” on page 14. NDMP migration Backup applications that support Network Data Management Protocol (NDMP) 4.0 with Sun VTL virtual libraries can mount virtual tapes on a suitably configured VTL Plus 2.
Key VTL features and options controls NDMP agent software on the filer (D below). This agent software copies data from the filer over the SAN to virtual tape volumes (E) mounted by the backup media server (F), so no softwre has to be hosted on the VTL appliance. Data-mover software on NAS filer copies data over SAN to virtual tapes.
Key VTL features and options including the device in question, the failure is local to the primary, and the secondary initiates failover. If the secondary cannot access devices, the outage is global, and no failover occurs.
Key VTL features and options Storage path failover In a standard‐availability VTL system, there is one logical path from a VTL client to VTL storage, and every Fibre Channel port is either a target port for a VTL client or a storage‐facing initiator. But in a high‐availability system, there are two paths, a primary and a secondary or standby path, as shown below.
Key VTL features and options Automated Tape Caching The Automated Tape Caching option presents backup applications with virtual tape volumes that are physically implemented on disk, tape, or both. This keeps the implementation simple—the backup application manages only the virtual tape volumes and virtual libraries—while giving the backup administrator the ability to fine tune the physical implementation for best performance and reliability.
Key VTL features and options Auto Replication The Auto Replication option copies virtual tapes from a virtual library to another VTL server whenever a backup application or utility moves a virtual tape to an import/export slot. You enable Auto Replication at the library level when you create a virtual tape library (see “Setting up the Auto Replication option” on page 50). You can then selectively enable the feature on a tape‐by‐tape basis as tapes are created.
Key VTL features and options Remote Copy Remote Copy copies a single virtual tape to another server on demand. VTL Secure Tape encryption option The VTL Secure Tape option uses the Advanced Encryption Standard (AES) algorithm to protect physical media that might otherwise be vulnerable to theft or diversion during transit. VTL software encrypts data when it is exported to physical tape and decrypts it when it is reimported to virtual tape.
CHAPTER 2 Understanding VTL Zoning Zoning is the crucial first step when integrating a storage system, such as the VTL appliance, into a Fibre Channel storage area network (SAN). While specific zoning recommendations must vary from SAN environment to SAN environment, this chapter describes the basic requirements that all successful VTL deployments must address. ■ “Zoning for standard‐availability systems” on page 15 ■ “Zoning for high‐availability systems” on page 16.
Zoning for high‐availability systems Zoning a high‐availability system is slightly more complex than zoning a standard system, due to the need for redundant paths between initiators and targets. Once again, each SAN zone can have only one initiator and one target. But the total number of zones you need depends on whether the SAN is soft‐zoned (by World Wide Port Name) or hard‐zoned (by port number). See: ■ “WWPN zoning (soft zoning)” on page 16 ■ “Port zoning (hard zoning)” on page 17.
SAN Client Failed VTL server node I T I Active VTL server node A W n Zo * N2 WP eA Client B T T I WWPN6 WWPN4 Zone B Active VTL server node B Port zoning (hard zoning) A hard‐zoned SAN maps initiator to target using a physical port address. This port‐ to‐port zoning establishes a fixed, physical route through the SAN. So, since each SAN zone can contain only one initiator and one target, you must provide two zones for each initiating client.
During failover, the standby port becomes active by spoofing the WWPN of the failed port. The figure below represents a hard‐zoned SAN after VTL failover: SAN Client A port1 port2 T I I Active VTL server node A e on port3 * Z 2 PN W W port5 A T Client B T I port6 Zone B port4 Active VTL server node B A B C D E F ACSLS server G SAN clients include backup application hosts, such as Symantec NetBackup master servers, and ACSLS servers (if ACSLS is to control VTL virtual libraries).
CHAPTER 3 Using the VTL console The Virtual Tape Library console application is the graphical user interface that you use when administering and managing the VTL system. The console provides you with full control over virtual library operations, from creating libraries and tapes to managing disk storage and data migration from disk to physical tape. The VTL console software is installed on a management workstation that you provide and communicates with the appliance via your local area network (LAN).
Running the VTL console application Running the VTL console application ▼ Launching the VTL console 1. To launch the console on a Sun Solaris workstation, open a terminal window and enter the command shown below: % /usr/local/vtlconsole/vtlconsole & 2. On a Microsoft Windows system, press the Start bar to access the main menu system, and select All Programs > Sun Microsystems > VTL 5.0 > VTL Console. 3.
Populating the console 1. From the console main menu, select Tools (A below), then select Discover VTL Servers from the submenu (B). A B 2. When the Discover Virtual Tape Library Server dialog appears, enter the subnet filter (F below) and subnet mask (G) for the VTL appliance. Then press OK (H). C subnet_of_VTL_node D subnet_mask_of_VTL_node E After a short wait, the VTL console application discovers the appliance and adds it to the list on the left side of the graphical user interface (GUI).
Understanding the VTL console interface 3. When the VTL User Login dialog appears, enter the VTL Server host name or IP address (C above) and the User Name, and Password (D), and press OK (E). Stop here. ▼ Deleting a server node from the console tree 1. In the tree view of the VTL console, right‐click on the name of the server you wish to delete from the console view. 2. From the context menu, select Delete. 3. When the confirmation dialog appears, select Yes. Stop here.
Understanding the VTL console interface A D B C E F Once you have logged in to the server, clicking on the plus (+) symbol next to the icon expands the server branch of the interface, revealing the sub‐components of the VTL system: the Virtual Tape Library System, SAN Clients, Reports, and Physical Resources (C above). Clicking on the plus (+) symbol next to any icon expands the corresponding branch of the object tree, revealing the sub‐components and sub‐branches that lie beneath it.
Understanding the VTL console interface Virtual Tape Library System The Virtual Tape Library System branch of the object tree is the primary management tool for routine VTL operations. Right‐clicking on the subbranches of the Virtual Tape Library System gives you access to context sensitive menus that control most of the common VTL management operations. Virtual Tape Library System icons The following table explains the icons that represent virtual tape drives and virtual tapes in the console object tree.
Understanding the VTL console interface The Virtual Vault branch lists the virtual tapes that are currently being stored outside the virtual tape libraries, in barcode order. Virtual tapes in the vault can be replicated, exported to a physical tape, or moved to a virtual library or standalone drive. The number of tapes that can be stored in the vault is limited only by the available disk storage space.
Understanding the VTL console interface ■ virtual tape and library information ■ job status By right‐clicking on this branch, you can select and generate reports. Physical Resources The Physical Resources branch of the VTL object tree lists Fibre Channel HBAs and storage devices attached to the VTL server. Storage devices include the disk volumes that hold virtual tapes, physical tape libraries and physical tape drives.
CHAPTER 4 VTL operations This chapter covers routine configuration, administration, and management of server nodes, virtual tape libraries, drives, and tapes, including: ■ “Managing network connectivity” on page 27 ■ “Managing virtual libraries” on page 33 ■ “Managing tapes” on page 86 ■ “Managing tape caching” on page 120 ■ “Creating and viewing reports” on page 123 ■ “Encrypting and shredding data” on page 127 ■ “Working with the Event Log” on page 135 ■ “Managing VTL servers” on page 140
Managing network connectivity ▼ Configuring local area network connections 1. In the Network Configuration property sheet, enter the Domain name (A below). Check the Append suffix to DNS lookup check box (B) if the customer needs to append the domain name to the machine name during DNS lookup. A domain_name B nnn.nnn.nnn.1 C nnn . nnn . nnn . nnn NIC_name D E 2. Enter IP address information for the Domain Name Server (if used) in the DNS section (C above), using the Add and Edit buttons. 3.
Managing network connectivity 5. When the IP Address Configuration property sheet appears, click the Static radio button (F below). F NIC_name nnn.nnn.nnn.nnn G J H 6. Click the Edit button (G above), and enter the IP address that the customer provided. 7. Leave the MTU text field (H above) as set by the factory. 8. Press OK (J above). You return to the Network Configuration property sheet. 9. If Network Time Protocol (NTP) is in use, press Config NTP (K above).
Managing network connectivity Note the Enable SSH, Enable FTP, and Allow root to login in telnet session check boxes. While ssh is enabled by default, ftp and remote login by root are disabled for security reasons. Sun recommends that you leave these options set to the defaults. For secure remote access, use the vtladmin account with ssh or sftp. Then, if root privileges are required, use the su command after logging in. 10. When you return to the Network Configuration property sheet, click OK (N above).
Managing network connectivity 3. When prompted to restart the network and server, press Yes (C below). C 4. Log back in to the server to continue working. Stop here. ▼ Obtaining SAN interface configuration information You can obtain the configuration information for any of the Fibre Channel host bus adapters on the VTL server by examining the object in the VTL console. 1. In the tree‐view pane of the VTL console, select Physical Resources (A below) and Storage HBAs (B).
Managing network connectivity 2. Select the HBA that you wish to check (C above), and, in the pane at right, use the tabs to locate the required information (D). Stop here. ▼ Administering SAN client connections You can obtain the configuration information for any of a VTL server’s SAN clients by examining the object in the VTL console, as described below. To add a SAN client, see “Connecting virtual libraries with storage clients” on page 64. 1.
Managing virtual libraries 3. To see virtual device assignments, expand the client node (D below) and Fibre Channel protocol node (C) of the tree view. F D E 4. Right‐clicking on the client node (D above) or Fibre Channel protocol (C) node opens a menu of administrative actions (F). Using the context menu, you can Assign virtual devices to clients, Unassign virtual devices from clients, Delete the client or protocol, Detach devices, and view or refresh client properties. Stop here.
Managing virtual libraries Configuring physical libraries and devices VTL software supports either direct‐attached libraries or, optionally, shared libraries managed by ACSLS/Library Station software. ■ If you are using a direct‐attached library, see “Managing direct‐attached physical tape storage” on page 34. ■ If you are using a shared library, see “Managing ACSLS and Library Station tape pools” on page 38.
Managing virtual libraries 2. Otherwise, in the object tree of the VTL console, right‐click the Physical Resources node (A below), and select Prepare Devices from the context menu (B). A B 3. When the Select a Preparation Operation dialog appears, click the Prepare Device(s) radio button (C below). C D E 4. Select Reserved for Direct Device from the Device Category list control (D above), and press Next (E).
Managing virtual libraries 5. When the Select Physical Devices panel appears, use the check boxes and/or the selection buttons (F below) to select the libraries or devices that you want to assign to the VTL system. Press Next (G). If you are configuring an IBM iSeries/AS400 solution, assign IBM Magstar 3590E11, 3592, or Ultrium LTO1, LTO2, or LTO3 physical drives to the virtual tape library for use in import and export operations. A B 6. When the Prepare Device panel appears, press Finish.
Managing virtual libraries ▼ Assigning direct‐attached physical tape libraries/devices 1. In the object tree of the VTL console application, open the branch for the VTL server (A below). A B D C 2. Open the branch for the Virtual Tape Library System (B above). 3. Right‐click on the Physical Tape Libraries branch (C above), and select Assign from the context menu (D). 4.
Managing virtual libraries Managing ACSLS and Library Station tape pools When the VTL software’s ACSLS/Library Station option is enabled, Sun StorageTek ACSLS Manager™ or Library Station software manages the physical library and the tape volumes in the VTL system’s assigned tape pools. You merely need to update the VTL console view whenever tapes are added or removed from the pool. Proceed as follows.
Managing virtual libraries Configuring and provisioning virtual libraries This section describes the procedures for creating and maintaining virtual libraries, with their virtual drives and media.
Managing virtual libraries both the needed long‐term storage capacity and the fastest possible transfer to tape media. Compression hardware cannot further compress data that has been compressed by software, so the end‐to‐end backup process is significantly slower.
Managing virtual libraries ▼ Creating virtual tape libraries 1. When the Create Virtual Library Wizard appears, select the type of library that you want to emulate (A below), enter a Virtual Library Name (B) or use the default, and press Next (C). Select a unique, informative virtual library name. A name that indicates the backup application media server and the function or usage of the library (such as NDMP data migration) is one useful possibility.
Managing virtual libraries If you plan to attach a physical tape library to the VTL appliance for tape import or export, emulate the physical library so that virtual tapes will be compatible with their physical counterparts. Select an informative virtual drive‐name prefix that shows the relationships between virtual libraries and drives. Using the virtual library name plus the make and model of the emulated drive is one possibility. 3.
Managing virtual libraries 6. If you do not intend to implement autoarchiving or replication, press Next (L below) to skip over the Auto Archive/Replication dialog. L The Auto Archive option writes data to physical tape whenever a backup application or utility moves a virtual tape from a virtual library to an import/export slot.
Managing virtual libraries 7. Indicate if you want to use tape duplication. Tape duplication allows you to make up to five duplicate copies of a physical tape whenever virtual tape data is exported to physical tape. You must have at least two identical physical libraries (same model, same number of drives, same tapes with the same barcodes). When data is exported, separate export jobs will be created for each physical library and each job will have a unique job ID.
Managing virtual libraries Next task: ■ ■ ■ ■ If you are going to configure tape caching on this virtual library, go to “Configuring Automated Tape Caching” on page 45. If you are going to use the automatic archiving features, go to “Setting up the Auto Archive feature” on page 49. If you are going to use the automatic replication feature, go to “Setting up the Auto Replication option” on page 50 Otherwise, go to “Generating the virtual library” on page 51.
Managing virtual libraries ▼ Creating simple schedule‐driven migration policies When the Please select migration trigger(s) dialog appears, proceed as follows. 1. Click the Time Based radio button (A below). 2. To migrate data every day, click the Daily Migration Schedule radio button (B below). Using the controls provided (C), enter the time when migration should begin. 3.
Managing virtual libraries 2. To migrate data when ALL of of the conditions specified are satisfied, click the And radio button (B below). A C B D E F G H J 3. To migrate data when ONE OR MORE of the conditions specified is satisfied, click the the Or radio button (C above). 4. To trigger migration based on the age of the data, check the Age Based check box, and use the spinner control to select the desired number of days (D above). 5.
Managing virtual libraries ▼ Creating a reclamation policy The reclamation policy determines when expired virtual volumes are released. Proceed as follows. 1. When the Please select a reclamation trigger dialog appears, click the radio button that corresponds to the desired triggering condition (A below). A B C D E 2. If you choose to specify a Retention Period, use the spinner control (B above) to specify the number of Day(s). 3. Then press Next (C above).
Managing virtual libraries ▼ Setting up the Auto Archive feature 1. When the Auto Archive/Replication dialog appears, check the Auto Archive/Replication check box (A below). A B C D E F 2. Specify Auto Archive by clicking the Auto Archive radio button (B above). 3. Select the desired archiving behavior by clicking either the Move radio button (and setting the grace period using the spinner and list controls provided) or the Copy radio button (C above).
Managing virtual libraries ▼ Setting up the Auto Replication option 1. When the Auto Archive/Replication dialog appears, check the Auto Archive/Replication check box (A below). A B C D E F G 2. Click the Auto Replication radio button (B above). 3. To copy virtual media to the target library while leaving the source virtual media in the source library, click the Copy radio button (C above). 4.
Managing virtual libraries ▼ Generating the virtual library Using this procedure, you define the remaining characteristics of your virtual library and media. You supply a barcode range, slot count, and import/export slot count for the library and define the capacity of the media. Setting the barcode range defines the set of barcodes that the virtual library will support. Each batch of cartridges that you subsequently create must be a subset of the range you define now—you cannot change it later.
Managing virtual libraries 3. Using the spinner control provided, adjust the Number of Slots to 4096, the maximum supported by major backup application software for a single virtual library (C above). In most cases, set the slot number to the maximum value. Once a library is defined, you cannot change the number of slots that it contains, so it makes sense to set this number as high as possible.
Managing virtual libraries 6. When the Enter virtual tape properties dialog appears, check the Tape Capacity On Demand check box (E below). Sun recommends capacity on demand for most users. E F G 7. If you are not using tape caching, use the Maximum Capacity spinner control (F above) to set the maximum size of your virtual tapes to 50‐60 GB or to the average size of your backup jobs (whichever is larger).
Managing virtual libraries 10. Press Next (E above). 11. When the confirmation screen appears, press Finish (F below). F 12. When the Batch Creation Status panel appears, press OK (G below). G Next task: If you decided to create tapes, go to “Creating virtual tapes” on page 56. ▼ Enabling Auto Replication on an existing library 1. In the object tree of the VTL console, expand the node for the VTL server. 2. Under the VTL server, expand the Virtual Tape Library System and Virtual Tape Libraries nodes.
Managing virtual libraries 3. Under the Virtual Tape Libraries node, right‐click on the virtual tape library that you want to enable, and select Properties. 4. When the Change Virtual Library Properties property sheet appears, check the Auto Archive/Replication check box (A below), and click the Auto Replication radio button (B). A B C D E 5.
Managing virtual libraries Creating virtual tapes Follow the procedures outlined below: ■ “Enabling the advanced tape creation method” on page 56 ■ “Setting replication parameters for virtual tape volumes” on page 61 ■ “Launching the virtual tape batch creation process” on page 64. ▼ Enabling the advanced tape creation method 1. If you have not already done so, from the console main menu, select Tools (A below), then select Console Options (B) from the submenu. 2.
Managing virtual libraries tries to calculate this value for you, it does so using the currently allocated size of the virtual tapes. If you are using the capacity on demand feature of the Sun VTL, the currently allocated size is the increment size (typically 5 GB), not the full capacity of the emulated media (for example, 40 GB for Sun StorageTek 9840C cartridges).
Managing virtual libraries ■ Otherwise, the wizard skips directly to the Specify Batch Mode Information dialog. So go to “Allocating disk space to virtual tapes” on page 60. ▼ Setting Auto Archive parameters for virtual tape volumes If the new virtual tapes will reside in a library that has the Auto Archive option enabled, proceed as follows. 1. In the Select a Physical Tape Library dialog, check the Create virtual tape(s) to match physical tape(s) ... check box (A below). Press Next (B). A nnn.nnn.
Managing virtual libraries 2. In the Select Physical Tapes dialog , select physical tapes using the check boxes (C below) and/or button controls provided (D ). Then press Next (E). C D E Next task: “Allocating disk space to virtual tapes” on page 60.
Managing virtual libraries ▼ Allocating disk space to virtual tapes 1. When the Specify Batch Mode Information panel appears, enter a descriptive prefix for the virtual tape labels (A below). Choose a meaning name prefix that shows the relationships between virtual tape volumes and virtual libraries. virtualLibraryName_VTV A 2. If you only plan to create one virtual library for your VTL system, you can use all of the available disk capacity for tapes.
Managing virtual libraries 3. Otherwise, if you plan to create additional libraries later, divide the Maximum (B above) between the libraries, and enter the number allocated to this library as the Number of Virtual Tapes (C). The new value has to be less than the Maximum, so that capacity is reserved for creating tapes for the additional libraries. 4. Check the Use Default ID for Starting Number check box (D above). Press Next (E). 5.
Managing virtual libraries 1. When the Select Target Server for Auto-Replication Option dialog appears, check the Automatically replicate the virtual tape(s) to the selected target server check box (A below). A C B D 2. Select the remote server from the list (B above), or press Add to add a server to the list (C). Press Next (D). 3. When the Target Server Information panel appears, press Next (E below).
Managing virtual libraries 4. When the Specify Replication Timeout and Retry Policy property sheet appears, configure timeout and retry intervals using the spinner controls provided (F below). Then press Next (G). F G 5. When the Specify the Options for Data Transmission property sheet appears, check the Compress Data (H below) check box to enable compression. Compression software can be valuable when transmitting replica data over slow links. However, assess requirements carefully.
Managing virtual libraries 7. Press Next (K above). Next task: “Launching the virtual tape batch creation process” on page 64. ▼ Launching the virtual tape batch creation process 1. When the Create Virtual Tapes summary screen appears, press Finish (A below). B A 2. When the batch job finishes and the Virtual Tape Batch Creation Status panel appears, press OK (B above). Note that tape creation can take some time, so the status panel will not appear immediately. Stop here.
Managing virtual libraries ■ “Adding Fibre Channel SAN clients” on page 66 ■ “Assigning virtual libraries to storage clients” on page 69. ▼ Starting the Add Client Wizard 1. In the tree menu of the VTL console, select the VTL server branch. 2. Right‐click the SAN Clients branch (A below). 3. Select Add from the context menu (B below). A B Next task: “Adding Fibre Channel SAN clients” on page 66.
Managing virtual libraries ▼ Adding Fibre Channel SAN clients 1. When the Enter the Generic Client Name dialog appears, enter the client name in the text field provided (A below). Press Next (B). The client is typically an ACSLS server or a backup application host, such as a Symantec NetBackup master server. A B 2. When the Select Client Protocols dialog appears, check the Fibre Channel check box (C below), and press Next (D).
Managing virtual libraries 3. When the Set Client Fibre Channel Properties property sheet appears, select the World Wide Port Name (WWPN) of the initiator by checking the corresponding check box (E below), or press the Add button (F), enter a new Initiator WWPN, and press OK (G). Then press Next (H). G E F H 4. When the Fibre Channel Option panel appears, check the check boxes for any optional support that the client requires (J below). Then press Next (K).
Managing virtual libraries 5. When the Add the Generic Client summary screen appears, press Finish (L below) to add the client. client_name WWPN L Next task: “Starting the Assign a Virtual Tape Library Wizard” on page 68. ▼ Starting the Assign a Virtual Tape Library Wizard VTL storage clients are the backup application hosts that manage your backup jobs. To assign libraries to clients, proceed as follows. 1.
Managing virtual libraries ▼ Assigning virtual libraries to storage clients 1. When the Assign a Virtual Tape Library Wizard appears, check the Assign the tape library and all drives... check box (A below), select a client (B), and press Next (C). As a general rule, assign one library per client. virtual_library_name A client_x B client_y client_z C 2.
Managing virtual libraries 3. When the Assign a Fibre Channel Client to the Virtual Tape Library confirmation screen appears, press Finish (F). virtual_library_name client_name F 4. Log in to each VTL client (each backup server), and scan for new Fibre Channel devices. Stop here.
Managing virtual libraries 3. Perform a configuration reboot: [ACSLS_server]root:# ./reboot -- -r Next task: “Creating ACSLS host driver instances for virtual libraries” on page 71. ▼ Creating ACSLS host driver instances for virtual libraries Once you have discovered the newly attached VTL virtual libraries, proceed as follows. 1. Log in to the ACSLS server as root. 2.
Managing virtual libraries 5. Edit the file /usr/kernel/drv/mchanger.conf, adding an entry for each virtual library that the oeprating system discovered. Each library entry includes a driver name (mchanger), a parent driver (fp, the Solaris Fibre Channel port driver), a driver class (scsi), a logical unit number (lun), and a World Wide Name for the remote Fibre Channel port (fc-port-wwn): [ACSLS_server]root:# vi /usr/kernel/drv/mchanger.
Managing virtual libraries 10. When prompted, confirm your entries by entering y (yes). The script builds the driver instances for the specified libraries: Is this correct? (y or n): y Building an mchanger instance for each library... Successfully built the following... /dev/mchanger0: STK L700 678-cells 10-drives /dev/mchanger1: STK L700 678-cells 10-drives /dev/mchanger2: STK L700 678-cells 10-drives 11. Load the driver: [ACSLS_server]root:# ./add_drv mchanger 12.
Managing virtual libraries 2.
Managing virtual libraries 4. Wait for 60 seconds (one minute), then start the ACSLS command preocessor, cmd_proc: $ cmd_proc (c) Copyright (2004) Storage Technology Corporation All Rights Reserved This material is confidential and proprietary to StorageTek and may be licensed only under a valid StorageTek licence. Do not copy or distribute unless authorized in writing by StorageTek.
Managing virtual libraries ■ “Manually saving the VTL configuration” on page 76 ■ “Automatically backing up the VTL configuration” on page 76. ▼ Manually saving the VTL configuration 1. In the object tree of the VTL console, highlight the VTL server node (A below). B A D C E 2. From the VTL main menu, select Tools (B above). 3. From the submenu, select Save Configuration (C above). 4. When the Save dialog appears, supply a filename (D above), and press Save (E). Stop here.
Managing virtual libraries 1. In the object tree of the VTL console, right‐click on the the VTL server branch (A below). A B 2. From the context menu, select Properties (B above).
Managing virtual libraries 3. Select the Auto Save Config tab (C below). C D E F G H J K 4. Check Enable Auto Save Configuration File check box (D above). 5. In the field provided, enter the Ftp Server Name for the machine that will host the backup configuration files (E above). The target server must have FTP server installed and enabled. 6. Enter the relative path to the Target Directory in the field provided (F above). The specified path should be relative to the root directory of the ftp server.
Managing virtual libraries Stop here. Recovering the server configuration If the VTL server configuration is lost or corrupt, you can recover it from a backup file using the procedure below. Caution – This is a disaster recovery procedure only. Never execute it during day‐ to‐day operation of the server. Restoring a configuration overwrites existing virtual device and client configurations and does not restore VTL partition information. ▼ Restoring the configuration 1.
Managing virtual libraries Mirroring supplies an additional layer of protection. Mirrored databases maintain two separate, synchronized copies of the metadata, either of which can provide access to virtual tape data on its own. ▼ Mirroring the VTL database 1. In the object tree of the VTL console, expand the branch for the VTL server (A below). 2. Expand the Virtual Tape Library System branch (B below). 3. Right‐click on the Database object (C below). A B E D C 4.
Managing virtual libraries 5. When the Select a Creation Method dialog appears, select Express (F below), and press Next (G). F G The Express method takes advantage of the intelligence built in to the RAID subsystem to make best use of disk resources.
Managing virtual libraries 6. When the confirmation dialog appears, confirm that all information is correct, and then click Finish to create the mirrors. The VTL software creates and synchronizes the mirror database. When the process completes, the value of the Mirror Synchronization Status field of the database property sheet becomes Synchronized (H below). H Stop here. ▼ Removing a mirror configuration 1. Right‐click on the database. 2.
Managing virtual libraries ▼ Managing administrators Only the root user can add or delete a VTL administrator or change an administrator’s password. 1. In the object tree of the VTL console, right click on the server name (A below), and select Administrators from the context menu (B). A B vtl C There are two types of administrators: ■ VTL Administrators are authorized for full VTL console access. ■ VTL Read-Only Users are only permitted to view information in the Console.
Managing virtual libraries ▼ Changing administrator passwords 1. Right‐click on the VTL server node name (A below), and select Change Password from the context menu (B). A B 2. When the dialog appears, enter the password that you need to change in the Old Password text box (C below). C D E 3. Enter the changed password in the New Password and Confirm Password text boxes (D above). 4. Press OK (E). Stop here.
Managing virtual libraries VTL supports two types of compression: ■ Hardware compression ‐ uses a Hifn Express DR1000 (1 GB/sec compression) or DR600 (600 MB/sec) compression card. A license keycode is required for hardware compression. ■ Software compression ‐ uses an LZO algorithm that runs on the VTL server. In order to use compression, you must also enable tape drive compression in your backup application.
Managing tapes UNIX — On backup servers that run Solaris or other UNIX operating systems, specify a compressed tape device file such as /dev/rmt/0cbn to enable compression or /dev/rmt/0ubn to disable compression. Windows — On Windows servers select the option in your backup software to enable or disable hardware tape drive compression. If global VTL compression is disabled, it is possible to enable individual drive compression, but it will have no effect.
Managing tapes ■ “Setting up replication for individual tapes” on page 92 ■ “Manually synchronizing replicas (manual replication)” on page 98 ■ “Stopping a replication that is already under way” on page 99 ■ “Manually synchronizing replicas (manual replication)” on page 98 ■ “Checking replication status from the target VTL server” on page 101 ■ “Checking replication status with a report” on page 101 ■ “Changing replication properties” on page 102 ■ “Deleting a replication configuration” on p
Managing tapes 6. When the Select Virtual Tapes to enable Replication... panel appears, use the check boxes (D below) and/or selection buttons to select tapes (E). Press Next (F). D E F 7. When the Specify the Target server Type panel appears, click the radio button for a Remote or Local Server (G below). Then press Next (H).
Managing tapes 8. When the Select Target Server panel appears, use the list (J below) to select or server or press Add (K) to add one to the list. Press Next (L). J H K 9. If you chose the Remote Server option above, in Step 7, edit the IP address of the remote VTL server in the space provided (M below), if necessary, then press Next (N).
Managing tapes 10. If you chose the Local Server option above, in Step 7, press Next (O below). O 11. When the Select the Replication Policy ... panel appears, use the check boxes, list boxes, and spinner controls provided to define the policy you want to apply (P below). Press Next (R).
Managing tapes 12. When the Select the Replication Timeout and Retry Policy panel appears, use the spinner controls provided to define the policy you want to apply (S below). Press Next (T). S T 13. When the Specify the Options for Data Transmission panel appears, use the check boxes provided to select the options you want to use (U below). Press Next (V). Remember that compression and encryption are CPU‐intensive software processes that reduce system throughput. Use them judiciously, when necessary.
Managing tapes 14. When the confirmation panel appears, press Finish (W below). W Stop here. ▼ Setting up replication for individual tapes 1. In the object tree of the VTL console, expand the VTL server node, the Virtual Tape Library System node, and the Virtual Tape Libraries node.
Managing tapes 2. Then open the node for the library that holds the tape you want to replicate (A below), and open the Tapes node (B). A B C D E 3. Right‐click on the virtual tape for which you want to enable replication (C above). 4. From the context menus, select Replication (D above), then select Add (E). 5. When the Specify the Target server Type panel appears, click the radio button for a Remote or Local Server (F below). Then press Next (G).
Managing tapes 6. When the Select Target Server panel appears, use the list (H below) to select or server or press Add (J) to add one to the list. Press Next (K). J H K 7. If you chose the Remote Server option above, in Step 7, edit the IP address of the remote VTL server in the space provided (L below), if necessary, then press Next (M).
Managing tapes 8. If you chose the Local Server option above, in Step 7, press Next (N below). N 9. When the Select the Replication Policy ... panel appears, use the check boxes, list boxes, and spinner controls provided to define the policy you want to apply (N below). Press Next (P).
Managing tapes 10. When the Select the Replication Timeout and Retry Policy panel appears, use the spinner controls provided to define the policy you want to apply (Q below). Press Next (R). Q R 11. When the Specify the Options for Data Transmission panel appears, use the check boxes provided to select the options you want to use (S below). Press Next (T). S T Remember that compression and encryption are CPU‐intensive software processes that reduce system throughput.
Managing tapes 12. When the Select a Creation Method panel appears, click the Express radio button (U below), and press Next (V). U V The Sun StorageTek VTL appliance includes an integrated RAID device, so there is no advantage to manually selecting target volumes using the Custom method. The Custom method may also result in load balancing problems and significantly greater management overhead. 13.
Managing tapes 14. When the confirmation panel appears, press Finish (Y below). Y Note – Once you create your replication configuration, you should not change the hostname of the source (primary) server. If you do, you will need to recreate your replication configuration. Stop here. ▼ Manually synchronizing replicas (manual replication) You can synchronize replicas manually, when necessary. To do so, proceed as follows. 1.
Managing tapes ▼ Suspending and resuming replication You can manually suspend forthcoming replications that would otherwise be launched automatically from your replication policies (currently active replications are unaffected). To do so, proceed as follows. 1. Right‐click on the primary virtual tape, and select Replication and Suspend from the context menus. 2.
Managing tapes ▼ Checking replication status from the primary VTL server 1. In the object tree of the VTL console, drill down to the Tapes node, and select the primary virtual tape (A below). B A C 2. In the properties sheet at the right, select the Replication tab (B above). 3. Scan down the sheet until you see the Replication Status row (C above). Stop here.
Managing tapes ▼ Checking replication status from the target VTL server 1. In the object tree of the VTL console, drill down to the Replica Resources node (A below). C D A B 2. Select the replica resource corresponding to the primary virtual tape (B above)) 3. In the properties sheet at the right, select the General tab (C above). 4. Scan down the sheet until you see the Replication Status row (D above). Stop here. ▼ Checking replication status with a report 1.
Managing tapes ■ all tapes on a group of servers Reports can be filtered to exclude all but current replication configurations, all but deleted or prompted configurations, or any desired combination. 2. Examine the report for the status (A below) of the job or jobs you are interested in. A Stop here.
Managing tapes ▼ Deleting a replication configuration 1. Right‐click on the primary virtual tape, and select Replication from the context menu. 2. Select Remove from the following context menu. This allows you to remove the replication configuration on the primary and either delete or promote the replica resource on the target server at the same time. Stop here.
Managing tapes 3. From the context menus, select Replication (B below), Promote (C). A B C 4. When the confirmation panel appears, press OK (D below). D 5. Rescan devices from the SAN client or restart the client so that it can see the promoted virtual tape. Stop here. Copying tapes You can copy the contents of a single tape to a remote server, on demand, using the VTL Remote Copy feature. The Remote Copy feature replicates full tapes.
Managing tapes You can only copy tapes with barcodes that are not found on the remote server. If a copy exists and you wish to proceed, you must first delete the existing remote copy copy. You cannot copy a tape that is configured to take advantage of the Replication, Auto Replication, or Auto Archive features. To copy tapes to a remote server, proceed as follows. ▼ Copying a tape to a remote server 1. In the object tree of the VTL console, expand the VTL server node. 2.
Managing tapes 5. When the Select the Target Server panel appears, use the list to select the server where you want to copy the tape (E below) or press Add (F) to add a server to the list. Then press Next (G). F E G 6. When the Enter Replication Parameters panel appears, edit the IP address if necessary (H below), then press Next (J). nnn.nnn.nnn.
Managing tapes 7. When the Specify a Location panel appears, select a location on the remote server (K below), and press Next (L). K L 8. When the confirmation panel appears, press Finish (M below). M Stop here. Moving tapes between virtual and physical libraries VTL software can import a physical tape as a virtual tape or export virtual tape to physical tape, using an attached physical tape library or tape drive.
Managing tapes ■ copy a physical tape to a virtual tape that emulates the same type of media ■ directly access a physical tape without copying the entire tape ■ recycle a physical tape after importing its contents to virtual media ■ move data from a virtual tape to a physical tape of the same media type VTL import/export capabilities are particularly useful when you are not using the Automated Tape Caching feature and want to move tapes from a virtual library to physical media for long term storage
Managing tapes ▼ Importing a physical tape into a virtual library 1. In the object tree of the VTL console, right‐click the node for the physical tape library or drive that holds the tape you wish to import (A below). Select Import Tape from the context men (B). A B 2. When the Select virtual library ... panel appears, use the list to select a virtual library that holds volumes of the same capacity as the volume you want to import (C below). Press Next (D). C D VTL exports tapes to like media only.
Managing tapes 3. When the Select the import mode ... panel appears, click the radio button that corresponds to the behavior you want (E below). E F G 4. If the tape is encrypted and you wish to decrypt it, check the Decrypt data ... check box (F above), and enter the correct key. If the data was not previously encrypted, imported data is unusable. If you supply an incorrect key or if you enter an invalid password when challenged, the imported data is not decrypted. 5. Press Next (G above).
Managing tapes 6. When the Select the physical tape to import ... panel appears, use the check boxes and/or selection buttons provided to select the tape(s) that you want to import (H below). Then press Next (J). H J You can select a tape based on its barcode or slot location. You can then use the same barcode for the virtual tape or you can enter a new barcode. You can also select a slot for the virtual tape. 7.
Managing tapes 8. When the Select Physical Devices panel appears, use the check boxes and/or selection buttons provided to select the LUNs that you wish to use (M below). Press Next (N). M N 9. When the Specify Batch Mode Information panel appears, enter a Virtual Tape Name Prefix that matches the convention used in the rest of the virtual library (P below).
Managing tapes 10. Set the Virtual Tape Size to the full size of the emulated media (Q below), and Tab to another field to recalculate the Maximum number of tapes possible with the available storage (S). Make sure that the Number of Virtual Tapes that you will create in order to import your specified number of physical tapes (R) does not exceed the recalculated Maximum (S). Q R S 11.
Managing tapes 12. Otherwise, reset the Virtual Tape Size to the default value for using capacity on demand with this type of media (T below). Check the Use default ID for Starting Number check box (U), and press Next (V). T U V 13. Verify the information, and press Finish (W below) to import the tape. W Next task: If you are working in an IBM iSeries/AS400 environment, go to “Importing cartridges in an IBM iSeries environment” on page 115. Otherwise, stop here.
Managing tapes ▼ Importing cartridges in an IBM iSeries environment 1. If you have not already done so, import tapes into the virtual library using the VTL console, as described in “Importing a physical tape into a virtual library” on page 109. 2. At the AS/400, re‐inventory the tape library. In the option field next to the tape library, enter 9 (INVENTORY). 3.
Managing tapes 2. When the Move Tape to Virtual Vault dialog appears, select the tape(s) that you want to move using the check boxes and/or selection buttons provided (C below). Press OK (D). C D 3. Now, in the object tree of the VTL console, open the Virtual Vault node, and right‐click the virtual tape that you want to export (E below).
Managing tapes 4. When the Select a physical library or drive panel appears, use the list to select the library or device to which you want to export virtual tape (G below). Press Next (H). G H 5. Select how you want the data exported. ■ Move Mode ‐ Copies the contents of the virtual tape to its physical counterpart and then removes the virtual tape from the system. Specify a grace period if you want to keep the virtual tape for a time before deleting it.
Managing tapes 6. Select or clear the Eject physical tapes to I/E slots after export check box. 7. Select Encrypt data when exporting to physical tape with the selected key if you want to encrypt the data on the tape. You can select this option only if at least one key has been created. If you select this option, you must select the key to use. All the data on the tape will be indecipherable until is imported back to a virtual tape library and decrypted using the same key.
Managing tapes 15. Press Next (S below). N Q R P S 16. When the Verify and Export ... panel appears, press Finish (T below). T Stop here. ▼ Exporting cartridges to the virtual vault in an IBM iSeries environment 1. Export a cartridge by entering the following at the command line: RMVTAPCTG DEV(library_device_name ) CTG(cartridge_identifier) 2. If desired, use the VTL console to verify that the cartridges have been removed from the virtual library and placed in the virtual vault. Stop here.
Managing tape caching Managing tape caching In most circumstances, the Automated Tape Caching feature maintains tape caches and linkages automatically, provided that policies are suitably defined. However, when necessary, you can manage caching manually.
Managing tape caching 1. In the object tree of the VTL console, right‐click on the direct link tape that you wish to recache. 2. Select Renew Cache from the context menu. Stop here. ▼ Disabling a policy To disable a tape caching policy: 1. In the object tree of the VTL console, right‐click on a virtual tape library, and select Automated Tape Caching from the context menu. 2. Clear the Enable Tape Caching Policy check box.
Managing tape caching 3. When the Sync Library dialog appears, check the checkbox that corresponds to the physical tape that needs to be relinked (A below) or use the Select-All button. A B 4. Press Next (B above). 5. When the select the mode panel appears, click the Create Direct Link radio button (C below).
Creating and viewing reports 6. If the data was encrypted before being migrated, check the Use encryption/decryption on tape(s) check box, and supply the select the appropriate key using the list control provided (D above). 7. Press Next (E above), then Finish. Stop here. Creating and viewing reports You can work with reports using the VTL console. See: ■ “Creating a report” on page 123 ■ “Viewing a report” on page 126 ■ “Exporting data from a report” on page 127. ▼ Creating a report 1.
Creating and viewing reports 2. When the Select a Report Type dialog appears, select a type from the list (C below). Press Next (D). C D 3. When the Select Report Options panel appears, select the desired report properties using the controls provided (E and F below). Press Next (G). E F G Note that different report types offer different options.
Creating and viewing reports 4. When the Enter the Report Name dialog appears, for the report, enter the name in the field provided (H below), and press Next (J). H J 5. When the Create the Report panel appears, press Finish (K below). K Stop here.
Creating and viewing reports ▼ Viewing a report 1. In the object tree of the VTL console, expand the Reports node (A below) to view the list of current reports. C A B 2. Select the current report that you wish to view (B above). The desired report appears in the right‐hand pane of the console (C above). Stop here.
Encrypting and shredding data ▼ Exporting data from a report 1. In the object tree of the VTL console, expand the Reports node and right‐click the name of the report that you want to export (A below). You can export server and device throughput and usage report data to comma‐or tab‐delimited text files. B D C A 2. In the context menu., select Export (B above). 3. When the Save dialog appears, use the Files of type list control to select the desired format (C above), and press Save (D). Stop here.
Encrypting and shredding data Each key consists of a secret phrase. For additional security, each key is password‐ protected. You must provide this password in order to change the key name, password, or password hint, or to delete or export the key. You can apply a single key to all virtual tapes when you export them to physical tape, or you can create a unique key for each one.
Encrypting and shredding data 5. In the New Password and Confirm Password text boxes (C below), type a password for accessing the key (10–16 characters). You will need to provide this password when changing the key name, password, or password hint and when deleting or exporting 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. 6.
Encrypting and shredding data If you rename a key, you can still use that key to decrypt data that was encrypted using the old key name. For example, if you encrypt data using Key1, and you change its name to Key2, you can decrypt the data using Key2, since the secret phrase is the same. To change a key name or password: 1. In the navigation tree, right‐click the server name, and click Key Management. 2. From the Key Name list, click the key you want to change. 3. Click Edit. 4.
Encrypting and shredding data ▼ Exporting a key When you export a key, you create a separate file called a key package that contains one or more keys. You can then send this file to another site that uses VTL, and administrators at that site can import the key package and use the associated keys to encrypt or decrypt data. Creating a key package also provides you with a backup set of keys.
Encrypting and shredding data 6. Select Prompt for new password for all keys in package if you want to create a new password for the key package. If you select this option, you will be prompted to provide the new password when you click OK on the Export Keys dialog box. You will subsequently be prompted for this password when you try to import a key from this package. In addition, all keys imported from this package will use this new password rather than the password originally associated with each key.
Encrypting and shredding data the key package. If you provide an incorrect password, you will still be able to import the keys in the package, but you will not be able to use them to decrypt any data that was previously encrypted using those keys. 6. From the Select Keys to Import list, select the keys that you want to import. You can select only those keys that have a green dot and the phrase Ready for Import in the Status column.
Encrypting and shredding data 1. Move the tape(s) you want to shred to the virtual vault. In the object tree of the VTL console, start by right‐clicking on a tape that you want to shred (A below), and select Move to Vault (B) from the context menu. A C B D E 2. When the Move tape to Virtual Vault dialog appears, use the check boxes (C above) and selection buttons (D) to select the tapes you want to shred. Press OK (E). 3. Select the tape(s) you want to shred.
Working with the Event Log 4. Right‐click on one of the tapes that you want to shred (G above), and select Tape Shredding (H) and Shred Tape (J) from the context menus. K L M 5. When the Shred Virtual Tape Resource dialog appears, check the Delete After Shredding check box (K above) if you wish to delete the tape after shredding. 6. In the space provided, type YES (L above) to confirm the shredding operation, and press OK (M). You can view the status by highlighting the virtual tape in the vault.
Working with the Event Log The columns displayed are: Type I: This is an informational message. No action is required. W: This is a warning message that states that something occurred that may require maintenance or corrective action. However, the VTL system is still operational. E: This is an error that indicates a failure has occurred such that a device is not available, an operation has failed, or a licensing violation. Corrective action should be taken to resolve the cause of the error.
Working with the Event Log ▼ Quickly printing an event log 1. From the VTL console main menu, select File. 2. From the submenu, select Print. Stop here. ▼ Filtering, exporting, purging, and printing an event log 1. With the Event Log tab (A below) of the server open, right‐click on the server icon in object tree of the VTL console (B). A B C D 2. From the context menu, select Event Log (C above).
Working with the Event Log 3. From the submenu, select the operation that you wish to perform (D above). If you wish to search or filter the log, the Event Log Options dialog (E below) lets you set up and apply your criteria. E Stop here. Using the Attention Required tab When events that may require user intervention occur, the VTL console flags the server icon with an exclamation point (!) and displays notifications in the Attention Required tab of the server properties sheet.
Working with the Event Log ▼ Accessing the Attention Required tab 1. In the VTL object tree, locate the flagged server (A below). B A C D E 2. In the right‐hand pane, select the Attention Required tab of the server property sheet (B above). Stop here. ▼ Clearing issues from the Attention Required list 1. If you want to clear an entire class of events from the list, check the check box for the event type (C above). 2.
Managing VTL servers Managing VTL servers The VTL console lets you manage the server node by: ■ “Setting server properties” on page 140 ■ “Configuring SNMP traps” on page 140. ▼ Setting server properties 1. Right‐click on the server and select Properties. 2. On the Activity Database Maintenance tab, indicate how often the VTL activity data should be purged.
Managing VTL servers 2. Select the SNMP Maintenance tab. 3. Indicate the information that should be included in traps sent to your SNMP manager. SysLocation ‐ Enter the location that should be included in traps. SysContact ‐ Enter any contact information that should be included in traps. This could be a name or an email address. 4. Specify the type of message that should be sent. Five levels of messages are available: ■ ■ ■ ■ ■ None: no messages will be sent.
Managing VTL servers 142 VTL User Guide • May 2008 G • 96267
CHAPTER 5 Installing the VTL console The Virtual Tape Library console application can be installed on a full range of operating platforms. In most cases, a Sun service representative installs the console on one customer‐provided server as part of the initial deployment. Customers can install as many additional instances as required on other machines. Note, however, that no more than two (2) instances of the console can access the same VTL server at the same time.
3. If you are installing the console software on an x86 platform, enter the following command, and respond to the on‐screen prompts: % pkgadd -d vtlconsole-n.nn-n.nnn.i386.pkg 4. If you are installing the console software on a SPARC platform, enter the following command, and respond to the on‐screen prompts: % pkgadd -d vtlconsole-n.nn-n.nnn.sparc.pkg 5. To launch the console, enter the following command: % /usr/local/vtlconsole/vtlconsole & Stop here.
2. Using Secure File Transfer Protocol (sftp), log on to the VTL server, change to the usr/vtl/packages/build/Windows/ directory, and download all listed installation files to a temporary directory on the client: % sftp vtladmin@appliance_IP-address sftp> cd /software/Windows/ sftp> ls data1.cab ikernel.ex_ layout.bin data1.hdr ISInstall.exe setup.bmp data2.cab ISInstall.ini Setup.exe sftp> get *.* Setup.ini setup.
146 VTL User Guide • May 2008 G • 96267
CHAPTER 6 Recovery following a system failure To recover a VTL high‐availability system following a failure on one node, carry out the following tasks: ■ “Failback” on page 147 ■ “Resuming backups following a failover/failback” on page 157. Failback For best results, run failback as a manual process, using the procedure outlined below. ▼ Initiating failback For the purposes of this description, the current, active node is VTLPLUSN2, the failover node for VTLPLUSN1, the failed/offline node. 1.
Failback The system should display the expected node name. 3. If you are not logged in to the correct system, you may have accidently logged into the service (“monitoring”) IP address of the failed node. Close the ssh session, and ssh to the other IP address for the current, active node. 4. Change to the directory that holds the VTL executables: [VTL_Plus]vtladmin# cd /usr/local/vtl/bin 5. Run the vtl status command: [VTL_Plus]vtladmin# vtl status Sun Microsystems VTL Server vn.
Failback 7. Run the sms command. The results should look like those shown.
Failback 9. Make sure that you are logged in to the actual, failed node: [VTL_Plus]vtladmin# uname -a SunOS VTLPLUSN1 n.nn Generic_nnnnnn-nn i86pc i386 i86pc The system should display the expected node name. 10. If you are not logged in to the correct system, you have accidently logged into the management IP address (which always connects to the active node) rather than the service (“monitoring”) address. Close the ssh session, and ssh to the other IP address for the failed node. 11.
Failback 13.
Failback where nnn.nnn.nnn.nnx is the service (“monitoring”) IP address of the restarted node, and vtladmin is the VTL administrator account user ID. 16. Make sure that you are logged in to the actual, restarted node: [VTL_Plus]vtladmin# uname -a SunOS VTLPLUSN1 n.nn Generic_nnnnnn-nn i86pc i386 i86pc The system should display the expected node name. 17.
Failback 21.
Failback 23. In the object tree of the VTL console, right‐click the restarted server node, VTLPLUSN1, and select Failover > Stop Takeover from the context menu. 24. Open a terminal window on the management host, and again ssh to the management (“server”) IP address of the restarted node, VTLPLUSN1: [mgt_host]user# ssh vtladmin@nn.nnn.nnn.nnx Connecting to nnn.nnn.nnn.nnx ... Password: where nnn.nnn.nnn.
Failback 28. Run the vtl status command: [VTL_Plus]vtladmin# vtl status Sun Microsystems VTL Server vn.nn (Build nnnn) Copyright 2001-2007 by FalconStor. All Rights Reserve Status Status Status Status Status Status Status Status Status Status Status Status Status Status Status Status Status of of of of of of of of of of of of of of of of of VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL SNMPD Module................ QLogic Module............... Authentication Module.......
Failback 30.
Resuming backups following a failover/failback Failover events are also available via the primary serverʹs Event Log. Next task: “Resuming backups following a failover/failback” on page 157. Resuming backups following a failover/failback Failover/failback take approximately three minutes to complete. During this period, I/O is not possible, and any backup, import/export, replication jobs that are launched fail.
Resuming backups following a failover/failback 158 VTL User Guide • May 2008 G • 96267
CHAPTER 7 Configuring email alerts You can configure VTL appliances to send automatic notifications to local system administrators via email whenever system problems arise. ▼ Configuring email alerts 1. In the object tree of the VTL console, right-click on the VTL server node, and select Options > Enable CallHome. 2.
Note that email notifications cannot use an SSL connection. If the email server requires SSL, configure email notification to use the local host SMTP server, and make sure that DNS and SMTP are set up and running on the VTL server node. The email account password is stored in plain text, so set up an account that the SMTP server will use exclusively for email notification. 3. Use the Interval controls provided (D above) to specify the frequency with which notifications are sent. Then press OK (E). 4.
■ ipstorckcfg check ipstor.conf (VTL configuration check) notifies the administrator if the VTL software’s XML configuration file, ipstor.conf, changes. If changes are found or if no previous version exists, the script creates a copy of the current file under the name ipstorconf.diff.nnn, where nnn is the script-generated version number of the file. ■ diskusagechk.sh / 95 notifies the administrator if root file system utilization exceeds a pre-defined percentage.
7. When the Set Email Alerts Event Notification Properties panel appears, use the radio buttons to select the event-severity level that should trigger notification (K below), use the spinner control to set the Maximum event wait time (L), and press Next (M). K L M 8. When the Verify the Email Alerts Properties panel appears, press Finish. Stop here. ▼ Modifying email alerts properties Once email alerts are enabled, you can modify the information as follows: 1.
1. In the object tree of the VTL console, right-click on the VTL server, and select Email Alerts from the context menu. 2. When the Set Email Alerts Properties dialog appears, select the Trigger tab (A below). A B D C E 3. If you want to modify an existing trigger, highlight the trigger (B above), and press Edit (C). In the Trigger dialog, make your changes (D), and press OK (E).
4. To create a new trigger, press Add (F below). When the Add a Customized Trigger dialog appears, supply a Trigger Name, a command line Argument string, and a File Location (path and filename) for the script (G), and redirect notifications, if desired (H). Press OK (J). G H F J 5. Press OK to exit the Set Email Alerts Properties dialog. Stop here.
CHAPTER 8 Updating VTL software When software patches become available, they are posted on the online Sun StorageTek Customer Resource Center with accompanying, explanatory text (“readme”) files. Download the patch files to a temporary directory on the VTL console host, and install them using the process below. In general, you should consult your Sun support representative before downloading and applying patches. Never apply patches from sources other than Sun.
3. Then, from the VTL console main menu, select Tools (A below). A B 4. From the submenu, select Add Patch (B above). 5. When the warning notice appears, click OK (C below) to continue.
6. Locate the subdirectory where the patch files reside (D below), select the patch file (E), and press Open (F). D update-vtxxxxxxsolarisnn E update-vtxxxxxxsolarisnn F In the example, the patch files are shown in the standard location where patches are kept on the VTL appliance. If you are running the console from a remote host, the patch files will be in the temporary download directory that you selected. 7. When the confirmation dialog appears, type YES in the text box (G below), and press OK (H).
9. Reconnect to the VTL server by double‐clicking on the server node in the object tree at the left of the VTL console. 10. Verify that the patch was successfully applied: after you have connected, select the Version Info tab for the server (J below), and make sure that the Version and Build (K) have been updated. J vN.N K N.
APPENDIX A VTL command line reference VirtualTape Library User Guide VirtualTape Library (VTL) provides a simple utility that allows you to perform some of the more common VTL functions at a command line instead of through the VTL Console. You can use this command line utility to automate many tasks, as well as integrate VTL with your existing management tools. Using the command line utility Type iscon at the command line to display a list of commands.
■ For a value entered as a literal, it is necessary to enclose the value in quotes (double or single) if it contains special characters such as *, <, >, ?, |, %, $, or space. Otherwise, the system will interpret the characters with a special meaning before it is passed to the command. ■ Literals cannot contain leading or trailing spaces. Leading or trailing spaces enclosed in quotes will be removed before the command is processed. Common arguments The following arguments are used by many commands.
Login/logout to the VTL Server Login/logout to the VTL Server Log in to the VTL Server iscon login [-s -u -p |-e] [-X ] iscon login [--server-name= --server-username= --server-password=|--environment] [--rpc-timeout=] Description: This command allows you to log into the specified VTL Server with a given username and password.
Virtual devices / Clients Log out from the VTL Server iscon logout -s [-X ] iscon logout --server-name= [--rpc-timeout=] Description: This command allows you to log out from the specified VTL Server. If the server was not logged in or you have already logged out from the server when this command is issued, error 0x0902000f will be returned. After logging out from the server, the ‐u and –p arguments will not be optional for the server commands.
Virtual devices / Clients ‐C (‐‐long‐client‐list) displays the assigned client list when ‐l (‐‐longlist) option is specified. ‐M (‐‐output‐delimiter) can be specified when ‐l is specified to replace the linefeed with the specified delimiter. The maximum length of the delimiter is 8. ‐X (‐‐rpc‐timeout) is an option to specify a number between 1 and 30000 in seconds for the RPC timeout. The system will retry the command for the amount of time specified if the server does not respond.
Virtual devices / Clients Add client iscon addclient -s [-u -p ] -c [-I ] [-a ] [-A ]] | [-C ] [-X ] iscon addclient --server-name= [--server-username= --server-password=] --client-name= [--initiator-wwpns=] [--enable-VSA=] [--enable-iSeries=]] | [--enableCelerra=] [--rpc-timeout=] Description: This command
Virtual devices / Clients This command allows you to delete a client from the specified server. ‐c (‐‐client‐ name) is the name of the client to be deleted. ‐X (‐‐rpc‐timeout) is an option to specify a number between 1 and 30000 in seconds for the RPC timeout. The system will retry the command for the amount of time specified if the server does not respond. The default RPC timeout is 30 seconds.
Virtual devices / Clients The values for are: Readonly, ReadWrite, ReadWriteNonExclusive. The values for the short format are: R / W / N. ‐y (‐‐vlib‐only) is an option that allows you to assign the virtual tape library to the client without assigning all of the virtual tape drives in the library. The default is to assign all of the virtual tape drives in the library. ‐I (‐‐initiatorWWPN) and ‐T (‐‐targetWWPN) are options for Fibre Channel clients.
Virtual devices / Clients ‐X (‐‐rpc‐timeout) is an option to specify a number between 1 and 30000 in seconds for the RPC timeout. The system will retry the command for the amount of time specified if the server does not respond. The default RPC timeout is 30 seconds.
Virtual devices / Clients ‐v (‐‐vdevid) is required to specify the virtual device ID. A virtual device cannot be deleted if any of the following conditions apply: ■ The specified virtual device is a virtual tape library or a virtual tape drive and there are clients currently connected to the library or drive. ■ The specified virtual device is a virtual tape configured for replication, unless the ‐f (‐‐force) option is used.
Virtual devices / Clients ‐X (‐‐rpc‐timeout) is an option to specify a number between 1 and 30000 in seconds for the RPC timeout. The system will retry the command for the amount of time specified if the server does not respond. The default RPC timeout is 30 seconds.
Virtual devices / Clients [--capacity-on-demand --initial-size= --incrementsize=] [--max-capacity=] [--auto-loader=] [--key-name= --key-pasword=] [--rpc-timeout=] Description: This command creates a virtual tape library. ‐t (‐‐vlib‐type) is required in the following format: : ‐n (‐‐vlib‐name) is optional.
Virtual devices / Clients ‐T (‐‐num‐of‐slots) and ‐E (‐‐import‐export‐slots) are optional. The can exceed the maximum number of slots supported by the specified library type, but it is limited to 65536. The <‐‐import‐export‐slots> cannot exceed the maximun number of IE slots supported by the specified library type. The default is to use the maximum number of slots supported by the specified library type. ‐D (‐‐capacity‐on‐demand) is an option to expand the virtual tape when needed.
Virtual devices / Clients ‐L (‐‐tape‐library‐vid) is required to specify the virtual tape library to add the virtual tape drive(s). ‐r (‐‐vdrive‐name‐prefix) is an option to specify the prefix of the virtual tape drive. The default prefix is in the format of ‐‐. ‐R (‐‐num‐of‐drives) is optional, the default is 1 if it is not specified. ‐X (‐‐rpc‐timeout) is an option to specify a number between 1 and 30000 in seconds for the RPC timeout.
Virtual devices / Clients The unit of , and are all in GB. ‐X (‐‐rpc‐timeout) is an option to specify a number between 1 and 30000 in seconds for the RPC timeout. The system will retry the command for the amount of time specified if the server does not respond. The default RPC timeout is 30 seconds.
Virtual devices / Clients ‐B (‐‐barcode) is an option to either set the virtual tape with the provided barcode or create virtual tapes in batch mode configured with barcodes form the specified barcode range. The argument must be within the barcode range configured for the library and must not contain used barcodes. When provided as a barcode range, the option creates a virtual tape for each barcode in the range.
Virtual devices / Clients iscon movevirtualtape --server-name= [--server-username= --server-password=] --vdevid= [--tape-library-vid= | --tape-drive-vid= | --slot-no=] [--rpc-timeout=] Description: This command moves a virtual tape to a different location. ‐v (‐‐vdevid) is required to specify the ID of the virtual tape to be moved. ‐L (‐‐tape‐library‐vid) is the virtual library to move to.
Virtual devices / Clients Tape copy iscon tapecopy -s [-u -p ] -v -S [-U -P ] [-L | -D ] [-n ] [-f] [-X ] iscon tapecopy --server-name= [--server-username= --server-password=] --source-vdevid= --target-name= [--target-username= --target-password=] [--tape-lib
Virtual devices / Clients -v -Z -Q [-X ] iscon setvirtuallibrarytapeduplication --server-name= [--server-username= --server-password=] --vdevid= --tape-duplication= --num-of-copies= [--rpc-timeout=] Description: This command sets the Tape Duplication property for a virtual tape library. ‐v (‐‐vdevid) is required in order to identify the virtual library.
Virtual devices / Clients Description: This command sets tape properties. ‐v (‐‐vdevid) is required to specify the ID of the virtual tape to set the properties. ‐B (‐‐barcode) is the option to specify the new barcode for the tape. ‐f (‐‐force) option is required if the new barcode is not in the barcode range specified for the parent library. Barcode is an alpha‐numerical value with a length of 4 to 12.
Automated tape caching ‐k (‐‐key‐name), ‐W (‐‐key‐password) and ‐d (‐‐disable‐key) are options for tape encryption support to be set in conjunction with Auto‐Archive Mode. Specify the key name and key password of the encryption key if you wish to encrypt the data when exporting the virtual tape to the physical tape. Specify ‐d (‐‐disable‐key) if you wish to disable tape encryption for this tape.
Automated tape caching Description: This command can be used in order to enable, disable, or change the Automated Tape Caching policy for a virtual tape library. ‐L (‐‐tape‐library‐vid) is the virtual device ID of the virtual tape library to be set. Set ‐t (‐‐tape‐caching‐enable) to 1 for enable or 0 to disable. If the disable option is used all other arguments will be ignored. The enable option must be used in order to set or change the tape caching policy.
Automated tape caching ‐X (‐‐rpc‐timeout) is an option to specify a number between 1 and 30000 in seconds for the RPC timeout. The system will retry the command for the amount of time specified if the server does not respond. The default RPC timeout is 30 seconds.
Automated tape caching ‐k (‐‐key‐name) and ‐W (‐‐key‐password) are options for tape encryption support. If the tape to be synchronized was encrypted through the system, you need to specify the key name and the key password of the encryption key to decrypt the data on the imported tape. [‐I <‐‐scsiaddress>] is the option to specify which physical devices to be used to create the virtual device. It can be a list of ACSLs separated with commas.
Automated tape caching Reclaim disk space iscon reclaimtapes -s [-u -p ] -T [-X ] iscon reclaimtapes --server-name= [--server-username= --server-password=] --tape-vid-list= [--rpc-timeout=] Description: This command reclaims the disk space occupied by the specified migrated virtual tapes.
System configuration ‐I (‐‐scsiaddress) is the option to specify which physical devices should be used to create the virtual device. It can be a list of ACSLs separated with commas or a file enclosed in <> containing an ACSL on each line. ACSL=#:#:#:# (adapter:channel:id:lun) ‐n (‐‐vdevname) is an option to specify the virtual tape name or prefix when creating more than one tape. The maximum length of the virtual device name is 64. Leading and trailing spaces will be removed.
System configuration Remove a license keycode iscon removelicense -s [-u -p ] -k [-X ] iscon removelicense --server-name= [--server-username= --server-password=] -license= [--rpc-timeout=] Description: This command removes a license keycode. ‐X (‐‐rpc‐timeout) is an option to specify a number between 1 and 30000 in seconds for the RPC timeout.
Import/Export ‐F (‐‐vtl‐info‐filter) is an additional filter that can be combined using the following values separated with commas: library or drive or tape. ■ library = include physical and/or virtual library information. ■ drive = include physical and/or virtual drive information. ■ tape = include physical and/or virtual tape information. For example: ‐F ʺlibrary,drive,tapeʺ or ‐‐vtl‐info‐filter=ʺlibrary,drive,tapeʺ The default is to display all of the information that applies.
Import/Export ‐M (‐‐import‐mode) is an option in one of the following values: copy (default) or direct‐access or recycle. ‐v (‐‐pdrive‐or‐pdrive‐vid) is required to specify the virtual device ID of the physical tape library or physical tape drive from which the physical tape is to be imported. If the physical tape is from a physical tape library, either or of the physical tape should be specified with ‐B (‐‐barcode) or ‐l (‐‐slot‐no) to identify the physical tape.
Import/Export Description: This command exports the information from a virtual tape to a physical tape. ‐v (‐‐vdevid) is required to specify the ID of the virtual tape to be exported to the physical tape. ‐L (‐‐tape‐library‐vid) is also required to specify the ID of the target physical tape library.
Import/Export [-j ] [-T -S ] [-X ] iscon getimportexportjobstatus --server-name= [--server-username= --server-password=] [--job-id-list=] | [--job-type= -job_status=] [--rpc-timeout=] Description: This command displays the status of the import/export jobs present in the queue. If no filters are specified, the command displays all the jobs that are in the queue.
Import/Export Delete import/export jobs iscon deleteimportexportjobs -s [-u -p ] -j [-X ] iscon deleteimportexportjobs --server-name= [--server-username= --server-password=] --job-idlist= [--rpc-timeout=] Description: This command deletes specified import/export jobs. The jobs must be held in the import/export queue. ‐j <‐‐job‐id‐list> is a list of job IDs separated with commas.
Replication [--server-username= --server-password=] --job-idlist= [--rpc-timeout=] Description: This command cancels specified import/export jobs. The jobs must be held in the import/export queue and must be running. ‐j <‐‐job‐id‐list> is a list of job IDs separated with commas. ‐X (‐‐rpc‐timeout) is an option to specify a number between 1 and 30000 in seconds for the RPC timeout.
Replication ‐v (‐‐source‐vdevid) is required to specify the ID of the virtual tape to be configured for replication. ‐S (‐‐target‐name) is required to specify the target server name. ‐U (‐‐target‐username) and ‐P (‐‐target‐password) are optional for connection and login to the target server if the target server are not logged in with a login command. The replication configuration requires a trigger policy to be set.
Replication Promote a replica iscon promotereplica -s -v | -S -V [-u -p ] [-U -P ] [f] [-X ] iscon promotereplica --server-name= --vdevid= | --target-name= --replicaid= [--serverusername= --server-password=] [--target-username= --target-password=] [--force] [--rpc-timeout=] Descr
Replication --server-password=] [--target-username= --target-password=] [--force] [--rpc-timeout=] This command allows you to remove the replication configuration from the primary disk on the primary server and delete the replica disk on the target server. Specify either the primary server and the source virtual tape ID or the target server and the tape replica ID.
Replication Resume replication iscon resumereplication -s [-u -p ] -v [-X ] iscon resumereplication --server-name= [--server-username= --server-password=] --vdevid= [--rpc-timeout=] Description: This command allows you to resume replication for a virtual device that was suspended by the suspendreplication command.
Replication ‐w (‐‐watermark) is a data size based trigger in MB. The watermark is checked when the tape is unloaded from the tape drive and the replication is triggered if the amount of new data on the tape has reached the specified watermark. ‐d (‐‐date) combined with ‐i (‐‐interval) is a time based trigger. The replication is triggered at the time specified by date and then repeated every interval.
Replication ‐v (‐‐source‐vdevid) is required to specify the ID of the source virtual tape. ‐X (‐‐rpc‐timeout) is an option to specify a number between 1 and 30000 in seconds for the RPC timeout. The system will retry the command for the amount of time specified if the server does not respond. The default RPC timeout is 30 seconds.
Physical devices Stop replication iscon stopreplication -s [-u -p ] -v [-X ] iscon stopreplication --server-name= [--server-username= --server-password=] -vdevid= [--rpc-timeout=] This command allows you to stop the replication that is in progress for a virtual device. ‐v (‐‐source‐vdevid) is the ID of the source virtual tape on the primary server to stop.
Physical devices Get physical tape list iscon getphysicaltapelist -s [-u -p ] -l [-X ] iscon getphysicaltapelist --server-name= [--server-username= --server-password=] --plib-vid= [--rpc-timeout=] Description: This command displays a list of physical tapes located in the specified physical tape library. ‐l (‐‐plib‐vid) is the ID of the physical tape library.
Physical devices ‐B(‐‐physical‐tape‐barcode) identifies the physical tape to be moved. If barcode is not provided, the current tape location must be provided accordingly to the requested operation. ‐l(‐‐from‐location‐d) is the current slot or import/export (IE) slot number, or the physical drive virtual ID. ‐t(‐‐to‐location‐id) is the destination slot or IE slot number or the physical drive virtual ID. This does not apply to the IEslot.
Physical devices Assign physical resource to VTL iscon assignresourcetovtl -s [-u -p ] -I [-L ] [-X ] iscon assignresourcetovtl --server-name= [--server-username= --server-password=] --scsiaddress= [--tape-library-vid=] [--rpc-timeout=] Description: This command assigns a physical tape library or drive to VTL.
Physical devices Get physical device information iscon getpdevinfo -s [-u -p ] [-F [-M | -C ] | [-a] [-A] [-I ] ] [-o ] [-X ] iscon getpdevinfo --server-name= [--server-username= --server-password=] [--config [--include-system-info | --category=] | [--allocated-list] [--available-list] [--scsiaddress=] ] [--output-format=] [--rpc-timeout=] Description:
Physical devices Rescan physical devices iscon rescandevices -s [-u -p ] [-a ] [-i ] [-l ] [-L] [-X ] iscon rescandevices --server-name= [--server-username= --server-password=] [--adapter-range=] [--scsi-range=] [--lunrange=] [--sequential] [--rpc-timeout=] Description: This command allows you to rescan the physical resource(s) on the spec
Physical devices The is the unique identifier of the physical device. is the SCSI address of the physical device in the following format: #:#:#:# (adapter:channel:scsi id:lun) Either ‐i (‐‐guid) or ‐I (‐‐scsiaddress) has to be specified. ‐X (‐‐rpc‐timeout) is an option to specify a number between 1 and 30000 in seconds for the RPC timeout. The system will retry the command for the amount of time specified if the server does not respond. The default RPC timeout is 300 seconds.
Reports Reports Server throughput report iscon createserverthroughputreport -s [-u -p ] | [-D ] [-o ] [-f] [-X ] iscon createserverthroughputreport --server-name= [--server-username= --server-password=] [--report-period=] | [--date-range=] [--output-file=] [--force] [--rpc-timeout=] Description: This command creates a report that display
Reports SCSI channel throughput report iscon createscsichannelthroughputreport -s [-u -p ] [-z ] | [-D ] -t [-o ] [-f] [-X ] iscon createscsichannelthroughputreport --server-name= [--server-username= --server-password=] [--report-period=] | [--date-range=] --adapter-no= [--output-file=] [--force] [--rpctimeout=] Des
Reports Device throughput report iscon createdevicethroughputreport -s [-u -p ] -I [-z ] | [-D ] [-o ] [-f] [-X ] iscon createdevicethroughputreport --server-name= [--server-username= --server-password=] -scsiaddress= [--report-period=] | [--date-range=] [--output-file=] [--force] [--rpc-timeout=] Description: This command crea
Reports Physical resources configuration report iscon createphyresourcesconfreport -s [-u -p ] [-o ] [-f] [-X ] iscon createphyresourcesconfreport --server-name= [--server-username= --server-password=] [--outputfile=] [--force] [--rpc-timeout=] Description: This command creates a report that displays the physical resources configuration for a specific server.
Reports Specify the ‐f (‐‐force) option if you want to overwrite the existing file if the output file already exists. ‐X (‐‐rpc‐timeout) is an option to specify a number between 1 and 30000 in seconds for the RPC timeout. The default RPC timeout is 300 seconds.
Reports This command creates a report that displays the physical resource allocation of a specific device on a specific server. ‐I (‐‐scsiaddress) is the LUN address of the device. ‐o (‐‐output‐file) is the file name used to save the report data. If the output filename is not specified, the default filename is: PhysicalResourceAllocation‐server‐MM‐DD‐ YYYY‐‐hh‐mm‐ss[.#] [.#] is the additional suffix when there is a duplicate.
Reports [-D ] [-r | -R ] [-o ] [-f] [-X ] iscon createreplicationstatusreport --server-name= [--server-username= --server-password=] [--daterange=] [--repl-resource-type= | --resource-list=] [[--output-file=] [--force] [--rpc-timeout=] Description: This command creates a report that displays the status of a specified resourc
Reports [-o ] [-f] [-X ] iscon createvirlibinforeport --server-name= [--server-username= --server-password=] [--outputfile=] [--force] [--rpc-timeout=] Description: This command creates a report that displays all of the virtual libraries for a specific server. ‐o (‐‐output‐file) is the file name used to save the report data.
Reports Create job report iscon createjobreport -s [-u -p ] [-z ] | [-D ] [-o ] [-f] [-X ] iscon createjobreport --server-name= [--server-username= --server-password=] [--report-period=] | [--date-range=] [--output-file=] [--force] [--rpc-timeout=] Description: This command creates a report that displays all of the jobs executed during a sel
Event Log Event Log Get Event Log iscon geteventlog -s [-u -p ] [-D ] [-F ] [-o ] [-H] [-f] [-X ] iscon geteventlog --server-name= [--server-username= --server-password=] [--daterange=] [--file-format=] [--include-heading] [-output-file=] [--force] [--rpc-timeout=] Description: This command gets the event log.
Technical support Technical support Get X‐Ray iscon getxray -s [-u -p ] [-l <#|all|YYMMDDhhmm-YYMMDDhhmm>] [-r] [-o ] [-f] [-X ] iscon getxray --server-name= [--server-username= --server-password=] [--get-log=<#|all|YYMMDDhhmm-YYMMDDhhmm>] [--rescan-for-xray] [--outputfile=] [--force] [--rpc-timeout=] Description: This command allows you to get X‐ray information from the VTL Server for diagnost
Technical support Get attention required information iscon getattentionrequired -s [-u -p ] [-X ] iscon getattentionrequired --server-name= [--server-username= --server-password=] [--rpc-timeout=] Description: This commands displays the attention required messages. ‐X (‐‐rpc‐timeout) is an option to specify a number between 1 and 30000 in seconds for the RPC timeout.
APPENDIX B Required ports In order to maintain a high level of security, you should disable all unnecessary ports. The only ports required by VTL are: ■ TCP port 11576 ‐ Used for VTL Console to VTL Server management communication. ■ UDP port 11577 ‐ Used for IP replication. ■ UDP port11578 ‐ Used for encryption. ■ UDP port11579 ‐ Used for encryption. ■ TCP port 11580 ‐ Used for communication between a failover pair. ■ UDP port 161 ‐ Used for SNMP traps. ■ TCP port 161 ‐ Used for SNMP traps.
228 VTL User Guide • May 2008 G • 96267
APPENDIX C Troubleshooting This appendix addresses the following issues: ■ “Problems during console operations” on page 229 ■ “Problems affecting physical resources” on page 232 ■ “Problems with virtual resources” on page 233 ■ “Problems during import/export operations” on page 237 ■ “Taking an X‐ray for technical support” on page 239 Problems during console operations Issue: VTL console is unable to connect to a VTL server Indications: The VTL console does not connect to the server node.
5. If you still cannot connect, try to connect using the server’s IP address instead of its server name (or vice versa). 6. If you can now connect, stop here. The host name or IP address that failed may be incorrect. 7. If you still cannot connect, check network connectivity. Ping the target server and other machines in the same subnet. 8. If you cannot ping the server or the hosts on the same subnet, there is a network outage. Stop here, and correct the problem. Then reconnect to the VTL server.
Case: Connection fails while expanding the VTL server node 1. Check the memory consumption on the console host. 2. If memory consumption is excessive, stop unnecessary processes, and retry. 3. If you can connect, stop here. Avoid running memory‐intensive applications on this host when the console is in use. 4. If you cannot connect or if memory consumption appears to be within normal limits, contact Sun technical support.
Case: High server activity 1. Check the Event Log or syslog (/var/adm/messages) for CPU-intensive activity on the server. Backup jobs that backup to multiple virtual or physical devices in parallel, data compression, and encryption all place heavy demands on the CPU. 1. Also, try starting a second instance of the VTL console. If the second VTL console cannot establish connections, that means the server is busy with previous RPC operations. 2.
7. If you have still not solved the problem, contact Sun technical support. Problems with virtual resources Issue: Virtual tapes are shown offline in the console Indications: Virtual tapes are offline. Diagnostics: Locate the physical resources that back the virtual tapes and assess their state. 1. Identify the physical resources that back the virtual tapes.
5. If you find disk space errors, there may not be enough physical disk space for the expansion. Add more physical storage or change the size of expansion. Then retry. 6. If no disk space problems were found, or if correcting them does not solve the problem, make sure that the physical storage partition is valid. Correct any problems, and retry. 7. If the partition is valid or if correcting it does not solve the problem, look for I/O errors. 8. If I/O errors are found, consult technical support. 9.
2. If the operating system does not show the device, got to “The operating system cannot detect the device” on page 235. 3. If the operating system does show the device, go to “Applications cannot see the device” on page 235. Case: The operating system cannot detect the device 1. If the operating system does not see the device, use the VTL console to check the status of the virtual device. 2.
Case: The backup application cannot see the device at all 1. If the operating system sees the device but a backup application does not, check the drivers for the backup software. Make sure the driver is appropriate for the library and tape drive type. 2. If a driver appears to be inappropriate, refer to the backup software manual. Some backup products recommend specific versions of drivers or special settings. Apply the correct driver. 3. If changing the driver solves the problem, stop here. 4.
3. Using the VTL console, load a tape into a virtual drive. While most raw device utilities work with tape drives, they cannot, in most cases, load tapes. Even if some can move tapes, you need to know the exact address of the tape and the drive. 4. Attempt to access the device using the raw utility. 5. If you cannot access the device, go to “The operating system cannot access the device” on page 237. 6. If you can access the device, go to “The operating system can access the device.” on page 237.
You can only import and export data between a physical tape device and a virtual tape device of the same type, using physical and virtual media of the same capacity. 2. If dissimilar physical and virtual devices or media are being used, stop here. Correct the condition, and retry the import/export job. 3. If physical and virtual devices are identical or if making them so does not solve the problem, see if compressed data is being imported/exported. 4.
2. If physical tape drives require cleaning, clean them, and stop here. Retry the import/export operation. 3. If cleaning is unnecessary or does not help, see if physical tapes need to be moved and mounted before the import/export operation can continue. 4. If tapes have to be moved, move them, and stop here. Retry the import/export operation. 5. If tapes do not need to be moved, check for other anomalous conditions. 6. It other anomalous conditions are found, correct them, and stop here.
▼ Taking an X‐Ray 1. In the object tree of the VTL console, right‐click on the branch representing the VTL server (A below), and select X-Ray from the context menu (B).
2. When the X-Ray Options dialog appears, check the checkboxes corresponding to the items that you need to include (C below). The defaults are shown below: C D E If you select the Log File option, you can filter the output by specifying a number of records or a date range. You can limit the results to VTL system‐related messages by checking the VTL Messages Only check box. 3. In the Save As text box (D above), specify an output path and filename for the X‐Ray archive. 4.
242 VTL User Guide • May 2008 G • 96267
APPENDIX D SNMP traps The VTL product family defines the following Simple Network Management Protocol (SNMP) traps. Trap Severity Message 9 Error SCSI Port Error -- %1. 1000 Error Socket connection could not be terminated properly -- %1. 1001 Error Socket connection could not be terminated properly due to error during shutdown -- %1. 1002 Error Unexpected interrupt occurred. 1003 Informational "VTL Server has detected virtual device[%1] at SCSI %2, channel %3, ID %4, LUN %5.
Trap Severity Message 1020 Informational Replication for virtual tape %1 started. 1021 Informational Replication for virtual tape %1 finished. 1022 Warning Replication has failed for virtual tape %1 -- %2. 1023 Error Failed to connect to physical device %1. Switching alias to %2. 1024 Informational Device %1 has attached to the VTL Server. 1025 Informational Device %1 has detached from the VTL Server.
Trap Severity Message 1047 Error Rescan replica has failed for virtual device %1 -- the replica device failed with error %2. 1048 Error Rescan replica has failed for virtual device %1 -- the network transport returned error %2.
Trap Severity Message 1074 Error Replication cannot proceed -- unable to allocate memory. 1075 Error Replication cannot proceed -- unexpected error %1. 1076 Informational Starting replication for virtual device %1 of group %2 to replica device %3. 1077 Informational Replication for group %1 has completed successfully.
Trap Severity Message 7002 Error Patch %1 failed -- it applies only to build %2. 7003 Error Patch %1 failed -- you must be the root user to apply the patch. 7004 Warning Patch %1 installation failed -- it has already been applied. 7005 Error Patch %1 installation failed -- prerequisite patch %2 has not been applied. 7006 Error Patch %1 installation failed -- cannot copy new binaries. 7007 Informational Patch %1 rollback completed successfully.
Trap Severity Message 10206 Informational Add scsi alias=%1. 10207 Error "Add Adapter %1 failed, not enough memory." 10208 Informational "Set Adapter %1 offline, adapter count %2." 10209 Error "Add Physical Device %1 failed, not enough memory." 10210 Warning Marked Physical Device [%1] OFFLINE because its GUID: %2 does not match scsi GUID: %3. 10211 Warning "Marked Physical Device [%1] OFFLINE because its wwid %2 does not match scsi wwid %3, [GUID: %4].
Trap Severity Message 11006 Error VTL communication module failed to start. 11007 Warning There is not enough disk space available to successfully complete this operation and maintain the integrity of the configuration file. There is currently %1 MB of disk space available. VTL requires %2 MB of disk space to continue. 11010 Informational Changed server time to %1. 11020 Informational Auto save configuration enabled: ftp_server=%1 directory=%2 interval=%3 copies= %4.
Trap Severity Message 11170 Error Failed to virtualize LUN %1 because of mismatching size between configuration file and disk. Please do rescan and try it again. 11200 Error Buffer overflow. 11201 Error Too many Console connections. 11202 Error Console (%1): Illegal access. 11203 Error Console (%1): SCSI device re-scanning has failed. 11204 Error Console (%1): SCSI device checking has failed. 11205 Error Console (%1): Failed to get information for file %2.
Trap Severity Message 11232 Error Console (%1): Failed to get memory status. 11233 Error Console (%1): Failed to map the SCSI device name for [%2 %3 %4 %5]. 11234 Error "Console (%1): Failed to execute ""hdparm"" for %2." 11235 Error Console (%1): Failed to get the VTL Server module status. 11236 Error Console (%1): Failed to get the version information for the message file. 11237 Error Console (%1): Failed to get file %2.
Trap Severity Message 11265 Error Console (%1): Failed to restart IOCore module. 11266 Error Console (%1): Failed to erase partition of virtual device %2. 11267 Informational Console (%1): Virtual device %2 partition erased. 11268 Error Console (%1): Failed to update meta information of virtual device %2. 11269 Error Console (%1): Failed to get ID for SAN Client (%2). 11270 Error Console (%1): Failed to add mirror for virtual device %2.
Trap Severity Message 11298 Error Console (%1): Failed to reset cache on target device %2 (ID: %3) for %4 copy. 11300 Error Invalid user name (%1) used by client at IP address %2. 11301 Error Invalid password for user (%1) used by client at IP address %2. 11302 Error Invalid passcode for machine (%1) used by client at IP address %2. 11303 Error Authentication failed in stage %1 for client at IP address %2. 11304 Informational User %1 at IP address %2 authenticated.
Trap Severity Message 11509 Informational Console (%1): Properties set for the VTL Server. 11510 Error Console (%1): Failed to save report -- %2. 11511 Error Console (%1): Failed to get the information for the NIC. 11512 Error "Console (%1): Failed to add a replica for virtual tape %2 to VTL Server %3 (watermark: %4 MB, time: %5, interval: %6, watermark retry: %7, suspended: %8).
Trap Severity Message 11539 Error Console (%1): Failed to import physical device %2. 11540 Error "Console (%1): Host name mismatch (old: %2, new: %3)." 11541 Error Console (%1): Failed to save event message (ID: %2). 11542 Error Console (%1): Failed to remove virtual tape replica %2. 11543 Informational Console (%1): Virtual tape replica %2 removed. 11544 Error Console (%1): Failed to modify virtual tape replica %2. 11545 Informational Console (%1): Virtual tape replica %2 modified.
Trap Severity Message 11575 Error Console (%1): Failed to unassign Fibre Channel device %2 from %3 (not rolled back) and returns %4. 11576 Informational Console (%1): Fibre Channel device %2 unassigned from %3. 11577 Error Console (%1): Failed to get Fibre Channel target information. 11578 Error Console (%1): Failed to get Fibre Channel initiator information. 11579 Error Console (%1): Failed to set %2 to Fibre Channel authentication mode %3.
Trap Severity Message 11651 Error Medium Test failed for SCSI device %1. 11652 Error "Could not get type for SCSI device %1, because of inquiry string failure." 11653 Error "Discarded scsi device %1, unsupported type ""%2""." 11654 Error "Discarded scsi device %1, missing MTI vendor in inquiry string." 11655 Error "Discarded scsi device %1, bad capacity size." 11656 Error "Discarded scsi device %1, unsupported Cabinet ID.
Trap Severity Message 11711 Error Console (%1): The replication setup for %2 %3(s) was rolled back. 11712 Error Console (%1): Failed to configure replication for %2 %3(s). Error: %4. 11713 Informational Console (%1): Replication for %2 %3(s) configured successfully. 11714 Error Console (%1): The configuration file update for replication removal for %2 %3(s) was rolled back. 11715 Error Console (%1): The disk partition update for replication removal for %2 %3(s) was rolled back.
Trap Severity Message 11740 Error Console (%1): Failed to create virtual tape drives. Error: %2. 11750 Informational Console (%1): Add VirtualTape Library Emulation option successfully. 11751 Informational Console (%1): Remove VirtualTape Library Emulation option successfully. 11780 Informational Tape id %1 [%2] is enabled with auto-replication move mode and will be deleted in %3 at about %4. 11781 Informational The scheduled deletion for virtual tape id %1 is cancelled.
Trap Severity Message 12005 Error Failed to allocate memory. 12006 Warning Log size warning. 12007 Error Failed to delete file %1. 12008 Error Wrong file format %1. 12009 Error Missing parameter %1. 12010 Error Invalid parameter %1. 12011 Error Wrong status for file %1.
Trap Severity Message 13311 Error Failed to merge static configuration for the primary server. 13312 Error Failed to merge dynamic configuration for the primary server. 13313 Error Out of memory -- %1. 13314 Error Failed to read from file %1. 13315 Error Failed to merge authentication information for the primary server. 13316 Error Fail to add virtual IP address. Error: %1. 13317 Error Fail to release virtual IP address. Error: %1.
Trap Severity Message 13811 Informational Primary server failback initiated. 13812 Informational Server IP address add successfully. 13814 Informational Quorum disk returned to primary. 13815 Informational Virtual drives added successfully. 13816 Informational Primary server restored. 13817 Critical Primary server failback was unsuccessful. Failed to update the primary configuration. 13818 Error Quorum disk negotiation failed.
Trap Severity Message 13843 Error Secondary server fail to get original conf file from repository before failback . 13844 Error Failed to write %1 to repository. 13845 Warning Quorum disk failure detected. Secondary is still in takeover mode. 13846 Informational Force takeover is initiated. Secondary will perform SCSI reserve to lock the storage. 13847 Informational Secondary server is performing SCSI release to storage. 13848 Warning Primary is already shut down.
Trap Severity Message 13878 Error Primary server has invalid failover configuration. 13879 Critical Secondary server detect kernel module failure, reboot machine may need. 15050 Error Server ioctl call %1 failed on vdev id %2: Invalid Argument (EINVAL). 15051 Error Server ioctl call %1 failed on vdev id %2: I/O error (EIO). 15052 Error Server ioctl call %1 failed on vdev id %2: Not enough memory space (ENOMEM).
Trap Severity Message 19051 Informational [Remote Copy] The copying of the virtual tape %1 to the remote server has been started. 19052 Informational [Remote Copy] The copying of the virtual tape %1 to the remote server has finished. 19053 Informational "[Remote Copy] The configuration for remote copy is removed. Server: %1, Virtual Tape: %2, Remote Server: %3, Tape Replica: %4.
Trap Severity Message 19204 Error Console (%1): Failed to delete Key %2. 19205 Informational Console (%1): Key %2 has been deleted successfully. 19206 Error Console (%1): Failed to update information for key %2. 19207 Informational Console (%1): Information for key %2 has been updated successfully. 19208 Error Console (%1): Failed to create key package %2. 19209 Informational Console (%1): Key package %2 has been created successfully.
Trap Severity Message 25001 Error %1 failed to start -- %2. 25002 Informational %1 paused. 25003 Error %1 failed to pause -- %2. 25004 Informational %1 resumed. 25005 Error %1 failed to resume -- %2. 25006 Informational %1 stopped. 25007 Error %1 failed to stop -- %2. 25008 Informational %1 shutdown. 25009 Informational %1 starting. 25010 Informational %1 stopping. 25011 Error Failed to open service manager -- %1. 25012 Error Failed to open service -- %1.
Trap Severity Message 26207 Error Failed to define device %1 -- %2. 26208 Error Failed to undefine device %1 -- %2. 26209 Error Drive %1 is busy and cannot be detached. time. 26210 Informational Both %1 and %2 have the same disk signature (%3). 27000 Error Failed to connect to VTL Server ’%1’ -- %2. 27001 Error Failed to get the version of VTL Server ’%1’ -- %2. 27002 Error Failed to get the information for VTL Server ’%1’ -- %2.
Trap Severity Message 40007 Error "Unload tape from drive failed, Drive %1, EC %2" 40008 Error Failed to create new tape in Virtual Library %1 40009 Error "HW Error with Move Medium command, Lib %1, SrcEle %2 DestEle %3" 40010 Error Attach to tape %1 failed 40011 Error "Failed to read from Virtual Tape. Tape VID %1, EC %2" 40012 Informational Unsupported SCSI command %1 40013 Error "Export Tape failed, not enough memory. Job id %1" 40014 Error "Read tape info failed.
Trap Severity Message 40038 Informational "Physical Library unassigned. Vid %1, [%2][%3]" 40039 Error Read Element command to Physical Library %1 failed. EC %2 40040 Error Attach to device %1 failed. EC %2 40041 Informational "Physical Tape Drive assigned to exclusive use for VTL. VID %1, [%2][%3]" 40042 Informational "Physical Tape Drive unassigned. Vid %1, [%2][%3]" 40043 Error "Move Medium command failed in Physical Library %1.
Trap Severity Message 40070 Error Cannot delete Tape %1 40071 Error "Cannot import Tape, dest slot %1 in Virtual Library %2 is full" 40072 Informational "Properties of Tape %1 has been changed. Barcode %2, MaxCapacity %3 MB" 40073 Informational "Tape Created in Stand Alone Virtual Tape Drive. Tape VID %1, Drive VID %2" 40074 Error "Export to Physical Tape failed.
Trap Severity Message 40100 Error Waited %1 seconds to get a response from %2 (%3) after trying to retrieve drive information in ACS %4. Timing out. 40101 Error Failed to retrieve volume information in ACS %1 and Pool %2. Error from %3 (%4): %5. 40102 Error Waited %1 seconds to get a response from ACSLS (%2) after trying to retrieve volume information in ACS %3 and Pool %4. Timing out. 40103 Error Failed to retrieve LSM information in ACS %1. Error from %2 (%3): %4.
Trap Severity Message 40127 Informational Disk space allocated for tape VID %1 Barcode [%2] in vault has been reclaimed successfully 40128 Error Failed to reclaim disk space allocated for tape VID %1 Barcode [%2] in vault 40129 Informational No Free physical drive to load direct link tape VID %1 BarCode [%2]. 40130 Warning Unable to renew cache for tape VID %1. Data will be redirected to physical tape [%2]. 40131 Informational The tape shredding job is successful on the tape [%1].
274 VTL User Guide • May 2008 G • 96267
APPENDIX E ILOM command reference The following table summarizes Integrated Lights Out Manager (ILOM) commands you can use to manage the service processor. For more information on ILOM commands, see the ILOM Administration Guide. Description Command User Commands Add a local user. create /SP/users/user1 password=password role=administrator|operator Delete a local user. delete /SP/users/user1 Change a local user’s properties.
Description Command Change the host serial port configuration. Note: This speed setting must match the speed setting for serial port 0, COM1 or /dev/ttyS0 on the host operating system. set /SP/serial/host pendingspeed=integer commitpending=true Alert Commands Display information about PET alerts. You can configure up to 15 alerts. show /SP/alert/rules/1...15 Change alert configuration. set /SP/alert/rules/1...
Description Command Host System Commands Delete this device from an SNMP private community. delete /SP/services/snmp/communities/private/comm2 Start the host system. start /SYS Stop the host system. stop /SYS Reset the host system. reset /SYS Start a session to connect to the host console. start /SP/console Stop the session connected to the host console. stop /SP/console Clock Settings Set the ILOM clock to synchronize with a primary NTP server.
278 VTL User Guide • May 2008 G • 96267
