A tape library is a hardware unit comprised of multiple physical or virtual tape drives and tape slots with a media changer for automatically inserting and removing tapes. The device is sometimes referred to as an automated tape library or jukebox.

Catalogic DPX supports tape devices and media changers compliant with the SCSI-2 standard. Tape drives must support variable-length records and allow a minimum transfer size of 32 KB. Additionally, media changer support on Microsoft Windows requires Microsoft Windows NT SCSI Pass-Through support from the HBA driver or a vendor-supplied media changer driver supporting Microsoft Windows NT SCSI Pass-Through.

Unless otherwise advised by Catalogic Data Protection Technical Support, the operating system of the Device Server that connects the tape or tape library device should have properly installed drivers as recommended by the device manufacturer.

Catalogic DPX treats a Virtual Tape Library (VTL) device as a regular tape library and supports it the same way it does for tape libraries.

Catalogic Software has qualified Catalogic DPX with the following tape media:

Catalogic Software has qualified Catalogic DPX with the following tape libraries:

This topic describes how to test communication between the tape library and the controller node containing the installed media changer device file. For DPX, verification is recommended if you installed your media changer device file by using the manual installation procedures described in .

Testing the Tape Library Installation

The tape library media changer test program JItest.exe (or ./jitest* depending on platform) is used to test the tape library installation. The test program requires as an argument the media changer device file name created during the installation procedure in the preceding chapter. The example here uses a Windows device name. The only difference between this example and other platforms is the device name which can be /dev/sync_sa0, /dev/rchg/c000t0d0s0, etc. For UNIX and Linux environments, run ./bin/bexenv prior to running the jitest utility.

1. At the command line, type jitest sync_sa0 (or ./jitest /dev/sync_sa/0 for UNIX). This produces the following output: Please type the command.

2. Enter the command open to open communications. Sample output follows:

   The output lists information about this particular tape library. An explanation of some of the parameters follows:

   In our example, the address of the first drive is 1030. The second drive therefore has an address of 1031. The same holds for the cartridges. The first cartridge has an address of 0, the second has an address of 1, and so on.

3. Type setup 0.

4. Type quit to quit JItest, or type help for other useful commands.

5. If the media changer accepts these commands without obvious error, the tape library is ready to be configured for use. Proceed to for the tape library configuration procedure.

This chapter provides an overview of how to manually configure a tape library for DPX after the media changer device file is installed. The detailed instructions can be found in Chapter 12: Configuring Devices in the DPX 4.9.x Reference Guide. Manual configuration is not needed for tape libraries that were successfully set up using Automatic Setup (Process A). However, Automatic Setup does not configure media pools, assign media, or define backup jobs, all of which are also summarized at the end of this topic.

All the manual configuration steps are performed from the management console.

Defining Tape Libraries and Tape Drives

The following steps are required if you set up your tape library by using Manual Setup (Process B):

1. If you have not already defined your Enterprise, do so now.

2. If you have not already added your controller node(s) and device server nodes to your Enterprise, do so now.

Adding Tape Library and Tape Drives to the Enterprise

The following steps are required if you set up your tape library by using Manual Setup (Process B):

1. Add the tape library to your Enterprise. Use the Adding a Tape Library function in the management console. You need to supply information about the controller node. Follow the instructions in Adding a Tape Library.

2. Assign the tape drives to the tape library.

To add the tape drives, use the Adding a Tape Library Device function in the management console. Follow the instructions in Adding a Tape Library Device.

You need to supply information about the Device ID of the tape drive and the Device Number of the drive bay. See the following section for a discussion about Device ID and Device Number mappings.

Determining Device Number and Device ID

Each tape drive in a tape library resides in a unique drive bay. The tape library drive bay is designated by the Device Number and the tape drive driver is designated by the Device ID.

This mapping between the drive bay and tape drive driver is critical for proper tape library operation.

Generally, the first drive bay (Device Number 0) is mapped to the first tape drive. So for Windows, the mapping would be as follows:

\\.\Tape0 is mapped to Drive Bay 0 (Device Number 0) \\.\Tape1 is mapped to Drive Bay 1 (Device Number 1) etc.

Similarly, for Solaris, the mapping would be as follows:

/dev/rmt/0cn is mapped to Drive Bay 0 (Device Number 0) /dev/rmt/1cn is mapped to Drive Bay 1 (Device Number 1) etc.

