SlideShare a Scribd company logo
1 of 628
Download to read offline
System Administrator’sGuide
ProductSeriesforUnix
DataManagementSystem
Version6
ForAllSupportedPlatforms
Storage
M
anagem
entSoftw
are
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 cs@qstar.com
• Or E-mail support in Europe is available through info@qstar.it
Addresses:
QStar Technologies, Inc. (USA)
8738 Ortega Park Drive
Navarre, FL 32566
Tel: +1-850-243-0900
Fax: +1-850-243-4234
E-mail: cs@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: info@qstar.it
Web URL: http://www.qstar.com/
QStar Technologies Japan
Shinjuku Park Tower N30F
3-7-1 Nishi Shinjuku, Shinjuku-ku
Tokyo 163-1030 Japan
E-mail: info@qstar.com
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, 8738 Ortega Park Drive Navarre,
FL 32566 USA.
Unpublished – All rights reserved under the copyright laws of the United States and of other countries.
GENERAL. If you acquired this product in the United States, the laws of the State of Florida govern this Agreement.
If this product was acquired outside the United States, then local law may apply.
This Agreement sets forth the entire Agreement between QStar and you may be amended only in writing signed by both parties.
No waiver of any right under this Agreement shall be effective unless in writing signed by both parties. If any provision in this
Agreement is invalid or unenforceable that provision shall be construed, limited, modified or, if necessary served, to the extent
necessary, to eliminate its invalidity or un-enforceability and all other provisions of this Agreement shall remain unaffected.
Should you have any questions concerning this Agreement, or if you desire to contact QStar Technologies for any reason, please
contact the subsidiary serving your country, or write: QStar Technologies, Inc., Attn: General Counsel, 8738 Ortega Park
Drive Navarre, FL 32566 USA.
QStar Technologies is a registered trademark of QStar Technologies, Inc
D-LIC-05-09
5/00
Page 1 of 4
QStar Technologies is the market leader in secure, large-scale client/server archiving and data management solutions for
Windows and UNIX. QStar provides solutions that allow every level of your organization to store and manage the resources of
even the most heterogeneous networks. The world’s leading organizations increasingly rely on QStar for the secure, cost
effective and reliable storage of their critical data.
More than two decades of experience and a large installed base have provided QStar with the knowledge to create software that
brings life to storage hardware. The functionality of QStar Software is based on extensive research of user requirements and
customer feedback, which has enabled QStar to develop an industry-leading product.
QStar Software significantly reduces the overall storage costs within a network. At the same time, productivity is boosted by
keeping all of the data logically online, all the time.
QStar Software integrates all storage media on the network. Magnetic disks, Cloud Storage, optical, tape, RDX, both offline and
nearline, are consolidated into a single network storage hierarchy. The view of the storage hierarchy is a network available
logical disk, transparent to users and applications. Using this method, terabytes or petabytes of data storage can be accessed in
real time.
QStar Software can represent multiple media as a single volume, keeping track of the exact location of all files on each medium.
Archiving applications for Media and Entertainment, Imaging, CAD/CAM, Document Management, PACS, and other
applications are fully compatible with QStar Software.
This System Administrator’s Guide provides the information you will need to install, configure and utilize QStar Software to
manage data. It contains all the necessary information to achieve the best results for implementing and customizing your mass
storage solution.
This Chapter contains an introduction to the platforms, devices and media supported.
PLATFORMS SUPPORTED ...................................................................................2
MEDIA SUPPORTED...........................................................................................3
QSTAR MANUAL REVISION.................................................................................3
CHAPTER SUMMARY..........................................................................................4
Page 2 of 4
PLATFORMS SUPPORTED
QStar Software supports the following server platforms:
• Sun - Solaris
• IBM - AIX
• Hewlett Packard - HP-UX series 700/800
• Microsoft - Windows 2003/2008, Windows XP, Windows Vista, Windows 7
• Linux - Redhat - SUSE - Debian - Ubuntu - Mandrake - Gentoo – Fedora - CentOS
• Apple - MAC
Page 3 of 4
MEDIA SUPPORTED
The type and quantity of data being stored by users determines which media they will use to store it.
QStar supports a wide variety of archival media, including Optical disks, digital Tapes, RDX, CD-ROMs, DVD-ROMs DVD-
RAMs and Blu-ray.
Removable Media, come in a wide range of sizes and capacities. Another distinguishing characteristic is whether they are
Rewritable, able to be erased and reused, or WORM, Write Once Read Many.
The following list defines the media types currently supported:
MEDIA TYPE SUPPORT TYPE
Rewritable MO Optical Read/Write
WORM MO Optical Read/Write
Rewritable UDO1 - UDO2 Read/Write
WORM UDO1 - UDO2 Read/Write
Compliance WORM UDO1 - UDO2 Read/Write
Rewritable PDD Read/Write
WORM PDD Read/Write
Tape (AIT - AIT2 - AIT3 - AIT3 WORM - SAIT) Read/Write
Tape (LTO1 - LTO2 - LTO3 - LTO4 - LTO5 – LT06) Read/Write
Tape (DLT - SDLT ) Read/Write
Tape (9730 - 9840 - 9940A - 9940B) Read/Write
Tape Oracle T10000C Read/Write
CD/DVD-ROM Read Only
CD-R Read/Write
CD-RW Read/Write
DVD-RAM Read/Write
DVD-R Read/Write
DVD-RW Read/Write
BD-RE Read/Write
BD-R Read/Write
RDX Read/Write
Centera/HCP/OSM/Cleversafe/Amplidata Read/Write
HARD DISK (Simulated Disk/Tape) Read/Write
QSTAR MANUAL REVISION
August 2012 Revision A (Windows and UNIX):
Manual for release starting with v6.0.
Page 4 of 4
CHAPTER SUMMARY
Chapter One: INTRODUCTION
This chapter contains an introduction to the platform, device and the media supported; it also contains a brief overview of QStar
products and their features.
Chapter Two: QSTAR COMPONENTS
This chapter describes the main components of QStar Software and the terminology used in later sections of the manual. These
descriptions will help the user gain an understanding of the product, to ensure that the maximum performance, functionality and
organization for the storage solution are obtained.
Chapter Three: INSTALLING AND CONFIGURING QSTAR SOFTWARE
The first section of this chapter describes how to load the QStar Software onto the system and how to connect the hardware
devices. The second section describes the installation of the QStar Software and the configuration of the storage device(s). The
third section describes how to generate and install license keys. There is also a section to aid in upgrading from earlier versions
of the QStar Software.
Chapter Four: LIBRARY MANAGEMENT
This chapter describes how to manage the library and its components including the media and drives within the library. Also
included are steps to gather library statistics and tune the library for optimum performance.
Chapter Five: THE VOLUME LIBRARIAN
This chapter describes the use of the Volume Librarian database and how it handles the media. There are sections on how media
is handled both in and out of the library as well as creating and managing Integral Volume sets.
Chapter Six: MIGRATION MANAGER
This chapter describes how to set-up the cache for an Integral Volume set and how to configure it for the best performance.
There is also a description of how the cache works.
Chapter Seven: MEDIA CONFIGURATIONS
This chapter describes how to create the Integral Volume set configuration for all type of media supported by QStar Software.
Included are walk through examples showing how each can be achieved.
Chapter Eight: DISASTER RECOVERY
This chapter covers some common hardware problems and how to recover from them.
Chapter Nine: COMMAND REFERENCE
This chapter covers all of the QStar commands available on the UNIX/Windows platforms, including explanations and
command options.
Page 1 of 20
Depending on the product purchased, QStar Software will install different components on the system. Before you install and
configure the Software, you should be comfortable with QStar’s terminology and concepts.
Please take the time to read all sections, as this will ensure that the maximum performance, functionality and organization for
the storage solution are obtained.
This section identifies key terminology and concepts that are vital for you to understand. Also included are the descriptions of
QStar modules and conceptual and practical definitions for creating the configuration.
GENERAL COMPONENTS ....................................................................................3
API Interface ................................................................................................3
Command Line Utilities...................................................................................3
QStar Administration Interface ........................................................................3
QStar Administration Interface Changes ...........................................................3
Privileged Users (UNIX Option)........................................................................3
Online Help Manual Pages...............................................................................3
Remote Administration...................................................................................4
VL Scheduler ................................................................................................4
No Media Option............................................................................................4
DEVICE MANAGER COMPONENTS........................................................................5
QStar “SCSI” Manager ...................................................................................5
Library Manager ............................................................................................5
View Store....................................................................................................5
Library Statistics ...........................................................................................5
MEDIA MANAGER COMPONENTS .........................................................................6
QStar “Volume Librarian” Database..................................................................6
Bar Code Support ..........................................................................................6
Online Media Management ..............................................................................6
Dated Mount.................................................................................................6
Offline Media Management..............................................................................6
Data Compaction...........................................................................................6
Simulated Media Libraries...............................................................................7
VL Copy Media ..............................................................................................7
VL Cross Copy Mirror Media ............................................................................7
VL Copy Using Publisher Devices......................................................................7
MIGRATION MANAGER COMPONENTS..................................................................8
Migration Manager.........................................................................................8
Cache ..........................................................................................................8
Cache Enhancements .....................................................................................8
File Migration ................................................................................................8
Transaction Logging Cache .............................................................................8
Read Only Grace Period..................................................................................8
Retention Period............................................................................................9
Write Once and Deny Rename .........................................................................9
NFS Mount ...................................................................................................9
Virtual Disk...................................................................................................9
Page 2 of 20
DIAGNOSTIC COMPONENTS............................................................................. 10
Syslog View Pane or QStar‘s Syslog File.......................................................... 10
SCSI Log View Pane or Qscsi_log Command .................................................... 10
Console View Pane or Vlconsole Command ...................................................... 10
Mail Notification .......................................................................................... 10
FILE SYSTEMS................................................................................................ 11
SDF (Standard Data Format)......................................................................... 11
UDF (Universal Disk Format) ......................................................................... 12
UVFS - Support for the Plasmon File Systems .................................................. 13
AAFS - Support for the Archive Appliance Plasmon File System .......................... 13
TDO (Tape and Disk Object File System)......................................................... 13
LTFS (Linear Tape File System) ..................................................................... 14
MEDIA ORGANIZATION ................................................................................... 15
MAJOR SOFTWARE ENHANCENENT IN VERSION 5.1 ............................................ 16
MAJOR SOFTWARE ENHANCENENT IN VERSION 6.0 ............................................ 18
Page 3 of 20
GENERAL COMPONENTS
The general components of the QStar Software are as follows:
API Interface
QStar operates seamlessly with all major UNIX and Windows Platforms with full Application Programming Interface (API)
support. A separate API Interface manual is available upon request from QStar.
Command Line Utilities
The QStar Software on the Windows platforms creates the c:qstarbin directory and on the UNIX platforms creates the
/opt/QStar/bin and the /opt/QStar/etc directories. In these directories QStar places all the user and Administrator commands.
The QStar Software for Windows platforms allows the System Administrator to run all the QStar commands from the Windows
DOS prompt. With this added functionality, System Administrators will have greater flexibility in managing and integrating the
QStar Software. Adding the /opt/QStar/bin and /opt/QStar/etc paths to the Administrator's default execute path (PATH
environment variable) on the UNIX platforms will make all QStar commands accessible to the System Administrator.
QStar Administration Interface
The QStar Administration Interface (Windows) allows configuring, and viewing of the underlying structure of the QStar Server,
providing a single interface for management of the QStar Software and devices. Through the QStar Graphical User Interface
(GUI) (Windows only) management of the hardware (configuration/ trouble shooting, and statistics), media (online/offline
databases), file systems, mounting and unmounting of the Integral Volume sets, migration behavior, logging, and email
notification alerts are all possible. A web-based GUI is available for Linux and Mac Administrators.
QStar Administration Interface Changes
The QStar Administration Interface (Windows) has been completely redesigned; the new GUI is resizable and consists of a
window divided into two panes. The navigation pane is on the left side and contains the categories tree. The categories tree
shows the items that are available to manage the QStar Software. The view pane is on the right side and shows information and
functions of each item. In addition, the GUI now supports Multinational languages. The current languages supported are
English, Japanese, Russian, German, Chinese, Dutch and Italian.
Privileged Users (UNIX Option)
Usually only the System Administrator can run QStar commands because of their administrative capabilities.
QStar creates a special option that, if required, allows non-root users to run QStar commands.
For more detailed information, please refer to Chapter 3 - Installing and Configuring QStar Software in this manual.
Online Help Manual Pages
The QStar Software for the Windows platforms contains context-sensitive help links that provide instructional help and
examples. The System Administrator can access the QStar Manual by selecting the bookshelf icon on the far right of the QStar
Administration Interface. Alternatively, the manual can be reached from the Start Button as well.
The QStar Software for the UNIX platforms creates the /opt/QStar/man directory. In this directory, QStar places all of the
Manual pages for the QStar commands. These pages explain the syntax and show some examples of the QStar commands to
help the System Administrator. Adding this path to the Administrator's default Manual pages path (MANPATH environment
variable) will make all QStar Man pages accessible to the System Administrator.
Page 4 of 20
Remote Administration
The QStar Administration Interface (Windows) can be used with any 2000/2003/2008/XP/Vista client machine to remote
administer, configure and manage any other server (Windows or UNIX) that has the QStar software installed on it located on the
network. The System Administrator simply copies the admin.exe file from c:qstarbin 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:qstarbin and its contents to the c:qstarbin of the remote client machine.
VL Scheduler
The QStar Software contains an event scheduler for scheduling certain processes. Scheduling of events allows the Software to
be used to its full potential, notifying the System Administrator of low availability of media and delaying system intensive
processes to be run at off peak times. The VL Scheduler can be used to initiate archiving from caches independently on a per
Integral Volume basis and run batch or single media erases as well as Copy Media requests. It can also be used to schedule more
time consuming tasks out of peak hours such as data Compaction on Integral Volume sets and bulk recording of CD/DVD-R
media.
No Media Option
The QStar Software can be configured to create an Integral Volume set with No Media, this allows data to be written to a cache
as normal, but the data will not be archived and therefore not secured. A library or standalone drive can be added at a later date,
and then the media can be added to the Integral Volume set and the data synchronized from the cache to the media.
Page 5 of 20
DEVICE MANAGER COMPONENTS
The term “device” refers to hardware such as standalone drives and library subsystems.
QStar Software can manage one or many standalone drives and library devices on the same system.
These devices can use Optical, Tape, or RDX media.
To manage the device(s), QStar Software has three components:
QStar “SCSI” Manager
The “QSCSI” commands are the low-level SCSI drivers and are used to provide an interface for performing any direct SCSI
device diagnostics, independent of the QStar drivers. These commands allow viewing of device profiles, inquiry strings,
capacities of media, defined vendors, sense log information and other data from devices.
Library Manager
The JB driver, through the “jbcmd or jb(UNIX)” commands, manages the storage library called historically jukebox.
The JB module performs various operations with the library and its elements (shelves, drives, carriers, and mailslots).
The commands can move media between elements as follows:
jbcmd load (jbload) move a medium from the shelf to the drive
jbcmd unload (jbunload) move a medium from the drive back to the shelf
jbcmd flip (jbflip) invert a medium in the drive
jbcmd export (jbexport) move a medium from the shelf or drive to the mailslot
jbcmd import (jbimport) move a medium from the mailslot to the shelf.
An application can control the online/offline status of the elements as well as the library time control parameters through API
calls.
View Store
Library management software provides a complete application transparent interface to libraries, scheduling the insertion of
particular media into a drive, based on demand for that volume.
Library Statistics
QStar Software provides statistics for the elements within the library. These statistics allow the System Administrator to monitor
for potential problems with the media and drives within the library. This allows problems to be rectified before they become too
serious. There are also statistics for media loads per shelf/surface and per drive. If the library is full and media needs to be taken
offline, these statistics will identify the less frequently accessed media. Additionally the statistics show the number of recovered
errors per surface/drive/carrier, the number of occasions when a shelf/drive has been marked as ‘bad’ and the number of primary
and secondary defect blocks on the DVD-RAM and Optical (MO/UDO/PDD/Blu-ray) surface. The Statistics view pane or the
jbcmd statistics (jbstatistics) command line allows library statistic information to be printed or cleared.
Page 6 of 20
MEDIA MANAGER COMPONENTS
QStar “Volume Librarian” Database
The “VLcmd or VL )” commands allow the system administrator to configure the QStar database named Volume Librarian
(VL). QStar’s Volume Librarian module is responsible for managing all archival media known to QStar, referred to as the
media library.
The Volume Librarian knows the location (physical and logical) and status of every archival medium, whether available online
in a library or offline in a storage facility. Its capabilities eliminate any errors that may occur during manual volume
management, while increasing productivity and performance.
The QStar Volume Librarian performs many different tasks including erasing, media initialization, export/import from the
storage devices, automatic electronic labeling, partitioning of the library, dynamic media allocation and compaction.
Bar Code Support
QStar supports most major manufacturer’s implementation of Bar Code for media management, this allows improved handling
for offline media and disaster recovery. In large-scale installations, media can be scanned in seconds for fast and efficient media
tracking. Media can be tracked by a user defined label, or its Bar Code information, whether inside or outside the library.
Online Media Management
For online media, the QStar Software automatically manages all storage media allocation and movement without operator
intervention.
Dated Mount
Dated Mount has the ability to mount an Integral Volume set, as read only, to a previous date and time. This feature is specific
to the SDF / TDO file system. Dated Mount allows multiple simultaneous mounts on different dates and times, while the
production mount continues to satisfy user requests. This allows the System Administrator to recover a previous version of a
file or recover a file that has been deleted from the file system. Please refer to the Chapter 6 - The Migration Manager for
more details.
Offline Media Management
The offline media management provides virtually unlimited storage capacity by managing media outside of the storage device.
For requests that require offline archival media access, the operator is prompted to retrieve the storage media from its storage
location and insert it into the QStar configured device.
Data Compaction
The Data Compaction utility is available for use with the SDF / TDO file systems, and is used for migrating live data from one
piece of media to the current write surface of the Integral Volume set. The Data Compaction feature lets the operator fully
reclaim media blocks after modifying or removing files on rewritable Optical media or Tape. This feature is managed under the
control of the VL database. This feature is available on all Integral Volume sets, or just selected ones. Once a piece of media has
been compacted and erased, the System Administrator has the option of adding the erased media to the same Integral Volume
set or removing it from the Integral Volume set entirely.
Page 7 of 20
Simulated Media Libraries
The QStar Software can create Simulated Libraries. The Simulated Library configuration extends the ability of the QStar
Software to mount an Integral Volume set utilizing magnetic disk space (RAID, Centera, SAN or hard drive) as simulated
media. This configuration allows the use of physical disk space available on a hard drive to be used as media for an Integral
Volume set. The hard drive may be partitioned into simulated virtual shelves and allows full use of import and export
commands. The media may be manually configured to any size, or pre-configured media types such as UDO or Blu-ray.
Integral Volume sets can then be created with any media configuration QStar supports, such as SDF / TDO. The Simulated
Libraries configuration may be useful for demonstrating or integration testing with the QStar product or API when a library is
not available.
It is possible to configure a conventional library, with media such as Tape or Optical in conjunction with a Simulated Library
and mirror the data between the two devices. For this, configure the Simulated Library media must be the same capacity and
type as the media in the conventional library containing real media, then using the Data Director product and QStar’s SDF /
TDO file system, mirror the data between the Simulated Media Library (on hard disk) and an Optical or Tape Library. This
configuration allows real time mirroring between a hard disk and an optical or tape library.
VL Copy Media
The QStar Software can manually or automatically execute a duplication process of the media that has been completely written.
With a properly configured Integral Volume set, the Automatic Copy Media command will run every time the Integral Volume
set reaches the point of dynamically allocating another piece of media to the Integral Volume set. With the VL Copy Media the
source and destination media may be selected and copied at the System Administrators convenience. The copied media is an
exact duplicate of the original media in the Integral Volume set. If a media is damaged, the copied media can be used to replace
the damaged media. For more information on how to enable the VL Copy Media, please refer to Chapter 5 - The Volume
Librarian in this manual.
VL Cross Copy Mirror Media
The Copy Media supports copy of the media within the mirror configuration (SDF / TDO file system). This new feature will
allow the System Administrator to recreate any lost or damaged primary or secondary mirror media simply by using the Copy
Media utility or vlcmd copy (vlcopy) command. The copied media is identical to the original with the exception of the Set
Identifier written at the beginning of the media, allowing it to be added to the mirror set.
VL Copy Using Publisher Devices
QStar Software is capable of interacting with different types of publisher/duplicator devices. In the Windows and Linux versions
a new QStar daemon will start if the software is configured to work with a publisher device. The daemon, through the
publisher’s proprietary SDK library, is responsible for the communication between QStar and the publisher device. Using a
simulated DVD or BD library with a spanning UDF Integral Volume set, it is possible to select the option of “Copy Media using
Publisher”. Once the virtual UDF media is full, it is automatically sent to the publisher to create single or multiple copies of the
media for offline storage.
Page 8 of 20
MIGRATION MANAGER COMPONENTS
Migration Manager
Migration is the movement of data between the magnetic disk cache partition and the archival media. The Migration Manager
was designed to provide a view of a collection of diverse types of storage media. This includes magnetic disks, RAID, Optical,
CD, DVD, Blu-ray, RDX, Tape drives and libraries. The job of the Migration Manager is to combine all of these technologies
into a Virtual File System called an Integral Volume set. An Integral Volume set looks and feels to the user like a standard
magnetic disk. This means that all standard applications, including network-based applications, can work with the Integral
Volume set without modification and in the same manner that they would work with a normal magnetic disk.
Cache
QStar Software uses server magnetic disk to temporarily store files to improve system performance.
Caching provides the ability to place frequently accessed files on magnetic disk or RAID for quicker access. Different
configurations of caching and cache logic provide instant access to the most recent and most active data without delays or a
need for special commands.
Cache Enhancements
The cache (Magnetic Cache File System) has been completely redesigned. The format of the cache now allows movement of the
cache files between different operating systems and the cache formatter is no longer needed. The limitation of the cache per
Integral Volume set size of 500 GB has been removed and better system resource utilization has been made. Multi threading has
been enhanced, increasing the performance of Read/Write operations. A new mmcmd admin (mmadmin) command allows the
ability to easily save all primary pages from the cache in case of disaster recovery.
File Migration
File Migration is defined as the movement of data from and to the disk cache from and to an archive storage medium. This
includes archiving files to the secondary storage media and replicating files back to the magnetic cache to service read requests.
In the case of archiving data in an Integral Volume set from the cache, there are several archiving policies that can be utilized to
maximize the efficiency of the archiving process. Automatic data migration in the Integral Volume set, or demand archiving
forces an archiving cycle when a pre-arranged watermark, High Primary Capacity, is reached. Archiving can also be started by
the System Administrator at any given time or scheduled in a timed interval using the VL Scheduler.
Transaction Logging Cache
The magnetic cache is implemented using transaction-logging technology. This ensures the highest level of reliability in case of
a system failure. Recovery of the cache requires the flushing of the transaction log. This takes place automatically at the next
mount of the Integral Volume set after an unclean unmount.
Read Only Grace Period
The QStar Software has a feature to allow data to be stored for a Grace Period before it is set to read only. A file may be
modified, providing the user has sufficient privilege, until the Grace Period has expired, it is then marked as read only, this
feature goes further than the standard UNIX, or Windows read only flag, as even the System Administrator cannot remove the
read only flag for files, the only way to overcome this, is to remove the Grace Period option. Enabling this feature provides a
WORM file system, even with rewritable media ideal for true archiving applications. This feature is configurable on an Integral
Volume set basis and can be set by seconds, minutes, hours, days and years. Please refer to the Chapter 6 - The Migration
Manager for more details.
Page 9 of 20
Retention Period
The Retention Period feature can be used alone or in conjunction with the Grace Period feature. Both Grace Period and
Retention Period start from the last modification time. The Retention period specifies a file can be removed only once the
Retention period has expired. The benefit to this feature is the ability to lock a file to read only status for the time the file is
required to remain available within corporate guidelines. This feature goes further than the standard UNIX, or Windows read
only flag, as even the System Administrator cannot remove the read only flag for files under Retention Period management.
Enabling this feature provides a WORM file system, even with rewritable media ideal for corporate data archiving compliance
requirement. Once a file has reached a point in time after the Retention Period, the file may then be modified or deleted from the
file system. If both the Retention and Grace Periods are specified, a file can only be modified or deleted either before the Grace
Period begins or after the Retention Period expires.
This feature is configurable on an Integral Volume set basis and can be set by seconds, minutes, hours, days and years. Please
refer to the vlcmd cache (vlcache) command in Chapter 9 - Command Reference for more details.
Write Once and Deny Rename
The Write Once feature provides a WORM file system, even with rewritable media, which is ideal for corporate data archiving
compliance requirement. Working differently from Grace Period, once a file is written in the file system; the overwrite, remove
and set size operations are prohibited. A file can only be appended and renamed. This option will be ignored if is used in
conjunction with Grace Period. If the Deny Rename option is specified with the Write Once option, the renaming operation is
also prohibited.
NFS Mount
This option allows mounting a QStar file system from a Windows platform to a UNIX platform via NFS. With this option, there
is no third party software required to mount the QStar file system from Windows to a UNIX platform. With this added
functionality, System Administrators will have greater flexibility in managing and integrating the QStar Software. Please refer
to the Chapter 6 - The Migration Manager for more details.
Virtual Disk
QStar Software consolidates all of the physical mass storage subsystems on a network-magnetic disk, Optical, CD-ROM, DVD-
ROM, DVD-RAM or Tape - into a single, hierarchically managed resource, or Virtual Disk, treated as one logical entity. Using
QStar’s caching technology, the most recently used data is available on the magnetic disk, providing fast access for users. Less
recently used data is stored on archival media, via the Volume Librarian (VL) and is automatically moved to the magnetic disk
if a user accesses it. This is a function of the Migration Manager. The moving of data between the magnetic disk and the
archival media is transparent to end-users. QStar Software’s automatic storage management provides the benefit of virtually
unlimited storage capacity without sacrificing access time to critical data.
Page 10 of 20
DIAGNOSTIC COMPONENTS
QStar Software provides different diagnostic components that can help the System Administrator monitor events, warnings and
errors within the system.
Syslog View Pane or QStar‘s Syslog File
In UNIX platform the QStar Software redirects any warning messages and main errors to the system console window. In
addition, the QStar Software places its own log file called syslog into the /opt/QStar/log directory. In the Windows platform the
QStar’s syslog file is placed into the c:qstarlog 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:qstarlog (Windows) or /opt/QStar/log (UNIX) directory where it will sequentially collect all the SCSI commands sent to
the devices as well as the response back from the SCSI devices.
Console View Pane or Vlconsole Command
The Console view pane or the vlcmd console (vlconsole) command prints a list of requests for manual assistance. The System
Administrator can cancel a particular request, or remove requests from the list upon completion. Requests might include Integral
Volume sets that need another piece of media added to the library or for offline media to be reinserted into the storage device to
satisfy a read request.
E-Mail Notification
The System Administrator can receive e-mail notification about abnormal events in the QStar software. An abnormal event can
be, for example, a drive/library failure, an unrecoverable write error, a request for additional medium (no more space in the
Integral Volume set), a request for medium that is currently offline. For more detailed information, please refer to Chapter 3 -
Installing and Configuring QStar Software in this manual.
Page 11 of 20
FILE SYSTEMS
A File System is an interface for saving and retrieving files on storage media.
The file system controls all aspects of media management, including directory/file structures, data layout, and data transfers.
The file system allows data to be written out to the storage device in the file format that is acceptable to the application.
QStar Software supports different types of standard file systems such as UFS, NTFS, FAT, UDF, LTFS and ISO.
In addition, QStar Software supports two file system types that have data layouts suitable to the media QStar controls. These
appear as standard file systems and give optimal performance for the storage and retrieval of data.
QStar media format manager stores information about the data on the surface of the media, thus providing the template for the
data written to the archival media. All archival media sets are self-contained, with file directory information, data, and indexes
on the same Optical media, DVD-RAM or Tape. The volume format is optimized to ensure maximum performance and
transportability between Optical, DVD-RAM or Tape libraries and file servers.
The benefits of QStar formatted media include:
• Transportability. - Media format easily moves media from one host system to another, regardless of the manufacturer. Thus,
QStar’s media format manager protects the company’s investment in current hardware and allows access to critical data using
other manufacturers’ products.
• Flexibility. - Media format describes the contents of a single archival media allowing it to be used as part of a logical group,
or media set. As part of a set, file and directory information is not restricted to a single piece of media; it may span several
platters or tapes, giving contiguous space for large files.
• Disaster recovery. - Making all archival media self-contained provides the means for disaster prevention and recovery. Any
magnetic disk cache in the storage hierarchy can be completely rebuilt from the archival media, thus preventing catastrophic
data loss.
QStar stores file databases on a stacking file system. The first time a file is written to storage, it creates a baseline copy of the
file. Subsequent changes to the file only cover the portions of the file that have been modified. The original file and each
subsequent change are simply overlaid by more recent file segments. This method provides true incremental changes to the file
without consuming excessive storage space. Similarly, changes made to directories are also stacked. Therefore, if a user
removes a file, the directory is simply rewritten without the name of the deleted file. The file, however, still exists physically on
the media.
The QStar file systems are as follows:
SDF (Standard Data Format)
This file system can be used for (MO/UDO/PDD/Blu-Ray) Optical and DVD-RAM devices to manage data storage and retrieval
on WORM and rewriteable (MO/UDO/PDD/ Blu-Ray) Optical and DVD-RAM media. SDF is available on both UNIX and
Windows platforms. Files are stored contiguously from the beginning to the end of each piece of media, with single-seek read
and write access.
This file system also supports SCSI Tape devices, specifically, Digital Linear Tape (DLT), SDLT, AIT, SAIT and LTO. The
files are stored contiguously from the beginning to the end of each tape.
The SDF file system is best suited for applications that will generate relatively small sized files.
Page 12 of 20
Shredding support for UDO Compliance WORM media and Rewritable Optical media has been added. The support is available
with ASM and Data Director (Mirroring) configurations.
A new approach of saving the SDF database has been created, allowing the SDF database to be saved to a dedicated, separate
media. The System Administrator can still use the old approach, which stores the SDF database to the beginning of each media.
In addition the SDF database can be stored on Hard Disk as the primary location or as a mirror location if the primary location is
the media. The database save procedure is triggered during rollover of media or can be initiated per GB of data written in the file
system. This new approach allows the user to have two different threads in the SDF migrator, one for writing data and one for
saving the database in two different media, removing the delay of archiving of data during the saving of the database. This
feature is available also on Mirroring configurations where two different Hot Sync procedures have been developed. One called
“Off Line Asynchronous Hot Sync” that is used to synchronize Database Media and all non current write surfaces and one
called “On Line Synchronous Hot Sync” that is used to synchronize the current write surface, this allows Hot Sync to run in
parallel with read/write operations.
UDF (Universal Disk Format)
This file system can be used to manage data storage and retrieval on WORM and rewriteable (MO/UDO/PDD/Blu-Ray) Optical
or DVD media. UDF is available on both UNIX and Windows platforms. Files are stored contiguously from the beginning to the
end of each piece of media, with single-seek read and write access. QStar Software supports UDF Version 1.2 in read only
mode and fully supports UDF Version 1.50, 2.00 and 2.01.
UDF file system supports the three following Interchange Levels:
• Single-volume: Single surface file system for standalone drive
• Automount: Single surface file system where each surface is seen within a single volume as a separate directory
• Spanning: All media are aggregate as large file system
The following new UDF Versions and file system have been supported:
• Version 2.5
• Version 2.6
• Plasmon UDF
• ISO 9660 File System
Note: CD File System (ISO 9660 File System) has been removed and the support for the ISO 9660 standard with Rock Ridge
and Microsoft extensions has been incorporated in the UDF file system. ISO and UDF media can coexist in the same file system
using Automout Intechange Level.
The UDF file system also supports the shredding operation offered with UDO Compliance WORM media.
A new version of the UDF spanning database has been introduced for spanning configurations that also contain directory
entries. This modification requires less access to the media when a user is browsing the file system and provides a faster mount
procedure in the case of rebuilding of the cache and media databases.
The floc command is now supported on UDF and can be used to list the files on an individual media.
Page 13 of 20
UVFS - Support for the Plasmon File Systems
This file system supports WORM and rewriteable (MO/UDO) Optical, DVD-ROM and DVD-RAM media on Linux and
Windows platforms. Using the UVFS file system QStar supports, Read Only access to the following three Plasmon file
systems:
• PFS - A simplified version of UDF, based on an older UDF implementation by HP
• AFS-1 - Archive File System, specifically developed for WORM
• AFS-2 - Improved version on AFS-1, optimized for speed and media usage
The UVFS file system supports the following three Interchange Levels:
• Single-volume: Single surface file system for standalone drives
• Automount: Single surface file system where each surface has a different label and it is seen within a single volume as
a separate directory
• Spanning: All media are aggregated as a large file system if the label name is identical on each media
AAFS - Support for the Archive Appliance Plasmon File System
This file system supports WORM and rewriteable (UDO) Optical, on Linux and Windows platforms. Using the AAFS file
system QStar supports, Read Only access to the Archive Appliance Plasmon File System.
TDO (Tape and Disk Object File System)
The TDO migrator (introduced in version 6.0) is a high performance file system created to optimize the read/write operations for
tape and optical disks. TDO is available on both UNIX and Windows platforms. Files are stored contiguously from the
beginning to the end of each piece of media, with single-seek read and write access. The design of TDO has removed the
majority of the bottlenecks that are inherent with other file systems for these types of media. TDO has been created in such a
way that it supports SDF media in read-only mode and writes all new data to the TDO file system. This allows to convert an
SDF Integral Volume set to an TDO Integral Volume set.
The read operation (for TDO and SDF) is multi-thread, which allows different read requests to be satisfied at the same time.
The TDO file system is best suited for applications that will generate relatively small or very large sized files.
The support is available with ASM and Data Director (Mirroring) configurations.
Page 14 of 20
LTFS (Linear Tape File System)
This file system can be used to manage data storage and retrieval on Tape media. LTFS is available on both UNIX and
Windows platforms. Files are stored contiguously from the beginning to the end of each piece of media, with single-seek read
and write access. QStar Software fully supports LTFS Version 2.0, allowing media to be exported and read in stand-alone
drives using LTFS drivers provided by various drive manufacturers. LTFS media created in stand-alone drives can also be
imported into the QStar controlled tape library.
LTFS file system supports the three following Interchange Levels:
• Direct-single-volume: Single media file system for standalone drive or library without QStar Magnetic Cache File
System (MCFS). This Interchange Level provides direct access to the LTFS tape
• Single-volume: Single media file system for standalone drive
• Automount: Single media file system where each media is seen within a single volume as a separate directory
• Spanning: All media are automatically aggregated as large file system
Page 15 of 20
MEDIA ORGANIZATION
The number of storage media in a system can run into thousands. System configurations can range in size from a 1.3 GB
personal archive systems to multi-petabyte storage solutions. QStar can configure the library(ies) to be seen as one or multiple
Virtual Disks. This partitioning allows a multi-media library to be logically divided so that the library can appear as multiple
standard virtual hard drives allocated to different applications. In addition, partitioning allows the user to predetermine where
and when files are written. This allows data to be written to a specific set of media, thereby simplifying backup and optimizing
performance. Creating ten partitions, each with one piece of media, is comparable to creating a single partition with ten pieces
of media, each with its own directory.
The main difference between these implementations is data organization.
QStar offers configuration, media paths, and write paths in the virtual file system to provide the most flexible data organization
available. When deciding between multiple partitions and/or media paths, consider the objective of the entire storage solution.
QStar Software allows for both standalone drives and libraries in the following configuration of data set:
Integral Volume (I.V.) Set Configuration
Use the “vlcmd or vl (UNIX)” commands to create and manage an Optical, DVD, Blu-ray, Tape media set or Structured Storage
Device (Centera, HCP, Cleversafe, Amplidata, OSM) as an Integral Volume set.
This configuration requires a CACHE that manages the migration of the data between the storage media and the Hard Disk.
This configuration is available with all file systems. The media used determines the file system needed.
Note: For more detailed information please, refer to Chapter 7 - Media Configurations in this manual.
Page 16 of 20
MAJOR SOFTWARE ENHANCENENT IN VERSION 5.1
Hitachi HCP Migrator (HCP)
Allows data to be migrated from the cache file system (CFS) to the Hitachi HCP device. Specific features were
introduced to support this device
The file can be written in compatibility mode or as an extent
Rename operation is implemented as a read/delete/write operation
Support for retention periods in HCP
Curl timeout raised to 8 min
Without retention, extent is rewritten (does not create a new version)
All communication and read/write operations with HCP uses the http interface exclusively
Initial tenant support
AAFS Migrator (Archive Appliance Plasmon File System)
Implemented the new migrator, which allows reading of media written with the Archive Appliance file system
from Plasmon. The AAFS migrator accesses the AA media in read only mode
Implemented all the commands to use this file system with the Integral Volume set
Added offline medium support
Local Mount (Windows):
QStar ASM can be exported by using a NetBIOS name (mapped network drive) as in previous versions. In
addition the Integral Volume can now be presented as a local drive letter. This feature allows the sharing of the
Integral Volume set using the standard share tools provided by Windows
Cluster Migrator
The Cluster Migrator allows two (2) different Integral Volumes set to be added, using the same cache and mounts
them using the same mount point. The first Integral Volume set added is always read only while the second
Integral Volume set added is read and write; the file system directories are aggregated at the root level. The cluster
migrator does not allow multiple directories with the same name at the root level. If this happens, only the read-
write directory will be displayed. The Cluster Migrator’s features, allow for example, mounting an AAFS file
system in Read Only (RO) and a QStar file system in Read Write (RW), giving the user the ability to have two file
systems mounted but clustered together and accessible as one
Access Control List (ACL’s)
The introduction of CBFS as the Windows File System Interface (FSI) allows the mounting of the QStar file
system as a local drive; it also allows the system administrator to store all ACL’s into the QStar Cache and the
media file systems such as SDF or UDF
SCSI Subsystem
Major overhaul to the QStar SCSI subsystem to add support for USB, iSCSI, SATA, Parallel SCSI, Fibre and SAS
devices. Most of the items listed will change their addresses when the system is restarted; the primary focus of the
overhaul was to be able to regain control of these items without the user reconfiguring the devices as in the
previous versions. Now the Software will automatically reconfigure the device for the user on QStar server restart
Added support for slow storage library support
Mixed LTO tape drives and media support; allows distinguishing between LTO-1 through LTO-5 and properly
manage drives and media ensuring that the correct media will be placed into the correct drive
BluSafe: Added Serial Port detection and other Mac Specific Serial Services BluSafe direct support Windows and
Mac
Page 17 of 20
Copy Disk Utility - Multiple Incremental Copy
Implemented Multiple Incremental Copy (MiC) for SDF and UDF file systems. This new feature allows two or
more copies of the media to be created incrementally
Administration GUI (Windows)
Updated Russian and Italian localizations
Added support of Chinese simplified localization
Added support of Dutch localization
WEB GUI
Linux
Apple (MAC)
Added localization support
MAC
OSX (10.5) with CLI and Web GUI management interface
Added checks for different Mac versions, updated Darwin; Definitions for proper library locations
Porting for OSX (10.6)
Generic job scheduler
Allows configuring any event in the schedule i.e., TMT intervals
Added option for real and simulated storage libraries in the same Integral Volume set
File pre-fetch support in asynchronous mode
Allows pre-fetching of data with real time access to the pre-fetched data, meanwhile continuing to allow full
access to the file system
Mirroring SDF File System (Data Director)
Expanded vlstartmirr command in order to compare and generate audit report between primary and mirror media.
In addition can be used to synchronize primary/mirror media
Page 18 of 20
MAJOR SOFTWARE ENHANCENENT IN VERSION 6.0
Magnetic Cache File System (MCFS)
Possibility to calculate checksum of the file on fly and store such information in the stream of the file in the cache
and in the back-end (archive) storage
Replication Migrator (RPL)
Allows the replication of data between different types of media and storage at the file system level. This is
accomplished by inserting itself between the cache file system (CFS) and up to four different migrators, such as
SDF, UDF, TDO, LTFS, Object Storage and GFS. The replication migrator includes a re-synchronization feature
in case of failure of one of the replicas
Local Mount (Windows):
QStar ASM cannot be exported by using a NetBIOS name (mapped network drive) as in previous versions. The
option to use NetBIOS can be enabled only upon request with a special procedure followed by QStar Support
personnel. Starting from this version the Integral Volume can be presented only as a local drive letter. This feature
allows the sharing of the Integral Volume set using the standard share tools provided by Windows
QStar Structured Storage Devices (QSSD)
Allows support for HCP, QStar OSM (Object Storage Manager), Amplidata, Cleversafe and GFS or non-SCSI
device subsystems
Implemented qssddefine, qssdrefresh, qssdlist, qssdrename and qssddel commands
Hitachi HCP Migrator (HCP)
Provides CIFS / NFS connection
Full tenant support
Amplidata Migrator (Ampl)
Provides CIFS / NFS connection
Cleversafe Migrator (Cloud)
Provides CIFS / NFS connection
Generic File System (GFS)
GFS is any file system that is available on the server i.e., NTFS, EXT3, EXT4 and Solaris. The GFS migrator
allows migrating data to any of the generic file systems on the server. This is achieved by creating an Integral
Volume set and assigning one of the generic file systems as the “media” for the Integral Volume set. The most
common application of GFS would be to use it with the Replication Migrator (RPL)
Tape and Disk Object file system and Migrator (TDO)
The TDO migrator is a high performance file system created to optimize the read/write operations for tape and
optical disks. The design of TDO has removed the majority of the bottlenecks that are inherent with other file
systems for these types of media. TDO has been created in such a way that it supports SDF media in read-only
mode and writes all new data to the TDO file system
The read operation (for TDO and SDF) is made using a different thread, which allows different read requests to be
satisfied at the same time
Added vlcopy and vlcmp commands to copy and compare TDO media
Created SDF to TDO database conversion
Added sync statistics
Added support for stat-fs
Page 19 of 20
TDO Mirroring
Extends the functionality of TDO to provide mirrored writes (if resources are available)
Provide same functionality as in previous SDF implementation, to mirror data between TDO media either using
two drives in the same library or between two libraries.
Extended the previous mirror limit of two pieces of media in the mirror to offer a maximum of four mirrored
copies. Mirrors can be between up to four drives in one library, single drives in up to four libraries or two drives in
two libraries.
TDO can also be used to mirror data between real media based libraries and simulated media on disk
Linear Tape File System and Migrator (LTFS)
Linear Tape File System (LTFS) refers to both the format of data recorded on magnetic tape media and the
implementation of specific software that uses this data format to provide a file system interface to data stored on
magnetic tape. The Linear Tape File System format is a self-describing tape format developed by IBM to address
tape archive requirements. The LTFS Format specification, which was adopted by the LTO Technology Provider
Companies, defines the organization of data and metadata on tape - files stored in hierarchical directory structure.
Data tapes written in the LTFS Format can be used independently of any external database or storage system
allowing direct access to file content data and file metadata. This format makes it possible to implement software
that presents a standard file system view of the data stored in the tape media. This file system view makes
accessing files stored on the LTFS formatted media similar to accessing files stored on other forms of storage
media such as disk or removable flash drives. The Linear Tape File System format is an open description of the
layout of data-structures stored on a sequential-access media. These data-structures hold the file content data and
associated file metadata. Data media, such as LTO data tape, written using this format can be exchanged between
systems that understand the Linear Tape File System format. Software systems that understand the format can
provide users with a file system view of the media. Software systems may alternatively understand the format only
to the degree that allows the system to read data from the media, or produce a tape that can be accepted by other
systems that implement the Linear Tape File System format.
The file system are supported in 4 different mode described in previous FILE SYSTEM session.
Object Storage Management (OSM) Migrator
This migrator allows data to be migrated from a QStar cache to the OSM product from QStar.
Crypto Server - Encryption support
Added licensing support for crypto functions
Added support for card removal/insertion control
Added detached file verification functionality
Added sha type verification and detailed error processing
Added support for expired certificates
SmartCard and Certificates pages functionality updates
Added key delete functionality
Added crypto backup functionality
Changed signed output file protection mode
Added log messages when signing files
Verify that certificate is still valid before signing
Added certificate extended key print
Added key usage for self signed certificate creation
Added support for card certificate print
Added -f option for crptcmd info command to print selected certificate
Added support for certificate creation
Added certificate information print in XML format
Time Stamp request converted to curl. Number of TS availability request hidden from GUI (as this is very
customer-specific)
Smart card info added to the cache
Crypto stamp from crypto stream (if any) is used for signing
Page 20 of 20
Crypto Server – Digital signature
Implemented Digital Signature for UDF single volume set
Check existence of a signature file before creating it
Added code to support digital signature using qcrypto server
Administration GUI (Windows)
Updated Russian and Italian localizations
Added support of Chinese simplified localization
Added support of Dutch localization
File pre-fetch support in asynchronous mode
Allows pre-fetching of data with real time access to the pre-fetched data, meanwhile continuing to allow full
access to the file system
Page 1 of 42
This chapter describes how to get the system up and running.
Installing the software is as simple as placing the QStar CD in the CD-ROM, or running the executable, if installing from a
downloaded copy . The Installation program guides the System Administrator through every step of the process.
Before installing the QStar Software, however, certain system components should be checked, such as the system, connection of
storage devices and server configuration. This ensures that the QStar Software installation will run smoothly and minimizes the
time it takes to set up the system.
This chapter contains instructions on how to verify these components, as well as information on completing the setup of the
QStar Software.
SYSTEM REQUIREMENTS ........................................................................................................2
Software Requirements .......................................................................................................2
QStar’s Recommendation for Optimization of the System .........................................................2
The Storage Devices.........................................................................................................3
Improving the Server’s Performance...................................................................................3
Improving File System Performance....................................................................................3
Protecting Against Data Loss .............................................................................................4
Installation Considerations ................................................................................................5
Hardware and SCSI Requirements.........................................................................................6
QSTAR SOFTWARE DIRECTORIES ............................................................................................7
UPGRADING TO THE CURRENT VERSION OF QSTAR SOFTWARE...................................................8
INSTALLATION STEPS ............................................................................................................9
Diagram Installation Step: ...................................................................................................9
HARDWARE INSTALLATION AND SETUP OF DEVICES................................................................ 10
INSTALLING THE QSTAR SOFTWARE ...................................................................................... 11
SELECTING LANGUAGES....................................................................................................... 13
INSTALLING THE LICENSE KEY AND REGISTERING THE SOFTWARE............................................ 17
Demo License Key ............................................................................................................ 18
Activate the Demo License Key ........................................................................................ 18
Permanent License Key...................................................................................................... 20
Activate the Permanent License Key ................................................................................. 21
SPECIFYING THE STORAGE DEVICE CONFIGURATION............................................................... 23
Hard Drive Simulated Library Configuration .......................................................................... 28
Centera Simulated Library Configuration .............................................................................. 32
Proxy Simulated Library Configuration ................................................................................. 36
POST INSTALLATION TEST.................................................................................................... 39
QSTAR SERVER PRIORITY..................................................................................................... 40
ADDING NEW STORAGE DEVICES.......................................................................................... 41
REMOVING QSTAR SOFTWARE .............................................................................................. 42
Page 2 of 42
SYSTEM REQUIREMENTS
The host computer must have the minimum configuration described below to install the QStar products.
Note: The following applications are known to cause serious problems with the QStar Software or the Libraries attached to the
Server that the QStar Software is installed on. Any Enterprise Management Software, such as Open File Manager (OFM) or
F.A.S.T. may cause serious problems that are configured to:
1) Query the internal drives or changer assembly of the Library
2) Query and cache the QStar Software directories, or the QStar cache directories
To avoid any issues with these applications QStar recommends reconfiguring the application not to monitor or cache any
portion of the QStar Software or the devices it controls.
Software Requirements
Listed below are the minimum system requirements for installing QStar Software on the host computer.
Windows 2003/XP/Vista/2008/7
Xeon class PC (Minimum 2Ghz) Required
Memory At least 4 GB
Disk space for QStar Software on Hard Disk At least 100 MB
Service Pack 2 Windows XP
Service Pack 3 Windows 2003
SCSI/SAS host adapter supported by Windows Required
Note: The storage devices should not be on the same adapter as a SCSI hard drive.
QStar’s Recommendation for Optimization of the System
• QStar recommends a minimum of 16 GB of RAM on Windows based platforms
• Upgrading the memory as much as possible will provide faster data access
• To improve processing speed, use a processor that is faster than the minimum requirement
• Use a separate SCSI host adapter for the library
• Additional Hard Drive space on the main NTFS volume or additional NTFS volumes will provide better cache utilization
• Use fast disk storage systems (RAID with FC or SAS drives) if very fast ingestion is required
Client Workstations mapping to a QStar Integral Volume set should have the following minimum configurations:
• Server 2000, XP Pro, Server 2003, Vista, 7, 2008
• PC with 4 GB of RAM
Page 3 of 42
To achieve the best possible performance from Windows based platforms and the QStar Software, the following are
suggested:
The Storage Devices
Selecting the Appropriate Hardware to Maximize Performance
One of the largest decisions to consider when setting up the QStar Software is which storage device(s) is best suited for the
environment. The hardware configurations can be significantly different depending upon the storage needs of the enterprise. To
determine which type of storage devices including the number of drives, number of shelves and media type will provide the best
performance; a complete and thorough evaluation of the enterprise needs should be conducted. The number of users and the
amount of data being accessed will determine the number of drives, shelves and type of media that will be required in the library
to maintain optimum performance.
Improving the Server’s Performance
All of the following affect the performance of the Server the QStar Software is installed on:
• The amount of available RAM
• The size, speed (in RPMs and bus speed) and the number of hard drives plus RAID configuration
• The number of processors and their power
• The network cabling and configuration
Amount of Available RAM
Memory is the fastest and cheapest way to improve performance on the Server the QStar Software is installed on. Maximizing
the RAM on the Server will significantly improve Windows based platforms and the QStar Software performance.
Number of Machine’s Processors
QStar Software can be installed on either single or multiple-processor machines. Using a multi-processor machine, the number
of multiple tasks that can be performed at the same time is increased significantly. Using a multiple-processor machine for the
QStar Software will greatly improve the migration performance.
Improving File System Performance
The following will affect the performance of the QStar file system:
• High and Low Primary capacities
• The total number of files per directory in the QStar file system
Setting the High Primary Capacity
The High Primary Capacity is set to 80% of the cache size by default. Lowering this setting can be beneficial when using a
large cache or during periods of high volume transfers to the QStar file system. This will allow the data in the cache to be
written to the archive media sooner, which will increase the available space in the cache for the new files.
Page 4 of 42
Creating an efficient file system
How the file system is structured will have a significant effect on its performance. The sector size of the media verses the size
of the files can significantly affect space utilization on the media. The layout of the directories and the number of files in any
given directory are an important consideration when designing a file system. QStar recommends no more than 3000 files per
directory to maintain optimum file system performance.
Expected Behaviors
Because the file system that QStar usually manages is removable and a multi-surfaced file system, there are some expected
behaviors that need to be addressed when creating the file system.
Creating a directory structure on removable media that is extremely deep and has a small number of files and a small file size in
each directory will offer poor space utilization on the media and should be avoided.
Exceeding the 3000 files on removable media per directory recommendation will cause degradation of performance to the file
system. This decrease in performance will manifest itself when a user tries to browse the directory and will increase with the
number of files in the directory. For example, with 5000 files in a directory the impact on the user will be slight. However,
with 50,000 files in a directory the impact will be more significant and could have an effect on other users trying to access the
file system. In extreme situations, this decrease in performance can cause extremely slow or no access to the mount point of the
QStar file system.
The number of files in the directory structure will have the most impact in a disaster recovery situation or if the cache files have
to be rebuilt. In this situation, the mount point may not be accessible for several hours depending on the number of files in the
directory structure.
If direct access to a file by an application is used, the number of files in a directory can be increased and there will be no impact
on performance under these circumstances. However, it must be understood that direct access will not remove degradation of
performance when browsing the directory or during a disaster recovery situation.
Protecting Against Data Loss
QStar copies the data out to the media during the archiving process automatically based on the High Primary Capacity (HPC)
value by default. To ensure that all data in the QStar file system is protected against system failure (including hard disk failure);
QStar offers several utilities to protect the data from loss or corruption. Using one or more of these utilities is highly
recommended.
Scheduled Archives
It is recommended that the System Administrator periodically archive data without waiting for the HPC to begin archiving. A
daily archive is beneficial to most users who maintain a large cache with a defaulted HPC value. Archiving can be scheduled to
start automatically every day using the QStar’s VL Scheduler.
Media Redundancy
QStar recommends the use of media redundancy for the Integral Volume sets (i.e. Copy Media), if the data is mission-critical.
Recovery time after a disaster can be significantly reduced if media redundancy is used on the QStar Integral Volume set.
However, further redundancy can be achieved utilizing QStar’s Data Director product in which all information is mirrored to
an Identical Integral Volume set. In the event the primary server goes down, the primary servers can be “swapped” and the
secondary mirror can become the primary file server in a matter of minutes.
Using Automated Copy Media to back up the Primary Media
The Copy Media feature creates an identical piece of media from the primary Integral Volume set. This capability takes away
the potential of data becoming unrecoverable because of a damaged media and provides for an off-site media copy.
Page 5 of 42
Installation Considerations
Before installing the QStar Software, it may be advantageous to consider the overall storage needs for the system.
It is advisable to make a cache size appropriate for daily usage.
Considerations for cache size are:
How much new data will be archived per day?
How much data will be requested from the library per day?
Some issues to consider include:
The total amount of files expected per directory inside of the QStar Integral Volume set, appropriate watermark levels and
scheduling data archiving.
Some organizations have existing file storage systems, and may have already decided upon an optimum arrangement for the file
server.
Sizing the Cache
A general rule for an Integral Volume’s cache size is, more is better. An Integral Volume’s cache size should be selected
depending upon the system’s activity and required response time. The larger the Integral Volume cache, the faster the system
performance, because there is a greater chance that the files being requested are already in the cache. For systems with large
volumes of data, the cache should be sized to accommodate an entire day’s processing. This allows the users to work at full
speed during the day, with the QStar Software performing time-costly migration at night.
Each Integral Volume set must be sized separately. Calculating overhead space in addition to cache size will help determine the
hardware requirements for the QStar file system.
As a general rule of thumb, 1,000,000 files will require 500 Megabytes of hard drive space over and above the cache size
for metadata overhead. However, this rule should only be used for an approximate estimate of required drive size.
Page 6 of 42
Hardware and SCSI Requirements
A library or standalone drive that will be connected to the host computer via the SCSI (Small Computer System Interface) bus
must comply with some requirements.
Every device attached to the SCSI bus must be assigned a unique SCSI ID or “address”.
Please refer to the SCSI host bus adapters’ manufacturer’s recommendation for maximum cable lengths. The combined internal
and external length of cables from the host computer to the end of the SCSI bus must be determined. This combined length
must not be exceeded. As an example the combined length of all SCSI cables, including the integration of the QStar subsystem,
must not exceed 6 meters (approximately 18 feet) for a single-ended SCSI bus. If the cable exceeds 6 meters, operational
problems such as device errors or system failures could occur. QStar recommends that the length of the SCSI cable from the
host computer to the library or standalone drive be no longer than 3 meters. The operating environment (noise and/or high
voltage power supply) could also have an effect on the optimal cable length. Ensure that the SCSI bus is terminated correctly
using an active terminator.
The number of SCSI IDs that will be needed for the QStar subsystem depends on the type of device that will be installed.
Be sure to keep track of which drive number in the library corresponds with each SCSI ID.
Once it has been determined what devices are currently attached to the SCSI bus, then decide which available SCSI IDs will be
used for the library or standalone drive.
In addition, before beginning the installation, make sure the following are available:
• The hardware manual for the particular library
• SCSI Cable(s) and active terminator for connecting the library or standalone drive
• QStar Software installation CD-ROM or downloaded software
Page 7 of 42
QSTAR SOFTWARE DIRECTORIES
QStar installs its Software by default in the c:qstar directory. In the c:qstar directory, the following files and directories will be
listed:
backup This directory contains internal backups of the Integral Volume set database.
bin This directory contains commands for managing and controlling the QStar Software. These commands can be
used at the MS-DOS command window as well as being included in Batch files.
crpt This directory contains commands for managing and controlling the encryption Software.
dev This directory contains internal descriptions of the QStar controlled devices.
doc This directory contains the API html documentation.
emg This directory contain configuration files used with OSM/TDO/Amplidata/Cleversafe Migrator.
include This directory contains the QStar Include files.
install This directory contains the list of configured devices as well as the classes configuration file.
jb This directory contains all of the configuration and database files used by the QStar Device Manager to maintain
and control the configured libraries.
lib This directory contains the QStar Library files.
license This directory includes the license file.
log This directory contains the various QStar log files. The most important file is the syslog text file. If SCSI
command logging is turned on then this directory will also contain the scsi_log text file.
mcfs This directory that contains the MCFS module - Front end caching.
qscsi This directory that contains the QSCSI module - Low level drivers.
sdf This directory that contains the SDF module - Standard Data Format file system.
svc This directory contains the QStar system services and drivers which are started automatically when the system is
booted.
tmp Temporary directory sometimes used by QStar Software.
vl This directory maintains the list of defined sets and the state of each medium within the devices utilized for set
allocation.
Page 8 of 42
UPGRADING TO THE CURRENT VERSION OF QSTAR
SOFTWARE
To de-install the QStar Software in order to install an upgrade, or in preparation of moving to another host, follow the steps
below:
1) Archive all data out of each Integral Volume’s cache.
In the QStar Administration Interface, select Integral Volumes and next select Migration View.
Select the Archive button to start the archiving. Do this for each Integral Volume set.
2) Unmount all Integral Volume sets.
In the QStar Administration Interface, select Integral Volumes and next select the Volume Management.
Select the Unmount button to unmount the Volumes. Do this for each Integral Volume set.
Note: For safety, QStar suggests saving the information of device and Integral Volume sets database by running from dos
prompt the vlcmd lsdev device_name and vlcmd lsset -va commands and redirects the output into a file.
3) Stop the QStar Server.
In the QStar Administration Interface, select QStar Server for version 4.x or select Server and next Status for version
5.x or and select the Stop button.
4) Remove the QStar Software from the computer.
From the Start menu, select the QStar program group and select the Uninstall QStar Software.
The machine will have to be rebooted to complete the de-installation.
5) Once the machine has restarted, in a Windows Explorer window, there are two options:
a) Remove the c:qstar directory and any files in the old cache directory (c:qstar is the default location for the QStar
Software). This removes all database files for the Integral Volume sets and libraries configured under the previous
installation.
b) Do not remove c:qstar directory. This will allow the ability to restore all previous QStar database files for Integral
Volume sets and libraries.
The format of the cache files in version 6.x are incompatible with the cache files for all 4.x and 5.x versions,
so the System Administrator will be forced to mount all Integral Volume sets with clean cache after the upgrade. For
DVD libraries after the uninstall procedure remove the file c:qstarjbfilesjb_param_*.
6) To install the new release of the QStar Software see the Installation Steps section on the next page.
INSTALLATION STEPS
For a correct installation of QStar Software these steps must be followed in the order shown on the diagram below:
Diagram Installation Step:
Page 9 of 42
Page 10 of 42
HARDWARE INSTALLATION AND SETUP OF DEVICES
To install the storage libraries or standalone drive(s), follow these steps:
1) Shut down the system using the standard shut down procedure.
2) Reboot the system and read the list of the attached SCSI devices from boot screen and take note of the currently used SCSI
target IDs.
3) Power off the system.
4) Select the appropriate SCSI target IDs from those that are available for each storage device that will be connected to the
host. Set the SCSI IDs of the storage devices per the instructions in the hardware operator’s manual. Select any available
number from target 0 through 6 on the SCSI bus for your storage devices.
For specific hardware information, consult the hardware manual that came with the library or standalone drive.
5) Attach each device to its appropriate SCSI controller(s) and attach a terminator to the last device on each SCSI bus. Power
up all peripherals. Power up the server.
Verify the SCSI ID settings of the libraries or standalone drive(s) to ensure there are no conflicts with other devices on the
same SCSI bus; use the SCSI Utility to verify target ID usage.
The system returns a list similar to the one seen in Step #2 above. This list should now also include the inquiry strings from
the newly attached devices. Confirm that all devices seen in Step #2 are still visible. If any of the devices that were
previously seen are not seen now, the device may have been set to an address already in use. In this case, recheck the results
from Step #2 and start again. Also, be sure to confirm all SCSI cables and terminators are securely connected.
6) During the boot process, the operating system will configure the devices attached to the system.
Page 11 of 42
INSTALLING THE QSTAR SOFTWARE
This section demonstrates the QStar Software installation program. The installation program automatically sets up all necessary
product directories and files.
Before installing the QStar Software, the System Administrator needs to do the following:
• Disable the Microsoft Removable Storage services
• Disable any Antivirus Software and if re-enabled after the installation be sure that the QStar program and
QStar Integral Volume Sets cache folders are excluded from antivirus check
• If QStar Software is going to be installed in any server where a different library management software vendor
was previously used, it requires any existing library software/drivers be uninstalled. The System Administrator
should contact the previous supplier for more specific un-installation instructions
To install the QStar Software, follow these steps:
1) Begin by inserting the CD-ROM into the drive. If Autorun is configured, a welcome screen should appear as the system
recognizes the disk. If Autorun is not configured, select the Start menu button. Then select Run and type D:autorun (D:
being the CD-ROM drive). This process is the same for downloaded software.
2) Once the Installation menu appears, please select the Install QStar Software for Windows button to install the QStar
Software. Select the Manuals and Documentations button to view the list of documents available on the CD-ROM.
3) After Choosing Install QStar Software or by manually running the Setup Program, select the appropriate language.
When finished, select the OK button.
4) Select the Next button on the setup wizard windows to continue.
5) Review the license terms before installing QStar Software. Place a check in the check box to accept the terms of the
agreement. The agreement must be accepted to install QStar Software. Select the Next button to continue. Otherwise select
the Cancel button to exit the Setup program.
6) Personalize the Software by filling in the blanks. Select the Next button to continue.
7) Choose Install location. To install the QStar Software to the default location of C:QStar, select the Next button. To install
the QStar Software to a different folder or drive letter, select the Browse button and select the desired drive letter or folder
name.
8) Select the required QStar product to be installed on the system.
The options are the following:
• QStar ASM (Full Storage Management Product)
• QStar Data Director (ASM + Mirroring Capabilities)
• QStar Archive Replicator (Synchronous file replicator)
After making the Software selection, select the Next button to continue, or select the Cancel button to leave the Setup program.
9) New USB and TCP/IP supported devices may conflict with RAID system.
Figure 3.1 Device Configuration
By default QStar will not check USB or TCP/IP
device during the claiming procedure. If
MO/UDO drive, USB device, BluSafe device
and TCP/IP device will be used. Place a check
mark in order to notify QStar to discover such
type of device during claiming procedure.
Note: For TCP/IP library the System
Administrator need to insert IP Address and
Port value.
10) Select the type of installation. Typical, which is the default and recommended installation, will give full functionality of the
QStar Software including the API support. Custom and Compact will not install API files and API documentation. After
making the selection, select the Next button to continue. Select Publisher if the Software needs to work with any publisher
device. Expand Publisher check box and then select the correct model of publisher device (available only with special
releases).
11) Select the location for the QStar Software icons in the Program Folder. Create a location for the QStar Software by filling
in the blanks or selecting the default location. Select the Next button to continue.
12) Mark the device(s) that are going to be controlled by the QStar Software and select the OK button.
In the Device Claiming Window, QStar will
display all hard disks on the system this is because
the operating system will report some types of
optical drives as hard disk. However, QStar
CANNOT control a real hard disk as a SCSI
device. Configuring the QStar Software with the
EMC Centera, Amplidata, HDS HCP, Cleversafe,
Simulated Tape, or Simulated Disk there is no
need to claim any devices. Do not mark any
device(s) and select the OK button.
Figure 3.2 QStar Device Claiming
13) After the installation is complete, select Reboot now and select the Finish button.
Page 12 of 42
SELECTING LANGUAGES
Once the QStar Software has been installed and the system has restarted, the following is required to select the languages of the
QStar Administration Interface:
Starting QStar ASM Product
Figure 3.3 - Start Button - QStar ASM Software Product
Log on to the system as the
Administrator.
Go to the Start button, then
Programs, then QStar ASM.
Select QStar Administration
Interface on LOCALHOST. Skip
Figure 3.6.
Or select QStar Administration
Interface, and go to Figure 3.6.
Starting QStar DDR Product
Figure 3.4 - Start Button - QStar Data Director Software Product
Log on to the system as the
Administrator.
Go to the Start button, then
Programs, then QStar DDR.
Select QStar Administration
Interface on LOCALHOST. Skip
Figure 3.6.
Or select QStar Administration
Interface, and go to Figure 3.6.
Page 13 of 42
Starting QStar Archive Replicator Product
Figure 3.5 - Start Button - QStar Archive Replicator Software Product
Log on to the system as the
Administrator.
Go to the Start button, then
Programs, then QStar Archive
Replicator.
Select QStar Administration
Interface on LOCALHOST. Skip
Figure 3.6.
Or select QStar Administration
Interface, and go to Figure 3.6.
Page 14 of 42
In this window, expand the My Network Places and select the computer
to administer.
Selecting the Cancel button will open the local host.
Figure 3.6 - Browse for Computer
Figure 3.7 - QStar Administration Interface
Once the computer is selected to
administer, the QStar
Administration Interface opens
displaying information about QStar
Version Number and the phone
numbers to call for assistance or
technical support. The same
information can be found by
selecting About QStar... under
Help option.
By default the language of the
QStar Administration Interface is
the one specified during the
installation procedure.
To change the language, select the
Language selection in the menu
bar. Once selected the QStar
Administration Interface will close
and open automatically with the
new language.
Page 15 of 42
The new QStar Administration
Interface consists of a window
divided into two panes. The
navigation pane in the left
displays the category tree that
shows the list of items that are
available to manage QStar
Software. The view pane in the
right contains the details of the
information, functions and
options pertaining to these items.
Figure 3.8 - QStar Administration Interface
Figure 3.9 - QStar Administration Interface. License Key is activated.
Selecting different items in the
category tree, the information in the
view pane changes.
Page 16 of 42
INSTALLING THE LICENSE KEY AND REGISTERING
THE SOFTWARE
Figure 3.10 - License
To install the license keys, select
License and call QStar Customer
Support for guidance through the
license key installation and to
provide an activation key.
License provides all the
information needed to obtain a
Demo or Permanent License Key
from QStar Customer Support
Personnel.
When Accessing License for the
first time an error message will be
displayed notifying the System
Administrator that the License
Key is invalid because it is not
entered yet.
The license information
displayed before the Software is
licensed contains the following:
• QStar version
• Platform
• Host ID
The Serial Number can be found
on the license card or on the
back of the CD case supplied
with the Software.
Figure 3.11 - License
Page 17 of 42
Demo License Key
Figure 3.12 - Inserting the Demo License Key Information
The information that the System
Administrator should provide to
QStar Customer Support personnel
for a Demo License key is the
following:
• Company: *
• Department:
• Contact person:
• Contact email: *
• Contact phone:
• QStar version: 6.0 *
• License Type: Demo
• Platform: *
• Host ID: *
*: Mandatory information
The above information can be inserted
into the Product Registration Form
available on the distribution CD-ROM
and faxed to +1-850-243-4234 (USA),
+39-02-45101-745 (EUROPE) or your
local QStar office.
If preferred, email to license@qstar.com or license@qstar.it. A Customer Support representative will email the License Key and
any further instructions. A license request page is available on the QStar website, http://www.qstar.com/support/license-key-
request-form/
Activate the Demo License Key
The Demo license key is a file that
will be sent to a specified email
address. Depending on the version
of Software, the file should be
either copied to the
c:QStarlicense folder or use the
Activate Button. Once the license
file is copied or uploaded, close
and then re-open the
Administration Interface to see the
new license key information.
T
The Demo License Key will allow
the use of all the QStar Products
with any device for the time
specified in the Expiration Date
box. The maximum number of
libraries that can be controlled by
the QStar Software at the same
time is 8.
The Serial Number for Demo
license is not necessary and will be
displayed as N/A (Not Available).
Note: In the example, the License
type is changed to Demo and the
Figure 3.13 - Inserting the Demo License Key Information License Key is activated.
Page 18 of 42
Figure 3.14 - Inserting the Demo License Key Information
If the Demo license expires, a
red question mark symbol will
appear in the Expiration date
box and a pop up window will
appear each time License is
selected.
Note: In the example, the Demo
License Key is expired.
If the library was already
configured, to restart the QStar
Server, select Status, in the view
pane select the Start button and
the server will restart, completing
the library configuration.
If the library configuration is not
already configured go to the
“Specifying the Storage Device
Configuration” section.
Note: The Publisher Manager
State information will be
available only if QStar Software
will be used with a publisher
device.
Figure 3.15 - QStar Server (Restarting the Server)
Page 19 of 42
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07
05. q star system_administrator's_guide_windows_v6.0_rev.07

