Quantum SDLC 2.6 User Manual

Page 1
m
®
Scalar
Distributed Library Controller
Installation Guide
2.6
ADVANCED DIGITAL INFORMATION CORPORATION
www.adic.co
Page 2
Copyright © 2006 ADIC
The information contained in this document is subject to change without notice.
This document contains proprietary information which is protected by copyright. All rights are reserved. No part of this document may be reproduced, modified, distributed, or translated to another language without prior written consent of ADIC.
ADIC USA 11431 Willows Road NE Redmond, Washington 98052-4952 Tel.: 1-800-336-1233 Fax: 1-425-881-2296
This document may describe designs for which patents are pending, or have been granted. By publishing this information, ADIC conveys no license under any patent or any other right.
ADIC shall not be liable for errors contained herein or for incidental or consequential damages (including lost profits) in connection with the furnishing, performance or use of this material whether based on warranty, contract, or other legal theory. ADIC makes no representation or warranty with respect to the contents of this document and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Further, ADIC reserves the right to revise or change this document without obligation on the part of ADIC to notify any person or organization of such revision or change.
Every effort has been made to acknowledge trademarks and their owners. All trademarks within this document are the property of their respective owners. Trademarked names are used solely for identification or exemplary purposes, and any omissions are unintentional. ADIC is a registered trademark of Advanced Digital Information Corporation.
Installation Guide
Published: May 2006 Document Number: 6-00659-03 Rev. A
Page 3
Table of Contents
1 About This Guide and Your Product 1
Explanation of Symbols and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Other Documents You Might Need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Getting More Information or Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 System Description 3
Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Standard Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Failover Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Self-Domain Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Compatibility Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 Setting Up the Scalar DLC 7
Setting Up the Standard Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Single-aisle Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Dual-aisle Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Setup Roadmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Collecting Setup Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Setting Up the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Installing the Scalar DLC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Configuring the Logical Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Setting Up the Failover Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Single-aisle Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Dual-aisle Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Setup Roadmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Collecting Setup Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Installing the Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Installing ADTX RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring SCSI for RAID and Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Setting Up IP Address, Node Name, and Joining Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Setting Up the RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuring Cluster Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Installing Scalar DLC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Configuring the Logical Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Post-install checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Installation Guide iii
Page 4
Setting Up the Self-Domain Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Setup Roadmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Collecting Setup Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Installing the Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Installing ADTX RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Configuring SCSI for RAID and Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Setting Up Network, IP Address and Computer Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Configuring Domain Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Setting Up the RAID disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Configuring Cluster Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Installing Scalar DLC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Post-install Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Common Setup Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4 Installing the Scalar DLC 45
Solution Checkup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Windows Service Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Microsoft Internet Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Java 2 Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Apache HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Microsoft SQL Server Desktop Engine 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
MSDE 2000 Service Pack 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Scalar DLC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5 DAS Client 65
Installing DAS Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Installing the DAS Administration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Installing the DAS/ACI Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Removing DAS Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6 SCSI/FC Target Drivers 71
SCSI and Fibre Channel Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Two-channel Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Initiator Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Installing the SCSI/FC Target Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Activating Target Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Add/Remove SCSI Target Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
7 Upgrade, Remove, Repair 81
Add/Remove Scalar DLC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Repair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Upgrading the Scalar DLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
iv Table of Contents
Page 5
Using Database from a Previous Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Upgrading from 2000 to 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Simple Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Advanced Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Upgrade Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Installing Scalar DLC Service Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Renaming and Repair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Change Cluster IP Address and Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Change Scalar DLC Node Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Change Cluster Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Replacing Old RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Startup and Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Back up Scalar DLC Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Restore Scalar DLC Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Updating Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Failure Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Downgrading the Scalar DLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
8 Troubleshooting 117
Troubleshooting Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Scalar DLC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Scalar DLC Database Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Scalar DLC Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
SCSI and Fibre Channel Target Mode Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Client Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Force Restart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Scalar DLC Force Removing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
A Advanced Setup Instructions 123
Setting Up the Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Host/Library Communication using Fibre Channel and SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
SNC Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Standard Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Failover and Self-Domain Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Building Client Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
DAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
SCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
ROBAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Installing SCSI/FC Target Adapters on a Live Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Securing the Scalar DLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Antivirus Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Installation Guide v
Page 6
vi Table of Contents
Page 7

About This Guide and Your Product

This manual contains reference information and instructions for setting up, installing, and upgrading the Scalar Distributed Library Controller (Scalar DLC) software. This guide is intended for customers, customer engineers, and administrators who use the Scalar DLC software.

Explanation of Symbols and Notes

The following symbols appear throughout this document to highlight important information.
WARNING
CAUTION
Note
INDICATES A POTENTIALLY HAZARDOUS SITUATION WHICH, IF NOT AVOIDED, COULD RESULT IN DEATH OR BODILY INJURY.
Indicates a situation that may cause possible damage to equipment, loss of data, or interference with other equipment.
Indicates important information that helps you make better use of your system.

Other Documents You Might Need

The following documents are also available for this product. These documents can be found on the product
CD or at www.adic.com/manuals
Scalar DLC Installation Guide
Scalar DLC Release Notes (6-00335-xx)
DAS Administration Guide (6-00345-xx)
:
DAS/ACI Interfacing Guide (6-00346-xx)
Scalar 10K SCSI Reference Guide
Scalar 1000 SCSI Reference Guide
Scalar DLC Installation Guide 1
Page 8
SCSI Primary Commands 2 (SPC-2)
SCSI Primary Commands 3 (SPC-3)
ROBAR Interfacing Guide
Scalar 10K Operator Guide
Scalar 1000 Operator Guide
RMU Reference Guide

Getting More Information or Help

More information about this product is available on the Customer Service Center website at
www.adic.com/csc
frequently asked questions (FAQs). You can also access software, firmware, and drivers through this site.
For further assistance, or if training is desired, contact ADIC:
ADIC Technical assistance center (ATAC) in the USA: 800-827-3822
ADIC Technical assistance center (ATAC) in Europe and Japan: 00-800-9999-3822
For additional contact information: www.adic.com/contact
To open a Service Request: www.adic.com/techsup
. The Customer Service Center contains a collection of information, including answers to
2 About This Guide and Your Product
Page 9

System Description

The Scalar DLC software runs as a service under Windows 2000 / 2003. It serves as a centralized library management tool that simplifies and automates the tracking and management of all system resources for optimal performance and maximum availability. The Scalar DLC software provides network and Systems Administrators with a Java-based interface that allows library monitoring from anywhere on the Web.
Note
It also allows administrators to select parameters that define which library events provide notifications to customers and ADIC Technical Assistance Center (ATAC) via email and Simple Network Management Protocol (SNMP) alerts.
The main working tool of the Scalar DLC software is the Management GUI. All the actions of management and configuration are executed via this tool. Refer to the Scalar DLC Reference Guide for the details.
Figure 1
Figure 1 Scalar DLC Structure
illustrates the structure of a typical Scalar DLC system.
If a firewall is being used, outside access by Web browsers might be denied.
Figure 2
Installation Guide 3
on page 4 illustrated the data flow and the Scalar DLC components.
Page 10
Figure 2 Scalar DLC Components
As shown on Figure 2 host (server) via the client interface; several interfaces are used (SCSI/FC, DAS, and ROBAR).
Depending on the request, the Scalar DLC either should search the information in the database and send the response back to the client, or transfer the command to the library via the library interface.
After the library has executed the requested operation, the response is sent back to the Scalar DLC indicating that the operation was executed.
The Scalar DLC server updates the database according to the information received from the library and transfers the response (operation executed) back to the client.
The Management GUI serves as the configuration tool to create a working configuration for clients, and also as the monitoring tool for the Administrator when it is necessary to watch the system activity.
The details for using Management GUI and other tools of the Scalar DLC software are described in the Scalar DLC Reference Guide.
, the client (user/backup application) sends the request/command to the Scalar DLC

Platforms

The Scalar DLC software can be installed on the operating systems (platforms) listed in Table 1.
Table 1 Scalar DLC platforms
OS/Platform
32-bit Windows Server 2003 Enterprise Edition SP1 Windows 2003 Server
32-bit Windows Server 2003 Standard Edition SP1 Windows 2003
Windows 2000 Advanced Server SP4 Windows 2000 Advanced
Windows 2000 Server SP4 Windows 2000
Windows 2000 Professional SP4 Windows 2000
The OS update with the required hot fixes and/or service packs is performed on regular basis, see Securing
the Scalar DLC on page 135.
4 System Description
Service
Pack
Referred as
Server
Page 11

Solutions

According to the customer requirements, the Scalar DLC introduce a basic (standard) solution or a failover (redundant, cluster) solution. The latter can be provided in plain version and in self-domain version, also called the self-domain solution. See S
Domain Solution on page 6.
Depending on the library used by the customer, the solution and system configuration should be selected, as shown in Table 2
Table 2 Libraries, Solutions, and OS
Library Scalar DLC Solution OS/Platform
Scalar 1000 Failover / Self-domain Windows 2000 Advanced Server
Scalar 10K Failover / Self-domain Windows 2000 Advanced Server
.
Standard Windows 2000 (all platforms)
Standard Windows 2000 (all platforms)
tandard Solution on page 5, Failover Solution on page 5, and Self-
Windows 2003 Server
Windows 2003 (all platforms)
Windows 2003 Server
Windows 2003 (all platforms)
Scalar 10K dual-aisle (DA)
Failover / Self-domain Windows 2000 Advanced Server
Windows 2003 Server
Standard (only as an exception) Windows 2000 (all platforms)
Windows 2003 (all platforms)

Standard Solution

The Scalar DLC standard (basic) solution keeps all Scalar DLC components (server, database) on a single host / PC that is connected to both the library and client(s). The client can work with the library when the Scalar DLC software is started and the library is online.
The Scalar DLC standard solution requires a single PC, the library, and the interface cables to provide the connection between PC (Scalar DLC host) and library. Additional cabling may be required to provide the client connections (SCSI/FC) and using SNC.
For the requirements and installation instructions see Setting Up the Standard Solution
on page 7.

Failover Solution

The Scalar DLC Failover (redundant, cluster) solution is provided for the clients using the Microsoft Cluster service. This solution allows the user to have a shared disk with the Scalar DLC database and two hosts containing the installed components of Scalar DLC software; for the redundancy reasons, one host is online and the other is offline. If an error occurs and the online Scalar DLC host turns offline, the other host is immediately online, so the user may not even notice there has been a problem with the host, and the customer engineer can work under the problem host without stopping the work of Scalar DLC software.
The Scalar DLC failover solution requires two identical PCs, a RAID system, the library, and the interface cables to provide the connections between PCs (Scalar DLC hosts), RAID (shared database), and library. Additional cabling may be required to provide the client connections (SCSI/FC) and using SNC.
For the requirements and installation instructions see Setting Up the
Installation Guide 5
Failover Solution on page 13.
Page 12

Self-Domain Solution

Up from version 2.5, Scalar DLC offers also so-called self-domain solution. This configuration of the Scalar DLC acts the same way as plain Failover solution and has the same hardware requirements, however it is installed without an external domain controller, so its setup does not exactly duplicate the failover solution instructions.
In terms of the network security, the self-domain solution is the most reliable method that Scalar DLC currently can provide.
For the details see Setting Up the Self-Domain Solution
on page 33.

Compatibility Matrix

The Scalar DLC compatibility with other hardware and third-party applications is described in Table 3.
Table 3 Scalar DLC Compatibility Matrix
Software/Hardware SW/FW Level
Scalar 10K (both single- and dual-aisle models) 310A
Scalar 1000 641A
SNC 5100 4.45.18
Scalar DLC 2.6
RMU 210
AMC 4.4
SNMS (StorNext Management System) 2.7
LTO-1 5AU1 (SCSI/FC)
LTO-2 5AT0 (SCSI/FC)
LTO-3 64D0 (FC)
AIT-2 0200_CY10
AIT-3 0209_0001
DLT8000 V80
SDLT 220 V87
SDLT 320 V87
3590 D0IF_26E
3592 D310_825
TS1120 D3I1_6E1
6 System Description
Page 13

Setting Up the Scalar DLC

Depending on the configuration used, follow the setup instructions:
Setting Up the Standard Solution
Setting Up the
Setting Up the Self-Domain Solution
Review also Common Setup Notes solutions only, the other are for all solutions.
Failover Solution on page 13.
on page 7.
on page 33.
on page 44. Some instructions are for Failover and Self-domain

Setting Up the Standard Solution

The Scalar DLC standard solution can be installed on any Windows 2000 or Windows 2003-based system.
Check the system requirements. Depending on the tape device used with the Scalar DLC, Single-
aisle Requirements on page 7 is for the single-aisle library, and Dual-aisle Requirements on page
8 is for the dual-aisle library.
Follow the Setup Roadmap

Single-aisle Requirements

Figure 3 Scalar DLC Basic Solution: Single-aisle
on page 9 to set up the Scalar DLC.
The minimum PC system hardware requirements are summarized in following list.
•A single PC:
1G MHZ or faster Intel Xeon or equivalent CPU
512 MB RAM
Dual 18Gb SCSI Hard Drives
Single On-Board NICS (build-in Ethernet)
CD-RW
Installation Guide 7
Page 14
3.5” inch Diskette Drive
Redundant AC Power
15" or greater SVGA Display
Standard keyboard & mouse
NT/2000 compliant LVD/HVD SCSI initiator adapter, library connection
CAUTION
CAUTION
1 middle length (2-3 m) SCSI cable (68 pins) for the library connection.
Recovery CD (Windows 2000 or 2003)
The following hardware (not shown on the scheme) is optional.
SCSI/FC target adapter(s)
Appropriate SCSI/FC cable(s)
Fibre Channel switch
•SNC
Do not use anteries (brand) SCSI adapters that do not allow setting reset on startup via BIOS.
Adaptec 39160 is an LVD/SE adapter, so note Table 16 on page 71 when choosing SCSI adapter for the library.

Dual-aisle Requirements

Figure 4 Scalar DLC Basic Solution: Dual-aisle
Note
The minimum PC system hardware requirements are summarized in following list.
•A single PC:
1G MHZ or faster Intel Xeon or equivalent CPU
512 MB RAM
Dual 18Gb SCSI Hard Drives
Single On-Board NICS (build-in Ethernet)
CD-RW
3.5” inch Diskette Drive
8 Setting Up the Scalar DLC
Although it is not recommended to use DA libraries in a Scalar DLC standard solution, this configuration is possible.
Page 15
Redundant AC Power
15" or greater SVGA Display
Standard keyboard & mouse
NT/2000 compliant LVD/HVD SCSI initiator adapter, library connection
CAUTION
CAUTION
1 middle length (2-3 m) SCSI cable (68 pins) for the library connection.
1 middle length (4-5 m) SCSI cable (68 pins) for the aisle connection. The total length of two SCSI cables required for the dual-aisle library connection (see Figure 4 page 8) must not exceed 12 m for LVD adapters and 25 m for HVD adapters.
2 SCSI Y-block connectors (Y-cable) to terminate the SCSI Bus on library.
1 SCSI Terminator, LVD/HVD for the library connection.
Recovery CD (Windows 2000 or 2003)
The following hardware (not shown on the scheme) is optional.
SCSI/FC target adapter(s)
Appropriate SCSI/FC cable(s)
Fibre Channel switch
Do not use anteries (brand) SCSI adapters that do not allow setting reset on startup via BIOS.
Adaptec 39160 is an LVD/SE adapter, so note Table 16 on page 71 when choosing SCSI adapter for the library.
on
•SNC

