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) QStar Technologies Japan

2175 West HWY 98 Shinjuku Park Tower N30F

Mary Esther, FL 32569 3-7-1 Nishi Shinjuku, Shinjuku-ku
Tel: +1-850-243-0900 Tokyo 163-1030 Japan
Fax: +1-850-243-4234 E-mail: [email protected]
E-mail: [email protected] Web URL: http://www.qstar.com/
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/

GERMANY
Am Katzenstadel 10
86152 Augsburg
Phone: +49 821 2287747
e-mail: [email protected]
Web URL: http://www.qstar.com/

UNITED KINGDOM
1 Berkeley Street
London
WIJ 8DJ - England
Tel +44(0) 207 016 9840
Fax +44(0) 207 016 9100
E-mail: [email protected]
Web URL: 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, 2175 West HWY 98, Mary Esther,
FL 32569.

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, 2175 West HWY 98,
Mary Esther, FL 32569.

QStar Technologies is a registered trademark of QStar Technologies, Inc

D-LIC-05-09
5/00
QStar Technologies is the market leader in secure, large-scale client/server STORAGE MANAGEMENT SOFTWARE
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 make the right
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 a class leading product.

QStar’s 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. Client magnetic disks, optical, tape, DVD and CD media, 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, many terabytes of data storage can be accessed
in real time.

With QStar Software, data is automatically and transparently migrated between the different storage media within the logical
disk based on real time access patterns. Data that is frequently accessed is migrated to faster media, while data that is accessed
less frequently is migrated to less costly and more abundant media. QStar Software can represent multiple media as a single
volume, keeping track of the exact location of all files on each medium.

Off-the-shelf software packages for Imaging, CAD/CAM, Document Management, 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................................................................................. 4
CHAPTER SUMMARY.......................................................................................... 5

Page 1 of 6
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 and Windows Vista
• Linux - Redhat - SUSE - Debian - Ubuntu - Mandrake - Gentoo - Fedora

Page 2 of 6
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, CD-ROMs, DVD-ROMs DVD-RAMs
and Blu-ray.

Optical disks, or platters, come in a wide range of sizes and capacities. The most common sizes are the 5 ¼ and 12 inch
varieties. Of these, the media storage size per platter can range from 650 Megabytes to over 60 Gigabytes. Another
distinguishing characteristic is whether the platters are Rewritable, able to be erased and reused, or WORM, Write Once Read
Many.

Tapes also come in many different types. Gigabytes per tape are in the triple digits and varieties include, but aren’t limited to,
AIT, DLT and LTO.

CD-ROM media remains at the 700 Megabytes limit but also boasts the most commonly used media type. Disks can be written
on any platform using a standardized ISO format and moved to any other platform to be read.

DVDs bring the best of two worlds, the commonality over many platforms like CD-ROM and near optical capacities.

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) Read/Write
Tape (DLT - SDLT ) Read/Write
Tape (9730 - 9840 - 9940A - 9940B) 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-RS Read/Write
CENTERA Read/Write
HARD DISK (Simulated Disk/Tape) Read/Write

Page 3 of 6
QSTAR MANUAL REVISION
September 2008 Revision A (Windows and Unix):
Manual for release starting with v5.0.0.

Page 4 of 6
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: JUKEBOX MANAGEMENT

This chapter describes how to manage the jukebox and its components including the media and drives within the jukebox. Also
included are steps to gather jukebox statistics and tune the jukebox 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 jukebox 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:
Windows Version: QSTAR SECURITY
This chapter describes how to set the security for the Integral Volume sets created.

Unix Version: COMMAND REFERENCE

This chapter covers all of the QStar commands available on the Unix platforms, including explanations and command
options.

Chapter Ten (Only for Windows): COMMAND REFERENCE

This chapter covers all of the QStar commands available on the Windows platforms, including explanations and command
options.

Page 5 of 6
Page 6 of 6
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
Copy Disk..................................................................................................... 4
VL Scheduler ................................................................................................ 4
No Media Option............................................................................................ 4
DEVICE MANAGER COMPONENTS........................................................................ 5
QStar “SCSI” Manager ................................................................................... 5
Jukebox Manager .......................................................................................... 5
View Store.................................................................................................... 5
Jukebox 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 Disk/Tape Jukeboxes....................................................................... 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

Page 1 of 14
 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
SDF Enhancements................................................................................... 12
UDF (Universal Disk Format) ......................................................................... 12
UDF Enhancements................................................................................... 12
UVFS - Support for the Plasmon File Systems .................................................. 13
OFS (Optical File System) ............................................................................. 13
MEDIA ORGANIZATION ................................................................................... 13

Page 2 of 14
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.

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, 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.

Page 3 of 14
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.

Copy Disk
The System Administrator can execute a duplication process of the media that has been written to, using the utility called Copy
Disk. The Copy Disk utility is only available from command line. The Copy Disk utility makes an exact duplicate of the
original media in the Integral Volume set that must be removed from the jukebox after the process is complete. If a disk is
damaged, the copied disk can be used to replace the damaged disk. For more information on how to use Copy Disk, please refer
to Chapter 9(Unix)/Chapter 10(Windows) - Command Reference in this manual.

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 jukebox 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.

Page 4 of 14
DEVICE MANAGER COMPONENTS
The term “device” refers to hardware such as standalone drives and jukebox subsystems.
QStar Software can manage one or many standalone drives and jukebox devices on the same system.
These devices can use Optical, Tape, CD/DVD-ROM, CD/DVD-R or DVD-RAM 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.

Jukebox Manager
The JB driver, through the “jbcmd or jb(Unix)” commands, manages the jukebox.
The JB module performs various operations with the jukebox 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 jukebox time control parameters through API
calls.

View Store
Jukebox management software provides a complete application transparent interface to jukeboxes, scheduling the insertion of
particular media into a drive, based on demand for that volume.

Jukebox Statistics
QStar Software provides statistics for the elements within the jukebox. These statistics allow the System Administrator to
monitor for potential problems with the media and drives within the jukebox. 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 jukebox 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
Jukebox Statistics view pane or the jbcmd statistics (jbstatisitics) command line allows jukebox statistic information to be
printed or cleared.

Page 5 of 14
MEDIA MANAGER COMPONENTS
QStar “Volume Librarian” Database
The “VLcmd or VL (Unix)” 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 jukebox 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 jukebox, 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 jukebox.

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 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 file system, 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.

Page 6 of 14
Simulated Disk/Tape Jukeboxes
The QStar Software offers two types of Simulated Jukeboxes, Simulated Disk Jukebox (SDJ) and Simulated Tape Jukebox
(STJ). The Simulated Jukebox 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 Optical disk or Tape 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 or UDF. It is possible to configure a conventional jukebox, with media
such as Tape or Optical in conjunction with a Simulated Jukebox and mirror the data between the two devices. For this,
configure the Simulated Jukebox media to the same capacity and type as the media in the conventional jukebox containing real
media, then using the Data Director product and QStar’s SDF file system, mirror the data between a hard disk (SDJ or STJ) and
an Optical or Tape Jukebox. This configuration allows real time mirroring between a hard disk and an optical or tape jukebox.
The Simulated Jukeboxes configuration may be useful for demonstrating or integration testing with the QStar product or API
when a jukebox is not available.

VL Copy Media
The QStar Software can manually or automatically execute a duplication process of the media (Disk or Tape) 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. 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 jukebox 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.

Page 7 of 14
MIGRATION MANAGER COMPONENTS
Migration Manager
Migration is the movement of data between the magnetic disk partition and the archival media. 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, RAID, Optical, CD, DVD, Blu-ray, Tape drives and jukeboxes. 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 moving 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 one storage medium to another. 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 to 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 to 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.

Page 8 of 14
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(Unix)/Chapter 10(Windows) - 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
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 optical media or other 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.

Page 9 of 14
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 jukebox or for offline media to be reinserted into the storage device
to satisfy a read request.

Mail Notification
The System Administrator can receive mail notification about abnormal events in the QStar software. An abnormal event can
be, for example, a drive/jukebox 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.

Page 10 of 14
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 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 jukeboxes 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.

Page 11 of 14
 SDF Enhancements
Shredding support for UDO Compliance WORM media and Rewritable Optical media has been added. The support is available
with HSM 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

UDF Enhancements
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.

Page 12 of 14
 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

OFS (Optical File System)

The QStar OFS file system has been removed and is no longer supported.

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-terabyte storage solutions.
QStar can configure the jukebox (es) to be seen as one or multiple Virtual Disks.
This partitioning allows a multi-platter jukebox to be logically divided so that the jukebox 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 platters, thereby simplifying back-up 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 jukeboxes in the following configuration of data sets:

Integral Volume (I.V.) Configuration

Use the “vlcmd or vl (Unix)” commands to create and manage an Optical, DVD or Tape media set as an Integral Volume.
This configuration requires a CACHE that manages the migration of the data between the storage media and the Hard Disk.
This configuration is available in SDF, UDF and UVFS 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.

Page 13 of 14
Page 14 of 14
This chapter describes how to get the system up and running.
The Installation program guides you through every step of the process.

Before installing 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 minimize 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 set-up of the
QStar Software.

SYSTEM REQUIREMENTS ....................................................................................... 3

Software Requirements .................................................................................. 3
QStar’s Recommendation for Optimization of the System .................................... 3
The Storage Devices ................................................................................... 3
Improving the Servers Performance .............................................................. 3
Improving File System Performance .............................................................. 4
Protecting Against Data Loss ........................................................................ 5
Installation Considerations........................................................................... 5
Hardware and SCSI Requirements ................................................................... 6
QSTAR SOFTWARE DIRECTORIES ........................................................................... 7
UPGRADING YOUR CURRENT VERSION OF QSTAR SOFTWARE .................................... 8
INSTALLATION STEPS ......................................................................................... 11
Diagram Installation Step ............................................................................. 11
STEP 1: HARDWARE INSTALLATION AND SETUP OF ................................................ 12
DEVICES ........................................................................................................... 12
Step1.1) Determining Available SCSI IDs and Setup of the Storage Device(s) ...... 12
Installed on: Sun Solaris .............................................................................. 12
Step1.2) Determining Available SCSI IDs and Setup of the Storage Device(s) ...... 13
Installed on: IBM AIX ................................................................................... 13
Step1.3) Determining Available SCSI IDs and Setup of the Storage Device(s) ...... 14
Installed on: Linux....................................................................................... 14
Step1.4) Determining Available SCSI IDs and Setup of the Storage Device(s) ...... 15
Installed on: Hewlett Packard HP-UX .............................................................. 15
STEP 2: LOADING THE QSTAR SOFTWARE ON THE.................................................. 16
SYSTEM ............................................................................................................ 16
STEP 3: INSTALLING THE LICENSE KEYS AND ........................................................ 17
REGISTERING THE SOFTWARE ............................................................................. 17
Demo License Key ....................................................................................... 17
Activate the Demo License Key...................................................................... 18
Permanent License Key ................................................................................ 19
Activate the Permanent License Key ............................................................... 20
STEP 4: INSTALLING THE QSTAR SOFTWARE ......................................................... 21
STEP 5: SPECIFYING YOUR STORAGE DEVICE ........................................................ 22
CONFIGURATION................................................................................................ 22
Step 5.1) SUN Solaris, Hewlett Packard HP-UX or Linux ................................. 22
Step 5.2) IBM AIX .................................................................................... 29
STEP 6: RESTORING QSTAR DATABASES ............................................................... 37
STEP 7: COMPILING THE KERNEL, IF APPLICABLE ................................................... 38
STEP 8: POST INSTALLATION TEST....................................................................... 40
RECONFIGURING STORAGE DEVICES .................................................................... 42
ADDING NEW STORAGE DEVICES ......................................................................... 47

Page 1 of 54
DE-INSTALLING QSTAR SOFTWARE ...................................................................... 51
PRIVILEGED USERS ............................................................................................ 53
SEND EMAIL NOTIFICATION................................................................................. 53
START OR STOP QSTAR SERVERS......................................................................... 54

Page 2 of 54
SYSTEM REQUIREMENTS
Below is the minimum configuration required on the host computer before installing QStar products and reconfiguring the
system kernel (only for some platforms).

Software Requirements
Listed below are the minimum system requirements for installing QStar Software on your host.

SOLARIS LINUX AIX HP-UX

Memory : 2 GB 2 GB 2 GB 2 GB
Disk space in /usr partition for Device 100 MB 100 MB 100 MB 100 MB
drivers, file systems, and special device
files:
Disk space on the /root Partition : ------ 10 MB ------ 10 MB
Disk space for QStar Software : 100 MB 100 MB 100 MB 100 MB
Media Drive : CD-ROM/

Note: The space in the /root partition is required to store multiple copies of the kernel image which is created during the
installation of the QStar Software.

Note1: The space on /usr partition is required to accommodate some commands for the QStar Software products.

QStar’s Recommendation for Optimization of the System

• Install as much memory as possible to provide faster data access.
• To improve processing speed, use a processor that is faster than the minimum requirement.
• Space planned on the cache partition for future expansion of cache file system.
• Use a separate SCSI host adapter for the jukebox.
• Additional hard drive space on the main hard disk (or additional hard disks on the server) for better cache utilization.

To achieve the best possible performance from the System that the QStar Software is installed on, the following are
suggested:

The Storage Devices

Appropriate Hardware for Desired Performance
One of the largest decisions to consider when setting up the QStar Software is the device(s) selection. 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 storage library to
maintain optimum performance.

Improving the Servers Performance

All of the following will 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.
• The number of processors and their power.
• The network cabling and configuration.

Page 3 of 54
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 the System and the QStar Software performance.

Numbers 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.

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.

Page 4 of 54
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 you periodically archive the 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 Cron tab.

Media Redundancy
QStar recommends the use of media redundancy for the Integral Volume sets (i.e. Copy Media), if the data is mission-critical.
Disaster recovery time for the QStar file system can be significantly reduced if media redundancy is used. 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 server 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 HSM set. This capability takes away the
potential of data becoming unrecoverable because of a damaged disk and provides for an off-site media copy.

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 jukebox 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 on the system’s activity and required response time. The larger the Integral Volume’s 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 the required drive size.

Page 5 of 54
Hardware and SCSI Requirements
The jukebox or standalone drive that will be connected to your computer via a SCSI (Small Computer System Interface) bus
must comply with these requirements.

1) Every device attached to the SCSI bus must be assigned a unique SCSI ID or “address”.

2) You must determine the combined internal and external length of your cables from your host computer to the end of the
SCSI bus. 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.

We recommend that the length of the SCSI cable from the host computer to the jukebox 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.

3) The number of SCSI IDs that you will need for your storage subsystem depends on the type of device that you are installing.
Ensure you know which drive number in the jukebox corresponds with each SCSI ID.

In the Installation Steps section, we will explain how to find your current SCSI configuration for each platform.

When you have determined what devices are currently attached to your SCSI bus, you can fill in the worksheet in Appendix
“A” and then decide which available SCSI IDs you will use for your jukebox or standalone drive.

In addition, before you begin the installation make sure that you have the following:
• The hardware manual for your particular storage device.

• SCSI Cable(s) and active terminators for connecting the jukebox or standalone drive.

• CD-ROM or Tape device to install the QStar Software.

Page 6 of 54
QSTAR SOFTWARE DIRECTORIES
QStar Software is installed in the /opt/QStar directory. Here you can find the following files and directories:

INSTALL (Installation Script)

bin (Directory of QStar user commands)**
common (Directory that contains common files)
dev (Directory that contains the QStar device nodes)
doc (Directory that contains the API html documentation)
etc (Directory of QStar administrator commands)**
fsi (File system interface) ***
include (Directory that contains include files)
install (Directory that contains installation and de-installation scripts called by the INSTALL script)
jb (Directory that contains the JB module - Jukebox management)
lib (Directory that contains the QStar Library files)
license (Directory that includes installkey program for the license key generation and the license file)
log (Directory that contains the QStar log file)
man (Directory of QStar command man pages)*
mcfs (Directory that contains the MCFS module - Front end caching)
media (Directory that contains the module to control publisher devices)
qscsi (Directory that contains the QSCSI module - Low level drivers)
sdf (Directory that contains the SDF module - Standard Data Format file system)
tmp (Temporary directory sometimes used by QStar Software)
udf (Directory that contains the UDF module - Universal Disk Format file system)
uvfs (Directory that contains the UVFS module - Universal file system)
vl (Directory that contains the VL module - Volume Librarian)

* /opt/QStar/man should be added to the Administrator's default man page search path environment variable (MANPATH)
** /opt/QStar/bin and /opt/QStar/etc should be added to the Administrator's default execute path environment variable (PATH)
*** Only on LINUX and HP-UX.

Page 7 of 54
UPGRADING YOUR CURRENT VERSION OF QSTAR
SOFTWARE
To de-install the QStar Software in order to install an upgrade, install system patches, or in preparation for moving to another
host, follow the steps below:
Step valid for release version 4.40.x.

1) Archive all data for each of the Integral Volume sets.

mmarc -e /mount_point For each set mounted.

2) Unmount all Integral Volume sets and stop all jukebox schedulers.

umount /mount_point For each media set or Integral Volume set mounted.
umountiv /mount_point For the Linux and HP-UX platforms.
Note: For safety, QStar suggests saving the information of device and Integral Volume sets database by running the
vllsdev device_name and vllsset -va commands and redirect the output into a file.
jbshut jb For each jbscheduler running.

3) Change directory to the QStar directory.

cd /opt/QStar

4) Keep details of the license key (/opt/QStar/license/license_description).

5) Run the installation program by entering:

./INSTALL

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit

Enter item number or ? for help: 5 Select #5 to uninstall the QStar Software.
Enter y for Yes or n for No.
Do you really want to uninstall [n]: y
Enter y for Yes or n for No.
Do you want to save the QStar databases [y]: y
QStar databases saved to /var/tmp/qs_db_saved.tar.Z
QStar Software uninstalled

Page 8 of 54
 QStar Software Installation Main Menu
1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
8) Upgrade QStar Software
9) Exit

Enter item number or ? for help: 9 Select #9 to exit from the installation program.

6) Remove the contents of the QStar directory.

rm -r /opt/QStar/*

7) Install the upgrade version of the QStar Software as described in the “Installation Steps” section of this manual.

Note: The VL configuration file /opt/QStar/vl/files/conf will not be valid. When the installation is complete and the QStar
Databases are restored, exit from the installation, the QStar daemons should be stopped and the VL configuration file
deleted. If the file is deleted, a new file will be created when the QStar daemons are started and this file will need to be
edited as required, as default values will be set in the new file. The format of the cache files in version 5.x are incompatible
with the cache files for all 4.x versions, so the System Administrator will be forced to mount all Integral Volume sets with
clean cache after the upgrade. For DVD jukeboxes after the uninstall procedure remove the file
c:\qstar\jb\files\jb_param_*.

Step valid for release version 5.0 and later.

1) Archive all data for each of the Integral Volume sets.

mmarc -e /mount_point For each set mounted.

2) Unmount all Integral Volume sets and stop all jukebox schedulers.

umount /mount_point For each media set or Integral Volume set mounted.
umountiv /mount_point For the Linux and HP-UX platforms.
jbshut jb For each jbscheduler running.

3) Change directory to the QStar directory.

cd /opt/QStar

Page 9 of 54
4) Run the installation program by entering:

./INSTALL

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit

Enter item number or ? for help: 8 Select #8 to upgrade the QStar Software.

Enter the upgrade filename [default=/tmp/upgrade.tar] or q)uit -> /linux-redhat_v5.0.13.709.tar

Note: Never copy the files used for upgrade into /opt/QStar, because the upgrade will fail.

Stopping QStar daemons ...

_rc: VL: Stopped
_rc: MM: Stopped
_rc: JB: Stopped
_rc: SCSI: Stopped

Upgrading QStar Software ...

QStar Software version:5/12/08 5.0.12.690 Linux 2.6 ix86 was installed at Mon Dec 8 16:12:34 CET 2008
It was upgraded to: 12/01/09 5.0.13.709 Linux 2.6 ix86 at Mon Dec 12 15:04:16 CET 2009

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit

Enter item number or ? for help: 9 Select #9 to exit from the installation program.

Note: The upgrade option will be not available on AIX platforms if /opt/QStar is a symbolic link and not a real directory, in
this case follow the procedure valid for a release before version 4.40.x.

Page 10 of 54
INSTALLATION STEPS
For the correct installation procedure of the QStar Software for each platform you must follow these steps in the order shown in
the diagram below:

Diagram Installation Step

STEP 1 STEP 2 STEP 3 STEP 4

Hardware Loading the Installing Installing

Installation QStar the License the
And Setup Software Key and QStar
of Devices on to Registering Software
the System the Software

STEP 5 STEP 7 STEP 8

Specifying Compiling Post

your Storage Kernel Installation
Device If Applicable Test
N NEW INSTALLATION
Configuration

UPGRADE
STEP 6
Restoring or
Upgrading
the
QStar
Databases

Page 11 of 54
STEP 1: HARDWARE INSTALLATION AND SETUP OF
DEVICES
Step1.1) Determining Available SCSI IDs and Setup of the
Storage Device(s)
Installed on: Sun Solaris
To install the jukebox(es) or standalone drive(s), follow these steps:

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

After the system is shut down, you will see the following “console mode” prompt on the display:

ok ÅSolaris

Verify the attached devices and their corresponding SCSI IDs, by entering the following maintenance command:

probe-scsi ÅSolaris - Single SCSI bus server

probe-scsi-all ÅSolaris - Multiple SCSI bus server

The system will display a list of the attached SCSI devices.

2) Fill in the SCSI configuration worksheet in Appendix “A” with the information you gathered on currently used
SCSI target IDs. A used SCSI target ID is one that appears on the screen. You may choose any available number from
target 0 through 6 on the SCSI bus for the storage devices.

3) Select appropriate SCSI target IDs from those that are available for each storage device connected to your host.
Enter this information in the worksheet in Appendix “A”. Each device will require between 1 and 13 target Ids. For
information specific to your hardware, consult the hardware manual that came with your jukebox or standalone drive.

4) Power off your system. Set the SCSI IDs of your storage devices per the instructions of the hardware operator's
manual. 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 your server.

5) Verify the SCSI ID settings of the jukebox(es) or the standalone drive(s) to ensure there are no conflicts with other
devices on the same SCSI bus using the maintenance command again:

probe-scsi ÅSolaris - Single SCSI bus server

probe-scsi-all ÅSolaris - Multiple SCSI bus server

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

6) Boot your system and log on as “root”. During the boot process, the operating system will configure the devices
attached to the system.

Page 12 of 54
Step1.2) Determining Available SCSI IDs and Setup of the
Storage Device(s)
Installed on: IBM AIX
To install the storage jukebox(es) or standalone drive(s), follow these steps:

1) Log on to the host computer as root. Verify the attached devices and their corresponding SCSI IDs by entering the
following maintenance command:

lsdev -Csscsi

The system will display a list of the attached SCSI devices.

2) Fill in the SCSI configuration worksheet in Appendix “A” with the information you gathered on currently used
SCSI target IDs. A used SCSI target ID is one that appears on the screen. You may choose any available number from
target 0 through 6 on the SCSI bus for the storage devices.

3) Select appropriate SCSI target IDs from those that are available for each storage device connected to your host.
Enter this information in the worksheet in Appendix “A”. Each device will require between 1 and 13 target IDs. For
information specific to your hardware, consult the hardware manual that came with your jukebox or standalone drive.

4) Power off your system. Set the SCSI IDs of your storage devices per the instructions of the hardware operator's
manual. 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 your server.

5) After the system boots, there should be sdoX and auchX devices at the SCSI addresses (where X is some sequential
number). There is one sdoX device for each optical drive and an auchX device for the autochanger for most
jukeboxes.

6) Log on to the host computer as root. Verify the SCSI ID settings on the storage library or on the standalone drive to
ensure there are no conflicts with other devices on the same SCSI bus using the maintenance mode command again:

lsdev -C for a general hardware listing or lsdev -Csscsi for a more concise SCSI listing

Verify these devices. The system returns a list similar to the one below of the SCSI devices attached to your system.
The list now shows the additional devices that have been attached to your system. All of the previously connected
devices, as well as any newly connected devices, should be included in the display. Check your SCSI ID
configuration and SCSI cabling if a device is missing from this list.

There should be a sdo0 and sdo1 device for a two-drive storage library and an auch0 device for the jukebox
autochanger.
The devices must be in the available state.
Example:

lsdev –Csscsi
cd0 Available 04-B0-00-3,0 SCSI Multimedia CD-ROM Drive
hdisk0 Available 04-B0-00-6,0 Other SCSI Disk Drive
rmt0 Defined 04-B0-00-5,0 Other SCSI Tape Drive
auch0 Available 04-B0-00-5,0 PLASMON Jukebox Autochanger
sdo0 Available 04-B0-00-2,0 650Mb SONY Magneto-optical drive
sdo1 Available 04-B0-00-4,0 650Mb SONY Magneto-optical drive

Page 13 of 54
Step1.3) Determining Available SCSI IDs and Setup of the
Storage Device(s)
Installed on: Linux
To install the jukebox(es) or standalone drive(s), follow these steps:

1) Log on to the host computer as root. Verify the attached devices and their corresponding SCSI IDs by entering the
following command:

more /proc/scsi/scsi

in no scsi device are displayed the system administratior can run insmod command with name of scsi card installed
and retry the above command.

The system will display a list of the attached SCSI devices.

2) Fill in the SCSI configuration worksheet in Appendix “A” with the information you gathered on currently used
SCSI target IDs. A used SCSI target ID is one that appears on the screen. You may choose any available number from
target 1 through 7 on the SCSI bus for the storage devices.

3) Select appropriate SCSI target IDs from those that are available for each storage device connected to your host.
Enter this information in the worksheet in Appendix “A”. Each device will require between 1 and 13 target Ids. For
information specific to your hardware consult the hardware manual that came with your jukebox or standalone drive.

4) Power off your system. Set the SCSI IDs of your storage devices per the instructions of the hardware operator's
manual. 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 your server.

5) Verify the SCSI ID settings of the jukebox(es) or the standalone drive(s) to ensure there are no conflicts with other
devices on the same SCSI bus using the following command again:

more /proc/scsi/scsi

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

Page 14 of 54
Step1.4) Determining Available SCSI IDs and Setup of the
Storage Device(s)
Installed on: Hewlett Packard HP-UX
To install the jukebox(es) or standalone drive(s), follow these steps:

1) Shut down the system using your standard shutdown procedure. After the system is shut down, you will see the
following “console mode “prompt on the display:

….…

Verify that the system recognizes the devices at the correct SCSI IDs by entering the following maintenance
command:

ioscan -f

The system will display a list of the attached SCSI devices.

2) Fill in the blank SCSI configuration worksheet in Appendix “A” with the information on currently used SCSI
target ids. An available SCSI target ID is one that does not appear on the screen. You can choose any available
number from target 0 through target 6 on the SCSI bus for the storage devices.

3) Power off your system. Attach each device to its appropriate SCSI controller(s) and connect the terminator to close
the SCSI chain and power it on.

4) Select an appropriate SCSI target IDs from those that are available for each storage device connected to your host.
Enter this information in the worksheet in Appendix “A”. Each storage library will require from 1 to 5 or more target
Ids. For more information, consult the hardware manual that came with your jukebox or standalone drive.

5) Verify the SCSI ID settings on the jukebox or on the standalone drive to ensure there are no conflicts with other
devices on the same SCSI bus using the maintenance mode command again:

ioscan -f

The list now shows the additional devices that have been attached to your system.
All of the previously connected devices as well as any newly connected devices should be included in the display.
Check your SCSI ID configuration and SCSI cabling if a device is missing from this list.

6) Boot your system and log on as “ROOT”. During the boot process, HP-UX configures the devices attached to the
system.

Page 15 of 54
STEP 2: LOADING THE QSTAR SOFTWARE ON THE
SYSTEM

Following these steps:

1) Log on to the system as root.

2) Create a directory named QStar in either the /opt directory (default) or another directory. If you created the QStar directory in
the /usr directory, for example, also do the following:

Create a symbolic link between /usr/QStar and /opt/QStar by entering the following command:

ln -s /usr/QStar /opt/QStar

3) To extract the QStar Software from the CD or tape into the QStar directory, issue the following commands:

CD:
Insert QStar Software CD into the local CD drive and mount it.

Examples of the correct syntax for the mount command are as follows (*):

mount –F hsfs –o ro /dev/<cd drive> /cdrom ÅSOLARIS

mount –v cdrfs –o ro /dev/cd0 /cdrom ÅIBM
mount -r -t cdfs /dev//dsk/c4d0s2 /cdrom ÅHP-UX 9.x Series 700
mount -r -F cdfs /dev/dsk/c0t4d0 /cdrom ÅHP-UX 10.x Series 700 and 800

Change directories to the QStar directory.

cd /opt/QStar

tar xvf /cdrom/…/Release/distribution_file.tar

(*): If the syntax displayed in the examples is no longer valid, please consult the Administrator's manual for the correct syntax
for the operating system of the server.

Page 16 of 54
STEP 3: INSTALLING THE LICENSE KEYS AND
REGISTERING THE SOFTWARE

Before the QStar Software will function a valid License Key for the specific QStar product you have purchased or are
evaluating should be installed.
The QStar Support personnel can generate two different types of keys:
• DEMO ( by default this License Key expires after 30 days)
• PERMANENT

The installkey program provides the hostid information needed to obtain a Demo or Permanent License Key from QStar
Customer Support Personnel.

Run the installkey program located in the /opt/QStar/license directory.

cd /opt/QStar/license/

./installkey -V
The license information displayed before the Software is licensed is the following:

Server: Host ID : 843ba758

Server: QStar Version: 5.0.13.709

The Serial Number can be found on the license card or on the back of the CD case supplied with the Software.
To create the proper list, go to the following section Demo License Key or Permanent License Key as required.

Demo License Key

The Default value is 30 days from the current date. With QStar’s approval, if needed the Demo License Key can be issued for
a longer period of time by the QStar Customer Support Personnel. The Demo License Key will allow the use of all the QStar
Products with any supported device for the time specified by the Demo Expiration Date. The maximum numbers of jukeboxes
that can be controlled by the QStar Software at the same time are “8”.
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: 5.0.13 *
• License Type: Demo
• Platform: *
• Host ID: *
*: Mandatory information

To facilitate the generation of the Demo License Key the Serial Number, QStar Software Version and License Version will
be requested.

Page 17 of 54
The above information can be inserted 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
instruction.

Activate the Demo License Key

The Demo license key is a file that will be sent via email to the email specified, that must be copied on the /opt/QStar/license
folder. Once the license file is copied, run the following command to display the license information:
./installkey -L
License: Product : QStar HSM
License: Company : QStar Technologies, Inc.
License: Department : Demo Laboratory
License: Person : Support Personnel
License: Phone : +1-850-2430900
License: Email : [email protected]
License: Version : 5.0
License: Type : Demo
License: Platform : Linux
License: Expiration date: 2009-02-26
License: Host ID : 843ba758
License: Serial number: N/A
Server: Host ID : 843ba758
Server: QStar Version: 5.0.13.709

Note: In the example, the License type is Demo and the License Key is activated.
The Demo License Key will allow the use of all the QStar Products with any device for the time specified in the Expiration
date line. The Serial Number for Demo license is not necessary and will be displayed as N/A (Not Available).

If the Demo license expires, a message will appear in the Expiration date line.
./installkey -L
License: Product : QStar HSM
License: Company : QStar Technologies, Inc.
License: Department : Demo Laboratory
License: Person : Support Personnel
License: Phone : +1-850-2430900
License: Email : [email protected]
License: Version : 5.0
License: Type : Demo
License: Platform : Linux
License: Demo license expired: 2009-02-27
License: Valid License file NOT found.
installkey: V5 License verification error: license file not found
Server: Host ID : 843ba758
Server: QStar Version: 5.0.13.709

Page 18 of 54
Permanent License Key
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: 5.0.13 *
•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: 2. Jukebox or Standalone Drive:
• QStar HSM • Number of Jukeboxes or Standalone Drives
• Data Director: DDR1/DDR2/DDR3 • Real Device Type
• CD/DVD-ROM Axxess • Optical
• CD/DVD-R Master: Master1/Master2/Master3 • Tape
• API (For API Support) • CD/DVD
• Digital Signature • 12 inch Worm
• Remote Copy • UDO/PDD
• Duplicator Support • BD (Blu-ray)
• HSM-Lite Basic • Simulated Device Type
• HSM Lite optional features: • Centera
• Copy media • Hard Drive
• Offline, magazine, media exchange • Number of Shelves
• Compaction • Capacity (GB) (Only for Simulated Device Type)
• Grace Retention period, Windows NFS

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.

Page 19 of 54
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
/opt/QStar/license folder. Once the license file is copied run the following command to display the license information:
./installkey –L
License: Product : QStar DDR
License: Company : QStar Technologies, Inc.
License: Department : Demo Laboratory
License: Person : Support Personnel
License: Phone : +1-850-2430900
License: Email : [email protected]
License: Version : 5.0
License: Type : Permanent
License: Host ID : 843ba758
License: Serial number: 50000
License: Platform : Linux
License: Jukebox type: licenseJB_TYPE_TAPE
License: #Shelves : 35
License: HSM : No
License: DDR : DDR1
License: API : No
License: Digital sign: No
Server: Host ID : 843ba758
Server: QStar Version: 5.0.13.709

Note: In the example the Permanent License Key is for the QStar DDR1 product and a Tape jukebox with 35 shelves is
activated.

./installkey –L
License: Product : QStar HSM
License: Company : QStar Technologies, Inc.
License: Department : Demo Laboratory
License: Person : Support Personnel
License: Phone : +1-850-2430900
License: Email : [email protected]
License: Version : 5.0
License: Type : Permanent
License: Host ID : 843ba758
License: Serial number: 50000
License: Platform : Linux
License: Jukebox type: licenseJB_TYPE_CD_DVD
License: #Shelves : 200
License: Jukebox type: licenseJB_TYPE_BD
License: #Shelves : 100
License: HSM : Yes
License: Master type : 3
License: API : No
License: Digital sign: No
License: Duplicator : No
Server: Host ID : 843ba758
Server: QStar Version: 5.0.13.709

Note: In the example the Permanent License Key is for the QStar HSM and Master 3 products and a CD/DVD jukebox with
200 shelves and a Blu-ray jukebox with 100 shelves is activated.

Page 20 of 54
STEP 4: INSTALLING THE QSTAR SOFTWARE
The installation program automatically sets up all necessary product directories, files, and symbolic links.

After the Software has been extracted from the CD-ROM or tape, start the Software installation script by entering the following
command sequence:

Change directory to the Software location.

cd /opt/QStar

Start the installation script

./INSTALL

QStar software is built for the Linux platform kernel 2.6 ix86
Current platform is Linux 2.6 ix86
QStar software version is 5.0.13.709

The installation script will display the license Agreement:

Please read and confirm a following QStar license agreement:

Pause for 3 seconds...

Enter y for Yes or n for No.

Do you agree with this license agreement [y]: Enter yes ”y” to proceed the installation.

The installation script will display the following menu:

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit

Enter item number or ? for help: Enter the number that corresponds with the product you've
purchased or are evaluating.

Page 21 of 54
STEP 5: SPECIFYING YOUR STORAGE DEVICE
CONFIGURATION

Step 5.1) SUN Solaris, Hewlett Packard HP-UX or Linux

To configure the devices, jukeboxes and/or standalone drives, which will be handled by the QStar Software, follow these steps:

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 1 Select #1 to check if any devices are configured.

No real devices

No simulated devices

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 2 Select #2 to add a storage library.

Getting SCSI probe. Please wait...

Enter jb_name, ? for help, ^ for cancel [jb]: jb Traditional naming convention.
The following SCSI devices have been found:
1. bus=0 target=0 lun=0 Disk id=SEAGATE ST32430W SUN2.1G0666 Å System Disk
2. bus=0 target=3 lun=0 Erasable id=HP C1113J 1.06 Å First Jukebox Drive
3. bus=0 target=4 lun=0 Erasable id=SONY SMO-F521-01 2.04 Å Standalone Optical Drive
4. bus=0 target=5 lun=0 Erasable id=HP C1113J 1.06 Å Second Jukebox Drive
5. bus=0 target=6 lun=0 Changer id=HP C1160J 1.47 Å Jukebox Autochanger

Enter item number for changer, ? for help, ^ for cancel: 5

Page 22 of 54
If the robot and drives use different SCSI buses, you must configure the
drives manually. Otherwise the drives can be configured automatically.

Automatically:

Enter y for Yes or n for No.

Do you want to configure drives manually [n]: n

Current device is:

Jukebox jb
Changer bus=0, target=6, lun=0

Enter y for Yes or n for No.

Add device to list of configured devices [y]: y

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 1

Real Devices:

1. Jukebox jb
Changer bus=0, target=6, lun=0 Only the changer will be configured, the drives not will be
present in this list until after the installation is completed.

No simulated devices

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 6 The configuration is complete, return to main menu.

Page 23 of 54
 QStar Software Installation Main Menu
1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit
UP GRADE - SELECT (8) and GOTO STEP 6

Enter item number or ? for help:

NEW INSTALLATION - SELECT (9) and GOTO STEP 7

If the message “Please configure drives manually” is displayed while exiting from the installation script, the device cannot be
configured automatically by the software. If this is the case, please restart the INSTALL script.

Once the INSTALL script is restarted follow the steps below to reconfigure the devices manually.

QStar software is built for Linux platform kenel 2.6 ix86

Current platform is Linux 2.6 ix86
QStar software version is 5.0.13.709
License Agreement for version 5.0.13.709 was confirmed at:
Thu Jan 15 16:42:12 CET 2009

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit

Enter item number or ? for help: 6 Select #6 to reconfigure QStar Software.

QStar Software Reconfiguration Menu

1) Configure Devices
2) SCSI Classes
3) Return

Enter item number or ? for help: 1 Select #1 to configure the devices.

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 1 Select #1 to list the configured devices.

Page 24 of 54
Real Devices:

1. Jukebox jb
Changer bus=0, target=6, lun=0

No simulated devices

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 4 Select #4 to remove all devices previously configured.
Stopping QStar daemons...
_rc: SCSI: Stopped

Real Devices:

1. Jukebox jb
Changer bus=0, target=6, lun=0

No simulated devices

Enter y for Yes or n for No.

Remove device 1 from list of configured devices [y]: y

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 2 Select #2 to add a storage library.

Getting SCSI probe. Please wait...

Enter jb_name, ? for help, ^ for cancel [jb]: jb Traditional naming convention.

The following SCSI devices have been found:

1. bus=0 target=0 lun=0 Disk id=SEAGATE ST32430W SUN2.1G0666 Å System Disk
2. bus=0 target=3 lun=0 Erasable id=HP C1113J 1.06 Å First Jukebox Drive
3. bus=0 target=4 lun=0 Erasable id=SONY SMO-F521-01 2.04 Å Standalone Optical Drive
4. bus=0 target=5 lun=0 Erasable id=HP C1113J 1.06 Å Second Jukebox Drive
5. bus=0 target=6 lun=0 Changer id=HP C1160J 1.47 Å Jukebox Autochanger

Enter item number for changer, ? for help, ^ for cancel: 5

Page 25 of 54
Manually:

Enter y for Yes or n for No.

Do you want to configure drives manually [n]: y

Enter y for Yes or n for No.

Do you want to configure drive 1 [y]: y

The following SCSI devices have been found:

1. bus=0 target=0 lun=0 Disk id=SEAGATE ST32430W SUN2.1G0666 Å System Disk
2. bus=0 target=3 lun=0 Erasable id=HP C1113J 1.06 Å First Jukebox Drive
3. bus=0 target=4 lun=0 Erasable id=SONY SMO-F521-01 2.04 Å Standalone Optical Drive
4. bus=0 target=5 lun=0 Erasable id=HP C1113J 1.06 Å Second Jukebox Drive
5. bus=0 target=6 lun=0 Changer id=HP C1160J 1.47 Å Jukebox Autochanger

Enter item number for drive 1, ? for help, ^ for cancel: 2

Current device is:

Jukebox jb
Changer bus=0, target=6, lun=0
Drive 1 bus=0, target=3, lun=0

Enter y for Yes or n for No.

Do you want to configure drive 2 [y]: y

The following SCSI devices have been found:

1. bus=0 target=0 lun=0 Disk id=SEAGATE ST32430W SUN2.1G0666 Å System Disk
2. bus=0 target=3 lun=0 Erasable id=HP C1113J 1.06 Å First Jukebox Drive
3. bus=0 target=4 lun=0 Erasable id=SONY SMO-F521-01 2.04 Å Standalone Optical Drive
4. bus=0 target=5 lun=0 Erasable id=HP C1113J 1.06 Å Second Jukebox Drive
5. bus=0 target=6 lun=0 Changer id=HP C1160J 1.47 Å Jukebox Autochanger

Enter item number for drive 2, ? for help, ^ for cancel: 4

Current device is:

Jukebox jb
Changer bus=0, target=6, lun=0
Drive 1 bus=0, target=3, lun=0
Drive 2 bus=0, target=5, lun=0

Enter y for Yes or n for No.

Do you want to configure drive 3 [y]: n In the example, the storage library only has two drives.

Current device is:

Jukebox jb
Changer bus=0, target=6, lun=0
Drive 1 bus=0, target=3, lun=0
Drive 2 bus=0, target=5, lun=0

Enter y for Yes or n for No.

Add device to list of configured devices [y]: y

Page 26 of 54
 Device Configuration Menu
1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 1

Real Devices:

1. Jukebox jb
Changer bus=0, target=6, lun=0
Drive 1 bus=0, target=3, lun=0
Drive 2 bus=0, target=5, lun=0

No simulated devices

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 3

Enter jb_name, ? for help, ^ for cancel [jb1]: drive0

The following SCSI devices have been found:

1. bus=0 target=0 lun=0 Disk id=SEAGATE ST32430W SUN2.1G0666 Å System Disk
2. bus=0 target=3 lun=0 Erasable id=HP C1113J 1.06 Å First Jukebox Drive
3. bus=0 target=4 lun=0 Erasable id=SONY SMO-F521-01 2.04 Å Standalone Optical Drive
4. bus=0 target=5 lun=0 Erasable id=HP C1113J 1.06 Å Second Jukebox Drive
5. bus=0 target=6 lun=0 Changer id=HP C1160J 1.47 Å Jukebox Autochanger
Enter item number for standalone_drive, ? for help, ^for cancel: 3

Current device is:

Drive drive0 bus=0, target=4, lun=0

Enter y for Yes or n for No.

Add device to list of configured devices [y]: y

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 1 Select #1 for List Configured Devices.

Page 27 of 54
Real Devices:

1. Jukebox jb
Changer bus=0, target=6, lun=0
Drive 1 bus=0, target=3, lun=0
Drive 2 bus=0, target=5, lun=0

2. Drive drive0 bus=0, target=4, lun=0

No simulated devices

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 6 The configuration is completed, return to main menu.

QStar Software installed.

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit
UP GRADE - SELECT (8) and GOTO STEP 6

Enter item number or ? for help:

NEW INSTALLATION - SELECT (9) and GOTO STEP 7

Page 28 of 54
Step 5.2) IBM AIX
First step of Installation is completed.
Now you will need to configure the device(s), jukeboxes and/or standalone drives, which will be handled by the QStar
Software.
The following devices have been already detected and configured:

auch0 scsi0 5,0 PLASMON Jukebox Autochanger

Note: Some devices you intend to use with the QStar Software may have already been configured by non-QStar drivers. If these
devices are missing in the list above then select “List Other Devices” in the menu below. Then you may start a shell and run
“rmdev -l 'device' -d” command(s) for such devices. Note also that some optical drives may be recognized as hard disks.

Device Configuration Menu

1) List Configured Devices
2) List Other Devices
3) Configure/Reconfigure/Remove Devices
4) Start shell
5) Return

Enter item number or ? for help: 1 Select #1 to check if any devices are configured.

No real devices

No simulated devices
Device Configuration Menu
1) List Configured Devices
2) List Other Devices
3) Configure/Reconfigure/Remove Devices
4) Start shell
5) Return

Enter item number or ? for help: 2

The following scsi devices are configured with non-QStar drivers. If you intend to use some of them with QStar Software then
please remove (deconfigure) them before configuring QStar devices.

omd0 Available 04-B0-00-1,0 Other SCSI Read/Write Optical Drive

omd1 Available 04-B0-00-2,0 Other SCSI Read/Write Optical Drive
cd0 Available 04-B0-00-3,0 SCSI Multimedia CD-ROM Drive
hdisk0 Available 04-B0-00-6,0 Other SCSI Disk Drive
Device Configuration Menu
1) List Configured Devices
2) List Other Devices
3) Configure/Reconfigure/Remove Devices
4) Start shell
5) Return

Enter item number or ? for help: 4

Type exit to return to the QStar installation.

Page 29 of 54
#> rmdev -l omd0 -d
omd0 deleted
#>rmdev -l omd1 -d
omd1 deleted
#> exit
#> Please wait: running /usr/sbin/cfgmgr...

Device Configuration Menu

1) List Configured Devices
2) List Other Devices
3) Configure/Reconfigure/Remove Devices
4) Start shell
5) Return

Enter item number or ? for help: 1

Real Devices:

1. sdo0 bus=scsi0 target,lun=1,0

2. sdo1 bus=scsi0 target,lun=2,0

No simulated devices

Device Configuration Menu

1) List Configured Devices
2) List Other Devices
3) Configure/Reconfigure/Remove Devices
4) Start shell
5) Return

Enter item number or ? for help: 2

The following scsi devices are configured with non-QStar drivers. If you intend to use some of them with QStar Software then
please remove (deconfigure) them before configuring QStar devices.

cd0 Available 04-B0-00-3,0 SCSI Multimedia CD-ROM Drive

hdisk0 Available 04-B0-00-6,0 Other SCSI Disk Drive

Device Configuration Menu

1) List Configured Devices
2) List Other Devices
3) Configure/Reconfigure/Remove Devices
4) Start shell
5) Return

Enter item number or ? for help: 3 Select #3 to add a storage library.

Usually devices supported by QStar Software are detected and configured automatically. You only have to configure the
Jukebox Manager using smit. Please be careful when specifying jukebox drives, specifying the drives in the wrong order will
result in incorrect operation of the Jukebox Manager. It is recommended that you check the storage library configuration (SCSI
id/LUNs) and list of already configured drives before configuring Jukebox Manager.

Enter y for Yes or n for No.

Do you want to configure devices now [y]: y

Note: In the example an Optical storage library is used.

Page 30 of 54
The QStar Device Configuration Menu calls the smit program to configure the devices.
Once the smit program starts the following menu is displayed:

System Management (Menu)

Move cursor to desired item and press Enter.

Software Installation and Maintenance

Software License Management
Devices Select Devices.
System Storage Management (Physical & Logical Storage)
Security & Users
Communications Applications and Services
Print Spooling
Problem Determination
Performance & Resource Scheduling
System Environments
Processes & Subsystems
Applications
Using SMIT (information only)

F1=Help F2=Refresh F3=Cancel F8=Image

F9=Shell F10=Exit Enter=Do

Devices (Menu)

Move cursor to desired item and press Enter.

Install/Configure Devices Added After IPL

Printer/Plotter
TTY
Asynchronous Adapters
PTY
Console
Fixed Disk
MO (Magnetic-Optical) Optical Disk Select this to configure an optical standalone drive.
Disk Array
WORM (Write-Once-Read-Many) Optical Disk
Jukebox Autochanger
Jukebox Manager Select Jukebox Manager.
CD ROM Drive Select this to configure a CD ROM standalone drive.
Read/Write Optical Drive
Diskette Drive
Tape Drive Select this to configure a tape standalone drive.
Communication
Graphic Displays
…….
ISA Adapters

F1=Help F2=Refresh F3=Cancel F8=Image

F9=Shell F10=Exit Enter=Do

Note: For standalone drive configuration, please refer page 39 of this chapter.

Page 31 of 54
Jukebox Manager (Menu)
Move cursor to desired item and press Enter.

Add a Jukebox Select Add a Jukebox.

Configure a Defined Jukebox
Remove a Jukebox Select this to remove a storage library.
List All Defined Jukeboxes
List All Supported Jukeboxes
Change/Show Characteristics of a Jukebox Select this for redefine a storage library.
Define a Jukebox

F1=Help F2=Refresh F3=Cancel F8=Image

F9=Shell F10=Exit Enter=Do

After you select the Add a jukebox item the following menu will appear:

Robot Device
In this menu you have to move the cursor to the desired and press ENTER. In the example, auch0 is selected.

auch0 Available 04-B0-00-5,0 PLASMON Jukebox Autochanger

F1=Help F2=Refresh F3=Cancel

F8=Image F10=Exit Enter=Do
/=Find n=Find Next

Add a Jukebox (Menu)

Type or select values in entry fields.
Press Enter AFTER making all desired changes.

[Entry Fields]
Robot Device [auch0]
Number of Shelves [52]
* Drive 1
* Drive 2

F1=Help F2=Refresh F3=Cancel F4=List

F5=Reset F6=Command F7=Edit F8=Image
F9=Shell F10=Exit Enter=Do

Select Drive1 in Add a Jukebox (Menu).

Note: Be sure to select drives in the correct order.

After you Select Drive1, the Drive 1 (Menu) menu will appear, use the F4 key to choose the devices for the drives.

Page 32 of 54
Drive 1 (Menu)
Move cursor to desired item and press Enter. In this example sdo0 is selected.

sdo0 Available 04-B0-00-1,0 SONY F541 Multifunction drive

sdo1 Available 04-B0-00-2,0 SONY F541 Multifunction drive
cd0 Available 04-B0-00-3,0 SCSI Multimedia CD-ROM Drive

Add a Jukebox (Menu)

Type or select values in entry fields.
Press Enter AFTER making all desired changes.

[Entry Fields]
Robot Device [auch0]
Number of Shelves [52]
* Drive 1 sdo0
* Drive 2

F1=Help F2=Refresh F3=Cancel F4=List

F5=Reset F6=Command F7=Edit F8=Image
F9=Shell F10=Exit Enter=Do

Select Drive2 in Add a Jukebox (Menu)

After the Drive2 has been selected, the Drive 2 (Menu) menu will appear, use the F4 key to choose the devices for the drives.

Drive 2 (Menu)
Move cursor to desired item and press Enter. In this example, sdo1 is selected.

sdo0 Available 04-B0-00-1,0 SONY F541 Multifunction drive

sdo1 Available 04-B0-00-2,0 SONY F541 Multifunction drive
cd0 Available 04-B0-00-3,0 SCSI Multimedia CD-ROM Drive

After All the selection the situation is the Following:

Add a Jukebox (Menu)

Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
Robot Device [auch0]
Number of Shelves [52]
* Drive 1 sdo0
* Drive 2 sdo1

F1=Help F2=Refresh F3=Cancel F4=List

F5=Reset F6=Command F7=Edit F8=Image
F9=Shell F10=Exit Enter=Do
Press Enter to create the jukebox home directory that will contain the special files and the configuration files that the storage
library needs.
The system will return “jbn Available”.

Page 33 of 54
COMMAND STATUS (Menu)
Command: OK stdout: yes stderr: no
Before command completion, additional instructions may appear below.

jb0 Available

F1=Help F2=Refresh F3=Cancel F6=Command

F8=Image F9=Shell F10=Exit
/=Find n=Find Next

Note: Always use the QStar INSTALL script to add or remove a jukebox or standalone drive devices. This guarantees a clean
install and de-install. Repeat steps for each individual jukebox that you have connected to the system.

Page 34 of 54
For a Standalone Drive

Devices (Menu)
Move cursor to desired item and press Enter.

Install/Configure Devices Added After IPL

Printer/Plotter
TTY
Asynchronous Adapters
PTY
Console
Fixed Disk
MO (Magnetic-Optical) Optical Disk Select this to configure an optical standalone drive.
Disk Array
WORM (Write-Once-Read-Many) Optical Disk
Jukebox Autochanger
Jukebox Manager
CD ROM Drive Select this to configure a CD-ROM standalone drive.
Read/Write Optical Drive
Diskette Drive
Tape Drive Select this to configure a tape standalone drive.
Communication
Graphic Displays
Graphic Input Devices
Low Function Terminal (LFT)
SCSI Initiator Device
SCSI Adapter
IDE Adapters
Asynchronous I/O
Multimedia
List Devices
Install Additional Device Software
ISA Adapters
F1=Help F2=Refresh F3=Cancel F8=Image
F9=Shell F10=Exit Enter=Do

In the AIX operating system a device can be used only if it is displayed in the lsdev -Csscsi output as available.
The System Administrator can use the above smit menu to configure a standalone drive (sdo0) that is marked as defined in the
lsdev –Csscsi output. Configuring the standalone drive will change its status in the lsdev -Csscsi output to available.

Once the standalone drive is displayed as available it can be used as Pseudo Jukebox device with SDF and UDF file systems.

To use any standalone drive as pseudo jukebox device, run the following command:

/usr/lib/methods/jbtune -c jb -t standalone -s node 1 sdo0

Where “1” is the number of “shelves” and “sdo0” is the drive name.

Note: Once this command has been executed the standalone drive will behave as a standard jukebox, allowing use of the
standard QStar “vl”, “jb” and “mm” jukebox commands.

Page 35 of 54
After Exiting from the smit menu

Device Configuration Menu

1) List Configured Devices
2) List Other Devices
3) Configure/Reconfigure/Remove Devices
4) Start shell
5) Return
Enter item number or ? for help: 1 Select #1 to list the configured devices.

Real Devices:

1. Jukebox jb0
Changer auch0 bus=scsi0 target,lun=5,0
Drive 1 sdo0 bus=scsi0 target,lun=1,0
Drive 2 sdo1 bus=scsi0 target,lun=2,0

No simulated devices

Device Configuration Menu

1) List Configured Devices
2) List Other Devices
3) Configure/Reconfigure/Remove Devices
4) Start shell
5) Return

Enter item number or ? for help: 5 The configuration is completed return to main menu.

QStar Software installed.

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit
UP GRADE - SELECT (8) and GOTO STEP 6

Enter item number or ? for help:

NEW INSTALLATION - SELECT (9) and GOTO STEP 7

Page 36 of 54
STEP 6: RESTORING QSTAR DATABASES
**Only if UPGRADING, for *NEW INSTALLATIONS* PROCEED TO STEP 7**

After the installation is completed, to restore the information from the QStar databases, do the following actions:

Upgrading from 5.0.x version to any newer 5.0.x versions of the QStar Software in possible to use the upgrade option included
in the INSTALL menu to automatically upgrade the installed version of QStar Software. Using this option described in the
“Upgrading Your Current Version of QStar Software” section earlier in this chapter, QStar will automatically upgrade the
current release without the need to save the QStar databases or reconfigure the devices. The upgrade procedure from version
4.x to 5.0.x must be done manually by uninstalling the currently installed release, this will prompt the administrator to backup
the QStar databases, after this, the current release needs to be deleted and then the new release installed by the same procedure
as a new installation. Following this, the database can be manually restored by selecting option Restore QStar Database. The
QStar databases comprise of the VL configuration file (/opt/QStar/vl/files/conf), the jukebox database for each configured
jukebox (information on what media is in which shelves) and the sets database (information on cache location, size, which
media is contained in the set, etc). The following section describes how to restore the QStar databases.

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit

Enter item number or ? for help: 7

found QStar databases at /var/tmp/qs_db_saved.tar.Z

Enter y for Yes or n for No.

Do you want to restore VL device database [y]: y

Enter y for Yes or n for No.

Do you want to restore VL set database [y]: y

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit

Enter item number or ? for help: 9 Select #9 to exit from the installation program.

Note: Also the setting made for Privileged Users and the Send Mail Notification was saved and is now restored.

Page 37 of 54
STEP 7: COMPILING THE KERNEL, IF APPLICABLE

A) Sun Solaris,
After exiting the installation program the following message will be printed to the screen:

Check for missing inquiry IDs...

Start jbschedulers for configured jukeboxes [y]:
Enter y for Yes or n for No.
Choose: y

B) IBM AIX
After exiting the installation program the following message will be printed to the screen:

Check for missing inquiry IDs...

It is highly recommended that you reboot now.
Enter y for Yes or n for No.
Do you want to reboot now [y]:
Choose: y

If you choose No, you will see this next question.

Start jbschedulers for configured jukeboxes [y]:
Enter y for Yes or n for No.
Choose: y

C) LINUX
After exiting the installation program, the following message will be printed to the screen:

Check for missing inquiry IDs...

Starting QStar daemons …
starting _fsi_server …
_media_server: VL: Started
_media_server: Jbscheduler Started: jb

D) HP-UX

Check for missing inquiry Ids...

The following are kernel configuration files which are known to currently exist.
Please select the file that the QStar products should be built upon.

/stand/system.1
/stand/system.2
/stand/system.prev
/stand/system.qstar
/stand/system
/stand/system.max

Enter the configuration filename to build upon [default=/stand/system.max] or q)uit ->

Page 38 of 54
The schgr driver has been detected in the current kernel. In some cases this driver
will conflict with the QStar device drivers. If this driver is not used to control any
other devices, QStar highly recommends removing this driver from the kernel.
WARNING: Retaining this driver in the current kernel may cause unexpected results
and will be at the user's own risk. QStar will not be responsible for any problems
incurred by retaining this driver.
Enter y for Yes or n for No.
Would you like this driver automatically removed now? [y]: y

Compiling conf.c...
Loading the kernel...
Generating kernel symbol table...

Kernel update request is scheduled.

Default kernel /stand/vmunix will be updated by

newly built kernel /opt/QStar/vmunix_test
at next system shutdown or startup time.

Enter y for Yes or n for No.

Reboot the system now [y]:

Note: In the case of an upgrade the kernel information will be recalled by the QStar Software and will not be requested
anymore.

Page 39 of 54
STEP 8: POST INSTALLATION TEST
Starting the Daemons
Before creating a Volume set or an Integral Volume set, verify that the following daemons are running. QStar Software adds
these daemons to your system and, on some platforms, automatically starts them at boot-up.

Server Operating System Description

_jbserver Solaris This server is multi threaded and processes the requests from various JB clients
(usually JB commands). Upon receiving a connect request the server creates a thread
AIX
for talking to the client. In addition, this server starts the jbscheduler system daemon
for each jukebox connected to your system.
The jbscheduler is required on all platforms:

• Starts automatically at boot up on all platforms.

• Initializes your storage devices.

• Controls and manages access to your storage devices.

_vlserver Solaris It’s the VL server which processes the requests from various VL clients (usually VL
commands). Upon receiving a connect request the server creates a thread for talking
AIX to the client. The -t option in _vlserver defines the maximum number of threads.
This daemons enables:

• Adding erased platters to a media set.

• Mounting additional platters as needed.

• Managing version access.

_qscsiserver This server performs all scsi command.
_mmserver This server performs the migration of the data between the Hard Disk and the media.
_fsi_server HP-UX This Server is a file system interface that allows support of all UNIX commands on
the QStar file systems. It is started for each volume set as a result of a “publish”
Linux request.
It also keeps a list of published volume sets and the associated port number.
_media_server HP-UX A multithread daemon that governs qscsi_server, qscsi_log, jb_server, jb_scheduler,
vl_server, mmserver threads.
Linux
HP-UX It registers itself as a standard mounted daemon. It accepts all mount requests,
responds to mount requests for Integral Volume sets, and redirects other requests to
Linux
the standard mounted daemon.

Page 40 of 54
To verify that all required daemons are running, follow these steps:

1) Log on as root.

2) Run the following commands:

#>qscsiping
qscsiping: SCSI server thread is running.

#>jbping
jbping: JB server thread is running.

#>vlping
vlping: VL server thread is running.

#>mmping
mmping: MM server thread is running.

#>jbschedcheck -a
jbschedcheck: JB Jbscheduler is running.

3) If the jbscheduler daemon is not running, start it now by entering the following command for each jukebox:

jbscheduler device_name

For example:
#>jbscheduler jb
jb: Jbscheduler started

Note: See the jbscheduler command in Chapter 9 - Command Reference for more information.

Page 41 of 54
RECONFIGURING STORAGE DEVICES
Changing the jukebox configuration from a one-drive unit to a two-drive unit.

Change directory to the QStar directory:

cd /opt/QStar

Start the installation script

./INSTALL

QStar software is built for Linux platform kernel 2.6 ix86

Current platform is Linux 2.6 ix86
QStar software version is 5.0.13.709
License Agreement for version 5.0.13.709 was confirmed at:
Thu Jan 15 16:42:12 CET 2009

The installation script will display the following menu:

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit

Enter item number or ? for help: 6 Select #6 to reconfigure QStar Software.

QStar Software Reconfiguration Menu

1) Configure Devices
2) SCSI Classes
3) Return

Enter item number or ? for help: 1 Select #1 to configure the devices.

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 1 Select #1 to list the configured devices.

Real Devices:
1. Jukebox jb
Changer bus=0,target=6,lun=0
Drive 1 bus=0,target=2,lun=0

Page 42 of 54
No simulated devices

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 4 Select #4 to remove all devices previously configured.
_rc: VL: Stopped
_rc: MM: Stopped
_rc: JB: Stopped
_rc: SCSI: Stopped

Real Devices:

1. Jukebox jb
Changer bus=0,target=6,lun=0
Drive 1 bus=0,target=2,lun=0

No simulated devices

Enter y for Yes or n for No.

Remove device 1 from list of configured devices [y]: y

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 1 Select #1 to list the configured devices.

No real devices

No simulated devices

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 6 Select #6 to return to the previous menu.

QStar Software Reconfiguration Menu

1) Configure Devices
2) SCSI Classes
3) Return

Enter item number or ? for help: 3 Select #3 to return to the previous menu.

Page 43 of 54
 QStar Software Installation Main Menu
1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit

Enter item number or ? for help: 9 Select #9 to exit from the installation program.

Now shut down your system, connect the new jukebox with unique SCSI IDs and boot your system back up.
When the system is up, change directory to the QStar directory:

cd /opt/QStar

Start the installation script

./INSTALL

QStar software is built for Linux platform kernel 2.6 ix86

Current platform is Linux 2.6 ix86
QStar software version is 5.0.13.709
License Agreement for version 5.0.13.709 was confirmed at:
Thu Jan 15 16:42:12 CET 2009

The installation script will display the following menu:

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit

Enter item number or ? for help: 6 Select #6 to reconfigure QStar Software.

QStar Software Reconfiguration Menu

1) Configure Devices
2) SCSI Classes
3) Return

Enter item number or ? for help: 1 Select #1 to configure the devices.

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Page 44 of 54
Enter item number or ? for help: 2 Select #2 to add a jukebox.

Getting SCSI probe. Please wait...

Enter jb_name, ? for help, ^ for cancel [jb]: jb Traditional naming convention.

The following SCSI devices have been found:

1. bus=0 target=0 lun=0 Disk id=SEAGATE ST32430W SUN2.1G0666 Å System Disk
2. bus=0 target=1 lun=0 Changer id=HP C1160J 1.47 Å Jukebox Autochanger
3. bus=0 target=4 lun=0 Erasable id=HP C1113J 1.06 Å First Jukebox Drive
4. bus=0 target=5 lun=0 Erasable id=HP C1113J 1.06 Å Second Jukebox Drive
Enter item number for changer, ? for help, ^ for cancel: 2

If robot and drives use different SCSI buses, you must configure the
drives manually. Otherwise drives can be configured automatically.

In this section the reconfiguration is made manually, to follow the automatic configuration see “Specifying Your Storage
Device Configuration” section in this chapter.

Enter y for Yes or n for No.

Do you want to configure drives manually [n]: y

Current device is:

Jukebox jb
Changer bus=0, target=1, lun=0

Enter y for Yes or n for No.

Do you want to configure drive 1 [y]: y

The following SCSI devices have been found:

1. bus=0 target=0 lun=0 Disk id=SEAGATE ST32430W SUN2.1G0666 Å System Disk
2. bus=0 target=1 lun=0 Changer id=HP C1160J 1.47 Å Jukebox Autochanger
3. bus=0 target=4 lun=0 Erasable id=HP C1113J 1.06 Å First Jukebox Drive
4. bus=0 target=5 lun=0 Erasable id=HP C1113J 1.06 Å Second Jukebox Drive
Enter item number for drive 1, ? for help, ^ for cancel: 3

Current device is:

Jukebox jb
Changer bus=0, target=1, lun=0
Drive 1 bus=0, target=4, lun=0

Enter y for Yes or n for No.

Do you want to configure drive 2 [y]: y

The following SCSI devices have been found:

1. bus=0 target=0 lun=0 Disk id=SEAGATE ST32430W SUN2.1G0666 Å System Disk
2. bus=0 target=1 lun=0 Changer id=HP C1160J 1.47 Å Jukebox Autochanger
3. bus=0 target=4 lun=0 Erasable id=HP C1113J 1.06 Å First Jukebox Drive
4. bus=0 target=5 lun=0 Erasable id=HP C1113J 1.06 Å Second Jukebox Drive
Enter item number for drive 2, ? for help, ^ for cancel: 4

Current device is:

Jukebox jb
Changer bus=0, target=1, lun=0
Drive 1 bus=0, target=4, lun=0
Drive 2 bus=0, target=5, lun=0

Page 45 of 54
Enter y for Yes or n for No.
Do you want to configure drive 3 [y]: n

Current device is:

Jukebox jb
Changer bus=0, target=1, lun=0
Drive 1 bus=0, target=4, lun=0
Drive 2 bus=0, target=5, lun=0

Enter y for Yes or n for No.

Add device to list of configured devices [y]: y
Device Configuration Menu
1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return
Enter item number or ? for help: 6 Select #6 to return to the previous menu.

QStar Software Reconfiguration Menu

1) Configure Devices
2) SCSI Classes
3) Return
Enter item number or ? for help: 3 Select #3 to return to the previous menu.

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit
Enter item number or ? for help: 9 Select #9 to exit from the installation program.

Check for missing inquiry Ids...

Unloading q_jb driver...
Unloading q_pdscsi driver...
Loading q_pdscsi driver...
_rc: SCSI: Started
_rc: JB: Started
_rc: MM: Started
_rc: VL: Started
Enter y for Yes or n for No.
Start jbschedulers for configured jukeboxes [y]: y

Page 46 of 54
ADDING NEW STORAGE DEVICES
Change directory to the QStar directory:

cd /opt/QStar

Start the installation script

./INSTALL

QStar software is built for Linux platform kernel 2.6 ix86

Current platform is Linux 2.6 ix86
QStar software version is 5.0.13.709
License Agreement for version 5.0.13.709 was confirmed at:
Thu Jan 15 16:42:12 CET 2009

The installation script will display the following menu:

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit

Enter item number or ? for help: 6 Select #6 to reconfigure QStar Software.

QStar Software Reconfiguration Menu

1) Configure Devices
2) SCSI Classes
3) Return

Enter item number or ? for help: 1 Select #1 to configure the devices.

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 1 Select #1 to list the configured devices.

Page 47 of 54
Real Devices:

1. Jukebox jb
Changer bus=0, target=1, lun=0
Drive 1 bus=0, target=4, lun=0
Drive 2 bus=0, target=5, lun=0

No simulated devices

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 2 Select #2 to add a jukebox.

_rc: VL: Stopped

_rc: MM: Stopped
_rc: JB: Stopped
_rc: SCSI: Stopped

Getting SCSI probe. Please wait...

Enter jb_name, ? for help, ^ for cancel [jb1]: jb1

The following SCSI devices have been found:

1. bus=0 target=0 lun=0 Disk id=SEAGATE ST32430W SUN2.1G0666 Å System Disk
2. bus=0 target=1 lun=0 Changer id=HP C1160J 1.47 Å Jukebox Autochanger
3. bus=0 target=2 lun=0 Erasable id=HP C1716T 3404 Å First Jukebox Drive
4. bus=0 target=4 lun=0 Erasable id=HP C1113J 1.06 Å First Jukebox Drive
5. bus=0 target=5 lun=0 Erasable id=HP C1113J 1.06 Å Second Jukebox Drive
6. bus=0 target=6 lun=0 Changer id=HP C1718T 2.11 Å Jukebox Autochanger
Enter item number for changer, ? for help, ^ for cancel: 6

If robot and drives use different SCSI buses, you must configure the
drives manually. Otherwise drives can be configured automatically.

In this section, the configuration is made manually, to follow the automatic configuration see “Specifying Your Storage
Device Configuration” section in this chapter.

Enter y for Yes or n for No.

Do you want to configure drives manually [n]: y

Current device is:

Jukebox jb1
Changer bus=0, target=6, lun=0

Page 48 of 54
Enter y for Yes or n for No.
Do you want to configure drive 1 [y]: y

The following SCSI devices have been found:

1. bus=0 target=0 lun=0 Disk id=SEAGATE ST32430W SUN2.1G0666 Å System Disk
2. bus=0 target=1 lun=0 Changer id=HP C1160J 1.47 Å Jukebox Autochanger
3. bus=0 target=2 lun=0 Erasable id=HP C1716T 3404 Å First Jukebox Drive
4. bus=0 target=4 lun=0 Erasable id=HP C1113J 1.06 Å First Jukebox Drive
5. bus=0 target=5 lun=0 Erasable id=HP C1113J 1.06 Å Second Jukebox Drive
6. bus=0 target=6 lun=0 Changer id=HP C1718T 2.11 Å Jukebox Autochanger
Enter item number for drive 1, ? for help, ^ for cancel: 3

Current device is:

Jukebox jb1
Changer bus=0, target=6, lun=0
Drive 1 bus=0, target=2, lun=0

Enter y for Yes or n for No.

Do you want to configure drive 2 [y]: n

Current device is:

Jukebox jb1
Changer bus=0, target=6, lun=0
Drive 1 bus=0, target=2, lun=0

Enter y for Yes or n for No.

Add device to list of configured devices [y]: y

Device Configuration Menu

1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 1 Select #1 to list the configured devices.

Real Devices:
1. Jukebox jb
Changer bus=0, target=1, lun=0
Drive 1 bus=0, target=4, lun=0
Drive 2 bus=0, target=5, lun=0
2. Jukebox jb1
Changer bus=0, target=6, lun=0
Drive 1 bus=0, target=2, lun=0

No simulated devices

Page 49 of 54
 Device Configuration Menu
1) List Configured Devices
2) Add Jukebox
3) Add Standalone Drive
4) Remove Device
5) Remove All Devices
6) Return

Enter item number or ? for help: 6 Select #6 to return to the previous menu.

QStar Software Reconfiguration Menu

1) Configure Devices
2) SCSI Classes
3) Return

Enter item number or ? for help: 3 Select #3 to return to the previous menu.

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit

Enter item number or ? for help: 9 Select #9 to exit from the installation program.

Check for missing inquiry Ids...

Unloading q_jb driver...

Unloading q_scsi driver...
Unloading q_pdscsi driver...
Loading q_pdscsi driver...
_rc: SCSI: Started
_rc: JB: Started
_rc: MM: Started
_rc: VL: Started

Enter y for Yes or n for No.

Start jbschedulers for configured jukeboxes [y]: y

Page 50 of 54
DE-INSTALLING QSTAR SOFTWARE
To de-install the QStar Software, follow these steps:
1) Archive all data out of the each Integral Volume's cache.

mmarc -e /mount_point For each mounted Integral Volume set.

2) Unmount all Media sets or Integral Volume sets and stop all jukebox schedulers.

umount /mount_point For each mounted Integral Volume set.

jbshut jb For each jbscheduler running.

3) Change directory to the QStar directory. For example:

cd /opt/QStar

4) Run the installation program by entering:

./INSTALL
QStar software is built for Linux platform kernel 2.6 ix86
Current platform is Linux 2.6 ix86
QStar software version is 5.0.13.709
License Agreement for version 5.0.13.709 was confirmed at:
Thu Jan 15 16:42:12 CET 2009

The installation script will display the following menu:

QStar Software Installation Main Menu

1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit
Enter item number or ? for help: 5 Select #5 to uninstall QStar Software.
Enter y for Yes or n for No.
Do you really want to uninstall [n]: y
Enter y for Yes or n for No.
Do you want to save QStar databases [y]: n
QStar Software uninstalled

Page 51 of 54
 QStar Software Installation Main Menu
1) Install QStar HSM
2) Install QStar CD/DVD-ROM Axxess
3) Install QStar CD/DVD-R Master
4) Install QStar Data Director
5) Uninstall QStar Software
6) Reconfigure QStar Software
7) Restore QStar Databases
8) Upgrade QStar Software
9) Exit
Enter item number or ? for help: 9 Select #9 to exit from the installation program.

5) Remove the contents of the QStar directory.

rm -r /opt/QStar/*

Page 52 of 54
PRIVILEGED USERS
Usually only the System Administrator as root can run the QStar commands.
QStar creates a special option that, if required, allows non-root users to run QStar commands.

QStar creates a special file called “priv.users” under the /opt/QStar/install directory.

Edit this file and insert the name(s) of the user(s) that should be allowed access to run all QStar commands.
Please insert one name for each line and save the file.
After that all the users that are listed in this file are allowed access to run the QStar commands.

SEND MAIL NOTIFICATION

QStar creates a special file called “send_notification” under the /opt/QStar/install directory.

The System Administrators can get mail notification about abnormal events in the QStar Software.
Abnormal events are - drive/jukebox failures, unrecoverable write errors, requests for additional medium (no more space
in the Integral Volume set), requests for medium that is currently offline, etc.
QStar Software puts messages into the /opt/QStar/log/message file and then executes this script.
To receive the mail, please select the appropriate mail program for your computer and set the
DESTINATION_MAIL_ADDRESS ( [email protected] ).

To test this script please create /opt/QStar/log/message file and execute the script.

DESTINATION_MAIL_ADDRESS=
if [ -n "$DESTINATION_MAIL_ADDRESS" -a -f /opt/QStar/log/message ]; then
#
# /bin/mail $DESTINATION_MAIL_ADDRESS < /opt/QStar/log/message
# /usr/sbin/Mail -s "message from QStar server" $DESTINATION_MAIL_ADDRESS < /opt/QStar/log/message
# /usr/sbin/mailx -s "message from QStar server" $DESTINATION_MAIL_ADDRESS < /opt/QStar/log/message
# /usr/bin/mailx -s "message from QStar server" $DESTINATION_MAIL_ADDRESS < /opt/QStar/log/message
#
mv /opt/QStar/log/message /opt/QStar/log/message.old
fi

Page 53 of 54
START OR STOP QSTAR SERVERS
As explained in Step 8 “Post Installation Test” the section QStar Software adds different daemons to the system and
automatically starts them at boot up. To do so QStar creates a special file called “rc” under the /opt/QStar/install directory that
is run at the time of boot up.
This is very useful for starting and stopping the QStar servers without rebooting the system.
Before stopping the QStar servers the System Administrator must be sure to unmount all the Integral Volume sets.

To stop the QStar Servers, enter: /opt/QStar/install/rc stop

To start the QStar Servers, enter: /opt/QStar/install/rc start

The “rc” file will return the confirmation messages for the stopping or starting procedure.

Page 54 of 54
This chapter describes the basic notions of the jukebox management, the device’s identifications, the jukebox parameters and
some jukebox management features of the QStar Software that let you recover from errors introduced by accident or caused by
hardware failure.
Topics include:
• Checking jukebox status and parameters

• Displaying jukebox statistics information

• Setting the media or drives on/offline

• Error recovery

• Selected errors

• Use of media not supported by the jukebox

BASIC NOTIONS OF JUKEBOX MANAGEMENT .......................................................................... 2

Jbscheduler .................................................................................................................................. 2
Element Status: Online/Offline ................................................................................................ 2
Jukebox or Standalone Drive Identification .......................................................................... 2
JUKEBOX PARAMETERS ................................................................................................................. 3
Time Control ................................................................................................................................ 3
Persistent Parameters................................................................................................................ 3
MANAGING THE JUKEBOX PARAMETERS................................................................................... 4
JUKEBOX STATISTICS.................................................................................................................... 5
MANAGING THE JUKEBOX STATISTICS ..................................................................................... 6
FEATURE JB COMMANDS............................................................................................................... 8
Displaying the Jukebox Status................................................................................................. 9
Setting the Drive Profile and Priority.................................................................................... 11
Examples of Controlling the Jukebox Using the JB Commands...................................... 13
Example 1 - Importing Media into the Jukebox and Checking
the Status of the Jukebox........................................................................... 13
Example 2 - Exporting Media from the Jukebox and Checking
the Status of the Jukebox........................................................................... 13
Example 3 - Setting a Drive and Shelf Offline, Loading a Media into a Drive
and then Checking the Jukebox Status ................................................... 14
Example 4 - Unloading a Media from the Drive, Setting the Drive
and Shelf Online and then Checking the Jukebox Status.................... 14
ERROR RECOVERY ........................................................................................................................ 15
Selected Errors .......................................................................................................................... 15
Examples of Recovery after a Hardware Failure Using the JB Commands .................. 15
Example 1 - Clearing Drive and Shelf Bad Status ......................................................... 15
Example 2 - Clearing a Drive Bad Status........................................................................ 17
Example 3 - Clearing a Shelf Bad Status ........................................................................ 17
Example of Recovery for Lost Source Shelf Information ................................................. 18
Example - Clearing Lost Source Shelf Information Error............................................. 18
Example of Recovery for Unknown Shelf Type Information............................................ 19
Example - Clearing Unknown Shelf Type Information Error ....................................... 19
USE OF MEDIA NOT SUPPORTED BY THE JUKEBOX.............................................................. 20
MEDIA IMPORTED VIA FRONT PANEL OF JUKEBOX INSTEAD OF VIA QSTAR................. 20

Page 1 of 20
BASIC NOTIONS OF JUKEBOX MANAGEMENT
Jbscheduler
The jbscheduler is activated by the jbscheduler command and deactivated by the jbshut 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 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 jbload
command or flipped by the jbflip command.

Element Status: Online/Offline

If the jbscheduler is running it does not mean that it controls all elements in the jukebox. 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
jbload command or flipped by the jbflip command. An application can change the online/offline status of the drives or shelves
by using the jbdrive command or jbshelf command.

Jukebox 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 jukebox control device, which accepts the changers SCSI commands, is a symbolic link to
the filename representing the changers 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 jukebox 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 jukebox operations with the control device call for operator intervention.

Page 2 of 20
JUKEBOX 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 jukebox 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 jukebox 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 jukebox control daemon called jbscheduler. The special jbdriver in
the operating system’s kernel supports the jukebox management interface. They are set when the jukebox management software
is configured for the jukebox and can be cleared or set to their default values using the jbparam command.

Page 3 of 20
MANAGING THE JUKEBOX PARAMETERS
To view the current jukebox parameter values, Quantum, Inactive and Idle times, and statistical information, number of
Imports, Exports, Loads, Unloads and Flips, use the jbparam command.

To display the current values for a jukebox identified as jb, enter:

#>jbparam jb
Inactive time: 900
Idle time: 0
Quantum time: 10
Imports: 0
Exports: 0
Loads: 1239
Unloads: 12
Flips: 3754

To modify the jukebox parameters, use the jbparam command with the following flags:

-i Set inactive time

-q Set quantum time
-d Set idle time

To reset the jukebox statistical information, use the jbparam command with the following flags:

-t Set all time parameters to their default values

-s Clear the statistics values
-f Allow jbscheduler to control the front panel of the jukebox.
-F Prohibit jbscheduler to control the front panel of the jukebox.

Note: For more detailed information on the jbparam command, please refer to Chapter 9 - Command Reference in this
manual.

Page 4 of 20
JUKEBOX STATISTICS
QStar Software provides statistics for the elements within the jukebox. These statistics allow the administrator to monitor for
potential problems with the media and drives within the jukebox. 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 jukebox is full and media needs to be
taken offline, these statistics will identify the less frequently accessed media. The jbstatistics command allows jukebox statistic
information to be printed 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.

Page 5 of 20
MANAGING THE JUKEBOX STATISTICS
To view the current jukebox Loads, Recover, Bad, PDL and SDL statistical information use the jbstatistics command.

To display the current statistics information for a jukebox identified as jb, enter:

#>jbstatistics jb
jb Loads Recover Bad PDL SDL
1a 0 0 0
1b 0 0 0
2a 5 0 0
2b 0 0 0
3a 0 0 0
3b 0 0 0
4a 0 0 0
4b 0 0 0
5a 0 0 0
5b 0 0 0
6a 0 0 0
6b 0 0 0
7a 0 0 0
7b 0 0 0
8a 0 0 0
8b 0 0 0
9a 0 0 0
9b 0 0 0
10a 0 0 0
10b 0 0 0
11a 0 0 0
11b 0 0 0
12a 0 0 0
12b 0 0 0
13a 0 0 0
13b 0 0 0
14a 0 0 0
14b 0 0 0
15a 0 0 0 36
15b 0 0 0
16a 13 0 0 2 12
16b 10 0 0 13 43
drive 1 6 2 0
drive 2 9 0 1
drive 3 9 0 0
drive 4 20 0 0
carrier 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.

Page 6 of 20
To display and sort the jukebox statistical information parameters, use jbstatistics with the following flags:

-S [LRBPS]
Print statistics in descending order according to the value of number of loads (L), number of recovered errors (R),
number of cases when a shelf/drive was marked bad (B), number of PDL blocks (P), or number of SDL blocks (S).

To clear the jukebox statistical information use jbstatistics with the following flags:

-C [LRBPS...]
Clear statistics for number of loads (L), number of recovered errors (R), number of cases when a shelf/drive
was marked bad (B), number of PDL blocks (P), number of SDL blocks (S).

-Ca
The -Ca is equal to -CLRBPS and clears all numbers.

Note: For more detailed information on the jbstatistics command, please refer to Chapter 9 - Command Reference in this
manual.

Page 7 of 20
FEATURE JB COMMANDS
The JB module allows various operations with the jukebox and its elements (shelves, drives, carriers, and mailslots).
All the jb commands are available once the jukebox scheduler is running.

The commands that enable and disable the jukebox driver are:

jbscheduler Start the jukebox driver (usually this command is automatically run at boot time).
jbshut Shut down the jukebox driver.

The movement commands are the following:

jbload Move a media from the shelf to the drive

jbunload Move a media from the drive back to the shelf
jbflip Invert a media in the drive
jbexport Move a media from the shelf or drive to the mailslot
jbimport Move a media from the mailslot to the shelf.
jbmove Moves a media from one shelf to another in the jukebox.
jbmagazine Exchanges media in the jukebox using the magazines.

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

jbreset Can clear the bad status of a drive and shelf in a single command when an error has occurred.
jbshelf Can set online/offline the media into the selected shelf and can clear the bad status of the shelf when
the error occurred.
jbdrive Can set online/offline the drive media into the selected shelf and can clear the bad status of the shelf when the
error occurred.
jbstatus Can show the status of the jukebox, including drives, shelves, mailslot and carriers.
jbparam Can show and change the parameters of the jukebox, including idle, inactive and quantum times, also
the number of imports, exports, loads, unloads and flips.
jbstatistics Can show and clear the statistics of the jukebox, including load, recover, PDL and SDL information.

Page 8 of 20
Displaying the Jukebox Status
The jbstatus command is used to display the jukebox status, including the drives, shelves, mailslot and carriers. The jbstatus
command can be run with different options please refer to Chapter 9 - Command Reference in this manual.
The jbstatus command is a useful tool to monitor the jukebox status and to detect which jukebox component may be failing.

Example for an Optical jukebox.

To display the status for a jukebox identified as jb, enter:

#>jbstatus jb
DISK-jb – JUKEBOX TYPE
-----------
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: online empty
Drive 2: online empty
Drive 3: online full loaded shelf 2a
Drive 4: offline empty
-----------
Shelf 1: online full
Shelf 2: online loaded open drive 3
Shelf 2: online full
Shelf 3: online full
Shelf 4: online full
Shelf 5: online empty
Shelf 6: online empty
Shelf 7: online empty
Shelf 8: online empty
Shelf 9: online empty
Shelf 10: online full
Shelf 11: online full
Shelf 12: online empty
Shelf 13: online empty
Shelf 14: online empty
Shelf 15: online empty
Shelf 16: online empty
Shelf 17: online empty
Shelf 18: online empty
Shelf 19: online empty
Shelf 20: online empty

Page 9 of 20
Example for a CD/DVD jukebox.

#>jbstatus jb
DVD-jb – JUKEBOX TYPE
-----------
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: cd-rom dvd-rom dvd-ram online empty
Drive 2: cd-rom dvd-rom dvd-ram online empty
Drive 3: cd-rom dvd-rom online empty
Drive 4: cd-rom dvd-rom online empty
Drive 5: dvd-rom dvd-r online empty
Drive 6: cd-rom cd-r cd-rw online empty
-----------
Shelf 1: dvd-ram online full magazine 1
Shelf 2: dvd-ram online full magazine 1
Shelf 3: dvd-ram online full magazine 1
Shelf 4: dvd-ram online full magazine 1
Shelf 5: dvd-ram online full magazine 1
Shelf 6: dvd-ram online full magazine 1
Shelf 7: dvd-r online full magazine 1
Shelf 8: dvd-r online full magazine 1
Shelf 8: dvd-ram online full magazine 1
Shelf 9: dvd-ram online full magazine 1
Shelf 10: dvd-ram online full magazine 1
Shelf 11: online empty magazine 2
Shelf 12: cd-rom 1-side online full magazine 2
Shelf 13: cd-rom 1-side online full magazine 2
Shelf 14: online empty magazine 2
Shelf 15: dvd-rom 1-side online full magazine 2
Shelf 16: online empty magazine 2
Shelf 17: cd-r 1-side online full magazine 2
Shelf 18: cd-r 1-side online full magazine 2
Shelf 19: cd-rom cd-r cd-rw dvd-rom dvd-r dvd-ram online full magazine 2
Shelf 20: cd-rom cd-r cd-rw dvd-rom dvd-r dvd-ram online full magazine 2

Note: The jbstatus command for CD/DVD device shows the magazine number information, the drives capabilities and media
type within the shelves. Before the refresh procedure (vlrefresh command) all media capabilities are assigned for every full
shelf (i.e shelves 19 and 20). 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 and “1-side” information will be
assigned if the media is single sided and the jukebox also supports dual sided media. After that, the jbscheduler will only allow
the proper media to be loaded into the drive that can handle this media type. For example, the media loaded into the shelf with a
“cd-r” status may be inserted only into the CD-R drive. Once the CD-R media is burned and becomes a CD-ROM media, the
QStar Software will automatically change the “cd-r” status to “cd-rom” . The shelf’s media type can also be manually cleared
or changed using the “-r” or “-p” option with the jbshelf command. The “1-side” information can be changed using the “-1”
flag.

Page 10 of 20
Setting the Drive Profile and Priority
Using the jbdrive command is possible to change the drive profile and the drive priority. These options are mostly used with
drive that support different type of media, like the DVD multi-function drive. Modifying the drive profile is possible to set a
drive for read only operation or write only operation. Changing the drive priority is possible to decide which drive should be
used mostly for the read operation or for the write operation or both read and write operation.

jbdrive [-H host_name] [-nfbr] [-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}] device_name drive_number

Note: For more detailed information on the jbdrive command, please refer to Chapter 9 - Command Reference in this manual.

To modify the drive profile, use the jbdrive command with the following flag:

-p [cd-rom | cd-r | cd-rw | dvd-rom | dvd-r | dvd-ram | dvd-rw | dvd-rw-s]

This flag is used primarily for jukeboxes with CD-ROM, CD-R, DVD-ROM, DVD-R, DVD-RAM 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.

To set the priority for the usage of the drive, use the jbdrive command with the following flag:

-u [priority_number | rrr:www:rw | auto | default]

This flag is used mostly for jukeboxes with CD-ROM, CD-R,DVD-ROM, DVD-R and DVD-RAM drives present. The priority
defines the order in which the drive's are used by jbscheduler when it is looking for an appropriate drive. Example, in a jukebox
with 4 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.

Example for a CD/DVD jukebox with multi-function drives.

To display the original profile of the multi-functional drives, enter:

#>jbstatus jb
DVD-jb – JUKEBOX TYPE
----------
Carrier 1: empty
Carrier 2: empty
----------
Mailslot 1: empty
----------
Drive 1: cd-rom cd-r cd-rw dvd-rom dvd-r dvd-ram dvd-rw dvd-rw-s online empty
Drive 2: cd-rom cd-r cd-rw dvd-rom dvd-r dvd-ram dvd-rw dvd-rw-s online empty

Page 11 of 20
To modify the drive 1 profile for read only operation, enter:

#>jbdrive –p cd-rom –p dvd-rom –p dvd-ram jb 1

To modify the drive 2 profile for write only operation, enter:

#>jbdrive –p cd-r –p cd-rw –p dvd-r –p dvd-rw –p dvd-rw–s –p dvd-ram jb 2

To display the new profile of the multi-functional drives, enter:

#>jbstatus jb
DVD-jb – JUKEBOX TYPE
-----------
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: cd-rom dvd-rom dvd-ram online empty
Drive 2: cd-r cd-rw dvd-r dvd-ram dvd-rw dvd-rw-s online empty

To set the generic priority equal 1 for a drive, enter:

#>jbdrive –u 1

To set the specific read and write priority for a drive, enter:

#>jbdrive –u 3:2:1

Note: The priority number go from 1 up to 128.

Page 12 of 20
Examples of Controlling the Jukebox Using the JB
Commands
Example 1 - Importing Media into the Jukebox and Checking the
Status of the Jukebox
#>jbimport jb 1

#>jbimport jb 2

#>jbimport jb 3

#>jbstatus jb
DISK-jb – JUKEBOX TYPE
-----------
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: online empty
Drive 2: online empty
-----------
Shelf 1: online full Note: Shelves 1,2,3 are full.
Shelf 2: online full
Shelf 3: online full
Shelf 4: online empty

Example 2 - Exporting Media from the Jukebox and Checking the

Status of the Jukebox
#>jbexport jb 2
jb: Please remove medium from mailslot.

#>jbstatus jb
DISK-jb – JUKEBOX TYPE
-----------
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: online empty
Drive 2: online empty
-----------
Shelf 1: online full
Shelf 2: online empty Note: Shelf 2 is empty.
Shelf 3: online full
Shelf 4: online empty

Page 13 of 20
Example 3 - Setting a Drive and Shelf Offline, Loading a Media into a
Drive and then Checking the Jukebox Status
#>jbdrive -f jb 1
jb drive 1: is set offline

#>jbshelf -f jb 1
jb shelf 1: is set offline

#>jbload jb 1 1a

#>jbstatus -d jb
Drive 1: offline full loaded shelf 1a Note: Drive status is changed.
Drive 2: online empty

#>jbstatus -s jb
Shelf 1: offline loaded drive 1 Note: Shelf status is changed.
Shelf 2: online empty
Shelf 3: online full
Shelf 4: online empty

Example 4 - Unloading a Media from the Drive, Setting the Drive and
Shelf Online and then Checking the Jukebox Status
#>jbunload jb 1

#>jbdrive -n jb 1
jb drive 1: is set online

#>shelf -n jb 1
jb shelf 1: is set online

#>jbstatus jb
DISK-jb – JUKEBOX TYPE
-----------
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: online empty
Drive 2: online empty
-----------
Shelf 1: online full
Shelf 2: online empty
Shelf 3: online full
Shelf 4: online empty

Note : For more detailed information on the jb commands, please refer to Chapter 9 - Command Reference in this manual.

Page 14 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 the jbstatus command. If the drive, with or without a media, is marked as Bad,
then try to recover with the jbreset command. This will clear the Bad status 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 jbstatus for the current status of the jukebox. If a Bad
status is still displayed on a shelf or drive, it can be cleared by using the jbshelf or jbdrive command.

Selected Errors
The commands you need to use to recover from most hardware failure or human errors are:
jbstatus
jbreset
jbdrive
jbshelf

Examples of Recovery after a Hardware Failure Using the

JB Commands
Example 1 - Clearing Drive and Shelf Bad Status
When a drive is marked bad you will see the following message appear in the console window:

JB: jb drive 1 marked bad, sense 00 00 00

To recover the correct status of the jukebox components, follow these steps:

#>jbstatus jb
DISK-jb – JUKEBOX TYPE
-----------
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: online full bad loaded shelf 1a Note: Drive is marked bad.
Drive 2: online empty
-----------
Shelf 1: online loaded bad open drive 1 Note: Shelf is marked bad.
Shelf 2: online full
Shelf 3: online full
Shelf 4: online empty

Page 15 of 20
a) Automatically

#>jbreset jb 1
jb drive 1: is set offline
jb shelf 1: is set offline
jb drive 1: is set online
jb shelf 1: is set online

b) Manually

#>jbdrive -bf jb 1
jb drive 1: is set offline

#>jbshelf -bf jb 1
jb shelf 1: is set offline

#>jbdrive -n jb 1
jb drive 1: is set online

#>jbshelf -n jb 1
jb shelf 1: is set online

In either of the above procedures, the status of the jukebox should appear as follows:

#>jbstatus jb
DISK-jb – JUKEBOX TYPE
-----------
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: online empty Note: Drive is unloaded and bad flag cleared.
Drive 2: online empty
-----------
Shelf 1: online full Note: Shelf’s bad flag cleared.
Shelf 2: online full
Shelf 3: online full
Shelf 4: online empty

Note: QStar highly recommends checking the status of the drive and shelf after jbreset command. If the jukebox is a DVD
jukebox it is also recommended checking if the media type information is correct. If the media type information is different or
not displayed, use the jbshelf -r command to reset the media type information and refresh the shelf using the vlrefresh
command.

Page 16 of 20
Example 2 - Clearing a Drive Bad Status
#> jbstatus -d jb
Drive 1: online bad empty Note: Drive is marked bad.
Drive 2: online empty

#> jbdrive -b jb 1

#> jbstatus -d jb
Drive 1: online empty Note: Drive bad flag is cleared.
Drive 2: online empty

Example 3 - Clearing a Shelf Bad Status

#>jbstatus -s jb
Shelf 1: online loaded drive 1
Shelf 2: online bad full Note: Shelf is marked bad.
Shelf 3: online full

#>jbshelf -b jb 2

#>jbstatus -s jb
Shelf 1: online loaded drive 1
Shelf 2: online full Note: Shelf’s bad flag is cleared.
Shelf 3: online full

Page 17 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 jukebox loads media into a drive and because of a hardware error, forgets which shelf the media came from. The
jbstatus command output displays this media as having lost the source shelf information.
The QStar Software redirects the following message into the /opt/QStar/log/syslog file as well as displaying it on the console:

JB: jb drive 1: Source shelf information lost - use jbreset

To clear this error the System Administrator must use the jbreset command additionally specifying an empty shelf number
that will be used by the QStar Software as the destination for this media.

Example - Clearing Lost Source Shelf Information Error

#>jbstatus jb
DISK-jb – JUKEBOX TYPE
-----------
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: online full lost source shelf Note: Drive is full with unknown media.
Drive 2: online empty
-----------
Shelf 1: online empty
Shelf 2: online full
Shelf 3: online full
Shelf 4: online empty

#>jbreset jb 1 1 Note: Shelf 1has been selected as the destination shelf.

#>jbstatus jb
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: online empty Note: Drive is empty and the error is cleared.
Drive 2: online empty
-----------
Shelf 1: online full Note: Shelf is full.
Shelf 2: online full
Shelf 3: online full
Shelf 4: online empty

Page 18 of 20
Example of Recovery for Unknown Shelf Type Information
This error can be introduced by a hardware failure during the refreshing operation executed with the vlrefresh command and it
is specific for DVD/CD jukeboxes 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 jukebox loads media into a drive and because of a hardware error could not detect the media type of
the shelf, the QStar Software automatically will removes all the profile information for the shelf in order to force the System
Administrator to refresh the shelf once again. The jbstatus command output displays this shelf without the media type
information. Using the jbshelf command with -r flag it is possible to reset all profile information for the media to determine the
correct media type for the shelf at the next refresh.

Example - Clearing Unknown Shelf Type Information Error

#>jbstatus jb
DVD-jb – JUKEBOX TYPE
------------
Carrier 1: empty
------------
Mailslot 1: empty
------------
Drive 1: cd-rom dvd-rom dvd-r dvd-ram online empty
Drive 2: cd-rom dvd-rom dvd-r dvd-ram online empty
Drive 3: cd-rom dvd-rom dvd-r dvd-ram online empty
Drive 4: cd-rom dvd-rom dvd-r dvd-ram online empty
------------
Shelf 1: cd-rom 1-side online full
Shelf 2: online full Note: The Shelf 2 is displayed without media type
Shelf 3: dvd-ram online full information.
Shelf 4: dvd-r 1-side online full

#>jbshelf -r jb 2
jb shelf 1: is set online cd-rom dvd-rom dvd-r dvd-ram
Shelf 1: cd-rom dvd-rom dvd-r dvd-ram online full

#>jbstatus jb
DVD-jb – JUKEBOX TYPE
------------
Carrier 1: empty
------------
Mailslot 1: empty
------------
Drive 1: cd-rom dvd-rom dvd-r dvd-ram online empty
Drive 2: cd-rom dvd-rom dvd-r dvd-ram online empty
Drive 3: cd-rom dvd-rom dvd-r dvd-ram online empty
Drive 4: cd-rom dvd-rom dvd-r dvd-ram online empty
------------
Shelf 1: cd-rom 1-side online full
Shelf 2: cd-rom dvd-rom dvd-r dvd-ram online full
Shelf 3: dvd-ram online full
Shelf 4: dvd-r 1-side online full

Note: The Shelf 2 is displayed with all media capabilities. The media type of the shelf will be reassigned by running the
vlrefresh command for the specific shelf.

Page 19 of 20
USE OF MEDIA NOT SUPPORTED BY THE JUKEBOX
This type of incident is rare, but could happen if the manufacturer’s drive does not support the type of media that you are trying
to use. Assume that you import a WORM disk into a jukebox that only supports rewritable disks. Jbscheduler, after loading the
disk into the drive, cannot spin the disk and make it ready for use. Thus, jbscheduler will not unblock the I/Os that were issued
to the disk. The jbstatus command shows that the imported disk and the drive in which it is loaded are marked Bad.
The only way to properly unblock the I/O is by using the jbreset command. The jbexport command should be run to export the
wrong disk, use jbstatus to check that no bad flags were set. If this fails, try jbunload or ejecting the media from the front panel
of the jukebox.

MEDIA IMPORTED VIA FRONT PANEL OF JUKEBOX INSTEAD

OF VIA QSTAR
This can happen with some jukebox models as the front panel of the jukebox prompts the user to import the media to a shelf as
it is inserted into the mailslot. Should this happen, an updated jukebox map is needed. This can be achieved by running the
jbstatus command (jbstatus device_name). This will refresh the jbdriver so it will know that the shelf is now occupied.

Page 20 of 20
This chapter describes the basic notions of the Volume Librarian (VL) and the relationship between VL and the devices (media,
jukebox 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 attached to the system and offline from the system. Details of recovery procedures in the
event of VL database inconsistency.

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
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 ................................................................................................. 7
MANAGING MEDIA VIA THE VL DATABASE............................................................................... 7
VL MEDIA SET RELATED COMMANDS......................................................................................... 7
MANAGING THE VL DATABASE .................................................................................................... 8
Importing and Exporting the Media ........................................................................................ 8
Erasing the Media ....................................................................................................................... 9
Refreshing the Media ............................................................................................................... 10
Creating an Integral Volume Set........................................................................................... 10
Creating an Integral Volume Set with the SDF File System........................................ 11
Database Backup Configuration Option ....................................................................... 12
Additional Shredding Options for Optical Archive Media.......................................... 16
Additional Compression Option for Tape Archive Media .......................................... 16
Creating an Integral Volume Set with the UDF or ISO 9660 File System................ 17
Creating an Integral Volume Set with Single-Volume and Automount
Interchange Level............................................................................................................. 17
Creating an Integral Volume Set with Spanning Interchange Level ..................... 20
Additional Options for CD/DVD-ROM Archive Media with UDF and
ISO 9660 File System .......................................................................................................... 21
Creating a Set with No Media File System ...................................................................... 22
Creating and Adding a Cache to an Integral Volume Set ................................................ 22
Modifying the Cache for an Integral Volume Set ............................................................... 24
Adding Media to an Integral Volume Set............................................................................. 24
Adding Media to an SDF Integral Volume Set ................................................................ 25
Adding Media to an UDF or ISO 9660 Integral Volume Set ........................................ 25
Adding Media to a UDF or ISO 9660 Integral Volume Set Specifying
the Logical Volume ID.......................................................................................................... 26

Page 1 of 100
 Displaying Integral Volume Set Information ...................................................................... 27
Displaying the Information for the SDF File System and Optical Media................... 27
Displaying the Information for the SDF File System and Tape Media....................... 28
Displaying the Information for the UDF File System with the Single-Volume
Interchange Level and DVD-RAM Media .......................................................................... 28
Displaying the Information for the UDF File System with the Automount
Interchange Level and DVD-RAM Media .......................................................................... 29
Displaying the Information for the UDF or ISO 9660 File System with
the Automount Interchange Level and CD/DVD-ROM Media ...................................... 29
Displaying the Information for the UDF File System with the Automount
Interchange Level and CD/DVD-R or BD-RS Media and Packet Writing................... 30
Displaying the Information for the UDF File System with the Spanning
Interchange Level and Optical Media ............................................................................... 30
Displaying the Information for the UDF File System with the Spanning
Interchange Level and CD/DVD-R or BD-RS Media and Packet Writing................... 31
Displaying the Information for the No Media File System ........................................... 31
VL JUKEBOX RELATED COMMANDS .......................................................................................... 34
Main Information for the Media in the VL Database ......................................................... 34
Displaying the Jukebox Media and Shelf Information....................................................... 35
Displaying jukebox shelf Information for the SDF and UDF File Systems ............... 36
FIXING VL DATABASE INCONSISTENCIES.............................................................................. 37
Fixing a Database Inconsistency after a Jukebox Hardware Failure ............................. 37
Fixing Database Inconsistencies after a Media has been Manually Removed
from the Jukebox ...................................................................................................................... 40
MANAGING OFFLINE MEDIA UNDER VL CONTROL ................................................................ 41
Managing Offline Media ........................................................................................................... 41
Canceling a Request for Offline Media ................................................................................ 44
Managing Offline Integral Volume Sets ............................................................................... 44
MANAGING OFFLINE MEDIA UNDER VL CONTROL USING THE MAGAZINE OR PACK
IMPLEMENTATION......................................................................................................................... 45
ADDING MEDIA TO AN INTEGRAL VOLUME SET.................................................................... 50
Media Available.......................................................................................................................... 50
No Media Available ................................................................................................................... 50
RESTORING AN INTEGRAL VOLUME SET................................................................................. 51
Restoring an Integral Volume Set not Known to the VL Database ................................ 51
Restoring an Integral Volume Set after a Software Upgrade ......................................... 51
Restoring an Exported Integral Volume Set Deleted from the VL Database ............... 52
DATA COMPACTION UNDER VL CONTROL............................................................................... 54
Data Compaction Feature for the SDF File System ........................................................... 55
Data Compaction Feature Using the Reallocation Only Option....................................... 58
Data Compaction not Available.............................................................................................. 60
ERROR RECOVERY ........................................................................................................................ 60
THE COPY AND COMPARE MEDIA UTILITIES .......................................................................... 61
Copy and Compare Media without VL Control (SDF Only)............................................... 61
Substitute the Original Copy of the Media with the Exact Duplicate......................... 62
Copy and Compare Media Under VL Control....................................................................... 62
Substitute the Original Copy of the Media with the Duplicate .................................... 66
Automated Copy Media Under VL Control ........................................................................... 68

Page 2 of 100
VL CONFIGURATION PROPERTIES FILE ................................................................................... 71
Displaying and Setting the General VL Configuration Properties ................................... 72
Displaying and Setting the VL Configuration Threshold Blank/Erased
Media Properties........................................................................................................................ 72
Displaying and Setting the VL Configuration for Offline Media Request Properties ... 72
Displaying and Setting the VL Configuration for the Export Root
Directory Location..................................................................................................................... 72
Displaying and Setting the VL Configuration for the Remote
Administration Properties........................................................................................................ 73
Displaying and Setting the VL Configuration for the Big Space Root
Directory Properties ................................................................................................................. 73
Displaying and Setting the VL Configuration for the Minimum File System
Space Available ......................................................................................................................... 74
Displaying and Setting the QStar Server Port Configurations ........................................ 74
DELAYED JOBS UNDER VL SCHEDULER CONTROL................................................................ 75
Displaying the Delayed Jobs under VL Scheduler Control ............................................... 75
Displaying and Setting the VL Configuration CD/DVD-R Delayed Recording
Properties ................................................................................................................................... 76
Starting the Delayed Recording Procedure ..................................................................... 77
Examples of Delayed Write Procedure Using the Any Shelf Option....................... 79
Examples of Delayed Write Procedure Using a Specified Shelf .............................. 80
Displaying and Setting the Delayed VL Configuration Copy Media Properties ............ 81
Starting the Delayed Copy Media Procedure .................................................................. 82
Examples of the Delayed Copy Media Procedure Specifying the Destination
Shelf .................................................................................................................................... 83
Examples of the Delayed Copy Media Procedure without Specifying the
Destination Shelf .............................................................................................................. 83
Displaying and Setting the Delayed VL Configuration Compare Media Properties..... 84
Starting the Delayed Compare Media Procedure........................................................... 84
Examples of Delayed Compare Media Procedure ...................................................... 85
Displaying and Setting the Delayed VL Configuration Data Compaction Properties.. 86
Starting the Delayed Data Compaction Procedure........................................................ 86
Examples of Delayed Data Compaction Procedure ................................................... 87
Displaying and Setting the VL Configuration Delayed Erase Media Properties ........... 88
Starting the Delayed Erase Procedure ............................................................................. 88
Examples of Delayed Erase Media Procedure............................................................. 89
Displaying and Setting the VL Configuration Delayed Archive Properties.................... 90
Starting the Delayed Archive Procedure.......................................................................... 90
Examples of Delayed Archive Procedure ..................................................................... 91
Displaying the Delayed Jobs Status in the Delayed Jobs Queue List ............................ 92
Displaying the Delayed Jobs Status for a Single Job .................................................... 93
Displaying the Delayed Jobs Status for Different Delayed Jobs................................. 94
Displaying the Delayed Jobs Status in Long Format..................................................... 96
Moving Delayed Jobs from the Delayed Jobs List .............................................................. 98
Deleting Delayed Jobs from the Delayed Jobs List............................................................ 99
DISPLAYNG ERROR CONDITIONS FOR DELAYED JOBS.................................................. 100

Page 3 of 100
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 jukebox 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 jukebox 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 can be referred to in different ways depending on the type of
configuration specified by the System Administrator as follows:

“Set” or “Media set”: Is a group of media in the jukebox associated to a same set.

“Integral Volume set”: Is a group of media that appears as one continuously growing disk space associated to a set with a
cache, so the Media set is mounted with a front end cache.

Electronic Labeling
The key to each archival medium 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 jukebox, the QStar Software prompts the Administrator to “retrieve volume 101
from the storage facility and place it in jukebox 1”. Once inserted, the database changes the new location for volume 101 to
jukebox 1.

Dynamic Media Allocation

As Media sets fill with data, it may be necessary to add additional media. The QStar Software can automatically allocate
additional media to a set. The user benefits, because no time is spent resolving a request for more space. The QStar Software
simply appends additional media to the Media set, and the user’s write request is satisfied. The System Administrator may also
define their own allocation policies for staggering Media 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 set, or
the maximum number of archival media in a set, at set creation time. This feature gives the System Administrator additional
control over the use of the Media sets, particularly against runaway processes that consume more space than expected. Quotas
can be increased after a Media set is created.
If a 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 Media 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 a set as needed. The
additional disk or tape is appended to the online Media set without interrupting any current processes using the set.

Page 4 of 100
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. That means the host devices can be distributed between several domains. A domain is identified by its name. For
every domain, a host belongs to there is a subdirectory in the /opt/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 jukebox 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. /opt/QStar/dev/jb for Solaris, /dev/jb0 for AIX IBM) is the name used in the
JB functions and commands. The last component of this name (jb 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 volume set. Each volume has its 0-based volume number. If a volume is loaded into the device (on the
shelf in a jukebox or into a standalone drive) it is online. Otherwise, it is considered offline and the Volume Librarian maintains
its offline location.

Volume Set
A sequence of volumes integrated as a single unit. For example, a file system containing a couple of surfaces is a set. A Media
set has a name (set name) and attributes. A medium belonging to a Media set can be online (residing in the jukebox or
standalone drive) or offline (outside the jukebox 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 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, sets and archives on the current
host. The root database directory (/opt/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 set, this directory contains a set database. A set database is a file whose name matches the set name.

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

Set Id
A string of characters which are normally written on every volume and identifying the set, this volume belongs to.

Surface Id
A string of characters which is normally written on every surface and identifying the volume within the set.

Refreshing
To build the state of the surfaces, the Volume Librarian has to examine the existence of the medium (on the shelf or in the
standalone drive), read information from the existing media and populate the VL database. This procedure is called refreshing.
Importing a medium into a jukebox also causes the medium 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 set dynamically.

Page 6 of 100
USING THE VOLUME LIBRARIAN
The VL module manages the media in the jukebox and allows the QStar Software to track all media in and out of the jukebox.
The Volume Librarian module makes it possible to configure the entire jukebox as a unique volume or to create multiple
volumes inside the same or multiple jukeboxes. Using the VL commands, media can be configured to the Administrator's
requirements. Different applications can have different media criteria to suit the applications requirements.

MANAGING MEDIA VIA THE VL DATABASE

Media is tracked in and out of the jukebox by the VL database. When media is imported into the jukebox with the vlimport
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 jukebox using the vlexport command, the VL database is updated to
show that shelf as empty. If the media being exported is part of a 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
VL requests an offline media from a mounted 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 optical, tape or DVD-RAM, then it needs to be erased before use
with the vlerase command, if the media is WORM optical, CD/DVD-ROM or CD/DVD-R, then it is ready for use. The
vlrefresh command can be used to refresh all or selected shelves within the jukebox and update the VL database. The selected
shelves will be loaded into the drives of the jukebox and read to find the status of each media as to whether it has a volume
label, or it is blank, etc. The vlexchange command is used to move either media within the jukebox, 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 jukebox via the vlmagazine command (mainly CD/DVD jukeboxes with magazine support).
The VL database is updated once the media is exchanged. The vlmagazine 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 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.

Media Management commands:

vlimport Import a media into a jukebox and checking the media contents
vlexport Export a media from the jukebox and store its offline location (if it belongs to a set) in the VL
database
vlerase Erase media, a surface, a group of media, the whole jukebox
vlrefresh Refreshing the database as to media type and contents
vlexchange Moves a media from one shelf to another in the jukebox and updates the VL database.
vlmagazine Exchanges media in the jukebox using the magazines and updates the VL database.

VL MEDIA SET RELATED COMMANDS

In the “INTRODUCTION” section, the difference between “Set” or “Media set” and “Integral Volume set” has been
explained. To simplify the explanation, in this chapter, the media managed by the Volume Librarian will be referred to “Set” or
“Media set”. Media sets are created using the vlcrset command, which can be used to specify options such as the amount of
media in a set, the media type (Rewritable, WORM, UDO, PDD, Blu-ray, CD, DVD or Tape), or the file system type to be
created (SDF, UDF, ISO). The set can be modified with the vleditset command, or viewed using the vllsset command. The set
can be renamed with the vlmvset command. Initialize media and add them to a set with the vladdtoset command. If a magnetic
cache is required for the set, then the vlcache command is used to set the cache parameters. The vlcache command may also be
used to modify the cache parameters. The vlinset command allows changes to be made to the media within a set, such as offline
location and cache specific functions relating to that media (mainly CD-ROM). If a set is no longer required, then it can be
deleted with the vldelset command, this command deletes the 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 vlerase command. VL will not allow vlerase
command on any media contained within a set. Using vldelset command will also remove any reference to the cache for that set,
but the magnetic cache files will not be removed.

Page 7 of 100
The VL commands related to managing a Media set (Integral Volume set):
vlcrset Create a Media set (file system) on the archival media
vladdtoset Add additional media to the Media set
vlcache Create and modify a cache for a Media set
vldelset Delete a Media set
vlmvset Rename a Media set name
vleditset Display and modify Media set information
vlinset Modify information relating to a CD within the Media set
vllsset List set information in the database
vlclose Close the media of a UDF volume
mountiv Mount an Integral Volume set
umount/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.

MANAGING THE VL DATABASE

This section will explain the main functionality of the VL database using the VL commands. 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

The vlimport command is used to import media into a shelf within the jukebox. After the media is imported to the specified
shelf in the jukebox, the media is refreshed.

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}]
[-C] [-S simulation_param] 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

Note: The -p option is used to specify the type of media that will be imported. This option can be used with CD/DVD or Blu-ray
jukeboxes with mixed drives types or drives that support different types of media. This allows loading media into the correct
drive during the refresh procedure to determine the media type of the shelf. If the -p option is omitted 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. QStar recommends reviewing the
explanation for the vlimport command in Chapter 9 - Command Reference of this manual, while reading this section.

Note1: The operations related to the simulated Hard Disk/Centera jukebox are omitted.

1) To import the media into a shelf of a jukebox identified as jb, enter:

#>vlimport jb 1

2) To import the media into a shelf of a jukebox identified as jb specifying the media type, enter:

#>vlimport –p dvd-ram jb 1

3) To import the media into a shelf of a jukebox identified as jb specifying that is single surface and the media type, enter:

#>vlimport –p dvd-ram –p 1 jb 1

Page 8 of 100
4) To import 5 media into a shelves starting from shelf 1 of a jukebox with magazine mailslot identified as jb, enter:

#>vlimport jb 1 5

The vlexport command is used to export media from the jukebox.

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

1) To export media from shelf 1 of a jukebox identified as jb, enter:

#>vlexport jb 1

Erasing the Media

If rewritable media is being used (rewritable Optical (MO/UDO/PDD/Blu-ray), Tape or DVD-RAM media, erase the media
before using it. The vlerase command is used to erase single or multiple media.

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

-f Full erase option can be used to check the consistency of a faulty media. By default a fast erase will be performed.

If using Optical (MO/UDO/PDD) media with UDF, select -e emulate erase option. 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).

1) To erase the media in shelf 1 of a jukebox identified as jb, enter:

#>vlerase jb 1

2) To erase the media from shelf 3 to shelf 6 of a jukebox identified as jb, enter:

#>vlerase jb 3:6

Note: To erase the media using the Delayed Erase Media procedure, please refer to Displaying and Setting the VL
Configuration Properties for Delayed Erase Media section in this chapter.

Page 9 of 100
Refreshing the Media
The vlrefresh command is used to refresh 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.

vlrefresh [-H host_name] [-sB] device_name shelf_number ...

vlrefresh [-H host_name] [-sB] device_name shelf_number:shelf_number
vlrefresh [-H host_name] [-sB] device_name
vlrefresh [-H host_name] [-sB] -f

1) To refresh the media in shelf 1 of a jukebox identified as jb, enter:

#>vlrefresh jb 1

2) To refresh the entire jukebox identified as jb, enter:

#>vlrefresh jb

Creating an Integral Volume Set

The vlcrset command is used to create an Integral Volume set (Media set); there are several different types of file system
available. Specifying only the set_name, by default the command will create a set using rewritable media with Nom (no
media) file system. The SDF file system is QStar’s primary file system.

vlcrset [-T set_type] [-H host_name][-u{disk,cd,tape,dvd,erasable,worm,rdonly,cd-dvd,bd-re,bd-rs,bd-rom,hd-sdisk,hd-

stape,c-sdisk,c-stape}] [-q quota][-s] [-I] [-r] [-N] [-b{full|cron_like_schedule|Publisher_schedule}] [-U
{local|share}][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 {CDR|DVDR}] [-A Publisher_media_retained]
[-D {0|1|2|3}] [-Q Publisher_host_name]
[-Y Publisher_port][-L Pubisher_label_file]
[[-k label_param1 -e label_value1]
[-k label_param2 -e label_value2] ...]
uvfs [-v{s|a}]
nom

The -q 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.

The –s Spread option allows the Integral Volume set to spread across multiple jukeboxes automatically. Without this option the
Integral Volume set will reside within the same jukebox it was created in. However, media from another jukebox can be
manually added to the Integral Volume set at anytime.

Page 10 of 100
The -U {local|share} option is used to specify whether an Integral Volume set can only be mounted and accessed from the local
server. This option is only available for HP-UX and Linux. The default value is share.

The cron_like_schedule option is used for incremental Copy Media and is available only for the SDF file system. QStar
recommends reviewing the explanation for the vlcrset command in Chapter 9 - Command Reference of this manual, while
reading this section.

The [-E {CDR|DVDR}] [-A Publisher_media_retained][-D {0|1|2|3}] [-Q Publisher_host_name][-Y Publisher_port][-L

Pubisher_label_file] [[-k label_param1 -e label_value1] [-k label_param2 -e label_value2] ...] options for the UDF file system
are related to the Publisher Archive product and will not be explained in this manual, for more information please refer to
QStar Publisher Archive Getting Started Guide.

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

Thie creation of an Integral Volume set with the UVFS file system will not be explained in this manual, for more information
please refer to QStar Windows Administratior’s Guide.

Creating an Integral Volume Set with the SDF File System

The Standard Data Format (SDF) file system is used to create a Media set with WORM or writable Optical (MO/UDO/PDD)
media, Blu-ray (BD-RE, BD-RS) media, DVD-RAM media or Tape media. This configuration allows the use of multiple media
to be created as a single seamless file system with a magnetic cache. The “-m” and “-2” options are used to set up the Mirroring
configuration in the Data Director product, please refer to the Mirroring manual for a full explanation of the Mirroring
configuration.

The SDF default parameters are disk and writable Optical media. The -r readonly, -s spread, -q quota, -b full (Make a copy of
full media) and -b cron_like_schedule (Make an Incremental Copy) options are all available with the SDF file system. See
the THE COPY AND COMPARE MEDIA UTILITIES section later in this chapter for more details. The quota limit for an
Integral Volme set with the SDF file system is equal to 2048 media.

1) To create a new Integral Volume set definition named Test for rewritable Optical media with an SDF file system, enter:

#>vlcrset –T sdf Test

2) To create a new Integral Volume set definition named Test for WORM Optical media with an SDF file system, enter:

#>vlcrset –T sdf –u worm Test

3) To create a new Integral Volume set definition named Test for WORM and rewritable Optical media with an SDF file
system, enter:

#>vlcrset –T sdf –u writable –u worm Test

4) To create a new Integral Volume set definition named Test for DVD-RAM media with an SDF file system, enter:

#>vlcrset –T sdf –u dvd Test

Page 11 of 100
5) To create a new Integral Volume set definition named Test for Blu-ray BD-RE rewritable media with an SDF file system,
enter:

#>vlcrset –T sdf –u bd-re Test

6) To create a new Integral Volume set definition named Test for Blu-ray BD-RS WORM media with an SDF file system, enter:

#>vlcrset –T sdf –u bd-rs Test

7) To create a new Integral Volume set definition named Test for rewritable Optical media with an SDF file system and the
spread option enabled (so the set can spread across multiple jukeboxes), enter:

#>vlcrset –T sdf –s Test

8) To create a new Integral Volume set definition named Test for rewritable Optical media with an SDF file system and the
read only option enabled, enter:

#>vlcrset –T sdf –r Test

9) To create a new Integral Volume set definition named Test for WORM Optical media with an SDF file system and the
automatic start of Copy Media for full media enabled, enter:

#>vlcrset -T sdf -u worm –b full Test

10) To create a new Integral Volume set definition named Test for WORM Optical media with an SDF file system and the
scheduling of Automatic Incremental Copy Media media enabled, enter:

#>vlcrset -T sdf -u worm –b “37 17 * * 1,2,3,4,5” Test

Note: With this command and the selected -b cron_like_schedule option, the Automatic Incremental Copy Media will be
scheduled to take place from Monday to Friday every week and month at 17:37. To change the scheduled time, the vleditset
command would be used.

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 jukebox when
there are written media located offline (outside of the jukebox).

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.

Page 12 of 100
 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 (New option in v5.0)

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.
Backup on mirrored volumes: If the backup is performed to a medium in a mirrored SDF set environment, the database
backup is written to a medium in the primary and secondary sets. This is true for data base operations to data or special backup
volumes. The status of the mirrored volumes can be monitored using mmparam command and synchronized using vlstartmirr
command.

To configure how the SDF file system performs the backup of the database files, select and edit the
/opt/QStar/sdf/files/Integral volume name_backup_config.xml file. QStar will automatically create a file in this directory for
each Integral Volume set created. For example if the Integral Volume set name created is Test a file Test_backup_config.xml
file will be created. This file will be automatically deleted if the Integral Volume set is deleted with vldelset command.

The default value of all the available configuration options will be displayed in this file.

<?xml version="1.0" ?>

- <!--
SDF BACKUP CONFIGURATION FILE
Created: 02/17/2009 10:37:49
Set name: Test
-->
<configuration>

Page 13 of 100
<!-- First volume to start using the separate medium for backups
The number greater then 2048 is used for separate medium always -->
<First_SDF_DB_backup_volume>
<direct>2048</direct>
<sequential>2048</sequential>
</First_SDF_DB_backup_volume>

The First_SDF_DB_backup_volume option, displays the first surface/media used to start to backup the SDF database files on
separate media. This option allows the System Administrator to specify when the SDF file system will begin storing the
database files on separate media. By default the SDF file system will not use separate media for the SDF database file but it will
store them at the beginning of each volume until the specified volume number is reached. If 2048 is selected the SDF file
system will not backup to the he SDF database files on separate media. Leave 2048 in order to use Configuration 1. The direct
value is referred to Disk media and the sequential value is referred to Tape media. QStar recomends leaving the value of
2048 for Tape device.

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

<!-- If no new volumes were created after the backup was triggered -->
<Force_SDF_BACKUP_after_days>0</Force_SDF_BACKUP_after_days>

The Force_SDF_BACKUP_after_days (Inactive Days) option specifies when the set will perform a database backup if a
database backup has not been performed in a specified number of days. The value of 0 means that this option is disabled.

<!-- Do not perform backup if less then ??? GB was written after previous backup
Supported following format for test purposes: <number>[G|M|K|B]
Where, G-gigabytes(default), M-megabytes, K-kilobytes, B-bytes -->
<Minimal_SDF_BACKUP_data_trigger>
<direct>0</direct>
<sequential>50</sequential>
</Minimal_SDF_BACKUP_data_trigger>

The Minimal_SDF_BACKUP_data_trigger option 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 database backup. The direct value is
referred to Disk media and the sequential value is referred to Tape media. 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. The value of 0 means that this option
is disabled.

<!-- Backup type: 'media' or 'file system'.

Default value is 'media'. -->
<SDF_BACKUP_target>media</SDF_BACKUP_target>
The SDF_BACKUP_target option allows the System Administrator to choose the primary location where to store the SDF
database files between a File System on hard disk or on the Media. The default location is media.
QStar recommends storing the database files to removable 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 the database files are backed up and not deleted from the specified location.

Page 14 of 100
- <!-- Specifies where data base backups can be performed on the primary node.
This should be a directory essentially assigned by the user where backup files
shall be stored. -->
<Primary_SDF_BACKUP_path />

Example to specify /data/primary_backup_files as location modify the line as follows:

<Primary_SDF_BACKUP_path>/data/primary_backup_files</Primary_SDF_BACKUP_path>

The Primary_SDF_BACKUP_path option work in conjunction with the SDF_BACKUP_target option. If the System
Administator chooses a file system location as the primary location for the SDF database file then the administrator needs to
specify in which directory the SDF database files should be stored.

<!-- Specifies data base backup location on the mirror node.

It should be expressed in platform dependent terms because
remote node is not required to be of the same type of media. -->
<Mirror_SDF_BACKUP_path />

Example to specify /data/secondary_backup_files as the location, modify the line as follows:

<Mirror_SDF_BACKUP_path>/data/secondary_backup_files</Mirror_SDF_BACKUP_path>

The Mirror_SDF_BACKUP_path option allows the System Administrator to specify an additional database backup location
on a file system, where the QStar Software will write a secondary copy of the SDF database files.

<!-- Specifies number of backup set versions.

Older version shall be deleted to manage file system space. -->
<Number_of_SDF_BACKUP_copies>2048</Number_of_SDF_BACKUP_copies>
</configuration>

The Number_of_SDF_BACKUP_copies option works in conjunction with Primary_SDF_BACKUP_path and

Mirror_SDF_BACKUP_path options and define how many SDF database file version will be kept on the location specified.
Once the number of copies specified is reached, the oldest version will be automatically deleted. QStar set the limit of these
copies to 2048, that is the same as the maximum number of media which can be added to an Integral Volume set. QStar will
generate a version of the SDF database files for every rollover, at a minimum, for each new media/surface. This means that a lot
of space for these file will be used in the file system and if the System Administrator does not monitor the space where the SDF
database files will be saved, then a problem can occur where insufficient space will be available for the new files and archiving
will stop.

QStar sets the limit high because without all the database versions the System Administrator will loose the opportunity to use
the Mount On Date option, which allows mounting the file system to a specific time and date in the past. In addtition, if the
SDF database is lost or unavailable, the only way to recreate the file system is to rescan all media block by block.

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

The System Administrator can monitor all backup and restore operations on all SDF Integral Volume sets from the
c:\QStar\log\backup-log.xml file.

Page 15 of 100
Additional Shredding Options for Optical Archive Media

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. The SDF file system supports the shredding operation in two ways:
• Using UDO Compliance WORM media, QStar supports a specific SHRED SCSI command that allows shredding a block
on the media. If Complainant UDO WORM media are added to an Integral Volume set, the Software will detect that they
are Compliance 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.
• Using the Shredding option on Optical rewritable media. If the Shredding option is enabled with rewritable optical
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 allows treating the rewritable Optical media as compliance media.

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 HSM and Data Director (Mirroring) products.

Additional Compression Option for Tape Archive Media

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

1) To create a new Integral Volume set definition named Test for tape media with an SDF file system and compression option
enabled, enter:

#>vlcrset –T sdf –c on –u tape Test

Page 16 of 100
Creating an Integral Volume Set with the UDF or ISO 9660 File
System

The Universal Disk Format (UDF) file system can be used with WORM or rewritable Optical (MO/UDO/PDD) media, Blu-
ray (BD-RE) media, DVD-RAM media, CD/DVD-R/Blu-ray (BD-RS) 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.

The Interchange Level defines how many volumes are in the Integral Volume set. The UDF file system allows three
Interchange Level configurations:
• Single-Volume:
Each surface is a separate file system with a magnetic cache and a mapped network drive for each surface.
• Automount:
Multiple media are viewed as a large file system each surface is a separate file system with a single magnetic cache
mounted under a single mapped network drive, each presented as a separate directory.
• 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 mapped network drive.

The UDF default parameters are disk and writable Optical media, the interchange level is single-volume set, packet writing is
disabled, space calculation is enabled, verification is disabled and the UDF version is 1.50.

The -v option is used to specify the interchange level, the -R UDF revision option is used to specify the UDF version. The -r
readonly and -q quota options are 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 -W Write Verification option is used to specify if verification after write will be performed. 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-RS) 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 in the last data block is verified.

Creating an Integral Volume Set with Single-Volume and Automount Interchange

Level

The Single-Volume Interchange Level should only be used with a standalone drive. This configuration will only create a UDF
file system on a single surface of the media. The file system is limited to the single surface size of the media being used. If this
configuration is used in a jukebox with dual sided media, it will require exporting the media, flipping the media manually and
then importing the media back into the jukebox to use the second side of the media. However, if single sided media is used the
jukebox will function correctly. The Automount Interchange Level can also be used with a standalone drive.

The -S Space Calculation option is specific for Single-Volume and Automount Interchange Levels. This option is used to
enable or disable the space calculation. 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 media
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

Page 17 of 100
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.

1) To create a new Integral Volume set definition named Test for rewiteable Optical media with a UDF file system and single-
volume interchange level, enter:

#>vlcrset –T udf Test

2) To create a new Integral Volume set definition named Test for WORM Optical media with a UDF file system and single-
volume interchange level, enter:

#>vlcrset –T udf –u worm Test

3) To create a new Integral Volume set definition named Test for DVD-RAM media with a UDF file system and single-
volume interchange level, enter:

#>vlcrset –T udf –u dvd Test

4) To create a new Integral Volume set definition named Test for Blu-ray BD-RE rewritable media with a UDF file system and
single-volume interchange level, enter:

#>vlcrset -T udf –u bd-re Test

5) To create a new Integral Volume set definition named Test for Blu-ray BD-RS WORM media with a UDF file system and
single-volume interchange level, enter:
#>vlcrset –T udf –u bd-rs Test

6) To create a new Integral Volume set definition named Test for rewiteable Optical media with a UDF file system and
automount interchange level, enter:

#>vlcrset –T udf –v a Test

7) To create a new Integral Volume set definition named Test for WORM Optical media with a UDF file system and
automount interchange level, enter:

#>vlcrset –T udf –v a –u worm Test

8) To create a new Integral Volume set definition named Test for DVD-RAM media with a UDF file system and automount
interchange level, enter:

#>vlcrset –T udf –v a –u dvd Test

9) To create a new Integral Volume set definition named Test for DVD-RAM media with a UDF file system and automount
interchange level and the verification option enabled, enter:

#>vlcrset –T udf -v a –W 1 –u dvd Test

10) To create a new Integral Vomume set definition named Test for DVD-RAM media with a UDF file system and automount
interchange level and the space calculation option disabled (by default is enabled), enter:

#>vlcrset –T udf -v a –S 0 –u dvd Test

Page 18 of 100
11) To create a new Integral Volume set definition named Test for Blu-ray BD-RE rewritable media with a UDF file system
and automount interchange level, enter:

#>vlcrset –T udf –v a –u bd-re Test

12) To create a new Integral Volume set definition named Test for Blu-ray BD-RS WORM media with a UDF file system and
automount interchange level, enter:

#>vlcrset –T udf -v a –u bd-rs Test

13) To create a new Integral Volume set definition named Test for DVD-RAM media with a UDF file system and automount
interchange level and the read only option enabled, enter:
#>vlcrset –T udf -v a -u dvd –r Test

14) To create a new Integral Volume set definition named Test for DVD-RAM media with a UDF file system and automount
interchange level and the UDF revision set to 201 (by default is 1.50), enter:

#>vlcrset –T udf -v a –R 201 –u dvd Test

Additional Options for CD/DVD-R and BD-RS 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 mapped network drive. The -P Packet Writing option is used to specify
if the packet writing will be used for CD/DVD-R or Blu-ray (BD-RS) media, The Packet Writing option will be available if
CD/DVD-R and BD-RS is selected as the archive media type. The CD/DVD-R or BD-RS 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.

15) To create a new Integral Volume set definition named Test for CD/DVD-R media with a UDF file system, single-volume
interchange level and the packet writing option enabled, enter:

#>vlcrset -T udf -P 1 -u cd-dvd Test

16) To create a new Integral Volume set definition named Test for CD/DVD-R media with a UDF file system, automount
interchange level and the packet writing option enabled, enter:

#>vlcrset –T udf -v a –P 1 –u cd-dvd Test

17) To create a new Integral Volume set definition named Test for CD/DVD-R media with a UDF file system and automount
interchange level and the packet writing and verification options enabled, enter:

#>vlcrset -T udf -v a –P 1 –W 1 -u cd-dvd Test

Page 19 of 100
Creating an Integral Volume Set with Spanning Interchange Level

The UDF file system with the Spanning Intechange Level is best suited for WORM media and not recommended for
rewritable media if files are likely to be deleted or modified, as deletion of files will cause fragmentation and heavily impact the
performance. QStar also suggests the use of a cache large enough to accommodate a full day’s data to be stored without
archiving, because the cache has run out of space. Once data has been commited to the optical media, minimal or no changes to
files should occur. The Spanning Interchange Level, allows media to be dynamically added when a sequence is full, but still
maintains UDF compliance.

The -s spread option is only available for the Spanning Interchange Level. The -F File Spanning option is specific to the
Spanning Interchange Level and is enabled by default. This option 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 -V Close Full Volume
option is specific to the Spanning Interchange Level and is enabled by default. This option will automatically close the media
or surface once it is full.

The -b full (Make copy of full media) option is specific to a Spanning Interchange Level with CD/DVD-R, Blu-ray (BD-
RS) and WORM media and will be available only if the Close Full Volume option is enabled. See the THE COPY AND
COMPARE MEDIA UTILITIES section later in this chapter for more details.

1) To create a new Integral Volume set definition named Test for WORM Optical media with a UDF file system, spanning
interchange level and the close of full volume option enabled, enter:

#>vlcrset –T udf –v s –V 1 –u worm Test

2) To create a new Integral Volume set definition named Test for DVD-RAM media with a UDF file system, spanning
interchange level and the close of full volume option enabled, enter:

#>vlcrset –T udf –v s –V 1 –u dvd Test

3) To create a new Integral Volume set definition named Test for Blu-ray BD-RS WORM media with a UDF file system,
spanning interchange level and the close of full volume option enabled, enter:

#>vlcrset –T udf -v s –V 1 –u bd-rs Test

Additional Options for CD/DVD-R and BD-RS 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 mapped network drive. The -P Packet Writing option is used to specify
if the packet writing will be used for CD/DVD-R or Blu-ray (BD-RS) media, The Packet Writing option will be available if
CD/DVD-R and BD-RS is selected as the archive media type. The CD/DVD-R or BD-RS 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.

The -B 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.

4) To create a new Integral Volume set definition named Test for CD/DVD-R media with a UDF file system, spanning
interchange level, packet writing and the close on full volume options eanbled, enter:

#>vlcrset –T udf -v s –P 1 –V 1 –u cd-dvd Test

Page 20 of 100
5) To create a new Integral Volume set definition named Test for CD/DVD-R media with a UDF file system, spanning
interchange level and the packet writing option enabled, enter:

#>vlcrset -T udf -v s –P 1 -u cd-dvd Test

6) To create a new Integral Volume set definition named Test for CD/DVD-R media with a UDF file system, spanning
interchange level, the packet writing and the image backup options enabled, enter:

#>vlcrset -T udf -v s –P 1 –B 1 -u cd-dvd Test

7) To create a new Integral Volume set definition named Test for CD/DVD-R media with a UDF file system, spanning
interchange level, the packet writing, the image backup and the Automatic Full Media Copy Media options enabled, enter:

#>vlcrset -T udf -v s –P 1 –B 1 –b full -u cd-dvd Test

Additional Options for CD/DVD-ROM Archive Media with UDF and ISO 9660
File System
Starting with this version 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 HSM Automount product as a Read Only file system for CD/DVD-ROM media. Also with
HSM 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 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 jukebox 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 jukebox to allow the more frequently accessed CD/DVD-ROM’s to be present in the jukebox.

The UDF and ISO 9660 file systems used with the CD/DVD-ROM media is used with Automount Interchange Level and as a
read only file system. The Readonly flag 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.

1) To create a new Integral Volume set definition named Test for CD/DVD-ROM media with a UDF file system, single-volume
interchange level and the read only option enabled, enter:

#>vlcrset –T udf -r -u cd-dvd Test

2) To create a new Integral Volume set definition named Test for CD/DVD-ROM media with a UDF file system, automount
interchange level and the read only option enabled, enter:

#>vlcrset –T udf -v a -r -u cd-dvd Test

Page 21 of 100
Creating a Set with No Media File System
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 jukebox 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 the SDF or UDF Spanning file system.

1) To create a new Integral Volume set definition named Test with No Media file system, enter:

#>vlcrset Test

Creating and Adding a Cache to an Integral Volume Set

The vlcache command is used to create a cache for an Integral Volume set. 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.

vlcache [-H host_name][-D0rn][-e][-p{max_number_of_pages | xxMB | xxGB}]

[-l {low_primary_capacity | xxMB | xxGB | xx%}][-h {high_primary_capacity | xxMB | xxGB | xx%}][-s page_size]
[-c cache_root][-g rdonly_grace_period][-R retention_period][-w {0|1][-x {0|1][-c cache_root] set_name

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.
The -s Page Size option 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
smaller the page size selected. The Page Sizes that are available are from 1KB up to 128KB. The 128KB can be used only with
the AIT tape drive.

The -e 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 -r Readonly option allows mounting a file system in read only mode.

The -g Grace Period option specifies a period of 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 file system, even with rewritable media which is ideal
for corporate data archiving compliance requirement.

The -R 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 UNIX, or 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 and days.

Page 22 of 100
The -w 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 -x Deny Rename option is specified with the Write Once option, the
renaming operation is also prohibited.

Note: QStar recommends reviewing the explanation for the vlcache command in Chapter 9 - Command Reference of this
manual, while reading this section.

1) To create a cache with 100MB on the /export/home/cache_Test cache_root directory for an Integral Volume set named Test,
enter:

#>vlcache –p 100MB –c /export/home/cache_Test Test

2) To create a cache with 100MB on the /export/home/cache_Test cache_root directory and the high_primary_capacity value
set to 80 pages for an Integral Volume set named Test, enter:

#>vlcache –p 100MB –c /export/home/cache_Test –h 80 Test

3) To create a cache with 100MB on the /export/home/cache_Test cache_root directory and the cache in read only mode for an
Integral Volume set named Test, enter:

#>vlcache –p 100MB -r –c /export/home/cache_Test Test

4) To create a cache with 100MB on the /export/home/cache_Test cache_root directory and enabling the write operation on the
cache even if a covered error occurs for an Integral Volume set named Test, enter:

#>vlcache –p 100MB -e –c /export/home/cache_Test Test

5) To create a cache with 100MB on the /export/home/cache_Test cache_root directory and the cache pages size set to 32
(default is 64K) for an Integral Volume set named Test, enter:

#>vlcache –p 100MB –s 32 –c /export/home/cache_Test Test

6) To create a cache with 100MB on the /export/home/cache_Test cache_root directory and the grace period value set to 20
minutes for an Integral Volume set named Test, enter:

#>vlcache –p 100MB –c /export/home/cache_Test –g 0h20m0s Test

Page 23 of 100
Modifying the Cache for an Integral Volume Set
The vlcache command is also used to modify the cache options for an Integral Volume set. If the cache was already created and
the set is mounted this change will take effect at the next mount. QStar suggests umounting the Integral Volume set, change the
cache options and then remount the Integral Volume set.

1) To increase the cache size from 100MB to 15GB for an Integral Volume named Test, enter:

#>vlcache –p 15GB Test

2) To change the high_primary_capacity value to 70 pages for an Integral Volume named Test, enter:

#>vlcache –h 70 Test

3) To change the low_primary_capacity value to 10 pages for an Integral Volume named Test, enter:

#>vlcache –l 10 Test

Note: After the cache is added to the Integral Volume set, the vllsset command will display an output similar to the following.

Cache: Cache_root=/export/home/cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Low_primary_capacity=10
High_primary_capacity=70

Note: For more detailed information on changing the number of pages of the cache and the cache location, please refer to
Chapter 6 - Migration Manager in this manual.

Adding Media to an Integral Volume Set

The vladdtoset command is used for adding media to a Media set.

vladdtoset [-H host_name] [-n number_of_media] set_name

vladdtoset [-H host_name] [set_type_specific_options] set_name device_name shelf_number
vladdtoset [-H host_name] set_name device_name shelf_number:shelf_number
vladdtoset [-H host_name] -f offline set_name in_set_number

set_type set_type_specific_options:
sdf
udf [-A identifier][-B identifier]
uvfs [-X directory][-Y directory]
[-A identifier][-B identifier]

Note: QStar recommends reviewing the explanation for the vladdtoset command in Chapter 9 - Command Reference of this
manual, while reading this section.

1) To add the first available media to an Integral Volume set named Test, enter:

#>vladdtoset Test

Page 24 of 100
2) To add the media in shelf 1 to an Integral Volume set named Test, enter:

#>vladdtoset Test jb 1

3) To add a range of media to an Integral Volume set named Test, enter:

#>vladdtoset Test jb 1:10

Adding Media to an SDF Integral Volume Set

1) To add the first available media to an Integral Volume set named Test, enter:

#>vladdtoset Test

2) To add the media in shelf 1 to an Integral Volume set named Test, enter:

#>vladdtoset Test jb 1

3) To add a range of media to an Integral Volume set named Test, enter:

#>vladdtoset Test jb 1:10

Adding Media to an UDF or ISO 9660 Integral Volume Set

1) To add the first available media to an Integral Volume set named Test, enter:

#>vladdtoset Test

2) To add the media in shelf 1 to an Integral Volume set named Test, enter:

#>vladdtoset Test jb 1

3) To add a range of media to an Integral Volume set named Test, enter:

#>vladdtoset Test jb 1:10

• 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_#).

Page 25 of 100
• 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 jukebox, 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 Media to a UDF or ISO 9660 Integral Volume Set Specifying

the Logical Volume ID

1) To add a media (single side) to an Integral Volume set with a UDF or ISO 9660 file system named Test with a specified
Logical Volume ID or directory name (BD001), enter:

#>vladdtoset –A BD001 Test jb 1

2) To add a media (dual side) to an Integral Volume set with a UDF or ISO 9660 file system named Test with a specified
Logical Volume ID or directory name (BD001A and BD001B), enter:

#>vladdtoset –A BD001A –B BD001B Test jb 1

• 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 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. 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.

Page 26 of 100
Displaying Integral Volume Set Information
After creating an Integral Volume set, the contents can be displayed including the status of all surfaces in the set and its
configuration including its cache parameters, its maximum number of media, and more.

The vllsset command is used to display the set information.

vllsset [-H host_name] set_name in_set_number |

vllsset [-H host_name] [-v] set_name |
vllsset [-H host_name] [-nv] -a

Note: QStar recommends reviewing the explanation for the vllsset command in Chapter 9 - Command Reference of this manual,
while reading this section.

1) To display the Integral Volume set information for all set created, enter:

#>vllsset -va

2) To display the Integral Volume set information for the set named Test, enter:

#>vllsset –v Test

Displaying the Information for the SDF File System and Optical Media

1) To display the set information for the Integral Volume set named Test, enter:

#>vllsset –v Test

Test
Use_media=disk,writable Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
Set_Id=c25b016a.3453d0e4
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
4: Online=jb:3 Sequence_numbers=4,5 Mounted=a,b

Note: The Use_Media information will display disk, writable or disk, worm for Optical media, tape, writable for Tape media,
bd,writable for Blu-ray BD-RE media, bd,worm,rdonly for Blu-ray BD-RS Media, and dvd, writable for DVD-RAM media.

Note1: The Shredding mode option will be displayed if enabled.

Page 27 of 100
Displaying the Information for the SDF File System and Tape Media

1) To display the set information for the Integral Volume set named Test, enter:

#>vllsset –v Test

Test
Use_media=tape,writable Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
Compression=Default
SetId=5246b54c.36b9c01a
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_number=0 Mounted=a
1: Online=jb:2 Sequence_number=1 Mounted=a
2: Online=jb:3 Sequence_number=2 Mounted=a

Note: For tape media the compression option by default is default.

Displaying the Information for the UDF File System with the Single-
Volume Interchange Level and DVD-RAM Media

1) To display the set information for the Integral Volume set named Test, enter:

#>vllsset –v Test

Test
Use_media=dvd,writable Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=q_3b0a88e0
UDF_revision=150 Interchange_level=single-volume
Packet_writing_init=no Space_calculation=yes Verify_write=no
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_number=1 Mounted=a

Note: In the example, DVD-RAM single surface media were used and the Interchange_level (how many volumes are in the set)
was specified as single-volume. In the single-volume configuration the Logical_volume_identifier is a unique
logical_volume_identifier number.

Note1: The Use_Media information will display disk, writable or disk, worm for Optical media, bd, writable for Blu-ray BD-
RE media, bd,worm,rdonly for Blu-ray BD-RS media, and dvd, writable for DVD-RAM media.

Page 28 of 100
Displaying the Information for the UDF File System with the
Automount Interchange Level and DVD-RAM Media

1) To display the set information for the Integral Volume set named Test, enter:

#>vllsset –v Test

Test
Use_media=dvd,writable Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=no Space_calculation=yes Verify_write=no
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 Automount_sequence_numbers=0,1 Mounted=a,b
1: Online=jb:2 Automount_sequence_numbers=2,3 Mounted=a,b A_dir=jb2a B_dir=jb2b
2: Online=jb:3 Automount_Sequence_numbers=4,5 Mounted=a,b

Note: In the example, DVD-RAM dual surface media was used and the Interchange_level (how many volumes are in the set)
was specified as automount. In the automounter configuration, the Logical_volume_identifier is equal to NA (Not Available)
and instead the Automount_Sequence_number is displayed. The media in shelf 2 was added specifying the Logical Volume ID.

Note1: The Use_Media information will display disk, writable or disk, worm for Optical media, bd, writable for Blu-ray BD-
RE media, bd,worm,rdonly for Blu-ray BD-RS media, and dvd, writable for DVD-RAM media.

Displaying the Information for the UDF or ISO 9660 File System with
the Automount Interchange Level and CD/DVD-ROM Media

1) To display the set information for the Integral Volume set named Test, enter:

#>vllsset –v Test

Test
Use_media=cd,dvd,worm,rdonly Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=yes Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=no Space_calculation=yes Verify_write=no
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 Automount_sequence_number=0 Mounted=a,b
1: Online=jb:2 Automount_sequence_number=2 Mounted=a,b A_dir=cd2
2: Online=jb:3 Automount_Sequence_number=4 Mounted=a,b

Page 29 of 100
Note: The CD/DVD-ROM media with the UDF or ISO 9660 file system pre-recorded or recorded (session at once) using the
QStar MASTER product can be accessed using the automount Interchange_level. In the automounter configuration the
Logical_volume_identifier (Volume Label) of the CD/DVD-ROM media is used as the name of the CD/DVD-ROM in the root
directory of the file system once it is mounted. The CD/DVD-ROM name in the root directory can be changed specifying the -A
-B options in the vladdtoset command. In this case, the new sub-directories name will be printed in the set information for each
surface (see media in shelf 2 on the example).The Integral Volume set must be configured in Read_only mode for the QStar
AXXESS product.

Displaying the Information for the UDF File System with the Automount
Interchange Level and CD/DVD-R or BD-RS Media and Packet Writing

1) To display the set information for the Integral Volume set named Test, enter:

#>vllsset –v Test

Test
Use_media=cd,dvd,worm,rdonly Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=yes Space_calculation=yes Verify_write=no
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 Automount_sequence_number=0 Mounted=a,b
1: Online=jb:2 Automount_sequence_number=2 Mounted=a,b A_dir=cd2
2: Online=jb:3 Automount_Sequence_number=4 Mounted=a,b

Note: The CD/DVD-R media having been recorded (session at once) with the UDF file system using the QStar MASTER
product can be directly added and accessed using the automount Interchange level and the Packet writing options enabled.
In the automounter configuration the Logical_volume_identifier is equal to NA (Not Available) and instead the
Automount_Sequence_number is displayed. The media in shelf 2 was added specifying the Logical Volume ID.

Displaying the Information for the UDF File System with the Spanning
Interchange Level and Optical Media

1) To display the set information for the Integral Volume set named Test, enter:

#>vllsset –v Test

Test
Use_media=disk,worm Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=q_a40a36f87
UDF_revision=150 Interchange_level=spanning
Packet_writing_init=no Verify_write=no
Close_full_volume=yes File_spanning=yes Use_image_backup=no
Cache: Cache_root=/export/home/cache_Test

Page 30 of 100
 Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Mounted at /mnt
0: Online=jb:1 Span_numbers=1,2 Mounted=a,b
1: Online=jb:2 Span_numbers=3,4 Mounted=a,b
2: Online=jb:3 Span_numbers=5,6 Mounted=a,b

Note: The UDF file system with Spanning Intechange Level is best suited for WORM media and not recommended for writable
media if files are likely to be deleted, as deletion of files will cause fragmentation and impact heavily on performance.

Displaying the Information for the UDF File System with the Spanning
Interchange Level and CD/DVD-R or BD-RS Media and Packet Writing

1) To display the set information for the Integral Volume set named Test, enter:

#>vllsset –v Test

Test
Use_media= cd,dvd,worm,rdonly Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=q_a30a36f78
UDF_revision=150 Interchange_level=spanning
Packet_writing_init=yes Verify_write=no
Close_full_volume=yes File_spanning=yes Use_image_backup=yes
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 Span_numbers=1,2 Mounted=a,b
1: Online=jb:2 Span_numbers=3,4 Mounted=a,b
2: Online=jb:3 Span_numbers=5,6 Mounted=a,b

Note: Use_image_backup option is set to yes by default for CD/DVD-R media. The image backup can be used to burn backup
media in order to replace the original if damaged. The procedure to burn the image backup onto a new media can be done using
the vlinset command with -R flag.

Note1: The Use_Media information will display bd,worm,rdonly for Blu-ray BD-RS media.

Displaying the Information for the No Media File System

1) To display the set information for the Integral Volume set named Test, enter:

#>vllsset –v Test

Test
Set_type=nom (No Media)
Cache: Cache_root=/export/home/cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Mounted at /mnt

Note: Only the cache information is available.

Page 31 of 100
The main parameters are described as follows:

General Parameters Description

Use_media Media type selected for the set.
Default = disk, writable for the SDF and UDF file system
Spread Spread option yes if the set can be spread to another jukebox.
Default = NO
Quota=2048 The maximum number of media that can be allocated to the set.
Default = 2048
Media Number of media currently belonging to the set.
Set_type File system selected (SDF or UDF)
Restore_fsdb Option that allows rebuilding, UDF and SDF Data Base on the next
mount.
Default = NO
Read_only The set can be mounted read only with this option.
Default = NO
Make_copy Automatic start of vlcopy. When current medium is filled, vlcopy
command copies it to the first available medium with the same capacity.
Option disabled for UDF single volume/automount.
Default = NO
Set_Id Set ID for this surface, assigned automatically by VL
For UDF spanning and SDF only
Cache: Cache parameters related to the set, created with vlcache command.
Cache_root=/export/home/cache_Test
Max_number_of_pages=1600 (100 MB) Default =No cache
Page_size=64 Kbytes
0: In set number
Online=jb:1 Status on line = shelf number
Status offline = off line location
Sequence_numbers=0,1 (SDF) Surface sequence numbers for the media in the set.
Sequence_numbers=1,2 (UDF spanning) For UDF spanning and SDF only
Mounted Surface status: a,b both surfaces are mounted.

Mounted at Directory where the file system is mounted.

SDF Specific Parameters Description

Compression This compression option is available only for tape media.
Default = Default
Shreddng mode This shredding option is available only for rewritable optical media.
Default = Not displayed

Page 32 of 100
UDF Specific Parameters Description
Logical_volume_identifier q_3b0a578e
NA (Not Available) for automount Interchange Level
UDF_revision=150 Version of the UDF file system.
Type of Integral Volume set created.
Interchange_level
Single -Volume set
Automount set.
Spanning set.
Automount_Sequence_numbers=0,1 For automount Interchange Level
Sequence_numbers=0,1 For single-surface and spanning Interchange Level
Packet_writing_init=no Packet writing option.
Default=no
Space_calculation=yes Space calculation option.
Default=yes
Verify write option.
Verify_write=no
Default=no
Close_full_volume=yes Automatically close the media when it is full option.
Only for spanning Interchange Level.
Default=no
File_spanning=yes Span the file across different media.
Only for spanning Interchange Level.
Default=yes
Use_image_backup=no Create an image backup of the current write surface.
Only for spanning Interchange Level.
Default=yes for CD/DVD-R media, no for WORM Optical media.

Page 33 of 100
VL JUKEBOX RELATED COMMANDS
The jukebox shelves and media information can be extracted from the VL database. Please note that if media is imported or
exported from the jukebox without the use of the VL commands (vlimport/vlexport), the changes will not be updated in the VL
database. The VL database associates each media to a Shelf # when the media is imported into the jukebox.

The vllsdev command is used to displays the jukebox shelves and media information.

vllsdev [-H host_name] [-nBI] device_name shelf_number

vllsdev [-H host_name] [-nsiebwuSABCI] device_name
vllsdev [-H host_name] [-vnsiebwuSABCI] -a

Note: QStar recommends reviewing the explanation for the vllsdev command in Chapter 9 - Command Reference of this
manual, while reading this section.

Main Information for the Media in the VL Database

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-RS 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.
dup The media in the shelf is identical to another in the jukebox.
inaccessible The shelf is marked as inaccessible when the shelf has been set to offline by jb command, check its status
with jbstatus and rectify with the jbshelf command.
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-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.

Size of each surface of the media #MB or #GB

Type of media present in the shelves Rewritable, Worm, Tape, CD-ROM, CD-R,
DVD-RAM, DVD-ROM, DVD-R, BD-RE, BD-RS
Status of write -protection tab of the media prot (physical media write protect switch is on)

Page 34 of 100
If the media is already added to the Integral Volume set,
using the vllsdev command with -n option, the SetName is
displayed instead of the Set_id SetName=Test

The information for SDF and UDF file systems are described as follows:

Set Identifier for each media added to a Integral Volume set Set_Id=807aeea2.34ba1fc5 (SDF)
Log_vol_id=q_3bc5af80 (UDF)

Sequence Surface Number of the media in the Integral Volume set Seq=0/Seq=1 (SDF)
Seq=1/Seq=1 (UDF Single-Volume
/Automount)
Span=1/Span=2 (UDF Spanning)

The name used as a CD/DVD-ROM identifier is CD/DVD-ROM label LabelName=QSTAR_SOFTWARE

LabelName=NO_NAME (CD/DVD-ROM without label)

The unique CD/DVD-ROM identifier is the Set_id. Set_id=478fe.680039ec

Displaying the Jukebox Media and Shelf Information

1) To display the jukebox shelf information for a jukebox with a device name jb, enter:

#>vllsdev jb

2) To display the jukebox shelf information by the set_name instead of the set_Id for a jukebox with a device name jb, enter:

#>vllsdev -n jb

3) To display the jukebox shelf information for shelves with blank or erased media only for a jukebox with a device name jb,
enter:

#>vllsdev -b jb

4) To display the jukebox shelf information sorted by set_name for a jukebox with a device name jb, enter:

#>vllsdev -Sn jb

5) To display the jukebox shelf information by the bar code instead of the set_Id for a jukebox with a device name jb, enter:

#>vllsdev -B jb

6) To display the jukebox shelf information by the the Media Serial Number (option available only for UDO media) instead of
the set_Id for a jukebox with a device name jb, enter:

#>vllsdev -I jb

Page 35 of 100
Displaying jukebox shelf Information for the SDF and UDF File
Systems

1) To display the jukebox shelf information for a jukebox with a device name jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
-----------------------------------------------------------------------------
1a: udf-201 2.4 GB Rewritable Seq=1 Log_vol_id=q_abc5af80
1b: udf-201 2.4 GB Rewritable Seq=1 Log_vol_id=q_3bc5afbf
1a: udf-200-F 2.4 GB Rewritable Seq=1 Log_vol_id=q_abc5efc0
1b: udf-200-F 2.4 GB Rewritable Seq=1 Log_vol_id=q_bbc3afbf
3a: erased 1.2 GB Rewritable
3b: erased 1.2 GB Rewritable
4a: udf-150 2.4 GB Rewritable Seq=1 Log_vol_id=q_3b45af90
4b: udf-150 2.4 GB Rewritable Seq=1 Log_vol_id=q_3bdbbfbf
5a: unknown 622 MB Rewritable
5b: unknown 622 MB Rewritable
6a: udf-150 2.4 GB Rewritable Span=1 Log_vol_id=q_3cd546f0-1
6b: udf-150 2.4 GB Rewritable Span=2 Log_vol_id=q_3cd546f0-2
7: empty
8: empty
9: empty
10a: sdf 1.2 GB Worm Seq=0 SetId=807bef41.361b3d4d
10b: sdf 1.2 GB Worm Seq=1 SetId=807bef41.361b3d4d
11a: sdf 1.2 Gb Worm Seq=2 SetId=807bef41.361b3d4d
11b: sdf 1.2 GB Worm Seq=3 SetId=807bef41.361b3d4d

Output: CD/DVD-ROM media with the UDF and ISO 9660 file systems
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
-------------------------------------------------------------------------------------
1a-1: udf-150-F 85 MB CD-ROM Seq=1 Log_vol_id=QStar_Software
2a-1: udf-150-F 700 MB CD-ROM Seq=1 Log_vol_id=Backup_01
3a-1 udf-150-F 700 MB CD-ROM Seq=1 Log_vol_id=Backup_02
4a-1: udf-150-F 150 MB CD-ROM Seq=1 Log_vol_id=windows_manual
5a-1: udf-150-F 3.7 GB DVD-ROM Seq=1 Log_vol_id=unix_manual
6a-1: udf-150-F 650 MB CD-ROM Seq=1 Log_vol_id=Data_01
7a-1: udf-150-F 650 MB CD-ROM Seq=1 Log_vol_id=Data_02
8a-1: 9660-RJ 3.8 GB DVD-ROM Manual_01 3a14c0.8ee56da1
9a-1: 9660-RJ 4.2 GB DVD-ROM Manual_02 3c04c0.8dd75dc0
10a-1: udf-150-F 3.5 GB DVD-ROM Seq=1 Log_vol_id=data2000
10b-1: udf-150-F 4.2 GB DVD-ROM Seq=1 Log_vol_id=data2001

Note: The “1a-1” or “13a-2” value on the first column of the vllsdev output for a CD/DVD jukebox represents respectively the
shelf number and the magazine or pack number.

Note1: By using the vllsdev command, the jukebox shelf information can be sorted by SetName, Set_id or LabelName.
For more detailed information on the vllsdev command, please refer to Chapter 9 - Command Reference in this manual.

Page 36 of 100
FIXING VL 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 jukebox or a manual intervention (when someone has manually
moved media, within or out of the jukebox 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 jukebox status.

The vlverify command is used to print any inconsistencies in the VL database.

vlverify [-H host_name]

The vlrefresh command is used to refresh and fix the inconsistencies in the VL database.

vlrefresh [-H host_name] -f

Note: QStar recommends reviewing the explanation for the vlverify and vlrefresh commands in Chapter 9 - Command
Reference of this manual, while reading this section.

If either of the above listed problems is suspected, the vlverify command should be used to check the jukebox media status. If
the jukebox media status differs from the VL database, then the vlrefresh command must be run at the earliest convenience to
avoid any further 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 jukeboxes. The more shelves to refresh, the longer this will take. This process must be
allowed to complete without interference.

Fixing a Database Inconsistency after a Jukebox Hardware

Failure
To explain this procedure an SDF 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 jukebox 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 jukebox and the
QStar Software can detect it. The vllsset and vllsdev command is used to displays the current status of the Integral Volume set
and jukebox databases.

A set Test was created, three media were added and the Integral Volume set is currently mounted.

A) To display the set information for the Integral Volume set Test, enter:
#>vllsset –v Test

Test
Use_media=disk,writable Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
Set_Id=807aeea2.34ba1fc5
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
2: Online=jb:2 Sequence_numbers=2,3
4: Online=jb:3 Sequence_numbers=4,5

Note: The media with sequence_number 2 and 3 was imported into shelf 2.

Page 37 of 100
B) To display the jukebox shelf information for a jukebox with a device name jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
----------------------------------------------------------------------------------
1a: sdf 2.4 GB Rewritable Seq=0 SetId=807aeea2.34ba1fc5
1b: sdf 2.4 GB Rewritable Seq=1 SetId=807aeea2.34ba1fc5
2a: sdf 2.4 GB Rewritable Seq=2 SetId=807aeea2.34ba1fc5
2b: sdf 2.4 GB Rewritable Seq=3 SetId=807aeea2.34ba1fc5
3a: sdf 2.4 GB Rewritable Seq=4 SetId=807aeea2.34ba1fc5
3b: sdf 2.4 GB Rewritable Seq=5 SetId=807aeea2.34ba1fc5
4a: erased 2.4 GB Rewritable
4b: erased 2.4 GB Rewritable
5a: erased 2.4 GB Rewritable
5b: erased 2.4 GB Rewritable
6a: erased 2.4 GB Rewritable
6b: erased 2.4 GB Rewritable
7: empty
8: empty

Note: The shelf information for the jukebox named jb matches the information reported in the vllsset output and the vllsdev
output also shows that shelf 8 is empty.

Using the eject/load button on the front panel of the jukebox the media in shelf 2 is moved to shelf 8.
The VL database cannot track this operation, so when an attempt is made to access this media, an error message will be
returned.

C) To verify if there is any inconsistency in the VL database, enter:

#>vlverify
host_name, device jb, shelf 2: Shelf empty
host_name, device jb, shelf 8: Shelf full
host_name, set Test, in_set_number 1: Shelf empty

If the VL database is consistent with the jukebox status information, no messages will be returned. If the VL database is
inconsistent with the jukebox status information a message such as the one above will be returned.

D) To fix the inconsistency the System Administrator must first ensure that all the Integral Volume sets are unmounted, that
there are no administrative commands running for any of the jukeboxes connected to the system and enter the following
command:

#>vlrefresh -f
jb: refreshing shelf 1….
jb: refreshing done
Fixing databases ...

Note: This command refreshes all media present in all jukeboxes connected to the system and fixes any database inconsistencies.
If the media was found in the jukebox, no additional information will be reported in the /opt/QStar/log/syslog file.

Page 38 of 100
E) To display the changes that were made in the set information for the Integral Volume set Test, enter:

#>vllsset –v Test

Test
Use_media=disk,writable Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
Set_Id=807aeea2.34ba1fc5
Cache: Cache_root=/export/home/cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
0: Online=jb:1 Sequence_numbers=0,1
2: Online=jb:8 Sequence_numbers=2,3
4: Online=jb:3 Sequence_numbers=4,5

Note: The fixing procedure found the media in the jukebox and corrected the set database information for the Integral Volume
set Test by updating the correct location for the media. Now the media is reported as loaded in shelf 8.

F) To display the changes that were made to the jukebox shelves information, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
----------------------------------------------------------------------------------
1a: sdf 2.4 GB Rewritable Seq=0 SetId=807aeea2.34ba1fc5
1b: sdf 2.4 GB Rewritable Seq=1 SetId=807aeea2.34ba1fc5
2: empty
3a: sdf 2.4 GB Rewritable Seq=4 SetId=807aeea2.34ba1fc5
3b: sdf 2.4 GB Rewritable Seq=5 SetId=807aeea2.34ba1fc5
4a: erased 2.4 GB Rewritable
4b: erased 2.4 GB Rewritable
5a: erased 2.4 GB Rewritable
5b: erased 2.4 GB Rewritable
6a: erased 2.4 GB Rewritable
6b: erased 2.4 GB Rewritable
7: empty
8a: sdf 2.4 GB Rewritable Seq=2 SetId=807aeea2.34ba1fc5
8b: sdf 2.4 GB Rewritable Seq=3 SetId=807aeea2.34ba1fc5

Note: The vllsdev output also displays the information about the new location of the media in the jukebox. Now shelf 2 is
marked as empty and shelf 8 now contains the media with sequence numbers 2 and 3.

Page 39 of 100
Fixing Database Inconsistencies after a Media has been
Manually Removed from the Jukebox
In this example the media is exported using the eject command from the front panel of the jukebox. The procedure is the same
as shown in the previous example, but in this case, the media was not found in the jukebox. The changes that are made in the
vllsset and vllsdev output are different from the previous example and additional information is reported in the
/opt/QStar/log/syslog file because the media is considered lost. After the refresh procedure is complete and the database is
fixed, if the media was not found in the jukebox, the /opt/QStar/log/syslog file and in the console window will report the
following message:
VL: set Test fixed: in_set_number 1 (jb:2) set offline: Shelf empty

A) To display the changes that were made in the set information for the Integral Volume set Test, enter:

#>vllsset –v Test

Test
Use_media=disk,writable Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
Set_Id=807aeea2.34ba1fc5
Cache: Cache_root=/export/home/cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
0: Online=jb:1 Sequence_numbers=0,1
2: Offline= Lost Media jb:2 Sequence_numbers=2,3
4: Online=jb:3 Sequence_numbers=4,5
This time the media was not found in the jukebox. The procedure to correct the set database information for the Integral Volume
set Test is to set the media as Offline 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_numbers=2,3 as Offline=Lost
Media jb:2. 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 "Managing Offline Media under VL Control" section in this chapter for more
detailed information.

B) To display the changes that were made to the jukebox shelf information, enter:
#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
----------------------------------------------------------------------------------
1a: sdf 2.4 GB Rewritable Seq=0 SetId=807aeea2.34ba1fc5
1b: sdf 2.4 GB Rewritable Seq=1 SetId=807aeea2.34ba1fc5
2: empty
3a: sdf 2.4 GB Rewritable Seq=4 SetId=807aeea2.34ba1fc5
3b: sdf 2.4 GB Rewritable Seq=5 SetId=807aeea2.34ba1fc5
4a: erased 2.4 GB Rewritable
4b: erased 2.4 GB Rewritable
5a: erased 2.4 GB Rewritable
5b: erased 2.4 GB Rewritable
6a: erased 2.4 GB Rewritable
6b: erased 2.4 GB Rewritable
7: empty
8: empty

Note: The vllsdev output displays that shelf 2 is now empty.

Page 40 of 100
MANAGING OFFLINE MEDIA UNDER VL CONTROL
The QStar offline volume tracking is managed through the VL database. As all media has a unique electronic Set ID, Surface
Sequence ID (SDF) or Logical Volume id (UDF), the media can be tracked by the VL database. Any media from an Integral
Volume set that is exported with the vlexport command requires 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 jukebox. The
request can then be satisfied or canceled using the vlconsole command.

If the QStar E-Mail notification service is configured, the System Administrators will receive an E-mail notification to import
the requested media. For this reason, configuring mail notification is highly recommended.

The vlimport command is used to import the media into a jukebox and check the media’s content.

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}]
device_name shelf_number [num_shelves]

The vlexport command is used to export media from the jukebox and store it in an offline location, if it belongs to an Integral
Volume set in the VL database.

vlexport [-H host_name] [-a] [-o] device_name shelf_number [num_shelves]

The vlconsole command is used to manage the list of VL requests for manual assistance. The vlconsole -l command displays a
list of all the pending requests that the VL module sent to the System Administrator and their status. For example, a typical
request can be to import an erased or an offline media and the status can be pending, satisfied, or canceled.

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

Note: QStar recommends reviewing the explanation for the vlimport, vlexport and vlconsole commands in Chapter 9 -
Command Reference of this manual, while reading this section.

Managing Offline Media

To explain this procedure an SDF 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, three 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
jukebox 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 the request to re-import the offline media will wait until the offline request is satisfied by importing the media
or canceled using the proper option in the vlconsole command. The System Administrator instead of waiting can
immediately receive an error for an offline request. To change the offline behavior, please refer to Displaying and Setting
the VL Configuration for Offline Media Request Properties section later in this chapter.

Page 41 of 100
A) To display the current set information for the Integral Volume set Test, enter:

#>vllsset –v Test

Test
Use_media=disk,writable Spread=no Quota=2048 Media=3
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
4: Online=jb:3 Sequence_numbers=4,5 Mounted=a,b

Note: The media in shelf 1, shelf 2 and shelf 3 belong to the Integral Volume set Test.

B) The media in shelf 1 is exported usung the vlexport command. Because the media belongs to the Integral Volume set Test
an offline location is requested by the QStar Software. In the example, “firesafe” is the offline location specified. To
export the media in shelf 1, enter:

#>vlexport jb 1
jb: Please remove medium from mailslot.
Test:0 exported from jb:1.
Please enter offline location [Test_0]: firesafe

If no offline location is specified, the QStar Software will assign the default offline location, which 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_0).

If the Pack ID number (DISC/NSM) 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 the vlinset command.

C) To display the new set information for the Integral Volume set Test after the media in shelf 1 was stored offline, enter:

#>vllsset –v Test

Test
Use_media=disk,writable Spread=no Quota=2048 Media=3
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: Offline=firesafe Sequence_numbers=0,1 Mounted=a,b
2: Online=jb:2 Sequence_numbers=2,3 Mounted=a,b
4: Online=jb:3 Sequence_numbers=4,5 Mounted=a,b

Note: The media with in_set_number 0 and Sequence_numbers =0 ,1 is offline and “firesafe” is its offline location.

Page 42 of 100
D) Now that the media has been moved to an offline location, if a user tries to access a file residing on that media, the VL
will request the media to be re-imported.

Below is displayed a VL request for offline media with the SDF file system. This request goes into the /opt/QStar/log/syslog
file and console window and will also generate an E-mail notification (if mail notification is configured).

SDF: set Test, sequence_number 0, offline firesafe : Please vlimport medium

E) To Display the list of the VL requests, enter:

#>vlconsole -l
10/11/2001 20:57:08 Pending Bring online Test:0 firesafe

Note: The VL request to bring the media online is still pending.

F) To satisfy the request for the offline media, import the media into any available empty shelf of the jukebox. In this example,
the media is re-imported to shelf 1. To import the media to shelf 1, enter:

#>vlimport jb 1
jb: refreshing shelf 1 ...

After the media is refreshed, the QStar Software will satisfy the user’s request and mark the media as online in the VL set
database.

G) To display the new set information for the Integral Volume set Test after the media has been re-imported, enter:

#>vllsset –v Test

Test
Use_media=disk,writable Spread=no Quota=2048 Media=3
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 Offloc=firesafe
2: Online=jb:2 Sequence_numbers=2,3 Mounted=a,b
4: Online=jb:3 Sequence_numbers=4,5 Mounted=a,b

The set database displays the media in shelf 1 as online and the QStar Software maintains the offline location information in its
database. The next time the media is exported this offline location will be used as default.

H) To Display the list of the VL requests, enter:

#>vlconsole -l
10/11/2001 20:59:10 Satisfied Bring online Test:0 jb:1

Note: The VL request to bring the media online has been satisfied.

Page 43 of 100
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, use the following command:

vlconsole -c -N set_name sequence_number

Displayed below is a VL request for offline media with the SDF file system:
SDF: set Test, sequence_number 0, offline firesafe : Please vlimport medium

A) To display the list of the VL requests, enter:

#>vlconsole -l
10/11/2001 21:00:02 Pending Bring online Test:0 firesafe

Note: The VL request to bring the media online is still pending.

B) To cancel the VL request, enter:

#>vlconsole -c -N Test 0

C) To display a list of the VL requests, enter:

#>vlconsole -l
10/11/2001 21:02:45 Canceled Bring online Test:0 firesafe

Note: The VL request to bring the media online is canceled. Once the request is canceled, the user will get the prompt back in
the window where the request for the offline media was run.

Managing Offline Integral Volume Sets

With the QStar Software, the Integral Volume set can be taken offline and all the information can be maintained in the VL
database.

To export the entire Integral Volume set with one command, enter:

#>vlexport –s Test

To import the entire Integral Volume set with one command, enter:

#>vlimport –s Test

Page 44 of 100
MANAGING OFFLINE MEDIA UNDER VL CONTROL
USING THE MAGAZINE OR PACK IMPLEMENTATION
The QStar Software for certain type of jukeboxes, 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 jukebox but loaded
on a different shelf, the shelf information will be updated in the VL set database with the new location. If the media is removed
from the jukebox, the shelf in the VL set database will be automatically switched to offline.

The exchange and update operations in the magazines or packs are made using the vlmagazine command; 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 the
vlexchange command.

QStar suggests unmounting all Integral Volume sets before running the vlmagazine command in order to insure correct
exchange operation. Once the vlmagazine command is run, all the media loaded in the drives will return to their shelves and
the exchange operation is allowed automatically, removing the prevent_removal status and allowing the door to be opened or
removal of the packs. Terminating the exchange procedure by closing the door or reinserting the pack will automatically start a
refreshing procedure 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.
A jbmagazine command is also available to open the jukebox door or allow the packs to be removed without updating the VL
database. For example, this command can be used in the case of a hardware failure to open the jukebox door.

The vlmagazine command is used to exchange media in the jukebox using the magazines and updates the VL database.

vlmagazine [-H host_name] [-p {cd-rom | cd-r | cd-rw | dvd-rom | dvd-r | dvd-ram | dvd-rw | dvd-rw-s | 1}][-s]
device_name [magazine_number | h]

Note: If magazine_number is omitted all magazines are available for exchange. The h option as magazine_number is used for
hyper magazine (Pioneer jukebox only).

The vlexchange command is used to move media from one internal shelf or shelf belonging to a pack, to another in the jukebox
and updates VL databases.

vlexchange [-H host_name] device_name shelf_number_1 shelf_number_2 [num_shelves]

If the destination shelf is empty, the vlexchange command moves media from the source shelf to the destination shelf in the
jukebox. If media is present on the destination shelf, the vlexchange command exchanges a media from the source shelf with
the destination shelf.

Note: QStar recommends reviewing the explanation for the vlmagazine, vlexchange and jbmagazine commands in Chapter 9 -
Command Reference of this manual, while reading this section.

Page 45 of 100
To explain the exchange procedure CD/DVD media with ISO 9660 and the UDF file system is used. An Integral Volume set
named Test was created, five pieces of media were added to it and the Integral Volume set is currently mounted.

A) To display the current set information for the Integral Volume set Test, enter:

#>vllsset –v Test

Test
Use_media=cd,dvd,worm,rdonly Spread=no Quota=2048 Media=5
Restore_fsdb=no Read_only=yes Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=no Space_calculation=yes Verify_write=no
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 Automount_sequence_number=0 Mounted=a A_dir=Test_0
1: Online=jb:2 Automount_sequence_number=1 Mounted=a
2: Online=jb:3 Automount_Sequence_number=2 Mounted=a
3: Online=jb:4 Automount_sequence_number=3 Mounted=a
4: Online=jb:5 Automount_sequence_number=4 Mounted=a

Note: The media from shelf 1 to shelf 5 belong to the Integral Volume set Test.

B) To display the jukebox shelf information for a jukebox with a device name jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
---------------------------------------------------------------------------------
1a-1: 9660 11 MB CD-ROM NO_NAME 017ea.43ce21e8
2a-1: 9660-R 30 MB CD-ROM QStar_Manual 03c8d.65e720a1
3a-1: 9660 9 MB CD-ROM QSTAR 012f0.c31b4dc5
4a-1: 9660 58 MB CD-ROM Q_SOURCE 074c1.a122bb6c
5a-1: 9660-J 79 MB CD-ROM QSTAR_SOFTWARE 09ed2.51a571a0
6-1: empty
7-1: empty
8-1: empty
9-1: empty
10-1: empty

Note: The shelves from shelf 1 to shelf 5 are full and the shelves from shelf 6 to shelf 10 are empty.

C) To exchange the magazines for a jukebox with a device name jb, enter:

#>vlmagazine jb
jb: Please open the door, do manual operations and close the door.
Type Enter when ready:

Page 46 of 100
The vlmagazine command can also be used with the -p option. The -p option is used to specify the type of media that will be
imported. This option can be used with CD/DVD jukeboxes with mixed drives types or drives that support different types of
media. This ensures loading the media into the correct drive during the refresh procedure to determine the media type of the
shelf. If the -p option is omitted 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 which can
handle this media type.

Note: QStar highly recommends ensuring mounted volumes do not contain media within the removable packs/magazines,
otherwise all Integral Volume sets will need to be unmounted before using the vlmagazine command. If any pack/magazine has
a mounted volume, the vlmagazine command will return busy error. With the NSM/DISC series, any individual pack may be
unlocked, providing it does not contain media from a mounted Integral Volume set. This is done by specifying the pack number
in the vlmagazine command. Example: vlmagazine jb 2 this will release pack 2.

The vlmagazine command will open the door or will release the pack and will return the message below:

jb: Please open the door, do manual operations and close the door.
Type Enter when ready:

Before typing Enter do the following:

1) Exchange the media in the jukebox.

2) Close the door.
3) Type Enter.

In our example, the media in shelf 1and shelf 2 of the first magazine are moved respectively to the shelf 8 and shelf 10 of the
same magazine, the others media are removed from the magazine and new media is inserted in shelf 9.

Once the door is closed, the QStar Software will automatically start the refresh procedure of the media exchanged and
subsequently the fixing procedure of the VL databases.

jb: refreshing shelves 8 9 10 ...

jb: refreshing done
Fixing databases ...

D) To display the jukebox shelf information for a jukebox with a device name jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
---------------------------------------------------------------------------------
1-1: empty
2-1: empty
3-1: empty
4-1: empty
5-1: empty
6-1: empty
7-1: empty
8a-1: 9660 11 MB CD-ROM NO_NAME 017ea.43ce21e8
9a-1: 9660-J 85 MB CD-ROM QSTAR_SOFTWARE_1 0a5da.76fe3a14
10a-1: 9660-R 30 MB CD-ROM QStar_Manual 03c8d.65e720a1

Note: The media from shelf 1 to shelf 7 are empty, 8 and 10 contain the media previously in shelves 1, 2 and 9 is a new media.

Page 47 of 100
E) To display the new set information for the Integral Volume set Test after the exchange procedure, enter:

#>vllsset –v Test

Test
Use_media=cd,dvd,worm,rdonly Spread=no Quota=2048 Media=5
Restore_fsdb=no Read_only=yes Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=no Space_calculation=yes Verify_write=no
Cache: Cache_root=/export/home/cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Mounted at /mnt
0: Online=jb:8 Automount_sequence_number=0 Mounted=a A_dir=Test_0
1: Online=jb:10 Automount_sequence_number=1 Mounted=a
2: Offline=jb:Test_2 Automount_Sequence_number=2 Mounted=a
3: Offline=jb:Test_3 Automount_sequence_number=3 Mounted=a
4: Offline=jb:Test_4 Automount_sequence_number=4 Mounted=a

Note: The media from shelves 1 and 2 are still on line, they are now located in shelves 8 and 10, all the other media are set
offline.

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 (NSM/DISC) 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. The offline location name can be changed if
required using the vlinset command. 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. Once the exchange operation is completed, remount all Integral Volume sets.

F) To exchange the media in the magazines or between the packs and the internal shelves for a jukebox with a device name jb,
enter:

#>vlexchange jb 8 1

In our example the media in shelf 8 and shelf 1 of the magazine or pack 1 will be exchanged. Because shelf 1 is empty, the
media from shelf 8 will be moved to shelf 1 and the QStar VL database for the jukebox and the Integral Volume set will be
automatically updated.

Page 48 of 100
G) To display the jukebox shelf information for a jukebox with a device name jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
---------------------------------------------------------------------------------
1a-1: 9660 11 Mb CD-ROM NO_NAME 017ea.43ce21e8
2-1: empty
3-1: empty
4-1: empty
5-1: empty
6-1: empty
7-1: empty
8-1: empty
9a-1: 9660-J 85 Mb CD-ROM QSTAR_SOFTWARE_1 0a5da.76fe3a14
10a-1: 9660-R 30 Mb CD-ROM QStar_Manual 03c8d.65e720a1

Note: Shelf 8 is empty and shelf 1 contains the media previously in shelf 8.

H) To display the new set information for the Integral Volume set Test after the exchange procedure, enter:
#>vllsset –v Test

Test
Use_media=cd,dvd,worm,rdonly Spread=no Quota=2048 Media=5
Restore_fsdb=no Read_only=yes Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=no Space_calculation=yes Verify_write=no
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 Automount_sequence_number=0 Mounted=a A_dir=Test_0
1: Online=jb:10 Automount_sequence_number=1 Mounted=a
2: Offline=jb:Test_2 Automount_Sequence_number=2 Mounted=a
3: Offline=jb:Test_3 Automount_sequence_number=3 Mounted=a
4: Offline=jb:Test_4 Automount_sequence_number=4 Mounted=a

Note: The media from shelf 8 is still on line, but is now located in shelf 1.

Page 49 of 100
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 as more space is needed.

No Media Available
To explain this procedure an Optical jukebox is used, but the example is valid for every type of jukebox supported by the QStar
Software.

In the following example an Integral Volume set is mounted; writing data to the cache and archiving the data to the media in the
set has exceeded the available capacity and there is no available (blank or erased) media in the jukebox. The _vlserver daemon
will automatically display the following message in the QStar syslog file, in an E-mail if the mail notification is enabled and in
the output of vlconsole command:
SDF: set Test, sequence_number 1: Please vladdtoset erased (blank) medium

UDF: 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, the Integral Volume set can not be unmounted nor can the process be terminated. To fix this problem, do the
following:

1) The vlimport command is used to import the media into a jukebox and check the media’s content.

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}]
device_name shelf_number [num_shelves]

To import a new media into the jukebox, enter:

#>vlimport jb 1

Note: If all the shelves are full, one of the media will have to be exported to an offline location and import into this free shelf.

2) The vlerase command is used to erase the media.

vlerase [-H host_name] [-v] [-fe] [-j {delayed_job_name | "default"}] [-d {[mmdd]HHMM|[cc]yymmddHHMM}]
device_name shelf_number[{a|b}]

If the media is rewritable and is not erased, it must be erased, to erase the media, enter:

#>vlerase jb 1

3) The vladdtoset command is used to add the media to the set.

vladdtoset set_name device_name shelf_number

To add the new media to the set, enter:

#>vladdtoset Test jb 1

The _vlserver 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 jbscheduler automatically activates the process that was in the disk wait-state and the archiving
can continue.

Page 50 of 100
RESTORING AN INTEGRAL VOLUME SET

Restoring an Integral Volume Set not Known to the VL

Database
There are usually two situations where an Integral Volume set is not known to the Volume Librarian (VL) database.

1) After an upgrade from an earlier version of the QStar Software.

2) The Integral Volume set was exported from the jukebox and the Integral Volume set definition was deleted from the VL
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 jukebox, use the vlimport command to bring the media back into the jukebox, this will
update the VL database on import. If an upgrade has been carried out and the media is still in the jukebox, use the vlrefresh
command 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.

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 jukebox 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) To refresh the contents of the jukebox identified as jb (for each configured jukebox), enter:

#>vlrefresh jb

2) To create an Integral Volume set definition named Test, enter:

#>vlcrset Test

3) To add the media in shelf 1 to the Integral Volume set named Test, enter:

#>vladdtoset Test jb 1

Note: This will also add to the Integral Volume set any other media in the jukebox with the same set_Id.

After that, the Integral Volume set is ready to be mounted with the mountiv command.

Page 51 of 100
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 using the vldelset command,
bringing the Integral Volume set back online can be achieved in one of two ways.

The following are examples of both scenarios:

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.

a) To import a media that belongs to the Integral Volume set exported from the jukebox into shelf 10 of the jukebox
named jb (this will automatically update the VL database), enter:

#>vlimport jb 10

b) To create an Integral Volume set definition named Test, enter:

#>vlcrset –T sdf Test

Note: The vlcrset command should be run with the appropriate options for the media and file system used. The example
has created an Integral Volume set with the SDF file system and rewritable media.

c) To add to the media into shelf 10 to the Integral Volume set Test, enter:

#>vladdtoset Test jb 10

Note: Once the first media is added to the set, any other media imported into the jukebox that has the same Set_Id will be
automatically added.

d) To import any other media belonging to the Integral Volume set, enter:

#>vlimport jb 11

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, add a cache to the
Integral Volume set with the vlcache command and then the Integral Volume set is ready to be mounted with the
mountiv command.

2) Import all the media belonging to the Integral Volume set and then create the Integral set definition.

a) To import all media belonging to the Integral Volume set, enter:

#>vlimport jb 10

#>vlimport jb 11

Note: In the example there are only two media in the Integral Volume set.

Page 52 of 100
b) To create an Integral Volume set definition named Test, enter:

#>vlcrset –T sdf Test

c) To add to the media into shelf 10 to the Integral Volume set Test (shelf 11 will automatically be added to the set),
enter

#>vladdtoset Test jb 10

The Integral Volume set is now re-created. The next step is to add a cache to the Integral Volume set with the vlcache
command and then the Integral Volume set is ready to be mounted with the mountiv command.

Page 53 of 100
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
on the media. 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”.
The Data Compaction utility is available only for Optical, DVD-RAM and Blu-ray media written with the SDF file system.
The Data Compaction utility can also be used with Tape but QStar highly recommends not using it because the performance of
Data Compaction on tape device is extremely poor.

The following commands are used for managing the dead space on a piece of media:

vlmediausage 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
“Dead Space”.
vlmediausage [-H host_name] set_name
vlreuse 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
vlmediausage 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.
vlreuse [-r] [-H host_name] set_name in_set_number [-j {delayed_job_name | "default"}] [-d {[mmdd]HHMM |
[cc]yymmddHHMM}] set_name in_set_number...
vldelfromset 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.
vldelfromset [-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.

Page 54 of 100
Data Compaction Feature for the SDF File System
The following is an example of the Data Compaction utility using the vlreuse command 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. The vllsset command is used to display the current status for the Integral Volume set database.

An Integral Volume set Test was created, eight media were added and the Integral Volume set is currently mounted.

A) To display the set information for the Integral Volume set Test, enter:

#>vllsset –v Test

Test
Use_media=disk,writable Spread=no Quota=2048 Media=8
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
SetId=5246b54c.36fa4670
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
2: Online=jb:2 Sequence_numbers=2,3
4: Online=jb:3 Sequence_numbers=4,5
6: Online=jb:4 Sequence_numbers=6,7
8: Online=jb:5 Sequence_numbers=8,9
10: Online=jb:6 Sequence_numbers=10,11
12: Online=jb:7 Sequence_numbers=12,13
14: Online=jb:8 Sequence_numbers=14,15

Note: The media from shelf 1 to 8 belongs to the Integral Volume set Test.

B) To list and analyze the statistical information for all media belonging to the Integral Volume set Test, enter:

#>vlmediausage Test

[>-------------------------------------------------] Analyzing file maps...

[+++++++++++++++++++++++++>------------------------] Checking volumes...
[++++++++++++++++++++++++++++++++++++++++++++++++++] Done.
Set Test: 8 media
Seq. Status Location Capacity Used Dead Available %used
0. Written jb:1 614MB 273MB 341MB 0MB 44
2. Written jb:2 614MB 280MB 335MB 0MB 45
4. Written jb:3 563MB 262MB 302MB 0MB 46
6. Written jb:4 614MB 358MB 257MB 0MB 58
8. Written jb:5 563MB 544MB 20MB 0MB 96
10. Current jb:6 563MB 397MB 19MB 148MB 70
12. Empty jb:7 563MB 0MB 0MB 563MB 0
14. Empty jb:8 614MB 0MB 0MB 614MB 0
Total: 4.6GB 2.1GB 1.2GB 1.3GB
The following media may be reclaimed:
Seq. Location Add.space(MB) Time(min)
0. jb:1 341 15
2. jb:2 335 15
4. jb:3 302 14
6. jb:4 257 20

Page 55 of 100
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. Once the analysis is complete all information about
the media usage statistics for the Integral Volume set Test will be displayed. 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 jukebox
• Capacity of the media
• Used capacity used by the available data
• Dead capacity used by the deleted data (dead space)
• Available capacity on the media
• % used percentage of media used

The media usage analysis suggests all the media that may be reclaimed and an estimated time for the compaction. In the
example, the media in shelf 1 can be reclaimed in approximately 15 minutes.

C) To reclaim the space on the media in shelf 1with sequence number 0, erase it and add it to the Integral Volume set Test,
enter:

#>vlreuse Test 0

Reclaiming seq. 0 in set Test

[>-------------------------------------------------] Collecting data pages...
[>-------------------------------------------------] 4266 data pages selected,
[>-------------------------------------------------] Writing to vol 11 (/dev/jb
[++>-----------------------------------------------] 200 pages written
[++>-----------------------------------------------] 200 pages relocated.
[+++++++++++++++++++++++++>------------------------] Writing to vol 11 (/dev/jb
[+++++++++++++++++++++++++>------------------------] 200 pages written
[+++++++++++++++++++++++++>------------------------] 2200 pages relocated.
[+++++++++++++++++++++++++++>----------------------] Writing to vol 12 (/dev/jb
[+++++++++++++++++++++++++++++++++++++++++++++++++>] 200 pages written
[+++++++++++++++++++++++++++++++++++++++++++++++++>] 4200 pages relocated.
[+++++++++++++++++++++++++++++++++++++++++++++++++>] Writing to vol 12 (/dev/jb
[++++++++++++++++++++++++++++++++++++++++++++++++++] 66 pages written
[++++++++++++++++++++++++++++++++++++++++++++++++++] completed relocation of 42
[++++++++++++++++++++++++++++++++++++++++++++++++++] Done.
OK

Once the media has been reclaimed the next action of the Data Compaction utility is to erase the media and add it to the end of
the Integral Volume set.

Seq. 0 in set Test contains no more data

Seq. 0 has been removed from set Test
Erasing platter jb:1

Note: The Compaction procedure can be delayed. To reuse media using the Delayed Reuse Media procedure, please refer to
Displaying and Setting the VL Configuration Properties for Delayed Reuse Media section in this chapter.

Page 56 of 100
D) To list and analyze the new statistical information for all media belonging to the Integral Volume set Test after the vlreuse
command, enter:

#>vlmediausage Test

[>-------------------------------------------------] Analyzing file maps...

[+++++++++++++++++++++++++>------------------------] Checking volumes...
[+++++++++++++++++++++++++>------------------------] Volume # (N/A)
[++++++++++++++++++++++++++++++++++++++++++++++++++] Done.

Set Test: 8 media

Seq. Status Location Capacity Used Dead Available %used
2. Written jb:2 614MB 280MB 335MB 0MB 45
4. Written jb:3 563MB 262MB 302MB 0MB 46
6. Written jb:4 614MB 358MB 257MB 0MB 58
8. Written jb:5 563MB 544MB 20MB 0MB 96
10. Written jb:6 563MB 544MB 19MB 0MB 96
12. Current jb:7 563MB 125MB 4MB 434MB 22
14. Empty jb:8 614MB 0MB 0MB 614MB 0
16. Empty jb:1 614MB 0MB 0MB 614MB 0
Total: 4.6GB 2.1GB 0.9GB 1.6GB
The following media may be reclaimed:
Seq. Location Add.space(MB) Time(min)
2. jb:2 335 15
4. jb:3 302 14
6. jb:4 257 20

The new media usage analysis displays that the media with sequence number 0 is no longer part of the Integral Volume set; the
media in shelf 1 is empty (capacity of 0% used) and was added to the Integral Volume set Test with sequence number 16, 17.

E) To display the set information for the Integral Volume set Test after the media has been erased and added to the Integral
Volume set, enter:

#>vllsset -v Test
Test
Use_media=disk,writable Spread=no Quota=2048 Media=8
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
SetId=5246b54c.36fa4670
Cache: Cache_root=/export/home/cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Mounted at /mnt
2: Online=jb:2 Sequence_numbers=2,3
4: Online=jb:3 Sequence_numbers=4,5
6: Online=jb:4 Sequence_numbers=6,7
8: Online=jb:5 Sequence_numbers=8,9
10: Online=jb:6 Sequence_numbers=10,11
12: Online=jb:7 Sequence_numbers=12,13
14: Online=jb:8 Sequence_numbers=14,15
16: Online=jb:1 Sequence_numbers=16,17

Now the media that was loaded in shelf 1, that had a Sequence_number = 0, 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 = 16, 17 and a new in_set_number
16.

Page 57 of 100
Data Compaction Feature Using the Reallocation Only Option
The vlreuse command can also be used in the reallocation only mode. The reallocation only mode is enabled with the “-r”
flag. Specifying the reallocation only mode option, after successfully completing the reallocation procedure, where the data and
metadata that are NOT considered dead space will be copied from the specified media to the end of the Integral Volume set.
The reclaimed media will contain no up to date data and is displayed as a media that contains 100% dead space in the
vlmediausage output. However, the media still belongs to the Integral Volume set. The reallocation only mode will not erase
the reclaimed media or add it to the end of the Integral Volume set. This allows the System Administrator to decide if the media
should be exported from the jukebox (for backup purposes) or erased and added to the same or different Integral Volume set.
The media can be removed from the Integral Volume set using the vldelfromset command.

A) To reclaim only the data on the media in shelf 1 with sequence number 0, enter:

#>vlreuse -r Test 0

B) To list and analyze the new statistical information for all media belonging to the Integral Volume set Test after the vlreuse
command, enter:

#>vlmediausage Test

[>-------------------------------------------------] Analyzing file maps...

[+++++++++++++++++++++++++>------------------------] Checking volumes...
[+++++++++++++++++++++++++>------------------------] Volume # (N/A)
[++++++++++++++++++++++++++++++++++++++++++++++++++] Done.

Set Test: 8 media

Seq. Status Location Capacity Used Dead Available %used
0. Written jb:1 614MB 0MB 614MB 0MB 0
2. Written jb:2 614MB 280MB 335MB 0MB 45
4. Written jb:3 563MB 262MB 302MB 0MB 46
6. Written jb:4 614MB 358MB 257MB 0MB 58
8. Written jb:5 563MB 544MB 20MB 0MB 96
10. Written jb:6 563MB 544MB 19MB 0MB 96
12. Current jb:7 563MB 125MB 4MB 434MB 22
14. Empty jb:8 614MB 0MB 0MB 614MB 0
Total: 4.6GB 2.1GB 1.5GB 1.0GB
The following media may be reclaimed:
Seq. Location Add.space(MB) Time(min)
0. jb:1 614 0
2. jb:2 335 15
4. jb:3 302 14
6. jb:4 257 20

Note: Now the media in shelf 1 contains 100% dead space, because all the live data that was on the media has been copied to
the end to the Integral Volume set.

C) To remove the media in shelf 1 with sequence number 0 from the Integral Volume set Test, enter:

#>vldelfromset Test 0

Note: Now the media can be erased using the vlerase command and can be added to the same or different Integral Volume set
by using the vladdtoset command.

Page 58 of 100
D) To display the set information for the Integral Volume set Test, after the media has been removed, enter:

#>vllsset -v Test

Test
Use_media=disk,writable Spread=no Quota=2048 Media=7
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
SetId=5246b54c.36fa4670
Cache: Cache_root=/export/home/cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Mounted at /mnt
2: Online=jb:2 Sequence_numbers=2,3
4: Online=jb:3 Sequence_numbers=4,5
6: Online=jb:4 Sequence_numbers=6,7
8: Online=jb:5 Sequence_numbers=8,9
10: Online=jb:6 Sequence_numbers=10,11
12: Online=jb:7 Sequence_numbers=12,13
14: Online=jb:8 Sequence_numbers=14,15

Note: Now the media in shelf 1 with sequence numbers 0 and 1 is completely removed from the Integral Volume set information.

Page 59 of 100
Data Compaction not Available
The vlmediausage command may advise that the amount of free space present on the Integral Volume set it is not sufficient for
running the Data Compaction utility.

The message display as follows:

#>vlmediausage Test

[>-------------------------------------------------] Analyzing file maps...

[+++++++++++++++++++++++++>------------------------] Checking volumes...
[++++++++++++++++++++++++++++++++++++++++++++++++++] Done.
Set Test: 8 media
Seq. Status Location Capacity Used Dead Available %used
0. Written jb:1 614MB 273MB 341MB 0MB 44
2. Written jb:2 614MB 280MB 335MB 0MB 45
4. Written jb:3 563MB 262MB 302MB 0MB 46
6. Written jb:4 614MB 358MB 257MB 0MB 58
8. Written jb:5 563MB 544MB 20MB 0MB 96
10. Current jb:6 563MB 397MB 19MB 148MB 70
Total: 4.6GB 2.1GB 1.2GB 1.3GB
The following media may be reclaimed:
Seq. Location Add.space(MB) Time(min)
------ Medium below may not be reclaimed due to lack of free space! ------

0. jb:1 341 15
2. jb:2 335 15
4. jb:3 302 14
6. jb:4 257 20

If the above message appears in the vlmediausage output, add an available piece of media to the Integral Volume set using the
vladdtoset command. Run the vlmediausage command again to see if the reclaim procedure is now allowed. If allowed, then
use the vlreuse command to start the Data Compaction procedure.

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 jukebox status, this can be due to a hardware problem or human
intervention with the jukebox. To recover from this, there is a utility called vlrefresh that can be run on a single shelf, multiple
shelves or all the shelves contained in the jukebox. See the Chapter 9 - Command Reference for full details or read the
“Fixing Database Inconsistencies” section of this chapter.

Page 60 of 100
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 jukebox and verifies it
with the original once created. The Copy and Compare Media procedure can be used with Optical and Tape media with the
SDF file system and with Optical media written with UDF or ISO 9660 File system. There are three 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:

• Copy and Compare Media without VL control (SDF Only)

• Copy and Compare Media under VL control

• Automatic Copy Media under VL control

Copy and Compare Media without VL Control (SDF Only)

The System Administrator can execute a duplication process of the Optical media that has been written to, using the copydisk
command and then compare the duplicate media with the original media using the cmpdisk command once the duplication
process is finished. Both the copydisk and cmpdisk commands are available only for Optical media. The copydisk command
creates an exact duplicate of the original media written with the SDF file system in the Integral Volume set, if the original
media is damaged, the duplicate media can be used to replace the damaged media.

The copy media procedure made with the copydisk command is completely unknown to the QStar Volume Librarian database
because the VL database does not allow an exact duplicate media to co-exist in the jukebox. This means that if a media, created
with the copydisk command, is refreshed using the vlrefresh command the VL database will recognize the media as an exact
duplicate media. The VL database will mark both the original and the copied media as duplicates and will lock the Integral
Volume set that the original media belongs to until the exact duplicate media is exported from the jukebox using the vlexport
command. For this reason it is highly recommended to immediately remove the duplicate media from the jukebox after the copy
disk process has been completed. For more detailed information about “Error Recovery Using Duplicate Media”, please refer
to Chapter 8 - Disaster Recovery in this manual.

The copydisk command is used to create an exact duplicate copy of a media surface written with the SDF file system.

copydisk [-va] source destination

The cmpdisk command is used to compare the original media surface with the duplicate media surface once the Copy Media
procedure has been completed.

cmpdisk [-v] disk1 disk2

Note: The copydisk and the cmpdisk commands are available only for the Standard Data Format (SDF) file system. QStar
recommends reviewing the explanation for the copydisk and cmpdisk commands in Chapter 9 - Command Reference of this
manual, while reading this section.

1) To create an exact duplicate copy of the media in shelf 5 (side a and b) with the media in shelf 10, enter:
#>copydisk /opt/QStar/dev/jb/rjb5a /opt/QStar/dev/jb/rjb10a
#>copydisk /dev/jb0/rjb5a /dev/jb0/rjb10a (IBM syntax)

#>copydisk /opt/QStar/dev/jb/rjb5b /opt/QStar/dev/jb/rjb10b

#>copydisk /dev/jb0/rjb5b /dev/jb0/rjb10b (IBM syntax)

Page 61 of 100
2) To compare the media in shelf 5 (side a and b) with the media in shelf 10, enter:

#>cmpdisk -v /opt/QStar/dev/jb/rjb5a /opt/QStar/dev/jb/rjb10a

#>cmpdisk -v /dev/jb0/rjb5a /dev/jb0/rjb10a (IBM syntax)

#>cmpdisk -v /opt/QStar/dev/jb/rjb5b /opt/QStar/dev/jb/rjb10b

#>cmpdisk -v /dev/jb0/rjb5b /dev/jb0/rjb10b (IBM syntax)

3) To export the media in shelf 10, enter:

#>vlexport jb 10

Note: The jbexport command may also be used to export the media from the jukebox.

Substitute the Original Copy of the Media with the Exact Duplicate
To substitute the original media with the duplicate media for an Integral Volume set requires exporting the original media with
the vlexport command. When the original media is exported the System Administrator will be prompted for an offline location.
Import the duplicate media to an available shelf with the vlimport command and the media will be automatically added to the
VL set database.

Note: Substitute the original media with the duplicate media only if the cmpdisk command reports that both side a and b are
identical.

Copy and Compare Media Under VL Control

The System Administrator can execute a duplication process of the media that has been written to, using the vlcopy command
and then compare the duplicate media with the original media using the vlcmp command once the duplication process is
finished. The vlcopy command 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 Copy Media procedure made with the vlcopy
command works under the control of the QStar Volume Librarian database and creates a duplicate copy of a media (SDF, 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 (jukebox), without introducing the error condition
using duplicate media or locking the set database when the vlrefresh command is used. This means that after the Copy Media
process is completed the vlcopy command will automatically update the VL database and the media can be left in the jukebox 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.

The vlcopy command also supports the UDF and SDF file systems. Using the Incremental Copy Media option, means that if
more data is written after the vlcopy has been run, running the vlcopy subsequently will write the changes to the destination
media.

The Incremental Copy Media for the UDF file system is available only for WORM (MO/UDO/PDD/CD/DVD-R/BD-RS)
media using the vlcopy command.

The incrematal Copy Media for the SDF file system is available using the -b {full|cron_like_schedule} option in the vlcrset
command and the Delayed VL Configuration Copy Media Properties.

Page 62 of 100
The vlcopy command is used to create a duplicate copy of a media.

vlcopy [-H host_name] [-v] [-c copy_number] [-C {yes|no} [-j{delayed_job_name | "default"}]
[-d {[mmdd]HHMM|[cc]yymmddHHMM}] src_dev_name:shelf_number dst_dev_name:shelf_number]

The vlcopy command includes the following different options:

-H host_name
Specifies the name of the host where the source_jukebox and destination_jukebox are connected. Without this option, the local
host is used. The Copy Media procedure can be made from a jukebox that is connected remotely. Also, the Compare procedure
is supported using a jukebox that is connected remotely. The remote Copy Media and Compare options are available only if
the Remote Copy has been licensed.

-v: Verbose. Prints a progress report on the user’s terminal.

-c copy_number: This option allows the System Administrator to change the incremented number of the copy_number to a
different value; which will allow multiple copies to be made of the original media and all copies may co-exist in the jukebox.
Without this option the copy_number on destination media is equal to the copy_number of the original media plus one.

The vlcopy command belongs to the list of the commands that can be delayed and placed under the VL scheduler control. The
options -j, -d and -C are related to the delayed start option and will be explained on the Delayed Jobs under VL Scheduler
Control section in this chapter.

The vlcmp command is used to compare the original media with the duplicate media once the Copy Media procedure has been
completed.

vlcmp [-H host_name] [-v] [-j {delayed_job_name | "default"}] [-d {[mmdd]HHMM|[cc]yymmddHHMM}]

source_jukebox:shelf_number destination_jukebox:shelf_number

The vlcmp command includes the following different options:

-H host_name
Specifies the name of the host where the source_jukebox and destination_jukebox are connected. Without this option, the local
host is used.

-v: Verbose. Prints a progress report on the user’s terminal.

The vlcmp command belongs to the list of the commands that can be delayed and placed under the VL scheduler control. The
options -j and -d are related to the delayed start option and will be explained on the Delayed Jobs under VL Scheduler
Control section on this chapter.

Note: QStar recommends reviewing the explanation for the vlcopy and vlcmp commands in Chapter 9 - Command Reference of
this manual, while reading this section.

1) To create a duplicate copy of the media in shelf 1 (side a and b) with the media in shelf 8, enter:

#>vlcopy jb:1 jb:8

Note: If the destination shelf is omitted on the command line, the QStar Software will automatically use the first available media
present in jukebox with the same capacity and block size as destination media.

Page 63 of 100
2) To display the jukebox shelf information during the Copy Media procedure for a jukebox with a device name jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
-----------------------------------------------------------------------------
1a: sdf 2.4 GB Rewritable Seq=0 SetId=807aeea2.34ba1fc5
1b: sdf 2.4 GB Rewritable Seq=1 SetId=807aeea2.34ba1fc5
2a: sdf 2.4 GB Rewritable Seq=2 SetId=807aeea2.34ba1fc5
2b: sdf 2.4 GB Rewritable Seq=3 SetId=807aeea2.34ba1fc5
3a: sdf 2.4 GB Rewritable Seq=4 SetId=807aeea2.34ba1fc5
3b: sdf 2.4 GB Rewritable Seq=5 SetId=807aeea2.34ba1fc5
4a: erased 2.4 GB Rewritable
4b: erased 2.4 GB Rewritable
5a: erased 2.4 GB Rewritable
5b: erased 2.4 GB Rewritable
6a: erased 2.4 GB Rewritable
6b: erased 2.4 GB Rewritable
7: empty
8: copying

Note: The media in shelf 8 is being copied.

3) To display the jukebox shelf information after the Copy Media procedure has been completed for a jukebox with a device
name jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
------------------------------------------------------------------------------
1a: sdf 2.4 GB Rewritable Seq=0 SetId=807aeea2.34ba1fc5
1b: sdf 2.4 GB Rewritable Seq=1 SetId=807aeea2.34ba1fc5
2a: sdf 2.4 GB Rewritable Seq=2 SetId=807aeea2.34ba1fc5
2b: sdf 2.4 GB Rewritable Seq=3 SetId=807aeea2.34ba1fc5
3a: sdf 2.4 GB Rewritable Seq=4 SetId=807aeea2.34ba1fc5
3b: sdf 2.4 GB Rewritable Seq=5 SetId=807aeea2.34ba1fc5
4a: erased 2.4 GB Rewritable
4b: erased 2.4 GB Rewritable
5a: erased 2.4 GB Rewritable
5b: erased 2.4 GB Rewritable
6a: erased 2.4 GB Rewritable
6b: erased 2.4 GB Rewritable
7: empty
8a: sdf 2.4 GB Rewritable Seq=0.1 SetId=807aeea2.34ba1fc5
8b: sdf 2.4 GB Rewritable Seq=1.1 SetId=807aeea2.34ba1fc5

Note: The media in shelf 1 has been copied to shelf 8. The VL database displays identical SetId number on both media but a
different seq_no, the duplicate media has been incremented by 1.

Page 64 of 100
4) To display the jukebox shelf information by the set_name instead of the set_Id for a jukebox with a device name jb, enter:

#>vllsdev -n jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
-----------------------------------------------------------------------------
1a: sdf 2.4 GB Rewritable Seq=0 SetName=Test
1b: sdf 2.4 GB Rewritable Seq=1 SetName=Test
2a: sdf 2.4 GB Rewritable Seq=2 SetName=Test
2b: sdf 2.4 GB Rewritable Seq=3 SetName=Test
3a: sdf 2.4 GB Rewritable Seq=4 SetName=Test
3b: sdf 2.4 GB Rewritable Seq=5 SetName=Test
4a: erased 2.4 GB Rewritable
4b: erased 2.4 GB Rewritable
5a: erased 2.4 GB Rewritable
5b: erased 2.4 GB Rewritable
6a: erased 2.4 GB Rewritable
6b: erased 2.4 GB Rewritable
7: empty
8a: sdf 2.4 GB Rewritable Seq=0.1 SetId=807aeea2.34ba1fc5
8b: sdf 2.4 GB Rewritable Seq=1.1 SetId=807aeea2.34ba1fc5

Note: Shelf 8 displays the Set_Id instead of the SetName. This means, although this media has an identical Set_Id as another
media belonging to the Integral Volume set Test, it isn't considered part of the Integral Volume set because the original media is
still present in the VL set database.

5) To compare the media in shelf 1(side a and b) with the media in shelf 8, enter:

#>vlcmp jb:1 jb:8

Note: If the vlcmp command is run with the verbose option enabled it will print a progress report of the comparison on the
users terminal.

Note1: Once the vlcmp command has been completed it will generate in the /opt/QStar/log directory a report file (i.e.
vlcmp_JB_1-JB_8) that will display the results of the comparison.

Below is an example of the contents of the report file:

Vlcmp report Date October 19 2001 17:07:19

JB0:1 sdf, Side capacity: blocksize 2048, 1263472 blocks
JB0:8 sdf, Side capacity: blocksize 2048, 1263472 blocks
Block size for compare 2048
Blocks to compare 1263472
JB0:8a JB0:1a are equal.
JB0:8b JB0:1b are equal.
Vlcmp completed at 18:13:49

6) To export the media in shelf 8, enter:

#>vlexport jb 8

Page 65 of 100
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 with the vladdtoset command.

Note: Substitute the original media with the duplicate media only if the vlcmp command reports that both side a and b are
identical.

1) To display the set information for the Integral Volume set named Test, enter:

#>vllsset -v Test

Test
Use_media=disk,writable Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
SetId=687077ff.3b535493
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
2: Online=jb:2 Sequence_numbers=2,3
4: Online=jb:3 Sequence_numbers=4,5

Note: The media in shelf 1 is online and belongs to the Integral Volume set Test with Sequence_numbers = 0,1.

2) To export the media in shelf 1, enter:

#>vlexport jb 1

3) To display the set information for the Integral Volume set named Test, enter:

#>vllsset -v Test

Test
Use_media=disk,writable Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
SetId=687077ff.3b535493
Cache: Cache_root=/export/home/cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Mounted at /mnt
0: Offline=Test_0 Sequence_numbers=0,1
2: Online=jb:2 Sequence_numbers=2,3
4: Online=jb:3 Sequence_numbers=4,5

Note: The media in shelf 1 is now set offline.

Page 66 of 100
4) To import the duplicate media in shelf 1, enter:

#>vlimport jb 1

5) To add the duplicate media in shelf 1 to the Integral Volume set named Test, enter:

#>vladdtoset Test jb 1

6) To display the set information after the duplicate media has been added to the Integral Volume set named Test, enter:

#>vllsset -v Test

Test
Use_media=disk,writable Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
SetId=687077ff.3b535493
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 Offloc=Test_0
2: Online=jb:2 Sequence_numbers=2,3
4: Online=jb:3 Sequence_numbers=4,5

Note: The media in shelf 1 is now set online.

7) To display the jukebox shelf information by the set_name instead of the set_Id for a jukebox with a device name jb, enter:

#>vllsdev -n jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
-----------------------------------------------------------------------------
1a: sdf 2.4 GB Rewritable Seq=0.1 SetName=Test
1b: sdf 2.4 GB Rewritable Seq=1.1 SetName=Test
2a: sdf 2.4 GB Rewritable Seq=2 SetName=Test
2b: sdf 2.4 GB Rewritable Seq=3 SetName=Test
3a: sdf 2.4 GB Rewritable Seq=4 SetName=Test
3b: sdf 2.4 GB Rewritable Seq=5 SetName=Test
4a: erased 2.4 GB Rewritable
4b: erased 2.4 GB Rewritable
5a: erased 2.4 GB Rewritable
5b: erased 2.4 GB Rewritable
6a: erased 2.4 GB Rewritable
6b: erased 2.4 GB Rewritable
7: empty
8: empty

Note: The jukebox shelf information displays that the duplicate media now belongs to the Integral Volume set Test.

Page 67 of 100
Automated Copy Media Under VL Control
The Automated Copy Media 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 Automated Copy Media 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 (jukebox), without introducing an error condition using
duplicate media or locking the set database when the vlrefresh command is used. This means that after the Automated Copy
Media process is completed the VL database will be automatically updated and the media can be left in the jukebox or exported
and stored in a safe location until it is needed.

The Automated Copy Media procedure can be done for Full Media (full option) or Incremental (cron_like_schedule option)
and is configured during the creation of the Integral Volume set using the -b flag with the vlcrset command and can also be
activated or deactivated, after the creation of the Integral Volume set, using the vleditset command.

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 SDF, UDF 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 Copy Media” section above.

The Automatic Incremental Copy Media can be scheduled to run Incrementally at a pre-determined time. This means that if
more data is written after the Copy Media has been run; running the Copy Media subsequently will write the changes to the
destination media. The Automatic Incremental Copy Media procedure is only supported for Optical and Tape media with the
SDF file system. For this procedure to work correctly, the destination media MUST be in the jukebox at the scheduled time, if it
is not a new media will be initialized and a new copy made, if no backup media is located in the jukebox at the scheduled time,
the Incremental Copy Media will start to copy all media in the set from the beginning. For this reason, it is important the
current destination media is left in the jukebox, once a new destination media is started, all previous destination media can be
removed from the jukebox. Only one destination media is supported for the Incremental Copy Media, alternating between
two or more destination media is not supported as each media will not be complete and cannot be used as a direct
replacement.

The UDF file system supports a Manual Incremental Copy Media only for WORM (MO/UDO/PDD/CD/DVD-R/BD-RS)
media using the vlcopy command.

It may be required to configure the automated Copy Media for full media procedure to be added to the Delayed Jobs under VL
scheduler control. The parameters are set in the /opt/QStar/vl/files/conf file, to enable COPY Delayed Start within a certain
time period, the Copy Media will then be deferred until this time. This would be the preferred option for a jukebox with less
than 4 drives, or to simply move the automated Copy Media to a time period when the jukebox is under less load. See the
“Displaying and Setting the Delayed VL Configuration Copy Media Properties” later in this chapter to configure this
option. With the incremental copy mode, the scheduling it set in a cron_like_schedule, so the COPY Delayed Start should be
left at default.

Note: QStar recommends reviewing the explanation for the vlcrset and vleditset commands in Chapter 9 - Command Reference
of this manual, while reading this section.

Note1: Automated Copy Media with the UDF spanning Interchange Level is only supported if the Close_Full_Volume=yes
option enabled.

Page 68 of 100
1) To create an Integral Volume set named Test with the SDF file system and the Automated Copy Media of full media
procedure enabled, enter:

#>vlcrset -T sdf –b full Test

2) To display the Integral Volume set information for the Integral Volume set named Test, enter:

#>vllsset –v Test
Test
Use_media=disk,writable Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=of full media
Set_type=sdf (standard data format)
SetId=b29ea11f.3ee0bb86
No cache
0: Online=jb:3 Sequence_numbers=0,1

Note: The vllsset output displays the Make_copy option is set to of full media (Automated Copy Media of full media enabled).

QStar recommends when using the Automatic Copy Media of full media procedure, that the jukebox 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 copy media process and one
drive for the destination media of the copy media process. Alternately, configure the VL scheduler to process the
Automatic Copy Media of full media procedure outside of normal working hours.

1) To create an Integral Volume set named Test with the SDF file system and the incremental Automated Copy Media
procedure to take place each day at 22:00, enter:

#>vlcrset –T sdf –b “0 22 * * *” Test

2) To display the Integral Volume set information for the Integral Volume set named Test, enter:

#>vllsset –v Test
Test
Use_media=disk,writable Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=incremental (0 22 * * *)
Set_type=sdf (standard data format)
SetId=b29ea11f.3ee0bb86
No cache
0: Online=jb:3 Sequence_numbers=0,1

Note: The vllsset output displays the Make_copy is set to incremental and the scheduled time is displayed in the brackets in
cron format.

3) To display the delayed job information for the Incremental Automated Copy Media, enter:

#>vlqlist Test
1 2003/06/09_11:42 VLINCRCOPY Test IncrCopy Waiting For Time 0:

4) To modify the time for the Incremental Automated Copy Media, use the vleditset command, for example to change the time
to 23:00 daily, enter:

#>vleditset -b "0 23 * * *" Test

Page 69 of 100
1) To create an Integral Volume set named Test with the BD-RS media, the UDF file system as spanning Interchange Level,
packet writing and the Automatic Full Media Copy Media options enabled, enter:

#>vlcrset -T udf -v s –P 1 –B 1 –b full -u bd-rs Test

2) To display the Integral Volume set information for the Integral Volume set named Test, enter:

#>vllsset –v Test
Test
Use_media= bd,worm,rdonly Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=of full media
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=q_a30a36f78
UDF_revision=150 Interchange_level=spanning
Packet_writing_init=yes Verify_write=no
Close_full_volume=yes File_spanning=yes Use_image_backup=yes
No cache
0: Online=jb:1 Span_number=1

Note: The vllsset output displays the Make_copy option is set to of full media (Automated Copy Media of full media enabled).

Page 70 of 100
VL CONFIGURATION PROPERTIES FILE
QStar creates a special file called “conf” under the /opt/QStar/vl/files directory. The conf file keeps all the configuration
information used by the QStar Software on the Volume Librarian (VL) database and by the QStar Commands that can be run
as delayed jobs.

In the conf file are available the following configuration options:

# VL Configuration File

RECORD Images Dir Path = "/opt/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"
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 = "No"
Exportfs Root Dir = "/opt/QStar/fsi/mnt"
# 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"
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"

This section will display only the generic VL configuration information used by QStar Software, leaving the VL
configuration information relating to delayed jobs until the next section.

Page 71 of 100
Displaying and Setting the General VL Configuration
Properties
Keep Done Records = "7"

Number of latest records kept in the delayed jobs queue list. The default number is 7; the System Administrator can change this
by editing the /opt/QStar/vl/files/conf file and typing the new value.

Displaying and Setting the VL Configuration Threshold

Blank/Erased Media Properties
This option allows the System Administrator to send (receive) an E-mail notification when a set number of Erased or Blank
media are left in the jukebox.

Blank Media Threshold = "0"

Erase Media Threshold = "0"
Monitor Blank/Erase Mail Address = ""

By default, this option is disabled. For example if the threshold of the Blank/Erase media is “3” the System Administrator can
set to receive an E-mail notification when this level has been reached or passed by editing the /opt/QStar/vl/files/conf file and
typing the following value:

Blank Media Threshold = "3"

Erase Media Threshold = "3"
Monitor Blank/Erase Mail Address = "[email protected]"

Displaying and Setting the VL Configuration for Offline Media

Request Properties
This option sets whether access to the Integral Volume set is suspended, or not by an error until an offline media request has
been satisfied.

Return Error on Access to Offline Media = "No"

By default, the request will wait until the offline request is satisfied by importing the media or canceled using the vlconsole
command. The System Administrator can immediately receive an error by typing the following value:

Return Error on Access to Offline Media = "Yes"

Displaying and Setting the VL Configuration for the Export

Root Directory Location
This option sets the location of the export root directory that will be used by QStar Software as a mount point for NFS mounting
of a QStar Integral Volume set from a client machine on a Linux and HP-UX Operating System.

Exportfs Root Dir = "/opt/QStar/fsi/mnt"

Page 72 of 100
By default, the export root directory is set as /opt/QStar/fsi/mnt. The mount point name can be changed as required by the
System Administrator, who must be sure that the specified root directory location is created. A sub directory will appear in this
directory named as the Integral Volume set for every Integral Volume set mounted.
This mount point can be automatically or manually exported in the “/etc/exports” file. Once the Integral Volume set is mounted
on the local server, depending of the Operating System settings the directory can be automatically exported by QStar Software
for the local server only.

Displaying and Setting the VL Configuration for the Remote

Administration Properties
These options are related to the Remote Administration of the QStar Software. The System Administrator can remotely run all
the QStar commands by including the “–H” flag with the command. In addition is possible to use the admin.exe GUI program
from Windows. For more information, please refer to Chapter 9 - Command Reference in this manual.

# Remote Administration - {Prohibited | Allowed | Allowed Hosts}

Remote Administration = "Prohibited"
Remote Administration Allowed Hosts = ""

By default, the Remote Administration is Prohibited.

Select Allowed or Allowed Hosts to enable the Remote Administration.

Allowed Hosts: Hosts allowed the use of Remote Administration

Note: Every Host must be comma separated.

Example:

# Remote Administration - {Prohibited | Allowed | Allowed Hosts}

Remote Administration = "Allowed Hosts"
Remote Administration Allowed Hosts = "mars, pluto, venus"

This will allow the systems mars, pluto and venus to remotely administer the QStar Software.

Displaying and Setting the VL Configuration for the Big Space

Root Directory Properties
Big Space Root Dir = ""

By default, the big space root directory is not defined. This directory is used to store the backup images created with 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 be sure that the specified root directory
location has been created.

Page 73 of 100
Displaying and Setting the VL Configuration for the Minimum
File System Space Available
Minimum Filesystem Space Available = "0"

The SDF or UDF Spanning file system, 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 (Map Network 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

The conf file keeps all the port configuration information used by the QStar Software servers. If necessary the System
Administrator can change the port number used by QStar Software in the case of a conflict with other applications, once the port
is changed the QStar servers must be stopped and restarted.

FSI NFS Port = "5005"

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"

Page 74 of 100
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 at off peak times. The VL scheduler can be used to run batch or single media erases as well as Copy Media 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.

Displaying the Delayed Jobs under VL Scheduler Control

The /opt/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. The System Administrator can use the delayed queue commands option to
manage and monitor the delayed commands in the delayed jobs queue list by using the vlqlist command. The options available
in the conf file are represented with a key word that identifies the delayed command that can be under the VL scheduler's
control.

The key words are as follows:

RECORD: Option related to the Recording procedure.

COPY: Option related to the Copy Disk procedure.
CMP: Option related to the Compare Procedure, which follows the Copy Disk procedure.
REUSE: Option related to the Compaction procedure.
ERASE: Option related to the Erase procedure.
ARC: Option related to the Archiving procedure.

Below the contents of the conf file relating to the Delayed Jobs commands:
# VL Configuration File

RECORD Images Dir Path = "/opt/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"
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"
REGRESS Delayed Start = "0:0 0:0"
ARC Delayed Start = "0:0 0:0"

Page 75 of 100
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.

RECORD Images Dir Path = "/opt/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"

By default, Direct write is Prohibited and Delayed write is always allowed with the default delayed write options below:

A) Images Dir Path: /opt/QStar/vl/files/cd_images

The Images Directory on the server where the temporary image files that will be recorded to the CD/DVD-R media will be
stored.

B) Image Max Dir Size (Mb): 650 Mb

Maximum Size of the Images Directory.

C) Direct: “Prohibited”

Type of recording procedure allowed, by default Direct write is prohibited.

D) Allowed Hosts: Hosts allowed doing the Direct write procedure.

Select Allowed or Allowed Hosts enables the Direct write procedure.

Note: Every Host must be comma separated.

E) Delayed Start: Start Time and Stop Time when the VL scheduler processes 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.

F) Max Parallel Recording: The Number of parallel recordings defines the number of images that can be recorded at the same
time; the value entered defines the number of drives that can be used simultaneously for recording. A “0”value ensures that
all cd/dvd-r drives available will be used.

Note: The VL Configuration option for the recording procedure and related commands with a full explanation regarding the
QStar CD/DVD Master Software can be found in the MANAGING QSTAR CD/DVD MASTER PRODUCT WITH ISO 9660
AND UDF FILE SYSTEMS section in Chapter 7 - Media Configuration of this manual.

The System Administrator can change any of the default parameters by editing the /opt/QStar/vl/files/conf file and typing the
new value.

Page 76 of 100
In the example, default Delayed write options are set as follows:

RECORD Images Dir Path = "/export/home/cd_images"

RECORD Images Max Size Mb = "2000"
RECORD Delayed Start = "23:30 06:30"
RECORD Max Parallel Recording = "2"

To create the directory where the images will be temporarily transferred and kept until the delayed jobs are completely
processed, enter:

#>mkdir /export/home/cd_images

Note: Ensure the hard disk partition where the Images Directory was created has sufficient space for the required images.

Note1: There may be a requirement for the users of the QStar CD/DVD Master Software to transfer the image to the cd_images
directory from a client machine. To allow the users to access the Images Directory, the correct permissions must be applied to
the directory.

Starting the Delayed Recording Procedure

The vlrecord command is used to record an ISO/UDF image to a CD/DVD-R media. The CD/DVD-R media is specified by the
device_name:shelf_number argument. If “any” option is specified instead of a shelf number then the first available blank
CD/DVD-R in the storage device will be used. The image location and name is specified by the image_path argument.

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]

The options available with the vlrecord command are described as follows:

-H host_name
Specifies the name of the host where the device is connected. Without this option, the local host is used.

-v Verbose output.

-x speed_X
Specifies the recording speed at which all CD/DVDs will be recorded. Without this option the recording speed is selected
automatically based on the memory buffer filling time. The options available are any number below the maximum write speed of
the drive (i.e. 2x =2 3x = 3 4x =4), or Max.
The selection of “Auto” as the recording speed ensures that the server will automatically detect the writing speed. With a buffer
on the server, data is transferred from the client machine to the buffer first and then from the buffer to the drive. The server
waits until the buffer is full before it starts to write. It calculates the speed of transfer for the first 4MB (buffer size) of data and
sets the appropriate write speed for the drive. The auto speed selection of the software may not always be accurate as the server
assumes that all transfers will be made at the same speed calculated for the first 4MB.

If the recording procedure returns an error, the speed is not correct; a write speed test must then be carried out. This procedure is
described in the Burn Test Procedure Before Starting the Write Operation section of this manual, QStar recommends
reading the section before starting the recording procedure to determine the correct write speed for your drives.

-b buffer_Mb
Specifies memory buffer size used for recording. The default value is 4 Mb.

Page 77 of 100
-t
The Laser OFF test mode is used to test and verify the optimum write speed to be used with the CD/DVD-R drive. When the
Laser OFF test mode is specified, the Software and the 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
The Write OFF test mode is used to measure the data transfer rate. When the Write OFF test mode is specified, the Software
will send the data to the drive, but will not perform the write operation on the media.

Note: For more detailed information about the test procedure, please refer to “Burn Test Before Start Write Operation”
section of this manual.

-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).

-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 “RECORD
Delayed Start” field in the /opt/QStar/vl/files/conf file.

Note: The -d flag can only be used 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 date values are supplied as defaults.

-m mail_addr
Specifies the E-mail address to which confirmation is sent when the job has been completed. An E-mail notification can be sent
reporting the exit status information of the recording operation using the -m option and specifying the E-mail address of the
person who should receive the notification.

-n number_of_copies
Specifies the number of copies of the same ISO/UDF image that will be recorded to the CD/DVD-R media. Without this option
only one ISO/UDF image will be recorded. This option is only available with the Delayed write procedure in conjunction with
any option and will be ignored if is used with the Direct write procedure.

-p
Sets the media type for the recording session. If the media type is omitted from the syntax of the command the first
available media in the jukebox, starting from the shelf with the lowest number, will automatically be used. If the
jukebox contains different types of media, (i.e. cd-r, dvd-r, dvd-rw, cd-rw, dvd-ram) the software will select the first
available media with a capacity that is equal to or larger than the ISO/UDF image, starting from the shelf with lowest
number.

Page 78 of 100
-V
Specifies verification mode. The vlrecord command reads recorded data back and compares with the source image.

Note: The recording is a long procedure, QStar suggests using the -v option to track the progress of the recording.

If the Delayed write procedure is used with an existing ISO/UDF image, the image is first transferred to the Images Directory
specified in the RECORD Images Dir Path entry of the conf VL Configuration file. Then in accordance with the RECORD
Delayed Start Time settings also specified in the conf VL Configuration file, the image will be recorded to the CD/DVD-R
media. When the record procedure has been completed the existing ISO/UDF image will not be removed from the server hard
disk, however, the transferred image will be removed from the Images Directory.

To select the Delayed write procedure the System Administrator will need to use the -j delayed_job_name option and assign a
name to the job using the vlrecord command. The job name must be a unique name, if the same job name is already present in
the delayed jobs queue list then the job will be denied and the following message will be returned to the vlrecord command:

vlrecord: QStar_Unix_Release: Can't add to VL-queue: Record already exists

By default the recording Start Time will follow the setting inserted in the RECORD Delayed Start Time setting specified in
the conf VL Configuration file. The System Administrator can change the recording Start Time specifying the date and time
the jobs should be executed on the delayed jobs list using the -d [mmdd]HHMM | [cc]yymmddHHMM option using the
vlrecord command.

Note: If the Delayed write procedure is interrupted, the interruption will cancel the delayed job request and the partial image
that has been transferred will be removed from the Images Directory.

Examples of Delayed Write Procedure Using the Any Shelf Option

Using the Any option on the vlrecord command, the target shelf will be chosen by the QStar Software.
In the examples, the QStar_Release is the name assigned to the delayed_job_name option.

1) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb
using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -j QStar_Release jb:any /home/QStar_Software_Unix.iso

Note: In the example, the -s set_name option is used to add the new CD/DVD-ROM created to the Integral Volume set Test. The
new media will then be mounted immediately after the recording has been completed and the data will be available online.

2) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb
using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -m [email protected] -j QStar_Release jb:any /home/QStar_Software

_Unix.iso

Note: In the example the -m mail_addr option is used to send an E-mail notification reporting the exit status information of the
delayed recording operation.

3) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb
using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -m [email protected] -j QStar_Release jb:any /home/QStar_

Software_Unix.iso

Note: In the example, both -s set_name and -m mail_addr options are used.

Page 79 of 100
4) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb
using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -j QStar_Release -d 2330 jb:any /home/QStar_

Software_Unix.iso

Note: In the example, the -d option is used to set the Delayed Start Time to 23:30.

5) To record the /home/QStar_Software_Unix.iso image to the first available DVD-R media in the jukebox identified as jb
using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -V –p dvd-r -j QStar_Release jb:any /home/QStar_

Software_Unix.iso

Note: In the example, the-s set_name, the -V verification and -p dvd-r options are used.

Examples of Delayed Write Procedure Using a Specified Shelf

In the examples, the QStar_Release is the name assigned to the delayed_job_name option.

1) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb using
the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -j QStar_Release jb:1a /home/QStar_Software_Unix.iso

Note: In the example, the -s set_name option is used to add the new CD/DVD-ROM created to the Integral Volume set Test. The
new media will then be mounted immediately after the recording has been completed and the data will be available online.

2) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb using
the Delayed write procedure, enter:

#>vlrecord -v -x 2x -m [email protected] -j QStar_Release jb:1a /home/QStar_Software

_Unix.iso

Note: In the example, the -m mail_addr option is used to send an E-mail notification reporting the exit status information of the
recording operation.

3) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb using
the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -m [email protected] -j QStar_Release jb:1a /home/QStar_

Software_Unix.iso

Note: In the example, both -s set_name and -m mail_addr options are used.

4) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb using
the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -j QStar_Release -d 2330 jb:1a /home/QStar_Software_

Unix.iso

Note: In the example, the -d option is used to set the Delayed Start Time to 23:30.

Page 80 of 100
Displaying and Setting the Delayed VL Configuration Copy
Media Properties
These options are related to the Delayed Copy Media procedure under the VL control. They can also be used to configure the
Automated Copy Media feature to take place in pre-determined hours. A full explanation regarding the Copy Media procedure
under the VL control can be found in The Copy and Compare Media Utilities section in this chapter. If
dst_dev_name:shelf_number is omitted the vlcopy command consults “COPY Jb Name”, “COPY Start Shelf Number”,
“COPY End Shelf Number” fields in the /opt/QStar/vl/files/conf file. If there are no such fields in /opt/QStar/vl/files/conf
file the vlcopy command examines the src_dev_name jukebox first and then all other jukeboxes.

COPY Jb Name = ""

COPY Start Shelf Number = "0"
COPY End Shelf Number = "0"
COPY Interchange Worm Rewritable Media = "No"
COPY Delayed Start = "0:0 0:0"
COPY Compare After Copy = "No"

By default the jukebox name and the range of destination shelves are not defined with the below default options:

A) Jb Name: “ ”
The name of the jukebox, which the QStar Software will use to examine for available media that can be used as destination
media in the vlcopy command.

B) Start Shelf Number: “0”

The first available shelf (media) usable as the destination media.

C) End Shelf Number: “0”

The last shelf (media) usable as the destination media.

D) Interchange Worm Rewritable Media: “No”

Allows using rewritable or WORM media as the destination media. By default, the QStar Software will use identical media
as the original for the destination media.

E) Delayed Start: Start Time and Stop Time when 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.

F) Compare After Copy: “No”

Allows automatically starting the Compare procedure once the Copy Media procedure has been completed.

The System Administrator can change any of the default parameters by editing the /opt/QStar/vl/files/conf file and typing the
new values.

In the example, default Delayed Copy Disk options are set as follows:

COPY Jb Name = "jb"

COPY Start Shelf Number = "80"
COPY End Shelf Number = "90"
COPY Interchange Worm Rewritable Media = " Yes "
COPY Delayed Start = "23:30 06:30"
COPY Compare After Copy = "Yes"

Note: In the example, the Automated Copy Media feature would only take place between the hours of 23:30 and 06:30 and
would only use rewritable media to copy to from shelves 80 to 90 inclusive. It would also Compare the media afterwards
(vlcmp).

Page 81 of 100
Starting the Delayed Copy Media Procedure
The vlcopy command is used to create a duplicate copy of a media.

vlcopy [-H host_name] [-v] [-c copy_number] [-C {yes|no} [-j{delayed_job_name | "default"}]
[-d {[mmdd]HHMM|[cc]yymmddHHMM}] src_dev_name:shelf_number dst_dev_name:shelf_number]

The vlcopy command creates a copy of the media (SDF, UDF or ISO 9660 file system). 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:shelf_number specifies the
jukebox and shelf number for the original media. The dst_dev_name:shelf_number specifies the jukebox and shelf number for
the copy.

Note: The original and the copy media must reside on the same host and if the media is double-sided both sides will be copied.

The options available with the vlcopy command are described as follows:

-H host_name
Specifies the name of the host where the source_jukebox and destination_jukebox are connected. Without this option, the local
host is used.

-v: Verbose. Prints a progress report on the user’s terminal.

-c copy_number: This option allows the System Administrator to change the incremented number of the copy_number to a
different value; which will allow multiple copies to be made of the original media and all copies may co-exist in the jukebox.
Without this option the copy_number on destination media is equal to the copy_number of the original media plus one.

-C yes|no
Compare 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 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).

-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 “COPY Delayed
Start” field in the /opt/QStar/vl/files/conf file.

Note: The -d flag can only be used 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 date values are supplied as defaults.

Page 82 of 100
Examples of the Delayed Copy Media Procedure Specifying the Destination Shelf

In the examples, the Make copy of shelf #3 is the name assigned to the delayed_job_name option and shelf 5 is the destination
media of the copy.

1) To create a duplicate copy of the media in shelf 3 (side a and b) with the media in shelf 5 using the Delayed Copy Media
procedure, enter:

#> vlcopy -j "Make copy of shelf #3" jb:3 jb:5

Note: The job will be executed according to the “COPY Delayed Start” field in the /opt/QStar/vl/files/conf file.

2) To create a duplicate copy of the media in shelf 3 (side a and b) with the media in shelf 5 using the Delayed Copy Media
procedure, enter:

#> vlcopy -j "Make copy of shelf #3" –d 1330 jb:3 jb:5

Note: In the example, the -d option is used to set the Delayed Start Time to 1:30 PM. The “COPY Delayed Start” field in the
/opt/QStar/vl/files/conf file makes no difference if -d is specified.

Examples of the Delayed Copy Media Procedure without Specifying the Destination
Shelf

In the examples, the Make copy of shelf #3 is the name assigned to the delayed_job_name option and the destination shelf is
not specified. Without specifying the destination shelf, the destination shelf will be chosen by the QStar Software, according to
the values set for COPY Start and End shelf in the /opt/QStar/vl/files/conf file.

1) To create a duplicate copy of the media in shelf 3 (side a and b) without specifing the destination shelf using the Delayed
Copy Media procedure, enter:

#> vlcopy -j "Make copy of shelf #3" jb:3

Note: The job will be executed according to the “COPY Delayed Start” field in the /opt/QStar/vl/files/conf file.

2) To create a duplicate copy of the media in shelf 3 (side a and b) with the media in shelf 5 using the Delayed Copy Media
procedure, enter:

#> vlcopy -j "Make copy of shelf #3" –d 1330 jb:3

Note: In the example, the -d option is used to set the Delayed Start Time to 1:30 PM. The “COPY Delayed Start” field in the
/opt/QStar/vl/files/conf file makes no difference if -d is specified.

Page 83 of 100
Displaying and Setting the Delayed VL Configuration
Compare Media Properties
This option is related to the Delayed Compare Media procedure that can be performed in order to verify a copy of the media is
made with the Copy Media under the VL control to ensure the vlcopy command has copied the media correctly. A full
explanation regarding the Copy Media procedure under the VL control can be found in The Copy and Compare Media
Utilities section in this chapter.

CMP Delayed Start = "0:0 0:0"

This is used by default with the options below:

A) Delayed Start: Start Time and Stop Time when the VL scheduler processes 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.

The System Administrator can change any of the default parameters by editing the /opt/QStar/vl/files/conf file and typing the
new values.

In the example, default Delayed Compare Media options are set as follows:

CMP Delayed Start = "23:30 06:30"

Starting the Delayed Compare Media Procedure

The vlcmp command is used to compare the original media with the duplicate media once the Copy Media under the VL control
procedure is completed to ensure that their contents are identical.

vlcmp [-H host_name][-v][-j {delayed_job_name | "default"}][-d {[mmdd]HHMM|[cc]yymmddHHMM}]

source_jukebox:shelf_number destination_jukebox:shelf_number

The options available with the vlcmp command are described as follows:

-H host_name
Specifies the name of the host where the source_jukebox and destination_jukebox are connected. Without this option, the local
host is used.

-v: Verbose. Prints a progress report on the user’s terminal.

-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).

-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 /opt/QStar/vl/files/conf file.

Note: The -d flag can only be used by the superuser.

Page 84 of 100
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 date values are supplied as defaults.

Examples of Delayed Compare Media Procedure

In the examples, the Compare 5 and 6 is the name assigned to the delayed_job_name option and the shelf 5 is the destination.

1) To compare all data on the media in jukebox#1 (jb1) in shelf 5 to the media in jukebox#2 (jb2) in shelf 6 using the Delayed
Compare Media procedure, enter:

#> vlcmp -j "Compare 5 and 6" jb1:5 jb2:6

Note: The job will be executed according to the “CMP Delayed Start” field in the /opt/QStar/vl/files/conf file.

2) To compare all data on the media in jukebox#1 (jb1) in shelf 5 to the media in jukebox#2 (jb2) in shelf 6 using the Delayed
Compare Media procedure, enter:

#> vlcmp -j "Compare 5 and 6" –d 1330 jb1:5 jb2:6

Note: In the example the -d option is used to set the Delayed Start Time to 1:30 PM. The “CMP Delayed Start” field in the
/opt/QStar/vl/files/conf file makes no difference if -d is specified.

Page 85 of 100
Displaying and Setting the Delayed VL Configuration Data
Compaction Properties
This option is related the Delayed Data Compaction procedure that relocates data, erases media and adds it to an Integral
Volume set. A full explanation regarding the Data Compaction procedure under the VL control can be found in the Data
Compaction Under VL Control section in this chapter.

REUSE Delayed Start = "0:0 0:0"

This is used by default with the options below:

A) Delayed Start: Start Time and Stop Time when 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.

The System Administrator can change any of the default parameters by editing the /opt/QStar/vl/files/conf file and typing the
new value.

In the example, default Delayed Compaction options are set as follows:

REUSE Delayed Start = "23:30 06:30"

Starting the Delayed Data Compaction Procedure

The vlreuse command is used to relocate data, erase the media and add it to an Integral Volume set.

vlreuse [-H host_name] [-r] [-j {delayed_job_name | "default"}] [-d {[mmdd]HHMM|[cc]yymmddHHMM}]

set_name in_set_number [in_set_number2..]

The vlreuse command relocates up-to-date data from a specified media ('in_set_number' in set 'set_name') to the 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 may be specified for the same command.

The options available with the vlreuse command are described as follows:

-H host_name
Specify the name of the host where the device is connected. Without this option, the local host is used.

-r
Specify relocation only mode. After successful completion of the command, the media may be exported from jukebox (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).

Page 86 of 100
-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 “REUSE Delayed
Start” field in the /opt/QStar/vl/files/conf file.

Note: The -d flag can only be used 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 date values are supplied as defaults.

Note: The command will fail if the specified set contains an SDF filesystem and is in a mounted state. It may also fail if there is
not enough space for the reallocated data.

Examples of Delayed Data Compaction Procedure

In the examples, the Reuse volume #1 is the name assigned to the delayed_job_name option.

1) To relocate data, erase the media with in_set_number 1 and add it to an Integral Volume set beta using the Delayed Data
Compaction procedure, enter:

#> vlreuse -j "Reuse volume #1" beta 1

Note: The job will be executed according to the “REUSE Delayed Start” field in the /opt/QStar/vl/files/conf file.

2) To relocate data, erase the media with in_set_number 1 and add it to an Integral Volume set beta using the Delayed Data
Compaction procedure, enter:

#> vlreuse -j "Reuse volume #1" -d 1330 beta 1

Note: In the example, the -d option is used to set the Delayed Start Time to 1:30 PM. The “REUSE Delayed Start” field in the
opts/QStar/vl/files/conf file makes no difference if -d is specified.

Page 87 of 100
Displaying and Setting the VL Configuration Delayed Erase
Media Properties
This option is related the Delayed Erase Media procedure.

ERASE Delayed Start = "0:0 0:0"

This is used by default with the options below:

A) Delayed Start: Start Time and Stop Time when the VL scheduler processes 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.

The System Administrator can change any of the default parameters by editing the /opt/QStar/vl/files/conf file and typing the
new value.

In the example, default Delayed Erase Media options are set as follows:

ERASE Delayed Start = "23:30 06:30"

Starting the Delayed Erase Procedure

The vlerase command is used to erase re-writable media.

vlerase [-v] [-fe] [-H host_name] [-j {delayed_job_name | "default"}] [-d {[mmdd]HHMM|[cc]yymmddHHMM}]
device_name shelf_number[{a|b}]

The vlerase command erases either an individual media, (in a standalone drive, or jukebox) or a group of media in the specified
range of shelves, (within a jukebox). The jukebox or standalone drive is specified by the device_name argument. A shelf range
can only be used for an immediate erase, only a single erase is allowed in the Delayed Erase, if multiple erases are required,
they must be entered as separate jobs. 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.

Note: If media belongs to an Integral Volume set, the erase process will be denied.

The options available with the vlerase command are described as follows:

-H host_name
Specify the name of the host where the device is connected. Without this option, the local host is used.

-v Verbose
Print 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 both UDF or
SDF file systems. The full erase procedure can be used to check faulty media, because all blocks will be erased.

Page 88 of 100
-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).

-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 “ERASE Delayed
Start” field in the /opt/QStar/vl/files/conf file.

Note: The -d flag can only be used 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 date values are supplied as defaults.

Examples of Delayed Erase Media Procedure

In the examples, the Erase shelf #2 is the name assigned to the delayed_job_name option.

1) To erase the media in shelf 2 using the Delayed Erase Media procedure, enter:

#> vlerase -j "Erase shelf #2" jb:2

Note: The job will be executed according to the “ERASE Delayed Start” field in the /opt/QStar/vl/files/conf file.

2) To erase the media in shelf 2 using the Delayed Erase Media procedure, enter:

#> vlerase -j "Erase shelf #2" -d 1330 jb:2

Note: In the example, the -d option is used to set the Delayed Start Time to 1:30 PM. The “ERASE Delayed Start” field in the
/opt/QStar/vl/files/conf file makes no difference if -d is specified.

Page 89 of 100
Displaying and Setting the VL Configuration Delayed
Archive Properties
This option is related to the Delayed Archive procedure.

ARC Delayed Start = “0:0 0:0”

This is used by default with the options below:

A) Delayed Start: Start Time and Stop Time when the VL scheduler processes 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.

The System Administrator can change any of the default parameters by editing the /opt/QStar/vl/files/conf file and typing the
new values.

In the example, default Delayed Archive options are set as follows:

ARC Delayed Start = "23:30 06:30"

Starting the Delayed Archive Procedure

The mmarc command is used to start, stop and schedule archiving of data for each Integral Volume set.

mmarc [-H host_name] {-l | -e | -a age | -s} [-w] [-j {delayed_job_name | "default"}] [-S cron_like_schedule]
{set_name | filename}

The mmarc command may be run manually to archive any primary data that resides in the cache, alternately it may be
scheduled via a delayed job, or a cron_like_schedule. Primary data in the cache can be secured to the archive by means of the
HPC (High Primary Capacity) setting, the mmarc command, or a combination of the two. By ensuring primary data is written
to the archive media on a regular basis, ensures the data is secure, even in the event of a catastrophic failure on the system.

Note: Each mounted Integral Volume set has its own archiving policy. QStar recomends they do not all take place at the same
time, if there are more mounted Integral Volume sets than available drives in the jukebox, this could lead to excessive media
swaps.

The options available with the mmarc command are described as follows:

-H host_name
Specify the name of the host where the device is connected. Without this option, the local host is used.

-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.

-w
Wait for archiving to stop. Without this option, the command returns immediately.

Page 90 of 100
-j {delayed_job_name | default}
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)

-d {[mmdd]HHMM | [cc]yymmddHHMM}
Specifies the date and time the job 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 ARC Delayed Start
field in the vl/files/conf file.

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.

-S cron_like_schedule
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 of Delayed Archive Procedure

In the examples, the Daily Archive #Test is the name assigned to the delayed_job_name option.

1) To archive all events for the Integral Volume set called Test using the Delayed Archive procedure, enter:

#> mmarc –e -j "Daily Archive #Test" Test

Note: The job will be executed according to the “ARC Delayed Start” field in the /opt/QStar/vl/files/conf file.

2) To archive until the low_primary_capacity is reached for the Integral Volume set called Test using the Delayed Archive
procedure, enter:

#> mmarc –l -j "Daily Archive #Test" –S “30 1 * * *” Test

Note: In the example the -S option is used to set the Delayed Start Time to 1:30 PM. The “ARC Delayed Start” field in the
/opt/QStar/vl/files/conf file makes no difference if -S is specified.

Page 91 of 100
Displaying the Delayed Jobs Status in the Delayed Jobs
Queue List
The vlqlist command is used to list all the information for the delayed jobs present in the delayed jobs queue list, which is
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 System Administrator using the vlqlist command can manage and monitor the delayed jobs in the
delayed jobs queue list.

vlqlist [-H host_name] [-j [a][d][c][m][r][e][g][A][i][o]] [-s [w][s][d][e]] [-l] [-h sender_hostname] [-u user_id]

The options available with the vlqlist command are described as follows:

-H host_name
Specifies the name of the host where the device is connected. Without this option, the local host is used.

-l
Output long format.

-j [d][c][m][r][e]
The –j flag allows specific job type filters to be used. Multiple filters may be used together on the same command line.

d - Display only vlrecord jobs.

c - Display only vlcopy jobs.
m - Display only vlcmp jobs.
r - Display only vlreuse jobs.
e - Display only vlerase jobs.
A - Display only mmarc jobs
i - Display only incremental copy jobs
o - Display only offline SDF mirror synchronization jobs

Note: By default all types of jobs are displayed.

-s [w][s][d][e]
The -s flag allows specific job state filters to be used. Multiple filters may be used together on the same command line.

w - Display all jobs waiting for execution.

s - Display all jobs that have started.
d - Display all jobs that have completed without error.
e - Display all jobs that have completed with error.

Note: By default, all types of job states are displayed.

-h sender_hostname
Display all records that came from the host specified by sender_hostname

-u user_id
Display all records that originated from the user specified by user_id.

Page 92 of 100
Displaying the Delayed Jobs Status for a Single Job
The delayed jobs listed in the vlqlist command output are displayed in the order they were added to the delayed jobs queue.
In this section there are examples of a delayed job for a recording procedure.

1) To display the delayed job status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/03/10_21:43 QStar_Release Record Waiting 0:natasha

In the example, the job with the name QStar_Release is present on the delayed jobs queue list and was registered in the list with
Job ID 1 and Registration Date 2002/03/10 at 21:43 and currently this job has a Status of Waiting.
The Delayed Start Date information is empty because the scheduling procedure follows the general settings made in the
RECORD Delayed Start Time setting specified in the conf VL Configuration file.

Note: The User ID "0" is the User root.

2) To display the delayed job status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/03/10_21:43 QStar_Release Record Started 0:natasha 2002/03/10_21:44

The Status of the job with Job ID 1 has changed to Started and the recording was started at 2002/03/10_21:44 Delayed Start
Date.

3) To display the delayed job status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/03/10_21:43 QStar_Release Record Done 0:natasha 2002/03/10_21:44 2002/03/10_21:50

The Status of the job with Job ID 1 has changed to Done and the recording has been completed without any errors at
2002/03/10_21:50 End Date.

Note: If the Status displays Error the recording procedure has failed to write the image on the media.

Page 93 of 100
Displaying the Delayed Jobs Status for Different Delayed Jobs
The delayed jobs listed in the vlqlist command output are displayed in the order they were added to the delayed jobs queue. If
different types of jukeboxes are connected to the same server, a combination of different delayed jobs can 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 at top of the delayed jobs queue list has the highest priority.

1) To display the delayed jobs status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/05/28_20:51 QStar_Release Record Waiting 0:natasha
2 2002/05/28_20:53 Erase shelf #2 Erase Waiting 0:
3 2002/05/28_20:54 Make copy of shelf #8 Copy Waiting 0:

In the example, the jobs with the name QStar_Release, Erase shelf #2, Make copy of shelf #8 are present in the delayed jobs
queue list. They were registered in the list respectively with Job ID 1, Job ID 2, Job ID 3 and with different Registration
Date. Currently these jobs have a Status of Waiting. The Delayed Start Date information is empty because the scheduling
procedure follows the general settings made respectively in the RECORD, ERASE, COPY Delayed Start Time settings
specified in the conf VL Configuration file

Note: The User ID "0" is the User root.

2) To display the delayed jobs status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/05/28_20:51 QStar_Release Record Started 0:natasha 2002/05/28_21:00
2 2002/05/28_20:53 Erase shelf #2 Erase Waiting 0:
3 2002/05/28_20:54 Make copy of shelf #8 Copy Waiting 0:

The Status of the job with Job ID 1 has changed to Started and the recording was started at 2002/05/28_21:00 Delayed Start
Date.

3) To display the delayed jobs status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/05/28_20:51 QStar_Release Record Started 0:natasha 2002/05/28_21:00
2 2002/05/28_20:53 Erase shelf #2 Erase Started 0: 2002/05/28_21:01
3 2002/05/28_20:54 Make copy of shelf #8 Copy Waiting 0:

The Status of the job with Job ID 2 has changed to Started and the erasing was started at 2002/05/28_21:01 Delayed Start
Date.

Page 94 of 100
4) To display the delayed jobs status, enter:

#>vlqlist
JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date
2 2002/05/28_20:53 Erase shelf #2 Erase Started 0: 2002/05/28_21:01
3 2002/05/28_20:54 Make copy of shelf #8 Copy Waiting 0:
1 2002/05/28_20:51 QStar_Release Record Done 0:natasha 2002/05/28_21:00 2002/05/28_21:07

The recording has been completed successfully, the Status of the job with Job ID 1 has changed to Done and the job details are
then moved to the bottom of the delayed jobs queue list.

5) To display the delayed jobs status, enter:

#>vlqlist
JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date
2 2002/05/28_20:53 Erase shelf #2 Erase Started 0: 2002/05/28_21:01
3 2002/05/28_20:54 Make copy of shelf #8 Copy Started 0: 2002/05/28_21:15
1 2002/05/28_20:51 QStar_Release Record Done 0:natasha 2002/05/28_21:00 2002/05/28_21:07

The Status of the job with Job ID 3 has changed to Started and the copying was started at 2002/05/10_21:15 Delayed Start
Date.

6) To display the delayed jobs status, enter:

#>vlqlist
JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date
3 2002/05/28_20:54 Make copy of shelf #8 Copy Started 0: 2002/05/28_21:15
1 2002/05/28_20:51 QStar_Release Record Done 0:natasha 2002/05/28_21:00 2002/05/28_21:07
2 2002/05/28_20:53 Erase shelf #2 Erase Done 0: 2002/05/28_21:01 2002/05/28_22:08

The erasing has been completed successfully, the Status of the job with Job ID 2 has changed to Done and the job details are
then moved to the bottom of the delayed jobs queue list.

7) To display the delayed jobs status, enter:

#>vlqlist
JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date
1 2002/05/28_20:51 QStar_Release Record Done 0:natasha 2002/05/28_21:00 2002/05/28_21:07
2 2002/05/28_20:53 Erase shelf #2 Erase Done 0: 2002/05/28_21:01 2002/05/28_22:08
3 2002/05/28_20:54 Make copy of shelf #8 Copy Done 0: 2002/05/28_21:15 2002/05/28_23:06

The copying has been completed successfully, the Status of the job with Job ID 3 has changed to Done and the job details are
then moved to the bottom of the delayed jobs queue list.

Page 95 of 100
If the System Administrator has changed the Delayed Start Time specifying the date and time the jobs should be executed in
the delayed jobs list using the -d [mmdd]HHMM | [cc]yymmddHHMM option on the delayed commands, this new recording
start time information will be displayed on the vlqlist output on the Delayed-Start-Date information.

1) To display the delayed jobs status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/05/28_20:51 QStar_Release Record Waiting 0:natasha 2002/05/28_23:30
2 2002/05/28_20:53 Erase shelf #2 Erase Waiting 0: 2002/05/28_23:30
3 2002/05/28_20:54 Make copy of shelf #8 Copy Waiting 0: 2002/05/28_23:30

Note: The Registration-Date reports the Date and Time when the delayed job was added to the delayed jobs queue list and the
Delayed-Start-Date shows the Date and Time when the job is to be processed.

Displaying the Delayed Jobs Status in Long Format

The vlqlist command used with the –l (Output on Long Format) option allows displaying detailed information for the delayed
jobs present in the delayed jobs queue list.

#>vlqlist –l

Record ID: 1
Job: Record
Job Status: Waiting
Job Name: QStar_Release
Sender Hostname: natasha
Sender UID: 0
Registration Date: 2002/05/28_20:51
Start Date:
End Date:
Error:
Delayed Start Date:
Notification Mail Address:
Test Write Mode: no test
Write Speed: 4
Buffer Size(Mb): default
Media profile: cd-r
Device Name: jb
Shelf Number: 1
Side: A
Image Size: 90052608 – 89Mb
Image Path: /opt/QStar/vl/files/cd_images/natasha.1022539813.img
Set Name:
Leave Open: No
Verify After Recording: No

Page 96 of 100
Record ID: 2
Job: Erase
Job Status: Waiting
Job Name: Erase shelf #2
Sender UID: 0
Registration Date: 2002/05/28_20:53
Start Date:
End Date:
Error:
Delayed Start Date:
Notification Mail Address:
Device Name: jb
Shelf Number: 2
Sides: 2
Fast Erase: No

Record ID: 3
Job: Copy
Job Status: Waiting
Job Name: Make copy of shelf #8
Sender UID: 0
Registration Date: 2002/05/28_20:54
Start Date:
End Date:
Error:
Delayed Start Date:
Notification Mail Address:
Source Device Name: jb
Source Shelf Number: 8
Destination Device Name: jb
Destination Shelf Number From: 6
Destination Shelf Number To: 6
Copy Number: 0
Compare After Copy: No

Page 97 of 100
Moving Delayed Jobs from the Delayed Jobs List
The vlqmove command is used to move the jobs in the delayed jobs queue list that is controlled by the QStar VL scheduler
process. The delayed jobs listed in the vlqlist command output are displayed in the order they were added to the delayed jobs
queue. 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. The System
Administrator using the vlqmove command can change the order the jobs will be processed.

vlqmove [-H host_name] job_id1 [after] job_id2

Note: By default, this command moves job_id1 ahead of job_id2.

The options available with the vlqmove command are described as follows:

-H host_name
Specifies the name of the host where the device is connected. Without this option, the local host is used.

[after]
Specifies that job_id1 should be placed after job_id2.

Example:

1) To display the delayed jobs status, enter:

#>vlqlist
JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date
1 2002/05/28_20:51 QStar_Release Record Waiting 0:natasha 2002/05/29_01:30
2 2002/05/28_20:53 Erase shelf #2 Erase Waiting 0: 2002/05/29_01:30
3 2002/05/28_20:54 Make copy of shelf #8 Copy Waiting 0: 2002/05/29_01:30

Note: In the example, the job with Job ID 1 will be the first to be started.

2) To change the priority order of the jobs 1 and 2, enter:

#>vlqmove 2 1

Note: In the example, the job with Job ID 2 is selected to move this job to the top of the list.

3) To display the delayed jobs status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

2 2002/05/28_20:53 Erase shelf #2 Erase Waiting 0: 2002/05/29_01:30
1 2002/05/28_20:51 QStar_Release Record Waiting 0:natasha 2002/05/29_01:30
3 2002/05/28_20:54 Make copy of shelf #8 Copy Waiting 0: 2002/05/29_01:30

Note: Now the job with Job ID 2 is at the top of the list and will be the first job that will be processed.

Page 98 of 100
Deleting Delayed Jobs from the Delayed Jobs List
The vlqremove command is used to remove a job in the delayed jobs queue list that is controlled by the QStar VL scheduler
process. This command can be used to clear completed, completed with error, and unwanted incomplete records.

vlqremove [-H host_name] job_id

The options available with the vlqremove command are described as follows:

-H host_name
Specifies the name of the host where the device is connected. Without this option, the local host is used.

Example:

1) To display the delayed jobs status, enter:

#>vlqlist
JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date
1 2002/05/28_20:51 QStar_Release Record Waiting 0:natasha 2002/05/29_01:30
2 2002/05/28_20:53 Erase shelf #2 Erase Waiting 0: 2002/05/29_01:30
3 2002/05/28_20:54 Make copy of shelf #8 Copy Waiting 0: 2002/05/29_01:30

2) To delete a job from the delayed jobs queue list, enter:

#>vlqremove 1

Note: In the example, the job with Job ID 1 is removed from the list.

3) To display the delayed jobs status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

2 2002/05/28_20:53 Erase shelf #2 Erase Waiting 0: 2002/05/29_01:30
3 2002/05/28_20:54 Make copy of shelf #8 Copy Waiting 0: 2002/05/29_01:30

Note: Once a job for the delayed recording procedure is removed from the list the job is canceled and the associated image file
in the Images Directory is removed.

Page 99 of 100
DISPLAYNG ERROR CONDITIONS FOR DELAYED JOBS
If an error occurred during a Delayed job, the error information will be displayed in the record regarding the job. Information on
the error encountered in the delayed jobs queue list can be displayed using the vlqlist command. The syslog file will report
additional information about the error encountered during the job procedure.

The vlqlist command used with the –l (Output on Long Format) option allows displaying detailed error information for the
delayed jobs present in the delayed jobs queue list.

#>vlqlist –l

Record ID: 2
Job: Record
Job Status: Error
Job Name: QStar Release
Sender Hostname: brian
Sender UID: 0
Registration Date: 2002/04/19_13:15
Start Date: 2002/04/19_13:29
End Date: 2002/04/19_13:30
Error: USCSICMD ioctl: try jb:6a 82 Mb: cdr_write: write process was interrupted:
SCSI cmd 0x2a (write): I/O error
Delayed Start Date:
Notification Mail Address: [email protected]
Test Write Mode: no test
Write Speed: 4
Buffer Size(Mb): default
Media profile: cd-r
Device Name: jb
Shelf Number: 6
Side: A
Image Size: 86372352 – 85Mb
Image Path: /opt/QStar/vl/files/cd_images/brian.1019214846.img
Set Name:
Leave Open: No
Verify After Recording: No

Note: In the example, an error occurred during the delayed recording procedure is displayed.

Page 100 of 100

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........................................................................................ 2

Migration Manager Terminology .............................................................................................. 2
Events............................................................................................................................................ 3
File Migration Attributes ............................................................................................................ 3
Migrator Manager Parameters for an Integral Volume Set................................................ 4
CREATING THE CACHE .................................................................................................................. 5
Non Stop Write Cache Option .................................................................................................. 5
Read Only Grace Period Cache Option ................................................................................... 6
Retention Period Cache Option ................................................................................................ 6
Write Once and Deny Rename Options.................................................................................. 6
Multiple Cache Area Mechanism .............................................................................................. 8
MODIFYING THE CACHE PARAMETERS ...................................................................................... 9
FILE MIGRATION ........................................................................................................................... 10
Archiving ..................................................................................................................................... 10
File Migration Modes................................................................................................................. 11
MANAGING THE CACHE ............................................................................................................... 12
Structure and Files in the Cache Database ......................................................................... 12
The Cache Files ......................................................................................................................... 12
MIGRATION MANAGER COMMANDS ......................................................................................... 14
MOUNTING AN INTEGRAL VOLUME SET .................................................................................. 15
CHECKING THE MOUNTED STATUS OF AN INTEGRAL VOLUME SET................................. 16
ERROR CONDITION DURING MOUNT OPERATIONS.............................................................. 17
SHARE AN INTEGRAL VOLUME SET FROM A SERVER MACHINE ........................................ 18
MOUNT AN INTEGRAL VOLUME SET FROM A CLIENT MACHINE......................................... 18
UNMOUNTING AN INTEGRAL VOLUME SET............................................................................. 20
DATED MOUNT OPTION ............................................................................................................... 21
ARCHIVING NOTIFICATION ........................................................................................................ 22
DISPLAYING AND MONITORING CACHE INFORMATION ...................................................... 23
Information Displayed for a SDF File System..................................................................... 23
Information Displayed for the ISO 9660 or UDF File System ......................................... 24
MANAGING THE CACHE PARAMETERS ..................................................................................... 27
ERROR HANDLING AND RECOVERY FOR ALL FILE SYSTEMS.............................................. 30
Error Condition while Processing a Delayed Event ............................................................ 30
Example of Error Condition in the Cache............................................................................. 30
POWER FAILURE, SYSTEM CRASH OR REBOOTING WITHOUT UNMOUNTING................ 31
Transaction Logging Cache..................................................................................................... 32

Page 1 of 32
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 or DVD jukeboxes and drives, Tape
jukeboxes 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. 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.
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.
Archived since mount Number of Primary pages archived after last mount.
Replicated since mount Number of Replicated pages after last mount.

Page 2 of 32
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: create, link, mkdir, remove, rename, rmdir, setattr (combines chmod, chown, truncate,
utime), symlink and write syscalls. Events that read information from the file system: lookup, readdir, readlink, and statfs. 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.
Umount Event
Generated by umount syscall.
Events from the Migrator Manager commands
Generated by the mmarc, mmchmod, mmparam, mmpurge, mmresume, mmsubtree 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 mmchmod command, and can be viewed using mmls
command.

Full File Migration Whenever a file is migrated, its entire contents are moved completely from one tier of
the hierarchy to the other.
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.

Page 3 of 32
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 vlcache and the
mmparam commands.

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.

Page 4 of 32
CREATING THE CACHE
The vlcache command is used to create a cache for an Integral Volume set. 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.

vlcache [-H host_name][-D0rn] [-e][-p{max_number_of_pages | xxMB | xxGB}]

[-l {low_primary_capacity | xxMB | xxGB | xx%}][-h {high_primary_capacity | xxMB | xxGB | xx%}][-s page_size]
[-c cache_root][-g rdonly_grace_period][-R retention_period][-w {0|1] [-x {0|1][-c cache_root] set_name

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.

The -r Readonly option allows mounting a file system in read only mode.

-p {max_number_of_pages | xxMB | xxGB}

Sets the maximum number of pages that can be used for caching data. This option defines the size of the cache. Example, by
default the page size is 64k, if 100 pages are assigned to the cache this means that the cache size will be 64k x 100=6.4MB. If
the nn is specified, this option is mandatory. The -p xxMB -p xxGB syntax is also supported.

-l low_primary_capacity
Number of pages used to control the stop point for 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 point for 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 -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.

-c cache_root
Specify the cache root directory.

The -s Page Size option 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 128KB. The 128KB can be used only with
AIT tape drive.

Non Stop Write Cache Option

The -e Stop on covered error option of the vlcache command, 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 jukebox. 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.

Page 5 of 32
Read Only Grace Period Cache Option
The QStar Software has a feature to allow data to be stored for a Grace Period before it is set to read only.

-g rdonly_grace_period
The Grace Period option of the vlcache command 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 period of 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, 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 requirement.

Retention Period Cache Option

-R retention_period
The Retention Period option of the vlcache command 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 to specify a period of years, days, hours, minutes and
seconds as a timeout prohibiting modification/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. 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, a file can be modified either
before the Grace Period expires or after the Retention Period expires. Both Grace Period and Retention Period start from the last
modification time. 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 requirement.

The retention period has the following format:

retention_period=<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}

Write Once and Deny Rename Options

-w {0|1} Write Once -x {0|1} Deny Rename
The Write Once feature provides a WORM file system, even with rewritable media, which is ideal for corporate data archiving
compliance requirement. With -w0 or by default, file system is not WORM. With -w1 option the Write Once option is enabled
and the file system is WORM. 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 and Retention Period
will be ignored if is used in conjunction with this option. With -x1 option the Deny Rename option is enabled. If it enabled with
the Write Once option, the renaming operation is prohibited.

Note: QStar recommends reviewing the explanation for the vlcache command in Chapter 9 - Command Reference of this
manual, while reading this section.

Page 6 of 32
Examples of creation a cache for an Integral Volume set:

1) To create a cache with 100MB on the /export/home/cache_Test cache_root directory for an Integral Volume set named Test,
enter:

#>vlcache –p 100MB –c /export/home/cache_Test Test

2) To create a cache with 100MB on the /export/home/cache_Test cache_root directory and the high_primary_capacity value
set to 80 pages for an Integral Volume set named Test, enter:

#>vlcache –p 100MB –c /export/home/cache_Test –h 80 Test

3) To create a cache with 100MB on the /export/home/cache_Test cache_root directory and the cache in read only mode for an
Integral Volume set named Test, enter:

#>vlcache –p 100MB -r –c /export/home/cache_Test Test

4) To create a cache with 100MB on the /export/home/cache_Test cache_root directory and enabling the write operation on the
cache even if a covered error occurs for an Integral Volume set named Test, enter:

#>vlcache –p 100MB -e –c /export/home/cache_Test Test

5) To create a cache with 100MB on the /export/home/cache_Test cache_root directory and the cache pages size set to 32
(default is 64K) for an Integral Volume set named Test, enter:

#>vlcache –p 100MB –s 32 –c /export/home/cache_Test Test

6) To create a cache with 100MB on the /export/home/cache_Test cache_root directory and the grace period value set to 20
minutes for an Integral Volume set named Test, enter:

#>vlcache –p 100MB –c /export/home/cache_Test –g 0h20m0s Test

Page 7 of 32
Multiple Cache Area Mechanism
Each Integral Volume set has is own cache that is specified during the Integral Volume set creation using the vlcache command.
The information of the cache location is saved into the VL set database and is displayed using the vllsset command. From the
vlcache command 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 the cache across different
cache locations.

Below is the description of cache area mechanism:

1) The cache areas file resides in /opt/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 by the vlcache command and is removed by the vldelset command. The user can list cache areas
before the set is mounted. With the "mountiv -n" command, 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 with the mmresume command.

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 on mmresume command.

Page 8 of 32
MODIFYING THE CACHE PARAMETERS
The vlcache command is also used to modify permanently the cache parameters for an Integral Volume set. If the cache was
already created and the set is mounted this change will take effect at the next mount. QStar suggests umounting the Integral
Volume set, change the cache options and then remount the Integral Volume set.

The mmparam command on the current mount point can be used to modify the cache parameters temporarily.
The modification of the parameters will be cleared once the integral volume is unmounted. At the next mount the default
parameters specified with the vlcache command and displayed with the vllsset command will be reused.

1) To increase the cache size from 100MB to 15GB for an Integral Volume named Test, enter:

#>vlcache –p 15GB Test

2) To change the high_primary_capacity value to 70 pages for an Integral Volume named Test, enter:

#>vlcache –h 70 Test

3) To change the low_primary_capacity value to 10 pages for an Integral Volume named Test, enter:

#>vlcache –l 10 Test

Note: After the cache is added to the Integral Volume set, the vllsset command will display an output similar to the following.

Cache: Cache_root=/export/home/cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Low_primary_capacity=10
High_primary_capacity=70

Page 9 of 32
FILE MIGRATION
Archiving
Archiving is the copying of primary data from the magnetic disk (cache) to the archival media.

The mmarc command is used to start and stop the archiving of the files from the cache to the archival media.

mmarc [-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 mmarc command in Chapter 9 - Command Reference of this
manual, while reading this section.

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.

• User Initiated Archiving - The System Administrator initiates archiving on a selected Integral Volume set. This
method allows archiving of critical files as soon as they are written.

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 the mmarc command
with the cron command. Once the mmarc command is inserted in the appropriate crontab file, the cron command starts a
process that executes the mmarc command on the specified dates and times.

QStar also supports 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 - 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.

• 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.

• User Initiated Stop Archiving - The System Administrator initiates the stop archiving on a selected Integral
Volume set. This method stops the archiving on selection.

The System Administrator sets the primary agetime and low primary capacity parameters based on Integral Volume set usage
characteristics.

Page 10 of 32
File Migration Modes
QStar’s migration manager allows migration to occur in two modes: data segment mode and full file mode.

In data segment mode, 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 mode, the migration manager always migrates the complete file as a single entity.

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.

Page 11 of 32
MANAGING THE CACHE
Once the Integral Volume set is created using the vlcrset command and the cache location is assigned using the vlcache
command, the Integral Volume set can be mounted using the mountiv command. This command can be run 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 root directory that was specified with the vlcache command, 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 the SDF and UDF file systems. 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_tree Holds directory layout information about the Integral Volume set. This is an
analog map of the directory tree of the covered file system.
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_event All delayed events are held in this file.
cfs_pte Holds Page Table Entries (PTEs), which describe the state of every page in the
cache.
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 virtually unlimited by creating
multiple page files (named cfs_pages_0, cfs_pages_1, etc), up to a maximum of
256.
cfs_acl This file is not used on v5.0 version but will be used on v5.1 and contains the
access control list for all files in MCFS.
cfs_crypto This file is not used on v5.0 version but will be used on v5.1 and contains
cryptographic information for regular files.
cfs_btree This file contains balanced trees used for searching directories and mapping file
pages to the page in the cfs_page file.
set_name Holds the name of the 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.

Page 12 of 32
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 a sdf
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

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 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 - 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.

Note: The cfs_page file is a static file, the size is represented in 2 GB cfs_page files, 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_*, udf_db and sdf_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.

Page 13 of 32
Note1: QStar recommends not doing a backup of the directory where the QStar Software is installed 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.

MIGRATION MANAGER COMMANDS

Command Description
mmarc Start and stop the archiving
mmchmod Change migration attributes of the specified files
mmdelay Print the delayed queue
mmls List the information of specified files
mmparam Set or print the cache parameters
mmresume Clear covered file system errors
mmpurge Free pages in the cache
mmsubtree Remove or add a sub tree in the cache

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

Page 14 of 32
MOUNTING AN INTEGRAL VOLUME SET
The mountiv command is used to mount an Integral Volume set on a specified mount_point directory.

mountiv [-H host_name] [-Inrf] set_name mount_point [-c cache_root -t {[mmdd]HHMM|[cc]yymmddHHMM}]

set_name mount_point

Note: QStar recommends reviewing the explanation for the mountiv command in Chapter 9 - Command Reference of this
manual, while reading this section.

1) To mount the Integral Volume set Test for the first time (cache root directory empty) on the /mnt directory, enter:

#>mountiv Test /mnt

Note: No flag is needed to build the cache files if the cache root directory is empty.

2) To mount the Integral Volume set Test with a clean cache on the /mnt directory, enter:
#>mountiv –n Test /mnt

Note: The “–n” flag will rebuild all existing cache files, ensure that all primary pages have been archived before using this
flag.

3) To mount the Integral Volume set Test with a new sdf_db or udf_db files on the /mnt directory, enter:

#>mountiv –I Test /mnt

4) To mount the Integral Volume set Test in read only mode on the /mnt directory, enter:

#>mountiv –r Test /mnt

Note: The Integral Volume set can be mounted in read only mode and with new sdf_db or udf_db files using the vlcrset or
vleditset commands. For more detailed information, please refer to Chapter 9 - Command Reference in this manual.

Note1: When using Tape media the number of Integral Volume sets that can be mounted at one time is limited by the
number of drives available in the jukebox.

Page 15 of 32
CHECKING THE MOUNTED STATUS OF AN INTEGRAL
VOLUME SET
The System Administrator can verify that the file system is correctly mounted using the UNIX df -k or mount commands.
The QStar Software also maintains the mount status information of the Integral Volume set in the VL database. This information
is displayed using vllsset command.

1) To display the mount status for the Integral Volume set named Test, enter:

#>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

Page 16 of 32
ERROR CONDITION DURING MOUNT OPERATIONS
The mountiv command can return with an error condition.

This section will explain what these errors mean and how to remedy them.

Error message example 1:

mountiv: host_name: , set Test: Migrator files invalid or belong to different set

This error means that the sdf_db files are corrupted or are already in use with another Integral Volume set. Check to see if the
cache root directory specified for this Integral Volume set is the same as another Integral Volume set. If it is the same, change it
or remove all files inside the cache root directory and run the mountiv command.

Error message example 2:

mountiv: /export/home/Test: host_name: , set Test: prepare cache: Cache files belong to different file system

This error means that the “cfs_*” files are already in use with another Integral Volume set (set with cache). Check to see if the
cache root directory specified for this Integral Volume set is the same as another Integral Volume set. If it is the same, change it
or remove all files inside the cache root directory and run the mountiv command again with the option, “-n”.

Error message example 3:

mountiv: host_name: , set Test: Busy directory or mount point

This error means that the mount point specified for this Integral Volume set is already in use by another Integral Volume set or
file system. Change the mount point directory.

Error message example 4:

mountiv: /export/home/Test: clean_cache required: Cache files may need to be recreated. Use -f flag to mount with
existing cache

This error means that the “cfs_*” files may already be in use by another or old Integral Volume set. Check to see if the cache
root directory specified for this Integral Volume set is the same as another Integral Volume set. If it is the same, change it or
remove all files inside the cache root directory or run the mountiv -n command to clean the cache. If the cache root directory
belonged to an Integral Volume set that was recreated, run the mountiv -f command to mount using the existing cache files.

Error message example 5:

mountiv: /export/home/Test: Migrator files may need to be recreated. Use -f flag to mount with existing migrator
database

This error means that the Integral Volume set information has been recreated and the sdf_db files have been used with a
different or old Integral Volume set. If the Integral Volume set is the same as the old one and only the Integral Volume set
information has changed, run the mountiv -f command to mount using the existing migrator database. If the Integral Volume set
is not the same, remove all files inside the cache root directory or run the mountiv -n command to clean the cache.

Page 17 of 32
SHARE AN INTEGRAL VOLUME SET FROM A SERVER
MACHINE
Once the Integral Volume set is created and the file system is mounted, the System Administrator if required can share the file
system on the network.

A) Share from the server machine the Integral Volume set on Solaris and AIX platforms.

To share the file system use the UNIX specific share or exportfs commands.

share [ -F FSType ] [ -o specific_options ] [ -d description ] [ pathname ] (Solaris)

exportfs [-aiuv] [-o options] [directory] (AIX)

B) Share from the server machine the Integral Volume set on Linux and HP-UX platforms.

For these platforms by default, the file system is already shared, to change this option use the -U {local|share} option in vlcrset
or vleditset command. This option specifies whether an Integral Volume set can only be accessed from the local server or
shared on the network.

MOUNT AN INTEGRAL VOLUME SET FROM A CLIENT

MACHINE
Once the Integral Volume set is shared, the System Administrator if required can mount the file system from the network.

A) Mount from the client machine the Integral Volume set shared from Solaris and AIX platforms.

To mount the file system from a client machine the UNIX specific platform mount command is used.

mount host_name:/remote_mount_point /local_mount_point

B) Mount from the client machine the Integral Volume set shared from Linux and HP-UX platforms.

To mount the file system from a client machine the UNIX specific platform mount command is used specifying the port number
as 5005 and the QStar Export root directory.

QStar creates a special file called “conf” under the /opt/QStar/vl/files directory. The conf file keeps all the configuration
information used by the QStar Software.

Below is the field of the conf file regarding QStar Export Root directory:
# VL Configuration File
……………
Exportfs Root Dir = "/opt/QStar/fsi/mnt"
……………

In this field is displayed the default location of the export root directory that will be used by QStar Software as a mount point for
the nfs mounting of a QStar Integral Volume set from a client machine on a Linux and HP-UX Operating Systems.

Page 18 of 32
The mount point name can be changed as required by the System Administrator, who must be sure that the specified root
directory location is created. In this directory will appear a sub directory named as the Integral Volume set for every Integral
Volume set mounted. This mount point can be automatically or manually exported in the “/etc/exports” file.

Once the Integral Volume set is mounted on the local server, depending of the Operating System settings the directory can be
automatically exported by QStar Software only for of the local server only.

The check which file systems are exported, the UNIX exportfs command can be used.

Example:

#>exportfs
/opt/QStar/fsi/mnt/Test
server_1.qstar.com

Note: The Integral Volume set Test is automatically exported for local access only.

If no entrees are displayed by the exportfs command, the System Administrator can display which file systems are available for
remote mount and the correct mount point that should be used on the “/etc/ exportfs” file using the fsi_lsset command.

Example:
# >fsi_lsset
Set name Type Set Id Flags Port Cache root Exportfs
Test cd 1067868030 Ro 5005 /cache/Test /opt/QStar/fsi/mnt/Test

Finally edit the “/etc/exports” file to include the QStar Integral Volume set.

The following is an example from server called server_1, with Integral Volume set named Test:

Example 1:
# vi /etc/exports
/opt/QStar/fsi/mnt/Test
server_1.qstar.com

The following is an example from server called server_2, with Integral Volume set named Test:

Example 2:
# vi /etc/exports
/opt/QStar/fsi/mnt/Test
server_2.qstar.com(rw)

The following is an example from any server on the qstar.com domain, with Integral Volume set named Test:

Example 3:
# vi /etc/exports
/opt/QStar/fsi/mnt/Test
*.qstar.com(rw)

Note: In the above examples, either each individual client can be specified, or a wildcard (*) can be used for multiple clients.
See man pages for exports for available options.

Page 19 of 32
The file system can be exported running the following command:

#>exportfs -a
//exports all directories in “/etc/exports” file, check the man pages on exportfs for more options.

To mount the Integral volume set Test from the client machine using /mnt as local mount, enter:

mount -o port=5005 server_1:/opt/QStar/fsi/mnt/Test /mnt

Note: The new path created by QStar is the mount point "/opt/QStar/fsi/mnt/set_name" NOT the set_name or physical mount
point of the Integral Volume set.

UNMOUNTING AN INTEGRAL VOLUME SET

QStar highly recommends that the file system is unshared before the Integral Volume set is unmounted.

To unmount the Integral Volume set the umount or umountiv commands are used.

The QStar 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 the Integral Volume set are located on the
same host, umountiv closes the Integral Volume set (making the integral volume unavailable to all clients).

umountiv [-H host_name] [-f] {set_name | mount_point}

The UNIX umount command unmounts the Integral Volume set specifying with the argument of either the mount_point or the
set_name. The umount command is only available for the Solaris and AIX platforms.

umount { set_name | mount_point }

The main difference between umount and the umountiv commands are that the umountiv command does not require root
privileges to be run and any users that have been added to the priv.users file can run the umountiv. For more detailed
information, please refer to Chapter 3 - Installing and Configuring QStar Software in this manual.

A) Unmount the Integral Volume set on Solaris and AIX platforms.

1) To unmount the Integral Volume set Test on the /mnt directory, enter:

#>umount /mnt

2) To unmount the Integral Volume set Test on the /mnt directory, enter:

#>umount Test

3) To unmount the Integral Volume set Test on the /mnt directory, enter:

#>umountiv /mnt

4) To unmount the Integral Volume set Test on the /mnt directory, enter:

#>umountiv Test

Page 20 of 32
Note: The System Administrator may use either the umountiv or the umount command to unmount an Integral Volume set for
these platforms.

B) Unmount the Integral Volume set Test on Linux and HP-UX platforms.

1) To unmount the Integral Volume set Test on the /mnt directory, enter:

#>umountiv Test

2) To unmount the Integral Volume set Test on the /mnt directory, enter:

#>umountiv /mnt

Note: To ensure that the Integral Volume set will be completely unmounted, QStar does not recommend using the umount
command on these platforms. The umount command will unmount the Integral Volume set locally only but will not remove
access from the network because the Integral Volume set will remain Published. At this point the System Administrator may
unmount the Integral Volume set from the network also, by running the unmountiv command or may restore the Integral
Volume set locally by running the mountiv command.

DATED MOUNT 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 SDF 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.

The Integral Volume set can be mounted on different dates using the mountiv command.

mountiv [-H host_name] [-Inrf] set_name mount_point [-c cache_root -t {[mmdd]HHMM|[cc]yymmddHHMM}]

set_name mount_point

Note: Please refer to the mountiv command in Chapter 9 – Command Reference for more details.

The following options are used for the Dated Mount procedure.

-c cache_root

The -c option specifies where the temporary cache is located for the Dated Mount, for each required Dated Mount, a new cache
location will be required. Once the Dated Mount is no longer required, the System Administrator can delete the contents of this
directory if required.

-t {[mmdd]HHMM|[cc]yymmddHHMM}]

The -t option specifies the date and time for the Dated Mount, several Dated Mounts can be used simultaneously on different
dates and times. The Dated Mount can be specified in Year, Month, Day, Hours and Minutes.

1) To mount the Integral Volume set Test for a Dated Mount of 12:00 1st January 2002 on the /mnt directory and a cache root
of /temp_cache, enter:

#>mountiv –c /temp_cache –t 0201011200 Test /mnt

Page 21 of 32
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 /opt/QStar/log directory. Once this file is created all the archiving
start/stop information will be logged into the QStar /opt/QStar/log/syslog file.

Page 22 of 32
DISPLAYING AND MONITORING CACHE
INFORMATION
The mmparam command is used to display, modify and monitor cache information. To display the cache use the mmparam
command with no options, this will display the current status of the cache. To modify the cache use the mmparam command
with the flags and switches to alter the high_primary_capacity or the low_primary_capacity. To monitor the cache during
archiving use the mmparam command repeatedly to view the current state of the on going archive.

Using the mmparam command without any switches will display the following information.

mmparam {-c cache_root | [-H host_name] set_name | filename} |

mmparam [-l {low_primary_capacity | xxMB | xx%}] [-h {high_primary_capacity | xxMB | xx%}]
{[-H host_name] set_name | filename}

Note: QStar recommends reviewing the explanation for the mmparam command in Chapter 9 - Command Reference of this
manual, while reading this section.

Information Displayed for a SDF File System

To display the cache parameters for an Integral Volume set named Test, enter:

#>mmparam /mnt

Cache root: /export/home/cache_Test

Mount point: /mnt
Max number of pages: 100 6.2 MB
Low primary capacity: 0 pages 0 KB
High primary capacity: 80 pages 5.0 MB
Page size: 64 Kbytes
Present pages: 80 5.0 MB
Primary pages: 0 0 KB
Replicated pages: 0 0 KB
Archived pages: 80 5.0 MB
Keep in cache: 0 0 KB
Archived since mount: 1.5 KB
Replicated since mount: 0 KB
Files in cache: 29
Number of delayed events: 0
Read/write access: Read-write
Error condition: No
Stop on covered error: Yes
Archiving: Not started
Migrator: sdf
Medium drive type: ERASABLE
Writing to partition: jb:1a
Number of partitions: 1
Free space on current partition: 3.0 GB
Max.number of opened partitions: 8
Max. buffer size: 15488
Compression: Off

Note: On the Linux and HP-UX platforms instead of “Mount point” the “Share name” will be displayed.

Page 23 of 32
Information Displayed for the ISO 9660 or UDF File System
To display the cache parameters for an Integral Volume set named Test, enter:
#>mmparam /mnt

Cache root: /export/home/cache_Test

Mount point: /mnt
Max number of pages: 100 6.2 MB
Low primary capacity: 0 pages 0 KB
High primary capacity: 80 pages 5.0 MB
Page size: 64 Kbytes
Present pages: 90 5.6 MB
Primary pages: 0 0 KB
Replicated pages: 0 0 KB
Archived pages: 90 5.6 MB
Keep in cache: 0 0 KB
Archived since mount: 2.5 KB
Replicated since mount: 0 KB
Files in cache: 362
Number of delayed events: 0
Read/write access: Read-write
Error condition: No
Stop on covered error: Yes
Archiving: Not started
Migrator: udf
Last write on: /opt/QStar/dev/jb/rjb1a

Note: On the Linux and HP-UX platforms instead of “Mount point” the “Share name” will be displayed.

Page 24 of 32
The main parameters are described as follows:

General Parameter Description

Cache root: /export/home/cache_Test Displays the location of the cache root directory
Mount point: /mnt (Solaris,AIX) Mount point of the Integral Volume set
Share name: /mnt (HP-UX,LINUX)
Max number of pages: 100 6.2 MB Total number of cache pages allocated to the Integral
Volume set
Low primary capacity: 0 pages 0 KB Low primary Capacity value (the point archiving stops)
Default = 0 pages
High primary capacity: 80 pages 5.0 MB High primary capacity value (the point archiving will
begin automatically)
Default = 80 % of the total pages
Page size: 64 Kbytes Size of each page
Default = 64 Kbytes
Present pages: 0 0 MB Status of the pages in the cache
Primary pages: 0 0 KB
Replicated pages: 0 0 KB
Archived pages: 0 0 MB
Keep in cache: 0 0 KB Number of pages set with these specific attributes
Archive never: 0 0 KB
Archived since mount: 2.5 KB Number of pages archived or replicated since last mount
Replicated since mount: 0 KB
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 SDF and UDF
Default = Read-only ISO 9660
Mount state: Mounted Mount status of the Integral volume set
Error condition: No Error condition notification
Archiving: Not started Archiving status
Stop on covered error: Yes Status of the Write operation (Enabled/Disabled) after
covered error occurs.
Default = Yes
Migrator: sdf Type of migrator
udf

Page 25 of 32
Medium drive type: ERASABLE Type of current writing medium of the Integral
Volume set
For SDF only
Writing to partition:jb:1a (SDF) Device name of the current write surface
Last write on: /opt/QStar/dev/jb/rjb1a (UDF)
Number of partitions: 2 Total number of “partitions” (sides of double-sided media
or individual tapes) allocated to the sdf set
This may grow when the Volume Librarian adds new
volumes to the Integral Volume set
For SDF only
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 jukebox
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.
For SDF only
Compression: off This flag displays if compression is used on the tape
drive; for optical media it is Off
For SDF only

Page 26 of 32
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.

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.

A) The 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 mounted on /mnt, enter:

#>mmls -R /mnt
Directory -f-k /
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 mounted on /mnt, enter:

#>mmls -Rs /mnt

Directory -f-k /
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
Cnode_number=1272 Present=190 Primary=0
Ino=1135 Mode=100644 UID=0 GID=0 Nlink=1 Size=12420857
Regular Archived -f-k winapps-357-4.tar.bz2

Page 27 of 32
To display detailed information including online/offline status of the files in the cache for an Integral Volume set named Test
mounted on /mnt, enter:

#>mmls -Rso /mnt

Directory -f-k /
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 mmchmod command is used to change the migration attributes of specified cache files. This command is useful if the
System Administrator does not want to archive some files to the archival media but wants to keep them in the cache.

mmchmod [-R] [-p file_pattern] [-t {file|dir}][-u user_name] [-U uid] [-g group_name] [-G gid][-m mode]
[{+|-}{fk}] ... filename ...

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 number of keep in cache and archive never files is printed using the mmparam command, and the files status
attributes can be displayed with mmls command.

C) The 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} path
mmsubtree -r {tree|data|kill} [hostname:]setname/path
mmsubtree -c {tree|data} path
mmsubtree -c {tree|data} [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.

Page 28 of 32
D) The 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 [-l {low_primary_capacity | xxMB | xx%}]

[-h {high_primary_capacity | xxMB | xx%}]
[-H host_name] {set_name | filename}

E) The vlinset command depending on the file system being used allows editing 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 jukebox and allows removal of the media from
the jukebox by keeping the contents of the CD/DVD-ROM online in the cache.

Page 29 of 32
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
jukebox 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. In this condition the archiving will stop. In addition, any processes waiting on an event, which
requires access to the archive, will return errors as will any new accesses to the Integral Volume set which require access to the
archive. Any accesses to the Integral Volume set, which does not require access to the archive, will process as normal.

Example of Error Condition in the Cache

If an error condition occurs in the cache, the QStar Software directs an error message to the system console window and the
/opt/QStar/log/syslog file.

Below is an example of the error messages:

mmserver: /cache/103019992: Covered file system error: No such device or address:

PAGE_FAULT: Client UID=0, Client GID=0
Cnode_number=6602, Ino=7273, page_number=0, page_address=155, map_size=65536

The status of the cache can be monitored using the mmparam command and if an error occurs, the “Error Condition” line of
this command will display the following message:
Error condition: COVERED ERROR

At this point, the System Administrator can fix the problem with the archive and resume normal processing by clearing the error
condition of the Integral Volume set using the following command:

#>mmresume (mount_point | set_name)

Note: This command can be used in conjunction with two different flags, “–e” and “–n”. Never use these flags without
contacting QStar Technical Support Personnel first. For more detailed information on the mmresume command, please refer
to Chapter 9 - Command Reference in this manual.

Note1: If a DVD jukeboxes is used once the covered error is cleared using the mmresume command, QStar highly recommends
checking to see if the media type information of the current write surface is still reported correctly in the jbstatus output . 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 on Chapter 8.

If necessary, the Integral Volume set may be unmounted and the system halted to repair the problem with the archive prior to
issuing the mmresume command. During this entire process, the maximum level of availability to data is maintained while at
the same time protecting the Integral Volume set from data loss or corruption.

Page 30 of 32
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 UNIX fsck command:

Platform Command (example)

Sun Solaris fsck /dev/rdsk/c0t3d0s5
HP/UX fsck /dev/vg00/rvol4
IBM AIX fsck /dev/lv08

2) Remount the sets using the mountiv command. Some sets may take longer to mount, as the QStar Software may need to
carry out further recovery procedures or consistency checks.

3) After the set is mounted, try to access a file. If an I/O error is received it means that the db_files (sdf_db or udf_db files)
present in the cache partition are corrupted.

To rebuild these index_files, umount the sets and run the following commands:

vlrestore_fsdb [-H host_name] set_name For SDF and UDF file system.

vlrestore_fsdb [-H host_name] [-D SDF_span_number] set_name

For SDF file system, specify the SDF volume number (starting from 1) which must be used for restoring SDF database.
Without this option (or if volume number is equal to 0) the SDF database will be restored from the last surface in the
set. The database will be restored from specified volume and SDF events will be replayed from that medium. The
saved database on the next volume will not be used to restore data base. Rather the data portion of the SDF volume will
be scanned and events replayed. This process continues until last medium (surface) in the set is scanned. The mirrored
SDF volume set restore with this option is not supported.

vlrestore_fsdb [-H host_name] [-D {UDF_span_number|+}] set_name

For UDF file system with Spanning Interchange Level. 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 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).

Once the vlrestore_fsdb command has completed remount the Integral Volume sets.

Note: 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.

Page 31 of 32
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.

#>mountiv set_name mount_point

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 of in /opt/QStar/log/syslog file.

Example - If there is not an inconsistency between the file system and the log file, the /opt/QStar/log/syslog file 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.

Page 32 of 32
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 jukebox. This allows the user to tailor the
media sets within the jukebox to their own requirements. There follows a detailed description on how to create and manage each
of the types of media configuration.

INTEGRAL VOLUME SET CONFIGURATION................................................................................ 3

Cache Management for Integral Volume Set Configuration .............................................. 4
MANAGING QSTAR HSM PRODUCT WITH SDF FILE SYSTEM ................................................ 5
MANAGING AN INTEGRAL VOLUME (I.V.) SET..................................................................... 6
Design Considerations for Integral Volume Set ............................................................... 6
Overview of Creating an Integral Volume Set.................................................................. 6
INTEGRAL VOLUME SET CONFIGURATION FOR A JUKEBOX OR STANDALONE
DRIVE ........................................................................................................................................ 7
MANAGING QSTAR HSM PRODUCT WITH THE UDF FILE SYSTEM ..................................... 14
MANAGING AN INTEGRAL VOLUME (I.V.) SET................................................................... 15
Design Considerations for Integral Volume Set ............................................................. 15
Overview of Creating an Integral Volume Set................................................................ 16
INTEGRAL VOLUME SET CONFIGURATION FOR A JUKEBOX OR STANDALONE
DRIVE WITH AUTOMOUNT AND SINGLE-VOLUME INTERCHANGE LEVELS ............. 17
INTEGRAL VOLUME SET CONFIGURATION FOR A JUKEBOX WITH SPANNING
INTERCHANGE LEVEL........................................................................................................... 26
MANAGING QSTAR CD/DVD AXXESS PRODUCT WITH ISO 9660 AND UDF FILE
SYSTEMS......................................................................................................................................... 32
INTEGRAL VOLUME SET CONFIGURATION FOR A CD/DVD-ROM JUKEBOX OR
STANDALONE WITH AUTOMOUNT AND SINGLE-VOLUME INTERCHANGE LEVELS 33
MANAGING QSTAR CD/DVD MASTER PRODUCT WITH ISO 9660 AND UDF FILE
SYSTEMS......................................................................................................................................... 39
MANAGING QSTAR CD/DVD MASTER SOFTWARE FOR ISO/UDF IMAGES RECORDED
AS DISC-AT-ONCE.................................................................................................................... 40
INTEGRAL VOLUME SET CONFIGURATION FOR A CD/DVD-ROM JUKEBOX................. 41
SETTING THE CD/DVD-R WRITE PROCEDURE ................................................................... 41
Displaying the Delayed Commands under VL Scheduler Control............................... 42
Displaying and Setting the General VL Configuration Properties............................... 43
Displaying the VL Configuration CD/DVD-R Write Properties ..................................... 43
Setting the VL Configuration CD/DVD-R Direct Write Properties............................... 43
Setting the VL Configuration CD/DVD-R Delayed Write Properties ........................... 44
CREATING AN ISO IMAGE....................................................................................................... 47
Examples of Creating an ISO Image ................................................................................ 48
CREATING A UDF IMAGE......................................................................................................... 49
Examples of Creating a UDF Image.................................................................................. 49
WRITING AN IMAGE FILE TO THE CD/DVD-R MEDIA ....................................................... 50
Starting the RECORD Procedure........................................................................................ 50
Selecting Target Jukebox.................................................................................................... 52
Selecting Target Shelves..................................................................................................... 52
Selecting Media Type ........................................................................................................... 52
Starting the CD/DVD-R Direct Write Procedure............................................................. 53
Direct Write Procedure Using the Any Shelf Option.................................................. 53
Direct Write Procedure Using a Specified Shelf ......................................................... 54
Information Displayed During the Direct Write Procedure ...................................... 55

Page 1 of 88
 Starting the CD/DVD-R Delayed Write Procedure ......................................................... 56
Delayed Write Procedure Using the Any Shelf Option .............................................. 56
Delayed Write Procedure Using a Specified Shelf ..................................................... 57
Delayed Write Procedure Using the Any Option and Multiple Copy....................... 58
Information Displayed During the Delayed Write Procedure .................................. 59
Displaying the Delayed Jobs Status in the Delayed Jobs Queue List.................... 60
Displaying the Delayed Jobs Status for a Single Copy............................................. 61
Displaying the Delayed Jobs Status for a Multiple Copy.......................................... 62
Displaying the Delayed Jobs Status in Long Format................................................. 64
Moving Delayed Jobs from the Delayed Jobs List...................................................... 66
Deleting Delayed Jobs from the Delayed Jobs List.................................................... 67
Burn Test Procedure Before Starting the Write Operation .......................................... 68
Laser OFF Burn Test......................................................................................................... 68
Write OFF Burn Test......................................................................................................... 70
ERROR CONDITIONS DURING RECORDING........................................................................ 72
MANAGING QSTAR CD/DVD MASTER SOFTWARE FOR UDF FILE SYSTEM WRITTEN
WITH PACKET WRITING .......................................................................................................... 73
MANAGING AN INTEGRAL VOLUME (I.V.) SET................................................................... 73
Design Considerations for Integral Volume Set ............................................................. 73
Overview of Creating an Integral Volume Set................................................................ 74
INTEGRAL VOLUME SET CONFIGURATION FOR A CD/DVD-R JUKEBOX OR
STANDALONE DRIVE WITH AUTOMOUNT AND SINGLE-VOLUME INTERCHANGE
LEVELS .................................................................................................................................... 75
INTEGRAL VOLUME SET CONFIGURATION FOR CD/DVD-R JUKEBOX WITH
SPANNING INTERCHANGE LEVEL AND PACKET WRITING........................................... 82
RECOVERING A DAMAGED CD/DVD-R MEDIA WRITTEN WITH UDF SPANNING
INTERCHANGE LEVEL AND PACKET WRITING USING THE BACKUP IMAGE ........ 88

Page 2 of 88
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 the 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 jukebox to an offline location, to free up shelf
space for new media to be added to the jukebox, 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 jukebox 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 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. 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; namely, users normally 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 cope with multiple file systems.

• Ease of handling: large data files that require more than one surface are easily accommodated.

• 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 levels of access security.

• Transportability: complete Integral Volume sets can be exported from a jukebox and then imported into another
jukebox.

• 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 jukebox 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 reaches capacity, less frequently accessed media can be exported from the , but the
data stil appears online to the users.

Page 3 of 88
 • 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 into 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 jukebox, or across all jukeboxes, 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 jukebox, or across all jukeboxes, 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

An Integral Volume set configuration has an additional module to consider the cache. The Migration Manager controls the
cache. The status of the cache can be checked and modified by the mmparam command. This allows cache parameters such as
a High Water Mark and flush on umount 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 the mmarc command. 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.

Page 4 of 88
 MANAGING QSTAR HSM PRODUCT WITH SDF FILE
SYSTEM
In this section Optical (MO/UDO/PDD), DVD-RAM, Blu-ray 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 jukebox and standalone drive that QStar Software supports.

Page 5 of 88
MANAGING AN INTEGRAL VOLUME (I.V.) SET
Design Considerations for Integral Volume Set
The Standard Data Format (SDF) file system can be used with jukeboxes and standalone drives that support WORM or
rewritable Optical (MO/UDO/PDD) media, Blu-ray, DVD-RAM and Tape media.

The SDF file system used with a jukebox 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
commands. Detailed information follows in subsequent topics.

Steps for jukebox and standalone drive Command To Use

1. Importing the media into the jukebox(es) vlimport
Loading the media to the drive manually (For Standalone Drive) vlrefresh
2. Erasing the media, if rewritable vlerase
3. Repeat the above steps 1 and 2 for all media needed (For a
Jukebox)
4. Creating the Integral Volume set definition vlcrset
5. Adding the media to an Integral Volume set vladdtoset
6. Creating the cache for the Integral Volume set vlcache
7. Creating the mount point directory mkdir
8. Mounting the Integral Volume set mountiv
9. Unmounting the Integral Volume set umount/umountiv
Unloading the media from the drive (Standalone Drive) vlexport

Monitoring an Integral Volume set Command To Use

1. Displaying the jukebox shelf information jbstatus
2. Monitoring the VL device information vllsdev
3. Monitoring the Integral Volume set information vllsset
4. Monitoring the file system df -k (Command platform independent)
5. Monitoring the cache status mmparam

Page 6 of 88
 INTEGRAL VOLUME SET CONFIGURATION FOR A
JUKEBOX OR STANDALONE DRIVE

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. Because the QStar Software simulates a Standalone Drive as a virtual jukebox with one shelf, containing a
media with a single surface, an MO Optical jukebox will be used as an example in the walk through described below. The
only effective difference from a jukebox and a standalone drive is the number of shelves and some additional features available
only for the jukebox.

Note: All the default parameters are used, for more detailed information, please refer to Chapter 5 - The Volume Librarian or
Chapter 9 - Command Reference in this manual.

To create an Integral Volume set, follow the directions below.

1) To determine the jukebox shelf and media information in reference to the Volume Librarian, enter:

vllsdev device_name

Example - To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
----------------------------------------------------------------------------
1: empty Note: The shelf 1 is empty.
2: empty
3: empty
4: empty
5: empty
6: empty
7: empty
8: empty
9: empty
10: empty
11: empty
12: empty
13: empty
14: empty
15: empty
16: empty

2) To import the media into a shelf, enter:

vlimport device_name shelf_number

Example - to import the media to shelf 1 of the jukebox identified as jb, enter:

#>vlimport jb 1
jb:refreshing shelf 1 ...

Page 7 of 88
 Note: If a standalone drive is used manually load the media into the drive and then refresh the status of the media.

To refresh the status of the media in the standalone drive, enter:

vlrefresh device_name

Example - to refresh the media in the standalone drive identified as jb, enter:

#>vlrefresh jb

3) To import additional media, repeat the above steps with the appropriate shelf number.

4) To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
----------------------------------------------------------------------------
1a: unknown 2.4 GB Rewritable Note: This message appears if the media is rewritable and new.
1b: unknown 2.4 GB Rewritable
2: empty
3: empty
4: empty
5: empty
6: empty
7: empty
8: empty
9: empty
10: empty
11: empty
12: empty
13: empty
14: empty
15: empty
16: empty

Note: For Tape and single sided media only Shelf 1a information will be displayed and the Type column will display Tape for
Tape media, DVD-RAM for DVD-RAM media and BD-RS or BD-RE for Blu-ray media.

5) To erase the media before using it, enter:

vlerase device_name shelf_number[a/b]

Example - to erase the media in shelf 1 of the jukebox identified as jb, enter:

#>vlerase jb 1 Note: If the media is WORM skip this command.

Page 8 of 88
6) To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
----------------------------------------------------------------------------
1a: erased 2.4 GB Rewritable Note: The status in the VL database now displays erased.
1b: erased 2.4 GB Rewritable Note1: The status in the VL database for new WORM media is blank.
2: empty
3: empty
4: empty
5: empty
6: empty
7: empty
8: empty
9: empty
10: empty
11: empty
12: empty
13: empty
14: empty
15: empty
16: empty

7) To create a new Integral Volume set, enter:

vlcrset -T fs_type set_type_specific_options -u media_type set_name

Example for OPTICAL (MO/UDO/DVD-RAM/Blu-ray):

Example-A - create a new Integral Volume set definition named Test for rewritable Optical media with an SDF file system,
enter:

#>vlcrset –T sdf Test

Example-B - create a new Integral Volume set definition named Test for WORM Optical media with an SDF file system, enter:

#>vlcrset –T sdf –u worm Test

Example-C - create a new Integral Volume set definition named Test for DVD-RAM media with an SDF file system, enter:

#>vlcrset –u dvd Test

Example-D - create a new Integral Volume set definition named Test for Blu-ray BD-RE rewritable media with an SDF file
system, enter:

#>vlcrset –T sdf –u bd-re Test

Page 9 of 88
 Example-E - create a new Integral Volume set definition named Test for Blu-ray BD-RS WORM media with an SDF file
system, enter:

#>vlcrset –T sdf –u bd-rs Test

Example for TAPE:

Example-A - create a new Integral Volume set definition named Test for tape media with an SDF file system and compression
option enabled, enter:

#>vlcrset –T sdf –c on –u tape Test

Example-B - create a new Integral Volume set definition named Test for tape media with an SDF file system and compression
option as default, enter:

#>vlcrset –T sdf –c default –u tape Test

Example-C - create a new Integral Volume set definition named Test for tape media with an SDF file system and compression
option disabled, enter:

#>vlcrset –T sdf –c off –u tape Test

8) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: The Integral Volume set is empty because no media (Media=0) is associated with it.
Test
Use_media=disk,writable Spread=no Quota=2048 Media=0
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
Set_Id=
No Cache

Note: The Use_Media information will display disk, writable or disk, worm for Optical media, tape, writable for Tape media,
bd,writable for Blu-ray BD-RE media, bd,worm,rdonly for Blu-ray BD-RS Media, and dvd, writable for DVD-RAM media.
For Tape media the additional information about compression will be displayed by default the comprssion is displayed as
Compression=On.

9) To add media to the Integral Volume set Test, enter:

vladdtoset set_name device_name shelf_number

Example - to add the media on shelf 1 to the Integral Volume set Test, enter:

#>vladdtoset Test jb 1
jb:initializing side a ...

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 jukebox with the same Set_Id will be added to the Integral Volume set automatically. If
in the future a media with the same Set_Id is imported into the jukebox it will be added to the Integral Volume set automatically.

Page 10 of 88
10) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now one media is associated with the Integral Volume set Test that has the Set_Id.
Test
Use_media=disk,writable Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
Set_Id=c25b016a.3453d0e4
No Cache
0: Online=jb:1 Sequence_numbers=0,1

11) To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
----------------------------------------------------------------------------
1a: sdf 2.4 GB Rewritable Seq=0 SetId=c25b016a.3453d0e4
1b: sdf 2.4 GB Rewritable Seq=1 SetId=c25b016a.3453d0e4
2: empty
3: empty
4: empty
5: empty
6: empty
7: empty
8: empty
9: empty
10: empty
11: empty
12: empty
13: empty
14: empty
15: empty
16: empty

12) To create the cache for the Integral Volume set, enter:

vlcache -p xxMB -c /cache_root set_name

Example - to create a cache with 100 MB and cache located on /Cache_Test for the Integral Volume set Test, enter:

#>vlcache -p 100MB -c /Cache_Test Test

Page 11 of 88
13) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now the cache is associated with the Integral Volume set Test.
Test
Use_media=disk,writable Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
Set_Id=c25b016a.3453d0e4
Cache: Cache_root=/Cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
0: Online=jb:1 Sequence_numbers=0,1

14) To create the mount point directory, enter:

mkdir directory_name

Example - to create the mount point /mnt, enter:

#>mkdir /mnt

15) To mount the Integral Volume set with a new cache, enter:

mountiv -n set_name mount_point

Example - to mount the Integral Volume set Test on the mount point /mnt, enter:

#>mountiv -n Test /mnt

Note: The “-n” option is used only with the first mount, on subsequent mounts, do not use the “-n” option in the mountiv
command syntax.

Note1: When using Tape media the number of Integral Volume sets that can be mounted at one time is limited by the
number of drives available in the jukebox.

16) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now the Integral Volume set Test is mounted.
Test
Use_media=disk,writable Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
Set_Id=c25b016a.3453d0e4
Cache: Cache_root=/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

Page 12 of 88
17) To monitor the Integral Volume set, enter:

#>df -k /mnt

18) To monitor the cache status of an Integral Volume set, enter:

mmparam { set_name | mount_point}

Example - to monitor the cache status of the Integral Volume set Test, enter:

#>mmparam /mnt

#>mmparam Test

19) To start archiving files from the cache to the archival media, enter:

mmarc [-H host_name] {-l | -e | -a age | -s} [-w][-j {delayed_job_name | "default"}] [-S cron_like_schedule]
{set_name | filename}

Example - to start archiving files from the cache of the Integral Volume set Test, enter:

#>mmarc -e /mnt

#>mmarc -e Test

20) To unmount the Integral Volume set, enter:

umount /mount_point

umountiv set_name

Example - to unmount the Integral Volume set Test on the mount point /mnt, enter:

#>umount /mnt

#>umountiv Test (For Linux and HP-UX platforms)

Note: QStar does not recommend using the umount command for Linux or HP-UX platforms; this ensures the Integral Volume
set is completely unmounted. Please refer to Chapter 6 - Migration Manager in this manual for more detailed information.

21) To unload the media from the drive, enter:

#>vlexport jb 1

Page 13 of 88
 MANAGING QSTAR HSM PRODUCT WITH THE UDF
FILE SYSTEM
In this section Optical (MO/UDO/PDD), DVD-RAM 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 jukebox and standalone drive that QStar Software supports.

Page 14 of 88
 MANAGING AN INTEGRAL VOLUME (I.V.) SET

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
jukeboxes and standalone drives that support WORM or rewritable Optical (MO/UDO/PDD) media, Blu-ray, DVD-RAM 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.

B) Single-Volume (Used with 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. This configuration is primarily used with standalone drives. The
QStar Software simulates the Standalone Drive as a virtual jukebox with one shelf, containing a media with a single surface,
but may also be used in jukeboxes 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. This configuration should be primarly used with WORM media but may also be used for rewritable
media. Retrieval performance of data may be significantly decreased if any files are deleted or renamed from the file system.

The recommendations for using UDF spanning:

1) A cache 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 Volumes.
4) WORM media
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 explained in the Master
product section.

Page 15 of 88
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
commands. Detailed information follows in subsequent topics.

Steps for jukebox and standalone drive Command To Use

1. Importing the media into the jukebox(es) vlimport
Loading the media to the drive manually (Single-Volume) vlrefresh
2. Erasing the media, if rewritable vlerase
3. Repeat the above steps 1 and 2 for all media needed (For a Jukebox)
4. Creating the Integral Volume set definition vlcrset
5. Adding the media to an Integral Volume set vladdtoset
6. Creating the cache for the Integral Volume set vlcache
7. Creating the mount point directory mkdir
8. Mounting the Integral Volume set mountiv
9. Unmounting the Integral Volume set umount/umountiv
Unloading the media from the drive (Single-Volume) vlexport

Monitoring an Integral Volume set Command To Use

1. Displaying the jukebox shelf information jbstatus
2. Monitoring the VL device information vllsdev
3. Monitoring the Integral Volume set information vllsset
4. Monitoring the file system df –k (Command platform independent)
udfdf (Automount Interchange Level)
5. Monitoring the cache status mmparam

Page 16 of 88
 INTEGRAL VOLUME SET CONFIGURATION
FOR A JUKEBOX OR STANDALONE DRIVE WITH 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. Because the QStar Software simulates a Standalone Drive as a
virtual jukebox with one shelf, containing a media with a single surface, a DVD-RAM jukebox will be used as an example
in the walk through described below. The only effective difference from a jukebox and a standalone drive is the number of
shelves and some additional features available only for the jukebox.

Note: All the default parameters are used, for more detailed information, please refer to Chapter 5 - The Volume Librarian or
Chapter 9 - Command Reference in this manual.

To create a UDF Automount or Single-Volume Integral Volume set, follow the directions below.

1) To determine the jukebox shelf and media information in reference to the Volume Librarian, enter:

vllsdev device_name

Example - To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
---------------------------------------------------------------------------------
1-1: empty Note: The shelf 1 is empty.
2-1: empty
3-1: empty
4-1: empty
5-1: empty
6-1: empty
7-1: empty
8-1: empty
9-1: empty
10-1: empty
11-1: empty
12-1: empty
13-1: empty
14-1: empty
15-1: empty
16-2: empty

2) To import the media into a shelf, enter:

vlimport device_name shelf_number

Example - to import the media to shelf 1 of the jukebox identified as jb, enter:

#>vlimport jb 1
jb:refreshing shelf 1 ...

Page 17 of 88
 Note: If a standalone drive is used manually, load the media into the drive and then refresh the status of the media.

To refresh the status of the media in the standalone drive, enter:

vlrefresh device_name

Example - to refresh the media in the standalone drive identified as jb, enter:

#>vlrefresh jb

3) To import additional media, repeat the above steps with the appropriate shelf number.

4) To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
---------------------------------------------------------------------------------
1a-1: unknown 4.3 GB DVD-RAM Note: This message appears if the media is rewritable and new.
1b-1: unknown 4.3 GB DVD-RAM
2-1: empty
3-1: empty
4-1: empty
5-1: empty
6-1: empty
7-1: empty
8-1: empty
9-1: empty
10-1: empty
11-1: empty
12-1: empty
13-1: empty
14-1: empty
15-1: empty
16-2: empty

Note: For single sided media only Shelf 1a information will be displayed and the Type column will display Rewritable or
Worm for Optical media, DVD-RAM for DVD-RAM media and BD-RS or BD-RE for Blu-ray media.

5) To erase the media before using it, enter:

vlerase device_name shelf_number[a/b]

Example - to erase the media in shelf 1 of the jukebox identified as jb, enter:
#>vlerase jb 1

Page 18 of 88
6) To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
---------------------------------------------------------------------------------
1a-1: erased 4.3 GB DVD-RAM Note: The status in the VL database now displays erased.
1b-1: erased 4.3 GB DVD-RAM Note1: The status in the VL database for new WORM media is blank.
2-1: empty
3-1: empty
4-1: empty
5-1: empty
6-1: empty
7-1: empty
8-1: empty
9-1: empty
10-1: empty
11-1: empty
12-1: empty
13-1: empty
14-1: empty
15-1: empty
16-2: empty

7) To create a new Integral Volume set, enter:

vlcrset -T fs_type set_type_specific_options -u media_type set_name

Example for OPTICAL (MO/UDO/DVD-RAM/Blu-ray):

Example-A - create a new Integral Volume set definition named Test for rewiteable Optical media with a UDF file system and
single-volume interchange level, enter:

#>vlcrset –T udf Test

Example-B - create a new Integral Volume set definition named Test for WORM Optical media with a UDF file system and
single- volume interchange level, enter:

#>vlcrset –T udf –u worm Test

Example-C- create a new Integral Volume set definition named Test for DVD-RAM media with a UDF file system and single-
volume interchange level, enter:

#>vlcrset –T udf –u dvd Test

Example-D - create a new Integral Volume set definition named Test for Blu-ray BD-RE rewritable media with a UDF file
system and single-volume interchange level, enter:

#>vlcrset –T udf –u bd-re Test

Page 19 of 88
 Example-E - create a new Integral Volume set definition named Test for Blu-ray BD-RS WORM media with a UDF file system
and single-volume interchange level, enter:

#>vlcrset –T udf –u bd-rs Test

Example-F - create a new Integral Volume set definition named Test for rewiteable Optical media with a UDF file system and
automount interchange level, enter:

#>vlcrset –T udf –v a Test

Example-G - create a new Integral Volume set definition named Test for WORM Optical media with a UDF file system and
automount interchange level, enter:

#>vlcrset –T udf –v a –u worm Test

Example-H- create a new Integral Volume set definition named Test for DVD-RAM media with a UDF file system and
automount interchange level, enter:

#>vlcrset –T udf –v a –u dvd Test

Example-I - create a new Integral Volume set definition named Test for Blu-ray BD-RE rewritable media with a UDF file
system and automount interchange level, enter:

#>vlcrset –T udf –v a –u bd-re Test

Example-L - create a new Integral Volume set definition named Test for Blu-ray BD-RS WORM media with a UDF file system
and automount interchange level, enter:

#>vlcrset –T udf -v a –u bd-rs Test

Note: For more detailed information of the UDF specific options, please refer to “Creating an Integral Volume Set with UDF
or ISO 9660 File System” session on Chapter 5 - The Volume librarian in this manual.

8) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: The Integral Volume set is empty because no media (Media=0) is associated with it.

Single-Volume Interchange Level output:

Test
Use_media=dvd,writable Spread=no Quota=1 Media=0
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=single-volume
Packet_writing_init=no Space_calculation=yes Verify_write=no
No cache

Page 20 of 88
 Automount Interchange Level output:

Test
Use_media=dvd,writable Spread=no Quota=2048 Media=0
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=no Space_calculation=yes Verify_write=no
No cache

Note: The difference between the two above outputs are in the Interchange Level type and in the Quota number.

Note1: The Use_Media information will display disk, writable or disk, worm for Optical media, bd,writable for Blu-ray BD-
RE media, bd,worm,rdonly for Blu-ray BD-RS media, and dvd, writable for DVD-RAM media.

9) To add media to the Integral Volume set, enter:

vladdtoset set_name device_name shelf_number

Example - to add the media on shelf 1 to the Integral Volume set Test, enter:

#>vladdtoset Test jb 1
jb:initializing side a ...

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 will not change its status. 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.

10) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now one media is associated with the Integral Volume set Test.

Single-Volume Interchange Level output:

Test
Use_media=dvd,writable Spread=no Quota=1 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=q_3c0ec380
UDF_revision=150 Interchange_level=single-volume
Packet_writing_init=no Space_calculation=yes Verify_write=no
No cache
0: Online=jb:1 Sequence_number=1

Page 21 of 88
 Automount Interchange Level output:

Test
Use_media=dvd,writable Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=no Space_calculation=yes Verify_write=no
No cache
0: Online=jb:1 Automount_sequence_numbers=0,1

Note: In the automounter configuration the Logical_volume_identifier is equal to NA (Not Available) and instead the
Automount_Sequence_number is displayed. When a media is added to the Integral Volume set, every surface will be initialized
wih a unique Set_id number (Logical Volume Identifier). By default, this unique Set_id number is equal to “q_number”. The
Automount_Sequence_numbers represent the sequence number of the surfaces in the root directory of the file system once it is
mounted. All sub-directories (surfaces) in the root directory will be labeled by default as vol_Automount_Sequence_number
(i.e. vol_0, vol_1, vol_#) if the Set_id number is one that is assigned by default by QStar Software, if not, theVolume Label will
be used as the sub-directories name. With the vladdtoset command it is possible to specify the Logical Volume Identifier using
the -A -B options. If the media is blank/erased the specified Logical Volume Identifier will be written to the surface as a unique
surface_id number and used as the directory name that identifies the surfaces under the Automount mount point. If the Media
already has the Logical Volume Identifier (initialized) the -A and -B option will only change the default vol_0, vol_1 and vol_#
directory names that identified the surfaces under the Automount mount point with the specified name. In this case, the new sub-
directories name will be printed in the set information for each surface.

Note1: In the rest of the walk through only the automout interchange level output will be diplayed.

11) To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
---------------------------------------------------------------------------------
1a-1: udf-150 4.3 GB DVD-RAM Seq=1 Log_vol_id=q_a0ce5c5e
1b-1: udf-150 4.3 GB DVD-RAM Seq=1 Log_vol_id=q_b0ce5c5e
2-1: empty
3-1: empty
4-1: empty
5-1: empty
6-1: empty
7-1: empty
8-1: empty
9-1: empty
10-1: empty
11-1: empty
12-1: empty
13-1: empty
14-1: empty
15-1: empty
16-2: empty

Page 22 of 88
12) To create the cache for an Integral Volume set, enter:

vlcache -p xxMB -c /cache_root set_name

Example - to create a cache with 100 MB and cache located on /Cache_Test for the Integral Volume set Test, enter:

#>vlcache -p 100MB -c /Cache_Test Test

13) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now a cache is associated with the Integral Volume set Test.
Test
Use_media=dvd,writable Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=no Space_calculation=yes Verify_write=no
Cache: Cache_root=/Cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
0: Online=jb:1 Automount_sequence_numbers=0,1

14) To create the mount point directory, enter:

mkdir directory_name

Example - to create the mount point /mnt, enter:

#>mkdir /mnt

15) To mount the Integral Volume set with a new cache, enter:

mountiv –n set_name mount_point

Example - to mount Integral Volume set Test on the mount point /mnt, enter:

#>mountiv –n Test /mnt

Note: The “-n” option is used only with the first mount, on subsequent mounts, do not use the “-n” option in the mountiv
command syntax.

Page 23 of 88
16) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now the Integral Volume set Test is mounted.
Test
Use_media=dvd,writable Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=no Space_calculation=yes Verify_write=no
Cache: Cache_root=/Cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Mounted at /mnt
0: Online=jb:1 Automount_sequence_numbers=0,1 Mounted=a,b

17) To monitor the Integral Volume set, enter:

Single-volume Interchange Level:

#>df -k /mnt

Automount Interchange Level:

#>df -k /mnt Note: This command will display the total capacity of all the surfaces already accessed

#>udfdf -t /mnt

#>udfdf -f -a 0 /mnt

Note: QStar recommends reviewing the explanation for the udfdf command in Chapter 9 - Command Reference of this manual.

18) To monitor the cache status of an Integral Volume set, enter:

mmparam { set_name | mount_point}

Example - to monitor the cache status of the Integral Volume set Test, enter:

#>mmparam /mnt

#>mmparam Test

19) To start archiving files from the cache to the archival media, enter:

mmarc [-H host_name] {-l | -e | -a age | -s} [-w][-j {delayed_job_name | "default"}] [-S cron_like_schedule]
{set_name | filename}

Page 24 of 88
 Example - to start archiving files from the cache of the Integral Volume set Test, enter:

#>mmarc -e /mnt

#>mmarc -e Test

20) To unmount the Integral Volume set, enter:

umount /mount_point

umountiv set_name

Example - to unmount the Integral Volume set Test on the mount point /mnt, enter:
#>umount /mnt

#>umountiv Test (For Linux and HP-UX platforms)

Note: QStar does not recommend using the umount command for Linux or HP-UX platforms; this ensures the Integral Volume
set is completely unmounted. Please refer to Chapter 6 - Migration Manager in this manual for more detailed information.

21) To unload the media from the drive, enter:

#>vlexport jb1 1

Page 25 of 88
 INTEGRAL VOLUME SET CONFIGURATION FOR A
JUKEBOX WITH 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. This configuration should be used mainly with WORM media, it may also be used with
rewritable media, but retrieval performance of data can be significantly decreased if any files are deleted or renamed on
the file system. An MO Optical jukebox 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 or
Chapter 9 - Command Reference in this manual.

To create a UDF Spanning Integral Volume set, follow the directions below.

1) To determine the jukebox shelf and media information in reference to the Volume Librarian, enter:

vllsdev device_name

Example - To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
----------------------------------------------------------------------------
1: empty Note: The shelf 1 is empty.
2: empty
3: empty
4: empty
5: empty
6: empty
7: empty
8: empty
9: empty
10: empty
11: empty
12: empty
13: empty
14: empty
15: empty
16: empty

2) To import the media into a shelf, enter:

vlimport device_name shelf_number

Example - to import the media to shelf 1 of the jukebox identified as jb, enter:

#>vlimport jb 1
jb:refreshing shelf 1 ...

Page 26 of 88
3) To import additional media, repeat the above steps with the appropriate shelf number.

4) To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
----------------------------------------------------------------------------
1a: blank 2.4 GB Worm Note: The status in the VL database for new WORM media is blank.
1b: blank 2.4 GB Worm
2: empty
3: empty
4: empty
5: empty
6: empty
7: empty
8: empty
9: empty
10: empty
11: empty
12: empty
13: empty
14: empty
15: empty
16: empty

Note: For single sided media only Shelf 1a information will be displayed and the Type column will display Rewritable or
Worm for Optical media, DVD-RAM for DVD-RAM media and BD-RS or BD-RE for Blu-ray media.

5) To erase the media before using it, enter:

vlerase device_name shelf_number[a/b]

Example - to erase the media in shelf 1 of the jukebox identified as jb, enter:
#>vlerase jb 1 Note: If the media is WORM skip this command.

6) To create a new Integral Volume set, enter:

vlcrset -T fs_type set_type_specific_options -u media_type set_name

Example for OPTICAL (MO/UDO/DVD-RAM/Blu-ray):

Example-A - create a new Integral Volume set definition named Test for WORM media with a UDF file system, spanning
interchange level and the close of full volume option enabled, enter:

#>vlcrset –T udf –v s –V 1 –u worm Test

Example-B - create a new Integral Volume set definition named Test for DVD-RAM media with a UDF file system, spanning
interchange level and the close of full volume option enabled, enter:

#>vlcrset –T udf –v s –V 1 –u dvd Test

Page 27 of 88
 Example-C - create a new Integral Volume set definition named Test for Blu-ray BD-RS WORM media with a UDF file
system, spanning interchange level and the close of full volume option enabled, enter:

#>vlcrset –T udf -v s –V 1 –u bd-rs Test

Note: For more detailed information of the UDF specific options, please refer to “Creating an Integral Volume Set with UDF
or ISO 9660 File System” session on Chapter 5 - The Volume librarian in this manual.

7) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: The Integral Volume set is empty because no media (Media=0) is associated with it.
Test
Use_media=disk,worm Spread=no Quota=2048 Media=0
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=spanning
Packet_writing_init=no Verify_write=no
Close_full_volume=yes File_spanning=yes Use_image_backup=no
No cache

Note: The Use_Media information will display disk, writable or disk, worm for Optical media, bd,writable for Blu-ray BD-RE
media, bd,worm,rdonly for Blu-ray BD-RS Media, and dvd, writable for DVD-RAM media.

8) To add media to the Integral Volume set Test, enter:

vladdtoset set_name device_name shelf_number

Example - to add the media on shelf 1 to the Integral Volume set Test, enter:

#>vladdtoset Test jb 1
jb:initializing side a ...

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 jukebox with the same Set_Id will be added to the Integral Volume set automatically. If
in the future a media with the same Set_Id is imported into the jukebox it will be added to the Integral Volume set automatically.

9) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now one media is associated with the Integral Volume set Test that has the Set_Id.
Test
Use_media=disk,worm Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=q_a40a36f87
UDF_revision=150 Interchange_level=spanning
Packet_writing_init=no Verify_write=no
Close_full_volume=yes File_spanning=yes Use_image_backup=no
No cache
0: Online=jb:1 Span_numbers=1,2

Page 28 of 88
10) To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
------------------------------------------------------------------------------
1a: udf-150 2.4 GB Worm Span=1 Log_vol_id=q_a40a36f87-1
1b: udf-150 2.4 GB Worm Span=2 Log_vol_id=q_a40a36f87-2
2: empty
3: empty
4: empty
5: empty
6: empty
7: empty
8: empty
9: empty
10: empty
11: empty
12: empty
13: empty
14: empty
15: empty
16: empty

11) To create the cache for the Integral Volume set, enter:

vlcache -p xxMB -c /cache_root set_name

Example - to create a cache with 100 MB and cache located on /Cache_Test for the Integral Volume set Test, enter:

#>vlcache -p 100MB -c /Cache_Test Test

12) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now the cache is associated with the Integral Volume set Test.
Test
Use_media=disk,worm Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=q_a40a36f87
UDF_revision=150 Interchange_level=spanning
Packet_writing_init=no Verify_write=no
Close_full_volume=yes File_spanning=yes Use_image_backup=no
Cache: Cache_root=/Cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
0: Online=jb:1 Span_numbers=1,2

Page 29 of 88
13) To create the mount point directory, enter:

mkdir directory_name

Example - to create the mount point /mnt, enter:

#>mkdir /mnt

14) To mount the Integral Volume set with a new cache, enter:

mountiv –n set_name mount_point

Example - to mount the Integral Volume set Test on the mount point /mnt, enter:

#>mountiv -n Test /mnt

Note: The “-n” option is used only with the first mount, on subsequent mounts, do not use the “-n” option in the mountiv
command syntax.

15) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now the Integral Volume set Test is mounted.
Test
Use_media=disk,worm Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=q_a40a36f87
UDF_revision=150 Interchange_level=spanning
Packet_writing_init=no Verify_write=no
Close_full_volume=yes File_spanning=yes Use_image_backup=no
Cache: Cache_root=/Cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Mounted at /mnt
0: Online=jb:1 Span_numbers=1,2 Mounted=a,b

16) To monitor the Integral Volume set, enter:

#>df -k /mnt

17) To monitor the cache status of an Integral Volume set, enter:

mmparam { set_name | mount_point}

Example - to monitor the cache status of the Integral Volume set Test, enter:

#>mmparam /mnt

#>mmparam Test

Page 30 of 88
18) To start archiving files from the cache to the archival media, enter:

mmarc [-H host_name] {-l | -e | -a age | -s} [-w][-j {delayed_job_name | "default"}] [-S cron_like_schedule]
{set_name | filename}

Example - to start archiving files from the cache of the Integral Volume set Test, enter:

#>mmarc -e /mnt

#>mmarc -e Test

19) To unmount the Integral Volume set, enter:

umount /mount_point

umountiv set_name

Example - to unmount the Integral Volume set Test on the mount point /mnt, enter:

#>umount /mnt

#>umountiv Test (For Linux and HP-UX platforms)

Note: QStar does not recommend using the umount command for Linux or HP-UX platforms; this ensures the Integral Volume
set is completely unmounted. Please refer to Chapter 6 - Migration Manager in this manual for more detailed information.

Page 31 of 88
 MANAGING QSTAR CD/DVD AXXESS PRODUCT WITH
ISO 9660 AND UDF FILE SYSTEMS
The Universal Disk Format (UDF) file system can be used with CD/DVD-ROM media pre-recorded with UDF file system or
pre-recorded with ISO 9660, Rock Ridge and Microsoft extensions, standard file systems. In this section, to understand how to
configure the CD/DVD-ROM media, a simple walk through will be presented that will support every type of jukebox and
standalone drive that QStar Software supports.

Page 32 of 88
 INTEGRAL VOLUME SET CONFIGURATION
FOR A CD/DVD-ROM JUKEBOX OR STANDALONE WITH AUTOMOUNT
AND SINGLE-VOLUME INTERCHANGE LEVELS

Detailed Walk Through:

The following pages will describe how to manage the media with the UDF and ISO 9660 file systems in Automount and
Single-Volume configurations, create and manage an Integral Volume set. Because the QStar Software simulates a
Standalone Drive as a virtual jukebox with one shelf, containing a media with a single surface, a CD/DVD jukebox will
be used as an example in the walk through described below. The only effective difference from a jukebox and a standalone
drive is the number of shelves and some additional features available only for the jukebox.

Note: All the default parameters are used, for more detailed information, please refer to Chapter 5 - The Volume Librarian or
Chapter 9 - Command Reference in this manual.

To create a UDF Automount or Single-Volume Integral Volume set, follow the directions below.

1) To determine the jukebox shelf and media information in reference to the Volume Librarian, enter:

vllsdev device_name

Example - To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
-------------------------------------------------------------------------------
1-1: empty Note: The shelf 1 is empty.
2-1: empty
3-1: empty
4-1: empty
5-1: empty
6-1: empty
7-1: empty
8-1: empty
9-1: empty
10-1: empty
11-2: empty
12-2: empty
13-2: empty
14-2: empty
15-2: empty
16-2: empty

2) To import the CD/DVD-ROM media into a shelf, enter:

vlimport device_name shelf_number

Page 33 of 88
 Example - to import the CD/DVD-ROM on shelf 1 of the jukebox identified as jb, enter:

#>vlimport jb 1
jb: refreshing shelf 1 ...

Note: If a standalone drive is used manually load the media into the drive and then refresh the status of the media.

To refresh the status of the media in the standalone drive, enter:

vlrefresh device_name

Example - to refresh the media in the standalone drive identified as jb, enter:

#>vlrefresh jb

3) To import additional CD/DVD-ROM, repeat the above steps with the appropriate shelf number.

4) To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
-------------------------------------------------------------------------------------
1a-1: udf-150-F 85 MB CD-ROM Seq=1 Log_vol_id=QStar_Software
2a-1: udf-150-F 700 MB CD-ROM Seq=1 Log_vol_id=Backup_01
3a-1 udf-150-F 700 MB CD-ROM Seq=1 Log_vol_id=Backup_02
4a-1: udf-150-F 150 MB CD-ROM Seq=1 Log_vol_id=windows_manual
5a-1: udf-150-F 3.7 GB DVD-ROM Seq=1 Log_vol_id=unix_manual
6a-1: udf-150-F 650 MB CD-ROM Seq=1 Log_vol_id=Data_01
7a-1: udf-150-F 650 MB CD-ROM Seq=1 Log_vol_id=Data_02
8a-1: 9660-RJ 3.8 GB DVD-ROM Manual_01 3a14c0.8ee56da1
9a-1: 9660-RJ 4.2 GB DVD-ROM Manual_02 3c04c0.8dd75dc0
10a-1: udf-150-F 3.5 GB DVD-ROM Seq=1 Log_vol_id=data2000
10b-1: udf-150-F 4.2 GB DVD-ROM Seq=1 Log_vol_id=data2001
11-2: empty
12-2: empty
13-2: empty
14-2: empty
15-2: empty
16-2: empty

5) To create a new Integral Volume set to contain the CD/DVD-ROM media, enter:

vlcrset -T fs_type set_type_specific_options -r set_name

Note: The UDF file system used with the CD/DVD-ROM media is used with the automount interghange level and as a read only
file system. The Readonly flag must be applied to mount the Integral Volume set with QStar CD/DVD Axxess product. If the
flag is not applied, the mount will be denied.

Page 34 of 88
 Example-A - create a new Integral Volume set definition named Test for CD/DVD-ROM media with a UDF file system, single-
volume interchange level and the read only option enabled, enter:

#>vlcrset –T udf -r -u cd-dvd Test

Example-B - create a new Integral Volume set definition named Test for CD/DVD-ROM media with a UDF file system,
automount interchange level and the read only option enabled, enter:

#>vlcrset –T udf -v a -r -u cd-dvd Test

6) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated CD/DVD-ROM.
Note1: The Integral Volume set is empty because no CD/DVD-ROM (Media=0) are
associated with it.

Single-Volume Interchange Level output:

Test
Use_media= cd,dvd,worm,rdonly Spread=no Quota=1 Media=0
Restore_fsdb=no Read_only=yes Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=single-volume
Packet_writing_init=no Space_calculation=yes Verify_write=no
No cache

Automount Interchange Level output:

Test
Use_media= cd,dvd,worm,rdonly Spread=no Quota=2048 Media=0
Restore_fsdb=no Read_only=yes Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=no Space_calculation=yes Verify_write=no
No cache

Note: The difference between the two above outputs are in the Interchange Level type and in the Quota number. The
Use_Media information will display bd,worm,rdonly for Blu-ray BD-ROM media.

Note1: In the rest of the walk through only the automout interchange level output will be diplayed.

7) To add media to the Integral Volume set, enter:

vladdtoset set_type_specific_options set_name device_name shelf_number

Example - to add media from shelf 1 to 9 to the Integral Volume set Test, enter:

#>vladdtoset Test jb 1:9

Note: The media were added to the Integral Volume set without specifying the set type specific option.

Page 35 of 88
 Example - to add media on shelf 10 (side a and b) to the Integral Volume set Test with identifier equal to JB10a and JB10b,
enter:

#>vladdtoset -A JB10a –B JB10b Test jb 10

Note: The media on shelf 10 was added using the UDF (valid also for ISO 9660) specific option –A/B [identifier]. This option
specifies the identifier assigned to surface A/B. If the option was specified, the system tries to use it as a root directory name for
the surface. Otherwise, it tries to use the Logical Volume Identifier.

8) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Ten media are associated to the Integral Volume set Test.
Test
Use_media=cd,dvd,worm,rdonly Spread=no Quota=2048 Media=10
Restore_fsdb=no Read_only=yes Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=no Space_calculation=yes Verify_write=no
No cache
0: Online=jb:1 Automount_sequence_number=0
1: Online=jb:2 Automount_sequence_number=1
2: Online=jb:3 Automount_sequence_number=2
3: Online=jb:4 Automount_sequence_number=3
4: Online=jb:5 Automount_sequence_number=4
5: Online=jb:6 Automount_sequence_number=5
6: Online=jb:7 Automount_sequence_number=6
7: Online=jb:8 Automount_sequence_number=7
8: Online=jb:9 Automount_sequence_number=8
9: Online=jb:10 Automount_sequence_numbers=9,10 A_dir=JB10a B_dir=JB10b

9) To create the cache for the Integral Volume set, enter :

vlcache -p xxMB -c /cache_root set_name

Example - to create a cache with 100 MB and cache located on /Cache_Test for the Integral Volume set Test, enter:

#>vlcache -p 100MB -c /Cache_Test Test

10) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: The cache is associated to the Integral Volume set Test.
Test
Use_media=cd,dvd,worm,rdonly Spread=no Quota=2048 Media=10
Restore_fsdb=no Read_only=yes Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=no Space_calculation=yes Verify_write=no
Cache: Cache_root=/Cache_Test

Page 36 of 88
 Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
0: Online=jb:1 Automount_sequence_number=0
1: Online=jb:2 Automount_sequence_number=1
2: Online=jb:3 Automount_sequence_number=2
3: Online=jb:4 Automount_sequence_number=3
4: Online=jb:5 Automount_sequence_number=4
5: Online=jb:6 Automount_sequence_number=5
6: Online=jb:7 Automount_sequence_number=6
7: Online=jb:8 Automount_sequence_number=7
8: Online=jb:9 Automount_sequence_number=8
9: Online=jb:10 Automount_sequence_numbers=9,10 A_dir=JB10a B_dir=JB10b

11) To create the mount point directory, enter:

mkdir directory_name

Example - to create the mount point /mnt, enter:

#>mkdir /mnt

12) To mount the Integral Volume set with a new cache, enter:

mountiv -n set_name mount_point

Example - to mount the Integral Volume set Test on the mount point /mnt, enter:

#>mountiv -n Test /mnt

Note: The “-n” option is used only with the first mount, on subsequent mounts, do not use the “-n” option in the mountiv
command syntax.

13) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now the Integral Volume set Test is mounted.
Test
Use_media=cd,dvd,worm,rdonly Spread=no Quota=2048 Media=10
Restore_fsdb=no Read_only=yes Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=no Space_calculation=yes Verify_write=no
Cache: Cache_root=/Cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Mounted at /mnt
0: Online=jb:1 Automount_sequence_number=0
1: Online=jb:2 Automount_sequence_number=1
2: Online=jb:3 Automount_sequence_number=2
3: Online=jb:4 Automount_sequence_number=3
4: Online=jb:5 Automount_sequence_number=4
5: Online=jb:6 Automount_sequence_number=5
6: Online=jb:7 Automount_sequence_number=6

Page 37 of 88
 7: Online=jb:8 Automount_sequence_number=7
8: Online=jb:9 Automount_sequence_number=8
9: Online=jb:10 Automount_sequence_numbers=9,10 Mounted=a,b A_dir=JB10a B_dir=JB10b

14) To monitor the Integral Volume set, enter:

Single-volume Interchange Level:

#>df -k /mnt

Automount Interchange Level:

#>df -k /mnt Note: This command will display the total capacity of all the surfaces already accessed

#>udfdf -t /mnt

#>udfdf -f -a 0 /mnt

Note: QStar recommends reviewing the explanation for the udfdf command in Chapter 9 - Command Reference of this manual.

15) To monitor the cache status of an Integral Volume set, enter:

mmparam { set_name | mount_point}

Example - to monitor the cache status of the Integral Volume set Test, enter:

#>mmparam /mnt

#>mmparam Test

16) To unmount the Integral Volume set, enter:

umount /mount_point

umountiv set_name

Example - to unmount the Integral Volume set Test on the mount point /mnt, enter:
#>umount /mnt

#>umountiv Test (For Linux and HP-UX platforms)

Note: QStar does not recommend using the umount command for Linux or HP-UX platforms; this ensures the Integral Volume
set is completely unmounted. Please refer to Chapter 6 - Migration Manager in this manual for more detailed information.

17) To unload the media from the drive, enter:

#>vlexport jb1 1

Page 38 of 88
 MANAGING QSTAR CD/DVD MASTER PRODUCT WITH
ISO 9660 AND UDF FILE SYSTEMS
This manual describes how to create an Integral Volume set for CD/DVD-ROM devices and how to set-up, configure and use
the QStar CD/DVD Master product. The QStar Software can control CD/DVD-ROM media written with the ISO 9660 or the
UDF file systems by using the CD/DVD Axxess product. Both products allow CD/DVD-ROMs to be bound together as an
Integral Volume set. The Integral Volume is created with a cache and each CD/DVD-ROM is seen as a separate directory
within the Integral Volume set. The CD/DVD-R media are recorded using the QStar CD/DVD Master product and if required
the media, once recorded can be automatically added to a specified Integral Volume set.

Page 39 of 88
MANAGING QSTAR CD/DVD MASTER SOFTWARE FOR
ISO/UDF IMAGES RECORDED AS DISC-AT-ONCE
The following sections will give a detailed walk through on how to use the QStar CD/DVD Master Software, create an
ISO/UDF image and record it to CD/DVD-R media and how to use the QStar CD/DVD Axxess Software to manage the jukebox
and the Integral Volume sets.

The QStar Software also allows the use of CD/DVD-RW with the disc-at-once recording procedure. This media can only
be used to record an ISO image and should not be used to write a UDF image, this is only supported by QStar with
CD/DVD-R media. Before use the media must be fully erased using the vlerase command.

The walk through will be divided into the following main sections:

A) Configuration of an Integral Volume set for CD/DVD-ROM media.

B) Setting the CD/DVD-R write options and parameters.

C) Description of how to create an ISO/UDF image.

D) Description of how to write an ISO/UDF image to the CD/DVD-R media.

E) Description of how to manage the delayed jobs list.

F) Display an error condition during the recording procedure.

Note: In the walk through described below a CD-R jukebox is used in the examples, but the explanation is also valid for DVD-R
jukeboxes.

Page 40 of 88
INTEGRAL VOLUME SET CONFIGURATION FOR A CD/DVD-
ROM JUKEBOX
In this section an Integral Volume set will be created, some media will be added to it, and the Integral Volume set will be
mounted. This initial procedure is explained because mounting an Integral Volume set that does not contain any media is not a
valid operation. In order to have the data written on the new CD/DVD-ROM media available the Integral Volume set must be
mounted. If the Integral Volume set is mounted any new CD/DVD-ROM media recorded may be automatically added to the
Integral Volume set allowing the data recorded on the CD/DVD-ROM to be accessible online.
This walk through is described for both ISO and UDF file systems on the QSTAR CD/DVD AXXESS PRODUCT -
MANAGING CD-ROM/DVD-ROM MEDIA section on this chapter. QStar recommends gaining some experience using the
QStar CD/DVD Axxess Software before using the QStar CD/DVD Master Software.

SETTING THE CD/DVD-R WRITE PROCEDURE

The QStar CD/DVD Master Product can be used from the server that the QStar Software is installed on. It can also be accessed
from a client machine to create an ISO/UDF image and record it to a CD/DVD-R media.

The QStar CD/DVD Master product allows two methods of recording.

A) Direct write

The Direct write procedure sends the ISO/UDF image data directly to the CD/DVD-R drive and the ISO/UDF image is not
saved on the sever or on the remote client machine hard disk.

To use the Direct write procedure QStar recommends the following:

1) Locate the CD/DVD-R drives and the CD/DVD-ROM drives on separate buses in the jukebox and connected to the server
via different SCSI cards.

2) Only allow the Direct write procedure if the remote client machine is in a fast network environment.

These recommendations will avoid the “buffer underun” problem from occurring.

Note: Selecting the Direct write procedure does not deny the Delayed write procedure.

B) Delayed write

The ISO/UDF image is first transferred into an Images Directory on the server specified by the System Administrator and will
then be recorded according to the scheduled settings or can be canceled if required.

Note: Selecting the Delayed write procedure will deny the Direct write procedure.

Page 41 of 88
Displaying the Delayed Commands under VL Scheduler Control
QStar creates a special file called “conf” under the /opt/QStar/vl/files directory. The conf file keeps all the configuration
information for the QStar Commands that can 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.
The System Administrator can use the delayed queue commands option to manage and monitor the delayed commands in the
delayed jobs queue list by using the vlqlist command.

The options available in the conf file are represented with a key word that identifies the delayed command that can be under the
VL scheduler's control.

The key words are as follows:

RECORD: Option related to the Recording procedure.

COPY: Option related to the Copy Disk procedure.
CMP: Option related to the Compare Procedure, which follows the Copy Disk procedure.
REUSE: Option related to the Compaction procedure.
ERASE: Option related to the Erase procedure.
ARC: Option related to the Archiving procedure.

Below the content of the conf file:

# VL Configuration File

RECORD Images Dir Path = "/opt/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"
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 = "No"
Exportfs Root Dir = "/opt/QStar/fsi/mnt"
# 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"
SCSI Server Port = "5001"

Page 42 of 88
JB Server Port = "5002"
MM Server Port = "5003"
VL Server Port = "5004"
Mirror Slave Port = "5015"
Centera Server Port = "5281"
Crypto Server Port = "5007"
Qmage Server Port = "5006"

Note: In this section only the VL Configuration option for the CD/DVD-R recording procedure will be explained.

Displaying and Setting the General VL Configuration Properties

Keep Done Records = "7"

Number of latest records kept in the delayed jobs queue list. The default number is 7; the System Administrator can change this
by editing the /opt/QStar/vl/files/conf file and typing the new value.

Displaying the VL Configuration CD/DVD-R Write Properties

RECORD Images Dir Path = "/opt/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"

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): Maximum Size of the Images Directory.

Direct: Type of recording procedure allowed.

Allowed Hosts: Hosts allowed doing the Direct write procedure.

Delayed Start: Start Time and Stop Time when the VL scheduler processes 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.

Max Parallel Recording: The Number of parallel recordings defines the number of images that can be recorded at the same
time, the value entered defines the number of drives that can be used simultaneously for recording.
A “0”value ensures that all cd/dvd-r drives available will be used.

Setting the VL Configuration CD/DVD-R Direct Write Properties

# RECORD Direct - {Prohibited | Allowed | Allowed Hosts}
RECORD Direct = "Prohibited"
RECORD Allowed Hosts = ""
RECORD Max Parallel Recording = "0"

By default, the Delayed write is allowed and the Direct write is Prohibited. Select Allowed or Allowed Hosts to enable the
Direct write procedure.

Page 43 of 88
Select the Allowed option to enable the Direct write procedure for all users.

RECORD Direct = "Allowed"

Select the Allowed Hosts option to enable the Direct write procedure for specific users only.

RECORD Direct = "Allowed Hosts"

Specify in the Allowed Hosts option, the name of the hosts that are allowed Direct write access.

RECORD Allowed Hosts = "Host1,Host2,Host3,Host4"

In the example a generic Host# name is used, the Host name must be separated with a comma and there is no limitation on the
number of hosts that can be specified.

Note: Also the Delayed write will be enabled for all users.

Specify the number of drives that can be used for recording. By default all drives available can be used. Please refer the next
section for more information about this option .

RECORD Max Parallel Recording = "0"

Setting the VL Configuration CD/DVD-R Delayed Write Properties

RECORD Images Dir Path = "/opt/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"

By default, the Delayed write is always allowed with the below default delayed write options:

A) Images Dir Path: /opt/QStar/vl/files/cd_images

B) Image Max Size (Mb): 650 Mb

C) Delayed Start: 0:0 0:0

The 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.

D) Max Parallel Recording: 0

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

In the example, default Delayed write options are set as follows:

RECORD Images Dir Path = "/export/home/cd_images"

RECORD Images Max Size Mb = "2000"
RECORD Delayed Start = "23:38 06:38"
RECORD Max Parallel Recording = "2"

Page 44 of 88
To create the directory where the images will be temporarily transferred and kept until the delayed jobs are completely
processed, enter:

#>mkdir /export/home/cd_images

Note: Ensure the hard disk partition where the Images Directory was created has sufficient space for the required images.

Note1: There may be a requirement for the users of the QStar CD/DVD Master Software to transfer the image to the cd_images
directory from a client machine. To allow the users to access the Images Directory, the correct permissions must be applied to
the directory.

Maximum Parallel Recording and Drive Usage Configuration

By default, QStar Software allows all available CD/DVD-R drives within the jukebox for parallel recording. The System
Administrator can select a serial or parallel recording configuration and which drives should be used for which purpose. The
options to configure this selection is the Max Parallel Recording in the /opt/QStar/vl/files/conf file and the jbdrive command.
A jukebox with multiple drive and media types can be tailored to suit the amount of reading and writing required by manually
setting each drives capability.

A) The option Max Parallel Recording can be used to specify how many drives can be used for recording at the same time. A
"0" value ensures that all CD/DVD-R capable drives available will be used. Setting a non-zero value will specify how many
drives can be used for recording. If the jukebox has multiple drive types, then the most appropriate drive type will be
selected first, for example, a CD/DVD-R drive will be selected in preference to a multi-function drive that also supports
DVD-RAM. This ensures the drive/drives that have the greater media type support are available for read/write requests on
any media type within the jukebox.

B) With the jbdrive command it is possible to configure each drives profile/priority in order to allow/deny the specified drive
to be used for recording or reading. The System Administrator can configure which drives are dedicated to which media type
over-riding the drives default capability, this can allow CD/DVD-R drives to be installed on a separate SCSI bus dedicated for
recording and with the jbdrive command, configure the drives on this SCSI bus for this purpose.

The usage for the jbdrive command is:

jbdrive [-H host_name] [-nfbr] [-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}] device_name drive_number

To set the priority for the usage of the drive, use the jbdrive command with the following flag:

-u [priority_number | rrr:www:rw | auto | default]

The priority defines the order in which the drives are used by jbscheduler when it is looking for an appropriate drive. Example,
in a jukebox with 4 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.

Below is displayed an example, using a CD/DVD jukebox with 4 Multi-function drives and 2 CD/DVD-ROM drives and
discrides how to use the profile and the Maximun Parallel Recording options.

Page 45 of 88
The jbstatus command shows the following information:

#>jbstatus –d jb
Drive 1: cd-rom cd-r cd-rw dvd-rom dvd-r dvd-ram dvd-rw dvd-rw-s online empty
Drive 2: cd-rom cd-r cd-rw dvd-rom dvd-r dvd-ram dvd-rw dvd-rw-s online empty
Drive 3: cd-rom cd-r cd-rw dvd-rom dvd-r dvd-ram dvd-rw dvd-rw-s online empty
Drive 4: cd-rom cd-r cd-rw dvd-rom dvd-r dvd-ram dvd-rw dvd-rw-s online empty
Drive 5: cd-rom dvd-rom online empty
Drive 6: cd-rom dvd-rom online empty

The configuration will be the following:

A) Configure 2 drives for parallel recording

B) Drives 1 and drive 2 will be used always only for recording (read CD/DVD-ROM media will be denied)
C) Drive 3 will be available for reading and writing
D) Drive 4 will be used for reading only

The following procedure would be used:

A) Set the /opt/QStar/vl/files/conf file with the option RECORD Max Parallel Recording = “2”
B) jbdrive -p cd-r -p cd-rw -p dvd-ram -p dvd-r -p dvd-rw -p dvd-rw-s jb 1
C) jbdrive -p cd-r -p cd-rw -p dvd-ram -p dvd-r -p dvd-rw -p dvd-rw-s jb 2
D) jbdrive -p cd-rom -p dvd-ram -p dvd-rom jb 4

Note: Drive 3 will be available for reading and writing.

The jbstatus command now shows the following new information:

#>jbstatus –d jb
Drive 1: cd-r cd-rw dvd-r dvd-ram dvd-rw dvd-rw-s online empty
Drive 2: cd-r cd-rw dvd-r dvd-ram dvd-rw dvd-rw-s online empty
Drive 3: cd-rom cd-r cd-rw dvd-rom dvd-r dvd-ram dvd-rw dvd-rw-s online empty
Drive 4: cd-rom dvd-rom dvd-ram online empty
Drive 5: cd-rom dvd-rom online empty
Drive 6: cd-rom dvd-rom online empty

Note: The values set by the jbdrive command are non-persistent, so a script would need to be applied in a system start-up file to
ensure this configuration is always implemented.

Page 46 of 88
CREATING AN ISO IMAGE
The mkiso command is used to create an ISO 9660 file system image from a specified file tree which may later be recorded
onto a CD/DVD-R media and it includes several options that will cover all the ISO standard requirements.

mkiso [-x exclude_path] [-c charset] [-s system_id] [-v volume_id][-V volume_set_id] [-p preparer_id] [-q quiet]
[-P publisher_id] [-a application_id] [-o image_file_name|-] [-R] [-J] [-D] [-S][cd_dir_name=]path [...]

Note: If the -o option is omitted the mkiso command only calculates the size of the image and exits.

Note1: On Unix platforms the default file system type is ISO-R (ISO 9660 with RockRidge extension).

The options available with the mkiso command are described as follows:

-R
Use RockRidge extensions with the ISO-9660 standard. These extensions are mainly used for UNIX systems.

-J
Use 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
Use 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.

-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
Set optional volume_set_id, preparer_id, publisher_id, system_id or application_id fields of the ISO volume descriptor.

Page 47 of 88
-c charset
Specifying 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
Exclude 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.

[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.

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 API (3)) and an error message is printed to stderr.

Examples of Creating an ISO Image

1) To create an ISO CD/DVD image at /home/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 QSTAR_SOFTWARE_UNIX, enter:

#>mkiso -v QSTAR_SOFTWARE_UNIX -o /home/cdimage.iso /usr/docs/part2

2) To create an ISO CD/DVD image with Joliet extensions at /home/cdimage.iso and copy 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 QSTAR_SOFTWARE_UNIX and excludes files with names ending with .bak, enter:

#>mkiso -J -x '*.bak' -v QSTAR_SOFTWARE_UNIX -o /home/cdimage.iso /part2=/usr/docs/part2

/part3=/usr/docs/part3

3) To create an ISO CD/DVD image at /home/QStar_Software_Unix.iso using the /Release48 subtree as the root of the
CD/DVD with the name of the CD/DVD (Volume Label) set to QSTAR_SOFTWARE_UNIX, enter:

#>mkiso -v QSTAR_SOFTWARE_UNIX -o /home/QStar_Software_Unix.iso /Release48

Page 48 of 88
CREATING A UDF IMAGE
The mkudf command is used to create a UDF file system image containing file trees specified by path arguments, which may
later be recorded onto an optical or CD/DVD-R media. 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). The UDF Revison Level of the
UDF file system can be 1.50, 2.00 or 2.01.

mkudf -o [image_file|-] [-b block_size] [-m{rewritable|worm}] [-l logical_volume_identifier] [-u{150|200|201}] [-t]

[dir_name=]path ...

The options available with the mkudf command are described as follows:

-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. The 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 media type: rewritable or WORM. The default is worm.

Examples of Creating a UDF Image

1) To create a UDF CD/DVD image at /home/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) set to QSTAR_SOFTWARE_UNIX, enter:

#>mkudf -l QSTAR_SOFTWARE_UNIX -o /home/cdimage.udf /usr/docs/part2

2) To create a UDF CD/DVD image at /home/cdimage.udf and copy 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 (logical_ volume_identifier) set to
QSTAR_SOFTWARE_UNIX, enter:

#>mkudf -l QSTAR_SOFTWARE_UNIX -o /home/cdimage.iso /part2=/usr/docs/part2

/part3=/usr/docs/part3

3) To create a UDF CD/DVD image at /home/QStar_Software_Unix.udf using the /Release48 subtree as the root of the
CD/DVD with the name of the CD/DVD (logical_ volume_identifier) set to QSTAR_SOFTWARE_UNIX, enter:

#>mkudf -l QSTAR_SOFTWARE_UNIX -o /home/QStar_Software_Unix.udf /Release48

Page 49 of 88
WRITING AN IMAGE FILE TO THE CD/DVD-R MEDIA
In this section using the vlrecord command both Direct and Delayed write procedures will be described in the examples using
ISO as the file system type. The same procedures are also applicable to the UDF file system.

Starting the RECORD Procedure

The vlrecord command is used to record an ISO/UDF image to a CD/DVD-R media. The CD/DVD-R media is specified by the
device_name:shelf_number argument. If “any” option is specified instead of a shelf number then the 1st available blank
CD/DVD-R in the storage device will be used. The image location and name is specified by the image_path argument.

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]

The options available with the vlrecord command are described as follows:

-H host_name
Specifies the name of the host where the device is connected. Without this option, the local host is used.

-v Verbose output.

-x speed_X
Specifies the recording speed at which all CD/DVDs will be recorded. Without this option the recording speed is selected
automatically based on the memory buffer filling time. The options available are any number below the maximum write speed of
the drive (i.e. 2x =2 3x = 3 4x =4), or Max.
The selection of “Auto” as the recording speed ensures that the server will automatically detect the writing speed. With a buffer
on the server, data is transferred from the client machine to the buffer first and then from the buffer to the drive. The server
waits until the buffer is full before it starts to write. It calculates the speed of transfer for the first 4MB (buffer size) of data and
sets the appropriate write speed for the drive. The auto speed selection of the software may not always be accurate as the server
assumes that all transfers will be made at the same speed calculated for the first 4MB.
If the recording procedure returns an error, the speed is not correct; a write speed test must then be carried out. This procedure is
described in the Burn Test Procedure Before Starting the Write Operation section of this manual, QStar recommends
reading the section before starting the recording procedure to determine the correct write speed for your drives.

-b buffer_Mb
Specifies memory buffer size used for recording. The default value is 4 Mb.

-t
The Laser OFF test mode is used to test and verify the optimum write speed to be used with the CD/DVD-R drive. When the
Laser OFF test mode is specified, the Software and the 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
The Write OFF test mode is used to measure the data transfer rate. When the Write OFF test mode is specified, the Software
will send the data to the drive, but will not perform the write operation on the media.

Note: For more detailed information about the test procedure, please refer to “Burn Test Before Start Write Operation”
section of this manual.

Page 50 of 88
-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).

-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 “RECORD
Delayed Start” field in the /opt/QStar/vl/files/conf file.

Note: The -d flag can only be used 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 date values are supplied as defaults.

-m mail_addr
Specifies the E-mail address to which confirmation is sent when the job has been completed. An E-mail notification can be sent
reporting the exit status information of the recording operation using the -m option and specifying the E-mail address of the
person who should receive the notification.

-n number_of_copies
Specifies the number of copies of the same ISO/UDF image that will be recorded to the CD/DVD-R media. Without this option
only one ISO/UDF image will be recorded. This option is only available with the Delayed write procedure in conjunction with
any option and will be ignored if is used with the Direct write procedure.

-p
Sets the media type for the recording session. If the media type is omitted from the syntax of the command the first
available media in the jukebox, starting from the shelf with the lowest number, will automatically be used. If the jukebox
contains different types of media, (i.e. cd-r, dvd-r, dvd-rw, cd-rw, dvd-ram) the software will select the first available
media with a capacity that is equal to or larger than the ISO/UDF image, starting from the shelf with lowest number.

-V
Specifies verification mode. The vlrecord command reads recorded data back and compares with the source image.

Note: The recording is a long procedure, QStar suggests using the -v option to track the progress of the recording.

Page 51 of 88
Selecting Target Jukebox
In the vlrecord command the -H host_name option is used to select the hostname of the server to which the jukebox or
jukeboxes are connected. If the QStar Software is installed on the same server as the jukebox (es), the -H host_name option is
not required because by default the local host is used.
If the jukebox to use for recording the CD/DVD-R media is connected remotely, type the host name using the -H host_name
option.

Note: If the host name was not already inserted in the system /etc/hosts file, use the IP address.

1) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb and
connected to the remote server production1, enter:

#>vlrecord -H production1 jb:1 /home/QStar_Software_Unix.iso

Selecting Target Shelves

In the vlrecord command the device_name:{shelf_number{a|b}|any} argument is used to specify the target device and shelves
(media) that will be used for recording. If the any option is selected the first available CD/DVD-R media in the jukebox will be
automatically used by the QStar Software for the recording procedure. If multiple jukeboxes are connected, select the name of
the required jukebox in the device_name argument.

1) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb,
enter:

#>vlrecord jb:1a /home/QStar_Software_Unix.iso

2) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb,
enter:

#>vlrecord jb:any /home/QStar_Software_Unix.iso

Selecting Media Type

1) To record the /home/QStar_Software_Unix.iso image to the first available CD-R media in the jukebox identified as jb, enter:

#>vlrecord –p cd-r jb:any /home/QStar_Software_Unix.iso

2) To record the /home/QStar_Software_Unix.iso image to the first available DVD-R media in the jukebox identified as jb,
enter:

#>vlrecord –p dvd-r jb:any /home/QStar_Software_Unix.iso

Page 52 of 88
Starting the CD/DVD-R Direct Write Procedure
The Direct write procedure is used with an existing ISO/UDF image; once the recording is completed the existing ISO/UDF
image will not be removed from the server hard disk. In the examples displayed below the recording speed is set to 2x and the -v
Verbose output option will be used to track the progress of the recording. QStar recomends to always use the -v Verbose
output option because the recording process is a long procedure.

The vlrecord command allows the use of the Direct write procedure only if it was enabled in the RECORD Direct entry on the
conf VL Configuration file. If the System Administrator tries to use the Direct write procedure without enabling it, the
following error messages will be returned to the vlrecord command:

vlrecord: host_name: Direct record prohibited: Operation not supported

Direct Write Procedure Using the Any Shelf Option

Using the Any option on the vlrecord command, the target shelf will be chosen by the QStar Software.

1) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb
using the Direct write procedure, enter:

#>vlrecord -v -x 2x -s Test jb:any /home/QStar_Software_Unix.iso

Note: In the example, the -s set_name option is used to add the new CD/DVD-ROM created to the Integral Volume set Test. The
new media will then be mounted immediately after the recording has been completed and the data will be available online.

2) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb
using the Direct write procedure, enter:

#>vlrecord -v -x 2x -m [email protected] jb:any /home/QStar_Software_Unix.iso

Note: In the example, the -m mail_addr option is used to send an E-mail notification reporting the exit status information of the
recording operation.

3) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb
using the Direct write procedure, enter:

#>vlrecord -v -x 2x -s Test -m [email protected] jb:any /home/QStar_Software_Unix.iso

Note: In the example, both -s set_name and -m mail_addr options are used.

4) To record the /home/QStar_Software_Unix.iso image to the first available DVD-R media in the jukebox identified as jb
using the Direct write procedure, enter:

#>vlrecord -v -x 2x -s Test -V –p dvd-r jb:any /home/QStar_Software_Unix.iso

Note: In the example, the-s set_name, the -V verification and -p dvd-r options are used.

Page 53 of 88
Direct Write Procedure Using a Specified Shelf
1) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb using
the Direct write procedure, enter:

#>vlrecord -v -x 2x -s Test jb:1a /home/QStar_Software_Unix.iso

Note: In the example, the -s set_name option is used to add the new CD/DVD-ROM created to the Integral Volume set Test. The
new media will then be mounted immediately after the recording has been completed and the data will be available online.

2) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb using
the Direct write procedure, enter:

#>vlrecord -v -x 2x -m [email protected] jb:1a /home/QStar_Software_Unix.iso

Note: In the example, the -m mail_addr option is used to send an E-mail notification reporting the exit status information of the
recording operation.

3) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb using
the Direct write procedure, enter:

#>vlrecord -v -x 2x -s Test -m [email protected] jb:1a /home/QStar_Software_Unix.iso

Note: In the example, both -s set_name and -m mail_addr options are used.

4) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb
using the Direct write procedure, enter:

#>vlrecord -v -x 2x -s Test -V jb:1a /home/QStar_Software_Unix.iso

Note: In the example, the -s set_name and the -V verification options are used.

Page 54 of 88
Information Displayed During the Direct Write Procedure
In order to displays the events performed during the record the -v Verbose output option must be used with the vlrecord
command, the Memory Buffer and Drive Buffer will then depict their relative values.

1) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb
using the Direct write procedure, enter:

#>vlrecord -v -x 2x jb:any /home/QStar_Software_Unix.iso

jb:0 setup
jb:0 ready. Recording started
jb:0 5Mb of 85Mb (2560 blks)299Kb/s, Total:248Kb/s, buffers:memory 95%, drive 84% full
jb:0 10Mb of 85Mb (5120 blks)300Kb/s, Total:271Kb/s, buffers:memory 95%, drive 84% full
jb:0 15Mb of 85Mb (7680 blks)300Kb/s, Total:280Kb/s, buffers:memory 95%, drive 86% full
jb:0 20Mb of 85Mb(10240 blks)300Kb/s, Total:284Kb/s, buffers:memory 95%, drive 84% full
jb:0 25Mb of 85Mb(12800 blks)299Kb/s, Total:287Kb/s, buffers:memory 95%, drive 84% full
jb:0 30Mb of 85Mb(14848 blks)297Kb/s, Total:289Kb/s, buffers:memory 95%, drive 86% full
jb:0 35Mb of 85Mb(17408 blks)299Kb/s, Total:291Kb/s, buffers:memory 95%, drive 84% full
jb:0 39Mb of 85Mb(19968 blks)300Kb/s, Total:292Kb/s, buffers:memory 95%, drive 84% full
jb:0 44Mb of 85Mb(22528 blks)300Kb/s, Total:293Kb/s, buffers:memory 95%, drive 84% full
jb:0 49Mb of 85Mb(25088 blks)300Kb/s, Total:293Kb/s, buffers:memory 95%, drive 43% full
jb:0 54Mb of 85Mb(27648 blks)300Kb/s, Total:294Kb/s, buffers:memory 95%, drive 84% full
jb:0 59Mb of 85Mb(30208 blks)300Kb/s, Total:294Kb/s, buffers:memory 95%, drive 84% full
jb:0 64Mb of 85Mb(32768 blks)364Kb/s, Total:293Kb/s, buffers:memory 95%, drive 34% full
jb:0 69Mb of 85Mb(34816 blks)300Kb/s, Total:295Kb/s, buffers:memory 95%, drive 84% full
jb:0 74Mb of 85Mb(37376 blks)300Kb/s, Total:295Kb/s, buffers:memory 95%, drive 84% full
jb:0 78Mb of 85Mb(39936 blks)300Kb/s, Total:296Kb/s, buffers:memory 95%, drive 84% full
jb:0 83Mb of 85Mb(42496 blks)300Kb/s, Total:296Kb/s, buffers:memory 75%, drive 84% full
jb:0 85Mb of 85Mb(43971 blks)103Kb/s, Total:294Kb/s, buffers:memory 0%, drive 45% full
jb:0 closing
85 Mb done

Note: The shelf used for recording is displayed as "0" because the any option was used in the example.
Additional information relating to the write will be reported in the QStar /opt/QStar/log/syslog file.

Page 55 of 88
Starting the CD/DVD-R Delayed Write Procedure
If the Delayed write procedure is used with an existing ISO/UDF image, the image is first transferred to the Images Directory
specified in the RECORD Images Dir Path entry of the conf VL Configuration file. Then in accordance with the RECORD
Delayed Start Time settings also specified in the conf VL Configuration file, the image will be recorded to the CD/DVD-R
media. When the record procedure has completed the existing ISO/UDF image will be not removed from the server hard disk
however, the transferred image will be removed from the Images Directory.

To select the Delayed write procedure the System Administrator will need to use the -j delayed_job_name option and assign a
name to the job using the vlrecord command. The job name must be a unique name, if the same job name is already present on
the delayed jobs queue list then the job will be denied and the following message will be returned to the vlrecord command:

vlrecord: QStar_Unix_Release: Can't add to VL-queue: Record already exists

By default, the recording Start Time will follow the setting inserted in the RECORD Delayed Start Time setting specified in
the conf VL Configuration file. The System Administrator can change the recording Start Time specifying the date and time
the jobs should be executed on the delayed jobs list using the -d [mmdd]HHMM | [cc]yymmddHHMM option using the
vlrecord command.
Note: If the Delayed write procedure is interrupted, the interruption will cancel the delayed job request and the partial image
that has been transferred will be removed from the Images Directory.

Delayed Write Procedure Using the Any Shelf Option

Using the Any option on the vlrecord command, the target shelf will be chosen by the QStar Software.
In the examples, the QStar_Release is the name assigned to the delayed_job_name option.

1) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb
using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -j QStar_Release jb:any /home/QStar_Software_Unix.iso

Note: In the example, the -s set_name option is used to add the new CD/DVD-ROM created to the Integral Volume set Test. The
new media will then be mounted immediately after the recording has been completed and the data will be available online.

2) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb
using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -m [email protected] -j QStar_Release jb:any /home/QStar_Software

_Unix.iso

Note: In the example, the -m mail_addr option is used to send an E-mail notification reporting the exit status information of the
delayed recording operation.

3) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb
using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -m [email protected] -j QStar_Release jb:any /home/QStar_

Software_Unix.iso

Note: In the example, both -s set_name and -m mail_addr options are used.

Page 56 of 88
4) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb
using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -j QStar_Release -d 2330 jb:any /home/QStar_

Software_Unix.iso

Note: In the example, the -d option is used to set the Delayed Start Time to 23:30.

5) To record the /home/QStar_Software_Unix.iso image to the first available DVD-R media in the jukebox identified as jb
using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -V –p dvd-r -j QStar_Release jb:any /home/QStar_

Software_Unix.iso

Note: In the example, the-s set_name, the -V verification and -p dvd-r options are used.

Delayed Write Procedure Using a Specified Shelf

In the examples, the QStar_Release is the name assigned to the delayed_job_name option.

1) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb using
the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -j QStar_Release jb:1a /home/QStar_Software_Unix.iso

Note: In the example, the -s set_name option is used to add the new CD/DVD-ROM created to the Integral Volume set Test. The
new media will then be mounted immediately after the recording has been completed and the data will be available online.

2) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb using
the Delayed write procedure, enter:

#>vlrecord -v -x 2x -m [email protected] -j QStar_Release jb:1a /home/QStar_Software

_Unix.iso

Note: In the example, the -m mail_addr option is used to send an E-mail notification reporting the exit status information of the
recording operation.

3) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb using
the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -m [email protected] -j QStar_Release jb:1a /home/QStar_

Software_Unix.iso

Note: In the example, both -s set_name and -m mail_addr options are used.

4) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb using
the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -j QStar_Release -d 2330 jb:1a /home/QStar_Software_

Unix.iso

Note: In the example, the -d option is used to set the Delayed Start Time to 23:30.

Page 57 of 88
5) To record the /home/QStar_Software_Unix.iso image to the CD/DVD-R media in shelf 1 in the jukebox identified as jb
using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -s Test -V -j QStar_Release jb:1a /home/QStar_Software_Unix.iso

Note: In the example, the -s set_name and the -V verification options are used.

Delayed Write Procedure Using the Any Option and Multiple Copy
The Delayed write procedure allows creating multiple copies of CD/DVD using the same ISO/UDF image specifying the
-n number_of_copies and any options on the vlrecord command.

In the examples, the QStar_Release is the name assigned to the delayed_job_name option.

1) To record the /home/QStar_Software_Unix.iso image to the first three available CD/DVD-R media in the jukebox identified
as jb using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -j QStar_Release -n 3 jb:any /export/home/QStar_Software_Unix.iso

If the -n number_of_copies option is used with a specified shelf an error is returned to the vlrecord command.

Below is an example of the error returned:

#>vlrecord -v -x 2x -j QStar_Release -n 3 jb:1a /home/QStar_Software_Unix.iso

#>vlrecord: several copies on one shelf requested: Invalid argument

Note: The specified shelf 1 is an invalid argument with -n number_of_copies option.

2) To record the /home/QStar_Software_Unix.iso to the first three available CD/DVD-R media in the jukebox identified as jb
using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -j QStar_Release -s Test -n 3 jb:any /home/QStar_Software_

Unix.iso

Note: If the -s set_name option is used with the -n number_of_copies option, the first media that will be recorded as first copy
will be added automatically to the Integral Volume set and the other media will be available in the jukebox but will not be
added to the Integral Volume set.

Page 58 of 88
Information Displayed During the Delayed Write Procedure
In order to display the events performed during the transfer of the ISO/UDF image to the Images Directory the -v Verbose
output option must be used with the vlrecord command.

1) To record the /home/QStar_Software_Unix.iso image to the first available CD/DVD-R media in the jukebox identified as jb
using the Delayed write procedure, enter:

#>vlrecord -v -x 2x -j QStar_Release jb:any /home/QStar_Software_Unix.iso

QStar_Release 8Mb of 85Mb 10666Kb/s, Total: 1590Kb/s

QStar_Release 17Mb of 85Mb 351Kb/s, Total: 1519Kb/s
QStar_Release 25Mb of 85Mb 659Kb/s, Total: 1516Kb/s
QStar_Release 33Mb of 85Mb 516Kb/s, Total: 1512Kb/s
QStar_Release 41Mb of 85Mb 1122Kb/s, Total: 1500Kb/s
QStar_Release 49Mb of 85Mb 2133Kb/s, Total: 1459Kb/s
QStar_Release 58Mb of 85Mb 10666Kb/s, Total: 1437Kb/s
QStar_Release 66Mb of 85Mb 415Kb/s, Total: 1423Kb/s
QStar_Release 74Mb of 85Mb 64000Kb/s, Total: 1427Kb/s
QStar_Release 82Mb of 85Mb 10666Kb/s, Total: 1433Kb/s
QStar_Release 85Mb of 85Mb 2064Kb/s, Total: 1426Kb/s
QStar_Release 85Mb done

Note: The example shows that the transfer has completed without any errors and now the ISO image is ready to be recorded to
the first available shelf that contains a Blank CD/DVD-R media.
Additional information relating to the transfer will be reported in the QStar /opt/QStar/log/Syslog file.

Page 59 of 88
Displaying the Delayed Jobs Status in the Delayed Jobs Queue List
The vlqlist command is used to list all the information for the delayed jobs present in the delayed jobs queue list, which is
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 System Administrator using the vlqlist command can manage and monitor the delayed jobs in the
delayed jobs queue list.

vlqlist [-H host_name] [-j [a][d][c][m][r][e][A][i][o]] [-s [w][s][d][e]] [-l] [-h sender_hostname] [-u user_id]

The options available with the vlrecord command are described as follows:

-H host_name
Specifies the name of the host where the device is connected. Without this option, the local host is used.

-j [d][c][m][r][e][g][A]
The –j flag allows specific job type filters to be used. Multiple filters may be used together on the same command line.

d - Display only vlrecord jobs.

c - Display only vlcopy jobs.
m - Display only vlcmp jobs.
r - Display only vlreuse jobs.
e - Display only vlerase jobs.
A - Display only mmarc jobs.
i - Display only incremental copy jobs.
o - Display only offline SDF mirror synchronization jobs.

Note: By default, all types of jobs are displayed.

-s [w][s][d][e]
The -s flag allows specific job state filters to be used. Multiple filters may be used together on the same command line.

w - Display all jobs waiting for execution.

s - Display all jobs that have started.
d - Display all jobs that have completed without error.
e - Display all jobs that have completed with error.

Note: By default all types of job states are displayed.

-h sender_hostname
Display all records that came from the host specified by sender_hostname

-u user_id
Display all records that originated from the user specified by user_id.

-l
Output long format.

Page 60 of 88
Displaying the Delayed Jobs Status for a Single Copy
The delayed jobs listed in the vlqlist command output are displayed in the order they were added to the delayed jobs queue.

1) To display the delayed job status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/03/10_21:43 QStar_Release Record Waiting 0:natasha

In the example, the job with the name QStar_Release is present on the delayed jobs queue list and was registered on the list
with Job ID 1 and Registration Date 2002/03/10 at 21:43 and currently this job has a Status of Waiting.
The Delayed Start Date information is empty because the scheduling procedure follows the general settings made in the
RECORD Delayed Start Time setting specified in the conf VL Configuration file.

Note: The User ID "0" is the User root.

2) To display the delayed job status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/03/10_21:43 QStar_Release Record Started 0:natasha 2002/03/10_21:44

The Status of the job with Job ID 1 has changed to Started and the recording was started at 2002/03/10_21:44 Delayed Start
Date.

3) To display the delayed job status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/03/10_21:43 QStar_Release Record Done 0:natasha 2002/03/10_21:44 2002/03/10_21:50

The Status of the job with Job ID 1 has changed to Done and the recording has been completed without any errors at
2002/03/10_21:50 End Date.
Note: If the Status displays Error the recording procedure has failed to write the image on the media.
Note1: The image transferred to the Images Directory will be removed in both cases, whether the recording procedure was
successful, or if it ended with an error.

Page 61 of 88
Displaying the Delayed Jobs Status for a Multiple Copy
The delayed jobs listed in the vlqlist command output are displayed in the order they were added to the delayed jobs queue. If
the Number of Copies option is used to create multiple CD/DVD-ROM media with the same image, a job will be created for
each copy in the delayed jobs queue. These jobs will differ in the Job ID and the copy number will be added to Job Name. The
jobs will be processed according to the priority order specified. The job at top of the delayed jobs queue list has the highest
priority.

1) To display the delayed jobs status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/03/10_21:43 QStar_Release<#1 copy> Record Waiting 0:natasha
2 2002/03/10_21:43 QStar_Release<#2 copy> Record Waiting 0:natasha
3 2002/03/10_21:43 QStar_Release<#3 copy> Record Waiting 0:natasha

In the example, the jobs with the name QStar_Release<#1 copy>, QStar_Release<#2 copy>, QStar_Release<#3 copy> are
present in the delayed jobs queue list. They were registered in the list respectively with Job ID 1, Job ID 2, Job ID 3 and
Registration Date 2002/03/10 at 21:43. Currently these jobs have a Status of Waiting. The Delayed Start Date information
is empty because the scheduling procedure follows the general settings made in the RECORD Delayed Start Time setting
specified in the conf VL Configuration file

Note: The User ID "0" is the User root.

2) To display the delayed jobs status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/03/10_21:43 QStar_Release<#1 copy> Record Started 0:natasha 2002/03/10_21:44
2 2002/03/10_21:43 QStar_Release<#2 copy> Record Waiting 0:natasha
3 2002/03/10_21:43 QStar_Release<#3 copy> Record Waiting 0:natasha

The Status of the job with Job ID 1 has changed to Started and the recording was started at 2002/03/10_21:44 Delayed Start Date.

3) To display the delayed jobs status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/03/10_21:43 QStar_Release<#1 copy> Record Started 0:natasha 2002/03/10_21:44
2 2002/03/10_21:43 QStar_Release<#2 copy> Record Started 0:natasha 2002/03/10_21:45
3 2002/03/10_21:43 QStar_Release<#3 copy> Record Waiting 0:natasha

The Status of the job with Job ID 2 has changed to Started and the recording was started at 2002/03/10_21:45 Delayed Start
Date.

Note: The QStar CD/DVD Master Software will use all the CD/DVD-R drives available simultaneously. With the jukebox used
in the example, two CD-R drives are available.

Page 62 of 88
4) To display the delayed jobs status, enter:

#>vlqlist
JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date
2 2002/03/10_21:43 QStar_Release<#2 copy> Record Started 0:natasha 2002/03/10_21:45
3 2002/03/10_21:43 QStar_Release<#3 copy> Record Waiting 0:natasha
1 2002/03/10_21:43 QStar_Release<#1 copy> Record Done 0:natasha 2002/03/10_21:44 2002/03/10_21:50

The recording of the first copy has been completed successfully. The Status of the job with Job ID 1 has changed to Done and
the job details are then moved to the bottom of the delayed jobs queue list.

5) To display the delayed jobs status, enter:

#>vlqlist
JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date
2 2002/03/10_21:43 QStar_Release<#2 copy> Record Started 0:natasha 2002/03/10_21:45
3 2002/03/10_21:43 QStar_Release<#3 copy> Record Started 0:natasha 2002/03/10_21:51
1 2002/03/10_21:43 QStar_Release<#1 copy> Record Done 0:natasha 2002/03/10_21:44 2002/03/10_21:50

The Status of the job with Job ID 3 has changed to Started and the recording was started at 2002/03/10_21:51 Delayed Start Date.

6) To display the delayed jobs status, enter:

#>vlqlist
JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date
3 2002/03/10_21:43 QStar_Release<#3 copy> Record Started 0:natasha 2002/03/10_21:51
1 2002/03/10_21:43 QStar_Release<#1 copy> Record Done 0:natasha 2002/03/10_21:44 2002/03/10_21:50
2 2002/03/10_21:43 QStar_Release<#2 copy> Record Done 0:natasha 2002/03/10_21:45 2002/03/10_21:51

The recording of the second copy has been completed successfully. The Status of the job with Job ID 2 has changed to Done
and the job details are then moved to the bottom of the delayed jobs queue list.

7) To display the delayed jobs status, enter:

#>vlqlist
JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date
1 2002/03/10_21:43 QStar_Release<#1 copy> Record Done 0:natasha 2002/03/10_21:44 2002/03/10_21:50
2 2002/03/10_21:43 QStar_Release<#2 copy> Record Done 0:natasha 2002/03/10_21:45 2002/03/10_21:51
3 2002/03/10_21:43 QStar_Release<#3 copy> Record Done 0:natasha 2002/03/10_21:51 2002/03/10_21:57

The recording of the third copy has been completed successfully. The Status of the job with Job ID 3 has changed to Done and
the job details are then moved to the bottom of the delayed jobs queue list.

Note: The QStar syslog file will report detailed information about the recording for all three copies.

The image transferred to the Images Directory is kept until the recording is completed for all the copies. When all the jobs are
completed with or without error the image is deleted from the Images Directory.

Page 63 of 88
The vllsdev command output will display all these copies as duplicate. The QStar Software will not allow duplicate media in
the same jukebox, it prevents the addition of these media to an Integral Volume set or locks the Integral Volume set if the
original media is already part of the Integral Volume set. In order to add media or unlock the Integral Volume set the two copies
must first be exported from the jukebox.

Note: For more detailed information about duplicate media, please refer to Chapter 8 Disaster Recovery on the QStar System
Administrator's Guide.

If the System Administrator has changed the recording Start Time specifying the date and time the jobs should be executed on
the delayed jobs list using the -d [mmdd]HHMM | [cc]yymmddHHMM option on the vlrecord command, this new recording
start time information will be displayed on the vlqlist output on the Delayed-Start-Date information.

1) To display the delayed jobs status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

1 2002/03/10_21:43 QStar_Release<#1 copy> Record Waiting 0:natasha 2002/03/10_23:30
2 2002/03/10_21:43 QStar_Release<#2 copy> Record Waiting 0:natasha 2002/03/10_23:30
3 2002/03/10_21:43 QStar_Release<#3 copy> Record Waiting 0:natasha 2002/03/10_23:30

Note: The Registration-Date reports the Date and Time when the delayed job was added to the delayed jobs queue list and the
Delayed-Start-Date shows the Date and Time when the job is to be processed.

Displaying the Delayed Jobs Status in Long Format

The vlqlist command used with the –l (Output on Long Format) option allows displaying detailed information for the delayed
jobs present in the delayed jobs queue list.

#>vlqlist –l

Record ID: 1
Job: Record
Job Status: Waiting
Job Name: QStar_Release
Sender Hostname: natasha
Sender UID: 0
Registration Date: 2002/03/10_21:43
Start Date:
End Date:
Error:
Delayed Start Date:
Notification Mail Address:
Test Write Mode: laser off
Write Speed: 2
Buffer Size(Mb): default
Media profile: cd-r
Device Name: jb
Shelf Number: 0
Side: A
Image Size: 68960256 – 69Mb
Image Path: /opt/QStar/vl/files/cd_images/nataha.1019164293.img
Set Name:
Leave Open: No
Verify After Recording: No

Page 64 of 88
Record ID: 2
Job: Record
Job Status: Waiting
Job Name: QStar_Release 1
Sender Hostname: brian
Sender UID: 0
Registration Date: 2002/04/19_13:15
Start Date:
End Date:
Error:
Delayed Start Date:
Notification Mail Address: [email protected]
Test Write Mode: no test
Write Speed: 4
Buffer Size(Mb): default
Media profile: cd-r
Device Name: jb
Shelf Number: 6
Side: A
Image Size: 86372352 – 87Mb
Image Path: /opt/QStar/vl/files/cd_images/brian.1019214846.img
Set Name:
Leave Open: No
Verify After Recording: No

Record ID: 3
Job: Record
Job Status: Done
Job Name: QStar_Release 3
Sender Hostname: brian
Sender UID: 0
Registration Date: 2002/04/19_15:24
Start Date: 2002/04/19_15:25
End Date: 2002/04/19_15:29
Error:
Delayed Start Date:
Notification Mail Address: [email protected]
Test Write Mode: no test
Write Speed: 4
Buffer Size(Mb): default
Media profile: cd-r
Device Name: jb
Shelf Number: 1
Side: A
Image Size: 86372352 – 87Mb
Image Path: /opt/QStar/vl/files/cd_images/brian.1019222594.img
Set Name:
Leave Open: No
Verify After Recording: No

Page 65 of 88
Moving Delayed Jobs from the Delayed Jobs List
The vlqmove command is used to move the jobs in the delayed jobs queue list that is controlled by the QStar VL scheduler
process. The delayed jobs listed in the vlqlist command output are displayed in the order they were added to the delayed jobs
queue. The job that has the highest priority in the queue is the job that is displayed at the top of the list. When the recording
starts, the job at the top of the list will be the first delayed job to be processed. The System Administrator using the vlqmove
command can change the order the jobs will be processed.

vlqmove [-H host_name] job_id1 [after] job_id2

Note: By default, this command moves job_id1 ahead of job_id2.

The options available with the vlqmove command are described as follows:

-H host_name
Specifies the name of the host where the device is connected. Without this option, the local host is used.

[after]
Specifies that job_id1 should be placed after job_id2.

Example:

1) To display the delayed jobs status, enter:

#>vlqlist
JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date
1 2002/03/11_00:57 QStar_Release<#1 copy> Record Waiting 0:natasha 2002/03/11_01:30
2 2002/03/11_00:57 QStar_Release<#2 copy> Record Waiting 0:natasha 2002/03/11_01:30
3 2002/03/11_00:57 QStar_Release<#3 copy> Record Waiting 0:natasha 2002/03/11_01:30

Note: In the example, the job with Job ID 1 will be the first to be recorded.

2) To change the priority order of the jobs 1 and 2, enter:

#>vlqmove 2 1

Note: In the example, the job with Job ID 2 is selected to move this job to the top of the list.

3) To display the delayed jobs status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

2 2002/03/11_00:57 QStar_Release<#2 copy> Record Waiting 0:natasha 2002/03/11_01:30
1 2002/03/11_00:57 QStar_Release<#1 copy> Record Waiting 0:natasha 2002/03/11_01:30
3 2002/03/11_00:57 QStar_Release<#3 copy> Record Waiting 0:natasha 2002/03/11_01:30

Note: Now the job with Job ID 2 is at the top of the list and will be the first job that will be processed.

Page 66 of 88
Deleting Delayed Jobs from the Delayed Jobs List
The vlqmove command is used to remove the job records in the delayed jobs queue list that is controlled by the QStar VL
scheduler process. This command can be used to clear completed, completed with error, and unwanted incomplete records.

vlqremove [-H host_name] job_id

The options available with the vlqremove command are described as follows:

-H host_name
Specifies the name of the host where the device is connected. Without this option, the local host is used.

Example:

1) To display the delayed jobs status, enter:

#>vlqlist
JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date
1 2002/03/11_00:57 QStar_Release1 Record Waiting 0:natasha 2002/03/11_01:30
2 2002/03/11_01:10 QStar_Release2 Record Waiting 0:natasha 2002/03/11_01:30
3 2002/03/11_01:17 QStar_Release3 Record Waiting 0:natasha 2002/03/11_01:30

2) To delete a job from the delayed jobs queue list, enter:

#>vlqremove 1

Note: In the example, the job with Job ID 1 is removed from the list.

3) To display the delayed jobs status, enter:

#>vlqlist

JobID Registration-Date Job-Name Job-Type Status UserID:User-Hostname Delayed-Start-Date End-Date

2 2002/03/11_01:10 QStar_Release2 Record Waiting 0:natasha 2002/03/11_01:30
3 2002/03/11_01:17 QStar_Release3 Record Waiting 0:natasha 2002/03/11_01:30

Note: Once a job is removed from the list the job is canceled and the associated image file in the Images Directory is removed.

Page 67 of 88
Burn Test Procedure Before Starting the Write Operation
Before starting the actual write operation, QStar suggests carrying out a recording test. This will ensure that the write speed
between the CD/DVD-R drive and the CD/DVD-R media is adequate without wasting any media.

The QStar CD/DVD Master Software allows two types of test procedures:

A) Laser OFF (-t option on vlrecord command)

This test can be done either with the QStar CD/DVD Master Software running on the server, or with it running on a client
machine. When the Laser OFF test mode is specified, the Software and CD/DVD-R drive simulate the write process, but
the CD/DVD-R drive does not actually write data to the media. The CD/DVD-R drive will accept the data sent by the
Software and will behave as if it is actually writing the data to the media but with the laser power turned off the write will
not actually occur. This test mode is used to determine the optimum write speed that can be used with the CD/DVD-R drive
controlled by QStar Software. This test is useful to determine the compatibility between the media, the drive and the
system, in order to prevent wasting media. This can be done using the Direct and Delayed write procedures. The only
difference is that with the Delayed write procedure the System Administrator will get the information about the test from
the QStar Syslog file only. The final exit status of the test is displayed, whether the test was local, or over the network.

B) Write OFF (-T option on vlrecord command)

Test mode without a write operation. This mode is used to determine the data transfer rate of the CD-R/DVD-R drives over
the network. This test should be used with the Direct write procedure if the QStar CD/DVD Master Software is running on
a client machine to determine the optimum transfer rate and set the best write speed for the environment.

Typically a client machine on a 1Mb network will have drive transfer rates of, 1x = 150k/sec, 2x = 300k/sec, 6x = 1mb/sec,
12x = 2mb/sec. Therefore, write speeds greater than 6x will generate a buffer under run error.

Either test can be carried out using the Direct or Delayed write procedures.

In the following example, an existing ISO image is transferred to the media on shelf 1 using the Direct write procedure.

Laser OFF Burn Test

In the Laser OFF test procedure the -v Verbose, -t (Laser OFF) option must be specified on the vlrecord command.

A) In the first test the write speed of the CD/DVD-R drive is selected as Max.

1) To enable the Laser OFF test procedure using the /home/QStar_Software_Unix.iso image, enter:

#>vlrecord -v -x max -t jb:1a /home/QStar_Software_Unix.iso

During the test the Verbose output will display the events performed and the progress of the test.

Example of the Verbose output:

jb:1 setup
jb:1 ready. Recording started
jb:1 5Mb of 85Mb (2560 blks)600Kb/s, Total:407Kb/s, buffers:memory 95%, drive 83% full
jb:1 6Mb of 85Mb (3072 blks)576Kb/s, Total:430Kb/s, buffers:memory 95%, drive 85% full
vlrecord: I/O error

If a problem is encountered during the test an error will be generated, the test will be stopped and the Verbose output will
display the error generated.

Page 68 of 88
Note: In the example, an error is generated.

Detailed information about the error is reported in the QStar syslog file.

Example of the information displayed on the QStar syslog file:

03/11/2002 14:02:44 VL: record:jb:1 - start

write mode: laser off, max speed, default buffer, image size 90052608 - 85 Mb
03/11/2002 14:02:44 record:jb:1: create_service
03/11/2002 14:02:47 record: jb:1 - max write speed 705 Kb/s - 4X, current write speed
705 Kb/s - 4X, 4 Mb buffer, close media
03/11/2002 14:03:06 JB: jb drive 1: Sync failed : I/O error
03/11/2002 14:03:06 JB: jb shelf 1: is set offline
03/11/2002 14:03:28 VL: record:jb:1 - end, error 3000002

Note: The QStar syslog file reports any errors encountered.

B) The first test shows that at the maximum write speed allowed by the CD/DVD-R drive, the recording procedure can have a
problem that will cause an error. To find the correct write speed, the speed is set to a lower value (in the example it is 2x) and
the test is re-run.

Note: The maximum speed for the drive used on the first example is 4x.

1) To enable the Laser OFF test procedure using the /home/QStar_Software_Unix.iso image, enter:

#>vlrecord -v -x 2 -t jb:1a /home/QStar_Software_Unix.iso

During the test the Verbose output will display the events performed and the progress of the test.

Example of the Verbose output:

jb:1 setup
jb:1 ready. Recording started
jb:1 5Mb of 85Mb (2560 blks)299Kb/s, Total:248Kb/s, buffers:memory 95%, drive 84% full
jb:1 10Mb of 85Mb (5120 blks)299Kb/s, Total:272Kb/s, buffers:memory 95%, drive 84% full
jb:1 15Mb of 85Mb (7680 blks)1684Kb/s, Total:273Kb/s, buffers:memory 95%, drive 84% full
jb:1 20Mb of 85Mb (10240 blks)299Kb/s, Total:283Kb/s, buffers:memory 95%, drive 77% full
jb:1 25Mb of 85Mb (12800 blks)299Kb/s, Total:287Kb/s, buffers:memory 95%, drive 84% full
jb:1 30Mb of 85Mb (14848 blks)299Kb/s, Total:289Kb/s, buffers:memory 95%, drive 84% full
jb:1 35Mb of 85Mb (17408 blks) 57Kb/s, Total:286Kb/s, buffers:memory 95%, drive 25% full
jb:1 39Mb of 85Mb (19968 blks)299Kb/s, Total:292Kb/s, buffers:memory 95%, drive 84% full
jb:1 44Mb of 85Mb (22528 blks)299Kb/s, Total:293Kb/s, buffers:memory 95%, drive 84% full
jb:1 49Mb of 85Mb (25088 blks)1505Kb/s,Total:292Kb/s, buffers:memory 95%, drive 84% full
jb:1 54Mb of 85Mb (27648 blks)300Kb/s, Total:294Kb/s, buffers:memory 95%, drive 84% full
jb:1 59Mb of 85Mb (30208 blks)300Kb/s, Total:294Kb/s, buffers:memory 95%, drive 84% full
jb:1 64Mb of 85Mb (32768 blks)1699Kb/s,Total:295Kb/s, buffers:memory 95%, drive 84% full
jb:1 69Mb of 85Mb (34816 blks)1560Kb/s,Total:294Kb/s, buffers:memory 95%, drive 49% full
jb:1 74Mb of 85Mb (37376 blks)299Kb/s, Total:295Kb/s, buffers:memory 95%, drive 84% full
jb:1 78Mb of 85Mb (39936 blks)299Kb/s, Total:296Kb/s, buffers:memory 95%, drive 84% full
jb:1 83Mb of 85Mb (42496 blks)300Kb/s, Total:296Kb/s, buffers:memory 75%, drive 84% full
jb:1 85Mb of 85Mb (43971 blks)111Kb/s, Total:296Kb/s, buffers:memory 0%, drive 96% full
jb:1 closing
85 Mb done

Page 69 of 88
The Verbose output displays that this time the test procedure completed without any errors. The selected write speed is clearly
the correct speed for the CD/DVD-R drive.

Detailed information about the exit status of the test is reported in the QStar syslog file.

Example of the information displayed on the QStar syslog file:

03/11/2002 16:48:47 VL: record:jb:1 - start
write mode: laser off, 2X speed, default buffer, image size 90052608 - 85 Mb
03/11/2002 16:48:47 record:jb:1: create_service
03/11/2002 16:48:48 record: jb:1 - max write speed 705 Kb/s - 4X, current write
speed 352 Kb/s - 2X, 4 Mb buffer, close media
03/11/2002 16:54:06 VL: record:jb:1 - end, error 0

Note: The QStar syslog file shows that the test was completed with “0” error.

Write OFF Burn Test

In the Write OFF test procedure the -v Verbose, -T (Write OFF) option must be specified on the vlrecord command.

A) In the test the write speed of the CD/DVD-R drive is selected as Max.

1) To enable the Write OFF test procedure using the /home/QStar_Software_Unix.iso image, enter:

#>vlrecord -v -x max -T jb:1a /home/QStar_Software_Unix.iso

During the test the Verbose output will display the events performed and the progress of the test.

Example of the Verbose output:

jb:1 setup
jb:1 ready. Recording started
jb:1 1Mb of 85Mb (512 blks) 0Kb/s, Total: 0Kb/s, buffers:memory 78%, drive 100% full
………
jb:1 5Mb of 85Mb(2560 blks)864Kb/s, Total:4376Kb/s, buffers:memory 1%, drive 100% full
jb:1 6Mb of 85Mb(3072 blks)864Kb/s, Total:2603Kb/s, buffers:memory 1%, drive 100% full
jb:1 7Mb of 85Mb(3584 blks)864Kb/s, Total:2019Kb/s, buffers:memory 1%, drive 100% full
jb:1 8Mb of 85Mb(4096 blks)864Kb/s, Total:1728Kb/s, buffers:memory 1%, drive 100% full
jb:1 9Mb of 85Mb(4608 blks)864Kb/s, Total:1554Kb/s, buffers:memory 1%, drive 100% full
jb:1 10Mb of 85Mb(5120 blks)853Kb/s, Total:1438Kb/s, buffers:memory 1%, drive 100% full
jb:1 40Mb of 85Mb(20480 blks)864Kb/s, Total:952Kb/s, buffers:memory 1%, drive 100% full
jb:1 41Mb of 85Mb(20992 blks)864Kb/s, Total:950Kb/s, buffers:memory 1%, drive 100% full
jb:1 42Mb of 85Mb(21504 blks)864Kb/s, Total:947Kb/s, buffers:memory 1%, drive 100% full
jb:1 43Mb of 85Mb(22016 blks)864Kb/s, Total:945Kb/s, buffers:memory 1%, drive 100% full
jb:1 44Mb of 85Mb(22528 blks)864Kb/s, Total:943Kb/s, buffers:memory 1%, drive 100% full
jb:1 45Mb of 85Mb(23040 blks)864Kb/s, Total:941Kb/s, buffers:memory 1%, drive 100% full
jb:1 46Mb of 85Mb(23552 blks)864Kb/s, Total:938Kb/s, buffers:memory 1%, drive 100% full
………
jb:1 82Mb of 85Mb(41984 blks)853Kb/s, Total:901Kb/s, buffers:memory 1%, drive 100% full
jb:1 83Mb of 85Mb(42496 blks)864Kb/s, Total:900Kb/s, buffers:memory 1%, drive 100% full
jb:1 84Mb of 85Mb(43008 blks)864Kb/s, Total:900Kb/s, buffers:memory 1%, drive 100% full
jb:1 85Mb of 85Mb(43520 blks)864Kb/s, Total:899Kb/s, buffers:memory 1%, drive 100% full
jb:1 85Mb of 85Mb(43965 blks)865Kb/s, Total:899Kb/s, buffers:memory 1%, drive 100% full
jb:1 closing
85Mb done

Page 70 of 88
The Verbose output displays that this time the test procedure completed without any errors. The Kb/sec information relates to
the transfer rate achieved over the network.

Detailed information about the exit status of the test is reported in the QStar syslog file.

Example of the information displayed on the QStar syslog file:

03/11/2002 17:33:45 VL: cdrecord:jb:1 - start

write mode: write off, max speed, default buffer, image size 90052608 - 85 Mb
03/11/2002 17:33:45 cdrecord:jb:1: create_service
03/11/2002 17:33:47 cdrecord: jb:1 - max write speed 705 Kb/s - 4X, current write
speed 705 Kb/s - 4X, 4 Mb buffer, close media
03/11/2002 17:36:07 VL: cdrecord:jb:1 - end, error 0

Note: The QStar syslog file shows that the test was completed with “0” error.

Page 71 of 88
ERROR CONDITIONS DURING RECORDING
If an error occurred during the Direct write procedure the error will be displayed during the recording if the Vebose output
option was specified in the vlrecord command. The QStar syslog file will report additional information about the error
encountered during the recording procedure.

If an error occurred during the Delayed write pocedure the error information will be displayed on the record regarding the job
that encountered the error in delayed jobs queue list, displayed using the vlqlist command. The syslog file will report additional
information about the error encountered during the recording procedure.

If an error is frequently encountered during the recording procedure, QStar suggests monitoring the CD/DVD-R drive to detect
which error the device returns using the qscsi_log command with the option that allows collecting all the SCSI command
information in the /opt/QStar/log/scsi_log file. For more detailed information regarding the qscsi_log command, please refer to
Chapter 8 Disaster Recovery on this manual.

The vlqlist command used with the -l (Output on Long Format) option allows displaying detailed error information for the
delayed jobs present in the delayed jobs queue list.

#>vlqlist -l

Record ID: 2
Job: Record
Job Status: Error
Job Name: QStar Release
Sender Hostname: brian
Sender UID: 0
Registration Date: 2002/04/19_13:15
Start Date: 2002/04/19_13:29
End Date: 2002/04/19_13:30
Error: USCSICMD ioctl: try jb:6a 82 Mb: cdr_write: write process was interrupted:
SCSI cmd 0x2a (write): I/O error
Delayed Start Date:
Notification Mail Address: [email protected]
Test Write Mode: no test
Write Speed: 4
Buffer Size(Mb): default
Media profile: cd-r
Device Name: jb
Shelf Number: 6
Side: A
Image Size: 86372352 – 85Mb
Image Path: /opt/QStar/vl/files/cd_images/brian.1019214846.img
Set Name:
Leave Open: No
Verify After Recording: No

Note: In the example, an error occurred during the delayed recording procedure is displayed.

Page 72 of 88
MANAGING QSTAR CD/DVD MASTER SOFTWARE FOR UDF
FILE SYSTEM WRITTEN WITH PACKET WRITING
In this section, to understand how to configure the CD/DVD-R media with the UDF file system and Packet Writing option
enabled, we will present a simple walk through that will support every type of jukebox and standalone drive that the QStar
Software supports.

MANAGING AN INTEGRAL VOLUME (I.V.) SET

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
jukeboxes and standalone drives that support WORM or rewritable Optical (MO/UDO/PDD) media, Blu-ray, DVD-RAM 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.

B) Single-Volume (Used with 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. This configuration is primarily used with standalone drives. The
QStar Software simulates the Standalone Drive as a virtual jukebox with one shelf, containing a media with a single surface,
but may also be used in jukeboxes 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. This configuration should primarly be used with WORM media but may also be used for rewritable
media. Retrieval performance of data may be significantly decreased if any files are deleted or renamed from the file system.

The recommendations for using UDF spanning:

1) A cache 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 Volumes.
4) WORM media
Please contact your QStar representative for more detailed information on how to configure UDF Spanning.

Page 73 of 88
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
commands. Detailed information follows in subsequent topics.

Steps for jukebox and standalone drive Command To Use

1. Importing the media into the jukebox(es) vlimport
Loading the media to the drive manually (Single-Volume) vlrefresh
2. Erasing the media, if rewritable vlerase
3. Repeat the above steps 1 and 2 for all media needed (For a Jukebox)
4. Creating the Integral Volume set definition vlcrset
5. Adding the media to an Integral Volume set vladdtoset
6. Creating the cache for the Integral Volume set vlcache
7. Creating the mount point directory mkdir
8. Mounting the Integral Volume set mountiv
9. Unmounting the Integral Volume set umount/umountiv
Unloading the media from the drive (Single-Volume) vlexport

Monitoring an Integral Volume set Command To Use

1. Displaying the jukebox shelf information jbstatus
2. Monitoring the VL device information vllsdev
3. Monitoring the Integral Volume set information vllsset
4. Monitoring the file system df –k (Command platform independent)
udfdf (Automount Interchange Level)
5. Monitoring the cache status mmparam

Page 74 of 88
 INTEGRAL VOLUME SET CONFIGURATION
FOR A CD/DVD-R JUKEBOX OR STANDALONE DRIVE WITH
AUTOMOUNT AND SINGLE-VOLUME INTERCHANGE LEVELS

Detailed Walk Through:

The following pages will describe how to manage the media with UDF file system in Automount and Single-Volume
configurations, create and manage an Integral Volume set. Because the QStar Software simulates a Standalone Drive as a
virtual jukebox with one shelf, containing a media with a single surface, a DVD-R jukebox will be used as an example in
the walk through described below. The only effective difference from a jukebox and a standalone drive is the number of shelves
and some additional features available only for the jukebox.

Note: All the default parameters are used, for more detailed information, please refer to Chapter 5 - The Volume Librarian or
Chapter 9 - Command Reference in this manual.

To create a UDF Automount or Single-Volume Integral Volume set, follow the directions below.

1) To determine the jukebox shelf and media information in reference to the Volume Librarian, enter:

vllsdev device_name

Example - To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
---------------------------------------------------------------------------------
1-1: empty Note: The shelf 1 is empty.
2-1: empty
3-1: empty
4-1: empty
5-1: empty
6-1: empty
7-1: empty
8-1: empty
9-1: empty
10-1: empty
11-1: empty
12-1: empty
13-1: empty
14-1: empty
15-1: empty
16-2: empty

2) To import the media into a shelf, enter:

vlimport device_name shelf_number

Example - to import the media to shelf 1 of the jukebox identified as jb, enter:

#>vlimport jb 1
jb:refreshing shelf 1 ...

Page 75 of 88
 Note: If a standalone drive is used manually load the media into the drive and then refresh the status of the media.

To refresh the status of the media in the standalone drive, enter:

vlrefresh device_name

Example - to refresh the media in the standalone drive identified as jb, enter:

#>vlrefresh jb

3) To import additional media, repeat the above steps with the appropriate shelf number.

4) To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
---------------------------------------------------------------------------------
1a-1: blank 4.4 GB DVD-R Note: The status in the VL database for new CD/DVD-R media is blank.
1b-1: blank 4.4 GB DVD-R
2-1: empty
3-1: empty
4-1: empty
5-1: empty
6-1: empty
7-1: empty
8-1: empty
9-1: empty
10-1: empty
11-1: empty
12-1: empty
13-1: empty
14-1: empty
15-1: empty
16-2: empty

Note: For single sided media only Shelf 1a information will be displayed. and the Type column will display BD-RS for Blu-ray
media.

5) To create a new Integral Volume set, enter:

vlcrset -T fs_type set_type_specific_options -u media_type set_name

Example-A - create a new Integral Volume set definition named Test for CD/DVD-R media with a UDF file system, single-
volume interchange level and the packet writing option enabled, enter:

#>vlcrset -T udf -P 1 -u cd-dvd Test

Page 76 of 88
 Example-B - create a new Integral Volume set definition named Test for CD/DVD-R media with a UDF file system,
automount interchange level and the packet writing option enabled, enter:

#>vlcrset –T udf -v a –P 1 –u cd-dvd Test

Note: The Packet Writing option is available when selecting CD/DVD or Blu-ray (BD-RS) media as the Archive Media Type.
The CD/DVD-R or BD-RS 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. For more detailed information of the UDF specific options, please refer to “Creating an Integral Volume Set with
UDF or ISO 9660 File System” session on Chapter 5 - The Volume librarian in this manual.

6) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: The Integral Volume set is empty because no media (Media=0) is associated with it.

Single-Volume Interchange Level output:

Test
Use_media= cd,dvd,worm,rdonly Spread=no Quota=1 Media=0
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=single-volume
Packet_writing_init=yes Space_calculation=yes Verify_write=no
No cache

Automount Interchange Level output:

Test
Use_media= cd,dvd,worm,rdonly Spread=no Quota=2048 Media=0
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=yes Space_calculation=yes Verify_write=no
No cache

Note: The difference between the two above outputs are in the Interchange Level type and in the Quota number.

Note1: The Use_Media information will display bd,worm,rdonly for Blu-ray BD-RS media.

7) To add media to the Integral Volume set, enter:

vladdtoset set_name device_name shelf_number

Example - to add the media on shelf 1 to the Integral Volume set Test, enter:
#>vladdtoset Test jb 1
jb:initializing side a ...

Page 77 of 88
 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 will not change its status. 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.

8) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now one media is associated with the Integral Volume set Test.

Single-Volume Interchange Level output:

Test
Use_media= cd,dvd,worm,rdonly Spread=no Quota=1 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=q_3c0ec380
UDF_revision=150 Interchange_level=single-volume
Packet_writing_init=yes Space_calculation=yes Verify_write=no
No cache
0: Online=jb:1 Sequence_number=1

Automount Interchange Level output:

Test
Use_media=cd,dvd,worm,rdonly Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=yes Space_calculation=yes Verify_write=no
No cache
0: Online=jb:1 Automount_sequence_numbers=0,1

Note: In the automounter configuration the Logical_volume_identifier is equal to NA (Not Available) and instead the
Automount_Sequence_number is displayed. When a media is added to the Integral Volume set, every surface will be initialized
wih a unique Set_id number (Logical Volume Identifier). By default, this unique Set_id number is equal to “q_number”. The
Automount_Sequence_numbers represent the sequence number of the surfaces in the root directory of the file system once it is
mounted. All sub-directories (surfaces) in the root directory will be labeled by default as vol_Automount_Sequence_number
(i.e. vol_0, vol_1, vol_#) if the Set_id number is one that is assigned by default by QStar Software, if not, theVolume Label will
be used as the sub-directories name. With the vladdtoset command it is possible to specify the Logical Volume Identifier using
the -A -B options. If the media is blank/erased the specified Logical Volume Identifier will be written to the surface as a unique
surface_id number and used as the directory name that identifies the surfaces under the Automount mount point. If the Media
already has the Logical Volume Identifier (initialized) the -A and -B option will only change the default vol_0, vol_1 and vol_#
directory names that identified the surfaces under the Automount mount point with the specified name. In this case, the new sub-
directories name will be printed in the set information for each surface.

Note1: In the rest of the walk through only the automout interchange level output will be diplayed.

Page 78 of 88
9) To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
---------------------------------------------------------------------------------
1a-1: udf-150 4.4 GB DVD-R Seq=1 Log_vol_id=q_a3e82f5cd
1b-1: udf-150 4.4 GB DVD-R Seq=1 Log_vol_id=q_b3e82f5cd
2-1: empty
3-1: empty
4-1: empty
5-1: empty
6-1: empty
7-1: empty
8-1: empty
9-1: empty
10-1: empty
11-1: empty
12-1: empty
13-1: empty
14-1: empty
15-1: empty
16-2: empty

10) To create the cache for an Integral Volume set, enter:

vlcache -p xxMB -c /cache_root set_name

Example - to create a cache with 100MB and cache located on /Cache_Test for the Integral Volume set Test, enter:
#>vlcache -p 100MB -c /Cache_Test Test

11) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now a cache is associated with the Integral Volume set Test.
Test
Use_media=cd,dvd,worm,rdonly Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=yes Space_calculation=yes Verify_write=no
Cache: Cache_root=/Cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
0: Online=jb:1 Automount_sequence_numbers=0,1

12) To create the mount point directory, enter:

mkdir directory_name

Page 79 of 88
 Example - to create the mount point /mnt, enter:

#>mkdir /mnt

13) To mount the Integral Volume set with a new cache, enter:

mountiv -n set_name mount_point

Example - to mount Integral Volume set Test on the mount point /mnt, enter:

#>mountiv -n Test /mnt

Note: The “-n” option is used only with the first mount, on subsequent mounts, do not use the “-n” option in the mountiv
command syntax.

14) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now the Integral Volume set Test is mounted.
Test
Use_media=cd,dvd,worm,rdonly Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=automount
Packet_writing_init=yes Space_calculation=yes Verify_write=no
Cache: Cache_root=/Cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Mounted at /mnt
0: Online=jb:1 Automount_sequence_numbers=0,1 Mounted=a,b

15) To monitor the Integral Volume set, enter:

Single-volume Interchange Level:

#>df -k /mnt

Automount Interchange Level:

#>df -k /mnt Note: This command will display the total capacity of all the surfaces already accessed

#>udfdf -t /mnt

#>udfdf -f -a 0 /mnt

Note: QStar recommends reviewing the explanation for the udfdf command in Chapter 9 - Command Reference of this manual.

Page 80 of 88
16) To monitor the cache status of an Integral Volume set, enter:

mmparam { set_name | mount_point}

Example - to monitor the cache status of the Integral Volume set Test, enter:

#>mmparam /mnt

#>mmparam Test

17) To start archiving files from the cache to the archival media, enter:

mmarc [-H host_name] {-l | -e | -a age | -s} [-w][-j {delayed_job_name | "default"}] [-S cron_like_schedule]
{set_name | filename}

Example - to start archiving files from the cache of the Integral Volume set Test, enter:

#>mmarc -e /mnt

#>mmarc -e Test

18) To close a media once full, enter:

vlclose [-H host_name] [-f] device_name shelf_number[{a|b}]

Example - to close the surface “a” of the media on shelf 1 belonging to the Integral Volume set Test, enter:

#>vlclose jb 1a

Note: With Automount Interchange level the close procedure will be allowed with the Integral Volume set mounted if at least
two media are added to the Integral Volume set. If only one media was added, unmount the Integral Volume set before running
the vlclose command. For the standalone drive the close procedure will be allowed only if the Integral Volume set is
unmounted. For more detailed information about the vlclose command, please refer to Chapter 9 - Command Reference in this
manual.

19) To unmount the Integral Volume set, enter:

umount /mount_point

umountiv set_name

Example - to unmount the Integral Volume set Test on the mount point /mnt, enter:
#>umount /mnt

#>umountiv Test (For Linux and HP-UX platforms)

Note: QStar does not recommend using the umount command for Linux or HP-UX platforms; this ensures the Integral Volume
set is completely unmounted. Please refer to Chapter 6 - Migration Manager in this manual for more detailed information.

20) To unload the media from the drive, enter:

#>vlexport jb1 1

Page 81 of 88
 INTEGRAL VOLUME SET CONFIGURATION FOR CD/DVD-R JUKEBOX
WITH SPANNING INTERCHANGE LEVEL AND PACKET WRITING

DETAILED WALK THROUGH:

To create an Integral Volume set, follow the directions below.

Note: In the walk through described below, a DVD-R jukebox and all the default parameters are used, for more detailed
information, about the QStar commands referenced in this procedure, please refer to Chapter 5 - The Volume Librarian or
Chapter 9 - Command Reference in this manual.

1) To determine the jukebox shelf and media information in reference to the Volume Librarian, enter:

vllsdev device_name

Example - To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
----------------------------------------------------------------------------
1: empty Note: The shelf 1 is empty.
2: empty
3: empty
4: empty
5: empty
6: empty
7: empty
8: empty
9: empty
10: empty
11: empty
12: empty
13: empty
14: empty
15: empty
16: empty

2) To import the media into a shelf, enter:

vlimport device_name shelf_number

Example - to import the media to shelf 1 of the jukebox identified as jb, enter:

#>vlimport jb 1
jb:refreshing shelf 1 ...

3) To import additional media, repeat the above steps with the appropriate shelf number.

Page 82 of 88
4) To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
---------------------------------------------------------------------------------
1a-1: blank 4.4 GB DVD-R Note: The status in the VL database for new CD/DVD-R media is blank.
1b-1: blank 4.4 GB DVD-R
2-1: empty
3-1: empty
4-1: empty
5-1: empty
6-1: empty
7-1: empty
8-1: empty
9-1: empty
10-1: empty
11-1: empty
12-1: empty
13-1: empty
14-1: empty
15-1: empty
16-2: empty

Note: For single sided media only Shelf 1a information will be displayed. and the Type column will display BD-RS for Blu-ray
media.

5) To create a new Integral Volume set, enter:

vlcrset -T fs_type set_type_specific_options -u media_type set_name

Example - create a new Integral Volume set definition named Test for CD/DVD-R media with a UDF file system, spanning
interchange level, packet writing and close of full volume options eanbled, enter:

#>vlcrset –T udf -v s –P 1 –V 1 –u cd-dvd Test

Note: The Packet Writing option is available when selecting CD/DVD or Blu-ray (BD-RS) media as the Archive Media Type.
The CD/DVD-R or BD-RS 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. For more detailed information of the UDF specific options, please refer to “Creating an Integral Volume Set with
UDF or ISO 9660 File System” session on Chapter 5 - The Volume librarian in this manual.

6) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: The Integral Volume set is empty because no media (Media=0) is associated with it.
Test
Use_media= cd,dvd,worm,rdonly Spread=no Quota=2048 Media=0
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=NA
UDF_revision=150 Interchange_level=spanning
Packet_writing_init=yes Verify_write=no
Close_full_volume=yes File_spanning=yes Use_image_backup=yes
No cache

Page 83 of 88
 Note: Use_image_backup option is set to yes by default for CD/DVD-R media. The image backup can be used to burn a backup
media in order to replace the original if damaged. The procedure to burn the image backup onto a new media can be done using
the vlinset command with -R flag.

Note1: The Use_Media information will display bd,worm,rdonly for Blu-ray BD-RS media.

7) To add media to the Integral Volume set Test, enter:

vladdtoset set_name device_name shelf_number

Example - to add the media on shelf 1 to the Integral Volume set Test, enter:

#>vladdtoset Test jb 1
jb:initializing side a ...

Note: Include media 1 and any other media in the jukebox with the same Set_Id in this Integral Volume set.

8) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now one media is associated with the Integral Volume set Test that has the Set_Id.
Test
Use_media= cd,dvd,worm,rdonly Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=q_a30a36f78
UDF_revision=150 Interchange_level=spanning
Packet_writing_init=yes Verify_write=no
Close_full_volume=yes File_spanning=yes Use_image_backup=yes
No cache
0: Online=jb:1 Span_numbers=1,2

9) To display the jukebox shelf information for a jukebox identified as jb, enter:

#>vllsdev jb
jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
--------------------------------------------------------------------------------
1a: udf-150 4.4 GB DVD-R Span=1 Log_vol_id=q_a30a36f78-1
1b: udf-150 4.4 GB DVD-R Span=2 Log_vol_id=q_a30a36f78-2
2-1: empty
3-1: empty
4-1: empty
5-1: empty
6-1: empty
7-1: empty
8-1: empty
9-1: empty
10-1: empty
11-1: empty
12-1: empty
13-1: empty
14-1: empty
15-1: empty
16-2: empty

Page 84 of 88
10) To create the cache for the Integral Volume set, enter:

vlcache -p xxMB -c /cache_root set_name

Example - to create a cache with 100 MB and cache located on /Cache_Test for the Integral Volume set Test, enter:

#>vlcache -p 100MB -c /Cache_Test Test

11) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now the cache is associated with the Integral Volume set Test.
Test
Use_media= cd,dvd,worm,rdonly Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=q_a30a36f78
UDF_revision=150 Interchange_level=spanning
Packet_writing_init=yes Verify_write=no
Close_full_volume=yes File_spanning=yes Use_image_backup=yes
Cache: Cache_root=/Cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
0: Online=jb:1 Span_numbers=1,2

12) To create the mount point directory, enter:

mkdir directory_name

Example - to create the mount point /mnt, enter:

#>mkdir /mnt

13) To mount the Integral Volume set with a new cache, enter:

mountiv -n set_name mount_point

Example - to mount the Integral Volume set Test on the mount point /mnt, enter:

#>mountiv -n Test /mnt

Note: The “-n” option is used only with the first mount, on subsequent mounts, do not use the “-n” option in the mountiv
command syntax.

Page 85 of 88
14) To display the status of the Integral Volume set Test, enter:

#>vllsset –v Test Note: List the Integral Volume set definition and associated media.
Note1: Now the Integral Volume set Test is mounted.
Test
Use_media= cd,dvd,worm,rdonly Spread=no Quota=2048 Media=1
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=udf (Universal Disk Format)
Logical_volume_identifier=q_a30a36f78
UDF_revision=150 Interchange_level=spanning
Packet_writing_init=yes Verify_write=no
Close_full_volume=yes File_spanning=yes Use_image_backup=yes
Cache: Cache_root=/Cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Mounted at /mnt
0: Online=jb:1 Span_numbers=1,2 Mounted=a,b

15) To monitor the Integral Volume set, enter:

#>df -k /mnt

16) To monitor the cache status of an Integral Volume set, enter:

mmparam { set_name | mount_point}

Example - to monitor the cache status of the Integral Volume set Test, enter:

#>mmparam /mnt

#>mmparam Test

17) To start archiving files from the cache to the archival media, enter:

mmarc [-H host_name] {-l | -e | -a age | -s} [-w][-j {delayed_job_name | "default"}] [-S cron_like_schedule]
{set_name | filename}

Example - to start archiving files from the cache of the Integral Volume set Test, enter:

#>mmarc -e /mnt

#>mmarc -e Test

18) Using the Spanning configuration, it is possible to Automatically close a full media. This option should be specified at the creation
of the Integral Volume set. QStar highly recommends using this option with CD/DVD-R media, but the System Administrator can
also close the media as follows.

Page 86 of 88
 To close a media once full, enter:

vlclose [-H host_name] [-f] device_name shelf_number[{a|b}]

Example - to close the surface “a” of the media on shelf 1 belonging to the Integral Volume set Test1, enter:
#>vlclose jb 1a

Note: For more detailed information about the vlclose command, please refer to Chapter 9 - Command Reference in this
manual.

19) To unmount the Integral Volume set, enter:

umount /mount_point

umountiv set_name

Example - to unmount the Integral Volume set Test on the mount point /mnt, enter:

#>umount /mnt

#>umountiv Test (For Linux and HP-UX platforms)

Note: QStar does not recommend using the umount command for Linux or HP-UX platforms; this ensures the Integral Volume
set is completely unmounted. Please refer to Chapter 6 - Migration Manager in this manual for more detailed information.

Page 87 of 88
RECOVERING A DAMAGED CD/DVD-R MEDIA WRITTEN WITH UDF SPANNING
INTERCHANGE LEVEL AND PACKET WRITING USING THE BACKUP IMAGE

This procedure is designed for CD/DVD-R media with the Spanning Interchange level and Packet Writing. If a problem is
encountered with the current write surface, a new media can be created from the backup image. This option is enabled by
default for CD/DVD-R media, but may also be used on Optical WORM media. By default, the QStar Software will create the
backup image in the cache root of each Integral Volume set, the System Administrator needs to be sure there is adequate disk
space for this purpose. The backup images can be stored in another location, the System Administrator can change it by editing
the in the /opt/QStar/vl/files/conf file and typing a new value between the quotes of the following line:

Big Space Root Dir = “”

The directory entered between the quotes will need to exist. With this option set, the backup images of all sets will be stored in
this common location.

The backup image is named as udf_image_backup_set_name and will be the same block size and capacity as the media
surface currently being written to. When the media is closed, the backup image is deleted and a new one is created for the next
media in the Integral Volume set, if there is a failure, the vlinset command is used to create a new media surface for the Integral
Volume set from the backup image.

To recover a new media surface from the backup image, enter:

vlinset [-H host_name] -R device_name:shelf_number set_name in_set_number

Example - to use the backup image to restore to the media number “4” with a new media in shelf 10 for jukebox named jb for an
Integral Volume set named Test, enter:

# >vlinset –R jb:10 Test 4

The backup image will be used to create a new media for the Integral Volume set; the media will be the same as the original,
with a copy number increased by “1”.

If the media is single sided, once the vlinset command has completed the recording of the backup image, it will automatically
substitute the original media in the Integral volume set with the new backup media.

If the media is double sided and the problem occurred to the side A, once the vlinset command has completed the recording of
the backup image to the side A will initialize side B and after that will automatically substitute the original media in the Integral
volume set with the new backup media.

If the media is double sided and the problem occurred to the side B, the vlinset command first will copy the side A of the
original media to the side A of the backup media and when the copy is completed it will record the backup image to the side B.
Once the vlinset command has completed the recording of the backup image to the side B, it will automatically substitute the
original media in the Integral volume set with the new backup media.

Note: For more detailed information about the vlinset command, please refer to Chapter 9 - Command Reference in this
manual.

Page 88 of 88
This chapter describes how to recover from various hardware failures. Earlier sections covered error recovery for each module,
this section covers overall steps to recovering Media sets in the event of a hardware failure, while ensuring minimum downtime
and preventing data loss or corruption. Any message relating to a hardware problem will be sent to the system console window
and recorded in the QStar syslog file.

This chapter covers instances of:

• Diagnostic utilities

• Drive failure in a jukebox

• Jukebox failure

• Power failure or system crash

• Recovery from magnetic disk cache failure

DIAGNOSTIC UTILITIES ................................................................................................................ 2

The QStar Syslog File................................................................................................................. 2
The Qscsi_log Command........................................................................................................... 2
The VLconsole Command .......................................................................................................... 6
Send Mail Notification ................................................................................................................ 6
DRIVE FAILURE IN A JUKEBOX .................................................................................................... 7
Recovery for Lost Source Shelf Information ......................................................................... 9
Example of Recovery for Unknown Shelf Type Information............................................ 10
Example - Clearing Unknown Shelf Type Information Error ....................................... 10
JUKEBOX FAILURE ........................................................................................................................ 11
ERROR CONDITION DURING MOUNT ....................................................................................... 12
ERROR HANDLING AND RECOVERY FOR ALL FILE SYSTEMS.............................................. 13
Error Condition while Processing a Delayed Event ............................................................ 13
Example of Error Condition in the Cache............................................................................. 13
POWER FAILURE, SYSTEM CRASH OR REBOOTING WITHOUT UNMOUNTING................ 14
RECOVERY FROM MAGNETIC DISK CACHE FAILURE ............................................................ 15
ERROR RECOVERY IN THE VL DATABASE ............................................................................... 16
ERROR RECOVERY USING DUPLICATE MEDIA ................................................................... 16
Set Status in the VL Database when a Duplicate Media is Imported into
the Jukebox................................................................................................................................ 17
TROUBLESHOOTING..................................................................................................................... 18

Page 1 of 22
DIAGNOSTIC UTILITIES
The QStar Software contains several diagnostic utilities allowing users to easily collect information about the status of the QStar
Software and the devices it is managing. They can be used as tools to monitor the system status and view events, errors and
warnings messages. These utilities provide a quick look at the activity of the actions performed by the QStar Software and can
help to identify and solve potential problems that occurred during the runtime of the system.

The QStar Software diagnostic utilities include:

- The QStar syslog file where all events, errors and warning messages are chronologically logged. This information can then
be used for debugging, detecting and diagnosing system errors or problem identification in the system.

- The qscsi_log command is used for device debugging purposes and allows the System Administrator to collect and view all
the SCSI commands issued to and received from the device in order to detect hardware errors.

- The vlconsole command is used to list and manage warning messages and Software requests sent by the QStar Software to
the System Administrator.

- The mail notification service will inform System Administrators of issues that arise in the storage configuration as soon
as they appear.

The QStar Syslog File

The QStar syslog file is located in the /opt/QStar/log directory. In this file the system events, errors, warnings and all the events
performed by the QStar Software are automatically logged. The QStar syslog file is not only a useful informational tool, but can
also be helpful in diagnostic situations, for example, it can be used for debugging and problem determination purposes.
All the information logged in the QStar syslog file is saved in a chronological list. The most recent events are listed last in the
list.
The QStar Software will collect all event information until the QStar syslog file reaches a size of 4 Mb.
Once the 2 Mb size is reached the QStar syslog file is automatically renamed to syslog.old and a new syslog file is created.
The QStar Software will save the last 8 Mb (4+4) of event information, so very old information might be lost.

The Qscsi_log Command

The qscsi_log command allows System Administrators to enable, disable and manage SCSI command logging and is a useful
tool for detecting and diagnosing hardware errors. The main hardware errors are displayed in the QStar syslog file as well, but
the qscsi_log command provides a more precise focus for error tracking.
The qscsi_log command logging is disabled by default, once enabled it collects all the SCSI information for the devices that
have been specified in the command. The SCSI information collected includes the commands sent by the QStar Software to the
selected device and any error codes returned by the device performing the SCSI command.

Page 2 of 22
The syntax of the qscsi_log command is as follows:

qscsi_log {-acCeEluULgt | -{n|f} device_name [{drive_number | all}]}

The qscsi_log command can be run with different options, the options are specified using the flags listed below:

-n|-f Enable (-n) or disable (-f) SCSI command logging for the selected device(s).

-a Disable SCSI log for all devices.

-g Get the SCSI log. The SCSI log is printed on stdout and saved in /opt/QStar/log/last_scsi_log file.

-l Print all bytes of the SCSI sense.

-L Print sense key, additional sense key and additional sense key qualifier only. This is the default.

-e Log only the SCSI commands with non-zero sense.

-E Log all SCSI commands. This is the default.

-c Copy SCSI log to /opt/QStar/log/scsi_log file by the SCSI log daemon.

-C Do not copy SCSI log to /opt/QStar/log/scsi_log file. This is the default.

-t Truncate /opt/QStar/log/scsi_log file to the size 0.

-u /opt/QStar/log/scsi_log file size limit is 4 MB. This is the default.

-U /opt/QStar/log/scsi_log file size unlimited.

Select the device(s) that should have the SCSI information logged by specifying the device_name and the optional drive_number.
If the drive_number is omitted, the option is applied to the robot and all the drives of this device. If the drive_number is equal to
0, the option is applied to the robot. Otherwise, the drive_number specifies the drive it is applied to.

A) Enable SCSI logging

The qscsi_log command allows collecting all SCSI information for only one jukebox at a time.

1) To enable SCSI logging for the changer and all drives contained in the jukebox identified as jb, enter:

#>qscsi_log -n jb

2) To enable SCSI logging for drive 1 only contained in the jukebox identified as jb, enter:

#>qscsi_log -n jb 1

3) To enable SCSI logging for drive 2 only contained in the jukebox identified as jb, enter:

#>qscsi_log -n jb 2

4) To enable SCSI logging for all drives within the jukebox identified as jb, enter:

#>qscsi_log -n jb all

Page 3 of 22
5) To enable SCSI logging for a standalone drive identified as rsdo0, enter:

#>qscsi_log -n rsdo0

6) To enable SCSI logging for a standalone drive identified as rdrive1, enter:

#>qscsi_log -n rdrive0

Immediately, for the selected device(s), the qscsi_log command will start to collect each SCSI command sent, including the
time, the device information (Scsi bus, Target ID, Lun), and the type and parameters of the SCSI command. In addition, the
sense key, additional sense key and additional sense key qualifier for the SCSI commands that return an error code will also be
logged.

B) Display the SCSI log

The QStar Software can display the last 50 commands or all the SCSI information logged.

1) To display the last 50 SCSI command in the stdout, enter:

#>qscsi_log -g

Note: Once displayed this information is also saved in /opt/QStar/log/last_scsi_log file.

2) To have the SCSI log daemon automatically collect all the SCSI command information in the /opt/QStar/log/scsi_log file,
enter:

#>qscsi_log -c

The information is displayed as follows:

Time Time in-Time out Bus,Tg.ID,Lun Command Scsi information

12:44:47 733 738 0:2:0 inquiry 12 00 00 00 38 00
12:44:47 738 746 0:2:0 inquiry 12 00 00 00 38 00
12:44:47 746 753 0:2:0 test unit ready 00 00 00 00 00 00
12:44:47 753 761 0:2:0 inquiry 12 00 00 00 38 00
12:44:47 763 769 0:2:0 mode sense 1a 00 1d 00 1a 00
12:44:47 769 777 0:2:0 mode sense 1a 00 1f 00 18 00
12:44:47 777 789 0:2:0 read picker status b8 01 1f 41 00 02 00 00 04 00 00 00
12:44:47 790 279 0:2:0 read shelf status b8 02 00 01 03 6b 00 00 da d0 00 00
12:44:48 281 294 0:2:0 read mail status b8 03 0f a1 00 0a 00 00 04 00 00 00
12:44:48 294 308 0:2:0 read drive status b8 04 17 71 00 06 00 00 04 00 00 00
12:44:48 308 320 0:2:0 read CD MSF b9 00 00 01 00 57 00 00 01 64 00 00

The QStar Software will collect all the SCSI information until the QStar scsi_log file reaches a size of 2 Mb. Once the 2 Mb size
is reached the QStar scsi_log file is automatically renamed to scsi_log.old and a new scsi_log file is created. The QStar
Software will save the last 4 Mb (2+2) of SCSI information, so very old information might be lost.

Note: The “-c” option disables the “-g” option; to reinstate the “-g” option run qscsi_log -C command.
Note1: In both case the most recent SCSI information are listed at the end of the stdout or the scsi_log file.

Page 4 of 22
C) Change the characteristic of the SCSI information logged

Once the SCSI logging is enabled, it is possible to change the characteristic of the SCSI information that is logged.

1) To collect all the SCSI information including all bytes of the SCSI sense, enter:
#>qscsi_log -l

Note: This option is useful for the SCSI commands that return an error code.

2) To collect sense key, additional sense key and additional sense key qualifier only (this is the default), enter:

#>qscsi_log -L

3) To collect only the SCSI commands that returns an error code (non-zero sense), enter:

#>qscsi_log -e

4) To collect all SCSI information (this is the default), enter:

#>qscsi_log -E

D) Disable SCSI logging

1) To disable SCSI logging for the changer and all drives contained in the jukebox identified as jb, enter:

#>qscsi_log -f jb

2) To disable SCSI logging for drive 1 only contained in the jukebox identified as jb, enter:

#>qscsi_log -f jb 1

3) To disable SCSI logging for drive 2 only contained in the jukebox identified as jb, enter:

#>qscsi_log -f jb 2

3) To disable SCSI logging for all drives within the jukebox identified as jb, enter:

#>qscsi_log -f jb all

4) To disable SCSI logging for a standalone drive identified as rsdo0, enter:

#>qscsi_log -f rsdo0

5) To disable SCSI logging for a standalone drive identified as rdrive1, enter:

#>qscsi_log -f rdrive0

6) To disable SCSI logging for all devices, enter:

#>qscsi_log -a

Note: If the qscsi_log command was started with one/or all of the options “-c”, “-e”, and/or “-l” and the qscsi_log command
was stopped using the “-f” flag. The next time the qscsi_log command is started the default will be whatever the previous
settings were. To reset the default before stopping the qscsi_log use the options “-C”, “-E” and /or “-L” before using the “-f”
flag.

Page 5 of 22
The VLconsole Command
The vlconsole command displays and manages warning messages and requests from the QStar Software to the System
Administrator.

It provides warning messages 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.

Using the vlconsole command it is possible to list these requests, check the status and if required cancel an event. QStar allows
the System Administrator to decide to cancel a request or to satisfy it, whichever is more convenient. The vlconsole –l command
displays a list of all the pending requests that the VL module sent to the System Administrator and their status. For example, a
typical request can be to import an erased or an offline media and the status can be pending, satisfied, or canceled.

Note: The cancel action can be applied to any VL request.

Note1: For more detailed information on the vlconsole command, please refer to Chapter 9 - Command Reference or read the
"Managing Offline Media under VL Control" section in Chapter 5 - The Volume librarian in this manual.

Send Mail Notification

QStar creates a special file called send_notification under the /opt/QStar/install directory.

The System Administrators can get mail notification about abnormal events in the QStar Software.
Abnormal events are - drive/jukebox failures, unrecoverable write errors, requests for additional medium (no more space in the
Integral Volume set), requests for medium that is currently offline, etc.
QStar Software puts messages into the /opt/QStar/log/message file and then executes this script.
To receive the mail, please select the appropriate mail program for your computer and
set the DESTINATION_MAIL_ADDRESS ([email protected]).

To test this script please create the /opt/QStar/log/message file and execute the script.

DESTINATION_MAIL_ADDRESS=
if [ -n "$DESTINATION_MAIL_ADDRESS" -a -f /opt/QStar/log/message ]; then
#
# /bin/mail $DESTINATION_MAIL_ADDRESS < /opt/QStar/log/message
# /usr/sbin/Mail -s "message from QStar server" $DESTINATION_MAIL_ADDRESS < /opt/QStar/log/message
# /usr/sbin/mailx -s "message from QStar server" $DESTINATION_MAIL_ADDRESS < /opt/QStar/log/message
# /usr/bin/mailx -s "message from QStar server" $DESTINATION_MAIL_ADDRESS < /opt/QStar/log/message
#
mv /opt/QStar/log/message /opt/QStar/log/message.old

Page 6 of 22
DRIVE FAILURE IN A JUKEBOX
If the jbscheduler daemon detects an error during access to the media in a drive, jbscheduler automatically marks this drive as
bad and pauses all I/O requests to the device. All other drives will function as normal. The System Administrator can determine
where the problem originates by using the jbstatus command:

jbstatus [-H host_name] [-csmdp] device_name

To display the jukebox status, enter:

#>jbstatus jb
DISK-jb – JUKEBOX TYPE
-----------
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: online full bad loaded shelf 1a Note: Drive is marked bad.
Drive 2: online empty
-----------
Shelf 1: online loaded bad open drive 1 Note: Shelf is marked bad.
Shelf 2: online full
Shelf 3: online full
Shelf 4: online empty
Shelf 5: online empty

The System Administrator can follow two procedures to clear the drive and media bad status:

A) Use the jbreset command (Example 1).

jbreset [-H host_name] device_name drive_number [shelf_number]

B) Use jbdrive and jbshelf commands (Example 2).

jbdrive [-H host_name] [-nfbr] [-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}] device_name drive_number

jbshelf [-H host_name] [-nfbr1AB] device_name shelf_number [-p {cd-rom | cd-r | cd-rw | dvd-rom | dvd-r | dvd-ram |
dvd-rw | dvd-rw-s}] device_name shelf_number

Both procedures will reset the drive, unload the media to its storage shelf and clear both bad flags. The I/O request will then
continue. If the same drive is again marked bad, the drive should be set offline using the jbdrive command until it is repaired.
Once the drive is functional, it can be set online with the jbdrive command.

Page 7 of 22
Example 1 - Clear the bad status on the drive and media using the jbreset command.

#>jbreset jb 1
JB: jb drive 1: is set offline
JB: jb shelf 1: is set offline
JB: jb drive 1: is set online
JB: jb shelf 1: is set online

#>jbstatus jb
DISK-jb – JUKEBOX TYPE
-----------
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: online empty Note: Drive is unloaded and bad flag is cleared.
Drive 2: online empty
-----------
Shelf 1: online full Note: Shelf’s bad flag cleared.
Shelf 2: online full
Shelf 3: online full
Shelf 4: online empty
Shelf 5: online empty

Example 2 - Clear a bad status for a drive and shelf using the jbdrive and jbshelf commands to take the drive and shelf offline
and online.

#>jbdrive -bf jb 1 Note: Sets the drive offline, this will eject the media from
JB: jb drive 1: is set offline the drive, and return it to the shelf.

#>jbshelf -bf jb 1 Note: Sets the shelf offline and reset the bad flag on shelf 1.
JB: jb shelf 1: is set offline

#>jbdrive -n jb 1 Note: Sets the drive online after repair, so it available.

JB: jb drive 1: is set online

#>jbshelf -n jb 1
jb shelf 1: is set online Note: Sets the shelf 1 online, so it available.

Page 8 of 22
Recovery for Lost Source Shelf Information
This error can be introduced by human intervention or hardware failure. In this case, the jukebox loads a media into the drive,
and because of a hardware error, forgets which shelf the media came from. The jbstatus command output displays this media as
having lost the source shelf information. The QStar Software redirects the following message into the /opt/QStar/log/syslog file
as well as displaying it on the system console window:

JB: jb drive 1: Source shelf information lost - use jbreset

To clear this error the System Administrator must use the jbreset command additionally specifying an empty shelf number
that will be used by the QStar Software as the destination for this media.

jbreset [-H host_name] device_name drive_number [shelf_number]

Example - Clear the Lost Source Shelf Information Error.

#>jbstatus jb
DISK-jb – JUKEBOX TYPE
-----------
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: online full lost source shelf Note: Drive is full with unknown media.
Drive 2: online empty
-----------
Shelf 1: online empty
Shelf 2: online full
Shelf 3: online full
Shelf 4: online empty

#>jbreset jb 1 1 Note: Shelf 1has been selected as the destination shelf.

#>jbstatus jb
DISK-jb – JUKEBOX TYPE
-----------
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: online empty Note: Drive is empty and the error is cleared.
Drive 2: online empty
-----------
Shelf 1: online full Note: Shelf is full.
Shelf 2: online full
Shelf 3: online full
Shelf 4: online empty

Page 9 of 22
Example of Recovery for Unknown Shelf Type Information
This error can be introduced by a hardware failure during the refreshing operation executed with the vlrefresh command and it
is specific for DVD/CD jukeboxes with mixed drives types or drives that support different types of media. Prior to the refresh
procedure, all media types are assigned for every full shelf. This allows the loading of the media into all drives during the
refresh procedure to determine the correct media type for each 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 the media
type. If during the refresh procedure the jukebox loads media into a drive and because of a hardware error could not detect the
media type of the shelf, the QStar Software automatically will remove all the profile information for the shelf in order to force
the System Administrator to refresh the shelf once again. The jbstatus command output displays this shelf without the media
type information. Using the jbshelf command with -r flag will reset the profile information for the media. The correct media
type for the shelf will then be determined at the next refresh.

Example - Clearing Unknown Shelf Type Information Error

#>jbstatus jb
DVD-jb – JUKEBOX TYPE
------------
Carrier 1: empty
------------
Mailslot 1: empty
------------
Drive 1: cd-rom dvd-rom dvd-r dvd-ram online empty
Drive 2: cd-rom dvd-rom dvd-r dvd-ram online empty
Drive 3: cd-rom dvd-rom dvd-r dvd-ram online empty
Drive 4: cd-rom dvd-rom dvd-r dvd-ram online empty
------------
Shelf 1: cd-rom 1-side online full
Shelf 2: online full Note: The Shelf 2 is displayed without media type
Shelf 3: dvd-ram online full information.
Shelf 4: dvd-r 1-side online full

#>jbshelf -r jb 2
jb shelf 1: is set online cd-rom dvd-rom dvd-r dvd-ram
Shelf 1: cd-rom dvd-rom dvd-r dvd-ram online full

#>jbstatus jb
DVD-jb – JUKEBOX TYPE
------------
Carrier 1: empty
------------
Mailslot 1: empty
------------
Drive 1: cd-rom dvd-rom dvd-r dvd-ram online empty
Drive 2: cd-rom dvd-rom dvd-r dvd-ram online empty
Drive 3: cd-rom dvd-rom dvd-r dvd-ram online empty
Drive 4: cd-rom dvd-rom dvd-r dvd-ram online empty
------------
Shelf 1: cd-rom 1-side online full
Shelf 2: cd-rom dvd-rom dvd-r dvd-ram online full
Shelf 3: dvd-ram online full
Shelf 4: dvd-r 1-side online full

Note: The Shelf 2 is displayed with all media types. The correct media type for the shelf will be determined by running the
vlrefresh command for the specific shelf.

Page 10 of 22
JUKEBOX FAILURE
In the event of jukebox failure, media cannot be moved between the shelves and drives. Depending upon jukebox manufacturer
and model, there may be an error code in the jukebox display. Refer to the jukebox manual for this information. The following
steps should be carried out:

1) Terminate any read/write processes to the jukebox if possible.

2) Unmount all media sets if possible.

3) Shut down the workstation.

4) Rectify the failure on the jukebox.

5) Ensure the jukebox is configured the same as before the failure (SCSI Ids, etc), then restart the workstation.

6) Refresh the jukebox with vlverify and vlrefresh -f commands, for more detailed information see Chapter 9 - Command
Reference in this manual.

7) Remount all sets. All sets will mount quickly if they unmounted cleanly, sets that would not unmount may take longer to
mount.

Page 11 of 22
ERROR CONDITION DURING MOUNT
The mountiv command can return with an error condition.

This section will explain what these errors mean and how to remedy them.

Error message example 1:

mountiv: host_name: , set Test: Migrator files invalid or belong to different set

This error means that the sdf_db files are corrupted or are already in use with another Integral Volume set. Check to see if the
cache root directory specified for this Integral Volume set is the same as another Integral Volume set. If it is the same, change it
or remove all files inside the cache root directory and run the mountiv command.

Error message example 2:

mountiv: /export/home/Test: host_name: , set Test: prepare cache: Cache files belong to different filesystem

This error means that the “cfs_*” files are already in use with another Integral Volume set (set with cache). Check to see if the
cache root directory specified for this Integral Volume set is the same as another Integral Volume set. If it is the same, change it
or remove all files inside the cache root directory and run the mountiv command again with the option, “-n”.

Error message example 3:

mountiv: host_name: , set Test: Busy directory or mount point

This error means that the mount point specified for this Integral Volume set is already in use by another Integral Volume set or
file system. Change the mount point directory.

Error message example 4:

mountiv: /export/home/Test: clean_cache required: Cache files may need to be recreated. Use -f flag to mount with
existing cache

This error means that the “cfs_*” files may already be in use by another or old Integral Volume set. Check to see if the cache
root directory specified for this Integral Volume set is the same as another Integral Volume set. If it is the same, change it or
remove all files inside the cache root directory or run the mountiv -n command to clean the cache. If the cache root directory
belonged to an Integral Volume set that was recreated, run the mountiv -f command to mount using the existing cache files.

Error message example 5:

mountiv: /export/home/Test: Migrator files may need to be recreated. Use -f flag to mount with existing migrator
database

This error means that the Integral Volume set information has been recreated and the sdf_db files have been used with a
different or old Integral Volume set. If the Integral Volume set is the same as the old one and only the Integral Volume set
information has changed, run the mountiv -f command to mount using the existing migrator database. If the Integral Volume set
is not the same, remove all files inside the cache root directory or run the mountiv -n command to clean the cache.

Page 12 of 22
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
jukebox 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. In this condition the archiving will stop. In addition, any processes waiting on an event, which
requires access to the archive, will return errors as will any new accesses to the Integral Volume set which require access to the
archive. Any accesses to the Integral Volume set, which does not require access to the archive, will process as normal.

Example of Error Condition in the Cache

If an error condition occurs in the cache, the QStar Software directs an error message to the system console window and the
/opt/QStar/log/syslog file.

Below is an example of the error messages:

mmserver: /cache/103019992: Covered file system error: No such device or address:

PAGE_FAULT: Client UID=0, Client GID=0
Cnode_number=6602, Ino=7273, page_number=0, page_address=155, map_size=65536

The status of the cache can be monitored using the mmparam command and if an error occurs, the “Error Condition” line of
this command will display the following message:
Error condition: COVERED ERROR

At this point, the System Administrator can fix the problem with the archive and resume normal processing by clearing the error
condition of the Integral Volume set using the following command:

#>mmresume (mount_point | set_name)

Note: This command can be used in conjunction with two different flags, “-e” and “-n”. Never use these flags without
contacting QStar Technical Support Personnel first. For more detailed information on the mmresume command, please refer
to Chapter 9 - Command Reference in this manual.

Note1: If a DVD jukeboxes is used once the covered error is cleared using the mmresume command, QStar highly recommends
checking to see if the media type information of the current write surface is still reported correctly in the jbstatus output . 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 on this chapter.

If necessary, the Integral Volume set may be unmounted and the system halted to repair the problem with the archive prior to
issuing the mmresume command. During this entire process, the maximum level of availability to data is maintained while at
the same time protecting the Integral Volume set from data loss or corruption.

Page 13 of 22
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 UNIX fsck command:

Platform Command (example)

Sun Solaris fsck /dev/rdsk/c0t3d0s5
HP/UX fsck /dev/vg00/rvol4
IBM AIX fsck /dev/lv08

2) Remount the sets using the mountiv command. Some sets may take longer to mount, as the QStar Software may need to
carry out further recovery procedures or consistency checks.

3) After the set is mounted, try to access a file. If an I/O error is received it means that the db_files (sdf_db or udf_db files)
present in the cache partition are corrupted.

To rebuild these index_files, umount the sets and run the following commands:

vlrestore_fsdb set_name For SDF and UDF file system.

vlrestore_fsdb [-D SDF_span_number] set_name

For SDF file system, specify the SDF volume number (starting from 1), which must be used for restoring SDF database.
Without this option (or if volume number is equal to 0) the SDF database will be restored from the last surface in the set.
The database will be restored from specified volume and SDF events will be replayed from that medium. The saved
database on the next volume will not be used to restore data base. Rather the data portion of the SDF volume will be
scanned and events replayed. This process continues until last medium (surface) in the set is scanned. The mirrored SDF
volume set restore with this option is not supported.

vlrestore_fsdb [-D {UDF_span_number|+}] set_name

For UDF file system with Spanning Interchange Level. 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 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).

Once the vlrestore_fsdb command has completed remount the Integral Volume sets.

Note: 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.

Page 14 of 22
RECOVERY FROM MAGNETIC DISK CACHE FAILURE
In the event of a magnetic disk failure that contains the cache, the cache data will need to be rebuilt from the media contained in
the set. Since the media set is a self contained file system, the cache can be recovered from the media set. After the cache is
rebuilt, initial access to the set will be slow. Requests are serviced from the archive media. This information is then cached. This
is refereed to as “rebuild on demand”. To speed up this process, a user can force a demand by requesting the directory structure
in part or in full, the UNIX ls command can be used to achieve this. Then, any future access to files will ensure the directory
information is already in cache, improving performance. The cache can be rebuilt to the same or different location. If disk space
is available, you can change the location of the cache.

To rebuild the cache (in the same location), use the “-n” flag for the mountiv command to specify a new cache.

Example:
#>mountiv -n set1 /optical

To rebuild the cache in a new location, use the vlcache command to specify the new location. Next, use the mountiv command
with the “-n” flag.

Example:
#>vlcache -p XXX -c /cache/set1_cache set1

This specifies /cache/set1_cache as the cache location and XXX as the number of 64K pages in cache (cache size).
#>mountiv -n set1 /optical

This will mount the Integral Volume set with a new cache using the parameters specified in the vlcache command.

Page 15 of 22
ERROR RECOVERY IN THE VL DATABASE
QStar's Software contains features that allow you to recover from most errors introduced by human error or caused by hardware
failure. If the VL database gets out of synch with the jukebox status, this can be due to a hardware problem or human
intervention with the jukebox. To recover from this, there is a utility called vlrefresh that can be run on a single shelf, multiple
shelves or all the shelves contained in the jukebox. See the Chapter 9 - Command Reference for full details or Chapter 5 -
The Volume Librarian in the “Fixing Database Inconsistencies” section.

ERROR RECOVERY USING DUPLICATE MEDIA

The QStar Software does not allow the use of identical or duplicate media in the jukebox. Duplicate media can be created, for
example, by using the copydisk command or by vlimporting a CD-ROM that is identical to another CD-ROM already present in
the jukebox. When the VL database detects a duplicate media, it marks the identical media as “dup” within the VL database. 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 jukebox using the vlexport command.

Example of error message when vlimport command imports a duplicate media:

#>vlimport jb 1
jb: refreshing shelf 1 ...
vlimport: Medium in the VL database already exists

The vllsdev command displays the duplicate optical media as follows:

#>vllsdev jb

jb JUKEBOX TYPE
FS_type Size Type LabelName/Seq_no Set_id/SetName
----------------------------------------------------------------------------
1a: dup 2.4 Gb Rewritable Seq=0 SetId=807aeea2.34ba1fc5
1b: dup 2.4 Gb Rewritable Seq=2 SetId=807aeea2.34ba1fc5
2a: dup 2.4 Gb Rewritable Seq=0 SetId=807aeea2.34ba1fc5
2b: dup 2.4 Gb Rewritable Seq=2 SetId=807aeea2.34ba1fc5
Note: In the example, the SDF file system is used.

To solve the problem created by the duplicate media, it is sufficient to export one of the identical media from the jukebox using
the vlexport command.

The following example shows that exporting the media on shelf 1 with the vlexport command solves the duplicate media
problem. After the media is exported, the vllsdev command displays the appropriate information about the media. If the media
belongs to an Integral Volume set, the Integral Volume set is now mountable.

Using the vlexport command the duplicate media is removed from the jukebox:

#>vlexport jb 1

The vllsdev command now displays the following information:

#>vllsdev jb

jb JUKEBOX TYPE
FS_type Size Type LabelName/Seq_no Set_id/SetName
----------------------------------------------------------------------------
1a: sdf 2.4 Gb Rewritable Seq=0 SetId=807aeea2.34ba1fc5
1b: sdf 2.4 Gb Rewritable Seq=2 SetId=807aeea2.34ba1fc5

Page 16 of 22
Set Status in the VL Database when a Duplicate Media is
Imported into the Jukebox
If the duplicate media is identical to a media already added to the Integral Volume set, the vlserver, that manages the VL
database, locks the Integral Volume set making the Integral Volume set temporarily unavailable until the duplicate media is
exported from the jukebox using the vlexport command.

#>mountiv Test /mnt

mountiv: host #####, set Test: read database: Set non-accessible

The vllsset command displays the following information:

#>vllsset -v Test
Test
Use_media=disk,writable Spread=no Quota=1024 Media=8
Restore_fsdb=no Read_only=no Make_copy=no
Set status=Not mountable. There are duplicate media
Set_type=sdf (standard data format)
SetId=5246b54c.36fa4670
Cache: Cache_root=/home/cache_Test
Max_number_of_pages=100
0: Online=jb:1 Sequence_numbers=0,1 Mounted=a,b
2: Online=jb:2 Sequence_numbers=2,3 Mounted=a,b

Page 17 of 22
TROUBLESHOOTING
In this section, the most frequently encountered warning and error messages are listed and explained with the relative solution.

MESSAGE DISPLAYED FOR ALL JB COMMAND PROBLEM AND SOLUTION

Example: The drive number is wrong. With the jbstatus command,

jbdrive -f jb 6 check the number of drives present in the jukebox.
Message:
jbdrive: jb, drive 6: Invalid drive number

Example: The shelf number is wrong. With the jbstatus command,

jbshelf -f jb 200 check the number of shelves present in the jukebox.
Message:
jbshelf: jb, shelf 200: Invalid shelf number

Example: The device name is wrong. with the vllsdev –a

jbstatus jb command, check the device name.
Message:
jbstatus: jb: No such device

Example: The jbscheduler cannot be stopped because the device is

jbshut jb busy. Check to see if any sets are mounted. If there are,
Message: unmount them all and stop the jbscheduler by running
jbshut: /dev/jbctl: jb, drive 2: call kernel: the jbshut command.
Device busy

Example: The QStar _jbserver server isn’t running.

jbstatus jb Check the QStar syslog file for the problem. If the
Message: license key is invalid or expired, get a new license and
jbstatus: jb: create_client: connect: go to the /opt/QStar/install directory and run ./rc stop
Connection refused followed by ./rc start.

Example: The device is not available due to a hardware problem.

jbimport jb 21 Call QStar Customer Support for additional instructions.
Message:
jbimport: jb: /dev/jb/jbctl: Q_SCSI_PT_CMD
ioctl: No such device or address

Page 18 of 22
MESSAGE DISPLAYED FOR ALL VL COMMAND PROBLEM AND SOLUTION

Example: The device name is wrong. With the vllsdev –a

vllssev jb command, check the device name.
Message:
vllsdev: host xxx:, device jb: check device
name: Invalid device name

Example: This message will appear only after an upgrade of the

vlrefresh jb 1:10 QStar Software. The version of the VL database is not
Message: compatible with the new one.
vlrefresh: host xxx:, device jb: read device Go to /opt/QStar/vl/files/devices and remove the device
conf: Invalid version of database file (i.e. jb). Then run vlrefresh command.

Example: The specified shelf exceeded the number of available

vlrefresh jb 123 shelves in the jukebox.
Message: Run either vllsdev command or jbstatus command to see
vlrefresh: host xxx: , device jb: shelf 123: the correct number of available shelves.
Invalid shelf number

Example: This message notifies the user that a duplicate media

vlrefresh jb 42 was imported into the jukebox and the set was made
Message: inaccessible to avoid any major disasters.
vlrefresh: host xxx: set Test: read database: For more detailed information, please refer to the Error
Set non-accessible Recovery Using Duplicate media section of this
chapter.

Example: The specified shelf is wrong.

vlrefresh jb 0 Run either vllsdev command or jbstatus command to see
Message: the correct number of available shelves.
vlrefresh: 0: Number out of range

Example: This message will appear only after an upgrade of the

vllsset -v Test QStar Software. The version of the VL database is not
Message: compatible with the new one or the set file in the VL
vllsset: host xxx: set Test: read database: database is corrupted.
Invalid size of database Go to /opt/QStar/vl/files/sets and remove the set file (i.e.
Test) and recreate the set definition with the vlcrset,
vladdtoset and vlcache commands.

Example: The specified set does not exist in the VL set database.
vldelset Test Using the vllsset –a command, check the set names that
Message: are available in the VL set database.
vldelset: host xxx: set Test: open set
database: Set does not exist

Page 19 of 22
Example: The specified shelf cannot be added to the set because
vladdtoset Test jb 6 it is empty or it contains a type of media that does not
Message: match the type of media specified for the set in the VL
vladdtoset: host xxx: , device jb: shelf 6: set database.
Medium cannot be added to set Using with vllsset –va command, check the
specification made for the media in the VL set database.

Example: The QStar _vlserver server is not running.

vllsdev jb Check the QStar syslog file for the problem. If the
Message: license key is invalid or expired, get a new license and
vllsdev: connect: create_client: Connection go to the /opt/QStar/install directory and run ./rc stop
refused followed by ./rc start.

Example: The QStar _vlserver server is not running.

vllsset -va Check the QStar syslog file for the problem. If the
Message: license key is invalid or expired, get a new license and
vllsset: connect: create_client: Connection go to the /opt/QStar/install directory and run ./rc stop
refused followed by ./rc start.

Example: The shelf cannot be refreshed because the jbscheduler is

vlrefresh jb not running or the drives are all in an offline or bad
Message: condition.
vlrefresh: current host: device jb: No drives Check to see if the jbscheduler is running using the
available jbschedcheck command. If it is not running, start it with
the jbscheduler command.
With the jbstatus command, check the status of the
drives in the jukebox. If they are bad, clear the bad state
with the jbreset command.

Example: The media cannot be erased because it belongs to a set.

vlerase jb 16 Check the status of the shelf in VL database by running
Message: the vllsdev –n command and then check the set status by
vlerase: host xxx: device jb: , shelf 16: running vllsset command. If the media belongs to a set
Medium belongs to set and it is the correct media to be erased, delete the set by
running the vldelset command and erase the media.

Example: The media cannot be erased because it is inaccessible.

vlerase jb 42 Check the status of the shelf in VL database by running
Message: the vllsdev command if the shelf is displayed as
vlerase: Medium inaccessible inaccessible set the shelf online by running the jbshelf -
n command. Refresh the media by running vlrefresh
command and erase the media.

Example: The destination shelf selected for the vlcopy command

vlcopy -v jb:34 jb:42 is empty or doesn't contain a blank or erased media.
Message: Check the status of the shelf in VL database by running
vlcopy: host xxx: device jb: shelf 42: the vllsdev command.
copy_medium: No medium to initialize

Page 20 of 22
MESSAGE DISPLAYED FOR QSTAR MOUNT COMMAND PROBLEM AND SOLUTION

Example: The specified set doesn’t exist in the VL set database.

mountiv Test /mnt Using the vllsset –va command, check the available sets
Message: in the VL set database.
mountiv: host xxx: , set Test: open set
database: Set does not exist

Example: This message notifies the user that a duplicate media

mountiv Test /mnt was imported into the jukebox and the set was made
Message: inaccessible to avoid any major disasters.
mountset: host xxx: , set Test: read For more detailed information, please refer to the
database: Set non-accessible “Error Recovery Using Duplicate media” section of
this chapter.

Example: The specified set cannot be mounted without cache. The

mountiv Test /mnt file system specified in the VL set database requires the
Message: set to be mounted with cache.
mountiv: host xxx: , set xxxx: host xxx: , Run the vllsset –va command to check the VL set
set Test: Cannot be mounted without cache information for the set and run the vlcache command to
specify the cache for the set.

Example: The specified set cannot be mounted without cache. The

mountset Test /mnt file system specified in the VL set database requires the
Message: set to be mounted with cache.
mountset: current host: , set Test: Cannot be Mount the set with the mountiv command.
mounted without cache

Example: The set cannot be mounted because the current write

mountiv Test /mnt1 media is set offline or was manually exported from the
Message: jukebox.
mountiv: host xxx: , set Test: No such device

Example: The set cannot be mounted because it doesn’t exist in

mountiv Test /mnt the VL set database.
Message: Using the vllsset –va command, check the available sets
mountiv: host xxx: , set Test: open set in the VL database.
database: Set does not exist

Example: The mount_point used to mount the set is already in use

mountiv Test /mnt for another one.
Message: Mount the set on a different mount_point.
mountiv: host xxx: , set Test: Busy directory
or mount point

Example: The set is already mounted.

mountiv Test /mnt
Message:
mountiv: host xxx: , set Test: Is mounted

Example: The QStar _mmserver server isn’t running.

mountiv Test /mnt Check the QStar syslog file for the problem. If the
Message: license key is invalid or expired, get a new license and
mountiv: connect: create_client: Connection go to the /opt/QStar/install directory and run ./rc stop
refused followed by ./rc start.

Page 21 of 22
Page 22 of 22
This chapter describes all the QStar commands and displays some examples for more detail.

QSTAR REMOTE ADMINISTRATION INTERFACE .................................................................. 3

Remote Administration of a UNIX Server from a UNIX Machine.................................. 3
Remote Administration of a UNIX Server from a WINDOWS Machine........................ 6
COMMAND CONVENTIONS........................................................................................................ 9
CMPDISK..................................................................................................................................... 10
COPYDISK................................................................................................................................... 11
FLOC ............................................................................................................................................ 12
FLSVOL ........................................................................................................................................ 13
JBCLEANING............................................................................................................................... 14
JBDRIVE ...................................................................................................................................... 15
JBEXPORT ................................................................................................................................... 17
JBFLIP.......................................................................................................................................... 18
JBIMPORT ................................................................................................................................... 19
JBLOAD........................................................................................................................................ 22
JBMAGAZINE.............................................................................................................................. 23
JBMOVE ....................................................................................................................................... 24
JBPARAM ..................................................................................................................................... 25
JBPING ........................................................................................................................................ 28
JBRESERVE................................................................................................................................. 29
JBRESET...................................................................................................................................... 30
JBSCHEDCHECK ........................................................................................................................ 31
JBSCHEDULER ........................................................................................................................... 32
JBSHELF ...................................................................................................................................... 33
JBSHUT........................................................................................................................................ 35
JBSIM........................................................................................................................................... 36
JBSTATISTICS............................................................................................................................ 40
JBSTATUS ................................................................................................................................... 42
JBUNLOAD .................................................................................................................................. 43
MKISO ......................................................................................................................................... 44
MKUDF......................................................................................................................................... 47
MMADMIN ................................................................................................................................... 48
MMARC ........................................................................................................................................ 50
MMCHMOD.................................................................................................................................. 52
MMEXEC ...................................................................................................................................... 55
MMDELAY .................................................................................................................................... 57
MMLS ........................................................................................................................................... 59
MMPARAM ................................................................................................................................... 61
MMPING ...................................................................................................................................... 63
MMPURGE ................................................................................................................................... 64
MMRESUME ................................................................................................................................ 65
MMSUBTREE............................................................................................................................... 66
MOUNTIV .................................................................................................................................... 68
QCENTERA .................................................................................................................................. 70
UDFDF ......................................................................................................................................... 75
UMOUNT...................................................................................................................................... 76
UMOUNTIV.................................................................................................................................. 77
VLADDTOSET ............................................................................................................................. 78
VLCACHE..................................................................................................................................... 81

Page 1 of 138
 VLCLOSE ..................................................................................................................................... 84
VLCMP.......................................................................................................................................... 85
VLCONSOLE................................................................................................................................ 87
VLCOPY........................................................................................................................................ 89
VLCRSET ..................................................................................................................................... 92
VLDELFROMSET....................................................................................................................... 100
VLDELSET ................................................................................................................................. 101
VLEDITSET ............................................................................................................................... 102
VLERASE ................................................................................................................................... 106
VLEXCHANGE ........................................................................................................................... 109
VLEXPORT................................................................................................................................. 110
VLIMPORT ................................................................................................................................. 112
VLINSET .................................................................................................................................... 117
VLLSDEV ................................................................................................................................... 119
VLLSSET.................................................................................................................................... 121
VLMAGAZINE............................................................................................................................ 123
VLMEDIAUSAGE ...................................................................................................................... 124
VLMVSET................................................................................................................................... 125
VLPING ...................................................................................................................................... 126
VLQLIST .................................................................................................................................... 127
VLQMOVE.................................................................................................................................. 128
VLQREMOVE ............................................................................................................................. 129
VLRECORD................................................................................................................................ 130
VLREFRESH .............................................................................................................................. 132
VLREPLACE ............................................................................................................................... 134
VLRESTORE_FSDB .................................................................................................................. 135
VLREUSE ................................................................................................................................... 136
VLVERIFY .................................................................................................................................. 138

Page 2 of 138
QSTAR REMOTE ADMINISTRATION INTERFACE
The QStar commands can be used to remotely configure and manage any devices controlled by another QStar server. If user
access is allowed, the Remote Administration can be run from any workstation on the network. The System Administrator can
remotely run all the QStar commands by including the “-H host_name” option with the command. In addition, it is possible to
use the admin.exe GUI program from Windows 2000/2003/XP/Vista/2008. Before using the admin.exe command to remote
administer a remote host, the Remote Administration option must be enabled on the local server.

Below are the fields related to the Remote Administration from the “/opt/QStar/vl/files/conf” file.

# Remote Administration - {Prohibited | Allowed | Allowed Hosts}

Remote Administration = "Prohibited"
Remote Administration Allowed Hosts = ""

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: Once changed, the service has to be stopped/started to take effect.

Remote Administration of a UNIX Server from a UNIX Machine

To remotely run the QStar commands from another server follow the procedure below:

1) Create the /opt/QStar directory on the remote server

2) Copy the correct QStar release in the /opt/QStar directory
3) On the main server, add the remote username to the priv.user file in the /opt/QStar/install directory to allow QStar commands
to be run.

Note: For more detailed information about priv.users setting, please refer to Chapter 3 - Installing and Configuring QStar
Software in this manual.

All the QStar commands are available in the /opt/QStar/bin directory and the System Administrator can check which commands
can be run remotely by reading the description of the QStar commands found in this chapter.

Note: No license is required to intall the remote server to remotely run the QStar commands.

Page 3 of 138
A) Example of the vllsset command ran on the remote server:

alfa#>vllsset -H beta -va

beta:Test
Use_media=disk,writable Spread=no Quota=2048 Media=3
Restore_fsdb=no Read_only=no Make_copy=no
Set_type=sdf (standard data format)
SetId=8c0110ac.3bf06577
Cache: Cache_root=/export/home/cache_Test
Max_number_of_pages=1600 (100 MB)
Page_size=64 Kbytes
Mounted at /mnt
0: Online=jb:2 Sequence_numbers=0,1 Mounted=a,b
2: Online=jb:10 Sequence_numbers=2,3 Mounted=a,b
4: Online=jb:15 Sequence_numbers=4,5 Mounted=a,b

Note: The server name is also diplayed in the vllsset command output.

B) Example of the jbstatus command ran on the remote server:

alfa#>jbstatus -H beta jb
Carrier 1: empty
Carrier 2: empty
-----------
Mailslot 1: empty
-----------
Drive 1: online full loaded shelf 2a
Drive 2: online empty
-----------
Shelf 1: online empty
Shelf 2: online loaded open drive 1
Shelf 3: online empty
Shelf 4: online empty
Shelf 5: online empty
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
Shelf 13: online empty
Shelf 14: online empty
Shelf 15: online full
Shelf 16: online full

C) Example of the vllsdev command ran on the remote server:

alfa#>vllsdev -H beta jb
beta: jb JUKEBOX TYPE
FS_type Size Type LabelName/BC/Seq_no Set_id/SetName
-----------------------------------------------------------------------------
1: empty

Page 4 of 138
 2a: sdf 2.4 Gb Rewritable Seq=0 SetId=687077ff.3b535493
2b: sdf 2.4 Gb Rewritable Seq=1 SetId=687077ff.3b535493
3: empty
4: empty
5: empty
6: empty
7: empty
8: empty
9: empty
10a: sdf 2.4 Gb Rewritable Seq=2 SetId=687077ff.3b535493
10b: sdf 2.4 Gb Rewritable Seq=3 SetId=687077ff.3b535493
11: empty
12: empty
13: empty
14: empty
15a: sdf 2.4 Gb Rewritable Seq=4 SetId=687077ff.3b535493
15b: sdf 2.4 Gb Rewritable Seq=5 SetId=687077ff.3b535493
16a: erased
16b: erased

Note: The server name is also diplayed in the vllsdev command output.

D) Example of the mmparam command ran on the remote server:

alfa#>mmparam -H beta Test

Cache root: /export/home/cache_Test
Mount point: /mnt
Max number of pages: 200 (12800 Kbytes)
Flush on umount: No
Low primary capacity: 0 pages (0 Kbytes)
High primary capacity: 160 pages (10240 Kbytes)
Page size: 64 Kbytes
Present pages: 142
Primary pages: 110
Replicated pages: 32
Archived pages: 0
Keep in cache: 0
Archive never: 0
Files in cache: 8102
Number of delayed events: 21
Read/write access: Read-write
Mount state: Mounted
Error condition: No
Stop on covered error: Yes
Archiving: Not started
Migrator: sdf
Medium drive type: ERASABLE
Writing to partition: /opt/QStar/dev/jb/rjb15b
Number of partitions: 12
Max.number of opened partitions: 8
Max.number of write buffers: 2
Compression: Off

Page 5 of 138
Remote Administration of a UNIX Server from a WINDOWS
Machine
QStar Software UNIX Version can be operated with limited functionality using the the admin.exe program from a Windows
2000/2003/XP/2008 Operating System. Once the Remote Administration is enabled the System Administrator can run the
admin.exe command. To Start the Remote Administration Interface run the following command.

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

Not all functionality is available for the remotely administered system and some view panes are missing completely from the
Remote Administration Interface. All the functionality of the QStar Administration Interface are explained in the QStar
System Administrator's Guide for Windows platforms.

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:
Security
Available view panes:
Server Status
Unavailable Functions:
Change Server Priority
Access Security view pane
Starting / Stopping Servers
Installing / Un-installing Software
Changing Security
Available Functions:
Server / Daemons Status

Devices:
Unavailable view pane:
Jukebox Configuration
Unavailable Functions:
Reconfigure Jukebox
Troubleshooting
Available view pane:
Jukebox Status
Unavailable Functions:
Access To Troubleshooting (all low level qscsi commands)

Page 6 of 138
 Available Functions:
Edit JB Parameters
Drive/Shelf Manipulation (On/Off/Reset)
Element Status
Jukebox Statistics
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 Medias (Appears Available)
Available Functions:
Copying Media
Comparing Media
Integral Volumes:
Unavailable view pane:

Available view pane:

Volume Management
Unavailable Functions:
Creating Mirrored Sets
Editing Mirror Sets
Mounting Integral Volumes
Creating Cache Directories
Browsing Local Machine For Cache Locations
Mounting on Server Restart

Available Functions:
Creating SDF/UDF Integral Volumes
Unmounting Sets
Starting / Stopping Secondary Mirrors
Viewing Sets Information
Altering Cache Size, and HPC/LPC Attributes
Switching to Mount on Clean Cache, and Rebuild Database

Page 7 of 138
 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
Keep Full File
Don't Keep Full File
Add tree
Copy Tree
Copy Data (Prefect)
Remove Tree
Remove Data
Attributes
Log:
Unavailable view pane:
Syslog
Scsi Log
Email Notification

Available view pane:

Console
Available Functions:
View Status
Refreshing Status
Delayed Jobs
Unavailable Functions:
Delayed Erases
Delayed Copy Media
Delayed Compaction

Page 8 of 138
COMMAND CONVENTIONS
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 two 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 commands for Windows.

UNIX WINDOWS UNIX WINDOWS

CMPDISK CMPDISK QCENTERA QCENTERA
COPYDISK COPYDISK UDFDF UDFCMD FDF
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
JBLOAD JBCMD LOAD VLCRSET VLCMD CRSET
JBMAGAZINE JBCMD MAGAZINE VLDELFROMSET VLCMD DELFROMSET
JBMOVE JBCMD MOVE VLDELSET VLCMD DELSET
JBPARAM JBCMD PARAM VLEDITSET VLCMD EDITSET
JBPING JBCMD PING VLERASE VLCMD ERASE
JBRESERVE JBCMD RESERVE VLEXCHANGE VLCMD EXCHANGE
JBRESET JBCMD RESET VLEXPORT VLCMD EXPORT
JBSCHEDCHECK JBCMD SCHEDCHECK VLIMPORT VLCMDOMPORT
JBSCHEDULER JBCMD SCHEDULER VLINSET VLCMD INSET
JBSHELF JBCMD SHELF VLLSDEV VLCMD LSDEV
JBSHUT JBCMD SHUT VLLSSET VLCMD LSSET
JBSIM JBCMD SIM VLMAGAZINE VLCMD MAGAZINE
JBSTATISTICS JBCMD STATISTICS VLMEDIAUSAGE VLCMD MEDIUSAGE
JBSTATUS JBCMD STATUS VLMVSET VLCMD MVSET
JBUNLOAD JBCMD UNLOAD VLPING VLCMD PING
MKISO MKISO VLQLIST VLCMD QLIST
MKUDF MKUDF VLQMOVE VLCMD QMOVE
MMADMIN MMCMD ADMIN VLQREMOVE VLCMD QREMOVE
MMARC MMCMD ARC VLRECORD VLCMD RECORD
MMCHMOD MMCMD CHMOD VLREFRESH VLCMD REFRESH
MMDELAY MMCMD DELAY VLREPLACE VLCMD REPLACE
MMEXEC MMCMD EXEC VLRESTORE_FSDB VLCMD RESTORE_FSDB
MMLS MMCMD LS VLREUSE VLCMD REUSE
MMPARAM MMCMD PARAM VLVERIFY VLCMD VERIFY
MMPING MMCMD PING
MMPURGE MMCMD PURGE
MMRESUME MMCMD RESUME
MMSUBTREE MMCMD SUBTREE
MOUNTIV VLCMD MOUNTIV

Note: In the examples, the Unix path and device name for the jukebox 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 directory, then creating a symbolic link to /opt/QStar.

Page 9 of 138
CMPDISK
NAME
cmpdisk - Compares two optical disk surfaces.

SYNOPSIS

cmpdisk [-v] disk1 disk2

DESCRIPTION

The cmpdisk command compares two optical disk surfaces to ensure

that they are identical. Normally this command is used to verify a
copy of an optical disk surface made with the copydisk command to
ensure it is correct. Note that these are raw devices, so, for
example, to refer to the media on shelf one, type
/opt/QStar/dev/jb/rjb1a.

For IBM only, type /dev/jb0/rjb1a.

OPTIONS

-v Verbose.

EXAMPLES

cmpdisk /opt/QStar/dev/jb/rjb5a /opt/QStar/dev/jb/rjb6a

cmpdisk /dev/jb0/rjb5a /dev/jb0/rjb6a (IBM)

Page 10 of 138
COPYDISK
NAME
copydisk - Makes a copy of an optical disk surface.

SYNOPSIS

copydisk [-va] source destination

DESCRIPTION

The copydisk command copies a source device to destination device

saving the file system structure of the Standard Data Format (SDF)
file systems. This is the only way to copy a SDF Volume because
SDF Volumes may contain small unwritten spots intermixed with
written ones which will cause I/O errors during reads by other raw
level copies. In contrast, the copydisk command analyzes the
source and copies only the written blocks to the destination.

NOTES

These are raw devices, so, for example, to refer to the media on
shelf one, type /opt/QStar/dev/jb/rjb1a.

For IBM only, type /dev/jb0/rjb1a.

OPTIONS

-v Verbose.

-a Copy all blocks. Otherwise copydisk stops after 300

blank blocks are detected on the source medium.

NOTES

The copying of a disk surface is a long procedure so please be

patient. Use the -v to keep track of the copy’s location.

EXAMPLES

copydisk /opt/QStar/dev/jb/rjb5a /opt/QStar/dev/jb/rjb6a

Copies all data from rewritable media side 5a to
rewritable media side 6a.

copydisk /dev/jb0/rjb5a /dev/jb0/rjb6a (IBM)

Page 11 of 138
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 file system.

EXAMPLES

floc /cache/cache_test /file1

Lists the media that has the file called file1 located
on it where the cache root is /cache/test.

/file1:
2 data_pages (128 KB)
Vol 0: 128 KB

floc /cache/cache_test /folder1/folder2/file2

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

Remember that the input commands are key sensitive!

Page 12 of 138
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 file system.

EXAMPLES

flsvol /cache/test 1
Lists all files located on volume (sequence number) 1
where the cache root is /cache/test.

Page 13 of 138
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.

Page 14 of 138
JBDRIVE
NAME
jbdrive – Changes or shows the status of a jukebox drive.

SYNOPSIS

jbdrive [-H host_name] [-nfbr] [-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 | bd-rs | bd-rr | bd-
re}] 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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

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 jukeboxes with CD-ROM, CD-R, DVD-
ROM, DVD-R, DVD-RAM drives present.

-p Set media type of the drive. This flag is used with

jukeboxes with CD-ROM, CD-R, DVD-ROM, DVD-R, DVD-RAM,
BD-ROM, BD-RS 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.

Page 15 of 138
 –u priority_number | rrr:www:rw | auto | default
Sets the priority for the usage of the drives. This flag
is used for jukeboxes with CD-ROM, CD-R,DVD-ROM, DVD-R
and DVD-RAM 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 jukebox 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.

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 jukebox 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.

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

Page 16 of 138
JBEXPORT
NAME
jbexport – Exports a media from the jukebox.

SYNOPSIS

jbexport [-H host_name] device_name shelf_number

jbexport [-H host_name] -s device_name

DESCRIPTION

The first form of the jbexport command exports a media from the
shelf to the mailslot. The shelf is specified by the shelf_number
argument.

The second form of the jbexport command exports a trash media to

the mailslot. This form is only available for array jukeboxes.

OPTIONS

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

EXAMPLES

jbexport jb 1
Export the media from shelf 1.

Page 17 of 138
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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

EXAMPLES

jbflip jb 1

Page 18 of 138
JBIMPORT
NAME
jbimport – Imports a media into the jukebox.

SYNOPSIS

jbimport [-H host_name] device_name shelf_number

jbimport [-H host_name] -s device_name

For Hard Disk simulated jukebox:

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-rs|bd-re-50|bd-rs-50}] 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 jukebox:

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-

rs|bd-re-50|bd-rs-50}] device_name shelf_number

jbimport [-H host_name] -S centera_tape_id[:capacity_meg:{dlt|sdx|sdz|ultrium}]

device_name shelf_number

For CAS simulated jukebox:

jbimport [-H host_name] -S [A=]qcas_disk_id[:{number_of_blocks|xxMB|xxGB}

:block_size] device_name shelf_number

jbimport [-H host_name] -S [A=]qcas_disk_id[:{pdd|udo|udo2|mo91|dvd-r|cd-r|bd-

rs|bd-re-50|bd-rs-50}] device_name shelf_number

jbimport [-H host_name] -S qcas_tape_id[:capacity_meg:{dlt|sdx|sdz|ultrium}]

device_name shelf_number

Page 19 of 138
DESCRIPTION

The first form of the jbimport command imports a media from the
mailslot to the shelf. The shelf is specified by the
shelf_number argument.

The second form of the jbimport command imports spare media

from the mailslot. This form is only available for array
jukeboxes.

The form of the jbimport command with the -S simulation_param

option imports the simulated disk to the specified shelf. See
jbsim command.

OPTIONS

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-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 jukebox. 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-rs Number_of_blocks 12219392, block_size 2048.
With dvdram, dvd-r, cd-r, bd-re, or bd-rs, 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.

Page 20 of 138
 -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 jukebox. The actual file name is <disk_id>_A.<type> where
<type> is dlt, sdx, etc.

-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.

Page 21 of 138
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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-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.

Page 22 of 138
JBMAGAZINE
NAME
jbmagazine - Exchanges media in the jukebox using the magazines.

SYNOPSIS

jbmagazine [-H host_name] [-h] [-v] device_name [magazine_number | h]

DESCRIPTION

The jbmagazine command exchanges media in the jukebox using the

magazines. The jukebox 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 jukebox only).

OPTIONS

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-v Verbose
Prints a list of the shelves exchanged.

EXAMPLES

jbmagazine jb

Page 23 of 138
JBMOVE

NAME
jbmove - Moves a media from one shelf to another in the jukebox.

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 jukebox.

OPTIONS

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

EXAMPLES

jbmove jb 1 2
Moves the media from the shelf 1 to shelf 2.

Page 24 of 138
JBPARAM
NAME
jbparam – Prints or sets the tunable time parameters of the
jukebox.

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 jukebox. These parameters include the inactive time, the idle
time and the quantum time.

OPTIONS

-H host_name
Specifies the name of the host where the device is connected.
Without this option, the local host is used.

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 jukebox 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 jukebox inactive time
expires, the media is unloaded back to its shelf. The
default value of the jukebox inactive time is 15 minutes or
900 seconds.
If the inactive time is set to zero, the mechanism is
disabled. The jukebox 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.

Page 25 of 138
 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 jukebox 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 jukebox quantum time unless the jukebox
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 jukebox 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 jukebox 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 jukebox idle time is 0 seconds,

which means that this mechanism is disabled. This mechanism
should be enabled to improve overall performance of the
jukebox.

The –d option can be used to fine tune the idle time in a

jukebox. The idle time must be set to a value between 5
seconds and one half of the jukebox quantum time or to zero
to disable this mechanism.

The jbparam command without options can be used to get the

current value of the jukebox idle time.

This command requires that the jbscheduler is running.

Page 26 of 138
ERROR MESSAGES

Value out of boundaries. The given value is too little or too

large relative to the jukebox 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 jukebox 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 jukebox.

-F Prohibit jbscheduler to control the front panel of the jukebox.

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

Page 27 of 138
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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

EXAMPLES

jbping
jbping: JB server thread is running.

Page 28 of 138
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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

EXAMPLES

jbreserve jb 1a 15

Page 29 of 138
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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

EXAMPLES

jbreset jb 1

Page 30 of 138
JBSCHEDCHECK
NAME
jbschedcheck – Checks to see if the jbscheduler is running for a
jukebox.

SYNOPSIS

jbschedcheck [-H host_name][-a | device_name]

DESCRIPTION

The jbschedcheck command checks to see if the jbscheduler daemon is

running for the jukebox specified by the device_name argument.

OPTIONS

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-a Checks to see if the jbscheduler daemons are started for

all jukeboxes connected to the server.

EXAMPLES

jbschedcheck jb
jb: Jbscheduler is running.

Page 31 of 138
JBSCHEDULER
NAME
jbscheduler – Starts the scheduler for a jukebox.

SYNOPSIS

jbscheduler [-H host_name] [-sdL] device_name

DESCRIPTION

The jbscheduler command starts the scheduler daemon for the jukebox
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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-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.

Page 32 of 138
JBSHELF
NAME
jbshelf – Changes or shows the status of the jukebox shelves.

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 | bd-rs |
bd-rr | bd-re | 1}] 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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-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 jukeboxes that support single and double
sided media.

-r Sets default media type of the shelf.

This flag is used with jukeboxes with CD-ROM, CD-R, DVD-
ROM, DVD-R, DVD-RAM 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.

Page 33 of 138
 -p Sets media type of the shelf.
This flag is used for jukeboxes with CD-ROM, CD-R, DVD-
ROM, DVD-R, DVD-RAM, BD-ROM, BD-RS drives present.
The jbstatus command shows drives 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 jukebox is running.

EXAMPLES

jbshelf -f jb 2
Sets the shelf number 2 offline.

Page 34 of 138
JBSHUT
NAME
jbshut – Stops the jbscheduler for a jukebox.

SYNOPSIS

jbshut [-H host_name] [-f] device_name

DESCRIPTION

The jbshut command stops the jbscheduler for the specified jukebox.
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 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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-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.

Page 35 of 138
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] -q {disk|tape} device_name shelf_count [qcas_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 jukebox or prints information

about the simulated jukebox and its shelves. With -h, -c, -q or
-p option, the jukebox is created. With -P option, it lists all files in
the directory associated with the HD (hard drive) jukebox. Without
options, the jukebox and shelves information is printed.

OPTIONS

-H host_name
Specifies the name of the host where the jukebox 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 jukebox.

-h {disk|tape}
Creates a simulated HD jukebox with name device_name and the
number of shelves equal to shelf_count. -h disk creates a disk
jukebox, -h tape - a tape jukebox. 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 jukebox has two sides.

Page 36 of 138
 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 jukebox with name device_name and
the number of shelves equal to shelf_count. -c disk creates a
disk jukebox, -c tape - a tape jukebox. Each disk/tape resides
on the Centera. Each shelf in the jukebox has two sides. An
optional argument centera_index specifies which Centera storage
system (1-30) will hold the jukebox. The default centera_index
is 1.

-q {disk|tape}
Creates a simulated CAS jukebox with name device_name and
the number of shelves equal to shelf_count. -q disk creates a
disk jukebox, -q tape - a tape jukebox. Each disk/tape resides
on the CAS. Each shelf in the jukebox has two sides. An
optional argument qcas_index specifies which Centera storage
system (1-30) will hold the jukebox. The default qcas_index is
1.

-p Creates a proxy disk jukebox with name device_name and the num-
ber 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 jukebox: 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 jukebox
creation. A proxy disk is automatically added to the set if the set
defintion includes proxy media. When the proxy disk becomes fully
written, it is copied to a disk in the destination jukebox. After the
copy, the destination disk is used in the set instead of the proxy
disk, whereas the proxy disk is declared empty and can be used again.

Page 37 of 138
IMPORT IN SIMULATED JUKEBOX

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+ 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 jukebox.
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).

-S [A=]disk_id:[rw|worm]:shortcut
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.
With dvdram, dvd-r, cd-r, bd-re, or bd-rs, 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.

Page 38 of 138
 A tape is represented by a file in directory dir_path associated with
the HD tape jukebox. The actual file name is <disk_id>_A.<type> where
<type> is dlt, sdx, etc.

-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 jukebox of HD disks with 10 shelves.
The directory /export/home/disks is associated with the
jukebox; files representing disks will reside in this
directory.

jbsim -h tape simt 6 /export/home/tapes

Creates a simulated jukebox of HD tapes with 6 shelves.
The directory /export/home/tapes is associated with the
jukebox; files representing tapes will reside in this
directory.

jbsim -c disk cend 4

Creates a simulated jukebox of Centera disks with 4
shelves.

Page 39 of 138
JBSTATISTICS
NAME
jbstatistics - Manages JB 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 JB

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.

Page 40 of 138
 -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 jukebox “jb”.

Page 41 of 138
JBSTATUS
NAME
jbstatus – Prints the status of the jukebox.

SYNOPSIS

jbstatus [-H host_name] [-cmsdpa] device_name

DESCRIPTION

The jbstatus command prints the state of all elements present in

the jukebox.

OPTIONS

-H host_name
Specifies the name of the host where the device is connected. Without
this option, the local host is used.

-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

Page 42 of 138
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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

EXAMPLES

jbunload jb 1
Unloads a medium back to the shelf.

Page 43 of 138
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.

Page 44 of 138
-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.

Page 45 of 138
 [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 respec-
tively with the name of the CD/DVD (Volume Label) set
to DOCS_2_3 and excludes files with names ending with
.bak.

Page 46 of 138
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. Specifing '-' 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.

Page 47 of 138
MMADMIN
NAME
mmadmin - Administrative operations for MCFS.

SYNOPSIS

mmadmin -c check_list set_name[/filename]

mmadmin -s set_name

mmadmin -p dst_root_path set_name

mmadmin -d cache_root {info|chunk|entry|cnode|event|btree|acl|

crypto|pte} element_number

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

-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.

Page 48 of 138
 -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.

EXAMPLES

Page 49 of 138
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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-a age
Stops archiving when all delayed events created before
the agetime specified are processed.

-l Stops archiving when the number of primary pages in the

cache is equal to or less than the low_primary_capacity
value.

-e Stops archiving when the delayed queue becomes empty or

all the delayed events are processed.

-s Stops archiving.
.
-w Waits 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).

Page 50 of 138
 -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.

Page 51 of 138
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] {+|-}{fk}
{path|[hostname:]setname/path} ...

DESCRIPTION

The mmchmod command changes the migration attributes of the

specified files. Attributes are designated by the letters fk with
the +/- prefix.

OPTIONS

+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 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.

-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.

-m The permissions of the named files or directories are

changed according to mode.

Page 52 of 138
 -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 infomation run man find, man regexp.

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 devoloped for MS Windows and they are present

for compatibility with unix semantics. On unix the same goal
is achived with chmod, chown, chgrp commands.

Page 53 of 138
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 attibute.

mmls /mnt
Directory -f-k /
Directory -f+k files
Directory -f-k scratch
The command mmls shows the new directory attributes.

Page 54 of 138
MMEXEC
NAME
mmexec - Handles cache manager.

SYNOPSIS
mmexec -R cache_root [-p {max_number_of_pages | xxMB | xxGB}] [-s
page_size] [-m mount_point] [-y crypto_parameters}] [-l
{all|no|list_of_log_options}] [-nr] set_name

mmexec -K {man set_name | mig cache_root}

mmexec[-L|-I] {all|no|list_of_log_options} set_name

mmexec set_name

DESCRIPTION

The mmexec command allows starting the cache manager, setting log
options, stopping cache manager and migrator, and performing Unix-like
commands with files in cache. The 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 talking to a mounted set (run Unix-like commands).

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.

-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
set (as it happens when mountiv command is issued). If this
option is not present, the only way to talk to the set would
be the fourth form of mmexec command.

Page 55 of 138
 -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 the cache manager (the same syntax
for options as in -L, see below).

-n Cleans cache. MCFS files are created from scratch.

-r Read-only mount.

-K man set_name
Stops cache manager.

-K mig cache_root
Stops migrator specified by cache_root argument.

-L {all|no|list_of_log_options}
Specifies log options for the cache manager. The 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

-I {all|no|list_of_log_options}
Specifies log options for the kernel or FSI. The 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 log rdwr events

Page 56 of 138
MMDELAY
NAME
mmdelay - Prints information about delayed events.

SYNOPSIS

mmdelay [-n number] {-c cache_root|[-H host_name] set_name | filename}

DESCRIPTION

The mmdelay command prints the information about 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.

Page 57 of 138
 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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-n number
Prints the specified number of delayed events. Without
this option, the mmdelay command tries to print all of
the delayed events.

-c cache_root
Cache_root Pathname of the directory used as a cache
root. This option allows printing mmdelay information
without mounting the cache.

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

Page 58 of 138
MMLS
NAME
mmls - Lists information about the cache files.

SYNOPSIS

mmls [-Rpso][ filename ...]

mmls [-Rpso] [[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 zero 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. If the
filename is a directory, the mmls command does not print column 2

Page 59 of 138
 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 the address of
the target filename is displayed.
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
jukebox.

NOTES

1. The mmls command does not copy the directories it lists into the
cache. If the directory has not been copied into the cache by the
normal access (like ls command), the mmls command displays the
directory as empty. It allows using the mmls command in cases when
the cache has behaved strangely or is not mounted at all.

2. 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 log
facility for writing into the cache files, mmls output may not be
up-to-date and inaccurate.

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

Page 60 of 138
MMPARAM
NAME
mmparam - Prints information and set parameters for the cache.

SYNOPSIS

mmparam [-l {low_primary_capacity | xxMB | xx%}]

[-h {high_primary_capacity | xxMB | xx%}]
{[-H host_name] set_name | filename}

DESCRIPTION

The mmparam command in the first form prints the information

of the cache. Without any options mmparam prints:

- 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:

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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

Page 61 of 138
 -l low_primary_capacity
Number of pages used to control a stop archiving policy.
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 archiving
policy. 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.

EXAMPLES

mmparam /mnt
The command prints the following:

Cache root: /export/home/cache

Mcfs mount point: /mnt
Max number of pages: 100 (6400 Kbytes)
Flush on umount: Yes
Low primary capacity 0 pages (0 Kbytes)
High primary capacity 100 pages(6400 Kbytes)
Page size: 64 Kbytes
Present pages: 100
Primary pages: 90
Replicated pages: 10
Archived pages: 52
Keep in cache: 0
Archive never: 0
Files in cache: 250
Number of delayed events: 1
Read/write access: Read-write
Mount state: Mounted
Error condition: No
Archiving: Not started
Migrator: standard
Covered root: /opt/QStar/tmp/mnt_913300223_1856

mmparam -h 2800 -u 0 /mnt

The command sets the high primary capacity to 2800 pages
and specifies that the delayed event queue will be
flushed on umount.

Page 62 of 138
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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

EXAMPLES

mmping
mmping: MM server thread is running.

Page 63 of 138
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 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.

Page 64 of 138
MMRESUME
NAME
mmresume - Resumes the cache.

SYNOPSIS

mmresume [-e] [-n] {[-H host_name] set_name | filename}

DESCRIPTION

The mmresume command clears an archiving error status in the

mmparam output. 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 canceled with the ENOSYS error (Function not
implemented). If the source of the error can be eliminated, the
situation is recoverable and archiving can continue by using the
mmresume command.

OPTIONS

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-e After the cache is resumed, the first event will be

removed from the delayed event queue. This might be
necessary if the system crashed when the event had
already been processed for the covered filesystem but
has not been removed from the delayed event queue.
This option should only be used under supervision of
QStar personnel.

-n This flag instructs the migrator to add a new piece of

media to the set before resuming the write. Only the sdf
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

The flags -e and -n are mutually exclusive.

EXAMPLES

mmresume /mnt

Page 65 of 138
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} path

mmsubtree -r {tree|data|kill} [hostname:]setname/path

mmsubtree -c {tree|data} path

mmsubtree -c {tree|data} [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}
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. All
delayed events related to that subtree are removed. The
kill option is available for UDF file system used with
Automount Interchange Level and ISO file system.

Page 66 of 138
 -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.

EXAMPLES

mmsubtree –r /images/dir10
Removes the hierarchy below directory dir10 from the
cache, resynchronizing on next access of the directory.

Page 67 of 138
MOUNTIV
NAME
mountiv - Mounts an Integral Volume set.

SYNOPSIS

mountiv [-H host_name] [-n] [-I] [-r] [-f] [-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 set (specified in the Integral Volume set database) with the
cache. The migrator that represents the "covered filesystem"
depends on the set type.

OPTIONS

-H host_name
Specifies the name of the host where the Integral Volume
set resides. Without this option, the local host is
used.

-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” set option by
vleditset command. This option is disabled (ignored)
for CD and UDF 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.

Page 68 of 138
 -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 set.

-t {[mmdd]HHMM|[cc]yymmddHHMM}
Specifies the date and time for "dated mount". The set will be
mounted (read-only) reflecting file system state on the specified
date/time. Cache root must also be specified for dated mount.
The dated mount is an SDF specific option.

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.

Page 69 of 138
QCENTERA
NAME
qcentera - Manages a Centera connection.

SYNOPSIS
qcentera [-i storage_index] -L{0|1}

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 centera_index] -m {store|restore|print} [-h hours] volume_id

qcentera [-i centera_index] -m store +

qcentera [-i centera_index] [-r|-R] volume_id

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

Linux
LD_LIBRARY_PATH <centera_root>/lib/32

HP-UX
SHLIB_PATH <centera_root>/lib/32

Page 70 of 138
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

HP-UX
<centera_root>/lib/32

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.

Page 71 of 138
 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.

OPTIONS

-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.

To use a PEA file intead 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.

Page 72 of 138
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.

-c=
Prints the current configuration.

-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|restore|print} [-h hours] volume_id

Handles volume maps. The Centera volume is specified by
volume_id.

-m store
Stores a volume map on the Centera. The Centera daemon
must be running. The ClipId of the clip where the
map has been stored is printed in the QStar Syslog tab.

-m store +
Stores all volume maps on the Centera.

Page 73 of 138
 -m restore
Finds the last clip where the volume map was stored
and restores the map from that clip. If -h hours is
present it specifies the number of hours (to the current
moment) for which the clips are queried.
Without this option the number of hours is 24. 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
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.

-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.

-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

Sets the Centera configuration.

qcentera -c=
Prints the Centera configuration.

qcentera -d start
Starts the Centera daemon.

Page 74 of 138
UDFDF
NAME
udfdf - Reports number of blocks and files in UDF set.

SYNOPSIS

udfdf [-H host_name][-f][{-t|-a automount_sequence_number|-d

dir_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

-H host_name
Specifies the name of the host where the set resides.
Without this option, the local host is used.

-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

Page 75 of 138
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.

Page 76 of 138
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

-H host_name
Specifies the name of the host where the Integral Volume
set resides. Without this option, the local host is
used.

-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.

Page 77 of 138
VLADDTOSET
NAME
vladdtoset - Adds media to set (Volume set or Integral Volume set).

SYNOPSIS

vladdtoset [-H host_name] [-n number_of_media] set_name

vladdtoset [-H host_name] [set_type_specific_options] set_name

device_name shelf_number

vladdtoset [-H host_name] set_name device_name

shelf_number:shelf_number

vladdtoset [-H host_name] -f offline set_name in_set_number

set_type set_type_specific_options:
sdf
udf [-A identifier][-B identifier]
uvfs [-X directory][-Y directory]
[-A identifier][-B identifier]
DESCRIPTION

The vladdtoset command adds media to sets. The set is specified

by the set_name argument.

The first form of the command initializes and adds media to the
set.

The second form of the command includes in the 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 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 and
occupy the shelves in the range specified by the
shelf_number:shelf_number argument.

The fouth form of the command adds an offline medium to the set
specified by the set_name and specifies its offline location.

If the medium specified in the second or third form of the command

is erased (blank) it can be added to the set if the medium type
matches the use-media parameter of the set. Otherwise, the
compatibility is set specific.

Page 78 of 138
 If the medium contains a set identification, the second or third
form of the command does not expand the set. It merely
includes media in the database for the specified set. If a medium
is already included in the set command does nothing. Such
operation is usually required after the device has been refreshed.

OPTIONS

-H host_name
Specify the name of the host where the device is
connected. Without this option, the local host is used.

-n number_of_media
Specifies the number of additional media which will be
initialized and added to the set. The total number of
media in the set must be less than or equal to the set
quota.

-f offline
Specifies the offline location for a medium offline.

SET TYPE SPECIFIC OPTIONS

In the second form of command the extra options can be specified
depending on the set type:

sdf No extra options.

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
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 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.

Uvfs The specific options are:

-A identifier
Specifies the logical volume identifier assigned to the
surface A in the case of an automount set. If the
option is not specified for the surface, the logical
volume identifier is generated by the system.

Page 79 of 138
 -B identifier
Specifies the logical volume identifier assigned to the
surface B in the case of an automount 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.

EXAMPLES

vladdtoset -n 3 alpha
Initializes three media and adds them to the set
"alpha".

vladdtoset beta jb 4
Adds to the set "beta" all media (one of them is on the
shelf 4) which are compatible with the set "beta".

Page 80 of 138
VLCACHE
NAME
vlcache - Creates or edits cache information for an Integral Volume
set.

SYNOPSIS

vlcache [-H host_name] [-D0rne]

[-p{max_number_of_pages | xxMB | xxGB}]
[-s page_size]
[-l {low_primary_capacity | xxMB |xx%}]
[-h {high_primary_capacity | xxMB |xx%}]
[-g rdonly_grace_period]
[-R retention_period]
[-w {0|1] [-x {0|1]
[-c cache_root] set_name

DESCRIPTION

The vlcache command creates or edits the cache information used by

mountiv to mount a set with cache (Integral Volume set). The set is
specified by the set_name argument.

OPTIONS

-H host_name
Specifies the name of the host where the set resides.
Without this option, the local host is used.

-D Deletes all the cache options. This means that no cache

is assigned to the 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 "rnulh"
options.

-r Filesystem is mounted read-only.

-n Mounts the Integral Volume set with a clean cache. This

flag should be used with the vlcmd mountiv command
instead. If this flag is added with the vlcmd cache
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.

Page 81 of 138
 -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 K. Default is 64K and 128K is only for AIT tape.

-l low_primary_capacity
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.

-h high_primary_capacity
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.

-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 set.

-w {0|1}
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.

-x {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.

-g rdonly_grace_period
Specifies the grace period option. The grace period
option is used to specify a period of years, days,
hours, minutes and seconds as a timeout for modifying

Page 82 of 138
 the state of an existing file or directory. Once the
grace period has expired, the file will be treated as a
read only file even for the Super User, so no one can
modify the files or directory on the volume. The
only way to modify the files is to remove the grace
period option from the set properties.

-R retention_period
Specifies the retention period option. The retention
period option is used to specify a period of years,
days, hours, minutes and seconds as a timeout
prohibiting modification/removal of the file. Once
the retention period has expired, the file can be
removed. If both the retention and rdonly grace periods
are specified, a file can be modified either before the
rdonly grace period expires or after the retention
period expires.

Both the grace and retention periods have 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}

EXAMPLES

vlcache -c /cache set1

Assigns the cache with /cache as the cache root directory to
the set "set1".

vlcache -l 2 set2
Sets the low primary capacity in set "set2" to 2.

Page 83 of 138
VLCLOSE
NAME
vlclose - Closes volume.

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 set, it must be not mounted. If the disk
belongs to an automount set, during close procedure the disk is
deleted from the set, closed, and added back to the set.
After the disk is closed it is refeshed 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

-H host_name
Specifies the name of the host where the set resides.
Without this option, the local host is used.

-f Forces the command to delete the disk from the 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 set.

EXAMPLES

vlclose jb 1a
Closes the session on shelf 1a.

Page 84 of 138
VLCMP
NAME
vlcmp - Compares two media.

SYNOPSIS

vlcmp [-H host_name] [-v] [-j {delayed_job_name | "default"}]

[-m][-d{[mmdd]HHMM|[cc]yymmddHHMM}]
source_jukebox:shelf_number
destination_jukebox: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.

OPTIONS

-H host_name
Specifies the name of the host where the source_jukebox
and destination_jukebox are connected. Without this
option, the local host is used.

-v Verbose output.

-m Compares mirror medium. This option is applicable to SDF

volumes only. It allows it to compare mirror medium.

-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.

Page 85 of 138
 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 jukebox#1 (jb1) on
shelf 5 to the media in jukebox#2 (jb2) on shelf 6.

vlcmp -j "Compare 5 and 6" jb1:5 jb2:6

Compares all data on the media in jukebox#1 (jb1) on
shelf 5 to the media in jukebox#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.

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.

Page 86 of 138
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

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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-l Without the -PSC options, all the requests are printed.

Otherwise, the pending (-P), satisfied (-S), or canceled
(-C) requests are printed.

-r Removes satisfied (-S), or canceled (-C) requests from

the list. Without the -SC options, all the satisfied
and canceled requests are removed.

-c Cancels the specified request.

With the -A option, a request to add a medium to the set
is canceled.
With the -N option, a request to bring a medium online
is canceled.

A set is specified by set_name. 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.

Page 87 of 138
 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.

EXAMPLES

vlconsole –l
Prints all request.

vlconsole –r –S
Removes all satisfied events.

Page 88 of 138
VLCOPY
NAME
vlcopy - Creates a (backup) copy of a media.

SYNOPSIS

vlcopy [-H host_name] [-v] [-c copy_number] [-C {yes|no}

[-r source_host_name] [-j delayed_job_name | "default"}]
[-d {[mmdd]HHMM|[cc]yymmddHHMM}]
[-h hostid -t timeid] to copy sdf volumes with different set id
[-I] to incremntal copy sdf volumes
src_dev_name:shelf_number [dst_dev_name:shelf_number]

DESCRIPTION

The vlcopy command creates a copy of a media (SDF, UDF). 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. src_dev_name:shelf_number
specifies the jukebox and shelf number for the original media.
dst_dev_name:shelf_number specifies the jukebox 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
jukebox first and then all other jukeboxes.

NOTES

Both the copy and the original must reside on the same host. If
the media is double-sided both sides are copied.

OPTIONS

-H host_name
Specifies the name of the host where the device is
physically connected. Without this option, the local
host is used.

-v Verbose. Prints a progress report on the user's

terminal.

-h and -t
Flags -h and -t allows performing volume copy in SDF
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

Page 89 of 138
 volume which belongs to mirror set 12345678.aabcd123.
Both options -h and -t should be specified. Supported
for SDF mirror sets only.

-c copy_number
Forces the value of the copy number in the volume_id
block to copy_number. 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).

-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 "COPY 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.

-I To copy incrementally an sdf media.

-r source_host_name
Remote sorce host name.

Page 90 of 138
EXAMPLES

vlcopy jb:3 jb:5

Copies the media on shelf 3 to the media on shelf 5 of
the jukebox 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.

Page 91 of 138
VLCRSET
NAME
vlcrset - Creates a set (Volume set or Integral Volume set).

SYNOPSIS

vlcrset [-T set_type] [-H host_name]

[-u{disk,cd,tape,dvd,erasable,worm,rdonly,cd-dvd,bd-re,bd-rs,bd-rom,
hd-sdisk,hd-stape,c-sdisk,c-stape}] [-q quota][-s] [-I] [-r] [-N]
[{full|cron_like_schedule|Publisher_schedule}] [-U {local|share}]
[set_type_specific_options]set_name [number_of_media]

set_type set_type_specific_options:

sdf [-c {default|on|off}](tape media only)

[-Z{0-15}] (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 {CDR|DVDR}] [-A Publisher_media_retained]
[-D {0|1|2|3}] [-Q Publisher_host_name]
[-Y Publisher_port][-L Pubisher_label_file]
[[-k label_param1 -e label_value1]
[-k label_param2 -e label_value2] ...]

uvfs [-v{s|a}]

nom

DESCRIPTION

The vlcrset command creates a new volume set. The 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 set. Without this argument the command does
not include any media in the set, it merely creates a record about
the set in the VL database. The number_of_media must be less than
or equal to the set quota.

Page 92 of 138
OPTIONS

-H host_name
Specifies the name of the host where the set resides.
Without this option, the local host is used.

-T set_type
Specifies the set type which defines the set specific
options in the command (see below). The default is nom
(set with no media).

-u use_media
Specifies the type of media which can be used in the 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-rs 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.

Writable, worm, or rdonly specify the type of media in the set

from the read-write point of view. Other words specify the
nature of media. The default depends on the set type. Multiple
-u options can be used to specify a set of different types of
media. For example, presence of -u writable and -u worm in the
same vlcrset command means that a 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) cannot be mixed in
the set with real media or simulated media of different type.

-s Specifies that the set can spread to another jukebox on

the same host. Without this option, the media available
for use for the set is limited to the jukebox where the
set resides.

-q quota
Specifies the quota for the set. The quota is defined as
the maximum number of media that can be allocated to the
set. The default value depends on the set type.

-I Recreates the filesystem databases before mounting.

When the set is unmounted, this parameter is set to off.
This option is disabled for CD set type.

Page 93 of 138
 -r Filesystem is mounted read-only.

-N Set must be digitally signed. Currently works for UDF

sets only.

-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 for HP-UX and Linux.

[-p{yes|no}]
Used to specify whether an Integral Volume set can be
mounted at server restart.from The default value is no.

This option is only available for Windows.

-b {full|cron_like_schedule|Publisher_schedule}

full
Automatic start of vlcopy (Copy Media). When current
media is filled up, vlcopy command copies it to first
available medium with the same capacity. This
option is available for SDF file system. It is also
available in spanning UDF for finalized media.

cron_like_schedule
Incremental start of vlcopy (Copy Media).
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 filesystem.

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, -Y, -L,
-k and -e).

Page 94 of 138
SET TYPES AND SPECIFIC OPTIONS

All set specific options must be used after the generic options listed
above. Not all 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 set types.

sdf:

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 jukeboxes.

-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.

udf:

If the -u option is omitted, the default is disk and writable.

The quota limit is 1 for single-volume set and 2048 for
automount and spanning set.

The specific options are:

-v {s|a}
Specifies the interchange level: s - spanning set,
and a - automount set. Without this option the 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 set. The default is 150.

Page 95 of 138
 -P {0|1}
With -P1, CDR/DVDR blank surface or a surface with
an empty last session can be initialized for packet
writing and added to the set. With –P 0 (default),
such a surface is considered uninitial-izable and
left intact.

-S {0|1}
For single-volume and automount 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).

-F {0|1}
For spanning sets. 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 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 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.

Page 96 of 138
-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 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.

-Y {Publisher_port}
For vlcopy with using Publisher device. To use
this parameter, option -b Rx should be specified on
the command-line before. Publisher_port specifies
the port for QPublisher daemon. If omitted, the
default port (5006) will be used.

-L {label_file}
For vlcopy with using Publisher evice. 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.

Page 97 of 138
 -k {Parameter_name}
For vlcopy with using Publisher device (printing
parameters). Parameter_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 {Parameter_value}
For vlcopy with using Publisher device (printing
parameters). Parameter_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
jukebox 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

-v {s|a}
Specifies the interchange level: s - spanning set,
and a - automount set. Without this option the set
is single-volume.

The way how to use this file system will be

explained only in the QStar Windows
Administratior’s Guide.

Page 98 of 138
EXAMPLES

vlcrset -T sdf alpha 2

Creates the set "alpha" with the default attributes,
initializes 2 media with SDF file system and includes
them in the set.

vlcrset –T sdf -u writable –u worm beta

Creates the 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 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 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.

Page 99 of 138
VLDELFROMSET
NAME
vldelfromset – Removes a media from a set (Volume set or 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 jukebox. If the media
contains no up-to-date data then it may be erased (and reused for
the same or different set).

OPTIONS

-H host_name
Specifies the name of the host where the set resides.
Without this option, the local host is used.

-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 set is not mounted this
procedure will be done immediately after the set is
mounted.

EXAMPLES

vldelfromset alpha 0
Removes the media with in_set_number="0" from the set
"alpha".

Page 100 of 138

VLDELSET
NAME
vldelset – Deletes a set (Volume set or Integral Volume set).

SYNOPSIS

vldelset [-H host_name] set_name

DESCRIPTION

The vldelset command deletes a Volume set or an Integral Volume

set. The set is specified by the set_name argument.

The vldelset command removes the record about the set from the VL
database. It does nothing with the media included in the set.

OPTIONS

-H host_name
Specifies the name of the host where the set resides.
Without this option, the local host is used.

EXAMPLES

vldelset alpha
Removes the set "alpha" from the VL database.

Page 101 of 138

VLEDITSET
NAME
vleditset – Changes the set (Volume set or Integral Volume set)
parameters.

SYNOPSIS

vleditset [-H host_name] [-q quota] –U {local|share} [-s] [-I]

[-b {none|full|cron_like_schedule}] [-r {0|1}]
[set_type_specific_options] 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]
[-Y Publisher_port_name] [-L Pubisher_label_file]
[ [-k label_param1 -e label_value1] [-k label_param2 -e
label_value2] ...]

DESCRIPTION

The vleditset command changes and edits the parameters of a set.

The set is specified by the set_name argument.

OPTIONS

-H host_name
Specifies the name of the host where the set resides.
Without this option, the local host is used.

-q quota
Specifies the quota for the set. The quota is defined as
the maximum number of media that can be allocated to the
set. The default value depends on the set type.

-s Specifies that the set can spread to another jukebox on

the same host. Without this option, the media available
for use for the set is limited to the jukebox where the
set resides.

-I Recreates the filesystem databases before mounting.

When the set is unmounted, this parameter is set to off.
This option is disabled (ignored) for CD and UDF set
types.

-r {0|1}
Disable and enable the read-only option.

Page 102 of 138

 -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 for HP-UX and Linux.

-b {none|full|cron_like_schedule}

none
Disables any type of Automatic start of vlcopy
(Copy Media).

full
Automatic start of vlcopy (Copy Media). When
current media is filled up, vlcopy command copies
it to first available medium with the same
capacity. This option is available for SDF file
system. It is also available in spanning UDF
for finalized media.

cron_like_schedule
Incremental start of vlcopy (Copy Media). 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. This
option is available only for SDF file system.

SET TYPES AND SPECIFIC OPTIONS

All set specific options must be specified after the generic

options listed above.

sdf:

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 jukeboxes.

[{-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.

Page 103 of 138

 udf:

The specific options are:

-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
set. The default is 150.

-P {0|1}
With -P1, CDR/DVDR blank surface or a surface with an
empty last session can be initialized for packet writing
and added to the set. With –P 0 (default), such a
surface is considered uninitializable and left intact.

-S {0|1}
For single-volume and automount 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).

-F {0|1}
For spanning sets. 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 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 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.

Page 104 of 138

 -Y {Publisher_port_name}
For vlcopy with using Publisher device. Publisher_por
t_name specifies the port name for QPublisher daemon. If
omitted, the default port (5006) will be used.

-L {label_file}
For vlcopy with using Publisher device. label_file spec
ifies 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 {Parameter_name}
For vlcopy with using Publisher device (printing param
eters). Parameter_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 {Parameter_value}
For vlcopy with using Publisher device (printing paramet
ers). Parameter_value specifies the next parameter value
to be used with the label file (see -L option). Every
parameter value (optio
n -v) should have the corresponding parameter name
(option -k). There can be more than one parameter/value
pair in the command line.

EXAMPLES

vleditset -r 1 beta
Turns the read only option on for the set "beta".

Page 105 of 138

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 jukebox 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 a Volume set or an Integral Volume set, the

erase process will be denied.

OPTIONS

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-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.

Page 106 of 138

-f Full erase
By default the QStar software erases only the first 2048
blocks on each side of the media which is acceptable
for both UDF or SDF file systems. The full erase
procedure can be used to check faulty media, because all
blocks will be erased.

-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).

-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 "ERASE 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.

Page 107 of 138

EXAMPLES

vlerase jb 3:5
Erases media on shelves 3, 4 and 5 of the jukebox
specified by the jb VL name.

vlerase jb 8a
Erases surface "a" of the media on shelf 8.

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.

Page 108 of 138

VLEXCHANGE
NAME
vlexchange - Moves a media from one shelf to another in the
jukebox.

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 jukebox. 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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

EXAMPLES

vlexchange jb 1 2
Moves the media from shelf 1 to shelf 2.

Page 109 of 138

VLEXPORT
NAME
vlexport - Exports a media or a complete set from the jukebox 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 a Volume set or Integral Volume set.

The first form of the command exports a media from the jukebox or
standalone drive specified by the device_name argument, the
shelf_number specifies the shelf.

The second form of the command exports a media belonging to the

set. The set_name argument specifies the name of the set. The
in_set_number argument specifies the number of the media within the
set.

The third form of the command exports all media included in a set.
The set_name argument specifies the name of the 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
S_N, where S is a set name, N is the in_set_number. 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

-H host_name
Specifies the name of the host where the device is connected.
Without this option, the local host is used.

-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.

Page 110 of 138

 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
jukeboxes

-s set_name
Specifies the set name in the second and third forms of the
command.

EXAMPLES

vlexport jb 3
Exports a media from shelf number 3 of the jukebox specified
by the device_name jb.

vlexport -H boa -s alpha

Exports all media from the set "alpha" on the host "boa".

Page 111 of 138

VLIMPORT
NAME
vlimport - Imports media into the jukebox 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}] [-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 jukebox:

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-rs|bd-re-50|bd-rs-50}] 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 jukebox:

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

rs|bd-rs-50}] 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]

For CAS simulated jukebox:

vlimport [-H host_name] -S [A=]qcas_disk_id[:{number_of_blocks|xxMB|xxGB}

:block_size] device_name shelf_number [num_shelves]

vlimport [-H host_name] -S [A=]qcas_disk_id[:{pdd|udo|udo2|mo91|dvd-r|cd-r|bd-

rs|bd-rs-50}] device_name shelf_number [num_shelves]

vlimport [-H host_name] -S qcas_tape_id[:capacity_meg:{dlt|sdx|sdz|ultrium}]

device_name shelf_number [num_shelves]

Page 112 of 138

DESCRIPTION

The vlimport command imports a media into a jukebox or standalone

drive.

The first form of the command imports a media into the jukebox 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.

The second form of the command imports a media belonging to the

set. The set_name argument specifies the name of the set.

The in_set_number argument specifies the number of the media within

the set.

The third form of the command imports all media included into the
set. The set_name argument specifies the name of the 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 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 jukebox,

the media is refreshed. If the media contains a 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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-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.

Page 113 of 138

 -o open_door
Opens the door to access the mail slot (s)on specific
jukeboxes.

-s set_name
Specifies the set name in the second and third forms of
the command.

-C Imported media is cleaning tape.

-p Sets media type of the shelf.

This flag is used with jukeboxes 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
jukeboxes that support both single and double side
media.

IMPORT IN SIMULATED JUKEBOX

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 direc-
tory dir_path associated with the HD disk jukebox. 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).

Page 114 of 138

 -S [A=]disk_id:[rw|worm]:shortcut
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.
With dvdram, dvd-r, cd-r, bd-re, or bd-rs, 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:
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 jukebox. The actual file name is <disk_id>_A.<type> where
<type> is dlt, sdx, etc.

-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.

Page 115 of 138

EXAMPLES

vlimport jb 3
Imports a media to shelf number 3 of the jukebox
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 jukebox 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 jukebox 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 jukebox
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 jukebox cend. The disk has capacity of PDD
disk.

Page 116 of 138

VLINSET
NAME
vlinset - Edits media in a set (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 set. The 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 set. In_set_numbers are 0-based and printed in the left column
by vllsset -v command.

OPTIONS

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-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.

Page 117 of 138

 -r {tree|data|medium|all}
Removes information related to the media from the cache
and/or from the set.
tree Removes the tree structure and data from the
cache.
data Removes the data only.
medium Removes the media from the set.
all Removes the tree structure and data from the
cache and the media from the set.

SET TYPES AND SPECIFIC OPTIONS

All 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 set types.

sdf: No specific options.

A media cannot be removed from the set.

udf: The specific options are:

-R [device_name:shelf_number]
Used with 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 set is mounted, the UDF
migrator is notified of that.

A media cannot be removed from the set.

EXAMPLES

vlinset -f new_offline beta 2

Changes the offline location of the media number 2 in
the set "beta" to "new_offline".

Page 118 of 138

VLLSDEV
NAME
vllsdev – Prints the status of the media and jukebox(es) 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 jukebox is specified by the device_name argument.

The second form of the command prints the status of the device
which may be a jukebox or a standalone drive. In the case of a
jukebox it prints the status of all the shelves in the jukebox. 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 a set, the surface
information depends on the -ni options. With the -ni options and if
the set exists, the set name is printed. Without the -ni option or
if the set name does not exist, the set specific information is
printed. The command output is directed to the user terminal.

OPTIONS

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-n Prints the set name instead of the set specific

information.

Page 119 of 138

 -s Lists the shelves with media that belongs to a set.

-i Lists the shelves with media that belongs to a set not

listed in the VL database. Usually such media emerges
after the import or refresh operation. The 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 jukebox). 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 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 set names. With -B option, the output is sorted
by bar codes. Otherwise, it is sorted by set Ids for non-
CD/DVD devices and by LabelNames for CD/DVD devices.

-B Prints the bar code instead of the 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 sets. The set name should be printed instead of the
Ids.

Page 120 of 138

VLLSSET
NAME
vllsset - Prints status of a set (Volume set or 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

DESCRIPTION

The vllsset command prints the VL status for the specified 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 set. The set_name argument specifies the name
of the set. The in_set_number argument specifies the in-set-
medium.

The second form of the command prints the status of the specified
set. The set_name argument specifies the name of the set.

The third form of the command prints the status of all the sets on
the host.

Set parameters printed by the command include use_media, spread and

quota information, and the number of in-set- media. The rest are
set specific information. In-set-medium parameters include online
(device and shelf) or off-line information and set specific in-set-
medium data. The command output is directed to the user terminal.

OPTIONS

-H host_name
Specifies the name of the host where the set resides.
Without this option, the local host is used.

-n Prints only the set name. Without this option, the

command prints the set name and parameters.

-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 sets in the third form of the command.

Page 121 of 138

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

Page 122 of 138

VLMAGAZINE
NAME
vlmagazine - Exchanges media in the jukebox 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] device_name [magazine_number | h]

DESCRIPTION

The vlmagazine command exchanges media in the jukebox using the

magazines and updates the VL database. The jukebox 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 jukebox only).

OPTIONS

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-p Sets media type of the shelevs on the magazines. This

flag is used with jukeboxes 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 maybe determined automatically but the
media can be specified with the -p option, which causes
the jbscheduler to 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
jukeboxes that support both single and double side media.

-s Refreshes shelves in sequential order.

-P Refresh procedure will use physical refresh (not use bar

code media database). This option required for correct
changing of "Write Protect" media status.

EXAMPLES
vlmagazine jb

Page 123 of 138

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 set ‘set_name’

and prints statistics on how much up-to-date data is present on
each medium in a 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

-H host_name
Specify the name of the host where the set resides.
Without this option, the local host is used.

EXAMPLES

vlmediausage alpha
Analyses media usage for the set alpha.

Page 124 of 138

VLMVSET
NAME

vlmvset - Renames a set (Volume set or 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

-H host_name
Specifies the name of the host where the set resides. Without
this option, the local host is used.

EXAMPLES

vlmvset alpha beta

Renames the set "alpha" to "beta" in the VL database.

Page 125 of 138

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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

EXAMPLES

vlping
vlping: VL server thread is running.

Page 126 of 138

VLQLIST
NAME
vlqlist – Prints the delayed job queue.

SYNOPSIS

vlqlist [-H host_name] [-j [d][c][m][r][e][A][i][o]]

[-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

-H host_name
Specifies the name of the host where the device is connected.
Without this option, the local host is used.

-j [d][c][m][r][e][g][A][i][o]
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.

-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.

EXAMPLES
vlqlist

Page 127 of 138

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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

[after]
Specifies that job_id1 should be placed after job_id2.

EXAMPLES

vlqmove 1 3

Page 128 of 138

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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

EXAMPLES

vlqremove 1

Page 129 of 138

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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-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.

Page 130 of 138

 -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).

-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 "RECORD Delayed Start"
field in the vl/files/conf file. Note - the -d flag is
only usuable 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.

-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 been 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 jukebox#1.

Page 131 of 138

VLREFRESH
NAME
vlrefresh - Refreshes media, jukebox(es) and standalone drive(s)
and fixes the VL database.

SYNOPSIS

vlrefresh [-H host_name] [-sB] device_name shelf_number ...

vlrefresh [-H host_name] [-sB] device_name shelf_number:shelf_number

vlrefresh [-H host_name] [-sB] device_name

vlrefresh [-H host_name] [-sB] -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
jukebox 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 jukebox
is specified by the device_name argument.

The third form of the command refreshes the device which may be a
jukebox or a standalone drive. In case of a jukebox it refreshes
all the shelves in the jukebox. 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.

Page 132 of 138

OPTIONS

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-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.

EXAMPLES

vlrefresh jb 3
Refreshes shelf number 3 of the jukebox specified by the
jb VL name.

vlrefresh jb
Refreshes the entire jukebox.

Page 133 of 138

VLREPLACE
NAME
vlreplace - Replaces a media in a Mirrored set (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, initialzes 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

-H host_name
Specifies the name of the host where the set resides.
Without this option, the local host is used.

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.

Page 134 of 138

VLRESTORE_FSDB
NAME
vlrestore_fsdb – Recreates filesystem databases.

SYNOPSIS

vlrestore_fsdb [-H host_name] [-D {UDF_span_number | +}] set_name

vlrestore_fsdb [-H host_name] [-D SDF_volume_number] set_name

DESCRIPTION

The vlrestore_fsdb command recreates filesystem specific databases

for set “set_name” in the cache directory assigned to the set.
Currently fs databases exist only for UDF and SDF filesystems. The
databases are restored from media belonging to the set. Note that
if the fs database already exists in the cache directory, they are
removed.

OPTIONS

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

-D UDF_db_span_number or SDF_volume_number
For UDF 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 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).

For SDF sets. Specifies the SDF volume number (starting from
1) which must be used for restoring SDF database. Without
this option (or if volume number is equal to 0) the SDF
database will be restored from the last surface in the set.
The database will be restored from specified volume and SDF
events will be replayed from that medium. The saved database
on the next vlume will not be used to restore data base.
Rather the data portion of the SDF volume will be scanned
and events replayed. This process continues until last medium
(surface) in the set is scanned. The mirrored SDF volume set
restore with this option is not supported.

EXIT CODES
The command fails if the specified set is in a mounted state.

EXAMPLES

vlrestore_fsdb alpha

Page 135 of 138

VLREUSE
NAME
vlreuse – Relocates data, erases the media and adds it to a set
(Integral Volume set).

SYNOPSIS

vlreuse [-H host_name] [-r][-j {delayed_job_name | "default"}]

[-d {[mmdd]HHMM | [cc]yymmddHHMM}]set_name in_set_number
[in_set_number2...]

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 set. As a result available space for the set is
increased. More than one in_set_number maybe specified for the
same command.

OPTIONS

-H host_name
Specifies the name of the host where the device is connected.
Without this option, the local host is used.

-r Specifies relocation only mode. After successful

completion of the command the media may be exported from
jukebox (for backup purposes) or erased and added to the
same or different 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).

-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 "REUSE 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)

Page 136 of 138

 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.

EXIT CODES

The command will fail if the specified set contains a SDF

filesystem and is in a mounted state.

It may also fail if there is not enough space for the real-located
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 set "alpha" and then erases the media
with in_set_number="0" and adds it to the end of set
"alpha".

vlreuse -r alpha 0
Relocates data from the media with in_set_number="0"
belonging to the set "alpha". The media is not erased
and there is no actual data on the media, but it still
belongs to the 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.

Page 137 of 138

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

-H host_name
Specifies the name of the host where the device is
connected. Without this option, the local host is used.

EXAMPLES

vlverify
Verifies any inconsistencies in the VL databases.

Page 138 of 138

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., 2175 West Highway 98, Mary
Esther, Florida 32569-1450 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., 2175 West Highway 98, Mary Esther, Florida 32569-1450
USA.
Unpublished - Rights reserved under the copyright laws of the United States and of other countries.

Copyright 1995-2007 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., 2175 West Highway 98, Mary Esther, Florida 32569-1450 USA.