To confirm this, configure the tape drives in this manner, then try to load and unload a tape.

If you determine that it is not the case that the drive bays are mapped to the tape drives in order, do the following to manually map the device bays to the tape drives:

1. Find out how the tape library numbers the drive bays internally. For example, top down, bottom up, or other. Consult the tape library documentation or manufacturer.

2. Load the tape drives with tapes (preferably scratch tapes).

3. Use the tapedump utility to acquire one of the tape drives and unload the tape. For example:

   $ ./tapedump tape /dev/rmt/0cn open rdonly unload

4. Look inside the tape library and determine which tape ejected. Make note of:

   • The tape library drive bay number (Device Number) of the tape that physically ejects.

   • The Device ID you used to acquire this tape drive (/dev/rmt/0cn in our example)

   • The device server node for this tape drive.

5. Quit tapedump and cycle through the device drivers on this and other device servers to map the tape library in its entirety.

Media Configuration

The following steps are required regardless of whether you set up your tape library using Automatic Setup (Process A) or Manual Setup (Process B):

1. Before backups can be performed using the tape library, media pools (also called tape pools) for the tape library must be created. Use the Adding a Media Pool function in the management console. Media pools should be set up in a way that makes sense for your Enterprise. Follow the instructions in Adding a Media Pool.

2. Associate media volumes (tapes) with the media pools and label the media volumes. You usually want to add tape volumes in sets of consecutively named volsers. DPX provides several methods for assigning media volumes to media pools and labeling media volumes.

Follow the instructions in Adding a Media Volume or Writing a Label in the DPX 4.9.x Reference Guide.

Backing up Data to the Tape Library

Now that DPX recognizes your tape library, tape drives, and media and is able to control the tape library media changer, you are ready to perform backups to media associated with your tape library. For details about defining, scheduling, and running backups and restores, see the Backup and Restore sections.

Manual tape library installation involves creating, on the controller node, a device file for the tape library media changer. This media changer device file is a handle used by DPX to identify the hardware address of the media changer. It thereby allows communication with the media changer. Once that communication is established, the tape library driver controls the media changer.

This chapter explains how to manually install the media changer device file. This procedure is required if you are setting up your tape library using Manual Setup (Process B).

The manual installation procedure for the media changer device file varies according to the operating system installed on the controller node. To see specific installation instructions for a particular operating system, refer to the topic that applies to the controller node of your tape library:

• Tape Library Installation on Windows

• Tape Library Installation on Linux

Furthermore, if you are using third-party software no longer supported by the vendor, Catalogic Software Data Protection Technical Support may be limited for functions dependent on that software. To address certain issues, the analyst may recommend you upgrade the relevant software.

Tape Library Installation on Windows

This procedure explains how to install a tape library for a Windows controller node. Before you begin, make sure the tape library is in random mode (not sequential or stacker mode) and that the media changer is not claimed by the operating system. See Tape Library Setup.

DPX supports both 32-bit and 64-bit versions of Windows.

To install the media changer device file on your controller node, run detect -i at the command prompt. This will automatically generate media changer device files of the form sync_saX, where X is a non-negative integer starting with 0.

Device files are placed in the bin\JB folder. detect -i also creates a symbolic link for each sync_saX device, allowing it to be used as a native Windows device name.

Sample output for detect -i follows:

SCSI Devices found:

------------------

Device       Adapter     Target            Device

ID           ID      BUS ID     LUN STATUS Type                     String

------------ ------- --- ------ --- ------ ------------------------ -------------

\\.\Tape0    2       0   0      2   0      Sequential Access Device SONY    SDX-500C

\\.\Tape1    2       0   0      5   0      Sequential Access Device HP      Ultrium 1

\\.\sync_sa0 2       0   1      3   0      Media Changer Device     BHTi    216

\\.\Tape2    2       0   1      1   0      Sequential Access Device QUANTUM DLT8000

Device                    Serial / Unique                                    

ID                        Number / Id              World Wide Name           Auto

------------------------- ------------------------ ------------------------- ----

\\.\Tape0                 0000902585               20 0 0 50 13 b0 78 94     Yes

\\.\Tape1                 0000911832               20 0 0 50 13 b0 78 94     Yes

\\.\sync_sa0              216B10                                             Yes

\\.\Tape2                 PXB34P3669               20 0 0 50 13 b0 78 94     Yes

