Pre Install Commvault

® ™
CommVault Galaxy
Pre-Installation Checklist
Software Version 6.1.0
TM
Dynamic Data Management
Data & Storage

Management
Software
Copyright
© 2000-2006 by CommVault Systems, Inc. All rights reserved.
The information in this document is subject to change without notice. CommVault Systems assumes no
responsibility for any errors that may appear in this document. No part of this document may be
reproduced in any form or by any means - graphic, electronic or mechanical, including photocopying,
recording, taping, or storage in an information retrieval system - without prior written permission of the
copyright owner.
Trademarks
CommVault, CommVault Systems and logo, QiNetix, QNet, QSM, CommVault Galaxy and design,
DataMigrator, DataArchiver, QuickRecovery, QR, CommServe, CommServe StorageManager,
MediaAgent, iDataAgent, CommCell, QCell and CommNet are trademarks, and may be registered
trademarks, of CommVault Systems, Inc.
EMC, Symmetrix, SnapView, and TimeFinder are trademarks or registered trademarks of EMC
Corporation.
Enterprise Volume Manager, and EVM are trademarks or registered trademarks of Compaq Computer
Corporation.
InstallShield and UnInstallShield are registered trademarks of InstallShield Software Corporation.
Exchange 5.5, Exchange 2000, Exchange 2003, Microsoft, SQL, SQL2000, Windows, Windows NT,
Windows 2000, and Windows Server 2003 are trademarks or registered trademarks of Microsoft
Corporation.
AIX is a registered trademark of International Business Machines Corporation.
Solaris and JAVA are registered trademarks of Sun Microsystems.
Oracle is a trademark or registered trademark of Oracle Corporation.
Any other trademarks appearing in this document are the property of their respective owners.
Printed in the United States of America