More Related Content

What's hot

【NGINXセミナー】API ゲートウェイとしてのNGINX Plus活用方法
【NGINXセミナー】API ゲートウェイとしてのNGINX Plus活用方法【NGINXセミナー】API ゲートウェイとしてのNGINX Plus活用方法
【NGINXセミナー】API ゲートウェイとしてのNGINX Plus活用方法NGINX, Inc.
 
Data × AI でどんな業務が改善できる? ​製造業様向け Data × AI 活用ユースケース & 製造MVPソリューションのご紹介
Data × AI でどんな業務が改善できる? ​製造業様向け Data × AI 活用ユースケース & 製造MVPソリューションのご紹介Data × AI でどんな業務が改善できる? ​製造業様向け Data × AI 活用ユースケース & 製造MVPソリューションのご紹介
Data × AI でどんな業務が改善できる? ​製造業様向け Data × AI 活用ユースケース & 製造MVPソリューションのご紹介IoTビジネス共創ラボ
 
從雲端到邊緣 Azure IoT Edge 幫工廠設備長智慧
從雲端到邊緣 Azure IoT Edge 幫工廠設備長智慧從雲端到邊緣 Azure IoT Edge 幫工廠設備長智慧
從雲端到邊緣 Azure IoT Edge 幫工廠設備長智慧Poy Chang
 