This concludes the installation of the tape library media changer device file under Windows. To test the installation, proceed to Tape Library Verification. Use the media changer device file name (for example, sync_sa0) as the argument for the tape library interface test program (JItest).

Tape Library Installation on Linux

This procedure explains how to install a tape library for a Linux controller node. You need to have Linux release 2.2.14 or later. The procedure below is for Linux on Intel-compatible architectures.

For Linux, device files of the media changers are generated by the operating system and are located in /dev/sgX, where X is a non-negative integer starting with 0. Device files of the tape drives are located in /dev/stX or /dev/nstX where X is a non-negative integer starting with 0. The tape drives must be set to no rewind and variable block size, which are commonly not the default. For more information, see the man pages for “st” and “stinit” in addition to consulting the drive manufacturer.

The following is the procedure for tape library installation on Linux:

1. On your controller node, run detect -q at the command prompt. detect -q displays the file names and other information about all SCSI devices accessible by the node on which you are running detect. If everything was connected properly, you will see a media changer device that represents your tape library. Sample output follows:

SCSI Devices found:

-------------------

Device       Adapter     Target            Device

ID           ID      BUS ID     LUN STATUS Type                     String

------------ ------- --- ------ --- ------ ------------------------ -------------

/dev/nst0    2       0   0      2   0      Sequential Access Device SONY    SDX-500C

/dev/nst1    2       0   0      5   0      Sequential Access Device HP      Ultrium 1

/dev/sg1     2       0   1      3   0      Media Changer Device    BHTi    216

/dev/nst2    2       0   1      1   0      Sequential Access Device QUANTUM DLT8000

Device                    Serial / Unique                                    

ID                        Number / Id              World Wide Name           Auto

------------------------- ------------------------ ------------------------- ----

/dev/nst0                 0000902585               20 0 0 50 13 b0 78 94     Yes

/dev/nst1                 0000911832               20 0 0 50 13 b0 78 94     Yes

/dev/sg1                  216B10                                             Yes

/dev/nst2                 PXB34P3669               20 0 0 50 13 b0 78 94     Yes

1. If you do not see any devices, ensure that the kernel has generic SCSI support and tape drive support installed. For more information, see the man pages for “sgen” and “mtx.”

2. If necessary, run detect -i from the bin/JB subdirectory to create any additional device mappings.

This concludes the installation of the tape library media changer device file under Linux. To test the installation, proceed to Tape Library Verification. Use the media changer device file name (for example, /dev/sg1) as the argument for the tape library interface test program (JItest).

Introduction to Tape Library Setup

Catalogic DPX is designed with comprehensive tape library support in mind.

Tape library setup involves two major procedures: installation and configuration. Each of these procedures is described below.

• Tape Library installation entails creating the media changer device file needed to enable communication between DPX and the tape library media changer.

• Tape Library configuration entails defining the tape library properties so DPX can back up to and restore from media (tapes) accessible to the tape library.

For more information about tape libraries in the NetApp environment, read knowledge base article 46357 – Configuring Tape Library Connected to NetApp Appliance.

Tape Library Pre-Setup

Before beginning the tape library setup process, use the Detect utility to ensure DPX can communicate with the medium changer and that the medium changer status is zero.

The recommended starting point is Unknown Medium Changer disabled, which displays in the Windows Device Manager. If Detect can communicate with the medium changer, the status is zero. For each Detect attempt, the goal is to validate that Detect can see a medium changer and that the status is zero. If those states are not displayed, make a change and run Detect again.

Prepare to use Detect

Ensure the following conditions are met before using Detect:

• SCSI support and tape drive support are enabled on the operating system. Physically connect each tape library to its controller node and device servers. You can do this directly or through a SAN.

• The tape device drivers, which are supplied by tape drive manufacturers, are properly installed. Drivers are often available from the manufacturer’s website. Additionally:

  • Drivers are compatible with the operating system of the device server. Consult the documentation provided by your hardware vendor.

  • Tape drivers are capable of writing in variable block size mode.

• On Windows platforms, tape drives are visible in Device Manager and the drives are enabled.

• DPX client software is installed on controller nodes and device servers. Client software is installed on the master server by default.

• For controller nodes, the media changer is not claimed by the operating system or any other software. The media changer must be available for DPX to claim.

• The media changer device is disabled in the Device Manager. On Windows Server, the media changer is usually displayed in Device Manager as an Unknown Medium Changer.

To disable the media changer:

1. Use either of the following methods to navigate to Device Manager:

   • Click Start > Settings > Control Panel > Administrative Tools > Computer Management > Device Manager.

   • Right-click My Computer, then select Properties > Hardware > Device Manager.

2. Right-click on the media changer (usually Unknown Medium Changer). Select Disable.

If you see the message Disabling this device will cause it to stop functioning. Do you want to disable? Select Yes.

Note that disabling the device does not cause the tape library to stop functioning; rather, it removes control of the device by Windows. This enables DPX to claim, detect, and control the device.

Run Detect

Use the Detect utility to validate the status of the medium changer before using the DPX Device Control Wizard. For UNIX and Linux environments, run ./bin/bexenv before running the Detect utility.

To run Detect to validate medium changer status:

1. On the Controller node, click Start > All Programs > DPX Command Prompt (Run as Administrator).

1. From the DPX command prompt, navigate to <product-directory>\bin\JB.

2. Run detect -i.

   The expected result is Device ID \\.\sync_sa# and status 0.

   If the expected result is displayed, go to step 6.

   If the expected result does not display, enable the Unknown Medium Changer and proceed to the next step.

3. Run detect -i again.

   The expected result is Device ID \\.\sync_sa# and status 0.

   If the expected result is displayed, go to step 6.

   If the expected result does not display, install the hardware manufacturer driver for the arm of the tape library. This resolves the Device ID and status of the Medium Changer. Proceed to the next step.

4. Run detect -i again.

   The expected result is Device ID \\.\Changer# and status 0.

   If the expected result is displayed, go to step 6.

   If the expected result does not display, contact Catalogic Software Data Protection Technical Support.

5. If you have not already defined your Enterprise, do it now.

6. Add controller nodes and device servers to your Enterprise.

Device Configuration Wizard

This section is intended for system administrators who are setting up their tape libraries by using Automatic Setup (Process A). If you are setting up your tape library by using Manual Setup (Process B), proceed to Device Detection.

The DPX Device Configuration Wizard allows you to bypass many of the manual steps otherwise required for setting up tape libraries.

When possible, the Device Configuration Wizard generates, maps and names device drivers for each tape drive and tape library media changer. It then adds the tape libraries and tape drives to the Enterprise.

You can apply the Device Configuration Wizard to an existing installation. If you do, the Device Configuration Wizard may update those devices for which it detects a Unique ID, which is the unique identifier assigned to a device by the vendor or agency, usually the device’s serial number.

Platform Considerations

The Device Configuration Wizard is supported by any DPX client running an operating system supported for DPX device servers. An exception is Linux OES, which does not support the wizard.

Tape libraries on platforms that do not support the Device Configuration Wizard must be set up manually, using the procedures described in this instruction set.

Devices Not Auto-Configurable

You should be aware of the following caveat before executing the wizard:

The Device Configuration Wizard may set up some, but not all of the tape drives and media changers in your Enterprise. For example, a device (tape drive or media changer) might not be configurable by the wizard if DPX cannot detect a Unique ID for that device.

Any device not completely set up by the Device Configuration Wizard should be set up manually, using the procedures described in the following sections.

Before starting the Device Configuration Wizard, you can determine whether a given device is configurable by the wizard by running “detect -q” from a device server node accessible to the device. The Detect utility is described in detail in Device Detection. The Auto field on the output report produced by Detect indicates whether the device can be set up with Device Configuration Wizard.

Executing the Device Configuration Wizard

Before executing the Device Configuration Wizard, confirm that all pre-setup steps have been completed. The Device Configuration Wizard can be run from any machine that can ping your master server. Set the environmental variable SSICMAPI so that it points to the master server.

For example:

set SSICMAPI = -a 6123

or

setenv SSICMAPI "-a 6123"

Launching the Device Configuration Wizard

To launch the Device Configuration Wizard from Windows:

• Click Start > DPX > Device Configuration Wizard

To launch the Device Configuration Wizard from UNIX:

1. Change to the bin directory under the installation directory. In addition, you may need to set the DISPLAY environment variable to your local host.

2. Enter ./devconfwizard at the shell prompt.

The Device Configuration Wizard window is launched.

The wizard asks you to log into your Enterprise. Log into the master server as an administrator. After entering your credentials, click next.

Using the Device Configuration Wizard

The Device Configuration Wizard uses an intuitive graphical user interface to guide you through the device configuration process. The wizard probes your Enterprise and detects information about your nodes, devices, tape libraries, and connections.

