05. q star system_administrator's_guide_windows_v6.0_rev.07

System Administrator’s Guide

Product Series for UnixData Management SystemVersion 6For All Supported Platforms

Storage Management Software

Please refer to the QStar license and Copyright information at the end of this manual before installing any QStar Software.

IF YOU NEED ASSISTANCE

Contact QStar Technical Support: • In the United States, Dial +1-850-243-0900 • In Europe, Dial +39-02-45-171-1 • Or E-mail support in North America is available through [email protected] • Or E-mail support in Europe is available through [email protected]

Addresses: QStar Technologies, Inc. (USA) 8738 Ortega Park Drive Navarre, FL 32566 Tel: +1-850-243-0900 Fax: +1-850-243-4234 E-mail: [email protected] Web URL: http://www.qstar.com/ QStar Technologies Europe ITALY Viale Italia 12 20094 Corsico (Milano) Italy Tel: +39-02-45-171-1 Fax: +39-02-45-101-745 E-mail: [email protected] Web URL: http://www.qstar.com/ QStar Technologies Japan Shinjuku Park Tower N30F 3-7-1 Nishi Shinjuku, Shinjuku-ku Tokyo 163-1030 Japan E-mail: [email protected] Web URL: http://www.qstar.com/

mailto:[email protected]

http://www.qstar.com/



QStar SOFTWARE LICENSE CARD This License Agreement is your proof of License.

Please treat it as valuable property.

QStar LICENSE AGREEMENT This is a legal Agreement between you (either an individual or an entity) and QStar Technologies, Inc. By opening the sealed software packages and/or by using the SOFTWARE, you agree to be bound by the terms of this Agreement. If you do not agree to the terms of this Agreement, do not open the SOFTWARE packages. Promptly return the SOFTWARE packages and any other materials that are parts of this QStar Product.

QStar SOFTWARE LICENSE GRANT OF LICENSE. License grant in consideration of payment of the License fee you paid for this QStar Product. QStar as LICENSOR, grants you, the LICENSEE, a non-exclusive right to use and display this copy of the QStar Product and permits you to use the QStar Product on as many computers as you have authorized Licenses. The SOFTWARE is “in use” on a computer when it is loaded into the temporary memory (i.e., RAM) or installed into the permanent memory (e.g., hard disk, CD-ROM, or other storage device) of that computer, except that a copy installed on a network server for the sole purpose of distribution to other computers is not “in use”. QStar reserves all rights not expressly granted to the LICENSEE.

COPYRIGHT. The SOFTWARE (including any images, photographs, animations, video, audio, music, and text incorporated into the SOFTWARE) is owned by QStar Technologies, or its suppliers, and is protected by United States copyright laws and international treaty provisions. Therefore, you must treat the SOFTWARE as any other copyrighted material (e.g., a book or musical recording) except that you may either (a) make one copy of the SOFTWARE solely for backup or archival purposes, or (b) transfer the SOFTWARE to a single hard disk provided you keep the original solely for backup or archival purposes. Unauthorized copying of the QStar Product even if modified, merged or included with other SOFTWARE, or of the written materials, is expressly forbidden. OTHER RESTRICTION. This QStar Product, user guide, and documentation is licensed to you, the LICENSEE, and may not be transferred to any third party for any length of time without the written consent of QStar. You may not reverse engineer, de-compile, modify, adapt, translate or disassemble the SOFTWARE, except to the extent that applicable law expressly prohibits the foregoing restriction. DUAL-MEDIA SOFTWARE. As the LICENSEE, you own the magnetic or other physical media on which the QStar Product is recorded or fixed, but QStar retains title to and ownership in the SOFTWARE program of the QStar Product. You may not use the media on any other computer or computer network, or loan, rent, lease, or transfer them to another user except as part of a permanent transfer (as provided above) or other use expressly permitted by this License. This License is not a sale of the original SOFTWARE program of the QStar Product or any portion or copy of it. DISCLAIMER AND LIMITED WARRANTY. QStar Technologies warrants that the SOFTWARE will perform substantially in accordance with the accompanying product manuals for a period of ninety (90) days from the date of receipt. Any implied warranties on the SOFTWARE are limited to ninety (90) days. Some states/jurisdictions do not allow limitations on duration of an implied warranty, so the above limitation may not apply to you. QStar Technologies’ entire liability and your exclusive remedy shall be repair or replacement of the SOFTWARE that does not meet QStar Technologies’ Limited Warranty. This Limited Warranty is void if failure of the SOFTWARE has resulted from accident, abuse, or misapplication. QStar shall have no responsibility to replace the disk or refund the License fee. TERMINATION. This Agreement is effective until terminated. This Agreement will terminate automatically without notice from QStar Technologies if you fail to comply with any provision contained herein. Upon termination, you shall destroy the written materials, the QStar Product and all copies of them, in part and in whole, including any modified copies. PRODUCT UPDATES. QStar may from time to time update the QStar Product. Updates may be made available to you based upon payment of annual software support fees and/or upgrade fees, to QStar or QStar’s Authorized Service Partners, and the level of service purchased.

EVALUATION SOFTWARE. If the SOFTWARE you have requested is an evaluation copy only, LICENSEE recognizes that the SOFTWARE has tangible value, contains valuable trade secrets, copyrights, and confidential information of QStar and is the sole property of QStar. LICENSEE shall have no right to print or copy the QStar SOFTWARE or documentation in whole or in part. All SOFTWARE shall remain the property of QStar and must be returned upon completion of evaluation. QStar SOFTWARE is “For Demonstration or Evaluation Use Only.” LICENSEE agrees not to re-sell and/or use the SOFTWARE provided for its own internal business usage without the formal written consent of QStar. NO OTHER WARRANTIES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, QSTAR TECHNOLOGIES DISCLAIMS ALL OTHER WARRANTIES, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE SOFTWARE, AND THE ACCOMPANYING WRITTEN MATERIALS. THIS LIMITED WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS. YOU MAY HAVE OTHER RIGHTS, WHICH VARY FROM STATE/JURISDICTION TO STATE/JURISDICTION. NO LIABILITY FOR CONSEQUENTIAL DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL QSTAR TECHNOLOGIES, OR ITS SUPPLIERS, BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OR INABILITY TO USE THIS QSTAR TECHNOLOGIES PRODUCT, EVEN IF QSTAR TECHNOLOGIES HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Because some states/jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, the above limitation may not apply to you.

RESTRICTED RIGHTS. The SOFTWARE and documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraph (c)(1) and (2) of the Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is QStar Technologies, 8738 Ortega Park Drive Navarre, FL 32566 USA. Unpublished – All rights reserved under the copyright laws of the United States and of other countries. GENERAL. If you acquired this product in the United States, the laws of the State of Florida govern this Agreement. If this product was acquired outside the United States, then local law may apply.

This Agreement sets forth the entire Agreement between QStar and you may be amended only in writing signed by both parties. No waiver of any right under this Agreement shall be effective unless in writing signed by both parties. If any provision in this Agreement is invalid or unenforceable that provision shall be construed, limited, modified or, if necessary served, to the extent necessary, to eliminate its invalidity or un-enforceability and all other provisions of this Agreement shall remain unaffected. Should you have any questions concerning this Agreement, or if you desire to contact QStar Technologies for any reason, please contact the subsidiary serving your country, or write: QStar Technologies, Inc., Attn: General Counsel, 8738 Ortega Park Drive Navarre, FL 32566 USA.

QStar Technologies is a registered trademark of QStar Technologies, Inc

D-LIC-05-09 5/00

of 4

QStar Technologies is the market leader in secure, large-scale client/server archiving and data management solutions for Windows and UNIX. QStar provides solutions that allow every level of your organization to store and manage the resources of even the most heterogeneous networks. The world’s leading organizations increasingly rely on QStar for the secure, cost effective and reliable storage of their critical data. More than two decades of experience and a large installed base have provided QStar with the knowledge to create software that brings life to storage hardware. The functionality of QStar Software is based on extensive research of user requirements and customer feedback, which has enabled QStar to develop an industry-leading product. QStar Software significantly reduces the overall storage costs within a network. At the same time, productivity is boosted by keeping all of the data logically online, all the time. QStar Software integrates all storage media on the network. Magnetic disks, Cloud Storage, optical, tape, RDX, both offline and nearline, are consolidated into a single network storage hierarchy. The view of the storage hierarchy is a network available logical disk, transparent to users and applications. Using this method, terabytes or petabytes of data storage can be accessed in real time. QStar Software can represent multiple media as a single volume, keeping track of the exact location of all files on each medium. Archiving applications for Media and Entertainment, Imaging, CAD/CAM, Document Management, PACS, and other applications are fully compatible with QStar Software. This System Administrator’s Guide provides the information you will need to install, configure and utilize QStar Software to manage data. It contains all the necessary information to achieve the best results for implementing and customizing your mass storage solution. This Chapter contains an introduction to the platforms, devices and media supported.

PLATFORMS SUPPORTED ...................................................................................2 MEDIA SUPPORTED...........................................................................................3 QSTAR MANUAL REVISION.................................................................................3 CHAPTER SUMMARY..........................................................................................4

of 4

PLATFORMS SUPPORTED QStar Software supports the following server platforms: • Sun - Solaris • IBM - AIX • Hewlett Packard - HP-UX series 700/800 • Microsoft - Windows 2003/2008, Windows XP, Windows Vista, Windows 7 • Linux - Redhat - SUSE - Debian - Ubuntu - Mandrake - Gentoo – Fedora - CentOS • Apple - MAC

of 4

MEDIA SUPPORTED The type and quantity of data being stored by users determines which media they will use to store it. QStar supports a wide variety of archival media, including Optical disks, digital Tapes, RDX, CD-ROMs, DVD-ROMs DVD-RAMs and Blu-ray. Removable Media, come in a wide range of sizes and capacities. Another distinguishing characteristic is whether they are Rewritable, able to be erased and reused, or WORM, Write Once Read Many. The following list defines the media types currently supported: MEDIA TYPE

SUPPORT TYPE

Rewritable MO Optical Read/Write WORM MO Optical Read/Write Rewritable UDO1 - UDO2 Read/Write WORM UDO1 - UDO2 Read/Write Compliance WORM UDO1 - UDO2 Read/Write Rewritable PDD Read/Write WORM PDD Read/Write Tape (AIT - AIT2 - AIT3 - AIT3 WORM - SAIT) Read/Write Tape (LTO1 - LTO2 - LTO3 - LTO4 - LTO5 – LT06) Read/Write Tape (DLT - SDLT ) Read/Write Tape (9730 - 9840 - 9940A - 9940B) Read/Write Tape Oracle T10000C Read/Write CD/DVD-ROM Read Only CD-R Read/Write CD-RW Read/Write DVD-RAM Read/Write DVD-R Read/Write DVD-RW Read/Write BD-RE Read/Write BD-R Read/Write RDX Read/Write Centera/HCP/OSM/Cleversafe/Amplidata Read/Write HARD DISK (Simulated Disk/Tape) Read/Write

QSTAR MANUAL REVISION August 2012 Revision A (Windows and UNIX): Manual for release starting with v6.0.

of 4

CHAPTER SUMMARY Chapter One: INTRODUCTION This chapter contains an introduction to the platform, device and the media supported; it also contains a brief overview of QStar products and their features. Chapter Two: QSTAR COMPONENTS This chapter describes the main components of QStar Software and the terminology used in later sections of the manual. These descriptions will help the user gain an understanding of the product, to ensure that the maximum performance, functionality and organization for the storage solution are obtained. Chapter Three: INSTALLING AND CONFIGURING QSTAR SOFTWARE The first section of this chapter describes how to load the QStar Software onto the system and how to connect the hardware devices. The second section describes the installation of the QStar Software and the configuration of the storage device(s). The third section describes how to generate and install license keys. There is also a section to aid in upgrading from earlier versions of the QStar Software. Chapter Four: LIBRARY MANAGEMENT This chapter describes how to manage the library and its components including the media and drives within the library. Also included are steps to gather library statistics and tune the library for optimum performance. Chapter Five: THE VOLUME LIBRARIAN This chapter describes the use of the Volume Librarian database and how it handles the media. There are sections on how media is handled both in and out of the library as well as creating and managing Integral Volume sets. Chapter Six: MIGRATION MANAGER This chapter describes how to set-up the cache for an Integral Volume set and how to configure it for the best performance. There is also a description of how the cache works. Chapter Seven: MEDIA CONFIGURATIONS This chapter describes how to create the Integral Volume set configuration for all type of media supported by QStar Software. Included are walk through examples showing how each can be achieved. Chapter Eight: DISASTER RECOVERY This chapter covers some common hardware problems and how to recover from them. Chapter Nine: COMMAND REFERENCE This chapter covers all of the QStar commands available on the UNIX/Windows platforms, including explanations and command options.

of 20

Depending on the product purchased, QStar Software will install different components on the system. Before you install and configure the Software, you should be comfortable with QStar’s terminology and concepts. Please take the time to read all sections, as this will ensure that the maximum performance, functionality and organization for the storage solution are obtained. This section identifies key terminology and concepts that are vital for you to understand. Also included are the descriptions of QStar modules and conceptual and practical definitions for creating the configuration.

GENERAL COMPONENTS ....................................................................................3 API Interface ................................................................................................3 Command Line Utilities...................................................................................3 QStar Administration Interface ........................................................................3 QStar Administration Interface Changes ...........................................................3 Privileged Users (UNIX Option) ........................................................................3 Online Help Manual Pages...............................................................................3 Remote Administration ...................................................................................4 VL Scheduler ................................................................................................4 No Media Option............................................................................................4

DEVICE MANAGER COMPONENTS........................................................................5 QStar “SCSI” Manager ...................................................................................5 Library Manager ............................................................................................5 View Store....................................................................................................5 Library Statistics ...........................................................................................5

MEDIA MANAGER COMPONENTS .........................................................................6 QStar “Volume Librarian” Database..................................................................6 Bar Code Support ..........................................................................................6 Online Media Management ..............................................................................6 Dated Mount.................................................................................................6 Offline Media Management..............................................................................6 Data Compaction...........................................................................................6 Simulated Media Libraries ...............................................................................7 VL Copy Media ..............................................................................................7 VL Cross Copy Mirror Media ............................................................................7 VL Copy Using Publisher Devices......................................................................7

MIGRATION MANAGER COMPONENTS..................................................................8 Migration Manager.........................................................................................8 Cache ..........................................................................................................8 Cache Enhancements .....................................................................................8 File Migration ................................................................................................8 Transaction Logging Cache .............................................................................8 Read Only Grace Period..................................................................................8 Retention Period............................................................................................9 Write Once and Deny Rename.........................................................................9 NFS Mount ...................................................................................................9 Virtual Disk...................................................................................................9

of 20

DIAGNOSTIC COMPONENTS............................................................................. 10 Syslog View Pane or QStar‘s Syslog File .......................................................... 10 SCSI Log View Pane or Qscsi_log Command .................................................... 10 Console View Pane or Vlconsole Command ...................................................... 10 Mail Notification .......................................................................................... 10

FILE SYSTEMS................................................................................................ 11 SDF (Standard Data Format)......................................................................... 11 UDF (Universal Disk Format) ......................................................................... 12 UVFS - Support for the Plasmon File Systems .................................................. 13 AAFS - Support for the Archive Appliance Plasmon File System .......................... 13 TDO (Tape and Disk Object File System)......................................................... 13 LTFS (Linear Tape File System) ..................................................................... 14

MEDIA ORGANIZATION ................................................................................... 15 MAJOR SOFTWARE ENHANCENENT IN VERSION 5.1 ............................................ 16 MAJOR SOFTWARE ENHANCENENT IN VERSION 6.0 ............................................ 18

of 20

GENERAL COMPONENTS The general components of the QStar Software are as follows: API Interface QStar operates seamlessly with all major UNIX and Windows Platforms with full Application Programming Interface (API) support. A separate API Interface manual is available upon request from QStar.

Command Line Utilities The QStar Software on the Windows platforms creates the c:\qstar\bin directory and on the UNIX platforms creates the /opt/QStar/bin and the /opt/QStar/etc directories. In these directories QStar places all the user and Administrator commands. The QStar Software for Windows platforms allows the System Administrator to run all the QStar commands from the Windows DOS prompt. With this added functionality, System Administrators will have greater flexibility in managing and integrating the QStar Software. Adding the /opt/QStar/bin and /opt/QStar/etc paths to the Administrator's default execute path (PATH environment variable) on the UNIX platforms will make all QStar commands accessible to the System Administrator.

QStar Administration Interface The QStar Administration Interface (Windows) allows configuring, and viewing of the underlying structure of the QStar Server, providing a single interface for management of the QStar Software and devices. Through the QStar Graphical User Interface (GUI) (Windows only) management of the hardware (configuration/ trouble shooting, and statistics), media (online/offline databases), file systems, mounting and unmounting of the Integral Volume sets, migration behavior, logging, and email notification alerts are all possible. A web-based GUI is available for Linux and Mac Administrators.

QStar Administration Interface Changes The QStar Administration Interface (Windows) has been completely redesigned; the new GUI is resizable and consists of a window divided into two panes. The navigation pane is on the left side and contains the categories tree. The categories tree shows the items that are available to manage the QStar Software. The view pane is on the right side and shows information and functions of each item. In addition, the GUI now supports Multinational languages. The current languages supported are English, Japanese, Russian, German, Chinese, Dutch and Italian.

Privileged Users (UNIX Option) Usually only the System Administrator can run QStar commands because of their administrative capabilities. QStar creates a special option that, if required, allows non-root users to run QStar commands. For more detailed information, please refer to Chapter 3 - Installing and Configuring QStar Software in this manual.

Online Help Manual Pages The QStar Software for the Windows platforms contains context-sensitive help links that provide instructional help and examples. The System Administrator can access the QStar Manual by selecting the bookshelf icon on the far right of the QStar Administration Interface. Alternatively, the manual can be reached from the Start Button as well. The QStar Software for the UNIX platforms creates the /opt/QStar/man directory. In this directory, QStar places all of the Manual pages for the QStar commands. These pages explain the syntax and show some examples of the QStar commands to help the System Administrator. Adding this path to the Administrator's default Manual pages path (MANPATH environment variable) will make all QStar Man pages accessible to the System Administrator.

of 20

Remote Administration The QStar Administration Interface (Windows) can be used with any 2000/2003/2008/XP/Vista client machine to remote administer, configure and manage any other server (Windows or UNIX) that has the QStar software installed on it located on the network. The System Administrator simply copies the admin.exe file from c:\qstar\bin to the desktop of the client machine to be used as the remote manager. Executing the qstar.exe will open a Window called “Browse for Computer”, select the computer to administrate and the QStar Administration Interface will open on the windows remote client machine. The majority of the QStar Software functionality is available from a remote host using the GUI. The QStar Software also has in depth command line utilities that may be used to manage the QStar Software with full functionality. All of the command line utilities must be used with the exclusive “-H” flag to signify what Host the command is being directed to. To remote administer the QStar Software from command line copy the c:\qstar\bin and its contents to the c:\qstar\bin of the remote client machine.

VL Scheduler The QStar Software contains an event scheduler for scheduling certain processes. Scheduling of events allows the Software to be used to its full potential, notifying the System Administrator of low availability of media and delaying system intensive processes to be run at off peak times. The VL Scheduler can be used to initiate archiving from caches independently on a per Integral Volume basis and run batch or single media erases as well as Copy Media requests. It can also be used to schedule more time consuming tasks out of peak hours such as data Compaction on Integral Volume sets and bulk recording of CD/DVD-R media.

No Media Option The QStar Software can be configured to create an Integral Volume set with No Media, this allows data to be written to a cache as normal, but the data will not be archived and therefore not secured. A library or standalone drive can be added at a later date, and then the media can be added to the Integral Volume set and the data synchronized from the cache to the media.

of 20

DEVICE MANAGER COMPONENTS The term “device” refers to hardware such as standalone drives and library subsystems. QStar Software can manage one or many standalone drives and library devices on the same system. These devices can use Optical, Tape, or RDX media. To manage the device(s), QStar Software has three components: QStar “SCSI” Manager The “QSCSI” commands are the low-level SCSI drivers and are used to provide an interface for performing any direct SCSI device diagnostics, independent of the QStar drivers. These commands allow viewing of device profiles, inquiry strings, capacities of media, defined vendors, sense log information and other data from devices.

Library Manager The JB driver, through the “jbcmd or jb(UNIX)” commands, manages the storage library called historically jukebox. The JB module performs various operations with the library and its elements (shelves, drives, carriers, and mailslots). The commands can move media between elements as follows: jbcmd load (jbload) move a medium from the shelf to the drive jbcmd unload (jbunload) move a medium from the drive back to the shelf jbcmd flip (jbflip) invert a medium in the drive jbcmd export (jbexport) move a medium from the shelf or drive to the mailslot jbcmd import (jbimport) move a medium from the mailslot to the shelf. An application can control the online/offline status of the elements as well as the library time control parameters through API calls. View Store Library management software provides a complete application transparent interface to libraries, scheduling the insertion of particular media into a drive, based on demand for that volume.

Library Statistics QStar Software provides statistics for the elements within the library. These statistics allow the System Administrator to monitor for potential problems with the media and drives within the library. This allows problems to be rectified before they become too serious. There are also statistics for media loads per shelf/surface and per drive. If the library is full and media needs to be taken offline, these statistics will identify the less frequently accessed media. Additionally the statistics show the number of recovered errors per surface/drive/carrier, the number of occasions when a shelf/drive has been marked as ‘bad’ and the number of primary and secondary defect blocks on the DVD-RAM and Optical (MO/UDO/PDD/Blu-ray) surface. The Statistics view pane or the jbcmd statistics (jbstatistics) command line allows library statistic information to be printed or cleared.

of 20

MEDIA MANAGER COMPONENTS

QStar “Volume Librarian” Database The “VLcmd or VL )” commands allow the system administrator to configure the QStar database named Volume Librarian (VL). QStar’s Volume Librarian module is responsible for managing all archival media known to QStar, referred to as the media library. The Volume Librarian knows the location (physical and logical) and status of every archival medium, whether available online in a library or offline in a storage facility. Its capabilities eliminate any errors that may occur during manual volume management, while increasing productivity and performance. The QStar Volume Librarian performs many different tasks including erasing, media initialization, export/import from the storage devices, automatic electronic labeling, partitioning of the library, dynamic media allocation and compaction.

Bar Code Support QStar supports most major manufacturer’s implementation of Bar Code for media management, this allows improved handling for offline media and disaster recovery. In large-scale installations, media can be scanned in seconds for fast and efficient media tracking. Media can be tracked by a user defined label, or its Bar Code information, whether inside or outside the library.

Online Media Management For online media, the QStar Software automatically manages all storage media allocation and movement without operator intervention.

Dated Mount Dated Mount has the ability to mount an Integral Volume set, as read only, to a previous date and time. This feature is specific to the SDF / TDO file system. Dated Mount allows multiple simultaneous mounts on different dates and times, while the production mount continues to satisfy user requests. This allows the System Administrator to recover a previous version of a file or recover a file that has been deleted from the file system. Please refer to the Chapter 6 - The Migration Manager for more details.

Offline Media Management The offline media management provides virtually unlimited storage capacity by managing media outside of the storage device. For requests that require offline archival media access, the operator is prompted to retrieve the storage media from its storage location and insert it into the QStar configured device.

Data Compaction The Data Compaction utility is available for use with the SDF / TDO file systems, and is used for migrating live data from one piece of media to the current write surface of the Integral Volume set. The Data Compaction feature lets the operator fully reclaim media blocks after modifying or removing files on rewritable Optical media or Tape. This feature is managed under the control of the VL database. This feature is available on all Integral Volume sets, or just selected ones. Once a piece of media has been compacted and erased, the System Administrator has the option of adding the erased media to the same Integral Volume set or removing it from the Integral Volume set entirely.

of 20

Simulated Media Libraries The QStar Software can create Simulated Libraries. The Simulated Library configuration extends the ability of the QStar Software to mount an Integral Volume set utilizing magnetic disk space (RAID, Centera, SAN or hard drive) as simulated media. This configuration allows the use of physical disk space available on a hard drive to be used as media for an Integral Volume set. The hard drive may be partitioned into simulated virtual shelves and allows full use of import and export commands. The media may be manually configured to any size, or pre-configured media types such as UDO or Blu-ray. Integral Volume sets can then be created with any media configuration QStar supports, such as SDF / TDO. The Simulated Libraries configuration may be useful for demonstrating or integration testing with the QStar product or API when a library is not available. It is possible to configure a conventional library, with media such as Tape or Optical in conjunction with a Simulated Library and mirror the data between the two devices. For this, configure the Simulated Library media must be the same capacity and type as the media in the conventional library containing real media, then using the Data Director product and QStar’s SDF / TDO file system, mirror the data between the Simulated Media Library (on hard disk) and an Optical or Tape Library. This configuration allows real time mirroring between a hard disk and an optical or tape library.

VL Copy Media The QStar Software can manually or automatically execute a duplication process of the media that has been completely written. With a properly configured Integral Volume set, the Automatic Copy Media command will run every time the Integral Volume set reaches the point of dynamically allocating another piece of media to the Integral Volume set. With the VL Copy Media the source and destination media may be selected and copied at the System Administrators convenience. The copied media is an exact duplicate of the original media in the Integral Volume set. If a media is damaged, the copied media can be used to replace the damaged media. For more information on how to enable the VL Copy Media, please refer to Chapter 5 - The Volume Librarian in this manual.

VL Cross Copy Mirror Media The Copy Media supports copy of the media within the mirror configuration (SDF / TDO file system). This new feature will allow the System Administrator to recreate any lost or damaged primary or secondary mirror media simply by using the Copy Media utility or vlcmd copy (vlcopy) command. The copied media is identical to the original with the exception of the Set Identifier written at the beginning of the media, allowing it to be added to the mirror set.

VL Copy Using Publisher Devices QStar Software is capable of interacting with different types of publisher/duplicator devices. In the Windows and Linux versions a new QStar daemon will start if the software is configured to work with a publisher device. The daemon, through the publisher’s proprietary SDK library, is responsible for the communication between QStar and the publisher device. Using a simulated DVD or BD library with a spanning UDF Integral Volume set, it is possible to select the option of “Copy Media using Publisher”. Once the virtual UDF media is full, it is automatically sent to the publisher to create single or multiple copies of the media for offline storage.

of 20

MIGRATION MANAGER COMPONENTS

Migration Manager Migration is the movement of data between the magnetic disk cache partition and the archival media. The Migration Manager was designed to provide a view of a collection of diverse types of storage media. This includes magnetic disks, RAID, Optical, CD, DVD, Blu-ray, RDX, Tape drives and libraries. The job of the Migration Manager is to combine all of these technologies into a Virtual File System called an Integral Volume set. An Integral Volume set looks and feels to the user like a standard magnetic disk. This means that all standard applications, including network-based applications, can work with the Integral Volume set without modification and in the same manner that they would work with a normal magnetic disk.

Cache QStar Software uses server magnetic disk to temporarily store files to improve system performance. Caching provides the ability to place frequently accessed files on magnetic disk or RAID for quicker access. Different configurations of caching and cache logic provide instant access to the most recent and most active data without delays or a need for special commands.

Cache Enhancements The cache (Magnetic Cache File System) has been completely redesigned. The format of the cache now allows movement of the cache files between different operating systems and the cache formatter is no longer needed. The limitation of the cache per Integral Volume set size of 500 GB has been removed and better system resource utilization has been made. Multi threading has been enhanced, increasing the performance of Read/Write operations. A new mmcmd admin (mmadmin) command allows the ability to easily save all primary pages from the cache in case of disaster recovery.

File Migration File Migration is defined as the movement of data from and to the disk cache from and to an archive storage medium. This includes archiving files to the secondary storage media and replicating files back to the magnetic cache to service read requests. In the case of archiving data in an Integral Volume set from the cache, there are several archiving policies that can be utilized to maximize the efficiency of the archiving process. Automatic data migration in the Integral Volume set, or demand archiving forces an archiving cycle when a pre-arranged watermark, High Primary Capacity, is reached. Archiving can also be started by the System Administrator at any given time or scheduled in a timed interval using the VL Scheduler.

Transaction Logging Cache The magnetic cache is implemented using transaction-logging technology. This ensures the highest level of reliability in case of a system failure. Recovery of the cache requires the flushing of the transaction log. This takes place automatically at the next mount of the Integral Volume set after an unclean unmount.

Read Only Grace Period The QStar Software has a feature to allow data to be stored for a Grace Period before it is set to read only. A file may be modified, providing the user has sufficient privilege, until the Grace Period has expired, it is then marked as read only, this feature goes further than the standard UNIX, or Windows read only flag, as even the System Administrator cannot remove the read only flag for files, the only way to overcome this, is to remove the Grace Period option. Enabling this feature provides a WORM file system, even with rewritable media ideal for true archiving applications. This feature is configurable on an Integral Volume set basis and can be set by seconds, minutes, hours, days and years. Please refer to the Chapter 6 - The Migration Manager for more details.

of 20

Retention Period The Retention Period feature can be used alone or in conjunction with the Grace Period feature. Both Grace Period and Retention Period start from the last modification time. The Retention period specifies a file can be removed only once the Retention period has expired. The benefit to this feature is the ability to lock a file to read only status for the time the file is required to remain available within corporate guidelines. This feature goes further than the standard UNIX, or Windows read only flag, as even the System Administrator cannot remove the read only flag for files under Retention Period management. Enabling this feature provides a WORM file system, even with rewritable media ideal for corporate data archiving compliance requirement. Once a file has reached a point in time after the Retention Period, the file may then be modified or deleted from the file system. If both the Retention and Grace Periods are specified, a file can only be modified or deleted either before the Grace Period begins or after the Retention Period expires. This feature is configurable on an Integral Volume set basis and can be set by seconds, minutes, hours, days and years. Please refer to the vlcmd cache (vlcache) command in Chapter 9 - Command Reference for more details.

Write Once and Deny Rename The Write Once feature provides a WORM file system, even with rewritable media, which is ideal for corporate data archiving compliance requirement. Working differently from Grace Period, once a file is written in the file system; the overwrite, remove and set size operations are prohibited. A file can only be appended and renamed. This option will be ignored if is used in conjunction with Grace Period. If the Deny Rename option is specified with the Write Once option, the renaming operation is also prohibited.

NFS Mount This option allows mounting a QStar file system from a Windows platform to a UNIX platform via NFS. With this option, there is no third party software required to mount the QStar file system from Windows to a UNIX platform. With this added functionality, System Administrators will have greater flexibility in managing and integrating the QStar Software. Please refer to the Chapter 6 - The Migration Manager for more details.

Virtual Disk QStar Software consolidates all of the physical mass storage subsystems on a network-magnetic disk, Optical, CD-ROM, DVD-ROM, DVD-RAM or Tape - into a single, hierarchically managed resource, or Virtual Disk, treated as one logical entity. Using QStar’s caching technology, the most recently used data is available on the magnetic disk, providing fast access for users. Less recently used data is stored on archival media, via the Volume Librarian (VL) and is automatically moved to the magnetic disk if a user accesses it. This is a function of the Migration Manager. The moving of data between the magnetic disk and the archival media is transparent to end-users. QStar Software’s automatic storage management provides the benefit of virtually unlimited storage capacity without sacrificing access time to critical data.

of 20

DIAGNOSTIC COMPONENTS QStar Software provides different diagnostic components that can help the System Administrator monitor events, warnings and errors within the system.

Syslog View Pane or QStar‘s Syslog File In UNIX platform the QStar Software redirects any warning messages and main errors to the system console window. In addition, the QStar Software places its own log file called syslog into the /opt/QStar/log directory. In the Windows platform the QStar’s syslog file is placed into the c:\qstar\log directory and is visible in the QStar Administration Interface from the Syslog view pane. The QStar’s syslog file contains a chronological list of the events performed by the QStar Software and any system errors that occurred. Error and alert messages help to quickly identify and solve potential problems that might otherwise become critical problems if ignored or unnoticed.

SCSI Log View Pane or Qscsi_log Command The SCSI log view pane or the qscsicmd log (qscsi_log) command is a useful tool for detecting and diagnosing hardware errors. There may be occasions, under instruction from QStar Technical Support, that a SCSI log (scsi_log) file will need to be generated. The main hardware errors are displayed in the Syslog view pane or QStar’s syslog file as well, but the SCSI log provides a more detailed reporting for error tracking. When initiated, the QStar Software places a scsi_log file into the c:\qstar\log (Windows) or /opt/QStar/log (UNIX) directory where it will sequentially collect all the SCSI commands sent to the devices as well as the response back from the SCSI devices.

Console View Pane or Vlconsole Command The Console view pane or the vlcmd console (vlconsole) command prints a list of requests for manual assistance. The System Administrator can cancel a particular request, or remove requests from the list upon completion. Requests might include Integral Volume sets that need another piece of media added to the library or for offline media to be reinserted into the storage device to satisfy a read request.

E-Mail Notification The System Administrator can receive e-mail notification about abnormal events in the QStar software. An abnormal event can be, for example, a drive/library failure, an unrecoverable write error, a request for additional medium (no more space in the Integral Volume set), a request for medium that is currently offline. For more detailed information, please refer to Chapter 3 -Installing and Configuring QStar Software in this manual.

of 20

FILE SYSTEMS A File System is an interface for saving and retrieving files on storage media. The file system controls all aspects of media management, including directory/file structures, data layout, and data transfers. The file system allows data to be written out to the storage device in the file format that is acceptable to the application. QStar Software supports different types of standard file systems such as UFS, NTFS, FAT, UDF, LTFS and ISO. In addition, QStar Software supports two file system types that have data layouts suitable to the media QStar controls. These appear as standard file systems and give optimal performance for the storage and retrieval of data. QStar media format manager stores information about the data on the surface of the media, thus providing the template for the data written to the archival media. All archival media sets are self-contained, with file directory information, data, and indexes on the same Optical media, DVD-RAM or Tape. The volume format is optimized to ensure maximum performance and transportability between Optical, DVD-RAM or Tape libraries and file servers. The benefits of QStar formatted media include: • Transportability. - Media format easily moves media from one host system to another, regardless of the manufacturer. Thus, QStar’s media format manager protects the company’s investment in current hardware and allows access to critical data using other manufacturers’ products. • Flexibility. - Media format describes the contents of a single archival media allowing it to be used as part of a logical group, or media set. As part of a set, file and directory information is not restricted to a single piece of media; it may span several platters or tapes, giving contiguous space for large files. • Disaster recovery. - Making all archival media self-contained provides the means for disaster prevention and recovery. Any magnetic disk cache in the storage hierarchy can be completely rebuilt from the archival media, thus preventing catastrophic data loss. QStar stores file databases on a stacking file system. The first time a file is written to storage, it creates a baseline copy of the file. Subsequent changes to the file only cover the portions of the file that have been modified. The original file and each subsequent change are simply overlaid by more recent file segments. This method provides true incremental changes to the file without consuming excessive storage space. Similarly, changes made to directories are also stacked. Therefore, if a user removes a file, the directory is simply rewritten without the name of the deleted file. The file, however, still exists physically on the media. The QStar file systems are as follows:

SDF (Standard Data Format) This file system can be used for (MO/UDO/PDD/Blu-Ray) Optical and DVD-RAM devices to manage data storage and retrieval on WORM and rewriteable (MO/UDO/PDD/ Blu-Ray) Optical and DVD-RAM media. SDF is available on both UNIX and Windows platforms. Files are stored contiguously from the beginning to the end of each piece of media, with single-seek read and write access. This file system also supports SCSI Tape devices, specifically, Digital Linear Tape (DLT), SDLT, AIT, SAIT and LTO. The files are stored contiguously from the beginning to the end of each tape. The SDF file system is best suited for applications that will generate relatively small sized files.

of 20

Shredding support for UDO Compliance WORM media and Rewritable Optical media has been added. The support is available with ASM and Data Director (Mirroring) configurations. A new approach of saving the SDF database has been created, allowing the SDF database to be saved to a dedicated, separate media. The System Administrator can still use the old approach, which stores the SDF database to the beginning of each media. In addition the SDF database can be stored on Hard Disk as the primary location or as a mirror location if the primary location is the media. The database save procedure is triggered during rollover of media or can be initiated per GB of data written in the file system. This new approach allows the user to have two different threads in the SDF migrator, one for writing data and one for saving the database in two different media, removing the delay of archiving of data during the saving of the database. This feature is available also on Mirroring configurations where two different Hot Sync procedures have been developed. One called “Off Line Asynchronous Hot Sync” that is used to synchronize Database Media and all non current write surfaces and one called “On Line Synchronous Hot Sync” that is used to synchronize the current write surface, this allows Hot Sync to run in parallel with read/write operations.

UDF (Universal Disk Format) This file system can be used to manage data storage and retrieval on WORM and rewriteable (MO/UDO/PDD/Blu-Ray) Optical or DVD media. UDF is available on both UNIX and Windows platforms. Files are stored contiguously from the beginning to the end of each piece of media, with single-seek read and write access. QStar Software supports UDF Version 1.2 in read only mode and fully supports UDF Version 1.50, 2.00 and 2.01. UDF file system supports the three following Interchange Levels:

• Single-volume: Single surface file system for standalone drive

• Automount: Single surface file system where each surface is seen within a single volume as a separate directory

• Spanning: All media are aggregate as large file system

The following new UDF Versions and file system have been supported:

• Version 2.5

• Version 2.6

• Plasmon UDF

• ISO 9660 File System

Note: CD File System (ISO 9660 File System) has been removed and the support for the ISO 9660 standard with Rock Ridge and Microsoft extensions has been incorporated in the UDF file system. ISO and UDF media can coexist in the same file system using Automout Intechange Level. The UDF file system also supports the shredding operation offered with UDO Compliance WORM media. A new version of the UDF spanning database has been introduced for spanning configurations that also contain directory entries. This modification requires less access to the media when a user is browsing the file system and provides a faster mount procedure in the case of rebuilding of the cache and media databases. The floc command is now supported on UDF and can be used to list the files on an individual media.

of 20

UVFS - Support for the Plasmon File Systems This file system supports WORM and rewriteable (MO/UDO) Optical, DVD-ROM and DVD-RAM media on Linux and Windows platforms. Using the UVFS file system QStar supports, Read Only access to the following three Plasmon file systems:

• PFS - A simplified version of UDF, based on an older UDF implementation by HP

• AFS-1 - Archive File System, specifically developed for WORM

• AFS-2 - Improved version on AFS-1, optimized for speed and media usage

The UVFS file system supports the following three Interchange Levels:

• Single-volume: Single surface file system for standalone drives

• Automount: Single surface file system where each surface has a different label and it is seen within a single volume as a separate directory

• Spanning: All media are aggregated as a large file system if the label name is identical on each media

AAFS - Support for the Archive Appliance Plasmon File System This file system supports WORM and rewriteable (UDO) Optical, on Linux and Windows platforms. Using the AAFS file system QStar supports, Read Only access to the Archive Appliance Plasmon File System.

TDO (Tape and Disk Object File System) The TDO migrator (introduced in version 6.0) is a high performance file system created to optimize the read/write operations for tape and optical disks. TDO is available on both UNIX and Windows platforms. Files are stored contiguously from the beginning to the end of each piece of media, with single-seek read and write access. The design of TDO has removed the majority of the bottlenecks that are inherent with other file systems for these types of media. TDO has been created in such a way that it supports SDF media in read-only mode and writes all new data to the TDO file system. This allows to convert an SDF Integral Volume set to an TDO Integral Volume set. The read operation (for TDO and SDF) is multi-thread, which allows different read requests to be satisfied at the same time. The TDO file system is best suited for applications that will generate relatively small or very large sized files. The support is available with ASM and Data Director (Mirroring) configurations.

of 20

LTFS (Linear Tape File System) This file system can be used to manage data storage and retrieval on Tape media. LTFS is available on both UNIX and Windows platforms. Files are stored contiguously from the beginning to the end of each piece of media, with single-seek read and write access. QStar Software fully supports LTFS Version 2.0, allowing media to be exported and read in stand-alone drives using LTFS drivers provided by various drive manufacturers. LTFS media created in stand-alone drives can also be imported into the QStar controlled tape library. LTFS file system supports the three following Interchange Levels:

• Direct-single-volume: Single media file system for standalone drive or library without QStar Magnetic Cache File System (MCFS). This Interchange Level provides direct access to the LTFS tape

• Single-volume: Single media file system for standalone drive

• Automount: Single media file system where each media is seen within a single volume as a separate directory

• Spanning: All media are automatically aggregated as large file system

of 20

MEDIA ORGANIZATION The number of storage media in a system can run into thousands. System configurations can range in size from a 1.3 GB personal archive systems to multi-petabyte storage solutions. QStar can configure the library(ies) to be seen as one or multiple Virtual Disks. This partitioning allows a multi-media library to be logically divided so that the library can appear as multiple standard virtual hard drives allocated to different applications. In addition, partitioning allows the user to predetermine where and when files are written. This allows data to be written to a specific set of media, thereby simplifying backup and optimizing performance. Creating ten partitions, each with one piece of media, is comparable to creating a single partition with ten pieces of media, each with its own directory. The main difference between these implementations is data organization. QStar offers configuration, media paths, and write paths in the virtual file system to provide the most flexible data organization available. When deciding between multiple partitions and/or media paths, consider the objective of the entire storage solution. QStar Software allows for both standalone drives and libraries in the following configuration of data set: Integral Volume (I.V.) Set Configuration Use the “vlcmd or vl (UNIX)” commands to create and manage an Optical, DVD, Blu-ray, Tape media set or Structured Storage Device (Centera, HCP, Cleversafe, Amplidata, OSM) as an Integral Volume set. This configuration requires a CACHE that manages the migration of the data between the storage media and the Hard Disk. This configuration is available with all file systems. The media used determines the file system needed. Note: For more detailed information please, refer to Chapter 7 - Media Configurations in this manual.

of 20

MAJOR SOFTWARE ENHANCENENT IN VERSION 5.1 Hitachi HCP Migrator (HCP)

Allows data to be migrated from the cache file system (CFS) to the Hitachi HCP device. Specific features were introduced to support this device

The file can be written in compatibility mode or as an extent Rename operation is implemented as a read/delete/write operation Support for retention periods in HCP Curl timeout raised to 8 min Without retention, extent is rewritten (does not create a new version) All communication and read/write operations with HCP uses the http interface exclusively Initial tenant support

AAFS Migrator (Archive Appliance Plasmon File System)

Implemented the new migrator, which allows reading of media written with the Archive Appliance file system from Plasmon. The AAFS migrator accesses the AA media in read only mode

Implemented all the commands to use this file system with the Integral Volume set Added offline medium support

Local Mount (Windows):

QStar ASM can be exported by using a NetBIOS name (mapped network drive) as in previous versions. In addition the Integral Volume can now be presented as a local drive letter. This feature allows the sharing of the Integral Volume set using the standard share tools provided by Windows

Cluster Migrator

The Cluster Migrator allows two (2) different Integral Volumes set to be added, using the same cache and mounts them using the same mount point. The first Integral Volume set added is always read only while the second Integral Volume set added is read and write; the file system directories are aggregated at the root level. The cluster migrator does not allow multiple directories with the same name at the root level. If this happens, only the read-write directory will be displayed. The Cluster Migrator’s features, allow for example, mounting an AAFS file system in Read Only (RO) and a QStar file system in Read Write (RW), giving the user the ability to have two file systems mounted but clustered together and accessible as one

Access Control List (ACL’s)

The introduction of CBFS as the Windows File System Interface (FSI) allows the mounting of the QStar file system as a local drive; it also allows the system administrator to store all ACL’s into the QStar Cache and the media file systems such as SDF or UDF

SCSI Subsystem

Major overhaul to the QStar SCSI subsystem to add support for USB, iSCSI, SATA, Parallel SCSI, Fibre and SAS devices. Most of the items listed will change their addresses when the system is restarted; the primary focus of the overhaul was to be able to regain control of these items without the user reconfiguring the devices as in the previous versions. Now the Software will automatically reconfigure the device for the user on QStar server restart

Added support for slow storage library support Mixed LTO tape drives and media support; allows distinguishing between LTO-1 through LTO-5 and properly

manage drives and media ensuring that the correct media will be placed into the correct drive BluSafe: Added Serial Port detection and other Mac Specific Serial Services BluSafe direct support Windows and

Mac

of 20

Copy Disk Utility - Multiple Incremental Copy

Implemented Multiple Incremental Copy (MiC) for SDF and UDF file systems. This new feature allows two or more copies of the media to be created incrementally

Administration GUI (Windows)

Updated Russian and Italian localizations Added support of Chinese simplified localization Added support of Dutch localization

WEB GUI

Linux Apple (MAC) Added localization support

MAC

OSX (10.5) with CLI and Web GUI management interface Added checks for different Mac versions, updated Darwin; Definitions for proper library locations Porting for OSX (10.6)

Generic job scheduler

Allows configuring any event in the schedule i.e., TMT intervals

Added option for real and simulated storage libraries in the same Integral Volume set

File pre-fetch support in asynchronous mode Allows pre-fetching of data with real time access to the pre-fetched data, meanwhile continuing to allow full

access to the file system Mirroring SDF File System (Data Director)

Expanded vlstartmirr command in order to compare and generate audit report between primary and mirror media. In addition can be used to synchronize primary/mirror media

of 20

MAJOR SOFTWARE ENHANCENENT IN VERSION 6.0 Magnetic Cache File System (MCFS)

Possibility to calculate checksum of the file on fly and store such information in the stream of the file in the cache and in the back-end (archive) storage

Replication Migrator (RPL)

Allows the replication of data between different types of media and storage at the file system level. This is accomplished by inserting itself between the cache file system (CFS) and up to four different migrators, such as SDF, UDF, TDO, LTFS, Object Storage and GFS. The replication migrator includes a re-synchronization feature in case of failure of one of the replicas

Local Mount (Windows):

QStar ASM cannot be exported by using a NetBIOS name (mapped network drive) as in previous versions. The option to use NetBIOS can be enabled only upon request with a special procedure followed by QStar Support personnel. Starting from this version the Integral Volume can be presented only as a local drive letter. This feature allows the sharing of the Integral Volume set using the standard share tools provided by Windows

QStar Structured Storage Devices (QSSD)

Allows support for HCP, QStar OSM (Object Storage Manager), Amplidata, Cleversafe and GFS or non-SCSI device subsystems

Implemented qssddefine, qssdrefresh, qssdlist, qssdrename and qssddel commands

Hitachi HCP Migrator (HCP) Provides CIFS / NFS connection Full tenant support

Amplidata Migrator (Ampl)

Provides CIFS / NFS connection

Cleversafe Migrator (Cloud) Provides CIFS / NFS connection

Generic File System (GFS)

GFS is any file system that is available on the server i.e., NTFS, EXT3, EXT4 and Solaris. The GFS migrator allows migrating data to any of the generic file systems on the server. This is achieved by creating an Integral Volume set and assigning one of the generic file systems as the “media” for the Integral Volume set. The most common application of GFS would be to use it with the Replication Migrator (RPL)

Tape and Disk Object file system and Migrator (TDO)

The TDO migrator is a high performance file system created to optimize the read/write operations for tape and optical disks. The design of TDO has removed the majority of the bottlenecks that are inherent with other file systems for these types of media. TDO has been created in such a way that it supports SDF media in read-only mode and writes all new data to the TDO file system

The read operation (for TDO and SDF) is made using a different thread, which allows different read requests to be satisfied at the same time

Added vlcopy and vlcmp commands to copy and compare TDO media Created SDF to TDO database conversion Added sync statistics Added support for stat-fs

of 20

TDO Mirroring

Extends the functionality of TDO to provide mirrored writes (if resources are available) Provide same functionality as in previous SDF implementation, to mirror data between TDO media either using

two drives in the same library or between two libraries. Extended the previous mirror limit of two pieces of media in the mirror to offer a maximum of four mirrored

copies. Mirrors can be between up to four drives in one library, single drives in up to four libraries or two drives in two libraries.

TDO can also be used to mirror data between real media based libraries and simulated media on disk

Linear Tape File System and Migrator (LTFS) Linear Tape File System (LTFS) refers to both the format of data recorded on magnetic tape media and the

implementation of specific software that uses this data format to provide a file system interface to data stored on magnetic tape. The Linear Tape File System format is a self-describing tape format developed by IBM to address tape archive requirements. The LTFS Format specification, which was adopted by the LTO Technology Provider Companies, defines the organization of data and metadata on tape - files stored in hierarchical directory structure. Data tapes written in the LTFS Format can be used independently of any external database or storage system allowing direct access to file content data and file metadata. This format makes it possible to implement software that presents a standard file system view of the data stored in the tape media. This file system view makes accessing files stored on the LTFS formatted media similar to accessing files stored on other forms of storage media such as disk or removable flash drives. The Linear Tape File System format is an open description of the layout of data-structures stored on a sequential-access media. These data-structures hold the file content data and associated file metadata. Data media, such as LTO data tape, written using this format can be exchanged between systems that understand the Linear Tape File System format. Software systems that understand the format can provide users with a file system view of the media. Software systems may alternatively understand the format only to the degree that allows the system to read data from the media, or produce a tape that can be accepted by other systems that implement the Linear Tape File System format. The file system are supported in 4 different mode described in previous FILE SYSTEM session.

Object Storage Management (OSM) Migrator

This migrator allows data to be migrated from a QStar cache to the OSM product from QStar. Crypto Server - Encryption support

Added licensing support for crypto functions Added support for card removal/insertion control Added detached file verification functionality Added sha type verification and detailed error processing Added support for expired certificates SmartCard and Certificates pages functionality updates Added key delete functionality Added crypto backup functionality Changed signed output file protection mode Added log messages when signing files Verify that certificate is still valid before signing Added certificate extended key print Added key usage for self signed certificate creation Added support for card certificate print Added -f option for crptcmd info command to print selected certificate Added support for certificate creation Added certificate information print in XML format Time Stamp request converted to curl. Number of TS availability request hidden from GUI (as this is very

customer-specific) Smart card info added to the cache Crypto stamp from crypto stream (if any) is used for signing

of 20

Crypto Server – Digital signature

Implemented Digital Signature for UDF single volume set Check existence of a signature file before creating it Added code to support digital signature using qcrypto server

Administration GUI (Windows)

Updated Russian and Italian localizations Added support of Chinese simplified localization Added support of Dutch localization

File pre-fetch support in asynchronous mode

Allows pre-fetching of data with real time access to the pre-fetched data, meanwhile continuing to allow full access to the file system

of 42

This chapter describes how to get the system up and running.

Installing the software is as simple as placing the QStar CD in the CD-ROM, or running the executable, if installing from a downloaded copy . The Installation program guides the System Administrator through every step of the process.

Before installing the QStar Software, however, certain system components should be checked, such as the system, connection of storage devices and server configuration. This ensures that the QStar Software installation will run smoothly and minimizes the time it takes to set up the system.

This chapter contains instructions on how to verify these components, as well as information on completing the setup of the QStar Software. SYSTEM REQUIREMENTS ........................................................................................................2

Software Requirements .......................................................................................................2 QStar’s Recommendation for Optimization of the System .........................................................2

The Storage Devices.........................................................................................................3 Improving the Server’s Performance ...................................................................................3 Improving File System Performance....................................................................................3 Protecting Against Data Loss .............................................................................................4 Installation Considerations ................................................................................................5

Hardware and SCSI Requirements.........................................................................................6 QSTAR SOFTWARE DIRECTORIES ............................................................................................7 UPGRADING TO THE CURRENT VERSION OF QSTAR SOFTWARE...................................................8 INSTALLATION STEPS ............................................................................................................9

Diagram Installation Step: ...................................................................................................9 HARDWARE INSTALLATION AND SETUP OF DEVICES................................................................ 10 INSTALLING THE QSTAR SOFTWARE ...................................................................................... 11 SELECTING LANGUAGES....................................................................................................... 13 INSTALLING THE LICENSE KEY AND REGISTERING THE SOFTWARE............................................ 17

Demo License Key ............................................................................................................ 18 Activate the Demo License Key ........................................................................................ 18

Permanent License Key...................................................................................................... 20 Activate the Permanent License Key ................................................................................. 21

SPECIFYING THE STORAGE DEVICE CONFIGURATION............................................................... 23 Hard Drive Simulated Library Configuration .......................................................................... 28 Centera Simulated Library Configuration .............................................................................. 32 Proxy Simulated Library Configuration ................................................................................. 36

POST INSTALLATION TEST.................................................................................................... 39 QSTAR SERVER PRIORITY..................................................................................................... 40 ADDING NEW STORAGE DEVICES.......................................................................................... 41 REMOVING QSTAR SOFTWARE .............................................................................................. 42

of 42

SYSTEM REQUIREMENTS The host computer must have the minimum configuration described below to install the QStar products. Note: The following applications are known to cause serious problems with the QStar Software or the Libraries attached to the Server that the QStar Software is installed on. Any Enterprise Management Software, such as Open File Manager (OFM) or F.A.S.T. may cause serious problems that are configured to: 1) Query the internal drives or changer assembly of the Library 2) Query and cache the QStar Software directories, or the QStar cache directories To avoid any issues with these applications QStar recommends reconfiguring the application not to monitor or cache any portion of the QStar Software or the devices it controls.

Software Requirements Listed below are the minimum system requirements for installing QStar Software on the host computer. Windows 2003/XP/Vista/2008/7

Xeon class PC (Minimum 2Ghz) Required

Memory At least 4 GB

Disk space for QStar Software on Hard Disk At least 100 MB

Service Pack 2 Windows XP

Service Pack 3 Windows 2003

SCSI/SAS host adapter supported by Windows Required Note: The storage devices should not be on the same adapter as a SCSI hard drive.

QStar’s Recommendation for Optimization of the System • QStar recommends a minimum of 16 GB of RAM on Windows based platforms

• Upgrading the memory as much as possible will provide faster data access

• To improve processing speed, use a processor that is faster than the minimum requirement

• Use a separate SCSI host adapter for the library

• Additional Hard Drive space on the main NTFS volume or additional NTFS volumes will provide better cache utilization

• Use fast disk storage systems (RAID with FC or SAS drives) if very fast ingestion is required Client Workstations mapping to a QStar Integral Volume set should have the following minimum configurations:

• Server 2000, XP Pro, Server 2003, Vista, 7, 2008

• PC with 4 GB of RAM

of 42

To achieve the best possible performance from Windows based platforms and the QStar Software, the following are suggested:

The Storage Devices

Selecting the Appropriate Hardware to Maximize Performance

One of the largest decisions to consider when setting up the QStar Software is which storage device(s) is best suited for the environment. The hardware configurations can be significantly different depending upon the storage needs of the enterprise. To determine which type of storage devices including the number of drives, number of shelves and media type will provide the best performance; a complete and thorough evaluation of the enterprise needs should be conducted. The number of users and the amount of data being accessed will determine the number of drives, shelves and type of media that will be required in the library to maintain optimum performance.

Improving the Server’s Performance

All of the following affect the performance of the Server the QStar Software is installed on:

• The amount of available RAM

• The size, speed (in RPMs and bus speed) and the number of hard drives plus RAID configuration

• The number of processors and their power

• The network cabling and configuration

Amount of Available RAM

Memory is the fastest and cheapest way to improve performance on the Server the QStar Software is installed on. Maximizing the RAM on the Server will significantly improve Windows based platforms and the QStar Software performance.

Number of Machine’s Processors

QStar Software can be installed on either single or multiple-processor machines. Using a multi-processor machine, the number of multiple tasks that can be performed at the same time is increased significantly. Using a multiple-processor machine for the QStar Software will greatly improve the migration performance.

Improving File System Performance

The following will affect the performance of the QStar file system:

• High and Low Primary capacities

• The total number of files per directory in the QStar file system

Setting the High Primary Capacity

The High Primary Capacity is set to 80% of the cache size by default. Lowering this setting can be beneficial when using a large cache or during periods of high volume transfers to the QStar file system. This will allow the data in the cache to be written to the archive media sooner, which will increase the available space in the cache for the new files.

of 42

Creating an efficient file system

How the file system is structured will have a significant effect on its performance. The sector size of the media verses the size of the files can significantly affect space utilization on the media. The layout of the directories and the number of files in any given directory are an important consideration when designing a file system. QStar recommends no more than 3000 files per directory to maintain optimum file system performance.

Expected Behaviors

Because the file system that QStar usually manages is removable and a multi-surfaced file system, there are some expected behaviors that need to be addressed when creating the file system.

Creating a directory structure on removable media that is extremely deep and has a small number of files and a small file size in each directory will offer poor space utilization on the media and should be avoided.

Exceeding the 3000 files on removable media per directory recommendation will cause degradation of performance to the file system. This decrease in performance will manifest itself when a user tries to browse the directory and will increase with the number of files in the directory. For example, with 5000 files in a directory the impact on the user will be slight. However, with 50,000 files in a directory the impact will be more significant and could have an effect on other users trying to access the file system. In extreme situations, this decrease in performance can cause extremely slow or no access to the mount point of the QStar file system.

The number of files in the directory structure will have the most impact in a disaster recovery situation or if the cache files have to be rebuilt. In this situation, the mount point may not be accessible for several hours depending on the number of files in the directory structure.

If direct access to a file by an application is used, the number of files in a directory can be increased and there will be no impact on performance under these circumstances. However, it must be understood that direct access will not remove degradation of performance when browsing the directory or during a disaster recovery situation.

Protecting Against Data Loss

QStar copies the data out to the media during the archiving process automatically based on the High Primary Capacity (HPC) value by default. To ensure that all data in the QStar file system is protected against system failure (including hard disk failure); QStar offers several utilities to protect the data from loss or corruption. Using one or more of these utilities is highly recommended.

Scheduled Archives

It is recommended that the System Administrator periodically archive data without waiting for the HPC to begin archiving. A daily archive is beneficial to most users who maintain a large cache with a defaulted HPC value. Archiving can be scheduled to start automatically every day using the QStar’s VL Scheduler.

Media Redundancy

QStar recommends the use of media redundancy for the Integral Volume sets (i.e. Copy Media), if the data is mission-critical. Recovery time after a disaster can be significantly reduced if media redundancy is used on the QStar Integral Volume set. However, further redundancy can be achieved utilizing QStar’s Data Director product in which all information is mirrored to an Identical Integral Volume set. In the event the primary server goes down, the primary servers can be “swapped” and the secondary mirror can become the primary file server in a matter of minutes.

Using Automated Copy Media to back up the Primary Media

The Copy Media feature creates an identical piece of media from the primary Integral Volume set. This capability takes away the potential of data becoming unrecoverable because of a damaged media and provides for an off-site media copy.

of 42

Installation Considerations

Before installing the QStar Software, it may be advantageous to consider the overall storage needs for the system.

It is advisable to make a cache size appropriate for daily usage.

Considerations for cache size are:

How much new data will be archived per day?

How much data will be requested from the library per day?

Some issues to consider include:

The total amount of files expected per directory inside of the QStar Integral Volume set, appropriate watermark levels and scheduling data archiving.

Some organizations have existing file storage systems, and may have already decided upon an optimum arrangement for the file server.

Sizing the Cache

A general rule for an Integral Volume’s cache size is, more is better. An Integral Volume’s cache size should be selected depending upon the system’s activity and required response time. The larger the Integral Volume cache, the faster the system performance, because there is a greater chance that the files being requested are already in the cache. For systems with large volumes of data, the cache should be sized to accommodate an entire day’s processing. This allows the users to work at full speed during the day, with the QStar Software performing time-costly migration at night. Each Integral Volume set must be sized separately. Calculating overhead space in addition to cache size will help determine the hardware requirements for the QStar file system. As a general rule of thumb, 1,000,000 files will require 500 Megabytes of hard drive space over and above the cache size for metadata overhead. However, this rule should only be used for an approximate estimate of required drive size.

of 42

Hardware and SCSI Requirements A library or standalone drive that will be connected to the host computer via the SCSI (Small Computer System Interface) bus must comply with some requirements. Every device attached to the SCSI bus must be assigned a unique SCSI ID or “address”. Please refer to the SCSI host bus adapters’ manufacturer’s recommendation for maximum cable lengths. The combined internal and external length of cables from the host computer to the end of the SCSI bus must be determined. This combined length must not be exceeded. As an example the combined length of all SCSI cables, including the integration of the QStar subsystem, must not exceed 6 meters (approximately 18 feet) for a single-ended SCSI bus. If the cable exceeds 6 meters, operational problems such as device errors or system failures could occur. QStar recommends that the length of the SCSI cable from the host computer to the library or standalone drive be no longer than 3 meters. The operating environment (noise and/or high voltage power supply) could also have an effect on the optimal cable length. Ensure that the SCSI bus is terminated correctly using an active terminator. The number of SCSI IDs that will be needed for the QStar subsystem depends on the type of device that will be installed.

Be sure to keep track of which drive number in the library corresponds with each SCSI ID.

Once it has been determined what devices are currently attached to the SCSI bus, then decide which available SCSI IDs will be used for the library or standalone drive.

In addition, before beginning the installation, make sure the following are available:

• The hardware manual for the particular library

• SCSI Cable(s) and active terminator for connecting the library or standalone drive

• QStar Software installation CD-ROM or downloaded software

of 42

QSTAR SOFTWARE DIRECTORIES

QStar installs its Software by default in the c:\qstar directory. In the c:\qstar directory, the following files and directories will be listed:

backup This directory contains internal backups of the Integral Volume set database.

bin This directory contains commands for managing and controlling the QStar Software. These commands can be used at the MS-DOS command window as well as being included in Batch files.

crpt This directory contains commands for managing and controlling the encryption Software.

dev This directory contains internal descriptions of the QStar controlled devices.

doc This directory contains the API html documentation.

emg This directory contain configuration files used with OSM/TDO/Amplidata/Cleversafe Migrator.

include This directory contains the QStar Include files.

install This directory contains the list of configured devices as well as the classes configuration file.

jb This directory contains all of the configuration and database files used by the QStar Device Manager to maintain and control the configured libraries.

lib This directory contains the QStar Library files.

license This directory includes the license file.

log This directory contains the various QStar log files. The most important file is the syslog text file. If SCSI command logging is turned on then this directory will also contain the scsi_log text file.

mcfs This directory that contains the MCFS module - Front end caching.

qscsi This directory that contains the QSCSI module - Low level drivers.

sdf This directory that contains the SDF module - Standard Data Format file system.

svc This directory contains the QStar system services and drivers which are started automatically when the system is booted.

tmp Temporary directory sometimes used by QStar Software.

vl This directory maintains the list of defined sets and the state of each medium within the devices utilized for set allocation.

of 42

UPGRADING TO THE CURRENT VERSION OF QSTAR SOFTWARE To de-install the QStar Software in order to install an upgrade, or in preparation of moving to another host, follow the steps below:

1) Archive all data out of each Integral Volume’s cache. In the QStar Administration Interface, select Integral Volumes and next select Migration View. Select the Archive button to start the archiving. Do this for each Integral Volume set.

2) Unmount all Integral Volume sets. In the QStar Administration Interface, select Integral Volumes and next select the Volume Management. Select the Unmount button to unmount the Volumes. Do this for each Integral Volume set.

Note: For safety, QStar suggests saving the information of device and Integral Volume sets database by running from dos prompt the vlcmd lsdev device_name and vlcmd lsset -va commands and redirects the output into a file.

3) Stop the QStar Server. In the QStar Administration Interface, select QStar Server for version 4.x or select Server and next Status for version 5.x or and select the Stop button.

4) Remove the QStar Software from the computer. From the Start menu, select the QStar program group and select the Uninstall QStar Software. The machine will have to be rebooted to complete the de-installation.

5) Once the machine has restarted, in a Windows Explorer window, there are two options:

a) Remove the c:\qstar directory and any files in the old cache directory (c:\qstar is the default location for the QStar Software). This removes all database files for the Integral Volume sets and libraries configured under the previous installation.

b) Do not remove c:\qstar directory. This will allow the ability to restore all previous QStar database files for Integral Volume sets and libraries.

The format of the cache files in version 6.x are incompatible with the cache files for all 4.x and 5.x versions, so the System Administrator will be forced to mount all Integral Volume sets with clean cache after the upgrade. For DVD libraries after the uninstall procedure remove the file c:\qstar\jb\files\jb_param_*.

6) To install the new release of the QStar Software see the Installation Steps section on the next page.

INSTALLATION STEPS For a correct installation of QStar Software these steps must be followed in the order shown on the diagram below:

Diagram Installation Step:

Page 9 of 42

of 42

HARDWARE INSTALLATION AND SETUP OF DEVICES To install the storage libraries or standalone drive(s), follow these steps:

1) Shut down the system using the standard shut down procedure.

2) Reboot the system and read the list of the attached SCSI devices from boot screen and take note of the currently used SCSI target IDs.

3) Power off the system.

4) Select the appropriate SCSI target IDs from those that are available for each storage device that will be connected to the host. Set the SCSI IDs of the storage devices per the instructions in the hardware operator’s manual. Select any available number from target 0 through 6 on the SCSI bus for your storage devices.

For specific hardware information, consult the hardware manual that came with the library or standalone drive.

5) Attach each device to its appropriate SCSI controller(s) and attach a terminator to the last device on each SCSI bus. Power up all peripherals. Power up the server.

Verify the SCSI ID settings of the libraries or standalone drive(s) to ensure there are no conflicts with other devices on the same SCSI bus; use the SCSI Utility to verify target ID usage.

The system returns a list similar to the one seen in Step #2 above. This list should now also include the inquiry strings from the newly attached devices. Confirm that all devices seen in Step #2 are still visible. If any of the devices that were previously seen are not seen now, the device may have been set to an address already in use. In this case, recheck the results from Step #2 and start again. Also, be sure to confirm all SCSI cables and terminators are securely connected.

6) During the boot process, the operating system will configure the devices attached to the system.

of 42

INSTALLING THE QSTAR SOFTWARE This section demonstrates the QStar Software installation program. The installation program automatically sets up all necessary product directories and files. Before installing the QStar Software, the System Administrator needs to do the following:

• Disable the Microsoft Removable Storage services

• Disable any Antivirus Software and if re-enabled after the installation be sure that the QStar program and QStar Integral Volume Sets cache folders are excluded from antivirus check

• If QStar Software is going to be installed in any server where a different library management software vendor was previously used, it requires any existing library software/drivers be uninstalled. The System Administrator should contact the previous supplier for more specific un-installation instructions

To install the QStar Software, follow these steps:

1) Begin by inserting the CD-ROM into the drive. If Autorun is configured, a welcome screen should appear as the system recognizes the disk. If Autorun is not configured, select the Start menu button. Then select Run and type D:\autorun (D:\ being the CD-ROM drive). This process is the same for downloaded software.

2) Once the Installation menu appears, please select the Install QStar Software for Windows button to install the QStar Software. Select the Manuals and Documentations button to view the list of documents available on the CD-ROM.

3) After Choosing Install QStar Software or by manually running the Setup Program, select the appropriate language. When finished, select the OK button.

4) Select the Next button on the setup wizard windows to continue.

5) Review the license terms before installing QStar Software. Place a check in the check box to accept the terms of the agreement. The agreement must be accepted to install QStar Software. Select the Next button to continue. Otherwise select the Cancel button to exit the Setup program.

6) Personalize the Software by filling in the blanks. Select the Next button to continue.

7) Choose Install location. To install the QStar Software to the default location of C:\QStar, select the Next button. To install the QStar Software to a different folder or drive letter, select the Browse button and select the desired drive letter or folder name.

8) Select the required QStar product to be installed on the system.

The options are the following:

• QStar ASM (Full Storage Management Product)

• QStar Data Director (ASM + Mirroring Capabilities)

• QStar Archive Replicator (Synchronous file replicator)

After making the Software selection, select the Next button to continue, or select the Cancel button to leave the Setup program. 9) New USB and TCP/IP supported devices may conflict with RAID system.

Figure 3.1 Device Configuration

By default QStar will not check USB or TCP/IP device during the claiming procedure. If MO/UDO drive, USB device, BluSafe device and TCP/IP device will be used. Place a check mark in order to notify QStar to discover such type of device during claiming procedure.

Note: For TCP/IP library the System Administrator need to insert IP Address and Port value.

10) Select the type of installation. Typical, which is the default and recommended installation, will give full functionality of the QStar Software including the API support. Custom and Compact will not install API files and API documentation. After making the selection, select the Next button to continue. Select Publisher if the Software needs to work with any publisher device. Expand Publisher check box and then select the correct model of publisher device (available only with special releases).

11) Select the location for the QStar Software icons in the Program Folder. Create a location for the QStar Software by filling in the blanks or selecting the default location. Select the Next button to continue.

12) Mark the device(s) that are going to be controlled by the QStar Software and select the OK button.

In the Device Claiming Window, QStar will display all hard disks on the system this is because the operating system will report some types of optical drives as hard disk. However, QStar CANNOT control a real hard disk as a SCSI device. Configuring the QStar Software with the EMC Centera, Amplidata, HDS HCP, Cleversafe, Simulated Tape, or Simulated Disk there is no need to claim any devices. Do not mark any device(s) and select the OK button.

Figure 3.2 QStar Device Claiming

13) After the installation is complete, select Reboot now and select the Finish button.

Page 12 of 42

SELECTING LANGUAGES Once the QStar Software has been installed and the system has restarted, the following is required to select the languages of the QStar Administration Interface:

Starting QStar ASM Product

Figure 3.3 - Start Button - QStar ASM Software Product

Log on to the system as the Administrator.

Go to the Start button, then Programs, then QStar ASM.

Select QStar Administration Interface on LOCALHOST. Skip Figure 3.6.

Or select QStar Administration Interface, and go to Figure 3.6.

Starting QStar DDR Product

Figure 3.4 - Start Button - QStar Data Director Software Product


Go to the Start button, then Programs, then QStar DDR.



Page 13 of 42

Starting QStar Archive Replicator Product

Figure 3.5 - Start Button - QStar Archive Replicator Software Product


Go to the Start button, then Programs, then QStar Archive Replicator.



Page 14 of 42

In this window, expand the My Network Places and select the computer to administer.

Selecting the Cancel button will open the local host.

Figure 3.6 - Browse for Computer

Figure 3.7 - QStar Administration Interface

Once the computer is selected to administer, the QStar Administration Interface opens displaying information about QStar Version Number and the phone numbers to call for assistance or technical support. The same information can be found by selecting About QStar... under Help option.

By default the language of the QStar Administration Interface is the one specified during the installation procedure.

To change the language, select the Language selection in the menu bar. Once selected the QStar Administration Interface will close and open automatically with the new language.

Page 15 of 42

The new QStar Administration Interface consists of a window divided into two panes. The navigation pane in the left displays the category tree that shows the list of items that are available to manage QStar Software. The view pane in the right contains the details of the information, functions and options pertaining to these items.


Figure 3.9 - QStar Administration Interface. License Key is activated.

Selecting different items in the category tree, the information in the view pane changes.

Page 16 of 42

INSTALLING THE LICENSE KEY AND REGISTERING THE SOFTWARE

Figure 3.10 - License

To install the license keys, select License and call QStar Customer Support for guidance through the license key installation and to provide an activation key.

License provides all the information needed to obtain a Demo or Permanent License Key from QStar Customer Support Personnel.

When Accessing License for the first time an error message will be displayed notifying the System Administrator that the License Key is invalid because it is not entered yet.

The license information displayed before the Software is licensed contains the following:

• QStar version

• Platform

• Host ID

The Serial Number can be found on the license card or on the back of the CD case supplied with the Software.

Figure 3.11 - License

Page 17 of 42

Demo License Key

Figure 3.12 - Inserting the Demo License Key Information

The information that the System Administrator should provide to QStar Customer Support personnel for a Demo License key is the following:

• Company: * • Department: • Contact person: • Contact email: * • Contact phone: • QStar version: 6.0 * • License Type: Demo • Platform: * • Host ID: *

*: Mandatory information

The above information can be inserted into the Product Registration Form available on the distribution CD-ROM and faxed to +1-850-243-4234 (USA), +39-02-45101-745 (EUROPE) or your local QStar office.

If preferred, email to [email protected] or [email protected]. A Customer Support representative will email the License Key and any further instructions. A license request page is available on the QStar website, http://www.qstar.com/support/license-key-request-form/ Activate the Demo License Key The Demo license key is a file that will be sent to a specified email address. Depending on the version of Software, the file should be either copied to the c:\QStar\license folder or use the Activate Button. Once the license file is copied or uploaded, close and then re-open the Administration Interface to see the new license key information.

T

The Demo License Key will allow the use of all the QStar Products with any device for the time specified in the Expiration Date box. The maximum number of libraries that can be controlled by the QStar Software at the same time is 8.

The Serial Number for Demo license is not necessary and will be displayed as N/A (Not Available).

Note: In the example, the License type is changed to Demo and the

Figure 3.13 - Inserting the Demo License Key Information License Key is activated.

Page 18 of 42



http://www.qstar.com/support/license-key-request-form/


Figure 3.14 - Inserting the Demo License Key Information

If the Demo license expires, a red question mark symbol will appear in the Expiration date box and a pop up window will appear each time License is selected.

Note: In the example, the Demo License Key is expired.

If the library was already configured, to restart the QStar Server, select Status, in the view pane select the Start button and the server will restart, completing the library configuration.

If the library configuration is not already configured go to the “Specifying the Storage Device Configuration” section. Note: The Publisher Manager State information will be available only if QStar Software will be used with a publisher device.

Figure 3.15 - QStar Server (Restarting the Server)

Page 19 of 42

Permanent License Key

Figure 3.16 - Inserting the Permanent License Key Information

The information that the System Administrator should provide to QStar Customer Support personnel for a Permanent License key is the following:

• Company: * • Department: * • Contact person: * • Contact email: * • Contact phone: * • QStar version: 6.0 * • License Type: Permanent * • Platform: * • Serial number: The Serial

Number can be found on the license card or on the back of the CD case supplied with the Software. *

• Host ID: * • Permanent License

Information *

*: Mandatory information Permanent License Information is the following: 1. QStar Product Purchased:

• QStar ASM • Data Director: DDR1/DDR2/DDR3 • API (For API Support) • Digital Signature • Remote Copy • Duplicator Support • ASM-Lite Basic • ASM Lite optional features: • Copy media • Offline, magazine, media exchange • Compaction • Grace Retention period, Windows NFS

2. Library or Standalone Drive: • Number of Libraries or Standalone Drives • Real Device Type • Optical • Tape • CD/DVD • 12 inch Worm • UDO/PDD • BD (Blu-ray)

• Simulated Device Type • Centera/OSM/HCP/Amplidata/Cleversafe • Hard Drive

• Number of Shelves • Capacity (GB) (Only for Simulated Device Type)

The above information can be insert into the Product Registration Form available on the distribution CD-ROM and faxed to either +1-850-243-4234 (USA), +39-02-45101-745 (EUROPE) or your local QStar office. If preferred, email to [email protected] or [email protected]. A Customer Support representative will email the License Key and any further instructions. A license request page is available on the QStar website, http://www.qstar.com/support/license-key-request-form/

Page 20 of 42




Activate the Permanent License Key

The Permanent license key is a file that will be sent via email to the email specified, that must be copied on the c:\QStar\license folder. Once the license file is copied, close and re-open the Administration Interface to see the license key information.

Note: In the example, the License type is changed to Permanent and the License Key is activated for every item displayed on the License view pane.

In the example, the Permanent License Key for DDR3, Master3 products and for UDO library with 238GB, DVD library 200 GB and simulated Hard Disk library of 104GB is activated.

Figure 3.17 - Activating the Permanent License Key

Figure 3.18 - Inserting the Permanent License Key Information

In the example, the Permanent License Key for QStar ASM-Lite with Copy Media extension, API, Digital Signature, Publisher products and for Tape library with 150 GB and Blu-ray library 200 GB is activated.

Note: For a full QStar ASM license - “Activated” will be displayed.

Page 21 of 42

If the library was already configured, to restart the QStar Server, select Status, in the view pane select the Start button and the server will restart, completing the library configuration.

If the library configuration is not already configured, go to “Specifying the Storage Device Configuration” section. Note: The Publisher Manager State information will be available only if QStar Software will be used with a publisher device.

Figure 3.19 - QStar Server (Restarting the Server)

Page 22 of 42

SPECIFYING THE STORAGE DEVICE CONFIGURATION In the Once the QStar Software has been installed and the system has restarted, the following is required to configure the hardware:


Once the computer is selected to administer, the QStar Administration Interface opens displaying information about QStar Version Number and the phone numbers to call for assistance or technical support. Same information can be found selecting About QStar... under Help option.

To begin configuring the library, select Server and then Status.

Status provides information about the system and the QStar Software.

Ensure the QStar Server Status is installed.

If the QStar Server is running and all modules are accepting requests, stop the QStar Server by selecting the Stop button. When the Server has stopped proceed to the next step.

When ready, select Storage Libraries and then select Configuration. Note: The Publisher Manager State information will be available only if QStar Software will be used with a publisher device.

Figure 3.21 - Stopping the QStar Server

Page 23 of 42

Figure 3.22 - Library Configuration

If the library claimed during the installation procedure is on the list of the library that supports Automatic Device Configuration, the library will be automatically configured and named as JB0.

If a library with more than two SCSI buses is used, the automatic device configuration will add all drives from the first two buses in the correct order, the drives on the third bus must be checked and if required, added manually.

The System Administrator can assign the library a different name by selecting the Delete button and reconfiguring the library.

If everything is accepted, the device configuration can be considered complete and the system Administrator can proceed with the next step of the installation procedure.

If the library doesn’t support the Automatic Device Configuration, the library and drive information will not be displayed in Configuration.

The library can be added manually.

The configuration process does the following: • Installs device drivers • Creates device files • Configures the devices

Select the Add button to begin adding the device.


Page 24 of 42

Figure 3.24 - Adding a Library

All libraries connected to the system, which are available for configuration, will appear in this window.

By default, the library is named JB0; the library name can be changed by typing a new name on the Library Name box.

Select either the library or standalone drive by highlighting the device required to be configured and then select the Next button.

Note: In the example, a library will be configured.

If the library supports the Automatic Drive Configuration, the QStar Software will automatically configure all the drives belonging to the selected library and they will be displayed in the left window.

When all drives have been configured, select the Finish button. Note: The right window will be empty and there will be no question marks in the left window when all drives have been configured.

Figure 3.25 - Configuring the Drives

Page 25 of 42

Figure 3.26 - Configuring the Drives Manually

To configure the drives Manually, they must first be removed from the Configured Library Drives window and moved to the Available Drives window.

To move the drives, highlight the first drive and select the arrow in-between the two windows. Do this for each drive.

To reconfigure the drives, move them back to the Configured Library Drives list-box in the correct SCSI target order.

If no drives are present in the left windows this means that the device does not support Automatic Drive Configuration.

If this is true, configure the device manually.

All Drives which are available for configuration will appear in this window.

In the right window highlight the first drive and select the left arrow between the two windows. Do this for each drive.

Note: The drives must be selected in order. It is required to know which drive number in the library corresponds with each SCSI ID.

Figure 3.27 - Adding a Library

Page 26 of 42

Figure 3.28 - Configuring the Drives

The question mark will be replaced with a drive icon as the drive is configured.

Once all drives have been configured select the Finish button.

After selecting the Finish button, the Configuration view pane will contain the SCSI information for the library.

Note: Before using the QStar Software, a valid set of license keys must be installed for the specific QStar products used.

Figure 3.29 - Devices with Library Configured

Page 27 of 42

Hard Drive Simulated Library Configuration





By default, the library is named JB0; the library name can be changed by typing a new name on the Library Name box. The Hard Drive Simulated Library can be configured only if the QStar Server is running, if it is not running, a warning message will appear at the top saying that the QStar server must be started before continuing with the configuration.

Select the Hard Drive Simulated Library and then select the Next button.


Page 28 of 42


At the bottom of the window all configuration options for Hard Drive Simulated Library will appear.

Number Of Shelves: Choose the number of shelves that will be allocated to the Hard Drive Simulated Library.

Simulated Library Type drop box: Two options are available: Disk and Tape. Disk will configure the Simulated Library shelves as double or single sided media. Tape will configure the Simulated Library shelves as single sided media.

Directory Path: Select the directory on the system where the Simulated shelves will be created.

Note: The directory must have a sufficient amount of space to create the shelves. For example, if 100 shelves were chosen and each shelf is 1 gigabyte in size the specified directory must have at least 100 gigabytes of available space.

Enter the number of shelves in the Number Of Shelves text field.

From the drop box select Disk or Tape.

In this example a Disk type Simulated Library will be created.

Note: In this example a 100 shelf Hard Drive Simulated Library will be created.


Page 29 of 42


Select the Browse button to browse the system for the directory path where the simulated shelves will be created on the system.

Once all configuration options are chosen, select the Finish button to create the Hard Drive Simulated Library.


Page 30 of 42


After selecting the Finish button, the Configuration view pane will contain the information for the library, the Directory Path information will be displayed only if the QStar server running.

Page 31 of 42

Centera Simulated Library Configuration Prior to installing the Centera Simulated Library, the EMC Centera SDKs must be installed. Please refer to the installation instruction provide by EMC for installing the EMC Centera SDKs.

Figure 3.37 - Qcentera Command

The Centera Simulated Library must be configured by command line. From QStar Administration Interface main menu bar select Tools, then QStar DOS Prompt Commands.

Run the qcentera.exe command to configure the Centera options. The Figure shows an example of the qcentera.exe command. Please refer to QStar SML Simulated Media Library manual for more configuration options.

The qcentera.exe command has an exit code of 0. If there are errors running the qcentera.exe command, an error code will print to the screen.

To verify the qcentera.exe command options, run the following command:

qcentera.exe -c =

To start the qcentera daemon stop and restart the QStar Server.

Figure 3.38 - Qcentera Command

Page 32 of 42





By default, the library is named JB0; the library name can be changed by typing a new name on the Library Name box. The Centera Simulated Library can be configured only if the QStar Server is running, if it is not running a warning message will appear at the top saying that the QStar server must be started before continuing with the configuration.

Select the Centera Simulated Library and then select the Next button.


Page 33 of 42


At the bottom of the window all configuration options for Centera Simulated Library will appear.

Number Of Shelves: Choose the number of shelves that will be allocated to the Centera Simulated Library.

Centera Simulated Library Type drop box: Two options are available: Disk and Tape. Disk will configure the Simulated Library shelves as double sided media. Tape will configure the Simulated Library shelves as single sided media.


From the drop box select Disk or Tape.

In this example a Disk type Simulated Library will be created. Note: In this example a 10 shelf Centera Simulated Library will be created.


Page 34 of 42

Figure 3.43 - Library Configurations

Once all configuration options are chosen, select the Finish button to create the Centera Simulated Library.

After selecting the Finish button, the Configuration view pane will contain the information for the library.

The Centera Simulated Library will be available only if qcentera daemon is running.

To start the qcentera daemon stop and restart the QStar Server.

.


Page 35 of 42

Proxy Simulated Library Configuration


The configuration process does the following:

• Installs device drivers • Creates device files • Configures the devices



By default, the library is named JB0; the library name can be changed by typing a new name on the Library Name box. The Proxy Simulated Library can be configured only if the QStar Server is running, if it is not running a warning message will appear at the top saying that the QStar server must be started before continuing with the configuration.

Select the Proxy Simulated Library and then select the Next button.

At the bottom of the window all configuration options for Proxy Simulated Library will appear.


Page 36 of 42

Figure 3.47 - Library Configuration Note: The directory must have a sufficient amount of space to create the shelves. For example, if 100 shelves were chosen and each shelf is 1 gigabyte in size the specified directory must have at least 100 gigabytes of available space.

The Proxy Simulated Library contains only DVD-R media. With the QStar Server started, select all configuration options for Proxy Simulated Library.

Library Name: The Library Name must be in form “proxyN” where N is a number from 1 to 31 (the default name is proxy1).

Number Of Shelves: Choose the number of shelves that will be allocated to the Proxy Simulated Library. Dest Lib Name: Specifies the destination of the physical DVD-R library associated with the Proxy Simulated Library. In this example the physical library JB0 has been selected.

From and To: Specify the range of shelves used to find a destination disk. One Side Media: The destination disks are DVD-R 2-sided; otherwise select the One Side Media check box.

Directory Path: Select the directory on the system where the Simulated shelves will be created.


Note: In this example a 10 shelf Proxy Simulated Library will be created.

All proxy disks (DVD-R) are automatically imported at the time of the library creation. A proxy DVD-R disk is automatically added to the Integral Volume set if the Integral Volume set definition includes proxy media. When the proxy DVD-R disk becomes fully written, it is copied to a DVD-R disk in the destination library. After the copy, the destination DVD-R disk is used in the Integral Volume set instead of the proxy DVD-R disk, whereas the proxy DVD-R disk is declared empty and can be used again.

Specify in the From and To text fields the range of shelves used to find a destination disk. If they are absent, all shelves are used. In this example the range is from shelf 100 up to shelf 200.


Page 37 of 42


Select the Browse button to browse the system for the directory path where the simulated shelves will be created on the system.

Once all configuration options are chosen, select the Finish button to create the Proxy Simulated Library.


Page 38 of 42


After selecting the Finish button, the Configuration view pane will contain the information for the library, the Directory Path, Dest Lib Name and range of shelves information will be displayed only if the QStar server running.

POST INSTALLATION TEST

Figure 3.52 - Library Status

Once the QStar Server has restarted, verify the status of the library to ensure that the Scheduler is running.

Select Devices to verify the status of the library.

Select Storage Libraries, and then select Status to verify the Scheduler Status of the library that was just configured.

Note: Select the Library Name drop box and check the status for each configured library.

Page 39 of 42

QSTAR SERVER PRIORITY

The Priority button allows the QStar Server to utilize more of the system’s processor time. This can be advantageous if there is a requirement to move large amounts of data. Access to the system server should be restricted if the Server Priority is set to High.

In QStar Server, select the Priority button to change the Priority of the QStar Server.

In the Server Priority window select the desired level of priority for the QStar Server. Select the OK button.

By default, the QStar Server Priority is set to Low.

Figure 3.53 - QStar Server Priority

Page 40 of 42

ADDING NEW STORAGE DEVICES To add a new storage device to the system all the Integral Volume sets must be unmounted and the QStar server should be stopped.

Figure 3.54 - Claiming a Device

Go to the Start button, then Programs, then QStar ASM or QStar DDR depending on which Software was installed.

Select QStar Device Claiming.

Note: If the device is not already connected to the server, the server must be shut down, the device connected and the server restarted. Once this is complete follow the instructions above.

Mark the NEW device(s) that is going to be controlled by the QStar Software and select the OK button.

An additional window will appear notifying that the system will be rebooted. Select the OK button.

After the system has rebooted, open the QStar Administration Interface and stop the QStar Server.

Please refer to Chapter Three, Specifying the Storage Device Configuration section to complete the additional configuration and licensing of the additional library.

Figure 3.55 - Claiming an Additional Library

Page 41 of 42

REMOVING QSTAR SOFTWARE If the QStar Software is being installed to move to another server, or for an upgrade, ensure all Primary data is archived before proceeding.

Figure 3.56 - Removing QStar Software

To remove the QStar Software from the server select the Start button, select the QStar Program Group, this will differ depending which product is installed, select the “Uninstall QStar Software” option. The machine will need to be rebooted.

By default, not all the QStar directories will be removed from the c:\qstar directory (c:\qstar is the default location for the QStar Software). All the database and the configuration files will be kept.

Select YES to keep the default settings or Select NO to perform a clean uninstall.



Selecting NO, the system will ask you an additional confirm.

Page 42 of 42

of 20

This chapter describes the basic notions of the library management, the device’s identifications, the library parameters and some library management features of the QStar Software that let you recover from errors introduced by accident or caused by hardware failure.

Topics include:

• Checking library status and parameters

• Displaying library statistics information

• Setting the media or drives on/offline

• Error recovery

• Selected errors

• Use of media not supported by the library

BASIC NOTIONS OF LIBRARY MANAGEMENT .............................................................................2

Jbscheduler .......................................................................................................................2 Element Status: Online/Offline..............................................................................................2 Library or Standalone Drive Identification...............................................................................2

LIBRARY PARAMETERS ...........................................................................................................3 Time Control ......................................................................................................................3 Persistent Parameters .........................................................................................................3

MANAGING THE LIBRARY PARAMETERS ....................................................................................4 LIBRARY STATISTICS.............................................................................................................5

Managing the Library Statistics .............................................................................................5 FEATURE JB COMMANDS ........................................................................................................6

Using the JB Commands ......................................................................................................6 Displaying the Library Status................................................................................................7 Setting the Drive Profile and Priority......................................................................................9 Setting the Lease Time......................................................................................................11 Setting a Drive Offline/Online and Checking the Library Status ................................................12 Setting a Shelf Offline/Online and Checking the Library Status ................................................12

ERROR RECOVERY ...............................................................................................................14 Examples of Recovery after a Hardware Failure .....................................................................14

Example 1 - Clearing a Drive and Shelf Bad State...............................................................14 Example 2 - Clearing a Drive Bad State.............................................................................15 Example 3 - Clearing a Shelf Bad State .............................................................................16

Example of Recovery for Lost Source Shelf Information..........................................................17 Example of Recovery for Unknown Shelf Type Information......................................................18

USE OF MEDIA NOT SUPPORTED BY THE LIBRARY....................................................................20 MEDIA IMPORTED VIA FRONT PANEL OF LIBRARY INSTEAD OF VIA QSTAR.................................. 20

of 20

BASIC NOTIONS OF LIBRARY MANAGEMENT

Jbscheduler The jbscheduler is activated by the jbcmd scheduler command and deactivated by the jbcmd shut command. When the jbdriver receives an I/O request for a surface, and a medium is not loaded into any drive or a medium is loaded but the access to another side is requested, the driver notifies the jbscheduler. The jbscheduler processes all necessary loading, unloading or flipping of the media to get the requested surface accessible and notifies the jbdriver that all I/O requests to this surface can be satisfied. The described procedure - the automatic binding of the shelf / slot to the drive - is the main task of the jbscheduler. If the jbscheduler is not running, there is no automatic binding and the surface can be accessed only if a medium has been loaded by jbcmd load command or flipped by the jbcmd flip command.

Element Status: Online/Offline If the jbscheduler is running it does not mean that it controls all elements in the library. Whether an element is under the jbscheduler jurisdiction or not depends on its online/offline status. If the element is online, it is controlled by the jbscheduler, if the element is offline, it is not controlled by the jbscheduler. The jbscheduler makes the automatic bindings only for online shelves and uses only the drives that are online. The offline shelf can be accessed only after it has been explicitly loaded by the jbcmd load command or flipped by the jbcmd flip command. An application can change the online/offline status of the drives or shelves by using the jbcmd drive command or jbcmd shelf command.

Library or Standalone Drive Identification A device is represented by the name of the directory containing the special files used for accessing the device. In the API functions and commands, this name is designated as the jb_name.

Filenames

The following filenames reside in the jb_name directory:

jbctl

The library control device, which accepts the changers SCSI commands, is a symbolic link to the filename representing the changer character device.

driveN, rdriveN

The devices that accept the drives SCSI commands. N is a drive number (1, 2, etc). The driveN (rdriveN) filename is a

symbolic link to the filename representing the drive block (character) device.

jbNa, jbNb, rjbNa, rjbNb

The platter surface devices. N is the shelf number (1, 2, etc), ‘a’ and ‘b’ designate the sides, prefix ‘r’ symbolizes the

character device.

The library elements are specified by their numbers, which are 1-based.

The directory for a standalone drive contains the special files for one drive, one shelf and control device.

All normal library operations with the control device call for operator intervention.

of 20

LIBRARY PARAMETERS

Time Control The jbscheduler uses the time parameters - inactive time, idle time, quantum time and reserve time - for the automatic unloading of media from the drives. The inactive, idle and quantum times are built on a per library basis, the reserve time - on a per surface basis. All times are set in seconds.

The inactive time is defined as the maximum number of seconds a media is allowed to stay in the drive without access. If a media remains in the drive, without access, longer than the inactive time, the jbscheduler unloads it back to the shelf. If the inactive time is set to “0”, this mechanism is disabled. The default inactive time value is 900 seconds (15 minutes ).

The idle time is defined as the minimum number of seconds a media is allowed to stay in the drive without access. If a new media has to be loaded, but all drives are full, the jbscheduler may unload the media which has remained in the drive, without access, for more than the quantum or idle time, whichever is less. If the idle time is set to “0”, this mechanism is disabled and the quantum time defines the minimum period of time the media remains in the drive without access. The default idle time value is “0”.

The quantum time is defined as the number of seconds after which the jbscheduler examines again if the media can be unloaded. The minimum and default value is 10 seconds. A surface that has a non-zero reserve time is reserved. The minimum number of seconds a media with the reserved surface is allowed to stay in the drive without access is incremented by the reserve time. The reserved surface is not affected by the idle time mechanism, but is affected by the inactive time mechanism. If a reserved surface has been idling more than the idle time, a media will not be eligible to be swapped out (unlike the unreserved surface). However, if a reserved surface has been idling more than inactive time, a media is unloaded. The default reserve time for every surface is “0”, which means the reserve time mechanism is disabled. The reserve time is applied only to the next loading of the media; when the media is unloaded the reserve times of its upper surface drops to “0”.

The reserve time can be set only for the surface on the online shelf and is cleared when the shelf becomes offline.

Persistent Parameters Some parameters controlling the library management are persistent; they remain unchanged through a system reboot. These parameters include time control values (inactive, idle, and quantum times) and generic statistics values (nimports, nexports, nloads, nunloads, and nflips) and are related to the special library control daemon called jbscheduler. The special jbdriver in the operating system’s kernel supports the library management interface. They are set when the library management software is configured for the library and can be cleared or set to their default values on Library Status and Library Statistics.

of 20

MANAGING THE LIBRARY PARAMETERS

To modify the Library Parameters (Quantum, Inactive and Idle times) select the Change button and insert the new value.

The view pane displays the current value.

Selecting the Change button will bring up the Swap Time Parameters window as in figure 4.2.

Note: See jbcmd param command in Chapter 9 - Command Reference for more detailed information.


Figure 4.2 - Library Swap Time Parameters

The Swap Time Parameters allow the library to be finely tuned to the application, the values set are persistent, but may be set individually back to the default value at any time by placing a check in the Default check box.

of 20

LIBRARY STATISTICS QStar Software provides statistics for the elements within the library. These statistics allow the System Administrator to monitor for potential problems with the media and drives within the library. This allows problems to be rectified before they become too serious. There are also statistics for media loads per shelf/surface and per drive. If the library is full and media needs to be taken offline, these statistics will identify the less frequently accessed media. Statistics view pane allows library statistic information to be displayed or cleared. Statistics are collected for every surface and drive and contains the following counts: Loads: Number of media loads for shelf surface/drive. Recover: Number of recovered errors occurred on surface/drive/carrier. Bad: Number of cases when a shelf/drive was marked bad. PDL: Number of primary defect blocks on the DVD-RAM and MO/UDO/Blu-ray Optical surface. SDL: Number of secondary defect blocks on the DVD-RAM and MO/UDO/Blu-ray Optical surface. The number of DVD-RAM defect blocks is recalculated on every load of the surface.

Managing the Library Statistics To view the current library Loads, Recover, Bad, PDL and SDL statistical information select Statistics.

To reset the Statistics values select the required fields to be cleared and then select the Clear button. All the statistical values will be set to “0”. Note: A DVD-RAM media that contains more than 300 PDL or SDL blocks should be considered not to be reliable anymore. QStar highly recommends not erasing and reusing such media.

Figure 4.3 - Library Statistics

of 20

FEATURE JB COMMANDS The JB module allows various operations with the library and its elements (shelves, drives, carriers, and mailslots). All commands are available only if the library scheduler is running. These commands are to be used from a DOS window in the directory c:\qstar\bin.

The movement commands are the following: jbcmd load Move a medium from the shelf to the drive jbcmd unload Move a medium from the drive back to the shelf jbcmd flip Invert a medium in the drive jbcmd export Move a medium from the shelf or drive to the mailslot jbcmd import Move a medium from the mailslot to the shelf.

Note: jbcmd scheduler, jbcmd shut, jbcmd import and jbcmd export commands are for testing and diagnostic purposes only, as these commands do not alter the status of the GUI. Platters to be imported for set use, should be imported thorough the GUI interface, please refer to Importing Media into the Library in Chapters 5 and 7 in this manual.

The Commands that can set the online/offline status of the elements or show their status are the following:

jbcmd reset Clears the bad status of a drive and shelf in a single command when an error has occurred. jbcmd shelf Sets the online/offline status and moves the media into the selected shelf and clears the bad status of

the shelf where the error occurred. Sets profile of media type, can be automatic, this will detect the media type, or can be set manually.

jbcmd drive Sets the online/offline status of the drive and moves the media into the selected shelf and clears the bad status of the shelf where the error occurred. Sets drive priority for read/write and profile for the media types it can handle, the default in both cases is automatic.

jbcmd status Shows the status of the library, including drives, shelves, mailslot and carriers. jbcmd param Shows and changes the parameters of the library, including idle, inactive and quantum times, also the

number of imports, exports, loads, unloads and flips. jbcmd statistics Can show and clear the statistics of the library, including load, recover, PDL and SDL information. jbcmd lease Sets the drive lease time for the shelf.

Using the JB Commands


The three buttons at the bottom left are the equivalent of the following jbcmd commands: Off = jbcmd drive or shelf –f Set Good = jbcmd drive or shelf -b On = jbcmd drive or shelf –n The Reset button is the equivalent of the jbcmd reset command. Note: For more detailed information on the “jb” commands please, refer to Chapter 9 - Command Reference in this manual.

of 20

Displaying the Library Status Status view pane is used to display and monitor the library status, including the Scheduler Status, the Swap Time Parameters, and the Element Status. Status is a useful tool to detect which library component may be failing.

Example for an Optical library. To display the status for a library identified as JB0, select JB0 from the Library Name drop menu:


Figure 4.6 - Library Status (Element Status)

Example for a CD/DVD library.

Status for a CD/DVD device shows the Drive Capabilities and media type within the shelves. Before the refresh procedure, all media capabilities are assigned for every full shelf. This allows loading the media into all drives during the refresh procedure to determine the correct media type of the shelf. The media type is automatically set after the refresh procedure. After that, the jbscheduler will only allow the correct media to be loaded into the drive that can handle this media type. For example, the media loaded into the shelf with a “dvd-r” status may only be inserted into a DVD-R drive. Once the DVD-R media is burned and becomes a DVD-ROM media, the QStar Software will automatically change the “dvd-r” status to “dvd-rom”. If the library supports dual sided media and single sided media is used in any shelf, “1-side” information will be assigned to that shelf. Note: Single surface media should always be imported data side down.

of 20

Example for a Tape library. Status for a Tape device shows the Drive Capabilities and media type within the shelves. The same explanation made in the figure before for DVD libraries is applicable to the Tape libraries.

Figure 4.7 - Library Status (Element Status)

of 20

Setting the Drive Profile and Priority Using the Drive Profile and Drive Priority it is possible to change the drive profile and the drive priority. These options are mostly used with drives that support different type of media, like the DVD multi-function drive. Modifying the drive profile allows the setting of a drive for read only operation or write only operation. Changing the drive priority specifies that a drive should be used mostly for the read operation or for the write operation or both read and write operation.

The QStar Software will automatically select the drive profile for the Drive Capabilities, this may also be configured manually by Highlighting the required drive, then right click the mouse and select Set Profile. A second window will appear (as shown in figure 4.9) to manually select the required profile. It is also possible to select Reset Profile to set the drive back to default.

Figure 4.8 - Library Status (Setting the Drive Profile)

Figure 4.9 - Drive Capabilities

Place a check in each of the check boxes for each media type to be supported by this drive, select Default to set the drive back to its default Drive Capabilities. This feature allows drives to be dedicated to certain tasks, such as only reading or for writing.

of 20

The priority of the drives can be changed by Highlighting the required drive, then right click the mouse and select Change Priority. The Drive Priority option is used primarily for libraries with CD/DVD/Blu-ray and Tape drives present. The priority defines the order in which the drives are used by jbscheduler when it is looking for an appropriate drive.

Figure 4.10 - Changing the Drive Priority

Figure 4.11 - Drive Priority

The default mode is Auto; this means the first drive has the lowest number and therefore the highest priority for Read, Write and Read/Write. The drives then continue in priority for each consecutive drive.

When set to Manual, the Read, Write and Read/Write priority can be set individually for each drive in the library.

of 20

Setting the Lease Time The Software utilizes a default tape leasing feature during mount session of the Integral Volume set. The tape unlock feature allows to pool tape drives and mount more Integral Volume set file systems than there are available tape drives. The media loaded from a shelf will occupy the drive and prevent other media from being loaded. In order to prevent monopolization of the drive, the time the media remains loaded in the drive may be managed using drive lease approach. The media loaded in the drive may be “locked” which may be necessary for some operations such as tape copy. By default the media is loaded into drive for some time period which depends on the drive load/unload time. The Lease Time option allows the manipulation of media residency timing in the drive. The drive lease is mainly relevant to tape drives because operations on the tape are position sensitive. There is a difference in lease timing for real and virtual tape libraries. The virtual tape load/unload and positioning operations are much faster and lease time can be made (and by default are) smaller.

To set the Lease Time, first Highlight the shelf and then select the Lease Time option.

Figure 4.12 - Lease Time

Figure 4.13 - Lease Time

The default value for real tape is 900 sec. The Leasing Time check box allows enabling and disabling of the leasing time for a specified shelf or slot.

The value time leasing is set in seconds, or reset to default Infinity button locks the shelf to a drive. Note: For more detailed information about lease option commands please, refer to jblease (jbcmd lease) or vllease (vlcmd lease) command on Chapter 9 - Command Reference in this manual.

of 20

Setting a Drive Offline/Online and Checking the Library Status

Figure 4.14 - Library Status (Drive Offline/Online)

If one of the drives present in the library is causing frequent hardware errors, the drive can be made inaccessible by setting the drive Offline. To set the drive Offline, first Highlight the drive and then select the Off button. Note: If there is media present in the drive when the drive is set Offline, it will be put back on the source shelf. Once the drive is repaired, set the drive online. To set the drive Online, first Highlight the drive and then select the On button.

Setting a Shelf Offline/Online and Checking the Library Status

If one of the media present in the library is causing frequent hardware errors, the shelf can be made inaccessible by setting the shelf Offline. To set the shelf Offline, first Highlight the shelf and then select the Off button. To set the shelf Online, first Highlight the shelf and then select the On button.

Figure 4.15 - Library Status (Shelf Offline/Online)

of 20

Figure 4.16 - Library Status (Right mouse button context menu)

Drives and shelves can also be selected for various functions with a right mouse button context menu, Highlight the required drive/shelf and with the right mouse button, select the option required.

of 20

ERROR RECOVERY QStar's Software contains features that let you recover from most errors introduced by accident or caused by hardware failure. When jbscheduler fails to move media from a shelf to a drive and vice versa or when it fails to flip media, it marks both the media and drive as “Bad”. From that moment on, the media and the drive, which are marked as Bad, will not be used by the jbscheduler until the problem is fixed. Check the status of the drives and shelves with Status view page. If the drive, with or without a media, is marked as Bad, then try to recover with the Reset button. This will clear the Bad State of a drive and, if media is present in the drive, of the shelf and then move the media back to the shelf. Again, check with Status for the current status of the library. If a Bad State is still displayed on a shelf or drive, it can be cleared by setting the drive/shelf to On/Off, or the Set Good button.

Examples of Recovery after a Hardware Failure

Example 1 - Clearing a Drive and Shelf Bad State

Automatically To clear the Bad State for a drive and shelf at the same time select the Reset button. After the Reset command has completed both the shelf and drive States will return to Good. Note: The Reset button does not alter the Status of the drive or the shelf.

Figure 4.17 - Library Status (Clearing Bad State Automatically)

of 20

Figure 4.18 - Library Status (Clearing Bad State Manually)

Manually To clear the Bad State for a drive and shelf separately, use the three buttons below in the following sequence. Highlight the Drive that has a Bad State then select the Off button, next select the Set Good button. Finally select the On button. The State of the drive will return to Good. Highlight the Shelf and follow the same sequence as above.

Note: QStar highly recommends checking the status of the drive and shelf after the Automatic or Manual procedure. If the library is a DVD/Blu-ray or Tape library it is also recommended to check if the media type information is correct. If the media type information is different or not displayed, Highlight the shelf, press the right mouse button and select the Reset profile option to reset the media type information. Then refresh the shelf from Online Media by Highlighting the shelf and select the Refresh button. See figures 4.20 and 4.21 for additional information.

Example 2 - Clearing a Drive Bad State

To clear the Bad State for a drive use the Set Good button.

Highlight the Drive that has a Bad State then select the Set Good button, this will change the State of the drive to Good.

Figure 4.19 - Library Status (Clearing Bad State on a Drive)

of 20

Example 3 - Clearing a Shelf Bad State

Figure 4.20 - Library Status (Clearing Bad State on a Shelf)

To clear a Bad State for a shelf use the Set Good button. Highlight the Shelf that has a Bad State then select the Set Good button, this will change the State of the shelf to Good.

of 20

Example of Recovery for Lost Source Shelf Information This error can be introduced by human intervention or hardware failure. In this case the library loads media into a drive and because of a hardware error forgets which shelf the media came from. Status displays this media as having lost the source shelf information. The QStar Software also, redirects the following message into Syslog view pane or c:\qstar\log\syslog.txt file.

JB0: jb0 drive 1: Source shelf information lost - use jbreset

To clear the Lost Source Shelf status, the System Administrator must use the Reset button additionally specifying an empty shelf number that will be used by the QStar Software as the destination for this media. Note: Before using the Reset button, ensure you have an empty shelf available in the library and know the corresponding shelf number.

Figure 4.21 - Library Status (Clearing Lost Source Shelf Status)


After selecting the Reset button a new window will appear requesting the available Shelf number. Enter the number and select OK. The media in the drive will be placed in the specified shelf, clearing the Lost Source Shelf error. QStar also recommends performing the following action: Select Media and Refresh the specified shelf and then select Database and check the consistency of the database by selecting the Verify button. Note: See Chapter 5 -The Volume Librarian in this manual for additional detailed information.

of 20

Example of Recovery for Unknown Shelf Type Information This error can be introduced by a hardware failure during the refresh operation and it is specific for DVD/CD/Blu-ray or Tape libraries with mixed drive types or drives that support different types of media. Before the refresh procedure all media capabilities are assigned for every full shelf. This allows loading of the media into all drives during the refresh procedure to determine the correct media type. The media type is automatically set after the refresh procedure. After that, the jbscheduler will only allow the correct media to be loaded into the drive that can handle this media type. If during the refresh procedure the library loads media into a drive and because of hardware error could not detect the media type of the shelf, the QStar Software will automatically remove all the profile information for the shelf in order to force the System Administrator to refresh the shelf once again.

In the example, shelf 2 is displayed without media type information, so its profile has been lost.

Figure 4.23 - Library Status (Unknown Shelf Type Information)


Example for DVD/CD/Blu-ray Library:

Highlighting the required shelf, then right click the mouse and select Reset Profile can reset the shelf’s profile. Then from Online Media, select the shelf whose profile has just been reset and press the Refresh button, this will refresh the shelf to find the true media type.

of 20

Example for Tape Library:



of 20

USE OF MEDIA NOT SUPPORTED BY THE LIBRARY

Figure 4.26 - Library Status (Unsupported Media)

These types of incidents are rare, but could happen if the manufacturer’s drive does not support the type of media trying to be used. Assume that a WORM disk is imported into a library that only supports rewritable disks, the jbscheduler, after loading the disk into the drive, cannot spin the disk and make it ready for use. Thus, the jbscheduler will not unblock the I/Os that were issued to the disk. Status shows the drive in which the media was loaded and the media marked as Bad State.

The only way to properly unblock the I/O is by using the Reset button. Then exporting the media from Online Media. Use Status to check that no Bad flags were set. If this fails, eject the media from the front panel of the library.

MEDIA IMPORTED VIA FRONT PANEL OF LIBRARY INSTEAD OF VIA QSTAR This can happen with some library models, as the front panel of the library prompts the user to import the media to a shelf as it is inserted into the mailslot. If this happens, an updated library map is needed. This can be achieved by viewing Status, then select Online Media, the shelf will probably be marked as empty, Highlight the shelf and select the Refresh button. This will refresh the jbdriver so it will know that the shelf is now occupied and update the VL database with the media status.

of 152

This chapter describes the basic notions of the Volume Librarian (VL) and the relationship between VL and the devices (media, library and standalone drives). There are detailed explanations of the commands used to control the VL to ensure the maximum potential is obtained from the devices, both attached and offline from the system. Details of recovery procedures in the event of VL database inconsistency are also included. INTRODUCTION ....................................................................................................................4

Electronic Labeling ..............................................................................................................4 Location Tracking................................................................................................................4 Dynamic Media Allocation ....................................................................................................4 Media Set Quotas ...............................................................................................................4

BASIC NOTIONS....................................................................................................................5 VL Domain.........................................................................................................................5 VL Device Name .................................................................................................................5 Volume .............................................................................................................................5 Integral Volume Set ............................................................................................................5 VL Server ..........................................................................................................................5 VL Database ......................................................................................................................5 Volume Set Policies.............................................................................................................6 Set Id ...............................................................................................................................6 Surface Id .........................................................................................................................6 Refreshing .........................................................................................................................6 VL Daemons ......................................................................................................................6

USING THE VOLUME LIBRARIAN ..............................................................................................6 MANAGING MEDIA VIA THE VL DATABASE ................................................................................6 VL MEDIA SET RELATED COMMANDS........................................................................................7 MANAGING THE VL DATABASE ................................................................................................8

Importing and Exporting the Media........................................................................................8 Erasing the Media ...............................................................................................................9

Displaying and Setting the VL Configuration Properties for Delayed Erase Media........................9 Refreshing the Media.........................................................................................................11 Creating an Integral Volume Set .........................................................................................12 Available File Systems and Archive Media Type .....................................................................15

Standard Data Format (SDF) ...........................................................................................16 Archive Media Type .....................................................................................................16 Database Backup Configuration Option...........................................................................17 Available Configuration Options .....................................................................................19 Additional Shredding Options for Optical Compliant WORM and Rewritable Media..................20 Additional Compression Option for Tape Archive Media .....................................................21

Tape and Disk Object File System (TDO) ...........................................................................22 Archive Media Type .....................................................................................................22 Database Backup and Tuning Configuration Option...........................................................23 Available Configuration Options .....................................................................................23 Additional Compression and Encryption Option for Tape Archive Media................................24

Universal Disk Format (UDF) - (ISO 9660).........................................................................26 Archive Media Type .....................................................................................................27 Available Configuration Options .....................................................................................27 Additional Options for CD/DVD-R and BD-R Archive Media and Packet Writing...................... 28 Additional Options for CD/DVD-ROM Archive Media with UDF and ISO 9660 File System........29 Additional Options for Single-Volume and Automount Interchange Level.............................. 30 Additional Options for Spanning Interchange Level...........................................................31

of 152

Linear Tape File System (LTFS)........................................................................................32

Archive Media Type .....................................................................................................33 Available Configuration Options .....................................................................................33 Additional Options for Direct-Single-Volume ....................................................................34 Additional Options for Single-Volume and Automount Interchange Level.............................. 34 Additional Options for Spanning Interchange Level...........................................................35

Universal File System (UVFS) - Plasmon PFS/AFS File Systems .............................................37 Archive Media Type .....................................................................................................38 Available Configuration Options .....................................................................................38

Archive Appliance File System (AAFS) - Plasmon AA File System...........................................39 Archive Media Type .....................................................................................................39

No Media File System .....................................................................................................40 Archive Media Type with Simulated Media and Centera Libraries ...........................................40

Displaying and Deleting an Integral Volume Set ....................................................................41 Displaying and Modifying the Integral Volume Set Properties...................................................42

Integral Volume Set Common Properties ...........................................................................42 Integral Volume Set SDF Specific Properties ......................................................................44 Integral Volume Set TDO Specific Properties ......................................................................46 Integral Volume Set UDF Specific Properties ......................................................................49 Integral Volume Set LTFS Specific Properties .....................................................................50 Integral Volume Set UVFS and AAFS Specific Properties.......................................................52

Adding Media to a TDO or SDF or AAFS Integral Volume Set ...................................................53 Adding Media to an UDF or UVFS (PFS/AFS) Integral Volume Set.............................................54

Adding Media Specifying the Logical Volume ID ..................................................................57 Adding Media to an LTFS Integral Volume Set .......................................................................60

Adding Media to an LTFS Integral Volume Set Specifying the Volume Name............................62 Displaying Integral Volume Set Information..........................................................................65 Removing Media from a TDO/SDF and LTFS Spanning Integral Volume Set ...............................67 Removing Media from UDF/UVFS/LTFS Automount Integral Volume Set....................................68 Removing Media from UDF and UVFS Spanning Integral Volume Set ........................................69

VL LIBRARY RELATED COMMANDS .........................................................................................70 Main Characteristics of the Media in Online Media ..................................................................70 Displaying and Sorting Library Shelf Information ...................................................................72 Displaying Bar Code and Media ID Library Shelf Information ...................................................73

FIXING DATABASE INCONSISTENCIES ...................................................................................74 Fixing a Database Inconsistency after a Library Hardware Failure ............................................75 Fixing a Database Inconsistency after a Media has been Manually Removed from the Library.......78

MANAGING VL OFFLINE VOLUME TRACKING............................................................................80 Canceling a Request for Offline Media ..................................................................................84

Editing an Offline Location...............................................................................................85 Adding an Offline Location for Media Already Offline............................................................85 Displaying and Setting the VL Configuration for Offline Media Request Properties .................... 86

MANAGING OFFLINE MEDIA UNDER VL CONTROL USING THE MAGAZINE OR PACK IMPLEMENTATION .......................................................................................................87 ADDING MEDIA TO AN INTEGRAL VOLUME SET .......................................................................96 RESTORING AN INTEGRAL VOLUME SET .................................................................................96

Restoring an Integral Volume Set not Known to the VL...........................................................96 Restoring an Integral Volume Set after a Software Upgrade ....................................................97 Restoring an Exported Integral Volume Set Deleted from the VL Database ................................97

of 152

DATA COMPACTION UNDER VL CONTROL................................................................................98

Data Compaction Feature...................................................................................................99 Data Compaction not Available ......................................................................................... 103 Displaying and Setting the VL Configuration Properties for Delayed Data Compaction ............... 103

ERROR RECOVERY ............................................................................................................. 105 THE COPY AND COMPARE MEDIA UTILITIES .......................................................................... 106

Manual Media Copy and Compare...................................................................................... 106 Manual Media Copy ...................................................................................................... 106 Common Media Copy Options ........................................................................................ 107 Incremental Media Copy Option ..................................................................................... 108 SDF Specific Media Copy Option ..................................................................................... 108 Manual Media Compare................................................................................................. 109 Common Media Compare Options................................................................................... 109 SDF Specific Media Compare Option ............................................................................... 110 LTFS Specific Media Compare Option .............................................................................. 110 Example of Manual Media Copy ...................................................................................... 111 Displaying and Setting the VL Configuration Properties for Delayed Media Copy .................... 114 Example of Manual Media Compare ................................................................................ 116 Displaying and Setting the VL Configuration Properties for Delayed Media Compare............... 118 Substitute the Original Copy of the Media with the Duplicate .............................................. 120

Automatic Media Copy ..................................................................................................... 123 Automatic Copy of Full Media......................................................................................... 126 Automatic Incremental and Multi-Incremental Media Copy ................................................. 127

Managing Automatic Incremental and Multi-Incremental Media Copy ................................ 130 DELAYED JOBS UNDER VL SCHEDULER CONTROL .................................................................. 132

Displaying the Delayed Jobs under VL Scheduler Control in the Delayed Jobs Queue List ........... 132 Displaying and Setting QStar Command Under Cron Job....................................................... 134 Displaying and Setting the General Delayed Jobs VL Configuration Properties .......................... 134 Displaying and Setting the VL Configuration Scheduled Archive Properties .............................. 135 Displaying and Setting the VL Configuration CD/DVD-R Delayed Recording Properties............... 136 Managing the Delayed Jobs .............................................................................................. 137

DISPLAYING AND SETTING THE VL CONFIGURATION OPTIONS................................................ 139 Displaying and Setting the VL Configuration for Offline Media Request Properties ..................... 140 Displaying and Setting the VL Configuration Threshold Blank/Erased Media Properties .............. 141 Displaying and Setting the VL Configuration for the Remote Administration Properties .............. 141 Displaying and Setting the VL Configuration for the Big Space Root Directory Properties ........... 142 Displaying and Setting the VL Configuration for the Minimum File System Space Available ........ 143 Displaying and Setting the QStar Server Port Configurations ................................................. 143

ADMINISTRATION INTERFACE WITH LIMITED FUNCTIONALITY ................................................ 144 QSTAR REMOTE ADMINISTRATION INTERFACE ...................................................................... 147

of 152

INTRODUCTION The “VL” commands allow configuration of the QStar database named Volume Librarian (VL). The QStar Volume Librarian module is responsible for managing all archival media known to QStar, referred to as the media library. The Volume Librarian knows the location (both the physical and logical) and status of every archival media, whether available online in a library or offline in a storage facility. Its capabilities eliminate any errors that may occur in manual volume management, while increasing productivity and performance. For online media, the QStar Software automatically manages all disk or tape allocations and movement without operator intervention. For requests that require offline archival media access, the operator is prompted to retrieve the disk or tape from its storage location outside the library and insert it into the QStar designated device. To ensure integrity of the large numbers of archival media in the media library, the QStar Software uses a volume database to index the location and status of each disk or tape. In this chapter the media managed by the Volume Librarian is referred to as Integral Volume set, which is a group of media that appears as one continuously growing storage space using a disk cache.

Electronic Labeling The key to each archival media is a unique electronic ID, applied directly to each disk or tape. This label is used to record the surface, the physical media, and any additional information QStar needs. Using the electronic label, QStar can quickly locate any media under its control.

Location Tracking As disks or tapes move from one location to another, the VL database is updated with the new information. For example, if you request information residing on a disk outside a library, the QStar Software prompts the Administrator to “retrieve volume 101 from the storage facility and place it in library identified as jb0”. Once inserted, the database changes the new location for volume 101 to library identified as jb0.

Dynamic Media Allocation As Integral Volume sets fill with data, it may be necessary to add additional media. The QStar Software can automatically allocate additional media to an Integral Volume set. The user benefits, because no time is spent resolving a request for more space. The QStar Software simply appends additional media to the Integral Volume set, and the user’s write request is satisfied. The System Administrator may also define their own allocation policies for staggering Integral Volume sets across surfaces.

Media Set Quotas To prevent excessive usage of media, the QStar Software allows the System Administrator to pre-define the quota for the Integral Volume set, or the maximum number of archival media in an Integral Volume set, at Integral Volume set creation time. This feature gives the System Administrator additional control over the use of the Integral Volume sets, particularly against runaway processes that consume more space than expected. Quotas can be increased after an Integral Volume set is created. If an Integral Volume set requests additional media, the QStar Software first checks to see if the set quota has been reached and if so, notifies the System Administrator. If the quota is within limits, the QStar Software attempts to acquire an additional medium from a pool of blank disks or tapes and appends it to the Integral Volume set. If a blank disk or tape is not available, the Administrator is prompted to insert an additional piece of media into the QStar designated device. Media may also be manually added to an Integral Volume set as needed. The additional disk or tape is appended to the online Integral Volume set without interrupting any current processes using the Integral Volume set.

of 152

BASIC NOTIONS VL Domain A VL Domain is a collection of hosts and devices managed by the Volume Librarian. A host may belong to a number of domains. A domain is identified by its name. For every domain a host belongs to, there is a subdirectory in the c:\qstar\vl\files directory with that domain name. This subdirectory is referenced below as the domain root directory. See its contents in the VL Database entry.

VL Device Name A name used to identify the device in the Volume Librarian. The device can be a library or a standalone drive. Every device configured during the installation of the QStar Software is represented by a directory containing the special files needed to access the device. The name of this directory (e.g. c:\QStar\dev\JB0) is the name used in the JB functions and commands. The last component of this name (JB0 for the above example) is the VL device name. The installation program for the QStar Software allows the Administrator to specify which domain (or domains) a certain device belongs to.

Volume A surface is a part of the Integral Volume set. Each surface that belongs to an Integral Volume set has its 0-based volume number. If a media belonging to an Integral Volume set is loaded into the device (on the shelf in a library or into a standalone drive) it is online. Otherwise, it is considered offline and the Volume Librarian maintains its offline location.

Integral Volume Set The Integral Volume set is a sequence of volumes integrated as a single unit with cache. For example, a file system containing a couple of surfaces is an Integral Volume set. An Integral Volume set has a name (set name) and attributes. A medium belonging to an Integral Volume set can be online (residing in the library or standalone drive) or offline (outside the library but with the offline location known to VL).

VL Server When the VL starts on a host, a special daemon (VL server) is activated. The VL API communicating with the corresponding server directs all requests for the VL operations, which may be a VL server on the same host or on any other host in the same domain. The VL server maintains the VL database within the domain.

VL Database The VL database includes the list of hosts controlled by VL and the databases for the devices, Integral Volume sets and archives on the current host. The root database directory (c:\qstar\vl\files) contains the following files and directories: devices

For every device controlled by VL, this directory contains a device database. A database is a file whose name matches the VL device name.

sets For every Integral Volume set, this directory contains the Integral Volume set database. An Integral Volume set database is a file whose name matches the Integral Volume set name.

ac For every Integral Volume set, this directory contains the Advance Configuration database.

ssd For every Integral Volume set created with QSSD (QStar Structured Storage Devices), this directory contains the Integral Volume set database. An Integral Volume set database is a file whose name matches the Integral Volume set name.

of 152

Volume Set Policies There are two policies managing how to add media to an Integral Volume set. The stagger policy knows where to find a new surface, which can be used as the next volume in the Integral Volume set, on the same media, or on the next media. The spread policy determines whether an Integral Volume set can be distributed between several libraries and hosts within the same domain.

Set Id A string of characters, which is normally written on every volume to identify the Integral Volume set, this volume belongs to.

Surface Id A string of characters, which is normally written on every surface to identify the volume within the Integral Volume set.

Refreshing To build the state of the surfaces, the Volume Librarian has to examine the media (on the shelf or in the standalone drive), read information from it and populate the VL database. This procedure is called refreshing. Importing a media into a library also causes the media to refresh.

VL Daemons The Volume Manager processes all requests from the VL clients. The Volume Manager also controls the adding of any additional media to the Integral Volume sets. It also manages adding them to a mounted Integral Volume set dynamically.

USING THE VOLUME LIBRARIAN The VL module manages the media in the library and allows the QStar Software to track all media in and out of the library. The Volume Librarian module makes it possible to configure the entire library as a unique Integral Volume set, or to create multiple Integral Volume sets inside the same, or multiple libraries. Using the VL commands, media can be configured to the Administrator's requirements. Different applications can have different media criteria, suiting different requirements.

MANAGING MEDIA VIA THE VL DATABASE Media is tracked in and out of the library by the VL database. When media is imported into the library with the vlcmd import command, the VL database loads the media into a drive and reads it to find what the status of the media is; does it have a volume label, is it erased, etc. If media is exported from the library using the vlcmd export command, the VL database is updated to show that shelf as empty. If the media being exported is part of an Integral Volume set, then the VL database prompts the System Administrator to give an offline location and to label the media. Please label the media as instructed, as this is the information that will be used if the VL requests an offline media from a mounted Integral Volume set. The VL database will also reflect the offline location that is input by the System Administrator. If the media to be used is rewritable then it needs to be erased before use with the vlcmd erase command, if the media is Tape, WORM optical, Blu-ray, CD/DVD-ROM or CD/DVD-R then it is ready for use. The vlcmd refresh command can be used to refresh all or selected shelves within the library and update the VL database. The selected shelves will be loaded into the drives of the library and read to find the status of each media; that is whether it has a volume label, or it is blank, etc. The vlcmd exchange command is used to move either media within the library, from an empty to full shelf, or exchanging media between two, or more full shelves. The shelves may also be removable magazines so that media can be easily removed, or added to the library via the vlcmd magazine command (mainly CD/DVD/Blu-ray libraries with magazine support). The VL database is updated once the media is exchanged. The vlcmd magazine command allows media to be added/removed in bulk without the need for the mail slot; however, it is not recommended to store media here for mounted Integral Volume sets, as they will need to be un-mounted for safe magazine removal. Once the magazine is exchanged, the shelves represented by the magazine are refreshed and the VL database updated.

of 152

Media Management commands:

vlcmd import (vlimport) Imports a media into a library and check the media contents

vlcmd export (vlexport) Exports a media from the library and store its offline location (if it belongs to an Integral Volume set) in the VL database

vlcmd erase (vlerase) Erase a media, a surface, a group of media or the whole library

vlcmd refresh (vlrefresh) Refresh the database, refreshing media type and contents

vlcmd exchange (vlexchange) Moves a media from one shelf to another in the library and updates the VL database

vlcmd magazine (vlmagazine) Exchanges media in the library using the magazines and updates the VL database

vlcmd lsdev (vllsdev) Prints the status of the media and library (ies) or standalone drive(s).

VL MEDIA SET RELATED COMMANDS Integral Volume sets are created using the vlcmd crset command, which can be used to specify options such as the amount of media in an Integral Volume set, the media type (Rewritable, WORM, UDO, PDD, Blu-ray, CD, DVD, RDX or Tape), or the file system type to be created (TDO, LTFS, SDF, UDF, ISO). The Integral Volume set can be modified with the vlcmd editset command, or viewed using the vlcmd lsset command. The Integral Volume set can be renamed with the vlcmd mvset command. Media can be initialized and added to an Integral Volume set with the vlcmd addtoset command. A magnetic cache is required for the Integral Volume set, the vlcmd cache command is used to set the cache parameters. The vlcmd cache command may also be used to modify the cache parameters. The vlcmd inset command allows changes to be made to the media within an Integral Volume set, such as offline location and cache specific functions relating to that media (mainly CD-ROM). If an Integral Volume set is no longer required, then it can be deleted with the vlcmd delset command; this command deletes the Integral Volume set name from the VL database, however, nothing is removed from the media. If the media is tape or rewritable then it can be re-used after the vlcmd erase command. VL will not allow vlcmd erase command of any media contained within an active Integral Volume set. Using vlcmd delset command will also remove any reference to the cache for that Integral Volume set, but the magnetic cache files will not be removed. The VL commands related to managing an Integral Volume set:

vlcmd crset (vlcrset) Create an Integral Volume set on the archival media

vlcmd addtoset (vladdtoset) Add additional media to the Integral Volume set

vlcmd cache (vlcache) Create and modify a cache for an Integral Volume set

vlcmd delset (vldelset) Delete an Integral Volume set from the VL database

vlcmd mvset (vlmvset) Rename an Integral Volume set name

vlcmd editset (vleditset) Display and modify Integral Volume set information

vlcmd inset (vlinset) Modify information relating to a CD within the Integral Volume set

vlcmd lsset (vllsset) List Integral Volume set information in the database

vlcmd mountiv (mountiv) Mount an Integral Volume set

vlcmd umountiv (umountiv) Unmount an Integral Volume set

Note: QStar recommends reviewing the explanation for the VL related commands in Chapter 9 - Command Reference of this manual, while reading this chapter.

of 152

MANAGING THE VL DATABASE This section will explain the main functionality of the VL database using the QStar Administration Interface. The following pages will describe how to manage the media, how to create and manage an Integral Volume set, and define and explain the terms used.

Importing and Exporting the Media

Figure 5.1 - Importing and Exporting the Media

To import the media into the library, remove the check from the Only Show Shelves with Media box to display the empty shelves, Highlight an empty shelf, insert the media into the mail slot and select the Import button. To export the media from the library Highlight the full shelf and select the Export button. The import and export operation can be performed also by highlighting the media and selecting the right mouse button.

Note: During the import and export operation an additional window will appear requesting confirmation for the action performed.

Using CD/DVD or Blu-ray libraries with mixed drive types or drives that support different types of media, during the import an additional Media Type window will appear. This window can be used to specify the type of media that will be imported. This ensures loading the media into the correct drive during the refresh procedure to determine the media type of the shelf. If the Auto Detect option is selected the QStar Software will automatically detect the media type. The media type is automatically set after the refresh procedure. After that, the jbscheduler will only allow the correct media to be loaded into the drive that can handle this media type.

Figure 5.2 - Importing and Exporting the Media

of 152

Erasing the Media

Figure 5.3 - Erasing the Media

If rewritable media is being used, like Optical (MO/UDO/PDD), Blu-ray, Tape or DVD-RAM media, erase the media before using it. To erase a media, Highlight the shelf and select the Erase button. To erase multiple media, Highlight the shelves and select the Erase button. The Erase Windows will open requesting confirmation for the action performed. If using Optical (MO/UDO/PDD) media with UDF, select “Use Write Instead Of Erase” option. Use Full Erase option can be used to check the consistency of a faulty media. By default a fast erase will be performed. In the example, the media in shelf 1 will be erased.

Displaying and Setting the VL Configuration Properties for Delayed Erase Media

To erase the media in shelf 1 using the Delayed Erase Media procedure, place a check in the Delayed Job box and assign a name to the job. Select the OK button to proceed. In the example, “Erase of Shelf #1” is the name assigned to the delayed job. If the delayed job name is omitted a default delayed job name is automatically assigned. The job will be executed according to the “Delayed Time” field in the Erase VL Configuration properties.

Figure 5.4 - Displaying and Setting Delayed Erase Media

of 152


In Delayed Jobs view pane select the VL Conf button, then select Erase tab to display the default Delayed Erase Media properties. Delayed Time: Start Time and Stop Time determines when the VL scheduler will process the delayed jobs in 24-hour mode. The 0:0 0:0 value is the default and ensures the jobs will not be delayed and will be processed immediately.

The System Administrator can change any of the default parameters by typing the new value.

In the example, default Delayed Erase Media option is changed so that the Erase operation will only take place between the hours of 23:00 and 06:00.

To change the Delayed Start Time of a job from the default time in the Erase VL Configuration properties, place a check in the Job Start Date box and change the Time or Date from the drop bar or by using the Calendar. Select the OK button to proceed.


of 152

Refreshing the Media

Figure 5.7 - Refreshing the Media

To refresh the media, Highlight the shelf and select the Refresh button. In the example, the media in shelf 3 has been selected to refresh. To refresh multiple media, Highlight the shelves and select the Refresh button. Note: During the refresh operation an additional window will appear requesting cancellation, or status for the action performed. The number of media refreshed simultaneously is limited to the number of drives available.

of 152

Creating an Integral Volume Set The Create New Integral Volume button is used to create an Integral Volume set; there are several different types of file systems available. In preparation for creating the Integral Volume set, a decision must be made as to how much cache is required and where it will be located.

Note: The cache should be large enough to accept all new data, any requests for archived data and enough extra room for unexpected high volume days between Integral Volume set archives. There should be adequate space left for directory information to be cached, which will increase in size as the Integral Volume set does.

Figure 5.8 - Creating an Integral Volume set

To create an Integral Volume set from Volume Management, select the Create New Integral Volume button.

Choose a name for the Integral Volume Name (maximum 12 characters) and select a size for the Cache (minimum 4MB). To select or create the Cache Location directory, press the Browse button. The Page Size allows a cache page size other than the Default 64KB to be used, changing the page size allows for more efficient use of the space in the cache if the average file size is small. However, the performance will be slower with the smaller the page size selected. The Page Sizes that are available are from 1KB up to 256KB.

Figure 5.9 - Creating an Integral Volume set

of 152

Figure 5.10 - Creating the Cache Folder

Select the folder to use for the cache or create it using the New Folder button and then type in the name of the folder or type the path and folder name in the Cache Location box. The Software will create the folder when the OK button is selected. Note: The cache location must have at least 2GB of space available; if not the mount procedure of the file system will be denied.

All the options described below can be enabled by placing a check in the related box or by specifying the option requested. The Stop on covered error option (enabled by default) if disabled, allows data to continue to be written to a large cache even if there is a covered error; this option determines if service to the users is stopped or continued while the problem causing the covered error is rectified. The Readonly option allows mounting a file system in read only mode. The Spread option allows the Integral Volume set to spread across multiple libraries automatically. Without this option the Integral Volume set will reside within the same library it was created in. However, media from another library can be manually added to the Integral Volume set at anytime.

Figure 5.11 - Creating an Integral Volume Set

Mount As option allows a local drive letter to be chosen to mount the Integral Volume set against. Share drive option allows, as a default, the file system to be shared across the network. The Quota option specifies the maximum number of media that can be included in the Integral Volume set. The default maximum number of media that can be added to an Integral Volume set is 2048. For example, if “1” is specified as the Quota number once the first media is full QStar Software will return a file system full error. If “2” is specified as the Quota number the QStar Software will automatically add another media to the Integral Volume set once the first one is full.

of 152

The Simulated Media Type option allows specifying simulated media in the Archive Media Type; the simulated media is for use with the simulated media libraries. Real and Simulated Media can be mixed in the same Integral Volume set if configured with SDF or TDO file system. The Make Copy of the original option allows the creation of a duplicate copy media. This can be done once the original media is full and another media is added to the Integral Volume set. The Make Copy option can also be scheduled as a Delayed Job. The Incremental or Multi Incremental option for Make Copy is only available for the TDO, SDF and UDF file system type. For more detailed information refer to “THE COPY AND COMPARE MEDIA UTILITIES” section in this chapter.

Figure 5.12 - Advanced File System Settings

Selecting the Advance button is possible to specify the Advanced File System Setting for the Integral Volume set. The Grace Period option specifies a period of years, days, hours, minutes and seconds as a timeout for modifying the state of an existing file or directory. A file may be modified, providing the user has sufficient privilege, until the Grace Period has expired, it is then marked as read only. Enabling this feature provides a WORM (read-only) file system, even with rewritable media which is ideal for corporate data archiving compliance requirement. The Retention Period option can be used alone or in conjunction with the Grace Period feature. Both Grace Period and Retention Period start from the last modification time. The Retention Period specifies a file can be removed only once the Retention period has expired. The benefit to this feature is the ability to lock a file to read only status for the time the file is required to remain available within corporate guidelines. This feature goes further than the standard Windows read only flag, as even the System Administrator cannot remove the read only flag for files under Retention Period management. Once a file has reached a point in time after the Retention Period, the file may then be modified or deleted from the file system. If both the Retention and Grace Periods are specified, a file can only be modified or deleted either before the Grace Period begins or after the Retention Period expires. This feature is configurable on an Integral Volume set basis and can be set by seconds, minutes, hours, days and years.

Both Grace and Retention period can be set in soft (default setting) or permanent mode. In soft mode the System Administrator can disable or modify the period as need it. If Permanent check box is selected the value of both periods will be written permanently on the file system information and modification will no longer be possible. The Write Once option provides a WORM file system, even with rewritable media, which is ideal for corporate data archiving compliance requirement. Working differently from Grace Period, once a file is written in the file system; the overwrite; remove and set size operations are prohibited. A file can only be appended and renamed. This option will be ignored if it is used in conjunction with Grace Period. If the Deny Rename option is specified with the Write Once option, the renaming operation is also prohibited. Prefetching, Cryptography and File Data Digest options will be explained later on Chapter 6 - Migration Manager of this manual. To complete the Integral Volume set creation the File System Type and the Archive Media Type need to be chosen. See next section for detailed information.

Figure 5.13 - Advanced File System Settings

of 152

Available File Systems and Archive Media Type In this section each option used during the creation of an Integral Volume set, to include the use of all available file systems will be explained in detail. By default the QStar Software will display the information to create an Integral Volume set using rewritable media with the SDF file system, as these options are the first on the lists. The QStar Software supports several different types of file systems, for more detailed information please refer to the “File Systems” section in Chapter 2 - QStar Components of this manual.

Figure 5.14 - Available File Systems

The list of File System Type QStar support is very wide and each one of them will be explained later in this chapter. Note: The SDF Primary Mirror and SDF Secondary Mirror appear only if DDR (Data Director) product is installed. Note1: The file systems AMPL, CLOUD, HCP and OSM are used with Object Storage Devices and the Replication RPL file system will be explained in the QStar Structured Storage Devices and ASM Replication Migrator manual.

The Media Types are divided in Real and Simulated and some file system can be mixed. The media type displayed will depend of the file system selected.

Figure 5.15 - Archive Media Type

of 152

Standard Data Format (SDF)

Figure 5.16 - Available File Systems - SDF

The Standard Data Format (SDF) is one of the QStar file systems. This configuration allows the use of multiple media to be created as a single seamless file system with a magnetic cache.

Note: The options for mirroring are only available if the Data Director product is installed.

Archive Media Type

The Standard Data Format (SDF) file system can be used with WORM or rewritable Optical (MO/UDO/PDD) media, rewritable RDX media, Blu-ray (BD-RE, BR-R) media, DVD-RAM media or Tape media. To finish the creation process, select the Create button.


of 152

Database Backup Configuration Option

The SDF file system writes the data and metadata sequentially to the media. The metadata information for the files written to the file system are also kept in the SDF database which consists of 3 files the sdf_node, sdf_iblk, sdf_dir, one transaction log file sdf_log, the sdf_shred and sdf_shred_map are only for the shredding option. These files are located in the cache directory. For more detailed information about the sdf_db file, please refer to Chapter 6 - Migration Manager of this manual. Configuration 1 During initialization of the next volume (except the first) in the Integral Volume set the SDF database files are independently compressed (optical Media Only) and written to the beginning of the SDF volume (surface). QStar calls this process a rollover backup. This feature of the SDF file system permits having all the metadata information of all files written to the previous surface of the Integral Volume set on the next surface. In the case of disaster recovery this will allow for a very fast restore of the file system structure information without reading all the media and without re-importing any media into the library when there are written media located offline (outside of the library). Database recovery is performed by reading the SDF database from the last written volume in the Integral Volume set and uncompressing the SDF database files into the cache directory. After the database files are recovered the rest of the volume (surface) is scanned and all file system events are recovered into the database files in the cache. This allows recovering the rest of the meta-data that was written to the media after the database files were written. The SDF migrator uses a single thread model to handle all client requests and database backups. The database backup is synchronized with write event processing. This means that the database backup is done when a write operation is received and a new volume needs to be created. From a user’s perspective, the archiving write operation is delayed while the database files are being compressed and written to the media. For this reason a customer that has a file systems with millions of files, in some cases may experience a Windows CIFS time-out that expires which may result in a write error.

The configuration that has the SDF Database files at the beginning of every surface may see a performance issue in large file systems because it is a single threaded operation but it will be more reliable in disaster recovery because each surface will contain the database and file system structure which will also allow using the dated mount option with more accuracy. Storing the database at the beginning of each volume is more secure because the database is always accessible for the file system.

Configuration 2 During initialization of the second and subsequent volumes in the Integral Volume set the SDF database files are independently compressed (optical Media Only) and written to a separate location (Media or Hard Disk) using a separate thread. This allows access to the file system during the backup procedure increasing performance and reducing the amount of time required to run the backup procedure. This configuration allows the System Administrator the flexibility of storing the SDF backup to different locations as well as additional backups. The new multithreaded SDF migrator supports one thread to handle all client requests to the file system and a second thread for the database backup procedure, which allows satisfying all client requests and performing the database backup procedure simultaneously. Configurable SDF database destinations:

There are now three types of database target locations; they are defined in a special configuration file:

• Current volume: This destination type is the default location of the SDF database files and performs the same operations as Configuration 1. This destination cannot support parallel write operations or multithreading.

• Special volume: SDF backup for media with sequential numbers more than K will be stored on special volumes marked as backup media. Such a model allows doing backup operations simultaneously if the storage library has two or more drives.

• File on native file system: The SDF database can be protected using a native file system (or CIFS/NFS mount point) as a backup destination. Instead of using a separate backup media the database can be saved as a file in a special folder defined in the configuration file. The file can be located on NFS or CIFS file systems.

There are three types of Backup event triggers, Rollover backup and Backup on Time or Space constraints.

of 152

Backup on mirrored volumes: If the backup is performed to a medium in a mirrored SDF Integral Volume set environment, the database backup is written to a medium in the primary and secondary Integral Volume sets. This is true for data base operations to data or special backup volumes. The status of the mirrored volumes can be monitored using Migration View and synchronized using vlcmd startmirr command.

Figure 5.18 - Database Backup Configuration Option

Note: For tape libraries it is required to have an additional drive used to performed database backup in Configuration 2. For other library types QStar recommends having an additional drive in the library for database backup as thrashing can occur.

Please contact your QStar representative for more detailed information on how to configure SDF backup settings.

To configure how the SDF file system performs the backup of the database files, select the Backup DB button. The DB Backup Configuration window will appear.

The DB Backup Destination section allows the System Administrator to choose between storing the database files on a File System or on the Media.

Note: QStar recommends storing the database files to media. Storing the database files to a file system is possible but requires additional administration to prevent the loss of database files due to the possibility of file system failure. Please make sure database files are backed up and not deleted from the specified location.

The Alternative DB Backup Location On File System allows the System Administrator to specify an addition database backup location on a file system.

The First Volume (Surface/Media) Used to Start DB Backup on Separate Media section allows the System Administrator to specify when the SDF file system will begin storing the database files to the DB Backup Destination. The SDF file system will store the database files to the beginning of each volume until the specified number is reached. If 2048 is selected the SDF file system will not backup to the DB Backup Destination.

Leave 2048 in order to use Configuration 1.

The Auto DB Backup (Inactive Days) section specifies when the Integral Volume set will perform a database backup if a database backup has not been performed in the specified number of days.

The Auto DB backup (GB) section allows the System Administrator to specify that after the specified Gigabytes are written to the Integral Volume set the SDF file system will perform the backup of the database. For Tape the setting must be 50 Gigabytes or greater. For Disk this setting is not recommend as more space will be used on the media.

of 152

The System Administrator can monitor all backup and restore operations on all SDF Integral Volume sets from the SDF DB Backup Log view pane. Note: The same information is available on c:\QStar\log\backup-log.xml file.

Figure 5.19 - SDF DB Backup Log

Available Configuration Options

Figure 5.20 - Integral Volume Parameters (Make Copy)

The Readonly, Spread, Quota and Make Copy Of Full Media/Incremental/ Multi-Incremental options are all available with the SDF file system. In the example, an Integral Volume set named Test is created with the SDF file system and rewritable media; Make Copy is set to Incremental. By selecting the Schedule button, a Delayed Job can be created to schedule when the Incremental Media Copy procedure takes place. Alternately, the Incremental Media Copy may be set, or changed by selecting the Properties button for the Integral Volume set on Volume Management and then selecting the Schedule button or modifying the delayed job from Delayed Jobs (See “THE COPY AND COMPARE MEDIA UTILITIES” section later in this chapter for more details).

of 152

Once the Schedule button is selected, the Change Schedule window will appear allowing configuration of the schedule for the Incremental Media Copy. This procedure will determine when this will take place, so it can take place when the library is under less user load, generally outside of normal working hours.

Note: If multiple Integral Volume sets are used, it is advisable to ensure the Incremental Media Copy procedures do not all happen at the same time, as this could lead to excessive media swapping in the library.

Figure 5.21 - Integral Volume Parameters (Change Schedule)

Additional Shredding Options for Optical Compliant WORM and Rewritable Media

Figure 5.22 - Integral Volume Parameters (Shredding)

The shredding operation allows meeting compliance regulations that mandate if a file is deleted from the file system it must be physically removed from the media as well. Enabling and disabling the Shredding option several times may corrupt the file system. QStar recommends using this option with extreme care.

The Mount On Date option, which allows mounting the file system to a specific time and date in the past, will not be available if the Shredding option is enabled.

The shredding operation is available for both the ASM and Data Director (Mirroring) products.

The SDF file system supports the shredding operation in two ways: • Using UDO Compliant WORM media, QStar supports a specific SHRED SCSI command that allows shredding a block

on the media. If Compliant UDO WORM media are added to an Integral Volume set, the Software will detect that they are Compliant WORM media and will automatically send the shred command to the UDO drive for every file deletion on the file system. The option to disable Shredding in the QStar Software will be ignored if selected for Compliant WORM media.

of 152

• Using the Shredding option on Optical rewritable/DVD-RAM/RDX/BD-RE media. If the Shredding option is enabled with rewritable optical/dvd-ram/RDX/bd-re media, the files that are deleted will not be removed logically (which is the default method), the files will be physically deleted by erasing the blocks on the media. These blocks contain the file information and data for the files selected for deletion. This option treats the rewritable media as compliant media.

Additional Compression Option for Tape Archive Media

The Standard Data Format (SDF) file system using Tape media has the additional option of Compression. The Compression option is used to specify the compression setting for the Tape drive and can be set as follows: On = enabled Off = disabled Default = keeps the Default configuration that was set by the drive manufacturer.

Figure 5.23 - Integral Volume Parameters (Compression)

of 152

Tape and Disk Object File System (TDO)

Figure 5.24 - Available File Systems - TDO

The Tape and Disk Object (TDO) is the Primary and High Performance QStar file system. This configuration allows the use of multiple media to be created as a single seamless file system with a magnetic cache.

Note: The options for mirroring are only available if the Data Director product is installed.

Archive Media Type

The Tape and Disk Object (TDO) file system can be used with WORM or rewritable Optical (MO/UDO/PDD) media, rewritable RDX media, Blu-ray (BD-RE, BD-R) media, DVD-RAM media or Tape media. To finish the creation process, select the Create button.


of 152

Database Backup and Tuning Configuration Option

The TDO file system writes the data and metadata sequentially to the media. The metadata information for the files written to the file system are also kept in the TDO database which consists of different files the edb_bbb, edb_dir, edb_ext1, edb_ibk, edb_node, edb_raw, one transaction log file edb_log. These files are located in the cache directory. For more detailed information about the edb_db file, please refer to Chapter 6 - Migration Manager of this manual. The Database Backup and Tuning configuration options are explained in the Displaying and Modifying Integral Volume Set Properties section later in this chapter. Available Configuration Options

Figure 5.26 - Integral Volume Parameters (Make Copy)

The Readonly, Spread, Quota and Make Copy Of Full Media/Incremental/ Multi-Incremental options are all available with the TDO file system. In the example, an Integral Volume set named Test is created with the TDO file system and rewritable media; Make Copy is set to Incremental. By selecting the Schedule button, a Delayed Job can be created to schedule when the Incremental Media Copy procedure takes place. Alternately, the Incremental Media Copy may be set, or changed by selecting the Properties button for the Integral Volume set on Volume Management and then selecting the Schedule button or modifying the delayed job from Delayed Jobs (See “THE COPY AND COMPARE MEDIA UTILITIES” section later in this chapter for more details).

of 152

Once the Schedule button is selected, the Change Schedule window will appear allowing configuration of the schedule for the Incremental Media Copy. This procedure will determine when this will take place, so it can take place when the library is under less user load, generally outside of normal working hours.

Note: If multiple Integral Volume sets are used, it is advisable to ensure the Incremental Media Copy procedures do not all happen at the same time, as this could lead to excessive media swapping in the library.

Figure 5.27 - Integral Volume Parameters (Change Schedule)

Additional Compression and Encryption Option for Tape Archive Media

Figure 5.28 - Integral Volume Parameters (Compression)

Tape and Disk Object (TDO) file system using Tape media has the additional option of Compression. The Compression option is used to specify the compression setting for the Tape drive and can be set as follows: On = enabled Off = disabled Default =On enabled.

of 152

Tape and Disk Object (TDO) file system using Tape media has the additional option of HW Encryption. The HW Encryption option is used to specify the Hardware Encryption setting for the Tape drive and can be set as follows: No Encrypton Default =On enabled.

Figure 5.29 - Integral Volume Parameters (HW Encryption)

of 152

Universal Disk Format (UDF) - (ISO 9660)

Figure 5.30 - Available File Systems - UDF

The Interchange Level defines how many volumes are in the Integral Volume set.

The UDF file system allows three Interchange Level configurations: A) Single-Volume (Used with the UDF and ISO 9660 file systems)

With this configuration, it is possible to configure each media as a single surface file system with a magnetic cache, with each single-volume mounted on a separate local drive. This configuration is primarily used with standalone drives. The QStar Software simulates the Standalone Drive as a virtual library with one shelf, containing a media with a single surface, but may also be used in libraries with single sided media. If dual sided media is used with the Single-Volume configuration only the “A” side will be initialized and used. To use both sides of the media, use the Automount configuration.

B) Automount (Used with UDF and ISO 9660 file systems)

With this configuration, it is possible to configure multiple media as a large file system with a magnetic cache where each surface is a separate file system but mounted under a single local drive.

C) Spanning (Used only with the UDF file system)

With this configuration, it is possible to configure multiple media as a large file system with a magnetic cache where each surface is a single surface file system; aggregately it is seen as one continuously growing hard disk mounted under a single local drive.

of 152

Archive Media Type

The Universal Disk Format (UDF) file system can be used with WORM or rewritable Optical (MO/UDO/PDD) media, rewritable RDX media, Blu-ray (BD-RE) media, DVD-RAM media, CD/DVD-R Blu-ray (BD-R) with Packet Writing, CD/DVD-ROM media pre-recorded with the UDF file system or pre-recorded with ISO 9660, with Rock Ridge and Microsoft extensions. Note: The option for mixed media cd/dvd-r/rom/ram is not available for Spanning Interchange Level.



Figure 5.32 - Integral Volume Parameters

QStar Software support different versions of UDF file system. The versions supported are 1.50, 2.00, 2.01, 2.50 and 2.60. By default the Software will use the version 1.50 because is compatible with the majority of UDF reader present in all Operation System in the market. The System Administrator can select the UDF version from the Revision drop box. The Readonly option is available for all Interchange Levels. For Single-Volume the Quota limit is equal to 1 and for Automount or Spanning the Quota limit is 2048. The Spread option is only available for the Spanning Interchange Level.

By default, the Write Verification is disabled because it will significantly decrease write performance. There are many automatic features within the QStar Software to ensure data integrity. This option was introduced for System Administrators that do not need a fast archiving environment and prefer to have an additional check to ensure data integrity. QStar recommends using Write Verification for CD/DVD-R media when write verification is not implemented at the drive level. If the Write Verification option is enabled, the data is read from the medium into a separate buffer and compared. If medium operations are performed on track-oriented medium (CD-R, DVD-R, BD-R) the whole data buffer is verified. Otherwise, only the last block is compared, because of performance considerations. In both cases the presence of VAT (Virtual Allocation Table) ICB (Information Control Block) in the last data block is verified.

of 152

Additional Options for CD/DVD-R and BD-R Archive Media and Packet Writing

Using the QStar Master Software, CD/DVD-R media can be recorded as disk-at-once and added automatically to an Integral Volume set and seen as separate folders under a single local drive. The Packet Writing option is available when selecting CD/DVD or Blu-ray (BD-R) media as the Archive Media Type. The CD/DVD-R or BD-R media can be added directly to the Integral Volume set only if the Packet Writing option is selected. If Packet Writing is not selected, the adding procedure will be denied and QStar will return an error message of incompatible media type. CD/DVD-ROM media that was pre-recorded with the UDF and ISO 9660 file systems can be added to an Integral Volume set and seen as separate folders under a single local drive.

Figure 5.33 - Integral Volume Parameters (Packet Writing)

of 152

Additional Options for CD/DVD-ROM Archive Media with UDF and ISO 9660 File System

The support for the ISO 9660 file system has been consolidated into the UDF file system. This means that the CD/DVD Axxess (Read Only) product that manages pre-recorded CD/DVD-ROM media with the UDF and ISO 9660 file systems, behaves similar to the ASM Automount product as a Read Only file system for CD/DVD-ROM media. Also with ASM Automount (Read Only) the Integral Volume set is created with a cache and each CD/DVD-ROM is seen as a separate directory within the Integral Volume set. All directory information for the CD/DVD’s in the Integral Volume set will be cached. The data is cached on a most recently accessed basis. The cache can then be configured for each CD/DVD-ROM individually within the Integral Volume set. Each CD/DVD-ROM can have its own directory tree cache and data cache removed from the Integral Volume set, or just its data cache removed. CD/DVD-ROM’s can be added or removed from the Integral Volume set dynamically, even on a mounted set. CD/DVD-ROM’s can be exported from the library on a mounted set and QStar’s offline volume management can be used. This allows the CD/DVD-ROM to appear online after the CD/DVD-ROM has been removed from the library to allow the more frequently accessed CD/DVD-ROM’s to be present in the library.

Choose Automount as the Interchange Level.

Choose cd/dvd-r/dvd-rom as the Archive Media Type. Place a check mark in the Readonly box.

The UDF and ISO 9660 file systems used with the CD/DVD-ROM media is used as a read only file system.

The Readonly check MUST be applied to mount the Integral Volume set with QStar CD/DVD Axxess product. If the check mark is not applied, the mount will be denied.

Note: Trying to add CD/DVD-R (blank) to a read only Integral Volume set is not allowed and will generate an error.

Figure 5.34 - Integral Volume Parameters (Packet Writing)

of 152

Additional Options for Single-Volume and Automount Interchange Level

Figure 5.35 - Integral Volume Parameters (Automount and Single-Volume)

The Single-Volume Interchange Level should only be used with a standalone drive. This configuration will create a UDF file system on a single surface of the media only. The file system is limited to the single surface size of the media being used.

Note: If this configuration is used in a library with dual sided media, it will require exporting the media, flipping the media manually and then importing the media back into the library to use the second side of the media. However, if single sided media is used the library will function correctly.

The Automount Interchange Level can also be used with a standalone drive.

The QStar Software, in Automount and Single-Volume Interchange Level, by default will turn on Space Calculation in order to prevent accepting data into the cache if there is not enough space on the surface.

The Space Calculation will slow down the write performance at the end of the surface but will prevent accepting data into the cache which cannot be written to the surface. If the Space Calculation is disabled and there is not enough space, a covered error will be generated and the write procedure will be interrupted until the files that cannot be written to the surface are manually removed from the cache.

This option was introduced for applications that will make their own calculation regarding the amount of data that will be written on the surface, so there is no need to use QStar Space Calculation. For example, some applications will write data until 98% of the capacity of the surface is reached.

The Space Calculation option is not applicable to a Spanning Integral Volume set, as media is dynamically added as required.


of 152

Additional Options for Spanning Interchange Level

Figure 5.37 - Integral Volume Parameters (Spanning)

The Spanning Interchange Level, allows media to be dynamically added when a sequence is full, but still maintains UDF compliance. The File Spanning option is enabled by default and specifies if a file can span across to the next media or the remaining space on the media will be lost and the file will be completely written to the next sequence (media) in the Integral Volume set. If disabled and the file is larger than 200 MB, the file will always be spanned (the value of 200 MB is configurable under control of QStar personnel support). The Use Image Backup option is specific to a Spanning Interchange Level with CD/DVD-R media; it is enabled by default and creates an image backup of the current write surface in the cache root directory.

The Close Full Volume option will automatically close the media or surface once it is full. The Make Copy Of Full Media and Make an Automatic Incremental or Multi-Incremental Copy option are specific to a Spanning Interchange Level with CD/DVD-R, Blu-ray (BD-R) and WORM or rewritable media and will be available only if Close Full Volume option is enabled. See THE COPY AND COMPARE MEDIA UTILITIES section later in this chapter for more details.


of 152

Linear Tape File System (LTFS)

Figure 5.39 - Available File Systems - LTFS

The Interchange Level defines how many volumes are in the Integral Volume set. The LTFS file system allows four Interchange Level configurations:

The LTFS file system allows four Interchange Level configurations: A) Direct-Single-Volume

With this configuration, it is possible to configure each media as a single media file system without a magnetic cache, with each single-volume mounted on a separate local drive. This configuration is primarily used with standalone drives, but may also be used in a library. B) Single-Volume

With this configuration, it is possible to configure each media as a single media file system with a magnetic cache, with each single-volume mounted on a separate local drive. This configuration is primarily used with standalone drives. The QStar Software simulates the Standalone Drive as a virtual library with one shelf containing one media, but may also be used in a library. C) Automount

With this configuration, it is possible to configure multiple media as a large file system with a magnetic cache where each surface is a separate file system but mounted under a single local drive. D) Spanning

Multiple media are viewed as a large file system with a magnetic cache where each surface is a separate file system but, aggregated as a unique single file system mounted under a single local drive. With this preferred configuration, it is possible to configure multiple media as a large file system with a magnetic cache where each media is a single file system; it is aggregated and seen as one continuously growing hard disk mounted under a single mount point.

LTFS volumes can be organized in a multi-volume spanning Integral volume set. Such Integral Volume set is visible as a single file system where directories and files can span several volumes. At the same time, each volume is a valid LTFS file system, which can be mounted separately as a single-volume LTFS.

LTFS spanning Integral Volume set requires some extra information (volume spanning information) stored on every spanning volume under directory /.QSTAR_VSKIN. Files under this directory are used for maintaining spanning database and not visible

of 152

to the user if the volume is in the mounted spanning Integral volume set. They are visible if the volume is removed from the spanning set and mounted separately as a single-volume LTFS. Functioning of the spanning Integral Volume set is based on a special spanning database stored in the cache and backed up on spanning volumes. The database contains metadata information: directory entries, file attributes, file extent locations, special streams, symlink targets, btree chunks. With spanning database, any access to metadata is made without accessing the actual volumes, they are accessed only when new information is written into the Integral Volume set or when the file data has to be read. Archive Media Type

The Linear Tape File System (LTFS) file system can be used only with library and standalone drives that support rewritable LTO-5 and beyond and other tape media, such as T10000C or TS1140.




The Readonly option is available for all Interchange Levels. For Direct-Single-Volume, Single-Volume the Quota limit is equal to 1 and for Automount or Spanning the Quota limit is 2048. The Spread option is only available for the Spanning Interchange Level.

of 152

Additional Options for Direct-Single-Volume

To use LTFS directly without QStar cache choose Direct-Single-Volume as the Interchange Level.

Direct-Single-Volume Interchange Level can be used with a standalone drives and with library as well but the resulting file system is confined to the single volume. The single volume LTFS file system will be created on the tape and operations will be executed directly on the physical tape. The Direct-Single-Volume Interchange Level provides better performance once tape is loaded into drive but is less flexible when small files are frequently accessed. Even though this configuration does not use a QStar cache, a cache size and cache location MUST be specified in the Integral Volume set creation. This is due to LTFS requiring a disk location in order to place temporary files.

To finish the creation process, select the Create button.

Figure 5.42 - Integral Volume Parameters (Direct-Single-Volume)

Additional Options for Single-Volume and Automount Interchange Level


The Single-Volume Interchange Level is suited for use with a standalone drive. This configuration will only create a LTFS file system on a single media. The file system is limited to the single media size used. The Single-Volume Interchange Level can be used also with a library and the Automount Interchange Level can also be used with a standalone drive. Note: This configuration can be used also with a library. The Automount Interchange Level can also be used with a standalone drive.

of 152

The QStar Software, in Automount and Single-Volume Interchange Level, by default will turn on Space Calculation in order to prevent accepting data into the cache if there is not enough space on the surface. The Space Calculation will slow down the write performance at the end of the surface but will prevent accepting data into the cache which cannot be written to the surface. If the Space Calculation is disabled and there is not enough space, a covered error will be generated and the write procedure will be interrupted until the files that cannot be written to the surface are manually removed from the cache. This option was introduced for applications that will make their own calculation regarding the amount of data that will be written on the surface, so there is no need to use QStar Space Calculation. For example, some applications will write data until 98% of the capacity of the surface is reached. The Space Calculation option is not applicable to a Spanning Integral Volume set, as media is dynamically added as required.


Additional Options for Spanning Interchange Level


The Spanning Interchange Level, allows media to be dynamically added when a sequence is full, but still maintains LTFS compliance.

of 152

The File Spanning option is disabled by default and specifies if a file can span across to the next media or the remaining space on the media will be lost and the file will be completely written to the next sequence (media) in the Integral Volume set. If disabled and the file is larger than 10GB, the file will always be spanned if is not already completely in the cache. The Make Copy Of Full Media option is specific to a Spanning Interchange Level. See THE COPY AND COMPARE MEDIA UTILITIES section later in this chapter for more details.


of 152

Universal File System (UVFS) - Plasmon PFS/AFS File Systems The QStar Universal File System (UVFS) file system supports Read Only access to the following three Plasmon file systems:




The availability of the Plasmon PFS/AFS file system is only on Windows 32 bit platform.

Figure 5.47 - Available File Systems - UVFS (PFS/AFS)

The Interchange Level defines how many volumes are in the Integral Volume set.

The UVFS file system allows three Interchange Level configurations: A) Single-Volume

With this configuration, it is possible to configure each media as a single media file system with a magnetic cache, with each single-volume mounted on a separate local drive. This configuration is primarily used with standalone drives. The QStar Software simulates the Standalone Drive as a virtual library with one shelf containing one media, but may also be used in a library. B) Automount

With this configuration, it is possible to configure multiple media as a large file system with a magnetic cache where each surface is a separate file system but mounted under a single local drive. C) Spanning

With this preferred configuration, it is possible to configure multiple media as a large file system with a magnetic cache where each media is a single file system; it is aggregated and seen as one continuously growing hard disk mounted under a single local drive.

of 152

Archive Media Type

The Universal File System (UVFS) can be used with WORM or rewritable Optical (MO/UDO) media, DVD-RAM media or CD/DVD-ROM.




For Spanning and Automount Interchange Levels the available option is Quota. For Single-Volume the Quota limit is equal to 1 and for Automount or Spanning the Quota limit is 2048. The Spread option is working only for the Spanning Interchange Level.

of 152

Archive Appliance File System (AAFS) - Plasmon AA File System

Figure 5.50 - Available File Systems - AAFS

The Archive Appliance File System (AAFS) supports Read Only access to the AA Plasmon file system.

Archive Media Type

The Archive Appliance File System (AAFS) allows to can be used with WORM or rewritable Optical UDO media. To finish the creation process, select the Create button.


of 152

No Media File System

Figure 5.52 - Available File Systems - No Media

The QStar Software can be configured to create an Integral Volume set with No Media, this allows data to be written to a cache as normal, but the data will not be archived and therefore not secured. A library or standalone drive can be added at a later date, then the media can be added to the Integral Volume set and the data synchronized from the cache to the media. The cache can be synchronized only with an Integral Volume set with TDO, SDF, LTFS/UDF Spanning file systems.

Archive Media Type with Simulated Media and Centera Libraries QStar Software allows the use of physical disk space available on a Hard Drive (Hard Disk, RAID, DAS) or EMC Centera to be used as media loaded into a Simulated Library for an Integral Volume set. The Hard Drive or EMC Centera may be partitioned as such to simulate virtual shelves. The QStar Software offers Disk and Tape Simulated Libraries on the Hard Drive and EMC Centera, The Simulated Archive Media Type available are the following : HD-SDisk-Rewr: Simulated Hard Drive Disk rewritable media. HD-SDisk-Worm: Simulated Hard Drive Disk WORM media. HD-STape: Simulated Hard Drive Tape WORM media. C-SDisk-Worm: Simulated Centera Disk WORM media. C-STape: Simulated Centera Tape WORM media.

Figure 5.53 - Integral Volume Parameters (Archive Media Type)

of 152

Displaying and Deleting an Integral Volume Set

Figure 5.54 - Displaying and Deleting an Integral Volume Set

The creation process is now complete. Volume Management displays the Characteristics of the Integral Volume set. When multiple Integral Volume sets are configured, access them using the drop bar and selecting the appropriate Integral Volume set name. Choosing the appropriate Integral Volume set name from the drop bar and selecting the Delete button can delete an Integral Volume set. The File System Type information for an Integral Volume set with UDF or UVFS file system will also display the UDF Revision Level and the Interchange Level information, for LTFS display only the Interchange Level.

Note: Deleting an Integral Volume set does not remove automatically the cache (will be asked if need to be removed), or delete any data from the archive media, if the media is rewritable, it may be erased, if it is WORM, the data cannot be altered.

of 152

Displaying and Modifying the Integral Volume Set Properties

Integral Volume Set Common Properties To alter the properties of an Integral Volume set, in Volume Management view pane select the appropriate Integral Volume set name and then select the Properties button. In the Properties window, the High Primary Capacity and Low Primary Capacity can be changed for the Integral Volume set. The High Primary Capacity (HPC) is the point at which the software will start demand archiving based on a % value of the allocated cache size. Default is 80%. The Low Primary Capacity (LPC) is the point at which the software will stop demand archiving based on a % value of the allocated cache size. Default is 0%. The (HPC) and the (LPC) have no effect on an Integral Volume set with ISO 9660, AAFS or UVFS file systems because it is mounted in read only mode.

Figure 5.55 - Integral Volume Set Properties

Common Properties:

• The Mount As drop box allow to change the local drive letter used to mount the file system.

• Share drive option allows to share by default the file system in the network.

• Placing a check in the Mount On Server Restart block allows automatic mounting of the Integral Volume set on the Server Restart.

Cache Properties: • The Cache Location can be changed by selecting the Browse button. • Changing the value in the Cache Size block alters the size of the Cache for an Integral Volume set. The Cache Size

can be only increased.

• The cache Page Size can be changed with the drop down selection, a Page Size from 1KB to 256 KB may be selected. Changing the value in the Page Size block alters the size of the cache pages for an Integral Volume set. When the Page Size is altered, a check must be placed in the Clean cache block. Placing a check in the Clean cache block will rebuild all the files in the Cache Location directory for the Integral Volume set.

of 152

The procedure to modify the Cache size or Page Size of an Integral Volume set is a delicate procedure and must be carried out carefully. If is not done correctly, it can destroy the primary data (data not yet written to the media) present in the cache. Before mounting with a clean cache, be sure that no Primary data, or delayed events are present. If Primary data is left in the cache, it will be destroyed during the next mount. QStar suggests not altering the size of the cache unless it is necessary.

Note: An Integral Volume set created with ISO 9660, AAFS or UVFS file system cannot have Primary data because it is mounted in read only mode.

• The Stop on covered error option (enabled by default) if disabled, allows data to continue to be written to a large cache even if there is a covered error; this option determines if service to the users is stopped or continued while the problem causing the covered error is rectified.

• Advanced options are already explained in the Integral Volume Set Creation section.

Media Properties:

• The Quota (maximum number of media allowed in an Integral Volume set) can be changed. The default number of the media is 2048.

• Mixed Media option allows Real and Simulated Media to be mixed in the same Integral Volume set (not available for all file systems).

On next mount Properties:

• The Readonly option allows mounting a file system in read only mode (not available if file system is already read only).

• Placing a check in the Rebuild database block will rebuild all the *_db files (file system database files) in the Cache Location directory. This option MUST be used under QStar support personnel control because a misusage of this option can generate file system inconsistency.

• Placing a check in the Clean cache block will rebuild all the files in the Cache Location directory for the Integral

Volume set. This option for the read and write file systems must be used carefully. Before mounting with a clean cache, be sure that no Primary data is present. If Primary data is left in the cache, it will be destroyed during the next mount.

• Placing a check in the Force Mount block will mounts the Integral Volume set even if there is a possible

inconsistency between cache, file system databases and media. This option should be used if the Integral Volume set definition is recreated from scratch and cache file are not new. Software will detect date inconsistency and will print message to use force mount option to be sure that is what the System Administrator want. Use this option with caution, the result may be undesirable.

• Placing a check in the Local access only block will allow access to the Integral Volume set on the local host only. Note: All changes made in these properties will take effect once the Integral Volume set is remounted. The Rebuild database and Clean cache options are set only once for the next mount and all the others options are set permanently. For Advanced, Mount On Date and NFS Access options please refer to Chapter 6 - Migration Manager in this manual.

of 152

Integral Volume Set SDF Specific Properties

Figure 5.56 - Integral Volume Set SDF Specific Properties

Selecting Schedule and Copy Properties is possible to configure Incremental or Multi-Incremental Media Copy. Please, refer to THE COPY AND COMPARE MEDIA UTILITIES section for more detailed information later in this chapter. Mixed Media option is available for SDF file system. Selecting Backup DB allows changing the default location and parameters of the SDF database. Selecting Restore DB allows restoring the SDF database. Selecting Shredding allows Enabled or Disabled shredding option for rewritable optical/dvd-ram/RDX/bd-re media.

Note: All changes made in these properties will take effect once the Integral Volume set is remounted. The Rebuild database option is set only once for the next mount and the Readonly option is set permanently.

SDF Database Restore allows the SDF database to be restored from the Alternative DB Backup Location On File System. The Alternative DB Backup Location On File System setting is located in the Backup DB properties.

The Directory Path by default looks at the Alternative DB Backup Location On File System setting. Select the Change Path button to select a different directory.

The IVS Database Restore will display a list of available databases. Highlighting one of the available rows and then selecting the OK button will restore the database from this backup. Usually the last back up should be used.

Note: The options Force Rescan and Verbose are available only for AAFS file system.

Note1: Please contact your QStar representative for more detailed information before restoring the database.


of 152


This option converts SDF Integral Volume set to TDO type. Practically converts SDF Database and Integral Volume set definition on the into TDO Database and TDO Integral Volume set. All SDF media will be moved to new TDO Integral Volume set and will be available in read only mode. The Integral Volume set must be unmounted. The operation duration depends from SDF database size (entry number, file size, ...). Mirror SDF Integral Volume set will be converted to mirror TDO Integral Volume set. Force SDF database restore from media before conversion. Background mode option: The operation will be executed in background mode.

For Integral Volume sets created with Tape media and the SDF file system, the Compression option is also available. The Compression option is related to the compression setting for the Tape Drives and is described as follows: Default: The compression is set as default on the Tape Drive. On: Enable the compression. Off: Disable the compression. Note: The Compression option is set permanently and will take effect once the Integral Volume set is remounted.


Note: For more detailed information of the options available on the Properties windows, please refer to the above Creating an Integral Volume Set, Available File Systems and Archive Media Type sections.

of 152

Integral Volume Set TDO Specific Properties

Figure 5.60 - Integral Volume Set TDO Specific Properties

Selecting Schedule and Copy Properties is possible to configure Incremental or Multi-Incremental Media Copy. See THE COPY AND COMPARE MEDIA UTILITIES section later in this chapter for more details. Mixed Media option is available for TDO file system. Selecting Tuning the system Administrator will access to the Advance Configuration editor that allows modifying the default configuration parameters for TDO file system. Note: All changes made in these properties will take effect once the Integral Volume set is remounted. The Rebuild database option is set only once for the next mount and the Readonly option is set permanently.

The Advance Configuration editor include several setting for logging and debugging. The Main Advanced Configurations options for TDO are the following: wpc - write pool count. This is a number of buffers used to send data through network. rpc - read pool count. Number of buffers allocated to read objects from storage. Extent-size -The size of object to be written to the storage. Prefetch - Number of read-ahead buffers for a file. Verification - The object consistency verification method. XOR-4 by default. Sync-timeout - Time to perform checkpoint with CFS. Full-backup-size - Trigger data base backup based on data capacity written. Full-backup-period - Trigger data base backup based on time.


The frequency that the database is saved to the archive storage is configurable. By default the database will be saved every 50 GB of data written to the archive storage or every day. QStar highly recommends that these options are not modified without the help and support of QStar Technical personnel.

of 152


Also logging can be enabled for the TDO file system. Select as value debug to turn non logging and none to turning off logging.

For Integral Volume sets created with Tape media and the TDO file system, the Compression option is also available. The Compression option is related to the compression setting for the Tape Drives and is described as follows: Default: The compression is set as default on the Tape Drive. On: Enable the compression. Off: Disable the compression. Note: The Compression option is set permanently and will take effect once the Integral Volume set is remounted.


of 152


For Integral Volume sets created with Tape media and the TDO file system, the HW Encryption option is also available. The HW Encryption option is used to specify the Hardware Encryption setting for the Tape drive and can be set as follows: No Encrypton Default =On enabled.


of 152

Integral Volume Set UDF Specific Properties

Properties available for Single-Volume or Automount Interchange Level. Placing a check in the Space Calculation block will ensure the cache does not contain more Primary data than space available on the archive media. This will reduce overall performance. Placing a check in the Packet Writing block enables Packet Writing on CD/DVD-R and Blu-ray (BD-R) media. This option is only available for cd/dvd-r/rom, cd/dvd-r/rom/ram and bd-r. Placing a check in the Write Verification block forces verification of data written, recommended if the drive does not support write/verify. This will reduce overall performance, but will ensure data integrity.

Note: The Make Copy option is not available for the UDF file system with Single-Volume and Automount Interchange Level.

For Grace Period, Retention Period and NFS Access options please refer to Chapter 6 - Migration Manager in this manual.

Figure 5.65 - Integral Volume Set UDF Specific Properties

Figure 5.66 - Integral Volume Set UDF Specific Properties

Properties available for Spanning Interchange Level. The Close Full Volume option will automatically close the media or surface once it is full. The Use Image Backup option is specific to a Spanning Interchange Level with CD/DVD-R media; it is enabled by default and creates an image backup of the current write surface in the cache root directory. The Make Copy Of Full Media option is specific to a Spanning Interchange Level with CD/DVD-R, Blu-ray (BD-R) and WORM media and will be available only if Close Full Volume option is enabled.


of 152

Integral Volume Set LTFS Specific Properties

Properties available for Single-Volume or Automount Interchange Level. Placing a check in the Space Calculation block will ensure the cache does not contain more Primary data than space available on the archive media. This will reduce overall performance. Note: No additional options are available for Direct-Single-Volume. The Make Copy option is not available for the LTFS file system with Single-Volume and Automount Interchange Level.

For Advanced and NFS Access options please refer to Chapter 6 - Migration Manager in this manual.

Figure 5.67 - Integral Volume Set LTFS Specific Properties


Properties available for Spanning Interchange Level. The Make Copy Of Full Media option is specific to a Spanning Interchange Level. Selecting Tuning the system Administrator will access to the Advance Configuration editor that allows modification of the default configuration parameters for LTFS file system.


of 152

The Advance Configuration editor include several setting for logging and debugging. The Main Advanced Configurations options for LTFS are the following: max_block_size actual drive count QStar highly recommends that these options are not modified without the help and support of QStar Technical personnel.


of 152

Integral Volume Set UVFS and AAFS Specific Properties

Figure 5.70 - Integral Volume Set UVFS Specific Properties

No specific properties are present for UVFS. For NFS Access option please refer to Chapter 6 - Migration Manager in this manual.

AAFS file system has the option to restore the database of the media. This option must be used at first mount if not file system will be empty. IVS Database Restore allows restoring the AAFS database from the Alternative DB Backup Location On File System. The Alternative DB Backup Location On File System setting is located in the Backup DB properties. The Directory Path by default looks at the Alternative DB Backup Location On File System setting. Select the Change Path button to select a different directory. The IVS Database Restore will display a list of available databases. Highlighting one of the available rows and then selecting the OK button will restore the database from this backup. Usually the last back up should be used. Note: Please contact your QStar representative for more detailed information before restoring the database.

Figure 5.71 - Integral Volume Set AAFS Specific Properties

of 152

Adding Media to a TDO or SDF or AAFS Integral Volume Set

Figure 5.72 - Media Management (Adding Media)

Media Management displays all available media in the right list-box. This media can be added to an Integral Volume set. A media is considered available when it is erased, blank or is initialized with SDF or TDO or AAFS file system. The left list-box displays all the media that are already associated with the currently selected Integral Volume set. When multiple Integral Volume sets or Libraries are configured, access them by using the associated drop bar and selecting the appropriate Integral Volume set name or Library Name. To add media to a newly created or existing Integral Volume set select the appropriate Integral Volume set name, Highlight the media in the right list-box and click the left arrow button or double click on the media. The media will move to the left list-box.

The media is now added to the Integral Volume set. In the example, the media in shelf 1 was added to the Integral Volume set Test.

Figure 5.73 - Volume Management (Adding Media)

of 152


All media that have been added to the Integral Volume set will now appear in Volume Management under the appropriate Integral Volume set name. In the example, the media imported to shelf 1 in library JB0 was added to the Integral Volume set Test. The Integral Volume set is now ready to mount by selecting the Mount button.

Adding Media to an UDF or UVFS (PFS/AFS) Integral Volume Set Media Management displays all the available media in the right list-box that can be added to an Integral Volume set. A media is considered available when it is erased, blank or is initialized with an UDF, ISO 9660 or UVFS (PFS/AFS) file systems. The left list-box displays all the media that are already associated with the currently selected Integral Volume set. When multiple Integral Volume sets or Libraries are configured, access them by using the associated drop bar and selecting the appropriate Integral Volume set name or Library Name. To add media to a newly created or existing Integral Volume set select the appropriate Integral Volume set name, Highlight the media in the right list-box and click the left arrow button or double click on the media. The media will move to the left list-box. Note: In the example, an UDF Integral Volume set is used.


of 152

• Adding blank/erased media with the UDF file system When a blank or erased media is added to the Integral Volume set, every surface will be initialized using the UDF file system with a unique Set_id number (Logical Volume Identifier). By default, this unique Set_id number is equal to “q_number” for Single Volume and Automount and is equal to “q_number-N” where N is the span_number in the Integral Volume set for Spanning configuration. Once initialized the Set_id written also become the Volume Label of the media. In the Automount configuration the Automount_sequence_numbers is displayed, it represents the sequence number of the surfaces in the root directory of the file system once it is mounted. All media (surfaces) added to the Integral Volume set will be displayed as sub-directories in the root directory of the file system and will be named by default as vol_Automount_sequence_number (i.e. vol_0, vol_1, vol_#). • Adding already initialized media with the UDF and ISO 9660 file systems When a media already initialized with the UDF or ISO 9660 file system is added to the Integral Volume set with the Automount configuration, the Set_id is equal to the Volume Label. All media (surfaces) added to the Integral Volume set will be displayed as sub-directories in the root directory of the file system and will be named by default as the Volume Label. If there is no label on the media, the Volume Label is assigned as “NO_NAME” and will be used as the sub-directory name. If two media with the same Volume Label were imported into the library, the Volume Label is duplicated within the Integral Volume set with Automount configuration; the latter occurrence will be displayed vol_Automount_sequence_number (i.e. vol_0, vol_1, vol_#) as sub-directories name in the root directory of the file system instead of the original Volume Label. In Single Volume or Spanning configurations the file system will be displayed as a linear file system, there will be no sub-directories in the root directory of the file system unless they are created by the user. • Adding already initialized media with the UVFS (PFS/AFS) file system When a media already initialized with the UVFS (PFS/AFS) file system is added to the Integral Volume set with the Automount configuration, the Set_id is equal to the Volume Label. Only media that has UVFS file system on both sides and media that has UVFS file system on the first side and a blank/erased surface on another side is allowed to be added. All media (surfaces) added to the Integral Volume set will be displayed as sub-directories in the root directory of the file system and will be named by default as the Volume Label. If the Volume Label contains “\” at front then the symbol will be removed. If there is no label on the media, the Volume Label is assigned as “NO_NAME” and will be used as the sub-directory name. If two media with the same Volume Label were imported into the library, the Volume Label is duplicated within the Integral Volume set with the Automount configuration, the latter occurrence will be displayed as “S_N[A|B]” as sub-directories name in the root directory of the file system. Where S is the Integral Volume set name, N is the Automount_sequence_number (number of the media in the set) and A|B is side identifier. In case side A has label “S_NB” then label for side B will be changed to “S_G”, where S is the Integral Volume set name and G is Plasmon volume tag of the UVFS surface (number with 10-14 digits). It is not possible to add a media with duplicated Plasmon volume tag to UVFS Integral Volume set. In Single Volume or Spanning configurations the file system will be displayed as a linear file system, there will be no sub-directories in the root directory of the file system unless they are created by the user.

of 152





of 152

Adding Media Specifying the Logical Volume ID


To add media to a newly created or existing Integral Volume set specifying the Logical Volume Identifier, select the appropriate Integral Volume set name, remove the check mark from the Use Default Logical Volume ID box (By default the check mark is present), Highlight the media in the right list-box and click the left arrow button or double click on the media. The media will move to the left list-box. The option to Use Default Logical Volume ID is available for all Interchange Levels when using the UDF or the ISO 9660 file system and only for Automount Interchange level for UVFS file system.

Note: In the example, an UDF Integral Volume set is used.

An additional window will open for each media selected. From this window change the Logical Volume Identifier.

Note: For single sided media, only the side A will be prompted for.

Note1: Select the Cancel button and the media will keep the default properties.


of 152

• Adding Blank/erased media with the UDF file system When a blank or erased media is added to the Integral Volume set every surface will be initialized using the UDF file system with a unique Set_id number (Logical Volume Identifier). The specified Logical Volume Identifier entered into the Logical Volume Identifier window, will be written to the media (surface) as a unique Volume Label. All media (surfaces) added to the Integral Volume set will be displayed as sub-directories in the root directory of the file system and will be named as the Logical Volume Identifier specified. In Spanning configurations the specified Logical Volume Identifier will be applied only to the first media, once set, only the span_number will change for the additional volumes added to the Integral Volume set.

• Adding already initialized media with the UDF, ISO 9660 and UVFS file systems

When a media already initialized with the UDF, ISO 9660 and UVFS file system is added to the Integral Volume set with the Automount configuration, the Set_id is equal to the Volume Label. The specified Logical Volume Identifier entered into the Logical Volume Identifier window, will not be written to the surface 0 but will only change the default (vol_0, vol_1 and vol_# or Volume Label) sub-directory names in the root directory of the file system with the one specified. This means that if the media was written with various volume ID’s on each media, it can be added in a more logical format. The new sub-directories name will be printed in the Integral Volume set information for each surface as “A_dir=” and “B_dir=”.

The specified Logical Volume Identifier will be ignored if specified with already written media with Single Volume or Spanning configurations.



of 152

In the example, media in shelf 1 was added to the Integral Volume set Test. The new Logical Volume ID specified previously is now displayed in the Integral Volume set information. In the example, A_dir=Volume-lA and B_dir=Volume-1B has been applied to the A and B sides of the media respectively.


of 152

Adding Media to an LTFS Integral Volume Set


Media Management displays all available media in the right list-box that can be added to an Integral Volume set. A media is considered available when it is erased or is initialized with LTFS file system. The left list-box displays all the media that are already associated with the currently selected Integral Volume set. When multiple Integral Volume sets or Libraries are configured, access them by using the associated drop bar and selecting the appropriate Integral Volume set name or Library Name. To add media to a newly created or existing Integral Volume set select the appropriate Integral Volume set name, Highlight the media in the right list-box and click the left arrow button or double click on the media. The media will move to the left list-box. Note: In the example, an Automount LTFS Integral Volume set is used.

• Adding erased media with the LTFS file system When an erased media is added to the Integral Volume set, every media will be initialized using the LTFS file system with a unique Set_id number (Volume Name). By default, this unique Set_id number is equal to “q_number” for Direct-Single Volume, Single-Volume and Automount and is equal to “span-I-N” (I is 16 hexadecimal digits representing set Id and N is the spanning volume number) for Spanning configuration. Once initialized the Set_id written also become the Volume Name of the media. In the Automount configuration the Automount_volume_number is displayed, it represents the sequence number of the media in the root directory of the file system once it is mounted. All media added to the Integral Volume set will be displayed as sub-directories in the root directory of the file system and will be named by default as vol_Automount_volume_number (i.e. vol_1, vol_2, vol_#). • Adding already initialized media with the LTFS file system When a media already initialized with the LTFS file system is added to the Integral Volume set with the Automount configuration, the Set_id is equal to the Volume Name. All media added to the Integral Volume set will be displayed as sub-directories in the root directory of the file system and will be named by default as the Volume Name. If two media with the same Volume Name were imported into the library, the Volume Name is duplicated within the Integral Volume set with Automount configuration; the latter occurrence will be displayed Vol_automount_volume_number (i.e. vol_1, vol_2, vol_#) as sub-directories name in the root directory of the file system instead of the original Volume Name. In Direct-Single-Volume, Single-Volume or Spanning configurations the file system will be displayed as a linear file system, there will be no sub-directories in the root directory of the file system unless they are created by the user.

of 152





of 152

Adding Media to an LTFS Integral Volume Set Specifying the Volume Name To add media to a newly created or existing Integral Volume set specifying the Volume Name, select the appropriate Integral Volume set name, remove the check mark from the Use default directory name box (By default the check mark is present), Highlight the media in the right list-box and click the left arrow button or double click on the media. The media will move to the left list-box. The option to Use default directory name, except Direct-Single-Volume, is available for all other Interchange Levels when using the LTFS file system.

Note: In the example, an Automount LTFS Integral Volume set is used.



An additional window will open for each media selected. From this window change the Volume Name. Note: Select the Cancel button and the media will keep the default properties.

of 152

• Adding erased media with the LTFS file system When an erased media is added to the Integral Volume set every media will be initialized using the LTFS file system with a unique Set_id number (Volume Name). The specified Volume Name entered into the Volume Name windows, will be written to the media as a unique Volume Name. All media added to the Integral Volume set will be displayed as sub-directories in the root directory of the file system and will be named as the Volume Name specified. In Spanning configurations the specified Volume Name written on the tape is “span-I-N-name” where “name” is the name entered into the Volume Name windows and “span-I-N” (I is 16 hexadecimal digits representing set ID and N is the spanning volume number). • Adding already initialized media with the LTFS file system When a media, already initialized with the LTFS file system, is added to the Integral Volume set with the Automount configuration, the Set_id is equal to the Volume Name. The Volume Name entered into the Volume Name windows, will not be written to the media but will only change the default (vol_1, vol_2 and vol_# or Volume name) sub-directory names in the root directory of the file system with the one specified. This means that if the media was written with various volume ID’s on each media, it can be added in a more logical format. The new sub-directories name will be printed in the Integral Volume set information for each surface as “Dir=”. The specified Volume Name will be ignored if specified with already written media with Single-Volume or Spanning configurations.



of 152



of 152

Displaying Integral Volume Set Information The characteristic information for an Integral Volume set was already explained in the example above when the Integral Volume set was created. To explain the additional information for an Integral Volume set the examples below will consider the Integral Volume set as mounted with media added to it. All the Characteristics of an Integral Volume set are displayed in Volume Management view pane.

Figure 5.89 - Volume Management

Online = JB0:1 or Offline = firesafe: Displays the status of the media belonging to the Integral Volume set. If the status is Online, the library and shelf the media were imported to, are displayed. If the status is Offline the offline location that was specified by the System Administrator is displayed.

Published a, or Published a,b: Displays which surfaces (a and b) of the media are currently mounted (ready to be accessed). For single surface media only “a” will be displayed.

File System Type: Displays the file system used, “tdo”, “sdf”, “lfts,direct-single-volume”, “lfts,single-volume”, “ltfs,automount”, ltfs,spanning” “aafs”, uvfs,single-volume”, “uvfs, automount”, uvfs,spanning” or “udf,150, single-volume”, “udf,150, automount”, udf,150, spanning” where “1.50” is UDF version used by default.

Number of Media: The current number of media present in the Integral Volume set.

Mount State: Displays the current mount state, as mounted or unmounted.

Cache Location: Location of the cache.

Cache Size: Size of the cache.

Media Type: Displays the media type in the Integral Volume set, this may be rewritable or WORM Optical (MO/UDO/ PDD), dvd-ram, blu-ray, tape, cd/dvd-r/ rom or cd/dvd-r/rom/ram, rewritable (RDX) or simulated media.

in_set_number=0: The sequential number the QStar Software associates to each media added to the Integral Volume set.

Note: In the example, an Integral Volume set with TDO file system is used.

• The specific additional parameters for Integral Volume set are described as follows: TDO - “Sequence_numbers=0,1”: The surface sequence_number for the media belonging to the Integral Volume set SDF - “Sequence_numbers=0,1”: The surface sequence_number for the media belonging to the Integral Volume set UDF - “Sequence_number=0”: The surface sequence_number for the media belonging to the Integral Volume set with

Single-Volume Interchange Level. “Automount_sequence_numbers=0,1”: The surface Automount_sequence_numbers for the media belonging to the Integral Volume set with Automount Interchange Level, represents the sequence number of the surfaces in the root directory of the file system once it is mounted. All sub-directories will be labelled as vol_0, vol_1, vol_# by default, or can be changed by deselecting the check box Use Default Logical Volume ID in Media Management.

of 152

“Span_numbers=1,2”: The surface span_numbers for the media belonging to the Integral Volume set with Spanning Interchange Level.

UVFS - “ID = #”: The surface ID number for the media belonging to the Integral Volume set.

AAFS - “ID = #”: The surface ID number for the media belonging to the Integral Volume set.

LTFS - “Vol_UUID= #”: The Vol_UUID number for the media belonging to the Integral Volume set with Direct-Single-Volume Interchange Level. “Single_volume_number=0”: The volume_number for the media belonging to the Integral Volume set with Single-Volume Interchange Level. “Automount_volume_number=1”: The Automount_volume_number for the media belonging to the Integral Volume set with Automount Interchange Level, represents the volume name of the media in the root directory of the file system once it is mounted. All sub-directories will be labelled as vol_1, vol_2, vol_# by default, or can be changed by deselecting the check box Use default volume name in Media Management. “Span_number=1”: The span_number for the media belonging to the Integral Volume set with Spanning Interchange Level.

of 152

Removing Media from a TDO/SDF and LTFS Spanning Integral Volume Set

To remove media from an existing Integral Volume set, select the appropriate Integral Volume set name, Highlight the media in the left list-box and click the right arrow button or double click on the media. The media will move to the right list-box. The remove operation with the TDO/SDF or LTFS Spanning file system can be done only in the case of media error and under specific guidance of QStar Customer support personnel. In the example, the media in shelf 2 will be removed from the Integral Volume set Test.

Figure 5.90 - Media Management (Removing Media)


The media is removed from the Integral Volume set Test.

Note: The current write surface should not be removed from the library. If archiving starts the file system will return an error “covered error” and it will have to be imported back into the library to clear the error.

When the Integral Volume set is mounted the QStar Software denies the request to remove the media.

of 152

Removing Media from UDF/UVFS/LTFS Automount Integral Volume Set

To remove media from an existing Integral Volume set select the Integral Volume name, Highlight the media in the left list-box and click the right arrow button or double click on the media. The media will move to the right list-box. In the example, the media in shelf 2 will be removed from the Integral Volume set Test.



If the Integral Volume set is mounted, all the information for the removed media will disappear from the left list-box. In the example, only the media in shelf 1 is currently added to the Integral Volume set Test.

of 152

If the Integral Volume set is unmounted the media removed from the Integral Volume set will be set as Removed. In the example, the media in shelf 2 was removed from the Integral Volume set Test and the media with a sequence_number=1 was marked as Removed.


Figure 5.95 - Volume Management (Removing Media)

Once the media is removed from the Integral Volume set, Volume Management displays that the only media in the Integral Volume set Test is now shelf 1. The next access to the Integral Volume set from an Explorer window will no longer display the information about the files belonging to the media that were removed.

Removing Media from UDF and UVFS Spanning Integral Volume Set Removing media in a UDF Spanning configuration is allowed for the last media in the Integral Volume set and only in the case of disaster recovery do to a media error and under specific guidance of QStar Customer support personnel. For UVFS file system it is always denied.

of 152

VL LIBRARY RELATED COMMANDS The information about the media in the library can be viewed from the Media view pane. Media navigation pane contains five topics, Online Media, Offline Media, Database, Copy Media and Exchange Media. Online Media contains all of the main information about the media and all the primary commands for managing the media. The Online Media database associates each media to the Shelf # it was imported to. Note: QStar recommends reviewing the explanation for the vlcmd lsdev (vllsdev) command in Chapter 9 - Command Reference of this manual, while reading this section.

Main Characteristics of the Media in Online Media The media can have one of the following Statuses: unknown The media has unknown format. If rewritable, it will need to be erased before initializing with a file system. blank The media is blank. This can be a blank CD-R, DVD-R, Optical (MO/UDO/PDD) or BD-R Blu-ray media. erased The media has been erased and it is ready to be added to an Integral Volume set. empty The shelf contains no media. bad The media has a bad flag set and should be cleared, (See Library Status) and then refresh with Refresh button. dup The media in the shelf is identical to another in the library. inaccessible The shelf is marked as inaccessible when the shelf has been set to off in Library Status. erasing The media in the shelf is currently being erased. refreshing The media in the shelf is currently being refreshed, this can be the result of refresh or import. initializing The media in the shelf is currently being initialized. exporting The media in the shelf is currently being exported. importing The media in the shelf is currently being imported. recording The media in the shelf is currently being recorded. copying The media in the shelf is currently being copied. closing The media in the shelf is currently being closed. exchanging The media in the shelf is currently being exchanged. SDF The media contains an SDF file system. UVFS-PFS The media contains an UVFS (Plasmon PFS) file system. UVFS-AFS The media contains an UVFS (Plasmon AFS) file system. UDF-150 The media contains a UDF file system with revision level 1.50. UDF-200 The media contains a UDF file system with revision level 2.00. UDF-201 The media contains a UDF file system with revision level 2.01. UDF-250 The media contains a UDF file system with revision level 2.50. UDF-260 The media contains a UDF file system with revision level 2.60. UDF-150-F The media contains a UDF file system with revision level 1.50 and it is closed (read only). 9660 The media contains an ISO 9660 file system. 9660-J The media contains an ISO 9660 file system with Juliet extension. 9660-R The media contains an ISO 9660 file system with Rock Ridge extension. AAFS The media contains an Archive Appliance (Plasmon AA) file system. TDO The media contains a TDO file system. TDO-F The media contains a TDO file system and it is closed (read only). LTFS The media contains a LTFS file system. LTFS-S The media contains a LTFS Spanning file system. LTFS-I The media contains a LTFS Spanning file system in incomplete state.

of 152

Size of each surface of the media #MB or #GB or #TB Type of media present in the shelves Rewritable, Worm, Tape, CD-R/ROM, DVD-RAM, DVD-

R/ROM, BD-RE, BD-R/ROM Status of write -protection tab of the media prot (physical media write protect switch is on) Name of the Integral Volume set that the media belongs to Set Name = Test The media contains a file system but was not added to any Integral Volume set Set Name = <not in set> The information for the file systems are described as follows: Set Identifier for each media added to a Integral Volume set SetId=7a6f4029039246d0 (TDO) Set_Id=807aeea2.34ba1fc5 (SDF) Log_vol_id=q_3bc5af80 (UDF) SetId=7e5f40290fa03bf5 (LTFS Spanning) Vol_Name=q_t4cd94df3bae98 (LTFS Automount)

Sequence Surface Number of the media in the Integral Volume set Seq=0/Seq=1 (TDO and SDF) Seq=1/Seq=1 (UDF Single-Volume /Automount) Serial=TPSER0 (LTFS Single-Volume/Automount) Span=1/Span=2 (UDF and LTFS Spanning) The name used as a CD/DVD identifier is CD/DVD label LabelName=QSTAR_SOFTWARE LabelName=NO_NAME (CD/DVD-ROM without label) The unique CD/DVD identifier is the Set_id Set_id=478fe.680039ec

of 152

Displaying and Sorting Library Shelf Information To display all the information about the contents of the shelves in the library, select Online Media. To display this information for each library configured, select the appropriate name from the Device Name drop box. Place or remove the check mark in the box on the right to view all shelves or only the shelves with media. The Characteristics of the library shelves can be displayed in several different ways.

The information can be sorted as follows:

• Select the Item button to sort the information by shelf number (default)

• Select the Status button to sort the information by file system and shelf status

• Select the Type button to sort the shelves by media type • Select the Size button to sort the shelves by capacity • Select the Set Name button to sort the shelves by Integral Volume set Name and Set Identifier

• Select the Set Identifier button to sort the shelves by Set Identifier number • Select the Bar Code button to sort the shelves by Bar Code

• Select the Media Id button to sort the shelves by Media Id

Figure 5.96 - Online Media

In the example a Tape library is used.

For CD/DVD or Blu-ray library, the “Shelf 1a-1” or “Shelf 13a-2” value on the first column represents respectively the shelf number and the magazine or pack number.

of 152

Displaying Bar Code and Media ID Library Shelf Information

When using a library with a bar code reader that the QStar Software supports, the Bar Code field will contain the bar code of the media.

When the media is imported, the Bar Code will be read and the media will also be loaded into a drive to be refreshed to find media type and capacity.

It is possible to do a refresh from the command line using the Bar Code information, using the vlcmd refresh (vlrefresh) command. For more detailed information, please refer to Chapter 9 - Command Reference in this manual.

Figure 5.97 - Online Media (Bar Code Information) Note: When the bar code reader is present, the default offline location will be the bar code. Note1: With UDO and TAPE media the Media ID is also displayed.

of 152

FIXING DATABASE INCONSISTENCIES The Volume Librarian (VL) database will remain accurate under normal working conditions. However, the VL database can develop inconsistencies following a hardware failure on the library or a manual intervention (when someone has manually moved media, within or out of the library without using the QStar Software). In these circumstances, the status of the VL database must be verified and if necessary refresh the database to reflect the current library status. The commands used to achieve this are the following:

Verify Print any inconsistencies in the database

Fix Refreshes and fixes the database

Instances for checking VL database consistencies are as follows:

1. After a library hardware failure

2. After a manual intervention with the library If either of the above is suspected, go to Database view pane located under Media navigation pane and select the Verify button, this will check the library media status. If the library media status differs from the VL media status, then media has been moved without VL being updated. In this situation, the Fix button must be selected at the earliest convenience to avoid problems. This process requires all the Integral Volume sets to be unmounted on all VL devices while the refresh is carried out. This may take some time if there are multiple libraries. The more shelves to refresh, the longer this will take. This process must be allowed to complete without interference.

Figure 5.98 - Database

of 152

Fixing a Database Inconsistency after a Library Hardware Failure To explain this procedure a TDO Integral Volume set is used, but the example is valid for every type of file system supported by the QStar Software. The description below manually reproduces the typical library hardware failure caused by the picker inserting the media into a wrong shelf. In this case, the media is not considered lost because it is still in the library and the QStar Software can detect it.

Figure 5.99 - Volume Management (Fixing an Inconsistency)

Volume Management displays the current situation: An Integral Volume set named Test was created, seven media were added and the Integral Volume set is currently mounted. Note: The media with sequence_number 2 was imported into shelf 3.

The shelf information for the library named JB0, reported in Online Media, matches the information reported in Volume Management as described above.

In fact the Characteristics window shows that the media with the Sequence_number=2 was really imported into shelf 3.

Note: The eject/load button on the front panel of the library was used to move the media from shelf 3 to shelf to 9 to manually create a hardware failure caused by the picker inserting the media into a wrong shelf. The VL database cannot track this operation, so when an attempt is made to access the media in shelf 2, an error message will be returned.

Notice after moving the media using the front panel of the library that Shelf 9 is reported as empty.

Figure 5.100 - Volume Management (Fixing an Inconsistency)

of 152

Figure 5.101 - Database (Database Inconsistency Error)

To verify if there is an inconsistency in the VL database, select the Verify button. If the database is consistent a message appears in the text window with the following output: “Media database is consistent”. If the database is inconsistent a message will appear in the text window, reporting the inconsistency. To fix this inconsistency the System Administrator must first ensure that all the Integral Volume sets are unmounted and second that there is no access to any libraries connected to the system and then select the Fix button.

Once the Fix button is selected the refresh procedure starts to refresh all media present in all libraries connected to the system. When the refresh procedure is finished a message will appear in the text window confirming that the database is now consistent. Details of what was found and fixed, will be reported in Syslog.

Figure 5.102 - Database (Refresh and Fix)

of 152

Figure 5.103 - Volume Management (Database Updated)

Volume Management displays the changes, which were made in the database. The example displays that the procedure found the media in the library, corrected the Integral Volume set information by fixing the entry and updating its new location in the database. The media is now reported as loaded in shelf 9.

Online Media also displays the information about the new location of the media in the library. Now shelf 3 is marked as empty and shelf 9 contains the media that was reported as being imported to shelf 3.

Figure 5.104 - Online Media (Database Inconsistency Fixed)

of 152

Fixing a Database Inconsistency after a Media has been Manually Removed from the Library In this example the media is exported using the eject command from the front panel of the library. The procedure is the same as shown in the previous example, but in this case, the media was not found in the library. The changes that are made in Online Media and Volume Management are different from the previous example and additional information is reported in Syslog because the media is considered lost.

Figure 5.105 - Database (Refresh and Fix)

After the refresh procedure is complete and the database is fixed, if the media was not found in the library, Syslog will report the details of which media was lost.

Volume Management will display which changes were made in the database.

This time the media was not found in the library. The procedure to correct the set database information for the Integral Volume set is to set the media as lost with a location of Offline=Lost Media JB#: shelf#.

The example displays that the information for the Integral Volume set Test was corrected by setting the media with sequence_number=2 as Offline=Lost Media JB0:3.

If a user tries to access a file residing on the Offline media the System Administrator will be notified by VL to import the media to satisfy the request.

See the “Managing Offline Media under VL Control” section in this chapter for more detailed information.


of 152

Figure 5.107 - Online Media

Online Media now displays that shelf 3 is marked as empty.

of 152

MANAGING VL OFFLINE VOLUME TRACKING The QStar offline volume tracking is managed through the VL database. As all media has a unique electronic Set ID, Surface Sequence ID, Volume Name (SDF/TDO/LTFS/AAFS/UVFS), Logical Volume id (UDF) or Barcode or Pack ID the media can be tracked by the VL database. Any media from an Integral Volume set that is exported with the Export button will request an offline location, which the VL keeps in its database. If a file is needed from an offline media, a request is sent to the System Administrator to import that media into the library. The request can then be satisfied or cancelled using the proper option in Console view pane. To explain this procedure a TDO file system is used, but the example is valid for every type of file system supported by the QStar Software. In the following example, an Integral Volume set named Test was created, seven pieces of media were added to it and the Integral Volume set is currently mounted. A media belonging to the Integral Volume set is exported from the library and an offline location is requested from the System Administrator. Once the media is offline a read request is performed for a file located on the offline media and a VL request to re-import the media is sent by the QStar Software. By default, in UNIX the request to re-import the offline media will wait until the offline request is satisfied by importing the media or cancelled using the proper option in Console view pane, in Windows the request is automatically cancelled because in any case the CIFS time out will return an error after the default time out. The System Administrator can choose instead of waiting or immediately receive an error for an offline request. To change this offline behaviour, please refer to Displaying and Setting the VL Configuration for Offline Media Request Properties section later in this chapter. If the QStar Mail Notification service is configured, the System Administrator will receive an E-mail notification to import the requested media. For this reason, configuring Mail Notification is highly recommended.

For every Integral Volume set created the Offline Media maintains all the information about the media that is stored offline. To display the offline information for each Integral Volume set select the appropriate Integral Volume set name from the drop box.

Figure 5.108 - Offline Media

of 152


Volume Management displays the current situation: The specific information related to the Integral Volume set Test displays that the media from shelf 1 to shelf 7 belong to the Integral Volume set Test.

The media in shelf 6 is exported by selecting the Export button. Because the media belongs to the Integral Volume set Test an additional window will appear requesting an offline location for this media. In the example, “firesafe” is the offline location specified. If no offline location is specified in the additional window, the QStar Software will assign the default offline location. The default location is composed of the Integral Volume set name and the in_set_number of the media in the Integral Volume set (i.e., the default location for this media is Test_2). If the Pack ID number (DISC library) or Bar Code is available, the default offline location is composed of the Integral Volume set name, the in_set_number and the Pack ID or the Bar Code number. The offline location name can be changed if required using Offline Media view pane.

Figure 5.110 - Online Media (Moving Media Offline)

of 152

Figure 5.111 - Offline Media

Offline Media displays that in the Integral Volume set Test, the media with Sequence_number=6 is offline and the specified offline location is “firesafe”.

Volume Management displays the new Integral Volume set Test information after the media in shelf 6 was stored offline. In the example, the media with in_set_number 5 and Sequence_ number=6 is offline and “firesafe” is its offline location. Now that the media has been moved to an offline location and a user tries to access a file residing on that media, the VL will request that the media be re-imported. This request goes into Syslog, Console and will also generate an email notification (if Mail Notification is configured).


of 152

Figure 5.113 - Console (Offline Media Request)

The example displays a VL request recorded to Console view pane. If a request is not present on Console select the Refresh button and it will appear in the window. Console maintains all requests from the VL module sent to the System Administrator. For example, a typical request can be to import an erased or an offline media. In the example, Console shows that a request to import (Bring online) the media belonging to the Integral Volume set Test with sequence_number 6 located in the offline location “firesafe” is still Pending.

To satisfy the request for the offline media, import the media into any available empty shelf of the library. In this example, the media is re-imported to shelf 13. After that, the media is refreshed and the software will satisfy the users request and mark this media as online in the VL database. Volume Management shows that now the media is considered back online and that it was imported to shelf 13. Note: QStar keeps the offline information in its database. The next time this offline location will be used as default.


of 152

Figure 5.115 - Console (Removing a Satisfied Event)

The Console also reports that the request to import (Bring online) the media was Satisfied. The request can be cleared from the list by selecting the Remove Satisfied Events button.

Canceling a Request for Offline Media

In the previous example, the request for an offline media was satisfied. The QStar Software allows the System Administrator to decide to cancel a request or to satisfy it, whichever is more appropriate. To cancel a request for offline media, select the Pending request and select the Cancel Event button. The request can be cleared from the list by selecting the Remove Cancelled Events button.

Figure 5.116 - Console (Canceling a Pending Event)

of 152

Editing an Offline Location

Figure 5.117 - Offline Media (Editing an Offline Location)

From Offline Media it is possible to change an offline location without importing the media into the library. Highlight the media and select the Edit Offline Location button. Another window will open, type the new location and select the OK button.

Adding an Offline Location for Media Already Offline

An Integral Volume set that was partially located offline and the Integral Volume set definition was lost can be recreated by selecting the Add Offline Medium button without re-importing the media into the library. The surface Sequence Number within the Integral Volume set must be known to add the media in the correct order. This will ensure that the Software will request the proper piece of media for future requests of the offline media.

Figure 5.118 - Offline Media (Adding an Offline Location)

of 152

Displaying and Setting the VL Configuration for Offline Media Request Properties

Figure 5.119 - VL Configuration (Offline Media Request Properties)

Select the VL Conf button in the Delayed Jobs view pane to configure the VL Configuration options, an additional window will open. In the VL Configuration menu, select the Misc. tab. The default setting for Return Error On Access To Offline Media is enabled, in this mode, an I/O error is returned to the user if the media is out of the library, but the offline request is still sent to the System Administrator. If deselected, then the QStar Server will hold the I/O request until the media is imported, or the network timeout period has expired. This timeout may be altered from the default 45 seconds by the utility “setsesstimeout.exe” in the QStar bin directory. In either case, an offline media request is sent to the Console, Syslog and via Mail Notification (if enabled).

of 152

MANAGING OFFLINE MEDIA UNDER VL CONTROL USING THE MAGAZINE OR PACK IMPLEMENTATION The QStar Software for certain type of libraries, in most cases CD/DVD or Blu-Ray devices, that have shelves made as removable magazines or packs which allow exchanging the media in the magazines or packs will automatically update the contents of the media on the shelves in the VL database. During the update, if the media is still present in the library but loaded on a different shelf, the shelf information will be updated in the VL Integral Volume set database with the new location. If the media is removed from the library, the shelf in the VL Integral Volume set database will be automatically switched to offline. The exchange and update operations in the magazines or packs are made using the Magazine button on Online Media; these operations will be denied if any of the media are open (accesses by the users). The exchange and update operations between the magazines or the packs and the internal shelves are made using Exchange Media view pane. QStar suggests unmounting all Integral Volume sets before using the Magazine button in order to ensure a correct exchange operation, because if a media belongs to a file system that is mounted, the Software will deny the exchange operation. With some libraries, a pack may be removed individually without unmounting the Integral Volume sets, by specifying the pack number to exchange, providing no media from the Integral Volume sets are contained in that pack. Once the Magazine button is selected, any media loaded in the drives, will automatically be returned to their shelves and the exchange operation will be allowed to take place, removing the prevent removal status and allowing the door to be opened or removal of the packs. When the exchange procedure is terminated by closing the door or reinserting the pack, a refreshing procedure will automatically be started by the QStar Software for the magazine previously accessed. At the end of the refreshing procedure the VL database will be updated with the new information. Note: For some libraries instead of the Magazine button the Bulk Mail button will be displayed.

Figure 5.120 - Magazines or Packs Under VL Control

On Online Media the Magazine button is used to exchange media in the library using the magazines and update the VL database. The “Shelf 1-1” or “Shelf 11-2” value on the first column of the Online Media for a CD/DVD or Blu-ray library represents respectively the shelf number and the magazine or pack number.

of 152

Exchange Media is used to move media from one internal shelf or a shelf belonging to a pack, to another in the library and update VL databases. If the destination shelf is empty, the exchange media operation moves the media from the source shelf to the destination shelf in the library. If media is present on the destination shelf the exchange media operation exchanges the media from the source shelf with the destination shelf.



To explain the exchange procedure Blu-ray media with the UDF file system is used. Volume Management displays the current situation: An Integral Volume set named Test was created, four pieces of media were added to it and the Integral Volume set is currently Unmounted. QStar highly recommends umounting all Integral Volume sets before selecting the Magazine button, if any media are accessed during the exchange process, the magazine exchange procedure will return an error. Some libraries with packs are allowed to run the exchange magazine procedure even with the Integral Volume set mounted. This depends if there are media in the pack that belong to a mounted Integral Volume set. Note: The media from shelf 1 to shelf 4 belong to the Integral Volume set Test.

of 152

The shelf information reported in Online Media, matches the information reported in Volume Management described above. Note: The shelves from shelf 1 to shelf 4 are full and belong to the Integral Volume set Test.



Once the Magazine button is selected a window will appear. From this window it is possible to specify the magazine or pack number that is going to be removed or changed.

The default value is “Default”. This value allows all magazines to be exchanged. If magazine or pack number ( i.e.: 1, 2, 3, 4, 5, 6) is typed in on the Magazine Number box instead of the default value “Default”, only the specified magazine will be available to be removed or exchanged.

If the Hyper Magazine option is selected (only available with the Pioneer library) only the hyper magazine is allowed to be removed. Select the OK button to continue.

Note: If an individual pack number is selected, then the Integral Volume sets do not need to be unmounted, unless they contain media from any of the mounted Integral Volume sets (only available with the DISC library).

of 152

The magazine procedure exchanges media in the library using the magazines and updates the VL database. Note that to update "write protect" status of the media a physical refresh is needed (it will not use media bar codes and magazine Id in VL media database). Full refresh option: Refresh procedure will use physical refresh (not use bar code media database).

Use media Barcode Instead of physical refresh option: Refresh procedure will use bar code media database.


Use only one drive for refresh option: Refreshes shelves in sequential order (use single drive to refresh media). This allows a limited drive usage during magazine import. Use Magazine ID Instead of Physical refresh - Differential option: Differential refresh procedure will use magazine ID media database (without physical refresh). By default the magazine procedure will physical refresh all media found in the magazine. If magazine supports some form of the magazine identification (like RFID) the magazine procedure with differential option may recover media status using VL media database. Note that magazine procedure will check that all media are in the expected positions (as it was before magazine export). The differential checking verifies only media positions which were changed. If new media is added in the empty slot it will be refreshed. If media was removed from the slot it will be declared Offline in the VL database. Obviously there is no guarantee that media in full slots was not replaced. Use Magazine ID Instead of Physical refresh - Strict option: Strict refresh is similar to differential option, but if media positions mismatch the assumption is made that content of the magazine cannot be trusted and a full physical refresh will be performed. During the strict checking all positions in the magazine are verified. Because there is no possibility to verify that a user did not manually change media positions, the verification code shall include at least a check that all full slots during export are full during import and empty slots are still empty. If this verification is not passed the message in Syslog page will log info about magazine operation. Example “the media in imported magazine ID=.xxxxx. positions changed” if full magazine refresh is performed.

of 152


When using CD/DVD or Blu-ray libraries with mixed drive types or drives that support different types of media, an additional Media Type window will appear. This window can be used to specify the type of all media that will be imported through the magazine. This ensures loading the media into the correct drive during the refresh procedure to determine the media type of the shelf. If the Auto Detect option is selected the QStar Software will automatically detect the media type. The media type is automatically set after the refresh procedure. After the refresh, the jbscheduler will only allow the correct media to be loaded into the drive which can handle this media type. Note: The Auto Detect option must be used if the magazine contains mixed types of media.

Once the OK button is selected, the door that contains the magazines will be opened or the packs will be released and then the message displayed on the figure will be displayed. Before selecting the OK button, do the following: Exchange the media in the library pack/magazine. Close the door or put back the pack in the library. In the example, the media in shelf 1 and shelf 2 of the first magazine are moved respectively to shelf 10 and shelf 9 of the same magazine, the other media are removed from the magazine and new media is inserted in shelf 8. Once the door is closed and the OK button is selected, the QStar Software will automatically start the refresh procedure of the media exchanged and subsequently update the VL databases.


of 152


The QStar Software will assign the default offline location, which is composed of the Integral Volume set name and the in_set_number. If the Pack ID number (DISC libraries) or Barcode is available, the default offline location is composed of the Integral Volume set name, the in_set_number and the Pack ID or the Bar Code. In addition, the System Administrator can append to the default offline location specific offline location information for all media in the pack or magazine that is exported. Each media in the pack or magazine will be listed with the offline location.

After the magazine exchange procedure has completed, Online Media displays that the shelves from 1 to 7 are empty, 10 and 9 contain the media previously in shelves 1 and 2 and shelf 8 contains a new media.


of 152


Volume Management displays the new set information for the Integral Volume set Test after the magazine exchange procedure. The media from shelves 1 and 2 are still online, they are now located in shelves 10 and 9, all the other media are set offline. The offline location name can be changed if required using Offline Media. After the magazine exchange procedure has completed, remount all Integral Volume sets.

Exchange Media can be used to exchange the media in the magazines or between the packs and the internal shelves for a library. In the example, the media in shelf 10 and shelf 1 of the magazine or pack 1 will be exchanged. Because shelf 1 is empty, the media from shelf 10 will be moved to shelf 1 and the QStar VL database for the library and the Integral Volume set will be automatically updated.


of 152


After the Exchange procedure has completed, Exchange Media now displays shelf 10 as empty and shelf 1 as containing the media previously in shelf 10.

After the Exchange procedure has completed, Online Media now displays shelf 10 as empty and shelf 1 as containing the media previously in shelf 10.


of 152


Volume Management displays the new set information for the Integral Volume set Test after the exchange procedure. Note: The media from shelf 8 is still online, but is now located in shelf 1.

of 152

ADDING MEDIA TO AN INTEGRAL VOLUME SET Media Available If the quota is not exceeded and there is media available, it will be added automatically.

Media Not Available In the following example an Integral Volume set is mounted; writing data to the cache and archiving the data to the last media in the Integral Volume set has exceeded the available capacity and there is no available (blank or erased) media in the library. The QStar Software will automatically display the following message in the Syslog, in an email if the Mail Notification is enabled and in the Console:

TDO: set Test, sequence_number 1: Please vladdtoset erased (blank) medium

SDF: set Test, sequence_number 1: Please vladdtoset erased (blank) medium

UDF: set Test, sequence_number 1: Please vladdtoset erased (blank) medium

LTFS: set Test, sequence_number 1: Please vladdtoset erased (blank) medium

If the message to insert pre-erased media is not noticed, the process of writing the data is automatically placed in a disk wait-state. At this point, do not terminate the process or unmount the Integral Volume set. To fix this problem, do the following: 1. Load a new media into the mailslot and import the media into the library selecting the Import button from Online Media.

Note: If all the shelves are full, export a media to an offline location and import the new media into the free shelf.

2. If the media is rewritable and is not erased, erase it by selecting Erase button from Online Media.

3. To add the new media to the Integral Volume set, select Media Management, select the Integral Volume set name that requested the media, Highlight the media in the right list-box and click the left arrow button.

The QStar Software will add the media to the Integral Volume set and add it into the mounted file system. Now that the capacity for writing new data is available, the scheduler automatically activates the process that was in the disk wait-state and the archiving can continue.

RESTORING AN INTEGRAL VOLUME SET Restoring an Integral Volume Set not Known to the VL There are usually two situations where an Integral Volume set is not known by the Volume Librarian database.

1. After an upgrade from an earlier version of QStar.

2. The Integral Volume set was exported from the library and the Integral Volume set definition was deleted from the Volume Librarian database.

In both cases, to enable the Integral Volume set to be re-used, the media will have to be refreshed by the VL (Volume Librarian) database. If the media is out of the library, use the Import button located in Online Media to bring the media back into the library, this will update the VL database on import. If an upgrade has been carried out and the media is still in the library, use the Refresh button located in Online Media to read the media contents and update the VL database. Once the VL database knows the media’s contents, the Integral Volume set definitions can be re-created. There are two sections below explaining how to recover an Integral Volume set for each situation.

of 152

Restoring an Integral Volume Set after a Software Upgrade If you have upgraded from a QStar release earlier than Version 4, then the VL database will need to be rebuilt. This can be achieved by refreshing the library contents and then creating the Integral Volume set definitions and adding the media to the Integral Volume set.

Example, carry out the following actions:

1. Go to Online Media view pane, select the library name from the drop box, Highlight all media present in the library and press Refresh button. This will refresh the contents of the library (to be carried out for each attached library).

2. Go to Volume Management view pane and create a new Integral Volume set definition. 3. Go to Media Management view pane, select the appropriate Integral Volume set name from the drop bar, select the

appropriate library name from the drop bar, Highlight any media that previously belonged to the Integral Volume set in the right list-box and click the left arrow button. Automatically all the media with the same Set Identifier will be added to the Integral Volume set. After that, the Integral Volume set is ready to be mounted by pressing the Mount button from Volume Management view pane.

Restoring an Exported Integral Volume Set Deleted from the VL Database If an Integral Volume set has been exported and the Integral Volume set definition deleted, bringing the Integral Volume set back online can be achieved in one of two ways:

1. Importing one piece of media from the Integral Volume set and recreating the Integral Volume set definition, all other media imported that belongs to that set will automatically be added to the Integral Volume set definition.

2. Import all the media belonging to the Integral Volume set and then create the Integral Volume set definition.

The following are examples of both scenarios.

3. Example 1, carry out the following actions:

a) Go to Online Media view pane, Highlight an empty shelf and select the Import button to import a media that belongs to the Integral Volume set exported from the library.

b) Go to Volume Management view pane and create a new Integral Volume set definition.

c) Go to Media Management view pane, select the appropriate Integral Volume set name from the drop bar, select the appropriate library name from the drop bar, Highlight the media that was previously imported in the right list-box and click the left arrow button to add this media to the Integral Volume set.

d) Go to Online Media view pane, Highlight an empty shelf and select the Import button to import another media that belongs to the Integral Volume set that was recreated. Do this action for all media belonging to the Integral Volume set. The Integral Volume set database will be automatically updated during the import operation, adding the imported media to the Integral Volume set. After that, the Integral Volume set is ready to be mounted by pressing the Mount button from Volume Management view pane.

4. Example 2, carry out the following actions:

a) Go to Online Media view pane, Highlight an empty shelf and select Import button to import a media that belongs to the Integral Volume set that was exported from the library. Do this action for all media belonging to the exported Integral Volume set.

b) Go to Volume Management view pane and create a new Integral Volume set definition.

c) Go to Media Management view pane, select the appropriate Integral Volume set name from the drop bar, select the appropriate library name from the drop bar, Highlight any media that was previously imported in the right list-box and click the left arrow button. Automatically all the media with the same Set Identifier will be added to the Integral Volume set. After that, the Integral Volume set is ready to be mounted by pressing the Mount button from Volume Management view pane.

of 152

DATA COMPACTION UNDER VL CONTROL An Integral Volume set will contain a certain amount of “Dead Space” based on files being changed, rewritten, and/or updated. “Dead Space” is defined as those data bytes on the archive media that have a newer set of equivalent data bytes somewhere else in the archive. This includes both data and metadata. An example of “Dead Space” for a data byte is when a page has been re-written to the archive. An example of “Dead Space” for a metadata byte is when a file has been deleted, all metadata, event data, on the archive previous to the delete event, is Dead Space. Data Compaction is the process of rewriting the data and metadata which is NOT “Dead Space”, from one piece of media to a new piece of media, thus eliminating the “Dead Space” and reclaiming capacity. The Data Compaction utility is available only for Optical and Tape and media written with the TDO, SDF and UDF/LTFS Spanning file systems. The Data Compaction utility can be used with Tape but QStar highly recommends that it is used only if the media contains at least 95% of dead space. This is because the performance of Data Compaction on tape can be slow and take a long time. For tape compaction, at least 4GB of free space on the partition where the cache location resides is required for reallocation purposes. The following commands will exist for managing the dead space on a piece of media from a DOS Window:

vlcmd mediausage

This command will list the usage statistics for all media in an Integral Volume set. By default, these will be listed in order of sequence number. This list will be printed in descending order of amount of “Unused Space”.

vlcmd mediausage [-H host_name] set_name

vlcmd reuse

This command will copy the data and metadata that are NOT considered dead space from the specified media to the current write surface or to a pre-allocated empty piece of media.After this command has been completed, the specified media will show 100% dead space when the vlcmd mediausage command is run. Then it will erase the media that contain 100% dead space and add it to the end of the Integral Volume set. The -p option allows to specify the cache size (space) used for reclaim operations. If increased the reclaim operation can run faster. By is default is 6GB.

vlcmd reuse [-H host_name] [-r] [-j {delayed_job_name | "default"}] [-d {[mmdd]HHMM | [cc]yymmddHHMM}] [-p {cache size to used}] set_name in_set_number... vlcmd delfromset

This command will remove a piece of media that has 100% dead space from an Integral Volume set. If the media does not have 100% dead space, then this command will fail. This command can be run while the Integral Volume set is either mounted or unmounted.

vlcmd delfromset [-H host_name] [-k] set_name in_set_number Note: QStar recommends reviewing the explanation for the above commands in Chapter 9 - Command Reference of this manual, while reading this section.

of 152

Data Compaction Feature The following is an example using TDO file system of the Data Compaction utility using the Media Usage and Reuse option for the Integral Volume set Test. The Data Compaction utility requires that the Integral Volume set must be mounted and will run in background with no down time.


Volume Management displays the current situation: An Integral Volume set named Test was created and eight media were added. The specific information related to the Integral Volume set Test displays that the media from shelf 1 to shelf 8 belong to Integral Volume set Test.

Compaction will display all the Integral Volume sets that are mounted; the Data Compaction utility can be used on the Integral Volume sets that are available from the drop bar. Select the appropriate Integral Volume set from the drop box. Note: In the example, the Integral Volume set Test was selected.

Figure 5.136 - Compaction

of 152

Figure 5.137 - Compaction (Media Usage)

To begin analyzing the media usage for the selected Integral Volume set select the Media Usage button. If the media usage analysis returns a BUSY error message it means that the Integral volume set was not cleanly unmounted. To fix the media usage problem mount and umount the Integral Volume set. Note: In the example, the Integral Volume set Test is being analyzed.

Once the analysis is complete all information about the media usage statistics for the Integral Volume set Test will appear in Compaction view pane. The following information is displayed for each media belonging to the Integral Volume set:

• The Sequence of the media in the Integral Volume set

• The Status of the media;

Written

Current (current writing surface)

Empty

• Location of the media in the library

• Capacity of the media

• Used capacity used by the available data

• % used percentage of media used

Figure 5.138 - Compaction (Media Usage) The media usage analysis suggests all the media that may be reclaimed and an estimated time for the compaction. Note: In the example, the media in shelf 1 can be reclaimed in approximately 0 minutes.

of 152

Figure 5.139 - Compaction (Reuse)

To reclaim the space and reuse the media Highlight the media suggested and select the Reuse button. The Compaction procedure can be delayed by placing a check mark in the Delayed Job box and specifying a Name for the Delayed Reuse procedure.

During the Compaction different progress windows will appear.

Once the media has been reclaimed the next action of the Compaction utility is to erase the media and add it to the end of the Integral Volume set.

Figure 5.140 - Compaction (Reuse)

of 152


After the Compaction has been completed, select the Media Usage button to list the new media usage statistical information. The new media usage information displays that the media with Sequence_number 0 is no longer part of the Integral Volume set; the media in shelf 1 is Empty and was added to the Integral Volume set Test with Sequence_number 8. Note: The media in shelf 1 now has a capacity of 0% used.

Volume Management displays the new information about the Integral Volume set Test after the Compaction has been completed. Now the media that was loaded in shelf 1, that had a Sequence_number=1 is no longer associated with the in_set_number 0. It has been removed and added to the Integral Volume set Test with Sequence_numbers=8 and a new in_set_number 8.


of 152

Data Compaction not Available


The Media Usage analysis may advise that the amount of free space present in the Integral Volume set is not sufficient for running the Compaction utility. In this case, a message will be displayed in the media usage statistical information. To solve this problem, add a new empty media to the Integral Volume set. Verify that the amount of available space is now sufficient for the Compaction to run by selecting the Media Usage button. If the media usage statistical information does not display any other advice, select the Reuse button to start the Compaction procedure.

Displaying and Setting the VL Configuration Properties for Delayed Data Compaction

To relocate data, erase the media with Sequence “0” and add it to an Integral Volume set Test using the Delayed Data Compaction procedure, go to Compaction, Highlight the media suggested and place a check in the Delayed Job box and assign a name to the job.

Select the Reuse button to proceed.

In the example, “Compaction Media 1” is the name assigned to the delayed job. If the delayed job name is omitted a default delayed job name is automatically assigned. The job will be executed according to the “Delayed Time” field in the Reuse VL Configuration properties.

Figure 5.144 - Displaying and Setting Delayed Data Compaction

of 152


In Delayed Jobs view pane select the VL Conf button then select the Reuse tab to display the Delayed Data Compaction properties. The Reuse option is related to the Delayed Compaction procedure that relocates data, erases media and adds it to an Integral Volume set. Delayed Time: Start Time and Stop Time shows when the VL scheduler will process the delayed jobs in 24-hour mode. The 0:0 0:0 value is the default and ensures the jobs will not be delayed and will be processed immediately. The System Administrator can change any of the default parameters by typing the new value. In the example, default Delayed Reuse option is changed so that the Data Compaction operation will only take place between the hours of 23:00 and 06:00.

To change the Delayed Start Time of a job from the default time in the “Delayed Time” field in the VL Configuration properties, place a check in the Job Start Date box and change the Time or Date from the drop bar or by using the Calendar. Select the Reuse button to proceed.


of 152

ERROR RECOVERY The QStar Software contains features that allow recovery from most errors introduced by human error or caused by hardware failure. If the VL database gets out of synchronization with the library status, this can be due to a hardware problem or human intervention with the library. To recover from this go to Online Media, select the Refresh button, for a single shelf, multiple shelves or all the shelves contained in the library, or use the utility in Database. See the Chapter 9 - Command Reference for full details or read the “Fixing Database Inconsistencies” section of this chapter.

of 152

THE COPY AND COMPARE MEDIA UTILITIES The QStar Software allows the System Administrator to create a back up copy of the media used in the library and verifies it with the original once created. The Copy and Compare Media procedure can be used with Optical and Tape media with the TDO, SDF file system, with Optical media written with UDF or ISO 9660 file system and Tape media with LTFS file system. There are two ways of creating a back up copy of the media in an Integral Volume set and compare it with the original, they are as follows:

• Manual Media Copy and Compare

• Automatic Media Copy

Manual Media Copy and Compare The System Administrator from Copy Media view pane can execute a duplication process of the media that has been written to using the Media Copy procedure and then compare the duplicate media with the original media using the Compare procedure once the duplication process is finished.

Manual Media Copy The Media Copy procedure creates a duplicate of the original media in the Integral Volume set, if an original media is damaged, the duplicate media can be used to replace the damaged media. The Media Copy procedure works under the control of the QStar Volume Librarian database and creates a duplicate copy of a media (TDO, SDF, LTFS, UDF or ISO 9660 file system). The only exception is that the copy_number in volume_id block is incremented in order to create a different sequence_number that identifies the media as a backup copy of the original. This difference in the sequence_number allows both the original and duplicate media to co-exist in the VL database (library), without introducing the error condition using duplicate media or locking the set database when the Refresh button from Online Media view pane is used. This means that after the Media Copy process is completed the QStar Software will automatically update the VL database and the media can be left in the library or exported and stored in a safe location until it is needed. Note: When using double-sided media both sides will be copied; also, the original and the copy media must reside on the same host unless Remote Copy has been licensed. In the Copy Media view pane are available the main option for Manual Copy Media Procedure. Additional option are available only using the vlcmd copy (vlcopy) command.

vlcmd copy [-H host_name] [-v] [-c copy_number] [-C {yes|no}] [-r src_host_name] [-j {delayed_job_name | "default"}] [-d {[mmdd]HHMM | [cc]yymmddHHMM}] [-h sdfHostID -t sdfTime] to copy sdf volumes with different set id [-I] to incremental copy the sdf or tdo media [-l] to lock both sdf or tdo tape volumes (default lease) src_dev_name[@src_host_name]:shelf_number [dst_dev_name[@dst_host_name][:shelf_number]] Note: QStar recommends reviewing the explanation for the vlcmd copy (vlcopy) command in Chapter 9 - Command Reference of this manual, while reading this section.

of 152

Common Media Copy Options In Copy Media view pane, the Media Copy procedure is used to create a duplicate copy of a media. Copy Media view pane includes different sections and options for the Media Copy procedure. The following are the common options: Source Media: The media that belongs to the Integral Volume set that will be copied. Device Name: The library that the source media resides in. Destination Media: The media the copy will be sent to. Device Name: The library that the destination media resides in. Compare After Copy: Compares the duplicate media with the original media. The Media Copy procedure can be delayed by placing a check mark in the Delayed Job box and specifying a Name for the Delayed Media Copy.

Figure 5.147 - Manual Media Copy

The Media Copy procedure can be made by selecting the Source Media from a library that is connected remotely. To make the library information available, place a check mark in the Host box and type the host name and select the Refresh button. If the host name was not already inserted in the system HOST file, use the IP address and select the Refresh button. The remote Media Copy option is available only if the Remote Copy has been licensed. Options available only using vlcmd copy (vlcopy) command:

-c copy_number This option allows the System Administrator to change the incremented number of the copy_number (0 - 128) to a different value; which will allow multiple copies to be made of the original media and all copies may co-exist in the library. Without this option the copy_number on destination media is equal to the copy_number of the original media plus one. -l (Tape Specific Option) Lock SDF, TDO or LTFS volumes during copy (only for tape drives). This option allows tape drives to be monopolized during copy. By default, volumes will stay in the drive for the duration of the drive lease time and may be unloaded if there are other pending requests for the tape drive in this case the copy may continue later once drives become free.

of 152

Incremental Media Copy Option

Figure 5.148 - Manual Media Copy

The Incremental option initiates an incrementally the media copy procedure. The Incremental option is supported with TDO, SDF, UDF and LTFS file systems. Using the Incremental Media Copy option, means that if more data is written after the Media Copy procedure has been run, running the Media Copy procedure subsequently will write the changes to the destination media. The Incremental Media Copy for the UDF file system is available only for WORM (MO/UDO/ PDD/CD/DVD-R/BD-R) media. The Destination Media will display all media Blank/Erased and all media not finalized.

SDF Specific Media Copy Option This option is available only using vlcmd copy (vlcopy) command. The -h and -t options allows a media copy to be performed in a SDF Mirror configuration. In case the System Administrator wants to recreate a bad or lost media of the Primary Mirror Integral Volume set using the corresponding media from the Secondary Mirror Integral Volume set (or vice versa) the -h and -t option must be used. The Primary Mirror Integral Volume set media and the Secondary Mirror Integral Volume set media contain the same data, block by block, the only difference is the Integral Volume set Identifier that identifies each media as belonging to either the Primary Mirror Integral Volume set or the Secondary Mirror Integral Volume set. The correct Set_Id must be specified to allow media intregation with the appropriate Primary or secondary Integral Volume set. Here -h and -t should specify Set_Id (which is a combination of the host_id and time_id) for mirror Integral Volume set. For example, the Secondary Mirror Integral Volume set has Set_Id:12345678.aabcd123, the option must be specified in the following way -h 0x12345678 -t 0xaabcd123. In this case, media copy procedure will create a copy from the Primary Mirror Integral Volume set for the Mirror Integral Volume set with Set_Id: 12345678.aabcd123.

of 152

Manual Media Compare The System Administrator from Copy Media view pane can execute a Compare procedure once the duplication process is finished In the Copy Media view pane are available the main option for Manual Compare Media Procedure. Additional option are available only using the vlcmd cmp (vlcmp) command.

vlcmd cmp [-H host_name] [-v] [-r src_host_name] [-m] [-j {delayed_job_name | "default"}] [-d {[mmdd]HHMM | [cc]yymmddHHMM}] [-l] to lock both sdf or tdo tape volumes (default lease) [-1|-2] compare only 1st or 2nd LTFS partition (default both) [-o] Single-thread compare mode [-t compare_size] - compare XX{K|M|G} bytes starting at the tail of the shortest media or from specified logical block (lL) [-f] compare media even if NWA are different src_dev_name[@src_host_name]:shelf_number dst_dev_name[@dst_host_name]:shelf_number Note: When using double-sided media both sides will be copied; also, the original and the copy media must reside on the same host unless Remote Copy has been licensed. Note1: QStar recommends reviewing the explanation for the vlcmd cmp (vlcmp) command in Chapter 9 - Command Reference of this manual, while reading this section.

Common Media Compare Options

Figure 5.149 - Manual Media Compare

Under Copy Media view pane, the Media Compare procedure is used to compare the original media with the duplicate media once the Media Copy procedure is completed to ensure that their contents are identical. The following are the common options: Copy Media view pane includes different options for the Compare Media procedure as follows: Source Media: The media that belongs to the Integral Volume set that has been be copied. Device Name: The library that the source media resides in. Destination Media: The duplicate media. Device Name: The library that the duplicate media resides in. The Compare procedure can be delayed by placing a check mark in the Delayed Job box and specifying a Name for the Delayed Media Compare procedure.

of 152

The Media Compare procedure can be made selecting the Source Media from a library that is connected remotely. To make the library information available, place a check mark in the Host box and type the host name and select the Refresh button. If the host name was not already inserted in the system HOST file, use the IP address and select the Refresh button. The remote Compare Media option is available only if the Remote Copy has been licensed. Compare Tail Only (MB): This option can be used to compare only the “tail” of the media because the full tape media compare may take significant time. Once selected in the text box insert the size in MB of data to compare starting at the tail of the shortest media. Skip Size Check: Compare media even if NWA (Next Writable Address) are different. The first operation of the media comparison procedure is to check if the amount of data written on both media is the same. To do so the Software will search the Next Writable Address and if identical start are the comparison procedure block by block. If are different immediately exit from the comparison operation. With this flag the Software will start compare operation without do check the NWA. This can be useful when System Administrator want to compare media used during Multi-Incremental Media Copy procedure. Options available only using vlcmd cmp (vlcmp) command: -l (Tape Specific Option) Lock SDF, TDO or LTFS volumes during copy (only for tape drives). This option allows tape drives to be monopolized during copy. By default volumes will stay in the drive for the duration of the drive lease time and may be unloaded if there are others pending requests for the tape drive. Later the copy may continue once drives become free. -o Single thread compare mode. To increase compare performance (especially tape) vlcmd cmp (vlcmp) uses two threads to read data into multiple buffers. That requires hundreds of megabytes of memory but provides serious performance gains. If memory is scarce, the single thread compare mode should be used.

SDF Specific Media Compare Option The -m allows to compares mirror medium. This option is applicable to SDF volumes only. It allows it to compare mirror medium. This option is available only using vlcmd cmp (vlcmp) command.

LTFS Specific Media Compare Option The option -1|-2 allows to compare just the first (-1) or just the second (-2) LTFS partition. By default, both are compared. This option is available only using vlcmd cmp (vlcmp) command.

of 152

Example of Manual Media Copy

Online Media displays the information about the initial status of the media in the library. In the example, the TDO file system is used. The media in shelf 1 and shelf 2 belong to the Integral Volume set Test and the media in shelf 3 and 4 are erased.

Figure 5.150 - Example of Manual Media Copy


To create a duplicate copy of the media in shelf 1 with the media in shelf 3, select the Copy radio button. Highlight shelf 1 in the Source Media window and select shelf 3 in the Destination Media window and select the Copy button.

of 152

Once the Copy button is selected the confirmation window will open reporting the copy information. Select the OK button to continue or select the Cancel button to abort the Media Copy procedure. Once the OK button is selected the Copy window will open reporting the different status information as the copy proceeds. This window displays that the copy operation has been started; the progress during the Media Copy procedure is reported and at the end of the Media Copy procedure will report the media is in closing phase.



Online Media will display the library shelf information as copying during the Media Copy procedure. Note: The media in shelf 3 is being copied.

of 152

The Media Copy procedure is complete and now the media in shelf 3 is displayed in the Source Media and Destination Media window and is reported with Seq equal to 0.1. This means that this media is the first copy of a media with sequence 0.



Go to Online Media to display the library shelf information after the Media Copy procedure has been completed. The media in shelf 1 has been copied to shelf 3. Online Media displays an identical Set Identifier number for both media but a different Seq number, the duplicate media has been incremented by 1. Shelf 3 displays <not in set> instead of the Set Name Test. Although this media has an identical Set Identifier, it is not considered part of the Integral Volume set Test because the original media is still present in the Integral Volume set.

of 152

Displaying and Setting the VL Configuration Properties for Delayed Media Copy

To create a duplicate media using the Delayed Media Copy procedure, place a check in the Delayed Job box and assign a name to the job. Select the Compare After Copy option if required to compare the duplicate media with the original immediately after the Delayed Media Copy procedure is completed. Select the Copy button to proceed. In the example, shelf 1 will be copied to shelf 3 and Compare After Copy has been selected. The “Make copy of shelf #1” is the name assigned to the delayed job. If the delayed job name is omitted a default delayed job name is automatically assigned. If the Destination Media and Device Name are omitted the Media Copy procedure will use the first available media specified in the Copy VL Configuration properties.

Figure 5.156 - Displaying and Setting Delayed Media Copy The job will be executed according to the “Delayed Time” field in the Copy VL Configuration properties.

Figure 5.157 - Displaying and Setting Delayed Media Copy Delayed Time: Start Time and Stop Time when the VL scheduler will process the delayed jobs in 24-hour mode. The 0:0 0:0 value is the default and ensures the jobs will not be delayed and will be processed immediately.

In Delayed Jobs view pane select the VL Conf button then select the Copy tab to display the Delayed Media Copy properties. The Delayed Media Copy properties under the VL control can be used also to configure the Automated Copy Of Full Media feature to take place at a pre-determined time. By default, the library name and the range of destination shelves are not defined with the following default options: Library Name: “ ” - The name of library, which the QStar Software will use to examine for available media that can be used as destination media in the Media Copy procedure. Start Shelf Number: “0” - The first available shelf (media) usable as destination media. End Shelf Number: “0” - The last shelf (media) usable as destination media.

of 152

Compare After Copy: “No” - Allows automatically starting the Media Compare procedure once the Media Copy procedure is completed. Interchange Worm Rewritable Media: A check will allow using rewritable or WORM media as destination media. By default (unchecked), the QStar Software will use identical media as the original for the destination media.

If Destination Device and Destination Media are omitted, the Media Copy procedure consults “Library Name”, “Start Shelf Number”, “End Shelf Number” fields in Copy tab. If there are no such fields in Copy tab the Media Copy procedure examines the library where the source media resides first and then all other libraries. The System Administrator can change any of the default parameters by typing the new value. In the example, default Delayed Media Copy options are changed so that the Automated Media Copy operation will only take place between the hours of 23:00 and 06:00 and will only use media from shelves 80 to 90 inclusive as destination media. It would also Compare the media afterwards.

Figure 5.158 - Displaying and Setting Delayed Media Copy

Figure 5.159 - Displaying and Setting Delayed Media Copy

To change the Delayed Start Time of a job from the default time in the Copy VL Configuration properties, place a check in the Job Start Date box and change the Time or Date from the drop bar or by using the Calendar. Select the Copy button to proceed.

of 152

Example of Manual Media Compare

The Compare Media option allows verifying a copy of a media made with the Manual Media Copy to ensure the Media Copy procedure has been copied the media correctly. To compare the media in shelf 1 with the media in shelf 3, select the Compare radio button. Highlight shelf 1 on the Source Media window and select shelf 3 in the Destination Media window and select the Compare button. The Manual Media Compare procedure can be delayed by placing a check mark in the Delayed Job box and specifying a Name for the Delayed Compare Media procedure.

Figure 5.160 - Example of Manual Media Compare


Once the Compare button is selected, the confirmation window will open reporting the compare information. Select the OK button to continue or select the Cancel button to abort the Media Compare procedure. Once the OK button is selected the Compare window will open reporting the different status information as the compare proceeds. This window displays that the compare operation has been started, and the progress is reported during the Media Compare procedure.

of 152

Once the Media Compare procedure has been completed an additional window will open reporting the compare result, in addition, it will generate a report file in the c:\qstar\log directory (i.e. vlcmp_JB0_1-JB0_3.txt) that will display the results of the comparison.


Example of report file: vlcmp_JB0_1-JB0_3.txt

Below is an example of the contents of the report file:

vlcmp report Date April 24 2013 13:25:47

JB0:1 tdo, Side capacity: blocksize 1024, 512000 blocks

JB0:3 tdo, Side capacity: blocksize 1024, 512000 blocks

Blocksize for compare 1024

Blocks to compare 512000

The compare process was terminated at block 134913.

381 blank blocks were read.

All remaining blocks are presumed blank.

JB0:1a JB0:3a are equal.

The compare process was terminated at block 257.

256 blank blocks were read.

All remaining blocks are presumed blank.

JB0:1b JB0:3b are equal.

vlcmp completed at 12:36:1

of 152

Displaying and Setting the VL Configuration Properties for Delayed Media Compare

Figure 5.163 - Displaying and Setting the Delayed Compare Properties

To compare a duplicate media with the original using the Delayed Media Compare procedure, place a check in the Delayed Job box and assign a name to the job.

Select the Compare button to proceed.

In the example, shelf 1 will be compared to shelf 3. The “Compare shelves 1 & 3” is the name assigned to the delayed job.

If the delayed job name is omitted a default delayed job name is automatically assigned.

The job will be executed according to the “Delayed Time” field in the Compare VL Configuration properties. Once the Delayed Media Compare procedure has been completed, it will generate a report file in the c:\qstar\log directory (i.e. vlcmp_JB0_1-JB0_3.txt) that will display the results of the comparison.

In Delayed Jobs view pane select the VL Conf button then select the Compare tab to display the Delayed Media Compare properties. Delayed Time: Start Time and Stop Time when the VL scheduler will process the delayed jobs in 24-hour mode. The 0:0 0:0 value is the default and ensures the jobs will not be delayed and will be processed immediately. The System Administrator can change any of the default parameters by typing the new value. In the example, default Delayed Media Compare option is changed so that the Automated Media Compare operation will only take place between the hours of 23:00 and 06:00.


of 152


To change the Delayed Start Time of a job from the default time in the Compare VL Configuration properties, place a check in the Job Start Date box and change the Time or Date from the drop bar or by using the Calendar. Select the Compare button to proceed.

of 152

Substitute the Original Copy of the Media with the Duplicate To substitute the original media with the duplicate media for an Integral Volume set requires exporting the original media. When the original media has been exported the System Administrator will be prompted for an offline location. Import the duplicate media to an available shelf and add the media to the Integral Volume set. The Media Management is used to substitute the original media with the duplicate media for an Integral Volume set.

Volume Management displays the media in shelf 1 is online and belongs to the Integral Volume set Test with Sequence_number=0.

Figure 5.166 - Substitute the Original Copy of the Media with the Duplicate


Media Management displays the media in shelf 1 belongs to the Integral Volume set Test and the media in shelf 3 as available media. To substitute the original copy of the media with the duplicate, Highlight the media on the right window and select the left arrow or double click on the media.

of 152

Once the substitution is complete, Media Management will display the media in shelf 3 is now in the left window and belongs to the Integral Volume set Test and the media in shelf 1 is in the right window as available media.



Volume Management now displays that the media in shelf 3 is online and belongs to the Integral Volume set Test with Sequence_number=0.

of 152

Online Media displays the current library shelf information after the substitution. Online Media now displays the Set Name of the shelf 1 as <not in set> instead of the Set Name Test. It no longer belongs to the Integral Volume set Test. The media in shelf 3 has been substituted with shelf 1 and now has the Set Name Test instead of <not in set>. Note: The library shelf information displays that the duplicate media now belongs to the Integral Volume set Test.

To export the original media, Highlight Shelf 1 and select the Export button.


of 152

Automatic Media Copy The Automatic Media Copy procedure creates a duplicate of the original media in the Integral Volume set; if an original media is damaged, the duplicate media can be used to replace the damaged media. The Automatic Media Copy procedure is under the control of the QStar Volume Librarian database and creates a duplicate copy of a media. The only exception is that the copy_number in volume_id block is incremented in order to create a different sequence_number that identifies the media as a backup copy of the original. This difference in the sequence_number allows both the original and duplicate media to co-exist in the VL database (library), without introducing an error condition using duplicate media or locking the set database when the Refresh button from Online Media view pane is used. This means that after the Automatic Media Copy process is completed the VL database will be automatically updated and the media can be left in the library or exported and stored in a safe location until it is needed. The Automatic Media Copy procedure can be done for Full Media or Incremental or Multi-Incremental with an additional license, and is available selecting Of Full Media or Incremental or Multi-Incremental in the Make Copy option during the creation of the Integral Volume set or selecting the Properties button in Volume Management view pane. The Automatic Copy Of Full Media will run every time the Integral Volume set reaches the point of dynamically allocating another piece of media to the Integral Volume set and it is supported for the TDO, SDF, UDF/LTFS Spanning file system. It may be required to configure the Automatic Copy Of Full Media procedure as a Delayed Jobs under VL scheduler control. See the “Displaying and Setting the VL Configuration Properties for Delayed Media Copy” section. The Automatic Incremental or Multi-Incremental Media Copy can be scheduled to run Incrementally at a pre-determined time. This means that if more data is written after the Media Copy has been run; running the Media Copy subsequently will write the changes to the destination media.

Figure 5.171 - Automatic Media Copy

To create an Integral Volume set named Test with the Automatic Media Copy feature enabled, select the Make Copy option; there are three options available: None: No copy will take place; any media duplication will need to be taken manually. Of Full Media: At the point another media is dynamically allocated a media duplication is invoked. Incremental or Multi-Incremental: An incremental Media Copy procedure is scheduled. Selecting the Schedule button, a second window is enabled to configure when the incremental Media Copy takes place. Note: In the example, a TDO file system is used.

of 152

The Schedule is an additional option for Incremental or Multi-Incremental. Once the Schedule button has been selected, the Change Schedule window will appear allowing configuration of the schedule for the Incremental or Multi-Incremental Media Copy. The configured schedule will then be submitted as a Delayed Job. The schedule can be modified from here, or from Delayed Jobs view pane.



The additional options displayed for Incremental or Multi-Incremental are the following: Copies: Number of copies used for multiple incremental copy operations. This option represents the number of media copies that will be created automatically, from each original media in the Integral Volume set, during the incremental copy or the multi-incremental copy operation. Each media copied will differ in the sequence number.

Example the sequence number for original media is:

seq=0 (Original media single surface) seq=0.1 (First copy) seq=0.2 (Second copy) seq=0.3 (Third copy)

For Incremental Media Copy this option is disabled because the number of copies is set by default to fixed value equal “one”.

of 152

Allocation Policy: Media allocation policy for Incremental or Multi-Incremental Media Copy.

• Auto allocate medium: Medium Allocated Automatically (used by default). • Manual medium allocation: Medium allocated Manually.

By default the Incremental or Multi-Incremental Media Copy procedure will automatically use the first available (blank or erased) media present in the library as its destination. This is the default option used by the Software (Auto allocate medium). If the System Administrator configured in the Copy tab of the Delayed Copy Media properties the options for library name and range of shelves the Software will not use the first available media but will use one from the range specified. If the Auto allocate medium option is specified, the Automatic Incremental or Multi-Incremental Media Copy will stop after the copy of the media is completed and will wait the System Administrator to add new media for the copy to continue.



Order Policy: Specifies method of the copy production for Multi-Incremental Media Copy.

• One copy first: Produce at least one copy for each main volume first. This the default option used by the Software.

• All copy are done for volume: Produce all copies for the main volume then all copies for the next volumes, etc.

This option is specific for Multi-Incremental Media Copy and specifies the copy production method.

This feature is explained with the following example. Suppose that an Integral Volume set has been configured with 3 media. The volume sequence of the media in the Integral Volume set is Seq=0, Seq=1 and Seq=2 and the current write media is Seq=2. Subsequently the System Administrator has decided to enable the Multi-Incremental Media Copy for the Integral Volume set, specifying 2 as the number of copies of each media. In case there are 2 copies requested and there are several volume copies to be produced, there may be several strategies in which order the copy production is implemented. A) One strategy could be to immediately produce at least one copy of the main volumes (N, N+1, etc.) and in that way assure that all data is replicated at least once. Then, when there are enough resources, produce a second copy for volume N, N+1, etc. B) The other strategy would be to produce all 2 copies for volume N, then 2 copies for volume N + 1, etc. A) Option One copy first First make one copy for each volume and then after that start the second copy for each volume. In this case, the copy procedure will be the following:

Seq=0.1 - Seq=1.1 - Seq=2.1 and then

Seq=0.2 - Seq=1.2 - Seq=2.2 B) Option All copy are done for volume Make all the copy for the first volume and then after that start the all the copy for the second volume. In this case, the copy procedure will be the following:

Seq=0.1 - Seq=0.2 and then

Seq=1.1 - Seq=1.2 and then

Seq=2.1 - Seq=2.2

of 152

Time Slice (sec): Incremental and Multi-Incremental Media Copy time limitation in seconds (600 by default). This option defines how long the copy procedure will continue without interruption before allowing any other I/O request for the same media to be satisfied. Data size per slice: Multiple Incremental Media Copy written data size limitation in gigabytes (<number>GB) or megabytes (<number>MB). This option defines how long the copy procedure will continue without interruption before allowing any other I/O request for the same media to be satisfied. In this case the interruption is defined as the amount of data need to be copied before interruption. By default, this option is disabled because the Time Slice (sec) option is used.


Automatic Copy of Full Media

The Automatic Copy of Full Media is supported for the TDO, SDF, UDF/LTFS Spanning file systems.

Figure 5.177 - Automated Copy Of Full Media Note: In the example, an UDF file system is used, the Make Copy option is available only if Close Full Volume option check box is selected.

Select the Of Full Media option under Make Copy drop box. The Automatic Copy of Full Media will run every time the Integral Volume set reaches the point of dynamically allocating another piece of media to the Integral Volume set. The copy will start immediately after the media is completed, this may cause problems unless there are an adequate number of drives in the library. QStar recommends using this option when the library has a minimum of four drives. This is recommended because when archiving begins three drives will be in use; it will require one drive for archiving and dynamic allocation of more media, one drive for the source media of the Media Copy process and one drive for the destination media of the Media Copy process. It is preferable to configure the VL scheduler to process the Automatic Copy Of Full Media procedure outside of normal working hours, setting a Delayed Start time under the VL Configuration Properties for Delayed Media Copy. See the “Displaying and Setting the VL Configuration Properties for Delayed Media Copy” section.

of 152

Automatic Incremental and Multi-Incremental Media Copy

In this session we will refer to Automatic Incremental and Multi-Incremental Media Copy using just Automatic Incremental Media Copy because they are the same, with the only difference being the Number of Copy option is limited to one for Incremental Media Copy. The Automatic Incremental Media Copy can be scheduled to run incrementally at a pre-determined time. This means that if more data is written after the Media Copy has been run; running the Media Copy subsequently will write the changes to the destination media. The Automatic Incremental Media Copy procedure is only supported for Optical and Tape media with the TDO file system, only for Optical media with the SDF file system and only for WORM media with the UDF Spanning file system. For this procedure to work correctly, the destination media MUST be in the library at the scheduled time. For this reason, it is important the current destination media is left in the library, once a new destination media is started, all previous destination media can be removed from the library. Only one destination media is supported for the Incremental Media Copy, alternating between two or more destination media is supported only with Multi-Incremental Media Copy feature. The Automatic Incremental Media Copy is based on VL database and a special Database called MiCdb (Multi Incremental Copy Database), the database is the same but the Number of Copy option are limited to one for Incremental Media Copy. Select the Incremental option under Make Copy drop box and then select the Schedule button to configure when the Incremental Media Copy will take place. The Incremental Media Copy can also be activated or deactivated by selecting the Properties button for the Integral Volume set on Volume Management and then selecting the Schedule button. In the example, the Copy Properties button is not selected because will be used the default options. Note: Automatic Incremental Media Copy with the UDF Spanning Interchange Level is only supported if the Close Full Volume option is enabled and media is WORM.

Figure 5.178 - Automatic Incremental and Multi-Incremental Media Copy

of 152


Once the Schedule button has been selected, the Change Schedule window will appear allowing configuration of the schedule for the Incremental Media Copy. The configured schedule will then be submitted as a Delayed Job. The schedule can be modified from here, or from Delayed Jobs view pane.

Delayed Jobs displays the delayed job information for the Incremental Automatic Media Copy. Double click on the job record to display detailed information.


of 152


The Delayed Job may be modified by Highlighting the job and selecting the Schedule button, a second window will appear. If the schedule is no longer required, it may be removed by Highlighting the delayed job record and then selecting the Delete button. Removing the record on Delayed Jobs or deselecting Incremental under Make Copy option on the set properties window will deactivate the Incremental Media Copy.

of 152

Managing Automatic Incremental and Multi-Incremental Media Copy Additional command vlcmd micopy (vlmicopy) is avalilable selecting Tools\QStar Dos Propt Commands in order to manage Incremental/Multi-Incremental Media Copy.

vlcmd micopy [-H host_name] [-v] set_name

The vlcmd micopy command starts Incremental/Multi-Incremental Copy (MiC) operation for the Integral Volume sets specified by set_name. The operation is used for SDF, TDO and UDF-Spanning Integral Volume set with defined incremental copy job. The command works in both cases, with either the Integral Volume set mounted or unmounted and waits while operation is finished. OPTIONS

-H host_name

Specifies the name of the host where the Integral Volume set resides. Without this option, the local host is used. -v Verbose messages initiated. Note: QStar recommends reviewing the explanation for the vlcmd micopy (vlmicopy) command in Chapter 9 - Command Reference of this manual, while reading this section.


From the Migration View pane, selecting the Copy Info button is possible to open the Multi/ Incremental Copy Status windows.

of 152

From the Multi/Incremental Copy Status windows the System Administrator can display and modify MiC database. This database is used by the Software for Incremental/Multi-Incremental Media Copy operations for SDF, TDO and UDF-Spanning Integral Volume set. The status can be displayed for mounted and unmounted Integral Volume sets. Note: The MiC database is stored in XML format.



Selecting a volume and pressing the right mouse button the following available option for each media will be displayed: Detach Replica: Unlink destination volume from source volume. Used for MiC operations. Clear error: Clear error volume status after reason for error has been resolved. Set “Off” sync state: Set OFF synchronization status for given volume. Used for TDO mirror synchronization. Experts use only. Set “On” sync state: Set ON synchronization status for given volume. Used for TDO mirror synchronization. Experts use only. Set “Done” sync state Set DONE synchronization status for given volume. Used for TDO mirror synchronization. Experts use only.

Note: The option available on the Copy Info windows are related to the vlcmd micdb (vlmicdb) command. Extra options are available from command line. QStar recommends reviewing the explanation for the vlcmd micdb (vlmicdb) command in Chapter 9 - Command Reference of this manual, while reading this section.

of 152

DELAYED JOBS UNDER VL SCHEDULER CONTROL The QStar Software contains an event scheduler for scheduling certain processes. Scheduling of events allows the Software to be used to its full potential. Notifying the System Administrator of low available media and delaying system intensive processes to be run during off peak hours. The VL scheduler can be used to run batch or single media Erase as well as Media Copy requests. It can also be used to schedule more complicated tasks such as Data Compaction on Integral Volume sets and Recording of CD/DVD-R media. The c:\qstar\vl\files\conf file keeps all the configuration information for the QStar commands that can be run as delayed jobs. Once a command is submitted, a job will be created and placed into the delayed jobs queue list that is managed and controlled by the QStar VL scheduler process.

Displaying the Delayed Jobs under VL Scheduler Control in the Delayed Jobs Queue List From Delayed Jobs the System Administrator can set up the option for each type of delayed job, manage and monitor the delayed jobs in the delayed jobs queue list. Delayed Jobs lists all the information for the delayed jobs present in the queue controlled by the QStar VL scheduler process. The VL scheduler will start to process the jobs in the list at the time set by the System Administrator.

The types of jobs that can be delayed and run under the VL scheduler’s control are as follows:

Record: Jobs related to the Recording procedure. Copy: Jobs related to the Copy Media procedure. Compare: Jobs related to the Compare procedure, which follows the Copy Media procedure. Reuse: Jobs related to the Compaction procedure. Erase: Jobs related to the Erase procedure. Offsync: Jobs related to synchronizing SDF mirror media procedure. Publisher: Jobs related to the Recording procedure made with Publisher device.

of 152

Figure 5.185 - Displaying and Setting the Delayed Jobs Information

The Jobs can all be displayed together or a selected type of job may be displayed by placing a check mark in the box for the job type required. By default, all types of jobs are displayed.

The displayed information for each job is as follows: Job ID, Job, Status, Registration Date, Job Name, User ID, User Hostname, Delayed Start Date.

The jobs will change their status as Waiting, Started, Done, Error and can be displayed by status placing a check mark in the box for the status required. By default, the jobs are displayed for all types of status.

The delayed jobs listed on Delayed Jobs can be refreshed by selecting the Refresh button.

By default, the delayed jobs information is displayed for All Hosts and All Users.

However, it can be displayed for a specified User or Host by enabling the From User and From Host buttons. The User “0” is assigned to the Administrator. Once a command is submitted, a job will be created and placed in the delayed jobs queue list that is managed and controlled by the QStar VL scheduler process. To display the Delayed Jobs setting and properties, from Delayed Jobs, select the VL Conf button. Once the VL Conf button is selected, the VL Configuration window will appear. This window will include different tabs where all the configuration information is kept for the QStar Commands that can be delayed. Note: The information displayed in the VL Configuration window is kept in a special file called “conf” under the c:\qstar\vl\files directory.

Figure 5.186 - Displaying and Setting the Delayed Jobs Information

of 152

Displaying and Setting QStar Command Under Cron Job

Figure 5.187 - Displaying and Setting the VL Configuration Properties

The VL Configuration window. From this window is possible to set under QStar Scheduler control any command available on the Software.

Displaying and Setting the General Delayed Jobs VL Configuration Properties


The VL Configuration window will appear displaying the General Delayed Jobs VL Configuration properties: Keep Done Records: Number of latest records kept in the delayed jobs queue list. The default number is 7; the System Administrator can change this by typing the new value.

of 152

Displaying and Setting the VL Configuration Scheduled Archive Properties

Select the required Integral Volume set from the drop down menu on Migration View and then select the Delayed Archiving button and place a mark in the Enabled check box and select Schedule button. An additional window will appear to set the schedule.

Figure 5.189 - Starting the Scheduled Archive Procedure


The configured schedule will then be submitted as a Delayed Job. The schedule can be modified from here, or from Delayed Jobs. If the schedule is no longer needed, it can be deleted from the Delayed Jobs tab, or remove the mark in the Enabled check box as shown in previous Figure.

of 152

Select the required Delayed Job, then select the Schedule button, this will then allow the scheduled archive time to be modified, if the schedule is no longer required, it may be removed by Highlighting the delayed job record and selecting the Delete button. Note: Each mounted Integral Volume set has its own archiving policy, so it is recommended they do not all take place at the same time, if there are more mounted Integral Volume sets than drives in the library, this could lead to excessive media swapping.


Displaying and Setting the VL Configuration CD/DVD-R Delayed Recording Properties These options are related to the write options for CD/DVD-R devices managed by the QStar CD/DVD Master Software. A full explanation regarding the QStar CD/DVD Master Software can be found in the QSTAR CD/DVD MASTER manual.


Max Parallel Recording: The number of parallel recordings defines the number of images that can be recorded at the same time; this will also define the number of drives that can be used simultaneously for recording.

Select Record tab to display the default Record VL Configuration properties: Images Dir Path: The Images Directory on the server where the temporary image files that will be recorded to the CD/DVD-R media will be stored. Image Max Dir Size (MB): Max Size of the Images Directory. Direct: Type of recording procedure allowed. Allowed Hosts: Hosts allowed to use the Direct write procedure. Every Host name must be separated by a comma. Delayed Time: The Start Time and Stop Time the VL scheduler will process the delayed jobs in 24-hour mode. A 0:0 0:0 value ensures the jobs will not be delayed and will be processed immediately after the ISO/UDF image has been completely transferred to the Images Directory.

of 152

Managing the Delayed Jobs The list of jobs and the status of the delayed jobs are displayed on Delayed Jobs view pane. In the example, the jobs with the names “QStar_Release”, “Erase Shelf #12”, “Copy Media #1” are present in the delayed jobs queue list. They were registered on the list respectively with Job ID 1, Job ID 2 and Job ID 3 and with same Registration Date. Currently these jobs have a Status of Waiting For Time. The Delayed Start Date information is not visible on the figure below; it can be displayed by moving the scroll bar to the right. However, the Delayed Job Start Date columns will be empty if the default time settings are used from the VL Configuration window.

The delayed jobs listed on Delayed Jobs view pane are displayed in the order they were added to the delayed jobs queue. If different types of libraries are connected to the same server a combination of different delayed jobs may be present in the delayed jobs queue. These jobs will differ mainly in the Job ID, Job Type and Job Name. The jobs will be processed according to the priority order specified. The job that has the highest priority in the queue is the job that is displayed at the top of the list. The job at the top of the list will be the first delayed job to be processed if the Delayed Start Time is the same for all types of delayed jobs.

Figure 5.193 - Managing the Delayed Jobs

Figure 5.194 - Managing the Delayed Jobs

To change the priority order of the jobs, Highlight the job information and select the Up or Down arrow button. The delayed jobs listed on Delayed Jobs can be refreshed by selecting the Refresh button. Double click on the job record to display detailed information about a job in the delayed jobs queue list. Note: The User ID "0" is the Administrator.

of 152

To delete a job from the delayed jobs queue list, Highlight the job and select the Delete button. The Delete button can be used to clear completed, completed with error, and unwanted incomplete records. Once a job for the delayed recording procedure is removed from the list the job is cancelled and the associated image file in the Images Directory is removed.

In the example, the recording, the erasing and the copying were completed successfully, the Status of the job with Job ID 1 Job ID 2 and Job ID 3 were changed to Done. If an error occurred during a Delayed job, an error status will be displayed in the record regarding the job in Delayed Jobs view pane. Additional information of the error can be displayed by double clicking on the job record. The Syslog will report additional information about the error encountered during the job procedure.

Figure 5.195 - Displaying the Delayed Job Status for a Multiple Jobs

of 152

DISPLAYING AND SETTING THE VL CONFIGURATION OPTIONS The c:\qstar\vl\files\conf file not only keeps all the configuration information for the QStar commands that can be run as delayed jobs but also keeps the information of different options and features that are available under the VL Control. The options available in the conf file are represented with a key word that identifies the delayed command under the VL scheduler's control. The key words are as follows: RECORD: Option related to the Recording procedure. COPY: Option related to the Media Copy procedure. CMP: Option related to the Compare Procedure, which follows the Media Copy procedure. REUSE: Option related to the Compaction procedure. ERASE: Option related to the Erase procedure. ARC: Option related to the Archiving procedure. Below is an example of the content of the conf file:

# VL Configuration File

RECORD Images Dir Path = "C:\QStar\vl\files\cd_images"

RECORD Images Max Size MB = "650"

# RECORD Direct - {Prohibited | Allowed | Allowed Hosts}

RECORD Direct = "Prohibited"

RECORD Allowed Hosts = ""

RECORD Delayed Start = "0:0 0:0"

RECORD Max Parallel Recording = "0"

COPY Jb Name = ""

COPY Start Shelf Number = "0"

COPY End Shelf Number = "0"

# This parameter allows to specify vlcopy buffer capacity in MB (64:256:1024). COPY Buffer Capacity Used For Tape Volume Copy = "256"

COPY Interchange Worm Rewritable Media = "No"

COPY Delayed Start = "0:0 0:0"

COPY Compare After Copy = "No"

CMP Delayed Start = "0:0 0:0"

REUSE Delayed Start = "0:0 0:0"

ERASE Delayed Start = "0:0 0:0"

ARC Delayed Start = "0:0 0:0"

Keep Done Records = "7"

Blank Platter Threshold = "0"

Erase Platter Threshold = "0"

Monitor Blank Mail Address = ""

Return Error on Access to Offline Media = "Yes"

of 152

# Remote Administration - {Prohibited | Allowed | Allowed Hosts}

Remote Administration = "Prohibited"

Remote Administration Allowed Hosts = ""

Big Space Root Dir = ""

Minimum Filesystem Space Available = "0"

FSI NFS Port = "5005" Log File Control Mask = "0"

SCSI Server MiC Mail notifications = "No"

UDF/ISO Bridge Part (UDF or ISO) = "UDF"

SCSI Server Port = "5001"

JB Server Port = "5002"

MM Server Port = "5003"

VL Server Port = "5004"

Mirror Slave Port = "5015"

Centera Server Port = "5281"

Crypto Server Port = "0"

QPublisher Server Port = "5006"

Displaying and Setting the VL Configuration for Offline Media Request Properties

Figure 5.196 - Displaying and Setting the Offline Media Properties The request can be cancelled using the Console view pane. This will suspend all user requests to the Integral Volume set until the event is satisfied. In either case, an offline media request is sent to the Console, Syslog and Mail Notification (if enabled).

Select Misc. tab to display the Offline Media Request properties. The Return Error On Access To Offline Media option sets whether access to the Integral Volume set is suspended or not by an error until an offline media request has been satisfied. By default this option is enabled, in this mode, an I/O error is returned to the user if the media is out of the library. The System Administrator will immediately receive an error for an offline media request. At this time the System Administrator can satisfy or cancel the request. The error will be posted to the Syslog, Console and Mail Notification (if enabled). The users will continue to have full access the Integral Volume set. If deselected, then the QStar Server will hold the I/O request until the offline request is satisfied by importing the media, or the network timeout period has expired. This timeout may be altered from the default 45 seconds by the utility “setsesstimeout.exe” in the QStar bin directory.

of 152

Displaying and Setting the VL Configuration Threshold Blank/Erased Media Properties

Select Misc. tab to display the Threshold properties. This option allows the System Administrator to receive an E-Mail notification when a set number of Erased or Blank media are left in the library. By default this option is disabled by setting a value of “0” for Blank/Erase Media Threshold. In the example the threshold of the Blank/Erase media is set to “3” the System Administrator can receive an E-mail notification when this level has been reached or passed by modifying the Threshold parameters and adding an email address as displayed in the example.

Figure 5.197 - Displaying and Setting Threshold Blank/Erased Media Properties

Displaying and Setting the VL Configuration for the Remote Administration Properties

Figure 5.198 - Displaying and Setting the Remote Administration Properties

Select Misc. tab to display the Remote Administration properties. By default, the Remote Administration is Prohibited. Select Allowed or Allowed Hosts to enable the Remote Administration. For more information, please refer to the Remote Administration section later in this chapter.

of 152

Displaying and Setting the VL Configuration for the Big Space Root Directory Properties Select Misc. tab to display Big Space Root Director properties. By default, the Big Space Root Directory is not defined. This directory can be used as follows: A) This directory is used to store the backup images created by a UDF Spanning Integral Volume set. If it is not defined, all backup images will be created in the respective cache root directory for each Integral Volume set. If it is defined, a common directory will store all the backup images for all Integral Volume sets. The directory name can be changed as required by the System Administrator, who must ensure that the specified root directory location has been created and has adequate space to store all the backup images. B) This directory is used to store the images created during the Media Copy procedure of a UDF Media. By default, Media Copy procedure will copy from a source media to a destination media, if the big space root directory is specified the copy will be done from media to image and from image to destination media.

Figure 5.199 - Displaying and Setting the Big Space Root Directory Properties The Directory path used for image backup is the one before comma. The Directory path for the copy is the one after comma.

of 152

Displaying and Setting the VL Configuration for the Minimum File System Space Available

Figure 5.200 - Displaying and Setting the Minimum File System Space Available

Select Misc. tab to display Minimum File System Space Available properties. The SDF, TDO or UDF, LTFS Spanning file systems, using the dynamic allocation feature, automatically adds new media to the Integral Volume set once the file system is full. With dynamic allocation, the file system can grow automatically until reaching the Quota value that is set by default to 2048 media per Integral volume set. The Minimum Filesystem Space Available option allows the System Administrator that are using applications that require a minimum amount of space before sending any data to the mount point (Local Drive) to configure the minimum amount of space reported by the QStar file system when the statfs command is issued by typing in the size (MB) to report when the statfs command is issued.

Displaying and Setting the QStar Server Port Configurations

Server Ports keeps all the port configuration information used by the the QStar Software servers. If necessary the System Administrator can change the port number used by the QStar Software in the case of a conflict with other applications, once the port is changed the QStar servers must be stopped and restarted.

Figure 5.201 - Displaying and Setting the QStar Server Port Configurations

of 152

ADMINISTRATION INTERFACE WITH LIMITED FUNCTIONALITY

Figure 5.202 - Limited User Administration Interface

If a user opens the Administration Interface that is not in the priv.users file access will be limited to the list below. The QStar Administration Interface will open with limit access, this will prevent users form running portions of the Interface that might cause serious issues.

The priv.users file is located in the C:\QStar\install. Editing this file will allow/prevent rights based on the users permission on the server. Removing the Administrator from the file will cause the QStar Administration Interface to open with limited access.

The following outline is separated into the various view panes of the QStar Administration Interface. Starting from the top all the view panes are listed displaying the functions that are Unavailable and Available from the local Administration Interface: Server: Unavailable view pane: Available view panes: Server Status Unavailable Functions: Change Server Priority Starting / Stopping Servers Installing / Un-installing Software Available Functions: Server / Daemons Status Storage Libraries: Unavailable view pane: Configuration Unavailable Functions: Configure and Reconfigure Library Available view pane: Status Available Functions: Element Status

Edit Library Parameters Drive/Shelf Manipulation (On/Off/Reset)

Access To Troubleshooting (all low level qscsi commands)

of 152

Statistics Available Functions: Library Statistics Information

Console Available Functions: View Status Refreshing Status Media: Unavailable view pane:

Available view pane: Online Media Unavailable Functions: Scheduling Erases

Erasing Media Available Functions: Refreshing Media Media Status Import/Export Media Offline Media Available Functions: Adding Offline Media Locations Editing Offline Media Locations Database Unavailable Functions: Fixing Database Available Functions: Verifying Database Consistency Copy Media Available Functions: Copying Media Comparing Media Scheduling Copy Media Integral Volumes: Unavailable view pane: Available view pane: Volume Management Unavailable Functions: Integral Volume set properties Editing and viewing Integral Volume set options Mounting on Server Restart Altering Cache Size, and HPC/LPC Attributes Switching to Mount on Clean Cache, and Rebuild Database

Available Functions: Creating Integral Volume Sets

Mounting Integral Volume Sets Unmounting Integral Volume Sets Starting / Stopping Secondary Mirrors Viewing Integral Volume Sets Information

of 152

Media Management Unavailable Functions: Adding Media to an Integral Volume Removing Media from an Integral Volume Migration View Available Functions: Migration Parameters/Status Archiving HPC / LPC Adjustment Restart Mirror Compaction Available Functions: Media Usage Status Media Usage Compaction Scheduling Compaction Explorer Unavailable Functions: Keep in cache Don't Keep in Cache Pin-to-cache Policy Keep Full File Don't Keep Full File Add tree Copy Tree Copy Data (Prefect) Remove Tree Remove Data Attributes Available Functions: Properties Log: Available view pane: Syslog Unavailable Functions: Clean Log Scsi Log Email Notification Delayed Jobs Unavailable Functions: VL Conf options

of 152

QSTAR REMOTE ADMINISTRATION INTERFACE The QStar Remote Administration Interface can be started by running the program located in C:\qstar\bin\admin.exe (if default installation path is used), this program can be copied to a remote system or run remotely.

Figure 5.203 - Remote Administration

Before using the admin.exe command to remote administer a remote host the Remote Administration option must be enabled on the local server. Select the Misc. tab to display the Remote Administration properties. By default, the Remote Administration is Prohibited.

Select Allowed or Allowed Hosts to enable the Remote Administration. The Allowed option allows Remote Administration of the QStar Software from any client machine. The Allowed Hosts option allows Remote Administration of the QStar Software only from specified hosts (client machine). Every Host name must be separated by a comma. Note: In the example, Allowed Hosts option is used. Note1: Once changed, the service has to be stopped/started to take effect.


of 152

Once the Remote Administration is enabled the System Administrator can run the admin.exe command. When running the admin.exe without any options, the Software will open a Browse For Computer window to select which system is to be administered. Alternately, running the admin.exe command with some options allows connecting directly to a specific host. If the hostname or IP address of the server is known the program can be started as follows: C:\qstar\bin\admin.exe -host production or C:\admin.exe -host 10.10.10.10 Note: In the example, production is the hostname and 10.10.10.10 is the IP address of the server. If the product installed is Data Director (Mirroring) add -ddr option to the command as follows: C:\admin.exe - ddr -host 10.10.10.10


The admin.exe program can be run in windows 2000/2003/XP/Vista/7/2008. Not all functionality is available for the remotely administered system and some view panes are missing completely from the Remote Administration Interface. Note: At the top of the QStar Administration Interface the IP and Sever Name are displayed for the system being remotely managed.

The following outline is separated into the various view panes of the QStar Administration Interface. Starting from the top all the view panes are listed displaying the functions that are Unavailable and Available from the Remote server. Server: Unavailable view pane: Available view panes: Server Status Unavailable Functions: Change Server Priority Access Security view pane Starting / Stopping Servers Installing / Un-installing Driver Software Available Functions: Server / Daemons Status

of 152

Storage Libraries: Unavailable view pane: Configuration Unavailable Functions: Configure and Reconfigure Library Available view pane: Status Available Functions: Edit Library Parameters Drive/Shelf Manipulation (On/Off/Reset) Element Status Access To Troubleshooting (all low level qscsi commands) Statistics Available Functions: Library Statistics Information

Console Available Functions: View Status Refreshing Status

Media: Unavailable view pane:

Available view pane: Online Media Unavailable Functions: Scheduling Erases Import/Export Media (Appears Available) Available Functions: Refreshing Media Media Status Erasing Media Offline Media Available Functions: Adding Offline Media Locations Editing Offline Media Locations Database Available Functions: Verifying Database Consistency Fixing Database Copy Media Unavailable Functions: Scheduling Copy Media (Appears Available) Available Functions: Copying Media Comparing Media Integral Volumes: Unavailable view pane: Available view pane: Volume Management Unavailable Functions: Creating Cache Directories Browsing Local Machine For Cache Locations

of 152

Available Functions:

Creating Integral Volumes (cache location must exist will not be created automatically) Mounting Integral Volume set Unmounting Integral Volume set Starting / Stopping Secondary Mirrors

Viewing Sets Information Altering Cache Size, and HPC/LPC Attributes Switching to Mount on Clean Cache, and Rebuild Database

Mounting on Server Restart Media Management Available Functions: Adding Media to an Integral Volume Removing Media from an Integral Volume Migration View Available Functions: Migration Parameters / Status Archiving HPC / LPC Adjustment Restart Mirror Compaction Unavailable Functions: Scheduling Compaction Available Functions: Media Usage Status Media Usage Compaction Explorer Unavailable Functions: Properties Available Functions: Keep in cache Don't Keep in Cache Pin-to-cache Policy Keep Full File Don't Keep Full File Add tree Copy Tree Copy Data (Prefect) Remove Tree Remove Data Attributes Structured Storage Devices: Unavailable view pane: Available view pane: QSSD Configuration

Available Functions: Define Refresh Rename Delete

of 152

Log:

Unavailable view pane: Scsi Log Available view pane: Syslog Delayed Jobs Unavailable Functions: Delayed Erases Delayed Copy Media Delayed Compaction

Email Notification

of 152

of 68

This chapter describes, in detail, the inner workings of the magnetic cache. The magnetic cache serves as the interface between the user requests and the archive media. All migration to and from the archive media is transparent to all users and applications due to the advanced underlying features of the magnetic cache. Included in this chapter are the following:

• Definitions of commonly used terms

• Descriptions of cache management

• Procedures for recovery after an error has occurred

• Descriptions of cache files created in the cache_root directory

• Examples of how to use the Migration Manager commands

MIGRATION MANAGER DESCRIPTION........................................................................................ 3

Migration Manager Terminology .............................................................................................. 3 Events............................................................................................................................................ 4 File Migration Attributes ............................................................................................................ 4 Migrator Manager Parameters for an Integral Volume Set................................................ 5

CREATING THE CACHE .................................................................................................................. 6 Non Stop Write Cache Option .................................................................................................. 7 Set Features Cache Options ..................................................................................................... 7 Extra Applications Options ........................................................................................................ 8 Read Only Grace Period Cache Option ................................................................................... 8 Retention Period Cache Option ................................................................................................ 9 Write Once and Deny Rename Options................................................................................ 10 File Data Digest Options.......................................................................................................... 10 Cryptography Option................................................................................................................ 11 Prefetching Options .................................................................................................................. 11 Multiple Cache Area Mechanism ............................................................................................ 12

MODIFYING THE CACHE PARAMETERS .................................................................................... 13 FILE MIGRATION ........................................................................................................................... 15

Archiving ..................................................................................................................................... 15 Scheduling an Archive using QStar scheduler .................................................................... 16 File Replication and Prefetching from Backend File System to the Cache ................... 18

Replication Mode ................................................................................................................... 18 File Prefetching...................................................................................................................... 18

MANAGING THE CACHE ............................................................................................................... 22 Structure and Files in the Cache Database ......................................................................... 22 The Cache Files ......................................................................................................................... 22

MIGRATION MANAGER COMMANDS FROM THE DOS PROMPT ........................................... 26 MOUNTING AN INTEGRAL VOLUME SET .................................................................................. 27 CHECKING THE MOUNTED STATUS OF AN INTEGRAL VOLUME SET................................. 28 THE INTEGRAL VOLUME SET MOUNT PROPERTIES............................................................... 29 MOUNTING AN INTEGRAL VOLUME SET ON SERVER STARTUP ......................................... 30 ADDING LOCAL DRIVE LETTER TO QSTAR FILE SYSTEM .................................................... 30 LOCAL DRIVE LETTER WITH SHARE DRIVE OPTION............................................................. 32 MAPPING THE QSTAR-SERVER DRIVE...................................................................................... 33 MAPPING THE QSTAR-SERVER DRIVE FROM A DOS PROMPT ............................................ 35

of 68

MOUNTING THE QSTAR-SERVER DRIVE FROM A UNIX CLIENT ......................................... 35 ERROR CONDITION DURING MOUNT OPERATIONS.............................................................. 37 UNMOUNTING AN INTEGRAL VOLUME SET............................................................................. 40 MOUNT ON DATE OPTION ........................................................................................................... 41 ARCHIVING NOTIFICATION ........................................................................................................ 43 DISPLAYING AND MONITORING CACHE INFORMATION ...................................................... 44

Cache Information Displayed for a Integral Volume set .................................................. 44 ERROR HANDLING AND RECOVERY FOR ALL FILE SYSTEMS.............................................. 48

Error Condition while Processing a Delayed Event ............................................................ 48 Error Condition in the Cache .................................................................................................. 48 Clearing Error Condition in the Cache .................................................................................. 49 Integral Volume System or Disk Crashes............................................................................ 49

POWER FAILURE, SYSTEM CRASH OR REBOOTING WITHOUT UNMOUNTING................ 50 Transaction Logging Cache ..................................................................................................... 51

MANAGING THE FILES IN THE CACHE FROM THE EXPLORER VIEW PANE ...................... 52 Removing a Tree from the File System ........................................................................... 55 Adding a Tree to the File System ...................................................................................... 56 Displaying the Covered Information of a File ................................................................. 58 Checking the Properties from Explorer View Pane ........................................................ 59 Displaying the Offline Information of a File .................................................................... 60 Changing the Owner/Group/Permission of a Directory or File.................................... 61

MANAGING THE CACHE PARAMETERS ..................................................................................... 64

of 68

MIGRATION MANAGER DESCRIPTION The Migration Manager was designed to provide a Hierarchical Storage Management (HSM) system view of a collection of diverse types of storage media. This includes magnetic disks and RAID, Optical, CD/DVD or Blu-ray libraries and drives, Tape libraries and drives. The job of the Migration Manager is to combine all of these technologies into a Virtual File System called an Integral Volume set. An Integral Volume set looks and feels to the user like a standard magnetic disk. This means that all standard applications, including network-based applications, can work with the Integral Volume set without modification and in the same manner that they would work with a normal magnetic disk. Logically, the Migration Manager is divided into two Software components: The first is called the Migration Server. The Migration Server is responsible for servicing all requests for the Integral Volume set. The Migration Server is primarily responsible for the first tier of the storage management hierarchy; in other words it manages the data which resides on the magnetic disk cache. The Migration Server is tuned to provide the highest performance for retrieving data that resides in the magnetic disk cache. It is also responsible for enforcing a set of Migration Policies, which determines when and what data is migrated to and from the secondary tiers of storage. The second component is the Migrator (File System Migrator). The Migrator is responsible for managing the archive(s). There are actually several different versions of the Migrator, depending on the type of storage managed by the archive and the functionality required when migrating the data.

Migration Manager Terminology Archive A mass storage resource that is the source and destination of all the files accessed by clients.

Cache A space (or a separate file system) that is used for temporarily holding data and metadata (directories and inodes - file status information) from the Archive.

Event An action to be performed which changes the state of a file or the file system itself.

Delayed event An event that has been performed on the cache but has not yet been performed on the Archive.

Page A portion, which every file is logically divided into one or more 64 Kb chunks, called pages.

Primary page A page that has been written to while it was present in the cache (that is, a page that has been modified in the cache but is not yet archived).

Replicated page A page which has been copied into the cache from the Archive.

Archived page A page, which has been written to the Archive but is still in the cache.

Archived since mount Number of Primary pages archived after last mount.

Replicated since mount Number of Replicated pages after last mount.

Archiving Writing the primary data from the cache to the Archive. Archiving can also refer to processing the delayed events.

Replicating Copying data from the Archive into the cache. Waiting Reading or writing operation waiting for media to be loaded. Reading Reading data or metadata from the Archive. Pending Reading or writing operation is pending until another request passed to migrator is completed.

of 68

Events Events are the basis of the Migrator Manager functionality. Every action on the Integral Volume set is represented by an event. The Migrator Server performs all changes that are to be carried out in response to an event both in the cache and on the Archive. In the cache, events are performed immediately. In the Archive, they are performed later.

The following groups of events are supported:

Events generated by file and I/O syscalls Events that change the file system state: assoc, attrib, copy, del, dir, mkdir, rename and rmdir syscalls. A free-file event is generated when the link count of the file drops to 0 and this file is no longer referenced in the kernel.

Page fault and Directory faults If the required page is not present in the cache, a read and write generate a page-fault event. Any access to a directory in which contents are not stored in the cache generates a dir-fault event.

Unmount Event Generated by unmount syscall.

Events from the Migrator Manager commands Generated by the mmcmd arc, mmcmd chmod, mmcmd param, mmcmd purge, mmcmd resume, mmcmd subtree commands.

Delayed Events Events, which have been generated but not processed on the Archive, are called delayed events. Delayed events are stored in the delayed queue and processed on the Archive in the same order in which they were generated. Processing of the delayed queue is called archiving.

File Migration Attributes Migration attributes control the behavior of how, when, and if the file is migrated. The following table lists the attributes which can be set on a per file basis. These parameters are changed using mmcmd chmod (mmchmod) command, and can be viewed using mmcmd ls (mmls) command or from the GUI using the Explorer view pane.

Full File Migration Whenever a file is migrated, its entire contents are moved completely from one tier of the hierarchy to the next.

Per Page Migration Only those pages, which are needed to satisfy the request, are migrated. An access to the file causes a page containing the referenced bytes to be read into the cache. Similarly, if a file in the cache is modified, then only those pages, which contain modified data (Primary Data), are archived.

Keep in Cache Any page of the file that is now present in the cache or will be put in the cache cannot be swapped out of the cache.

Pin to Cache This option allows parts of the file to be kept in cache. The difference between keep in cache and pin to cache is that with pin to cache it is possible to specify the size and part of the file to be retained in the cache.

of 68

Migrator Manager Parameters for an Integral Volume Set Parameters listed below control the behavior of the Integral Volume set. All of them can be set using the vlcmd cache (vlcache) and the mmcmd param (vlcache) commands or from the QStar GUI.

Number of Pages in Cache Maximum number of pages which will be used for caching data to magnetic disk.

Low Primary Capacity When archiving is initiated, either by Demand Archiving or Scheduled Archiving it will continue until the number of primary pages in the cache is less than or equal to this value. Default is set to 0.

High Primary Capacity This value specifies the number of primary pages that may reside in the cache. When the number of primary pages reaches this value then Demand Archiving will be initiated and will continue until the Low Primary Capacity value is reached. Default is set to 80% of the cache size.

of 68

CREATING THE CACHE

Figure 6.1 - Creating an Integral Volume set (Cache Parameters)

Choose a name for the Integral Volume Name (maximum 12 characters) and select a size for the Cache (minimum 4MB). To select or create the Cache Location directory, press the Browse button. The Page Size allows a cache page size other than the Default 64KB to be used, changing the page size allows for more efficient use of the space in the cache if the average file size is small. However, the performance will be slower with the smaller the page size selected. The Page Sizes that are available are from 1KB up to 256KB.

Select the folder to be used for the cache or create it using the New Folder button and then type in the name of the folder or type the path and folder name in the Cache Location box. The Software will create the folder when the OK button is selected. Note: The cache location must have at least 2GB of free space available; if not the mount procedure of the file system will be denied.

Figure 6.2 - Creating the Cache Folder

of 68

Figure 6.3 - Creating an Integral Volume set (Cache Parameters)

Choose the File System Type Choose the Archive Media Type To finish the creation process, select the Create button. The Readonly option allows mounting a file system in read only mode. The Spread option allows the Integral Volume set to spread across multiple libraries automatically. Without this option the Integral Volume set will reside within the same library it was created in. However, media from another library can be manually added to the Integral Volume set at any time. Mount As option chooses the local drive letter to be used to mount the Integral Volume set. Share drive option allows to share by default the file system in the network.

Non Stop Write Cache Option The Stop on covered error option (Non Stop Write Cache Option) if disabled, allows data to continue to be written to a large cache even if there is a covered error; this option determines if service to the users is stopped or continued while the problem causing the covered error is rectified; typically a hardware fault on the library. By default this option is enabled this means that after a covered error the file system returns an error on any write operations until the error condition is cleared.

Set Features Cache Options In Magnetic Cache File System the System Administrator can specify several options that are called “set features” as they define the way the Integral Volume set will be used. On mount, “set features” are stored in the root directory stream “q_set_features”. These features are: grace period retention period worm-fs no-worm-rename digest type encryption type prefetching mode prefetch priority period back end retention

of 68

The q_set_features stream is created on the first mount if the Integral Volume set has features specified during the creation or modification of the Integral Volume set. On the next mount the features will be taken from the stream unless they are overridden by new values specified selecting the Properties button in the Integral Volumes page and then selecting the Advanced button. A feature can be soft or permanent (changeable or fixed). Whether a feature is permanent or soft is specified in Advanced File System Setting windows, by default it is soft. A new value of soft features specified in Advanced File System Setting windows will be in effect after the next mount. It overrides the value in the q_set_features stream and the stream will be updated on mount. The soft/permanent attribute of the feature is also stored in the q_set_features stream.

Extra Applications Options -A [h=]{0|1} option is available only using vlcmd cache (vlcache) command line. This option allows (1) or disallows (0) to update a file access time. This affects a request to update an access time without updating a modification time. If option -A is 1, such an update is allowed, if 0 - it is ignored. The default is 0 - no access time update. The prefix h= specifies a permanent (hard) time update feature.

Read Only Grace Period Cache Option The QStar Software has a feature that allows data to be stored for a grace period before it is set to read only. The Grace Period option is available by selecting the Advanced button. The Grace Period option is configurable on an Integral Volume set basis and can be set by seconds, minutes, hours, days and years. The Grace Period option is used to specify a timeout for modifying the state of an existing file. A file may be modified, providing the user has sufficient privileges, until the grace period has expired, it is then marked as read only. This feature goes further than the standard UNIX read only flag, as even the System Administrator cannot remove the read only flag for files, the only way to overcome this, is to remove the Grace Period option. Enabling this feature provides a WORM file system, even with rewritable media, ideal for corporate data archiving compliance requirements.

Figure 6.4 - Grace Period (Cache Parameters)

This period is counted from the last file modification (file modification time) and specifies a period of time during which a file or its attributes can be modified. The grace period affects regular files and does not affect directories. The grace period for a file expires when the difference between the current time and the file modification time becomes equal to or greater than the grace period. Every time the file or its attributes are modified, while the grace period is still in effect (not expired yet), the file modification time changes and the grace period is counted from this new modification time.

of 68

Once the grace period has expired, the file is treated as read-only even for the superuser. The behavior is different if both the read-only grace period and the retention period are specified. In this case, a file can be modified either before the grace period expires or after the retention period expires. The Grace Period option can be soft or permanent (changeable or fixed), by default it is soft. If the grace period is soft, it can be removed from the Integral Volume set by setting it to 0. If it is done it will be in effect from the next mount. The feature is permanent if the System Administrator will place a check in the Permanent check box, in this case the grace period value will be written in the in the set feature stream in permanent mode in the covered file system (tape, optical, object storage). The value cannot be changed in the future. Even if the Integral Volume set is mounted with a clean cache and with grace period modified in the set database, the original value will be read and restored from the covered file system. The Grace Period option can be used also in conjunction with Deny Rename option. In this case after the grace period expires a renaming operation is prohibited. By default, it is allowed.

Retention Period Cache Option

Figure 6.5 - Retention Period (Cache Parameters)

The Retention Period option is available by selecting the Advanced button. The Retention Period option is configurable on an Integral Volume set basis and can be set by seconds, minutes, hours, days and years. The Retention Period option is used as a timeout, prohibiting modification or removal of the file. Once a file has reached a point in time after the retention period, the file may then be modified or deleted from the file system. This period is counted from the last file modification (file modification time) and specifies a period of time during which the file cannot be removed. The retention period affects regular files and does not affect directories. The retention period for a file expires when the difference between the current time and the file modification time becomes equal to or greater than the retention period. Every time when the file or its attributes are modified (if modification is allowed by the grace period) the file modification time changes and the retention period is counted from this new modification time. Once the retention period has expired, the file can be removed.

The Retention Period feature can be used alone or in conjunction with the Grace Period feature. If both the Retention and Grace Periods are specified, the retention period can terminate the read-only status set by expiration of the grace period. Practically a file can be modified either before the grace period expires or after the retention period expires. The benefit to this feature is the ability to lock a file to read only status for the time the file is required to remain available within corporate guidelines. This feature goes further than the standard UNIX, read only flag, as even the System Administrator cannot remove the read only flag for files under retention period management. Enabling this feature provides a WORM file system, even with rewritable media, ideal for corporate data archiving compliance requirements.

of 68

The Retention Period option can be soft or permanent (changeable or fixed), by default it is soft. If the retention period is soft, it can be removed from the Integral Volume set by setting it to 0. If it is done it will be in effect from the next mount. The feature is permanent if the System Administrator will place a check in the Permanent check box, in this case the retention period value will be written in the in the set feature stream in permanent mode in the covered file system (tape, optical, object storage). The value cannot be changed in the future. Even if the Integral Volume set is mounted with a clean cache and with retention period modified in the set database, the original value will be read and restored from the covered file system. The Retention Period option can be used also in conjunction with Write Once option. In this case the Retention Period cannot be used with the Grace Period option.

Write Once and Deny Rename Options The Write Once feature provides a WORM file system, even with rewritable media, which is ideal for corporate data archiving compliance requirement. With a check in the Write Once check box the Write Once option is enabled and the file system is WORM. If a check is placed also in Permanent WORM check box the feature is permanent, in this case the WORM feature value will be written in the set feature stream in permanent mode in the covered file system (tape, optical, object storage). The value cannot be changed in the future. Even if the Integral Volume set is mounted with a clean cache and the WORM option not configured in the set database, the original value will be read and restored from the covered file system. Working differently from Grace Period, once a file is written in the file system; the overwrite, remove and set size operations are prohibited. A file can only be appended and renamed. The Grace Period will be ignored if it is used in conjunction with this option. If Deny Rename option is enabled with the Write Once option, the renaming operation is prohibited.

File Data Digest Options

The Advanced File System Setting includes an add-on option (license required) that allows a digest (checksum) of the file in the cache to be calculated and to archive the digest value directly on the covered file system on the stream of the file. This digest value can be used later for verification of the integrity of the file. The Data Digest Algorithm available for the Integral Volume set are SHA1, SHA256 and SHA512, the SHA512 is the most secure digest but will be slower than using SHA1. If Permanent Prefetch or Permanent Period check box is checked, the option becomes permanent and it goes to “set features” stream of the set root directory. Special commands are used to verify the integrity of the files already archived. This is done by recalculating the digest and comparing it to that stored in the QStar stream at the time of the archiving. Please call QStar Support personnel for more detailed information. Note: This is a licensable feature.

Figure 6.6 - File Data Digest Option

of 68

Cryptography Option

Figure 6.7 - Cryptography Option

The Advanced File System Setting includes an add-on option (license required) that allows to encrypt the file on the covered file system. The Data Encryption Algorithm available for the Integral Volume set are; AES128, AES192 and AES256, the AES256 is the most secure but also slower than using AES128. If Permanent Encryption check box is checked, the encryption becomes permanent and it goes to “set features” stream of the set root directory. Please call QStar Support personnel for more detailed information about encryption feature. Note: This is a licensable feature.

Prefetching Options

The Advanced File System Setting includes 2 options for prefetching, these options are fully described in the File Migration section later in this chapter.

Figure 6.8 - File Prefetching Option

of 68

Multiple Cache Area Mechanism Each Integral Volume set has its own cache that is specified during the Integral Volume set creation. The information of the cache location is saved into the VL set database and is displayed using the Properties window. From the Properties window it is possible to specify only one cache location. If the System Administration needs to enlarge the cache size across different cache locations (different RAID) QStar has created a mechanism that allows spanning of the cache across different locations. Below is the description of cache area mechanism: 1) The cache areas file resides in c:\QStar\mcfs\files directory and is named "cache_areas.<set_name>". In this file the following instructions are reported: # Pathnames of next cache areas. # One pathname on a line. # Up to 4 areas can be listed. 2) The file is created empty when the Integral Volume is created and is removed when the Integral Volume is deleted. The user

can list cache areas before the Integral Volume set is mounted. With the Clean cache box in the Properties window selected, all the cache areas listed in the file can be cleaned.

3) The maximum number of additional cache areas is 4. The primary cache location specified in the set definition does not

belong to the list of cache areas, so the total number of cache areas is 5. If the list of cache areas contains the primary cache path or has duplicate paths or has more than 4 paths, an error is reported. The system reads the cache areas file and prints the cache area list and the numbers of free MB in each area on mount and when the Clear error condition state button is pushed from the Migration View pane.

4) The system periodically checks space in the current cache area. The area is considered full if the number of available blocks

reported by OS for the file system where the area resides is not greater than 1GB. For the primary cache we also take into account the space consumed by the migrator files (extra 30MB plus 200 bytes per user file in the cache). When the current area gets full, we smoothly switch to the next area (if any) without setting an error condition and interrupting a user application.

5) If the current area gets full and there is no more cache area listed in the cache area list, an error condition is set. If there are

less than 4 paths in cache areas list, a new area(s) can be added to the cache areas list by editing the cache areas file. The system reads this file and updates the list when the Clear error condition state button is pushed from the Migration View pane.

of 68

MODIFYING THE CACHE PARAMETERS To alter the Properties of an Integral Volume set select the Properties button. In the Properties window, the High Primary Capacity and Low Primary Capacity can be changed for the Integral Volume set. The High Primary Capacity (HPC) is the point at which the software will start demand archiving based on a % value of the allocated cache size. Default is 80%. The Low Primary Capacity (LPC) is the point at which the software will stop demand archiving based on a % value of the allocated cache size. Default is 0%. Note: The (HPC) and the (LPC) have no effect on an Integral Volume set with Read Only file system.

Figure 6.9 - Integral Volume Set Properties Note1: All changes made in these properties will take effect once the Integral Volume set is remounted and are set permanently.


Placing a check in the Local access only block will allow access to the Integral Volume set on the local host only. Placing a check in the Mount On Server Restart block allows automatic mounting of the Integral Volume set on the Server Restart. The Quota (maximum number of media allowed in an Integral Volume set) can be changed. The default number of the media is 2048. The Cache Location can be changed selecting the Browse button. The cache Page Size can be changed with the drop down selection, a Page Size from 1KB to 256KB may be selected. Note: All changes made in these properties will take effect once the Integral Volume set is remounted and are set permanently.

of 68

Changing the value in the Cache size block alters the size of the Cache for an Integral Volume set. Changing the value in the Page Size block alters the size of the cache pages for an Integral Volume set. When the Cache size or Page Size is altered, a check must be placed in the Clean cache block. Placing a check in the Clean cache block will rebuild all the files in the Cache Location directory for the Integral Volume set. This option for a Read and Write file system must be used carefully. Before mounting with a clean cache, be sure that no Primary data is present. If Primary data is left in the cache, it will be destroyed during the next mount. An Integral Volume set created with the Read Only file system cannot have Primary data because it is mounted in read only mode.


Note: All changes made in these properties will take effect once the Integral Volume set is remounted. The Rebuild database and Clean cache options are set only once for the next mount and all the others options are set permanently. Note1: The Properties window will display different information depending on the file system selected during the creation of the Integral Volume set. In the example, the properties windows of an Integral Volume set configured with TDO file system is shown.

of 68

FILE MIGRATION

Archiving Archiving is the copying of primary data from the magnetic disk (cache) to the archival media.

To start all data archiving from the magnetic cache to the archive media, select the Start Archiving button on the Migration View pane. The Periodic Archiving can be configured using the QStar Scheduler, see next sections for more detailed information.

Figure 6.12 - Starting an Archive

QStar Software supports three start archiving policies:

• Periodic Archiving - The System Administrator specifies a discrete time interval when the migration manager begins archiving. When periodic archiving is started, the migration manager begins processing delayed events until a stop archiving policy is satisfied. A copy of the data remains on the magnetic disk as archived data so you can quickly access it as needed without querying the slower archival media.

• Demand Archiving - The migration manager automatically begins archiving when the primary data on the magnetic

cache equals or exceeds the High Primary Capacity (HPC).

• User Initiated Archiving - The System Administrator initiates archiving on a selected Integral Volume set. This method lets you archive critical files as soon as they are written.

QStar also supports three stop archiving policies. These rules determine when the archiving cycle should cease. The supported policies are:

• All Delayed Events - All primary data and all delayed events are archived. This policy ensures that all files as well as all high level changes such as changing ownership or permissions are processed on the archive media. This is the default stop archiving policy.

• Low Primary Capacity (LPC) - The migration manager stops archiving once a certain amount of data has been

archived. This amount is determined by the value of the tunable parameter, Low Primary Capacity. This parameter is useful in controlling the archiving to a defined data amount decreasing the length of the archiving cycle.

of 68

• Agetime - Only files written prior to the agetime are archived. This user definable value maintains recently written data in primary form. This limit is highly useful for customers who mainly access recently written files. These files will remain in the cache until they exceed the agetime value.

The System Administrator sets the primary agetime and low primary capacity parameters based on Integral Volume set usage characteristics. To start archiving using the DOS prompt use the mmcmd arc command in the c:\qstar\bin directory to start the archiving of the files from the cache to the archival media.

mmcmd arc [-H host_name] {-l | -e | -a age | -s} [-w] -j {delayed_job_name | "default"}]

[-S cron_like_schedule]{set_name | filename}

Note: QStar recommends reviewing the explanation for the mmcmd arc (mmarc) command in Chapter 9 - Command Reference of this manual, while reading this section. Any archiving method, or all three, can occur in an Integral Volume set. However, a well-configured Integral Volume set uses periodic archiving as its primary method of controlling the migration cycle. This can be achieved using Delayed Archiving feature.

Scheduling an Archive using QStar scheduler Archiving can be configured to take place when the system is under less use, such as in the evening. This can be achieved by a Windows Scheduled Task or by QStar configuring a Delayed Job as in the following examples.

Select the required Integral Volume set from the drop down menu on the Migration View pane, select the Delayed Archiving button and then select the Enabled button. Once enabled is possible to configure the archiving policy by Age Time. Then select the Schedule button, the configured schedule will then be submitted as a delayed job. The schedule can be modified from here, or from the Delayed Jobs pane.


of 68


If Age Time option is not used is possible to configure the Periodic Archiving selecting the Schedule button. Once selected, configure the schedule parameters that will then be submitted as a delayed job. The schedule can be modified from here, or from the Delayed Jobs pane.

Select the required Delayed Job, then select the Schedule button, this will then allow the scheduled archive time to be modified, if the schedule is no longer required, it may be removed by Highlighting the Delayed Job, then selecting the Delete button. Note: Each mounted Integral Volume set has its own archiving policy, so it recommended they do not all take place at the same time, if there are more mounted Integral Volume sets than drives in the library, this could lead to excessive media swaps.


of 68

File Replication and Prefetching from Backend File System to the Cache

Replication Mode QStar’s migration manager allows replication (Migration of the data from backend file system to the cache), how many pages are replicated depends on the prefetching mode. The migration manager can replicate the data in two modes: data segment mode and full file mode. In data segment mode (Do not Keep Full File), displayed in Explorer page with (-f) attribute, a file is viewed as a collection of data segments of discrete size. Each segment can be migrated individually or collectively with other segments. In full file (Keep Full File) mode, displayed in Explorer page with (+f) attribute, the migration manager always migrates the complete file as a single entity up to 2GB. With large files, segmented migration is more efficient than full file migration. For example, imaging applications typically store a multi-page document as a single file, often as large as 100 Megabytes or more. In segment migration mode, only the pages that have been accessed or modified are migrated. This results in a substantial timesaving: it’s more efficient to migrate, modify, and archive two Megabytes (or less) than do the same with 100 Megabytes. Magnetic disk and archival media resources are used most efficiently, leaving more space on the magnetic disk for other data. In addition, segmented migration mode makes it possible to have files partially resident on magnetic and partially on the archival media. When a user application tries to read bytes from a file, a page containing these bytes is replicated from the covered file system into the cache. For a file without +f attribute, that is all that the read request does. An attempt to read a file with +f attribute induces prefetching (read ahead). Not only the page that contains the requested bytes is replicated into the cache but other pages are replicated as well (up to 2GB). QStar, depending by the technology used as storage device, will set different default values. For DVD/Blu-ray device the default is segmented mode (-f) for tape device is full mode (+f) these settings can be changed or displayed for a single file or for a directory using the Explorer page. Attributes are designated by the letters f and k (keep or not in cache) with the +/- prefix.

File Prefetching From different location on the GUI is possible to specify different prefetching option: Full Prefetching Mode The whole file is replicated into the cache. The read request that caused prefetching will be satisfied after the requested page is replicated but the prefetching will continue asynchronously and be done after all pages of the file are replicated. It makes no sense to use the full prefetching mode if the file size is greater than the cache size because the newly replicated pages would swap out previously replicated pages before the application would get a chance to read them. A similar situation can happen if prefetching of the new file would start before the application has read the previously prefetched file. Partial Prefetching Mode A piece of the file that contains the requested page is replicated into the cache. The size of that prefetching piece is equal to minimum of 2GB and 1/10 of the cache size. A file is considered to be a sequence of such pieces. The read request that caused prefetching will be satisfied after the requested page is replicated but the prefetching will continue asynchronously and will be done after all pages of the prefetching piece are replicated. Prefetching Period

A prefetching period allows concurrent prefetching and archiving. The prefetching period is a period of time in seconds which starts after the last read request in the cache. If this period is not 0, during it no archiving is made unless there is a need to free pages in the cache. The value of prefetching period must be between 5 and 120 and can be enabled only if the covered file system resides on tapes. Setting this period to 0 disables the feature.

of 68

Page Found In Cache Read of the file with +f attribute induces prefetching ONLY if the requested page is not in the cache. If it is, the application's read request is satisfied without reading from the covered filesystem (without involving the migrator) and prefetching of this file does not start. This is important because it covers the normal case: first read request was satisfied when the pages of the file or the prefetching piece were replicated into the cache and now all subsequent requests to those pages must not induce prefetching again. Concurrent Read Requests Currently a prefetching is a single-threaded operation. While a file is being prefetched, no application's read requests which require reading from the covered filesystem can be satisfied. All such read requests wait until the current prefetching is done. As was explained above, this does not happen if the requested page is in the cache. Read request for such a page is satisfied and does not induce prefetching. No Free Page in Cache If prefetching requires a free page in the cache but all pages are occupied, the following algorithm applies. If there are archived pages, some of them are declared free. Otherwise, if there are primary pages they will be archived and then some of the archived pages will be declared free. If there are no archived pages, then some of the replicated pages are declared free. The above algorithm was employed to minimize the probability of the situation when prefetched pages will be declared free again before an application gets a chance to read them. Prefetching and Archiving Prefetching and archiving are not mixed. While prefetching is active and there are free pages (or archived pages which can be declared free) archiving does not start. If prefetching is active but we need to archive to make room for prefetched pages, then prefetching stops and archiving starts. After pages were archived and subsequently declared free, prefetching proceeds. Full Prefetching Mode and Prefetch Priority Period

Figure 6.16 - File Prefetching Option

The Advanced File System Setting includes 2 options for prefetching. When a user application tries to read bytes from a file, a page containing these bytes is replicated from the covered filesystem into the cache. For a file without prefetching enabled that is all that the read request will do. An attempt to read a file with prefetching enabled induces prefetching or read ahead. Not only the page that contains the requested bytes is replicated into the cache but other pages are replicated as well. If the covered file system resides on tape, prefetching is enabled by default. Full Prefetch Sets prefetching mode to full. By default is partial (max 2 GB). Prefetch Priority Period (sec) The prefetch priority period is the period of time in seconds, starting after the last read request in the cache. If this period is not 0, during it no archiving is made unless there is a need to free pages in the cache. The value of prefetch_priority_period must be between 5 and 120 and can be enabled only if the covered file system resides on tape. Setting this period to 0 disables the feature. If Permanent Prefetch or Permanent Period check box is checked, the option becomes permanent and it goes to “set features” stream of the set root directory. Note: QStar recommends reviewing the explanation for the vlcmd cache (vlcache) command in Chapter 9 - Command Reference of this manual, while reading this section.

of 68

Keep Full File and Do Not Keep Full File

Keep Full File (+f): File is in full-file mode. This mode induces a prefetch. Do not Keep Full File (-f): File is in segmented mode. An access to the file causes a page containing the referenced bytes to be read into the cache.

Figure 6.17 - Keep Full File and Do Not Keep Full File

Keep In Cache File and Do Not Keep In Cache

Figure 6.18 - Keep In Cache and Do Not Keep In Cache

Keep in Cache (+k): Any page of the file that is now present in the cache, or will be put in the cache, cannot be swapped out of the cache. Do not Keep in Cache (-k): File pages can be swapped out of the cache.

of 68

Pin to Cache Policy This option defines what part of the file must be kept in cache. The difference between Pin to Cache and Keep in Cache options are the size of that part retained. In case of Keep in Cache the whole file is retained. In case of Pin to Cache the size of that part is defined by Size value and the offset of that part from the beginning of the file is defined by the Offset value. A file can have either Keep in Cache attribute or a Pin to Cache policy. If the Pin to Cache policy applies to a file with Keep in Cache attribute, the Pin to Cache policy is ignored. If the Keep in Cache attribute applies to a file with a Pin to Cache policy, Keep in Cache is ignored.

Figure 6.19 - Pin To Cache Policy

Figure 6.20 - Pin To Cache Policy

Size and Offset options can be either the number of bytes, or the number followed by MB or GB, so it is the number of megabytes or gigabytes. The Extensions option specifies a list of file name extensions separated by a comma. If used, only files with one of those extensions are affected by the Pin to Cache policy. To work the Size option must be specified, the Offset and Extensions option can be omitted. Examples: A) Size=100000 keeps in cache the

first 100000 bytes of all files. B) Size=10MB and Offset=1GB keeps

in cache 10 megabytes starting with 1 gigabyte from the beginning of the file.

C) Size=2GB and Extension=c,txt keeps in cache first 2 gigabytes of the file with extension “.c” or “.txt”.

If the Pin to Cache policy is present, all other prefetch options are not allowed. Both Recursively and Pin to Cache make sense if the file is a directory. In this case, the Pin to Cache policy applies to the directory and all files in it, and recursively to all files under the directory. If the file is regular, the Pin to Cache policy applies to that file only. The directory's Pin to Cache policy is stored in the “q_dir_features” stream, archived to the covered file system and replicated back from the covered file system into the cache. To remove the Pin to Cache policy, set size to 0. Thus, size=0 removes the Pin to Cache policy from the file, or from the directory and its files, or with Recursively option from the directory and all files under it.

of 68

MANAGING THE CACHE Once the Integral Volume set is created and the Cache Location is assigned, it can be mounted by selecting the Mount button from the Volume Management pane. The Integral Volume set can be mounted with different options that will be better understood after the following brief description of the cfs_cache_files and the db_files.

Structure and Files in the Cache Database Inside the Cache Location directory that was specified when the Integral Volume set was created, there will be two types of files present after the Integral Volume set is mounted.

1) The cfs_* files. Together these files represent the cache.

2) The *_db files. Created when using all the file systems supported by QStar. Together they contain the table of contents of all the surfaces belonging to the Integral Volume set.

The Cache Files The following are the files created in the cache_root directory: File Description

cfs_acl This file contains the access control list for all files in MCFS.

cfs_btree This file contains balanced trees used for searching directories and mapping file pages to the page in the cfs_page file.

cfs_cnode This file contains the file metadata. In other words, it contains all the standard attribute information about the files in the Integral Volume set. In addition it contains the extended attribute information which consists of the files Migration Attributes.

cfs_crypto This file contains cryptographic information for regular files.

cfs_event All delayed events are held in this file.

cfs_info Holds Integral Volume set information such as the Migration Parameters.

cfs_log This file contains the transaction log information. The transaction log will be replayed automatically by the QStar Software at the next mount to restore or repair the cache in case of abrupt computer failures.

cfs_page_<num> Holds the actual file data or pages. On many computer platforms there is a limitation on the size of a file to 2 or 4 GB. The Migration Manager Module allows the number of pages in a cache to be extended by creating multiple page files (named cfs_pages_0, cfs_pages_1, etc), up to a maximum of 256.

cfs_pte Holds Page Table Entries (PTEs), which describe the state of every page in the cache.

cfs_tree Holds directory layout information about the Integral Volume set. This is an analog map of the directory tree of the covered file system.

set_name Holds the name of the Integral Volume set that use this cache directory. It is used by external commands which are working with cache directory, to locate pipes.

Note: All cfs_files but cfs_info and cfs_log can, if they are large enough, consist of several sections. In this case the file name is cfs_page, cfs_page_1, cfs_page_2 and so on (mostly in 32 bit Operating System).

of 68

TDO file system uses the EMG (Extended Migrator) to migrate data and metadata from the cache to the backend storage. The EMG database (edb) is the database used by EMG migrator. The edb_db files are the table of content files for the TDO file system. The files are created in the cache_root directory and are as follows: File Description

edb_node This file contains entry general attributes: files, directories, permissions, streams

edb_dir This file contains entry name (and pointer to node).

edb_ext1 File content reference, depended from target archive type: TDO - volume position, OSM object id, partition... This file contains file intervals and location on storage (depended from storage type)

edb_bbb This file keeps binary tree index for big directories contains a lot of entries (to improve lookup)

edb_raw This file contains Internal stream content

edb_log This file contains the transaction log Also all Cloud or Object Storage that is supported uses the EMG (Extended Migrator) to migrate data and metadata from the cache to the backend storage. The sdf_db files are the table of content files for the SDF file system. The files are created in the cache_root directory and are as follows: File Description

sdf_node This file contains “tnodes” (sdf type inodes) for all files and directories on an Integral Volume set. Each tnode is 128 bytes in size and contains “map entries” (pairs of ‘volume, position’ for a 64K data block) for file or “directory blocks” for directories. It also contains attributes of file (directory). 2 tnodes (0 and 1) are reserved and contain some “global” data (number of tnodes, number of free tnodes, set ID etc.).

sdf_jblk This file contains “indirect blocks” and “double-indirect blocks” for map entries for file or directory entries. These blocks are used if a file grows larger than ~640K (~20K for directory).

sdf_dir This file contains directory blocks (1K each)

sdf_log This file collects information for sdf files.

sdf_shred This file will be created only with the Shredding option enabled and contains the information of blocks shredded on the last volume

sdf_shred_map This file will be created only with the Shredding option enabled and contains a bitmap that indicates which media block of the set is shredded

of 68

The udf_db files are the table of content files for the UDF file system. The files are created in the cache_root directory and are as follows: File Description

udf_master This file contains the indicator for the type of the Integral Volume set, automount and logical volume identifier (1 if single- or multi-volume, for every volume if automount).

udf_stamp This file has no data.

File length shows how the set has been synced or unmounted:

1 - transactions have not been synced yet

2 - udf_db files have been synced

3 - media have been synced

4 - Integral Volume set has been correctly unmounted

udf_transaction This file contains the sequence of transactions made after the last sync point.

udf_df This file contains the udfdf information of each surface under automount control.

udf_span This file contains the spanning database information. The vskin_db files are the table of content files for the LTFS file system. The files are created in the cache_root directory and are as follows: File Description vskin_info

Summary information about the database.

vskin_node File nodes (file status and other attributes).

vskin_tree Directory structure (directory entries).

vskin_btree Balanced trees used for searching directories.

vskin_extent Information of extents for spanned files.

vskin_pack Contents of symlinks and special streams.

vskin_log Transaction log data collected between synchronization points.

vskin_tuning Corrections for database collected between synchronization points.

vskin_volume_space Information about total and available blocks on volumes. Only with automount and single-volume interchange level.

of 68

The aafs_db files are the table of content files for the AAFS file system. The files are created in the cache_root directory and are as follows: File Description

aafsDB This directory will contain all metadata information of all media added to the Integral Volume set.

aafs_DB_ok_seqn_12

aafs_DB_ok_seqn_12.err

aafs_DB_ok_seqn_12.log

These files will be created for each surface and will keep information about error and information during the extraction of the Archive Appliance database from the surface.

aafs_root This directory will contain the database of all files and directory present on the file system.

cd 0000001 # ls dir_level0000_000000 dir_level0000_000001

This file is an example of database extracted from media with identifier 0000001.

Note: The cfs_page file is a static file, the size is represented in 2 GB cfs_page files (only for 32 bit Operating System), and the number of cfs_page files is equal to the cache size assigned to the Integral Volume set when it was created; except on 64 bit systems, which will only have one cfs_page file regardless of the cache size. All the cfs_*, edb/sdf/udf/vskin_db are dynamic files and will grow in size with the number of files written to the Integral Volume set. QStar recommends always reserving some free space in the cache location in order to let the dynamic cache files grow. Note1: QStar recommends not doing a backup of the directory where the QStar Software is installed (the default directory name is c:\qstar) or the QStar cache directories while the Integral Volume set is mounted. If a backup utility is used while an Integral Volume set is mounted there is a very good possibility that the cache files and the Integral Volume set database will be corrupted. The cache files will be rebuilt from the media in the case of disaster. However, if there is a requirement to do a backup of the cache files it is recommended that the Integral Volume set is un-mounted first. Also, keep in mind that because the cache files change every time a file is written to the Integral Volume set restoring the cache files from a backup will most likely generate an inconsistency between the cache files and the media. Therefore, restoring the cache files is not recommended.

of 68

MIGRATION MANAGER COMMANDS FROM THE DOS PROMPT To manage the Migration from a DOS prompt use the following commands located in the c:\qstar\bin directory.

Command Description

mmcmd arc (mmarc) Start and stop the archiving

mmcmd chmod (mmchmod) Change migration attributes of the specified files

mmcmd delay (mmdelay) Print the delayed queue

mmcmd ls (mmls) List the information of specified files

mmcmd param (mmparam) Set or print the cache parameters

mmcmd resume (mmresume) Clear covered file system errors

mmcmd purge (mmpurge) Free pages in the cache

mmcmd subtree (mmsubtree) Remove or add a sub tree in the cache

mmcmd streams (mmstreams) Print streams information Note: QStar recommends reviewing the explanation for these commands in Chapter 9 - Command Reference of this manual, while reading this chapter.

of 68

MOUNTING AN INTEGRAL VOLUME SET To mount the Integral Volume set go to the Volume Management pane, select the appropriate Integral Volume set name from the drop bar and select the Mount button. When the Integral Volume set is not mounted the Mount State is set to Unmounted and the Unmount button is disabled. In the example, the Mount button is selected to mount the Integral Volume set Test. During the mount an additional window will appear displaying that the Integral Volume set is being mounted. During this time the cache files (cfs_*) and the index files (*_db) for the media will be created. If the cfs_* and *_db files already exist the mount process only takes a few seconds because it is only checking for consistency. If the cfs_* and *_db files do not exist (i.e. first mount) the mount process takes as much time as necessary to create these files. When this additional window disappears the Integral Volume set is mounted.

Figure 6.21 - Mounting an Integral Volume Set

of 68

CHECKING THE MOUNTED STATUS OF AN INTEGRAL VOLUME SET

Once the Integral Volume set is mounted the Mount State is set to Mounted and all media belonging to the Integral Volume set which are already written to, including the current write surface, are considered as Published. In the example, the media belonging to the Integral Volume set Test is marked as Published = a, b. This means that both surfaces a and b of the media in shelf 1 are available to be accessed (Published). Note: The Mount button is now disabled and the Unmount button is enabled for the Integral Volume set Test.

Figure 6.22 - Mounting an Integral Volume Set

of 68

THE INTEGRAL VOLUME SET MOUNT PROPERTIES

Figure 6.23 - The Integral Volume set Mount Properties

An Integral Volume set can be mounted with different options. To change the mount properties select the Properties button from the Volume Management pane. To mount an Integral Volume set as Read Only place a check in the Readonly box. To mount an Integral Volume set rebuilding the database files place a check in the Rebuild database box. To mount an Integral Volume set with clean cache place a check in the Clean cache box. To mount an Integral Volume set with local access only place a check in the Local access only box. To make an automatic copy of a media use the Make Copy option. In this window all changes to the cache size, the Low primary capacity (LPC) and the High primary capacity (HPC) of an Integral Volume set are permanent. The changes made in this window will take effect once the Integral Volume set is remounted. The options Rebuild database and Clean cache are set only once, for the next mount only.

Note: For more detailed information, please refer to Chapter 5 - The Volume Librarian in this manual. Note1: The Properties windows will display different information depending on the file system selected during the creation of the Integral Volume set. In the example, the properties windows of an Integral Volume set configured with TDO file system is shown.

of 68

MOUNTING AN INTEGRAL VOLUME SET ON SERVER STARTUP

To mount an Integral Volume set already created on the startup, place a check in the Mount On Server Restart box. Once the check is placed this option will be set permanently and will take effect at the next mount. To not mount the Integral Volume set on the startup remove the check from the Mount On server Restart box.

Figure 6.24 - Mounting an Integral Volume Set on Server Startup

ADDING LOCAL DRIVE LETTER TO QSTAR FILE SYSTEM

Figure 6.25 - Local Drive Letter

During the Integral Volume set creation is possible to select the Mount As option and specify the local drive letter to be used to mount the QStar file system.

The drive letter can be changed after the Integral Volume set is created, by selecting the Properties button from Volume Management page.

of 68

Once the Local Drive (Z) is mounted the data in the Integral Volume set Test can be accessed and shared. To copy files to the Integral Volume set Test they must be copied to this Local Drive. Note: The QStar file system supports standard security options from Windows. The best way to set access permissions to such resource is to use Windows Explorer Security tab for setting ACLs. The SDF, UDF, TDO all support file system ACLs. The LTFS file system does not support ACLs.

Figure 6.26 - Local Drive Letter

of 68

LOCAL DRIVE LETTER WITH SHARE DRIVE OPTION

Figure 6.27 - Share Drive Option

During the Integral Volume set creation it is possible to select also the Share Drive option. This option takes a local hard drive and shares it as a network resource, for example \\compname\ sharename. If this option is not set, can mount Integral Volume set as local drive and then the system Administrator can share this local drive later from Windows Explorer. After a system reboot Windows Vista and later will 'forget' about sharing, it is not 'permanent'. The Integral Volume set configured with Share Drive first creates network share like \\compname\ ivs_name, and then maps this network resource to a local drive letter. After system reboot, network resource re-appears automatically. This option can be changed after the Integral Volume set creation, selecting the Properties button from Volume Management page.

Once the Local Drive (Z) is mounted the data in the Integral Volume set Test can be accessed and shared. To copy files to the Integral Volume set Test they must be copied to this Local Drive. Note: The QStar file system supports standard security options from Windows. The best way to set access permissions to such resource is to use Windows Explorer Security tab for setting ACLs. The SDF, UDF, TDO all support file system ACLs. The LTFS file system does not support ACLs.

Figure 6.28 - Share Drive Option

of 68

MAPPING THE QSTAR-SERVER DRIVE

Figure 6.29 - Mapping the QStar-Server Drive

During the Integral Volume set creation it is possible to select also the Share Drive option. During the Integral Volume set creation it is possible to select the Mount As option and specify SMB2 Share option to mount the QStar file system. Mount as SMB2 means mount as network share only. No automatic mapping to local drive letter. Only \\computername\ivsname network share This option can be changed after the Integral Volume set creation, selecting the Properties button from Volume Management page.

Once the Integral Volume set is mounted, the Integral Volume set is accessed by mapping the QStar Server drive. From QStar Administration Interface main menu bar select Tools, then Map Network Drive.


of 68


Select the Drive letter to map. In the Network Path drop box all network paths of the Integral Volume sets currently mounted are displayed: The Drive letter to map can be changed by selecting any other available drive from the drop list. If there is a need to login as a different user, place a check in the Different User Name box and type in the User Name and Password for that user. The server name is the default QStar Server Name and can be displayed or changed in Status view pane. In the example, the Integral Volume set Test with \\ENGINE-SERVER\Test Network Path will be mapped to the Drive letter K: by selecting the OK button. The Integral Volume will be reconnected at logon automatically.

Once the Network Drive (K) is mapped the data in the Integral Volume set Test can be accessed and shared. To copy files to the Integral Volume set Test they must be copied to this Mapped Drive.

Figure 6.32 - Network Drive

of 68

MAPPING THE QSTAR-SERVER DRIVE FROM A DOS PROMPT If during the Integral Volume set creation, SMB2 Share as Mount As option has been selected, it is possible to access the Integral Volume set using the Net Use command from a Windows based system. The Net Use command maps a network drive from command prompt and allows access to the Integral Volume set without having a mapped drive in the Explorer Window. The net use command is a DOS command that allows users to map a network drive from the command prompt. net use [drive letter] [the network path] To map a network drive from a DOS prompt, enter: net use f: \\qstarserver\set1

MOUNTING THE QSTAR-SERVER DRIVE FROM A UNIX CLIENT

Figure 6.33 - NFS Access for an Integral Volume set.

The QStar Software allows an Integral Volume set to be mounted from a UNIX client via NFS. To configure this option, select the NFS Access button under the Integral Volume set Properties window.

of 68

In the Exportfs window, the available options are; allow All Hosts, or Allowed Hosts to access the Integral Volume set via NFS. Note: If Allowed Hosts is selected as an option, the hostnames or IP addresses will need to be entered into the box provided, each host will need to be comma separated with no space, example: server1,server2,server3

Figure 6.34 - NFS Access for an Integral Volume set.

From the UNIX client, the Integral Volume set may now be mounted via port 5005. In the following example the Integral Volume set called Test on the server called Engine-Server is mounted to a mount point called /Test: #>mount -t nfs oport=5005 Engine-Server:Test /Test #>df -k Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t0d0s0 3528702 1874182 1619233 54% / /proc 0 0 0 0% /proc mnttab 0 0 0 0% /etc/mnttab fd 0 0 0 0% /dev/fd swap 522464 48 522416 1% /var/run swap 522432 16 522416 1% /tmp /dev/dsk/c0t1d0s0 17505838 13253965 4076815 77% /cache /dev/dsk/c0t0d0s7 13452439 47861 13270054 1% /export/home Demo:Test 2437920 416777 2021143 18% /Test #

of 68

ERROR CONDITION DURING MOUNT OPERATIONS The mount procedure can return with an error condition. This section will explain what these errors mean and how to remedy them.

ERROR MESSAGE 1:

Migrator files invalid or belong to different set

This error means that the *_db files are corrupted or are already in use by another Integral Volume set.

SOLUTION:

Check to see if the Cache Location directory specified for this Integral Volume set is the same as another Integral Volume set.

If they are the same, change it or remove all files inside the Cache Location and select the Mount button.

Figure 6.35 - Error Condition During Mount


ERROR MESSAGE 2:

Cache files belong to different file system

This error means that the cfs_* files are already in use by another Integral Volume set.

SOLUTION:


If they are the same, change it or remove all files inside the Cache Location directory or mount the Integral Volume set with the Clean cache option enabled and select the Mount button.

of 68

ERROR MESSAGE 3:

No such file or directory

This error means that the Cache Location directory specified for the Integral Volume set has not been created.

SOLUTION:

Check to see if the Cache Location directory specified for this Integral Volume set exists. If it does not exist, create it and select the Mount button.



ERROR MESSAGE 4:

No such device

This error means that the current writing media for the specified Integral Volume set was set offline or was exported manually from the library.

SOLUTION:

Check from Status to see if the media is offline, and if so, set it back online.

of 68

ERROR MESSAGE 5:

Set empty

This error means that the current writing media for the specified Integral Volume set was exported from the library and set offline.

SOLUTION:

Bring the media back online by selecting the Import button from the Online Media.


of 68

UNMOUNTING AN INTEGRAL VOLUME SET

To unmount the Integral Volume set go to the Volume Management pane, select the appropriate Integral Volume set name from the drop bar and select the Unmount button. In the example, the Unmount button is selected to unmount the Integral Volume set Test.

Figure 6.40 - Unmounting an Integral Volume Set

Figure 6.41 - Unmounting an Integral Volume Set

Once an Integral Volume set is unmounted the Mount State is set to Unmounted and all media belonging to the Integral Volume set are no longer considered Published. The Integral Volume set Test is unmounted and its Mount State is set to Unmounted. Note: Now the Mount button is enabled.

of 68

MOUNT ON DATE OPTION

Dated Mount has the ability to mount an Integral Volume set, as read only, to a previous date and time. This feature is specific to the TDO, SDF and UDF/LTFS Spanning file systems. Mount On Date allows multiple simultaneous mounts on different dates and times, while the production mount continues to satisfy user requests. This allows the System Administrator to recover a previous version of a file or recover a file that has been deleted from the file system. To configure the Mount On Date Option, select the Mount On Date Button.

Figure 6.42 - Mount On Date configuration


To create a new Mount On Date Integral Volume set, select the New button, this will open a new dialog box to input the Mount On Date parameters. The Mount On Date can take place while the Integral Volume set is mounted for read/write and multiple Mount On Date configurations can be mounted simultaneously.

of 68

Select the Integral Volume name from the drop down menu, select a new cache location by typing in the cache path, or selecting the Browse button, then select a Snap Time for the Integral Volume to be mounted on. Once the OK is selected, the volume will mount. The Integral Volume set may take some time to mount, depending on the amount of data written up to the Snap Time.



The volume will mount on a share folder, named by the date and time, for example: 201306021306 This is the Year, Month, Day, Hours and Minutes.

of 68

From the Mount On Date window, new configurations can be created and existing configurations can be mounted/unmounted.



Once unmounted the mount on date volume can be removed by selecting the Remove button.

ARCHIVING NOTIFICATION The QStar Software includes a feature to inform the System Administrator when archiving starts and stops. To enable this logging feature, create the mcfs_archiving_log_on file in c:\qstar\log directory. Once this file is created all the archiving start/stop information will be logged into the Syslog view pane.

of 68

DISPLAYING AND MONITORING CACHE INFORMATION The Migration view pane displays the cache information and the Properties window modifies the cache parameters. To modify the cache parameters select the Properties button from Volume Management pane. For more detailed information about the cache parameters, please refer to Chapter 5 - The Volume Librarian in this manual.

Cache Information Displayed for a Integral Volume set The cache parameters are the following: # of Delayed Events: Number of delayed events to be processed when archiving starts. Writing to Partition (SDF/TDO)/Last Write on (UDF/LTFS): Device name of the current write surface. Read/Write Status: Type of access to the media. Default = Read-write for SDF, TDO, UDF and LTFS. Archiving State: Starts immediately to archive all the Primary Pages and all the Delayed Events present in the cache. Archiving status can be: Stop At Low, All Data or Inactive. Clear error condition state: If during archiving an error occurs, selecting the Clear error condition state button will clear the error. Once the error is cleared selecting the Archive button will restart the archiving of the files. Primary/Replicated/Archived pages: Status of the pages in the cache. Total File Count: Files present in the cache Pages Present: Total number of pages allocated to the Integral Volume set. Archive Status: Error condition notification and archive status.

Figure 6.48 - Information Displayed for a Integral Volume set Archived/Replicated Since Mount: Number of pages archived or replicated since last mount Cache Size: Total cache size Page Size: Size of each page (64 Kbytes) High primary capacity (HPC): High primary capacity value. Default = 80 % of the total pages Low primary capacity (LPC): Low primary capacity value. Default = 0 % of the total pages Note: For read only file systems: The Read/Write Status will display as Read-only and the Primary and Archived bars will show 0%.

of 68

The Low primary capacity (LPC) and the High primary capacity (HPC) can be changed from the Migration View pane by moving the bar to the requested value and selecting the Apply PC button. The modifications made from the Migration View pane are only temporarily set on the current mount section. When the Integral Volume set is remounted the value will return to the default value or the specified value selected using the Properties button from the Volume Management pane. The main parameters displayed from the DOS Prompt using mmcmd param command are described as follows:

General Parameter Description

Cache root: c:\cache-test Displays the location of the cache root directory

Share name: Test

Share name: /mnt/Test (LINUX with

fsi_server)

Mount point of the Integral Volume set

Max number of pages: 163840 10 GB Total number of cache pages allocated to the Integral Volume set

Low primary capacity: 0 pages Low primary Capacity value (the point archiving stops)

Default = 0 pages

High primary capacity: 131072 pages 8.0 GB High primary capacity value (the point archiving will begin automatically)

Default = 80 % of the total pages

Prefetch priority period: No Prefetch priority period (the type of prefetch used to read data)

Default = No

Prefetching mode: Partial Prefetching mode

Default = Partial

Page size: 64 Kbytes Size of each page

Default = 64 Kbytes

Present pages: 0 0 MB

Primary pages: 0 0 KB

Replicated pages: 0 0 KB

Archived pages: 0 0 MB

Status of the pages in the cache

Keep in cache: 0 0 KB Number of pages set with these specific attributes

Archived since mount: 2.5 KB

Replicated since mount: 0 KB

Number of pages archived or replicated since last mount

Files in cache: 9 Files present in the cache

Number of delayed events: 0 Number of delayed events to be processed when archiving starts

Read/write access: Read-write Type of access to the media

Default = Read-write for TDO, SDF, UDF and LTFS

Default = Read-only ISO 9660, UVFS and AAFS

of 68

Rdonly grace period: No Grace Period option

Default = No

Retention period: No Retention Period option

Default = No

Worm FS: No

No Worm Rename: No

Worm options

Default = No

Digest: No Digest Calculation option

Default = No

Encryption: No Encryption option

Default = No

Back end retention: No Back end Retention option only for HCP QSSD

Default = No

Atime update: No Access time update option

Default = No

Error condition: No Error condition notification

Stop on covered error: Yes Status of the Write operation (Enabled/Disabled) after covered error occurs.

Default = Yes

Archiving: Not started Archiving status

Migrator: TDO, SDF, UDF, LTFS UVFS and AAFS Type of migrator

Medium drive type: ERASABLE Type of current writing medium of the Integral

Volume set

For TDO and SDF only

Writing to partition:jb:1a (TDO and SDF)

Last write on: /opt/QStar/dev/jb/rjb1a (UDF and LTFS)

Device name of the current write surface

Number of partitions: 2 Total number of “partitions” (sides of double-sided media or individual tapes) allocated to the sdf Integral Volume set

This may grow when the Volume Librarian adds new volumes to the Integral Volume set

For SDF only

of 68

Max.number of opened partitions: 8 Maximum number of partitions that the sdf_migrator may keep open at one time, the default is 8. This is meaningless for sdf on MO/WORM disks, but should not be more than the actual number of drives in a library when tapes are used (jbscheduler can not unload a tape from a drive if the tape is open). This number instructs the sdf_migrator to close one of the partitions when it wants to open another and shows the number of currently open partitions that exceeds this max limit

For SDF only

Max. buffer size: 15488

Display the buffer size of the drives with a write buffer.

For SDF only

Free space on current partition: 3.0 GB Displays the space available on the current media/surface.


Compression: off This flag displays if compression is used on the tape drive


Extent Size: 4.0 MB Size of the Extent used by EMG Migrator

By default: 4MB

For TDO only

Virtual Drives:: 5 (2 for Writing) Virtual Drives represent the thread for write/read operations. Each such thread allows a number of atomic operations (read/write) simultaneously. In general, number of virtual drives should be corresponded to real drives. Virtual Drive count equates to the parallel operation level for special set. 5 virtual drives and two for writing means, we create 5 threads, and only 2 from then on are used for write operations: 5 - for read, and 2 for write. Only in mirror configuration will TDO migrator know the number of mirror copies and will increase virtual drives automatically

Write pool Count: 4: Write Pool Count is maximum number of objects used for writing. Example, 16 objects can be filled by CFS data but if TDO has 1 virtual drive for writing then, CFS can fill 16 objects, but only one will be written at a time. For QSSD Device the Software can write 16 object at the same time because QSSD Device can write in a parallel method

By default: 4

For TDO only

of 68

ERROR HANDLING AND RECOVERY FOR ALL FILE SYSTEMS The archive component of an Integral Volume set is typically a mass storage device such as a Tape, Optical, DVD or CD library connected either to the local computer or to another computer on the network. These mass storage devices, as well as the network, can have hardware faults, which cause an error to be produced during archiving. The Migration Server protects the integrity of the Integral Volume set, and its data, by maintaining the currently processed delayed event in the queue until the Migrator has notified it of successful completion.

Error Condition while Processing a Delayed Event If the Migrator returns an error condition while processing a delayed event, then the Migration Server will automatically set itself to an Error Condition State. In this mode, the current archiving will stop. In addition, any processes waiting on an event, which requires access to the archive, will return an error, as will any new accesses to the Integral Volume set which require access to the archive. Any accesses to the Integral Volume set, which do not require access to the archive will process as normal.

Error Condition in the Cache

Using the Migration View makes it possible to monitor the status of the cache and in case of an error the “Error” message will appear in the Archive Status window.

When an error occurs during archiving the Archiving State is switched to Inactive and the Clear error condition state button is Highlighted.

In the example, the cache for the Integral Volume set Test is in an error condition state. If an error condition occurs, the QStar Software directs this error into the Syslog pane. The cache message error is reported on the Syslog pane as follows: “Covered file system error”.

Figure 6.49 - Error Condition in the Cache

of 68

Clearing Error Condition in the Cache When the cache has an error condition, the System Administrator can investigate and see if the error was introduced by a hardware problem (failure). If this is true, fix it and restart the migration of the data between the cache and the media by selecting the Clear error condition state button.

Figure 6.50 - Clearing Error Condition in the Cache

If necessary the Integral Volume set may be unmounted and the system halted to find and repair the problem prior to selecting the Clear error condition state button.

During this entire process the maximum level of data protection to the Integral Volume set is maintained thus preventing data loss or corruption.

Note: If a DVD/Blu-ray library is used, once the covered error is cleared using the Clear error condition state button, QStar highly recommends checking to see if the media type information of the current write surface is still reported correctly in Status. If the media type information is suspicious or is not displayed correctly the System Administrator must clear the media type information and refresh it. To achieve this follow the procedure explained in the “Example of Recovery for Unknown Shelf Type Information” session.

Integral Volume System or Disk Crashes The QStar command checks and repairs any file system inconsistencies in the cache automatically at the next mount. In the case of a disk crash you may need to rebuild the cache area. However, do this only if it is absolutely necessary. Before mounting the Integral Volume set, the QStar Software performs a consistency check between the cache file system and the log file; this action will be completely transparent to the users. QStar keeps the result of this action in the Syslog pane. Example - If there isn’t an inconsistency between the file system and the log file, the Syslog pane will contain the following lines: qs_open_tlog: log file not empty, replaying... qs_open_tlog: log file replayed successfully. /export/home/cache: Filesystem is mountable If file names are displayed during this check, you should examine the listed files after the check is completed to see if they are corrupted.

of 68

POWER FAILURE, SYSTEM CRASH OR REBOOTING WITHOUT UNMOUNTING In the event of a system crash due to power failure or other cause, the Integral Volume sets will not be cleanly unmounted. Some steps will be taken care of automatically, but the System Administrator must ensure other steps are carried out to bring the Integral Volume sets back online. The set database will be initialized on startup by _vlserver and any media left in drives will be returned to their shelves when the jbscheduler starts. The first time the Integral Volume sets are mounted after the sever was rebooted the QStar Software will perform a consistency check between the cache file system and the cache log file (called Transaction Logging Cache), this action is completely transparent to the users. QStar recommends the following steps: 1) Check the consistency of the disk partition containing the QStar cache using the Windows Properties command: 2) Remount the Integral Volume sets using the mount button. Some Integral Volume sets may take longer to mount, as the

QStar Software may need to carry out further recovery procedures or consistency checks. 3) After the Integral Volume set is mounted, try to access a file. If an I/O error is received it means that the db_files (sdf_db,

udf_db, edb_db or vskin_db files) present in the cache partition are corrupted. To rebuild these index_files, umount the Integral Volume sets and run the following commands:

vlcmd restore_fsdb set_name For all file systems.

vlcmd restore_fsdb [-D SDF_span_number] set_name

For SDF or TDO Integral Volume sets. Specify the SDF or TDO volume number (starting from 1) which must be used for restoring SDF or TDO database. Without this option (or if volume number is equal to 0) the SDF or TDO database will be restored from the last surface in the Integral Volume set. The database will be restored from specified volume and SDF or TDO events will be replayed from that medium. The saved database on the next volume will not be used to restore database. Rather the data portion of the SDF or TDO volume will be scanned and events replayed. This process continues until last medium (surface) in the Integral Volume set is scanned. The mirrored SDF or TDO volume set restore with this option is not supported.

vlcmd restore_fsdb [-H host_name] [-D {UDF_span_number | +}[:to_span_number]] [-c fsdb_cache_root] set_name

For UDF Integral Volume sets. Specify the span number of the surface which must be used for restoring a spanning database. Without this option the database will be restored from the last surface in the Integral Volume set. If this number is “+”, a spanning database will be incrementally built (data from volumes not represented in the existing database will be added to it). If the_span_number is present, building of spanning database will be stopped after the specified span_number is processed.

vlcmd restore_fsdb [-H host_name] [-v] [-f] [{-L | -Q}] [-D AAFS_seq_number_from[:AAFS_seq_number_to]] set_name

For AAFS Integral Volume sets. Specify the AAFS from (and to) id number(s) of the surface from vllsdev command output list or sequence number. The -f option force restoring, even if database exists. The -L | -Q options define the Restoring type: L(ong) - scanning data on disk, Q(uick) - scanning DB on disk. Without this option: Quick, if DB exist, else Long.

of 68

vlcmd restore_fsdb [-H host_name] [-D {LTFS_span_number | +}[:to_span_number]] [-c fsdb_cache_root] set_name

For LTFS Integral Volume sets. Specify the span number of the surface which must be used for restoring a spanning database. Without this option the database will be restored from the last surface in the Integral Volume set. If this number is “+”, a spanning database will be incrementally built (data from volumes not represented in the existing database will be added to it). If the_span_number is present, building of spanning database will be stopped after the specified_span_number is processed.

Once the vlcmd restore_fsdb (vlrestore_fsdb) command has completed remount the Integral Volume sets. Note: The option -c fsdb_cache_root if used, builds the spanning database in fsdb_cache_root instead of the cache directory assigned to the Integral Volume set. This allows a rebuild of the database while the Integral Volume set is mounted. This command will require a long time to restore all the db_files. For more detailed information on the vlrestore_fsdb command, please refer to Chapter 9 - Command Reference in this manual.

Transaction Logging Cache The QStar Software checks and repairs any file system inconsistencies in the cache automatically at the next mount. In the case of a disk crash, the cache may need to be rebuilt; however, do this only if absolutely necessary.

From the DOS prompt, enter:

vlcmd mountiv set_name set_name - (SMB1) vlcmd mountiv set_name set_name\ - (SMB2) vlcmd mountiv set_name Z: - (local drive) vlcmd mountiv set_name Z:\ - local drive + SMB2 Note: Old Microsoft Samba server worked on the port 139 and used CIFS protocol; new version uses SMB2 protocol and works on port 445. From the QStar Administrative Interface, select the Volume Management pane then select the Mount button Before mounting the Integral Volume set, the QStar Software activates the Transaction Logging feature that performs a consistency check between the cache file system and the log file. The consistency check is completely transparent to the users and the QStar Software keeps the results in the Syslog pane. Example - If there is not an inconsistency between the file system and the log file, the Syslog pane will contain the following lines: qs_open_tlog: log file not empty, replaying... qs_open_tlog: log file replayed successfully. /export/home/cache_Test: File system is mountable Note: If file names are displayed during this check, the listed files should be examined to see if they are corrupted.

of 68

MANAGING THE FILES IN THE CACHE FROM THE EXPLORER VIEW PANE The Explorer view pane lists the files present in the cache and displays their status and attributes. The Explorer view pane will display one folder for each Integral Volume set mounted. If initially no folders are displayed, press the right mouse button and select the Refresh option to refresh the Explorer windows. By pressing the right mouse button, it is possible to set the view of the folder in different modes. By default, QStar displays the folder and files with Details option. The example shows how to change the way files are viewed. Right click on any empty space and select View, an additional window will open; now select the desired view.

Figure 6.51 - Managing the Files in the Cache from Explorer


The Figure above displays all the files and directories (folders) information contained on the Explorer view pane.

of 68

The information is described as follows: Column 1: Name Name of the file or directory. Column 2: Status The migration status is displayed as +/-P +/-R +/-A, Out-of-cache, Non-covered.

P = Primary => +P-R-A R = Replicated => -P+R-A A = Archived => -P-R+A

Out-of-cache => The data of the file is completely on the media. Non-covered => The file has a zero size and has not been created on the media. Column 3: Mode Permission of the file or directory. Column 4: UID User Id of the files or directory. Column 5: GID Group Id of the files or directory. Column 6: Flags Migration attributes. Column 5: Cnode Cnode number is the unique number that identifies the file in the cache. Column 6: Ino Inode number is the unique number that identifies the file on the media. Column 7: Present Number of pages in the cache that contain data associated to the file. Column 8: Primary Number of Primary pages present in the cache that contains data associated to the file. Column 9: Size Size of the file or the directory. Column 10: Offline Status Size of the file or the directory.

Select a file or a folder and press the right mouse button, an additional window will appear. From this window, the migration attributes of the specified cache files can be changed. Attributes are designated by the letters fk with the +/- prefix (Flags in the GUI).


of 68

+k (Keep in Cache) Any page of the file that is now present in the cache or will be put in the cache cannot be swapped out of the cache. -k (Do not keep in Cache) File pages can be swapped out of the cache. +f (Keep Full File) File is in full-file mode. An access to the file causes the whole file to be read into the cache. -f (Do Not Keep Full File) File is in segmented mode. An access to the file causes a page containing the referenced bytes to be read into the cache. Add Tree Adds the tree information to the cache after it was intentionally removed. Copy Tree Refresh or Copy all the subtree information to the cache once it was added to the cache with the Add Tree option. Copy Data (Prefetch) Copy all information about the file present into a directory and its data into the cache.

Figure 6.54 -Window

Remove Tree Removes a subtree from the cache. All files in the subtree must be inactive (closed). Remove Data Removes the data from the cache. Attributes Changing the Attributes of a Directory or File. If an attribute is set for the directory, it is inherited by all of the existing files and new files in this directory (excluding subdirectories). Offline location Displaying the Offline Location of a file in the Integral Volume set. Covered Info Displaying the Location of a file in the Integral Volume set. Properties Checking the Properties from Explorer. Media space for UDF/LTFS Automount. Note: The other options with gray color (Sign, Sign and Time Stamp and Verify Signature) will be not explained in this manual.


Selecting the option for View Offline/Online in the checkbox allows information in the cache to be viewed for offline media, by default is enabled. By typing inside the Find text box it is possible to search for the file in the file system. Note: Enabling this option will reduce overall performance of the cache as there is additional information to be maintained in the cache files.

of 68

Removing a Tree from the File System

Figure 6.56 - Removing a Tree from the File System

Removing and adding a tree to the cache is useful in situations when the structure of the covered file system tree is changed beyond the cache and this change must be reflected in the cache or if necessary, hide a part of the file system. In the example at the root level of the Integral Volume set Test there are three directories present. Select a file or a folder that should be removed and press the right mouse button, an additional window will appear. From this window, select the Remove Tree option. Once Remove Tree is selected, the QStar: Subtree Operation window will appear and will stay open until all the information of the files and directories are removed from the cache. Note: In the example, the directories and files included in the Data1 directory will be removed.

The Data1 directory has been removed from the Integral Volume set Test. The Syslog pane reports the directory names that were removed from the Integral Volume set. The exact name of the directory that was removed is kept in the Syslog pane as a reminder for the System Administrator in case in the future there is a need to add the directory back to the file system

Figure 6.57 - Removing a Tree from the File System

of 68

Adding a Tree to the File System

Figure 6.58 - Adding a Tree to the File System

To add a directory that was removed, press the right mouse button on any empty space and select the Add Tree option.

The Add Tree option is also available selecting the “.” directory name and selecting the right mouse button.


of 68


Once the Add Tree window appears, type in the name of the directory that was removed and select the OK button.

Once the Add Tree window disappears the directory information will reappear in the Explorer pane and the files contained in the Data1 directory are once again accessible.


of 68

Displaying the Covered Information of a File

Figure 6.62 - Displaying the Covered Information of a File

The Covered Info option is available only for an Integral Volume set created with the TDO, SDF, UDF/LTFS Spanning file system. This option displays on which media surface within an Integral Volume set a file has been written. Highlight the desired file name, press the right mouse button and select Covered Info option.

A new window will appear displaying the location information of the file. In the example, the file file_0000_type_offset3.2.dat resides completely on the Volume “2” of the Integral Volume set Test.

Figure 6.63 - Displaying the Covered Information of a File

of 68

Checking the Properties from Explorer View Pane

Figure 6.64 - Checking the Properties from Explorer

The Properties option will display information only for an Integral Volume set created with the UDF/LTFS file system and the Automount Interchange Level. This option displays the available and used disk space for each surface under the Automount control. By default, the surfaces are displayed as vol_0, vol_1 and vol_# folder names. Highlight the desired surface, press the right mouse button, and select Properties option.

The Properties window will appear. This window displays the amount of disk space available and used for the selected surface. In the example, the Integral Volume set Test is selected and the properties for the surface vol_0 are displayed.

Figure 6.65 - Checking the Properties from Explorer

of 68

Displaying the Offline Information of a File

Figure 6.66 - Displaying the Offline Information of a File

The Offline location option is available only for an Integral Volume set created with the TDO, SDF or UDF/LTFS Spanning file systems. This option displays the offline location for a file within an Integral Volume set. Highlight the desired file name, press the right mouse button and select Offline location option.

A new window will appear displaying the offline location information of the file. In the example, the file file_0027_type_offset32.dat resides completely on the media located in the offline media location Test_1:firesafe.

Figure 6.67 - Displaying the Offline Information of a File

of 68

Changing the Owner/Group/Permission of a Directory or File

Figure 6.68 - Changing the Owner/Group/Permission of a Directory or File

To change/assign the Group, Owner, permission attributes for a directory or file, right click on the directory or file name. From the menu select Attributes option. To change the permission attributes a file system must be present under the Integral Volume set name (i.e., a directory or file). Note: Any files or directories created once the Groups and Users are created will have the permission attributes of the creator.

In the Change Attributes window, type in the Group ID and the Owner ID numbers or select the “…” button. In the Mode block, place a check mark in the desired permissions for the Owner, Group and Other. The box at the bottom left allows file patterns such as wildcards to be selected. Placing a check mark in the Recursively box will change the attributes for the entire directory. Select the OK button to set the attributes.


of 68


Selecting the “…” button next to the User ID field will open the User List Window which lists the currently configured Users for Windows.

Selecting the “…” button next to the Group ID field will open the Group List Window which lists the currently configured Groups for Windows.


of 68


At the drop down menu on the right, criteria can be selected for Files, Directories, or Files and Directories.

The modification of the attributes for a directory/file can be viewed from the Explorer pane.


of 68

MANAGING THE CACHE PARAMETERS The QStar Software includes several commands that allow the System Administrator to tune the cache parameters to achieve the best performance and optimal setting for his environment. To use these commands from the QStar Administrative Interface see the “Managing the Files in the Cache from Explorer View Pane” section on this chapter. These commands can also be run from the DOS prompt. A description for each command is made in order to explain how and when the following commands should be used. QStar recommends reviewing the explanation of the following commands in Chapter 9 - Command Reference of this manual, while reading this section. The following are the available command from the DOS prompt: A) The mmcmd ls (mmls) command is used to display the status of the files in the cache and check the attributes for files and directories.

mmls [-Rpso] [filename ...] mmls [-Rpso] [filename ...] [[hostname:]setname[/filename] ...]

The mmls command prints the cache information on the files specified by the filename argument. If the files are not specified the current directory is used. If a file has a zero size and has not been created in the covered file system, its migration status is “Non-covered”. A page that is present in the cache can be primary, replicated, or archived. The mmls command does not copy the directories it lists into the cache, if the files are not present the mmls command displays the directory as empty. The mmls command does not communicate with the cache server (even when the system is mounted) and reads the data directly from the cache files. If the system is mounted and the server uses a log facility for writing into the cache files, the mmls output may not be up-to-date or accurate. To display the status of the files in the cache for an Integral Volume set named Test, enter: mmcmd ls -R Test\Data1 Directory -f-k /Data1 Directory -f-k SVN Regular Out-of-cache -f-k qstar-471-5.tar.bz2 Regular Archived -f-k winapps-357-5.tar.bz2 Regular Archived -f-k winapps-357-4.tar.bz2 Regular Archived -f-k winapps-357-3.tar.bz2 Regular Archived -f-k winapps-357-2.tar.bz2 Regular Out-of-cache -f-k winapps-208.tar.bz2 Regular Out-of-cache -f-k winapps-221.tar.bz2 Regular Out-of-cache -f-k qstar-464.tar.bz2 Regular Out-of-cache -f-k qstar-472.tar.bz2 Regular Out-of-cache -f-k qstar-465.tar.bz2 Regular Archived -f-k winapps-317-4.tar.bz2 To display detailed information of the files in the cache for an Integral Volume set named Test, enter: #>mmcmd ls -Rs Test\Data1 Directory -f-k /Data1 Cnode_number=2 Ino=2 Mode=40755 UID=0 GID=0 Nlink=4 Size=2048 Directory -f-k SVN Cnode_number=3 Ino=3 Mode=40755 UID=0 GID=0 Nlink=2 Size=26624 Regular Out-of-cache -f-k qstar-471-5.tar.bz2 Cnode_number=492 Present=0 Primary=0 Ino=903 Mode=100644 UID=0 GID=0 Nlink=1 Size=2246201385 Regular Archived -f-k winapps-357-5.tar.bz2

of 68

To display detailed information including online/offline status of the files in the cache for an Integral Volume set named Test, enter: #>mmcmd ls -Rso Test\Data1 Directory -f-k /Data1 Cnode_number=2 Ino=2 Mode=40755 UID=0 GID=0 Nlink=4 Size=2048 Directory -f-k SVN Cnode_number=3 Ino=3 Mode=40755 UID=0 GID=0 Nlink=2 Size=26624 Regular Online Out-of-cache -f-k qstar-471-5.tar.bz2 Cnode_number=492 Present=0 Primary=0 Ino=903 Mode=100644 UID=0 GID=0 Nlink=1 Size=2246201385 Regular Online Archived -f-k winapps-357-5.tar.bz2 Cnode_number=1272 Present=190 Primary=0 Ino=1135 Mode=100644 UID=0 GID=0 Nlink=1 Size=12420857 Regular Online Archived -f-k winapps-357-4.tar.bz2 Cnode_number=1274 Present=190 Primary=0 Ino=1141 Mode=100644 UID=0 GID=0 Nlink=1 Size=12420584 Regular Online Archived -f-k winapps-357-3.tar.bz2 Cnode_number=1276 Present=190 Primary=0 Ino=1147 Mode=100644 UID=0 GID=0 Nlink=1 Size=12420038 Regular Online Out-of-cache -f-k qstar-464-1.tar.bz2 B) The mmcmd chmod (mmchmod) command is used to change the migration attributes of specified cache files. This

command is useful if the System Administrator wants to keep some specific files in the cache. mmchmod [-R] [-p file_pattern] [-t {file|dir}] [-U uid |-u user_name] [-G gid|-g group_name]

[-m mode] [-K pin_to_cache_size [:pin_to_cache_offset[:pin_to_cache_ext]]] [-q quota] {+|-} {fkr} {path|[hostname:]setname/path} ...

The attributes are designated by the letters fk with the + / - prefix. The +/- f determines if a file is segmented or not. The +/- k determines if any page of a file that is present in the cache will be swapped out of the cache or not. If an attribute is set for a directory, all files in that directory will have the same attributes; this excludes any subdirectories. The total number of “keep in cache” files is printed using the mmcmd param (mmparam) command, and the files status attributes can be displayed with mmls command. Below are some mmchmod command options. For more detailed information on the mmchmod command, please refer to Chapter 9 - Command Reference in this manual.

-U uid Changes the owner of the files. New owner is specified by uid.

-u user_name Changes the owner of the files. New owner is specified by user_name.

-G gid Changes the group ID of the files. New group is specified by gid.

-g group_name Changes the group ID of the files. New group is specified by group_name.

of 68

-m The permissions of the named files or directories are changed according to mode. -q quota If not 0, sets a quota for the number of entries in the directory. mmls command prints for a directory the current entry count, the quota if it exists, and the alert if the entry count is greater than or equal to quota. If the alert is printed an email will be sent to the system Administrator with the quota information violation (email notification must be configured). -t file|dir

-t file flag will change attributes for regular files only. -t dir flag will change attributes for directories only.

-p file_pattern

-p *.exe - changes attributes for all files with .exe at the end of the file name. -p a* - changes attributes for files which started with “a” letter. -p m?x - changes attributes for files max, mox, mix. But files max1, maax still unchanged.

*- matches with any sequence of letters in the name.

? - matches with one letter.

If an attribute is set for the directory, it is inherited by all of the existing files and new files in this directory (excluding subdirectories).

-R With this option the mmchmod command sets the specified attribute recursively for all subdirectories. -U -G -m These options are developed for MS Windows and they are present for compatibility with Unix semantics. On Unix the same goal is achieved with chmod, chown, chgrp commands.

EXAMPLES

In the examples below Test is the Integral Volume set.

mmcmd ls Test Directory -f-k / Directory -f-k files Directory -f-k scratch

The command shows the current directory attributes.

mmcmd chmod +k Test\files Change the “Keep in cache” directory attribute.

mmcmd ls Test Directory -f-k / Directory -f+k files Directory -f-k scratch

The command shows the new directory attributes.

of 68

C) The mmcmd subtree (mmsubtree) command removes or adds a subtree within the cache. This command is useful for rebuilding one part of the directory subtree tree information stored in the cache database without rebuilding the whole directory structure within the cache.

mmsubtree -a path/new_subdir_name

mmsubtree -a [hostname:]setname/path/new_subdir_name mmsubtree -r {tree|data|kill|kill_data} path mmsubtree -r {tree|data|kill|kill_data} [hostname:]setname/path mmsubtree -c {tree|data} [-v] path mmsubtree -c {tree|data} [-v] [hostname:]setname/path Note: The mmsubtree -c data path command is used for Prefetching files. Once the mmsubtree command has started access to the cache will be denied until the mmsubtree command has finished. D) The mmcmd param (mmparam) command is used to change the High and Low Water Mark Level of the cache in order to

tune the cache to allow more reads than write requests or vice versa. mmparam [-H host_name] [-l {low_primary_capacity | xxMB | xxGB | xx%}] [-h {high_primary_capacity | xxMB | xxGB | xx%}] [-P {prefetch_priority_period|0}] [-g {rdonly_grace_period|0}] [-R {retention_period|0}] [-w {0|1}] [-x [h=]{0|1}] [-F {0|1}] [-B {dir|set|straight}] [-A {0|1}] {set_name | filename}

E) The vlcmd inset (vlinset) command, depending on the file system being used, allows editing of the offline location, adding

or removing a media from the covered file system, copying the information from the media into the cache, locking the data related to a media into the cache, removing related information for the media from the cache (tree, data, media or all), specifying the subdirectory name where the media will be mounted and specifying the filename format.

vlinset [-H host_name][-f offline]

[-c {tree|data}][-alu][-r {tree|data|medium|all}] [set_type_specific_options] set_name in_set_number

set_type set_type_specific_options: sdf udf [-R device_name:shelf_number]

Note: The vlinset command is used primarily with CD/DVD-ROM Integral Volume sets to implement Full Directory Caching of the contents of a selected CD/DVD-ROM media. Caching the directory structures of a selected CD/DVD-ROM into the cache increases the read performance by eliminating the need to repeatedly access the library and allows removal of the media from the library by keeping the contents of the CD/DVD-ROM online in the cache.

of 104

QStar Software allows the creation of different types of media configurations, depending which file system is used. A combination of any of the types of media configuration can co-exist within the same library. This allows the user to tailor the Integral Volume sets within the library to fit their own requirements. There follows a detailed description on how to create and manage each of the media configuration types.

INTEGRAL VOLUME SET CONFIGURATION .................................................................................. 3 Cache Management for Integral Volume Set Configuration........................................................... 4

MANAGING QSTAR ASM PRODUCT WITH TDO FILE SYSTEM ................................................... 5 MANAGING AN INTEGRAL VOLUME (I.V.) SET.......................................................................... 6

Design Considerations for an Integral Volume Set .................................................................... 6 Overview of Creating an Integral Volume Set ............................................................................ 6 INTEGRAL VOLUME SET CONFIGURATION FOR A LIBRARY OR STANDALONE DRIVE......................................................................................................................................... 7

Step 1 - Checking the Library Shelves Status ....................................................................... 7 Step 2 - Importing Media into the Library ............................................................................... 8 Step 3 - Erasing the Media..................................................................................................... 9 Step 4 - Creating an Integral Volume Set ............................................................................ 10 Step 5 - Adding Media to the Integral Volume Set............................................................... 12 Step 6 - Mounting the Integral Volume Set .......................................................................... 14 Step 7 - Monitoring the Data Migration ................................................................................ 16 Step 8 - Unmounting the Integral Volume Set ..................................................................... 16

MANAGING QSTAR ASM PRODUCT WITH SDF FILE SYSTEM.................................................. 17 MANAGING AN INTEGRAL VOLUME (I.V.) SET........................................................................ 18

Design Considerations for an Integral Volume Set .................................................................. 18 Overview of Creating an Integral Volume Set .......................................................................... 18 INTEGRAL VOLUME SET CONFIGURATION FOR A LIBRARY OR STANDALONE DRIVE....................................................................................................................................... 19

Step 1 - Checking the Library Shelves Status ..................................................................... 19 Step 2 - Importing Media into the Library ............................................................................. 20 Step 3 - Erasing the Media................................................................................................... 21 Step 4 - Creating an Integral Volume Set ............................................................................ 22 Step 5 - Adding Media to the Integral Volume Set............................................................... 24 Step 6 - Mounting the Integral Volume Set .......................................................................... 26 Step 7 - Monitoring the Data Migration ................................................................................ 28 Step 8 - Unmounting the Integral Volume Set ..................................................................... 28

MANAGING QSTAR ASM PRODUCT WITH THE UDF FILE SYSTEM ......................................... 29 MANAGING AN INTEGRAL VOLUME (I.V.) SET........................................................................ 30

Design Considerations for Integral Volume Set ....................................................................... 30 Overview of Creating an Integral Volume Set .......................................................................... 31 INTEGRAL VOLUME SET CONFIGURATION FOR A LIBRARY OR STANDALONE DRIVE WITH UDF AUTOMOUNT AND SINGLE-VOLUME INTERCHANGE LEVELS .......... 32

Step 1 - Checking the Library Shelves Status ..................................................................... 32 Step 2 - Importing Media into the Library ............................................................................. 33 Step 3 - Erasing the Media................................................................................................... 34 Step 4 - Creating an Integral Volume Set ............................................................................ 35 Step 5 - Adding Media to the Integral Volume Set............................................................... 38 Step 6 - Mounting the Integral Volume Set .......................................................................... 40 Step 7 - Monitoring the Data Migration ................................................................................ 42 Step 8 - Unmounting the Integral Volume Set ..................................................................... 43

of 104

INTEGRAL VOLUME SET CONFIGURATION FOR A LIBRARY WITH UDF SPANNING INTERCHANGE LEVEL............................................................................................................44

Step 1 - Checking the Library Shelves Status ......................................................................44 Step 2 - Importing Media into the Library..............................................................................45 Step 3 - Erasing the Media ...................................................................................................46 Step 4 - Creating an Integral Volume Set .............................................................................47 Step 5 - Adding Media to the Integral Volume Set ...............................................................49 Step 6 - Mounting the Integral Volume Set...........................................................................51 Step 7 - Monitoring the Data Migration .................................................................................53 Step 8 - Unmounting the Integral Volume Set ......................................................................53

MANAGING QSTAR ASM PRODUCT WITH LTFS FILE SYSTEM.................................................54 INTRODUCTION...........................................................................................................................55

References................................................................................................................................55 QStar LTFS Features................................................................................................................55 Supported Drives ......................................................................................................................55 LTFS and Data Synchronization...............................................................................................55 LTFS Log ..................................................................................................................................55

MANAGING AN INTEGRAL VOLUME (I.V.) SET ........................................................................56 Design Considerations for an Integral Volume Set...................................................................56 Overview of Creating an Integral Volume Set...........................................................................57 INTEGRAL VOLUME SET CONFIGURATION FOR A LIBRARY OR STANDALONE DRIVE WITH DIRECT SINGLE-VOLUME, SINGLE-VOLUME AND AUTOMOUNT INTERCHANGE LEVELS .........................................................................................................58

Step 1 - Checking the Library Shelves Status ......................................................................58 Step 2 - Importing Media into the Library..............................................................................59 Step 3 - Erasing the Media ...................................................................................................60 Step 4 - Creating an Integral Volume Set .............................................................................61 Step 5 - Adding Media to the Integral Volume Set ...............................................................64 Step 6 - Mounting the Integral Volume Set...........................................................................66 Step 7 - Monitoring the Data Migration .................................................................................69 Step 8 - Unmounting the Integral Volume Set ......................................................................70

INTEGRAL VOLUME SET CONFIGURATION FOR A LIBRARY WITH SPANNING INTERCHANGE LEVEL IN WINDOWS....................................................................................71

Step 1 - Checking the Library Shelves / Slot Status.............................................................71 Step 2 - Importing Media into the Library..............................................................................72 Step 3 - Erasing the Media ...................................................................................................73 Step 4 - Creating an Integral Volume Set .............................................................................74 Step 5 - Adding Media to the Integral Volume Set ...............................................................76 Step 6 - Mounting the Integral Volume Set...........................................................................78 Step 7 - Monitoring the Data Migration .................................................................................80 Step 8 - Unmounting the Integral Volume Set ......................................................................80

CHECKING AND RECOVERING LTFS MEDIA.......................................................................81 MANAGING QSTAR ASM PRODUCT WITH UVFS (PLASMON PFS/AFS) AND AAFS (PLASMON ARCHIVE APPLIANCE) FILE SYSTEMS.....................................................................84

MANAGING AN INTEGRAL VOLUME (I.V.) SET ........................................................................85 Design Considerations for Integral Volume Set........................................................................85 Overview of Creating an Integral Volume Set...........................................................................85 INTEGRAL VOLUME SET CONFIGURATION FOR A LIBRARY OR STANDALONE DRIVE .......................................................................................................................................87

Step 1 - Checking the Library Shelves Status ......................................................................87 Step 2 - Importing Media into the Library..............................................................................88 Step 3 - Creating an Integral Volume Set .............................................................................89 Step 4 - Adding Media to the Integral Volume Set ...............................................................91 Step 5 - Mounting the Integral Volume Set...........................................................................97 Step 6 - Monitoring the Data Migration ...............................................................................102 Step 7 - Unmounting the Integral Volume Set ....................................................................103

of 104

INTEGRAL VOLUME SET CONFIGURATION All of the combined storage media that QStar Software manages in a set is referred to as an Integral Volume (I.V.) set. An Integral Volume set is the sum total of all of the items in a single storage hierarchy. The Integral Volume set configuration allows a single piece, or a selected group of media to be bound together as a seamless file system. The Integral Volume set consists of sequenced surfaces of the physical archival media. Further sequences (media), can be added manually, or dynamically as required. As the Integral Volume set grows, sequences can be removed from the library to an offline location, to free up shelf space for new media to be added to the library, utilizing the QStar offline Volume Management within the Volume Librarian (V.L.). The data still appears online and media is requested to be inserted into the library if needed. By viewing the archival media as groups, or Integral Volume sets, rather than single, autonomous units, QStar Software lets you access large amounts of stored data without having to track their location. To users, the QStar Integral Volume set seems like a standard magnetic disk with unlimited storage capacity. It is completely compatible with existing applications and network shares or mount points mapped by the System Administrator. Integral Volume sets can also be completely offline, such as volumes that contain infrequently accessed data. QStar Software manages all of the media in the Integral Volume set as a single unit and knows the location of all of the files and media (including those that are offline) at all times. Like a standard magnetic disk, an Integral Volume set has a hierarchical directory structure, and it can be navigated by using normal system commands and operating system file searches. The difference is that at any point in time, a file on an Integral Volume set can actually reside on different types of storage media. For example, the entire file can be on magnetic disk only or on removable media only; the entire file can be on removable media with a copy on magnetic disk; or part of the file can be on magnetic disk, while the entire file is on removable media. As depicted in a tree hierarchy, the files controlled by QStar are composed of independent data segments. The data segments that make up the file are migrated according to user access patterns. A copy of directory trees and file attributes always resides on the magnetic disk. This allows faster file query, file open, and directory listing operations without losing performance. In addition, a copy of this directory and file information is maintained on archival media, using the QStar volume format feature, to prevent catastrophic loss in case of total magnetic disk failure. In a properly configured QStar Software Integral Volume set, files are always first written to and read from the magnetic disk. In other words, users access the faster magnetic medium directly, rather than the slower archival media. As the magnetic disk fills up, the least recently used data is moved to the archival media, where it can be easily retrieved later, if needed. The magnetic disk portion of the Integral Volume set should be large enough to accommodate general usage, based on the average file size and the average number of users who simultaneously access the Integral Volume set. The advantages of using the Integral Volume sets include:

• Ease of administration: you can export a single file system rather than manage multiple file systems.

• Ease of handling: large data files that require more than one surface are easily accommodated using QStar proprietary file system (SDF / TDO). Industry-standard file systems (UDF and LTFS) may not allow this feature.

• Information security: media sets can be organized and controlled by the type of information stored in them (e.g., accounting, personnel, engineering), to which you can assign different user access security.

• Transportability: complete Integral Volume sets can be exported from a library and then imported into another library. • Duplication: you can make fast copies of the Integral Volume sets. This feature enables you to create baseline copies

of critical sets and then store these media volumes offline for disaster recovery. • Dynamic Media Allocation means that media is added to each Integral Volume set as required, the library can have

several Integral Volume sets, then a pool of blank media, as each Integral Volume set requires more media, it will be dynamically added to the set, providing the set quota has not been reached.

• Offline Volume Tracking, if the library reaches capacity, less frequently accessed media can be exported from the

library, but the data still appears online to the users.

of 104

• QStar controls the Integral Volume sets according to each user’s needs. Some users may want to have one very large Integral Volume set, while others may prefer to departmentalize their data onto several sets. You have complete control over the data, including who may access it, how, and when. You can configure Integral Volume sets to match your needs in any combination of the following:

• A Single Integral Volume set per library, or across all libraries, or across the entire media library (online, near-line

or offline). Single Integral Volume sets give you greater ease of administration, handling, and transportability, and lets you set common controls for entire sets.

• Multiple Integral Volume sets per library, or across all libraries, or across the entire media library (online, near-line

or offline). Multiple sets facilitate offline storage and transportability. They also let you conveniently segregate data by type and set as many levels of security as required.

Cache Management for Integral Volume Set Configuration As mentioned, an Integral Volume set configuration has an additional module to consider, the disk cache. The Migration Manager controls the cache. The status of the cache can be checked and modified in Migration View under the Integral Volumes navigation pane. This allows cache parameters such as a High Water Mark and flush on unmount to be altered. The High Water Mark defines the level in the cache where the data begins to flush out to the archive media. This can also be started manually by selecting the Start Archiving button on Migration View. The flush on umount parameter sets a flag to archive the data out to the archive media if the set is unmounted. For further details see the Chapter 6 -Migration Manager or the Chapter 9 - Command Reference, later in this manual.

of 104

MANAGING QSTAR ASM PRODUCT WITH TDO FILE SYSTEM

In this section Optical (MO/UDO), DVD-RAM, Blu-ray, RDX and Tape media will be configured as an Integral Volume set with the TDO file system. To easily understand how to configure an Integral Volume set a simple walk through will be presented that will be suitable for every type of library and standalone drive that QStar Software supports.

of 104

MANAGING AN INTEGRAL VOLUME (I.V.) SET

Design Considerations for an Integral Volume Set The Tape Disk Object (TDO) file system can be used with libraries and standalone drives that support WORM or rewritable Optical (MO/UDO) media, Blu-ray, DVD-RAM, RDX and Tape media. TDO file system is the newest QStar file system developed to achieve best read and write performance for small and large files with Tape media. The read requests are satisfied in multithreading mode. A special tool has been developed in order to convert the older SDF file system to TDO file system. TDO (as SDF file system) supports Data Director (DDR) configuration for Block Mirroring. This configuration will be explained in QStar Mirroring Manual. The TDO file system used with a library allows the use of multiple media to be created as a single seamless file system with a magnetic cache, used with a standalone drive allows the use of a single surface media to be created as a single seamless file system with a magnetic cache. Overview of Creating an Integral Volume Set The following is a summary of the steps performed to create, mount and monitor an Integral Volume set using the QStar Administrator’s Interface. Detailed information follows in subsequent topics.

Steps for library and standalone drive View Pane Command To Use

1. Checking the library shelves status Online Media Refresh button

2. Importing the media into the library

Loading the media to the drive manually (For Standalone Drive)

Online Media Import button

Online Media Refresh(Import) button

3. Repeat the above steps 1 and 2 for all media needed (For a Library)

4. Erasing the media, if rewritable Online Media Erase button

5. Creating the Integral Volume set definition Volume Management Create New Integral Volume button

6. Adding the media to an Integral Volume set Media Management Double click on the media

7. Mounting the Integral Volume set Volume Management Mount button

8. Monitoring the data migration Migration View

9. Unmounting the Integral Volume set

Exporting the media from the library (Standalone Drive)

Volume Management Unmount button

Online Media Export button

Monitoring an Integral Volume Set View Pane Command To Use 1. Monitoring the library shelves information Online Media

2. Monitoring the Integral Volume set information Volume Management

3. Monitoring the cache status Migration View

of 104

INTEGRAL VOLUME SET CONFIGURATION FOR A LIBRARY OR STANDALONE DRIVE

Detailed Walk Through: The following pages will describe how to manage the media with the TDO file system and to create and manage an Integral Volume set, and define and explain the terms used in the Media and Integral Volumes navigation panes. Because the QStar Software simulates a Standalone Drive as a virtual library with one shelf, containing a media with a single surface, a Tape library will be used as an example in the walk through described below. The only effective difference from a library and a standalone drive is the number of shelves and some additional features available only for the library. Note: All the default parameters are used, for more detailed information; please refer to Chapter 5 - The Volume Librarian in this manual. To create an Integral Volume set, follow the directions below.

Step 1 - Checking the Library Shelves Status

Figure 7.1 - Checking the Library Shelves Status

To refresh multiple media, Highlight the shelves and select the Refresh button.

The information displayed refers to the file system used on the media, the Size of the media, the Set Name and Sequence number of the media and the unique Set Identifier.

In the example, the media in shelves 1 and 2 are refreshing.

Before checking the library shelves/slots status, the System Administrator needs to verify that the QStar Services are running in Server/Status view pane. If they are not running, they should be started by selecting the Start button, and then verify the status of the library to ensure that the Scheduler is running from Storage Library/Status view pane.

Before an Integral Volume set can be created, the QStar database, referred to as the Volume Librarian, must know the current status of the media in the library. To determine which library shelves are empty, refresh the status of the shelves in the library using the Refresh button.

Select Online Media, if the library already contains media on the shelves and their status is displayed as unknown, update the library shelves status by refreshing all shelves of the library. If Online Media displays that the library does not contain media or the status of the shelves is correct, there is no need to refresh them.

To refresh individual media, Highlight the shelf and select the Refresh button.

of 104

Step 2 - Importing Media into the Library

Remove the check from the Only Show Shelves with Media box to display the empty shelves in Online Media.

To import media into the library, insert the media into the mail slot, Highlight an empty shelf and select the Import button.

In the example, the library is empty and the media is imported into shelf 1.

Note: To import additional media, repeat this step.

To import media into a standalone drive, manually load the media into the standalone drive, Highlight the shelf and select the Refresh button.

Figure 7.2 - Importing Media into the Library


After the import operation has completed Online Media displays the status of the imported media.

The status of the media is displayed as Erased if the media imported is rewritable and new or as Blank if the media is a new WORM.

In the example, rewritable Tape media is used.

Note: The status of the media is displayed as Unknown after a new installation of the QStar Software before the shelves have been refreshed.

Note1: For Tape, RDX and single sided media only Shelf 1 information will be displayed and the Type column will display Rewritable for RDX media, Tape for Tape media, DVD-RAM for DVD-RAM media and BD-R or BD-RE for Blu-ray media.

of 104

Step 3 - Erasing the Media

If rewritable media is used, erase the media before using it.

To erase the media, Highlight the shelf and select the Erase button.

In the example, the media in shelf 1 will be erased.

To erase multiple media, Highlight the shelves and select the Erase button.

To erase additional media, repeat this step.

Note: For detailed information of the erase options or the possibility of delaying the erase of the media to a more convenient time, please refer to Chapter 5 - The Volume Librarian in this manual.



After the erase procedure has completed, Online Media displays that the status of the media has changed to Erased.

Note: The status for new Optical WORM media is Blank.

of 104

Step 4 - Creating an Integral Volume Set

In preparation of creating the Integral Volume set, a decision must be made as to how large a cache is required and where it will be located. Using an Explorer window, create a directory in the selected location for the cache, i.e.: C:\cache-test.

Note: The cache should be large enough to accept all new data, any requests for archived data and enough extra room for unexpected high volume days between Integral Volume set archives.

To create the Integral Volume set, from Volume Management, select the Create New Integral Volume button.



Name the Integral Volume set (maximum 12 characters) and select a size for the Cache, minimum 4MB.

To select or create the Cache Location directory, press the Browse button, select the directory previously created at the beginning of this section, and select the OK button.

Select the Page Size, Default is 64KB, or a value from 1KB to 256KB.

Choose the Tape Disk Object (TDO) as the File System Type.

Note: The TDO file system is the New Primary QStar file system, in the example the TDO file system and rewritable Tape media are used.

Choose the Real Media Type between Rewritable, WORM, Tape, DVD-RAM and BD-R or BD-RE for Blu-ray media.

of 104

To make a copy in the library of the media in the Integral Volume set once it is full or incrementally, select Of Full Media, Incremental or Multi Incremental in the Make Copy box and then select Schedule to complete the incremental copy configuration.

If tape media is used as Real Media Type, the additional HW Encryption and Compression options will be available. Choose Compression as Default.


Note: In the example, tape media and the TDO file system are used.

Note1: For more detailed information about all the Integral Volume set Parameters, please refer to Chapter 5 - The Volume librarian in this manual.



The creation process of the Integral Volume set record is now complete.

Volume Management displays the Characteristics of the specified Integral Volume set when it was created.

When multiple Integral Volume sets are configured, access them using the drop bar and selecting the appropriate Integral Volume set name.

An Integral Volume set can also be deleted by choosing the Integral Volume set Name from the drop bar and selecting the Delete button.

Any parameters may be changed by selecting the Properties button. Note: The Number Of Media is equal to 0 because no media has been associated with the Integral Volume set and the File System Type is equal to tdo. Note1: The Media Type will display rewritable for RDX media, rewritable or worm for Optical media, tape for Tape media, dvd-ram for DVD-RAM media and bd-r or bd-re for Blu-ray media.

of 104

Step 5 - Adding Media to the Integral Volume Set

Media Management displays all available media in the right list-box. This media may be added to the Integral Volume set. Media is considered available when it is erased, blank or is initialized with one of the QStar file systems.

The left list-box displays all the media that are already associated with the currently selected Integral Volume set.

When multiple Integral Volume sets or Libraries are configured, access them by using the associated drop bar and selecting the appropriate Integral Volume set/Library Name.

To add media to a newly created or existing Integral Volume set select the Integral Volume set name, Highlight the media in the right list-box and click the left arrow button or double click on the media. The media will move to the left list-box.

Figure 7.10 - Adding Media to the Integral Volume Set


The media has been initialized with the specified QStar file system and is now added to the Integral Volume set.

In the example, the media in shelf 1 was added to the Integral Volume set Test.

Note: If the media added to the Integral Volume set was media that has already been initialized with one of the QStar file systems, then all the media present in the library with the same Set Identifier will be added to the Integral Volume set automatically. If in the future a media with the same Set Identifier is imported into the library it will be added to the Integral Volume set automatically.

of 104

Online Media now displays all the information about the media that was added to the Integral Volume set.

The additional information displayed is the file system used on the media, the name of the Integral Volume set, which the media belongs to, and the sequence number of the surfaces of the media in the Integral Volume set, the unique Set Identifier and barcode label (if present).



The adding media to the Integral Volume set process is now complete and the added media will now appear in Volume Management under the appropriate Integral Volume set name.

In the example, the media loaded in shelf 1 in the library JB0 was added to the Integral Volume set Test.

The Integral Volume set is now ready to mount by selecting the Mount button.

Note: Now the Number Of Media has changed to 1.

of 104

Step 6 - Mounting the Integral Volume Set

To mount the Integral Volume set go to Volume Management, select the appropriate Integral Volume set name from the drop bar and select the Mount button.

When the Integral Volume set is not mounted, the Mount State is set to Unmounted and the Unmount button is disabled.

In the example, the Mount button is selected to mount the Integral Volume set Test.

Note: For Tape media, the number of Integral Volume sets that can be mounted concurrently in a library, depends on the lease time value selected. For additional detailed information about lease time, refer to Chapter 4 - Library Management in this manual.

Figure 7.14 - Mounting the Integral Volume Set


During the mount an additional window will appear displaying that the Integral Volume set is being mounted.

During this time the cache files (cfs_*) and the index files (edb_db) for the media will be created in the cache location.

If the cfs_* and edb_db files already exist the mount process only takes a few seconds because it is only checking for consistency.

If the cfs_* and edb_db files do not exist (i.e. first mount) the mount process takes as much time as necessary to create these files.

When this additional window disappears the Integral Volume set is mounted.

of 104

Once the Integral Volume set is mounted the Mount State is set to Mounted and all media belonging to the Integral Volume set which are already written to, including the current write surface, are considered as Published.

In the example, the media belonging to the Integral Volume set Test is marked as Published = a. Only a is shown for single sided, RDX or tape media.

For optical technology with two sides both a and b are shown.

Note: The Mount button is now disabled and the Unmount button is enabled for the Integral Volume set Test.

Note1: For additional detailed information, refer to Chapter 6 - The Migration Manager in this manual.


Figure 7.17 - QStar- Drive

Once the Integral Volume set is mounted, the Drive (Z) is available and the data in the Integral Volume set Test can be accessed and shared.

To write files to the Integral Volume set Test they must be written to this Drive letter.

of 104

Step 7 - Monitoring the Data Migration

Select Migration View to monitor the migration of the data in the cache.

In the example, the access to the Integral Volume set is set to Read-write and the current write surface is surface a of the media imported to shelf 1.

Note: For additional detailed information of the cache parameters, on how to start archiving the data from the cache and the archive policy, please refer to Chapter 6 - The Migration Manager in this manual.

Figure 7.18 - Monitoring the Data Migration

Step 8 - Unmounting the Integral Volume Set

Figure 7.19 - Unmounting the Integral Volume Set

To unmount the Integral Volume set go to Volume Management, select the appropriate Integral Volume set name from the drop bar and select the Unmount button.

In the example, the Unmount button is selected to unmount the Integral Volume set Test.

of 104

MANAGING QSTAR ASM PRODUCT WITH SDF FILE SYSTEM

In this section Optical (MO/UDO), DVD-RAM, Blu-ray, RDX and Tape media will be configured as an Integral Volume set with the SDF file system. To easily understand how to configure an Integral Volume set a simple walk through will be presented that will be suitable for every type of library and standalone drive that QStar Software supports.

of 104


Design Considerations for an Integral Volume Set The Standard Data Format (SDF) file system can be used with libraries and standalone drives that support WORM or rewritable Optical (MO/UDO) media, Blu-ray, DVD-RAM, RDX and Tape media. The SDF file system used with a library allows the use of multiple media to be created as a single seamless file system with a magnetic cache, used with a standalone drive allows the use of a single surface media to be created as a single seamless file system with a magnetic cache. Overview of Creating an Integral Volume Set The following is a summary of the steps performed to create, mount and monitor an Integral Volume set using the QStar Administrator’s Interface. Detailed information follows in subsequent topics.




Loading the media to the drive manually (For Standalone Drive)


Online Media Refresh(Import) button











Monitoring an Integral Volume Set View Pane Command To Use 1. Monitoring the library shelves information Online Media



of 104


Detailed Walk Through: The following pages will describe how to manage the media with the SDF file system and to create and manage an Integral Volume set, and define and explain the terms used in the Media and Integral Volumes navigation panes. Because the QStar Software simulates a Standalone Drive as a virtual library with one shelf, containing a media with a single surface, an MO Optical library will be used as an example in the walk through described below. The only effective difference from a library and a standalone drive is the number of shelves and some additional features available only for the library. Note: All the default parameters are used, for more detailed information, please refer to Chapter 5 - The Volume Librarian in this manual. To create an Integral Volume set, follow the directions below.










of 104










The status of the media is displayed as Unknown if the media imported is rewritable and new or as Blank if the media is a new Optical WORM.

In the example, rewritable Optical media is used.

Note: The status of the media is also displayed as Unknown after a new installation of the QStar Software before the shelves have been refreshed.

Note1: For Tape, RDX and single sided media only Shelf 1 information will be displayed and the Type column will display Rewritable for RDX media, Tape for Tape media, DVD-RAM for DVD-RAM media and BD-R or BD-RE for Blu-ray media.

of 104







Note: For detailed information of the erase options or the possibility of delaying the erase of the media to a more convenient time, please refer to Chapter 5 - The Volume Librarian in this manual.





of 104








To select or create the Cache Location directory, press the Browse button, select the directory previously created at the beginning of this section, and select the OK button.


Choose the Standard Data Format (SDF) as the File System Type.

Note: The SDF file system is the Primary QStar file system, in the example the SDF file system and rewritable Optical media are used.

Choose the Real Media Type between Rewritable, WORM, Tape, DVD-RAM and BD-R or BD-RE for Blu-ray media.

of 104

To make a copy in the library of the media in the Integral Volume set once it is full or incrementally, select Of Full Media, Incremental or Multi Incremental in the Make Copy box and then select Schedule to complete the incremental copy configuration. The Incremental or Multi Incremental option is available only for Optical media.

If tape media is used as Real Media Type, the additional Compression option will be available. Choose Compression as Default.


Note: In the example, tape media and the SDF file system are used.








Any parameters may be changed by selecting the Properties button. Note: The Number Of Media is equal to 0 because no media has been associated with the Integral Volume set. The File System Type is equal to sdf. Note1: The Media Type will display rewritable for RDX media, rewritable or worm for Optical media, tape for Tape media, dvd-ram for DVD-RAM media and bd-r or bd-re for Blu-ray media.

of 104











of 104


The additional information displayed is the file system used on the media, the name of the Integral Volume set, which the media belongs to, and the sequence number of the surfaces of the media in the Integral Volume set and the unique Set Identifier.







of 104





Note: For Tape media, the number of Integral Volume sets that can be mounted concurrently in a library, depends of the lease time value selected. For additional detailed information about lease time, refer to Chapter 4 - Library Management in this manual.



During the mount an additional window will appear displaying that the Integral Volume set is being mounted.

During this time the cache files (cfs_*) and the index files (sdf_db) for the media will be created in the cache location.

If the cfs_* and sdf_db files already exist the mount process only takes a few seconds because it is only checking for consistency.

If the cfs_* and sdf_db files do not exist (i.e. first mount) the mount process takes as much time as necessary to create these files.


of 104


In the example, the media belonging to the Integral Volume set Test is marked as Published = a, b. This means that both surfaces a and b of the media in shelf 1 are available to be accessed. Only surface a would be shown for single sided, RDX or tape media.




Figure 7.36 - QStar- Drive



of 104










of 104

MANAGING QSTAR ASM PRODUCT WITH THE UDF FILE SYSTEM

In this section Optical (MO/UDO), DVD-RAM, RDX and Blu-ray media will be configured as an Integral Volume set with the UDF or ISO 9660 file systems. To easily understand how to configure an Integral Volume set, a simple walk through will be presented that will be suitable for every type of library and standalone drive that QStar Software supports.

of 104


Design Considerations for Integral Volume Set The Universal Disk Format (UDF) file system can be configured with different types of Interchange Levels, can be used with libraries and standalone drives that support WORM or rewritable Optical (MO/UDO) media, Blu-ray, DVD-RAM, RDX or CD/DVD-R media with Packet Writing or CD/DVD-ROM media pre-recorded with the UDF file system or pre-recorded with ISO 9660, Rock Ridge and Microsoft extensions, standard file systems. The Interchange Level defines how many volumes are in the Integral Volume set. The UDF file system allows three Interchange Level configurations: A) Automount (Used with UDF and ISO 9660 file systems)

With this configuration, it is possible to configure multiple media as a large file system with a magnetic cache where each surface is a separate file system but mounted under a single mount point (local drive).

B) Single-Volume (Used with the UDF and ISO 9660 file systems) With this configuration, it is possible to configure each media as a single surface file system with a magnetic cache, with each single-volume mounted on a separate mount point (local drive). This configuration is primarily used with standalone drives. The QStar Software simulates the Standalone Drive as a virtual library with one shelf, containing a media with a single surface, but may also be used in libraries with single sided media. If dual sided media is used with the Single-Volume configuration only the “A” side will be initialized and used. To use both sides of the media, use the Automount configuration.

C) Spanning (Used only with the UDF file system) With this configuration, it is possible to configure multiple media as a large file system with a magnetic cache where each surface is a single surface file system; aggregately it is seen as one continuously growing hard disk mounted under a single mount point (local drive). The recommendations for using UDF spanning:

1) A cache large enough to accommodate a full days data to be stored without starting archiving because the cache ran out of space. 2) Scheduled archiving to take place during off peak hours when the Integral Volumes are not being accessed. 3) Minimal or no changes to files once they are written to the Integral Volume set.

Please contact your QStar representative for more detailed information on how to configure UDF Spanning. Note: The Integral Volume set configuration for CD/DVD with UDF and ISO 9660 file systems are also explained in the QStar CD/DVD Master Manual.

of 104

Overview of Creating an Integral Volume Set The following is a summary of the steps performed to create, mount and monitor an Integral Volume set using the QStar Administrator’s Interface. Detailed information follows in subsequent topics.




Loading the media to the drive manually (Single-Volume)


Online Media Refresh (Import) button











Monitoring an Integral Volume set View Pane Command To Use 1. Monitoring the library shelves information Online Media



4. Monitoring the file system (Automount) Explorer Select the root directory name, click on the mouse right button and select Properties

of 104

INTEGRAL VOLUME SET CONFIGURATION

FOR A LIBRARY OR STANDALONE DRIVE WITH UDF AUTOMOUNT AND SINGLE-VOLUME INTERCHANGE LEVELS

Detailed Walk Through: The following pages will describe how to manage the media with the UDF file system in Automount and Single-Volume configurations, create and manage an Integral Volume set, and define and explain the terms used in the Media and Integral Volumes navigation panes. Because the QStar Software simulates the Standalone Drive as a virtual library with one shelf, containing a media with a single surface, an MO Optical library will be used as an example in the walk through described below. The only effective difference from a library and a standalone drive is the number of shelves and some additional features available only for the library. Note: All the default parameters are used, for more detailed information, please refer to Chapter 5 - The Volume Librarian in this manual. To create a UDF Automount or Single-Volume Integral Volume set, follow the directions below. Step 1 - Checking the Library Shelves Status









of 104











In the example, rewritable Optical media is used.


Note1: For RDX, single sided media only Shelf 1 information will be displayed and the Type column will display Rewritable for RDX media, DVD-RAM for DVD-RAM media CD/DVD-R/ROM for CD/DVD-R/ROM media and BD-R or BD-RE for Blu-ray media.

of 104






To erase additional media, repeat this step. Note: If rewritable Optical media are used, place a check to the Use Write Instead Of Erase box before to select the OK button.

Note1: For detailed information of the erase options or the possibility of delaying the erase of the media to a more convenient time, please refer to Chapter 5 - The Volume Librarian in this manual.





of 104









To select or create the Cache Location directory, press the Browse button, select the directory previously created at the beginning of this section, select the OK button.


Choose the Universal Disk Format (UDF) as the File System Type.


Choose the Real Media Type. Select between Rewritable, WORM, DVD-RAM, CD/DVD-ROM/R and BD-R or BD-RE for Blu-ray media.


Note: In the example, the UDF file system and rewritable Optical media are used.

of 104

For Standalone drives choose Single-Volume as the Interchange Level.



The Packet Writing option is available when selecting CD/DVD or BD-R Blu-ray media as Real Media Type. Using the Packet Writing option for CD/DVD-R or BD-R Blu-ray media, the media can be added directly to the Integral Volume set. If not selected, the adding procedure will be denied, returning an error for incompatible media type.

of 104

CD/DVD-ROM media that was pre-recorded with the UDF and ISO 9660 file systems can be added to an Integral Volume set and seen as separate folders under a single mapped network drive.

Choose Automount as the Interchange Level. Choose cd/dvd-r/dvd-rom as the Real Media Type. Place a check mark in the Readonly box.

The UDF and ISO 9660 file system used with the CD/DVD-ROM media is used as a read only file system.



Note1: The Media Type will display rewritable for RDX media, rewritable or worm for Optical media, dvd-ram for DVD-RAM media, cd/dvd-r/rom for CD/DVD-R/ROM media and bd-r or bd-re for Blu-ray media.





Any parameters may be changed by selecting the Properties button.

Note: The Number Of Media is equal to 0 because no media has been associated with the Integral Volume set and the File System

Type is equal to; udf, 150, automount or udf, 150, single-volume.

of 104






Figure 7.50- Adding Media to the Integral Volume Set.




Note: If dual sided media was used with the single-volume configuration, then the A side of the media is initialized with a UDF file system and the B side is still erased/blank. Adding this media under automount control will include the file system on the A side and automatically the B side will also be initialized and added under the automount control.

The media was added to the Integral Volume set using the Default Logical Volume ID properties.

Note: For more detailed information about the Default Logical Volume ID properties, please refer to Chapter 5 - The Volume Librarian in this manual.

of 104








Note: Now the Number Of Media has changed to 1. For Automount configuration the Automount_ sequence numbers will be displayed, for Single-Volume configuration the Sequence_number will be displayed.

of 104







During the mount, an additional window will appear displaying that the Integral Volume set is being mounted.

During this time the cache files (cfs_*) and the index files (udf_db) for the media will be created in the cache location.

If the cfs_* and udf_db files already exist the mount process only takes a few seconds because it is only checking for consistency.

If the cfs_* and udf_db files do not exist (i.e. first mount) the mount process takes as much time as necessary to create these files.


of 104


In the example, the media belonging to the Integral Volume set Test is marked as Published = a, b. This means that both surfaces a and b of the media in shelf 1 are available to be accessed. Only surface a will be shown for RDX and single sided media.




Figure 7.57 - QStar Drive

Once the Integral Volume set is mounted, the Drive (Z) is available and the data in the Integral Volume set Test can be accessed and shared. In Automount configuration all media (surfaces) added to the Integral Volume set will be displayed as sub-directories in the root directory of the file system and will be named by default as the Volume Label.

To copy files to the Integral Volume set Test they must be copied to this Drive under vol_0 and vol_1 sub-directories.

of 104

Once the Drive (Z) is mapped the data in the Integral Volume set Test can be accessed and shared.

In Single-volume configuration, to copy files to the Integral Volume set Test they must be copied to this Drive.







of 104





of 104


FOR A LIBRARY WITH UDF SPANNING INTERCHANGE LEVEL Detailed Walk Through: The following pages will describe how to manage the media with the UDF file system in Spanning configuration, create and manage an Integral Volume set, and define and explain the terms used in the Media and Integral Volumes navigation panes. An MO Optical library will be used as an example in the walk through described below. Note: All the default parameters are used, for more detailed information; please refer to Chapter 5 - The Volume Librarian in this manual. To create a UDF Spanning Integral Volume set, follow the directions below. Step 1 - Checking the Library Shelves Status









of 104










In the example, WORM Optical media is used.


Note1: For RDX, single sided media only Shelf 1 information will be displayed and the Type column will display Rewritable for RDX media, DVD-RAM for DVD-RAM media CD/DVD-R/ROM for CD/DVD-R/ROM media and BD-R or BD-RE for Blu-ray media.

of 104






To erase additional media, repeat this step. Note: If rewritable Optical media are used, place a check to the Use Write Instead Of Erase box before to select the OK button. Note1: For detailed information of the erase options or the possibility of delaying the erase of the media to a more convenient time, please refer to Chapter 5 - The Volume Librarian in this manual.




In the example, Optical WORM media is used.


of 104











Choose the Universal Disk Format (UDF) as the File System Type.

Choose Spanning as the Interchange Level.

Choose the Real Media Type. Select between rewritable, WORM, DVD-RAM, CD/DVD-ROM/R and DVD-RAM and BD-R or BD-RE for Blu-ray media.


Note: In the example, the UDF file system and WORM Optical media are used.

of 104

The Packet Writing option is available when selecting CD/DVD or BD-R Blu-ray media as Real Media Type. Using the Packet Writing option for CD/DVD-R or BD-R Blu-ray media, the media can be added directly to the Integral Volume set. If not selected, the adding procedure will be denied, returning an error for incompatible media type.

Note: For more detailed information about all the Integral Volume set Parameters, please refer to Chapter 5 - The Volume librarian in this manual.



Note1: The Media Type will display rewritable for RDX media, rewritable or worm for Optical media, dvd-ram for DVD-RAM media, cd/dvd-r/rom for CD/DVD-R/ROM media and bd-r or bd-re for Blu-ray media.





Any parameters may be changed by selecting the Properties button. Note: The Number Of Media is equal to 0 because no media has been associated with the Integral Volume set and the File System Type is equal to udf, 150, spanning.

of 104











The media was added to the Integral Volume set using the Default Logical Volume ID properties.

Note: For more detailed information about the Default Logical Volume ID properties, please refer to Chapter 5 - The Volume Librarian in this manual.

of 104








Note: Now the Number Of Media has changed to 1. The media will be displayed as Span_numbers=1,2 for the first media, this will increment by 1 for each media added. For single sided media, this will start as Span_number=1 then Span_number=2.

of 104








During this time the cache files (cfs_*) and the index files (udf_db) for the media will be created in the cache location.

If the cfs_* and udf_db files already exist the mount process only takes a few seconds because it is only checking for consistency.

If the cfs_* and udf_db files do not exist (i.e. first mount) the mount process takes as much time as necessary to create these files. When this additional window disappears the Integral Volume set is mounted.

of 104


In the example, the media belonging to the Integral Volume set Test is marked as Published = a, b. This means that both surfaces a and b of the media in shelf 1 are available to be accessed. Only surface a would be shown for RDX and single sided media.






To copy files to the Integral Volume set Test they must be copied to this Drive.

of 104










of 104

MANAGING QSTAR ASM PRODUCT WITH LTFS FILE SYSTEM

In this section Tape media will be configured as an Integral Volume set with the LTFS file system. To easily understand how to configure an Integral Volume set a simple walk through will be presented that will be suitable for every type of tape library and standalone drive that QStar Software supports.

of 104

INTRODUCTION The QStar LTFS support is implemented using IBM specifications and example code. This document describes user management tools and methods to create and operate LTFS file system in the QStar Archive Manager environment. LTFS is a Trademark of the International Business Machines (IBM).

References [LTFS] Linear Tape File System (LTFS) Format Specification. March 11, 2011. http://www.trustlto.com/LTFS_Format_To%20Print.pdf [FUSE] File System in User Space. http://fuse.sourceforge.net/.

QStar LTFS Features QStar LTFS version provides these following features which differentiate QStar LTFS from the IBM implementation: • LTFS code is ported to use QStar SCSI interfaces. That provides following benefits:

• There is no requirement to install IBM tape drivers into Linux (or other platform OS).

• The tape library operations are fully supported.

• The tape drive is not monopolized during LTFS mount session. If there is no activity on the tape drive for some time (5 min by default) the tape drive may be released for other operations.

• The QStar functions such as refresh, erase, add to set are supported in a standard way.

• The tape format recovery procedures (which are a part of the LTFS code) are in testing.

• The supported LTFS format version is 2.

Supported Drives Firmware Versions of the Drives Needs to be Up to Certain Level • IBM: IBM ULTRIUM-HH5 - Fimrware B6W1 and newer

• HP: HP Ultrium 5-SCSI - Firmweare Y5CD and newer

• Oracle T10000C: STK T10000C - Firmware RF53 and newer

LTFS and Data Synchronization Since LTFS does not provide data or metadata caching the accumulated changes in the file system needs to be flushed back to the tape at some point. There are three tape synchronization methods: • Synchronization on file system unmount. The data will be flushed to the tape only during file system unmount.

This may result in tape inconsistency if the server were to crash before unmount is executed.

• Synchronization on file close. This is most reliable method but may be very slow if small files are written to the tape.

• Synchronization using timeout. This method may be most acceptable for operation in the tape library environment.

LTFS Log The QStar related LTFS logs are provided in the C:\QStar\log\syslog file.

http://www.trustlto.com/LTFS_Format_To Print.pdf

http://fuse.sourceforge.net/

of 104


Design Considerations for an Integral Volume Set The Linear Tape File System (LTFS) can be configured with different types of Interchange Levels, and can be used with library and standalone drives that support LTO-5 and beyond and other tape media, such as T10000C. The Interchange Level defines how many volumes are in the Integral Volume set. The LTFS file system allows four Interchange Level configurations: A) Direct-Single-Volume

With this configuration, it is possible to configure each media as a single media file system without a magnetic cache, with each single-volume mounted on a separate mount point (local drive). This configuration is primarily used with standalone drives, but may also be used in a library.

B) Single-Volume

With this configuration, it is possible to configure each media as a single media file system with a magnetic cache, with each single-volume mounted on a separate mount point (local drive). This configuration is primarily used with standalone drives. The QStar Software simulates the Standalone Drive as a virtual library with one shelf containing one media, but may also be used in a library.

C) Automount With this configuration, it is possible to configure multiple media as a large file system with a magnetic cache where each surface is a separate file system but mounted under a single mount point (local drive).

D) Spanning

With this preferred configuration, it is possible to configure multiple media as a large file system with a magnetic cache where each media is a single file system; aggregately it is seen as one continuously growing hard disk mounted under a single mount point (local drive). LTFS volumes can be organized in a multivolume spanning Integral volume set. Such Integral Volume set is visible as a single file system where directories and files can span several volumes. At the same time, each volume is a valid LTFS file system, which can be mounted separately as a single-volume LTFS. LTFS spanning set requires some extra information (volume spanning information) stored on every spanning volume under directory /.QSTAR_VSKIN. Files under this directory are used for maintaining spanning database and not visible to the user if the volume is in the mounted spanning Integral volume set. They are visible if the volume is removed from the spanning set and mounted separately as a single-volume LTFS. Functioning of the spanning set is based on a special spanning database stored in the cache and backed up on spanning volumes. The database contains metadata information: directory entries, file attributes, file extent locations, special streams, symlink targets, btree chunks. With spanning database, any access to metadata is made without accessing the actual volumes, they are accessed only when a new information is written into the set or when the file data has to be read.

of 104









4. Erasing the media Online Media Erase button













of 104

INTEGRAL VOLUME SET CONFIGURATION FOR A LIBRARY OR STANDALONE DRIVE WITH DIRECT SINGLE-VOLUME, SINGLE-

VOLUME AND AUTOMOUNT INTERCHANGE LEVELS

Detailed Walk Through: The following pages will describe how to manage the media with the LTFS file system in Direct-Single-Volume, Single Volume and Automount configurations, create and manage an Integral Volume set, and define and explain the terms used in the Media and Integral Volumes navigation panes. Because the QStar Software simulates the Standalone Drive as a virtual library with one shelf, containing a media with a single surface, a Tape library will be used as an example in the walk through described below. The only effective difference from a library and a standalone drive is the number of shelves and some additional features available only for the library. Note: All the default parameters are used, for more detailed information; please refer to Chapter 5 - The Volume Librarian in this manual. To create a LTFS Direct-Single-Volume, Single-Volume or Automount Integral Volume set, follow the directions below. Step 1 - Checking the Library Shelves Status









of 104










The status of the media is displayed as Erased if the media imported is rewritable and new or as Blank if the media is a new WORM.

In the example, rewritable Tape media is used.

Note: The status of the media is displayed as Unknown after a new installation of the QStar Software before the shelves have been refreshed.

of 104







Note1: For detailed information of the erase options or the possibility of delaying the erase of the media to a more convenient time, please refer to Chapter 5 - The Volume Librarian in this manual.




Note: The status for new WORM media is Blank.

of 104


In preparation for creating the Integral Volume set, a decision must be made as to how large a cache is required and where it will be located. Using an Explorer window, create a directory in the selected location for the cache, i.e.: C:\cache-test.








Choose the Linear Tape File System (LTFS) as the File System Type.




of 104



Note: This configuration can be used also with a library.



To use LTFS directly without QStar cache choose Direct-Single-Volume as the Interchange Level.

Also even if this configuration will not use QStar cache the cache size and cache location MUST be specified in the Integral Volume set creation because LTFS needs a location in order to place some temporary files of the content of the media.

To finish the creation process, select the Create button. Note: This configuration can be used also with a library.

of 104


Note: The Number Of Media is equal to 0 because no media are associated with the Integral Volume set.






The File System Type, depending of the interchange level selected will be displayed as ltfs-automount or ltfs-single-volume or lfts for Direct-Single-Volume.

of 104






Figure 7.90- Adding Media to the Integral Volume Set.




The media was added to the Integral Volume set using the Default Directory name properties.

Note: Use default directory name check box is available only for Automount Interchange Level. Once the media is added to the Integral Volume set, the media will be displayed with Automount volume number information.

Note: For more detailed information about the Default directory name properties, please refer to Chapter 5 - The Volume Librarian in this manual.

of 104

Once the media is added to the Integral Volume set, the media will be displayed with Volume UUID information for Direct-Single-Volume.

Once the media is added to the Integral Volume set, the media will be displayed with Single volume number information for Single-Volume.




The additional information displayed is the file system used on the media, the name of the Integral Volume set, which the media belongs to, and the Sequence number always equal TPSER0 and the Set Identifier that is equal to the UUID of the media in LTFS. The system will create unique UUID and write LTFS label (superblock) to the tape. The next time user is performing media “refresh” the media label will be recognized and displayed.

of 104

The adding media to the Integral Volume set process is now complete and the added media will now appear in Volume Management under the appropriate Integral Volume set name. In the example, the media loaded in shelf 1 in the library JB0 was added to the Integral Volume set Test. In the example, automount LTFS Integral Volume set is displayed in addition dir info are present


Note: Now the Number Of Media has changed to 1. For Automount configuration the Automount_volume_number will be displayed, for Single-Volume configuration the Single_volume _number will be displayed, for Direct-Single-Volume configuration UUID Volume will be displayed.







of 104



During this time the cache files (cfs_*) and the index files (vskin_db) for the media will be created in the cache location.

If the cfs_* and vskin_db files already exist the mount process only takes a few seconds because it is only checking for consistency.

If the cfs_* and vskin_db files do not exist (i.e. first mount) the mount process takes as much time as necessary to create these files.



In the example, the media belonging to the Integral Volume set Test is marked as Published = a.




of 104


Once the Integral Volume set is mounted, the Drive (Z) is available and the data in the Integral Volume set Test can be accessed and shared. In Automount configuration all media added to the Integral Volume set will be displayed as sub-directories in the root directory of the file system and will be named by default as the Volume Label.

To copy files to the Integral Volume set Test they must be copied to this Drive under vol_1 sub-directory.


In Single-volume configuration, to copy files to the Integral Volume set Test they must be copied to this Drive.


of 104




In the example, the access to the Integral Volume set is set to Read-write and the media imported to shelf 1 is the current write media.


of 104





of 104


FOR A LIBRARY WITH SPANNING INTERCHANGE LEVEL IN WINDOWS Detailed Walk Through: The following pages will describe how to manage the media with the LTFS file system in Spanning configuration, create and manage an Integral Volume set, and define and explain the terms used in the Media and Integral Volumes navigation panes. A Tape library will be used as an example in the walk through described below. Note: All the default parameters are used, for more detailed information; please refer to Chapter 5 - The Volume Librarian in this manual. To create a LTFS Spanning Integral Volume set, follow the directions below. Step 1 - Checking the Library Shelves / Slot Status



The information displayed refers to the file system used on the media, the Size of the media, the Set Name, Sequence number of the media, Bar Code, and the unique Set Identifier. In the example, the media in shelf 1 is refreshing.

Before checking the library shelves / slots status, the System Administrator needs to verify that the QStar Services are running in Server/Status view pane. If they are not running, they should be started by selecting the Start button, and then verify the status of the library to ensure that the Scheduler is running from Storage Libraries/Status view pane. Before an Integral Volume set can be created, the QStar database, referred to as the Volume Librarian, must know the current status of the media in the library. To determine which library shelves are empty, refresh the status of the shelves in the library using the Refresh button. Select Online Media, if the library already contains media on the shelves and their status is displayed as unknown, update the library shelves status by refreshing all shelves of the library. If Online Media displays that the library does not contain media or the status of the shelves is correct, there is no need to refresh them. To refresh individual media, Highlight the shelf and select the Refresh button.

of 104









The status of the media is displayed as Unknown if the media imported is rewritable and previously used.


Note1: The Type column will display Tape for Tape media.

of 104


If previously used rewritable media is present, erase the media before re-using it.




To erase additional media, repeat this step. Note: For detailed information of the erase options or the possibility of delaying the erase of the media to a more convenient time, please refer to Chapter 5 - The Volume Librarian in this manual. Figure 7.105 - Erasing the Media



of 104










Choose LTFS (Linear Tape File System) as the File System Type.

Choose Spanning as the Interchange Level.


of 104

Select the Drive letter on the QStar server to be used to mount the file system in the Mount As drop box. Place a check in Share drive check box if the file system should be automatically shared after mount.

Select File Spanning if you are using files larger than a single piece of media or large file sizes that may waste capacity on each media.

Note: selecting File Spanning breaks the LTFS standard. Special QStar tools are required to read all files on File Spanning media in stand-alone drives.





Volume Management displays the Characteristics of the specified Integral Volume set.



Any parameters may be changed by selecting the Properties button. Note: The Number Of Media is equal to 0 because no media has been associated with the Integral Volume set and the File System Type is equal to LTFS spanning. Note1: The Media Type will display tape,rewritable for tape media.

of 104


Media Management displays all available media in the right list-box. This media may be added to the Integral Volume set. Media is considered available when it is erased or is initialized with one of the QStar file systems.






The media has been initialized with the previously specified file system and is now added to the Integral Volume set.



of 104

Online Media now displays all the information about the media that has been added to the Integral Volume set.

The additional information displayed is the file system used on the media,(in this case LTFS-S for LTFS Spanning, the name of the Integral Volume set, which the media belongs to, and the sequence number of the surfaces of the media in the Integral Volume set and the unique Set Identifier.






Note: Now the Number Of Media has changed to 1. The media will be displayed as Span_numbers=1 for the first media, this will increment by 1 for each media automatically added.

of 104




When the Integral Volume set is not mounted, the Mount State is set to Unmounted and the Unmount button is disabled. In the example, the Mount button is selected to mount the Integral Volume set Test.


During this time the cache files (cfs_*) and the index files (vskin_db) for the media will be created in the cache location.

If the cfs_* and vskin_db files already exist the mount process only takes a few seconds because it is only checking for consistency.

If the cfs_* and vskin_db files do not exist (i.e. first mount) the mount process takes as much time as necessary to create these files.


Note: Vskin_db files contain the LTFS Spanning database.


of 104


Please not that mount time can be significant because LTFS daemon needs to load the tape into drive, to read metadata.


In the example, the media belonging to the Integral Volume set Test is marked as Published = a.






of 104




In the example, the access to the Integral Volume set is set to Read-write and the media imported to shelf 1 is the current write media.




In the example, the Unmount button is selected to unmount the Integral Volume set Test. During unmount the newly written metadata will be synchronized with the tape and that may require some time.


of 104

CHECKING AND RECOVERING LTFS MEDIA The vlltfs (vlcmd ltfs) command checks or repairs an incomplete LTFS tape. The device_name and shelf_number specify the tape. The command works with LTFS tapes only. If the tape belongs to a direct single-volume Integral Volume set, it must be not mounted. If the tape belongs to a single-volume, automount or spanning Integral Volume set, it can be mounted or unmounted. If the tape is incomplete, repair means a restoration the file system on the tape to the specified generation point, see -g option. After the tape is repaired it is refreshed to update VL databases (Incomplete LTFS tape flag). In Windows, the command can be executed from the Online Media page. Highlight the media that is displayed in Online Media page as LTFS-I and select the right mouse button. A menu will appear select the recover option to repair the media. SYNOPSIS

vlltfs [-H host_name] [-f|-n|-s|-S] [-r [-g generation]] device_name shelf_number OPTIONS

-H host_name Specifies the name of the host where the device resides. Without this option, the local host is used.

-f Set Incomplete LTFS tape flag.

-n Clear Incomplete LTFS tape flag.

-r Repair LTFS tape.

-g Specify the generation to which the file system will be restored during repair. The default (generation equal to 0

or no this option) means the last generation.

-s Print the VL status for the specified shelf (see vllsdev).

-S Examine the tape and report its complete or incomplete status. EXAMPLES vlltfs -s -r jb 1 Repair the tape on shelf 1 and print new status. An additional LTFS utility qltfsck verifies tape media consistency and, if necessary, recovers media from an inconsistent state. When a tape is mounted, it is checked for consistency. If a consistency problem is found, and can be recovered without the loss of data, the recovery is performed automatically. If the recovery cannot be performed without the loss of data, qltfsck or qltfsck -f can be used to locate the latest index and to recover the tape from an inconsistent state. Once the medium has been recovered to a consistent state, qltfsck -l can be used to display a list of available rollback points. The ltfsck utility then can be used to recover the medium to its last good state. If qltfsck detects extra data after the final index in a partition, ltfsck deletes it. When the full recover option is specified, qltfsck saves the data that would be lost and corrects block information in the _ltfs_lostandfound directory. When the qltfsck utility is run, it automatically removes invalid data from the end of the tape and recovers the tape to the last good state. LTFS appends the most recent changes to the end of the tape without overwriting the existing data. Additional

of 104

qltfsck utility options can be initiated to save the invalid data, or to list or recover consistency at a specific rollback point or date. SYNOPSIS

qltfsck [options] filesys Location: /opt/QStar/qltfs/bin/qltfsck (Unix) Location: C:\QStar\bin\qltfsck (Windows) OPTIONS filesys Available options are:

Device file for the tape surface

-g, --generation=<generation> Specify the index of the generation to roll back. Obtain the list of acceptable indexes by entering the qltfsck command with a -l option.

-t, --time=<time> Specify the time to roll back. Obtain the list of acceptable times by entering the qltfsck command with a -l option. Time value should be “yyyy-mm-dd HH:MM:SS.nanosec”. Example (Unix): qtfsck -t "2011-12-08 07:11:04.011319621" -r /opt/QStar/dev/jb0/rjb4a Example (Windows): qtfsck -t "2011-12-08 07:11:04.011319621" -r c:\QStar\dev\JB0\rjb4a

-r, --rollback Rollback to the point specified by -g or -t -n, --no-rollback Do not roll back. Just verify the point specified by -g or -t (Default) -f, --full-recovery Recover extra data blocks into directory _ltfs_lostandfound

Recover extra data blocks for which metadata is excluded from the index file. The recovered data is stored in the directory _ltfs_lostandfound. This directory is located in the root directory on the tape medium. When the tape medium is mounted, it can be seen at the mount point.

-z, --deep-recovery Recover EOD (end-of-data mark ) missing cartridge. Some blocks may be erased but recover to final unmount point which has an index version 2.0.0 or earlier at least Must be used to an unrecoverable cartridge by normal option Specify this option when the medium cannot be recovered in any other way. Data on the medium written before the final unmount point still can be recovered. Some blocks that are written to the medium when the drive power is lost, however, might not be recoverable.

-l, --list-rollback-points List rollback points (generations) -j, --erase-history Erase history at rollback

When this option is specified, the ltfsck command erases all index files and appended data up to the designated "roll back to" generation. Data newer than this generation cannot be recovered. When this option is not specified, any existing generation can be recovered even following a rollback operation.

-k, --keep-history Keep history at rollback (Rollback) -q, --quiet Suppress informational messages -a, --trace Enable diagnostic output -h, --help This help -p, --advanced-help Full help, including advanced options

of 104

EXAMPLES The resulting output qltfsck -l command is similar to the following: qltfsck -l /opt/QStar/dev/spectra/rjb4a LTFS16000I qltfsck starting, LTFS version 1.2.0 (201102171), log level 2 LTFS12158I Opening a device through qstartape driver (/opt/QStar/dev/spectra/rjb4a) LTFS12118I Drive identification is 'ULTRIUM-HH5 ' LTFS12162I Vendor ID is IBM LTFS12159I Firmware revision is B171 LTFS12160I Drive serial is 1012003DEE LTFS17160I Maximum device block size is 262144 LTFS12015I Attempting to load the medium LTFS16018I Listing rollback points of LTFS file system on '/opt/QStar/dev/spectra/rjb4a' LTFS12015I Attempting to load the medium LTFS16023I LTFS volume information: LTFS16024I Volser(Barcode) : TPSER0 LTFS16025I Volume UUID : a7655c29-2321-4c65-8eed-38afe9921496 LTFS16026I Format Time : 2011-12-07 06:52:06.548085404 CST LTFS16027I Block Size : 262144 LTFS16028I Compression : Enabled LTFS16029I Index Partition : ID = a, SCSI Partition = 0 LTFS16030I Data Partition : ID = b, SCSI Partition = 1 LTFS16077I Valid indexes: Generation: Date Time Zone SelfPtr->BackPtr (Part, Pos)->(Part, Pos) ------------------------------------------------------------------------------------------------------------- 1: 2011-12-07 06:52:44.025880322 CST (1, 5) <<Initial Index>> (2011-12-07 12:52:44.025880322 UTC) 2: 2011-12-07 06:59:51.000072266 CST (1, 9)->(1, 5) (2011-12-07 12:59:51.000072266 UTC) 3: 2011-12-08 06:06:10.000073042 CST (1, 13)->(1, 9) (2011-12-08 12:06:10.000073042 UTC) 4: 2011-12-08 06:29:07.860057167 CST (0, 5)->(1, 17) (2011-12-08 12:29:07.860057167 UTC) 4: 2011-12-08 06:29:07.860057167 CST (1, 17)->(1, 13) (2011-12-08 12:29:07.860057167 UTC) 5: 2011-12-08 07:05:53.018769849 CST (1, 21)->(1, 17) (2011-12-08 13:05:53.018769849 UTC) 6: 2011-12-08 07:11:04.011319621 CST (1, 10965)->(1, 21) (2011-12-08 13:11:04.011319621 UTC) The resulting output qltfsck -g or qltfsck -t command is similar to the following: For example, to roll back generation 6 (timestamp 2011-12-08 07:11:04.011319621), issue one of the following commands: qltfsck -g 6 -r /opt/QStar/dev/jb0/rjb4a or qltfsck -t “2011-12-08 07:11:04.011319621” -r /opt/QStar/dev/jb0/rjb4a

of 104

MANAGING QSTAR ASM PRODUCT WITH UVFS (PLASMON PFS/AFS) AND AAFS (PLASMON ARCHIVE

APPLIANCE) FILE SYSTEMS

In this section Optical (MO/UDO), DVD-RAM and CD/DVD-ROM media will be configured as an Integral Volume set with the UVFS or AAFS file system. To easily understand how to configure an Integral Volume set a simple walk through will be presented that will be suitable for every type of library and standalone drive that QStar Software supports.

of 104


Design Considerations for Integral Volume Set The Universal File System (UVFS) can be configured with different types of Interchange Levels, can be used with libraries and standalone drives that support WORM or rewritable Optical (MO/UDO) media, DVD-RAM or CD/DVD-ROM media. Using the UVFS file system QStar supports Read Only access to the following three Plasmon file systems:




The Interchange Level defines how many volumes are in the Integral Volume set. The UVFS file system allows three Interchange Level configurations:

A) Automount With this configuration, it is possible to configure multiple media as a large file system with a magnetic cache where each surface is a separate file system but mounted under a single mount point (local drive).

B) Single-Volume With this configuration, it is possible to configure each surface as a separate file system with a magnetic cache and with a local drive for each surface. Single-Volume should only be used with a standalone drive.

C) Spanning With this configuration, it is possible to configure multiple media as a large file system with a magnetic cache where each surface is a single surface file system; aggregated as a unique file system, it is seen as one continuously growing hard disk mounted under a single mount point (local drive).

The Archive Appliance File System (AAFS) can be used with libraries and standalone drives that support WORM or rewritable Optical (UDO) media. Using the AAFS file system QStar supports Read Only access to Plasmon Archive Appliance file systems.




2. Importing the media into the library(es)










Unloading the media from the drive (Single-Volume)



of 104





of 104


Detailed Walk Through: The following pages will describe how to manage the media with AAFS (Read Only) file system, UVFS (Read Only) file system in Automount, Single-Volume and Spanning configurations, create and manage an Integral Volume set, and define and explain the terms used in the Media and Integral Volumes navigation panes. Because the QStar Software simulates the Standalone Drive as a virtual library with one shelf, containing a media with a single surface, an MO/UDO Optical library will be used as an example in the walk through described below. The only effective difference from a library and a standalone drive is the number of shelves and some additional features available only for the libraries. Note: All the default parameters are used, for more detailed information, please refer to Chapter 5 - The Volume Librarian in this manual. To create an AAFS Integral Volume set and UVFS Automount or Single-Volume or UVFS Spanning Integral Volume set, follow the directions below.





In the example, the media in shelf 1is refreshing.





of 104




In the example, the library is empty and five media is imported from shelf 1 to 5.



Note1: The media can also be imported using the Import button.




In the example, three rewritable Optical media and two WORM are used.

Note: The status of the media is displayed as Unknown after a new installation of the QStar Software, before the shelves have been refreshed.

The media that contains the Plasmon file system are displayed as UVFS-PFS or UVFS-AFS and the media that contains the Archive Appliance File system are displayed as AAFS in the Status column.

Note1: For single sided media only Shelf 1 information will be displayed and the Type column will display DVD-RAM for DVD-RAM media, CD/DVD-R/ROM for CD/DVD-R/ROM media.

of 104



Note: The cache should be large enough to keep on line the amount of file is necessary.






Choose the Universal File System (UVFS) as the File System Type.


Choose the Real Media Type. Select between Optical, DVD-RAM and CD/DVD-ROM.


Note: In the example, the UVFS file system and rewritable Optical media are used.


of 104

To configure several UVFS-PFS and UVFS-AFS media with single surface file systems with different labels under the same drive letter, choose Automount as the Interchange Level.

The label of the media should be different. If the label is identical, it will be automatically modified in order to display both file systems.

To configure UVFS-PFS or UVFS-AFS media with the same label under the same drive letter as a large multi volume file system, choose Spanning as the Interchange Level.

Spanning configurations only allow adding of media with the same label.







Choose the Archive Appliance File System (AAFS) as the File System Type.


Choose the Real Media Type. Select between Optical Rewritable or WORM.


Note: In the example, the AAFS file system and WORM Optical media are used.


of 104


Note1: The Media Type will display rewritable or worm for Optical media,, dvd-ram for DVD-RAM media, cd/dvd-r/rom for CD/DVD-R/ROM media.






Note: The Number Of Media is equal to 0 because no media has been associated with the Integral Volume set and the File System Type for UVFS is equal to uvfs, automount (used as example) or uvfs, single-volume or uvfs,spanning. The File System Type for AAFS is equal to aafs.


Example for UVFS.

Media Management displays all available media in the right list-box. This media may be added to the Integral Volume set. Media is considered available when it initialized with UVFS-PFS or UVFS-AFS file systems.




Figure 7.129 - Adding Media to the Integral Volume Set.

of 104


Example for Automount and Single-Volume Interchange Levels.

The media has been added to the Integral Volume set.

In the example, the media in shelf 1 was added to the Integral Volume set Test. The media was added to the Integral Volume set using the Default Logical Volume ID properties.

Note: For more detailed information about the Default Logical Volume ID properties, please refer to Chapter 5 - The Volume Librarian in this manual



Note: Media in shelf 1 was added to the Integral Volume set Test.


of 104



In the example, the media loaded on shelf 1 in the library JB0 was added to the Integral Volume set Test.

Because the media have the same label on both surfaces the QStar Software automatically changes the name of the directory name displayed at the root level of the file system as A_dir=maxy B_dir=maxy_0B.



Example for Spanning Interchange Level.

The media has been added to the Integral Volume set.

If the media added to the Integral Volume set have an identical label to other media present in the library then all of them will be added to the Integral Volume set automatically.

In the example, the media in shelves 1 and 3 were added to the Integral Volume set Test. The media in shelf 3 was automatically added because it has the same label of media number 1.

Figure 7.133 - Adding Media to the Integral Volume Set.

of 104




Note: Media in shelf 1 and 3 have same set identifier and were added to the Integral Volume set Test.


In the example, the media loaded on shelf 1 and shelf 3 in the library JB0 was added to the Integral Volume set Test.




of 104

Example for AAFS.

Media Management displays all available media in the right list-box. This media may be added to the Integral Volume set. Media is considered available when it initialized with AAFS file system.





Figure 7.137- Adding Media to the Integral Volume Set


In the example, the media in shelf 4 and 5 were added to the Integral Volume set Test.


of 104






In the example, the AAFS media loaded in shelf 4 and 5 in the library JB0 were added to the Integral Volume set Test.



of 104



Example for UVFS.





During this time the cache files (cfs_*) will be created in the cache location.

If the cfs_* files already exist the mount process only takes a few seconds because it is only checking for consistency.

If the cfs_* files do not exist (i.e. first mount) the mount process takes as much time as necessary to create these files.



of 104


Example for Automount and Single-Volume Interchange Levels.

Once the Integral Volume set is mounted the Mount State is set to Mounted and all media belonging to the Integral Volume set are considered as Published.

In the example, the media belonging to the Integral Volume set Test is marked as Published = a, b. This means that both surfaces a and b of the media in shelf 1 are available to be accessed. Only surface a would be shown for single sided media.


Example for Spanning Interchange Level.

In the example, the media belonging to the Integral Volume set Test is marked as Published = a, b. This means that both surfaces a and b of the media in shelf 1 and shelf 3 are available to be accessed. Only surface a would be shown for single sided media.




of 104


Example for AAFS.




Before select the Mount button at the first mount the System Administrator MUST select the Properties button and place a check in the Restore database option check box and then select the OK button to complete.

This option will rebuild all database information from each media and will merge and displaying all files on these media in the cache.

The restore operation will start at the next mount.


of 104



During this time the cache files (cfs_*) will be created in the cache location.

If the cfs_* files already exist the mount process only takes a few seconds because it is only checking for consistency.

If the cfs_* files do not exist (i.e. first mount) the mount process takes as much time as necessary to create these files.


Once the Integral Volume set is mounted the Mount State is set to Mounted and all media belonging to the Integral Volume set are considered as Published.

In the example, the media belonging to the Integral Volume set Test is marked as Published = a, b. This means that both surfaces a and b of the media in shelf 1 are available to be accessed. Only surface a would be shown for single sided media.



of 104


Once the Drive (Z) is mounted the data in the Integral Volume set Test can be accessed and shared. In Automount with UVFS file system configuration all media (surfaces) added to the Integral Volume set will be displayed as sub-directories in the root directory of the file system and will be named by default as the Volume Label. In the example the file in surface A an surface B can be accessed selecting the folder maxy or maxy_0B.

Once the Drive (Z) is mounted the data in the Integral Volume set Test can be accessed and shared.

In Single-volume and in Spanning configurations with UVFS file system and with AAFS file system the label of the media as in Automount configuration with UVFS file system will not be displayed, but the file system present on the volumes will be displayed.

Figure 7.149 - QStar Drive Because AFS, PFS and AAFS are non QStar file systems, they do not contain an index database that can be extracted in order to rebuild the file system structure present on the media. This means during the mount and at the first access of

of 104

the media QStar will scan all the surfaces populating the cache with the file system information. This will allow the QStar cache to work as an index database for the media so that all subsequent access to the media will go directly to blocks containing the file that was requested. In an Automount configuration with UVFS file system, scanning will be done per surface base. In a Spanning configuration with UVFS and for AAFS file systems, QStar is forced to access and scan all media in order to create the file system structure. This is a very time consuming operation and it can require hours to complete, depending of the size and number of media in the set. QStar highly recommends that this operation should not be interrupted and To Be Patient. Note: During the initialization of the cache it is recommended to increase the SMB timeout value from 45 seconds to 6000 seconds using Setsmbtimeout.exe program located in C:\QStar\bin directory. This is will improve performance during initialization. Reset the SMB timeout to the default once the cache is finished building. Changing the SMB timeout value requires a reboot. Step 6 - Monitoring the Data Migration



In the example, the access to the Integral Volume set is set to Read only.

Note: The example is valid for both UVFS(AFS/PFS) and AAFS file systems.

of 104




Note: In the Example the UVFS integral Volume set is used with automount configuration, but this is valid for all configurations with UVFS (AFS/PFS) and AAFS file systems.


of 104

of 26

This chapter describes how to recover from various hardware failures. Earlier sections covered error recovery for each module; this section covers the overall steps to recovering data sets in the event of a hardware failure, while ensuring minimum downtime and preventing data loss or corruption. Any messages relating to a hardware problem will be entered into the QStar Syslog view pane. ADMINISTRATOR INTERVENTION REQUIRED............................................................2 THE QSTAR LOG...................................................................................................3 Syslog ................................................................................................................3 Capturing the Syslog Information ...........................................................................4 SCSI Log.............................................................................................................4 Capturing the SCSI Log Information........................................................................5 Mail Notification ...................................................................................................6 THE STORAGE LIBRARIES CONSOLE .......................................................................7 Console...............................................................................................................7 Canceling an Event ...............................................................................................8 DRIVE FAILURE IN A LIBRARY .............................................................................. 10 Example 1 - Clearing a Drive and Shelf Bad State ................................................... 10 Example 2 - Clearing a Drive Bad State ................................................................. 11 Example 3 - Clearing a Shelf Bad State.................................................................. 11 Example of Recovery for Lost Source Shelf Information............................................ 12 Example of Recovery for Unknown Shelf Type Information ....................................... 13 USE OF MEDIA NOT SUPPORTED BY THE LIBRARY................................................... 15 MEDIA IMPORTED VIA FRONT PANEL OF LIBRARY INSTEAD OF VIA QSTAR................. 15 LIBRARY FAILURE............................................................................................... 16 ERROR CONDITION DURING MOUNT OPERATIONS.................................................. 16 ERROR HANDLING AND RECOVERY FOR ALL FILE SYSTEMS...................................... 19 Error Condition while Processing a Delayed Event.................................................... 19 Error Condition in the Cache ................................................................................ 19 Clearing Error Condition in the Cache .................................................................... 20 THE SETSESSTIMEOUT PROGRAM......................................................................... 21 ERROR RECOVERY IN THE VL DATABASE ............................................................... 23 ERROR RECOVERY USING DUPLICATE MEDIA ......................................................... 23

of 26

ADMINISTRATOR INTERVENTION REQUIRED The QStar Software automatically notifies the System Administrator in the event that the Software encounters an error that could not be corrected without the Administrator’s intervention. When such an event occurs, a pop up windows will appear on the Server machine asking for the Administrator’s name and password.

The QStar Administrator Intervention Required pop up window is used on the Server Machine to alert the Administrator that administrative privileges are needed to correct an error with the QStar Software.

Note: The QStar Administrator Intervention Required window will only appear if the QStar Administrative Interface is closed.

Figure 8.1 - QStar Administrator Intervention Required

Figure 8.2 - Entering User Name and Password

Simply enter in the Administrator’s login and password to gain access to the QStar Administrative Interface.

of 26

THE QSTAR LOG The QStar Log navigation pane contains Syslog, SCSI Log, and Mail Notification view panes that can be used as tools to monitor the system’s events. These tools provide a quick look at the activity of the QStar Software and can help to identify and solve potential problems that occurred during the runtime of the system.

Syslog

Syslog view pane contains a chronological list of the events performed by the QStar Software and any system errors that occurred. Each event displays the time, date and message for each event performed or system error that occurred. The most recent events are listed last in the list, and the list scrolls automatically to display the most current events.

Syslog is not only a useful informational tool, but can also be helpful in diagnostic situations, for example they can be used for debugging and problem determination purposes.

Syslog reads the event information from the syslog.txt file created by the QStar Software in the c:\qstar\log directory.

To stop displaying this information in Syslog, select the Pause button. The auto scrolling will be disabled. If the Pause button was selected, the QStar Software will avoid the loss of any information by continuing to collect new events into the syslog.txt file. Selecting the Resume button will start the auto scrolling and Syslog will be updated with all the new event information from the syslog.txt file.

The QStar Software will collect all event information until the syslog.txt file reaches a limit of 8 Mb in size. Syslog displays the current size of this file in the Log size window. Once the 4 Mb size is reached the syslog.txt file is automatically renamed to syslog_old.txt and a new syslog.txt file is created.

The QStar Software allows saving the latest 8 Mb (4+4) of event information, so very old information might be lost. To delete the entire event information in the syslog.txt file select the Clean button, the syslog.txt file will be automatically resized to 0 KB.

Figure 8.3 shows the Syslog with the available features listed above.

Figure 8.3 - Syslog

of 26

Capturing the Syslog Information

Figure 8.4 - Syslog

It is possible to capture the Syslog information if QStar technical support needs it.

To capture the Syslog information, right click the mouse in Syslog view pane, a context-menu will appear, Highlight the Select All option.

Once all the text in Syslog view pane is selected, right click the mouse in Syslog view pane, a context-menu will appear, select the Copy option to copy the data from the window to the clipboard.

Note: It is also possible to use the text file located in the default directory of C:\qstar\log\syslog.txt.

SCSI Log SCSI log view pane is a useful tool for detecting and diagnosing hardware errors. The main hardware errors are displayed in Syslog as well, but SCSI log provides a more precise focus for error tracking. SCSI log is by default disabled, once enabled it collects all the SCSI information for the devices that have a check mark in the box next to the device. The SCSI information includes the commands sent by the QStar Software to the device selected and the eventual error code returned by the device performing the SCSI command.

To select which device(s) containing the SCSI information needed to be logged, place a check mark in the box next to the device, i.e.JB0, Drive0, Drive1. Immediately, for the device(s) selected, SCSI log view pane will start to display each SCSI command sent, the time, the device information (SCSI bus, Target ID, Lun), the type and parameters of the SCSI command. In addition, the following will be displayed, the sense key, additional sense key and additional sense key qualifier for the SCSI commands that return an error code.

SCSI log allows collecting all the SCSI information for only one library at a time. Placing a mark in the Library check box logs all the SCSI information for the Changer. To collect the SCSI information for the drives separately, place a check in the drive check box. The most recent SCSI commands are listed, and the list scrolls automatically to display the most recent SCSI command.

It is possible to change the characteristic of the SCSI information that is logged in SCSI log view pane. To collect only the SCSI command that returns an error code, place a mark in the Error only check box. To collect all the SCSI information including all bytes of the SCSI sense, place a mark in the Long format check box; this option is useful for the SCSI commands that return an error code. To move the text to the next line so all text can be displayed within the screen’s width, place a mark in the Word Wrap check box.

SCSI log reads the SCSI information from the scsi_log.txt file created by the QStar Software in the c:\qstar\log directory. To stop displaying this information, in SCSI log select the Pause button. The auto scrolling will be disabled. If the Pause button was selected, the QStar Software will avoid the loss of any information by continuing to collect new events into the scsi_log.txt file. Pressing the Resume button will start the auto scrolling and SCSI log will be updated with all the new event information from the scsi_log.txt file. The QStar Software collects all the SCSI information until the scsi_log.txt file reaches the limit of 4 MB size.

of 26

SCSI log displays the current size of this file in the Log size window. Once the 4 MB size has been reached, the scsi_log.txt file is automatically renamed to scsi_log_old.txt file and a new scsi_log.txt file is created. The QStar Software allows saving the latest 8 MB (4+4) of SCSI information, so the old information might be lost. To delete all the SCSI information in the scsi_log.txt file select the Clean button, the scsi_log.txt file will automatically resize to 0 KB.

Figure 8.5 shows the SCSI Log with the available features listed above.

Figure 8.5 - SCSI Log

Capturing the SCSI Log Information

Figure 8.6 - SCSI Log

It is possible to capture the SCSI log information if QStar technical support needs it.

To capture the SCSI log information, right click the mouse in SCSI log view pane, a context-menu will appear, Highlight the Select All option.

Once all the text in SCSI log view pane is selected, right click the mouse in SCSI log view pane, a context-menu will appear, select the Copy option to copy the data from the window to the clipboard.

Note: It is also possible to use the text file located in the default directory of C:\qstar\log\scsi_log.txt.

of 26

Mail Notification System Administrators can receive email notification about abnormal events in the QStar Software. Abnormal events are - drive/library failures, unrecoverable write errors, requests for additional medium (no more space in the Integral Volume set), requests for media that are currently offline, etc.

To receive e-mail, fill in the Outgoing SMTP Mail Server Address with the current SMTP Server used for e-mail.

Next, type an account name in Outgoing Mail Account field.

The From (login) field is used to display the “From Address” when QStar sends an Email notification.

This field can be left blank for the default display or the System Administrator can change this.

QStar sends messages via a local mail server. If outgoing mail server requires authentication the Password (optional) field is used to specify the password requested.

Then, type in all the e-mail accounts that will receive messages when instances occur with the QStar Software in the Destination Mail Address field.

Next, test the configuration with the Test button. If the configured destination e-mail address receives the test e-mail, Mail Notification is configured properly.

Finish by selecting the Enable button and the Mail Notification Service will change to ON.

Figure 8.7 - Mail Notification

of 26

THE STORAGE LIBRARIES CONSOLE The QStar Storage Libraries navigation pane contains Console view pane.

Console

Console view pane displays warning messages of possible requests made by the QStar Software to the System Administrator.

It provides warning messages for requests such as:

Requests to import an offline media

Requests to import and erase media

Requests to import a media

Requests to add new erased media to an Integral Volume set

From Console it is possible to list these requests, check the status and if required, cancel an event.

Figure 8.8 - Console


If a request is not present on Console select the Refresh button and it will appear in the window.

Console maintains all requests from the VL module sent to the System Administrator.

The example displays a typical VL request for an offline media.

Console shows a request to import (Bring online) the media belonging to the Integral Volume set Test with sequence_number 0 located in the offline location firesafe is still Pending.

of 26

Once the media is imported into the library, Console updates its information.

The example now reports that the request to import (Bring online) the media was Satisfied.

The request can be cleared from the list by selecting the Remove Satisfied Events button.


Canceling an Event In the previous example, the request to import (Bring online) a media was satisfied. The System Administrator can decide to cancel this request or to satisfy it, whichever is more convenient.


To cancel a request for offline media select Console and Highlight the request, then select the Cancel Event button.

Note: The Cancel Event button can be applied to any VL request.

of 26

Highlighting the Canceled event and selecting the Remove Canceled Events button will clear it from the list.


of 26

DRIVE FAILURE IN A LIBRARY If the jbscheduler daemon detects an error during access to the media in a drive, jbscheduler will automatically mark the drive as bad; pausing all I/O requests to the device. All the other drives will continue to function as normal (if the library has more than one drive). The System Administrator can determine where the problem originates by using the Status:

Example 1 - Clearing a Drive and Shelf Bad State

Automatically To clear the Bad State for a drive and shelf at the same time select the Reset button. After the Reset command has completed both the shelf and drive States will return to Good. Note: The Reset button does not alter the Status of the drive or the shelf.

Figure 8.13 - Library Status (Clearing Bad State Automatically)

Figure 8.14 - Library Status (Clearing Bad State Manually)

Manually To clear the Bad State for a drive and shelf separately, use the three buttons below in the following sequence. Highlight the Drive that has a Bad State then select the Off button, next select the Set Good button. Finally select the On button. The State of the drive will return to Good. Highlight the Shelf and follow the same sequence as above.

of 26

Note: QStar highly recommends checking the status of the drive and shelf after the Automatic or Manual procedure. If the library is a DVD/Blu-ray or Tape library it is also recommended to check if the media type information is correct. If the media type information is different or not displayed, Highlight the shelf, press the right mouse button and select the Reset profile option to reset the media type information. Then refresh the shelf from Online Media by Highlighting the shelf and select the Refresh button.

Example 2 - Clearing a Drive Bad State

To clear the Bad State for a drive, use the Set Good button.

Highlight the Drive that has a Bad State then select the Set Good button, this will change the State of the drive to Good.

Figure 8.15 - Library Status (Clearing Bad State on a Drive)

Example 3 - Clearing a Shelf Bad State

Figure 8.16 - Library Status (Clearing Bad State on a Shelf)

To clear a Bad State for a shelf, use the Set Good button. Highlight the Shelf that has a Bad State then select the Set Good button, this will change the State of the shelf to Good.

of 26

Example of Recovery for Lost Source Shelf Information This error can be introduced by human intervention or hardware failure. In this case the Library loads media into a drive and because of a hardware error forgets which shelf the media came from. Status displays this media as having lost the source shelf information. The QStar Software also redirects the following message into Syslog view pane or c:\qstar\log\syslog.txt file.

JB0: jb0 drive 1: Source shelf information lost - use jbreset

To clear the Lost Source Shelf status, the System Administrator must use the Reset button additionally specifying an empty shelf number that will be used by the QStar Software as the destination for this media. Note: Before using the Reset button, ensure you have an empty shelf available in the library and know the corresponding shelf number.



After selecting the Reset button a new window will appear requesting the available Shelf number. Enter the number and select OK. The media in the drive will be placed in the specified shelf, clearing the Lost Source Shelf error. QStar also recommends performing the following action: Select Media and Refresh the specified shelf and then select Database and check the consistency of the database by selecting the Verify button. Note: See Chapter 5 -The Volume Librarian in this manual for additional detailed information.

of 26

Example of Recovery for Unknown Shelf Type Information This error can be introduced by a hardware failure during the refresh operation and it is specific for DVD/CD/Blu-ray or Tape libraries with mixed drives types or drives that support different types of media. Before the refresh procedure all media capabilities are assigned for every full shelf. This allows loading the media into all drives during the refresh procedure to determine the correct media type of the shelf. The media type is automatically set after the refresh procedure. After that, the jbscheduler will only allow the correct media to be loaded into the drive that can handle this media type. If during the refresh procedure the library loads media into a drive and because of a hardware error could not detect the media type of the shelf, the QStar Software will automatically remove all the profile information for the shelf in order to force the System Administrator to refresh the shelf once again.

In the example, shelf 2 is displayed without media type information, so its profile has been lost.



Example for DVD/CD/Blu-ray Library:


of 26

Example for Tape Library:



of 26

USE OF MEDIA NOT SUPPORTED BY THE LIBRARY

Figure 8.22 - Library Status (Unsupported Media)

These types of incidents are rare, but could happen if the manufacturer’s drive does not support the type of media trying to be used. Assume that a WORM disk is imported into a library that only supports rewritable disks, the jbscheduler, after loading the disk into the drive, cannot spin the disk and make it ready for use. Thus, the jbscheduler will not unblock the I/Os that were issued to the disk. Status shows the drive in which the media was loaded and the media marked as Bad State.

The only way to properly unblock the I/O is by using the Reset button. Then exporting the media from Online Media. Use Status to check that no Bad flags were set. If this fails, eject the media from the front panel of the library.

MEDIA IMPORTED VIA FRONT PANEL OF LIBRARY INSTEAD OF VIA QSTAR This can happen with some library models, as the front panel of the library prompts the user to import the media to a shelf as it is inserted into the mailslot. Should this happen, an updated library map is needed. This can be achieved by viewing Status, then select Online Media, the shelf will probably be marked as empty, Highlight the shelf and select the Refresh button. This will refresh the jbdriver so it will know that the shelf is now occupied and update the VL database with the media status.

of 26

LIBRARY FAILURE In the event of a library failure, media cannot be moved between the shelves and drives. Depending upon the library manufacturer and model, there may be an error code in the library display, please refer to the library manual for this information. The following steps should be carried out to recover:

1) Terminate any read/write processes to the library if possible.

2) Unmount all Integral Volume sets if possible.

3) Shut down the workstation.

4) Rectify the failure on the library.

5) Ensure the library is setup the same as before the failure (SCSI Ids, etc), then restart the workstation.

6) Check the VL database for consistency, go to the Database located under the Media and select the Verify button, this will check the library media status. If the library media status differs from the VL media status, then the media has been moved without VL being updated. In this situation the Fix button must be selected at the earliest convenience to avoid problems. For more detailed information see Chapter 5 - The Volume Librarian in this manual.

7) Remount all Integral Volume sets. All Integral Volume sets will mount quickly if they were unmounted cleanly, an Integral Volume set that would not unmount may take longer to mount.

ERROR CONDITION DURING MOUNT OPERATIONS The mount procedure can return with an error condition.

This section will explain what these errors mean and how to remedy them.

ERROR MESSAGE 1:

Migrator files invalid or belong to different set

This error means that the *_db files are corrupted or are already in use by another Integral Volume set.

SOLUTION:


If they are the same, change it or remove all files inside the Cache Location and select the Mount button.


of 26


ERROR MESSAGE 2:

Cache files belong to different file system

This error means that the cfs_* files are already in use by another Integral Volume set.

SOLUTION:


If they are the same, change it or remove all files inside the Cache Location directory or mount the Integral Volume set with the Clean cache option enabled and select the Mount button.

ERROR MESSAGE 3:

No such file or directory

This error means that the Cache Location directory specified for the Integral Volume set has not been created.

SOLUTION:

Check to see if the Cache Location directory specified for this Integral Volume set exists. If it does not exist, create it and select the Mount button.


of 26


ERROR MESSAGE 4:

No such device

This error means that the current writing media for the specified Integral Volume set was set offline or was exported manually from the library.

SOLUTION:

Check from Status to see if the media is offline, and if so, set it back online.

ERROR MESSAGE 5:

Set empty

This error means that the current writing media for the specified Integral Volume set was exported from the library and set offline.

SOLUTION:

Bring the media back online by selecting the Import button from the Online Media.


of 26

ERROR HANDLING AND RECOVERY FOR ALL FILE SYSTEMS The archive component of an Integral Volume set is typically a mass storage device such as a Tape, Optical, DVD or CD library connected either to the local computer or to another computer on the network. These mass storage devices, as well as the network, can have hardware faults, which cause an error to be produced during archiving. The Migration Server protects the integrity of the Integral Volume set, and its data, by maintaining the currently processed delayed event in the queue until the Migrator has notified it of successful completion.

Error Condition while Processing a Delayed Event If the Migrator returns an error condition while processing a delayed event, then the Migration Server will automatically set itself to an Error Condition State. In this mode, the current archiving will stop. In addition, any processes waiting on an event, which requires access to the archive, will return an error, as will any new accesses to the Integral Volume set which require access to the archive. Any accesses to the Integral Volume set, which do not require access to the archive will process as normal.

Error Condition in the Cache

Using the Migration View makes it possible to monitor the status of the cache and in case of an error the “Error” message will appear in the Archive Status window.

When an error occurs during archiving the Archiving State is switched to Inactive and the Clear error condition state button is Highlighted.

In the example, the cache for the Integral Volume set Test is in an error condition state.


of 26


If an error condition occurs, the QStar Software directs this error into the Syslog.

The cache message error is reported on the Syslog as follows:

“Covered file system error”.

Clearing Error Condition in the Cache

When the cache has an error condition, the System Administrator can investigate and see if the error was introduced by a hardware problem (failure). If this is true, fix it and restart the migration of the data between the cache and the media by selecting the Clear error condition state button. If necessary the Integral Volume set may be unmounted and the system halted to find and repair the problem prior to selecting the Clear error condition state button.

During this entire process the maximum level of data protection to the Integral Volume set is maintained thus preventing data loss or corruption.

Note: If a DVD/Blu-ray library is used, once the covered error is cleared using the Clear error condition state button, QStar highly recommends checking to see if the media type information of the current write surface is still reported correctly in Status. If the media type information is suspicious or is not displayed correctly the System Administrator must clear the media type information and refresh it. To achieve this follow the procedure explained in the “Example of Recovery for Unknown Shelf Type Information” session.

Figure 8.30 - Clearing Error Condition in the Cache

of 26

THE SETSESSTIMEOUT PROGRAM There is a well-known problem – the client writes to the server – the server does not answer the client - the client closes the session. This is a general Windows problem. To fulfill a user’s request, the QStar server might need to start archiving. Archiving might be a long operation, depending on the number of files it must write to the archival media. As a result, the QStar server may exceed the time limit allocated to the request. If this happens, the client will close the session and report an I/O error. The default timeout value is approximately 45 seconds. The solution to this problem is to increase the timeout value on the client machine.

The setsesstimeout program can change the SESSTIMEOUT parameter, increasing the timeout value.

The function of the SESSTIMEOUT parameter has changed somewhat between Microsoft LAN Manager 2.x and Windows NT. In LAN Manager, SESSTIMEOUT is the maximum amount of time that the redirector waits for a server to respond to a Server Message Block (SMB). If SESSTIMEOUT expires, the session is disconnected. In Windows NT, SESSTIMEOUT is only part of the timeout equation.

Windows NT uses a dynamic SMB response timer algorithm. The timeout can be changed on a per-SMB basis. The redirector uses more sophisticated means to calculate a proper timeout. Using a new TDI API call, [TDIQueryConnectionInfo], the redirector can determine the bytes per second rate of the media. It also knows the size of the data being sent or received in the SMB. Using this information, it calculates how long the SMB response is expected to take. To this value, it adds SESSTIMEOUT, which defaults to 45 seconds.

[(SMB size + the size of data being sent OR the expected data to be read) / bytes per second] + SESSTIMEOUT

In Windows NT, SESSTIMEOUT can be thought of as a margin for error. If things go wrong or get delayed, the redirector waits an extra SESSTIMEOUT amount before giving up. In LAN Manager, it represents the absolute maximum amount of time to wait. Currently, there is no way to see the value of the SMB response timer at any one point in time. It has a variable type of REG_DWORD. This value is stored in decimal seconds. The default is 45, with a range of 10 to 65535 seconds. SESSTIMEOUT is never automatically adjusted. If you manually adjust the value it will take effect immediately. In addition, SESSTIMEOUT and the SMB Response timer are system-wide parameters. With LAN Manager, SESSTIMEOUT does not apply to TCP/IP. In Windows NT, it applies to all protocols including TCP/IP. SESSTIMEOUT does not apply to certain types of SMBs. These mostly consist of Transaction commands, which have their own timeout variable in the SMB. SESSTIMEOUT mostly comes into effect on Read and Write operations.

Before starting the setsesstimeout program, unmount all the Integral Volume sets.

Start the Windows NT explorer and select the c:\qstar\bin folder.

Figure 8.31 -The Setsesstimeout Program

of 26

Figure 8.32 - The Setsesstimeout Program

Double click on setsesstimeout to start the program

The SetSMBTimeout window displays the default value (45 sec).

Insert the new value in seconds and select the OK button.

Note: The Minimum SMB Timeout value for a Tape library is 300 (sec).

The computer must be rebooted for the new setting to take effect.

Figure 8.33 -The Setsesstimeout Program

of 26

ERROR RECOVERY IN THE VL DATABASE QStar’s Software contains features that allow recovery from most errors introduced by human error or caused by hardware failure. If the VL database gets out of synch with the library status, this can be due to a hardware problem or human intervention that has moved media in the library without the use of VL commands. To recover from this go to the Online Media, select the Refresh button, for a single shelf, multiple shelves or all the shelves contained in the library, or use the utility present in the Database. See the Chapter 5 -The Volume Librarian in the Fixing Database Inconsistencies section.

ERROR RECOVERY USING DUPLICATE MEDIA QStar’s Software does not allow the use of identical or duplicate media in the library, unless it is Optical, DVD-R, DVD-RW, DVD-RAM media that was created with either the Copy Disk utility available from the GUI, or the Automated Copy Disk Function available for Integral Volumes sets. Non-authorized duplicate media can be made, for example, by running the Copydisk utility from the command line.

When the VL daase detects a duplicate media, it marks the identical media as “Dup” within the daase on the Online Media. If this media has been added to an Integral Volume set, the QStar Software will not allow the Integral Volume set to be mounted until the duplicate media has been exported from the library by selecting the Export button from the Online Media.

The Online Media displays the current situation:

In the library JB0 a rewritable optical media was imported into shelf 1 and added to the Integral Volume set Test.

Figure 8.34 - Online Media (Error Recovery Using Duplicate Media)

of 26


A duplicate media is imported into shelf 2 of the library JB0 by selecting the Import button.

The QStar Software detects that the media imported is a duplicate within the library; an additional window appears during the import procedure notifying the System Administrator that another identical media already exists in the VL daase.

Note: This message will be printed in both cases, if the media is or is not added to an Integral Volume set.

Select the OK button to continue.


of 26


Once the import procedure is completed the QStar Software updates the VL daase marking the identical media as “Dup” on the Online Media.

The Online Media now displays that the media imported into shelf 1 and shelf 2 are duplicates and shows the word “Dup” in the Status column.

When a duplicate media is detected in the library, the QStar Software prevents a major disaster by locking the Integral Volume set, setting its Mount State as Not Mountable

If the Integral Volume set is already mounted before the import of the duplicate media, all the data contained in the Integral Volume set is still accessible. However, once unmounted the QStar Software will not allow the Integral Volume set to be mounted until the duplicate media has been exported from the library.


of 26


To solve the problem created by the duplicate media, it is sufficient to export the duplicated media from the library by Highlighting the media and selecting the Export button.

In the example, the media imported into shelf 2 is being exported.

The Online Media displays that the media in shelf 2 was exported, the appropriate information about the media in shelf 1 and that the media belongs to an Integral Volume set. The Integral Volume set is now mounle.

Note: The media in shelf 1 is now displayed correctly as belonging to the Integral Volume set Test.


of 180

This chapter describes all the QStar commands and displays some examples for more detail.

COMMAND CONVENTIONS............................................................................................................ 3 FLOC .................................................................................................................................................. 6 FLSVOL .............................................................................................................................................. 7 JBCLEANING..................................................................................................................................... 8 JBDRIVE ............................................................................................................................................ 9 JBEXPORT ....................................................................................................................................... 11 JBFLIP .............................................................................................................................................. 12 JBIMPORT ....................................................................................................................................... 13 JBLEASE .......................................................................................................................................... 16 JBLOAD............................................................................................................................................ 21 JBMAGAZINE .................................................................................................................................. 22 JBMOVE ........................................................................................................................................... 23 JBPARAM ......................................................................................................................................... 24 JBPING............................................................................................................................................. 27 JBRESERVE ..................................................................................................................................... 28 JBRESET .......................................................................................................................................... 29 JBSCHEDCHECK ............................................................................................................................ 30 JBSCHEDULER ............................................................................................................................... 31 JBSHELF .......................................................................................................................................... 32 JBSHUT............................................................................................................................................ 34 JBSIM............................................................................................................................................... 35 JBSTATISTICS................................................................................................................................ 39 JBSTATUS ....................................................................................................................................... 41 JBUNLOAD ...................................................................................................................................... 42 LTFSDF ............................................................................................................................................ 43 MKISO ............................................................................................................................................. 44 MKUDF............................................................................................................................................. 47 MMADMIN ....................................................................................................................................... 48 MMARC ............................................................................................................................................ 51 MMCHMOD ...................................................................................................................................... 53 MMDELAY ........................................................................................................................................ 58 MMEXEC .......................................................................................................................................... 60 MMLS ............................................................................................................................................... 63 MMPARAM ....................................................................................................................................... 66 MMPING........................................................................................................................................... 69 MMPURGE ....................................................................................................................................... 70 MMRESUME..................................................................................................................................... 71 MMSTREAM..................................................................................................................................... 72 MMSUBTREE ................................................................................................................................... 73 MOUNTIV ........................................................................................................................................ 75 QCENTERA ...................................................................................................................................... 77 UDFDF.............................................................................................................................................. 82 UDFFILE .......................................................................................................................................... 83 UMOUNT.......................................................................................................................................... 84 UMOUNTIV...................................................................................................................................... 85 VLADDTOSET ................................................................................................................................. 86 VLCACHE ......................................................................................................................................... 90 VLCLOSE ......................................................................................................................................... 98

of 180

VLCMP.............................................................................................................................................. 99 VLCONSOLE.................................................................................................................................. 102 VLCOPY.......................................................................................................................................... 104 VLCRSET ....................................................................................................................................... 108 VLDELFROMSET........................................................................................................................... 119 VLDELSET ..................................................................................................................................... 120 VLEDITSET.................................................................................................................................... 121 VLERASE ....................................................................................................................................... 127 VLEXCHANGE ............................................................................................................................... 130 VLEXPORT ..................................................................................................................................... 131 VLIMPORT ..................................................................................................................................... 133 VLINSET ........................................................................................................................................ 138 VLLEASE ........................................................................................................................................ 140 VLLSVOL........................................................................................................................................ 143 VLLSDEV ....................................................................................................................................... 145 VLLSSET ........................................................................................................................................ 147 VLLTFS........................................................................................................................................... 149 VLMAGAZINE................................................................................................................................ 150 VLMEDIAUSAGE........................................................................................................................... 152 VLMICDB ....................................................................................................................................... 153 VLMICOPY ..................................................................................................................................... 155 VLMVSET ....................................................................................................................................... 156 VLPING .......................................................................................................................................... 157 VLPROXY ....................................................................................................................................... 158 VLQLIST ........................................................................................................................................ 159 VLQMOVE ...................................................................................................................................... 160 VLQREMOVE ................................................................................................................................. 161 VLRECORD .................................................................................................................................... 162 VLREFRESH................................................................................................................................... 164 VLREPLACE ................................................................................................................................... 166 VLREPLICA .................................................................................................................................... 167 VLRESTORE_FSDB ...................................................................................................................... 172 VLREUSE ....................................................................................................................................... 174 VLSCHED....................................................................................................................................... 176 VLSDF2TDO .................................................................................................................................. 178 VLVERIFY ...................................................................................................................................... 179

of 180

COMMAND CONVENTIONS All the QStar commands are available under the C:\QStar\bin (Windows) or /opt/QStar/bin (UNIX) directory by default, if in Windows another location is chosen to install the QStar Software, then the bin directory will be located under the QStar home folder chosen at installation. Listed below are the commands that are explained in more detail in this chapter.

jbcmd.exe mkiso.exe mmcmd.exe

qcentera.exe udfcmd.exe vlcmd.exe

Using command help as the argument, all available commands will be displayed:

C:\QStar\bin>jbcmd help Usage: jbcmd command

Available commands: cleaning drive export flip import lease list load magazine move param ping printer reserve reset schedcheck scheduler shelf shut sim statistics status unload

C:\QStar\bin>mmcmd help Usage: mmcmd command

Available commands: admin arc check chmod delay exec ls param ping purge resume stream subtree

C:\QStar\bin>udfcmd help Usage: udfcmd command

Available commands: fvolume flogvol fset fmigr fmmserv fmount fdf flog fonoff fimage udf frepair fcpvol ffile ffin

C:\QStar\bin>vlcmd help Usage: vlcmd command

Available commands: mountiv umountiv addtoset cache close cmp console copy crset delfromset delset editset erase exchange export import incrcopy inset lsdev lsset lease lsvol ltfs magazine mediausage mvset ping qlist qmove qremove record refresh replace replica restore_fsdb reuse verify micdb sdf2tdo sched

of 180

micopy proxy

The commands available in the Windows and UNIX operating systems are the same. The only difference will be the name convention used, in most cases for the comparable command under Windows, use the first 2 characters of the UNIX command, then add CMD and a space, for example: JBIMPORT under UNIX will become JBCMD IMPORT under Windows. For simplicity the commands reported in this chapter will follow the UNIX convention and below is a list of the corresponding command for Windows.

UNIX WINDOWS UNIX WINDOWS FLOC FLOC UMOUNTIV VLCMD UMOUNTIV FLSVOL FLSVOL VLADDTOSET VLCMD ADDTOSET JBCLEANING JBCMD DRIVE VLCACHE VLCMD CACHE JBDRIVE JBCMD CLEANING VLCLOSE VLCMD CLOSE JBEXPORT JBCMD EXPORT VLCMP VLCMD CMP JBFLIP JBCMD FLIP VLCONSOLE VLCMD CONSOLE JBIMPORT JBCMD IMPORT VLCOPY VLCMD COPY JBLEASE JBCMD LEASE VLCRSET VLCMD CRSET JBLOAD JBCMD LOAD VLDELFROMSET VLCMD DELFROMSET JBMAGAZINE JBCMD MAGAZINE VLDELSET VLCMD DELSET JBMOVE JBCMD MOVE VLEDITSET VLCMD EDITSET JBPARAM JBCMD PARAM VLERASE VLCMD ERASE JBPING JBCMD PING VLEXCHANGE VLCMD EXCHANGE JBRESERVE JBCMD RESERVE VLEXPORT VLCMD EXPORT JBRESET JBCMD RESET VLIMPORT VLCMDOMPORT JBSCHEDCHECK JBCMD SCHEDCHECK VLINSET VLCMD INSET JBSCHEDULER JBCMD SCHEDULER VLLSDEV VLCMD LSDEV JBSHELF JBCMD SHELF VLLSSET VLCMD LSSET JBSHUT JBCMD SHUT VLLTFS VLCMD LTFS JBSIM JBCMD SIM VLLEASE VLCMD LEASE JBSTATISTICS JBCMD STATISTICS VLLSVOL VLCMD LSVOL JBSTATUS JBCMD STATUS VLMAGAZINE VLCMD MAGAZINE JBUNLOAD JBCMD UNLOAD VLMEDIAUSAGE VLCMD MEDIUSAGE LTFSDF LTFSDF VLMICDB VLCMD MICDB MKISO MKISO VLMICOPY VLCMD MICOPY MKUDF MKUDF VLMVSET VLCMD MVSET MMADMIN MMCMD ADMIN VLPING VLCMD PING MMARC MMCMD ARC VLPROXY VLCMD PROXY MMCHMOD MMCMD CHMOD VLQLIST VLCMD QLIST MMDELAY MMCMD DELAY VLQMOVE VLCMD QMOVE MMEXEC MMCMD EXEC VLQREMOVE VLCMD QREMOVE MMLS MMCMD LS VLRECORD VLCMD RECORD MMPARAM MMCMD PARAM VLREFRESH VLCMD REFRESH MMPING MMCMD PING VLREPLACE VLCMD REPLACE MMPURGE MMCMD PURGE VLRESTORE_FSDB VLCMD RESTORE_FSDB MMRCFS MMCMD RCFS VLREUSE VLCMD REUSE MMRESUME MMCMD RESUME VLSHED VLCMD SHED MMSTREAM MMCMD STREAM VLSDF2TDO VLCMD SDF2TDO MMSUBTREE MMCMD SUBTREE VLVERIFY VLCMD VERIFY MOUNTIV VLCMD MOUNTIV VLSDF2TDO VLCMD SDF2TDO QCENTERA QCENTERA VLVERIFY VLCMD VERIFY UDFDF UDFCMD FDF VLSDF2TDO VLCMD SDF2TDO UDFFILE UDFCMD FFILE VLVERIFY VLCMD VERIFY

of 180

Note: In the examples, the Unix path and device name for the library are used (example /opt/QStar/dev/jb/rjb1a; jb, jb1, jb2). The default Windows name of the device is JB0, JB1, etc, and the path should be changed with the Windows path. For Windows, the default path is C:\qstar\, an alternate path may be chosen at installation. For UNIX this path is /opt/QStar, but this may be altered by installing QStar in an alternate the commands use directory, then creating a symbolic link to /opt/QStar.

of 180

FLOC NAME

floc – Locates which media a file is located on. SYNOPSIS

floc cache_root filename DESCRIPTION

The floc command specifies which media a file is located on, it will print out the sequence number of the media in the Integral Volume set.

OPTIONS

None NOTES

Can only be used with the SDF / TDO file system. EXAMPLES

floc c:\cache\cache_test \file1 (Windows) floc /cache/cache_test /file1 (UNIX)

Lists the media that has the file called file1 located on it where the cache root is c:\cache\test.

\file1: 2 data_pages (128 KB) Vol 0: 128 KB

floc c:\cache\cache_test \folder1\folder2\file2 (Windows) floc /cache/cache_test /folder1/folder2/file2 UNIX)

List the media that has the file called file2 (with Sub-directories type the absolute path of the file) located on it where the cache root is c:\cache\cache_test.

\folder1\folder2\file2: 2 data_pages (128 KB) Vol 0: 128 KB

of 180

FLSVOL NAME

flsvol – Lists all files located on a media surface. SYNOPSIS

flsvol cache_root vol_number DESCRIPTION

The flsvol command lists all files located on a specified volume within an Integral Volume set.

OPTIONS

None NOTES

Can only be used with the SDF / TDO file systems. EXAMPLES

flsvol c:\cache\test 1 (Windows) flsvol /cache/test 1 (UNIX)

Lists all files located on volume (sequence number) 1 where the cache root is c:\cache\test.

of 180

JBCLEANING NAME

jbcleaning - Loads a cleaning tape from the shelf into the drive. SYNOPSIS

jbcleaning [-H host_name] device_name drive_number shelf_number DESCRIPTION

The jbcleaning command loads a cleaning tape from the shelf to the drive. The shelf is specified by the shelf_number argument. The drive is specified by the drive_number argument.

OPTIONS

-H host_name Specifies the name of the host where the device is connected. Without this option, the local host is used.

EXAMPLES

jbcleaning jb 1 2 Loads a cleaning tape from the shelf number 2 to drive number 1.

of 180

JBDRIVE NAME

jbdrive – Changes or shows the status of a library drive. SYNOPSIS

jbdrive [-H host_name] [-nfbrl] [-u {priority | rrr:www:rw | auto | default}] [-p {cd-rom | cd-r | cd-rw | dvd-rom | dvd-r | dvd-ram | dvd-rw | dvd-rw-s | bd-{rom|r|rr|re}] | lto{1|2|3|4|5|6}[r]}]device_name drive_number

DESCRIPTION

The jbdrive command changes the online/offline status of the drive or clears the bad status of the drive in case of a hardware failure.

OPTIONS


With options, set the drive state as follows:

-n Set the drive online.

-f Set the drive offline.

-b Clear the bad status of the drive. -r Set default media type of the drive.

This flag is used with libraries with CD-ROM, CD-R, DVD-ROM, DVD-R, DVD-RAM, DVD-RW, DVD-RW-S, BD-ROM, BD-R, BD-RR, BD-RE or library with LTO1, LTO2, LTO3, LTO4, LTO5, LTO6 drives present.

-p Set media type of the drive. This flag is used with

libraries with CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-R, DVD-RAM, DVD-RW, DVD-RW-S, BD-ROM, BD-R, BD-RR, BD-RE or library with LTO1, LTO2, LTO3, LTO4, LTO5, LTO6 drives present. The jbstatus command shows the drive's capabilities and media type of the shelves. The media type is automatically set and can be altered with -p option, and after that, the jbscheduler will only load a media to a drive, that can handle this media type. The -p option can be used several times.

of 180

–u priority_number | rrr:www:rw | auto | default

Sets the priority for the usage of the drives. This flag is used with libraries with CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-R, DVD-RAM, DVD-RW, DVD-RW-S, BD-ROM, BD-R, BD-RR, BD-RE or library with LTO1, LTO2, LTO3, LTO4, LTO5 drives present. The priority defines the order in which the drives are used by jbscheduler when it is looking for an appropriate drive.

Example,in a library with four drives the priority numbers that can be used are 1,2,3,4. The jbscheduler searches for the drive, starting with the lowest priority. The rrr:www:rw format assigns drive priority for read, write and read-write operations separately. The keyword auto assigns drive priority according to drive capabilities. This allows drives with the least capabilities to be used first, leaving multi-function drives with more capabilities available for a wider range of media types.

–l Print load and access elapsed time of the full drive.

NOTES

The -n and -f options are mutually exclusive. Only one may set the drive state. A drive can be set online only if the jbscheduler for the library is running.

Without options, print the current drive state:

- online/offline,

- full/empty,

- bad, if the last move operation with this drive failed.

- shelf_number and side ('a' or 'b'), if the drive contains a media.

- remaining lease time. - load and access elapsed time. NOTES

If the drive online/offline status is changed and the drive contains a media, which is not an open tape, it is unloaded back to the shelf it came from. The online/offline status of the drive is only valid if the jbscheduler is running.

EXAMPLES

jbdrive jb 1 Drive 1: online empty

of 180

JBEXPORT NAME

jbexport – Exports a media from the library. SYNOPSIS

jbexport [-H host_name] device_name shelf_number DESCRIPTION

The jbexport command exports a media from the shelf to the mailslot. The shelf is specified by the shelf_number argument.

OPTIONS


EXAMPLES

jbexport jb 1 Export the media from shelf 1.

of 180

JBFLIP NAME

jbflip – Inverts a media in the drive. SYNOPSIS

jbflip [-H host_name] device_name drive_number DESCRIPTION

The jbflip command inverts a media in the drive. The drive is specified by the drive_number argument. Either the drive must be offline or the jbscheduler should not be running.

OPTIONS


EXAMPLES

jbflip jb 1

of 180

JBIMPORT NAME

jbimport – Imports a media into the library. SYNOPSIS

jbimport [-H host_name] device_name shelf_number

For Hard Disk simulated library: jbimport [-H host_name] –S [A=]disk_id[:{rw|worm}:{number_of_blocks|xxMB|xxGB} :block_size]device_name shelf_number

jbimport [-H host_name] –S [A=]disk_id[:[rw|worm]:{pdd|udo|udo2|mo91|dvdram|dvd-r

|cd-r|bd-re| bd-re-50|bd-r|bd-rs-50|bd-r-100}] device_name shelf_number

jbimport [-H host_name] -S tape_id[:capacity_meg:{dlt|sdx|sdz|ultrium}] :{rw|worm}] device_name shelf_number

For Centera simulated library: jbimport [-H host_name] -S [A=]centera_disk_id[:{number_of_blocks|xxMB|xxGB} :block_size] device_name shelf_number jbimport [-H host_name] -S [A=]centera_disk_id[:{pdd|udo|udo2|mo91|dvd-r|cd-r|bd-

re|bd-re-50|bd-r|bd-rs-50|bd-r-100}] device_name shelf_number jbimport [-H host_name] -S centera_tape_id[:capacity_meg:{dlt|sdx|sdz|ultrium}] device_name shelf_number

DESCRIPTION

The jbimport command imports a media from the mailslot to the shelf. The shelf is specified by the shelf_number argument.

The form of the jbimport command with the -S simulation_param option imports the simulated disk to the specified shelf. See jbsim command for more detailed informations.

OPTIONS


of 180

-S [A=]disk_id:{rw|worm}:{number_of_blocks|xxMB|xxGB}:block_size A new HD disk is created to represent a rewritable (rw) or WORM(worm) disk with the capacity specified by number_of_blocks and block_size. If A= is present,the disk has side A only. Without A=,the disk is two-sided. Each surface is represented by a file in directory dir_path associated with the HD disk library. The actual file name is <disk_id>_A.rw_<number_of_blocks>_<block_size> for side B and <disk_id>_B.rw_<number_of_blocks>_<block_size> (if it exists). The block_size must be divisible by 512 and not exceed 8192. The disk capacity must be greater than or equal to 10MB and less than 100GB. Number_of_blocks may be specified indirectly as xxMB or xxGB, where "xx" is the number of megabytes(MB) or gigabytes(GB).

-S [A=]disk_id:[rw|worm]:shortcut

The same but the disk capacity is derived from a real disk type specified by shortcut:

pdd Number_of_blocks 10789472, block_size 2048. udo Number_of_blocks 1834348, block_size 8192. udo2 Number_of_blocks 3669718, block_size 8192. mo91 Number_of_blocks 1095840, block_size 4096. dvdram Number_of_blocks 2236704, block_size 2048. dvd-r Number_of_blocks 2297888, block_size 2048. cd-r Number_of_blocks 327680, block_size 2048.

bd-re Number_of_blocks 11826176, block_size 2048. bd-re-50 Number_of_blocks 23652352, block_size 2048. bd-r Number_of_blocks 12219392, block_size 2048. bd-r-50 Number_of_blocks 24438784, block_size 2048. bd-r-100 Number_of_blocks 48878592, block_size 2048.

With dvdram, dvd-r, cd-r, bd-re, bd-re-50, bd-r, bd-r-50, or bd-r-100 the medium type (rw|worm) must be omitted. With

pdd, udo, udo2, or mo91, the medium type must be present. -S [A=]disk_id An existing HD disk is imported. -S tape_id:capacity_meg:{dlt|sdx|sdz|ultrium}:{rw|worm} A new HD tape is created to represent a tape. Capacity_meg specifies the tape capacity in megabytes and must be greater

than or equal to 10 MB and less than 1000 GB. A tape can be rewritable (rw) or WORM (worm). A tape can be one of the following types:

dlt DLT tape. sdx SONY SDX tape. sdz SONY SDZ (S-AIT) tape. ultrium IBM/HP ULTRIUM tape.

A tape is represented by a file in directory dir_path associated with the HD tape library. The actual file name is <disk_id>_A.<type> where <type> is dlt, sdx, etc.

of 180

-S tape_id An existing HD tape is imported. -S [A=]centera_disk_id:{number_of_blocks|xxMB|xxGB}:block_size A new Centera disk is created to represent a WORM disk. If A= is present, the disk has side A only. Without A=, the disk is two-sided. The disk capacity is specified as for HD disk and has the same limitations. -S [A=]centera_disk_id:shortcut The same as above but the disk capacity is derived from shortcut (see

above). -S [A=]centera_disk_id An existing Centera disk is imported. -S centera_tape_id:capacity_meg:{dlt|sdx|sdz|ultrium} A new Centera tape is created. The tape capacity and type are specified as for HD tape. -S centera_tape_id An existing Centera tape is imported. EXAMPLES

jbimport jb 1 Import a media from the mailslot to shelf 1.

of 180

JBLEASE NAME

jblease - Sets the drive lease time for the shelf. SYNOPSIS

jblease [-H host_name] -L on -T default device_name [shelf_number[:to_shelf_number]]

jblease [-H host_name] -L on -T seconds device_name [shelf_number[:to_shelf_number]]

jblease [-H host_name] -L on -T restore device_name [shelf_number[:to_shelf_number]]

jblease [-H host_name] -L off device_name [shelf_number[:to_shelf_number]]

jblease [-H host_name] -L off -T save device_name [shelf_number[:to_shelf_number]]

jblease –l DESCRIPTION

The media loaded from a shelf into drive occupies the drive and prevents other media from being loaded. In order to prevent monopolization of the drive, the time the media is loaded in the drive may be managed using the drive lease approach. The media loaded in the drive may be "locked" which may be necessary for some operations such as tape copy. By default the media is loaded into drive for some time period which depends on the drive load/unload time. The jblease command allows manipulation of media residency timing in the drive. The drive lease is mainly relevant to the tape drives because operations on the tape are position sensitive. There is difference in lease timing for real and virtual tape libraries. The virtual tape load/unload and positioning operations are much faster and lease time can be made (and by default are) smaller. The first form of the command (-L on -T default) sets default lease time for the specified shelf and enables (or continues) leasing. Default value of lease time see in sixth form of the command. The second form of the command (-L on -T seconds) sets a lease time equal to specified number of seconds and enables (or continues) leasing. The third form of the command (-L on -T restore) sets an old (restores saved) value of the lease time (see fifth form of the command) and enables (or continues) leasing. The fourth form of the command (-L off) disables leasing and removes (reset) lease time. The fifth form of the command (-L off -T save) saves current lease time and disables leasing.

of 180

The sixth form of the command (-l) shows default value of lease time (900 sec for the real and 30 sec for virtual tape drives).

NOTE

The jblease command can be used for a single shelf specifying the shelf_number argument, for a range of shelves specifying the shelves shelf_number and the to_shelf_number arguments or for all shelves in the appropriate format. The jblease command should be applied only when the shelf is open, because qs_scsi_open and qs_scsi_close calls on shelf (in the application) resets the lease time of the shelf. It should be noted that the application itself is able to manage lease timing (using the qs_scsi_lease call). Currently the tape enabled migrators (TDO, SDF, LTFS) and utilities (vlcopy, vlcmp commands) sets default lease time after opening the shelf. Once the media from the shelf is loaded into a drive it becomes locked for a specified number of seconds (lease time). After the specified number of seconds expires, the tape in the drive is unlocked and can be unloaded if there is a request for other media to be loaded into the drive. If another media is loaded into the drive the application (SDF, TDO, LTFS migratory or utilities) remains unaware of that event because SCSI sub-system preserves all tape related parameters, such as position, compression, partition settings, and restores those values after media is returned back (please note that the media can be returned to a different compatible tape drive). The drive leasing is useful when a limited number of drives are present, for example, when three Integral Volume sets are mounted simultaneously while there are only two drives. The other usage example is when a media refresh or import is required, but all drives are busy.

OPTIONS

-H host_name

Specifies the name of the host where the device is connected. Without this option, the local host is used.

-L {on | off} Enables (on) or disables (off) leasing specified shelf. -T {seconds | default | restore | save}

Specifies the value time leasing (in seconds, default or saved value) or save current value.

-l Shows default value of lease time.

of 180

EXAMPLES Example 1. List the default drive lease values.

jblease -l Default lease time: Virtual tape drives: 30 sec. Real tape drives: 900 sec. Example 2. Set default drive lease time for shelf 10 into a storage library "spectra" (Real tape drive). jblease -L def spectra 10; jbshelf spectra 10 Shelf 10: lto4 online full lease=On,900 Example 3. Set default drive lease time for shelf 2 into the storage library "tand" (Virtual tape drive). jblease -L on -T default tand 2; jbshelf tand 2 Shelf 2: lto3 online full lease=On,30 Example 4. Enable infinite drive lease time for shelf 2 into the storage library "tand". jblease -L on -T 0 tand 2; jbshelf tand 2 Shelf 2: lto3 online full lease=On,infinity Example 5. Set 1234 second drive lease time for shelf 2 into the storage library "tand". jblease -L on -T 1234 tand 2; jbshelf tand 2 Shelf 2: lto3 online full lease=On,1234 Example 6. Disable drive lease feature and save current lease time for shelf 2 into the storage library "tand". This may be useful in case when system needs to finish some operation without interruption on the shelf 2, for example copy media. jblease -L off -T save tand 2; jbshelf tand 2 Shelf 2: lto3 online full lease=Off,1234 Example 7. Restore lease time and enable lease feature for shelf 2 into the storage library "tand". jblease -L on -T restore tand 2; jbshelf tand 2 Shelf 2: lto3 online full lease=On,1234 Example 8. Disable drive lease feature for shelf 2 into the storage library "tand". jblease -L off tand 2; jbshelf tand 2 Shelf 2: lto3 online full

of 180

LEASE EXAMPLES WITH TIME MONITORING The following UNIX command line example assumes that the drive lease time is set as follows: jblease -l tand Default lease time: Virtual tape drives: 30 sec. Real tape drives: 900 sec. Execute two simultaneous tape read operations from two shelves while the system has one drive available. During execution user periodically checks the storage library status (using jbstatus command). qscsi_read -L on -T default /opt/QStar/dev/tand/rjb2a /dev/null 0 10000 0& [1] 23781 qscsi_read -L on -T default /opt/QStar/dev/tand/rjb3a /dev/null 0 10000 0& [2] 23782 <qs_scsi_lease call on /opt/QStar/dev/tand/rjb3a> sleep 10; jbstatus tand TAPE-tand 2:4 EXABYTE MAGNUM 224 # 9008A446L110 ------------ Drive 1: lto3-rw online full loaded shelf 3a, remaining lease time 25s Drive 2: lto3-rw offline empty ------------ Shelf 1: online empty Shelf 2: lto3 online full open Shelf 3: lto3 online loaded open drive 1 lease=On,30 Shelf 4: online empty sleep 20; jbstatus tand TAPE-tand 2:4 EXABYTE MAGNUM 224 # 9008A446L110 ------------ Drive 1: lto3-rw online full loaded shelf 3a, remaining lease time 5s Drive 2: lto3-rw offline empty ------------ Shelf 1: online empty Shelf 2: lto3 online full open Shelf 3: lto3 online loaded open drive 1 lease=On,30 Shelf 4: online empty <qs_scsi_lease call on /opt/QStar/dev/tand/rjb2a> sleep 20; jbstatus tand TAPE-tand 2:4 EXABYTE MAGNUM 224 # 9008A446L110 ------------ Drive 1: lto3-rw online full loaded shelf 2a, remaining lease time 21s Drive 2: lto3-rw offline empty ------------ Shelf 1: online empty Shelf 2: lto3 online loaded open drive 1 lease=On,30 Shelf 3: lto3 online full open lease=On,30 Shelf 4: online empty

of 180

sleep 20; jbstatus tand TAPE-tand 2:4 EXABYTE MAGNUM 224 # 9008A446L110 ------------ Drive 1: lto3-rw online full loaded shelf 2a, remaining lease time 1s Drive 2: lto3-rw offline empty ------------ Shelf 1: online empty Shelf 2: lto3 online loaded open drive 1 lease=On,30 Shelf 3: lto3 online full open lease=On,30 Shelf 4: online empty sleep 20; jbstatus tand TAPE-tand 2:4 EXABYTE MAGNUM 224 # 9008A446L110 ------------ Drive 1: lto3-rw online full loaded shelf 3a, remaining lease time 16s Drive 2: lto3-rw offline empty ------------ Shelf 1: online empty Shelf 2: lto3 online full open lease=On,30 Shelf 3: lto3 online loaded open drive 1 lease=On,30 Shelf 4: online empty

of 180

JBLOAD NAME

jbload - Loads a media from the shelf into the drive. SYNOPSIS

jbload [-H host_name] [-o {rdonly|wronly}] device_name drive_number shelf_number{a|b}

DESCRIPTION

The jbload command loads a media from the shelf to the drive. The shelf is specified by the shelf_number{a|b} argument where the shelf number is concatenated with the letter designating which side('a' or 'b')is to be inserted. The drive is specified by the drive_number.

OPTIONS


-o {rdonly|wronly} Specifies the mode in which loaded media should be accessible: read or write-only. Without this option, the read-write access is assumed.

NOTES

Either both the shelf and drive must be offline or the jbscheduler should not be running.

EXAMPLES

jbload jb 1 2a Loads a media from the shelf number 2 to drive number 1 with the A side up.

of 180

JBMAGAZINE NAME

jbmagazine - Exchanges media in the library using the magazines. Magazines contain multiple pieces of media.

SYNOPSIS

jbmagazine [-H host_name] [-h] [-v] device_name [magazine_number | h] DESCRIPTION

The jbmagazine command exchanges media in the library using the magazines. The library is specified by the device_name argument. If magazine_number and -h option are omitted all magazines are available for exchange. Substitute "h" as the magazine_number or use -h option for the hyper magazine (Pioneer library only).

OPTIONS


-v Verbose

Prints a list of the shelves exchanged. EXAMPLES

jbmagazine jb

of 180

JBMOVE NAME

jbmove - Moves a media from one shelf / slot to another in the library. SYNOPSIS

jbmove[-H host_name]device_name source_shelf_number destination_shelf_number

DESCRIPTION

The jbmove command moves a media from the source shelf to the destination shelf in the library.

OPTIONS


EXAMPLES

jbmove jb 1 2 Moves the media from the shelf 1 to shelf 2.

of 180

JBPARAM NAME

jbparam – Prints or sets the tunable time parameters of the library.

SYNOPSIS

jbparam [-H host_name] [-{i|q|d} {D | seconds}] [-tsfF] device_name DESCRIPTION

The jbparam command prints or sets the tunable time parameters of the library. These parameters include the inactive time, the idle time and the quantum time.

OPTIONS


Without any options, print the current parameters and statistics values:

Time control values (inactive, idle, and quantum times) in seconds and statistics values (nimports, nexports, nloads, nunloads, and nflips).

With options, set the time parameters:

-i Set inactive time.

The library inactive time is defined as the amount of time a media loaded in a drive is allowed to stay in the drive without any pending I/O. After the library inactive time expires, the media is unloaded back to its shelf / slot. The default value of the library inactive time is 15 minutes or 900 seconds. If the inactive time is set to zero, the mechanism is disabled. The library inactive time must be set to zero or to a value greater or equal to 60 seconds. This command requires that the jbscheduler is running.

NOTES

This mechanism protects disks from spinning in the drives for long periods of time with no activity. It also makes access to heavily used platters quicker by leaving them in the drive for longer than one access.

of 180

If the inactive time is set to zero, a media loaded in a drive will stay in the drive until another media needs to be loaded into the drive.

-q Set quantum time.

The library quantum time is defined as the amount of time a surface is bound to a drive while other platters are queued for I/O. Once loaded in a drive, a surface stays in the drive for the entire library quantum time unless the library idle time is set to a positive value and there is no I/O activity for the loaded platter for the duration of the idle time. The default value of the library quantum time is 10 seconds. The quantum time must be in the range between 10 and 7200 seconds. The quantum time must be twice the value of the idle time if the idle time is not zero. This command requires that the jbscheduler is running.

ERROR MESSAGES

Value out of boundaries. The given value is too small, relative to the library idle time or not within the allowed time range.

-d Set idle time.

The idle time is defined as the amount of time a media loaded in a drive is allowed to stay in the drive without any I/O. After the idle time has elapsed, even when the quantum time has not, a loaded media is eligible to be swapped out. The default value of the library idle time is 0 seconds, which means that this mechanism is disabled. This mechanism should be enabled to improve overall performance of the library. The –d option can be used to fine tune the idle time in a library. The idle time must be set to a value between 5 seconds and one half of the library quantum time or to zero to disable this mechanism. The jbparam command without options can be used to get the current value of the library idle time. This command requires that the jbscheduler is running.

of 180

ERROR MESSAGES

Value out of boundaries. The given value is too little or too large relative to the library quantum time.

NOTES

This mechanism improves overall performance by allowing I/Os on media that are waiting for a loaded drive to be serviced more quickly, because they are not required to wait until the quantum times of media that are in drives elapse. Disabling the idle time mechanism will leave a media in a drive for the entire quantum time, even if there are no I/Os for the media in the drive. The idle time must be set to a value between 5 seconds and one half of the library quantum time or to zero to disable this mechanism. A value less than 5 seconds would make swapping of media too frequent and is all the more useless since the moving of media from shelves to drives and the waiting of media to be ready for use may take as long as 5 to 10 seconds (WORM disks).

-t Set all time parameters to their default values.

-s Clear the statistics values. -f Allow jbscheduler to control the front panel of the library.

-F Prohibit jbscheduler to control the front panel of the library.

NOTES

The -idq options set the time parameter to the value of the seconds argument. This value can be specified as a number of seconds or the letter D that means the default value. The default values are the following:

Inactive time is 15 minutes Quantum time is 10 seconds Idle time is 0

EXAMPLES

jbparam -q 20 jb Sets the quantum time to 20 seconds.

jbparam jb produces (after running the previous command)

Inactive time: 900 Idle time: 0 Quantum time: 20 Imports: 0 Exports: 0 Loads: 1 Unloads: 0 Flips: 0

of 180

JBPING NAME

jbping - Checks to see if the jbserver is running. SYNOPSIS

jbping [-H host_name] DESCRIPTION

The jbping command checks to see that the jbserver is running. OPTIONS


EXAMPLES

jbping jbping: JB server thread is running.

of 180

JBRESERVE NAME

jbreserve – Sets the reserve time for the surface. SYNOPSIS

jbreserve [-H host_name] device_name shelf_number{a|b} seconds DESCRIPTION

The jbreserve command reserves a specific surface in a drive for the specified number of seconds, in addition to the quantum time (See jbparam). The jbreserve command applies only to the next time the disk is loaded into a drive. After the specified number of seconds, the quantum time for the specified surface will revert to the previous quantum time setting. The surface is specified by the shelf_number{a|b} argument where the shelf number is concatenated with the letter ('a' or 'b') designating the side. The reserve time is specified by the seconds’ argument. A value of 0 means that reserve time mechanism for this surface is disabled. The shelf must be online.

OPTIONS


EXAMPLES

jbreserve jb 1a 15

of 180

JBRESET NAME

jbreset - Clears the bad status of a drive. SYNOPSIS

jbreset [-H host_name] device_name drive_number [shelf_number] DESCRIPTION

The jbreset command clears the possible bad status of a drive. The drive is specified by the drive_number argument. If the drive contains a medium, jbreset first clears the possible bad status of the shelf and then moves the medium back to its shelf. The online/offline status of the drive and shelf is not changed.

If the drive has lost source shelf information, an optional empty shelf_number should be used to specify the destination of the unload. If this argument is used when the source shelf information is not lost, it is ignored.

OPTIONS


EXAMPLES

jbreset jb 1

of 180

JBSCHEDCHECK NAME

jbschedcheck – Checks to see if the jbscheduler is running for a library.

SYNOPSIS

jbschedcheck [-H host_name][-a | device_name] DESCRIPTION

The jbschedcheck command checks to see if the jbscheduler daemon is running for the library specified by the device_name argument.

OPTIONS


-a Checks to see if the jbscheduler daemons are started for

all libraries connected to the server. EXAMPLES

jbschedcheck jb jb: Jbscheduler is running.

of 180

JBSCHEDULER NAME

jbscheduler – Starts the scheduler for a library. SYNOPSIS

jbscheduler [-H host_name] [-sdL] device_name DESCRIPTION

The jbscheduler command starts the scheduler daemon for the library specified by the device_name argument. On start, the jbscheduler does the following:

Sets all drives online and, if a drive contains a medium, it is unloaded back to the shelf. Sets all shelves online.

OPTIONS


-d On start, sets all drives offline.

-s On start, sets all shelves offline. -L On start, enables debug log.

EXAMPLES

jbscheduler jb jb: Jbscheduler is running.

of 180

JBSHELF NAME

jbshelf – Changes or shows the status of the library shelves / slots. SYNOPSIS

jbshelf [-H host_name] [-nfbr1ABC] [-p {cd-rom | cd-r | cd-rw | dvd-rom | dvd-r | dvd-ram | dvd-rw | dvd-rw-s | bd-{rom |r|rr|re} | lto{1|2|3|4|5|6}}] device_name shelf_number

DESCRIPTION

The jbshelf command changes the online/offline status of the shelf or clears the bad status of a shelf in case of a hardware failure, reports/sets medium type.

OPTIONS


-n Sets the shelf online.

-f Sets the shelf offline and clears its reserve time.

-b Clears the bad status of the shelf.

-C Shelf contains cleaning tape.

-1 Sets single sided media type for the shelf. This flag

is used with libraries that support single and double sided media.

-r Sets default media type of the shelf.

This flag is used with libraries with CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-R, DVD-RAM, DVD-RW, DVD-RW-S, BD-ROM, BD-R, BD-RR, BD-RE or library with LTO1, LTO2, LTO3, LTO4, LTO5, LTO6 drives present.

-A or –B Sets specified profile for side A or side B respectively. Without these options profile is set for both sides of double sided media.

of 180

-p Sets media type of the shelf. This flag is used with libraries with CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-R, DVD-RAM, DVD-RW, DVD-RW-S, BD-ROM, BD-R, BD-RR, BD-RE or library with LTO1, LTO2, LTO3, LTO4, LTO5, LTO6 drives present. The jbstatus command shows drive's capabilities and media type of the shelves. The media type is automatically set and can be altered with -p option, and after that, the jbscheduler will only load a media to a drive, that can handle this media type. The -p option can be used several times. Value 1 is the same as -1 flag.

NOTES

The -n and -f options are mutually exclusive. Only the administrator may set the shelf state. A shelf can be set online only if the jbscheduler for the library is running.

EXAMPLES

jbshelf -f jb 2 Sets the shelf number 2 offline.

of 180

JBSHUT NAME

jbshut – Stops the jbscheduler for a library. SYNOPSIS

jbshut [-H host_name] [-f] device_name DESCRIPTION

The jbshut command stops the jbscheduler for the specified library. This command sends a stop request to the jbscheduler. The jbscheduler will be stopped only if there are no outstanding requests waiting for jbscheduler and all Integral Volume sets are unmounted. Upon receiving this request the jbscheduler does the following steps: - Unloads media from all drives which are online.

- Sets all shelves and drives offline.

- Satisfies all pending bind and block-fault requests with the ENODEV error.

- Exits.

OPTIONS


-f With this option, the jbscheduler will be stopped

unconditionally and all processes waiting for its response will get the ENODEV error.

EXAMPLES

jbshut –f jb Stop jbscheduler unconditionally.

of 180

JBSIM NAME

jbsim - Manages simulated devices. SYNOPSIS

jbsim [-H host_name] device_name jbsim [-H host_name] -LP device_name

jbsim [-H host_name] -h {disk|tape} device_name shelf_count dir_path

jbsim [-H host_name] -c {disk|tape} device_name shelf_count [centera_index]

jbsim [-H host_name] -p device_name shelf_count dir_path [A=]dst_device_name

[:from_shelf:to_shelf] DESCRIPTION

The jbsim command creates a simulated library or prints information about the simulated library and its shelves. With -h, -c or -p option, the library is created. With -P option, it lists all files in the directory associated with the HD (hard drive) library. Without options, the library and shelves information is printed.

OPTIONS

-H host_name Specifies the name of the host where the library will be created. Without this option, the local host is used.

-L Prints shelves and locations of imported media. For HD/proxy medium

the location is the pathname of the file representing the medium. For Centera medium, it is just volume Ids of its surfaces. Without this option (and without -P option) the location is just volume Ids.

-P Prints volume Ids of all media (imported and not imported) associated

with this library.

-h {disk|tape} Creates a simulated HD library with name device_name and the number of shelves equal to shelf_count. -h disk creates a disk library, -h tape - a tape library. Each disk/tape is a file on the hard drive (HD disk/tape). The last argument - dir_path - specifies the directory where these files will be held. Each shelf in the library has two sides.

of 180

The dir_path argument is the location where the simulated media will be created. Inside the dir_path location a file called __links will be automatically created. This file can be used to insert the directories pathname of the other locations where the simulated media will be created. This allows the System Administrator to specify several locations where the simulated media will be created in case the main partition has limited space. In the __links file every continuation directory pathname occupies a single line. Empty lines and lines that begin with the “#” sign are ignored. The simulated media will be created on the main dir_path once there is no space available for new simulated media the Software will start to create the new simulated media in the location specified in the __links files starting from the first pathname inserted.

-c {disk|tape} Creates a simulated Centera library with name device_name and the number of shelves equal to shelf_count. -c disk creates a disk library, -c tape - a tape library. Each disk/tape resides

on the Centera. Each shelf in the library has two sides. An optional argument centera_index specifies which Centera storage system (1-30) will hold the library. The default centera_index is 1.

-p Creates a proxy disk library with name device_name and the number of shelves equal to shelf_count. The device_name must be in form "proxyN" where N is from 1 to 31 (for example proxy1, proxy23). Each disk is a file on the hard drive. dir_path specifies the directory where these files will be held. The last argument specifies the destination library: dst_device_name is its device name. from_shelf and to_shelf specify the range of shelves used to find a destination disk. If they are absent, all shelves are used. With A=, the disks are 2-sided, otherwise 1-sided. PROXY DISKS

All proxy disks are automatically imported at the time of the library creation. A proxy disk is automatically added to the Integral Volume set if the Integral Volume set definition includes proxy media. When the proxy disk becomes fully written, it is copied to a disk in the destination library. After the copy, the destination disk is used in the Integral Volume set instead of the proxy disk, whereas the proxy disk is declared empty and can be used again.

IMPORT IN SIMULATED LIBRARY

An extra option is used in jbimport and vlimport commands to specify a simulated disk/tape to be "imported" to the shelf. The characters accepted in disk_id and tape_id below are letters, digits, '_', '-', and '.'. In case of HD disk/tape the letters are locale-specific alphabetic characters. In case of Centera disk/tape the letters are ASCII alphabetic characters and the first character must be a letter or an underscore '_'.

of 180

The option (-S simulation_param) has one of the following forms:

-S+ Import all existing media. Import starts from the shelf specified by shelf_number. Already imported media and full shelves are skipped.

-S [A=]disk_id:{rw|worm}:{number_of_blocks|xxMB|xxGB}:block_size

A new HD disk is created to represent a rewritable (rw) or WORM (worm) disk with the capacity specified by number_of_blocks and block_size. If A= is present, the disk has side A only. With- out A=, the disk is two-sided. Each surface is represented by a file in directory dir_path associated with the HD disk library. The actual file name is <disk_id>_A.rw_<num- ber_of_blocks>_<block_size> for side B and <disk_id>_B.rw_<num- ber_of_blocks>_<block_size> (if it exists). The block_size must be divisible by 512 and not exceed 8192. The disk capacity must be greater than or equal to 10 MB and less than 100 GB. num- ber_of_blocks may be specified indirectly as xxMB or xxGB, where "xx" is the number of megabytes (MB) or gigabytes (GB).


The same as above but the disk capacity is derived from a real disk type specified by shortcut:

pdd Number_of_blocks 10789472, block_size 2048. udo Number_of_blocks 1834348, block_size 8192. udo2 Number_of_blocks 3669718, block_size 8192. mo91 Number_of_blocks 1095840, block_size 4096. dvdram Number_of_blocks 2236704, block_size 2048. dvd-r Number_of_blocks 2297888, block_size 2048. cd-r Number_of_blocks 327680, block_size 2048. bd-re Number_of_blocks 11826176, block_size 2048.

bd-re-50 Number_of_blocks 23652352, block_size 2048. bd-r Number_of_blocks 12219392, block_size 2048. bd-r-50 Number_of_blocks 24438784, block_size 2048. bd-r-100 Number_of_blocks 48878592, block_size 2048.

With dvdram, dvd-r, cd-r, bd-re, bd-re-50, bd-r, bd-r-50, or bd-r-100 the medium type (rw|worm) must be omitted. With pdd, udo, udo2, or mo91, the medium type must be present.

-S [A=]disk_id An existing HD disk is imported. -S tape_id:capacity_meg:{dlt|sdx|sdz|ultrium}:{rw|worm} A new HD tape is created to represent a tape. Capacity_meg specifies the tape capacity in megabytes and must be greater

than or equal to 10 MB and less than 1000 GB. A tape can be rewritable (rw) or WORM (worm). A tape can be one of the following types:



of 180

-S tape_id An existing HD tape is imported. -S [A=]centera_disk_id:{number_of_blocks|xxMB |xxGB}:block_size A new Centera disk is created to represent a WORM disk. If A= is present, the disk has side A only. Without A=, the disk is two-sided. The disk capacity is specified as for HD disk and has the same limitations. -S [A=]centera_disk_id:shortcut The same as above but the disk capacity is derived from shortcut (see

above). -S [A=]centera_disk_id An existing Centera disk is imported. -S centera_tape_id:capacity_meg:{dlt|sdx|sdz|ultrium} A new Centera tape is created. The tape capacity and type are specified as for HD tape. -S centera_tape_id An existing Centera tape is imported. EXAMPLES jbsim -h disk simd 10 /export/home/disks Creates a simulated library of HD disks with 10 shelves. The directory /export/home/disks is associated with the library; files representing disks will reside in this directory. jbsim -h tape simt 6 /export/home/tapes Creates a simulated library of HD tapes with 6 shelves. The directory /export/home/tapes is associated with the library; files representing tapes will reside in this directory. jbsim -c disk cend 4 Creates a simulated library of Centera disks with 4 shelves.

of 180

JBSTATISTICS NAME

jbstatistics - Manages library statistics. SYNOPSIS

jbstatistics [-S {LRBPS}|-C {LRBPS...|a}] -s device_name [shelf_number{a|b} ...]

jbstatistics [-S {LRBPS}|-C {LRBPS...|a}] -d device_name [drive_number ...]

jbstatistics [-Ca] -c device_name

jbstatistics [-S {LRBPS}|-C {LRBPS...|a}] device_name DESCRIPTION

The jbstatistics command allows clearing or printing of QStar library statistics. Statistics are collected for every surface and drive and contains the following counts: "Loads" (number of loads for surface/drive, "Recover" (number of recovered errors occurred on surface/drive), "Bad" (number of cases when shelf/drive was marked bad), "PDL" (number of primary defect blocks on the surface), and "SDL" (number of secondary defect blocks on the surface). Statistics for number of recovered errors are also collected for the carrier. The number of defect blocks are recalculated on every load of the surface.

The 1st form of the command prints or clears shelf statistics. The 2nd form of the command prints or clears drive statistics. The 3rd form of the command prints or clears carrier statistics. The 4th form of the command prints or clears statistics for all shelves, drives, and carrier. With the –C option, the command clears statistics, otherwise it prints it.

OPTIONS

-S {LRBPS} Prints statistics in descending order according to the value of number of loads (L), number of recovered errors (R), number of cases when shelf/drive was marked bad (B), number of PDL blocks (P), or number of SDL blocks (S).

-C {LRBPS...|a}

Clears statistics for number of loads (L), number of recovered errors (R), number of cases when shelf/drive was marked bad (B), number of PDL blocks (P), number of SDL blocks (S). -Ca is equal to -CLRBPS and clears all numbers.

of 180

-s Used in the 1st form of the command and specifies that the arguments after device_name are shelf numbers or surfaces (Na or Nb where N is the shelf number). If there are no arguments after device_name, the command is applied to all shelves.

-d Used in the 2nd form of the command and specifies that

the arguments after device_name are drive numbers. If there are no arguments after device_name, the command is applied to all drives.

-c Used in the 3rd form of the command and clears/prints

carrier statistics. EXAMPLES

jbstatistics jb Prints the statistics information of library “jb”.

of 180

JBSTATUS NAME

jbstatus – Prints the status of the library. SYNOPSIS

jbstatus [-H host_name] [-cmsdp] device_name DESCRIPTION

The jbstatus command prints the state of all elements present in the library.

OPTIONS


-c Prints only the full/empty status for carriers. -m Prints only the full/empty status for mailslots. -s Prints only the shelf state (see the jbshelf command) for all shelves. -d Prints only the drive state (see the jbdrive command) for all drives. -p Prints the printer state (see the jbprinter command) for all printers.

EXAMPLES

jbstatus jb produces ----------------- Carrier 1: empty ----------------- Mailslot 1: empty ----------------- Drive 1: online full loaded shelf 2a ----------------- Shelf 1: online empty Shelf 2: online loaded drive 1 Shelf 3: online empty Shelf 4: online empty Shelf 5: online full Shelf 6: online empty Shelf 7: online empty Shelf 8: online empty Shelf 9: online empty Shelf 10: online full Shelf 11: online empty Shelf 12: online empty

of 180

JBUNLOAD NAME

jbunload – Unloads a medium from a drive. SYNOPSIS

jbunload [-H host_name] device_name drive_number DESCRIPTION

The jbunload command unloads a medium from the drive back to the shelf. The drive is specified by the drive_number argument. Either the shelf and drive must be offline or the jbscheduler should not be running. If a medium is an open tape it cannot be unloaded.

OPTIONS


EXAMPLES

jbunload jb 1 Unloads a medium back to the shelf.

of 180

LTFSDF NAME

ltfsdf - prints LTFS capacity information. SYNOPSIS

ltfsdf [-H host_name] {filename|set_name}

ltfsdf [-H host_name] -a automount_volume_number {filename|set_name}

ltfsdf [-H host_name] -d dir_name {filename|set_name} DESCRIPTION

The ltfs commands prints LTFS (VSKIN) set capacity information in the manner of Unix "df" command. The set must be mounted. The information includes the number of total blocks, the number of used blocks, and the number of available blocks.

For a spanning set, this is the combined capacity of the whole set. For a single-volume set, this is the capacity of the volume. For an automount set, it is either information for all volumes in the set or for a specified volume.

The set is specified either by its name or by the pathname of any of its files.

OPTIONS

-H host_name Specifies the name of the host where the set resides. Without this option, the local host is used.

-a automount_volume_number

Automount set only. Print information for the volume with this volume number.

-d dir_name

Automount set only. Print information for the volume with

of 180

MKISO NAME

mkiso - Creates an ISO 9660 image image for recording. SYNOPSIS

mkiso [-RJDSq] [-s system_id] [-v volume_id] [-V volume_set_id] [-p preparer_id] [-P publisher_id] [-a application_id] [-c charset] [-x exclude_path] [-o {image_file_name|-}] [cd_dir_name=]path[...]

DESCRIPTION

The mkiso command creates an ISO-9660 filesystem image which may later be recorded onto a CD/DVD-R media. If the -o option is omitted, mkiso only calculates the size of the image and exits.

OPTIONS

-R Uses RockRidge extensions with the ISO-9660 standard. These extensions are mainly useful for UNIX systems.

-J Uses Microsoft Joliet extensions. These extensions are

used for MS-Windows OS.

-D Deference symlinks. This will force symlink files, when encountered, to be replaced by the file or directory that they point to. Without this option symlink files are either omitted from the ISO image or if the -R flag is specified they are preserved as the original symlink file.

-S Uses strict attributes. With this option owner and

permissions of files and directories are preserved and device special files are also saved into the image (the latter makes sense only if the CD is to be mounted on the same OS the image was created on). This flag can only be specified if used in conjunction with the –R flag.

of 180

-q Silently ignore large (>2GB) files. The ISO-9660 filesystem does not support such files. Without this option if a large file is encountered, mkiso prints an error and exits. With this option mkiso skips the file and continues.

-v volume_id

Sets the volume id of the image to volume_id (maximum 32 chars). The volume_id is used as the Volume Label of the CD/DVD media that will be used by the QStar Software as the root directory of the CD/DVD media within the Integral Volume set.

-V volume_set_id

-p preparer_id

-P publisher_id

-s system_id

-a application_id

Sets optional volume_set_id, preparer_id, publisher_id, system_id or application_id fields of the ISO volume descriptor.

-c charset

Specifies the charset to be used for translating filenames to unicode. This option will have no effect unless -J is also specified. The Unicode translation table for the charset is required to be in the /opt/QStar/vl/files sub-directory.

-x exclude_path

Excludes files or directories matching the set pattern. This option allows specifying which types of files should not be included in the ISO image. This option may be repeated as necessary.

-o image_file_name

-o –

Specifies the image output file name. In the first form the output image will be written to image_file_name. In second form the output will be written to a standard output. If it is not a regular file but rather a pipe, 8 bytes of image size are written before the actual image. If the -o is omitted no output is produced but the mkiso will print the information about image size only.

of 180

[cd_dir_name=]path Directory of file named path will be copied into resulting image under name cd_dir_name. If cd_dir_name is omitted then root directory is assumed. The argument may be repeated, but at least one path argument is required.

EXAMPLES

mkiso -v DOC_2 -o /var/spool/cdimage.iso /usr/docs/part2 Creates an ISO CD/DVD image at /var/spool/cdimage.iso using the /usr/docs/part2 subtree as the root of the CD/DVD with the name of the CD/DVD (Volume Label) set to DOC_2.

mkiso -J -x "*.bak" -v DOCS_2_3 -o /var/spool/cdimage1

/part2=/usr/docs/part2 /part3=/usr/docs/part3

Similar to the above but creates an ISO CD/DVD image with Joliet extensions at /var/spool/cdimage.iso and copies the subtrees /usr/docs/part2 and /usr/docs/part3 into the CD/DVD directories /part2 and /part3 respectively with the name of the CD/DVD (Volume Label) set to DOCS_2_3 and excludes files with names ending with .bak.

of 180

MKUDF NAME

mkudf - Creates an UDF volume image from a specified file tree. SYNOPSIS

mkudf [-o image_file|-] [-b block_size] [-m{rewritable|worm}] [-l logical_volume_identifier] [-u{150|200|201}] [-t] [dir_name=]path ...

DESCRIPTION

The mkudf command creates an UDF volume image containing file trees specified by path arguments, which may later be recorded onto an optical or CD/DVD disk. For every path argument, the file specified by path will keep its name in the image (if dir_name= is omitted) or will be renamed to dir_name (if dir_name= is present).

OPTIONS

-o image_file Specifies the pathname of the file where the volume image will be stored. Specifying '-' for the image_file sends the image to standard output.

-b block_size Specifies the block size on the media. The default is 2048.

-l logical_volume_identifier Specifies the logical volume identifier of the volume. The logical_volume_identifier is used as the Volume Label of the CD/DVD media that will used by the QStar Software as a root directory of the CD/DVD media within the Integral Volume set.

-u {150|200|201} Specifies the UDF revision. Default is 1.50.

-t All file times will be set to the current system time. Without this option, they are inherited from the source file.

-m {rewritable|worm}

Specifies the medium type: rewritable or WORM. Default is worm.

EXAMPLES

mkudf -l DOC_2 -o /var/spool/cdimage.udf /usr/docs/part2 Creates an UDF CD/DVD image at /var/spool/cdimage.udf using the /usr/docs/part2 subtree as the root of the CD/DVD with the name of the CD/DVD (logical_ volume_identifier) is set to DOC_2.

of 180

MMADMIN NAME

mmadmin - Administrative operations for MCFS. SYNOPSIS

mmadmin [-H host_name] –c {all,rec,vbtree,pbtree,sbtree,page} {set_name[/filename] I |filename}

mmadmin [-H host_name] -s set_name

mmadmin [-H host_name] -p dst_root_path {set_name[/filename]|filename|set_name

cnode_number} mmadmin [-H host_name] -t [-R] [-o offset:size] {set_name[/filename]|filename} mmadmin [-H host_name] -P {no|yes|invalid} set_name mmadmin [-H host_name] -l{p|l} {set_name/filename|filename} mmadmin [-H host_name] -C cache_root mmadmin [-H host_name] -e set_name mmadmin -d cache_root {info|chunk|entry|hchunk|hentry|cnode|event|btree

|acl|crypto|pte|dw256|dw512|dw1024} element_number

mmadmin -r cache_root chunk chunk_number {clear|empty|prev=N:next=N: total=N:entry=N:removed=N:dir=N}

mmadmin -r cache_root entry entry_address {clear|removed|flags=N:size=N:

content=N:cnode=N:event=N:name=N}

mmadmin -6 {all|meta} src_cache_root dst_cache_root DESCRIPTION

The mmadmin command allows checking the MCFS consistency, taking a snapshot, saving primary data from the cache, and dumping the cache files. It should not be used under normal circumstances. The cache is specified by set_name.

OPTIONS

-H host_name Specifies the name of the host where the Integral Volume set or the cache resides. Without this option, the local host is used.

of 180

-c {all|rec,vbtree,pbtree,sbtree,page} Checks MCFS consistency. The results are sent to the log/<set_name> _manager_consistency file in the release area. What is checked is a comma separated list of keywords: all Checks everything (means "vbtree,pbtree,sbtree,page") rec Does check recursively down the file tree vbtree Validates btrees pbtree Prints btrees sbtree Scans btrees (read directory and match it to btree) page Checks page counts

If a filename is not present the root directory is checked. If a filename is present it specifies a relative (from the root) pathname of the file to be checked. If the file is a directory and rec is specified, the check is applied recursively to every file under this directory.

-s Takes a snapshot of the cache managers internal state. The result goes to the standard output and to log/<set_name>_ manager_snapshot file in the release area.

-p dst_root_path

Saves files with primary data under the destination directory dst_root_path.

-t

Touches a regular file, i.e. declares its replicated and archived pages primary. The argument set_name[/filename] specifies the pathname of the file. If this a regular file, its replicated and archived pages are affected. If this is a directory, it applies to all regular files in that directory. If this is a directory and the option -R is present, this is done recursively for all the files under that directory. If -o offset:size is present, it specifies the offset and size of the piece of the file. Only pages which belong to that piece become primary. This option makes sense only if the file specified in the command is regular, otherwise it is ignored. If the file does not have replicated or archived pages, it is skipped. Pages are not read from the covered filesystem, only those that are present in the cache are affected.

-P {no|yes|invalid}

Controls incore pages - pages cached on the client side. "-P no" disables incore pages,"-P yes" enables incore pages, "-P invalid" invalidates them.

of 180

-l {p|l} Prints list of pages for a specified file. With letter p it is a list of primary pages, with letter l it is a list of replicated and archived pages. For every page in the list prints the page number in the file and the page address in the cache (one line per page). The Integral Volume set must be mounted.

-C cache_root

Cleans up all the pages in the cache. After that the number of present pages in the cache is 0 and cfs_pte/cfs_page files are truncated to zero size. The Integral Volume set must be unmounted and all primary data must be archived.

-e Discards the current event i.e. removes from the delayed queue

the next event scheduled for sending to the migrator (event which marked by the arrow in mmdelay output). This operation is dangerous and intended for use by QStar staff only.

-R Specifies a recursive operation for -t option.

-o offset:size Specifies a part (offset and size) of the regular file for -t option.

-d cache_root {info|chunk|entry|cnode|event|btree|acl|crypto|pte} element_number

Prints dump of the cache file element. The cache is specified by cache_root. The file whose element is to be dumped is specified by one of the following words:

info Prints cfs_info. element_number is 0. chunk Prints chunk of cfs_tree. element_number is the chunk

number. entry Prints directory entry from cfs_tree. element_number

is the entry address. cnode Prints cfs_cnode. element_number is the cnode number. event Prints cfs_event. element_number is the event number. btree Prints cfs_btree. element_number is the btree chunk

number. acl Prints cfs_acl. element_number is the acl number. crypto Prints cfs_crypto, element_number is the crypto

number. pte Prints cfs_pte. element_number is the pte number.

-6 {all|meta} src_cache_root dst_cache_root

Converts cache files from version 5.1 to version 6.0. The 5.1 cache is specified by src_cache_root, the 6.0 cache is specified by dst_cache_root. If the argument is all, all files are converted, if it is meta, all files but cfs_page files are converted.

of 180

MMARC NAME

mmarc - Starts archiving. SYNOPSIS

mmarc [-H host_name] {-l|-e|-a age|-s} [-w] [-j {delayed_job_name| "default"}] [-S cron_like_schedule] {set_name | filename}

DESCRIPTION

The mmarc command tells the mmserver to start archiving or process the delayed events. The options l,e,a are mutually exclusive and inform the mmserver when to stop archiving. The filename is the name of the mount_point where the Integral Volume set is mounted and the set_name is the Integral Volume set name.

OPTIONS


-a age Stop archiving when all delayed events created before the agetime specified are processed.

-l Stop archiving when the number of primary pages in the cache is equal to or less than the low_primary_capacity value.

-e Stop archiving when the delayed queue becomes empty or

all the delayed events are processed. -s Stop archiving. . -w Wait for archiving to stop. Without this option, the

command returns immediately. -j delayed_job_name

Specifies the job name used to identify the job in the delayed job list. If the delayed_job_name is the keyword "default", the actual job name will be generated automatically. Without the –j flag the job will be executed according to the -d flag (without the -d flag, the job will execute immediately).

of 180

-S Schedules archiving by cron time. Cron schedule: Minute Hour Day Month Weekday. For more detailed information about the syntax, please refer to the crontab man pages.

EXAMPLES

In the examples below /mnt is the mount_point.

mmarc -ew /mnt Processes the whole delayed queue and wait until

archiving stops.

mmarc -a 3600 /mnt Processes all events older than one hour.

mmarc –e -S “55 23 * * 1,2,3,4,5” /mnt Processes all events daily at 23:55 from Monday to Friday.

of 180

MMCHMOD NAME

mmchmod - Changes the migration attributes of the cache files. SYNOPSIS

mmchmod [-R] [-p file_pattern] [-t {file|dir}] [-U uid |-u user_name] [-G gid|-g group_name] [-m mode] [-K pin_to_cache_size [:pin_to_cache_offset[:pin_to_cache_ext]]] [-q quota] {+|-} {fkr} {path|[hostname:]setname/path} ...

DESCRIPTION

The mmchmod command changes the migration attributes of the specified files. Attributes are designated by the letters fkr with the +/- prefix.

OPTIONS

+f (Keep full-file) File is in full-file mode. This mode induces a prefetching, see section PREFETCHING below.

-f File is in segmented mode. An access to the file causes a page

containing the referenced bytes to be read into the cache.

+k (Keep in cache). Any page of the file that is now present in the cache, or will be put in the cache, cannot be swapped out of the cache.

-k File pages can be swapped out of the cache.

+r Applied to directories and means that files in that directory

can be under back end retention. Used with HCP migrator only. Always is set recursively. See vlcache command.

-r Invalidates +r attribute.

-U uid

Changes the owner of the files. New owner is specified by uid.

-u user_name Changes the owner of the files. New owner is specified by user_name.

-G gid

Changes the group ID of the files. New group is specified by gid.

-g group_name

Changes the group ID of the files. New group is specified by group_name.

of 180

-m The permissions of the named files or directories are changed

according to mode.

-q quota If not 0, sets a quota for the number of entries in the directory. mmls command prints for a directory the current entry count, the quota if it exists, and the alert if the entry count is greater than or equal to quota.

-t file|dir

-t file flag will change attributes for regular files only. -t dir flag will change attributes for directories only.

-p file_pattern

-p *.exe - changes attributes for all files with .exe at the end of the file name. -p a* - changes attributes for files which started with “a” letter. -p m?x - changes attributes for files max, mox, mix. But files max1, maax still unchanged.

*- matches with any sequence of letters in the name.

? - matches with one letter.

On unix systems file_patterns are treated exactly as with the "find" utility. For additional information run man find, man regexp.

[-K pin_to_cache_size[:pin_to_cache_offset[:pin_to_cache_ext]]]

Specifies a pin-to-cache policy. This option allows to tell what part of the file must be kept in cache. The difference between "K" and "k" options is the size of that part. In case of "k" it is the whole file. In case of "K" the size of that part is pin_to_cache_size and offset of that part from the beginning of the file is pin_to_cache_offset. Each of pin_to_cache_size and pin_to_cache_offset is either the number of bytes, or the number followed by MB or GB, so it is the number of megabytes or gigabytes. pin_to_cache_ext is the list of file name extensions separated by comma: only files with one of those extensions are affected by the pin-to-cache policy.

With -K option, pin_to_cache_size must be present, pin_to_cache_offset and pin_to_cache_ext can be omitted. Missing pin_to_cache_offset is equal to 0, missing pin_to_cache_ext means that any file name is eligible. Thus, "mmchmod -K 100000" keeps in cache the first 100000 bytes of the file, "mmchmod -K 10MB:1GB" keeps in cache 10 megabytes starting with 1 gigabyte from the beginning of the file, "mmchmod -K 2GB:0:c,txt" keeps in cache first 2 gigabytes of the file with extension ".c" or ".txt".

of 180

If the -K option is present in mmchmod command, all other options (except for -R) are not allowed. Both -R and pin_to_cache_ext make sense if the file is a directory. In this case, the pin-to-cache policy applies to the directory and all files in it, and with -R - recursively to all files under the directory. If the file is regular, the pin-to-cache policy applies to that file only. The directory's pin-to-cache policy is stored in the "q_dir_features" stream, archived to the covered filesystem and replicated back from the covered filesystem into the cache. To get rid of the pin-to-cache policy, set pin_to_cache_size to 0. Thus, "mmchmod -K 0" removes the pin-to-cache policy from the file, or from the directory and its files, or (with -R) - from the directory and all files under it. A file can have either "+k" attribute or a pin-to-cache policy. If the pin-to-cache policy applies to a file with "+k" attribute, the pin-to-cache policy is ignored. If the "+k" attribute applies to a file with a pin-to-cache policy, "+k" is ignored.

PREFETCHING

When a user application tries to read bytes from a file, a page containing these bytes is replicated from the covered filesystem into the cache. For a file without "+f" attribute, that is all that the read request does. An attempt to read a file with "+f" attribute induces prefetching (read ahead). Not only the page that contains the requested bytes is replicated into the cache but other pages are replicated as well. If the covered filesystem resides on tapes, all files get "+f" attribute by default. How many pages are prefetched depends on the prefetching mode. There are two prefetching modes: full and partial. The default is the partial prefetching mode. The prefetching mode is set by vlcache command (option -F). Full Prefetching Mode

The whole file is replicated into the cache. The read request that caused prefetching will be satisfied after the requested page is replicated but the prefetching will continue asynchronously and be done after all pages of the file are replicated.

It makes no sense to use the full prefetching mode if the file size is greater than the cache size because the newly replicated pages would swap out previously replicated pages before the application would get a chance to read them. A similar situation can happen if prefetching of the new file would start before the application read the previously prefetched file.

of 180

Partial Prefetching Mode

A piece of the file that contains the requested page is replicated into the cache. The size of that prefetching piece is equal to minimum of 2GB and 1/10 of the cache size. A file is considered to be a sequence of such pieces. The read request that caused prefetching will be satisfied after the requested page is replicated but the prefetching will continue asynchronously and will be done after all pages of the prefetching piece are replicated.

Page Found In Cache

Read of the file with "+f" attribute induces prefetching ONLY if the requested page is not in the cache. If it is, the application's read request is satisfied without reading from the covered filesystem (without involving the migrator) and prefetching of this file does not start.

This is important because it covers the normal case: first read request was satisfied when the pages of the file or the prefetching piece were replicated into the cache and now all subsequent requests to those pages must not induce prefetching again.

Concurrent Read Requests

Currently a prefetching is a single-threaded operation. While a file is being prefetched, no application's read requests which require reading from the covered filesystem can be satisfied. All such read requests wait until the current prefetching is done. As was explained above, this does not happen if the requested page is in the cache. Read request for such a page is satisfied and does not induce prefetching.

No Free Page In Cache

If prefetching requires a free page in the cache but all pages are occupied, the following algorithm applies. If there are archived pages, some of them are declared free. Otherwise, if there are primary pages they will be archived and then some of the archived pages will be declared free. If there are no archived pages, then some of the replicated pages are declared free.

The above algorithm was employed to minimize the probability of the situation when prefetched pages will be declared free again before an application gets a chance to read them.

Prefetching And Archiving

Prefetching and archiving are not mixed. While prefetching is active and there are free pages (or archived pages which can be declared free) archiving does not start.

If prefetching is active but we need to archive to make room for prefetched pages, then prefetching stops and archiving starts. After pages were archived and subsequently declared free, prefetching proceeds.

of 180

Prefetching Period

A prefetching period allows to handle concurrent prefetching and archiving. It is set by vlcache command (option -P) and can be changed on fly by mmparam(8) command (option -P). The prefetching period is a period of time in seconds which starts after the last read request in the cache. If this period is not 0, during it no archiving is made unless there is a need to free pages in the cache. The value of prefetching period must be between 5 and 120 and can be enabled only if the covered filesystem resides on tapes. Setting this period to 0 disables the feature.

KEEP-IN-CACHE

In case of Darwin operating system all user streams (forks) and files with name ".DS_Store" are kept-in-cache and cannot be swapped out of the cache.

NOTES

If an attribute is set for the directory, it is inherited by all of the existing files and new files in this directory (excluding subdirectories).

The current file attributes are printed by the mmls command. The total number of keep in cache and archive never pages are printed by the mmparam command.

-R with this the mmchmod command sets the specified attribute

recursively for all subdirectories. -U -G -m options are devloped for MS Windows and they are present for

compatibility with unix semantics. On unix the same goal is achieved with chmod, chown, chgrp commands.

EXAMPLES

In the examples below /mnt is the mount_point.

mmls /mnt Directory -f-k / Directory -f-k files Directory -f-k scratch

The command mmls shows the current directory attributes.

mmchmod +k /mnt/files Change the “Keep in cache” directory attribute.

mmls /mnt Directory -f-k / Directory -f+k files Directory -f-k scratch

The command mmls shows the new directory attributes.

of 180

MMDELAY NAME

mmdelay - Prints information about delayed events. SYNOPSIS

mmdelay [-H host_name] [-n number] [-t] {set_name|filename} DESCRIPTION

The mmdelay command prints the information about of the delayed events that have not been processed to the covered filesystem. This information contains the total number of delayed events in the delayed event queue and two lines of information per event. The first line contains the time when the event occurred, the event name and the UID and GID of the process (client) who produced the event. The second line contains the attribute address of the file involved in the event and specific information depending on the event type:

CREATE Covered directory inode number, directory entry name,

mode, and flags.

LINK Covered directory inode number, directory entry name, file inode number.

MKDIR Covered directory inode number, directory entry name,

mode.

REMOVE Covered directory inode number, directory entry name.

RENAME Covered old directory inode number, old directory entry name, and covered new directory inode number, new directory entry name.

RMDIR Covered directory inode number, directory entry name.

SETATTR Setattr mask, file inode number, status attributes to

be changed. Setattr mask is the |-separated sequence of the words (UID, GID, MODE, ATIME, MTIME, CTIME, SIZE) and designates which status attributes are to be changed.

SYMLINK Covered directory inode number, directory entry name,

symlink target, and mode.

WRITE File inode number.

FREE FILE File inode number.

of 180

If an inode number is printed as 0, the file that is used in the event has not been created in the covered filesystem.

The filename is the name of the mount_point where the Integral Volume set is mounted and the set_name is the Integral Volume set name.

OPTIONS


-n number

Print the specified number of delayed events. Without this option, the mmdelay command tries to print all of the delayed events.

-t

Events from the time queue are printed. The time queue is a separate queue of events which wait for a specific moment of time to be moved to the delayed event queue.

EXAMPLE

mmdelay /mnt Example of the mmdelay output:

Number of delayed events: 3 08/28/94 18 10:14 CREATE: Client UID=101, Client GID=200 Attr_address=408, Dir_ino=2, Name=xxx Mode=100444 08/28/94 10:16:06 SETATTR: Client UID=101, Client GID=200 Attr_address=408, Mask=MODE, Ino=0, Mode=100444 08/28/94 10:17:52 WRITE: Client UID=101, Client GID=200 Attr_address=408, Ino=0

of 180

MMEXEC NAME

mmexec - Handles cache manager operations. SYNOPSIS

mmexec -R cache_root [-p {max_number_of_pages | xxMB | xxGB}] [-s page_size] [-m mount_point] [-y crypto_parameters}] [-l {all|all,short|no|list_of_log_options}] [-nr] set_name

mmexec -K {man|mig set_name}

mmexec -L {all|all,short|no|list_of_log_options} set_name

mmexec -I {all||no|trace|rdwr} set_name mmexec -U set_name mmexec -A mmexec set_name

DESCRIPTION The mmexec command allows starting the cache manager, setting log options, stopping cache manager and migrator, force umount and performing Unix-like commands with files in cache. The Integral Volume set is specified by set_name argument. The first form of the command starts the cache manager. Options -c, -p, -s, -m, -y, -l, -n, and -r are valid only with -R option. The second form allows stopping the cache manager or migrator. The third form allows specifying the log options. The fourth form allows to specifying the FSI log options. The fifth form forces umount of the Integral Volume set. The sixth form umount of all the Integral Volume sets. The seventh form allows to run Unix-like commands interactively on a mounted Integral Volume set. OPTIONS

-R cache_root Starts the cache manager and specifies the root directory of the cache. The following options can be used with -R:

-p {max_number_of_pages | xxMB | xxGB}

Specifies the max number of pages in the cache which are represented either by max_number_of_pages or by number of megabytes (xxMB, xx is the number) or by number of gigabytes (xxGB, xx is the number). If the clean cache is used (no MCFS files in the cache or -n is specified), this option must be present.

of 180

-s page_size

Specifies page size in kilobytes. The default is 64KB.

-m mount_point Specifies mount point. In this case, cache manager mounts the Integral Volume set (as it happens when mountiv command is issued). If this option is not present, the only way to talk to the Integral Volume set would be the seventh form of mmexec command. On Windows use Integral Volume set name as mount point.

-y crypto_parameters

Specifies cryptographic parameters: digest and encryption. Digest is specified by "digest[=SHA1|=SHA256|=SHA512]", the default is SHA1. Encryption is specified by "encrypt[=AES128|=AES192|=AES256|=AES512]", the default is AES256. If both digest and encryption are present, they are separated by a comma.

-l {all|no|list_of_log_options}

Specifies log options for cache manager (the same syntax for options as in -L, see below). This option works only in the special case of the cache manager running not as a daemon and should not be used.

-n Cleans cache. MCFS files are created from scratch.

-r Read-only mount.

-K {man|mig} set_name

Stops cache manager (man) or migrator (mig).

-L {all|no|all,short|list_of_log_options} Specifies log options for the cache manager. The Integral Volume set must be mounted or the cache manager must be started by mmexec -R command. The log options are either "all" or "no" or a comma separated list of other words:

all logs everything no stops logging client logs client events covered logs covered events arch logs archiving decisions sync logs sync operations pte logs page operations scalc logs space calculation readdir logs readdir operations consist logs consistency checks rlookup logs recent lookup operations rreaddir logs recent readdir operations rpte logs recent pte operations wait logs waits incore logs incore operations prefetch logs prefetch operations sec logs security (crypto) operations short saves last 20 MB of log in log_file.short (can

be listed with all)

of 180

-I {all|no|list_of_log_options} Specifies log options for the kernel or FSI. The Integral Volume set must be mounted or cache manager must be started by mmexec -R command. The log options are either "all" or "no" or a comma separated list of other words:

all logs everything no stops logging trace logs all events rdwr logs rdwr events

-U set_name Forces umount of the Integral Volume set.

-A Forces umount of all the Integral Volume sets.

of 180

MMLS NAME

mmls - Lists information about the cache files. SYNOPSIS

mmls [-RpsocrK@][ filename ...] mmls [-RpsocrK@] [[hostname:]setname/filename ...]

DESCRIPTION

The mmls command prints the cache information of the files specified by the filename arguments. If filename is not specified the current directory is used.

The mmls command without options prints:

Column 1: Regular, Directory, Fifo, or Symlink.

Column 2: Migration status.

Column 3: Migration attributes fk with +/- prefix.

Column 4: Filename in the local directory.

The migration status of the file is a combination of the status of its pages. A page that is present in the cache can be primary, replicated, or archived:

Primary

The page has been modified or added to the file.

Replicated The page was copied from the covered filesystem and has not been modified.

Archived

The page has been written from the cache to the covered filesystem.

If a file has a zeroth size and has not been created in the covered filesystem, its migration status is "Non-covered". By default, a file is in segmented mode.

The file is in full-file mode, if it has +f attribute. In segmented mode, an access to the file causes a page containing the referenced bytes to be read into the cache. In full-file mode, an access to the file causes the whole file to be read into the cache. Migration attributes fk can be set by the mmchmod command.

of 180

If the filename is a directory, the mmls command does not print column 2 but lists the contents of the directory. Additional information is printed depending on options.

OPTIONS

-R Recursively lists all directories and subdirectories encountered.

-s Prints the following:

Cnode number This number plays a role of the inode number for the cache file.

Symlink address If the file is a symlink, Symlink address of the target filename is displayed.

Entry information If the file is a directory. Entry count, entry quota (if was set), alert if the entry count is greater than or equal to quota.

Number of present and primary pages

For regular or fifo file. Status

Inode number, mode, UID, GID, link count and size of the covered file.

-p Prints only files which have primary pages in cache. In

this mode no status is reported but the full pathname (relative to filesystem root) is printed.

-o Prints online/offline status of the file. The offline

status means that file data is not present in the cache and the media with file data was exported from the library.

-c Prints crypto information related to the file: digest,

encryption type, object id.

-r Prints information about file retention in the covered file system: no retention, no deletion, or time when the retention period expires.

-K Prints pin-to-cache information: pin size and pin offset

in bytes. If this is a directory, prints the list of file extentions affected by the pin policy. If this is a regular file, prints the number of pinned pages.

-@ Processes file streams if any.

of 180

NOTES

When the mmls command is applied to a directory and the directory contents is not in the cache, the directory contents is read. In this respect, mmls behaves like Unix "ls".

EXAMPLES

In the example below /mnt is the mount_point.

mmls /mnt The command prints the following:

Directory -f-k / Directory -f-k files Directory -f-k scratch

of 180

MMPARAM NAME

mmparam - Prints information and set parameters for the cache. SYNOPSIS

mmparam [-H host_name] {set_name | filename}

mmparam [-H host_name] [-l {low_primary_capacity | xxMB | xxGB | xx%}] [-h {high_primary_capacity | xxMB | xxGB | xx%}] [-P{prefetch_priority_period|0}] [-g {rdonly_grace_period|0}] [-R {retention_period|0}] [-w {0|1}] [-x {0|1}] [-F {0|1}] [-B {dir|set|straight}] [-A {0|1}] [-O {owner_access_period|0}] {set_name | filename}

DESCRIPTION

The mmparam command in the first form prints the information of the cache. In the second form, it sets the cache parameters. The cache information are the following: - Cache root directory name - MCFS mount point name - Maximum number of pages - Low primary capacity - High primary capacity - Page size - Total number of present pages - Total number of primary pages - Total number of replicated pages - Total number of archived pages - Total number of keep in cache pages - Total number of never archive pages - Number of delayed events - Number of files in the cache - Read/write access: read-only or read/write - Directory copying (on mount or on access) - Mount state: mounted or unmounted - Error condition: no error, covered error, no space in cache. - Migrator type. - Migrator specific information.

The migrator specific information depends on the migrator type and is as follows:

of 180

Standard migrator: Covered root directory name.

The filename is the name of the mount_point where the Integral Volume set is mounted and the set_name is the Integral Volume set name.

OPTIONS


-l low_primary_capacity Number of pages used to control the stopping of archiving. When archiving starts because of the number of primary pages in the cache becomes equal to the high_primary_capacity value, it proceeds until the number of primary pages in the cache is equal to or less than the low_primary_capacity value. The maximum value is the maximum number of pages in the cache minus 1. The default is 0. The value may also be specified in MB, GB and %(percentage) as follows: -l xxMB -l xxGB -l xx% where "xx" is the numeric value.

-h high_primary_capacity

Number of pages used to control the start of archiving. Archiving starts when the number of primary pages in the cache becomes equal to the high_primary_capacity value. The default and the maximum value are the maximum number of pages in the cache. The value may also be specified in MB, GB and %(percentage) as follows: -h xxMB -h xxGB -h xx% where "xx" is the numeric value.

-P prefetch_priority_period

Period of time in seconds which starts after the last read request in the cache. If this period is not 0, during it no archiving is made unless there is a need to free pages in the cache. The value of prefetch_priority _period must be between 5 and 120 and can be enabled only if the covered filesystem resides on tapes. Setting this period to 0 disables the feature.

-PgRwxFBAO

This options allow to modify soft features set by vlcache command. The new value will be in effect for the current mount session only and will not be stored in the "q_set_features" stream. Next time the set is mounted the value of the feature will be defined by the "q_set_features" stream or vlcache command option. See vlcache command.

of 180

EXAMPLES

mmparam /mnt The command prints the following:

Cache root: /cache/oleg Mount point: /mnt/oleg Max number of pages: 8192 512 MB Low primary capacity: 0 pages High primary capacity: 6553 pages 409 MB Prefetch priority period: No Prefetching mode: Partial Page size: 64 Kbytes Present pages: 1156 72 MB Primary pages: 0 Replicated pages: 1156 72 MB Archived pages: 0 Keep in cache: 0 Archived since mount: Replicated since mount: Files in cache: 4 Number of delayed events: 0 Read/write access: Read-write Rdonly grace period: No Retention period: No Worm FS: No No Worm rename: No Digest: No Encryption: No Back end retention: No Atime update: No Error condition: No Stop on covered error: Yes Archiving: Not started Migrator: tdo Medium drive type: DISK Extent size: 4.0 MB Virtual drives: 4 (1 for writting) Write pool count: 4 Writing to partition: jb:3a Free space on current partition: 35 MB Mirroring state: In Sync

mmparam -h 2800 /mnt

The command sets the high primary capacity to 2800 pages.

of 180

MMPING NAME

mmping – Checks to see if the mmserver is running. SYNOPSIS

mmping [-H host_name] DESCRIPTION

The mmping command checks to see if the mmserver is running. OPTIONS


EXAMPLES

mmping mmping: MM server thread is running.

of 180

MMPURGE NAME

mmpurge - Removes pages from cache. SYNOPSIS

mmpurge [-H host_name] set_name filename mmpurge {path|[hostname:]setname/path} ...

DESCRIPTION

The mmpurge command removes from the cache all pages belonging to the specified files. The files are specified by filename arguments. A file must not have primary or keep-in-cache pages and must not be active (open).

OPTIONS

-H host_name Specifies the name of the host where the Integral Volume set resides. Without this option, the local host is used.

EXAMPLES

mmpurge test /mnt/readme.txt Removes all pages belonging to the readme.txt file from the cache.

of 180

MMRESUME NAME

mmresume - Clear cache error. SYNOPSIS

mmresume [-H host_name] [-n] {set_name | filename} DESCRIPTION

The mmresume command handles the state of error condition in MCFS. The filename is the name of the mount_point where the Integral Volume set is mounted and the set_name is the Integral Volume set name. If processing of the event in the covered filesystem returns an error, the migration is stopped. It means that the delayed event queue is not being processed and all of the client requests are cancelled with the ENOSYS error (Function not implemented). If the source of the error can be eliminated, the situation is recoverable i.e. archiving can continue by using the mmresume command.

OPTIONS


-n This flag instructs the migrator to add a new piece of

media to the set before resuming the write. Only the multivolume migrator (SDF, UDF Spanning, TDO, LTFS Spanning) migrator currently supports this flag. Without this option, the migrator attempts to restart writing at the same position where the error occurred. This flag should only be used if the migrator gets a medium error (rather than device error) and cannot continue on the current media surface.

NOTES Error condition is cleared.

EXAMPLES

mmresume /mnt

of 180

MMSTREAM NAME

mmstream - Print file or directory stream information. SYNOPSIS

mmstream [-H host_name] {-s | -d | -p | -w |-c} {path | set_name[/path]} DESCRIPTION

The mmstream command prints the file stream information of the specified filePath in XML format. The stream of the file is an additional information associated with the file or directory. Additional information is printed depending on options.

Not all streams are available for files in the Integral Volume sets. For example, the cryptographic stream is available only if the Integral Volume set is configured to support cryptographic functionality.

Windows and Posix ACL most likely will not be present at the same time.

OPTIONS


-s Prints q_set_features stream. The last argument must refer to the root directory.

-d Prints q_dir_features stream.

-p Print file Posix ACL stream information

-w Print file Windows ACL stream information

-c Print file cryptographic stream information. EXAMPLES

In the examples below it is assumed that Integral Volume set is mounted to the /mnt/sdfe mount point.

mmstream -s /mnt/sdfe

of 180

MMSUBTREE NAME

mmsubtree - Removes and/or adds a subtree in cache. SYNOPSIS

mmsubtree -a path/new_subdir_name mmsubtree -a [hostname:]setname/path/new_subdir_name mmsubtree -r {tree|data|kill|kill_data} path mmsubtree -r {tree|data|kill|kill_data} [hostname:]setname/path mmsubtree -c {tree|data} [-v] path mmsubtree -c {tree|data} [-v] [hostname:]setname/path

DESCRIPTION

The mmsubtree command works with directory trees in the cache. The command is useful in situations when the structure of the covered filesystem tree is changed beyond the MCFS (Magnetic Cache File System) and this change must be reflected in the cache. The prior method of resynchronizing the covered filesystem with the MCFS required the cache to be completely rebuilt. With the mmsubtree command, a specific directory hierarchy in the cache can now be rebuilt exclusively.

OPTIONS

-a Add new_subdir_name subtree to the cache. The parent directory (to add new_subdir_name to) is specified by the path argument. The new_subdir_name must already exist in the covered filesystem and must not exist in the cache.

-r {tree|data|kill|kill_data}

Remove a subtree from the cache. The root directory of the subtree is specified by the path argument and must exist in the cache. Specifying the data option means that only data pages will be removed from the cache. Specifying the tree option means that both directory structure and data pages will be removed from the cache. To remove data pages, all files in the subtree must not be active (open). The kill option removes a subtree without archiving. The kill_data option removes data only. All delayed events related to that subtree or data are removed. The kill options work even if the file has primary data or error condition is set.

of 180

-c {tree|data} Copy a subtree into the cache. The root directory of the subtree is specified by the path argument and must exist in the cache. Specifying the tree option means that only directory structure will be copied into the cache. Specifying the data option means that both directory structure and data pages will be copied into the cache.

-v Verbose. Works with -c option and prints a pathname of the file being copied.

EXAMPLES mmsubtree –r /images/dir10

Removes the hierarchy below directory dir10 from the cache, resynchronizing on next access of the directory.

of 180

MOUNTIV NAME

mountiv - Mounts an Integral Volume set. SYNOPSIS

mountiv [-H host_name] [-n] [-I] [-r] [-f] [-a] [-i] [-R] [-c cache_root [-t {[mmdd]HHMM|[cc]yymmddHHMM}]] set_name [mount_point]

DESCRIPTION

The mountiv command mounts the Integral Volume set to the mount point specified by the mount_point argument. The Integral Volume set name is specified by the set_name argument. An Integral Volume set is a media set with a cache.

All mount information is obtained from the Volume Librarian database. Mounting of the Integral Volume set means mounting of the target Integral Volume set (specified in the Integral Volume set database) with the cache. The migrator that represents the "covered filesystem" depends on the set type.

OPTIONS


-n Mounts with the clean cache. It is necessary to use this

option on the first mountiv command for the Integral Volume set but not used with all subsequent mountiv commands unless rebuilding the cache is desired.

-I Recreates the filesystem databases before mounting.

This flag is equivalent to setting “-I” Integral Volume set option by vleditset command. This option is disabled (ignored) for CD/UDF and LTFS Automount Integral Volume set types.

Without options the filesystem databases are created automatically only if they do not exist.

-r Mounts the Integral Volume set read only.

-f Mounts the Integral Volume set even if there is a

possible inconsistency between cache, filesystem databases and media. Use this flag with caution, the result may be undesirable.

of 180

-c cache_root Specifies an alternative cache root for "dated mount" (see below). The directory must exist and be different from regular cache root for the Integral Volume set.

-t {[mmdd]HHMM|[cc]yymmddHHMM}

Specifies the date and time for "dated mount". The Integral Volume set will be mounted (read-only) reflecting file system state on the specified date/time. Cache root must also be specified for dated mount. Only the multivolume migrator (SDF, UDF Spanning, TDO, LTFS Spanning) migrator currently supports this flag.

mm is the month dd is the day of month HH is the hour (24 hour system) MM is the minute cc is the century yy is the last 2 digits of the year

The month, day, year, and century may be omitted, in this case, the current values are supplied as defaults.

NOTES

Filesystem databases that belong to a different Integral Volume set may not be overwritten by mountiv command. Mountiv may fail if the filesystem specific databases exist in a cache directory but belong to a different Integral volume set. To force removal and recreation of filesystem databases vlrestore_fsdb command may be used.

EXAMPLES

mountiv -n alpha /mnt Mount the Integral Volume set "alpha" on the /mnt mount_point and also rebuild the cache.

of 180

QCENTERA NAME qcentera - Manages a Centera connection. SYNOPSIS

qcentera -c {host=host_name|lib=lib_path|=} qcentera -c pool[_centera_index]=pool_address qcentera -c dir[_centera_index]=dir_path qcentera -c ret[_centera_index]=ret_string

qcentera –d {start | stop | ping} (not available on Windows) qcentera [-i centera_index] -s {on|off|ping}

qcentera [-i storage_index] -m store {volume_id|+} qcentera [-i storage_index] -m restore period{h|d|m|y} volume_id qcentera [-i storage_index] -m print volume_id

qcentera [-i centera_index] [-r|-R] volume_id

qcentera –C

qcentera [-i centera_index] –L {0|1}

DESCRIPTION

The qcentera command allows setting the Centera configuration, to start/stop/ping the Centera daemon, to handle Centera volume maps, and to switch debug log facilities. Up to 30 Centera storage systems are supported. An optional argument -i centera_index specifies which Centera storage system (1-30) is the target of the command. The default centera_index is 1. The command depends on the Centera SDK libraries so the platform dependent environment variable must be set to run the qcentera command. The variable and its values are listed below (<centera_root> is the directory where Centera SDK is installed):

Solaris (32 bit) LD_LIBRARY_PATH <centera_root>/lib/32 Solaris (64 bit) LD_LIBRARY_PATH <centera_root>/lib/64

of 180

Linux LD_LIBRARY_PATH <centera_root>/lib/{32 or 64} Aix LIBPATH <centera_root>/lib/{32 or 64} The Centera configuration (see -c option below) must be set before any other operation with the Centera is made. The Centera daemon links to the Centera SDK libaries at run-time. The path to the Centera SDK lib directory must be configured by qcentera -c lib=lib_path where lib_path is

platform dependent: Windows <centera_root>/lib Solaris <centera_root>/lib Linux <centera_root>/lib/{32 or 64} Aix <centera_root>/lib/{32 or 64}

The Centera daemon is the program responsible for communication with the Centera storage system. The latter is identified by an IP address, or a list of IP addresses. This address/list is the value (pool_address) assigned to pool in the Centera configuration (pool=pool_address). Both sumulated disks and tapes are implemented for the Centera. Throughout this explanation, the word "volume" is used for both of them. Every Centera volume is named by its volume_id. The volume_id is also the name of the subdirectory under the root directory of the Centera volumes. The root directory pathname is the value (dir_path) assigned to dir in the Centera configuration (dir=dir_path). The retention period is the time the volume can reside on the Centera storage system before the system allows removing it. By default the retention period is equal to 0 which indicates that the disk/tape can be removed at any time. To set an arbitrary retention period, ret_string has to be assigned to ret in the Centera configuration (ret=ret_string). The general form for ret_string is either "0" (set the retention period to 0) or YyMmDdHh, where Y is the number of years, M is the number of months, D is the number of days, H is the number of hours. A month is equal to 30 days, a year - to 365 days. Any part can be omitted. Thus, ret=25d3h sets the retention period to 25 days and 3 hours.

of 180

The Centera daemon and the QStar servers exchanging data with the Centera can run on different hosts. In this case, the name of the Centera daemon host is the value (host_name)assigned to host in the Centera configuration (host=host_name). A subdirectory volume_id holds the file mapping disk blocks to the Centera clips (map) and buffer files (0, 1, etc) used to accumulate write data before they will be written into a new clip on the Centera. The map is the essential part of the volume identification; it holds the content address (clip_id) of all the clips comprising the volume. The map should be periodically (e.g. on daily basis) stored on the Centera (see -m store below). The map can be recovered from the Centera (see -m restore) in the case of a disaster.

NOTE

Suppose, the name for the qcentera command inserted by the System Administrator is simjb_shelf43 the command will automatically append the “_A” suffix during the import operation to each media and the volume_id will become simjb_shelf43_A. Any command that requires volume_id will only work with the real name assigned to the Centera by the volume. Using jbsim –P device_name as the command it is possible to display only the media online. Using jbsim –L device_name as the command is possible to display also the media that is offline. If the media is offline it will be displayed as OFF-simjb_shelf43_A, but also it is displayed in such a way the System Administrator must use simjb_shelf43_A as the volume_id on theqcentera command

OPTIONS

-c= Prints the current configuration.

-c lib=lib_path Sets the path to the Centera SDK lib directory.

-c host=host_name

Sets the name of the host where the Centera daemon is to run. The default is the local host.

-c pool[_centera_index]=pool_address

Sets the Centera pool IP address(es). The pool_address is a comma-separated (without spaces) string of IP addresses or DNS names of available Centera Access Nodes. The default centera_index is 1.

In the pool argument the Pool Entry Authorization (PEA) information can also be specified. The PEA file is used by a Centera administrator for application authentication (See Centera Programmer's Guide - Application Authentication and Authorization). By default when QStar Software opens a pool it uses an anonymous profile.

of 180

To use a PEA file instead of the anonymous profile the Administrator will need to specify the pool connection string. Example of pool connection sting from the Centera Programmer's guide: “10.2.3.4,10.6.7.8?c:\centera\rwe.pea” Note: The pool connection string “?c:\centera\rwe.pea” specifies a PEA file. Example - to specify the PEA file in the qcentera command, enter: qcentera –c pool=10.2.3.4,10.6.7.8?/centera/rwe.pea This value will be passed to the pool, open the SDK function and the PEA file will be used during authentication.

-c dir[_centera_index]=dir_path

Sets the root directory of the Centera volumes on the Centera daemon host. The default centera_index is 1.

-c ret[_centera_index]=ret_string Sets the retention period. The default centera_index is 1.

Several -c options can be used in the same command. If the string following “=” is “-“ it means that no value is assigned. The configuration for pool, dir, lib, and ret must be specified on the host where the daemon is running.

-d {start|stop|ping}

Handles the Centera daemon. -d start starts the daemon. -d stop stops the daemon. -d ping checks if the daemon is running.

-s {on|off|ping} Handles Centera storage systems. -s on sets the storage on. -s off sets the storage off. -s ping checks if the storage is on.

-m store volume_id Stores a volume map on the Centera. The Centera volume is specified by volume_id. The Centera daemon must be running. The ClipId of the clip where the map has been stored is printed in the QStar Syslog.

-m store +

Stores all volume maps on the Centera.

of 180

-m restore period{h|d|m|y} volume_id

Restores the volume map from the Centera. Finds the last clip where the volume map was stored and restores the map from that clip. Then it finds all clips from that volume which were stored after that map clip and use them to populated the map. The period specifies starting time for which the clips are queried. It is the number of hours (h) or days (d) or months (m) or years (y) back from the current moment. For map restoration, the Centera capability "clip-enumeration" must be true. The Centera daemon must be running and the volume must not be in use (e.g. mounted).

-m print volume_id

Prints the map contents. This operation does not need the daemon and is always performed on the local host.

-R volume_id

Prints the retention information (creation date and retention period) for the Centera volume specified by volume_id.

The [-i centera_index] option is mandatory.

-r volume_id

Removes the Centera volume specified by volume_id. The Centera daemon must be running. The volume cannot be in use (e.g. mounted). Clips comprising a Centera volume are written with the retention period 0, which means that they can be removed at any time. This operation removes the clips belonging to the volume; the blobs will be removed by the Centera garbage collection. Make sure that the Centera capability "delete" is true and "garbage-collection" and "data-shredding" are enabled.

The [-i centera_index] option is mandatory.

-C Prints the total number of megabytes written to the Centera

and the number of licensed megabytes.

-L {0|1} Turns the Centera daemon debug log on (1) or off (0). The daemon must be running.

EXAMPLES

qcentera -c pool=199.111.222.333 -c dir=C:\Centera (Windows) qcentera -c pool=199.111.222.333 -c dir=/export/home/centera (UNIX)

Sets the Centera configuration.

qcentera -c= Prints the Centera configuration.

qcentera -d start (UNIX)

Starts the Centera daemon.

qcentera –i 2 –r simjb_shelf43_A Remove the centera volume named simjb_shelf43_A.

of 180

UDFDF NAME

udfdf - Reports number of blocks and files in UDF set. SYNOPSIS

udfdf [-H host_name][-f][{-t|-a automount_sequence_number|-ddir_name}] {filename|setname}

DESCRIPTION

The udfdf command prints the total number of kbytes, the number of used kbytes, the number of available kbytes, the percentage of used kbytes, and the total number of files in the mounted UDF set. The filename is a mount point or any file under it. The command is primarily dedicated to auto-mount, where every volume is an independent file system. Without options, prints a line for every volume in auto-mount. Prints "deleted" or "not accessed yet", if the volume in question has been deleted and has not been accessed.

OPTIONS


-f Forces an access of every volume that has not been

accessed yet.

-t Prints a single line summing up values for all volumes.

-a sequence_number Prints the values for a specified volume.

-d dir_name

Prints the values for a volume whose root directory is dir_name.

EXAMPLES

udfdf -f /mnt

of 180

UDFFILE NAME udffile - Lists files on volume and volumes for file. SYNOPSIS udffile {-f filename|-v volume_span_number} cache_root DESCRIPTION

The udffile command works for spanning volumes only. If the file is specified (-f option), the command lists all volumes the file spans and file size on every volume. If the volume is specified (-v option), the command lists files which reside on the volume.

The command works with span DB and does not access the volumes themselves. The cache_root argument specifies the directory where span DB resides.

OPTIONS -f filename Specify the file pathname relative to the root. -v volume_span_number Specify the volume by its span number.

of 180

UMOUNT NAME

umount - Unmounts a Volume set or a Integral Volume set. SYNOPSIS

umount { filesystem_name | mount_point } DESCRIPTION

The mounted cache is assigned a name, which is the last component of the mcfs_mount_point filename. This name can be used in the umount command along with the mount point name.

Umount unmounts cache. The filesystem is specified either by the mount point name or by the filesystem name assigned during the mount operation.

EXAMPLES

umount /mnt Unmounts the set mounted in /mnt mount_point.

of 180

UMOUNTIV NAME

umountiv - Unmounts an Integral Volume set. SYNOPSIS

umountiv [-H host_name] [-f] {set_name|mount_point} DESCRIPTION

The umountiv command finds the mount_point for the Integral Volume set specified by the set_name argument. It then detaches the mount_point from the Integral Volume set. If the mount_point and Integral Volume set are located on the same host, umountiv closes the Integral Volume set making the Integral Volume set unavailable to all clients.

OPTIONS


-f Forced umount. Unmount the set, even if there are open

files. Not supported on Solaris and AIX. EXAMPLES

umountiv alpha Unmount the Integral Volume set "alpha" on the local host.

of 180

VLADDTOSET NAME

vladdtoset - Adds media to the Integral Volume set. SYNOPSIS

vladdtoset [-H host_name] [-n number_of_media] set_name

vladdtoset [-H host_name] [set_type_specific_options] [-o] set_name device_name shelf_number

vladdtoset [-H host_name] set_name device_name

shelf_number:shelf_number

vladdtoset [-H host_name] set_name QSSD_specific_args vladdtoset [-H host_name] -f offline set_name [A=]A_sequence_number

vladdtoset [-H host_name] -f offline set_name in_set_number

vladdtoset [-H host_name] -f RECOVER_OFFLINE set_name 1 vladdtoset [-H host_name] -f del_set_name in_set_number

set_type set_type_specific_options: sdf tdo [-c [sequence_number.]copy_number] udf [-A identifier][-B identifier] uvfs [-X directory][-Y directory]

[-A identifier][-B identifier] ltfs [-D volume_name]

set_type QSSD_specific_args: cluster node_set_name gfs ssd_name hcp ssd_name [partition_name] osm ssd_name partition_number ampl ssd_name partition_name cs ssd_name vault_name rpl replica_set_name

DESCRIPTION

The vladdtoset command adds media to Integral Volume sets. The Integral Volume set is specified by the set_name argument. The first form of the command initializes and adds media to the Integral Volume set.

of 180

The second form of the command includes in the Integral Volume set all the media in the device specified by the device_name argument which are compatible with the set specified by the set_name argument. The shelf_number argument specifies any shelf containing such a medium. The third form of the command includes in the Integral Volume set all the media in the device specified by the device_name argument which are compatible with the Integral Volume set specified by the set_name argument and occupy the shelves in the range specified by the shelf_number:shelf_number argument. The fourth form of the command adds QSSD and its partition to the Integral Volume set. The fifth form of the command adds an offline medium to the Integral Volume set specified by the set_name. Offline is the offline location. A_sequence_number specifies the side A sequence_number of the offline medium. By default, the medium is considered double-sided, otherwise the form A=A_sequence_number must be used. The sixth form of the command removes an offline medium from the Integral Volume set specified by the set_name. The in_set_number specifies the position of offline medium within the Integral Volume set. If the medium specified in the second or third form of the command is erased (blank) it can be added to the Integral Volume set if the medium type matches the use-media parameter of the Integral Volume set. Otherwise, the compatibility is Integral Volume set specific.

If the medium contains an Integral Volume set identification, the second or third form of the command does not expand the Integral Volume set. It merely includes media in the database for the specified Integral Volume set. If a medium is already included in the Integral Volume set command does nothing. Such operation is usually required after the device has been refreshed.

OPTIONS


-n number_of_media

Specifies the number of additional media which will be initialized and added to the Integral Volume set. The total number of media in the Integral Volume set must be less than or equal to the Integral Volume set quota.

of 180

-f offline Specifies the offline location for a medium offline. Specifies the offline location for a medium offline. The offline location text is an arbitrary text specifying offline location of the medium. If the offline is equal to string RECOVER_OFFLINE the command will attempt to recover offline information saved during set deletion. The volume sequence number in this case shall be 1.

-o This option prevents search for compatible medium in all libraries. It may be useful when adding medium to the Integral Volume set from large library to exclude search time.

SET TYPE SPECIFIC OPTIONS

In the second form of command the extra options can be specified depending on the Integral Volume set type:

sdf No extra options. tdo The specific options are:

-c [sequence_number.]copy_number Used for TDO mirror sets only and allows to assign copy and sequence number distinct foem default (current + 2)

udf The specific options are:

-A identifier

Specifies the logical volume identifier assigned to the surface A in the case of a single-volume or automount Integral Volume set, if the surface is blank/erased and will be initialized. If the option is not specified for the surface, the logical volume identifier is generated by the system.

-B identifier

Specifies the logical volume identifier assigned to the surface B in the case of an automount Integral Volume set, if the surface is blank/erased and will be initialized. If the option is not specified for the surface, the logical volume identifier is generated by the system.

of 180

uvfs The specific options are:

-A identifier Specifies the logical volume identifier assigned to the surface A in the case of an automount Integral Volume set. If the option is not specified for the surface, the logical volume identifier is generated by the system.

-B identifier

Specifies the logical volume identifier assigned to the surface B in the case of an automount Integral Volume set. If the option is not specified for the surface, the logical volume identifier is generated by the system.

-X directory

Specifies the directory that will be assigned as surface A of the virtual media.

-Y directory

Specifies the directory that will be assigned as surface B of the virtual media.

gfs No specific options. The fourth form of the command is

used. hcp No specific options. The fourth form of the command is

used. ltfs The specific options are:

-D volume_name

Specifies the volume name which will be written on the ltfs tape at the time of initialization for automount or single-volume Integral Volume set. This name will also be the root directory name of this volume in the mounted automount Integral Volume set. In case of the spanning set the volume name written on the tape is "span-I-N-name" where "name" is the name from -D option or "span-I-N" if -D option is not used (I is 16 hexadecimal digits representing set Id and N is the spanning volume number).

EXAMPLES

vladdtoset -n 3 alpha Initializes three media and adds them to the Integral Volume set "alpha".

vladdtoset beta jb 4

Adds to the Integral Volume set "beta" all media (one of them is on the shelf 4) which are compatible with the Integral Volume set "beta".

of 180

VLCACHE NAME

vlcache - Creates or edits cache information for an Integral Volume set. SYNOPSIS

vlcache [-H host_name][-c cache_root] [-e] [-s page_size]

[-D0rn] [-p {max_number_of_pages|xxMB|xxGB}] [-l {low_primary_capacity|xxMB|xxGB|xx%}] [-h {high_primary_capacity|xxMB|xxGB|xx%}] [-P [h=]{prefetch_priority_period|0}] [-g [h=]{rdonly_grace_period|0}] [-R [h=]{retention_period|0}] [-w [h=]{0|1}] [-x [h=]{0|1}] [-S [h=]{SHA1 | SHA256 | SHA512 |0}] [-E [h=]{AES128 | AES192 | AES256 |0}] [-F [h=]{0|1}] [-B [h=]{dir|set|straight}] [-A [h=]{0|1}] [-O [h=]{owner_access_period|0}] set_name

DESCRIPTION

The vlcache command creates or edits the cache information used by mountiv to mount an Integral Volume set. The Integral Volume set is specified by the set_name argument.

SET FEATURES

Some of the options represent "set features" and on mount are stored in the root directory stream "q_set_features". These features are:

grace period retention period worm-fs no-worm-rename digest type encryption type prefetching mode prefetch priority period back end retention

access time update ability owner access period

The q_set_features stream is created on the first mount if the Integral Volume set has features specified by the vlcache command. On the next mount the features will be taken from the stream unless they are overridden by new values from vlcache.

of 180

A feature can be soft or hard. Whether a feature is hard or soft is specified in vlcache command: prefix h= means hard feature, by default it is soft. A new value of the soft feature in vlcache command will be in effect after the next mount. It overrides the value in the q_set_features stream and the stream will be updated on mount. A new value of the soft feature can also be overridden by mmparam command when the Integral Volume set is mounted, but that new value will be in effect during the mount session only and will not change the q_set_features stream.

A hard feature cannot be modified neither by vlcache command nor by mmparam command. The soft/hard attribute of the feature is also stored in the q_set_features stream.

RETENTION

The retention period set by -R option affects the permission to delete the file in the cache. If the back end filesystem (and the relevant migrator) supports retention, that period can be passed to the migrator and assigned to the file in the back end filesystem. The retention in the back end filesystem is called back end retention. Currently it can be done in HCP and GFS-NetApp only.

Setting of the back end retention is made by -B option of vlcache command and is based on the grace and retention periods. The retention period gives the value of retention that will be set for the file on the back end filesystem. An expiration of the grace period for a particular file gives the moment when the retention for that file can be set.

The back end retention is not set at the time when the file is created on the back end filesystem. The reason:

we should be able to remove the file in case of: - rename (if the back end filesystem prohibits rename, e.g. HCP) - repeat of event (crash or something like that) - overwrite of the file.

As a result, the back end retention is set when the grace period expires (the file will not be modified anymore) and the last event for the file is archived and synced (no more repeat of event).

There are three cases of the back end retention in -B option: directory-based, set-based and straight.

Directory-based

Assigning a retention to a file depends on the migration attribute "+r" which is set by mmchmod command. The attribute applies to a directory. If the directory has "+r" attribute, all files in the file tree under that directory get the back end retention. Without that attribute, the back end retention is not assigned to the files. This case requires the grace and retention periods.

of 180

Set-based

All files in Integral Volume the set get the back end retention. This case requires the grace and retention periods.

Straight

In this case, it is supposed that the retention is set straight in the back end filesystem (bypassing QStar services), but the possibility to delete a file must be checked. Since MCFS does not assign a retention in this case, the grace and retention periods are not required. This case tells MCFS to check the back end retention. Every time when a file is to be removed, renamed, or overwritten MCFS calls the migrator to check whether the retention set in the back end filesystem allows file deletion. Without –B option, MCFS does not check the back end retention and if the retention was set bypassing QStar services, archiving of file removal would result in error condition.

After the back end retention time is reached, the only operation allowed for a file is its removal.

BACK END RETENTION ON HCP

In the set-based and directory-based cases the back end retention is assigned by MCFS (Magnetic Cache File System), so when the user wants to remove the file, MCFS can check the back end retention without calling the migrator. This is true until the cache is rebuilt. When the cache is populated from HCP, whether or not the back end retention is passed to MCFS depends on the type of HCP namespace:

Default namespace

The back end retention is not read from HCP and not passed to MCFS (because it requires extra calls to HCP which affects performance). Thereafter, if the user decides to remove a file that was replicated, MCFS calls the migrator to check the back end retention.

Tenants

The back end retention is read from HCP and passed to MCFS so there will be no need to call the migrator to check the back end retention.

BACK END RETENTION ON GFS-NetApp

The back end retention time is always known to MCFS because it is stored in the file access time. Since the back end retention is set by QStar services, an attempt of a user application to set retention (by setting read-only permissions on a file) is ignored.

of 180

OPTIONS


-D Deletes all the cache options. This means that no cache

is assigned to the Integral Volume set.

-0 Clears all the cache parameters except for the cache_root and max_number_of_pages. This allows redefinition of the cache parameters with the "rnulhPgRwxSEF" options.

-r Filesystem is mounted read-only.

-n Mounts the Integral Volume set with a clean cache. It

makes no sense to specify -n in the cache parameters use this flag with the mountiv command instead. If this flag is added with the vlcache command, the cache will be zeroed on every mount, regardless of primary data.

-e Enables write operation after covered error occurs. By

default after covered error filesystem returns error on any write operation until error condition is cleared.

-p{max_number_of_pages|xxMB|xxGB}

Sets the maximum number of pages that can be used for caching data. If the -n is specified, this option is mandatory. The -p xxMB -p xxGB syntax is also supported.

-s page_size Sets the page size for the cache. The number should be power of 2 in range from 1 to 128 and specifies page size in KB. Default value is 64KB.

-l {low_primary_capacity | xxMB | xxGB |xx%}

The number of pages used to control the stop archiving. When archiving starts because of the number of primary pages in the cache becomes equal to the high_primary_capacity value, it proceeds until the number of primary pages in the cache is equal to or less than the low_primary_capacity value. The maximum value is the maximum number of pages in the cache minus 1. The default is 0. The value may also be specified in MB, GB and %(percentage) as follows: -l xxMB -l xxGB -l xx% where "xx" is the numeric value.

of 180

-h {high_primary_capacity|xxMB|xxGB|xx%} The number of pages used to control the start archiving. Archiving starts when the number of primary pages in the cache becomes equal to or greater than high_primary_capacity value. The maximum value is the maximum number of pages in the cache (see the –p option). The default value is 80% of the maximum number of pages. The value may also be specified in MB, GB and %(percentage) as follows: -h xxMB -h xxGB -h xx% where "xx" is the numeric value.

-P [h=]{prefetch_priority_period|0} Period of time in seconds which starts after the last read request in the cache. If this period is not 0, during it no archiving is made unless there is a need to free pages in the cache. The value of prefetch_priority_period must be between 5 and 120 and can be enabled only if the covered filesystem resides on tapes. Setting this period to 0 disables the feature. The prefix h= specifies a hard prefetch priority period. See mmchmod(8), section PREFETCHING.

-c cache_root Specifies the cache root directory. If the cache_root has not been specified or has been deleted by the –D option, no cache is supposed to be assigned to the Integral Volume set.

-w [h=]{1|0}

With -w1, filesystem is worm. It is prohibited to overwrite a file, remove it, or set its size. A file can be only appended. With this option, grace and retention periods are ignored. With -w0 or by default, filesystem is not worm. The prefix h= specifies a hard worm-fs feature.

-x [h=]{0|1} With -x1, file renaming in the worm filesystem or after the grace period expires is prohibited. With -x0 or by default, it is allowed. The prefix h= specifies a hard no-worm-rename feature.

-g [h=]{rdonly_grace_period|0}

Specifies the read-only grace period option. This period is counted from the last file modification (file modification time) and specifies a period of time during which a file or its attributes can be modified. The grace period affects regular files and does not affect directories. The grace period for a file expires when the difference between the current time and the file modification time becomes equal to or greater than the grace period. Every time when the file or its attributes are modified while the grace period is still in effect (not expired yet), the file modification time changes and the grace period is counted from this new modification time.

of 180

Once the grace period has expired, the file is treated as read-only even for the superuser. The behavior is different if both the read-only grace period and the retention period are specified. In this case, a file can be modified either before the grace period expires or after the retention period expires.

If the grace period is soft, it can be removed from the set by setting it to 0. If it is done by vlcache command, it will be in effect from the next mount. If it is done by mmparam command, it will be in effect only during the current mount session. The prefix h= specifies a hard grace period. See below the format of the grace period.

-R [h=]{retention_period|0} Specifies the retention period option. This period is counted from the last file modification (file modification time) and specifies a period of time during which the file cannot be removed. The retention period affects regular files and does not affect directories. The retention period for a file expires when the difference between the current time and the file modification time becomes equal to or greater than the retention period. Every time when the file or its attributes are modified (if modification is allowed by the grace period) the file modification time changes and the retention period is counted from this new modification time.

Once the retention period has expired, the file can be removed. If both the read-only grace period and the retention period are specified, the retention period can void the read-only status set by expiration of the grace period. In this case, a file can be modified either before the grace period expires or after the retention period expires.

If the retention period is soft, it can be removed from the set by setting it to 0. If it is done by vlcache command, it will be in effect from the next mount. If it is done by mmparam command, it will be in effect only during the current mount session. The prefix h= specifies a hard retention period. See below the format of the retention period.

-S [h=]{SHA1|SHA256|SHA512|0}

Specifies digest type of the set. If prefix h= is specified, the digest type becomes "permanent", i.e. it goes to "set features" stream of the set root directory. The prefix h= specifies a hard digest type.

of 180

-E [h=]{AES128|AES192|AES256|0} Specifies encryption type of the set. The prefix h= specifies a hard encryption type.

-F [h=]{0|1}

Sets prefetching mode to full (1) or partial (0). The prefix h= specifies a hard prefetching mode. See mmchmod(8), section PREFETCHING.

-B [h=]{dir|set|straight}

Sets back end retention. dir means directory-based retention, set - set-based retention, straight-straight retention.

-A [h=]{0|1}

Allows (1) or disallows (0) to update a file access time. This affects a request to update an access time without updating a modification time. If option -A is 1, such an update is allowed, if 0 - it is ignored. The default is 0 - no access time update. The prefix h= specifies a hard atime update feature.

-O [h=]{owner_access_period|0}

Specifies the owner access period option. This period is counted from the last file modification (file modification time)and specifies a period of time during which the owner of the file can have any access to the file regardless of the file permissions. This is useful when the file is created via NFS with read-only permissions and the owner of the file wantsto be able to write the file regardless of the NFS server behavior (mostly NFS3 case). The owner of the file in this case is either the process with effective UID matching file owner UID or the process with effective GID matching the member of the file’s list of groups. The owner access period for a file expires when the difference between the current time and the file modification time becomes equal to or greater than the owner access period. Every time when the file or its attributes are modified the file modification time changes and the owner access period is counted from this new modification time. If the owner access period is soft, it can be removed from the set by setting it to 0. If it is done by vlcache command, it will be in effect from the next mount. If it is done by mmparam command, it will be in effect only during the current mount session. The prefix h= specifies a hard owner access period. See below the format of the owner access period.

of 180

GRACE AND RETENTION PERIOD FORMAT

Both the grace and retention periods are specified as a number of years, days, hours, minutes and seconds in the following format:

<y>y<d>d<h>h<m>m<s>s where <y> is {0,1,......,19} <d> is {0,1,......,365} <h> is {0,1,.....,10000} <m> is {0,1,.....,10000} <s> is {0,1,......,10000} For example the period 3d1h means three days and 1 hour. EXAMPLES

vlcache -c /cache set1 (UNIX) vlcache -c c:\cache set1 (Windows)

Assigns the cache with /cache as the cache root directory to the Integral Volume set "set1".

vlcache -l 2 set2

Sets the low primary capacity in the Integral Volume set "set2" to 2.

of 180

VLCLOSE NAME

vlclose - Closes an UDF volume (surface or media). SYNOPSIS

vlclose [-H host_name] [-f] device_name shelf_number [{a|b}] DESCRIPTION

The vlclose command closes a sequentially written UDF volume. The device_name and shelf_number specify the disk. If the shelf_number is followed by a (b), the volume on side A (B) is closed. If no a (b) is present, a volume is closed on side A for a single-sided disk or on both sides for a double-sided disk. The command works with UDF disks only. If the disk belongs to a single-volume Integral Volume set, it must be not mounted. If the disk belongs to an automount Integral Volume set, during close procedure the disk is deleted from the Integral Volume set, closed, and added back to the Integral Volume set. After the disk is closed it is refreshed to update VL databases.

Closing the volume means writing special data as specified in the UDF standard. For CD-R and DVD-R, BD-RS after the UDF volume is closed, the session and the disk itself are also closed.

OPTIONS


-f Forces the command to delete the disk from the Integral

Volume set without archiving. All primary pages and events related to the disk will be discarded. Without this option the command archives all the delayed events before deleting the disk from the Integral Volume set.

EXAMPLES vlclose jb 1a Closes the session on shelf 1a.

of 180

VLCMP NAME

vlcmp - Compares two media. SYNOPSIS

vlcmp [-H host_name] [-v] [-r src_host_name] [-m] [- [-j

{delayed_job_name|"default"}] d{[mmdd]HHMM|[cc]yymmddHHMM}] [-l] to lock both sdf or tdo tape volumes (default lease) [-1|-2] compare only 1st or 2nd LTFS partition (default both) [-o] old compare (without thread) [-t compare_size] - compare last size (kKmMgG) or from logical block (lL) [-f] ignore no match nwa error src_dev_name[@src_host_name]:shelf_number dst_dev_name[@dst_host_name]:shelf_number

DESCRIPTION

The vlcmp command compares two media to ensure that their contents are identical. This command is used to verify a copy of a media made with the vlcopy command to ensure it has copied correctly.

NOTES

Both media may not reside on the same host. Source media resides on src_host_name (if specified), otherwise on host_name (if specified), otherwise on local host. Destination media resides on dst_host_name (if specified), otherwise on host_name (if specified), otherwise on local host. Compare operation will be executed on the current host or the host specified by -H option (host_name). If the media is double-sided both sides are compared.

OPTIONS

-H host_name Specifies the name of the host where the src_dev_name and dst_dev_name are connected. Without this option, the local host is used.

-r src_host_name

Specifies the name of the remote host where the source media resided (if src_host_name not specified in the source definition).

-v Verbose output.

-f Ignore no match NWA (Next Writable Address) error.

of 180

-t compare_size[unit]

Specifies the tail compared size or start logical block of the sdf, tdo or ltfs volumes (only for tape). Size in KB (unit k or K), in MB (unit m, M or not specified), in GB (unit g or G). If (unit l or L - start logical block.

-m Compares mirror medium. This option is applicable to SDF

/ TDO volumes only. It allows it to compare mirror medium.

-l Locking sdf, tdo or ltfs volumes (only for tape). Default - leasing volumes on default time.

-o Old compare (without thread)

-1|-2 Compare only 1st or 2nd LTFS partition (default both)

-j delayed_job_name

Specifies the job name used to identify the job in the delayed job list. If the delayed_job_name is the keyword "default", the actual job name will be generated automatically. Without the -j flag the job will be executed according to the -d flag (without the -d flag, the job will execute immediately).

-d [mmdd]HHMM|[cc]yymmddHHMM

Specifies the date and time the jobs should be executed on the delayed jobs list. The job will be executed immediately if there is no -j flag and no -d flag. If there is a -j flag and there is no -d flag the job will be executed according to the "CMP Delayed Start" field in the vl/files/conf file. Note - the -d flag is only usable by the superuser.

mm is the month number dd is the day number in the month HH is the hour number (24 hour system) MM is the minute number cc is the century yy is the last 2 digits of the year number

The month, day, year, and century may be omitted; the current values are supplied as defaults.

EXAMPLES

vlcmp jb1:5 jb2:6 Compares all data on the media in library#1 (jb1) on shelf 5 to the media in library#2 (jb2) on shelf 6.

vlcmp -j "Compare 5 and 6" jb1:5 jb2:6

Compares all data on the media in library#1 (jb1) on shelf 5 to the media in library#2 (jb2) on shelf 6. This command creates a delayed job. The job will be executed according to the "CMP Delayed Start" field in the vl/files/conf file.

of 180

vlcmp -j "Compare 5 and 6" -d 1330 jb1:5 jb2:6 The same as above but the job will be executed at 1:30 PM. "CMP Delayed Start" field in the vl/files/conf file makes no difference if -d is specified.

vlcmp -j "Compare 5 and 6" -d 1330 jb1:5 jb2:6

The same as above but the job will be executed at 1:30 PM. "CMP Delayed Start" field in the vl/files/conf file makes no difference if -d is specified.

vlcmp jbs:3 jbd@gamma:5

Compares all data on the media on shelf 3 of the library jbs on the local host and the media on shelf 5 of the library jbd on host gamma. The vlcmp process will be executed on the local host.

vlcmp -H alpha jbs:3 jbd@gamma:5

Compares all data on the media on shelf 3 of the library jbs on host alpha and the media on shelf 5 of the library jbd on host gamma. The vlcmp process will be executed on the host alpha.

vlcmp -H alpha jbs@beta:3 jbd@gamma:5

Compares all data on the media on shelf 3 of the library jbs on host beta and the media on shelf 5 of the library jbd on host gamma. This request equivalent vlcmp -H alpha -r beta jbs:3 jbd@gamma:5 The vlcmp process will be executed on the host alpha.

of 180

VLCONSOLE NAME

vlconsole - Manages the list of requests for manual assistance. SYNOPSIS

vlconsole [-H host_name] -l [-PSC]

vlconsole [-H host_name] -r [-SC]

vlconsole [-H host_name] -c -A set_name

vlconsole [-H host_name] -c -N set_name sequence_number

vlconsole [-H host_name] -c{-E|-I} device_name shelf_number

vlconsole [-H host_name] -c {-E|-I} -s set_name in_set_number set_type set_type_specific_name: sdf sequence_number udf sequence_number DESCRIPTION

The vlconsole command prints the list of requests for manual assistance, to cancel a particular request, or to remove requests from the list.

OPTIONS


-l Without the -PSC options, all the requests are printed.

Otherwise, the pending (-P), satisfied (-S), or cancelled (-C) requests are printed.

-r Removes satisfied (-S), or cancelled (-C) requests from

the list. Without the -SC options, all the satisfied and cancelled requests are removed.

-c Cancels the specified request.

With the -A option, a request to add a medium to the Integral Volume set is cancelled. With the -N option, a request to bring a medium online is cancelled.

of 180

An Integral Volume set is specified by set_name. The sequence_number specifies the medium within the Integral Volume set. The sequence number or in_set_name can be obtained with -l option or taken from the message printed on the system console and to /opt/QStar/log/syslog file. It is a message asking a user to vlimport or vladdtoset a medium.

With the -E (-I) option, a request to export (import) a medium is canceled. A medium is specified either by device_name and shelf_number or (with -s option) by set_name and in_set_number.

SET TYPE SPECIFIC NUMBER The value of set_type_specific_name depends on the Integral Volume set type:

sdf Sequence_number. udf Sequence_number.

The sequence number or in_set_number can be obtained with -l option or taken from the message printed on the system console and to /opt/QStar/log/syslog file. It is a message asking a user to vlimport or vladdtoset a medium.

EXAMPLES vlconsole –l Prints all request. vlconsole –r –S Removes all satisfied events.

of 180

VLCOPY NAME

vlcopy - Creates a (backup) copy of a media. SYNOPSIS

vlcopy [-H host_name] [-v] [-c copy_number] [-C {yes|no} [-r src_host_name] [-j delayed_job_name | "default"}] [-d {[mmdd]HHMM|[cc]yymmddHHMM}] [-h sdfHostID -t sdfTime] to copy SDF volumes with different set id [-I] to incremental copy SDF or TDO volumes [-l] to lock both sdf or tdo tape volumes (default lease) src_dev_name[@src_host_name]:shelf_number [dst_dev_name[@dst_host_name][:shelf_number]]

DESCRIPTION

The vlcopy command creates a copy of a media (SDF, UDF, TDO, LTFS). The resulting copy is identical to the original except that the copy_number in the volume_id block is incremented. The copy may be used for backup purposes and may be substituted for the original if the original becomes bad or unavailable. The src_dev_name@src _host_name:shelf_number specifies the library, host and shelf number for the original media. The dst_dev_name@dst_host_name :shelf_number specifies the library, host and shelf number for the copy. If dst_dev_name:shelf_number is omitted the vlcopy consults "COPY Jb Name", "COPY Start Shelf Number", "COPY End Shelf Number" fields in the vl/files/conf file. If there are no such fields in vl/files/conf file the vlcopy examines the src_dev_name library first and then all other libraries.

NOTES

Both the copy and the original may not reside on the same host. Original resides on src_host_name (if specified), otherwise on host_name (if specified), otherwise on local host. Copy resides on dst_host_name (if specified), otherwise on host_name (if specified), otherwise on local host. Copy operation will be executed on the current host or the host specified by -H option (host_name) or dst_host_name (if specified), i.e. on copy resides host. If the media is double-sided both sides are copied.

OPTIONS

-H host_name Specifies the name of the host where the original and/or copy is resided (if src_host_name or dst_host_name are omitted). Without this option, the local host is used.

of 180

-r src_host_name

Specifies the name of the remote host where the original resided (if src_host_name not specified in the source definition).

-v Verbose. Prints a progress report on the user's

terminal.

-h and -t Flags -h and -t allows performing volume copy in SDF / TDO mirror configuration. Here -h and -t should specify set ID (which is a combination of the hostid and timeid) for mirror set. For example, -h 0x12345678 -t 0xaabcd123. In this case volume copy will create a volume which belongs to mirror set 12345678.aabcd123. Both options -h and -t should be specified. Supported for SDF / TDO mirror sets only.

-I Incremental copy for an SDF or TDO media.

-l Locking sdf or tdo volumes (only for tape). Default -

leasing volumes on default time.

-c copy_number Forces the value of the copy number in the volume_id block to copy_number (0 - 128). Without this option, the copy_number on the destination media is equal to the copy_number of the original plus one.

-C yes|no

Compares source and target media after copy. This flag takes effect only for delayed jobs.

-j delayed_job_name

Specifies the job name used to identify the job in the delayed job list. If the delayed_job_name is the keyword "default", the actual job name will be generated automatically. Without the -j flag the job will be executed according to the -d flag (without the -d flag, the job will execute immediately).


Specifies the date and time the jobs should be executed on the delayed jobs list. The job will be executed immediately if there is no -j flag and no -d flag. If there is a -j flag and there is no -d flag the job will be executed according to the "COPY Delayed Start" field in the vl/files/conf file. Note - the -d flag is only usable by the superuser.


of 180


EXAMPLES

vlcopy jb:3 jb:5 Copies the media on shelf 3 to the media on shelf 5 of the library specified by the jb VL name.

vlcopy -v -c 0 jb:8 jb:11

Creates a copy of the media on shelf 8 to shelf 11, sets the copy_number of the copy to 0 and reports the progress of the copying. In this case the media on shelf 11 will be recognized by the VL as the original rather than a copy. This may produce a "Duplicate shelves" error after a vlrefresh if the source media also has copy_number 0.

vlcopy jb:3

Copies the media on shelf 3. The destination media will be determined by the "COPY Jb Name", "COPY Start Shelf Number", "COPY End Shelf Number" fields in the vl/files/conf file.

vlcopy -j "Make copy of shelf #3" jb:3 jb:5

This command creates a delayed job. The job will be executed according to the "COPY Delayed Start" field in the vl/files/conf file.

vlcopy -j "Make copy of shelf #3" -d 1330 jb:3 jb:5

The same as above but the job will be executed at 1:30 PM. "COPY Delayed Start" field in the vl/files/conf file makes no difference if -d is specified.

vlcopy -H alpha jbs:3 jbd:5

Copies the media on shelf 3 of the library jbs to the media on shelf 5 of the library jbd (both on host alpha). The vlcopy process will be executed on the host alpha.

vlcopy -H alpha -r beta jbs:3 jbd:5

Copies the media on shelf 3 of the library jbs on host beta to the media on shelf 5 of the library jbd on host alpha. The vlcopy process will be executed on the host alpha. This request equivalent vlcopy -H alpha jbs@beta:3 jbd:5.

vlcopy -r beta jbs:3 jbd:5

Copies the media on shelf 3 of the library jbs on host beta to the media on shelf 5 of the library jbd on local host. The vlcopy process will be executed on the local host. This request equivalent vlcopy jbs@beta:3 jbd:5.

of 180

vlcopy jbs:3 jbd@gamma:5

Copies the media on shelf 3 of the library jbs on the local host (delta for example) to the media on shelf 5 of the library jbd on host gamma. The vlcopy process will be executed on the host gamma. This request equivalent vlcopy -H gamma jbs@delta:3 jbd:5.

vlcopy -H alpha jbs:3 jbd@gamma:5

Copies the media on shelf 3 of the library jbs on host alpha to the media on shelf 5 of the library jbd on host gamma. The vlcopy process will be executed on the host gamma. This request equivalent vlcopy -H gamma jbs@alpha:3 jbd:5.

vlcopy -H alpha jbs@beta:3 jbd@gamma:5

Copies the media on shelf 3 of the library jbs on host beta to the media on shelf 5 of the library jbd on host gamma. The vlcopy process will be executed on the host gamma. Host alpha specification is ignored. This request equivalent vlcopy -H gamma jbs@beta:3 jbd:5.

of 180

VLCRSET NAME

vlcrset - Creates an Integral Volume set. SYNOPSIS vlcrset [-T set_type][-H host_name][-U {local|share}][-p {yes|no}][-u {disk|cd| tape|dvd|writable|worm|rdonly|cd-dvd|bd-re|bd-r|bd-rom|hd-sdisk|hd-stape| c-sdisk|c-stape|proxyN|cs|mirror}][-d default_mount_point][-q quota][-r] [-s][-I][-N][-M][-b {full|cron_like_schedule |Publisher_schedule}] [-n number_of_copies] [-C {one|all}][-G {auto|manual}][-X time_slice] [-K data_size_per_slice][set_type_specific_options]set_name [number_of_media]

set_type set_type_specific_options:

sdf [-c {default|on|off}](tape media only) [-Z 1] (RW disk media only) [{-m [hostname_2]:setname_2 |-2 [hostname_1]:setname_1} [-h {low|high|normal}]

udf [-v {s|a}] [-R {150|200|201|250|260}] [-P {0|1}] [-S {0|1}]

[-W{0|1}] [-F {0|1}] [-V {0|1}] [-B {0|1}] [-E {cd-r|dvd-r|dvd-r-dl|bd-r|bd-re|bd-r-50|bd-re-50}] [-A Publisher_media_retained][-D {0|1|2|3}] [-Q Publisher_host_name] [-L Publisher_label_file [{-k label_field_name -e label_field_value}...]]

uvfs [-v{s|a}]

aafs cluster ltfs [-v{s|a|1}] [-F{0|1}] [-S{0|1}] gfs hcp [-s extent_size_mb] [-f] osm rpl tdo [-c {on|off}] (tape media only, 'on' - default) [-j library_list] (mirror mode only, delimiter is comma) [-2 set_id] (SDF secondary set id for mirror mode only)

[-W{0|1|2|3|4|5}] ampl nom cloud

DESCRIPTION

The vlcrset command creates a new Integral volume set. The Integral volume set is specified by the set_name argument. If the number_of_media argument is present, it specifies the number of media which will be initialized and included in the Integral volume set. Without this argument the command does not include any media in the Integral volume set, it merely creates a record about the

of 180

Integral volume set in the VL database. The number_of_media must be less than or equal to the Integral volume set quota.

OPTIONS

-H host_name Specifies the name of the host where the Integral volume set resides. Without this option, the local host is used.

-T set_type

Specifies the Integral volume set type which defines the Integral volume set specific options in the command (see below). The default is nom (Integral volume set with no media).

-u use_media

Specifies the type of media which can be used in the Integral Volume set. use_media is one of the following words: disk Magnetic, optical, or simulated disks. cd CD-ROM and CD-R disks. tape Tapes. dvd DVD disks. writable Rewritable disks. worm WORM disks. rdonly Read-only disks. cd-dvd CD-ROM, CD-R, DVD-ROM, and DVD-R disks. bd-re Rewritable BD disks. bd-r Sequentially written and read-only BD disks. bd-rom Read-only BD disks. hd-sdisk Simulated HD disks. hd-stape Simulated HD tapes. c-sdisk Simulated CENTERA disks. c-stape Simulated CENTERA tapes. proxyN Proxy Media. cs Cleversafe Vault. mirror TDO Mirror volume. Writable, worm, or rdonly specify the type of media in the Integral Volume set from the read-write point of view. Other words specify the nature of media. The default depends on the Integral Volume set type. Multiple -u options can be used to specify an Integral Volume set of different types of media. For example, presence of -u writable and -u worm in the same vlcrset command means that an Integral Volume set can consist of rewritable and WORM media. cd-dvd is equal to "-u cd, -u dvd, -u rdonly, -u worm". Simulated media (e.g. hd-sdisk) can be mixed in the Integral Volume set with real media but cannot be mixed with simulated media of different type.

of 180

-s Specifies that the Integral Volume set can spread to another library on the same host. Without this option, the media available for use for the Integral Volume set is limited to the library where the Integral Volume set resides.

-q quota

Specifies the quota for the Integral Volume set. The quota is defined as the maximum number of media that can be allocated to the Integral Volume set. The default value depends on the Integral Volume set type.

-I Recreates the filesystem databases before mounting.

When the Integral Volume set is unmounted, this parameter is set to off. This option is disabled for CD set type.

-r Filesystem is mounted read-only.

-M Real and simulated media can be mixed in the Integral

Volume set. By default, this mix is prohibited. -U {local|share}

Used to specify whether an Integral Volume set can only be mounted and accessed from the local server. The default value is share. This option is only available on Linux if is not used FUSE as file system interface but is used old implementation with NFS server.

[-p{yes|no}]

Enable or disable the mount (publish) on server restart (see mountiv command with key -a). The default value is no.

-d default_mount_point

Set default mount point. Used for mountiv command with key -a (if mount on server restart enabled), or if mount_point omitted. By default /mnt/set_name.

-b {full|cron_like_schedule|Publisher_schedule}

full

Automatic start of vlcopy (Media Copy). When current media is filled up, vlcopy command copies it to first available medium with the same capacity. This option is available for SDF, TDO and Spanning LTFS file systems. It is also available in Spanning UDF file system for finalized media.

of 180

cron_like_schedule Incremental start of vlcopy (Media Copy). At a scheduled time the vlcopy command will incrementally copy data to the first available erased or blank media with the same capacity. Cron schedule: Minute Hour Day Month Weekday. For more detailed information about the syntax, please refer to the crontab man pages. This option is available only for SDF and TDO file systems.

Publisher_schedule Using Publisher device for copying the disks (available only for simulated spanned UDF file system). Publisher_schedule is in form Rn where n is a number from 1 to 99 and it specifies the number of copies required. If -b Rn is used, additional Publisher options can be used later (-E, -Q, -L, -k and -e).

SET TYPES AND SPECIFIC OPTIONS

All Integral Volume set specific options must be used after the generic options listed above. Not all Integral Volume set specific options that can be used in vlcrset can be used in vleditset and vice versa. It makes sense not to use generic option letters in the specific options of newly created Integral Volume set types.

sdf :

Standard Data Format support. If the -u option is omitted, the default is disk and writable. The quota limit is 2048.

The specific options are:

-c {default|on|off}

This option specifies the compression option. on enable the compression. off disable the compression. default the compression is set as default. This option is available only for tape libraries.

-Z{1}

This option specifies the shredding mode. Only RW disks are available for shredding mode. For UDO WORM COMPLIANCE disks shredding mode activated automatically. 1 is the shredding algorithm number.

[{-m [hostname_2]:setname_2 | -2 [hostname_1]:setname_1}] [-h {low|high|normal}]

These options specify the Mirroring parameters. See the QStar Mirroring Manual for more detailed information.

of 180

udf:

Universal Disk Format support. If the -u option is omitted, the default is disk and writable. The quota limit is 1 for single-volume Integral Volume set and 2048 for automount and spanning Integral Volume sets.


-v {s|a}

Specifies the interchange level: s - spanning Integral Volume set, and a - automount Integral Volume set. Without this option the Integral Volume set is single-volume.

-R {150|200|201|250|260}

Specifies UDF revision which will be assigned to a blank/erased disk when it is initialized and added to the Integral Volume set. The default is 150.

-P {0|1}

With -P1, CDR/DVDR/BD blank surface or a surface with an empty last session can be initialized for packet writing and added to the Integral Volume set. With –P0(default), such a surface cannot be initialized.

-S {0|1} For single-volume and automount Integral Volume sets. With -S1, the system will make space calculation in order to prevent accepting data into the cache if there is no enough space on the disk. This is the default. With -S0, space calculation is disabled and lack of disk space will result in a covered error.

-W {0|1} With -W1, write verification is enabled: after write, data is read and tested for comparison against the data that has been written. With -W0, write verification is disabled (default).q

-F {0|1}

This option is valid for udf spanning only. With -F1, file spanning is enabled: if there is no space on the last volume where the file resides, the file will be spanned to the next volume with enough space. This is the default. With -F0, file spanning is disabled: if there is no space on the volume where the file resides, the file will be moved to the next volume with enough space.

of 180

-V {0|1} For spanning Integral Volume sets. With -V1, once the WORM volume becomes full it is closed. With -V0, there is no automatic closing (default).

-B {0|1} For spanning Integral Volume sets. With -B1, image backup is used for CD-R/DVD-R (default). With -B0, image backup is not used.

-E {CDR|DVDR}

For vlcopy with using Publisher device. To use this parameter, option -b Rx should be specified on the command-line before. Parameter allows to select what disk type is used by Publisher.

-A {Publisher_media_retained} For vlcopy with using Publisher device. To use this parameter, option -b Rx should be specified on the command-line before. Publisher_media_retained specifies the number of last media retained in Integral Volume set, other finalized media are exported and disk space freed.

-D {0|1|2|3} For vlcopy with using Publisher device. To use this parameter, option -b Rx should be specified on the command-line before. Automount set suppors this option. The number (0,1,2,3) points to simulated medium disposal actions after publishing. 0 declares media online (no addition actions). 1 declares media offline (export media from set). 2 declares media offline and reuse space (export media from set and then add new empty simulated media). 3 declares media offline, purge cache and reuse space. Last two actions allows to use media retained parameter together.

-Q {Publisher_host_name} For vlcopy with using Publisher device. To use this parameter, option -b Rx should be specified on the command-line before. Publisher_host_name specifies the host name where QPublisher daemon is running. Now localhost is the only allowed value for this option.

of 180

-L Publisher_label_file For vlcopy with using Publisher device. To use this parameter, option -b Rx should be specified on the command-line before. Label_file specifies the label file for the copying job. When the next disk is being produced, it will be printed with the label. The additional parameters may be specified with -k and -e options

--k label_field_name For vlcopy with using Publisher device (printing parameters). Label_field_name specifies the next parameter name to be used with the label file (see -L option). Every parameter (option -k) has to have the corresponding value(option -v). There can be more than one parameter/value pair in the command line.

-e label_field_value For vlcopy with using Publisher device (printing parameters). Label_field_value specifies the next parameter value to be used with the label file (see -L option). Every parameter value (option -v) should have the corresponding parameter name (option -k). There can be more than one parameter/value pair in the command line.

nom:

The QStar Software can be configured to create an Integral Volume set with No Media, this allows data to be written to a cache as normal, but the data will not be archived and therefore not secured. A library or standalone drive can be added at a later date, and then the media can be added to the Integral Volume set and the data synchronized from the cache to the media.

uvfs:

The QStar Universal File System (uvfs) file system supports Read Only access to the following three Plasmon file systems: PFS - A simplified version of UDF, based on an older UDF implementation by HP. AFS-1 - Archive File System, specifically developed for WORM. AFS-2 - Improved version on AFS-1, optimized for speed and media usage.

of 180

The specific options are: -v {s|a}

Specifies the interchange level: s - spanning Integral volume set, and a - automount Integral volume set. Without this option the Integral volume set is single-volume. The way how to use this file system will be explained only in the QStar Windows Administratior’s Guide because is available only in Windows 32 bit.

aafs:

AA - Archive Appliance File System support. No Integral volume set type specific options should be specified for an aafs Integral volume set.

ltfs:

Linear Tape File System support.


-v {s|a|1}

Specify the set style: s - spanning Integral Volume set, a - automount Integral Volume set, 1 - single-volume Integral Volume set. Without this option the Integral Volume set is a direct-single-volue LTFS.

-F {0|1}

This option is valid for ltfs spanning only. With -F1, file spanning is enabled: if there is no space on the last volume where the file resides, the file will be spanned to the next volume with enough space. This is the default. With -F0, file spanning is disabled: if there is no space on the volume where the file resides, the file will be moved to the next volume with enough space. By default, file spanning is disabled.

-S {0|1}

For single-volume and automount Integral Volume sets. With -S1, the system will make space calculation in order to prevent accepting data into the cache if there is no enough space on the disk. This is the default. With -S0, space calculation is disabled and lack of disk space will result in a covered error.

of 180

cluster:

Cluster Migrator support. No generic or Integral volume set type specific options should be specified for a cluster Integral volume set except for –H option.

gfs:

Generic File System support. No generic or Integral volume set type specific options should be specified for a gfs Integral volume set except for -H option.

hcp:

Hitachi Content Platform support.


-s extent_size_mb

A file in HCP archive is stored in extents of equal size. The extent_size_mb specifies the size of the extent in megabytes (1 - 32). The default is 1.

-f Specify filesystem compatibility mode. In this

mode it is assumed that a file cannot be archived until all work with it is done. A file size must be less than extent size, in HCP it is not broken into extents. regular files and empty directories can be renamed. Without this option, files in HCP can be broken into extents, regular files cannot be renamed, only empty directories can be renamed.

tdo:

Tape and Disk Object file system support. If the -u option is omitted, the default is disk and writable. The quota limit is 2048.


-c {on|off}

This option specifies the compression option. on enable the compression. off disable the compression. The default value is on. This option is available only for tape libraries.

of 180

[-j library_list] Contains library list with delimiter comma and needed for allocation replica volume automatically. (similar on vl/conf file.

[-2 set_id] (SDF set id for mirror mode only) This option is needed during the conversion of the SDF mirror Integral Volume set to TDO mirror Integral Volume set. By default, is possible to associate only ONE Integral Volume set ID (Idetifier) to an Integral Volume set, with this option is possible to include in the Integral Volume set the media from the SDF mirror Integral Volume set.

[-W{0|1|2|3|4|5}]

The write verification methods for TDO are supported only for disk devices. The tape devices implement write verification in the hardware and in case of error the data is automatically rewritten on other media location. In case the communication path fails, the upper layers of the software will repeat write operation. The write verification method on disks is hardware dependent. Some of the devices provide hardware write verification which can be disabled, the other ones do not allow such disabling. The hardware verification methods on Blu�Ray disks also depends on media type (BD-R or BD-RW). To account for variety of the disk hardware verification methods the migrator can be configured to support several verification approaches. Not all approaches may be supported for the particular hardware. If hardware verification is not available, the data verification may be provided by the software (by reading back data and comparing the with memory image). Obviously, any verification will decrease performance, especially if hardware verification is combined with software verification.

Following configuration options are provided for TDO set: -W 0 Default. Hardware verification is enabled if device

supports it. -W 1 In addition to method -W 0 the software verification

is performed. The written data is read back from the disk and compared with memory image.

-W 2 Hardware verification is performed using WRITE & VERIFY SCSI commands.

-W 3 Hardware verification is performed using WRITE &

VERIFY SCSI commands and in addition software verification is performed.

of 180

-W 4 No hardware verification but data is read and verified by the software.

-W 5 No No hardware or software verification of any

sort. Provides highest write performance. EXAMPLES

vlcrset -T sdf alpha 2 Creates the Integral volume set "alpha" with the default attributes, initializes 2 media with SDF file system and includes them in the Integral volume set.

vlcrset –T sdf -u writable –u worm beta

Creates the Integral volume set "beta" which can contain writable and WORM disks.

vlcrset –T sdf –u worm -b “55 23 * * 1,2,3,4,5” beta

Creates the Integral volume set "beta" with SDF file system and WORM disks. And enable the incremental Copy Media to start daily at 23:55 from Monday to Friday.

vlcrset -T udf -u hd-sdisk -u worm -b R1 -v s -V 1 Set1 Creates the Integral volume set "Set1" with UDF file system and WORM simulated disk. Publisher system will be used to receive the hard copy of simulated disks when the next disk is filled with data.

of 180

VLDELFROMSET NAME

vldelfromset – Removes a media from an Integral Volume set. SYNOPSIS

vldelfromset [-H host_name] [-k] set_name in_set_number DESCRIPTION

The vldelfromset command removes specified media (‘in_set_number’) from set ‘set_name’ without exporting it from library. If the media contains no up-to-date data then it may be erased (and reused for the same or different Integral Volume set).

OPTIONS


-k The media will be killed, i.e. all primary pages and

delayed events related to that media will be removed from the cache. If the Integral Volume set is not mounted this procedure will be done immediately after the Integral Volume set is mounted.

EXAMPLES

vldelfromset alpha 0 Removes the media with in_set_number="0" from the Integral Volume set "alpha".

of 180

VLDELSET NAME

vldelset – Deletes an Integral Volume set. SYNOPSIS

vldelset [-H host_name] set_name DESCRIPTION

The vldelset command deletes an Integral Volume set. The Integral Volume set is specified by the set_name argument. The vldelset command removes the record about the Integral Volume set from the VL database. It does nothing with the media included in the Integral Volume set.

OPTIONS


EXAMPLES

vldelset alpha Removes the Integral Volume set "alpha" from the VL database.

of 180

VLEDITSET NAME

vleditset – Changes the Integral Volume set parameters. SYNOPSIS

vleditset [-H host_name] [-q quota] –U {local|share} [-s] [-I] [-M] [-p {yes|no}] [-b {none|full|cron_like_schedule}] [-d default_mount_point] [-r {0|1}] [set_type_specific_options] [-n number_of_copies] [-C {one|all}] [-G {auto|manual}] [-X time_slice] [-K data_size_per_slice] set_name

set_type set_type_specific_options: sdf [-c {default|on|off}](tape media only)

[{-m {-|[hostname_2]:setname_2} | -2 [hostname_1]:setname_1}] [-h {low|high|normal}]

udf [-R {150|200|201|250|260}] [-P {0|1}] [-S {0|1}] [-W{0|1}] [-F {0|1}] [-V {0|1}] [-B {0|1}][-Q Publisher_host_name] [-L Publisher_label_file [{-k label_field_name -e label_field_value}...]]

tdo [-c {on|off}] (tape media only, 'on' - default) [-j library_list] (mirror mode only, delimiter is comma) [-W{0|1|2|3|4|5}]

ltfs [-F{0|1}] [-S{0|1}] DESCRIPTION

The vleditset command changes and edits the parameters of an Integral Volume set. The Integral Volume set is specified by the set_name argument.

OPTIONS


-q quota Specifies the quota for the Integral Volume set. The quota is defined as the maximum number of media that can be allocated to the Integral Volume set. The default value depends on the Integral Volume set type.

-s Specifies that the Integral Volume set can spread to

another library on the same host. Without this option, the media available for use for the Integral Volume set is limited to the library where the Integral Volume set resides.

of 180

-I Recreates the filesystem databases before mounting. When the Integral Volume set is unmounted, this parameter is set to off. This option is disabled for CD set type.

-r {0|1}

Disable and enable the read-only option. -M Real and simulated media can be mixed in the Integral

Volume set. By default, this mix is prohibited.

-U {local|share} Used to specify whether an Integral Volume set can only be mounted and accessed from the local server. The default value is share. This option is only available on Linux if is not used FUSE as file system interface but is used old implementation with NFS server.

[-p{yes|no}]

Enable or disable the mount (publish) on server restart (see mountiv command with key -a). The default value is no.

-d default_mount_point

Set default mount point. Used for mountiv command with key -a (if mount on server restart enabled), or if mount_point omitted. By default /mnt/set_name.

-b {none|full|cron_like_schedule}

none Disables any type of Automatic start of vlcopy (Copy Media).

full

Automatic start of vlcopy (Media Copy). When current media is filled up, vlcopy command copies it to first available medium with the same capacity. This option is available for SDF, TDO and Spanning LTFS file systems. It is also available in Spanning UDF file system for finalized media.

cron_like_schedule

Incremental start of vlcopy (Media Copy). At a scheduled time the vlcopy command will incrementally copy data to the first available erased or blank media with the same capacity. Cron schedule: Minute Hour Day Month Weekday. For more detailed information about the syntax, please refer to the crontab man pages. This option is available only for SDF and TDO file systems.

of 180


All Integral Volume set specific options must be specified after the generic options listed above.

sdf:


-c {default|on|off}

This option specifies the compression option. on enable the compression. off disable the compression. default the compression is set as default. This option is available only for tape libraries.

[{-m [hostname_2]:setname_2 | -2 [hostname_1]:setname_1}] [-h {low|high|normal}]

These options specify the Mirroring parameters. See the QStar Mirroring Manual for more detailed information.

udf:


-R {150|200|201|250|260}

Specifies UDF revision which will be assigned to a blank/erased disk when it is initialized and added to the Integral Volume set. The default is 150.

-P {0|1}

With -P1, CDR/DVDR/BD blank surface or a surface with an empty last session can be initialized for packet writing and added to the Integral Volume set. With –P0(default), such a surface cannot be initialized.

-S {0|1} For single-volume and automount Integral Volume sets. With -S1, the system will make space calculation in order to prevent accepting data into the cache if there is not enough space on the disk. This is the default. With -S0, space calculation is disabled and lack of disk space will result in a covered error.

-W {0|1} With -W1, write verification is enabled: after write, data is read and tested for comparison against the data that has been written. With -W0, write verification is disabled (default).

of 180

-F {0|1} This option is valid for udf spanning only. With -F1, file spanning is enabled: if there is no space on the last volume where the file resides, the file will be spanned to the next volume with enough space. This is the default. With -F0, file spanning is disabled: if there is no space on the volume where the file resides, the file will be moved to the next volume with enough space.

-V {0|1} For spanning Integral Volume sets. With -V1, once the WORM volume becomes full it is closed. With -V0, there is no automatic closing (default).

-B {0|1} For spanning Integral Volume sets. With -B1, image backup is used for CD-R/DVD-R (default). With -B0, image backup is not used.

-Q {Publisher_host_name} For vlcopy with using Publisher device. Publisher_host_name specifies the host name where QPublisher daemon is running. Now localhost is the only allowed value for this option.

-L Publisher_label_file For vlcopy with using Publisher device. To use this parameter, option -b Rx should be specified on the command-line before. Publisher_label_file specifies the label file for the copying job. When the next disk is being produced, it will be printed with the label. The additional parameters may be specified with -k and -e options.

--k label_field_name For vlcopy with using Publisher device (printing parameters). Label_field_name specifies the next parameter name to be used with the label file (see -L option). Every parameter (option -k) has to have the corresponding value(option -v). There can be more than one parameter/value pair in the command line.

-e label_field_value For vlcopy with using Publisher device (printing parameters). Label_field_value specifies the next parameter value to be used with the label file (see -L option). Every parameter value (option -v) should have the corresponding parameter name (option -k). There can be more than one parameter/value pair in the command line.

of 180

ltfs:

Linear Tape File System support.


-F {0|1}

This option is valid for ltfs spanning only. With -F1, file spanning is enabled: if there is no space on the last volume where the file resides, the file will be spanned to the next volume with enough space. This is the default. With -F0, file spanning is disabled: if there is no space on the volume where the file resides, the file will be moved to the next volume with enough space. By default, file spanning is disabled.

-S {0|1}

For single-volume and automount Integral Volume sets. With -S1, the system will make space calculation in order to prevent accepting data into the cache if there is no enough space on the disk. This is the default. With -S0, space calculation is disabled and lack of disk space will result in a covered error.

tdo:

Tape and Disk Object file system support. If the -u option is omitted, the default is disk and writable. The quota limit is 2048.


-c {on|off}

This option specifies the compression option. on enable the compression. off disable the compression. The default value is on. This option is available only for tape libraries.

[-j library_list]

Contains library list with delimiter comma and needed for allocation replica volume automatically. (similar on vl/conf file.

of 180

[-W{0|1|2|3|4|5}] The write verification methods for TDO are supported only for disk devices. The tape devices implement write verification in the hardware and in case of error the data is automatically rewritten on other media location. In case the communication path fails, the upper layers of the software will repeat write operation. The write verification method on disks is hardware dependent. Some of the devices provide hardware write verification which can be disabled, the other ones do not allow such disabling. The hardware verification methods on Blu�Ray disks also depends on media type (BD-R or BD-RW). To account for variety of the disk hardware verification methods the migrator can be configured to support several verification approaches. Not all approaches may be supported for the particular hardware. If hardware verification is not available, the data verification may be provided by the software (by reading back data and comparing the with memory image). Obviously, any verification will decrease performance, especially if hardware verification is combined with software verification.

Following configuration options are provided for TDO set: -W 0 Default. Hardware verification is enabled if device

supports it. -W 1 In addition to method -W 0 the software verification

is performed. The written data is read back from the disk and compared with memory image.

-W 2 Hardware verification is performed using WRITE & VERIFY SCSI commands.

-W 3 Hardware verification is performed using WRITE &

VERIFY SCSI commands and in addition software verification is performed.

-W 4 No hardware verification but data is read and

verified by the software.

-W 5 No No hardware or software verification of any sort. Provides highest write performance.

EXAMPLES

vleditset -r 1 beta Turns the read only option on for the Integral Volume set "beta".

of 180

VLERASE NAME

vlerase - Erases a media. SYNOPSIS

vlerase [-H host_name] [-v] [-fe] [-j {delayed_job_name | "default"}] [-d {[mmdd]HHMM|[cc]yymmddHHMM}] device_name shelf_number[{a|b}]

vlerase [-H host_name] [-vfe] device_name shelf_number:shelf_number

DESCRIPTION

The vlerase command erases either individual media or a group of media in the specified range of shelves. The library or standalone drive is specified by the device_name argument.

The first form of the command erases both sides of the media if the surface (a or b) is not specified. The shelf is specified by the shelf_number argument.

The second form of the command erases all existing media in the range of shelves specified by the shelf_number:shelf_number argument.

NOTES

If media belongs to an Integral Volume set, the erase process will be denied.

OPTIONS


-v Verbose

Prints the progress report on the user terminal. If erasing a single shelf (surface), the command prints a line with the number of blocks, block size and approximate time needed for erasing. If erasing a range of shelves the command prints a line with shelf number.

-f Full erase

By default the QStar software erases only the first 2048 blocks on each side of the media which is acceptable for any file systems. The full erase procedure can be used to check faulty media, because all blocks will be erased.

of 180

-e Emulate erase A special pattern will be written on the media instead of physically erasing it. By default the QStar software erases only the first 2048 blocks on each side of the media, with the -f option the pattern will be written in every block on the media. For vlrefresh a block with this pattern is recognized as an erased block. Erase emulation is available for magneto-optical rewritable media only and its main purpose is to ensure that there are no blank blocks on the media (blocks that cannot be read without error). It should be used on media that will hold the UDF file system and then will be moved to a non-QStar Windows UDF implementation (some of which will not recognize blank blocks).

-j delayed_job_name

Specifies the job name used to identify the job in the delayed job list. If the delayed_job_name is the key word "default", the actual job name will be generated automatically. Without the -j flag the job will be executed according to the -d flag (without the -d flag, the job will execute immediately).


Specifies the date and time the jobs should be executed on the delayed jobs list. The job will be executed immediately if there is no -j flag and no -d flag. If there is a -j flag and there is no -d flag the job will be executed according to the "ERASE Delayed Start" field in the vl/files/conf file. Note - the -d flag is only usable by the superuser.



EXAMPLES

vlerase jb 3:5 Erases media on shelves 3, 4 and 5 of the library specified by the jb VL name.

vlerase jb 8a

Erases surface "a" of the media on shelf 8.

of 180

vlerase -j "Erase shelf #3" jb:3 This command creates a delayed job. The job will be executed according to the "ERASE Delayed Start" field in the vl/files/conf file.

vlerase -j "Erase shelf #3" -d 1330 jb:3

The same as above but the job will be executed at 1:30 PM. "ERASE Delayed Start" field in the vl/files/conf file makes no difference if -d is specified.

of 180

VLEXCHANGE NAME

vlexchange - Moves a media from one shelf to another in the library.

SYNOPSIS

vlexchange [-H host_name] device_name shelf_number_1 shelf_number_2 [num_shelves]

DESCRIPTION

If destination shelf is empty the vlexchange command moves the medium from the source shelf (shelf_number_1) to destination shelf (shelf_number_2) in the library. If medium is present on destination shelf the vlexchange command exchanges the medium from the source shelf with destination shelf. Also the command updates VL databases. Optional num_shelves argument specifies number of media to exchange between source and destination.

OPTIONS


EXAMPLES

vlexchange jb 1 2 Moves the media from shelf 1 to shelf 2.

of 180

VLEXPORT NAME

vlexport - Exports a media or a complete set from the library or standalone drive.

SYNOPSIS

vlexport [-H host_name] [-a] [-o] device_name shelf_number [num_shelves]

vlexport [-H host_name] [-a] -s set_name in_set_number

vlexport [-H host_name] [-a] -s set_name DESCRIPTION

The vlexport command exports a single media or all media included in an Integral Volume set. The first form of the command exports a media from the library or standalone drive specified by the device_name argument, the shelf_number specifies the shelf(or starting shelf), optional num_shelves specifies number of media to export. The second form of the command exports a media belonging to the Integral Volume set. The set_name argument specifies the name of the Integral Volume set. The in_set_number argument specifies the number of the media within the Integral Volume set. The third form of the command exports all media included in an Integral Volume set. The set_name argument specifies the name of the Integral Volume set.

The offline location of the media can be specified by the vlinset -f command or during an export operation. Otherwise it is built as S1_N1_N2[_S2], where S1 is a set name, N1 is the in_set_number, N2 is the sequence_number, S2 is a bar_code or magazine_id (if exist). A user will be asked to confirm it or enter another one. Typing of '^' followed by Enter cancels the operation. Operator help output and input required for export are directed to the user terminal.

OPTIONS


of 180

-a If the local host is not the host where the device is connected (remote administration), the command does not do the real export but places a request on the remote host for manual assistance. In case of local administration, this option allows the same behavior. The list of requests for manual assistance can be obtained with vlconsole command. The real export is done only when the command is running on the local host without -a option.

-o open_door

Opens the door to access the mail slot(s)on specific libraries.

-s set_name

Specifies the Integral Volume set name in the second and third forms of the command.

EXAMPLES

vlexport jb 3 Exports a media from shelf number 3 of the library specified by the device_name jb.

vlexport -H boa -s alpha

Exports all media from the Integral Volume set "alpha" on the host "boa".

of 180

VLIMPORT NAME

vlimport - Imports media into the library or standalone drive. SYNOPSIS

vlimport [-H host_name] [-a][-o] [-p {cd-rom | cd-r | cd-rw | dvd-rom | dvd-r | dvd-ram | dvd-rw | dvd-rw-s | 1}] ][-P] [-C] device_name shelf_number [num_shelves]

vlimport [-H host_name] [-a] -s set_name in_set_number

vlimport [-H host_name] [-a] -s set_name

For Hard Disk simulated library: vlimport [-H host_name] -S+ device_name shelf_number

vlimport [-H host_name] -S [A=]disk_id[:{rw|worm}:{number_of_blocks|

xxMB|xxGB}:block_size] device_name shelf_number [num_shelves] vlimport [-H host_name] -S [A=]disk_id[:[rw|worm]:{pdd|udo|udo2|mo91|

dvdram|dvd-r| cd-r|bd-re|bd-re-50|bd-r|bd-rs-50|bd-r-100}] device_name shelf_number [num_shelves]

vlimport [-H host_name] -S tape_id[:capacity_meg:{dlt|sdx|sdz|ultrium}]

:{rw|worm}] device_name shelf_number [num_shelves] For Centera simulated library: vlimport [-H host_name] –S [A=]centera_disk_id[:{number_of_blocks|

xxMB|xxGB}:block_size] device_name shelf_number [num_shelves])

vlimport [-H host_name] -S [A=]centera_disk_id[:{pdd|udo|udo2|mo91|dvd-r |cd-r|bd-re|bd-re-50|bd-r|bd-rs-50|bd-r-100}] device_name shelf_number [num_shelves]

vlimport [-H host_name] -S centera_tape_id[:capacity_meg:{dlt|sdx|sdz

|ultrium}]device_name shelf_number [num_shelves] DESCRIPTION

The vlimport command imports a media into a library or standalone drive.

The first form of the command imports a media into the library or standalone drive specified by the device_name argument. The shelf_number specifies the shelf (or starting shelf), optional num_shelves specifies number of media to import.

of 180

The second form of the command imports a media belonging to the Integral Volume set. The set_name argument specifies the name of the Integral Volume set. The in_set_number argument specifies the number of the media within the Integral Volume set.

The third form of the command imports all media included into the Integral Volume set. The set_name argument specifies the name of the Integral Volume set. The offline location of the media can be specified by the vlinset -f command or during an export operation. If it is not specified, it is listed as S_N, where S is a Integral Volume set name, N is the in_set_number. A user will be prompted to enter the device name and the shelf number. Typing a '^' followed by Enter cancels the operation.

After the media is imported to the specified shelf in the library, the media is refreshed. If the media contains an Integral Volume set identification it may be printed by the vllsdev -i command and included into the VL database by the vladdtoset command. Operator help required for the erase is directed to the user terminal. The form of the vlimport command with the -S simulation_param option imports the simulated disk to the specified shelf. If this option is present num_shelves must be equal to 1. See jbsim command.

OPTIONS


-a If the local host is not the host where the device is

connected (remote administration), the command does not do the real import but places a request on the remote host for manual assistance. In case of local administration, this option has the same behavior. The list of requests for manual assistance can be obtained with vlconsole command. The real import is done only when the command is running on the local host without -a option.

-o open_door Opens the door to access the mail slot (s)on specific libraries.

of 180

-s set_name Specifies the Integral Volume set name in the second and third forms of the command.

-P Refresh procedure will use physical refresh (not use

bar code media database). This option required for correct changing of "Write Protect" media status.

-C Imported media is cleaning tape.

-p Sets media type of the shelf.

This flag is used with libraries with CD-ROM, CD-R, DVD-ROM, DVD-R, DVD-RAM drives present. The jbstatus command shows the drive's capabilities and media type of the shelves. The media type is automatically set but it can be altered with -p option, and after that, the jbscheduler will only load a media to a drive that can handle this media type. The -p option can be used several times. The 1 flag is used as media type flag that specifies the media being imported should be considered single sided. The latter is used with libraries that support both single and double side media.

IMPORT IN SIMULATED LIBRARY An extra option is used in jbimport and vlimport commands to specify a simulated disk/tape to be "imported" to the shelf. The option (-S simulation_param) has one of the following forms: -S+ Imports all existing HD disks/tapes. -S [A=]disk_id:{rw|worm}:{number_of_blocks|xxMB|xxGB}:block_size A new HD disk is created to represent a rewritable (rw) or WORM (worm) disk with the capacity specified by number_of_blocks and block_size. If A= is present, the disk has side A only. Without A=, the disk is two- sided. Each surface is represented by a file in directory dir_path associated with the HD disk library. The actual file name is <disk_id>_A.rw_<number_of_blocks>_<block_size> for side B and <disk_id>_B.rw_<number_of_blocks>_<block_size> (if it exists). The block_size must be divisible by 512 and not exceed 8192. The disk capacity must be greater than or equal to 10 MB and less than 100 GB. number_of_blocks may be specified indirectly as xxMB or xxGB, where "xx" is the number of megabytes (MB) or gigabytes (GB).

of 180


The same as above but the disk capacity is derived from a real disk type specified by shortcut:

pdd Number_of_blocks 10789472, block_size 2048. udo Number_of_blocks 1834348, block_size 8192. udo2 Number_of_blocks 3669718, block_size 8192. mo91 Number_of_blocks 1095840, block_size 4096. dvdram Number_of_blocks 2236704, block_size 2048. dvd-r Number_of_blocks 2297888, block_size 2048. cd-r Number_of_blocks 327680, block_size 2048. bd-re Number_of_blocks 11826176, block_size 2048. bd-rs Number_of_blocks 12219392, block_size 2048.

bd-re Number_of_blocks 11826176, block_size 2048. bd-re-50 Number_of_blocks 23652352, block_size 2048. bd-r Number_of_blocks 12219392, block_size 2048. bd-r-50 Number_of_blocks 24438784, block_size 2048. bd-r-100 Number_of_blocks 48878592, block_size 2048.

With dvdram, dvd-r, cd-r, bd-re, bd-re-50, bd-r, bd-r-50,

or bd-r-100 the medium type (rw|worm) must be omitted. With pdd, udo, udo2, or mo91, the medium type must be present.

-S [A=]disk_id -S tape_id:capacity_meg:{dlt|sdx|sdz|ultrium}:{rw|worm}

A new HD tape is created to represent a tape. Capacity_meg specifies the tape capacity in megabytes and must be greater than or equal to 10 MB and less than 1000 GB. A tape can be rewritable (rw) or WORM (worm). A tape can be of one of the following types:



-S tape_id An existing HD tape is imported. -S [A=]centera_disk_id:{number_of_blocks|xxMB|xxGB}:block_size A new Centera disk is created to represent a WORM disk. If A= is present, the disk has side A only. Without A=, the disk is two-sided. The disk capacity is specified as for HD disk and has the same limitations. -S [A=]centera_disk_id:shortcut

The same as above but the disk capacity is derived from shortcut (see above).

-S [A=]centera_disk_id An existing Centera disk is imported.

of 180

-S centera_tape_id:capacity_meg:{dlt|sdx|sdz|ultrium} A new Centera tape is created. The tape capacity and type are specified as for HD tape. -S centera_tape_id An existing Centera tape is imported. EXAMPLES

vlimport jb 3 Imports a media to shelf number 3 of the library specified by the device_name jb.

vlimport -S alpha:rw:700000:2048 simd 2 Creates a double-sided rewritable disk alpha and import it to shelf 2 in library simd. The disk has 700000 blocks of a 2k block size. vlimport -S alpha simd 3 The disk created by the previous command was then exported (detached from shelf 2). Now this command imports it to shelf 3. vlimport -S A=beta:worm:udo simd 4 Creates a single-sided WORM disk beta and import it to shelf 4 in library simd. The disk has capacity of UDO disk. vlimport -S beta:150:dlt simt 1 Creates a tape alpha and import it to shelf 1 in library simt. The tape capacity is 150 Mbytes, its type is dlt. vlimport -S A=gamma:pdd cend 2 Creates a single-sided WORM disk gamma and import it to shelf 2 in library cend. The disk has capacity of PDD disk.

of 180

VLINSET NAME

vlinset - Edits media in an Integral Volume set. SYNOPSIS

vlinset [-H host_name] [-f offline] [-c {tree|data}] [-alu] [-r {tree|data|medium|all}] [set_type_specific_options] set_name in_set_number

set_type set_type_specific_options: sdf udf [-R] [device_name:shelf_number]

DESCRIPTION

The vlinset command edits a media in the Integral Volume set. The Integral Volume set is specified by the set_name argument. The media is specified by in_set_number argument which is a sequential number of a media in the Integral Volume set. In_set_numbers are 0-based and printed in the left column by vllsset -v command.

OPTIONS


-f offline

Changes the offline location of the media to a new offline location. The media must be offline.

-a Adds a media to the cache without copying of its

information.

-c {tree|data} Copies information from the medium into the cache. tree Copies the tree structure only. data Copies the tree structure and data.

-l Locks data related to the medium in the cache. Same as

the -k option in mmchmod.

-u Unlocks data related to the medium in the cache. Same as the +k option in mmchmod.

of 180

-r {tree|data|medium|all} Removes information related to the media from the cache and/or from the Integral Volume set. tree Removes the tree structure and data from the

cache. data Removes the data only. medium Removes the media from the Integral Volume set. all Removes the tree structure and data from the

cache and the media from the Integral Volume set.


All Integral Volume set type specific options must be specified after the generic options listed above. It makes sense not to use generic option letters in the specific options of newly created Integral Volume set types.

sdf: No specific options. A media cannot be removed from the Integral Volume set.

udf: The specific options are:

-R [device_name:shelf_number]

Used with UDF spanning sets to recover from the image backup. The device_name:shelf_number argument specifies the device name and shelf number of the new media that will replace the original one in the in_set_number argument. An image backup is maintained for CD-R and DVD-R disks. The new media is initialized as a copy of the original media but the current side is copied from the image backup. The new media replaces the original one in the VL set database and if the Integral Volume set is mounted, the UDF migrator is notified of that.

A media cannot be removed from the Integral Volume set.

EXAMPLES

vlinset -f new_offline beta 2 Changes the offline location of the media number 2 in the Integral Volume set "beta" to "new_offline".

of 180

VLLEASE NAME

vllease - Manages the drive lease time for the media in the Integral Volume set. SYNOPSIS

Command has six forms:

1. vllease [-H host_name] -L on -T default set_name [in_set_number]

2. vllease [-H host_name] -L on -T seconds set_name [in_set_number]

3. vllease [-H host_name] -L on -T restore set_name [in_set_number]

4. vllease [-H host_name] -L off set_name [in_set_number]

5. vllease [-H host_name] -L off -T save set_name [in_set_number]

6. vllease -l DESCRIPTION

The media loaded from a shelf into drive occupies the drive and prevents other media from being loaded. In order to prevent monopolization of the drive the time the media is loaded in the drive may be managed using drive lease approach. The media loaded in the drive may be "locked" which may be necessary for some operations such as tape Integral Volume set migrator. By default the media is loaded into drive for some time period which depends on the drive load/unload time. The vllease command allows manipulate media residency timing in the drive. The drive lease is mainly relevant to the tape drives because operations on the tape are position sensitive. There is difference in lease timing for real and virtual tape libraries. The virtual tape load/unload and positioning operations are much faster and lease time can be made (and by default are) smaller. The first form of the command (-L on -T default) sets default lease time and enables (or continues) leasing. Default value of lease time see in sixth form of the command. The second form of the command (-L on -T seconds) sets a lease time equal to specified number of seconds and enables (or continues) leasing. The third form of the command (-L on -T restore) sets an old (restores saved) value of the lease time (see fifth form of the command) and enables (or continues) leasing. The fourth form of the command (-L off) disables leasing and removes (reset) lease time.

of 180

The fifth form of the command (-L off -T save) saves current lease time and disables leasing. The sixth form of the command (-l) shows default value of lease time (900 sec for the real and 30 sec for a virtual tape drives).

NOTES

The vllease command can be used for a single in-set-medium or for all medium in the Integral Volume set in the appropriate format. The set_name argument specifies the name of the Integral Volume set. The in_set_number argument specifies the in-set-medium.

The vllease command makes sense to apply only when the shelf is open, because qs_scsi_open and qs_scsi_close calls on shelf (in the migrator) resets the lease status of the shelf.

It should be noted that the migrator itself is able to manage lease timing (using the qs_scsi_lease call). Currently the tape enabled migrators (TDO, SDF, LTFS) and utilities (vlcopy, vlcmp commands) sets default lease time after opening the shelf.

Once the media from the shelf is loaded into a drive it becomes locked for a specified number of seconds (lease time).

After the specified number of seconds expires, the tape in the drive is unlocked and can be unloaded if there is a request for other media to be loaded into the drive.

If another media is loaded into the drive the application (SDF, TDO, LTFS migrator or utilities) remains unaware about that event because SCSI subsystem preserves all tape related parameters such as position, compression, partition settings and restores those values after media is returned back (please note that the media can be returned to the different compatible tape drive).

The drive leasing is useful when a limited number of drives are present, for example, when three Integral Volume Sets are mounted simultaneously while there are only two drives.

The other usage example is when a media refresh or import required, but all drives busy.

OPTIONS

-H host_name Specifies the name of the host where the Integral Volume set is connected. Without this option, the local host is used.

of 180

-L {on | off} Enables (on) or disables (off) leasing specified in-set-media shelf.

-T {seconds | default | restore | save} Specifies the value time leasing (in seconds, default or saved value) or save current value.

-l Shows default value of lease time.

of 180

VLLSVOL NAME

vllsvol - Provides possibility to list volume content. SYNOPSIS

vllsvol [-H host_name] [-x] set_name volume_number DESCRIPTION

The vllsvol command provides possibility to list volume content for SDF, TDO, UDF and LTFS file systems.

set_name - Specifies Integral Volume set name Please note that vllsvol command support listing of the volueme contents for LTFS and UDF spanning sets only. The single volume and automount IV sets do not require special tools to list contents since they are self contained.

volume_number - Specifies volume number in the Integral Volume set. The volume numbers are starting for 0 for SDF and TDO IV sets and from 1 for LTFS and UDF file systems.

OPTIONS

-H host_name Specifies the name of the host where the command execution shall occur. Without this option, the local host is used.

-x Provide output in XML format.

Without this option the user-frendly output is produced. EXAMPLES

vllsvol sdf 1 Set:

Name : mysdf Type : sdf Id : 4a35bb425106f55e

Volumes: Volume Status Media Shelf Library 1 online 0 16 jbsd Files on volume 1: Vol Pos Size Size_vol Path ---------------------------------------------

1 505 536870912 90636288 /vt1/file_00000001.dat 2 90560 536870912 536870912 /vt1/file_00000002.dat

of 180

Here the content volume 1 of the set type SDF is listed. First the volume information is displayed, then a listing of all files on the volume is provided (which could be quite long depending of the media capacity and number of files on the media). Please note that "Pos" column provides information about relative location of the file on media. In TDO and SDF it is actual position number but for LTFS the position is essentially file node number which somewhat represents file position on the tape. The position allows to perform file sorting when retrieving number of files from media to avoid excessive media positioning. The "Size_vol" column shows size of the portion of the file on this media and may be smaller then the whole size of the file.

The same listing in XML fromat looks like following: <?xml version="1.0" encoding="UTF-8"?> <data> <set> <name>sdf</name> <type>sdf</type> <id>4a35bb425106f55e</id> </set> <volume> <volume_seq>1</volume_seq> <volume_status>online</volume_status> <in_set_number>0</in_set_number> <slot_number>16</slot_number> <device_name>jbsd</device_name> </volume> <files> <file> <path>/vt1/file_00000001.dat</path> <pos>505</pos> <size>536870912</size> <size_vol>90636288</size_vol> </file> <file> <path>/vt1/file_00000002.dat</path> <pos>90560</pos> <size>536870912</size> <size_vol>536870912</size_vol> </file> </files> </data>

of 180

VLLSDEV NAME

vllsdev – Prints the status of the media and library(ies) or standalone drive(s).

SYNOPSIS

vllsdev [-H host_name] [-nBI] device_name shelf_number

vllsdev [-H host_name] [-nsiebwuSABCI] device_name [shelf_number:shelf_number]

vllsdev [-H host_name] [-vnsiebwuSABCI] –a DESCRIPTION

The vllsdev command prints the VL status for the specified shelf, device, or for all of them.

The first form of the command prints the status of the shelf specified by the shelf_number. The library is specified by the device_name argument.

The second form of the command prints the status of the device which may be a library or a standalone drive. In the case of a library it prints the status of all the shelves in the library. If optional shelf_number:shelf_number argument is present the output is limited by specified range of shelves. The device is specified by the device_name argument.

The third form of the command prints the status of all the devices on the host.

NOTES

If the medium is present on the shelf, the output is provided for every surface. If the medium belongs to an Integral Volume set, the surface information depends on the -ni options. With the -ni options and if the Integral Volume set exists, the Integral Volume set name is printed. Without the -ni option or if the Integral Volume set name does not exist, the Integral Volume set specific information is printed. The command output is directed to the user terminal.

OPTIONS


-n Prints the Integral Volume set name instead of the set

specific information.

of 180

-s Lists the shelves with media that belongs to an Integral

Volume set.

-i Lists the shelves with media that belongs to an Integral Volume set not listed in the VL database. Usually such media emerges after the import or refresh operation. The Integral Volume set can be included into the VL database by using the vlcrset and vladdtoset commands.

-e Lists the empty, inaccessible or bad shelves.

-b Lists the shelves with blank or erased media.

-w Lists the shelves which are currently working, i.e.

erasing, refreshing, etc.

-u Lists the shelves with unknown contents.

-v Prints the name of the device and the status of all the shelves (if it is a library). Without this option, the status of shelves is not printed.

-A Lists the shelves with audio media. -C Lists the shelves with cleaning media.

-I Prints the Media Serial Number instead of the

Integral Volume set specific information. Option available only for UDO media.

-a Specifies all devices on the host in the third form of

the command.

-S Sorts shelves (surfaces). With -n option, the output is sorted by Integral Volume set names. With -B option, the output is sorted by bar codes. Otherwise, it is sorted by Integral Volume set Ids for non CD/DVD devices and by LabelNames for CD/DVD devices.

-B Prints the bar code instead of the Integral Volume set

specific information. If none of the -siebw options are used all shelves are listed.

EXAMPLES

vllsdev jb 3 Prints the VL status of shelf number 3.

vllsdev -nbsa

Prints, for all devices on the current host, the status of shelves with media which are erased (blank) or belong to Integral Volume sets. The Integral Volume set name should be printed instead of the Ids.

of 180

VLLSSET NAME

vllsset - Prints status of an Integral Volume set. SYNOPSIS

vllsset [-H host_name] set_name in_set_number

vllsset [-H host_name] [-v] set_name

vllsset [-H host_name] [-nv] {-a|-m} DESCRIPTION

The vllsset command prints the VL status for the specified Integral Volume set, specified in-set-medium or for all of them.

The first form of the command prints the status of the specified in-set-medium in the Integral Volume set. The set_name argument specifies the name of the Integral Volume set. The in_set_number argument specifies the in-set-medium.

The second form of the command prints the status of the specified Integral Volume set. The set_name argument specifies the name of the Integral Volume set.

The third form of the command prints the status of all the Integral Volume sets on the host.

Integral Volume set parameters printed by the command include use_media, spread and quota information, and the number of in-set-media. The rest are Integral Volume set specific information. In-set-medium parameters include online (device and shelf) or off-line information and Integral Volume set specific in-set-medium data. The command output is directed to the user terminal.

The command output is directed to the user terminal.

OPTIONS


-n Prints only the Integral Volume set name. Without this

option, the command prints the Integral Volume set name and parameters.

of 180

-v Prints the information about the in-set-media. Without this option, the command does not print information about the in-set-media.

-a Specifies all Integral Volume sets in the third form of

the command.

-m Specifies all mounted Integral Volume sets in the third form of the command.

EXAMPLES

vllsset -v Test

Test Use_media=disk,writable Spread=no Quota=2048 Media=2 Restore_fsdb=no Read_only=no Make_copy=no Set_type=sdf (standard data format) SetId=807bef41.361b3d4d Cache: Cache_root=/export/home/cache_Test

Max_number_of_pages=1600 (100 MB) Page_size=64 Kbytes

Mounted at /mnt 0: Online=jb:1 Sequence_numbers=0,1 Mounted=a,b 2: Online=jb:2 Sequence_numbers=2,3 Mounted=a,b

of 180

VLLTFS NAME vlltfs - check or repair incomplete LTFS tape. SYNOPSIS

vlltfs [-H host_name] [-f|-n|-s|-S] [-r [-g generation]] device_name shelf_number

DESCRIPTION

The vlltfs command checks or repairs an incomplete Ltfs tape. The device_name and shelf_number specify the tape. The command works with LTFS tapes only. If the tape belongs to a direct single-volume Integral Volume set, it must be not mounted. If the tape belongs to a single-volume, automount or spanning Integral Volume set, it can be mounted or unmounted. If the tape is incomplete, repair means a restoration the file system on the tape to the specified generation point, see -g option. After the tape is repaired it is refreshed to update VL databases (Incomplete LTFS tape flag).

OPTIONS

-H host_name Specifies the name of the host where the device resides. Without this option, the local host is used.

-f Set Incomplete LTFS tape flag.

-n Clear Incomplete LTFS tape flag.

-r Repair LTFS tape.

-g Specify the generation to which the file system will be

restored during repair. The default (generation equal to 0 or no this option) means the last generation.

-s Print the VL status for the specified shelf (see vllsdev).

-S Examine the tape and report its complete or incomplete status.

EXAMPLES vlltfs -s -r jb 1 Repair the tape on shelf 1 and print new status.

of 180

VLMAGAZINE NAME

vlmagazine - Exchanges media in the library using the magazines and updates the VL database.

SYNOPSIS

vlmagazine [-H host_name] [-p {cd-rom | cd-r | cd-rw | dvd-rom

| dvd-r | dvd-ram | dvd-rw | dvd-rw-s | 1}] [-s] [-P] [-m [-c]] device_name [magazine_number | h]

DESCRIPTION

The vlmagazine command exchanges media in the library using the magazines and updates the VL database. Note that to update "write protect" status of the media the physical refresh is needed (not use media bar codes and magazine Id in VL media database). The library is specified by the device_name argument. If magazine_number is omitted all magazines are available for exchange. Substitute "h" as the magazine_number for the hyper magazine (Pioneer library only).

OPTIONS


-p Sets media type of the shelevs on the magazines. This flag is used with libraries with CD-ROM, CD-R, DVD-ROM, DVD-R, DVD-RAM drives present. The jbstatus command shows the drive's capabilities and media type of the shelves. The media type may be determined automatically but it may be alternatively specified with -p option, and after that, the jbscheduler will only load a media to a drive, that can handle this media type. The -p option can be used several times. The 1 flag is used as media type flag that specifies the media being imported should be considered single sided. The latter is used with libraries that support both single and double side media.

-s Refreshes shelves in sequential order (use single drive to

refresh media). This allows to limit drive resource usage during magazine import.

-P Refresh procedure will use physical refresh (not use bar

code media database). This option required for correct changing of "Write Protect" media status.

of 180

-m Differential refresh procedure will use magazine ID

media database (without physical refresh). By default the vlmagazine command will physical refresh all media found in the magazine. If magazine supports some form of the magazine identification (like RFID) the vlmagazine command with -m option may recover media status using VL media database. Note that vlmagazine will check that all media are in the expected positions (as it was before magazine export). The differential checking verifies only media positions which were changed. If new media is added in the empty slot it will be refreshed. If media was removed from the slot it will be declared Offline in the VL database. Obviously there is no guarantee that media in full slots was not replaced.

-c Strict refresh - the same as -m, but if media positions

mismatch the assumption is made that content of the magazine cannot be trusted and full physical refresh will be performed. During the strict checking all positions in the magazine are verified. Because there are no specific possibility to verify that user did not manually changed media positions, the verification code shall include at least check that all full slots during export are full during import and empty slots are still empty. If this verification is not passing the message in syslog shall be logged (the media in imported magazine ID=.xxxxx. positions changed. Performing full magazine refresh).

EXAMPLES

vlmagazine jb

of 180

VLMEDIAUSAGE NAME

vlmediausage - Analyses media usage within in a Integral Volume set.

SYNOPSIS

vlmediausage [-H host_name] set_name

DESCRIPTION

The vlmediausage command analyses media usage for the Integral Volume set ‘set_name’ and prints statistics on how much up-to-date data is present on each medium in the Integral Volume set. It also lists up to 5 media which contain more “dead” (unused) space and estimate how much time it would take to relocate all data to different media. (see vlreuse command).

OPTIONS


EXAMPLES

vlmediausage alpha Analyses media usage for the Integral Volume set alpha.

of 180

VLMICDB NAME vlmicdb - View and modify multiple incremental copy (MiC) database. SYNOPSIS vlmicdb [-H host_name][-v][-n][-f][-m]{-c|{-e|-i|-s0|-s1|-s2}

volume[.replica]} set_name DESCRIPTION

The vlmicdb command views and modifies MiC database. This database is used by the software for multiple incremental copy operations and for synchronization of the replicas of TDO mirror Integral Volume set. The command work in both case with the Integral Volume set mounted or unmounted. Database is in XML format and can be read by third-party applications directly.

OPTIONS


-v Verbose messages

-f Integral Volume set database offline mode. This parameter

needed by user application to begin direct database modification. Any database modification by other application disabled!

-n Set database online mode. This parameter needed by user

application to finish direct database modification

-i volume[.replica] Unlink destination volume from source volume. Used for MiC operation.

-e volume[.replica]

Clear error volume status when error's reason was fixed.

-m Clear email sending flag. This flag needed to decrease repeative messages sent by mail to operator.

-c Clear error status for all volumes.

-s0 volume[.replica]

Set OFF synchronization status for given volume. Used for TDO mirror synchronization.

of 180

-s1 volume[.replica] Set ON synchronization status for given volume. Used for TDO mirror synchronization.

-s2 volume[.replica]

Set DONE synchronization status for given volume. Used for TDO mirror synchronization.

EXAMPLES

vlmicdb alpha Show current TDO mirror synchronization status: VOL COPY REPLICA POSITION STATUS SYNC ---- ---- ----------- -------- --------- ---- 0.0 #1 jb_sdk:1a 34M open on 1 #2 jb_sdk:2a 34M open

Show current multiple incremental copy status:

VOL SOURCE POSITION STATUS REPLICA POSITION STATUS DATA TO COPY --- ------ -------- ------ ------- -------- ------ ------------ 0 jb_stp:1a 256M on jb_s:4a 123M open 64M 1 jb_stp:2a on 2 jb_stp:3a on jb_s:5a error

of 180

VLMICOPY NAME vlmicopy - Initiate Multiple Incremental Copy (MiC) operation. SYNOPSIS

vlmicopy [-H host_name] [-v] set_name DESCRIPTION

The vlmicopy command starts Multiple incremental Copy (MiC) operation for the Integral Volume sets specified by set_name. The operation used for SDF/TDO/UDF set with defined incremental copy job. For TDO mirror Integral Volume set this command initiates synchronization process. The command work in both case with the Integral Volume set mounted or unmounted and waits while operation will be finished.

OPTIONS -H host_name

Specifies the name of the host where the Integral Volume set resides. Without this option, the local host is used.

-v Verbose messages initiated. EXAMPLES

vlmicopy alpha Starts incremental copy or volume syncronization operation for the Integral Volume set 'alpha'.

of 180

VLMVSET NAME

vlmvset - Renames an Integral Volume set. SYNOPSIS

vlmvset [-H host_name] set_name new_set_name DESCRIPTION

The vlmvset command renames sets. The set is specified by the set_name argument. The vlmvset command changes the name of the set to the new_set_name. This command is not available for sets that are part of a Mirrored set.

OPTIONS


EXAMPLES

vlmvset alpha beta Renames the set "alpha" to "beta" in the VL database.

of 180

VLPING NAME

vlping – Checks to see if the vlserver is running. SYNOPSIS

vlping [-H host_name] DESCRIPTION

The vlping command checks to see if the vlserver is running. OPTIONS


EXAMPLES

vlping vlping: VL server thread is running.

of 180

VLPROXY NAME

vlproxy - Manages proxy devices and Integral Volume sets. SYNOPSIS

vlproxy [-H host_name] -b device_name [shelf_number]

vlproxy [-H host_name] -c set_name DESCRIPTION

The vlproxy command allows to handle proxy devices and Integral Volume sets. A proxy device is a simulated library created by jbsim -p command with the valid proxy device name (proxy1, proxy2, ..., proxy31). A proxy Integral Volume set is an Integral Volume set that can contain proxy media.


Specify the name of the host where the proxy library or Integral Volume set resides. Without this option, the local host is used.

-b Make proxy media blank and available for add to an Integral

Volume set. The proxy library is specified by device_name. If shelf_number is specified, the option applies to this shelf only, otherwise to all shelves in the library. If the shelf belongs to an Integral Volume set, it cannot be made blank. This option can be used after the Integral Volume set containing proxy media was deleted and now those media should be made available (blank and writable).

-c Force the system to check if there is available destination

media for the Integral Volume set specified by set_name. This option can be used if the copy of complete proxy media from the Integral Volume set stopped because there was no available destination media and now the available media appear. If there are proxy media awaiting for destination media the copy will start.

of 180

VLQLIST NAME

vlqlist – Prints the delayed job queue. SYNOPSIS

vlqlist [-H host_name] [-j [a][d][c][m][r][e][A][i][o][s][t]] [-s [w][s][d][e]] [-l][-h sender_hostname] [-u user_id]

DESCRIPTION

The vlqlist command prints delayed job queue obtained from the QStar scheduler daemon.

OPTIONS


-j [d][c][m][r][e][g][A][i][o][a] The –j flag allows for specific job type filters to be used. Multiple filters may be used together on the same command line. d - Displays only vlrecord jobs. c - Displays only vlcopy jobs. m – Displays only vlcmp jobs. r - Displays only vlreuse jobs. e - Displays only vlerase jobs. A - Displays only mmarc jobs. a – Displays all jobs type. i - Displays only incremental copy jobs. o - Displays only off-line SDF mirror synchronization jobs. t - queue convert, ex. SDF to TDO s - queue script for cron

-s [w][s][d][e] The -s flag allows for specific job state filters to be used. Multiple filters may be used together on the same command line. w - Displays all jobs waiting for execution. s - Displays all jobs that have started. d - Displays all jobs that have completed without error. e - Displays all jobs that have completed with error.

-h sender_hostname Displays all records that came from the host specified by sender_hostname

-u user_id Displays all records that originated from the user specified by user_id.

-l Outputs in long format.

of 180

VLQMOVE NAME

vlqmove – Moves records in the delayed job queue list. SYNOPSIS

vlqmove [-H host_name] job_id1 [after] job_id2 DESCRIPTION

The vlqmove command moves job records within the QStar scheduler daemon’s queue list. By default, this command moves job_id1 ahead of job_id2.

OPTIONS


[after]

Specifies that job_id1 should be placed after job_id2. EXAMPLES

vlqmove 1 3

of 180

VLQREMOVE NAME

vlqremove – Removes records in the delayed job queue list. SYNOPSIS

vlqremove [-H host_name] job_id DESCRIPTION

The vlqremove command removes a job record specified by job_id from the QStar scheduler daemon’s queue list. This command can be used to clear completed, completed with error, and unwanted incomplete records.

OPTIONS


EXAMPLES

vlqremove 1

of 180

VLRECORD NAME

vlrecord - Records an ISO/UDF image to a media. SYNOPSIS

vlrecord [-H host_name] [-v] [-x {speed_X|max}] [-b buffer_Mb][{-t

|-T}] [-s set_name] [-j delayed_job_name] [-d {[mmdd]HHMM|[cc]yymmddHHMM}] [-nnumber_of_copies] [-V] [-m mail_addr] [-p {cd-r | cd-rw | dvd-r|dvd-ram|dvd-rw|dvd-rw-s|mo|mo-worm|udo|udo2|dvdram|dvd-r|cd-r|bd-re| bd-rs} device_name: {shelf_number{a|b}|any} [image_path]

DESCRIPTION

The vlrecord command records an ISO/UDF image to a media. The media is specified by the device_name:shelf_number argument. If “any” is specified instead of a shelf number then the 1st available blank in the storage device will be used. The image location and name is specified by the image_path argument.

OPTIONS


-v Verbose output.

-x [speed_X | max]

Specifies recording speed. Without this option the recording speed is selected automatically based on the memory buffer filling time.

-b buffer_Mb

Specifies memory buffer size used for recording. The default value is 4 Mb.

-t Test mode. When the Test mode is specified, the

software and CD/DVD-R drive simulate the write process. The CD/DVD-R drive does not actually write data to the media as the Laser power is turned off.

-T Test mode with no write operations. This mode is used

to determine the data transfer rate. -V Specifies verification mode. The vlrecord command

reads data back and compares with the source image.

of 180

-p Sets media type of the media will be used for recording. -s set_name

Specifies the Integral Volume set name to which the newly written media will be automatically added.

-j delayed_job_name

Specifies the job name used to identify the job in the delayed job list. Without the -j flag the job will be executed according to the -d flag (without the -d flag,the job will execute immediately).


Specifies the date and time the jobs should be executed on the delayed jobs list. The job will be executed immediately if there is no -j flag and no -d flag. If there is a -j flag and there is no -d flag the job will be executed according to the "RECORD Delayed Start" field in the vl/files/conf file. Note - the -d flag is only usuable by the superuser.



-n number_of_copies

Specifies the number of copies of the same ISO/UDF image that will be recorded to CD/DVD-R media. Without this option only one ISO/UDF image will be recorded.

-m mail_addr

Specifies the email address to which confirmation is sent when the job has completed.

NOTES

Recording is a long process, QStar suggests using the –v (verbose output to terminal) option to track the progress of the recording.

EXAMPLES

vlrecord jb1:5 image_path Records the image from image_path file to the disk on shelf 5 in library#1.

of 180

VLREFRESH NAME

vlrefresh - Refreshes media, library (es) and standalone drive(s) and fixes the VL database.

SYNOPSIS

vlrefresh [-H host_name] [-sBoF] device_name shelf_number ...

vlrefresh [-H host_name] [-sBF] device_name shelf_number:shelf_number

vlrefresh [-H host_name] [-sBF] device_name

vlrefresh [-H host_name] [-sBF] -f DESCRIPTION

The vlrefresh command refreshes VL database information and fixes the VL database. Refreshing means reading information from the media (if the media is present) and updating the relevant VL database records.

The first form of the command refreshes the list of shelves. The library is specified by the device_name argument.

The second form of the command refreshes all shelves in the range specified by the shelf_number:shelf_number argument. The library is specified by the device_name argument.

The third form of the command refreshes the device which may be a library or a standalone drive. In case of a library it refreshes all the shelves in the library. The device is specified by the device_name argument.

The fourth form of the command refreshes all devices and fixes inconsistencies in the VL databases.

Unlike the previous version, the vlrefresh command does not maintain any kind of dialog with the user for creating new sets. After the device is refreshed, the vllsdev, vlcrset and vladdtoset commands can be used to register in the VL database the media containing set identification. The sequence of actions is normally as follows. The vllsdev command with the -i option lists media which contain set identification but does not belong to a set. The vlcrset command can be used to create an empty set. Then the vladdtoset command, with arguments containing the set name and one of the shelves with set identification to adds media on the specified shelf and all other media with the same Set_ID.

of 180

OPTIONS


-f Refreshes and fixes all.

-s Refreshes the device in sequential order.

-B Refresh procedure will use bar code media database

instead of physical refresh. -o Refresh procedure will attempt to unlock media in the

drive to perform refresh if no free drives are available.

-F Refresh procedure will be executed for full medium and

required long time. For example, TDO can find last write position and set finalization flag.

EXAMPLES

vlrefresh jb 3 Refreshes shelf number 3 of the library specified by the jb VL name.

vlrefresh jb

Refreshes the entire library.

of 180

VLREPLACE NAME

vlreplace - Replaces a media in a Mirrored Integral Volume set. SYNOPSIS

vlreplace [-H host_name] dev_name:shelf_number [repl_dev_name:[repl_shelf_number]] DESCRIPTION

The vlreplace command is a specific Data Director (Mirroring) command, it finds specified media in a Integral Volume set, removes the media from the set, initializes new media and adds new media into the set in place of the removed one. This command can be useful for Mirrored Integral Volume set in case of failure during the hot-sync procedure. It allows replacement of "bad" media in the set a with new one and resumes hot-syncing. The command should not be used for regular Integral Volume sets.

OPTIONS


dev_name:shelf_number

Identifies the media to be removed from the set.

repl_dev_name:repl_shelf_number Identifies the media to be inserted to the set. If repl_shelf_number is omitted the software selects shelf automatically on repl_dev_name. If repl_dev_name is also omitted the software selects a shelf automatically from all devices.

EXAMPLES

vlreplace jb:1 jb:11 Substitutes the media from shelf 1 in the set with shelf 11.

of 180

VLREPLICA NAME vlreplica - Handle replication Integral Volume sets. SYNOPSIS vlreplica -f {on | off | out | in | read} set_name replica_index

vlreplica -c [-LRV] [-b bad_replica_index] [-t time_limit] start set_name [rel_path]

vlreplica -c stop set_name

vlreplica -s [-L] [-O {size,mtime,keep,streams}] [-b bad_replica_index] [-t time_limit] start set_name

vlreplica -s stop set_name vlreplica -h [-L] [-O {size,mtime,keep,streams}] [-b bad_replica_index] [-t time_limit] start set_name vlreplica -h stop set_name vlreplica -S set_name DESCRIPTION

The vlreplica command allows to handle replication Integral Volume sets. The following terms are used:

replica

One of underlying Integral Volume sets. Write operations are performed on all replicas which are online and in sync.

online replica

Replica which belongs to the replication Integral Volume set and is online from VL point of view.

offline replica

Replica which belongs to the replication Integral Volume set and is offline from VL point of view.

in sync replica Online replica which is used in the replication operations. out of sync replica

Online replica which is not used in the replication operations. It can become in sync as a result of the sync process.

read replica

Replica which is used to read directories or file data. If the read replica gets offline or out of sync, the next online and in sync replica becomes read replica.

of 180

replication Id

A character string of the following type: "RPL.hostid.microseconds" which identifies replicas belonging to the same replication Integral Volume set. "hostid" and "microseconds" are sequences of hex characters. When a replica without a replication Id is added to the replication Integral Volume set, a replication Id of the set is written into the "q_set_features" stream of the replica's root directory.

sync

Process of synchronizing an online and in sync replica (good replica) with all or selected online but out of sync replicas (bad replicas). The sync process is done when the contents of the bad replicas match the contents of the good replica.

good/bad replica

Replica used in the sync process. The notions of good and bad replicas exist only while the sync process is in progress. The read replica is used as good replica. After the out of sync replica was successfully synced, it becomes in sync.

hot sync Sync process on the mounted replication Integral Volume set. cold sync

Sync process on the unmounted replication Integral Volume set. ADD TO REPLICATION INTEGRAL VOLUME SET

When a replica is added to the replication Integral Volume set, an attempt is made to read its replication Id.

Add a first replica to replication Integral Volume set

If the replication Id in the replica exists, it becomes the replication Id of the replication Integral Volume set. If it does not exist, a new unique replication Id is written to the replica and becomes the replication Id of the replication Integral Volume set. The first replica in the Integral Volume set is marked online and in sync.

Add a non-first replica to replication Integral Volume set

If the replication Id in the replica exists, it must match the replication Id of the replication Integral Volume set. If it does not exist, the replication Id of the replication Integral Volume set is written into the replica. The replica is marked online. The replica is marked in sync only if this replica and the "read replica" of the replication Integral Volume set are both empty. Otherwise, the replica is marked out of sync.

To make a non-first replica in sync, a cold or hot sync operation must be performed on the replication Integral Volume set.

of 180

OPTIONS

-f on Forces the replica to be online in the replication Integral Volume set. The replication Integral Volume set is specified by set_name, the replica is specified by replica_index.

-f off Forces the replica to be offline in the replication Integral

Volume set. The replication Integral Volume set is specified by set_name, the replica is specified by replica_index.

-f out Forces the replica to be out of sync in the replication

Integral Volume set. The replication Integral Volume set is specified by set_name, the replica is specified by replica_index.

-f in Forces the replica to be in sync in the replication Integral

Volume set. The replication Integral Volume set is specified by set_name, the replica is specified by replica_index. The replica must be out of sync, there should be no other in sync replica in the Integral Volume set and the Integral Volume set must be unmounted. This should not be used under normal conditions because the replica becomes in sync as a result of the successful synchronization.

-f read Forces the replica to be a read replica in the replication

Integral Volume set. The replication Integral Volume set is specified by set_name, the replica is specified by replica_index.

-c start

Start a comparison process. Without -b option, all online and out of sync replicas are considered bad replicas and used in the comparison process. The -b option can be used to specify a bad replica: a good replica is compared with this bad replica only. If rel_path is present, comparison starts not from the Integral Volume set root directory but from the path specified (rel_path is relative to the set root). The Integral Volume set is specified by set_name, The Integral Volume set must be unmounted. The report goes to <set_name>_rpl_sync_report file. If the comparison finds no differences, the bad replica is marked in sync.

-c stop

Stops the comparison process. The Integral Volume set is specified by set_name.

-s start

Start a cold sync process. Without -b option, all online and out of sync replicas are considered bad replicas and used in the sync process. The -b option can be used to specify a bad replica: a good replica is synchronized with this bad replica only. The Integral Volume set is specified by set_name, The Integral Volume set must be unmounted.

of 180

-s stop

Stops the cold sync process. The set is specified by set_name, The cold sync process is interrupted and bad replicas are left out of sync.

-h start

Start a hot sync process. Without -b option, all online and out of sync replicas are considered bad replicas and used in the sync process. The -b option can be used to specify a bad replica: a good replica is synchronized with this bad replica only. During the hot sync process the Integral Volume set remains mounted and all operations with MCFS proceed.

-h stop

Stops the hot sync process. The Integral Volume set is specified by set_name, The hot sync process is interrupted and bad replicas are left out of sync.

-L Logs synchronization operations in <set_name>_rpl_sync_log File

-R Specifies that regular files contents is used in comparison operations. By default, regular files contents is not compared.

-V Verbose, used with "-c start". Pathnames of the files compared printed in the report.

-O {mtime,check,keepf,keeps}

Specifies the list of comma separated words which allow to control cold or hot sync:

mtime Copy file if it has the same size in both good and bad replicas but its modification time in the good replica is greater than its modification time in the bad replica. By default, if the size is the same, the modification time is not checked and such file is not copied.

check

This option affects the file which is not copied because of its size or modification time. The option forces the sync procedure to compare the contents of the file in good and bad replicas and copy file if they differ.

keepf

Do not remove the file from the bad replica if it does not exist in the good replica. By default, such file is removed.

keeps

Do not remove the stream from the bad replica if it does not exist in the good replica. By default, such stream is removed if the word "keep" is not used.

-b bad_replica_index

Forces vlreplica to use a replica with this index as bad replica.

of 180

-t time_limit

Limits the duration of the comparison, cold sync, or hot sync: after the time limit expires, it works like "-c stop". The time_limit synopsis is the same as for grace/retention period in vlcache command.

-S Prints status of the replication Integral Volume set including

information on hot/cold sync. The Integral Volume set is specified by set_name and can be mounted or unmounted.

REPLICATION SYNC

Replicas which are not online and in sync do not participate in archiving. For each such replica the replication migrator maintains a track information which registers files and operations involved in archiving. A track information is stored in the cache directory associated with the replication Integral Volume set and is used in the cold or hot synchronization procedure.

The track information consists of the following files (the name of each of them ends with _N, where N is the replica number within the replication Integral Volume set):

track file

A text file which name is rpl_track_N. A special line (sync line) is put into the track file on each migrator sync. A synchronization procedure works step by step, each step starts on the sync line.

track position file

A text file which name is rpl_track_position_N. A track position file contains the position in the track file i.e. the byte offset from the beginning of the track file. The position marks the line in the track file from which the next step of synchronization will start. A position is written in the track position file every time the synchronization procedure reaches a sync line. If the synchronization procedure crashed or was cancelled, next time it will start from the sync line whose position was stored in the track position file.

track root directory

A directory which name is rpl_track_root_N. Under this directory the synchronization procedure creates a tree of files (names only) which are involved in the current synchronization step. At the end of the step all files that were synchronized are removed from that tree.

The track information related to a particular replica is removed once the replica is synchronized.

There are two modes of synchronization. One that described above uses the track information and synchronizes only the files listed in the track. Another one is employed if the track information is missing. In this case the synchronization procedure traverses both replicas and makes the bad replica looks like the good one.

of 180

VLRESTORE_FSDB NAME

vlrestore_fsdb – Recreates filesystem databases. SYNOPSIS

vlrestore_fsdb [-H host_name] [-D {UDF_span_number|+}[:to_span_number]]

[-c fsdb_cache_root] set_name vlrestore_fsdb [-H host_name] [-D volume_number] [-t [mmdd]HHMM |

[cc]yymmddHHMM] SDF_TDO_set_name vlrestore_fsdb [-H host_name] [-v] [-f] [{-L | -Q}] [-D AAFS_seq_number_from

[:AAFS_seq_number_to]] set_name vlrestore_fsdb [-H host_name] [-D{LTFS_span_number|+}[:to_span_number]]

[-c fsdb_cache_root] set_name

DESCRIPTION

The vlrestore_fsdb command recreates filesystem specific databases for Integral Volume set “set_name” in the cache directory assigned to the Integral Volume set. Currently fs databases exist only for UDF spanning, SDF, TDO, AAFS and LTFS filesystems. The databases are restored from media belonging to the Integral Volume set. Note that if fs databases already exist in the cache directory they are removed

OPTIONS


-D UDF_db_span_number or SDF_TDO_volume_number or AAFS_seq_number or LTFS_span_number

For UDF Integtal Volume sets. Specifies the span number of the surface which must be used for restoring a spanning database. Without this option the database will be restored from the last surface in the Integral Volume set. If this number is "+", a spanning database will be incrementally built (data from volumes not represented in the existing database will be added to it). If :to_span_number is present, building of spanning database will be stopped after the volume with to_span_number is processed. For SDF or TDO Integral Volume sets. Specifies the SDF or TDO volume number (starting from 1) which must be used for restoring SDF or TDO database. Without this option (or if volume number is equal to 0) the SDF or TDO database will be restored from the last surface in the Integral Volume set. The database will be restored from specified volume and SDF or TDO events will be

of 180

replayed from that medium. The saved database on the next volume will not be used to restore database. Rather the data portion of the SDF or TDO volume will be scanned and events replayed. This process continues until last medium (surface) in the set is scanned. The mirrored SDF or TDO volume set restore with this option is not supported.

For AAFS Integral Volume sets. Specifies the AAFS from (and to) Id number(s) of the surface from vllsdev list (or sequence number from vllsset list) which must be used for restoring AAFS database. For LTFS Integral Volume sets. Specifies the span number of the surface which must be used for restoring a spanning database. Without this option the database will be restored from the last surface in the Integral Volume set. If this number is "+", a spanning database will be incrementally built (data from volumes not represented in the existing database will be added to it). If :to_span_number is present, building of spanning database will be stopped after the volume with to_span_number is processed.

-cfsdb_cache_root

Building of the spanning database is made in fsdb_cache_root instead of the cache directory assigned to the Integral Volume set. This allows to rebuild a database while the Integral Volume set is mounted.

-v Verbose output to log file in cache (For AAFS sets only). -f AAFS: force restoring, even if database exists.

-L | -Q

Restoring type: L(ong) - scanning data on disk, Q(uick) - scanning DB on disk. Without this option: Quick, if DB exist, else Long. (For AAFS sets only)

EXIT CODES

The command fails if the specified Integral Volume set is in a mounted state.

EXAMPLES

vlrestore_fsdb alpha

of 180

VLREUSE NAME

vlreuse – Relocates data, erases the media and adds it to the Integral Volume set.

SYNOPSIS

vlreuse [-H host_name] [-r] [-j {delayed_job_name | "default"}] [-d {[mmdd]HHMM | [cc]yymmddHHMM}][-p {cache size to used}] set_name in_set_number...

DESCRIPTION

The vlreuse command relocates up-to-date data from a specified media ('in_set_number' in set 'set_name') to current write position. After successful relocation the media is erased and added to the Integral Volume set. As a result available space for the Integral Volume set is increased. More than one in_set_number maybe specified for the same command.

OPTIONS


-r Specifies relocation only mode. After successful

completion of the command the media may be exported from library (for backup purposes) or erased and added to the same or different Integral Volume set.

-j delayed_job_name

Specifies the job name used to identify the job in the delayed job list. If the delayed_job_name is the key word "default", the actual job name will be generated automatically. Without the -j flag the job will be executed according to the -d flag (without the -d flag, the job will execute immediately).


Specifies the date and time the jobs should be executed on the delayed jobs list. The job will be executed immediately if there is no -j flag and no -d flag. If there is a -j flag and there is no -d flag the job will be executed according to the "REUSE Delayed Start" field in the vl/files/conf file. Note - the -d flag is only usable by the superuser.

of 180



EXIT CODES

The command is available for any multi-volume file system, however, it will fail if the specified set is using a SDF or TDO file system and it is in a mounted state. UDF spanning will work in mounted or unmounted states. It may also fail if there is not enough space for the reallocated data.

The command returns the exit code 0 in the case of a successful completion. Otherwise, a positive non-zero error code is returned (see error codes in libqcommon(3), libqscsi(3), libjb(3) and libvl(3)) and an error message is printed to stderr.

EXAMPLES

vlreuse alpha 0 Relocates data from the media with in_set_number="0" belonging to the Integral Volume set "alpha" and then erases the media with in_set_number="0" and adds it to the end of Integral Volume set "alpha".

vlreuse -r alpha 0

Relocates data from the media with in_set_number="0" belonging to the Integral Volume set "alpha". The media is not erased and there is no actual data on the media, but it still belongs to the Integral Volume set.

vlreuse -j "Reuse volume #1" beta 1

This command creates a delayed job. The job will be executed according to the "REUSE Delayed Start" field in the vl/files/conf file.

vlreuse -j "Reuse volume #1" -d 1330 beta 1

The same as above but the job will be executed at 1:30 PM. "REUSE Delayed Start" field in the vl/files/conf file makes no difference if -d is specified.

of 180

VLSCHED NAME

vlsched - Provides generic job scheduling support. SYNOPSIS

vlsched [-H host_name] -p excutable_file_path -s cron_like_scheduler -j scheduled_job_name [-u argument0 . argumentN] DESCRIPTION

The vlsched command provides possibility to schedule execution of the QStar or any other executable program (including shell scripts) using CRON-like scheduled.


Specifies the name of the host where the command execution shall occur. Without this option, the local host is used.

-p executable_file_path

The mandatory -p flag allows to specify absolute path to the executable file. The software will check that it is regular file with at least one of the "executable" bits set.

-s cron_like_schedule

Cron schedule: Minute Hour Day Month Weekday. For more detailed information about the syntax, please refer to the crontab man pages. Note that vlsched is supported for Windows systems also.

-j scheduled_job_name

Specifies the job name used to identify the job in the delayed job list.

argument0 ... argumentN

A space separated list of the arguments required for the scheduled executable. A special care need taken to be to properly escape special characters. For example, if argument0 starts with "-" it needs to be escaped. vlsched -p /opt/QStar/sdf/etc/qms -s "50 3 * * *" -j "bk_Recycle" "\-s /bk -y -r".

In this example there are four arguments for the executable to proceed: "-s" "/bk" "-y" and "-r". Without escaping "-s" option the argument may be captured by the vlsched command itself rather then by the scheduled task.

of 180

EXECUTION ENVIRONMENT

The CRON job will be started with stderr and stdout redirected to the file /opt/QStar/log/ [job_name]_job_log.txt. The file name will contain job name and therefore job name should be compatible with file system limitations. Stdin will be redirected to the NULL device.

Before job start and after its completion there will be time stamp written to the log:

---Job [KeyDB Backup] started at Fri Jun 19 14:50:00 2009 --- *** Here goes output of the job execution *** ---Job [KeyDB Backup] finished at Fri Jun 19 14:50:00 2009 ---

In between of those lines the output and errors printed by the executable will be logged.

The log file will grow up to QStar log file size (4 MB) and will rotate through [job_name]_job_log_old.txt file.

In Windows the executable will be executed using privileges of the "qserver" which by default is "SYSTEM".

TERMINATING SCHEDULED JOB

The scheduled job may be listed using vlqlist command. The CRON jobs are marked as CronJob.

For example, 1 2009/06/19_16:20 KeyDB Backup CronJob Waiting For Time 0: 2009/06/19_16:25 2009/06/19_16:25

The scheduled job may be terminated using vlqremove command. NOTE: The QStar scheduler is not working if QStar servers are not started. EXAMPLES

vlsched -p /opt/QStar/sdf/etc/qms -s "50 3 * * *" -j "bk_Recycle"

"\-s /bk -y -r"

In this example the "qms" executable located in the /opt/QStar/sdf/etc/qms will be scheduled to run at 03:50 every night. The job name is "bk_Recycle" and the four arguments will be provided for the "qms" executable. "-s " and "/bk" defines source directory, "-y" specifies to remove expired files and "-r" specifies to recycle media which does not contain live data anymore.

of 180

VLSDF2TDO NAME vlsdf2tdo - Converts SDF Integral Volume set to TDO type. SYNOPSIS vlsdf2tdo [-H host_name] [-r] [-b] set_name DESCRIPTION

The vlsdf2tdo command converts SDF Integral Volume set 'set_name' to TDO in the place. The Integral Volume set must be unmounted. All SDF media will be moved to new TDO Integral Volume set and will be available in read only mode. SDF database will be converted to TDO database. The operation duration depends from SDF database size (entry number, file size, ...). Mirror SDF Integral Volume set will be converted to mirror TDO Integral Volume set.

OPTIONS


-r Force SDF database restore from media before conversion.

-b The operation will be executed in background mode.

EXAMPLES

vlsdf2tdo alpha

Converts SDF Integral Volume set 'alpha' to TDO Integral Volume set 'alpha'. All media will be added into new Integral Volume set. The cache will have the same parameters and location.

of 180

VLVERIFY NAME

vlverify – Checks the consistency of the VL database. SYNOPSIS

vlverify [-H host_name] DESCRIPTION

The vlverify command verifies the consistency of the VL databases and reports inconsistencies.

OPTIONS


EXAMPLES vlverify Verifies any inconsistencies in the VL databases.

of 180

SCSI CONFIGURATION WORKSHEET First SCSI Host adapter (Already configured) TARGET ID UNIT # (LUN) Inquiry information or Product Identification (PID) Comment 0 1 2 3 4 5 6 Second SCSI Host adapter (Jukebox or standalone drive(s) add to the system) TARGET ID UNIT # (LUN) Inquiry information or Product Identification (PID) Comment 0 1 2 3 4 5 6 HOST ID Number: LICENSE KEY Number :

CREDIT AND TRADEMARK This document contains information protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of QStar Technologies, Inc. The information contained in this document is subject to change without notice. QStar makes no warranty of any kind with regard to this printed material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. QStar shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. The contents of this manual are based on the most current information. Specifications are subject to change without notice. Additions and corrections to this manual will be available from QStar Technologies, Inc., by request, as they become available. This manual contains confidential and proprietary information of QStar Technologies, Inc. Distributing or photocopying this manual is in direct violation of US. copyright laws and is strictly prohibited without the express written consent of QStar Technologies. Should you have questions regarding any QStar product, please contact QStar Technologies Inc., 8738 Ortega Park Drive Navarre, FL 32566 USA or by telephone at (850) 243-0900, fax at (850) 243-4234, or e-mail at [email protected]. RESTRICTIVE RIGHTS NOTICE The computer software and documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to the restrictions stated in paragraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause 252.227-7013 (DFARS) and the Commercial Computer Software Restricted Rights clause 52.227-19 (FAR), whichever is applicable. Contractor/Manufacturer is QStar Technologies Inc., 8738 Ortega Park Drive Navarre, FL 32566 USA. Unpublished - Rights reserved under the copyright laws of the United States and of other countries.

Copyright 1995-2012 by QStar Technologies, Inc. All Rights Reserved

QStar Technologies is a registered trademark of QStar Technologies, Inc. Product names mentioned herein may be trademarks and/or registered

trademarks of their respective companies.

LIMITED WARRANTY ON MEDIA AND MANUAL QStar Technologies, Inc. warrants that the manual accompanying this software product and the physical media on which the software is furnished are free from defects in their production. QStar Technologies, Inc. will replace said media and / or manuals, if defective, if they are returned to QStar Technologies, Inc. postage prepaid, along with proof of purchase. The warranty and remedies set forth above are exclusive and in lieu of all others, oral or written, express or implied. No QStar Technologies, Inc. dealer, agent or employee is authorized to make any modification, extension, or addition to this warranty. This warranty gives you specific legal rights, and you may have additional rights, which may vary from state to state. DISCLAIMERS OF WARRANTY Even though QStar Technologies Inc. has tested the software and reviewed the documentation, QStar Technologies, Inc. makes no warranty or representation, either express or implied, with respect to this software, its quality, performance, merchantability, or fitness for a particular purpose, with the exception of the limited warranty on media and manual expressed above. As a result, this software is sold as is, and you the purchaser are assuming the entire risk as to its quality and performance. In no event will QStar Technologies, Inc. be liable for direct, indirect, special, incidental, or consequential damages resulting from any defect in the software or its documentation. In particular, QStar Technologies, Inc. shall have no liability for any damage to programs or data used with QStar Technologies Inc. products, including the costs of recovering such programs or data. The warranty and remedies set forth above are exclusive and lieu of all others, oral or written, express or implied. US GOVERNMENT RESTRICTED RIGHT LEGEND Use, duplication or disclosure of the QStar Technologies, Inc. software by any unit or agency of the United States Government (the “Government”) id subject to the restrictions set forth in FAR 52.227-19 (c ) (2), the Rights in Technical Data and Computer Software clause of DFARS 252.227-7013 ( c ) (1) (ii), and any similar or successor clauses in the FAR, DFARS, or the DoD or NASA FAR Supplements, whichever are applicable. In addition to the foregoing, the Government agrees to be bound and abide by the terms and conditions set forth in the following license agreement. Unpublished – all rights reserved under the copyright laws of the United States. Contractor/manufacturer is QStar Technologies Inc., 8738 Ortega Park Drive Navarre, FL 32566 USA.

Copyright 2012 QStar Technologies, Inc. All rights reserved

[email protected]@qstar.it

www.qstar.com

QStar Technologies, Inc.Corporate Headquarters8738 Ortega Park DriveNavarre, FL 32566Tel (850) 243 - 0900Fax (850) 243 - 4234

QStar QStar Technologies EuropeViale Italia, 1220094 Corsico, Milano - ItalyTel + 39 02451711Fax +39 0245101745

QStar Technologies JapanShinjuku Park Tower N30F3-7-1 Nishi-Shinjuku, Shinjuku-ku3-7-1 Nishi-Shinjuku, Shinjuku-kuTokyo, 163-1030 Japan

05. q star system_administrator's_guide_windows_v6.0_rev.07

Documents

qstar product

qstar license agreement

qstar software license

license fee

proof of license

sealed software packages

email support

japan email