20190222_インベントリ収集のオープンソースOpenAudITの機能紹介とIT資産管理で必要なこと
20190222_インベントリ収集のオープンソースOpenAudITの機能紹介とIT資産管理で必要なこと20190222_インベントリ収集のオープンソースOpenAudITの機能紹介とIT資産管理で必要なこと
20190222_インベントリ収集のオープンソースOpenAudITの機能紹介とIT資産管理で必要なことIO Architect Inc.
 
ぶっちゃけAIPスキャナってどうよ?~AIPスキャナ検証録~
ぶっちゃけAIPスキャナってどうよ?~AIPスキャナ検証録~ぶっちゃけAIPスキャナってどうよ?~AIPスキャナ検証録~
ぶっちゃけAIPスキャナってどうよ?~AIPスキャナ検証録~Akito Katsumata
 
クラウドコストを最適化せよ!マルチクラウド時代に届けるクラウド活用2.0
クラウドコストを最適化せよ!マルチクラウド時代に届けるクラウド活用2.0クラウドコストを最適化せよ!マルチクラウド時代に届けるクラウド活用2.0
クラウドコストを最適化せよ!マルチクラウド時代に届けるクラウド活用2.0Tomohisa Koyanagi
 
Top home security keywords
Top home security keywordsTop home security keywords
Top home security keywordsEvan Kramer
 