Setup Roadmap

Complete the following steps to set up the basic solution.
1 Collect
2 S
3 I
4 C
For the optional additional activity, see Setting Up the Library page 131, and Host/
Remove, Repair on page 81.
ing Setup Data on page 9.
etting Up the Host on page 10.
nstalling the Scalar DLC Software on page 12.
onfiguring the Logical Library on page 12.
Library Communication using Fibre Channel and SNC on page 127. See also Upgrade,

Collecting Setup Data

Collect the following information before starting setup.
Computer
computer name (max 14 symbols)
on page 123, Building Client Connections on
public IP address
Installation Guide 9
Page 16
public Subnet mask
public default Gateway
public preferred DNS
public Alternate DNS
public Primary WINS
public Secondary WINS
private IP address
private subnet mask
Local administrator login name and password
Scalar DLC serial number
Domain
domain name
domain admin login name and password
Table 4 Standard Solution: Installation Time
Installation procedure Time
Provide cabling and setup for PC system 10 min
Set IP address and computer name 10 min
Install Scalar DLC on PC 50 min

Setting Up the Host

Step 1 Set up the host hardware (network adapters, SCSI and FC adapters if required). Note Table 18
on page 72.
Step 2 Connect the PC to a local network. Install Windows 2000 / 2003. Resolve the network name
and TCP/IP. Join the PC to the domain, if required (domain admin password is required).
Note
Step 3 Install all required software services, for example, antivirus packages and firewall. Install all
Enter BIOS. Go to Chipset section. Hyper threading parameter should be disabled.
required device drivers (for example, initiator SCSI and RAID). Install the latest Microsoft Service Pack (SP4 for Win2000 and SP1 for Windows 2003 is required).
Step 4 When the operation system is installed successfully, reboot and ensure all services work
correctly.
Note
10 Setting Up the Scalar DLC
Unplug the target card SCSI cable if the server has trouble booting (may be a termination problem).
Page 17
Configuring SCSI for Library
Step 1 Configure the SCSI ID's for the LVD/HVD adapter connected to the library.
•Set termination mode to automatic
•Set Reset SCSI Bus parameter to disabled
Set the SCSI ID of this board to 5
Note
Step 2 Log on. Update drivers (Adaptec, QLA, etc.) as described in Updating Drivers
Step 3 Reboot host PC.
Adapter ID must not overlap with the single aisle LIBRARY SCSI ID.
Adapter ID must not overlap with the either libraries.
Any number could be used as SCSI IDs as long as it follows the rules above.
of the LIBRARY SCSI IDs for the dual-aisle
Setting Up IP Address, Host Name, and Joining Domain
Step 1 Log in host PC as administrator.
Step 2 Set up Public network.
<pause> Right click “My Network Places” and select “Properties”.
Right click “Local Area Connection” and rename in to ‘Public’. Select “Properties”.
Select “Show Icon in the Task Bar when Connected”.
Select “Internet Protocol (TCP/IP)” and select “Properties”.
on page 110.
Select “Use the Following IP Address”
•Set IP Address (208.230.5.100 in lab)
•Set Subnet Mask to 255.255.255.0
•Set Preferred DNS Server to 208.230.5.4 (in lab)
Note
Step 3 Join computer to the domain
Right click “My Computer” and select “Properties”.
Installation Guide 11
Also enter any additional customer networking information (additional DNS, WINS etc.).
Press “OK” and “OK”.
(on Windows 2000) Open “Network Identification” and select “Properties”.
(on Windows 2003) Open Computer Name > Change > More. Ensure that the checkbox ‘Change primary DNS suffix when domain membership changes’ is enabled (see Figure 5 on page 12). Press OK.
Page 18
Figure 5 Windows 2003: DNS suffix enabled
Set “Computer name” (SDLC)
CAUTION
Select “Domain” and enter <domain name without postfix> and OK (“domain” for lab)
Enter domain admin name and password and OK (“adicuser” and “pa$$w0rd”)
•Wait for Welcome to domain.
Press “OK” and “OK” to reboot and “OK” and “Yes”.
Step 4 ‘Yes’ to reboot now. Wait until reboot.
Computer name must not be longer than 14 symbols.

Installing the Scalar DLC Software

Step 1 Log in as administrator or as a domain user with the local administration rights.
Step 2 Set up the library media changer unless it has been already done. See Setting Up the Library
on page 123.
Step 3 Install the Scalar DLC software with all required components (see Installing the Scalar DLC
page 45).
on

Configuring the Logical Library

Step 1 Log in as administrator or as a domain user with the local administration rights and start the
Scalar DLC software if it is not started automatically.
Step 2 Double click the Scalar DLC Manager icon to start the Scalar DLC Management GUI from a
local computer. From a remote computer, use
http://ScalarDLC-machine-name in current browser.
Step 3 The first start of the Scalar DLC Management GUI launches the configuration engine. Select
either the Automatic or Manual configuration option to configure the logical library automatically, or Advanced configuration option in case of more then one logical library should be created. Refer to the Configuration chapter of the Scalar DLC Reference Guide for the instructions.
12 Setting Up the Scalar DLC
Page 19

Setting Up the Failover Solution

The Scalar DLC Failover (Redundant, Cluster) solution can be installed only on a Windows 2000 Advanced Server or Windows 2003 Server because it uses the Microsoft Cluster Service that is not available under Windows 2000 Professional, Windows 2000 Server, and Windows 2003.
Check the system requirements. Depending on the tape device used with the Scalar DLC, Single-
aisle Requirements on page 13 is for the single-aisle library, and Dual-aisle Requirements on page
14 is for the dual-aisle library.
Follow the Setup Roadmap
on page 15 to set up the Scalar DLC.

Single-aisle Requirements

Figure 6 Scalar DLC Failover Solution: Single-aisle
The minimum PC system hardware requirements are summarized in following list.
Two PCs with identical hardware and software:
1G MHZ or faster Intel Xeon or equivalent CPU
512 MB RAM
Dual 18Gb SCSI Hard Drives
PERC3-DI, 128MB Battery Backed Cache, two Internal Channel - Embedded RAID Controller
(1, 2 Drives connected to on-board RAID)
Dual On-Board NICS (build-in Ethernet)
CD-RW
3.5” inch Diskette Drive
Redundant AC Power
15" or greater SVGA Display
Standard keyboard & mouse
NT/2000 compliant LVD SCSI initiator adapter, RAID connection
NT/2000 compliant LVD/HVD SCSI initiator adapter, library connection
CAUTION
Installation Guide 13
Do not use anteries (brand) SCSI adapters that do not allow setting reset on startup via BIOS.
Page 20
CAUTION
1 ArrayMasStor P-Series ADTX RAID System.
1 Network cross cable (twisted-pair) (~1 m), for the internal cluster network.
2 short (~1 m) SCSI cables (68 pins), for the RAID connections.
2 middle length (2-3 m) SCSI cable (68 pins), for the library connections.
2 Y-Block connectors to terminate the SCSI Bus on library.
2 LVD SCSI Terminators for the RAID connections.
2 LVD/HVD SCSI Terminators for the library connections.
Recovery CD (Windows 2000 Advanced Server or 2003 Server)
Adaptec 39160 is an LVD/SE adapter, so note Table 16 on page 71 when choosing SCSI adapter for the library.
CAUTION
The following hardware (not shown on the scheme) is optional.
SCSI/FC target adapter(s)
Appropriate SCSI/FC cable(s)
Fibre Channel switch
•SNC
The hardware configuration of both cluster nodes must be identical, and they must remain identical. For example, all cards/adapters must be identical and need to be placed in identical slots.

Dual-aisle Requirements

Figure 7 Scalar DLC Failover Solution: Dual-aisle
The minimum PC system hardware requirements are summarized in following list.
Two PCs with identical hardware and software:
1G MHZ or faster Intel Xeon or equivalent CPU
512 MB RAM
Dual 18Gb SCSI Hard Drives
PERC3-DI, 128MB Battery Backed Cache, two Internal Channel - Embedded RAID Controller
(1, 2 Drives connected to on-board RAID)
14 Setting Up the Scalar DLC
Page 21
Dual On-Board NICS (build-in Ethernet)
CD-RW
3.5” inch Diskette Drive
Redundant AC Power
15" or greater SVGA Display
Standard keyboard & mouse
NT/2000 compliant LVD SCSI initiator adapter, RAID connection
NT/2000 compliant LVD/HVD SCSI initiator adapter, library connection
CAUTION
CAUTION
1 ArrayMasStor P Series ADTX RAID System.
1 Network cross cable (twisted-pair) (~1 m), for the internal cluster network.
2 short (~1 m) SCSI cables (68 pins), for the RAID connections.
2 middle length (2-3 m) SCSI cable (68 pins), for the library connections.
2 middle length (4-5 m) SCSI cable (68 pins), for the aisle connections. The total length of two SCSI cables required for the dual-aisle library connection (see Figure 7 page 14) must not exceed 12 m for LVD adapters and 25 m for HVD adapters.
4 Y-Block connectors to terminate the SCSI Bus on library.
2 LVD SCSI Terminators for the RAID connections.
2 LVD/HVD SCSI Terminators for the library connections.
Recovery CD (Windows 2000 Advanced Server or 2003 Server)
Do not use anteries (brand) SCSI adapters that do not allow setting reset on startup via BIOS.
Adaptec 39160 is an LVD/SE adapter, so note Table 16 on page 71 when choosing SCSI adapter for the library.
on
CAUTION
The following hardware (not shown on the scheme) is optional.
SCSI/FC target adapter(s)
Appropriate SCSI/FC cable(s)
Fibre Channel switch
•SNC
The hardware configuration of both cluster nodes must be identical, and they must remain identical. For example, all cards/adapters must be identical and need to be placed in identical slots.

Setup Roadmap

Complete the following steps to set up the Failover solution.
1 Collect
Installation Guide 15
ing Setup Data on page 16.
Page 22
2 Installing the Nodes on page 17.
3 Install
4 C
5 S
6 S
7 C
8 I
9 C
For the optional additional activity, see Setting Up the Library page 131, Installing SCSI/FC Target Adapters on a Live Machine
Communication using Fibre Channel and SNC on page 127. See also Upgrade, Remove, Repair on page
81.
ing ADTX RAID on page 18.
onfiguring SCSI for RAID and Library on page 20.
etting Up IP Address, Node Name, and Joining Domain on page 22.
etting Up the RAID on page 24.
onfiguring Cluster Service on page 26
nstalling Scalar DLC Software on page 28.
onfiguring the Logical Library on page 31.
on page 123, Building Client Connections on
on page 134, and Host/Library

Collecting Setup Data

