Installation Guide - Home - Tandberg Data · Increasing storage space with DPS Expansion Module DPS...
Transcript of Installation Guide - Home - Tandberg Data · Increasing storage space with DPS Expansion Module DPS...
Installation GuideTandberg Data™ DPS1000 Series™Model: DPS1100 and DPS1200, Release: 1.3
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vAbout this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vAudience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vTypographical conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vRelated documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viSupport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vi
1 Preparing for Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Authenticating with CHAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Determining whether to use jumbo frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Increasing storage space with DPS Expansion Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Exporting to physical tape with a physical tape device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Enabling iSNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 Configuring DPS1000 Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Accessing the web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Configuring ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Configuring system settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Setting up certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Using DPS1000 Series with iSNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Configuring initiators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Setting up virtual tape libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Adding user accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Uninstalling DPS1000 Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 Configuring Windows Initiators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Adding initiators in DPS1000 Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Providing connection information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Providing users with information required for the connection wizard . . . . . . . . . . . . . . . 10Providing users with information required to connect manually . . . . . . . . . . . . . . . . . . . 11
Providing users with driver updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Providing access to iSCSI initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Enabling CHAP authentication on DPS1000 Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Connecting to DPS1000 Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Connecting with the connection wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Connecting manually with no authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Connecting manually with authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installing additional drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19For initiators that use CA ARCserve Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19For initiators that use HP Data Protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20For initiators that use IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20For initiators that use Microsoft Windows Backup Utility . . . . . . . . . . . . . . . . . . . . . . . . 21For initiators that use Symantec Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Adding virtual tape drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Contents | iii
4 Configuring Linux Initiators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Providing connection information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Installing the iSCSI initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Editing the iSCSI node name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Enabling CHAP authentication on DPS1000 Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Adding an initiator to DPS1000 Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Configuring authentication on the initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Connecting to DPS1000 Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Adding virtual tape drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33DPS1000 Series issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Initiator issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
A Bar Code Label Specification for LTO Ultrium Cartridges . . . . . . . . . . . . . . . . . . . . . . . .37
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
iv | Contents
Preface
Welcome to the DPS1000 Series Installation Guide. Tandberg Data DPS1000 Series is a data protection solution that enables Internet Small Computer System Interface (iSCSI) desktop systems and backup servers to perform backup and recovery operations. DPS1000 Series provides a shared system that can be used by up to 100 individual iSCSI initiators as a private tape library. This guide enables you to plan and perform DPS1000 Series deployment.
About this guide
The DPS1000 Series Installation Guide is designed to help you plan your DPS1000 Series deployment and configure DPS1000 Series.
The following chapters are included:• Preparing for Deployment — Describes configuration decisions that must be made before
deployment begins.• Configuring DPS1000 Series — Describes how to set up the default users and configure
DPS1000 Series settings.• Configuring Windows Initiators — Describes how to connect Windows initiators to
DPS1000 Series.• Configuring Linux Initiators — Describes how to connect Linux initiators to DPS1000
Series.• Troubleshooting — Describes problems you might encounter while operating DPS1000
Series and provides suggestions for resolving the problems.
In addition, the following appendices are included:• XpanTape Specifications — Lists the technical specifications for DPS1000 Series.• Bar Code Label Specification for LTO Ultrium Cartridges — Lists the bar code label
specifications required for the tapes used by a physical tape device.
Audience
This guide is designed for use by anyone deploying DPS1000 Series. Familiarity with system and network configuration is highly recommended.
The instructions in this guide were written under the assumption that you have read the DPS1000 Series Technical Overview, which provides an introduction to product functionality and concepts, and performed the tasks in the DPS1000 Series Quick Setup Guide.
Typographical conventions
This guide uses the following typographical conventions:
Convention Description
Bold Used for file names, field names, URLs, interface elements that are clicked/selected, and information that must be used literally.
Preface | v
This icon is used to note the user is responsible for performing the procedure that follows.
Related documentation
In addition to this installation guide, the DPS1000 Series documentation library includes• DPS1000 Series Technical Overview, which provides an introduction to product
functionality and concepts• DPS1000 Series Quick Setup Guide, which provides instructions for installing the
hardware and configuring DPS1000 Series on the network• DPS1000 Series help set, which provides detailed instructions for working with the web
interface• DPS1000 Series Release Notes, which provides information about system requirements,
known issues, and other information about the current release• DPS Expansion Module Installation and Administration Guide, which provides
instructions for unpacking, cabling, powering, and configuring Tandberg Data DPS Expansion Module, the external array that can be attached to DPS1000 Series for additional storage
Support
For service and support assistance, contact your authorized service and support representative directly. For Technical Support, refer to http://www.tandbergdata.com/.
Bold Italic Represents variables within file names, command syntax, URLs, or other literal text.
Italics Used for emphasis, book titles, and variables.
Monospace Used for text that is displayed on-screen, command names and arguments (syntax), code, and command-line text.
Monospace Italic Represents variables within command syntax, code, or command-line text.
Blue Text Used for cross-references.
Convention Description
vi | Preface
Preparing for Deployment
Tandberg Data DPS1000 Series is a data protection solution that enables Internet Small Computer System Interface (iSCSI) desktop systems and backup servers to perform backup and recovery operations. DPS1000 Series provides a shared system that can be used by up to 100 individual iSCSI initiators as a private tape library. Each tape library supports up to eight virtual tape drives. If the DPS1100 is deployed, up to 32 virtual tape drives can be connected to DPS1000 Series simultaneously. If the DPS1200 is deployed, up to 64 virtual tape drives can be connected simultaneously. For a complete overview of DPS1000 Series, see the DPS1000 Series Technical Overview.
To make more informed choices about your deployment, you should review this chapter before you deploy and configure DPS1000 Series.
Authenticating with CHAP
DPS1000 Series supports Challenge Handshake Authentication Protocol (CHAP) with Message-Digest algorithm 5 (MD5) to validate the target or the target and initiators. DPS1000 Series supports one-way authentication that validates the iSCSI initiator, and it supports mutual authentication that validates both the initiator and the target (DPS1000 Series). If you want to use CHAP for authentication, determine whether you want one-way or mutual authentication.
For information about configuring DPS1000 Series and initiators for CHAP, see Configuring Windows Initiators on page 9.
Determining whether to use jumbo frames
Jumbo frames are Ethernet frames that can carry a higher payload than other frames and may enable better performance. Jumbo frames are not available in all environments; however, if your network topology (including initiators, switches, and so on) supports them, you should enable jumbo frames during deployment. In DPS1000 Series, jumbo frames can be enabled for the iSCSI ports, but not for the management port.
For information about enabling jumbo frames in DPS1000 Series, see Configuring ports on page 4.
Note If your network does not support jumbo frames, do not enable them on initiators or DPS1000 Series. Doing so may result in dropped SCSI commands and unexpected behavior.
1
Increasing storage space with DPS Expansion Module
DPS Expansion Module is an optional external storage array that can be connected to DPS1000 Series to increase the amount of storage space for virtual tapes. For information about installing DPS Expansion Module, see the DPS Expansion Module Installation and Administration Guide.
Exporting to physical tape with a physical tape device
You can connect an optional physical tape device to DPS1000 Series to export virtual tapes to physical tape. Refer to the documentation for the physical library for installation instructions.
You must also create bar code labels for each cartridge that will be used with DPS1000 Series. See Bar Code Label Specification for LTO Ultrium Cartridges on page 37 for information about how to property label cartridges.
Note If a StorageLibrary T24 will be used, you must also enable the library to identify the type of media installed in the library when it scans bar codes. With this option enabled, the bar code scan includes two extra digits: L2 for an LTO-2 data cartridge, L3 for an LTO-3 data cartridge, or L4 for an LTO-4 data cartridge. Refer to the StorageLibrary T24 documentation for more information.
Enabling iSNS
Internet Storage Name Service (iSNS) enables you to manage multiple storage devices from a central location. This is useful if you have multiple DPS1000 Series appliances in your environment and want initiators to have access to a subset of them. For information about enabling the iSNS client on DPS1000 Series, see Help, which is available within the web interface.
2 | Preparing for Deployment
Configuring DPS1000 Series
You must configure the default user accounts, the DPS1000 Series appliance, and initiators.
Accessing the web interface
The DPS1000 Series web interface enables you to configure and manage DPS1000 Series.
To access the web interface
1. If necessary, determine the IP address of the DPS1000 Series appliance. a. Access the appliance through the console using any terminal program.
For example, to access DPS1000 Series from Microsoft Windows using the HyperTerminal connection wizard, select All Programs→Accessories→Communications→HyperTerminal from the Start menu. In the HyperTerminal connection wizard, enter a connection name, choose an icon to associate with the connection, and click OK. In the Connect To dialog box, select a communications port and click OK. COM1 is the port used by most systems. Depending on your version of HyperTerminal, you may be required to click the Configure button to display the Properties dialog box for the selected communications port. In the Properties dialog box, set the following information:
Bits per second = 9600 Data bits = 8 Parity = None Stop bits = 1 Flow control = None
Click OK.b. At the command prompt, enter one of the following to verify the configuration of the
DPS1000 Series Management port: • For the DPS1100:
netconfig -f eth0
• For the DPS1200:
netconfig -f eth2
The IP address, gateway, and netmask are listed.
2. Launch a web browser.
3
3. Enter http://ip_address, where ip_address is the management network interface address.
The browser may display a warning page and certificate errors. DPS1000 Series ships with a self-signed certificate that is used to sign its audit log and to establish a secure communication channel between your browser and the DPS1000 Series web application server, through Secure Sockets Layer (SSL). This self-signed certificate may cause your browser to display a certificate warning for the following reasons:• Many browsers warn you when a web application employs a self-signed certificate,
which is are not considered as secure as a certificate signed by a Certificate Authority.• When the DPS1000 Series default self-signed certificate is created, a temporary
hostname is used for the appliance. During deployment, this hostname most likely changed. Many browsers warn you when the hostname on the certificate and the hostname on the appliance do not match.
4. If the browser displays a warning, accept the certificate or add an exception (depending on your browser) and continue to the web interface.
5. Log in as the admin or str_admin user, which are the default user accounts:• The admin account is assigned the Appliance Administrator role, which enables this
user to perform appliance configuration. • The str_admin account is assigned the Storage Administrator role, which enables this
user to set up the initiators, configure the virtual tape libraries, create users, and perform other tasks.
For more information about roles, see “Managing users” in the Security section of the help set, which is available within the web interface.
Configuring ports
Before you configure the DPS1000 Series ports, gather the following information:
Name Description Your Value
Hostname An optional system hostname for the appliance.
DNS domain The name of the domain in which the Domain Name System (DNS) server belongs. You can set up to three DNS domains.Not required if using DHCP.
DNS IP address The IP address of the DNS server. You can set up to three DNS IP addresses.Not required if using DHCP.
iSCSI port 0:IP address
The IP address of iSCSI port 0. Not required if using DHCP, in which case this port is automatically named hostname-iSCSI0.
4 | Configuring DPS1000 Series
To configure port settings
1. Log in as the admin user.
2. On the Configuration menu, click Edit Network Port Settings.
3. Set the hostname and click Apply. You can optionally set the DNS domain and DNS IP address, too.
After you set the hostname, users can access the web interface using the following address: http://appliance_hostname. Changes may be required to the DNS server to include this hostname.
4. In the iSCSI Port 0 section, choose whether to use jumbo frames, set the IP address and subnet mask for the iSCSI port, and click Apply. Or, select Use DHCP to gather this information from a DHCP server and click Apply.
Repeat this step for iSCSI port 1, if you have connected that port to the network as well.
Note If your network does not support jumbo frames, do not enable them on initiators or DPS1000 Series. Doing so may result in dropped SCSI commands and unexpected behavior.
iSCSI port 0:Subnet mask
The netmask that corresponds to the IP address for iSCSI port 0. Not required if using DHCP.
iSCSI port 0:Jumbo frame settings
Whether jumbo frames will be enabled for iSCSI port 0.For information about whether to enable this option, see Determining whether to use jumbo frames on page 1.
iSCSI port 1:IP address
The IP address of iSCSI port 1. This is only required if you have connected iSCSI port 1 to the network.Not required if using DHCP, in which case this port is automatically named hostname-iSCSI1.
iSCSI port 1:Subnet mask
The netmask that corresponds to the IP address for iSCSI port 1. This is only required if you have connected iSCSI port 1 to the network.Not required if using DHCP.
iSCSI port 1:Jumbo frame settings
Whether jumbo frames will be enabled for iSCSI port 1.For information about whether to enable this option, see Determining whether to use jumbo frames on page 1.
Name Description Your Value
Configuring DPS1000 Series | 5
Configuring system settings
Before you configure the system settings, gather the following information:
To configure system settings
1. Log in as the admin user.
2. On the Configuration menu, click Edit System Settings.• In the Appliance Clock area, configure NTP or set the time and click Apply.• In the SMTP Settings area, configure SMTP and click Apply. You can also send a test
email in the Test SMTP area.
Name Description Your Value
Time configuration The appliance time.• To use a Network Time Protocol (NTP)
server, you must have the name of the NTP server and the current time zone. DPS1000 Series provides default NTP servers.
• To manually set the time, you need the current date and time.
SMTP server The hostname of a Simple Mail Transfer Protocol (SMTP) server.
SMTP port The port number for a SMTP server. This number is usually 25.
Subject line prefix The text that you would like to use as the Subject line of any email sent to users.This text makes it easy for users to identify email from DPS1000 Series.
“From” address for email messages
The email address that you would like to appear in the From line of any email sent to users.Bounced email messages are returned to this address.
SMTP username The username required to access the SMTP server. (This is not required for all SMTP configurations.)
SMTP password The corresponding password required to access the SMTP server. (This is not required for all SMTP configurations.)
6 | Configuring DPS1000 Series
Setting up certificates
Replace the self-signed certificate with a certificate signed by a Certificate Authority. For more information, see “Managing certificates” in the Security section of Help, which is available within the web interface.
Using DPS1000 Series with iSNS
Internet Storage Name Service (iSNS) enables you to manage multiple storage devices from a central location.
To use DPS1000 Series with iSNS
1. Set up your iSNS server.
2. In the DPS1000 Series web interface, enable the DPS1000 Series iSNS client. Refer to “Enabling iSNS” in the Configuration section of Help, which is available within the web interface.
When you connect initiators to DPS1000 Series, follow the steps defined for iSNS.
Configuring initiators
Initiators must be configured before they can back up or restore data on DPS1000 Series. For instructions on connecting initiators, see Configuring Windows Initiators on page 9 or Configuring Linux Initiators on page 25.
Setting up virtual tape libraries
When you add an initiator, DPS1000 Series automatically creates a virtual tape library with five virtual tapes. You may want to add or remove virtual tapes or perform other operations to further configure this virtual tape library. For more information, see “Managing initiators” and “Managing virtual tape libraries” in the Administration section of Help, which is available within the web interface.
Adding user accounts
After deployment, you may want to create additional user accounts or assign other roles to the default accounts. For more information about users and roles, see the DPS1000 Series Technical Overview or refer to “Managing users” in the Security section of Help, which is available within the web interface.
Uninstalling DPS1000 Series
Contact Support for information about uninstalling DPS1000 Series.
Configuring DPS1000 Series | 7
8 | Configuring DPS1000 Series
Configuring Windows Initiators
Initiators must be configured before they can back up data on or restore data from DPS1000 Series. This chapter describes configuring Windows initiators. For information about configuring Linux initiators, see Configuring Linux Initiators on page 25.
Configuring Windows initiators involves tasks in DPS1000 Series and on the initiator. In this chapter, tasks performed by you in DPS1000 Series are labeled Storage Administrator because this is the role required for these tasks. Tasks performed on the initiator are labeled User.
Note It is your responsibility to provide your users with the information required to successfully configure their initiators and back up to DPS1000 Series. No DPS1000 Series end-user documentation is provided, although this chapter provides examples of the type of information required for end users.
Configuration overview
The steps required to configure an initiator vary depending on the type of authentication used when initiators connect to DPS1000 Series. By default, no authentication is used. You can enable Challenge Handshake Authentication Protocol (CHAP) with Message-Digest algorithm 5 (MD5) for authentication. DPS1000 Series supports one-way authentication that validates the iSCSI initiator and mutual authentication that validates both the initiator and the target (DPS1000 Series). Determine the authentication type before you begin configuring initiators.
The following is an overview of the steps needed to configure Windows initiators:
1. The Storage Administrator adds the initiator to DPS1000 Series. See Adding initiators in DPS1000 Series on page 10.
2. The Storage Administrator provides the user with connection information for the initiator. See Providing connection information on page 10.
3. The Storage Administrator provides the user with driver updates for the initiator. See Providing users with driver updates on page 12.
4. The Storage Administrator provides access to the iSCSI initiator to the user. See Providing access to iSCSI initiator on page 12.
5. If authentication is used, the Storage Administrator enables CHAP authentication. See Enabling CHAP authentication on DPS1000 Series on page 13.
9
6. The User connects the initiator to DPS1000 Series. See Connecting to DPS1000 Series on page 13.
7. The User updates drivers on the initiator, if necessary. See Installing additional drivers on page 19.
8. The Storage Administrator adds additional virtual tape drives if an initiator needs access to more than one. See Adding virtual tape drives on page 23.
Adding initiators in DPS1000 Series
If CHAP authentication is not enabled, an initiator is automatically created for any iSCSI client that connects to DPS1000 Series.
Storage Administrator task
To add an initiator
1. On the DPS1000 Series Administration menu, click Manage VTLs.
2. On the Manage VTLs page, click Add Initiator.
3. In the Add Initiator area, provide the information required for the type of authentication. See Providing connection information on page 10 for a description and example of this information.• iSCSI Name• Initiator CHAP name (one-way and mutual authentication)• Target CHAP secret (one-way and mutual authentication)• Target CHAP name (mutual authentication only)• Initiator CHAP secret (mutual authentication only)
Note The initiator CHAP secret and the target CHAP secret cannot be the same.
4. To allow this initiator to back up and retrieve data on DPS1000 Series, select Allow initiator to connect. Otherwise, clear this option.
5. Click Save.
Providing connection information
The information that you must provide to users varies based on whether they will be using the connection wizard.
Providing users with information required for the connection wizard
Storage Administrator task
To download the configuration file and connection wizard
1. On the DPS1000 Series Administration menu, click Manage VTLs.
2. In the Initiators table, click next to the initiator.
10 | Configuring Windows Initiators
3. Save the file to your computer.
4. In the Tips pane (displayed when you click at the top of the page), click Initiator Setup Files.
5. On the Initiator Setup Files page, click Download the Connection Wizard.
6. Save the EXE file to your computer.
7. Send the configuration file and the connection wizard to the user, who must install them on the initiator. Note that the configuration file contains the CHAP password. Be sure to secure this file when sending it to the end user. For example, you can use secure email, secure file transfer, directory permissions, or encryption to secure the file.
Providing users with information required to connect manually
Storage Administrator task
If the user must connect to DPS1000 Series manually, you must provide users with connection information.
Name Description Authentication
Alias An optional name that identifies an initiator within DPS1000 Series.
NoneOne-wayMutual
iSCSI Name The Internet Small Computer System Interface (iSCSI) Qualified Name of the initiator in the following format: iqn.yyyy-mm.domain_name:computer_nameFor example: iqn.2007-08.com.mycompany:mycomputerIn Microsoft iSCSI Initiator, the iSCSI name is displayed on the General tab in the Initiator Node Name field.It is recommended that you use the default iSCSI Name configured on the initiator.
NoneOne-wayMutual
Initiator CHAP name
The name required to authenticate the initiator for CHAP.In Microsoft iSCSI Initiator, this name must be 1-255 characters in length and by default is the same as the iSCSI Name.
One-wayMutual
Target CHAP secret
A password required to authenticate the target (DPS1000 Series) for CHAP.For Microsoft iSCSI Initiator, this password must be 12-16 characters in length.Note that the initiator CHAP secret and the target CHAP secret cannot be the same.
One-wayMutual
Configuring Windows Initiators | 11
Providing users with driver updates
Storage Administrator task
Users can download and install drivers manually or using the connection wizard. If your users back up data using Windows Backup Utility or Symantec Backup Exec, they must use the “Tandberg Data StorageLoader” changer driver for DPS1000 Series. If they do not have this changer driver installed, they may be prompted to update to this driver when they connect the initiator to the DPS1000 Series changer. Otherwise, they may have to update the driver after they connect the initiator.
Users may also have to update the driver for the drive. Typically, there is no need to download this driver because the hardware update wizard will find it automatically (if Windows Update is in use). However, you can download the drivers manually (as described below) in case the wizard cannot find the driver.
Unless your users will install the drivers using the connection wizard, you should download the drivers and provide your users with the appropriate drivers for their operating system before they begin.
To download the drivers manually
1. Click on the menu bar.
2. In the Tips pane, click Initiator Setup Files.
3. Click Download the Virtual Library drivers.
4. Save the ZIP file to your computer as necessary.
Providing access to iSCSI initiator
Storage Administrator task
Users can configure their initiators using Microsoft iSCSI Initiator for Windows systems or the iSCSI initiator available on other operating systems. If the initiator uses an iSCSI HBA
Target CHAP name
The name required to authenticate the target (DPS1000 Series) for CHAP. (Only some iSCSI initiators require this name.)For Microsoft iSCSI Initiator, this name must be 1-18 characters in length.
Mutual
Initiator CHAP secret
A password required to authenticate the initiator for CHAP.For Microsoft iSCSI Initiator, this password must be 12-16 characters in length.Note that the initiator CHAP secret and the target CHAP secret cannot be the same.
Mutual
Name Description Authentication
12 | Configuring Windows Initiators
(host bus adapter) card, the initiator should be configured using the tool that comes with the HBA. Ensure that your users have access to an iSCSI initiator.
The procedures in this chapter reference Microsoft iSCSI Initiator. Windows 2008 systems should already have Microsoft iSCSI Initiator installed on them. However, the latest version of iSCSI Initiator may need to be installed on other Windows operating systems.
Enabling CHAP authentication on DPS1000 Series
Storage Administrator task
If you want to enable authentication between DPS1000 Series and the initiator, complete the following steps. Otherwise, skip to Connecting to DPS1000 Series on page 13.
To enable CHAP authentication
1. On the DPS1000 Series Configuration menu, click Edit System Settings.
2. Select CHAP Authentication Required.
3. Click Apply.
Connecting to DPS1000 Series
Users can connect to DPS1000 Series using the connection wizard or manually.
Connecting with the connection wizard
User task
To connect using the connection wizard
1. Save the DPS1000 Series Connection Wizard and configuration file in the same directory on the initiator. The Storage Administrator will provide you with these files.
2. Double-click the EXE file to run the wizard.
3. Follow the steps in the wizard to install the necessary drivers and connect to DPS1000 Series.
If you are using a backup management application other than Microsoft Windows Backup Utility, choose the custom installation and do not install the drivers. Instead, install the drivers manually. Refer to Installing additional drivers on page 19.
If Windows displays a message that the driver has not passed Windows Logo testing, click Continue Anyway and finish the wizard.
Connecting manually with no authentication
User task
This procedure provides steps for using Microsoft iSCSI Initiator. You will need a different set of steps if another iSCSI initiator is installed on the client.
Configuring Windows Initiators | 13
To connect manually
1. Open Microsoft iSCSI Initiator.
2. If the initiator must connect to DPS1000 Series using a custom name, complete these steps:a. On the General tab, click Change.b. In the Initiator Node Name Change dialog box, type the new iSCSI name and click
OK.
3. Click the Discovery tab.
4. Add iSCSI port information as follows:a. In the Target Portals area, click Add.
b. On the Add Target Portal dialog box, type the IP address or hostname of the iSCSI port to which you are connecting in the IP Address or DNS Name field. Here is an example hostname: DPS1000 Series-B02YVK-iscsi0.
c. Click OK.
5. In the iSCSI Initiator Properties dialog box, click the Targets tab.
Note If the targets do not display on this page, click Refresh. If the targets still do not display, the initiator may not be enabled to make connections. Contact Support.
14 | Configuring Windows Initiators
6. Log on to the changer using the following steps:a. Click the iSCSI name for the changer (“changer” is appended to its name) and click
Log On. The Log On to Target dialog box is displayed.
b. Select Automatically restore this connection when the system boots.
Note Do not select this option if more than 32 initiators will be connected when the DPS1100 is deployed. Do not select this option if more than 64 initiators will be connected when the DPS1200 is deployed. Instead, have initiators connect only when they are ready to back up data.
c. Click Advanced.d. On the Advanced Settings dialog box, select Microsoft iSCSI Initiator from the
Local adapter list.e. From the Source IP list, select your IP address.f. From the Target Portal list, select your target portal, which you entered in the Add
Target Portal dialog box.g. Click OK to close the Advanced Settings dialog box.h. Click OK to close the Log On To Target dialog box.i. If you are prompted for a new driver, browse to the location of the changer driver
provided by your Storage Administrator.
7. Repeat the previous step to log on to the drive. (If there is more than one drive, log on to each.) You do not need to update the driver for the drive at this time.
8. Close Microsoft iSCSI Initiator.
Connecting manually with authentication
User task
This procedure provides steps for using Microsoft iSCSI Initiator. You will need a different set of steps if another iSCSI initiator is installed on the client.
To connect manually with CHAP authentication
1. Open Microsoft iSCSI Initiator.
2. If the initiator must connect to DPS1000 Series using a custom name, complete these steps:a. On the General tab, click Change.b. In the Initiator Node Name Change dialog box, type the new iSCSI name and click
OK.
Configuring Windows Initiators | 15
3. If configuring mutual authentication, complete these steps:a. On the General tab, click Secret. The CHAP Secret Setup dialog box is displayed.
b. On the CHAP Secret Setup dialog box, type the initiator CHAP secret and click OK.
4. Click the Discovery tab.
5. If using iSNS server, perform the following steps:a. In the iSNS Servers area, click Add.b. In the Add iSNS Server dialog box, type the IP address or hostname of the iSNS
server and click OK.c. Skip to step 7.
6. Add iSCSI port information as follows:a. In the Target Portals area, click Add.
b. On the Add Target Portal dialog box, type the IP address or hostname of the iSCSI port to which you are connecting in the IP Address or DNS Name field.
16 | Configuring Windows Initiators
c. Click Advanced.
d. On the Advanced Settings dialog box, select CHAP logon information.e. In the User name field, type the initiator CHAP name.f. In the Target secret field, type the target CHAP secret.g. If configuring mutual authentication, select Perform mutual authentication.h. Click OK.i. Click OK to close the Add Target Portal dialog box.
7. Log on to the changer as follows:a. Click the Targets tab.
Configuring Windows Initiators | 17
b. Select the changer from the list (“changer” is appended to its name) and click Log On.
c. In the Log On To Target dialog box, select Automatically restore this connection when the system boots.
Note Do not select this option if more than 32 initiators will be connected when the DPS1100 is deployed. Do not select this option if more than 64 initiators will be connected when the DPS1200 is deployed. Instead, have initiators connect only when they are ready to back up data.
d. Click Advanced.
e. On the Advanced Settings dialog box, select Microsoft iSCSI Initiator from the Local adapter list.
f. From the Source IP list, select your IP address.g. From the Target Portal list, select your target portal, which you entered in the Add
Target Portal dialog box.h. Select CHAP logon information.i. In the User name field, type the initiator CHAP name.j. In the Target secret field, type the target CHAP secret.k. If configuring mutual authentication, select Perform mutual authentication.
18 | Configuring Windows Initiators
l. Click OK.m. Click OK to close the Log On to Target dialog box.n. If you are prompted for a new driver, browse to the location of the changer driver
provided by your Storage Administrator.
8. Repeat the previous step to log on to the drive. (If there is more than one drive, log on to each.) You do not need to update the driver for the drive at this time.
9. Close Microsoft iSCSI Initiator.
Installing additional drivers
If you do not install drivers using the connection wizard, you may need to update the drivers for the DPS1000 Series changer and tape drive manually.
For initiators that use CA ARCserve Backup
User task
On each initiator that uses CA ARCserve Backup, you must install an updated changer driver (if you were not prompted to do so during setup) and an updated tape drive driver.
To update the drivers
1. Right-click on My Computer and click Manage.
2. In the Computer Management window, click Device Manager.
3. Expand the Medium Changer area on the right to check the medium changer:• If the medium changer is Tandberg Data StorageLoader, continue with step 6.• If the medium changer is not Tandberg Data StorageLoader, continue with step 4.• If the medium changer is not available, check the Targets tab in iSCSI Initiator to
verify that you are connected to DPS1000 Series.
4. Right-click the medium changer and click Update driver.
Configuring Windows Initiators | 19
5. Follow the steps in the Hardware Update Wizard to find and install the driver that you downloaded before you configured the initiator.
6. Expand the Tape drives area on the right. If the tape drive does not display in this area, expand the Other area.
7. Right-click the drive and click Update driver.
8. Follow the steps in the Hardware Update Wizard to automatically find and install the correct driver. If the wizard cannot find the driver, use the driver that you downloaded before you configured the initiator.
9. Close the Computer Management window.
For initiators that use HP Data Protector
User task
No additional configuration is required for HP Data Protector.
For initiators that use IBM Tivoli Storage Manager
User task
Initiators that use IBM Tivoli Storage Manager (TSM) must use the TSM driver for the DPS1000 Series changer and tape drive, which are available by default.
To verify the connection to DPS1000 Series
1. Right-click on My Computer and click Manage.
2. In the Computer Management window, click Device Manager.
3. Expand the Medium Changer area on the right to check the medium changer. If the medium changer is not available, check the Targets tab in iSCSI Initiator to verify that you are connected to DPS1000 Series.
20 | Configuring Windows Initiators
For initiators that use Microsoft Windows Backup Utility
User task
On each initiator that uses the Windows Backup Utility, you must install an updated changer driver (if you were not prompted to do so during setup) and an updated tape drive driver.
To update the drivers
1. Right-click on My Computer and click Manage.
2. In the Computer Management window, click Device Manager.
3. Expand the Medium Changer area on the right to check the medium changer:• If the medium changer is Tandberg Data StorageLoader, continue with step 6.• If the medium changer is not Tandberg Data StorageLoader, continue with step 4.• If the medium changer is not available, check the Targets tab in iSCSI Initiator to
verify that you are connected to DPS1000 Series.
4. Right-click the medium changer and click Update driver.
5. Follow the steps in the Hardware Update Wizard to find and install the driver that you downloaded before you configured the initiator.
6. Expand the Tape drives area on the right. If the tape drive does not display in this area, expand the Other area.
7. Right-click the drive and click Update driver.
8. Follow the steps in the Hardware Update Wizard to automatically find and install the correct driver. If the wizard cannot find the driver, use the driver that you downloaded before you configured the initiator.
9. Close the Computer Management window.
If you cannot see tapes in the Media Pools area of the Computer Management window, refer to the following:• Virtual tapes not seen by Windows Backup Utility on page 34• Virtual tapes not recognized by Windows Backup Utility after import on page 35
Configuring Windows Initiators | 21
For initiators that use Symantec Backup Exec
User task
On each initiator that uses Symantec Backup Exec, you must install an updated changer driver (if you were not prompted to do so during setup).
To update the drivers
1. Right-click on My Computer and click Manage.
2. In the Computer Management window, click Device Manager.
3. Expand the Medium Changer area on the right to check the medium changer:• If the medium changer is Tandberg Data StorageLoader, you can skip the remaining
steps.• If the medium changer is not Tandberg Data StorageLoader, continue with step 4.• If the medium changer is not available, check the Targets tab in iSCSI Initiator to
verify that you are connected to DPS1000 Series.
4. Right-click the medium changer and click Update driver.
5. Follow the steps in the Hardware Update Wizard to find and install the driver that you downloaded before you configured the initiator. If the wizard cannot find the driver, use the driver that you downloaded before you configured the initiator.
6. Close the Computer Management window.
22 | Configuring Windows Initiators
Adding virtual tape drives
Storage Administrator task
If an initiator needs access to more than one virtual tape drive, this optional procedure enables you to add a virtual tape drive.
To add a virtual tape drive
1. On the Administration menu, click Manage VTLs.
2. In the Initiators table, click next to the initiator associated with the virtual tape library.
3. In the Virtual Tape Library area, click .
4. In the confirmation dialog box, click OK.
DPS1000 Series automatically adds the virtual tape drive to the list of targets in the iSCSI initiator. The user must then log in to the new tape drive.
Configuring Windows Initiators | 23
24 | Configuring Windows Initiators
Configuring Linux Initiators
Initiators must be configured before they can back up data on or restore data from DPS1000 Series. This chapter describes configuring Linux initiators. For information about configuring Windows initiators, see Configuring Windows Initiators on page 9.
Configuring Linux initiators involves tasks in DPS1000 Series and on the initiator. In this chapter, tasks performed by you in DPS1000 Series are labeled Storage Administrator because this is the role required for these tasks. Tasks performed on the initiator are labeled User.
Note It is your responsibility to provide your users with the information required to successfully configure their initiators and back up to DPS1000 Series. No DPS1000 Series end-user documentation is provided, although this chapter provides examples of the type of information required for end users.
Configuration overview
The steps required to configure an initiator vary depending on the type of authentication used when initiators connect to DPS1000 Series. By default, no authentication is used. You can enable Challenge Handshake Authentication Protocol (CHAP) with Message-Digest algorithm 5 (MD5) for authentication. DPS1000 Series supports one-way authentication that validates an iSCSI initiator and mutual authentication that validates both the initiator and the target (DPS1000 Series). Determine the authentication type before you begin configuring initiators.
The following is an overview of the steps needed to configure Linux initiators:
1. The Storage Administrator provides the user with connection information for the initiator. See Providing connection information on page 26.
2. The User installs the iSCSI initiator. See Installing the iSCSI initiator on page 27.
3. The User edits the iSCSI node name on the initiator. See Editing the iSCSI node name on page 27.
4. If authentication is used:a. The Storage Administrator enables CHAP authentication. See Enabling CHAP
authentication on DPS1000 Series on page 28.b. The Storage Administrator adds the initiator to DPS1000 Series. See Adding an
initiator to DPS1000 Series on page 28.c. The User configures authentication on the initiator. See Configuring authentication
on the initiator on page 29.
25
5. The User connects the initiator to DPS1000 Series. See Connecting to DPS1000 Series on page 30.
6. The Storage Administrator adds additional virtual tape drives if an initiator needs access to more than one. See Adding virtual tape drives on page 31.
Providing connection information
Storage Administrator task
Before users can connect their initiators to DPS1000 Series, you must provide users with connection information.
Name Description Authentication
iSCSI port 0:IP address or hostname
The IP address or hostname for iSCSI port 0. This IP address is available on the DPS1000 Series Home page.Each initiator should connect to only one of the iSCSI ports.
NoneOne-wayMutual
iSCSI port 1:IP address or hostname
The IP address or hostname for iSCSI port 1. The IP address is available on the DPS1000 Series Home page. (This is only needed if both iSCSI ports are used.)Each initiator should connect to only one of the iSCSI ports.
NoneOne-wayMutual
Alias A optional name that identifies an initiator within DPS1000 Series. The default value of the alias may be based on the initiator’s hostname; therefore, the user may have this information (see Editing the iSCSI node name on page 27).
NoneOne-wayMutual
iSCSI name The Internet Small Computer System Interface (iSCSI) Qualified Name of the initiator, which varies according to the Linux distributor, in the following format: iqn.yyyy-mm.domain_name:computer_nameFor example: iqn.1994-05.com.redhat:mycomputer.It is recommended that you use the default iSCSI name configured on the initiator, which may be based on the initiator’s hostname. Therefore, the user may have this information (see Editing the iSCSI node name on page 27).
NoneOne-wayMutual
Initiator CHAP name The name required to authenticate the initiator for CHAP.
One-wayMutual
26 | Configuring Linux Initiators
Installing the iSCSI initiator
User task
Before you begin, obtain connection information from your Storage Administrator. Then, perform the following steps on the command line to install the iSCSI initiator (on Red Hat Enterprise Linux).
To install the iSCSI initiator
1. To search for the most recent version of the iSCSI initiator, enter
yum search iscsi
2. To install the iSCSI initiator, enter
yum install iscsi-initiator-utils
Editing the iSCSI node name
User task
By default, the hostname of the initiator is specified in the iSCSI configuration file. If the host name is not specified in the file or if you wish to change the initiator name, complete the following steps:
To edit the iSCSI node name
1. Open the /etc/iscsi/initiatorname.iscsi file in a text editor.
2. Add or edit the InitiatorName parameter to specify the initiator name. Here is an example:
InitiatorName=iqn.1994-05.com.redhat:dpsrhel52
Target CHAP secret A password required to authenticate the initiator for CHAP.Note that the initiator CHAP secret and the target CHAP secret cannot be the same.
One-wayMutual
Target CHAP name The name required to authenticate the target (DPS1000 Series) for CHAP. (Only some iSCSI initiators require this name.)
Mutual
Initiator CHAP secret A password required to authenticate the target (DPS1000 Series) for CHAP.Note that the initiator CHAP secret and the target CHAP secret cannot be the same.
Mutual
Name Description Authentication
Configuring Linux Initiators | 27
3. Optionally, specify an alias for the initiator by editing the InitiatorAlias parameter. Here is an example:
InitiatorAlias=crdsrhel52
4. Save and close the file.
Enabling CHAP authentication on DPS1000 Series
Storage Administrator task
If you want to enable authentication between DPS1000 Series and the initiator, complete the following steps. Otherwise, skip to Connecting to DPS1000 Series on page 30.
To enable CHAP authentication
1. On the DPS1000 Series Configuration menu, click Edit System Settings.
2. Select CHAP Authentication Required.
3. Click Apply.
Continue to the next procedure.
Adding an initiator to DPS1000 Series
Storage Administrator task
If you enabled CHAP authentication, you must add an initiator to DPS1000 Series before the user connects the initiator. Complete the following steps to add an initiator using the DPS1000 Series web interface. Otherwise, skip to Connecting to DPS1000 Series on page 30.
To add an initiator
1. On the DPS1000 Series Administration menu, click Manage VTLs.
2. On the Manage VTLs page, click Add Initiator.
3. In the Add Initiator area, provide the following information. See Providing connection information on page 26 for a description and example of this information. • Alias• iSCSI Name• Initiator CHAP name (one-way and mutual authentication)• Target CHAP secret (one-way and mutual authentication)• Target CHAP name (mutual authentication only)• Initiator CHAP secret (mutual authentication only)
Note The initiator CHAP secret and the target CHAP secret cannot be the same.
4. To allow this initiator to back up and retrieve data on DPS1000 Series, select Allow initiator to connect. Otherwise, clear this option.
5. Click Save.
28 | Configuring Linux Initiators
Configuring authentication on the initiator
User task
If authentication was enabled, you must configure authentication on the initiator before connecting the initiator to DPS1000 Series. On Linux, Open-iSCSI supports CHAP authentication; see http://www.open-iscsi.org for more information about this iSCSI implementation.
Note For steps 3 and 4 below, the usernames and passwords specified for the node.session and discovery.sendtargets parameters must match. However, the initiator CHAP secret and target CHAP secret specified for mutual authentication cannot be the same.
If authentication was not enabled, skip to Connecting to DPS1000 Series.
To configure CHAP authentication on the initiator
1. Open the /etc/iscsi/iscsid.conf file in a text editor.
2. To enable CHAP authentication, uncomment these lines by removing the pound sign (#) from the beginning of the line and set the parameters to CHAP:
node.session.auth.authmethod = CHAP
discovery.sendtargets.auth.authmethod = CHAP
3. To set a CHAP username and password for authenticating the initiator for one-way and mutual authentication, uncomment the following lines and specify the username and password:
node.session.auth.username = initiator_chap_name
node.session.auth.password = target_chap_secret
discovery.sendtargets.auth.username = initiator_chap_name
discovery.sendtargets.auth.password = target_chap_secret
4. To set a CHAP username and password for authenticating the target for mutual authentication, uncomment the following lines and specify the username and password:
node.session.auth.username_in = target_chap_name
node.session.auth.password_in = initiator_chap_secret
discovery.sendtargets.auth.username_in = target_chap_name
discovery.sendtargets.auth.password_in = initiator_chap_secret
5. Save and close the file.
Configuring Linux Initiators | 29
Connecting to DPS1000 Series
User task
You can connect directly to DPS1000 Series or you can connect through iSNS using Open-iSCSI. Before you begin, obtain connection information from your Storage Administrator. Then, perform the following steps on the command line.
To connect an initiator directly to DPS1000 Series
1. To discover the available targets, enter the following command:
iscsiadm -m discovery -t sendtargets -p ip_address
where ip_address is the IP address of one of the DPS1000 Series iSCSI ports. A list of target devices is displayed. Here is an example of the output:192.168.30.113:3260,0 iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-changer-0192.168.30.127:3260,0 iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-changer-0192.168.30.113:3260,1 iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-drive-0192.168.30.127:3260,0 iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-drive-0
2. To connect the initiator to DPS1000 Series, enter the following:
iscsiadm -m node -T target_name -p target_portal -l
where target_name is the iSCSI qualified name of the target and target_portal is the IP address of one of the target devices. Example:
iscsiadm -m node -T iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-changer-0 -p 192.168.30.113 -l
Here is an example of the output:
Logging in to [iface: default, target: iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-changer-0, portal: 192.168.30.113,3260]
Login to [iface: default, target: iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-changer-0, portal: 192.168.30.113,3260]: successful
3. Repeat step 2 for the changer and drives on the IP address for which the discovery was performed (in step 1).
If no authentication is used, DPS1000 Series automatically adds this initiator to its list of initiators and creates a virtual library.
To connect an initiator through iSNS
User task
1. Open the /etc/iscsi/iscsid.conf file in a text editor.
2. Edit the following line to specify the IP address of the iSNS server.
isns.address = isns_server_ip_address
30 | Configuring Linux Initiators
3. Uncomment the following line by removing the pound sign (#) from the beginning of the line and specify a port number provided by your Storage Administrator:
#isns.port = 3205
4. Save and close the file
5. Perform a discovery using iSNS by entering the following command:
iscsiadm -m discovery -t isns
A list of target devices is displayed. Here is an example of the output:192.168.30.113:3260,0 iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-changer-0192.168.30.127:3260,0 iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-changer-0192.168.30.113:3260,1 iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-drive-0192.168.30.127:3260,0 iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-drive-0
6. To connect the initiator to DPS1000 Series, enter the following command:
iscsiadm -m node -T target_name -p target_portal -l
Here is an example of this command:
iscsiadm -m node -T iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-changer-0 -p 192.168.30.113 -l
Here is an example of the output:
Logging in to [iface: default, target: iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-changer-0, portal: 192.168.30.113,3260]
Login to [iface: default, target: iqn.1997-03.com.mycompany:b02yvk.0.DPS-vtl-changer-0, portal: 192.168.30.113,3260]: successful
7. Repeat step 6 for a changer and all drives on the same IP address returned by the discovery (in step 5).
Adding virtual tape drives
Storage Administrator task
If an initiator needs access to more than one virtual tape drive, this optional procedure enables you to add a virtual tape drive.
To add a virtual tape drive
1. On the Administration menu, click Manage VTLs.
2. In the Initiators table, click next to the initiator associated with the virtual tape library.
3. In the Virtual Tape Library area, click .
4. In the confirmation dialog box, click OK.
DPS1000 Series automatically adds the virtual tape drive to the list of targets in the iSCSI initiator. The user must then log in to the new tape drive.
Configuring Linux Initiators | 31
32 | Configuring Linux Initiators
Troubleshooting
The following sections describe issues you might encounter while operating DPS1000 Series and provide suggestions for resolving the issues.
DPS1000 Series issues
Use the following to troubleshoot DPS1000 Series and its virtual tape library.
Troubleshooting DPS1000 Series drives
Appliance drive problems are indicated in the web interface. The following illustration shows the drives, which are located on the front of the appliance.
Front of the DPS1100
Front of the DPS1200
In the web interface, the RAID Status area of the Home page shows the status of each drive in the RAID array. If one of the blocks in the RAID Status area is red (indicating a problem drive), hold your pointer over it to show which drive has a problem.
If you encounter a single drive error, the data on the appliance will remain safe, but the aggregate performance of the RAID may be severely limited. If another drive fails, you will lose data. Backups may not complete in a timely manner until the drive is replaced.
33
If a drive fails, perform the following steps:
1. Temporarily restrict backups to the most critical data.
2. Contact Support for a replacement drive.
3. Use instructions from Support to install the new drive. Do not resume regular backup activities until the drive’s status bar on the Home page returns to green (indicating the drive is functioning properly). This may take up to eight hours.
DPS1000 Series does not recognize DPS Expansion Module
• Verify that the interface cables from DPS Expansion Module to DPS1000 Series are fitted correctly. Change the cable with a known good cable.
• Verify that all drive carrier modules have been correctly installed and that the LEDs on all installed drive carrier modules are illuminated green. Note that the drive LEDs will not be lit during drive spinup.
• Verify that there is activity on the connector Activity LEDs and the Controller OK LEDs on RAID controller.
• Verify that the RAID controller module is set up correctly and all external links and cables are securely fitted. Verify that the maximum cable length (6 meters / 20 feet) has not been exceeded.
• Verify that the RAID controller module is properly set up at the software interface.
Note For details on how to remove and replace a plug-in module, contact Support.
Authentication errors
If authentication errors are displayed, even if CHAP is not enable, verify that the iSCSI ports are up and available.
Initiator issues
Use the following to troubleshoot issues with initiators and backup management applications.
Troubleshooting iSCSI initiator configuration
Microsoft iSCSI Initiator does not allow users to edit target portals. If a mistake is made during configuration or a change must be made, the target portal entry must be deleted and then added again with the correct information.
Virtual tapes not seen by Windows Backup Utility
When an initiator connects to DPS1000 Series, DPS1000 Series creates a virtual tape library and five virtual tapes. If you are using the Windows Backup Utility and you cannot see the virtual tapes from the initiator or Windows Backup Utility indicates that there is no free media available, perform the following steps:
1. Right-click My Computer and click Manage.
2. In the Computer Management window, expand Storage→Removable Storage→Media Pools.
34 | Troubleshooting
If the Media Pools option does not display, perform the following steps:a. From the command line, enter mmc.b. In the console window, select the compmgmt.msc file from the File menu.c. In the Computer Management window, click Removable Storage.d. Select View→Full.e. From File menu, select Save.f. Exit the Computer Management window.
Note This step is very important. If you continue working in this window, you may change settings you do not intend to change.
g. Return to step 1.
3. Free any tapes in the Unrecognized directory.
Virtual tapes not recognized by Windows Backup Utility after import
Imported tapes are not always recognized by Windows Backup Utility. If this occurs, you must inventory the library using the following steps:
1. Right-click My Computer and click Manage.
2. In the Computer Management window, expand Storage→Removable Storage→Libraries.
3. Right-click on the library and click Inventory.
Inventories, backups, or restores not responding
When an inventory, backup, or restore stops responding, verify that jumbo frames are not enabled on the initiator or DPS1000 Series. Never use jumbo frames if your network does not support them.
Restoring to different initiator fails when MaxTransferLength differs
Restoring files from one initiator to another may fail if the MaxTransferLength is not consistent. The same MaxTransferLength must be used when backing up and restoring a virtual tape.
Cannot use Windows Native Backup to restore from multiple virtual tapes at same time
Using Windows Native Backup, users can restore data from one virtual tape at a time. If data stored on multiple virtual tapes is restored at the same time, the restore will fail. Therefore, users must restore the files from one virtual tape at a time.
Troubleshooting | 35
36 | Troubleshooting
Bar Code Label Specification for LTO Ultrium Cartridges
This appendix provides specifications for creating bar code labels used on cartridges in a physical tape device. The specifications are defined to standardize labels and allow users the option of purchasing or printing their own labels. This specification contains the following information about the bar code labels:• Symbology• Bar code characters• Encodations• Quiet zone• Optical specification• Label dimensions• Volume identifier formats
Symbology
The LTO Ultrium cartridge label uses the bar code symbology of USS-39. A description and definition of this symbology is available from the Automatic Identification Manufacturers (AIM) specification Uniform Symbol Specification (USS-39) and the ANSI MH10.8M-1993 ANSI Barcode specification.
Bar code characters
The bar code string consists of a start character, eight alphanumeric characters, and the stop character. Quiet zones precede and follow the start and stop characters. The first six characters may be any combination of upper case A through Z or 0 through 9 (for example, ABC123) to identify the cartridge volume. The last two characters are determined by the LTO Ultrium cartridge media type (for example “L” for LTO Ultrium and “1” for tape cartridge generation or drive manufacturer-unique identifier).
Only upper case alpha A through Z or numeric 0 through 9 characters are allowed.
Human readable characters may be used, provided there is not a conflict or interference with the automation code. The user specifies the format, colors, and location of the human readable characters.
Encodation
Refer to the AIM Uniform Symbol USS-39 specification for the description and format of the start character, identifier characters, and stop character.
37
Quiet zone
The quiet zones are the areas preceding the start and after the stop characters. They are clear of any printing or reflective properties that could cause spurious reflections. The quiet zones are further defined in the AIM Uniform Symbol USS-39 specification.
Optical specification
The optical specifications for the bar code labels are listed below.• Use the white calibration standard to calibrate the print contrast of the Mcbeth PCMII.
Be sure the filter select switch is on position A for all calibration and measurements.• The reflectivity of the white background (RW) is the reflectivity measured in the center of
narrow spaces using the Mcbeth PCMII print contrast meter. The RW must be between 70% and 85%. At this measurement, isolated print defects and edge roughness are avoided.
• A spot is defined as an area anywhere within the white background in which the reflectivity is less than 65%. Spots may not be greater than 0.004 inches (0.102 mm) enclosed diameter. There may be no more than five spots in the bar code area per label. Spots may not be any closer to each other than 0.01 inches (0.254 mm).
• The reflectivity of the black areas (RB) may be measured anywhere within any black area on the bar code. The print contrast signal (PCS) is defined as (RW-RB)/RW and is measured using the Mcbeth PCMII print contrast meter. PCS must be a minimum of 0.85. Using the PCS measurement will avoid isolated print defects and edge roughness.
• A void is an area within a black area where the PCS is less than 0.85. No voids may be greater than 0.004 inches (0.102 mm) enclosed diameter. There may be no more than five voids in the bar code area per label. Voids may not be any closer to each other than 0.01 inches (0.254 mm).
Note For additional optical requirements and measurement techniques, refer to the AIM Uniform Symbol USS-39 specification.
Label dimensions
The following table lists the bar code label dimension specifications.
Note The LTO Ultrium label dimensions are derived using the AIM USS-39 specification.
Specification Dimension
Symbol height 0.44 inches (11.1 mm) minimum as measured to the inside of the edge roughness
Wide to narrow ratio 1:2.75
Narrow element width 0.017 inches + 0.001/–0.003 inches (0.432 mm +0.03/–0.076 mm)
Nominal width of wide spaces and bars
0.047 inches (1.188 mm)
Inter character gap 0.017 inches +0.001/–0.003 inches (0.432 mm +0.03/–0.076 mm)
38 |
* The edge roughness is defined as the transition encountered as a horizontal line is moved vertically from all black to all white. The bar code edge is defined as the edge of all printed area attached to the bar.** Must fit within the label recess on the face of the cartridge without curling up on the sides or ends.
Volume identifier formats
The volume identifier only uses ASCII characters A through Z (41h-5Ah), 0 through 9 (30h-39h), and the combinations of “CLN” and “DG{space}” as described below.• The prefix “CLNvnnL1”is reserved for cleaning cartridges. The “v” field is an
alphanumeric field to identify a drive-unique cleaning cartridge. The “nn” alphanumeric field is used to track individual cleaning cartridge activity (for example, usage and life). When the drive requires cleaning, it will request loading of the unique type cleaner cartridge.
Bar code element width maximum
Measured to the outside of the edge roughnessa. Space width is then the distance between bar maxima.
Quiet zone at the beginning and end of printed bar code string
10× narrow width = 0.17 inches (4.32 mm)
Total bar code string length, including quiet zones
Nominal 2.917 inches (74.088 mm)
Bar code string direction May be printed in either direction on the label but must begin/end with a valid start/stop character (Q)
Edge roughness * 0.0015 inches (0.037mm) maximum
Tolerances 0.XXX± 0.005 inches, 0.XX±.0.03 inches)(0.XXX± 0.127 mm, 0.XX± 0.762 mm)
Variation between all wide bars, white and black
Less than ± 0.0015 inches (0.0381 mm)
Variation between all narrow bars, white and black
Less than ± 0.0015 inches (0.0381 mm)
Print side Print the bar code string on the label so it is on the side of the label towards the hub
Label stock dimensions 3.110 x 0.669 inches (79 × 17 mm) **
Minimum length for quiet zones, start-stop and data characters
Nominal 2.917 inches (74.088 mm)
Minimum width No less than 0.059 inches (1.5 mm) narrower than the cartridge label recess width
Corner cut 0.059 inches (1.5 mm radius)
Specification Dimension
| 39
• Diagnostic/Service cartridges use the prefix “DG{space}vnnL1”. The “v” field is an alphanumeric field to identify a drive-unique diagnostic cartridge, if required. The “nn” alphanumeric field identifies a specific diagnostic cartridge volume.
• The volume identifier field consists of six left-justified alphanumeric characters as specified in SCSI-3 Medium Changer Commands (SMC) ANSI NCITS 314-199X.
• The media identifier characters “Lg” are controlled characters. The “L” designates the LTO Ultrium type of cartridge. The next character “g” (alphanumeric) designates the generation of the LTO Ultrium cartridge.
40 |
Index
Aaccessing CLI 3accounts
admin 4str_admin 4
adminoverview 4
appliancetime 6
audience v
Bbar code labels, creating 37
Ccertificate
setting 7warning message 4
CHAPoverview for Linux 25overview for Windows 9
CLI access 3clock, setting 6configuring
initiatorsby backup management application
CA ARCserve Backup 19HP Data Protector 20IBM Tivoli Storage Manager 20Symantec Backup Exec 22Windows Backup Utility 21
SMTP 6creating bar code labels 37
Ddefault user accounts 4DNS, setting 5document library vi
Hhostname, setting 5HyperTerminal example 3
Iinitiator CHAP name
for Linux 26for Windows 11
initiator CHAP secretfor Linux 27for Windows 12
initiatorsalias
for Linux 26for Windows 11
configuringby backup management application
CA ARCserve Backup 19HP Data Protector 20IBM Tivoli Storage Manager 20Symantec Backup Exec 22Windows Backup Utility 21
iSCSI namefor Linux 26for Windoes 11
overview for Linux 25overview for Windows 9steps for configuring for Linux 25steps for configuring for Windows 9
iSCSI namefor Linux 26for Windows 11
iSCSI portsDHCP 5IP address 4setting
IP address 5subnet mask 5
subnet mask 5
Jjumbo frames, description 1
Mmutual authentication, configuring
on Linux 25on Windows 9
NNTP 6
Index | 41
Oone-way authentication, configuring
on Linux 25on Windows 9
Rrelated documentation vi
Ssetting
certificate 7clock 6DNS 5hostname 5iSCSI ports 5NTP 6time 6
SMTPconfiguring 6email address 6password 6port 6server 6subject for email 6username 6
str_adminoverview 4
Support vi
Ttarget CHAP name
for Linux 27for Windows 12
target CHAP secretfor Linux 27for Windows 11
Technical Support vitime, setting 6troubleshooting 33typographical conventions v
Uuninstall 7user accounts
default 4overview 7
Vvirtual tape library, overview 7
Wweb interface
accessing 3
42 | Index