The following is a sample session of the Device Configuration Wizard for illustrative purposes. This sample session sets up a SAN with three heterogeneous servers and one six-drive tape library, as depicted in the following diagram:

1. The wizard displays all nodes in the Enterprise that can serve as device controller nodes.

   Use the checkboxes to select one or more controller nodes for which you want to install and configure devices.

1. Clicking the Options… button will display a dialogue box with a list of configurable scan options.

The following options can be adjusted:

• Show all the nodes

  There may be nodes on the Enterprise whose configuration options indicate they are not compatible with scanning. By default, these nodes are not displayed in the list of potential device controllers. Selecting this option will include those nodes in the list.

• Concurrent Nodes to Scan

  This setting affects how many nodes the wizard will communicate with concurrently while performing the scan. This can affect scan speed.

• NDMP Port NDMP-capable. This setting allows you to set a port number for communicating with NDMP-capable NAS nodes.

• Check here to enable Catalogic DPX LTO Encryption Option Clicking this check box will activate the Please Select pull-down menu, which you can use to enable, update or disable LTO hardware encryption functionality. The Enable/Update option enables the encryption option for nodes that support this feature or updates the list of tape devices to which the node can encrypt data.

1. Click OK to confirm your options choice.

2. Clicking the Assign Peer Nodes… button displays any other nodes that can communicate with devices in the SAN. (These nodes are not running one of the supported platforms listed at the beginning of this chapter).

3. When finished configuring options and selecting devices, click next. At this point, the wizard scans the selected node(s) for SCSI devices.

When the nodes have been successfully scanned, “Done” appears in the status column, and the next button becomes enabled. Click next to continue.

1. The wizard displays all unconfigured tape libraries accessible by the selected nodes. In this example, there is only one tape library, and it is accessible by both nodes. Select the tape library that corresponds to the server (controller node) that will control the media changer. You can either click anywhere in the entry’s row and then click the Add to Enterprise button (which becomes enabled once a selection is made), or you click the entry’s associated check box, which will advance you to the next step without the need to click Add to Enterprise

2. The wizard requests information about the tape library you selected.

Complete the active fields in the dialog:

• Configure As SAN

  This check box gives you the option to configure the device as a SAN. The check box appears if the device is seen by only one node. If multiple nodes see the device, it is automatically configured as a SAN and the check box does not appear.

• Tape Library Name

  Enter a name (up to 14 alphanumeric characters) for the tape library (for example, DEC_TL810). No two tape libraries in the Enterprise can have the same name.

• Tape Library Type

  Select the tape library type (for example, DEC_TL810) from the pull-down menu. If your tape library type is not shown, select the type that most closely matches yours.

• Controller ID

  The Device Configuration Wizard generates a media changer device file and installs it on your controller node. The name of that file, assigned by DPX, is displayed in this field.

• Data Slots

  From the pull-down menu, select the starting and ending slot numbers to use for media volumes. Note that slot numbers start at zero (0). Thus, the first slot is slot number 0, and the final slot is slot number (n-1), where n is the number of slots in your tape library.

• Cleaning Slots

  From the pull-down menu, select the starting and ending slot numbers to use for cleaning tapes. To configure a single cleaning slot (typical setup), enter the slot number twice. If no cleaning slots exist, leave these fields blank.

• Device Type

  Select a device type (for example, LTO) from the pull-down menu. All devices in a tape library must be the same type.

• Cleaning Threshold

  Enter the number of times a drive can be used before it is cleaned.

• Comment

  Optionally enter an alphanumeric string of up to 48 characters.

When you have filled in all the required information, click next.

1. The wizard displays a list of devices attached to the newly added tape library. If you need to change the device names, you can do so on this screen. Click inside the device name field and enter a new one.

2. When you are finished changing device names, click next.

3. The wizard indicates that the tape library has been added by placing a checkmark in the box in the leftmost column on the New Tape Libraries window. If you have additional tape libraries to add to the Enterprise (in this case we do not), repeat steps 3 through 5 for each.

1. Click next when you are finished adding tape libraries. The wizard shows the devices that were added, as well as other detected devices that were not part of a configurable tape library. Use this window to add additional devices, as well as to remove any of the devices added in previous steps.

2. To add additional listed devices, select a device and click Add to Enterprise, assign the device to a tape library or device pool, then specify a device name. To remove a device you have already added, select the device and click Remove from Enterprise.