C34 ニッチだけど、社会インフラを支えるデータベース、HiRDB ~HiRDBを選ぶ人、選ばない人、その選択基準とは~ by Taichi Ishikawa
C34 ニッチだけど、社会インフラを支えるデータベース、HiRDB ~HiRDBを選ぶ人、選ばない人、その選択基準とは~ by Taichi IshikawaC34 ニッチだけど、社会インフラを支えるデータベース、HiRDB ~HiRDBを選ぶ人、選ばない人、その選択基準とは~ by Taichi Ishikawa
C34 ニッチだけど、社会インフラを支えるデータベース、HiRDB ~HiRDBを選ぶ人、選ばない人、その選択基準とは~ by Taichi IshikawaInsight Technology, Inc.
 
kpackによるコンテナイメージのビルド
kpackによるコンテナイメージのビルドkpackによるコンテナイメージのビルド
kpackによるコンテナイメージのビルドMasanori Nara
 
Azure Active Directory Domain Services (Azure ADDS) キホンのキ
Azure Active Directory Domain Services(Azure ADDS)キホンのキAzure Active Directory Domain Services(Azure ADDS)キホンのキ
Azure Active Directory Domain Services (Azure ADDS) キホンのキTetsuya Yokoyama
 
вплив косметичних засобі на життя людини(чуєва, герій)
вплив косметичних засобі на життя людини(чуєва, герій)вплив косметичних засобі на життя людини(чуєва, герій)
вплив косметичних засобі на життя людини(чуєва, герій)orestznak
 

What's hot (13)

【NGINXセミナー】API ゲートウェイとしてのNGINX Plus活用方法
【NGINXセミナー】API ゲートウェイとしてのNGINX Plus活用方法【NGINXセミナー】API ゲートウェイとしてのNGINX Plus活用方法
【NGINXセミナー】API ゲートウェイとしてのNGINX Plus活用方法
 
私がなぜZscalerに?
私がなぜZscalerに?私がなぜZscalerに?
私がなぜZscalerに?
 
Data × AI でどんな業務が改善できる? ​製造業様向け Data × AI 活用ユースケース & 製造MVPソリューションのご紹介
Data × AI でどんな業務が改善できる? ​製造業様向け Data × AI 活用ユースケース & 製造MVPソリューションのご紹介Data × AI でどんな業務が改善できる? ​製造業様向け Data × AI 活用ユースケース & 製造MVPソリューションのご紹介
Data × AI でどんな業務が改善できる? ​製造業様向け Data × AI 活用ユースケース & 製造MVPソリューションのご紹介
 
