Spectra Logic Spectra nTier300 User manual

Implementing nTier
Deduplication
featuring FalconStor ®Software

Implementing Spectra nTier Deduplication
Spectra Logic, Inc. Spectra European office FalconStor Software, Inc.
1700 N. 55th Street Magdalen Center, Robert Robinson Avenue 2 Huntington Quadrangle, Suite 2S01
Boulder CO 80304 Oxford Science Park, OXFORD 0X44GA Melville, NY 11747
www.SpectraLogic.com United Kingdom 631-777-5188 Fax: [phone]
www.falconstor.com
Copyright © 2003-2008 FalconStor Software. All Rights Reserved.
Spectra, Spectra Logic, and BlueScale are registered trademarks of Spectra Logic, Inc. FalconStor Software, FalconStor, and IPStor are registered trademarks of FalconStor Software, Inc. in the United
States and other countries. Windows is a registered trademark of Microsoft Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.
Spectra Logic and FalconStor Software reserve the right to make changes in the information contained in this publication without prior notice. The reader should in all cases consult with Spectra Logic and
FalconStor Software to determine whether any such changes have been made.
90990035 revision A

Implementing nTier Deduplication i
Contents
Contents
Introduction
nTier VTL featuring FalconStor SIR Deduplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Single Instance Repository (SIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
VTL configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Standard VTL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Advanced VTL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Getting Started
Delivered components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Install the nTier VTL appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Cable the VTL appliance to your storage network . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Install the VTL Console on an administrative computer . . . . . . . . . . . . . . . . . . . . . . . . .10
Launch the VTL Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Configure network connections to the nTier VTL appliance . . . . . . . . . . . . . . . . . . . . . .11
Backup server access to the nTier VTL appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Using the built-in Everyone_iSCSI client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Prepare client initiators to access your nTier VTL appliance . . . . . . . . . . . . . . . . . .13
Create a target for the iSCSI client to log onto . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Assign the virtual tape library/drives to the iSCSI target . . . . . . . . . . . . . . . . . . . . .14
Log the client onto the target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Using the built-in Everyone_FC client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Assign the virtual tape library to the Everyone_FC client . . . . . . . . . . . . . . . . . . . .16
Discover the virtual tape library from your backup server . . . . . . . . . . . . . . . . . . . . . . . .17
Create and run backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Confirm successful backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Configure optional services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Save your VTL system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Set deduplication options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
The VTL Console
Launching the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Understanding the objects in the tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
VirtualTape Library System object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
SAN Resources object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
SAN Clients object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Reports object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Physical Resources object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Search for tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Set console options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Manage users and administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Contents
Implementing nTier Deduplication ii
View the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Version Info tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Attention Required tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Changing pre-configured defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Changing the default IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Changing the default hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Changing the default password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Changing the default deduplication properties . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Key Features
Creating virtual tape libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Creating virtual tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Controlling backup server access to the nTier appliance . . . . . . . . . . . . . . . . . . . . . . . .38
Assigning virtual tape libraries to backup servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Auto Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Physical tape libraries and import/export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Prepare physical libraries/drives for use with FalconStor VTL . . . . . . . . . . . . . . . . .41
Assign physical libraries/drives to the virtual tape library . . . . . . . . . . . . . . . . . . . .42
Importing/Exporting tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Import a tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Export data to a physical tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Advanced Features
Protecting your FalconStor VTL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Automatically save the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Manually save the configuration as needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Restore the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Virtual tape drive compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Setting server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Configuring FalconStor VTL to send SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Monitor Deduplication
Status of running jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Scanner history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Repository statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Virtual index tape status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Reclaiming Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Replication
Replication process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Replication requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Replication to another nTier VTL appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Configure replication for virtual index tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Checking replication status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Contents
Implementing nTier Deduplication iii
Accessing data on a replicated VIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Manually start the replication process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Changing replication configuration properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Suspending/resuming the replication schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Stopping a replication in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Removing replication configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
iSCSI Clients
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Supported platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Managing iSCSI clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
iSCSI users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Windows client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Prepare client initiators to access your nTier appliance . . . . . . . . . . . . . . . . . . . . .74
Add your iSCSI client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Create targets for the iSCSI client to log onto . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Log the client onto the target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Setup using Open iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Prepare the iSCSI initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Add your iSCSI client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Create targets for the iSCSI client to log onto . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Linux client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Prepare the iSCSI initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Add your iSCSI client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Create targets for the iSCSI client to log onto . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Log the client onto the target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Solaris client configuration with iSCSI only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Prepare the iSCSI initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Add your iSCSI client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Create targets for the iSCSI client to log onto . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Log the client onto the target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Disable iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Fibre Channel Clients
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Fibre Channel hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
QLogic HBAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Adding a Fibre Channel client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
CallHome
Configure CallHome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Modify CallHome properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Script/program trigger information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Custom email destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Contents
Implementing nTier Deduplication iv
New script/program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Troubleshooting
General Console operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Physical resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Logical resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Client cannot see tape library/drive as provisioned by FalconStor VTL . . . . . . . .100
Deduplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
System configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Take an X-ray of your system for technical support . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Appendix
System security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Index

Implementing nTier Deduplication 5
Introduction
nTier VTL featuring FalconStor SIR Deduplication
nTier VTL provides FalconStor Virtual Tape Library (VTL) and Single Instance
Repository (SIR) functionality in a single, pre-configured appliance.
VTL comprises the following components:
• VTL Storage Appliance - A pre-configured appliance that includes all
storage used by VTL and SIR, including the VTL database, SIR index, and
SIR repository.
• VTL Console - The graphical administration tool, installed on a separate
workstation, where you configure VTL, add/configure clients, set properties,
manage the import/export of tapes, and view statistics.
• VTL Clients - The backup servers that use VTL. VTL supports Fibre
Channel (FC) and iSCSI backup servers on most major platforms.
nTier with FalconStor VTL increases the speed and reliability of backups that use
standard backup applications by leveraging disk to emulate industry-standard tape
libraries, such as Spectra tape libraries. VTL takes advantage of your iSCSI or Fibre
Channel network to transfer data to and restore data from a disk-based virtual tape
at ultra-high speeds.
Because VTL can emulate more tape drives than the physical library has, more
backup streams can run simultaneously, letting organizations easily complete
backups in the allotted window.
If you have physical tapes that you would like to protect using VTL, simply import
data from physical tape into the nTier VTL. To recover files from a physical tape, you
can use your nTier VTL to access those tapes for immediate recovery.
iSCSI/FC
High-speed backup using the VTL interface
Direct tape export
Spectra tape
library
nTier VTL architecture
Note: Check www.SpectraLogic.com for the most recent nTier guides.

Introduction
Implementing nTier Deduplication 6
Single Instance Repository (SIR)
Single Instance Repository (SIR) with FalconStor VTL to eliminate redundant data
without impacting your established backup window, thereby minimizing storage
requirements.
After a virtual tape is unloaded
from a tape drive and moved to
a slot, the deduplication
process scans the virtual tape,
analyzes the data, and
determines whether data is
unique or has already been
copied to the SIR repository.
The process then passes only
single instances of unique data
to the SIR repository; data is
compressed automatically. The
original virtual tape is replaced
with a virtual index tape (VIT)
pointing to SIR storage, freeing
considerable space on the tape
for more data.
Deduplication occurs as a separate, off-line process. Backup and restore jobs have
higher priority than the deduplication process. Deduplication jobs are temporarily
suspended when the tape being deduplicated is needed for backup or restore; when
the backup application finishes using that particular tape, the deduplication job
automatically resumes from where it left off.
If replication is configured, SIR replicates its repository and metadata. Data
duplicated across remote sites is deduplicated at the central site, enabling only
globally unique data to be replicated to the disaster recovery site.
VTL configurations
VTL supports two disk-to-disk-to tape (D2D2T) configurations that let you choose
how to configure the various components: third-party backup software, the VTL
appliance, and one or more physical libraries. In either configuration, VTL makes it
easier for you to manage virtual tapes and physical tapes.
•Standard Configuration - Backup software runs on a backup server or on
the VTL appliance and manages all tapes—virtual and physical. Data is
copied to physical tape using the backup software’s tape copy function.
•Advanced Configuration - Backup software runs on a backup server and
manages the backup to virtual tape. VTL manages the disk storage and the
export of data to the physical tape library.

Introduction
Implementing nTier Deduplication 7
Standard VTL Configuration
In the Standard VTL Configuration, the backup software manages all tapes—virtual
and physical—by treating the virtual tape library as though it were just another
standalone tape library attached to the backup server. To copy data from virtual to
physical tapes, the backup software’s Tape Copy function is utilized.
The Standard VTL
Configuration is ideal for
organizations that already have
a backup process in place with
which they are comfortable but
which is not meeting all of their
backup objectives. Adding a
VTL appliance as another tape
library allows you to easily
increase your parallel backup
streams and take advantage of
VTL rapid data recovery
without having to alter your
current configuration. With the
backup application managing
the entire backup process,
virtual tapes and physical tapes
are seen in the same way: a
virtual tape is just another tape.
With the Standard VTL Configuration, backups to virtual tapes occur quickly. Then,
at a later time, the backup server can copy the data to physical tapes without
impacting the production environment. Because the backup server performs the
tape copying function in addition to backups, additional overhead can be incurred by
the backup server. Therefore, it is best to perform tape copying at off-peak hours.
Backup server
Standard configuration
Backup to
virtual tape Backup to
physical tape
using backup
application
nTier VTL with
FalconStor
software
Spectra tape
library

Introduction
Implementing nTier Deduplication 8
Advanced VTL Configuration
In the Advanced VTL Configuration, the backup software manages backups to the
virtual tape library while the VTL appliance controls the export of data from virtual
tapes to physical tapes.
VTL dramatically accelerates backups by
acting as a de facto cache to your
physical tape library and enables data to
be moved to physical tapes as a
background process without impacting
production servers. This innovative
approach to backup addresses the
limitations of conventional tape backup.
Moreover, since VTL manages the export
of data from virtual to physical tapes,
there is no additional overhead for the
backup server.
With the Advanced VTL Configuration,
backups to virtual tapes occur very
quickly. Then, at a later time, when you
are done using a given tape, you can
export data to physical tape for offsite
vaulting or disaster recovery without
impacting the production environment.
VTL can also be set up in Auto Archive
mode so that after each backup to virtual
tape completes, data is automatically
exported to physical tape.
The Advanced VTL Configuration
requires you to set up the initial physical
tape library emulation from within the VTL Console so that there is a 1:1 mapping,
with identical barcodes, between virtual and physical tapes. This enables the
backup software to keep track of backup tapes and prevents tapes from being
created that would be unidentifiable by the backup software.
Whenever data is written to physical tape, the virtual tape can then be deleted or the
copy can be left on the virtual tape for rapid recovery. The physical tape will always
have the same barcode as its virtual tape counterpart. This gives you the flexibility to
easily restore from either virtual or physical tape.
When it comes time to restore, the backup software identifies the barcode of the
tape containing the needed data. If the data still resides on virtual tape (it was never
exported or it was exported with the virtual tape left intact), it can be restored very
quickly because it is being read from disk. If the data is only on physical tape, the
tape must first be re-imported into VTL with a few simple keystrokes in the VTL
Console so that the backup software can access it and restore in its usual manner.
nTier VTL with
FalconStor
software
Backup to
virtual tape
Advanced Configuration
Backup to
physical
tape using
VTL Export
Backup server
Spectra tape
library

Implementing nTier Deduplication 9
Getting Started
nTier VTL appliances are designed for quick setup using pre-configured defaults.
This section guides you through setting up VTL using these defaults. Refer to
“Changing pre-configured defaults” for information about modifying defaults.
Delivered components
Verify that you have received the following items:
• nTier VTL appliance with FalconStor software
• Two or three power cords, depending upon the nTier VTL configuration
• Slide rail assembly kit
• VTL Management Console CD
• Product keycode certificates
• Installation guide for the nTier VTL configuration
Product keycodes have already been installed on the appliance.
Install the nTier VTL appliance
Install the nTier VTL by following the instructions in the nTier VTL Installation Guide.

Getting Started
Implementing nTier Deduplication 10
Cable the VTL appliance to your storage network
1. Optional: connect your monitor, keyboard, and mouse to the appliance. You may
use a KVM device if necessary. You may also use the USB ports for connecting
a keyboard and/or mouse, instead of the PS/2 ports. Note that the nTier
operating system automatically detect USB devices upon system startup. Check
the monitor to determine when the nTier VTL is completely initialized.
2. Connect an Ethernet cable to the appropriate port.
• If your network has a DHCP server and you would like the appliance to
obtain an IP address automatically, connect an Ethernet cable to ETH0.
Connect the other end of the same cable to a network switch or other
Ethernet interface accessible by an administrative computer running the
VTL Console.
• If your network does not have a DHCP server, connect an Ethernet cable to
ETH1 (IP address 192.168.1.2). Connect the other end of the same cable to
a network switch or other Ethernet interface accessible by an administrative
computer running the VTL Console.
3. If your appliance has a Fibre Channel card, connect a FC cable from your switch
to each of the FC ports on the rear of the appliance.
4. Some appliances contain a SCSI card for import from/export to physical tape. If
you are using a SCSI cable to connect to your backup server, connect the cable
from the SCSI connector on the rear of the appliance to your backup server.
5. Attach one end of a power cord to the appliance and plug the other end into a
standard AC outlet. Repeat this step for the remaining power cords.
6. Power on the nTier VTL using the power button on the front of the appliance.
7. When the server has completed the startup process, a login prompt is displayed
on the attached monitor. You do not need to log in.
Install the VTL Console on an administrative computer
The VTL Console is the graphical administration tool where you configure VTL, add/
configure clients, set properties, and manage the import/export of tapes.
Install the Console on your backup server. Alternately, you can install the Console
on any number of Windows machines. To install the Console on a Windows machine
you must be a Power User or Administrator.
1. Insert the VTL Management Console CD into a CD/DVD drive.
Note: If necessary, you can change network settings later.
Note: To ensure redundancy, be sure to use all power cords.

Getting Started
Implementing nTier Deduplication 11
The setup program should start automatically. If autoplay is not enabled on your
Windows machine, navigate to the \Console\Windows directory on the CD and
run Setup.exe to launch the VTL Console install program.
2. Click the Install Products button on the first screen.
3. Click the VTL Console for Windows button.
4. Follow the steps in the Install Wizard to complete installation.
Launch the VTL Console
To launch the Console, select Start --> Programs --> FalconStor. Select the version
of the VTL Console that corresponds to your installation and then click VTL Console.
You can also double-click the VTL Console shortcut on your desktop.
Configure network connections to the nTier VTL appliance
DHCP If you used ETH0 to physically connect to the network:
1. Right-click on the VTL Servers object in the left pane of the Console and select
Discover.
2. Specify the subnet range of your VTL appliance and click OK.
3. Wait for the nTier VTL appliance hostname to appear in the navigation tree. The
hostname has the format xxxxx, where xxxxx is the number of your VTL
appliance, which is displayed on a label on your appliance.
4. When the hostname appears in the navigation tree, right-click on it and select
Connect.
5. Log in using the default user name root and the default password spectra (all
lower case and case sensitive).
Static IP
address
If you used ETH1 to physically connect to the network:
1. Right-click on the VTL Servers object in the left pane of the console and select
Add.
2. Enter the default IP address for ETH1 (192.168.1.2).
Note: When you are connected to a server, the server icon will change to show
that you are connected:
Note: If your administrative computer and the VTL appliance are on different
subnets, you must either change the default subnet range when using the
discovery process in the previous step or use a static IP address as explained
below.

Getting Started
Implementing nTier Deduplication 12
3. Log in using the default user name root and the default password spectra (case
sensitive and all lower case).
4. Click OK and wait for the nTier VTL appliance hostname to appear in the
navigation tree.
The hostname has the format FSxxxxx, where xxxxx is a unique number for your
VTL appliance, which is displayed on a label on your appliance.
Backup server access to the nTier VTL appliance
Use one of these access schemes, which determine how backup servers access the
nTier VTL appliance:
• In the default "Open Access" scheme, the pre-defined Everyone_iSCSI or
Everyone_FC client represents the backup server and all or some of your
virtual tape libraries/drives must be assigned to this client. This scheme is
applied when you follow guidelines for Everyone clients below.
• In a “Secured Access” scheme, access is dictated by creating specific
clients to represent specific backup servers. A backup server can access
only its own designated virtual tape library or drives via a dedicated port.
This scheme is applied when you add a SAN client as described in
’Controlling backup server access to the nTier appliance’.
Using the built-in Everyone_iSCSI client
On all nTier VTL appliances, iSCSI is enabled by default and the client
Everyone_iSCSI is already created. This special SAN client represents your backup
server but does not correspond to any specific client machine. Using this client, you
can create iSCSI targets that are accessible by any iSCSI client that connects to the
nTier VTL appliance. Refer to ’Create a target for the iSCSI client to log onto’.
Typically, assign your default virtual tape libraries/drives to the Everyone_iSCSI
client.
While such a publicly available target is convenient, it may not be appropriate for all
organizations. If your nTier VTL appliance will be shared by multiple backup servers,
you may want to use a “secured access” scheme, where access is dictated by
creating specific clients to represent specific backup servers instead of using the
built-in Everyone_iSCSI client. In this mode, each backup server can access only its
own designated virtual tape library or drives. Refer to ’Managing iSCSI clients’.
Note: Complete these steps if your backup server will communicate with the VTL
appliance using the iSCSI protocol.

Getting Started
Implementing nTier Deduplication 13
Prepare client initiators to access your nTier VTL appliance
Before a backup server (the client initiator) can communicate with a nTier VTL
appliance, the two entities need to mutually recognize each other. To do this, install
an iSCSI software initiator on every backup server that will use Everyone_iSCSI.
This software will let you add the nTier VTL appliance as a target portal and log the
client onto the iSCSI target you create on the nTier VTL appliance.
For Windows servers, you can download software from Microsoft’s website:
http://www.microsoft.com/windowsserversystem/storage/iscsi.mspx. The following
steps are for the Microsoft iSCSI Initiator. If you are using a different iSCSI initiator,
refer to the documentation provided by the vendor.
1. Run Microsoft iSCSI Initiator on the backup server using the shortcut on your
desktop or by selecting Start --> Programs --> Microsoft iSCSI Initiator -->
Microsoft iSCSI Initiator.
2. Click the Discovery tab, then click Add under the Target Portals group box.
3. Enter the nTier VTL appliance’s IP address or name (if resolvable).
To determine the IP address, go to the VTL Console. Select the nTier VTL
appliance object. The IP address is on the Login Machine Name line in the right-
hand pane of the Console.
Use the default port (3260).
Click OK to add the client.
Create a target for the iSCSI client to log onto
To create a target on the Everyone_iSCSI client:
1. In the VTL Console, expand the SAN Clients object in the left pane of the
console.
2. Expand the Everyone_iSCSI object.
3. Right-click the iSCSI object and select Create Target

Getting Started
Implementing nTier Deduplication 14
4. Enter a name for the target or accept the default and select the IP address of the
adapter on the nTier VTL appliance. The list includes all Ethernet adapters you
have configured on the server.
5. Use the default starting LUN.
LUN IDs must start with zero.
Once the iSCSI target is created for a client, LUNs can be assigned under the
target using available virtual iSCSI devices.
6. Confirm all information and click Finish to show the iSCSI target in the navigation
tree.
7. A message is displayed when the iSCSI target has been created successfully.
When you close the message, a prompt asks if you want to assign a resource
(virtual tape library or drive) to the target.
Select No to close the prompt or Yes to continue with step 2 under ’Assign the
virtual tape library/drives to the iSCSI target’. If you select No, refer to ’Assigning
virtual tape libraries to backup servers’ at a later time for information on
assigning virtual resources to client targets.
Assign the virtual tape library/drives to the iSCSI target
1. Expand the SAN Clients object until you see the target object. For iSCSI clients,
this is the object below the client name and iSCSI.
Right-click the target object and select Assign.

Getting Started
Implementing nTier Deduplication 15
2. Select the default virtual library/drives to be assigned to the target. All tape
drives in the library will be assigned to the selected client. If you want to assign
tape drives in the library individually, select the checkbox for that option.
You can assign a device (library or drive) to a target only once.
Click Next when you are done.
3. In the next screen, change the LUN for the resource (if necessary) to resolve
any conflict.
4. Confirm all information and click Finish.
Log the client onto the target
The following steps are for the Microsoft iSCSI Initiator. If you are using a different
iSCSI initiator, refer to the documentation provided by the vendor.
1. Return to the backup server. To see the iSCSI targets from the client machine,
run Microsoft iSCSI Initiator again or, if the application is still open, click the
Targets tab.
If the iSCSI target assigned to the client is not listed, click Refresh. Assigned
iSCSI targets should now appear.
2. Select the added target and click Log On. If it is desirable to have a persistent
target, select Automatically restore this connection when the system boots.
Click OK.
3. Click OK to log on to the target.
The status for the target will change from Inactive to Connected.
The Targets tab lists all iSCSI targets, whether or not they are connected. To log
off a backup server from its connection, select the target, click Details, select the
Target Identifier, and then click Log Off.

Getting Started
Implementing nTier Deduplication 16
If you selected the option to Automatically restore this connection, the iSCSI
target is listed in the Persistent Targets tab.
4. Click OK to close the iSCSI Initiator.
The backup server must now discover the assigned virtual tape library and drives
(refer to ’Discover the virtual tape library from your backup server’).
Using the built-in Everyone_FC client
Depending on the configuration you ordered, your nTier VTL may have a dual-port
Fibre Channel card installed and have Fibre Channel enabled by default. The SAN
client Everyone_FC is already created and FC HBAs are already set to target mode.
Assign the virtual tape library to the Everyone_FC client
1. Expand the SAN Clients object in the left pane of the console.
2. Right-click the Everyone_FC object and select Assign.
3. Select the default virtual library to be assigned to the client. You can also select
Allow tape drives in the tape library to be assigned individually to display the
virtual drives in the library.
You can assign a virtual device (tape library or tape drive) to a client only once,
even if the client has multiple targets.
Note: Complete these steps if your backup server will communicate with the VTL
appliance using the Fibre Channel protocol.
Note: If your nTier VTL appliance will be shared by multiple backup servers, you
must add a SAN client to represent each backup server and ensure that each
backup server can access only its own designated virtual tape library/drives.
Refer to ’Adding a Fibre Channel client’.

Getting Started
Implementing nTier Deduplication 17
Click Next when you are done.
4. Confirm all information and click Finish.
The backup server must now discover the assigned virtual tape library and drives.
Refer to “Discover the virtual tape library from your backup server”
Discover the virtual tape library from your backup server
To enable your backup server to recognize the default virtual tape library and drives,
perform a device scan on your backup server at the operating system level and then
use your backup software to scan for new devices as well.
Use your
operating
system to scan
for hardware
changes
The steps to do this vary according to the backup server’s operating system. To do
this on a backup server with Windows OS:
1. Select Control Panel --> Administrative Tools --> Computer Management.
2. In the left pane, under System Tools, select Device Manager.
3. In the right pane, right-click the backup server and select Scan for hardware
changes.
New devices representing the specific VTL resources will appear (the library
under Medium Changers and tape drives under Tape Drives) and if the
appropriate tape drive and tape library device drivers are installed on the backup
server, the correct device name and type are associated and the devices will
become ready for use by the backup software.
If a new device is unknown, right-click it to display its Properties. Acquire and
update the driver according to your Windows documentation. Your backup
software may include a procedure that updates drivers.
Use your
backup
software to
detect new
devices
The steps to do this vary according to your backup software.
After you complete the procedure, you are ready to create and run backup jobs.
Create and run backup jobs
Use your backup software to create backup jobs that point to the tapes in the virtual
tape library. Generally, backup comprises these steps but they can vary according to
your backup software:
1. Start a "tape inventory" process in your backup software.
Note: For all other platforms, such as Unix and Linux, consult the appropriate
reference material that came with your backup software for details on how to load
drivers and how to perform discovery for hardware changes.