1. Click Exit to exit the Device Configuration Wizard.

2. Later, when you log into the management console and navigate to the Configure Devices window, you can open the device clusters to view all the devices and device paths for a given tape drive.

You can edit the information for any of these devices in the management console under Configure Devices.

Device Detection

General Remarks

If you set up your tape library using Manual Setup (Process B), detection is the first step. The DPX Detect utility is also a handy tool for troubleshooting down the road.

The Detect utility allows you to display and map media changers and tape drives accessible from a given device server or controller node. This utility is found in the /bin/JB subdirectory of the main directory.

Detect can be run from any machine on your network under an administrative User ID.

If you are using third-party software no longer supported by the vendor, Catalogic Software Data Protection Technical Support may be limited for functions dependent on that software. To address certain issues, the Catalogic Software Data Protection Technical Support may recommend you upgrade the relevant software.

The AIX platform offers limited support, meaning that the configuration phase is not supported and the detection phase may miss some properties such as the World Wide Name or Serial Number. Other platforms offer full support meaning that the Detect utility can detect devices and obtain their vendor ID, product ID, SCSI Target, LUN, etc., plus their World Wide Name and Serial Number. Besides the detection phase, this utility can create (configure) device files.

Some versions of UNIX detect require running in a shell that has the appropriate environment setup. For details contact Catalogic Software Data Protection Technical Support.

The detect -q Utility

You can use either detect -q or detect --query. They are different formats of the same command.

As the first step to every manual tape library installation on the above platforms, you should run the following on your tape library controller node:

detect -q

detect -q gathers and displays information about media changers and tape drives that are accessible from the node on which you are running Detect. detect -q does not create or install any new devices and does not modify any files. Thus, it is always safe to run Detect with the -q command line option. The following is an example of output from detect -q:

SCSI Devices found:

------------------

Device       Adapter     Target            Device

ID           ID      BUS ID     LUN STATUS Type                     String

------------ ------- --- ------ --- ------ ------------------------ -------------

\\.\Tape0    2       0   0      2   0      Sequential Access Device SONY    SDX-500C

\\.\Tape1    2       0   0      5   0      Sequential Access Device HP      Ultrium 1

\\.\sync_sa0 2       0   1      3   0      Media Changer Device     BHTi    216

\\.\Tape2    2       0   1      1   0      Sequential Access Device QUANTUM DLT8000

Device                    Serial / Unique                                    

ID                        Number / Id              World Wide Name           Auto

------------------------- ------------------------ ------------------------- ----

\\.\Tape0                 0000902585               20 0 0 50 13 b0 78 94     Yes

\\.\Tape1                 0000911832               20 0 0 50 13 b0 78 94     Yes

\\.\sync_sa0              216B10                                             Yes

\\.\Tape2                 PXB34P3669               20 0 0 50 13 b0 78 94     Yes

Note that the output contains two tables. The rows in both tables are identified by the Device ID field. The device representing the media changer is identified by Media Changer Device or simply Medium in the Device Type field. So, in the tables above, the third row (\\.\sync_sa0) is the row representing the media changer.

The output displayed above is for a Windows platform, but the content would be similar on any platform. (For Solaris, a freshly connected tape library might not be detected by detect -q, in which case you should use detect -i as described in the next chapter). The following describes the fields (columns) in the output from detect -q, specifically with regard to the media changer device:

Note that the Detect output does not have a specific field indicating whether the device is claimed. However, if the appropriate driver does not claim a device, its name will not appear in the Device ID column and -1 will appear in the status column.

More about the Detect Utility

Install Option: Overview

For all platforms listed in the introduction to this topic, you can use detect -i or detect --install, to install the media changer device file. This is discussed in greater detail in Manual Tape Library Installation.

Debug Option

The Detect utility also has a debug option, -d.

For all platforms listed in the introduction to this chapter, there are three debug levels: 1, 2, and 3, with level 3 being the most comprehensive. For example, you can run:

detect -d 3 -q

detect -f

The Detect utility -f N options (where N is 1, 2, 3, or 4) allow you to bypass some operations of detect -q.

• detect -f 1 processes only media changer devices.

• detect -f 2 processes only sequential access devices (tape drives).

• detect -f 3 processes media changer and sequential access devices.

• detect -f 4 processes only devices that are not changers or tape drives.

Prerequisites for Tape Library Deployment