AWS CognitoからAuth0への移行パターン4つ
AWS CognitoからAuth0への移行パターン4つAWS CognitoからAuth0への移行パターン4つ
AWS CognitoからAuth0への移行パターン4つ
 
從雲端到邊緣 Azure IoT Edge 幫工廠設備長智慧
從雲端到邊緣 Azure IoT Edge 幫工廠設備長智慧從雲端到邊緣 Azure IoT Edge 幫工廠設備長智慧
從雲端到邊緣 Azure IoT Edge 幫工廠設備長智慧
 
20190222_インベントリ収集のオープンソースOpenAudITの機能紹介とIT資産管理で必要なこと
20190222_インベントリ収集のオープンソースOpenAudITの機能紹介とIT資産管理で必要なこと20190222_インベントリ収集のオープンソースOpenAudITの機能紹介とIT資産管理で必要なこと
20190222_インベントリ収集のオープンソースOpenAudITの機能紹介とIT資産管理で必要なこと
 
ぶっちゃけAIPスキャナってどうよ?~AIPスキャナ検証録~
ぶっちゃけAIPスキャナってどうよ?~AIPスキャナ検証録~ぶっちゃけAIPスキャナってどうよ?~AIPスキャナ検証録~
ぶっちゃけAIPスキャナってどうよ?~AIPスキャナ検証録~
 
クラウドコストを最適化せよ!マルチクラウド時代に届けるクラウド活用2.0
クラウドコストを最適化せよ!マルチクラウド時代に届けるクラウド活用2.0クラウドコストを最適化せよ!マルチクラウド時代に届けるクラウド活用2.0
クラウドコストを最適化せよ!マルチクラウド時代に届けるクラウド活用2.0
 
Top home security keywords
Top home security keywordsTop home security keywords
Top home security keywords
 
C34 ニッチだけど、社会インフラを支えるデータベース、HiRDB ~HiRDBを選ぶ人、選ばない人、その選択基準とは~ by Taichi Ishikawa
C34 ニッチだけど、社会インフラを支えるデータベース、HiRDB ~HiRDBを選ぶ人、選ばない人、その選択基準とは~ by Taichi IshikawaC34 ニッチだけど、社会インフラを支えるデータベース、HiRDB ~HiRDBを選ぶ人、選ばない人、その選択基準とは~ by Taichi Ishikawa
C34 ニッチだけど、社会インフラを支えるデータベース、HiRDB ~HiRDBを選ぶ人、選ばない人、その選択基準とは~ by Taichi Ishikawa
 
kpackによるコンテナイメージのビルド
kpackによるコンテナイメージのビルドkpackによるコンテナイメージのビルド
kpackによるコンテナイメージのビルド
 
Azure Active Directory Domain Services (Azure ADDS) キホンのキ
Azure Active Directory Domain Services(Azure ADDS)キホンのキAzure Active Directory Domain Services(Azure ADDS)キホンのキ
Azure Active Directory Domain Services (Azure ADDS) キホンのキ
 
вплив косметичних засобі на життя людини(чуєва, герій)
вплив косметичних засобі на життя людини(чуєва, герій)вплив косметичних засобі на життя людини(чуєва, герій)
вплив косметичних засобі на життя людини(чуєва, герій)
 

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

Similar to 05. q star system_administrator's_guide_windows_v6.0_rev.07 (20)

TA Manual Supplement.pdf
TA Manual Supplement.pdfTA Manual Supplement.pdf
TA Manual Supplement.pdf
 
Ftk install guide
Ftk install guideFtk install guide
Ftk install guide
 
ORACLE DEMANTRA
ORACLE DEMANTRAORACLE DEMANTRA
ORACLE DEMANTRA
 
Opm costing
Opm costingOpm costing
Opm costing
 
Ftk ug
Ftk ugFtk ug
Ftk ug
 
EMR5000v23
EMR5000v23EMR5000v23
EMR5000v23
 
MDM-SGG_Business_User_Guide_v2_2_0_2.pptx
MDM-SGG_Business_User_Guide_v2_2_0_2.pptxMDM-SGG_Business_User_Guide_v2_2_0_2.pptx
MDM-SGG_Business_User_Guide_v2_2_0_2.pptx
 
MDM-SGG_Business_User_Guide_v2_2_0_2.pptx
MDM-SGG_Business_User_Guide_v2_2_0_2.pptxMDM-SGG_Business_User_Guide_v2_2_0_2.pptx
MDM-SGG_Business_User_Guide_v2_2_0_2.pptx
 
Sigtran oracle
Sigtran oracleSigtran oracle
Sigtran oracle
 
License
LicenseLicense
License
 
License
LicenseLicense
License
 
License
LicenseLicense
License
 
asl_ref
asl_refasl_ref
asl_ref
 
Oracle database 12c client installation guide
Oracle database 12c client installation guideOracle database 12c client installation guide
Oracle database 12c client installation guide
 
Tera data install guide for linux
Tera data install guide for linuxTera data install guide for linux
Tera data install guide for linux
 
Downloadattachmentprocessor
DownloadattachmentprocessorDownloadattachmentprocessor
Downloadattachmentprocessor
 
Oracle demantra implementation guide part e22232 09
Oracle demantra implementation guide part e22232 09Oracle demantra implementation guide part e22232 09
Oracle demantra implementation guide part e22232 09
 
A85248
A85248A85248
A85248
 
Micrso Strategy Advanced Guide
Micrso Strategy Advanced GuideMicrso Strategy Advanced Guide
Micrso Strategy Advanced Guide
 