Collect the following information before starting setup.
Nodes
Node1 computer name (14 symbols max)
Node1 public IP address
Node2 computer name (14 symbols max)
Node2 public IP address
public Subnet mask
public default Gateway
public preferred DNS
public alternate DNS (optional)
public primary WINS (optional)
public secondary WINS (optional)
Node1 private IP address
Node2 private IP address
private subnet mask
Local administrator login name and password (same on both nodes)
Scalar DLC serial number (same on both nodes
Cluster
name (14 symbols max)
IP address
Subnet mask = public subnet mask
Domain
•name
domain admin name and password
directory services restore mode password
16 Setting Up the Scalar DLC
Page 23
Table 5 Failover Solution: Installation Time
Installation procedure Time
Provide cabling and setup for dual PC failover system 30 min
SCSI configuration for RAID and library 20 min
Set IP addresses and computer names 30 min
Configure primary and secondary domain controllers 45 min
Setup RAID 10 min
Configure cluster service 20 min
Install Scalar DLC on both PC 120 min
Active Directory Account Information
Contact the local network administrator and ensure that the following settings are performed.
User account created with domain admin rights and the following options:
User must not change password under next logon.
User cannot change password.
Password never expires.
All other options are disabled.
Logon hours for this user are set to 24/7.
Log on rights are set either to all computers or to all Scalar DLC nodes.

Installing the Nodes

Step 1 Turn off external RAID.
Step 2 Insert the RAID SCSI HBA into the PCI slot of Node1 according to Table 18
Connect it and RAID SCSI channel (S11) with the short SCSI cable. Terminate the second RAID SCSI channel (S21) with the SCSI terminator (see Figure 8
Step 3 Insert the RAID SCSI HBA into the PCI slot of Node2 according to Table 18
Connect it and RAID SCSI channel (S12) with the short SCSI cable. Terminate the second RAID SCSI channel (S22) with the SCSI terminator (see Figure 8
on page 18).
on page 18).
on page 72.
on page 72.
Installation Guide 17
Page 24
Figure 8 RAID SCSI cabling
Step 4 Connect the monitor, keyboard, mouse, and KVM.
Step 5 Boot Node1. Log on (administrator / password).
Note
Step 6 <pause> select “I will configure the server later” and press Next. Unselect “Show This Screen
Step 7 Shutdown Node1.
Step 8 Repeat steps 4 to 7 for Node2.
Step 9 Connect ethernet cables LAN 1 (public network) and LAN 2 (private network).
Enter BIOS. Go to Chipset section. Hyper threading parameter should be disabled.
on Startup” and close window.

Installing ADTX RAID

Step 1 Power on RAID.
Step 2 Set SCSI ID.
The default setting is SCSI ID 0 for both channels. In order to verify the SCSI ID for both
channels use the Operator Panel on the RAID. RAID SUBSYSTEM
•MAIN MENU
[MAIN MENU]
SYSTEM INFO
[MAIN MENU]
VIEW CONFIG
18 Setting Up the Scalar DLC
Page 25
[VIEW CONFIG]
•SCSI
[SCSI]
CHANNEL 1
•SCSI ID
•0 The same steps for channel 2.
In order to change the SCSI ID for both channels use the following steps. RAID SUBSYSTEM
•MAIN MENU
[MAIN MENU]
SYSTEM INFO
[MAIN MENU]
CHANGE CONFIG
ENTER PASSWORD 1234
[CHANGE CONFIG]
•SCSI
[SCSI]
CHANNEL 1
•SCSI ID
SET 0 The same steps for channel 2.
Step 3 Change the RAID 'WRITE CACHE' setting.
In order to change the RAID 'WRITE CACHE' setting via Operator Panel use the following steps. RAID SUBSYSTEM
•MAIN MENU
[MAIN MENU]
SYSTEM INFO
[MAIN MENU]
CHANGE CONFIG
ENTER PASSWORD 1234
[CHANGE CONFIG]
OPTION SETTING
[OPTION SETTING]
CACHE SETTING
[CACHE SETTING]
WRITE CACHE
[WRITE CACHE]
SET 'DISABLE'
Installation Guide 19
Page 26
Step 4 Reset RAID by turning it off.

Configuring SCSI for RAID and Library

Step 1 Plug the SCSI cable directly in to the RAID vhdci connector.
Step 2 Power on RAID, then power on Node1.
Step 3 <Ctrl>+A to enter Bios for Adaptec SCSI card at Bios 3.10.0 (see Figure 9
Figure 9 Adaptec SCSI Bios
).
Select B for RAID configuration.
•Select SCSI disk utilities to scan for RAID device.
Press “Esc”.
Select “Configure / view SCSI settings”.
Set SCSI controller ID (14 for Node1 and 15 for Node2).
Set SCSI termination to Automatic.
•Go to Advanced configuration.
Set “Reset SCSI bus at IC Initialization” to Disabled.
Set “SCSI controller Int 13 Support“ to Disabled: NOT scan.
Press “Esc”.
Go to “SCSI device configuration” (see Figure 10
20 Setting Up the Scalar DLC
on page 21).
Page 27
Figure 10 Adaptec SCSI Bios: SCSI Device Configuration
Set “Sync Transfer Rate” to 40
Note
Press “Esc”.
Select A for library configuration
Select “Configure / view SCSI settings”
Step 4 Configure the SCSI ID's for the LVD/HVD adapters (connected to the library) on the cluster
Rate is 160 for L and P series RAIDs
Set “Start unit command” to No for #0.
Set “Include in Bios scan” to Yes for Node1 and No for Node2 for #0.
Press “Esc”, and “Esc”, and “Save changes”.
Set termination to Automatic
•Go to Advanced configuration
Set “Reset SCSI bus at IC Initialization” to Disabled
Press “Esc”, and “Esc”, and “Save changes”.
Press “Esc”, and “Esc”, and exit utility.
nodes.
Enter the LVD/HVD SCSI BIOS Setup on Node1 for the adapter connected to the library:
•Set termination mode to automatic
Installation Guide 21
Page 28
•Set Reset SCSI Bus parameter to disabled
Set the SCSI ID of this board to 5
Enter the LVD/HVD SCSI BIOS Setup on Node2 for the adapter connected to the library.
•Set termination mode to automatic
•Set Reset SCSI Bus parameter to disabled
Set the SCSI ID of this board to 6
Note
Step 5 Log on. Update drivers (Adaptec, QLA, etc.) as described in Updating Drivers
Step 6 Shutdown Node1.
Step 7 Repeat steps 2 - 5 using Node2 instead of Node1.
Both adapters must have different SCSI IDs.
Adapter IDs must not overlap with the single aisle LIBRARY SCSI ID.
Adapter IDs must not overlap with the either libraries.
Any number could be used as SCSI IDs as long as it follows the rules above.
of the LIBRARY SCSI IDs for the dual-aisle

Setting Up IP Address, Node Name, and Joining Domain

Step 1 Power on Node1 and log in.
Note
“HDD changed” message may appear. F1 to enter setup and esc and ok.
During logging in ignore duplicate name message if it appears.
on page 110.
Step 2 Set up Public network.
<pause> Right click “My Network Places” and select “Properties”.
Right click “Local Area Connection” and rename in to ‘Public’. Select “Properties”.
Select “Show Icon in the Task Bar when Connected”.
Select “Internet Protocol (TCP/IP)” and select “Properties”.
Select “Use the Following IP Address”
•Set IP Address (208.230.5.100 for Node1 and 208.230.5.200 for Node2 in lab)
•Set Subnet Mask to 255.255.255.0
•Set Preferred DNS Server to 208.230.5.4 (in lab)
•Set Public default Gateway to 208.230.5.4 (in lab)
Note
22 Setting Up the Scalar DLC
Also enter any additional customer networking information (additional DNS, WINS etc.).
Press “OK” and “OK”.
Page 29
Step 3 (This step is for Windows 2000 system only. On Windows 2003 follow the Step 4)
Right click “Public” and “Disable” then right click and “Enable”. A new item “Local Area Connection 2” will appear.
Step 4 Set up Private network
Right click “Local Area Connection 2” and rename it to ‘Private’. Select “Properties”
Select “Show Icon in the Task Bar when Connected”
Select “Internet Protocol (TCP/IP)” and select “Properties”
Select “Use the Following IP Address”
Set IP Address to (10.10.10.1 and 10.10.10.2 in lab) (use here a completely different IP
than for “Local Area Connection”).
Set Subnet Mask to 255.0.0.0.
Press “OK” and “OK”.
Step 5 (This step is for Windows 2000 system only. On Windows 2003 follow the Step 6)
Right click “Local Area Connection 2” and “Disable” then right click and “Enable”.
Step 6 Join node to the domain
Right click “My Computer” and select “Properties”.
(on Windows 2000) Open “Network Identification” and select “Properties”.
(on Windows 2003) Open Computer Name > Change > More. Ensure that the checkbox
‘Change primary DNS suffix when domain membership changes’ is enabled (see Figure
11). Press OK.
Figure 11 Windows 2003: DNS suffix enabled
Set “Computer name” (sdlc1 for Node1 and sdlc2 for Node2)
Both Node1 and Node2 names must not be longer than 14 symbols.
CAUTION
Select “Domain” and enter <domain name without postfix> and OK (“domain” for the computers in lab)
Enter domain user name and password and OK (“adicuser” and “pa$$w0rd”)
•Wait for Welcome to domain.
Press “OK” and “OK” to reboot and “OK” and “Yes”.
Installation Guide 23
Page 30
Step 7 ‘Yes’ to reboot now. Wait until reboot.
Step 8 Repeat steps 1 to 6 for Node2. ‘No’ to reboot now.
CAUTION
Step 9 Shutdown both nodes.
Using Start > Run do the following: From Node2 run: ping <Node1 public IP address> From Node2 run: ping <Node1 private IP address> From Node1 run: ping <Node2 public IP address> From Node1 run: ping <Node2 private IP address> From Node1 or Node2 run: ping <Domain name> If any of these commands returns “Request timed out“ response, that means the network settings are configured incorrectly, for example, the network connection that has been configured as ‘public’, is in fact internal cluster (private) network connection.

Setting Up the RAID

Same on both Windows 2000 and Windows 2003 unless the other specified.
Step 1 Power up Node1 and log in as Administrator for SDLC1 (this computer)
Step 2 Prepare to Format RAID disk
Right click “My Computer” and select “Manage”.
Select Device Manager and open Disk Drives. Scan for new devices (see Figure 12
Figure 12 Device Manager: Disk Drives
).
Verify that the ADTX RAID is present.
24 Setting Up the Scalar DLC
Page 31
Select “Disk Management”. Write Signature Wizard should start. Press “Next”.
Select “Disk 1” to write a Signature and press “Next”.
Unselect “Disk 1” to Upgrade (Convert on Windows 2003), press “Next” and then “Finish”.
Step 3 Format RAID
Right click unallocated space and select “Create Partition”. Create Partition Wizard starts. Click Next.
Select “Primary Partition” and press “Next”.
Set maximum value in “Amount of Disk Space to Use” and press “Next”.
Select “Assign a Drive Letter” and select “R:” and press “Next”.
Select “Format this Partition with the Following Settings”
Set “File System” to “NTFS”
Set “Allocation Unit Size” to “Default”
Set “Volume Label” to “RAID”
Select “Perform A Quick Format” (see Figure 13
Figure 13 Format RAID Partition
Press “Next” and “Finish” and let format complete.
)
Shutdown Node1, turn RAID off.
Step 4 Power up Node2 and log in as Administrator for SDLC2 (this computer). Turn RAID on and wait
for it to come ready.
Step 5 Join RAID disk
Right click “My Computer” and select “Manage”.
Select Device Manager and open Disk Drives. Scan for new devices.
Verify that the ADTX RAID is present.
Select “Disk Management”. Right click “RAID”. Select “Change Drive Letter and Path”.
Installation Guide 25
Page 32
Select “Edit” and “Assign Drive Letter” to “R”. Press OK. Press “Yes” to confirm.
Shutdown Node2.

Configuring Cluster Service

Under WIndows 2000 and Windows 2003 the cluster is installed differently.
Windows 2000
Step 1 Power up Node1 and log in as Administrator to SDLC1 (this computer)
Step 2 Configure Cluster Service on Node1.
•Select Start > Settings > Control panel > Add/Remove Programs > Add/Remove Windows Components >> Cluster Service. Press Next.
Insert Windows 2000 Advanced Server SP4 CD and press OK. Cluster Service Configuration Wizard will start. Press “Next”.
Click “I Understand” and “Next”.
Select “The First Node in the Cluster” and “Next”.
Set cluster name to SDLC-CLUSTER and “Next”.
CAUTION
Set User Name to “adicuser” and Password to “pa$$w0rd”. Set Domain to <domain> and
“Next”.
Click “Yes” to adding account to the Administrators Group.
Ensure that “R: Raid” is in managed disks and “Next”.
Select “R: Raid” and “Next” and “Next”.
Set up Cluster Network,
For Network Name “Public” select “Enable this Network for Cluster Use”.
Select “All Communications (mixed network)” and “Next”.
For Network Name “Private” select “Enable this network for cluster use”.
Select “Internal Cluster Communications Only (Private Network)” and “Next”.
Ensure that “Private” is at the top of Networks list and “Next”
“Finish” and “OK” to Cluster Service Started Successfully.
The cluster name must not be longer than 14 symbols.
Set “Cluster IP address” to <ip address> (208.230.5.3 in lab)
Set “Subnet Mask” to 255.255.255.0
Set “Network” to “Public” and “Next”.
Finish and eject CD and close all windows.
Step 3 Power up Node2 and log in as Administrator for SDLC2 (this computer)
Step 4 Configure Cluster Service on Node2.
26 Setting Up the Scalar DLC
Page 33
•Select Start > Settings > Control panel > Add/Remove Programs > Add/Remove Windows Components >> Cluster Service. Press Next.
Insert Windows 2000 Advanced Server SP4 CD and press OK.
Cluster Service Configuration Wizard will start and Next
Click “I Understand” and “Next”.
Select “Second or Next Node in the Cluster” and “Next”.
Set cluster name as SDLC-CLUSTER
Select “Connect to Cluster As”.
Set User Name to “adicuser” and Password to “pa$$w0rd”.
Set Domain to <domain> and “Next”.
Set password as “pa$$w0rd” and “Next”.
“Yes” to Specified Account not a Member
“Finish” and “OK” and “Finish”.
Step 5 Remove CD and close all windows.
Step 6 Verify Cluster service.
On Node2 select Start > Settings > Control Panel > Administrative Tools > Cluster
Administrator.
Select Groups > Cluster Group
Select File > Move Group to verify the cluster is working properly
Move group again and return ownership to Node1
Windows 2003
Step 1 Power on Node1. Log on as Administrator.
Step 2 Create Cluster on Node1.
Start > Administrative Tools > Cluster Administrator
Choose 'Create new cluster' and OK. Next. Enter cluster name (SDLCCLUSTER2003) and Next.
CAUTION
Review Node1 name and Next. The wizard will analyze an existing configuration.
The cluster name must not be longer than 14 symbols.
Next. Enter cluster IP (static, unique) and Next.
Enter domain user account & password. Next.
Review cluster summary and Next. Wizard creates a cluster.
Next and Finish.
Step 3 Join Node2 to Cluster
Installation Guide 27
Page 34
Power on Node2 and wait till it comes up. Wait circa 5 min until the virtual cluster name will be available from Node2. Switch to Node2.
Start > Administrative Tools > Cluster Administrator. Choose 'Open Connection to cluster' and enter the cluster name (SDLCCLUSTER2003).
OK. Then Fine > New > Node. Add new Node wizard starts.
Next. Add, then Next. The wizard will analyze an existing configuration.
Enter domain user account & password. Next.
Review cluster summary and Next. Wizard adds node to a cluster.
Next and Finish. The cluster is ready.
Step 4 Ensure the cluster works.
Select Start > Administrative Tools > Cluster Administrator
Select Groups > Cluster Group
Select File > Move Group to verify the cluster is working properly
Move group again and return ownership to Node1.

Installing Scalar DLC Software

Same on both Windows 2000 and Windows 2003 unless the other specified.
Step 1 Set up the library media changer unless it has been already done. See Setting Up the Library
on page 123.
Step 2 Install Scalar DLC on Node1.
Log in as the domain admin.
Insert Scalar DLC 2.6 CD. Select Scalar DLC Install to install the Scalar DLC with all required components (see Installing the Scalar DLC
Set SQL Destination to “R:”.
Specify Scalar DLC settings, as required for S
Set SDLC User Name to <SDLC user name>. Set password to <SDLC user password>.
Select domain account and “Check”. Wait (~5 min) and Submit.
Note
As the SDLC user is a domain account, the user name and password should match the local network security policy. Contact the local network administrator for the details.
Set Database Name as “SDLC”. Select Compact Database Weekly, Backup Database
None.
Unselect
“Turn On Email Notifications”.
on page 45).
calar DLC Software on page 50.
Select “Complete”.
Select “Install immediately” for Target Drivers (if required).
Install.
Java 2 install: “I accept” and “Next” and “Typical” and “Next” and “Finish”.
Apache install: “Next” and “I accept” and “Next” and “Next”.
28 Setting Up the Scalar DLC
Page 35
MSDE2000 install: “No”, then “Yes“.
Set Network Domain as <domain name>. Set Server name as <computer name>.<domain
name>. Set Administrators Email as “admin@<domain name>. Set “Run as a service for all Users” and “Next”.
Select “Complete” and “Next” and “Next” and “Install” and “Finish”. “OK” to “the system
being restarted now” and restart (15 min for SQL).
OK to restart and wait for <ctrl><alt><del>. Remove Scalar DLC Install disk from Node1.
Step 3 Install Scalar DLC on Node2.
Power on Node2. Log in as the domain admin.
Insert Scalar DLC 2.6 CD. Select Scalar DLC Install to install the Scalar DLC with all required components (see Installing the Scalar DLC
Set SQL Destination to “R:”.
on page 45).
Specify Scalar DLC settings, as required for S
Set SDLC User Name to <SDLC user name>. Set password to <SDLC user password>.
Select domain account and “Check”. Wait (~5 min) and Submit.
Note
Install.
As the SDLC user is a domain account, the user name and password should match the local network security policy. Contact the local network administrator for the details.
Set Database Name as “SDLC”. Select Compact Database Weekly, Backup Database
None.
Unselect
Select “Complete”.
Select “Install immediately” for Target Drivers (if required).
Java 2 install: “I accept” and “Next” and “Typical” and “Next” and “Finish”.
Apache install: “Next” and “I accept” and “Next” and “Next”.
MSDE2000 install: “No”, then “Yes“.
Set Network Domain as <domain name>. Set Server name as <computer name>.<domain
name>. Set Administrators Email as “admin@<domain name>. Set “Run as a service for all Users” and “Next”.
“Turn On Email Notifications”.
calar DLC Software on page 50.
Select “Complete” and “Next” and “Next” and “Install” and “Finish”. “Ok” to “the system
being restarted now” and restart (15 min for SQL).
Remove Scalar DLC Install disk from Node2.
Step 4 Finish installing Scalar DLC on Node1
Load Scalar DLC Install disk on Node1. Log in as the domain admin; installation should continue. Cancel immediately.
Open Cluster Administrator and go to Groups > Cluster Group. Verify that Node1 has ownership now.
Manually run <CD>:\autorun. Select Scalar DLC Install. Next and I Accept and Next and Next.
Specify Scalar DLC settings
Installation Guide 29
Page 36
Set user name to ADIC User and organization to ADIC. Enter serial number. Select Anyone
(all Users) and “Next”
Set SDLC User Name to <SDLC user name>. Set password to <SDLC user password>.
Select domain account and “Check”. Wait (~5 min) and Submit.
Note
Note
Install Scalar DLC.
Enter Registration Information and Next
Unselect Send License request to ADIC Now and Next. Unselect Read Installation Summary
Remove Scalar DLC Installation CD. “Yes” to restart Node1. Wait for <ctrl><alt><del> screen.
As the SDLC user is a domain account, the user name and password should match the local network security policy. Contact the local network administrator for the details.
Look for successful component registration and “Next”.
Set Database Name as “SDLC”. Select Compact Database Monthly, Backup Database
Weekly, set backup file “SDLC_backup” in folder “R:\MSSQL\Backup” and Next
The Backup directory is to be created manually.
Unselect “Turn On Email Notifications” and “Next”.
Select “Complete” and “Next”.
Select “Do not Install” for Target Drivers and “Next”. Install.
Now and Finish.
Step 5 Finish installing Scalar DLC on Node2
Load Scalar DLC Install disk on Node2. Log in as the domain admin; install should continue. Cancel immediately.
Open Cluster Administrator and go to Groups > Cluster Group. Verify that Node2 has ownership now.
Manually run <CD>:\autorun. Select Scalar DLC Install. Next and I Accept and Next and Next.
Specify Scalar DLC settings
Set user name to ADIC User and organization to ADIC. Enter serial number. Select Anyone
(all Users) and “Next”.
Set SDLC User Name to <SDLC user name>. Set password to <SDLC user password>.
Select domain account and “Check”. Wait (~5 min) and Submit.
Note
As the SDLC user is a domain account, the user name and password should match the local network security policy. Contact the local network administrator for the details.
Look for successful component registration and “Next”.
Set Database Name as “SDLC”. Select Compact Database Monthly, Backup Database
Weekly, set backup file “SDLC_backup” in folder “R:\MSSQL\Backup” and Next
30 Setting Up the Scalar DLC
Page 37
Note
Install. Cancel License wizard.
Unselect “Read Installation Summary Now” and “Finish”.
Remove Scalar DLC Install CD. “Yes” to restart Node2. Wait for <ctrl><alt><del> screen
Step 6 Install Target Drivers (optional, only for SCSI/FC clients with Scalar DLC. If no SCSI/FC Client
Insert Scalar DLC install CD in Node1. Autorun will start.
The Backup directory is to be the same one as for Node1.
Select “Use Existing Database” and Next. Do not choose “Create new database“ or the
Scalar DLC will not function.
Select “Do not Install” for Target Drivers and “Next”. Install.
will be used with the Scalar DLC software, proceed to Step 7)
Follow the installation sequence for Inst
Remove CD and reboot Node1.
Insert Scalar DLC install CD in Node2. Autorun will start.
Follow the installation sequence for Inst
Remove CD and reboot Node2.
On Node1 enable Target mode for the adapter, see Activating Target Mode reboot Node1.
On Node2 enable Target mode for the adapter, see Activating Target Mode reboot Node2.
Step 7 Set Scalar DLC to Failover (cluster) mode
Log in as the domain user with local admin rights.
Insert Scalar DLC Install CD. Close Autorun. Run
<CD>:\Scalar_DLC\Cluster\SDLC_ClusterConfig.exe
Verify that both nodes show as up in the SDLC Cluster Configurator.
Click Make SDLC Cluster Configuration.
alling the SCSI/FC Target Drivers on page 74.
alling the SCSI/FC Target Drivers on page 74.
on page 77. Then
on page 77. Then
“OK” when complete and close all windows.
Reboot Node1 and Node2.

Configuring the Logical Library

Step 1 Using any node, log in as administrator or as a domain user with the local administration rights
and start the Scalar DLC software if it is not started automatically.
Step 2 Double click the Scalar DLC Manager icon to start the Scalar DLC Management GUI from a
local computer. From a remote computer, use http://ScalarDLC-machine-name in current browser.
Installation Guide 31
Page 38
Note
Step 3 The first start of the Scalar DLC Management GUI launches the configuration engine. Select
It is strongly recommended to use the virtual Cluster name here (for example, SDLC-CLUSTER).
either the Automatic or Manual option to configure the logical library automatically, or Advanced option in case of more then one logical library should be created. Refer to the Configuration chapter of the Scalar DLC Reference Guide for further instructions.
CAUTION
Note
Note
The operating system and its service packs on both cluster nodes must be identical and they must remain identical. Otherwise it may cause cluster service malfunctions.
If the network parameters are changed, the cluster service will not function and should be repaired or re-configured manually. See R
Never turn the RAID shared disk off. Otherwise, the Scalar DLC will not work.
Never load off the SCSI terminators from RAID or library. This will put the Scalar DLC to malfunction.

Post-install checklist

Nodes
Node1 computer name (14 symbols max)
Node1 public IP address
Node2 computer name (14 symbols max)
enaming and Repair on page 97.
Node2 public IP address
public Subnet mask
public default Gateway
public preferred DNS
public Alternate DNS (optional)
public Primary WINS (optional)
public Secondary WINS (optional)
Node1 private IP address
Node2 private IP address
private subnet mask
Local administrator login name and password (same on both nodes)
Scalar DLC serial number (same on both nodes
Cluster
name (14 symbols max)
32 Setting Up the Scalar DLC
Page 39
IP address
Subnet mask = public subnet mask
Domain
•name
domain admin name and password
directory services restore mode password
Configuration
library SN
backup to RAID
backup to floppy
clients configured and tested
hardware configured and tested
email address settings
contact information
client type(s)
target card model
•License
Node1 SID
Node1 license string
Node2 SID
Node2 license string

Setting Up the Self-Domain Solution

Installing the Failover solution as Self-domain system, without an external domain controller, means that the Scalar DLC will be installed on both the Primary Domain Controller and the Backup Domain Controller. This configuration is possible but requires the extended setup, not the same as for the plain Failover solution that described in details in Setting Up the

Setup Roadmap

1 Collecting Setup Data on page 34.
2 Installing the Nodes
3 Installing ADTX RAID
4 Configuring SCSI for RAID and Library
on page 34.
on page 35.
Failover Solution on page 13.
on page 35.
5 Setting Up Network, IP Address and Computer Names
6 Configuring Domain Controllers
7 Setting Up the RAID disk
8 Configuring Cluster Service
9 Installing Scalar DLC Software
Installation Guide 33
on page 36.
on page 40.
on page 40.
on page 43.
on page 35.
Page 40
For the optional additional activity, see Setting Up the Library on page 123, Building Client Connections on page 131, Installing SCSI/FC Target Adapters on a Live Machine
Communication using Fibre Channel and SNC on page 127. See also Upgrade, Remove, Repair on page
81.
on page 134, and Host/Library

Collecting Setup Data

Nodes
Node1 computer name (14 symbols max)
Node1 public IP address
Node2 computer name (14 symbols max)
Node2 public IP address
public Subnet mask
public default Gateway = Node1 public IP
public preferred DNS = Node1 public IP
public alternate DNS = Node2 public IP
Node1 private IP address
Node2 private IP address
private subnet mask
private preferred DNS = Node1 private IP
private alternate DNS = Node2 private IP
Local administrator login name and password (same on both nodes)
Scalar DLC serial number (same on both nodes
Cluster
name (14 symbols max)
IP address
Subnet mask = public Subnet mask
Domain
name (14 symbols max; a compound name must be used, for example, SDLCDOMAIN.INT; the 14-symbol-length limit does not include postfix .INT)
domain admin name and password
directory services restore mode password
Contact information of IT person for connection questions

Installing the Nodes

First all the same as in plain Failover solution. See Installing the Nodes on page 17.
Then copy NewSID
Copy newsid program into a directory on the C: drive.
Run newsid /a
Node1 will reboot. Shutdown Node2
34 Setting Up the Scalar DLC
Page 41

Installing ADTX RAID

Same as in plain Failover solution. See Installing ADTX RAID on page 18.

Configuring SCSI for RAID and Library

Same as in plain Failover solution. See Configuring SCSI for RAID and Library on page 20.

Setting Up Network, IP Address and Computer Names

The procedure is more or less the same on both Win2000 and Win2003.
Step 1 Power on Node1 and log in (ignore duplicate name message).
Step 2 Set up Public network.
On Windows 2000, right click “My Network Places” and select “Properties”. On Windows 2003, use Start > Control Panel > Network Connections (right-click) > Open.
Right click “Local Area Connection”. Rename it to ‘Public’. Right-click and select “Properties”.
Select “Show Icon in the Task Bar/Notification Area when Connected”. Select “Internet Protocol (TCP/IP)” and select “Properties”.
Select “Use the Following IP Address”
•Set IP Address (192.168.0.220 for Node1 and 192.168.0.221 for Node2 in lab)
•Set Subnet Mask to 255.255.255.0
•Set Default gateway to same
•Set Preferred DNS to same
•Set Alternate DNS to static IP of Node2 (192.168.0.221)
Press “OK” and “OK”. (OK and Close on Windows 2003).
Step 3 (This step is for Windows 2000 system only. On Windows 2003 follow the Step 4)
Right click “Public” and “Disable” then right click and “Enable”. A new item “Local Area Connection 2” will appear.
Step 4 Set up Private (cluster) network.
Rename Local Area Connection 2 to ‘private’.
Right click “Private” and select “Properties”.
Select “Show Icon in the Task Bar when Connected”. Select “Internet Protocol (TCP/IP)” and select “Properties”
Select “Use the Following IP Address”
Set IP Address to (10.0.0.1 for Node1 and 10.0.0.2 for Node2 in lab) (use a completely
different IP than Local Area Connection that is on a higher subnet)
as static IP of Node1 (192.168.0.220)
as static IP for Node1 (192.168.0.220)
Set Subnet Mask to 255.0.0.0
Set preferred DNS to static IP of Node1 (10.0.0.1)
Set alternate DNS to static IP of Node2 (10.0.0.2)
Press “OK” and “OK” (OK and Close on WIndows 2003).
Installation Guide 35
Page 42
Step 5 Set computer name.
Right click “My Computer” and select “Properties”.
(on Windows 2000) Open “Network Identification” and select “Properties”.
(on Windows 2003) Open Computer Name > Change > More. Ensure that the checkbox
‘Change primary DNS suffix when domain membership changes’ is enabled (see Figure 11 on page 23). Press OK.
Set “Computer name” (sdlc1 for Node1 and sdlc2 for Node2)
CAUTION
Press “OK” and “OK” to reboot and “OK” and “No” to reboot server.
Step 6 Shutdown Node1.
Step 7 Repeat steps 1 to 6 for Node2.
CAUTION
Both Node1 and Node2 names must not be longer than 14 symbols.
Using Start > Run do the following: From Node2 run: ping <Node1 public IP address> From Node2 run: ping <Node1 private IP address> From Node1 run: ping <Node2 public IP address> From Node1 run: ping <Node2 private IP address> If any of these commands returns “Request timed out“ response, that means the network settings are configured incorrectly, for example, the network connection that has been configured as ‘public’, is in fact internal cluster (private) network connection.

Configuring Domain Controllers

Under WIndows 2000 Advanced Server and Windows 2003 Server, this procedure is not quite the same.
Windows 2000
Step 1 Configure Primary domain controller (Node1)
Power on Node1 and log in. In “Configure your server” window select “Active Directory”.
Select “Start the Active Directory Wizard” and “Next”.
Select “new domain” and “next”.
Select “create new domain tree” and “next”.
Select “create new forest of domain trees” and “next”.
Enter domain name (sdlcdomain.int) and next.
Accept short NetBIOS name and next
Accept default locations and next.
Accept default folder location and next
OK to unable to find DNS server
36 Setting Up the Scalar DLC
Page 43
Yes to install DNS and next
Select permissions “compatible only with windows 2000 servers” and “Next”. Set directory
services restore mode password. Confirm and Next and Next
Insert Windows 2000 Advanced Server CD and OK and Finish.
Unselect show this screen at startup in Configure your server window.
Remove CD.
Restart Node1.
Note
Step 2 Bring Node2 to the domain
Power on Node2 and log in
Right click My Computer and select Properties.
Open Network Identification and Properties
Select Domain and enter <domain name> and OK (sdlcdomain)
Enter user name and password and OK (administrator and password)
Wait for Welcome to domain and OK and OK to reboot and OK and Yes.
Log on to domain as administrator.
Step 3 Set up Backup Domain Controller (Node2)
In the Configure your server window select Active Directory.
Select Start the Active Directory Wizard and Next
Make changes to domain user account information on Node1 at this time.
Select “additional domain controller” and next
Enter user name and password (administrator and password) and Next
Accept domain name and next
Accept default locations and next
Accept default folder location and next
Set “directory services restore mode password” (password). Confirm and Next.
Finish and unselect Show this Screen at startup in Configure your server window. Restart.
After restart, launch Start > Settings > Control panel > Add/Remove Programs > Add/Remove Windows Components > Networking Services > Details
Select Domain Name System and OK and next
Insert Windows 2000 Advanced Server SP4 CD and OK and Finish.
Remove CD.
Restart Node2.
Step 4 Review network settings on both nodes (Public and Private). Restore DNS to the values
described in Step 2
Step 5 Review the Domain Operations mode, it should be ‘Native’. Change if required.
Installation Guide 37
on page 35 and Step 4 on page 35.
Page 44
On Node1 open Start > Programs > Administrative Tools > Active Directory Domains
and Trusts.
Right-click <Domain name> > Properties > General.
If Domain operation mode is Native, just close the dialog pane, otherwise press Change
mode button and then Yes to confirm changing mode.
Windows 2003
Step 1 Configure Primary domain controller (Node1)
Power Up Node1. Insert Windows 2003 Server CD. Start > Manage Your Server
Add or remove a role
Next. The wizard will detect network settings.
Typical configuration for first server and Next
Enter full DNS name for new domain (SDLCDOMAIN.INT) and Next. Next to confirm
Select 'No, it should not forward queries' and Next.
Review summary and Next.
Press OK to confirm restart when needed.
Choose 'Public' network.
Unselect "Enable security on the selected interface”. Next.
(for the PC with three and more network interfaces) Select ‘Private’ and Next.
Finish.
When the ‘ready-to-shutdown’ window appears remove Windows 2003 Server CD. Node1
will auto-restart and continue the setup.
Next. Finish, Close 'Manage Your Server'.
Correct Network Settings for Node1, as described in Step 4
Step 2 Join Node2 to domain.
Power up Node2. Start > My Computer (right-click) > Properties > Computer name.
Add description (optional) and press Change.
Choose domain and enter domain name (SDLCDOMAIN). OK. The domain admin login is required.
OK. wait till the Node2 joins to domain.
OK. 'You must restart' and OK.
OK, OK, and Yes for restart Node2.
Step 3 Configure Backup Domain Controller on Node2
on page 37.
After Node2 is power up log on into SDLCDOMAIN domain (Options button, change Node2 name SDLCCLUST2 to domain name SDLCDOMAIN) as domain admin.
Start > Manage Your Server > Add or remove a role
Next. The wizard will detect network settings.
Choose Domain Controller (Active DIrectory) and Next.
38 Setting Up the Scalar DLC
Page 45
Summary and Next and Next and Next.
Choose 'Additional domain controller' and Next.
Enter domain admin name/password and Next. Next.
Review the active directory DB and log folders (do NOT change unless necessary). Next.
Review the System Volume folder (do NOT change unless necessary). Next.
Enter domain admin password and confirm. Next.
CAUTION
passwords like 'password', 'qwerty123', etc. The password must contain both letters and numbers or other symbols like '+' or '_' and its length must be at least 8 symbols.
Review summary and Next. The wizard will install Active Directory service. Finish. Restart
Now to complete.
Finish configure Backup Domain Controller. Node2 is restarted. Log on as domain admin, then Finish.
Insert Windows 2003 Server CD. Start > Manage Your Server > Add or remove a role.
Next. The wizard will detect network settings.
Choose DNS Server and Next.
Summary and Next and Next.
Select 'Create forward lookup zone for small networks' and Next
Select 'An ISP maintains the zone...', as the Node2 is the secondary DNS, and Next.
Enter the zone name (any user-friendly, for example, SDLCZONE2) and Next.
Enter Master DNS (Node1 IP - 192.168.0.201), press Add, then Next.
Select 'No, it should not forward queries' and Next.
Windows2003 contains advanced security that strictly declines plain
Finish, and Finish.
An error window appears: ‘No it should not forward queries”; Error name:
CAUTION
DNS, the configure a DNS server wizard could not configure root hints’. Press OK.
Remove Windows 2003 CD and restart Node2.
Step 4 Review the Domain functional level, it should be ‘Windows 2000 native’. Change if required.
On Node1 open Start > Programs > Administrative Tools > Active Directory Domains
and Trusts.
Right-click <Domain name> > Raise Domain Functional Level.
If Current domain functional level is Windows 2000 native, just close the dialog pane,
otherwise select ‘Windows 2000 native’ level and then OK and OK to confirm changing level.
Restart Node1.
Installation Guide 39
Page 46

Setting Up the RAID disk

Same on both Windows 2000 and WIndows 2003.
Step 1 Power up Node1 and log in as Administrator for SDLCCLUSTER (cluster)
Step 2 Prepare to Format RAID disk
Right click “My Computer” and select “Manage”
Select “Disk Management”. Write Signature Wizard should start. Press “Next”.
Select “Disk 0” to write a Signature and press “Next”.
Unselect “Disk 0” to Upgrade, press “Next” and then “Finish”.
Step 3 Format RAID
Right click unallocated space and select “Create Partition”. Create Partition Wizard starts. Click Next.
Select “Primary Partition” and press “Next”.
Set maximum value in “Amount of Disk Space to Use” and press “Next”.
Select “Assign a Drive Letter” and select “R:” and press “Next”.
Select “Format this Partition with the Following Settings”
Set “File System” to “NTFS”
Set “Allocation Unit Size” to “Default”
Set “Volume Label” to “Cluster Raid”
Select “Perform A Quick Format”
Press “Next” and “Finish” and let format complete.
Step 4 Shutdown Node1 after the RAID is formatted. Power up Node2 and log in as Administrator for
SDLCCLUSTER (cluster).
Step 5 Join RAID disk
Right click “My Computer” and select “Manage”
Select “Disk Management”.
Right click “Cluster Raid”. Select “Change Drive Letter and Path”.
Select “Edit” and “Assign Drive Letter” to “R”.
Press OK. Press “Yes” to confirm.
Step 6 Shutdown Node2. The RAID is on.

Configuring Cluster Service

Windows 2000 Advanced Server and Windows 2003 Server require completely different procedures.
Windows 2000
Step 1 Power up Node1 and log in as Administrator to SDLC1 (this computer)
40 Setting Up the Scalar DLC
Page 47
Step 2 Configure Cluster Service on Node1
•Select Start > Settings > Control panel > Add/Remove Programs > Add/Remove Windows Components >> Cluster Service. Press Next.
Insert Windows 2000 Advanced Server SP4 CD and press OK. Cluster Service Configuration Wizard will start. Press “Next”.
Click “I Understand” and “Next”.
Select “The First Node in the Cluster” and “Next”.
Set cluster name to SDLCCLUSTER and “Next”.
CAUTION
Set User Name and Password (“administrator” and “password”). Set Domain to “sdlcdomain”
and “Next”.
Ensure that “R: Cluster Raid” is in managed disks and “Next”
Select “R: Cluster Raid” and “Next” and “Next”.
Set up Cluster Network
For Network Name “public” select “Enable this Network for Cluster Use”.
Select “All Communications (mixed network)” and “Next”.
For Network Name “private” select “Enable this network for cluster use”.
Select “Internal Cluster Communications Only (Private Network)” and “Next”.
Ensure that “private is at the top of Networks list and “Next”
Set “Cluster IP address” to <ip address> (192.168.0.222 in lab)
Set “Subnet Mask” to 255.255.255.0
Set “Network” to “public” and “Next”.
“Finish” and “OK” to Cluster Service Started Successfully.
The cluster name must not be longer than 14 symbols.
Finish and eject CD and close all windows and shutdown Node1
Step 3 Power up Node2 and log in as Administrator for SDLC2 (this computer)
Step 4 Configure Cluster Service on Node2.
•Select Start > Settings > Control panel > Add/Remove Programs > Add/Remove Windows Components >> Cluster Service. Press Next.
Insert Windows 2000 Advanced Server SP4 CD and press OK.
Power on Node1 and wait for <ctrl><alt><del> (log in) screen.
On Node2 Cluster Service Configuration Wizard will start and Next
Click “I Understand” and “Next”.
Select “Second or Next Node in the Cluster” and “Next”.
Set cluster name as SDLCCLUSTER
Select “Connect to Cluster As”.
Installation Guide 41
Page 48
Set User Name and Password (“administrator” and “password”). Set Domain to “sdlcdomain”
and “Next”.
Set password as “password” and “Next”.
“Finish” and “OK” and “Finish”.
Step 5 Remove CD and close all windows.
Step 6 Ensure the cluster works.
Select Start > Programs > Administrative Tools > Cluster Administrator
Select Groups > Cluster Group
Select File > Move Group to verify the cluster is working properly
Move group again and return ownership to Node1.
Step 7 Shutdown Node2
Windows 2003
Step 1 Power on Node1. Log on as self-domain admin.
Step 2 Create Cluster on Node1.
Start > Administrative Tools > Cluster Administrator
Choose 'Create new cluster' and OK. Next. Enter cluster name (SDLCCLUSTER2003) and Next.
CAUTION
Review Node1 name and Next. The wizard will analyze an existing configuration.
Next. Enter cluster IP (static, unique) and Next.
Enter domain admin account & Password. Next.
Review cluster summary and Next. Wizard creates a cluster.
Next and Finish.
Step 3 Join Node2 to Cluster
Power on Node2 and wait till it comes up. Wait circa 5 min until the virtual cluster name will
Start > Administrative Tools > Cluster Administrator. Choose 'Open Connection to cluster'
The cluster name must not be longer than 14 symbols.
be available from Node2. Switch to Node2.
and enter the cluster name (SDLCCLUSTER2003).
OK. Then File > New > Node. Add new Node wizard starts.
Next. Add, then Next. The wizard will analyze an existing configuration.
Enter domain user account & password. Next.
Review cluster summary and Next. Wizard adds node to a cluster.
Next and Finish. The cluster is ready.
42 Setting Up the Scalar DLC
Page 49
Step 4 Ensure the cluster works.
Select Start > Administrative Tools > Cluster Administrator
Select Groups > Cluster Group
Select File > Move Group to verify the cluster is working properly
Move group again and return ownership to Node1.

Installing Scalar DLC Software

Same as in plain Failover solution. See Installing Scalar DLC Software on page 28.
Note
If required the user security policy can be modified on Primary domain controller (Node1) via Start > Administrative Rules > Domain security policy; choose Account policies > Password policies.

Post-install Checklist

Nodes
Node1 computer name (14 symbols max)
Node1 public IP address
Node2 computer name (14 symbols max)
Node2 public IP address
public Subnet mask
public default Gateway = Node1 public IP
public preferred DNS = Node1 public IP
public alternate DNS = Node2 public IP
Node1 private IP address
Node2 private IP address
private subnet mask
private preferred DNS = Node1 private IP
private alternate DNS = Node2 private IP
Local administrator login name and password (same on both nodes)
Scalar DLC serial number (same on both nodes
Cluster
name (14 symbols max)
IP address
Subnet mask = public Subnet mask
Domain
•name
domain admin name and password
directory services restore mode password
Installation Guide 43
Page 50
Configuration
library SN
DB backup to RAID
DB backup to floppy
clients configured and tested
hardware configured and tested
email address settings
contact information
client type(s)
target card model
•License
Node1 SID
Node1 license string
Node2 SID
Node2 license string

Common Setup Notes

If changes are made to the RAID or it is powered off/on a Hard Disk Changed message may appear during reboot.
F1 to enter bios
Esc without making changes
•OK
The above will also happen when using a Jump Drive.
If a Jump Drive is in the USB during boot up an invalid disk error may happen
Reset the time when finished with the installation.
If the RAID is not new initialize it before starting it. The whole procedure takes approximately 6 hours.
WinZip needs to be installed and is not by default
Leave RAID off for a minimum of 20 seconds before powering back on
Hang on boot up at ATI Rage SDRAM Bios is not an uncommon condition
Immediately after the install is finished, if the cluster groups do not move from Node1 to Node2, shutdown Node1 and restart Node2. Make sure that Scalar DLC goes online for Node2, then restart Node1.
Set the event logs to overwrite when necessary. They will fill up often otherwise.
If the Ethernet card is installed with Wake on Lan Feature, disable it.
Typical user account security policy requires the password more than 6 symbols long and contained both numbers and letters in both small and capital.
44 Setting Up the Scalar DLC
Page 51

Installing the Scalar DLC

The Scalar DLC software must be installed on a PC running Windows 2000 / 2003. The Management GUI is installed as a part of the Scalar DLC software. After the software is installed, a remote user can connect to the Scalar DLC host.
Note
During the installation process, all required components are installed. System restart may be necessary after the installation of certain components. The system will warn the user that the restart is required, and the installation process will continue until all files have been installed.
•Before
Using the Scalar DLC setup engine install the required S
•After
To install the Scalar DLC software and all required components, local administrator rights are required.
The cluster solutions (both failover and self-domain) require the domain user with either local or domain administrator rights.
installing the Scalar DLC perform the Solution Checkup on page 45.
oftware Components on page 45.
this is finished, install Scalar DLC Software on page 50.

Solution Checkup

Make sure the appropriate solution is set up before installing the Scalar DLC.
See Setting Up the Standard Solution
Up the Self-Domain Solution on page 33.
on page 7, Setting Up the Failover Solution on page 13, and Setting

Software Components

Figure 14 on page 46 shows the components that are to be installed during the Scalar DLC setup process.
The required components that are currently not
Installation Guide 45
installed are marked automatically for the installation.
Page 52
Figure 14 Scalar DLC Setup Components
The following components must be installed and configured for the proper performance of the Scalar DLC software service:
Microsoft Windows 2000 Service Pack 4 (only for Windows 2000)
Microsoft Internet Explorer ver. 6.0 or newer (only for Windows 2000)
•Java
Apache Web Server ver.1.3.27
Secure Socket layer (SSL), optional
Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
MSDE 2000 Service Pack 4
2 Runtime Environment (Java 2) 1.4.2_09

Silent Mode

When a customer selects silent mode, all information that is required for the selected installation must be entered before the install process starts.
The install process continues until everything is complete, including automatically restarting the computer and logging on.
Note that the complete installation of both the required components and Scalar DLC software will take some time (circa 15-30 minutes).
Note
46 Installing the Scalar DLC
ADIC does not recommend using silent mode when installing Scalar DLC failover / self­domain solution.
Page 53

Windows Service Pack

The SP4 for Windows 2000 operating system must be used with the Scalar DLC software. After the service pack is installed, a restart is required. Then the system will configure the installed tools and services.
Note
ADIC supports the Win2000 SP4 developed by the Microsoft. This service pack can be used with all versions of Windows 2000 (Professional, Server, Advanced Server, etc.).
The SP1 for Windows 2003 is required for the Scalar DLC but not included onto the Scalar DLC Install CD. It must be installed with WIndows 2003.

Microsoft Internet Explorer

The Scalar DLC software is compatible with the MS IE browser 6.0 or newer version. ADIC offers the MS IE 6.0 installation kit. After the MS IE is installed, a restart is required. After rebooting, the system continues to configure the installed Internet Explorer tools and services.
Note
The installation of MS IE 6.0 under Windows 2003 is not required.

Java 2 Runtime Environment

The Java2 component installs over an existing Java runtime environment without producing a warning message. By default, the Java2 is installed in the <%SystemDrive%>\Program Files\Java\j2re1.4.2_09\ directory. An advanced user can install the Java2 to any directory desired, but ADIC recommends against this action.
Note
The Java2 installation may ask for a restart. ADIC recommends rebooting the PC.
Remove
Removing Java is performed via standard Windows Add/Remove Programs engine. A restart may be required afterwards.
Note
It is recommended also to check <%SystemDrive%>\Program Files\ afterwards. If Java folder is not removed, remove it manually.

Apache HTTP Server

ADIC does not recommend installing the Scalar DLC software on a machine with a previously installed copy of Apache Server. During installation, the configuration file overwrites any configuration file present on the hard drive without providing a warning. By default, the Apache HTTP Server is installed in the <%SystemDrive%>\Program Files\Apache Group\Apache\ directory. An advanced user can install the Apache HTTP Server in any desired directory.
If the default Apache directory exists, the installation provides a warning message.
Installation Guide 47
Page 54
Figure 15 Warning: Apache
Secure Socket Layer
The Secure Socket Layer (SSL) protocol encrypt the data that has been sent/received via the web. The SSL family of protocols includes also Transport Layer Security (TLS).
The SSL is built into all major browsers (Internet Explorer, Netscape), so implementing the SSL component into the Scalar DLC activates this feature when a customer launches the Scalar DLC Management GUI as the browser applet. Also the SSL encryption feature is activated when a customer launches the Java-based application Scalar DLC Manager which represents the same Management GUI. The details on Management GUI are described in the Scalar DLC Reference Guide, Configuration chapter.
The following are characteristics of SSL/TLS:
Generic enough to be incorporated into many applications
Provides security between the transport (TCP protocol) and upper application layer protocol such as HTTP, FTP, or TELNET.
Supports encryption, authentication, and key exchange
Encrypts data so that anyone who intercepts is unable to read it.
Assures clients that they are dealing with the server they intend to connect to.
Prevents any unauthorized clients from connecting to the server.
Prevents anyone from meddling with data going to or coming from the server.
Three protocol capabilities: authentication, encryption, and key exchange
Remove
Removing Apache is performed via standard Windows Add/Remove Programs engine. It is recommended to Stop the Apache service before (Start > Programs > Apache HTTP Server > Control Apache Server > Stop) and then remove the Apache itself.
Note
48 Installing the Scalar DLC
It is recommended also to check <%SystemDrive%>\Program Files\ afterwards. If Apache folder is not removed, remove it manually.
Page 55

Microsoft SQL Server Desktop Engine 2000

If the Microsoft SQL Server 2000 is installed already, it is not required to install the MSDE 2000. If there is either MSDE 7.0, or MS SQL Server 7.0 installed on the PC, the installation upgrades it for the MS SQL system service remains workable.
By default, the MSDE 2000 is installed in the <%SystemDrive%>\Program Files\Microsoft SQL Server\ directory. An advanced user can install the MSDE 2000 in any desired directory. After the MSDE 2000 installation is completed, re-start the system if required.
If the Scalar DLC should be installed as a Failover solution, the MS SQL 2000 should be installed on a shared disk (RAID - R:) to the ‘specified’ folder that must be shared, too.
Figure 16 MSDE 2000 Installation

MSDE 2000 Service Pack 4

The SP4 for MSDE 2000 was designed to fix bugs and security holes found in the basic version of the software (MSDE 2000). Because the Scalar DLC uses the SQL database to store all system information this service pack is required for the correct performance of the Scalar DLC software.
Note
CAUTION
Remove
Removing MSDE with the service pack is performed via standard Windows Add/Remove Programs engine. The MSDE SP4 separately cannot be removed. Restart is not required.
Installation Guide 49
If there is no MSDE 2000 but complete MS SQL 2000 installed, do not install this service pack. Go to the http://www.microsoft.com SQL 2000, and install it manually
ADIC recommends installing Service Pack 4 for MSDE 2000. Otherwise a security hole in MSDE 2000 remains open and could be used by internet viruses or worms (for example, Slammer).
instead, download the Service Pack 4 for MS
Page 56

Scalar DLC Software

All Setup windows contain the following buttons:
•Back
•Next
•Cancel
Follow the directions on the Setup Start window to install the Scalar DLC software.
Figure 17 Start Setup
Figure 18 Licensing
To continue the Scalar DLC Installation, accept the ADIC License Agreement. Click Next to proceed to the next screen (a copy of Figure 14
Proceed only after all of the required components are installed. Otherwise, the Scalar DLC Installation should be cancelled and launched again after the missing software is installed.
on page 46).
50 Installing the Scalar DLC
Page 57
Click Next to proceed to the following screen.
Figure 19 Personal Information
Table 6 Personal Information
Name Operation Description
User name Enter The user name (PC owner, by default).
Organization Enter The organization name (PC owner organization, by default)
Scalar DLC serial number
Enter The Scalar DLC serial number (5 digits). This number is shown
on the back of the Scalar DLC Installation CD.
Next, the installation process creates an account and registers the Scalar DLC internal components. See
Figure 20
for the local account, see Figure 21 on page 53 for the domain account, and see Figure 23 on
page 54 for the registration.
Installation Guide 51
Page 58
Figure 20 Create Local User Account
Enter the user account settings.
Table 7 Create User Account
Name Operation Description
User name Enter User account name, ‘SDLC’ by default
User
Enter User account password.
password
Confirm Enter Password must be confirmed.
User account
Select Local specifies the account type as local (default).
to be created
Domain specifies the account type as domain.
On host Supplied Local host name.
Domain Supplied The domain name (not editable for the local account).
Enter The domain name (editable for the domain account).
Server Supplied The domain server name, not editable.
Check (for domain
Click Check the rights on the domain. For a domain admin, the Next button
appears; otherwise, domain account installation is not available.
account only)
52 Installing the Scalar DLC
Page 59
Figure 21 Create Domain User Account
The user account should be entered in this window. Refer to Table 7
Note
If the account name already exists and the password does not match the existing account’s password, the User Account warning appears. See Figure 22 successfully, the Component Registration window appears. See Figure 23
Figure 22 User Account Warning
Domain administrator rights are required to install Scalar DLC under a domain account.
on page 53. Otherwise, if the user account is created
for the details. Click Next to proceed.
on page 54.
Go back and specify another user account or enter the correct password.
Installation Guide 53
Page 60
Figure 23 Component Registration
Note
Figure 24 Database Information
Do not use system tools to change the Scalar DLC user account created during installation. If a change is made, the Scalar DLC system will not start. To correct this situation, launch the Scalar DLC Add/Remove engine in the Repair mode.
See Table 8
Table 8 Database Information
SDLC Database name
MS SQL Server Supplied The default host name where the database should be created.
54 Installing the Scalar DLC
for the additional information.
Name Operation Description
Enter The default Scalar DLC database name, ‘SDLC’, will be used
unless the user specifies another name.
Page 61
Table 8 Database Information (Continued)
Name Operation Description
Compact Select The Compact Database schedule can be set here.
Backup Select The Backup Database schedule can be set here.
Backup file Enter Default database backup file, ‘SDLC_backup’ by default.
In folder Select Default database backup folder. The default is
%SystemDrive%\Program Files\Microsoft SQL Server\ (for standard solution) and %RAIDDrive%\Program Files\Microsoft SQL Server\ (for failover or self-domain solution).
Note
Specify the database name and backup/compact schedules, and press Next to proceed.
If the specified Scalar DLC database already exists, either keep it or create a new, clean database. See
Figure 25
it or create a new, clean database. See Figure 26 If a new database is installed, the next window, Email Notifications settings, appears. See Figure 27
57.
Figure 25 Selecting Database: Create or Keep
on page 55. If the database was created by an older version of Scalar DLC software, either update
The schedules for Backup and Compact jobs are described in more detail in the Database Utility section of the Scalar DLC Reference Guide. The backup and compact schedules can be changed later, as the database backup folder and filename, though the database name itself cannot be changed.
on page 56.
on page
Note
If a new database is created, click Next to proceed to the Figure 27 final screen.
Installation Guide 55
The old database may be used only with the same version of the Scalar DLC.
on page 57; otherwise, proceed to the
Page 62
Figure 26 Selecting Database: Create or Upgrade
See Table 9
for the additional information.
Table 9 Database Upgrade
Old Scalar DLC Version Additional activity
2.1
2.2, 2.2 SP1, 2.2 SP2, 2.2 SP3
2.3, 2.3 SP1, 2.3 SP2
2.4
2.5, 2.5 SP1, 2.5 SP2
2.6
Reconfigure SCSI Target manually after the database upgrade. See U
pgrading the Scalar DLC on page 86.
Upgrade database.
Upgrade database.
Upgrade database.
Upgrade database.
Use existing database.
If a new database is created, click Next to proceed to Figure 27 screen.
on page 57; otherwise, proceed to the final
56 Installing the Scalar DLC
Page 63
Figure 27 Email Notification Settings
Enter the email settings. See Table 10
Table 10 Email Notification Settings
Name Operation Description
Support service email address (To:)
Local email address (From:) Enter The email address shown in the From: field of emails.
Outgoing mail server: Name Enter The SMTP mail server name.
Outgoing mail server: Port Enter The SMTP mail server port.
Turn on email notifications Check Turn the email notifications on if the box is checked.
Note
Click Next to proceed to the figure below.
If the email settings are not properly configured, notifications will not be sent via email. The email parameters cannot be changed after the Scalar DLC is installed. Sending of email notification itself (on/off) can be changed later in Management GUI (Main Menu > Extended Service > Registration Information)
for details.
Supplied The email address for ADIC Scalar DLC technical
support: ‘watchman@adic.com’. Not changeable.
Installation Guide 57
Page 64
Figure 28 Setup Type
There are two types of Scalar DLC software installations: Complete and Custom.
The Complete Setup requires more disk space than various types of custom installs and places all Scalar DLC software components in the default directory: <%SystemDrive%>\Program Files\ADIC\SDLC\.
The Custom Setup allows to choose both the destination directory and the internal Scalar DLC software features that will be installed (if some features are not required, for example, Scalar DLC SCSI Client support). See Figure 29
for details.
Specify the installation type and click Next to proceed.
Figure 29 Custom Setup
58 Installing the Scalar DLC
Page 65
Table 11 Custom Setup
Name Operation Description
Scalar DLC
Supplied Mark/unmark the component for installation.
Components
Kernel Supplied The kernel of Scalar DLC software. Installed always.
Clients Supplied GUI The Scalar DLC Management GUI, main administrator
tool. Installed always.
Check SCSI The SCSI Client support. Installed optionally.
Check DAS and
The DAS Client support. Installed optionally.
NobleNet
Check ROBAR The ROBAR Client support. Installed optionally.
Physical Libraries
Supplied Scalar 10K The support of Scalar 10K single-aisle library. Installed
always.
Supplied Scalar 10K
DA
The support of Scalar 10K dual-aisle library. Installed always.
Supplied Scalar 1000 The support of Scalar 1000 library. Installed always.
Feature
Supplied The component name and disk space requirements.
Description
Install to Supplied The current destination folder where the Scalar DLC should be
installed. The default is
%SystemDrive%\Program Files\ADIC\SDLC\
Change Click Change the destination folder.
If the Scalar DLC destination folder already exists ensure that it is empty.
CAUTION
Never put any files in this folder because they will be removed with the Scalar DLC when the software is to be removed. See Add/
Remove Scalar DLC
Software on page 81.
Specify the components to install and the destination folder, and click Next to proceed.
Installation Guide 59
Page 66
Figure 30 Install SCSI Target Driver
When the SCSI Client component is selected for installation in either the Complete or Custom Setup, the installation process requests to install the SCSI and Fibre Channel Target driver. If this option is accepted, the SCSI Target Mode Driver installation proceeds after the Scalar DLC software is installed successfully. Otherwise the Scalar DLC software installation proceeds but the SCSI Target software features remain not operable if no SCSI Target driver is present in the system (for example, from a previous installation).
Note
This request is shown every time the Scalar DLC SCSI Client component is selected for the installation. ADIC recommends accepting the option and installing the drivers. If the drivers are installed already, decline this option. The drivers may be installed later manually as well.
For the details on SCSI Target Mode Driver installation and configuration process, see Inst
FC Target Drivers on page 74.
After the Scalar DLC components are installed, enter the registration information. See Figure 31
The SCSI/Fibre Channel Target drivers are needed to operate additional hardware (the SCSI card or FC card) required for using the Scalar DLC SCSI Target features. If this card is physically absent, the driver can be installed, but the Scalar DLC SCSI Target features will not work.
alling the SCSI/
on page 61.
60 Installing the Scalar DLC
Page 67
Figure 31 Registration Form
For licensing purposes, enter the registration information. Fields marked with the asterisk must contain valid information.
Table 12 Registration Form
Name Operation Description
Company name Enter The company’s name. Company address Enter The company’s mailing address. Contact name Enter The contact person’s name. Contact email * Enter The contact email address. SMTP Server * Enter The SMTP server name. Port * Enter The SMTP server port. Contact telephone Enter The contact phone number. Contact fax Enter The contact fax number. Service contract Check Marks the service contract feature as ‘signed’ if
checked. Site ID Enter The site ID (for the signed service contract). Scalar DLC S/N Supplied The Scalar DLC serial number. Scalar DLC location Enter The Scalar DLC location. Scalar DLC dial-in number Enter The Scalar DLC dial-in number. ATAC contact Select The Scalar DLC ATAC contact region (North America or
Europe)
Note
Installation Guide 61
The registration information can be changed later via the Management GUI (Main Menu > Extended service > Registration information).
Page 68
After entering the data, click Next to proceed. Review the information and make changes if necessary. See the following figure.
Figure 32 Review Registration Form
The request form can be printed out and/or send via email to ADIC customer support to obtain a license. See Table 13
for additional information.
Table 13 Review Registration Form
Name Operation Description
Send license request Check If checked, sends license request to ADIC.
Print now Click Print the registration form for mail or fax delivery.
Send email Click Send the registration form via email (see Figure 33
).
Figure 33 Email Registration Form
The email can be sent to any number of recipients. See Table 14
62 Installing the Scalar DLC
on page 63 for details.
Page 69
Table 14 Email Registration Form
Name Operation Description
From: Enter ‘From’ email address
To: Enter ‘To’ email address (list of addresses)
Subject Supplied Not changeable. Email ‘Subject’.
SMTP Server Enter The SMTP server name must be set here
Port Enter The SMTP server port must be set here.
Send Click Send email.
Exit Click Return to the previous dialog without sending email.
The Scalar DLC software is installed successfully. If no additional configuration steps are required, re-start the computer.
All activity concerning removing Scalar DLC software is described in Add/ page 81
Remove Scalar DLC Software on
Installation Guide 63
Page 70
64 Installing the Scalar DLC
Page 71

DAS Client

The DAS Client software allows the customer to use DAS interface with the Scalar DLC.

Installing DAS Client

The DAS Client software will be completely functional after the following configuration steps.
Step 1 Install the Scalar DLC software with the DAS support on the server PC. See S
Software on page 50. The server PC requires a restart.
Step 2 Start the Management GUI. Create the library configuration that the client requires. Create the
required mailboxes and clean/scratch pools. Create a DAS client and assign it to the created library. Refer to the Scalar DLC Reference Guide, Configuration chapter.
Step 3 Install the client application on the client PC.
Figure 34 Client software.
Figure 34 Select Scalar DLC DAS Client Components
shows the DAS Client components selection during the installation of Scalar DLC DAS
calar DLC
Installation Guide 65
Page 72
The installation will place the selected components in the <%SystemDrive%>\Program Files\ADIC\SDLC\ directory. Change the destination folder if it is required.
The DAS Administration Utility should be installed on a PC that will run the DAS Client software. See Ins
If there is a firewall between the Scalar DLC (server) host and the client host, the DAS/ACI firewall software should be installed on a PC inside the firewall. See Ins
68.
talling the DAS Administration Utility on page 67.
talling the DAS/ACI Firewall on page
Note
Figure 35
Figure 35 Scalar DLC DAS Client Network
The installation configures appropriate server, client, and media type values (see Table 15
The DAS/ACI firewall software can be installed directly on Scalar DLC host. In case of the Redundant solution, it should be installed on both cluster nodes.
illustrates the typical network structure.
).
Table 15 DAS Variables
Variable Explanation
DAS_SERVER Network names (TCP/IP) of the server which are accessed by the dasadmin
program. Both names are entered separated by a comma, only when installing dual DAS. The names must be resolvable on the computer into TCP/IP addresses. For the firewall connection, the DAS/ACI Firewall PC name is used here.
DAS_PORT A port being used to send DAS commands (for the firewall connection only).
DAS_CLIENT Name of the client under which the DAS PC is to access the server. The name
must be defined in the Scalar DLC database.
ACI_MEDIA_TYPE Default media type selected when using dasadmin if the parameter -t is omitted
from the command. See DAS Administration Guide for the details.
Note
66 DAS Client
These variables can be also set manually. This is very useful when several DAS Clients have to share one client host.
Page 73
Once the variables are set, the restart is requested. ADIC recommends accepting the restart so that the Scalar DLC DAS-Client software works properly.
Step 4 After the configuration is complete, the Scalar DLC software is ready to accept commands from
a DAS client.

Installing the DAS Administration Utility

The connection settings must be entered during the installation of the dasadmin software. See Figure 36 for a firewall-based connection and see Figure 37 on page 68
Figure 36 DAS Client Connections Using Firewall
for a direct (firewall-free) connection.
Property Operation Description
DAS Client connection
DAS/ACI firewall server name
Port Enter The firewall port (shown for Using DAS/ACI firewall selection only).
Scalar DLC server name
DAS Client name
ACI Media type
Select Not using firewall should be selected if there is no firewall between the
client host and the Scalar DLC host.
Using DAS/ACI firewall should be selected if a firewall exists between the client host and the Scalar DLC host.
Enter Name of the PC where the DAS/ACI Firewall software is installed
(shown for Using DAS/ACI firewall selection only).
Enter The Scalar DLC server name (shown for Not using firewall selection
only).
Enter The default DAS Client name. Refer to Table 15
Select The default ACI media type. Refer to Table 15
on page 66.
on page 66.
Installation Guide 67
Page 74
Figure 37 DAS Client Connection without Firewall
Note
If the connection type is specified incorrectly, the DAS Client software will install successfully but the connection with the Scalar DLC host cannot be established.

Installing the DAS/ACI Firewall

If there is a firewall between the Scalar DLC host and the client host, the DAS/ACI firewall software should be installed on the PC inside the firewall; this PC can be the Scalar DLC host itself. See Figure 35
66.
Note
Launch the DAS Client installation and when the component selection screen appears (see Figure 34 page 65), select a DAS/ACI Firewall component. See Figure 38 screen.
The DAS/ACI firewall software can be launched only under Windows or OS/2 platforms.
on page 69 for a DAS/ACI Firewall settings
on page
on
68 DAS Client
Page 75
Figure 38 DAS/ACI Firewall
Property Operation Description
Scalar DLC host name Enter The Scalar DLC server name.
Port Enter The firewall port to receive client commands.
After the DAS/ACI firewall is installed, the restart is requested. A new software service DAS-ACI Firewall appears in system services list.

Removing DAS Client

Using Add-Remove Software, launch Scalar DLC DAS Client and remove the software.
Installation Guide 69
Page 76
70 DAS Client
Page 77

SCSI/FC Target Drivers

The Scalar DLC software uses some SCSI and/or Fibre Channel adapters in Target mode to provide the customer access to the Scalar DLC via the SCSI.

SCSI and Fibre Channel Hardware

The SCSI and/or Fibre Channel adapters must be installed into the PCI-type slots as shown in Table 18 on page 72.
CAUTION
Before connecting SCSI Initiator (Scalar DLC / client host) and Target (Medium changer / Scalar DLC host) adapters with the SCSI cable, be sure that they match each other. See Table 16 that are currently supported and see Table 17
Table 16 SCSI and Fibre Channel Adapters
Adapter Type Connection (external) Max cable length, m
LSI 20860 SCSI 50-pin high density SE 5
LSI 8751D SCSI 68-pin high density HVD 25
LSI 8951U LSIU80LVD
QLA 2200 Fibre Channel SC duplex multi-mode -
QLA 2300 QLA 2310 QLA 2340 QLA 2342
Local SCSI
a
Connecting two adapters that do not match will cause hardware damage.
for a description of adapters
on page 72 for a match description.
SCSI 68-pin very high density
LVD/SE
Fibre Channel Small form factor multi-mode
optic LC
SCSI - -
12(LVD)
5(SE)
-
a. The driver is designed by ADIC to execute the SCSI backup applications right on the PC where the Scalar DLC software
is installed. No SCSI/FC hardware is required in this case.
Installation Guide 71
Page 78
Note
Table 17 Parallel SCSI Match
Single-ended (SE) SE, SE/LVD
Low voltage differential (LVD) LVD, SE/LVD
SE/LVD SE, LVD, SE/LVD
High voltage differential (HVD) HVD
The supported Fibre Channel adapters do match each other.
Table 18 SCSI/FC Adapters and PCI slots
The Local SCSI Target driver (powered by ADIC) is added for emulation the SCSI Target features on a PC without appropriate SCSI adapter. In the Management GUI, under the SCSI Target tab, the Local SCSI Target port appears, so the Target objects can be created and assigned to the SCSI Clients. However, this port is not reflected in the SCSI Target Port Tool because this utility shows only adapters that could operate either as Initiators or as Targets. Local SCSI Target only emulates the adapter port and sure cannot operate in Initiator mode.
Adapter Class Matched
Controller PN Slot 1 Slot 2 Slot 3
Standard 3-01632-01
Dual 3-01632-02
Standard 3-01632-03
Dual 3-01632-04
a. Adaptec 39160 is a two-channel SCSI adapter (see Two-channel Adapters
Adaptec 39160 (library)
Adaptec 39160 (RAID)
Adaptec 39160 (library)
Adaptec 39160 (RAID and library)
QLA 2340 / 42 Any target adapter (see Table
QLA 2342 (library) Any target adapter (see Table
on page 72) that is not used in Target mode.
Any target adapter (see Table
16 on page 71)
Any target adapter (see Table
a
16 on page 71)
16 on page 71)
16 on page 71)

Two-channel Adapters

Some adapters are designed as two-channel model so they are recognized by OS as two single-channel adapters. Device Manager shows two adapters, their Properties are, for example, PCI slot 2, Bus 1, Function 0 and PCI slot 2, Bus 1, Function 1 (note that the only difference is Function value).
For the Scalar DLC it means that it is technically possible to use single two-channel SCSI/FC adapter in both Initiator mode (Channel A / Port 1 - Function 0) to connect to the library medium changer, and in Target mode (Channel B / Port 2 - Function 1) to connect to the SCSI Client host (see Figure 39 of course, such two-channel adapters can be used for two different SCSI Clients, as if these clients were connected to the two different SCSI/FC target adapters, or as two single-channel initiator adapters if required.
on page 73). And
72 SCSI/FC Target Drivers
Page 79
Figure 39 Two-channel Adapter used for both library and client
The following adapters that Scalar DLC supports in Target mode are two-channel:
QLA 2342
Using FC adapters as Initiators to connect to the library medium changer requires additional setup which is described in Host/
Library Communication using Fibre Channel and SNC on page 127.

Initiator Driver

The Initiator driver can be installed before installing Scalar DLC software of after this operation as well. However, it should be done before
For each SCSI adapter found during the Windows setup and/or startup, the operating system usually installs the Initiator mode driver. However, for the newest adapter models, there can be trouble finding an appropriate driver because they are not present in a standard driver library. If such a problem encountered, follow the steps below.
installing SCSI Target drivers.
Note
Step 1 Be sure that you have a manufacturer disk with the appropriate software driver for your adapter,
Step 2 During setup/startup, the Windows 2000 / 2003 system opens Found New Hardware wizard.
Step 3 After Windows 2000 / 2003 startup, right-click on My Computer desktop icon, select Manage
Step 4 Repeat the steps above for each SCSI and Fibre Channel adapter that is not properly
Step 5 Re-start the PC if it is required.
Follow the instructions only if there is no proper Initiator mode driver(s) present in the system. When everything works, there is no need to re-install the drivers manually.
or you have downloaded this driver from the manufacturer’s web-site to the temporary folder. ADIC also offers all the required drivers at the <%Scalar DLC Install_CD%>\Drivers\Initiator folder.
Follow the wizard steps. Specify a driver location (disk or temporary folder) so that the system can install it.
and launch Device Manager system tool. Locate the Other Devices group and the SCSI adapter. Open the properties for the required device, select Driver tab and click Update Driver. Follow the Upgrade Device Driver Wizard steps. Specify a driver location (disk or temporary folder) so that the system can update it.
configured by the system.
The Target mode drivers now can be installed. Refer to Inst
Installation Guide 73
alling the SCSI/FC Target Drivers on page 74.
Page 80

Installing the SCSI/FC Target Drivers

The SCSI Target Mode Driver installation installs the Target driver for the SCSI/Fibre Channel Adapter(s) present on PC.
Note
CAUTION
Note
Figure below shows the Setup Start window of the SCSI Target software.
Figure 40 SCSI Target Start Setup
If the SCSI Target Mode Driver installation is launched on a PC with the installed target drivers from a previous version (for example, 2.4), the install engine will remove the old drivers. See A
If there is a Virtual SCSI Target Mode Driver installed, it should be removed before the SCSI Target Mode Driver installation. This can be done from Control Panel >
Add-Remove Programs.
There should be the Initiator driver(s) activated in the system before the Target driver(s) are installed. See Initiator Driver
dd/Remove SCSI Target Drivers on page 78.
on page 73 for the details.
Click Next to proceed.
74 SCSI/FC Target Drivers
Page 81
Figure 41 SCSI Target Licensing
Accept the ADIC License Agreement and click Next to proceed.
Figure 42 Personal Information
Enter the customer’s personal information. See Table 6
on page 51 for the meaning and required operation
of the fields. Click Next to proceed.
Installation Guide 75
Page 82
Figure 43 Driver Selection
Click the driver to select it. See Table 19
for driver selection details and Table 16 on page 71 for SCSI and
Fibre Channel adapters.
Table 19 Driver Selection
Name Operation Description
Drivers Check Mark/unmark the driver for installation.
See Table 16
on page 71 for a description of SCSI and Fibre
Channel adapters that could be used in the system.
Feature Description Supplied Driver name and disk requirements.
When the Local SCSI Target driver is installed, the following warning screen appears.
Figure 44 Local SCSI Target: No SIgnature
Press Yes and continue the installation: ADIC Local SCSI Target driver is not certified by Microsoft, no other failures in it are known currently.
76 SCSI/FC Target Drivers
Page 83
After the successful installation, if no additional configuration steps are required, the computer must be restarted.
Note
After rebooting, the adapters that should operate in Target mode are disabled. To enable them, use the SCSI Target Port Tool. See Activating Target Mode
on page 77.

Activating Target Mode

On the toolbar there will be a small three-penguin icon. Right click this icon and select Tools > Scalar DLC
SCSI Target Port Tool.
Figure 45 Access to SCSI Target Port Tool
The SCSI Target Port tool opens.
Figure 46 SCSI Target Port Tool: adapter disabled
Click Enable to enable the required SCSI Adapter(s) (as in the figure below).
Note
Installation Guide 77
The two-channel adapters are shown in the SCSI Target Port Tool as two different single-channel adapters. See Two-channel Adapters
on page 72.
Page 84
Figure 47 SCSI Target Port Tool: adapter enabled
(only for the Fibre Channel) Click Advanced to resolve the virtual World-Wide Name (WWN) and make the adapter available for the Failover (cluster) mode work if it is required.
Figure 48 FC Adapter Advanced properties
After enabling the adapter(s) and exiting the SCSI Target Port Tool, reboot if it is prompted.
Figure 49 Reboot after change SCSI Target properties

Add/Remove SCSI Target Drivers

To remove, modify, or repair the installed Target drivers, use the Add/Remove build-in system engine (Control Panel > Add/Remove Programs > SCSI Target Mode Drivers).
Note
The same engine should be used in order to perform an upgrade of the SCSI Target Mode Drivers from a previous version.
Before removing Target drivers, return the appropriate SCSI adapters to the Initiator mode, that is, disable them as Targets via the SCSI Target Port Tool. Refer to SCSI Target Port Tool section in the Utilities chapter of the Scalar DLC Reference Guide.
Step 1 Load the Scalar DLC Install CD. The autostart screen will appear.
Step 2 Launch the SCSI Target driver installation. The Add/Remove SCSI Target wizard will appear.
78 SCSI/FC Target Drivers
Page 85
Step 3 Select Remove to delete old target drivers installed on PC. Proceed until the remove engine will
request to restart PC.
Step 4 After reboot, open the autostart screen again. Launch the Scalar DLC installation (see S
DLC Software on page 50) to install both the Scalar DLC software and appropriate SCSI Target
drivers. If the Scalar DLC is installed already, launch only the SCSI Target driver installation (see
Inst
alling the SCSI/FC Target Drivers on page 74).
calar
Installation Guide 79
Page 86
80 SCSI/FC Target Drivers
Page 87

Upgrade, Remove, Repair

Add/Remove Scalar DLC Software on page 81 holds the basic instructions on Update, Remove, or Repair the Scalar DLC software.
U
pgrading the Scalar DLC on page 86 contains the detailed Upgrade instructions.
R
enaming and Repair on page 97 contains the detailed Repair instructions.

Add/Remove Scalar DLC Software

To add/remove the Scalar DLC software components launch: Control panel > Administrative Tools > Add-Remove Programs > Scalar DLC. This will run the Scalar DLC Add/Remove engine used to repair, modify, or remove the Scalar DLC software installed on the PC.
CAUTION
Note
Note
Note
For the Failover and Self-domain solution make sure that the Add/Remove is launched on the active ownership to the current node, and start Add/Remove engine again.
Before removing Scalar DLC software from any cluster node, launch SDLC Cluster Configurator and remove cluster configuration from the Scalar DLC resources (Remove button).
Local administrator rights are required to execute this procedure. Domain administrator rights are required if the Scalar DLC is installed under domain account and/or as the failover or self-domain solution.
The additional Repair instructions can be found at Renaming and Repair on page 97.
node. If not, cancel the operation, move Cluster group
Installation Guide 81
Page 88
Figure 50 Starting the Scalar DLC Add/Remove
Click Next to proceed to the following screen.
Figure 51 Modify/Repair/Remove
Specify the activity type and click Next to proceed.

Remove

CAUTION
The Remove process deletes all of the Scalar DLC software features except for the Scalar DLC account name and password that were set up during installation.
82 Upgrade, Remove, Repair
After removing the Scalar DLC software, always remove its SCSI Target drivers, too. See A
dd/Remove SCSI Target Drivers on page 78.
Page 89
Figure 52 Saving the Database
The Scalar DLC database can be either removed, or saved for future use. Click Next to proceed to the remove and the final screen.
Software programs such as Java2, Apache, MS IE, MSDE 2000, and so forth, are not removed and should continue to function normally. The Remove process also restores the old web server configuration software.
Note
To remove the software packages that are required by the Scalar DLC, use Control panel > Add-Remove Programs.

Repair

The Repair process allows the user to repair the damaged Scalar DLC configuration without re-installing the software.
Figure 53 Repair Options
Installation Guide 83
Page 90
Choose either the Server option to repair damaged Scalar DLC software components (see Server on page
84), or Database option to repair the damaged Scalar DLC database (see Da to proceed.
tabase on page 85). Click Next
Server
The Repair Scalar DLC Server process allows to re-register the Scalar DLC software components under new user account without re-installing them. This section has been added to avoid problems concerning the changes of user account name/password. This section also allows to repair the installed Scalar DLC software after the PC is renamed.
Figure 54 Repair Server Options
Select the repair options and click Next to proceed. See Table 20
Table 20 Repair Options
Name Operation Description
Computer renaming
Repair user account
If the Computer renaming mode is selected, the Repair checks all needed software components. If no software upgrade needed, the Repair process proceeds to the user account section. See User Account page 84.
Check Repair the Scalar DLC software after the computer has been renamed.
The Scalar DLC user account is also repaired.
Check Repair the damaged Scalar DLC user account. See User Account
page 84.
for details.
on
on
User Account
The repair user account screens look exactly the same as the user account creation screens appear during the Scalar DLC installation. See Figure 20 the domain account.
See Table 7
on page 52 for the user account settings.
on page 52 for the local account, and Figure 21 on page 53 for
84 Upgrade, Remove, Repair
Page 91
Note
If the account name already exists and the password does not match the existing account’s password, the User Account warning appears. See Figure 22 another user account.
To repair the Scalar DLC installed under a domain account, the domain administrator rights are required.
on page 53. Go back and specify correct password, or
If the account is repaired successfully, the Component Registration window appears. See Figure 23
54.
on page
Database
The Repair Scalar DLC Database process allows the user to repair the damaged Scalar DLC database. It contains the same database upgrade engine as the Scalar DLC installation and offers the same functionality.
Figure 55 Repair Database
Choose either the “recreate database” option to acquire the new, clean database, or “upgrade” option to update existing database according to current standards (the upgrade details are described at Table 9 page 56). Click Next to proceed to the upgrade and the final screen.
on

Modify

The Modify process allows to add or remove a number of Scalar DLC software features and to install the necessary software drivers. All changes will be applied only after system restart.
Installation Guide 85
Page 92
Figure 56 Modifying the System
During the installation process, all files are written to the hard drive but do not appear at startup on the configuration list. All of these files can be accessed and activated in the Modify process mode. It is allowed to add, register, or un-register the Scalar DLC software features that are the parts of the SCSI, or ROBAR, or DAS-interface. The un-register procedure leaves the software written on the hard drive but makes it inaccessible to the user.
Note
After Add/Remove process is finished, ADIC recommends restarting the PC.
The SCSI Client software feature cannot be installed completely without SCSI hardware (the SCSI/FC adapter) being present on the PC.

Upgrading the Scalar DLC

Although the upgrade engine is a part of Scalar DLC installation, some additional actions may be required. Depending on the configuration used, see S The instructions on which upgrade type is more preferable are located in Using Database from a Previous
Version on page 86 and Upgrading from 2000 to 2003 on page 87. Note also the Upgrade Issues on page
96.

Using Database from a Previous Version

If the customer has worked before with the older version of the Scalar DLC software, an upgrade must be performed in order to import the old database content to the new version. Use Table 21 upgrade method.
imple Upgrade on page 88 or Advanced Upgrade on page 92.
to select the correct
Note
86 Upgrade, Remove, Repair
The Advanced Upgrade can be used always, however sometimes it is possible to use the Simple Upgrade method.
Page 93
Table 21 Database Upgrade Methods
Old Database Version Old Solution
Standard Standard A
2.1
2.2, 2.2 SP1, 2.2 SP2, 2.2 SP3
2.3, 2.3 SP1, 2.3 SP2
2.4
Standard Standard A
Standard Standard A
Failover Standard A
Standard Standard S
Failover Standard A
Standard Standard S
New
Solution
Failover A
Failover A
Failover A
Failover A
Failover A
Failover S
Preferable Upgrade Method
dvanced Upgrade on page 92.
dvanced Upgrade on page 92.
dvanced Upgrade on page 92.
dvanced Upgrade on page 92.
dvanced Upgrade on page 92.
dvanced Upgrade on page 92.
dvanced Upgrade on page 92.
dvanced Upgrade on page 92.
imple Upgrade on page 88.
dvanced Upgrade on page 92.
dvanced Upgrade on page 92.
imple Upgrade on page 88.
imple Upgrade on page 88.
2.5, 2.5 SP1, 2.5 SP2
Failover A
Failover Standard A
Failover S
Standard Standard S
Failover A
2.6
Failover Standard A
Failover S
dvanced Upgrade on page 92
dvanced Upgrade on page 92
imple Upgrade on page 88.
imple Upgrade on page 88.
dvanced Upgrade on page 92
dvanced Upgrade on page 92
imple Upgrade on page 88.

Upgrading from 2000 to 2003

Plain upgrading the Scalar DLC from 2000 to 2003 platform is not supported, so if the customer wants to perform such operation, the setup order should be following:
Step 1 Backup the database to RAID disk, network resource or floppy (see Back up Scalar DLC
Database).
Step 2 Install the Scalar DLC 2.6 from scratch on Windows 2003 platform (see Setting Up the Scalar
DLC on page 7). Note that RAID needs no initialization in this case.
Step 3 Perform Recover database from old backup
on page 115.
Installation Guide 87
Page 94

Simple Upgrade

Follow this sequence to install the Scalar DLC on the host where the older version of the Scalar DLC software is working.
CAUTION
Note
Step 1 (For Scalar DLC ver. 2.1 only; for other versions, skip this step.)
Verify the current SCSI Target assignment. Log into the Scalar DLC Manager GUI (Start > Programs > ADIC Distributed Library Controller > Scalar DLC Manager) and look under SCSI Target > SCSI Management. Note which SCSI target cards are assigned to SCSI target IDs.
Step 2 (For Failover solution only; for Standard solution, skip this step.)
Remove Scalar DLC Cluster configuration.
Insert Scalar DLC Install CD. Close Autorun. Run
<CD>:\Scalar_DLC\Cluster\SDLC_ClusterConfig.exe.
Click Remove SDLC Cluster Configuration button. “OK” when complete
Step 3 Using Add-Remove Programs remove all following components.
It is strongly recommended to backup the Scalar DLC database to a file on a network resource or a floppy disk before launching Scalar DLC removing. If the Simple upgrade procedure fails, this backup file can be later used for the Advanced upgrade, as described in A
The instruction below is applied for both Standard and Failover solutions. Unless the other is specified, each operation is assumed to be executed on Node1.
dvanced Upgrade on page 92.
Remove all Scalar DLC Hot Fixes (mentioned separately from Scalar DLC itself) in descending order. Do not
Remove DAS Client software (if installed), as described in Removing DAS Client SCSI Target Drivers, as described in A now.
Initiate the install process for Scalar DLC. This will start by removing old release. During this process the system prompts, “Delete the Scalar DLC MS SQL Server database ‘SDLC’.” Select “No.” (see Figure 57 machine. Be sure to save the database so that it can be applied to the new release. Do not
reboot now.
on page 69, and
dd/Remove SCSI Target Drivers on page 78. Do not reboot
). This will preserve the configuration currently running on the Scalar DLC
reboot.
88 Upgrade, Remove, Repair
Page 95
Figure 57 Remove old Scalar DLC: do not delete the database
(optional) Remove Apache and Java. The newer/latest versions will be installed with the Scalar DLC 2.6.
Note
Reboot.
Step 4 (For Failover solution only; for Standard solution skip this step.)
Step 5 Insert Scalar DLC 2.6 Install CD. Install the Scalar DLC and all required components, as
Follow the Scalar DLC installation sequence.
During the installation of latest release the system informs that a database exists and requests whether the existing ‘SDLC’ database should be upgraded. Select “Upgrade” (see Figure 58 proceed.
(For Failover solution only; for Standard solution skip this substep.) When the Scalar DLC is installed on Node2, select “Use existing database“ and proceed.
It is recommended also to check <%SystemDrive%>\Program Files\ afterwards. If Java and Apache folders are not removed, remove them manually.
Repeat Step 3
described in Installing the Scalar DLC
on page 88 for the Node2.
on page 45.
) and
Installation Guide 89
Page 96
Figure 58 Install Scalar DLC: Upgrade database
(optional) Install the required SCSI Target drivers (see Inst
alling the SCSI/FC Target Drivers on
page 74). Then configure/activate the SCSI/FC Target adapter(s) via SCSI Target Port Tool, as described in Activating Target Mode
(optional) Install DAS Client software if required (see Ins
on page 77.
talling DAS Client on page 65).
Reboot the PC.
Step 6 (For Failover solution only; for Standard solution skip this step.)
Repeat Step 5
on page 89 for the Node2.
Step 7 (For Failover solution only; for Standard solution skip this step.)
Restore Scalar DLC Cluster configuration.
Insert Scalar DLC Install CD. Close Autorun. Run
<CD>:\Scalar_DLC\Cluster\SDLC_ClusterConfig.exe
Click Make SDLC Cluster Configuration button. “OK” when complete.
Step 8 Launch the Scalar DLC Manager (Start > Programs > ADIC Distributed Library Controller
> Scalar DLC Manager).
Step 9 (For upgrade from Scalar DLC ver. 2.1 only, otherwise skip this step.)
Resolve Port-Target assignment.
Log on as ‘admin’. Above the main Management GUI the SCSI configuration pop-up screen appears.
90 Upgrade, Remove, Repair
Page 97
Figure 59 SCSI Configuration Screen
Set the associations between Targets and Ports. Use the << button to associate Target with Target port. Remember that the customer may have multiple SCSI Targets. Each Target will have LUN 0; in case when a SCSI client exist for the target, the LUN 0 will be active with a client assigned to it.
Note
Figure 60 SCSI configuration: assign target(s) to port(s)
After this is completed, click OK. A pop-up confirmation window opens.
Figure 61 Confirmation to Restart Scalar DLC
The two-port adapters are shown in the Management GUI as two different single-port adapters.
Close the Scalar DLC Manager. Right-click on the three-penguin icon on the toolbar and select ‘Stop Scalar DLC’.
Figure 62 Access to Stop Scalar DLC
Installation Guide 91
Page 98
The Scalar DLC software service will be stopped.
Figure 63 Scalar DLC is successfully stopped
Re-start Scalar DLC using the Scalar DLC icon on the toolbar.
Figure 64 Access to Start Scalar DLC
After a successful start an appropriate message displays.
Figure 65 Scalar DLC is successfully started
Step 10 When the upgrade is complete verify that all target cards are correctly assigned and work ok.

Advanced Upgrade

Follow these steps to perform the upgrade of the Scalar DLC software on any PC and/or to restore the Scalar DLC configuration from an old version of the software.
Note
Note
Only the Advanced upgrade procedure can restore the Scalar DLC configuration from standard (basic) to failover (redundant) solution, or vica verse.
The instruction below is applied for both Standard and Failover solution. Unless the other is specified, each operation is assumed to be executed on Node1.
Step 1 Before
On the toolbar there will be a small Three Penguin Icon. Right click this icon and select Tools > Scalar DLC DB Tool.
92 Upgrade, Remove, Repair
removing the old release: backup an old database and keep it.
Page 99
Figure 66 Access to DB Tool
Launch Scalar DLC DB Tool and log on (see Figure 67
). If the Scalar DLC database has been installed under Trusted connection, only the local admin rights are required. If the Scalar DLC database has been installed under user account, either the SQL administrator logon name/ password, or the Scalar DLC SQL user name/password are required.
Figure 67 DB Tool Log On
Backup the database to file (for example, "OldSDLC.db"). Keep this file in any temporary folder or at floppy disk.
Installation Guide 93
Page 100
Figure 68 Backup Database
Step 2 (For Failover solution only; for Standard solution skip this step.)
Remove Scalar DLC Cluster configuration.
Insert Scalar DLC Install CD. Close Autorun. Run
<CD>:\Scalar_DLC\Cluster\SDLC_ClusterConfig.exe
Click Remove SDLC Cluster Configuration button. “OK” when complete
Step 3 Using Add-Remove Programs remove all following components.
Remove all Scalar DLC Hot Fixes (mentioned separately from Scalar DLC itself) in descending order. Do not
Remove DAS Client software (if installed), as described in Removing DAS Client on page 69, and SCSI Target Drivers, as described in A now.
Remove the old release of Scalar DLC with the database. Do not
Remove Apache, Java, and MS SQL 7.0. The newer/latest versions will be installed with the Scalar DLC 2.6.
Note
reboot now.
dd/Remove SCSI Target Drivers on page 78. Do not reboot
reboot now.
It is recommended also to check <%SystemDrive%>\Program Files\ afterwards. If Java and Apache folders are not removed, remove them manually.
Reboot the PC.
94 Upgrade, Remove, Repair
Loading...