A physical node in the Enterprise is available to control the tape library’s media changer. This can be a Windows server, Linux server, or the NetApp storage controller. A virtualized node cannot be used for media changer control. This controller node must have a host bus adapter. Note that a media changer is also referred to as a robotic arm and a host bus adapter is also referred to as an HBA.

Recommended Best Practices for Tape Libraries

• The media changer is attached to a SAN (storage area network) and zoned to the master server. Therefore the master server acts as the tape library’s controller node.

• The tape drives are attached to the SAN and zoned to the NetApp storage system. Therefore the NetApp storage system acts as the device server.

• The tape library is a modern, vendor-supported library with tape drives capable of writing in variable block size mode. The media changer is SMC-2 compliant and supports the DVCID option of the Read Element Status command. The tape drives are SCSI-2 compliant and support variable length records and extended file marks. The tape library and tapes support bar coding. Most modern tape libraries fit these requirements. DPX does not support libraries and tape drives currently unsupported by the device vendor.

• For DPX purposes, the media changer device and associated tape drives must belong to only one Enterprise controlled by a single master server. Tape library media changer control cannot be shared with other backup products and cannot be accessed by more than one master server.

Other Tape Library Setup Scenarios

If, in conjunction with the customer, a strategic determination is made to attach the media changer or tape drives differently, you can do so. However, the practices described in are highly recommended to maximize reliability and minimize troubleshooting challenges.

There are several supported ways to attach the tape library’s media changer and tape drives to the Enterprise. They can be connected through a fiber channel SAN, iSCSI SAN, direct fiber channel attachment, or legacy parallel SCSI cable attachment.

If the connection is through a fiber channel SAN, the media changer must be controlled by a device server, not by a NetApp storage system, and the tape drives can be controlled by any node or NetApp storage system.

If direct attachment through a fiber channel or legacy parallel SCSI is required, it is highly recommended for the media changer and at least one tape drive to be attached directly to the master server to support media changer control and Catalog backups. If a tape drive cannot be connected or accessed through the master server, an alternate strategy must be used to move Catalog backups to a safe medium that can be recovered in the event of a site disaster.

iSCSI SAN connections are generally not recommended due to latency and connection reliability. If iSCSI is absolutely necessary, for example, if no physical server with HBA is available for media changer control, great care must be taken by the site administrators to ensure such connections are very reliable. Any disruption in connection will impact backup and media control operations.

Though it is possible to attach a tape library directly to a NetApp storage system for exclusive control of media changer and all tape devices, it is not recommended as an alternate strategy for Catalog backups is required. Additionally, media changer reliability and troubleshooting may be problematic, requiring moving the media changer device to a node with an HBA physical server. NetApp media changer control is also limited to tape libraries with 600 total slots or less; larger tape libraries do not work properly due to SCSI limitations.

DPX automatically tracks the relationship of tapes to tape library tape slots. For example, when a tape is added to a tape library through an import/export port, DPX is aware of the new tape and the slot it occupies; that is, the Catalog assigns the tape to a slot.

However, the Catalog can become unsynchronized if, for example, a tape is physically removed from a tape library. In such cases, you can use the assign/unassign function of DPX to update the Catalog.

To assign media to tape library slots:

1. On the Configure Device window, click Display Slots and Media Controls.

   The Assign/Unassign Tapes window appears. Tape libraries are displayed in the left pane and media pools are displayed in the right pane.

2. In the left pane, expand the desired tape library to the tape slot level. In the right pane, expand the desired media pools to the tape level. The following shows one tape library with six defined slots (all of which have tapes assigned) and three media pools, with the JBLPool expanded.

1. In the right pane, select the unassigned tapes you want to assign.

1. Do one of the following:

• In the left pane, select the “empty” slots to which you want to assign the tapes. For multiple selections, use CTRL-click and SHIFT-click.

  Then click Assign Tapes to Slots.

• Drag and drop the tapes to one “empty” slot. If you selected multiple tapes, the slot should be the first slot that you want to assign tapes to.

DPX assigns the tapes to the slots in volume number and slot number order.

To unassign media from tape library slots:

1. On the Configure Device window, click Display Slots and Media Controls.

   The Assign/Unassign Tapes window appears. Tape libraries are displayed in the left pane and media pools are displayed in the right pane.

2. In the left pane, expand the desired tape library to the tape slot level.

3. In the left pane, select the “filled” slots that you want to unassign. For multiple selections, use CTRL-click and SHIFT-click.