Demantra12
Demantra12Demantra12
Demantra12
 

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

  • 2.
  • 3. 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 cs@qstar.com • Or E-mail support in Europe is available through info@qstar.it Addresses: QStar Technologies, Inc. (USA) 8738 Ortega Park Drive Navarre, FL 32566 Tel: +1-850-243-0900 Fax: +1-850-243-4234 E-mail: cs@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: info@qstar.it Web URL: http://www.qstar.com/ QStar Technologies Japan Shinjuku Park Tower N30F 3-7-1 Nishi Shinjuku, Shinjuku-ku Tokyo 163-1030 Japan E-mail: info@qstar.com Web URL: http://www.qstar.com/
  • 4.
  • 5. 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.
  • 6. EVALUATION SOFTWARE. If the SOFTWARE you have requested is an evaluation copy only, LICENSEE recognizes that the SOFTWARE has tangible value, contains valuable trade secrets, copyrights, and confidential information of QStar and is the sole property of QStar. LICENSEE shall have no right to print or copy the QStar SOFTWARE or documentation in whole or in part. All SOFTWARE shall remain the property of QStar and must be returned upon completion of evaluation. QStar SOFTWARE is “For Demonstration or Evaluation Use Only.” LICENSEE agrees not to re-sell and/or use the SOFTWARE provided for its own internal business usage without the formal written consent of QStar. NO OTHER WARRANTIES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, QSTAR TECHNOLOGIES DISCLAIMS ALL OTHER WARRANTIES, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE SOFTWARE, AND THE ACCOMPANYING WRITTEN MATERIALS. THIS LIMITED WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS. YOU MAY HAVE OTHER RIGHTS, WHICH VARY FROM STATE/JURISDICTION TO STATE/JURISDICTION. NO LIABILITY FOR CONSEQUENTIAL DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL QSTAR TECHNOLOGIES, OR ITS SUPPLIERS, BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OR INABILITY TO USE THIS QSTAR TECHNOLOGIES PRODUCT, EVEN IF QSTAR TECHNOLOGIES HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Because some states/jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, the above limitation may not apply to you. RESTRICTED RIGHTS. The SOFTWARE and documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraph (c)(1) and (2) of the Commercial Computer Software- Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is QStar Technologies, 8738 Ortega Park Drive Navarre, FL 32566 USA. Unpublished – All rights reserved under the copyright laws of the United States and of other countries. GENERAL. If you acquired this product in the United States, the laws of the State of Florida govern this Agreement. If this product was acquired outside the United States, then local law may apply. This Agreement sets forth the entire Agreement between QStar and you may be amended only in writing signed by both parties. No waiver of any right under this Agreement shall be effective unless in writing signed by both parties. If any provision in this Agreement is invalid or unenforceable that provision shall be construed, limited, modified or, if necessary served, to the extent necessary, to eliminate its invalidity or un-enforceability and all other provisions of this Agreement shall remain unaffected. Should you have any questions concerning this Agreement, or if you desire to contact QStar Technologies for any reason, please contact the subsidiary serving your country, or write: QStar Technologies, Inc., Attn: General Counsel, 8738 Ortega Park Drive Navarre, FL 32566 USA. QStar Technologies is a registered trademark of QStar Technologies, Inc D-LIC-05-09 5/00
  • 7. Page 1 of 4 QStar Technologies is the market leader in secure, large-scale client/server archiving and data management solutions for Windows and UNIX. QStar provides solutions that allow every level of your organization to store and manage the resources of even the most heterogeneous networks. The world’s leading organizations increasingly rely on QStar for the secure, cost effective and reliable storage of their critical data. More than two decades of experience and a large installed base have provided QStar with the knowledge to create software that brings life to storage hardware. The functionality of QStar Software is based on extensive research of user requirements and customer feedback, which has enabled QStar to develop an industry-leading product. QStar Software significantly reduces the overall storage costs within a network. At the same time, productivity is boosted by keeping all of the data logically online, all the time. QStar Software integrates all storage media on the network. Magnetic disks, Cloud Storage, optical, tape, RDX, both offline and nearline, are consolidated into a single network storage hierarchy. The view of the storage hierarchy is a network available logical disk, transparent to users and applications. Using this method, terabytes or petabytes of data storage can be accessed in real time. QStar Software can represent multiple media as a single volume, keeping track of the exact location of all files on each medium. Archiving applications for Media and Entertainment, Imaging, CAD/CAM, Document Management, PACS, and other applications are fully compatible with QStar Software. This System Administrator’s Guide provides the information you will need to install, configure and utilize QStar Software to manage data. It contains all the necessary information to achieve the best results for implementing and customizing your mass storage solution. This Chapter contains an introduction to the platforms, devices and media supported. PLATFORMS SUPPORTED ...................................................................................2 MEDIA SUPPORTED...........................................................................................3 QSTAR MANUAL REVISION.................................................................................3 CHAPTER SUMMARY..........................................................................................4
  • 8. Page 2 of 4 PLATFORMS SUPPORTED QStar Software supports the following server platforms: • Sun - Solaris • IBM - AIX • Hewlett Packard - HP-UX series 700/800 • Microsoft - Windows 2003/2008, Windows XP, Windows Vista, Windows 7 • Linux - Redhat - SUSE - Debian - Ubuntu - Mandrake - Gentoo – Fedora - CentOS • Apple - MAC
  • 9. Page 3 of 4 MEDIA SUPPORTED The type and quantity of data being stored by users determines which media they will use to store it. QStar supports a wide variety of archival media, including Optical disks, digital Tapes, RDX, CD-ROMs, DVD-ROMs DVD- RAMs and Blu-ray. Removable Media, come in a wide range of sizes and capacities. Another distinguishing characteristic is whether they are Rewritable, able to be erased and reused, or WORM, Write Once Read Many. The following list defines the media types currently supported: MEDIA TYPE SUPPORT TYPE Rewritable MO Optical Read/Write WORM MO Optical Read/Write Rewritable UDO1 - UDO2 Read/Write WORM UDO1 - UDO2 Read/Write Compliance WORM UDO1 - UDO2 Read/Write Rewritable PDD Read/Write WORM PDD Read/Write Tape (AIT - AIT2 - AIT3 - AIT3 WORM - SAIT) Read/Write Tape (LTO1 - LTO2 - LTO3 - LTO4 - LTO5 – LT06) Read/Write Tape (DLT - SDLT ) Read/Write Tape (9730 - 9840 - 9940A - 9940B) Read/Write Tape Oracle T10000C Read/Write CD/DVD-ROM Read Only CD-R Read/Write CD-RW Read/Write DVD-RAM Read/Write DVD-R Read/Write DVD-RW Read/Write BD-RE Read/Write BD-R Read/Write RDX Read/Write Centera/HCP/OSM/Cleversafe/Amplidata Read/Write HARD DISK (Simulated Disk/Tape) Read/Write QSTAR MANUAL REVISION August 2012 Revision A (Windows and UNIX): Manual for release starting with v6.0.
  • 10. Page 4 of 4 CHAPTER SUMMARY Chapter One: INTRODUCTION This chapter contains an introduction to the platform, device and the media supported; it also contains a brief overview of QStar products and their features. Chapter Two: QSTAR COMPONENTS This chapter describes the main components of QStar Software and the terminology used in later sections of the manual. These descriptions will help the user gain an understanding of the product, to ensure that the maximum performance, functionality and organization for the storage solution are obtained. Chapter Three: INSTALLING AND CONFIGURING QSTAR SOFTWARE The first section of this chapter describes how to load the QStar Software onto the system and how to connect the hardware devices. The second section describes the installation of the QStar Software and the configuration of the storage device(s). The third section describes how to generate and install license keys. There is also a section to aid in upgrading from earlier versions of the QStar Software. Chapter Four: LIBRARY MANAGEMENT This chapter describes how to manage the library and its components including the media and drives within the library. Also included are steps to gather library statistics and tune the library for optimum performance. Chapter Five: THE VOLUME LIBRARIAN This chapter describes the use of the Volume Librarian database and how it handles the media. There are sections on how media is handled both in and out of the library as well as creating and managing Integral Volume sets. Chapter Six: MIGRATION MANAGER This chapter describes how to set-up the cache for an Integral Volume set and how to configure it for the best performance. There is also a description of how the cache works. Chapter Seven: MEDIA CONFIGURATIONS This chapter describes how to create the Integral Volume set configuration for all type of media supported by QStar Software. Included are walk through examples showing how each can be achieved. Chapter Eight: DISASTER RECOVERY This chapter covers some common hardware problems and how to recover from them. Chapter Nine: COMMAND REFERENCE This chapter covers all of the QStar commands available on the UNIX/Windows platforms, including explanations and command options.
  • 11. Page 1 of 20 Depending on the product purchased, QStar Software will install different components on the system. Before you install and configure the Software, you should be comfortable with QStar’s terminology and concepts. Please take the time to read all sections, as this will ensure that the maximum performance, functionality and organization for the storage solution are obtained. This section identifies key terminology and concepts that are vital for you to understand. Also included are the descriptions of QStar modules and conceptual and practical definitions for creating the configuration. GENERAL COMPONENTS ....................................................................................3 API Interface ................................................................................................3 Command Line Utilities...................................................................................3 QStar Administration Interface ........................................................................3 QStar Administration Interface Changes ...........................................................3 Privileged Users (UNIX Option)........................................................................3 Online Help Manual Pages...............................................................................3 Remote Administration...................................................................................4 VL Scheduler ................................................................................................4 No Media Option............................................................................................4 DEVICE MANAGER COMPONENTS........................................................................5 QStar “SCSI” Manager ...................................................................................5 Library Manager ............................................................................................5 View Store....................................................................................................5 Library Statistics ...........................................................................................5 MEDIA MANAGER COMPONENTS .........................................................................6 QStar “Volume Librarian” Database..................................................................6 Bar Code Support ..........................................................................................6 Online Media Management ..............................................................................6 Dated Mount.................................................................................................6 Offline Media Management..............................................................................6 Data Compaction...........................................................................................6 Simulated Media Libraries...............................................................................7 VL Copy Media ..............................................................................................7 VL Cross Copy Mirror Media ............................................................................7 VL Copy Using Publisher Devices......................................................................7 MIGRATION MANAGER COMPONENTS..................................................................8 Migration Manager.........................................................................................8 Cache ..........................................................................................................8 Cache Enhancements .....................................................................................8 File Migration ................................................................................................8 Transaction Logging Cache .............................................................................8 Read Only Grace Period..................................................................................8 Retention Period............................................................................................9 Write Once and Deny Rename .........................................................................9 NFS Mount ...................................................................................................9 Virtual Disk...................................................................................................9
  • 12. Page 2 of 20 DIAGNOSTIC COMPONENTS............................................................................. 10 Syslog View Pane or QStar‘s Syslog File.......................................................... 10 SCSI Log View Pane or Qscsi_log Command .................................................... 10 Console View Pane or Vlconsole Command ...................................................... 10 Mail Notification .......................................................................................... 10 FILE SYSTEMS................................................................................................ 11 SDF (Standard Data Format)......................................................................... 11 UDF (Universal Disk Format) ......................................................................... 12 UVFS - Support for the Plasmon File Systems .................................................. 13 AAFS - Support for the Archive Appliance Plasmon File System .......................... 13 TDO (Tape and Disk Object File System)......................................................... 13 LTFS (Linear Tape File System) ..................................................................... 14 MEDIA ORGANIZATION ................................................................................... 15 MAJOR SOFTWARE ENHANCENENT IN VERSION 5.1 ............................................ 16 MAJOR SOFTWARE ENHANCENENT IN VERSION 6.0 ............................................ 18
  • 13. Page 3 of 20 GENERAL COMPONENTS The general components of the QStar Software are as follows: API Interface QStar operates seamlessly with all major UNIX and Windows Platforms with full Application Programming Interface (API) support. A separate API Interface manual is available upon request from QStar. Command Line Utilities The QStar Software on the Windows platforms creates the c:qstarbin directory and on the UNIX platforms creates the /opt/QStar/bin and the /opt/QStar/etc directories. In these directories QStar places all the user and Administrator commands. The QStar Software for Windows platforms allows the System Administrator to run all the QStar commands from the Windows DOS prompt. With this added functionality, System Administrators will have greater flexibility in managing and integrating the QStar Software. Adding the /opt/QStar/bin and /opt/QStar/etc paths to the Administrator's default execute path (PATH environment variable) on the UNIX platforms will make all QStar commands accessible to the System Administrator. QStar Administration Interface The QStar Administration Interface (Windows) allows configuring, and viewing of the underlying structure of the QStar Server, providing a single interface for management of the QStar Software and devices. Through the QStar Graphical User Interface (GUI) (Windows only) management of the hardware (configuration/ trouble shooting, and statistics), media (online/offline databases), file systems, mounting and unmounting of the Integral Volume sets, migration behavior, logging, and email notification alerts are all possible. A web-based GUI is available for Linux and Mac Administrators. QStar Administration Interface Changes The QStar Administration Interface (Windows) has been completely redesigned; the new GUI is resizable and consists of a window divided into two panes. The navigation pane is on the left side and contains the categories tree. The categories tree shows the items that are available to manage the QStar Software. The view pane is on the right side and shows information and functions of each item. In addition, the GUI now supports Multinational languages. The current languages supported are English, Japanese, Russian, German, Chinese, Dutch and Italian. Privileged Users (UNIX Option) Usually only the System Administrator can run QStar commands because of their administrative capabilities. QStar creates a special option that, if required, allows non-root users to run QStar commands. For more detailed information, please refer to Chapter 3 - Installing and Configuring QStar Software in this manual. Online Help Manual Pages The QStar Software for the Windows platforms contains context-sensitive help links that provide instructional help and examples. The System Administrator can access the QStar Manual by selecting the bookshelf icon on the far right of the QStar Administration Interface. Alternatively, the manual can be reached from the Start Button as well. The QStar Software for the UNIX platforms creates the /opt/QStar/man directory. In this directory, QStar places all of the Manual pages for the QStar commands. These pages explain the syntax and show some examples of the QStar commands to help the System Administrator. Adding this path to the Administrator's default Manual pages path (MANPATH environment variable) will make all QStar Man pages accessible to the System Administrator.
  • 14. Page 4 of 20 Remote Administration The QStar Administration Interface (Windows) can be used with any 2000/2003/2008/XP/Vista client machine to remote administer, configure and manage any other server (Windows or UNIX) that has the QStar software installed on it located on the network. The System Administrator simply copies the admin.exe file from c:qstarbin 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:qstarbin and its contents to the c:qstarbin of the remote client machine. VL Scheduler The QStar Software contains an event scheduler for scheduling certain processes. Scheduling of events allows the Software to be used to its full potential, notifying the System Administrator of low availability of media and delaying system intensive processes to be run at off peak times. The VL Scheduler can be used to initiate archiving from caches independently on a per Integral Volume basis and run batch or single media erases as well as Copy Media requests. It can also be used to schedule more time consuming tasks out of peak hours such as data Compaction on Integral Volume sets and bulk recording of CD/DVD-R media. No Media Option The QStar Software can be configured to create an Integral Volume set with No Media, this allows data to be written to a cache as normal, but the data will not be archived and therefore not secured. A library or standalone drive can be added at a later date, and then the media can be added to the Integral Volume set and the data synchronized from the cache to the media.
  • 15. Page 5 of 20 DEVICE MANAGER COMPONENTS The term “device” refers to hardware such as standalone drives and library subsystems. QStar Software can manage one or many standalone drives and library devices on the same system. These devices can use Optical, Tape, or RDX media. To manage the device(s), QStar Software has three components: QStar “SCSI” Manager The “QSCSI” commands are the low-level SCSI drivers and are used to provide an interface for performing any direct SCSI device diagnostics, independent of the QStar drivers. These commands allow viewing of device profiles, inquiry strings, capacities of media, defined vendors, sense log information and other data from devices. Library Manager The JB driver, through the “jbcmd or jb(UNIX)” commands, manages the storage library called historically jukebox. The JB module performs various operations with the library and its elements (shelves, drives, carriers, and mailslots). The commands can move media between elements as follows: jbcmd load (jbload) move a medium from the shelf to the drive jbcmd unload (jbunload) move a medium from the drive back to the shelf jbcmd flip (jbflip) invert a medium in the drive jbcmd export (jbexport) move a medium from the shelf or drive to the mailslot jbcmd import (jbimport) move a medium from the mailslot to the shelf. An application can control the online/offline status of the elements as well as the library time control parameters through API calls. View Store Library management software provides a complete application transparent interface to libraries, scheduling the insertion of particular media into a drive, based on demand for that volume. Library Statistics QStar Software provides statistics for the elements within the library. These statistics allow the System Administrator to monitor for potential problems with the media and drives within the library. This allows problems to be rectified before they become too serious. There are also statistics for media loads per shelf/surface and per drive. If the library is full and media needs to be taken offline, these statistics will identify the less frequently accessed media. Additionally the statistics show the number of recovered errors per surface/drive/carrier, the number of occasions when a shelf/drive has been marked as ‘bad’ and the number of primary and secondary defect blocks on the DVD-RAM and Optical (MO/UDO/PDD/Blu-ray) surface. The Statistics view pane or the jbcmd statistics (jbstatistics) command line allows library statistic information to be printed or cleared.
  • 16. Page 6 of 20 MEDIA MANAGER COMPONENTS QStar “Volume Librarian” Database The “VLcmd or VL )” commands allow the system administrator to configure the QStar database named Volume Librarian (VL). QStar’s Volume Librarian module is responsible for managing all archival media known to QStar, referred to as the media library. The Volume Librarian knows the location (physical and logical) and status of every archival medium, whether available online in a library or offline in a storage facility. Its capabilities eliminate any errors that may occur during manual volume management, while increasing productivity and performance. The QStar Volume Librarian performs many different tasks including erasing, media initialization, export/import from the storage devices, automatic electronic labeling, partitioning of the library, dynamic media allocation and compaction. Bar Code Support QStar supports most major manufacturer’s implementation of Bar Code for media management, this allows improved handling for offline media and disaster recovery. In large-scale installations, media can be scanned in seconds for fast and efficient media tracking. Media can be tracked by a user defined label, or its Bar Code information, whether inside or outside the library. Online Media Management For online media, the QStar Software automatically manages all storage media allocation and movement without operator intervention. Dated Mount Dated Mount has the ability to mount an Integral Volume set, as read only, to a previous date and time. This feature is specific to the SDF / TDO file system. Dated Mount allows multiple simultaneous mounts on different dates and times, while the production mount continues to satisfy user requests. This allows the System Administrator to recover a previous version of a file or recover a file that has been deleted from the file system. Please refer to the Chapter 6 - The Migration Manager for more details. Offline Media Management The offline media management provides virtually unlimited storage capacity by managing media outside of the storage device. For requests that require offline archival media access, the operator is prompted to retrieve the storage media from its storage location and insert it into the QStar configured device. Data Compaction The Data Compaction utility is available for use with the SDF / TDO file systems, and is used for migrating live data from one piece of media to the current write surface of the Integral Volume set. The Data Compaction feature lets the operator fully reclaim media blocks after modifying or removing files on rewritable Optical media or Tape. This feature is managed under the control of the VL database. This feature is available on all Integral Volume sets, or just selected ones. Once a piece of media has been compacted and erased, the System Administrator has the option of adding the erased media to the same Integral Volume set or removing it from the Integral Volume set entirely.
  • 17. Page 7 of 20 Simulated Media Libraries The QStar Software can create Simulated Libraries. The Simulated Library configuration extends the ability of the QStar Software to mount an Integral Volume set utilizing magnetic disk space (RAID, Centera, SAN or hard drive) as simulated media. This configuration allows the use of physical disk space available on a hard drive to be used as media for an Integral Volume set. The hard drive may be partitioned into simulated virtual shelves and allows full use of import and export commands. The media may be manually configured to any size, or pre-configured media types such as UDO or Blu-ray. Integral Volume sets can then be created with any media configuration QStar supports, such as SDF / TDO. The Simulated Libraries configuration may be useful for demonstrating or integration testing with the QStar product or API when a library is not available. It is possible to configure a conventional library, with media such as Tape or Optical in conjunction with a Simulated Library and mirror the data between the two devices. For this, configure the Simulated Library media must be the same capacity and type as the media in the conventional library containing real media, then using the Data Director product and QStar’s SDF / TDO file system, mirror the data between the Simulated Media Library (on hard disk) and an Optical or Tape Library. This configuration allows real time mirroring between a hard disk and an optical or tape library. VL Copy Media The QStar Software can manually or automatically execute a duplication process of the media that has been completely written. With a properly configured Integral Volume set, the Automatic Copy Media command will run every time the Integral Volume set reaches the point of dynamically allocating another piece of media to the Integral Volume set. With the VL Copy Media the source and destination media may be selected and copied at the System Administrators convenience. The copied media is an exact duplicate of the original media in the Integral Volume set. If a media is damaged, the copied media can be used to replace the damaged media. For more information on how to enable the VL Copy Media, please refer to Chapter 5 - The Volume Librarian in this manual. VL Cross Copy Mirror Media The Copy Media supports copy of the media within the mirror configuration (SDF / TDO file system). This new feature will allow the System Administrator to recreate any lost or damaged primary or secondary mirror media simply by using the Copy Media utility or vlcmd copy (vlcopy) command. The copied media is identical to the original with the exception of the Set Identifier written at the beginning of the media, allowing it to be added to the mirror set. VL Copy Using Publisher Devices QStar Software is capable of interacting with different types of publisher/duplicator devices. In the Windows and Linux versions a new QStar daemon will start if the software is configured to work with a publisher device. The daemon, through the publisher’s proprietary SDK library, is responsible for the communication between QStar and the publisher device. Using a simulated DVD or BD library with a spanning UDF Integral Volume set, it is possible to select the option of “Copy Media using Publisher”. Once the virtual UDF media is full, it is automatically sent to the publisher to create single or multiple copies of the media for offline storage.
  • 18. Page 8 of 20 MIGRATION MANAGER COMPONENTS Migration Manager Migration is the movement of data between the magnetic disk cache partition and the archival media. The Migration Manager was designed to provide a view of a collection of diverse types of storage media. This includes magnetic disks, RAID, Optical, CD, DVD, Blu-ray, RDX, Tape drives and libraries. The job of the Migration Manager is to combine all of these technologies into a Virtual File System called an Integral Volume set. An Integral Volume set looks and feels to the user like a standard magnetic disk. This means that all standard applications, including network-based applications, can work with the Integral Volume set without modification and in the same manner that they would work with a normal magnetic disk. Cache QStar Software uses server magnetic disk to temporarily store files to improve system performance. Caching provides the ability to place frequently accessed files on magnetic disk or RAID for quicker access. Different configurations of caching and cache logic provide instant access to the most recent and most active data without delays or a need for special commands. Cache Enhancements The cache (Magnetic Cache File System) has been completely redesigned. The format of the cache now allows movement of the cache files between different operating systems and the cache formatter is no longer needed. The limitation of the cache per Integral Volume set size of 500 GB has been removed and better system resource utilization has been made. Multi threading has been enhanced, increasing the performance of Read/Write operations. A new mmcmd admin (mmadmin) command allows the ability to easily save all primary pages from the cache in case of disaster recovery. File Migration File Migration is defined as the movement of data from and to the disk cache from and to an archive storage medium. This includes archiving files to the secondary storage media and replicating files back to the magnetic cache to service read requests. In the case of archiving data in an Integral Volume set from the cache, there are several archiving policies that can be utilized to maximize the efficiency of the archiving process. Automatic data migration in the Integral Volume set, or demand archiving forces an archiving cycle when a pre-arranged watermark, High Primary Capacity, is reached. Archiving can also be started by the System Administrator at any given time or scheduled in a timed interval using the VL Scheduler. Transaction Logging Cache The magnetic cache is implemented using transaction-logging technology. This ensures the highest level of reliability in case of a system failure. Recovery of the cache requires the flushing of the transaction log. This takes place automatically at the next mount of the Integral Volume set after an unclean unmount. Read Only Grace Period The QStar Software has a feature to allow data to be stored for a Grace Period before it is set to read only. A file may be modified, providing the user has sufficient privilege, until the Grace Period has expired, it is then marked as read only, this feature goes further than the standard UNIX, or Windows read only flag, as even the System Administrator cannot remove the read only flag for files, the only way to overcome this, is to remove the Grace Period option. Enabling this feature provides a WORM file system, even with rewritable media ideal for true archiving applications. This feature is configurable on an Integral Volume set basis and can be set by seconds, minutes, hours, days and years. Please refer to the Chapter 6 - The Migration Manager for more details.
  • 19. Page 9 of 20 Retention Period The Retention Period feature can be used alone or in conjunction with the Grace Period feature. Both Grace Period and Retention Period start from the last modification time. The Retention period specifies a file can be removed only once the Retention period has expired. The benefit to this feature is the ability to lock a file to read only status for the time the file is required to remain available within corporate guidelines. This feature goes further than the standard UNIX, or Windows read only flag, as even the System Administrator cannot remove the read only flag for files under Retention Period management. Enabling this feature provides a WORM file system, even with rewritable media ideal for corporate data archiving compliance requirement. Once a file has reached a point in time after the Retention Period, the file may then be modified or deleted from the file system. If both the Retention and Grace Periods are specified, a file can only be modified or deleted either before the Grace Period begins or after the Retention Period expires. This feature is configurable on an Integral Volume set basis and can be set by seconds, minutes, hours, days and years. Please refer to the vlcmd cache (vlcache) command in Chapter 9 - Command Reference for more details. Write Once and Deny Rename The Write Once feature provides a WORM file system, even with rewritable media, which is ideal for corporate data archiving compliance requirement. Working differently from Grace Period, once a file is written in the file system; the overwrite, remove and set size operations are prohibited. A file can only be appended and renamed. This option will be ignored if is used in conjunction with Grace Period. If the Deny Rename option is specified with the Write Once option, the renaming operation is also prohibited. NFS Mount This option allows mounting a QStar file system from a Windows platform to a UNIX platform via NFS. With this option, there is no third party software required to mount the QStar file system from Windows to a UNIX platform. With this added functionality, System Administrators will have greater flexibility in managing and integrating the QStar Software. Please refer to the Chapter 6 - The Migration Manager for more details. Virtual Disk QStar Software consolidates all of the physical mass storage subsystems on a network-magnetic disk, Optical, CD-ROM, DVD- ROM, DVD-RAM or Tape - into a single, hierarchically managed resource, or Virtual Disk, treated as one logical entity. Using QStar’s caching technology, the most recently used data is available on the magnetic disk, providing fast access for users. Less recently used data is stored on archival media, via the Volume Librarian (VL) and is automatically moved to the magnetic disk if a user accesses it. This is a function of the Migration Manager. The moving of data between the magnetic disk and the archival media is transparent to end-users. QStar Software’s automatic storage management provides the benefit of virtually unlimited storage capacity without sacrificing access time to critical data.
  • 20. Page 10 of 20 DIAGNOSTIC COMPONENTS QStar Software provides different diagnostic components that can help the System Administrator monitor events, warnings and errors within the system. Syslog View Pane or QStar‘s Syslog File In UNIX platform the QStar Software redirects any warning messages and main errors to the system console window. In addition, the QStar Software places its own log file called syslog into the /opt/QStar/log directory. In the Windows platform the QStar’s syslog file is placed into the c:qstarlog 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:qstarlog (Windows) or /opt/QStar/log (UNIX) directory where it will sequentially collect all the SCSI commands sent to the devices as well as the response back from the SCSI devices. Console View Pane or Vlconsole Command The Console view pane or the vlcmd console (vlconsole) command prints a list of requests for manual assistance. The System Administrator can cancel a particular request, or remove requests from the list upon completion. Requests might include Integral Volume sets that need another piece of media added to the library or for offline media to be reinserted into the storage device to satisfy a read request. E-Mail Notification The System Administrator can receive e-mail notification about abnormal events in the QStar software. An abnormal event can be, for example, a drive/library failure, an unrecoverable write error, a request for additional medium (no more space in the Integral Volume set), a request for medium that is currently offline. For more detailed information, please refer to Chapter 3 - Installing and Configuring QStar Software in this manual.
  • 21. Page 11 of 20 FILE SYSTEMS A File System is an interface for saving and retrieving files on storage media. The file system controls all aspects of media management, including directory/file structures, data layout, and data transfers. The file system allows data to be written out to the storage device in the file format that is acceptable to the application. QStar Software supports different types of standard file systems such as UFS, NTFS, FAT, UDF, LTFS and ISO. In addition, QStar Software supports two file system types that have data layouts suitable to the media QStar controls. These appear as standard file systems and give optimal performance for the storage and retrieval of data. QStar media format manager stores information about the data on the surface of the media, thus providing the template for the data written to the archival media. All archival media sets are self-contained, with file directory information, data, and indexes on the same Optical media, DVD-RAM or Tape. The volume format is optimized to ensure maximum performance and transportability between Optical, DVD-RAM or Tape libraries and file servers. The benefits of QStar formatted media include: • Transportability. - Media format easily moves media from one host system to another, regardless of the manufacturer. Thus, QStar’s media format manager protects the company’s investment in current hardware and allows access to critical data using other manufacturers’ products. • Flexibility. - Media format describes the contents of a single archival media allowing it to be used as part of a logical group, or media set. As part of a set, file and directory information is not restricted to a single piece of media; it may span several platters or tapes, giving contiguous space for large files. • Disaster recovery. - Making all archival media self-contained provides the means for disaster prevention and recovery. Any magnetic disk cache in the storage hierarchy can be completely rebuilt from the archival media, thus preventing catastrophic data loss. QStar stores file databases on a stacking file system. The first time a file is written to storage, it creates a baseline copy of the file. Subsequent changes to the file only cover the portions of the file that have been modified. The original file and each subsequent change are simply overlaid by more recent file segments. This method provides true incremental changes to the file without consuming excessive storage space. Similarly, changes made to directories are also stacked. Therefore, if a user removes a file, the directory is simply rewritten without the name of the deleted file. The file, however, still exists physically on the media. The QStar file systems are as follows: SDF (Standard Data Format) This file system can be used for (MO/UDO/PDD/Blu-Ray) Optical and DVD-RAM devices to manage data storage and retrieval on WORM and rewriteable (MO/UDO/PDD/ Blu-Ray) Optical and DVD-RAM media. SDF is available on both UNIX and Windows platforms. Files are stored contiguously from the beginning to the end of each piece of media, with single-seek read and write access. This file system also supports SCSI Tape devices, specifically, Digital Linear Tape (DLT), SDLT, AIT, SAIT and LTO. The files are stored contiguously from the beginning to the end of each tape. The SDF file system is best suited for applications that will generate relatively small sized files.
  • 22. Page 12 of 20 Shredding support for UDO Compliance WORM media and Rewritable Optical media has been added. The support is available with ASM and Data Director (Mirroring) configurations. A new approach of saving the SDF database has been created, allowing the SDF database to be saved to a dedicated, separate media. The System Administrator can still use the old approach, which stores the SDF database to the beginning of each media. In addition the SDF database can be stored on Hard Disk as the primary location or as a mirror location if the primary location is the media. The database save procedure is triggered during rollover of media or can be initiated per GB of data written in the file system. This new approach allows the user to have two different threads in the SDF migrator, one for writing data and one for saving the database in two different media, removing the delay of archiving of data during the saving of the database. This feature is available also on Mirroring configurations where two different Hot Sync procedures have been developed. One called “Off Line Asynchronous Hot Sync” that is used to synchronize Database Media and all non current write surfaces and one called “On Line Synchronous Hot Sync” that is used to synchronize the current write surface, this allows Hot Sync to run in parallel with read/write operations. UDF (Universal Disk Format) This file system can be used to manage data storage and retrieval on WORM and rewriteable (MO/UDO/PDD/Blu-Ray) Optical or DVD media. UDF is available on both UNIX and Windows platforms. Files are stored contiguously from the beginning to the end of each piece of media, with single-seek read and write access. QStar Software supports UDF Version 1.2 in read only mode and fully supports UDF Version 1.50, 2.00 and 2.01. UDF file system supports the three following Interchange Levels: • Single-volume: Single surface file system for standalone drive • Automount: Single surface file system where each surface is seen within a single volume as a separate directory • Spanning: All media are aggregate as large file system The following new UDF Versions and file system have been supported: • Version 2.5 • Version 2.6 • Plasmon UDF • ISO 9660 File System Note: CD File System (ISO 9660 File System) has been removed and the support for the ISO 9660 standard with Rock Ridge and Microsoft extensions has been incorporated in the UDF file system. ISO and UDF media can coexist in the same file system using Automout Intechange Level. The UDF file system also supports the shredding operation offered with UDO Compliance WORM media. A new version of the UDF spanning database has been introduced for spanning configurations that also contain directory entries. This modification requires less access to the media when a user is browsing the file system and provides a faster mount procedure in the case of rebuilding of the cache and media databases. The floc command is now supported on UDF and can be used to list the files on an individual media.
  • 23. Page 13 of 20 UVFS - Support for the Plasmon File Systems This file system supports WORM and rewriteable (MO/UDO) Optical, DVD-ROM and DVD-RAM media on Linux and Windows platforms. Using the UVFS file system QStar supports, Read Only access to the following three Plasmon file systems: • PFS - A simplified version of UDF, based on an older UDF implementation by HP • AFS-1 - Archive File System, specifically developed for WORM • AFS-2 - Improved version on AFS-1, optimized for speed and media usage The UVFS file system supports the following three Interchange Levels: • Single-volume: Single surface file system for standalone drives • Automount: Single surface file system where each surface has a different label and it is seen within a single volume as a separate directory • Spanning: All media are aggregated as a large file system if the label name is identical on each media AAFS - Support for the Archive Appliance Plasmon File System This file system supports WORM and rewriteable (UDO) Optical, on Linux and Windows platforms. Using the AAFS file system QStar supports, Read Only access to the Archive Appliance Plasmon File System. TDO (Tape and Disk Object File System) The TDO migrator (introduced in version 6.0) is a high performance file system created to optimize the read/write operations for tape and optical disks. TDO is available on both UNIX and Windows platforms. Files are stored contiguously from the beginning to the end of each piece of media, with single-seek read and write access. The design of TDO has removed the majority of the bottlenecks that are inherent with other file systems for these types of media. TDO has been created in such a way that it supports SDF media in read-only mode and writes all new data to the TDO file system. This allows to convert an SDF Integral Volume set to an TDO Integral Volume set. The read operation (for TDO and SDF) is multi-thread, which allows different read requests to be satisfied at the same time. The TDO file system is best suited for applications that will generate relatively small or very large sized files. The support is available with ASM and Data Director (Mirroring) configurations.
  • 24. Page 14 of 20 LTFS (Linear Tape File System) This file system can be used to manage data storage and retrieval on Tape media. LTFS is available on both UNIX and Windows platforms. Files are stored contiguously from the beginning to the end of each piece of media, with single-seek read and write access. QStar Software fully supports LTFS Version 2.0, allowing media to be exported and read in stand-alone drives using LTFS drivers provided by various drive manufacturers. LTFS media created in stand-alone drives can also be imported into the QStar controlled tape library. LTFS file system supports the three following Interchange Levels: • Direct-single-volume: Single media file system for standalone drive or library without QStar Magnetic Cache File System (MCFS). This Interchange Level provides direct access to the LTFS tape • Single-volume: Single media file system for standalone drive • Automount: Single media file system where each media is seen within a single volume as a separate directory • Spanning: All media are automatically aggregated as large file system
  • 25. Page 15 of 20 MEDIA ORGANIZATION The number of storage media in a system can run into thousands. System configurations can range in size from a 1.3 GB personal archive systems to multi-petabyte storage solutions. QStar can configure the library(ies) to be seen as one or multiple Virtual Disks. This partitioning allows a multi-media library to be logically divided so that the library can appear as multiple standard virtual hard drives allocated to different applications. In addition, partitioning allows the user to predetermine where and when files are written. This allows data to be written to a specific set of media, thereby simplifying backup and optimizing performance. Creating ten partitions, each with one piece of media, is comparable to creating a single partition with ten pieces of media, each with its own directory. The main difference between these implementations is data organization. QStar offers configuration, media paths, and write paths in the virtual file system to provide the most flexible data organization available. When deciding between multiple partitions and/or media paths, consider the objective of the entire storage solution. QStar Software allows for both standalone drives and libraries in the following configuration of data set: Integral Volume (I.V.) Set Configuration Use the “vlcmd or vl (UNIX)” commands to create and manage an Optical, DVD, Blu-ray, Tape media set or Structured Storage Device (Centera, HCP, Cleversafe, Amplidata, OSM) as an Integral Volume set. This configuration requires a CACHE that manages the migration of the data between the storage media and the Hard Disk. This configuration is available with all file systems. The media used determines the file system needed. Note: For more detailed information please, refer to Chapter 7 - Media Configurations in this manual.
  • 26. Page 16 of 20 MAJOR SOFTWARE ENHANCENENT IN VERSION 5.1 Hitachi HCP Migrator (HCP) Allows data to be migrated from the cache file system (CFS) to the Hitachi HCP device. Specific features were introduced to support this device The file can be written in compatibility mode or as an extent Rename operation is implemented as a read/delete/write operation Support for retention periods in HCP Curl timeout raised to 8 min Without retention, extent is rewritten (does not create a new version) All communication and read/write operations with HCP uses the http interface exclusively Initial tenant support AAFS Migrator (Archive Appliance Plasmon File System) Implemented the new migrator, which allows reading of media written with the Archive Appliance file system from Plasmon. The AAFS migrator accesses the AA media in read only mode Implemented all the commands to use this file system with the Integral Volume set Added offline medium support Local Mount (Windows): QStar ASM can be exported by using a NetBIOS name (mapped network drive) as in previous versions. In addition the Integral Volume can now be presented as a local drive letter. This feature allows the sharing of the Integral Volume set using the standard share tools provided by Windows Cluster Migrator The Cluster Migrator allows two (2) different Integral Volumes set to be added, using the same cache and mounts them using the same mount point. The first Integral Volume set added is always read only while the second Integral Volume set added is read and write; the file system directories are aggregated at the root level. The cluster migrator does not allow multiple directories with the same name at the root level. If this happens, only the read- write directory will be displayed. The Cluster Migrator’s features, allow for example, mounting an AAFS file system in Read Only (RO) and a QStar file system in Read Write (RW), giving the user the ability to have two file systems mounted but clustered together and accessible as one Access Control List (ACL’s) The introduction of CBFS as the Windows File System Interface (FSI) allows the mounting of the QStar file system as a local drive; it also allows the system administrator to store all ACL’s into the QStar Cache and the media file systems such as SDF or UDF SCSI Subsystem Major overhaul to the QStar SCSI subsystem to add support for USB, iSCSI, SATA, Parallel SCSI, Fibre and SAS devices. Most of the items listed will change their addresses when the system is restarted; the primary focus of the overhaul was to be able to regain control of these items without the user reconfiguring the devices as in the previous versions. Now the Software will automatically reconfigure the device for the user on QStar server restart Added support for slow storage library support Mixed LTO tape drives and media support; allows distinguishing between LTO-1 through LTO-5 and properly manage drives and media ensuring that the correct media will be placed into the correct drive BluSafe: Added Serial Port detection and other Mac Specific Serial Services BluSafe direct support Windows and Mac
  • 27. Page 17 of 20 Copy Disk Utility - Multiple Incremental Copy Implemented Multiple Incremental Copy (MiC) for SDF and UDF file systems. This new feature allows two or more copies of the media to be created incrementally Administration GUI (Windows) Updated Russian and Italian localizations Added support of Chinese simplified localization Added support of Dutch localization WEB GUI Linux Apple (MAC) Added localization support MAC OSX (10.5) with CLI and Web GUI management interface Added checks for different Mac versions, updated Darwin; Definitions for proper library locations Porting for OSX (10.6) Generic job scheduler Allows configuring any event in the schedule i.e., TMT intervals Added option for real and simulated storage libraries in the same Integral Volume set File pre-fetch support in asynchronous mode Allows pre-fetching of data with real time access to the pre-fetched data, meanwhile continuing to allow full access to the file system Mirroring SDF File System (Data Director) Expanded vlstartmirr command in order to compare and generate audit report between primary and mirror media. In addition can be used to synchronize primary/mirror media
  • 28. Page 18 of 20 MAJOR SOFTWARE ENHANCENENT IN VERSION 6.0 Magnetic Cache File System (MCFS) Possibility to calculate checksum of the file on fly and store such information in the stream of the file in the cache and in the back-end (archive) storage Replication Migrator (RPL) Allows the replication of data between different types of media and storage at the file system level. This is accomplished by inserting itself between the cache file system (CFS) and up to four different migrators, such as SDF, UDF, TDO, LTFS, Object Storage and GFS. The replication migrator includes a re-synchronization feature in case of failure of one of the replicas Local Mount (Windows): QStar ASM cannot be exported by using a NetBIOS name (mapped network drive) as in previous versions. The option to use NetBIOS can be enabled only upon request with a special procedure followed by QStar Support personnel. Starting from this version the Integral Volume can be presented only as a local drive letter. This feature allows the sharing of the Integral Volume set using the standard share tools provided by Windows QStar Structured Storage Devices (QSSD) Allows support for HCP, QStar OSM (Object Storage Manager), Amplidata, Cleversafe and GFS or non-SCSI device subsystems Implemented qssddefine, qssdrefresh, qssdlist, qssdrename and qssddel commands Hitachi HCP Migrator (HCP) Provides CIFS / NFS connection Full tenant support Amplidata Migrator (Ampl) Provides CIFS / NFS connection Cleversafe Migrator (Cloud) Provides CIFS / NFS connection Generic File System (GFS) GFS is any file system that is available on the server i.e., NTFS, EXT3, EXT4 and Solaris. The GFS migrator allows migrating data to any of the generic file systems on the server. This is achieved by creating an Integral Volume set and assigning one of the generic file systems as the “media” for the Integral Volume set. The most common application of GFS would be to use it with the Replication Migrator (RPL) Tape and Disk Object file system and Migrator (TDO) The TDO migrator is a high performance file system created to optimize the read/write operations for tape and optical disks. The design of TDO has removed the majority of the bottlenecks that are inherent with other file systems for these types of media. TDO has been created in such a way that it supports SDF media in read-only mode and writes all new data to the TDO file system The read operation (for TDO and SDF) is made using a different thread, which allows different read requests to be satisfied at the same time Added vlcopy and vlcmp commands to copy and compare TDO media Created SDF to TDO database conversion Added sync statistics Added support for stat-fs
  • 29. Page 19 of 20 TDO Mirroring Extends the functionality of TDO to provide mirrored writes (if resources are available) Provide same functionality as in previous SDF implementation, to mirror data between TDO media either using two drives in the same library or between two libraries. Extended the previous mirror limit of two pieces of media in the mirror to offer a maximum of four mirrored copies. Mirrors can be between up to four drives in one library, single drives in up to four libraries or two drives in two libraries. TDO can also be used to mirror data between real media based libraries and simulated media on disk Linear Tape File System and Migrator (LTFS) Linear Tape File System (LTFS) refers to both the format of data recorded on magnetic tape media and the implementation of specific software that uses this data format to provide a file system interface to data stored on magnetic tape. The Linear Tape File System format is a self-describing tape format developed by IBM to address tape archive requirements. The LTFS Format specification, which was adopted by the LTO Technology Provider Companies, defines the organization of data and metadata on tape - files stored in hierarchical directory structure. Data tapes written in the LTFS Format can be used independently of any external database or storage system allowing direct access to file content data and file metadata. This format makes it possible to implement software that presents a standard file system view of the data stored in the tape media. This file system view makes accessing files stored on the LTFS formatted media similar to accessing files stored on other forms of storage media such as disk or removable flash drives. The Linear Tape File System format is an open description of the layout of data-structures stored on a sequential-access media. These data-structures hold the file content data and associated file metadata. Data media, such as LTO data tape, written using this format can be exchanged between systems that understand the Linear Tape File System format. Software systems that understand the format can provide users with a file system view of the media. Software systems may alternatively understand the format only to the degree that allows the system to read data from the media, or produce a tape that can be accepted by other systems that implement the Linear Tape File System format. The file system are supported in 4 different mode described in previous FILE SYSTEM session. Object Storage Management (OSM) Migrator This migrator allows data to be migrated from a QStar cache to the OSM product from QStar. Crypto Server - Encryption support Added licensing support for crypto functions Added support for card removal/insertion control Added detached file verification functionality Added sha type verification and detailed error processing Added support for expired certificates SmartCard and Certificates pages functionality updates Added key delete functionality Added crypto backup functionality Changed signed output file protection mode Added log messages when signing files Verify that certificate is still valid before signing Added certificate extended key print Added key usage for self signed certificate creation Added support for card certificate print Added -f option for crptcmd info command to print selected certificate Added support for certificate creation Added certificate information print in XML format Time Stamp request converted to curl. Number of TS availability request hidden from GUI (as this is very customer-specific) Smart card info added to the cache Crypto stamp from crypto stream (if any) is used for signing
  • 30. Page 20 of 20 Crypto Server – Digital signature Implemented Digital Signature for UDF single volume set Check existence of a signature file before creating it Added code to support digital signature using qcrypto server Administration GUI (Windows) Updated Russian and Italian localizations Added support of Chinese simplified localization Added support of Dutch localization File pre-fetch support in asynchronous mode Allows pre-fetching of data with real time access to the pre-fetched data, meanwhile continuing to allow full access to the file system
  • 31. Page 1 of 42 This chapter describes how to get the system up and running. Installing the software is as simple as placing the QStar CD in the CD-ROM, or running the executable, if installing from a downloaded copy . The Installation program guides the System Administrator through every step of the process. Before installing the QStar Software, however, certain system components should be checked, such as the system, connection of storage devices and server configuration. This ensures that the QStar Software installation will run smoothly and minimizes the time it takes to set up the system. This chapter contains instructions on how to verify these components, as well as information on completing the setup of the QStar Software. SYSTEM REQUIREMENTS ........................................................................................................2 Software Requirements .......................................................................................................2 QStar’s Recommendation for Optimization of the System .........................................................2 The Storage Devices.........................................................................................................3 Improving the Server’s Performance...................................................................................3 Improving File System Performance....................................................................................3 Protecting Against Data Loss .............................................................................................4 Installation Considerations ................................................................................................5 Hardware and SCSI Requirements.........................................................................................6 QSTAR SOFTWARE DIRECTORIES ............................................................................................7 UPGRADING TO THE CURRENT VERSION OF QSTAR SOFTWARE...................................................8 INSTALLATION STEPS ............................................................................................................9 Diagram Installation Step: ...................................................................................................9 HARDWARE INSTALLATION AND SETUP OF DEVICES................................................................ 10 INSTALLING THE QSTAR SOFTWARE ...................................................................................... 11 SELECTING LANGUAGES....................................................................................................... 13 INSTALLING THE LICENSE KEY AND REGISTERING THE SOFTWARE............................................ 17 Demo License Key ............................................................................................................ 18 Activate the Demo License Key ........................................................................................ 18 Permanent License Key...................................................................................................... 20 Activate the Permanent License Key ................................................................................. 21 SPECIFYING THE STORAGE DEVICE CONFIGURATION............................................................... 23 Hard Drive Simulated Library Configuration .......................................................................... 28 Centera Simulated Library Configuration .............................................................................. 32 Proxy Simulated Library Configuration ................................................................................. 36 POST INSTALLATION TEST.................................................................................................... 39 QSTAR SERVER PRIORITY..................................................................................................... 40 ADDING NEW STORAGE DEVICES.......................................................................................... 41 REMOVING QSTAR SOFTWARE .............................................................................................. 42
  • 32. Page 2 of 42 SYSTEM REQUIREMENTS The host computer must have the minimum configuration described below to install the QStar products. Note: The following applications are known to cause serious problems with the QStar Software or the Libraries attached to the Server that the QStar Software is installed on. Any Enterprise Management Software, such as Open File Manager (OFM) or F.A.S.T. may cause serious problems that are configured to: 1) Query the internal drives or changer assembly of the Library 2) Query and cache the QStar Software directories, or the QStar cache directories To avoid any issues with these applications QStar recommends reconfiguring the application not to monitor or cache any portion of the QStar Software or the devices it controls. Software Requirements Listed below are the minimum system requirements for installing QStar Software on the host computer. Windows 2003/XP/Vista/2008/7 Xeon class PC (Minimum 2Ghz) Required Memory At least 4 GB Disk space for QStar Software on Hard Disk At least 100 MB Service Pack 2 Windows XP Service Pack 3 Windows 2003 SCSI/SAS host adapter supported by Windows Required Note: The storage devices should not be on the same adapter as a SCSI hard drive. QStar’s Recommendation for Optimization of the System • QStar recommends a minimum of 16 GB of RAM on Windows based platforms • Upgrading the memory as much as possible will provide faster data access • To improve processing speed, use a processor that is faster than the minimum requirement • Use a separate SCSI host adapter for the library • Additional Hard Drive space on the main NTFS volume or additional NTFS volumes will provide better cache utilization • Use fast disk storage systems (RAID with FC or SAS drives) if very fast ingestion is required Client Workstations mapping to a QStar Integral Volume set should have the following minimum configurations: • Server 2000, XP Pro, Server 2003, Vista, 7, 2008 • PC with 4 GB of RAM
  • 33. Page 3 of 42 To achieve the best possible performance from Windows based platforms and the QStar Software, the following are suggested: The Storage Devices Selecting the Appropriate Hardware to Maximize Performance One of the largest decisions to consider when setting up the QStar Software is which storage device(s) is best suited for the environment. The hardware configurations can be significantly different depending upon the storage needs of the enterprise. To determine which type of storage devices including the number of drives, number of shelves and media type will provide the best performance; a complete and thorough evaluation of the enterprise needs should be conducted. The number of users and the amount of data being accessed will determine the number of drives, shelves and type of media that will be required in the library to maintain optimum performance. Improving the Server’s Performance All of the following affect the performance of the Server the QStar Software is installed on: • The amount of available RAM • The size, speed (in RPMs and bus speed) and the number of hard drives plus RAID configuration • The number of processors and their power • The network cabling and configuration Amount of Available RAM Memory is the fastest and cheapest way to improve performance on the Server the QStar Software is installed on. Maximizing the RAM on the Server will significantly improve Windows based platforms and the QStar Software performance. Number of Machine’s Processors QStar Software can be installed on either single or multiple-processor machines. Using a multi-processor machine, the number of multiple tasks that can be performed at the same time is increased significantly. Using a multiple-processor machine for the QStar Software will greatly improve the migration performance. Improving File System Performance The following will affect the performance of the QStar file system: • High and Low Primary capacities • The total number of files per directory in the QStar file system Setting the High Primary Capacity The High Primary Capacity is set to 80% of the cache size by default. Lowering this setting can be beneficial when using a large cache or during periods of high volume transfers to the QStar file system. This will allow the data in the cache to be written to the archive media sooner, which will increase the available space in the cache for the new files.
  • 34. Page 4 of 42 Creating an efficient file system How the file system is structured will have a significant effect on its performance. The sector size of the media verses the size of the files can significantly affect space utilization on the media. The layout of the directories and the number of files in any given directory are an important consideration when designing a file system. QStar recommends no more than 3000 files per directory to maintain optimum file system performance. Expected Behaviors Because the file system that QStar usually manages is removable and a multi-surfaced file system, there are some expected behaviors that need to be addressed when creating the file system. Creating a directory structure on removable media that is extremely deep and has a small number of files and a small file size in each directory will offer poor space utilization on the media and should be avoided. Exceeding the 3000 files on removable media per directory recommendation will cause degradation of performance to the file system. This decrease in performance will manifest itself when a user tries to browse the directory and will increase with the number of files in the directory. For example, with 5000 files in a directory the impact on the user will be slight. However, with 50,000 files in a directory the impact will be more significant and could have an effect on other users trying to access the file system. In extreme situations, this decrease in performance can cause extremely slow or no access to the mount point of the QStar file system. The number of files in the directory structure will have the most impact in a disaster recovery situation or if the cache files have to be rebuilt. In this situation, the mount point may not be accessible for several hours depending on the number of files in the directory structure. If direct access to a file by an application is used, the number of files in a directory can be increased and there will be no impact on performance under these circumstances. However, it must be understood that direct access will not remove degradation of performance when browsing the directory or during a disaster recovery situation. Protecting Against Data Loss QStar copies the data out to the media during the archiving process automatically based on the High Primary Capacity (HPC) value by default. To ensure that all data in the QStar file system is protected against system failure (including hard disk failure); QStar offers several utilities to protect the data from loss or corruption. Using one or more of these utilities is highly recommended. Scheduled Archives It is recommended that the System Administrator periodically archive data without waiting for the HPC to begin archiving. A daily archive is beneficial to most users who maintain a large cache with a defaulted HPC value. Archiving can be scheduled to start automatically every day using the QStar’s VL Scheduler. Media Redundancy QStar recommends the use of media redundancy for the Integral Volume sets (i.e. Copy Media), if the data is mission-critical. Recovery time after a disaster can be significantly reduced if media redundancy is used on the QStar Integral Volume set. However, further redundancy can be achieved utilizing QStar’s Data Director product in which all information is mirrored to an Identical Integral Volume set. In the event the primary server goes down, the primary servers can be “swapped” and the secondary mirror can become the primary file server in a matter of minutes. Using Automated Copy Media to back up the Primary Media The Copy Media feature creates an identical piece of media from the primary Integral Volume set. This capability takes away the potential of data becoming unrecoverable because of a damaged media and provides for an off-site media copy.
  • 35. Page 5 of 42 Installation Considerations Before installing the QStar Software, it may be advantageous to consider the overall storage needs for the system. It is advisable to make a cache size appropriate for daily usage. Considerations for cache size are: How much new data will be archived per day? How much data will be requested from the library per day? Some issues to consider include: The total amount of files expected per directory inside of the QStar Integral Volume set, appropriate watermark levels and scheduling data archiving. Some organizations have existing file storage systems, and may have already decided upon an optimum arrangement for the file server. Sizing the Cache A general rule for an Integral Volume’s cache size is, more is better. An Integral Volume’s cache size should be selected depending upon the system’s activity and required response time. The larger the Integral Volume cache, the faster the system performance, because there is a greater chance that the files being requested are already in the cache. For systems with large volumes of data, the cache should be sized to accommodate an entire day’s processing. This allows the users to work at full speed during the day, with the QStar Software performing time-costly migration at night. Each Integral Volume set must be sized separately. Calculating overhead space in addition to cache size will help determine the hardware requirements for the QStar file system. As a general rule of thumb, 1,000,000 files will require 500 Megabytes of hard drive space over and above the cache size for metadata overhead. However, this rule should only be used for an approximate estimate of required drive size.
  • 36. Page 6 of 42 Hardware and SCSI Requirements A library or standalone drive that will be connected to the host computer via the SCSI (Small Computer System Interface) bus must comply with some requirements. Every device attached to the SCSI bus must be assigned a unique SCSI ID or “address”. Please refer to the SCSI host bus adapters’ manufacturer’s recommendation for maximum cable lengths. The combined internal and external length of cables from the host computer to the end of the SCSI bus must be determined. This combined length must not be exceeded. As an example the combined length of all SCSI cables, including the integration of the QStar subsystem, must not exceed 6 meters (approximately 18 feet) for a single-ended SCSI bus. If the cable exceeds 6 meters, operational problems such as device errors or system failures could occur. QStar recommends that the length of the SCSI cable from the host computer to the library or standalone drive be no longer than 3 meters. The operating environment (noise and/or high voltage power supply) could also have an effect on the optimal cable length. Ensure that the SCSI bus is terminated correctly using an active terminator. The number of SCSI IDs that will be needed for the QStar subsystem depends on the type of device that will be installed. Be sure to keep track of which drive number in the library corresponds with each SCSI ID. Once it has been determined what devices are currently attached to the SCSI bus, then decide which available SCSI IDs will be used for the library or standalone drive. In addition, before beginning the installation, make sure the following are available: • The hardware manual for the particular library • SCSI Cable(s) and active terminator for connecting the library or standalone drive • QStar Software installation CD-ROM or downloaded software
  • 37. Page 7 of 42 QSTAR SOFTWARE DIRECTORIES QStar installs its Software by default in the c:qstar directory. In the c:qstar directory, the following files and directories will be listed: backup This directory contains internal backups of the Integral Volume set database. bin This directory contains commands for managing and controlling the QStar Software. These commands can be used at the MS-DOS command window as well as being included in Batch files. crpt This directory contains commands for managing and controlling the encryption Software. dev This directory contains internal descriptions of the QStar controlled devices. doc This directory contains the API html documentation. emg This directory contain configuration files used with OSM/TDO/Amplidata/Cleversafe Migrator. include This directory contains the QStar Include files. install This directory contains the list of configured devices as well as the classes configuration file. jb This directory contains all of the configuration and database files used by the QStar Device Manager to maintain and control the configured libraries. lib This directory contains the QStar Library files. license This directory includes the license file. log This directory contains the various QStar log files. The most important file is the syslog text file. If SCSI command logging is turned on then this directory will also contain the scsi_log text file. mcfs This directory that contains the MCFS module - Front end caching. qscsi This directory that contains the QSCSI module - Low level drivers. sdf This directory that contains the SDF module - Standard Data Format file system. svc This directory contains the QStar system services and drivers which are started automatically when the system is booted. tmp Temporary directory sometimes used by QStar Software. vl This directory maintains the list of defined sets and the state of each medium within the devices utilized for set allocation.
  • 38. Page 8 of 42 UPGRADING TO THE CURRENT VERSION OF QSTAR SOFTWARE To de-install the QStar Software in order to install an upgrade, or in preparation of moving to another host, follow the steps below: 1) Archive all data out of each Integral Volume’s cache. In the QStar Administration Interface, select Integral Volumes and next select Migration View. Select the Archive button to start the archiving. Do this for each Integral Volume set. 2) Unmount all Integral Volume sets. In the QStar Administration Interface, select Integral Volumes and next select the Volume Management. Select the Unmount button to unmount the Volumes. Do this for each Integral Volume set. Note: For safety, QStar suggests saving the information of device and Integral Volume sets database by running from dos prompt the vlcmd lsdev device_name and vlcmd lsset -va commands and redirects the output into a file. 3) Stop the QStar Server. In the QStar Administration Interface, select QStar Server for version 4.x or select Server and next Status for version 5.x or and select the Stop button. 4) Remove the QStar Software from the computer. From the Start menu, select the QStar program group and select the Uninstall QStar Software. The machine will have to be rebooted to complete the de-installation. 5) Once the machine has restarted, in a Windows Explorer window, there are two options: a) Remove the c:qstar directory and any files in the old cache directory (c:qstar is the default location for the QStar Software). This removes all database files for the Integral Volume sets and libraries configured under the previous installation. b) Do not remove c:qstar directory. This will allow the ability to restore all previous QStar database files for Integral Volume sets and libraries. The format of the cache files in version 6.x are incompatible with the cache files for all 4.x and 5.x versions, so the System Administrator will be forced to mount all Integral Volume sets with clean cache after the upgrade. For DVD libraries after the uninstall procedure remove the file c:qstarjbfilesjb_param_*. 6) To install the new release of the QStar Software see the Installation Steps section on the next page.
  • 39. INSTALLATION STEPS For a correct installation of QStar Software these steps must be followed in the order shown on the diagram below: Diagram Installation Step: Page 9 of 42
  • 40. Page 10 of 42 HARDWARE INSTALLATION AND SETUP OF DEVICES To install the storage libraries or standalone drive(s), follow these steps: 1) Shut down the system using the standard shut down procedure. 2) Reboot the system and read the list of the attached SCSI devices from boot screen and take note of the currently used SCSI target IDs. 3) Power off the system. 4) Select the appropriate SCSI target IDs from those that are available for each storage device that will be connected to the host. Set the SCSI IDs of the storage devices per the instructions in the hardware operator’s manual. Select any available number from target 0 through 6 on the SCSI bus for your storage devices. For specific hardware information, consult the hardware manual that came with the library or standalone drive. 5) Attach each device to its appropriate SCSI controller(s) and attach a terminator to the last device on each SCSI bus. Power up all peripherals. Power up the server. Verify the SCSI ID settings of the libraries or standalone drive(s) to ensure there are no conflicts with other devices on the same SCSI bus; use the SCSI Utility to verify target ID usage. The system returns a list similar to the one seen in Step #2 above. This list should now also include the inquiry strings from the newly attached devices. Confirm that all devices seen in Step #2 are still visible. If any of the devices that were previously seen are not seen now, the device may have been set to an address already in use. In this case, recheck the results from Step #2 and start again. Also, be sure to confirm all SCSI cables and terminators are securely connected. 6) During the boot process, the operating system will configure the devices attached to the system.
  • 41. Page 11 of 42 INSTALLING THE QSTAR SOFTWARE This section demonstrates the QStar Software installation program. The installation program automatically sets up all necessary product directories and files. Before installing the QStar Software, the System Administrator needs to do the following: • Disable the Microsoft Removable Storage services • Disable any Antivirus Software and if re-enabled after the installation be sure that the QStar program and QStar Integral Volume Sets cache folders are excluded from antivirus check • If QStar Software is going to be installed in any server where a different library management software vendor was previously used, it requires any existing library software/drivers be uninstalled. The System Administrator should contact the previous supplier for more specific un-installation instructions To install the QStar Software, follow these steps: 1) Begin by inserting the CD-ROM into the drive. If Autorun is configured, a welcome screen should appear as the system recognizes the disk. If Autorun is not configured, select the Start menu button. Then select Run and type D:autorun (D: being the CD-ROM drive). This process is the same for downloaded software. 2) Once the Installation menu appears, please select the Install QStar Software for Windows button to install the QStar Software. Select the Manuals and Documentations button to view the list of documents available on the CD-ROM. 3) After Choosing Install QStar Software or by manually running the Setup Program, select the appropriate language. When finished, select the OK button. 4) Select the Next button on the setup wizard windows to continue. 5) Review the license terms before installing QStar Software. Place a check in the check box to accept the terms of the agreement. The agreement must be accepted to install QStar Software. Select the Next button to continue. Otherwise select the Cancel button to exit the Setup program. 6) Personalize the Software by filling in the blanks. Select the Next button to continue. 7) Choose Install location. To install the QStar Software to the default location of C:QStar, select the Next button. To install the QStar Software to a different folder or drive letter, select the Browse button and select the desired drive letter or folder name. 8) Select the required QStar product to be installed on the system. The options are the following: • QStar ASM (Full Storage Management Product) • QStar Data Director (ASM + Mirroring Capabilities) • QStar Archive Replicator (Synchronous file replicator) After making the Software selection, select the Next button to continue, or select the Cancel button to leave the Setup program. 9) New USB and TCP/IP supported devices may conflict with RAID system.
  • 42. Figure 3.1 Device Configuration By default QStar will not check USB or TCP/IP device during the claiming procedure. If MO/UDO drive, USB device, BluSafe device and TCP/IP device will be used. Place a check mark in order to notify QStar to discover such type of device during claiming procedure. Note: For TCP/IP library the System Administrator need to insert IP Address and Port value. 10) Select the type of installation. Typical, which is the default and recommended installation, will give full functionality of the QStar Software including the API support. Custom and Compact will not install API files and API documentation. After making the selection, select the Next button to continue. Select Publisher if the Software needs to work with any publisher device. Expand Publisher check box and then select the correct model of publisher device (available only with special releases). 11) Select the location for the QStar Software icons in the Program Folder. Create a location for the QStar Software by filling in the blanks or selecting the default location. Select the Next button to continue. 12) Mark the device(s) that are going to be controlled by the QStar Software and select the OK button. In the Device Claiming Window, QStar will display all hard disks on the system this is because the operating system will report some types of optical drives as hard disk. However, QStar CANNOT control a real hard disk as a SCSI device. Configuring the QStar Software with the EMC Centera, Amplidata, HDS HCP, Cleversafe, Simulated Tape, or Simulated Disk there is no need to claim any devices. Do not mark any device(s) and select the OK button. Figure 3.2 QStar Device Claiming 13) After the installation is complete, select Reboot now and select the Finish button. Page 12 of 42
  • 43. SELECTING LANGUAGES Once the QStar Software has been installed and the system has restarted, the following is required to select the languages of the QStar Administration Interface: Starting QStar ASM Product Figure 3.3 - Start Button - QStar ASM Software Product Log on to the system as the Administrator. Go to the Start button, then Programs, then QStar ASM. Select QStar Administration Interface on LOCALHOST. Skip Figure 3.6. Or select QStar Administration Interface, and go to Figure 3.6. Starting QStar DDR Product Figure 3.4 - Start Button - QStar Data Director Software Product Log on to the system as the Administrator. Go to the Start button, then Programs, then QStar DDR. Select QStar Administration Interface on LOCALHOST. Skip Figure 3.6. Or select QStar Administration Interface, and go to Figure 3.6. Page 13 of 42
  • 44. Starting QStar Archive Replicator Product Figure 3.5 - Start Button - QStar Archive Replicator Software Product Log on to the system as the Administrator. Go to the Start button, then Programs, then QStar Archive Replicator. Select QStar Administration Interface on LOCALHOST. Skip Figure 3.6. Or select QStar Administration Interface, and go to Figure 3.6. Page 14 of 42
  • 45. In this window, expand the My Network Places and select the computer to administer. Selecting the Cancel button will open the local host. Figure 3.6 - Browse for Computer Figure 3.7 - QStar Administration Interface Once the computer is selected to administer, the QStar Administration Interface opens displaying information about QStar Version Number and the phone numbers to call for assistance or technical support. The same information can be found by selecting About QStar... under Help option. By default the language of the QStar Administration Interface is the one specified during the installation procedure. To change the language, select the Language selection in the menu bar. Once selected the QStar Administration Interface will close and open automatically with the new language. Page 15 of 42
  • 46. The new QStar Administration Interface consists of a window divided into two panes. The navigation pane in the left displays the category tree that shows the list of items that are available to manage QStar Software. The view pane in the right contains the details of the information, functions and options pertaining to these items. Figure 3.8 - QStar Administration Interface Figure 3.9 - QStar Administration Interface. License Key is activated. Selecting different items in the category tree, the information in the view pane changes. Page 16 of 42
  • 47. INSTALLING THE LICENSE KEY AND REGISTERING THE SOFTWARE Figure 3.10 - License To install the license keys, select License and call QStar Customer Support for guidance through the license key installation and to provide an activation key. License provides all the information needed to obtain a Demo or Permanent License Key from QStar Customer Support Personnel. When Accessing License for the first time an error message will be displayed notifying the System Administrator that the License Key is invalid because it is not entered yet. The license information displayed before the Software is licensed contains the following: • QStar version • Platform • Host ID The Serial Number can be found on the license card or on the back of the CD case supplied with the Software. Figure 3.11 - License Page 17 of 42
  • 48. Demo License Key Figure 3.12 - Inserting the Demo License Key Information The information that the System Administrator should provide to QStar Customer Support personnel for a Demo License key is the following: • Company: * • Department: • Contact person: • Contact email: * • Contact phone: • QStar version: 6.0 * • License Type: Demo • Platform: * • Host ID: * *: Mandatory information The above information can be inserted into the Product Registration Form available on the distribution CD-ROM and faxed to +1-850-243-4234 (USA), +39-02-45101-745 (EUROPE) or your local QStar office. If preferred, email to license@qstar.com or license@qstar.it. A Customer Support representative will email the License Key and any further instructions. A license request page is available on the QStar website, http://www.qstar.com/support/license-key- request-form/ Activate the Demo License Key The Demo license key is a file that will be sent to a specified email address. Depending on the version of Software, the file should be either copied to the c:QStarlicense folder or use the Activate Button. Once the license file is copied or uploaded, close and then re-open the Administration Interface to see the new license key information. T The Demo License Key will allow the use of all the QStar Products with any device for the time specified in the Expiration Date box. The maximum number of libraries that can be controlled by the QStar Software at the same time is 8. The Serial Number for Demo license is not necessary and will be displayed as N/A (Not Available). Note: In the example, the License type is changed to Demo and the Figure 3.13 - Inserting the Demo License Key Information License Key is activated. Page 18 of 42
  • 49. Figure 3.14 - Inserting the Demo License Key Information If the Demo license expires, a red question mark symbol will appear in the Expiration date box and a pop up window will appear each time License is selected. Note: In the example, the Demo License Key is expired. If the library was already configured, to restart the QStar Server, select Status, in the view pane select the Start button and the server will restart, completing the library configuration. If the library configuration is not already configured go to the “Specifying the Storage Device Configuration” section. Note: The Publisher Manager State information will be available only if QStar Software will be used with a publisher device. Figure 3.15 - QStar Server (Restarting the Server) Page 19 of 42