CommVault Systems, Inc.
End User License and Limited Warranty Agreement
CommVault® Software Release 6.1.0
(including Microsoft® SQL Server™ 2000, SQL Server™ 2000 Desktop Edition and Windows Pre-Installation
Environment)
End User License Agreement
IMPORTANT- READ CAREFULLY: THIS END USER LICENSE AGREEMENT (“EULA”) IS A LEGAL
AGREEMENT BETWEEN YOU (EITHER AS A SINGLE INDIVIDUAL OR ENTITY) AND COMMVAULT
SYSTEMS, INC. (“COMMVAULT”) FOR THE SOFTWARE PRODUCT(S) IDENTIFIED HEREIN, WHICH
INCLUDES COMPUTER SOFTWARE AND MAY INCLUDE ASSOCIATED MEDIA, AND “ONLINE” OR
ELECTRONIC DOCUMENTATION (“SOFTWARE”). BY INSTALLING, COPYING OR OTHERWISE USING
THE SOFTWARE, YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA. IF YOU DO NOT AGREE
TO THE TERMS OF THIS EULA, DO NOT INSTALL OR USE THE SOFTWARE. YOU SHALL INFORM ALL
USERS OF THE SOFTWARE OF THE TERMS AND CONDITIONS OF THIS EULA.
This EULA, grants you, the user, a non-exclusive license to use the Software under the terms and conditions stated herein.
You agree that all upgrades, enhancements, maintenance releases, patches, bug-fixes or other modifications to the Software
provided to you shall be governed by the terms and conditions, including the limited warranty, exclusive remedies and
limitations of liability provisions, contained in this EULA. Except as otherwise provided herein, the license granted herein
shall be perpetual provided you comply with the terms hereof. This EULA shall be in effect until terminated. You may
terminate this EULA at any time by destroying all copies of Software and corresponding documentation. This EULA will
terminate immediately without notice from CommVault if you fail to comply with any provision of this EULA. Upon
termination, you must destroy all copies of Software in your possession or control.
You may: (i) use the Software, with the same or lower version number identified herein, in numbers equal to the number of
licenses purchased for all items; (ii) make copies of the Software, documentation or other user information accompanying the
Software solely for back-up purposes, provided such back-up copies are only utilized as a replacement for the original copy
on the same computer that the Software was previously installed; and, (iii) make a copy or print documentation provided in
electronic form. You must incorporate all copyright and other notices included on the materials on any copies or partial
copies that you make.
You may not: (i) make a copy of any of the Software for any purpose not explicitly permitted herein; (ii) provide commercial
hosting services , sell, sublicense, rent, loan or lease the Software to another party, without the prior written consent of
CommVault; (iii) except to the extent that such a prohibition is expressly prohibited by law, decompile, disassemble, reverse
engineer or modify, in any manner, any of the Software; (iv) transfer or assign your rights to use the Software; (v) use the
Software in violation of applicable local, federal or other laws or regulations; or, (vi) use the Software for any purpose other
than as permitted in this EULA.
Any software CommVault and/or its licensors may provide you as part of support services are governed by this EULA,
unless separate terms are provided. Except as specifically provided, this EULA does not obligate CommVault and/or its
licensors to provide any support services or to support any software provided as part of those services. You agree that
CommVault and/or its licensors may, for business purposes, collect, process, and use technical information gathered as part
of any product support services provided to you related to the Software and any other technical information you provide to
CommVault provided that such information does not personally identify you.
All title and intellectual property rights in and to the Software, and any copies you are permitted to make herein, are owned
by CommVault and/or its licensors and is protected by United States and other country copyright, trade secret, and other laws
and by international treaty provisions. This Software is licensed, not sold. CommVault and/or its licensors retain ownership
of the Software. No rights are granted to you other than a license to use the Software upon the terms expressly set forth in this
EULA. Such licensors, in addition to any other rights or remedies available to them, are third party beneficiaries of this
EULA for their respective software and may have the right to enforce such terms against you. The structure, sequence,
organization and source code of the Software are valuable trade secrets of CommVault and/or its licensors. The export of the
Software may be restricted by the export control laws of the United States of America and other countries. You agree to
comply strictly with all such regulations and acknowledge that you have the responsibility to obtain licenses to export, re-
export, or import Software. This EULA shall be governed by the laws of New Jersey, USA, without regard to any provisions
concerning the applicability of the laws of other jurisdictions. This EULA is the complete and exclusive statement of your
agreement with CommVault with respect to the subject matter hereof and supersedes all prior agreements. If any provision of
this EULA is held to be invalid or unenforceable by a court of competent jurisdiction, the remaining provisions of this EULA
shall remain in full force and effect.
All rights not expressly granted hereunder are expressly reserved by CommVault.
Software Labeled “Not for Resale” or Provided for Beta, Demonstration, Test, or Evaluation Purposes
If the Software is provided to you for beta, demonstration, test or evaluation purposes or is labeled “Not for Resale,” then,
notwithstanding anything to the contrary in the EULA: (i) The licenses granted herein shall be for a term of thirty (30) days
(the “Evaluation Period”) unless otherwise agreed to in writing by CommVault, and CommVault reserves the right to
terminate this EULA or any licenses granted hereunder immediately upon written notice at its convenience; (ii) Your use of
the Software is limited to use for demonstration, test or evaluation purposes, and you may not resell or otherwise transfer the
Software; (iii) You agree to keep confidential and not to disclose or otherwise make publicly available any information
related to the Software, including, but not limited to test results, characteristics, and performance of the software; (iv) You
agree not to copy the Software and not to provide a copy of the Software to any other party; (v) You agree not to use the
Software in a production environment or for production data processing purposes, and that any use of the Software in a
production environment or for production data processing purposes is at your sole risk to backup data and take other
appropriate measures to protect your computer programs and data; and (vi) You agree to immediately, on or before the end of
the Evaluation Period, promptly remove, destroy, and erase from computer memory and storage media any installed copy of
the Software, and return the Software to CommVault together with all documentation and other materials provided by
CommVault. Limited duration licenses, site licenses, beta, evaluation, test or demonstration Software products are delivered
“AS IS” without a warranty of any kind. CommVault shall have no obligation to support, maintain, or provide other
assistance regarding any limited duration licenses, site licenses, beta, evaluation, test, or demonstration Software products. IF
THE SOFTWARE IS PROVIDED TO YOU FOR BETA, DEMONSTRATION, TEST, OR EVALUATION PURPOSES
OR IS LABELED “NOT FOR RESALE,” IN NO EVENT WILL COMMVAULT BE LIABLE FOR ANY DAMAGES
FOR ANY CAUSE OR FOR ANY CLAIM BY BORROWER OR FOR ANY THIRD PARTY CLAIM, INCLUDING BUT
NOT LIMITED TO ANY DIRECT DAMAGES, ACTUAL DAMAGES, LOST PROFITS, LOST DATA, LOST SAVINGS,
OR ANY SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, EVEN IF COMMVAULT HAS
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Note on JAVA Support
THIS SOFTWARE PRODUCT MAY CONTAIN SUPPORT FOR PROGRAMS WRITTEN IN JAVA. JAVA
TECHNOLOGY IS NOT FAULT TOLERANT AND IS NOT DESIGNED, MANUFACTURED, OR INTENDED FOR
USE OR RESALE AS ONLINE CONTROL EQUIPMENT IN HAZARDOUS ENVIRONMENTS REQUIRING FAIL-
SAFE PERFORMANCE, SUCH AS IN THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR
COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, DIRECT LIFE SUPPORT MACHINES, OR WEAPONS
SYSTEMS, IN WHICH THE FAILURE OF JAVA TECHNOLOGY COULD LEAD DIRECTLY TO DEATH,
PERSONAL INJURY OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE. Microsoft Corporation obligated
CommVault to make this disclaimer.
Limited Warranty
With the exception of Software provided to you for beta, demonstration, test or evaluation purposes or that is labeled “Not for
Resale, CommVault warrants that the Software licensed hereunder shall be new and shall operate substantially in accordance
with its user documentation for a period of ninety (90) days from the date of shipment by CommVault (hereinafter the
"Warranty Period"). If, during the Warranty Period, you believe any Software product to be defective, you must immediately
notify CommVault in writing and follow CommVault’s instructions regarding the return of such Software product.
CommVault’s sole liability to you, and your sole remedy, shall be, at CommVault’s option, (i) repair or replacement of the
Software product which does not comply with this Limited Warranty, or (ii) return of the amount paid by you for the
Software product which does not comply with the Limited Warranty. In the event CommVault determines that the software
product is in compliance with this Limited Warranty, you shall pay the cost of all charges associated with the inspection and
shipment of such Software product by CommVault.
Disclaimer. COMMVAULT DOES NOT WARRANT THAT THE SOFTWARE WILL OPERATE
UNINTERRUPTED OR ERROR FREE. THIS LIMITED WARRANTY PROVIDED HEREIN IS IN LIEU OF ALL
OTHER WARRANTIES. COMMVAULT AND ITS LICENSORS DISCLAIM ALL OTHER WARRANTIES,
EXPRESS OR IMPLIED, EITHER IN FACT OR BY OPERATION OF LAW, STATUTORY OR OTHERWISE,
AND COMMVAULT AND ITS LICENSORS EXPRESSLY EXCLUDE AND DISCLAIM ANY WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, SATISFACTORY QUALITY,
RELIABILITY OR AVAILABILITY, ACCURACY OR COMPLETENESS OF RESPONSES, RESULTS, LACK
OF VIRUSES, NONINFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS, AND THE PROVISION OF
OR FAILURE TO PROVIDE SUPPORT OR OTHER SERVICES, INFORMATION, SOFTWARE, AND
RELATED CONTENT THROUGH THE SOFTWARE OR OTHERWISE ARISING OUT OF THE USE OF THE
SOFTWARE. THE PROVISIONS SET FORTH ABOVE STATE COMMVAULT’S AND ITS LICENSORS’
ENTIRE RESPONSIBILITY AND YOUR SOLE AND EXCLUSIVE REMEDY WITH RESPECT TO ANY
BREACH OF ANY WARRANTY.
No Consequential Damages. NEITHER COMMVAULT, NOR ANY OF ITS LICENSORS, WILL, UNDER ANY
CIRCUMSTANCES, BE LIABLE TO YOU OR ANY OTHER PARTY, FOR COSTS OF PROCUREMENT OF
SUBSTITUTE PRODUCTS OR SERVICES, LOST PROFITS, LOSS OF INFORMATION OR DATA OR ANY
OTHER SPECIAL, INCIDENTAL, PUNITIVE, INDIRECT OR CONSEQUENTIAL DAMAGES WHATSOEVER
(INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF CONFIDENTIAL OR OTHER
INFORMATION, FOR BUSINESS INTERRUPTION, FOR PERSONAL INJURY, FOR LOSS OF PRIVACY, FOR
FAILURE TO MEET ANY DUTY INCLUDING GOOD FAITH OR REASONABLE CARE, FOR NEGLIGENCE,
AND FOR ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER) REGARDLESS OF THE FORM OF
ACTION ARISING OUT OF OR RELATING TO THIS LIMITED WARRANTY OR RESULTING FROM THE
LICENSE OF SOFTWARE PRODUCTS OR USE BY YOU OR ANY OTHER PARTY OF SUCH PRODUCTS, OR
INABILITY TO USE THE SOFTWARE, THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT OR
OTHER SERVICES, INFORMATION SOFTWARE, AND RELATED CONTENT THROUGH THE SOFTWARE
OR OTHERWISE ARISING OUT OF THE USE OF THE SOFTWARE, OR OTHERWISE UNDER OR IN
CONNECTION WITH ANY PROVISION OF THIS EULA EVEN IN THE EVENT OF THE FAULT, TORT
(INCLUDING NEGLIGENCE), MISREPRESENTATION, STRICT LIABILITY, BREACH OF CONTRACT OR
BREACH OF WARRANTY OF COMMVAULT OR ANY OF IT’S LICENSORS AND EVEN IF COMMVAULT
OR ANOTHER PARTY HAS BEEN NOTIFIED OF THE POSSIBILITY OF SUCH DAMAGES AND
NOTWITHSTANDING ANY FAILURE OF AN ESSENTIAL PURPOSE OF THIS LIMITED WARRANTY.
Limit of Liability. IN THE EVENT COMMVAULT OR ITS LICENSORS ARE SUBJECT TO ANY LIABILITY IN
CONNECTION WITH THE SOFTWARE PRODUCTS FOR ANY REASON WHATSOEVER WHETHER
ARISING FROM NEGLIGENCE, BREACH OF CONTRACT OR OTHERWISE, (INCLUDING, WITHOUT
LIMITATION, ALL DAMAGES REFERENCED HEREIN AND ALL DIRECT OR GENERAL DAMAGES IN
CONTRACT OR OTHERWISE), NEITHER COMMVAULT’S LIABILITY NOR THE LIABILITY OF ITS
LICENSORS SHALL EXCEED THE SUM PAID BY YOU TO COMMVAULT FOR THE SOFTWARE PRODUCT
WHICH WAS FOUND TO HAVE NOT COMPLIED WITH THIS LIMITED WARRANTY. THIS LIMITATION
SHALL APPLY EVEN IF COMMVAULT OR ITS LICENSORS HAVE BEEN ADVISED OF THE POSSIBILITY
OF SUCH DAMAGES AND NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY
LIMITED WARRANTY.
These terms and conditions, warranties, limitations and remedies contain an allocation risk between you and CommVault.
Accordingly, CommVault’s prices reflect such allocation of risk. Because some jurisdictions restrict the ability to exclude
implied warranties, limit or exclude incidental or consequential damages or limit liability, the foregoing limitations and
exclusions may not apply to you.
United States Government and DOD
This article applies to all acquisitions of this Software by or for the Federal Government. By accepting delivery of this
Software, you hereby agree that this software qualifies as “commercial computer software” as that term is used in the
acquisition regulation(s) applicable to this procurement. The terms and conditions of this EULA shall pertain to the
Government’s use and disclosure of this Software, and shall supersede any conflicting contractual terms and conditions. If
this EULA fails to meet the Government’s minimum needs or is inconsistent in any respect with Federal procurement law,
the Government agrees to return this software, unused, to CommVault.
All Software provided to the U.S. Government pursuant to solicitations issued on or after December 1, 1995 is provided with
the commercial license rights and restrictions described elsewhere herein. All Software provided to the U.S. Government
pursuant to solicitations issued prior to December 1, 1995 is provided with “Restricted Rights” as provided for in FAR, 48
CFR 52.227-14 (JUNE 1987) or DFAR, 48 CFR 252.227-7013 (OCT 1988), as applicable.
The following paragraph is applicable only to CommVault 1-Touch products containing Microsoft Windows Pre-Installation
Environment (WinPE) software: (i) The license for the CommVault 1-Touch product is limited to its use as a boot,
diagnostic, disaster recovery, setup, restoration, emergency services, installation, test and/or configuration utilities program
and not for use as a general purpose operating system or a fully functional version of any operating system product; (ii) the
WinPE software is provided as is; (iii) the 1-Touch products, by virtue of the inclusion of WinPE, contain a security feature
that will cause the computer system to reboot without prior notification to you after 24 hours of continuous use; (iv) neither
Microsoft nor any Microsoft affiliate shall have any liability related to the 1-Touch or the WinPE products; (v) all customer
support issues will be handled solely by CommVault.
Trademark Acknowledgment
CommVault, CommVault Systems and logo, QiNetix, QNet, QSM, CommVault Galaxy and design, DataMigrator,
DataArchiver, QuickRecovery, QR, CommServe, CommServe StorageManager, MediaAgent, iDataAgent, CommCell, QCell
and CommNet are trademarks, and may be registered trademarks, of CommVault Systems, Inc.
Patent Acknowledgment
This Software is covered by US Patent Numbers 5,559,991; 5,642,496; 6,418,478; 6,542,972; 6,658,436; 6,760,723; and
6,721,767 and other patents and patents pending.
Copyright Acknowledgment
© 1997-2006 CommVault Systems, Inc. All rights reserved. DVD, MO and UDO recording software developed under
license from PoINT Software & Systems GmbH- www.pointsoft.de.
Table of Contents
The Pre-Installation Checklist helps you prepare and plan the CommServe and MediaAgent Installation.
1. CommCell Overview
2. Network Requirements
{ Domain Name Server (DNS) Environment
{ WINS or Other Non-DNS Environment
3. General Hardware Configuration

{ Libraries, Drives, and Media
{ SCSI Cabling and Adapters
4. Driver Configurations
{ Windows NT
{ Windows 2000 and Windows 2003 Server
{ Solaris
{ HP-UX
{ AIX
{ Tru64
{ NetWare
{ Linux
5. Direct-Attached Library Configuration

{ SCSI Ports and SCSI Targets
{ Single SCSI Configuration Guidelines
{ Multiple SCSI Configuration Guidelines
{ Shared Library SCSI Configuration Guidelines
{ Shared Library SCSI Configuration Guidelines
6. SAN Configuration
{ The Basic SAN Setup
{ SAN Addressing Overview
{ SCSI-LUN Mapping Guidelines for SAN Libraries
{ SCSI Target Guidelines
{ Fibre Channel LUN Guidelines
{ Multiple Router, Single Library Configuration
{ Avoiding Common Errors
{ SAN Configuration Summary
7. DISC Optical Library Configuration

8. ACSLS Library Configuration
{ Direct-Attached Library Configuration
{ DDS Configuration
9. ADIC Libraries Attached to Scalar Distributed Library Controller (SDLC) Configuration

{ Software Requirements
{ Hardware Requirements
10. Configuring Libraries Attached to a NAS File Server

{ Guidelines for Attaching Hardware Used by NAS to a SAN
{ Obtaining Information from a NAS File Server
Page 1 of 41
CommCell Overview
Introduction
QiNetix software provides a powerful set of storage management tools that help you move and manage your critical data.
These tools enable you to store and retrieve data associated with computer systems in your enterprise.
The QiNetix software consists of integrated software modules which can be grouped together in a CommCellTM. Each
CommCell consists of the following main components:
z One or more of the following Client Agents:
TM
{ iDataAgents that perform the backup and restore operations
TM
{ DataMigrator agents that perform the data migration, archival and recovery operations
{ DataArchiver Agents
{ Quick Recovery (QR) agents that create and recover QR volumes
{ ContinuousDataReplicator to perform data replication from a source Client to a destination Client
z The Common Technology Engine (CTE) components consisting of:
TM
{ One CommServe StorageManager
{ One or more MediaAgentsTM
Once installed and configured, these CommCell elements can be controlled and monitored from a single unified CommCell
ConsoleTM.
Client Agents
Client Agents are software modules that perform data protection and data recovery operations for specific operating
systems or applications. Multiple agents may be used to protect all types of data residing on a computer. The following
sections provide a brief description of each of these Client Agents.
iDataAgents
iDataAgents are software modules that are used for backing up and restoring data. QiNetix software provides a variety of
Page 2 of 41
iDataAgents, each one designed to handle a different kind of data. If a given computer has two or more types of data, it
requires one iDataAgent for each data type. For example, to secure all the data on a computer where a Microsoft Exchange
Server resides, you would need the following iDataAgents:
z One Windows File System iDataAgent to back up the computer’s file system.
z One Microsoft Exchange Database iDataAgent to back up the database.
In the CommCell Console, such a configuration would appear as two iDataAgents on a client computer.
DataMigrator Agents
DataMigrator Agents are software modules that are responsible for periodically moving unused or infrequently used data on
their host computers to secondary storage, thereby reducing the size of data on the primary storage. QiNetix software
provides several DataMigrator Agents, each one designed to handle a different kind of data. DataMigrator Agents reduce
the duration of backup windows by reducing the amount of data to be backed up by an iDataAgent.
DataArchiver Agent
DataArchiver agents are software modules that are designed for long term storage and indexing of data and to meet
security and compliance standards. The primary function of DataArchiver is to preserve data outside of the operational
environment. DataArchiver removes the data from the source client once it has been archived and/or indexed. In this way,
large amounts of data can be stored, for example, and reviewed at a later time.
Quick Recovery Agents
Quick Recovery agents are software modules that use the snapshot technology to create Quick Recovery (QR) volumes on
magnetic disks. These QR volumes can be easily recovered in minutes. Quick Recovery Agent integrates with major
storage-intensive applications, such as Microsoft SQL Server 2000, Microsoft Exchange 2000 and Oracle, to ensure that
data objects are properly synchronized and easily recovered. Quick Recovery Agents augment the traditional backup and
restore operations of an iDataAgent by allowing the user to create frequent images of the data which provides faster
application recovery, when needed; while iDataAgents can be used to perform the traditional backup and restore operations
of these images.
ContinuousDataReplicator Agent
ContinuousDataReplicator (CDR) agents are software modules that provide protection of application data and file systems,
by replicating data from a source computer to a destination computer in nearly real-time. High availability of protected data
in a consistent state is accomplished through the creation of Recovery Points, using snapshots created by QSnap on the
destination computer, which can be mounted, made available as shares, or recovered using Copyback. In addition, backups
can be made from the snapshots of file system data or application data in a consistent state for point-in-time recovery.
Common Technology Engine

Common Technology Engine consists of software modules that provide the necessary tools to manage and administer the
Client Agents and also manage the storage media associated with the CommCell. The following sections describe the
components of the Common Technology Engine.
CommServe StorageManager
The CommServeTM ties the elements of the CommCell together; it is the coordinator and administrator of the CommCell.
The CommServe communicates with all agents in the CommCell to initiate data protection, management and recovery
operations. Similarly, it communicates with MediaAgents when the media subsystem requires management. The
CommServe maintains a database containing all the information relating to the CommCell. In addition, it provides several
tools to administer and manage the CommCell.
MediaAgents
The MediaAgent transfers data between the client computer(s) and the storage media. Each MediaAgent communicates
locally or remotely to one or more storage devices, which contains the storage media. The QiNetix system provides support
for a wide variety of storage devices.
The MediaAgent can also function as a copy manager that leverages other data transfer mechanisms, such as a third party
copy. In such cases, the MediaAgent interfaces with the Quick Recovery Agent and Serverless Data Manager to move data.
The following diagram provides a summary of the CommCell components:
Page 3 of 41
Page 4 of 41
QiNetix Installations
The QiNetix software is modular and can reside on the same and/or separate computers depending on your needs. Some
administrators may have a dedicated CommServe computer and a dedicated MediaAgent computer. Others may want to
back up the file system data on the CommServe and therefore install the client software on the CommServe computer as
well. Still others may use the same computer to serve as the CommServe, MediaAgent, and a client. The QiNetix software
supports any and all of these configurations. The following figure shows an example of a CommCell:
Back to Top
Page 5 of 41
Software Installation Discs
This software package contains several CD-ROMs as described in the following table:
QiNetix
No. Title Contents

1A CommServe CommServe components for non-clustered environment or physical
installations in a clustered environment, which includes the following:
(Use this CD-ROM to install the
CommServe software.) CommServe
Microsoft SQL 2000 software with Service Pack 4 for the CommServe
Database Engine
MediaAgent
CommCell Console
CommCell Explorer
CommServe SNMP Enabler
CommNet Agent
Microsoft Windows File System iDataAgent
Microsoft SQL Server iDataAgent
Open File Handler
1B Windows, NetWare and CommNet All Windows components for non-clustered environment or physical
Agent installations in a clustered environment, and NetWare components for
clustered and non-clustered environment, which includes the following:
(Use this CD-ROM to Upgrade the
CommServe software and install or CommServe
upgrade other components.) Microsoft SQL 2000 Service Pack 4
MediaAgent (Windows and NetWare)
CommCell Console
CommCell Explorer
CommNet Agent
Agents supported on Windows and NetWare
2 Unix, Linux and Macintosh All Unix (AIX, FreeBSD, HP-UX, IRIX, Solaris and Tru64), Linux, and
Macintosh components (both clustered and non-clustered environments,
which includes the following:
MediaAgent (AIX, HP-UX, Linux, Solaris and Tru64)

CommCell Console (Macintosh)
Agents supported on Unix, Linux and Macintosh
3 Books Online and Resource Pack QiNetix Documentation
QiNetix and QNet Tools and Utilities
4 1-Touch for Windows and Solaris 1-Touch Server for Windows
1-Touch Server for Unix
5 CommServe and Windows Agents All Windows components for clustered virtual server, which includes the
for Cluster following:
CommServe
MediaAgent
CommCell Explorer
CommServe SNMP Enabler (Windows)
CommNet Agent
Agents supported on Windows cluster
6 Windows Agents for X64 All Windows X64 components for non-clustered environment or physical
installations in a clustered environment, which includes the following:
MediaAgent
Agents supported on Windows X64
7 Windows Agents for X64 Cluster All Windows X64 components for clustered virtual server, which includes
Page 6 of 41
the following:
MediaAgent
Agents supported on Windows X64 Cluster
8A CommServe for Itanium (IA-64) CommServe Itanium components for non-clustered environment or
physical installations in a clustered environment, which includes the
(Use this CD-ROM to install the following:
CommServe software.)
CommServe
Microsoft SQL 2000 software with Service Pack 4 for the CommServe
Database Engine
CommCell Console
CommCell Explorer
8B Windows Agents for Itanium (IA- All Windows Itanium components for non-clustered environment or
64) physical installations in a clustered environment, which includes the
following:
(Use this CD-ROM to Upgrade the
CommServe software and install or CommServe
upgrade other components in the Microsoft SQL 2000 Service Pack 4
non-clustered environment) MediaAgent
CommCell Console
CommCell Explorer
Agents supported on Windows 64-bit
9 CommServe and Windows Agents All Windows 64-bit components for clustered virtual server, which
for Itanium Cluster (IA-64) includes the following:
CommServe
MediaAgent
CommCell Explorer
Agents supported on Windows 64-bit cluster
CDR ContinuousDataReplicator ContinuousDataReplicator components, which includes the following:
ContinuousDataReplicator (CDR)
Journal Driver for CDR
QSnap
Service Pack 2
QNet
No. Title Contents

QNet QNet components (except CommNet Agent) for Windows, which includes
the following:
CommNet Server
Microsoft SQL 2000 Database software with Service Pack 4 for the
CommNet Server Database Engine
CommNet Browser
Books Online QNet Documentation
Service Pack
No. Title Contents
Page 7 of 41
Service Pack Includes Updates for QiNetix, QNet and QSM software.
Contact your software provider to verify whether you have the CDs
associated with the latest Service Pack in the software package.
Page 8 of 41
Network Requirements
Select the desired topic:

z Overview
z Domain Name Server (DNS) environment
{ Multi-Homed CommCell Computers
z WINS or other Non-DNS Environment
Overview
All CommCell computers (i.e., CommServe, MediaAgent, Client computers) must be connected via a network configured
with TCP/IP protocol. To ensure each computer can resolve the names of other CommCell computer members and therefore
communicate, we offer the following guidelines.
Domain Name Server (DNS) environment

A DNS environment provides a centralized means of resolving computer names with their corresponding IP addresses. Refer
to your operating system documentation for information on how to establish and manage DNS.
Multi-Homed CommCell Computers
A multi-homed computer is one that has two or more network interface cards (NICs). To ensure proper name/IP address
resolution within QiNetix, it is necessary to uniquely name each NIC in the DNS. For example, assume there is a computer
whose computer name is amber and fully qualified host names are amber1.company.com and amber2.company.com
respectively. This computer has two NICs with the following IP addresses:
z First NIC: 150.128.4.78
z Second NIC: 150.128.6.32
To ensure that both interfaces can be resolved, define unique names within DNS, such as:
z amber1.company.com 150.128.4.78
z amber2.company.com 150.128 6.32
WINS or other Non-DNS Environment

If your network does not have DNS lookup or some other name resolution facility, the CommServe will provide the names
and IP addresses of all the members in the CommCell. The fully qualified computer name and IP address of the CommServe
is stored in the hosts file of each CommCell member. The hosts file in the CommServe computer, in turn, stores the fully
qualified computer name and IP addresses of all the members in the CommCell, thereby providing the lookup facility to all
the members in the CommCell. Depending on the operating system on your computer, the hosts file is located in one of the
following directories:
z On a Windows computer, the hosts file is located in %SystemRoot%\system32\drivers\etc directory. (%SystemRoot% is
the Windows installation directory on your system.)
z On a computer with a Unix operating system, the hosts file is located in the /etc/inet directory.
During installation of each CommCell member, the install program attempts to resolve the name of the CommServe to an
IP address. If the resolution fails, the installation prompts you to enter the IP address of the CommServe computer.
Proper name/IP address resolution is essential to reliable network communications.
Back to Top
Page 9 of 41
General Hardware Configuration

z Overview
z Libraries, Drives, and Media
z SCSI Cabling and Adapters
Overview
You can avoid many installation problems by properly setting up your libraries and media drives. Read the appropriate
sections before configuring your storage libraries.
Each tape library and drive can be directly attached to one or more MediaAgents via SCSI buses or remotely connected via
a Storage Area Network (SAN). In addition, drives can be remotely accessed through a NetApp filer using the NDMP
protocol. In any case, in order to manage the media changers and drives within a CommCell, the MediaAgent must know
the SCSI address or NetApp filer drive address of each device, the MediaAgent that controls the device, and the library to
which the device belongs.
You must configure libraries and drives when:
z You install a new MediaAgent, library, or drive.
z The existing SCSI configuration changes and the MediaAgent cannot reconfigure them automatically.
We strongly recommend you to verify and ensure that proper hardware zoning of tape drives be
implemented, especially when you have HBA failover implemented in your environment. For more
information on zoning of HBA failover, contact your HBA software vendor.
Libraries, Drives and Media

Contact your software provider for a list of storage devices (libraries, drives, media and SAN devices) and compatible SCSI
cards supported by MediaAgents.
If the storage devices are attached to NAS filers, or UNIX computers, (Solaris, HP-UX, AIX or Tru64) refer to the
appropriate vendor documentation for a list of compatible devices.
NDMP Remote Server is only supported for Windows and Solaris MediaAgents.
SCSI Cabling and Adapters

The software supports the use of the following general types of SCSI based devices:
z Single-ended
z Differential
z LVD (low voltage differential)
z HVD (high voltage differential)
Each type requires its own set of adapters, cabling, devices (i.e., media drives) and terminators. Because they are
electrically incompatible with each other, you must not mix them (e.g., by connecting a single-ended adaptor, cable, or
terminator to a differential drive).
Back to Top
Page 10 of 41
Driver Configurations

z Overview
z Windows NT
z Windows 2000 and Windows 2003 Server
z Solaris
z HP-UX
z AIX
z Tru64
z NetWare
z Linux
Overview
Once you’ve cabled and configured the storage media, you must verify that the drivers are ready and working properly on
the computer in which you wish to install the MediaAgent. This is performed before installing the MediaAgent software. The
following steps, although not conclusive, should help you to identify most of the common configuration problems.
Ensure that all SCSI adapter and tape device drivers are installed.
Windows NT
1. When you start the MediaAgent computer, the computer should identify and list all connected drives on the monitor.
This information is normally displayed for 10 or more seconds, so you should be able to count and identify the drives
that were detected.
You access the SCSI Adapters window from the Windows Control Panel.
2. Once the computer has completed its start-up sequence, you should view the libraries and drives from the SCSI
Adapters window, which can be accessed from the Windows Control Panel.
From this window select each item, click the Properties button and verify that the SCSI port(s) and target(s) are set in
accordance with the guidelines presented in this document.
3. Now, view the drives from the Tape Devices window, that you access from the Windows Control Panel.
Page 11 of 41
From this window:

z Select each item, click the Properties button and verify that the drive information is correct.
z Verify that the status of each device driver is Driver loaded as shown in the example window.
Back to Top
Windows 2000 and Windows 2003 Server

You can access the Computer Management window using the following options from the Start
menu – Programs, Administrative Tools, Computer Management.
1. In the Computer Management window, make sure the attached media changer, tape or optical drives for the library are
listed.
Page 12 of 41
2. Expand tape or disk drives and select each drive, right click and select Properties to verify that the drive information
is correct. Check the Device Status and ensure that the device is working properly.
If drives are not listed, detect the device and install the appropriate driver. For more
information on this task, refer to the user manual provided by the manufacturer of
your library and drive.
For devices using the iSCSI and Storport drivers make sure that the medium changer for the library is enabled in the
Windows Computer Management window. For all other drivers we recommend that the media changer is disabled in the
Windows Computer Management window.
1. From the Computer Management window select Device Manager in the left window panel and expand Medium Changers
in the right window panel.
2. Right-click the library with the media changer and select Enable or Disable as appropriate.
If you are starting the computer for the first time after installing the MediaAgent, ensure that the Removable Storage
Management (RSM) is disabled.
1. Do one of the following:

{ Disable and stop RSM service from the Service pane.
{ If the RSM service cannot be disabled, verify that all targeted libraries and drives are absent from or disabled in the
list under the storage/removable storage/ physical locations folder.
Back to Top
Solaris
1. Ensure that the appropriate drivers for the SCSI/HBA/FC card are installed and working properly.
2. Ensure that all the devices (libraries and drives) are connected properly.
Back to Top
HP-UX
HP-UX MediaAgent requires the kernel modules stape, sctl and schgr to be loaded, in order to use tape libraries. Install
these kernel modules using the following steps:
1. At the Unix prompt type sam.

2. In the System Administration Manager dialog, select Kernel Configuration and press <Return>.
3. In the Kernel configuration dialog, select Drivers and press <Return>.
4. Select stape.
5. From the ACTION menu choose add drivers to kernel.
6. Repeat steps 4 and 5 to load sctl and schgr kernel modules.
7. Choose Process New Kernel.
8. At the prompt select the option to reboot the system.
Back to Top
AIX
In AIX MediaAgents, you can view a list of SCSI devices and tape drives using either the smit or lsdev command. You can
also use the wsm tool, which is a graphical administrative tool.
Using smit
1. At the Unix prompt type smit.
Viewing SCSI Adapters
Page 13 of 41
2. In the System Management Interface Tool dialog box, select Devices, SCSI Adapter and then List All SCSI Adapters.
A list of all SCSI adapters available in the system are displayed.
Viewing Tape Drives
3. In the System Management Interface Tool dialog box, select Devices, Tape Drives and then List All Defined
Tape Drives. A list of all the tape drives attached to the system are displayed.
Using lsdev
1. At the Unix prompt type:

lsparent -C -k scsi
A list of all SCSI adapters available in the system are displayed.

2. At the Unix prompt type lsdev -C -c tape.
A list of all the tape drives attached to the system are displayed.
Back to Top
Tru64
2. Use the following command to list the devices attached to the system:
hwmgr -show scsi
3. If you do not see the devices, use the following command to auto-detect the devices:
hwmgr -scan scsi
Back to Top
NetWare
2. Use the following command to list the devices attached to the system:
list devices
A list of devices connected to the NetWare server are displayed.

If you do not see the devices, use the following command to detect the devices:
nwconfig
If you have a Qlogic card and use the /IGNCFG command to see the devices edit the load command for the Qlogic HAM
with /IGNCFG in Startup.ncf file.
It is recommended that you unload any Custom Device modules (CDMs) that may be loaded,
before configuring the libraries. (e.g., nwtape.cdm)
Use the list storage adapters command to determine the CDMs that are loaded and then use
the unload command (e.g., unload nwtape.cdm) to unload these modules.
It is also recommended that the list of unload commands are included in the autoexec.ncf, to
prevent these modules from being loaded after subsequent reboots.
Back to Top
Linux
Page 14 of 41
In Linux MediaAgents, you can view a list of SCSI devices and tape drives using either the Hardware Browser or Terminal
to view the attached devices. Using the Hardware Browser
2. Install the necessary drivers for the SCSI devices.
For example, using GNOME, you can access the Hardware Browser using the following
options: From the Start menu – System, Hardware Browser.
3. On a Linux computer you can view the libraries and drives from the Hardware Browser.
4. Click on the SCSI devices to view a list of SCSI adapters available in the computer.
5. Click on Tape Drives to view a list of tape drives attached to the computer.
Using the Terminal
2. Install the necessary drivers for the SCSI devices.
3. Navigate to the following folder in the Terminal window:
/proc/scsi
The location of this file may vary in the various Linux Kernel versions.
4. Open the following file:

scsi
5. The SCSI devices attached to the computer should be listed.
Page 15 of 41
Direct-Attached Library Configuration

z Overview
z SCSI Ports and SCSI Targets
z Single SCSI Configuration Guidelines
{ Single Library Setup
z Multiple SCSI Configuration Guidelines
{ Single Library, Two Stand-Alone Drives Setup
{ Single Library Setup
{ Multiple Library Setup
Overview
The sections that follow present guidelines for configurations in which libraries are physically attached to the MediaAgents
that control them. For SAN configuration guidelines, see SAN Configuration.
SCSI Ports and SCSI Targets

When you install a MediaAgent that is attached to one or more tape libraries, the MediaAgent detects all attached media
changers and media drives. Similarly, when you attach a new library to one or more MediaAgents, the system maps the
library and its drives. The system attempts to identify the library to which each device belongs and the device’s physical
address within that library. Drives belonging to a shared library whose media changer is controlled by another MediaAgent
are detected as stand-alone drives. You must manually map such drives to the correct library by using the Library and
Drive Configuration window.
To automate the detection process, the MediaAgent assumes that the SCSI configurations (i.e., SCSI port and target
numbers) of media drives and media changers are set in a certain manner. If they are set according to the convention, then
the detection process correctly associates the SCSI target of each drive to the drive’s physical position, provided that the
MediaAgent that controls the drive also controls the media changer of the same library. If the SCSI configuration is not set
according to the convention, or if you are configuring drives and the related media changer is controlled by a different
MediaAgent, you may manually map the drives using the Library and Drive Configuration window or use exhaustive
detection. (For information on using the Library and Drive Configuration window, see Library and Drive Configuration.)
Most library and drive manufacturers strongly recommend against using the embedded SCSI
controller on a server’s system board to drive the media changer or drives. For this reason, all
libraries and drives should be attached to the MediaAgent computer via dedicated SCSI cards.
The following hardware configuration guidelines are intended to help you avoid the manual mapping process where
possible. If you follow these guidelines, the MediaAgent will detect drives in their physical order and associate them with
their proper libraries. While other SCSI configurations can result in a properly working system, we strongly recommend that
you follow these guidelines and thus avoid common errors.
Single SCSI Configuration Guidelines

Observe the following guidelines if your libraries and drives are connected to a MediaAgent via only one SCSI port.
When you install a new library, you must set a SCSI target of the media changer and each drive
within the library. See the manufacturer’s documentation for specific instructions.
z If you plan to attach stand-alone drives, allocate the lowest targets to the stand-alone drives, reserving the higher
target numbers for the media changers and their related drives for regular libraries.
z If you plan to attach a drive whose media changer is controlled by a different MediaAgent, see Direct-Attached Shared
Library Configuration.
z It is recommended that the media changer have a target lower than the targets of its drives. Otherwise, drives may be
associated with the wrong library or incorrectly detected as stand-alone drives. (By convention we assign it to target 0 in
single library setups, although a higher number is acceptable.)
Page 16 of 41
Stand-alone drives do not have media changers.
z When setting the SCSI targets, it is recommended that you assign SCSI target numbers in ascending order in
accordance with the physical drive location. The drive with the lowest physical address gets the lowest SCSI target. The
drive with the highest physical address gets the highest SCSI target. Drives in between are assigned sequentially. A
good convention to use, when possible, is to set the library media changer to 0, the first drive to target 1, the second
drive to target 2 and so on. This can make it easier to identify the drives later.
Physical drive locations are numbered differently depending on the library. The first
drive in one library may be 0 while in another library it may be 1. See the
manufacturer’s documentation for details on your library.
z Do not assign SCSI target 7 to a drive as this is normally reserved for the SCSI adapter. For wide SCSI (68-pin)
installations, 15 targets are available.
Single Library Setup
SCSI Port
In this configuration, a single SCSI port (i.e., port 1) connects the MediaAgent to the library and its media
drives, four in this case. The port number can vary from system to system and depends on whether any other
SCSI devices are already installed. For example, your system may have a CD-ROM drive assigned to a target
on SCSI port 0.
SCSI Target
When assigning SCSI targets, we started at target 0 and went in ascending order, matching the target
number to the physical drive location. We could have started at a higher number, provided we kept an
ascending sequence (e.g., 2, 5, 6, 8, and 9).
Back to Top
Multiple SCSI Configuration Guidelines

Observe the following guidelines if your libraries and drives are connected to a MediaAgent via two or more SCSI ports.
z Observe all of the single SCSI configuration guidelines.
z If you have two or more SCSI ports attached to your MediaAgent, try to assign unique SCSI targets to each device, even
for devices on different SCSI ports. Doing so can make it easier to identify the drives later, should that become
necessary.
z Always associate the media changer with the lowest drive in its library.
z You can attach two or more stand-alone drives to a MediaAgent. If you plan to attach stand-alone drives, allocate the
lowest SCSI port numbers to those drives, reserving the higher port numbers for any libraries.
The following illustrations provide several scenarios that demonstrate each of these guidelines.
Single Library, Two Stand-Alone Drives Setup
Page 17 of 41
SCSI Port
In this configuration, SCSI port 1 connects to two stand-alone drives. SCSI port 2 connects to a library and its media
drives. We use the lower numbered port (i.e., port 1) for the stand-alone drives and the higher numbered port (i.e., port 2)
for the library.
SCSI Target
When assigning SCSI targets, we started at target 0 and went in ascending order, keeping all targets unique across the
SCSI ports.
Single Library Setup
SCSI Port
In this configuration, two SCSI ports connect the MediaAgent to the library and its media drives. We must connect the
lower port number (i.e., port 1) to the media changer.
SCSI Target
When assigning SCSI targets, we started at target 0 and went in ascending order, keeping all targets unique across the
SCSI ports. We maintained this consistency across SCSI port 2 where we started the target numbers at 3.
Multiple Library Setup
Page 18 of 41
SCSI Port
In this configuration, five SCSI ports connect the MediaAgent to two libraries with two media drives on each
port. As before, we connected the lowest port number to the media changer in the first library and drives 1
and 2. (We could have chosen either library to be first.) Then we connected the next ports in ascending
sequence by port number to ascending drive pairs: port 2 to drives 3,4 and port 3 to drives 5,6. When all the
drives in the first library were connected, we connected the second library. With two ports remaining, we
connected the lower number port (i.e., port 4) to the media changer and drives 1 and 2. We connected the
last port (i.e., port 5) to the two remaining drives, drives 3 and 4.
SCSI Target
When assigning SCSI targets, we again assigned the media changer the lowest target number and proceeded
in ascending order, keeping all targets unique across the SCSI ports. Notice that we did not use target 7 as
this is normally reserved for the SCSI adapter.
This example assumes a wide SCSI implementation. If we had used narrow SCSI, which only has 7
available targets, we would have restarted the target numbering sequence on Library 2 using
targets 0 through 4.
Back to Top
Page 19 of 41
SAN Configuration
Select a topic:
z Overview
z The Basic SAN Setup
z SAN Addressing Overview
z SCSI-LUN Mapping Guidelines for SAN Libraries
z SCSI Target Guidelines
z Fibre Channel LUN Guidelines
{ Single Router, Multiple Library Configuration
{ Multiple Router, Single Library Configuration
z Avoiding Common Errors
{ Uniform Addressing Across Devices
{ Avoiding Dynamic Address Changes
z SAN Configuration Summary
Overview
Storage Area Networks (SAN) present additional configuration issues, that are discussed in the following sections.
Stop and disable Removable Storage Management (RSM) service on all Windows 2000 and
Windows Server 2003 computers on a SAN, which can detect the shared tape/optical drives that
are configured for the software. These include other MediaAgents and even other computers which
do not have any components installed. This is a very stringent requirement as data corruption
occurs if both RSM and MediaAgent running on any computer in the SAN access the same drive at
the same time.
We strongly recommend that in a SAN based backup environment, hardware zoning of tape drives
be implemented so that only the designated Media Agents can detect and control the devices. This
will minimize unnecessary monitoring and access to the devices from non-designated computers.
The Basic SAN Setup

A Storage Area Network (SAN) is a Fibre Channel network that is dedicated to carrying backup data. SAN enhances backup
and restore performance and eases congestion on an enterprise's Local Area Network (LAN), freeing it for normal business
activities and communication. You can configure your SAN environment to take advantage of the Dynamic Drive Sharing
(DDS) feature to share drives among multiple MediaAgents in a CommCell within a SAN environment.
Basic SAN components include:
z Host Bus Adapter (HBA)
Each computer that is attached to a fibre network needs a special adapter, an HBA, that can send and receive signals
across Fibre Channel cables.
z Bridge, Router or Gateway
These pieces of equipment translate fibre signals to signals that can be understood by SCSI devices (fibre-to-SCSI
communications) and vice versa. A gateway can also communicate between a Fibre Channel network and native fibre
devices (fibre-to-fibre communications). Bridges, routers, and gateways are used to connect servers and storage devices
to the SAN.
z Hub
In a Fibre Channel Arbitrated Loop (FC-AL) (see below), the hub is the fault-tolerant center of the network to which
servers and storage devices are connected.
z Switch
In the more complex network environment of switched fibre (see below), the switch is the center of the fabric, or
infrastructure, of the network. Servers and storage devices are connected to the switch, which is more intelligent and
has more bandwidth than a hub.
There are two basic SAN configurations:
Page 20 of 41
z Fibre Channel Arbitrated Loop (FC-AL)

This configuration is logically equivalent to a logical ring of fibre to which all of the devices are connected. FC-AL is
implemented by connecting devices to a hub. Bandwidth and storage resources on the network are pooled and shared by
all devices
z Switched Fibre
In a switched configuration, virtual loops are established between hosts and backup devices. Each host may have
exclusive use of its virtually attached storage devices.
Back to Top
SAN Addressing Overview

In order for backup devices to be available to the MediaAgent, the system must know which physical device is mapped to a
given SCSI address. When a MediaAgent is directly attached to a storage device, the SCSI address is determined by the
physical SCSI connection. SAN adds a Fibre Channel (FC) network between the MediaAgent and the SCSI backup device.
However, the MediaAgent and the backup device still use the SCSI protocol to communicate across the FC network.
Consequently, the MediaAgent still needs to be able to associate each physical device with a SCSI address.
A SCSI address includes three identifiers. The table below lists the components of a SCSI address and its counterparts in
the switched fibre and FC-AL addressing schemes.
Page 21 of 41
* Conceptually, both a loop and fabric represent collections of addressable devices. In practice, this part of the address is
generally the same as the port number of the HBA that connects the host to the FC network.
Back to Top
SCSI-LUN Mapping Guidelines for SAN Libraries

See the hardware manufacturer’s documentation for instructions on setting SCSI targets for
storage devices and SCSI-to-FC address mapping for SAN routers.
LUN guidelines must be followed in order for the system to function properly. SCSI target
guidelines are recommendations that can make system administration easier, but they are not
requirements.
Back to Top
SCSI Target Guidelines

Observe the following guidelines when assigning SCSI targets to storage devices attached to a SAN:
z Assign each media changer to a SCSI target lower than the targets of its drives.
z When setting the SCSI targets, you should assign SCSI target numbers in ascending order in accordance with the
physical drive location. The drive with the lowest physical address (e.g., Drive 0) gets the lowest SCSI target. The drive
with the highest physical address (e.g., Drive 4) gets the highest SCSI target. Drives in between are assigned
sequentially. A good convention to use, when possible, is to set the library media changer to 0, the first drive to target
1, the second drive to target 2, and so on.
Physical drive locations are numbered differently depending on the library. The first
drive in one library may be 0 while in another library it may be 1. See the
manufacturer’s documentation for details on your library.
z If multiple SCSI ports are to be attached to a single library, you should attach the SCSI ports in order of the physical
device sequence. For example, connect the first SCSI port to the media changer and drives 1 and 2; the next SCSI port
to drives 3 and 4, and so on.
z Try to assign a unique SCSI target to each device, even for devices on different SCSI ports. Doing so can make it easier
to identify the drives later, should that become necessary.
Back to Top
Fibre Channel LUN Guidelines

Observe the following guidelines when assigning fibre channel LUNs to storage devices attached to a SAN:
z Assign each media changer to a LUN lower than the LUNs of its drives. Otherwise, drives may be associated with the
wrong library or incorrectly detected as stand-alone drives.
z For each router, assign LUNs starting with zero and continue in ascending sequence. Do not skip any numbers in the
Page 22 of 41
sequence.
The following illustrations provide several scenarios that demonstrate these guidelines.
Single Router, Multiple Library Configuration
Moving from left to right, the diagram depicts the following: A MediaAgent contains an HBA that connects it, via a fibre
channel switch to a SAN router. Within the fibre network, SAN devices are addressed by fibre channel LUNs, which are set
through the LUN mapping interface provided by the manufacturer of the router. The router is connected via SCSI buses and
cables to two libraries. Within the libraries, each device has a SCSI target, which is set via the interface provided by the
manufacturer of the library.
SCSI Target
When assigning SCSI targets, target 0 is assigned first with the rest in ascending order. The lowest target within the library
is assigned to the library’s media changer. If the library has additional drives, target 7 would be skipped, because the SCSI
controller uses SCSI ID 7 by default, and the assignments continue with target 8.
LUN
When assigning fibre channel LUNs, we started at 0 and assigned contiguous LUNs in ascending order. The diagram only
depicts those aspects of the SCSI and FC addresses that are commonly configured by the user. The tables below show the
complete address translations that are performed by the router between SCSI addresses (Bus, Target, LUN) and fibre
channel addresses (Loop, AL_PA, LUN), and the reverse translations that are performed by the MediaAgent’s HBA. The left-
most SCSI addresses are the ones by which the SAN devices are identified in the Library and Drive Configuration
window. See Library and Drive Configuration for additional information on configuring libraries and drives in the Library
and Drive Configuration window. For details on SCSI and FC addressing schemes, see SAN Addressing Overview above.
Note that values of zero have been assigned to Loop, AL _PA, and the SCSI bus and target in the address on the left. The
actual values depend on the SAN configuration.
Back to Top
Multiple Router, Single Library Configuration
Page 23 of 41
This configuration can maximize performance for a library containing many drives. Moving from left to right, the diagram
depicts the following: A MediaAgent contains an HBA that connects it via a Fibre Channel network to a SAN switch. The
switch is connected to two SAN routers. Within the fibre network, SAN devices are addressed by Fibre Channel LUNs, which
are set through the LUN mapping interface provided by the manufacturer of the router. The router is connected via SCSI
buses and cables to a single library containing six drives. Within the library, each device has a SCSI target, which is set via
the interface provided by the manufacturer of the library.
SCSI Target
When assigning SCSI targets, we started at target 0 and went in ascending order. We assigned the lowest target within the
library to the library’s media changer. Note that if the library had additional drives, we would skip target 7 and continue
with target 8.
LUN
When assigning Fibre Channel LUNs, we started at 0 and assigned contiguous LUNs in ascending order. We restarted LUN
numbering with the second router. The diagram depicts only those aspects of the SCSI and FC addresses that are
commonly configured by the user. The tables below show the complete address translations that are performed by the
router between SCSI addresses (Bus, Target, LUN) and Fibre Channel addresses (Loop, AL_PA, LUN), and the reverse
translations that are performed by the MediaAgent’s HBA. The left most SCSI addresses are the ones by which the SAN
devices are identified in the Library and Drive Configuration window. For more information on configuring SAN devices
using the Library and Drive Configuration window, see SAN-Attached Libraries. Each router is represented in the
addresses on the left as a separate SCSI target. For details on SCSI and FC addressing schemes, see SAN Addressing
Overview above.
Note that in the tables below, values have been assigned to Loop, AL_PA, and the SCSI bus and target in the address on
the left. The actual values depend on the system configuration.
Back to Top
Avoiding Common Errors

In setting up a SAN for use by a MediaAgent, the essential goal is to ensure that each physical device is represented in the
CommCell by one, and only one, SCSI address, (bus, target and LUN) and that this SCSI address remains consistent
Page 24 of 41
through all layers of the SAN, at all times. If a single device is represented by multiple SCSI addresses, or if multiple
instances of a single address for a device exist within the network, resource contention can occur as different MediaAgents
attempt to use the same drive simultaneously.
Avoiding Dynamic Address Changes
A fibre channel address can change at either the AL_PA/ Port_ID level or at the LUN level. In either case, the HBA
translated SCSI address of affected devices changes as well. If the SCSI address of a configured device changes, the
MediaAgent will be unable to access the device. The sections that follow tell you how to maintain address stability within
your SAN.
AL_PAs and Port_IDs
AL_PAs and Port_IDs can be set in one of two ways:

z Hard addressing
This addressing scheme requires that you manually set switches on a device to assign it a permanent AL_PA. (A Port_ID
includes the AL_PA plus information about the fabric port to which the device is attached.)
z Soft addressing
If you use this scheme, AL_PAs are automatically assigned to fibre devices (e.g., routers, gateways, HBAs, etc.) when
they are attached to the network. However, if devices are added or removed, the addresses of other devices in the
network may be reassigned, rendering these devices inaccessible to the MediaAgent. If the AL_PA of a router changes,
all attached libraries become inaccessible to the MediaAgent. Note that soft addresses may be assigned even when you
use hard addressing. If the switches on two devices are set for the identical AL_PA, then the first device detected by the
network is assigned that address, while the second device is assigned a soft address.
To ensure that AL_PAs won’t change, use hard addressing and make sure that each device is
assigned a unique AL_PA. To ensure that Port_IDs won’t change, follow the AL_PA guidelines. In
addition, do not change the fabric ports of configured devices.
Some gateways do not work well with fibre channel switches unless you enable soft addressing.
Also some of the SAN gateways do not allow you to disable soft addressing. Enable soft addressing
in both these circumstances.
LUNs
Fibre channel LUNs are set by bridges, routers and gateways, which translate the SCSI addresses (SCSI port, target, and
LUN) of attached devices to fibre channel addresses. Routers have two addressing modes:
z Manual
This addressing scheme requires that you manually set the LUN for each device that is attached to the router.
z Automatic
In this addressing scheme, the router automatically assigns LUNs to attached devices. However, if devices are added or
removed, the addresses of other attached devices may be reassigned. Consequently, the MediaAgent is unable to access
the device. Note that LUNs must start from zero. They must also be sequential and contiguous (not skipping numbers).
To ensure that the LUNs of devices attached to a router won’t change, use manual addressing.
Make sure that each device is assigned a unique LUN, and that LUNs start from zero and are
sequential and contiguous. When you first configure your SAN, you may want to use automatic
addressing to ensure that LUNs meet these criteria. You can then switch to manual mode to set
the same addresses that were automatically assigned by the router.
Back to Top
SAN Configuration Summary

The following items summarize the SAN configuration issues that can impact the ability of the MediaAgent to successfully
detect and use SAN storage devices:
z All MediaAgents attached to a SAN must use the same brand and model HBA, as well as the same driver and firmware
revisions; all routers must also be of the same brand and model. This ensures that the same fibre channel-to-SCSI
address translation is used for all devices in the SAN.
z The latest available version of firmware and device drivers must be used.
z Use hard addresses rather than soft addresses to ensure that AL_PAs and Port_IDs will not change.
z Make sure that each device is assigned a unique AL_PA.
z Do not change the fabric port of configured devices that are attached to a switched network.
z Be careful to preserve the sequential, contiguous order, starting at 0 (assumed by operating systems) when you set
Page 25 of 41
AL_PAs in manual mode.

z Use manual addressing mode to prevent SAN routers from changing LUNs when the SCSI configuration changes.
z For easier system administration, follow SCSI configuration guidelines above when setting SCSI targets for storage
devices.
Back to Top
Page 26 of 41
DISC Optical Library Configuration
The DISC Optical Library must be attached to a MediaAgent running on a Windows 2000 or Windows 2003 Server
computer. The library can be connected through either an Adaptec or a Qlogic ultra SCSI differential card. We recommend
to connect no more than four drives per SCSI card. Observe the following guidelines while configuring this library:
z The latest firmware version should be loaded to the library.
z For DISC libraries, use the library front panel to set library System Options (both I/E Unit Atten and MB Def. Open) to
Yes. When equipped with a barcode reader set Module Options: Barcode ON.
z Use all optical drives with the same speed and optical cartridges of same capacity.
z Do not set the data-protect tab on any cartridge. Setting the data-protect tab will fail all operations on the cartridge.
z Disable RSM as described in Driver Configurations.
Page 27 of 41
ACSLS Library Configuration
Select a topic:
z Overview
z Direct-Attached Library Configuration
z Direct-Attached Library Configuration with SN6000
z DDS Configuration
z DDS Configuration with SN6000
Overview
StorageTek libraries controlled by an ACSLS Server can be configured. Such ACSLS controlled StorageTek libraries can be
shared between:
z Multiple MediaAgents in a CommCell
z Multiple CommCells, or
z CommCells and others applications like Vault 98, etc.
Note that the ACSLS server computer can also be a component (either a MediaAgent or an agent) of the CommCell. The
system can share a StorageTek (STK) library with Vault98 or other applications that are accessing the STK library via
ACSLS server.
Software Versions
The following software versions are supported in the various components:
Component Software Version

ACSLS Server on Solaris 6.0, 6.1, 6.1.1, 7.0 or 7.1
STK Library Manager on Windows 2.0
MediaAgents - Windows (including Windows NT
Cluster)
Windows 2000
Windows 2003 Server (32 bit)
See System Requirements - MediaAgent for information on the platforms supported
by MediaAgents.
MediaAgents - Solaris (including 32 bit - 2.7 (Solaris 7), 2.8 (Solaris 8) 2.9 (Solaris 9) and Solaris 10
Cluster)
64 bit - 2.7 (Solaris 7), 2.8 (Solaris 8), 2.9 (Solaris 9) and Solaris 10
Solaris 8 32-bit and 64-bit Sun Cluster
See System Requirements - MediaAgent for information on the platforms supported
by MediaAgents.
Library Attach for Windows 1.2 , 1.3 or 1.4
Within a CommCell, depending on the environment, the MediaAgents can be configured to access the StorageTek library
controlled by an ACSLS Server using one of the following configurations:
z Direct-attached library configuration.
z Dynamic Drive Sharing (DDS) configuration in the SAN environment.
In both the cases you can also have storage virtualization hardware, such as StorageTek SN6000.
The following sections describe the hardware setup for each of these configurations.
Direct-Attached Library Configuration

In a direct-attached library configuration, the Windows or Solaris MediaAgents can be configured to use the StorageTek
library controlled by ACSLS server: For the Windows MediaAgent, you must install an instance of StorageTek’s Library
attach for Windows program on the MediaAgent computer in which the StorageTek library will be configured. (See Software
Versions for information on the supported versions.)
Page 28 of 41
For the Sun Solaris MediaAgent, the ACSLS Client Service must be installed on the MediaAgent computer. This software is
available in the QiNetix Installation CD and can be installed during the MediaAgent installation. (See Installing ACSLS Client
Service on Solaris for more information on installing this software.)
The ACSLS server is connected to the library’s media changer with a direct SCSI. Each MediaAgent communicates with the
ACSLS server through the TCP-IP port. In addition, each MediaAgent must also be attached to the drive(s) in the library
using SCSI ports.
Within the StorageTek libraries, some or all drives must be assigned to the MediaAgents for
exclusive use by the CommCell. The unassigned drives will be available for other applications or
another CommCell.
The following diagrams provide an overview of the hardware configuration required for configuring the StorageTek library
using the ACSLS Server in the QiNetix system:
Back to Top
Direct-Attached Library Configuration with SN6000
Page 29 of 41
The ACSLS server is connected to the library’s media changer with a direct SCSI. Each MediaAgent communicates with the
SN6000 through the TCP-IP port. In addition, each MediaAgent must also be attached to SN6000 using Fibre Channel
cables. The SN6000 is connected to all the drives in the library through Bridge/Router using Fibre Channel cables.
The following diagram provides an overview of the hardware configuration required for configuring the StorageTek library
using the ACSLS Server in the system with StorageTek SN6000:
Back to Top
DDS Configuration
In a DDS configuration, all MediaAgents can be configured provided you have at least one of the Windows or Solaris
MediaAgent. (See Software Versions for information on the supported versions.)
This primary MediaAgent must have the following software:
z If the primary MediaAgent is a Windows MediaAgent, you must install an instance of StorageTek's Library attach for
Windows program on the MediaAgent computer.
z If the primary MediaAgent is a Sun Solaris MediaAgent, the ACSLS Client Service must be installed on the MediaAgent
computer. This software is available in the QiNetix Installation CD and can be installed during the MediaAgent
installation. (See Installing ACSLS Client Service on Solaris for more information on installing this software.)
The ACSLS server is connected to the library’s media changer with a direct SCSI. In addition, the primary MediaAgent must
also be attached to the ACSLS server through the TCP-IP port. Each MediaAgent in the CommCell communicates with the
drives in the library through the following:
z MediaAgent to Bridge/ Router/ Gateway using SCSI ports.
z Bridge/ Router/ Gateway to a SAN switch using Fibre Channel cable.
z SAN switch is connected to all the drives in the library using Fibre Channel cables.
The following diagram provides an overview of the hardware configuration required for sharing a StorageTek library among
multiple MediaAgents with DDS configuration.
Page 30 of 41
Back to Top
DDS Configuration with SN6000

The ACSLS server is connected to the library's media changer with a direct SCSI. In addition, the primary MediaAgent must
also be attached to the ACSLS server and SN6000 through the TCP-IP port. Each MediaAgent in the CommCell
communicates with the drives in the library through the following:
z MediaAgent to Bridge/ Router/ Gateway using SCSI ports.
z Bridge/ Router/ Gateway to SN6000 using Fibre Channel cable.
z SN6000 to a SAN switch using Fibre Channel cable.
The following diagram provides an overview of the hardware configuration required for sharing a StorageTek library among
multiple MediaAgents with DDS configuration using SN6000.
Page 31 of 41
Back to Top
Page 32 of 41
ADIC Libraries Attached to Scalar Distributed Library Controller (SDLC)

Configuration
Select a topic:
z Software Requirements
z Hardware Configuration
{ Direct-attached library configuration
{ DDS Configuration
Software Requirements
The following software versions are supported in the various components:
Component Software Version

MediaAgents - Windows Windows 2000
Windows 2003 Server (32 bit)
Scalar Distributed Library Controller (SDLC) 2.5
DAS Client software 3.12
ADIC library ADIC 1000 (or above)
The media changer should be attached to the computer in which the SDLC software is installed. Depending on your
configuration some or all the drives may be attached to this computer. If the library is shared among several MediaAgents,
you must install the DAS Client software on all the MediaAgent computers in which the library will be configured.
Hardware Configuration
Within a CommCell, depending on the environment, the MediaAgents can be configured to access the ADIC library
controlled by a Scalar Distributed Library Controller (SDLC) using one of the following configurations:
z Direct-attached library configuration.
z Dynamic Drive Sharing (DDS) configuration in the SAN environment.
Direct-attached library configuration

The SDLC is connected to the library’s media changer with a direct SCSI. Each MediaAgent communicates with SDLC
through the TCP-IP port. In addition, each MediaAgent must also be attached to the drive(s) in the library using SCSI ports.
Within the library, some or all drives must be assigned to the MediaAgents for exclusive use by the
CommCell. The unassigned drives will be available for other applications or another CommCell.
The following diagrams provide an overview of the hardware configuration required for configuring the ADIC library using
SDLC in the QiNetix system:
Page 33 of 41
DDS Configuration
In a DDS configuration, the SDLC is connected to the library’s media changer with a direct SCSI. Each MediaAgent in the
CommCell communicates with the SDLC and the drives in the library through the following:
z MediaAgent to Bridge/ Router/ Gateway using SCSI ports
z Bridge/ Router/ Gateway to a SAN switch using Fibre Channel cable.
The following diagram provides an overview of the hardware configuration required for sharing an ADIC library among
multiple MediaAgents with DDS configuration.
Page 34 of 41
Back to Top
Page 35 of 41
Guidelines for Attaching Hardware Used by NAS to a SAN

z Overview
z BlueArc
z EMC Celerra
z NetApp
Overview
Refer to the following for additional information:
z SAN Configuration
z SAN-Attached Libraries
For the EMC Celerra and NetApp NAS NDMP iDataAgents, both the MediaAgent and/or a NAS file server can be attached to
a SAN.
Observe the following guidelines if the library used by a NAS NDMP iDataAgent is attached to a SAN network.
BlueArc
The following is an example of a BlueArc SAN configuration:
The above is an example only. If your configuration is different, refer to BlueArc documentation.
SAN Hardware Guidelines
Any library connected to a BlueArc file server must be connected to the hub on the BlueArc via Fiber Channel. This is the
same hub to which that the BlueArc's processor and RAID arrays are connected.
z If the library is connected to the file server via a bridge/router, it is recommended that you use Brocade hardware.
z It is recommended that the user only connect one library to the file server.
z For instructions on making the BlueArc file server see the library after they are connected, refer to BlueArc
documentation.
EMC Celerra
EMC Celerra file servers can be connected to libraries through the Fibre Channel (FC) switch in a Storage Area Network
(SAN). The FC switch allows multiple EMC Celerra NAS NDMP iDataAgents to be connected to the drives in a library at the
same time.
In the case of such EMC Celerra clients, the file server must contain a fiber channel card to allow it to communicate over a
fibre channel connection to a fibre channel switch certified by EMC Celerra. The library can communicate to the fibre switch
through a bridge or fibre channel card.
The following is an example of an EMC Celerra SAN configuration:
Page 36 of 41
You must follow the EMC Celerra configuration when you are setting up to use SAN. The hardware guidelines for a EMC
Celerra SAN configuration can be found at: www.emc.com
Input the following text in the search field and click Search.
Celerra Interoperability Matrix.pdf
Select the Celerra Interoperability Matrix displayed in the results list.
If you are using a EMC Celerra file server, you will need information on assigning the user name
and password to NDMP-host Data Movers. This can be found in the EMC Celerra File Server Backup
Guide, Version 2.2. Additionally, if you are not using EMC Celerra OS 4 (e.g., EMC Celerra OS
2.2.49), you must contact EMC Celerra Technical Support to change your NDMP password.
NetApp
As with EMC Celerra file servers, NetApp file servers can be connected to a library through the Fibre Channel (FC) switch in
a Storage Area Network (SAN). The FC switch allows multiple NetApp NAS NDMP iDataAgents to be connected to the drives
in a library at the same time.
In the case of such NetApp NAS NDMP iDataAgents, the file server must contain a NetApp fibre channel card to allow it to
communicate over a fibre channel connection to a fibre channel switch certified by Network Appliance. The library can
communicate to the fibre switch through a bridge or fibre channel card.
The following is an example of a NetApp SAN configuration:
Page 37 of 41
You must follow the NetApp certification matrices configuration when you are setting up to use SAN.
The hardware guidelines for a NetApp SAN configuration can be found at the Certification Matrices page on the NetApp web
site: www.netapp.com.
Back to Top
Page 38 of 41
Obtaining Information from a NAS File Server

z Overview
z BlueArc
z EMC Celerra
z NetApp
Overview
Certain configuration procedures will require that you supply information about the NAS File Server; information is provided
below to help you obtain this information.
Obtaining Information from the BlueArc File Server

Obtaining the NAS NDMP Server Device Name
The NAS NDMP server device name is actually the name of the media changer device.
Refer to documentation provided by the BlueArc Corporation to determine the server device names
for the media changers and drives.
Back to Top
Obtaining Information from the EMC Celerra File Server

Obtaining NDMP Server Device Name and NDMP Drive Access Path
The NDMP Server Drive Path is the path through which the EMC Celerra file server communicates with NDMP drives. This
communication is necessary when backup and restore operations are being performed. The best method to provide this
information is to run auto detection on the NAS file server. See Configure a library and drives attached to the NAS file
server using automatic detection. If instead you want to add this information manually, follow the steps below.
To obtain the NDMP Server Device Name and the NAS NDMP Drive Access Path
1. Verify that the Data Mover’s TLU devices were added to the EMC Celerra file server database by entering the
server_devconfig command. A sample command would look like this:
server_devconfig server_2 -l -s -n,
where server_2 is the EMC Celerra file server name for the Data Mover.
This Data Mover is addressed directly by its NIS or DNS (Domain Name Service)
name.
You must enter the command in lowercase letters, as the command is case sensitive. The -l is the letter “L” (in
lowercase) and stands for list, -s for scsi, and -n for nondisk. To retrieve information for all the servers, type the
command:
server_devconfig ALL -l -s -n.
2. The SCSI Device Table is displayed. A sample table would appear as follows:
name addr type info
ATL P1000
jbox1 clt010 jbox
62200501.21
QUANTUM DLT7000
tape2 clt410 tape
245Fg_
QUANTUM DLT7000
tape3 clt510 tape
245Fg_
Page 39 of 41
If you entered the ALL command for all the servers, a separate SCSI Device Table will be displayed for each server,
with the server name at the top.
The table provides:
{ The name of the drive which is connected to the file server.
{ The access path for the tape drive (in the addr column). This is the device path name you must use to access a tape
drive on the file server.
{ The type of drive being used.
{ The name, product and serial number of the device.
3. Type the name of the device path in the NDMP Server Drive Path field in the Add NDMP Drive window.
Back to Top
Obtaining Information from the NetApp File Server

This section describes the NetApp procedures for obtaining the NAS NDMP server device names and drive access paths.
This information is NetApp-specific and is subject to change.
Obtaining the Device Name of Media Changer
1. Use either the web-based administration GUI, file server console, or telnet session to issue commands on the file
server.
2. Run the sysconfig -m command from the file server’s console or telnet session. This should display the media
changers device name, similar to the information displayed in the following screen.
In this example, the NDMP server device name is mc0.
Obtaining the Drive Access Path

The NAS NDMP Server Drive Path is the path through which the NetApp file server communicates with NDMP drives. This
communication is necessary when backup and restore operations are being performed. You must have the path available
when you are adding NDMP drives.
1. Use either the web-based administration GUI, file server console, or telnet session to issue commands on the file
server.
2. Run the sysconfig -t command from the file server’s console or telnet session. This should display the tape drive
access path information, similar to the information displayed below. Note that this file server has three drives attached
to it
Page 40 of 41
.
3. You need to select one of the available tape devices which are prefixed with the character “n” and indicated as no
rewind device. This indicates that when an application closes the tape device, it will not automatically rewind the tape.
This is an important requirement. Each tape drive is also suffixed with one of the following density modes used to write
to a tape:
“l” for low density

“m” for media density
“h’ for high density
“a” for high density with hardware compression
The number refers to the instance - zero normally corresponds to the first tape drive.
4. For a library which is directly attached to a NetApp file server, the drives can be configured using the prefixes listed
under Tape Drives with <0b.1> suffix.
For a library in a SAN environment, the drives can be configured using the prefixes listed under the Tape Drives with
the <6.6L> suffix.
NetApp NAS NDMP iDataAgent only supports no rewind device configurations.
Back to Top
Page 41 of 41
CommVault® Systems, Inc.
2 Crescent Place
P.O. Box 900
Oceanport, NJ 07757-0900
Phone: (732) 870-4000
Web: www.commvault.com

Pre Install Commvault

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Pre Install Commvault

Hochgeladen von

Copyright:

Verfügbare Formate

® ™

Software Version 6.1.0

Data & Storage

Printed in the United States of America

End User License and Limited Warranty Agreement

CommVault® Software Release 6.1.0

End User License Agreement

United States Government and DOD

3. General Hardware Configuration

5. Direct-Attached Library Configuration

7. DISC Optical Library Configuration

9. ADIC Libraries Attached to Scalar Distributed Library Controller (SDLC) Configuration

10. Configuring Libraries Attached to a NAS File Server

{ One or more MediaAgentsTM

Common Technology Engine

Software Installation Discs

No. Title Contents

MediaAgent (AIX, HP-UX, Linux, Solaris and Tru64)

No. Title Contents

No. Title Contents

Select the desired topic:

Domain Name Server (DNS) environment

WINS or other Non-DNS Environment

Proper name/IP address resolution is essential to reliable network communications.

General Hardware Configuration

Select the desired topic:

Libraries, Drives and Media

SCSI Cabling and Adapters

Select the desired topic:

From this window:

Windows 2000 and Windows 2003 Server

1. Do one of the following:

1. At the Unix prompt type sam.

1. At the Unix prompt type smit.

Viewing SCSI Adapters

1. At the Unix prompt type:

A list of all SCSI adapters available in the system are displayed.

A list of devices connected to the NetWare server are displayed.

Using the Terminal

4. Open the following file:

5. The SCSI devices attached to the computer should be listed.

Direct-Attached Library Configuration

Select the desired topic:

SCSI Ports and SCSI Targets

Single SCSI Configuration Guidelines

Stand-alone drives do not have media changers.

Single Library Setup

Multiple SCSI Configuration Guidelines

Single Library, Two Stand-Alone Drives Setup

Single Library Setup

Multiple Library Setup

The Basic SAN Setup

z Fibre Channel Arbitrated Loop (FC-AL)

SAN Addressing Overview

SCSI-LUN Mapping Guidelines for SAN Libraries

SCSI Target Guidelines

Fibre Channel LUN Guidelines

Multiple Router, Single Library Configuration

Avoiding Common Errors

AL_PAs and Port_IDs can be set in one of two ways:

SAN Configuration Summary

AL_PAs in manual mode.

DISC Optical Library Configuration

ACSLS Library Configuration