4. Do one of the following:

   • Click Unassign Tapes from Slots.

   • Drag and drop the selected tapes to any media pool.

   DPX unassigns the slots. Each tape remains in the media pool to which it had been added.

Considerations for Assigning and Unassigning Media and Slots

The following should be considered when assigning media to slots or unassigning media from slots:

• Irregular tape libraries, such as ACSLS, IBM ATL, or AML, do not appear on the Assign/Unassign Tapes window.

• A tape cannot be assigned to a slot that already has a tape assigned to it.

• An already assigned tape cannot be reassigned unless it is unassigned first.

• When you assign media using drag-and-drop, tapes cannot be assigned to slots that have not been rendered to the Assign/Unassign Tapes window. (DPX renders slots and tapes to the management console in batches of 200; scrolling renders the next batch). Selected tapes that do not get assigned remain selected for user convenience.

• When assigning media by using the Assign Tapes to Slots button:

  • If more slots than tapes are selected, only the necessary number of slots receive tape assignments.

  • If more tapes than slots are selected, the selected tapes that do not get assigned remain selected for user convenience.

General Overview

This topic describes the procedures required to set up an LTO4, 5, or 6 tape device for hardware encryption. The procedures that apply depend on the tape device manufacturer and operating system, as indicated in the following table:

Note the following:

• For HP and Quantum tape devices on Windows device servers, the Bexsptape device driver is required for hardware encryption. Implementing Bexsptape is done in .

• For IBM tape devices, Bexsptape is not needed. An IBM device driver supporting hardware encryption is required. Only applies to IBM drives.

• For Linux and UNIX operating systems, Bexsptape is not required.

Procedures for Setting up LTO Tape Drives for Hardware Encryption

Follow the procedures that apply to your tape device and operating system; thus, for IBM devices, skip to ; for Linux and UNIX device servers, omit .

Procedure 1. Enable Hardware Encryption

To enable hardware encryption using the Device Configuration Wizard:

1. Launch the Device Configuration Wizard.

2. In the Select Nodes to Scan dialog, select the node where the drive is installed, and then click Options. The Node Options dialog displays.

3. Select the check box Check here to enable DPX LTO Encryption options.

4. From the Please select drop-down menu, select Enable/Update.

5. Click OK.

6. If the drives are already added to the Enterprise, click Exit. If the drives are not added to the Enterprise, continue to use the Device Configuration Wizard to add them.

Procedure 2. Configure the Windows Device Sever to Use the Bextape Device Driver

To configure the device server for Bexsptape:

1. In the Windows Device Manager, locate the tape device to associate with the Bexsptape driver. Note the following:

   • If the tape device already has a driver associated with it, uninstall the driver. If a selection displays to permanently delete the driver, it is recommended to select it. This ensures that the driver is not available for the device in the future, eliminating possible conflict with Bexsptape.

   • Tape devices that do not have a driver associated with it are in the Other Devices container of the display.

2. Right-click the appropriate tape device, and then select Update Driver Software from the pop-up menu. The first page of a wizard appears.

3. You are asked how you want to search for driver software. Select Browse my computer for driver software.

4. On the next wizard page, select Let me pick from a list of device drivers on my computer. Click Next.

5. From the display list, select your device type, Tape drives. Click Next.

6. On the next page, enter the location of the Bexsptape device driver. Select Have Disk.

7. Browse to <product-directory>/bin/drivers/<Osver>, where <Osver> is specific to the version of Windows the device is installed on.

8. From the display list, select bexsptape. Click Open.

9. Select the tape drive manufacturer and model in the Model list. Click Next.

10. A success window appears, confirming that the driver software is updated. Click Close.

11. Confirm that the tape drive appears in the Tape drives container in the Windows Device Manager display.

Procedure 3. Run Detect

Run the Detect utility to record the device id and update your data protection Enterprise to use the Bexsptape driver.

The Bexsptape type of device file is formulated as: bexsptape_vp<0123456789>_cn or bexsptape_vp<0123456789>_n, where

• v and p are the first character of the vendor ID and product ID reported by the SCSI Inquiry command.

• <0123456789> is the ten-digit unit serial number reported from the tape device.

• n denotes no rewind.

• c denotes compression enabled.

Either device id format, ending in _cn or _n, may be used when configuring the tape device in your Enterprise.

Once the Detect utility completes, the tape device is available for hardware-encrypted tape backups.