data domain vtl

Integrating the Data Domain Appliance VTL with SANs

05/04/07 Rev. A 1 of 37


The instructions provided in this document by Data Domain are for customer convenience and are not warranted or supported by Data Domain. Data Domain expects users to customize installation of third-party software for use at a particular site, but Data Domain is not responsible for the usability of third-party software after installation. Copyright © Data Domain, Inc. 2005 - 2007


05/04/07 Rev. A 2 of 37

Table of Contents 1. Introduction............................................................................................................................. 3

1.1. Data Domain Technology ............................................................................................... 3 1.2. VTL Functionality .......................................................................................................... 3

2. Configuring the VTL feature on the Data Domain Restorer .................................................. 4 2.1. VTL Feature Notes ......................................................................................................... 5 2.2. VTL Guidelines .............................................................................................................. 5

2.2.1. Tape Model Numbers ............................................................................................. 5 2.2.2. Virtual Tape Cartridges........................................................................................... 5 2.2.3. LUN Masking ......................................................................................................... 6

2.3. Tape Markers .................................................................................................................. 8 2.4. VTL Quick Setup............................................................................................................ 9 2.5. Detailed VTL Setup Example......................................................................................... 9

3. Configure Zoning.................................................................................................................. 11 3.1. Zone Configuration Example Using Brocade Switches ............................................... 11

4. Configure Host Bus Adapters ............................................................................................... 13 4.1. Configuring Solaris HBAs............................................................................................ 13

4.1.1. Emulex LP Series HBA ........................................................................................ 13 4.1.2. QLogic SANBlade Series HBA............................................................................ 13 4.1.3. Troubleshooting for Solaris 8, 9 ........................................................................... 14

4.2. Configuring Windows HBAs........................................................................................ 15 4.2.1. QLogic SANBlade Series HBA............................................................................ 16

4.3. RHES 3.0 Server With Emulex HBA Card .................................................................. 18 4.4. Configuring HP-UX HBAs........................................................................................... 19

4.4.1. Troubleshooting for HP-UX 11.11 ....................................................................... 20 5. VTL Device OS Discovery and Configuration..................................................................... 21

5.1. Solaris 8 and Solaris 9 Backup Servers ........................................................................ 22 5.2. Windows Backup Servers ............................................................................................. 24 5.3. RedHat Backup Servers ................................................................................................ 25

5.3.1. Discover Restorer VTL Devices on RedHat Linux .............................................. 25 5.3.2. Enable Multiple LUNs in the Kernel .................................................................... 27

5.4. Using the Restorer VTL with EMC Celerra ................................................................. 28 5.4.1. Installation & Configuration ................................................................................. 28 5.4.2. Tips ....................................................................................................................... 30 5.4.3. Gotchas ................................................................................................................. 32 5.4.4. Performance Tuning.............................................................................................. 32 5.4.5. Troubleshooting .................................................................................................... 33

5.5. Using the Restorer VTL with Network Appliance ....................................................... 33 5.5.1. Verifying NetApp and VTL Connectivity ............................................................ 33 5.5.2. Troubleshooting Tips ............................................................................................ 34 5.5.3. When using a CISCO MDS switch, NetApp Filer, and VTL:.............................. 34

5.6. Using the Restorer With HP-UX Servers ..................................................................... 35


05/04/07 Rev. A 3 of 37

1. Introduction This document addresses the integration of Data Domain Appliance(s) with storage area networks (SANs) using the Virtual Tape Library (VTL) feature. VTL functionality makes disk storage appear as physical tape drives when seen from various operating systems, backup software products, and industry-standard device drivers. Although this document gives instructions for setting up the Data Domain VTL feature with 3rd party host bus adapters (HBAs), operating systems (OSes), and Fibre Channel switches (FC switch), always read and be familiar with documentation supplied by the product manufacturer. Assume that the 3rd party documentation is more up-to-date, detailed, and accurate than this document.

1.1. Data Domain Technology Data Domain’s Enterprise Protection Storage systems have transformed disk backup, network-based disaster recovery (DR) and remote office data protection with:

• Global Compression, highly efficient deduplication and compression technology, and radically changing disk storage economics to less than $0.35/GB

• Data Invulnerability Architecture, providing unprecedented levels of data integrity, data verification, and self-healing capabilities

• Replication technology, enabling automatic, secure transfer of compressed data over the wide area network (WAN) with 99% bandwidth reduction

• Compatibility with all leading enterprise backup software, ensuring seamless integration with existing backup and recovery infrastructure.

1.2. VTL Functionality For other vendors' products, set up for the Data Domain VTL feature is done in the same way as set up for physical tape devices and media changers. Data Domain has developed several manuals that address VTL functionality and these manuals should be consulted prior to your solution implementation:

• Restorer Operating System User Guide • Command Reference • Quick Start Guide • Release Notes

NOTE: StorageTek library and IBM Ultrium licenses may be necessary for your backup

software to use the data Domain VTL feature. NOTE: Backup and restore operations can also be done with the Data Domain file system

(CIFS and NFS) functionality. Contact your Data Domain or Partner Systems Engineer to determine an optimal backup and restore solution for your needs.


05/04/07 Rev. A 4 of 37

For backup software and backup server operating systems that are supported with the restorer VTL feature, see the Data Domain Support web site, Compatibility Matrices, Backup Software compatibility using VTL entry http://iweb.datadomain.com/support/compat_matrix.php. Each section of this document includes steps that allow an operating system, backup software, or protocol to recognize a Data Domain restorer as a tape drive destination. However, you should use this document in conjunction with Data Domain tech notes that address the configuration and operation of the VTL feature with specific 3rd party backup applications. Preparing the SAN and Data Domain VTL feature for backup application usage requires five main tasks in the following order:

o If using a Fibre Channel switch or fabric, configure the zoning. o Configure FCP Host Bus Adapters (HBAs). o Configure the Data Domain restorer and VTL feature. o Discover and configure the VTL LUNs on the backup server or filer. o Configure the backup & restore software to recognize and interoperate with the VTL. o Refer to separate Data Domain tech notes (http://iweb.datadomain.com/support/docs.php)

that describe the integration of the VTL feature with the backup application software you intend to use.

NOTE: See separate Data Domain tech notes to configure and operate the VTL feature with 3rd

party backup applications (http://iweb.datadomain.com/support/docs.php) NOTE: An HBA on the backup server dedicated for use with the VTL option is required.

Please contact Data Domain if you must share the same HBA with physical tape or storage.

2. Configuring the VTL feature on the Data Domain Restorer This section provides brief instructions for configuring the VTL feature and an example. Refer to the Data Domain user guide for detailed VTL instructions and reference material. To use the VTL feature, the restorer software must be DD OS release 3.2.2.4 or later. Before configuring the VTL feature, use the Data Domain Quick Start document to check the restorer setup information such as IP address, netmask, hostname, and CIFS configuration. Configuration of a Data Domain restorer is simple. Execute config setup at the command line and follow the prompts. Once configured, the restorer is ready to activate the VTL feature. NOTE: The default password for the sysadmin account is the restorer serial number. Use the serial number as the password to log on for the first time. After the first login, DD OS will launch config setup. Simply answer the questions and the restorer will be ready to setup the VTL feature.


05/04/07 Rev. A 5 of 37

2.1. VTL Feature Notes Be aware of the following behavior when configuring the VTL feature on a Data Domain restorer.

• The VTL feature is separately licensed and requires a separate license key • The first restorer library created uses LUN0 for the first device and the next LUNs in

sequence for the other devices in the library. If you have more than one library defined from one restorer, the second library starts with the next available LUN. For example, library1 with five tape drives takes five LUNs for tapes and one for the media changer, using LUNs 0 through 5. Library2 starts with LUN6.

• The library that uses LUN0 (the first library) can be deleted only if it is the only library. Other libraries can be deleted in any order, but to delete the first library, you must first delete all other libraries. If you want to delete library1 and keep library2, you must delete both libraries and recreate library2 to start with LUN0

2.2. VTL Guidelines To install and manage the Data Domain VTL feature:

2.2.1. Tape Model Numbers The current supported tape models are L180 and RESTORER-L180. Both models emulate an STK L180. The L180 tape library model name presents itself as an STK L180, which is a widely deployed tape library recognized by all major backup applications. The tape library model name is used by the backup application software to identify the physical device and the associated characteristics used by the backup application software. Some backup applications require the RESTORER-L180 tape library model name. Other applications may need an update to recognize RESTORER-L180 as a unique device that emulates a STK L180, and to assign the appropriate functionality. If the backup application update is not done, a backup application may fail to use the restorer VTL properly. Please see the appropriate backup application release notes. GUIDELINE: Check with your backup application software provider to determine what model

to use when adding the VTL.

2.2.2. Virtual Tape Cartridges

Barcodes Data Domain recommends creating virtual tape cartridges with unique barcodes. An error appears during an attempt to create a duplicate barcode in the same tape pool, but no error appears when creating a duplicate barcode in different tape pools. However, duplicate barcodes in different pools can result in operator confusion and anomalous backup application behavior.


05/04/07 Rev. A 6 of 37

Optimizing Restorer Storage Utilization The size and quantity of tapes created impact the use of restorer disk and CPU resources. For the efficient reuse of restorer disk space after data is obsolete (and the restorer cleaning process marks data for removal), Data Domain recommends setting tape capacity to 100 GB or less and creating only the number of virtual tape cartridges needed to support the defined backup retention policies. A tape is available when all data streams have expired and the media is marked as recyclable (reusable or scratch). However, many backup applications continue to use new tapes even though tapes with expired data are available. The applications only overwrite data when no new tapes are available and in some cases only when explicitly configured to do so. With such applications, you could run out of disk space to store backup data if too many tapes are defined. Several options exist to reduce such disk utilization. The first step is to create only the quantity of virtual tape cartridges needed to support the defined backup retention policies. To recycle expired media cartridges and free up restorer disk space: • Manually recycle the media. With some backup applications, re-labeling the virtual tape

cartridge recycles the media. • Configure the backup application to re-use media. Many backup applications by default set

policies to not overwrite media. Reconfigure the policies to re-use media. GUIDELINEs:

• Set virtual tape cartridge capacity to 100 GB or less • Create only as many virtual tape cartridges as needed, adding virtual

tape cartridges only when needed. • Configure the backup application to re-use media

Replicated Virtual Tape Cartridges Backup application behavior for handling Data Domain replicated tapes varies. Be aware that the replicated tapes are marked as read only. To minimize unexpected behavior or error conditions, virtual tape cartridges should remain imported in the destination libraries only for as long as needed. Once a replicated virtual tape cartridge is imported at the destination, follow the procedures identified by the backup application to re-use the replicated virtual tapes. The replicated virtual tapes should then be exported from the destination library. The objective is to ensure that at any time only one instance of a replicated virtual tape is visible to the backup application.

2.2.3. LUN Masking In most cases, a virtual tape library needs to be accessed by only one client (a host or media server). However, some issues, such as licensing, may call for multiple clients to access the same VTL. Under such circumstances, an important point is that only one LUN mask exists for each virtual tape drive and the virtual media changer. Anomalous and unexpected behavior can result if more than one initiator (host) accesses the same virtual tape drive or virtual media changer (that is, more than one LUN mask per virtual tape drive or virtual media changer exists).


05/04/07 Rev. A 7 of 37

Figure 1 shows how multiple servers can share the Data Domain Appliance. Server MS #1 has exclusive access to VTL 1. The Changer or VTL 2 (LUN 3) is controlled by server MS #2. Server MS #2 has access to VTL 2 drives 1 and 2. ServerMS #3 access VTL 2 drives 3 and 4.

Confidential10

VTL / LUN Relationship

VTL 1

VTL 2

ChangerLUN0

Drive 1LUN1

Drive 2LUN2

HBASAN

Can Access:VTL 1 Changer = LUN’ 0Tape Drive 1 = LUN’ 1Tape Drive 2 = LUN’ 2

MS #1

MS #2Can Access:VTL 2 Changer = LUN’ 0

MS #3Can Access:Tape Drive 1 = LUN’ 1Tape Drive 2 = LUN’ 2

VTL 1

Master Server

Media Server

Media Server

VTL 2

LUN’ are LUNs on HostLUNx are Devices on the DDR

ChangerLUN3

Drive 3LUN4

Drive 4LUN5

Figure 1 Sharing A VTL Note that in Figure 2, Server MS #2 can not access VTL 1, drives 1 or 2. The drives are masked to Server MS #3. In Figure 2, Server MS #1 controls the Changers for VTL 1, VTL 3, and VTL 8.


05/04/07 Rev. A 8 of 37

Confidential11

LUN Masking Enables Multiple Media Servers

* Note: Virtual tape drive and media changer sharing by multiple media managers is not supported

HBA

VTL 1

VTL 8DD4xxDD5xx

orDDxxxg

Tape Drive 1Tape Drive 2Tape Drive 3Tape Drive 4

Tape Drive 29Tape Drive 30Tape Drive 31Tape Drive 32

SAN

MediaServers

Can Access:VTL 1 ChangerVTL 3 ChangerVTL 8 Changer

MS #1

MS #3

MS #2Can Access:VTL 1, TD 3, 4VTL 3, TD 9, 10VTL 1, TD 1, 2*

Can Access:VTL 1, TD 1, 2VTL 8, TD 29, 30VTL 3, TD 9, 10*VTL 8 Changer

* Multi-initiator not supportedTape Drive (TD)

Figure 2 LUNs Can Not Be Shared

2.3. Tape Markers To realize optimal compression with some backup and restore applications, tape markers must be set on the restorer. Please reference the Compatibility Matrices, Backup Software compatibility using VTL entry (https://support.datadomain.com/compat_matrix.php) to determine if tape markers are necessary for your application. When referencing the matrix, identify the application you intend to use. If a tape marker is required, a note appears in the Backup Vendor column of the matrix. For example:


05/04/07 Rev. A 9 of 37

2.4. VTL Quick Setup This section provides a short example of using VTL configuration commands to setup a VTL. 1. On the restorer, define the tape devices and media changers, which are seen as devices by

backup applications. See the Data Domain Restorer Operating System User Guide for details. 2. The VTL feature is a licensed feature. Use the following commands to display licenses and

then install the license if needed:

# license show # license add <license code>

3. On the restorer, enter commands similar to the following. The fourth command is an example

of importing tapes into a VTL. The fifth command displays port and world-wide-name information for the restorer HBA and the media server HBA. For example:

# vtl enable # vtl add vtl1 model L180 drives 4 slots 32 # vtl tape add AAA000L1 capacity 100 count 32 # vtl import vtl1 barcode AAA000L1 count 32 # san show summary

2.5. Detailed VTL Setup Example This section illustrates the setup, on a restorer, of a new VTL with 4 drives and 32 slots with 32 newly imported tape volumes. The example also includes use of LUN masking of the VTL.

1. As the sysadmin or other user with administrator rights, add the VTL license:

# license add XXXX-XXXX-XXXX-XXXX

2. Verify that the new VTL License is installed:

# license show ## License Key Feature -- ------------------- ------- 1 XXXX-XXXX-XXXX-XXXX VTL -- ------------------- -------

3. Activate the VTL processes:

# vtl enable Starting VTL, please wait..... VTL is enabled.

4. Create a new VTL with the vtl add command:

# vtl add vtl1 model L180 drives 4 slots 32 VTL added. Use 'vtl show config vtl1' to view it.


05/04/07 Rev. A 10 of 37

5. Show the configuration:

# vtl show config Library Name Library Model Drive Model Slots Drives ------------ ------------- ----------- ----- ------ vtl1 L180 LTO-1 32 4 ------------ ------------- ----------- ----- ------

6. Create 32 virtual tapes and put the tapes into the virtual vault:

# vtl tape add AAA000L1 capacity 100 count 32 ... added 32 of 32 tapes...

7. Import all 32 tapes from the vault to the new vtl:

# vtl import vtl1 barcode AAA000L1 count 32 ... imported 32 of 32 tapes...

8. Show the imported tape volumes:

# vtl tape show all ... processed 30 tapes... Barcode Pool Location Type Size Used Compression -------- ------- -------- ----- -------- ------ ----------- AAA000L1 Default vault LTO-1 100.0 GB 0.0 GB 0x AAA001L1 Default vault LTO-1 100.0 GB 0.0 GB 0x . . .

9. View the world-wide-name information for the restorer HBA and the server HBA:

# san show summary Initiator Mode Ports Target Mode Ports HBA 0: WWNN 20:00:00:e0:8b:82:9c:da WWPN 21:00:00:e0:8b:82:9c:da Port ID: 0x010000 Port State: Link Up - 2Gb/s F_Port Node 0: WWNN 50:06:0b:00:00:13:48:c7 WWPN 50:06:0b:00:00:13:48:c6 Port ID: 0x010400 Roles: unknown Port State: Offline Name: alexa Nexus : Inactive


05/04/07 Rev. A 11 of 37

10. Configure LUN masking by defining an initiator and the defining the LUN masks:

# vtl initiator add alexa wwpn 50:06:0b:00:00:13:48:c6 # vtl initiator show Initiator WWPN Status --------- ----------------------- ------- alexa 50:06:0b:00:00:13:48:c6 Offline --------- ----------------------- ------- # vtl lunmask add vtl1 all name alexa # vtl lunmask show Device Initiator LUN ------------ --------- --- vtl1 changer alexa 0 vtl1 drive 1 alexa 1 vtl1 drive 2 alexa 2 vtl1 drive 3 alexa 3 vtl1 drive 4 alexa 4 ------------ --------- ---

3. Configure Zoning A Fibre Channel SAN requires the following steps to configure zoning.

• Identify the devices to be configured. Use the device World Wide Port Name (WWPN) or use Domain, Port.

• On a Fibre Channel switch, create a zone that contains the Data Domain VTL and the backup server HBA. Use either WWPN or Domain, Port.

• Save the new zoning configuration. • Activate the new zoning configuration.

GUIDELINE: Data Domain highly recommends using a single backup server or filer HBA in a

zone. The technique is called single initiator zoning. GUIDELINE: Data Domain also recommends that the HBA access only the restorer VTL

devices. In other words, do not share SAN-attached disks or tape and the SAN-attached restorer VTL tape LUNs on the same backup server HBA.

Exceptions to the above recommendations are possible. Please contact your Data Domain Systems Engineer to discuss exceptions.

3.1. Zone Configuration Example Using Brocade Switches An example of configuring zoning for Brocade switches is detailed in this section. To simplify the example and optimize the number of pages in this document, the command line interface (CLI) is used. The graphical user interface (GUI) is an acceptable means to configure zoning and in many cases may be easier and simpler than the CLI. The configuration used for this example is shown in Figure 3.


05/04/07 Rev. A 12 of 37

Figure 3 Zoning Data Domain VTL Using Brocade Switches The Media Server load23 needs to access the Data Domain 560 jp3. load23 is connected to the Brocade switch at port 1 and has a WWPN of 21:00:00:e0:8b:82:36:b3. jp3 is connected to the Brocade switch at port 0 and has a WWPN of 21:00:00:e0:8b:8f:ca:4a. First aliases are created. Then a zone called bue1 is created, which includes the Data Domain Appliance jp3 and Media Server load23. Finally, the zone bue1 is added to the configuration cfg1 and made active. The steps are shown in Figure 4.

brocade3:admin> switchshowswitchName: brocade3switchType: 16.2switchState: OnlineswitchMode: NativeswitchRole: SubordinateswitchDomain: 3switchId: fffc03switchWwn: 10:00:00:60:69:c0:8a:b0switchBeacon: OFFZoning: ON (cfg1)port 0: id N2 Online F-Port 21:00:00:e0:8b:8f:ca:4aport 1: id N2 Online F-Port 21:00:00:e0:8b:82:36:b3port 2: id N2 Online F-Port 21:00:00:e0:8b:8b:8c:76port 3: id N2 No_Lightport 4: id N2 No_Lightport 5: -- N2 No_Moduleport 6: id N2 Online E-Port 10:00:00:60:69:c0:0a:b6 "brocade4" (upstream) (Trunk master)port 7: id N2 Online E-Port (Trunk port, master is port #6)brocade3:admin> brocade3:admin> alicreate "load23","21:00:00:e0:8b:82:36:b3"brocade3:admin> alicreate "jp3","21:00:00:e0:8b:8f:ca:4a"brocade3:admin> zonecreate "bue1","load23;jp3"brocade3:admin> cfgadd "cfg1","bue1"brocade3:admin> cfgenable "cfg1"Starting the Commit operation...cfgEnable successfully completedbrocade3:admin>

Devices are connected

Create aliases

Create zones

Add zone to configuration andmake active

Figure 4 Commands to adding a Data Domain Appliance to a Brocade Zone


05/04/07 Rev. A 13 of 37

4. Configure Host Bus Adapters Install Fibre Channel HBAs in the restorer and in the backup server that is to access the restorer.

• In the restorer, use only an HBA supplied by Data Domain. • In the restorer, the HBA must be in slot 3 of the PCI card array.

See the Data Domain Support web site, Compatibility Matrices, Backup Software compatibility using VTL entry (https://support.datadomain.com/compat_matrix.php) for supported HBA, SAN switch, and backup server combinations. GUIDELINE: Data Domain highly recommends configuring the host operating system driver

for LUN persistent binding. Doing so avoids situations where because of target changes, backup software or the operating system needs to be reconfigured.

GUIDELINE: Install the HBA management software on the host. Follow the HBA vendor

recommendations before installing. The HBA management software simplifies troubleshooting and common configuration tasks such as persistent binding.

NOTE: An HBA on the backup server dedicated for use with the VTL option is required.

Please contact Data Domain if you need to share the same HBA with physical tape or storage.

4.1. Configuring Solaris HBAs Currently, Data Domain supports two HBA vendors, Emulex and QLogic. The instructions below are brief and may not be up to date. Refer to the online Emulex or QLogic installation and configuration instructions for further details.

4.1.1. Emulex LP Series HBA Download Emulex drivers from:

http://www.emulex.com/ts/downloads/solpci/sol.html Uncompress or untar the driver and use the pkgadd utility to install the driver. Once the driver is installed and the VTL devices are discovered and the VTL devices are discovered, Data Domain highly recommends configuring the driver for persistent binding. NOTE: Some HBA configuration files do not permit the automatic recognition of new SAN

devices (auto mapping) unless the host is rebooted. Consult the HBA configuration documentation to determine if a reboot is necessary. Setting an appropriate parameter in the HBA configuration file to prevent reboots in the future may be possible.

4.1.2. QLogic SANBlade Series HBA You can download QLogic driver packages from:

ftp://download.qlogic.com/drivers/


05/04/07 Rev. A 14 of 37

To set up a QLogic HBA: 1. Log into the Solaris system as root. 2. Download the QLogic driver package. 3. Run the following two commands:

> uncompress qla2300.sparc_pkg.Z > pkgadd -d qla2300.sparc_pkg

4. Follow the QLogic instructions to finish the driver installation and configuration.

4.1.3. Troubleshooting for Solaris 8, 9 The commands in this section are for troubleshooting connectivity problems between a restorer and a Solaris server when the server is using a QLogic HBA. For both the restorer and the media server, the commands display the world-wide-node name (WWNN), world-wide-port name (WWPN), and switch port ID used by the HBAs. On the restorer, enter the san show summary command. The first two information lines show the restorer WWNN, WWPN, and the port ID of the port on the switch used by the HBA. For example, the following output is from a DD400 series restorer connecting through a Fibre Channel switch. The Target section gives WWNN, WWPN, and port ID for the media server. f the Port State is Online and the Nexus is active, connectivity is established and no further action should be necessary. # san show summary Target Mode Ports HBA 0: WWNN 20:00:00:e0:8b:8f:ca:4a WWPN 21:00:00:e0:8b:8f:ca:4a Port ID: 0x031000 Port State: Link Up - 2Gb/s F_Port Node 0: WWNN 20:00:00:e0:8b:82:36:b3 WWPN 21:00:00:e0:8b:82:36:b3 Port ID: 0x031100 Roles: FCP Initiator Port State: Online Name: Default Nexus : Active The following example from a DD460g gateway restorer that is direct connected includes the number of LUNs found by the gateway: # san show summary Initiator Mode Ports HBA0@02:03.0: WWNN 20:00:00:e0:8b:1b:c0:6f WWPN 21:00:00:e0:8b:1b:c0:6f Port ID: 0x0000e8 Port State: 2Gbit NL-port Target 0: WWNN 50:06:01:60:b0:21:40:ee WWPN 50:06:01:61:30:21:40:ee Port ID: 0x000000 Role: None Device @ Target 0 1 Discovered Luns


05/04/07 Rev. A 15 of 37

On the Solaris media server, enter the following command: > grep -i qla /var/adm/messages | more The output displays the media server WWNN, WWPN, and port ID, and the restorer WWNN, WWPN, and port ID. In the example below, the names and port IDs for both the restorer and media server match those of the first san show summary display above. • The lines that include hba0-adapter refer to the media server. If a media server has two HBA

cards, entries for the second card show hba1. • The lines that include hba-SCSI-target-id refer to the restorer. If a media server has two HBA

cards, restorers communicating with the second card show hba1. • The hba0-SCSI-target-id node name, port name, and port ID should match the output from the san show summary command on the restorer. See the first san show summary example on the previous page.

The following relevant lines are taken from a longer display: # grep -i qla /var/adm/messages | more . . Dec 16 16:41:55 media3 qla2300: [ID 568177 kern.info] hba0-adapter-node-name="200000e07b1e6cd7"; Dec 16 16:41:55 media3 qla2300: [ID 562076 kern.info] hba0-adapter-port-name="210000e07b1e6cd7"; Dec 16 16:41:55 media3 qla2300: [ID 720712 kern.info] hba0-adapter-port-id="0000ef"; Dec 16 16:41:55 media3 qla2300: [ID 564312 kern.info] hba0-SCSI-target-id-1-fibre-channel-node-name="200000e07b813c8e"; Dec 16 16:41:55 media3 qla2300: [ID 558211 kern.info] hba0-SCSI-target-id-1-fibre-channel-port-name="210000e07b813c8e"; Dec 16 16:41:55 media3 qla2300: [ID 868424 kern.info] hba0-SCSI-target-id-1-port-id="0000e8";

4.2. Configuring Windows HBAs Data Domain has tested the VTL feature with various HBA cards and drivers. For current support, please refer to the Compatibility Matrices, Backup Software compatibility using VTL entry (https://support.datadomain.com/compat_matrix.php). The following sections provide brief instructions on setting up HBAs in a Windows environment. Refer to the online Emulex or QLogic Microsoft Windows installation and configuration instructions for further detail. NOTE: Be sure that the HBA driver in a Windows 2000 backup server is an up-to-date driver

from the HBA vendor. A driver supplied with the Windows 2000 operating system may be out-of-date and can cause problems. Also, be sure that current service packs and “hot fixes” are installed as recommended by the HBA vendor.


05/04/07 Rev. A 16 of 37

4.2.1. QLogic SANBlade Series HBA Commonly used cards are the QLA2340 or QLA2342. Download and install the appropriate driver from the QLogic website (http://www.qlogic.com). Normally the installation entails launching the appropriate setup.exe file. The following drivers work with no specific set up needs for a restorer: • For Windows 2000 and 2003 servers, use the SCSI Miniport driver version. NOTE: Currently, Windows 2003 has issues with the STORport driver, so the Miniport driver

is recommended. Similarly, with Windows 2000, Data Domain does not recommend the full port driver. In general, always use the Miniport driver.

1. Download the driver

2. Update the driver if necessary

Yes


05/04/07 Rev. A 17 of 37

3. Install the QLogic SANSurfer HBA management software. Note: Usually, a recommended match exists for the SANSurfer application and the driver version. Newer drivers generally have newer features that the management software uses.

4. Use SANSurfer to configure persistent binding


05/04/07 Rev. A 18 of 37

4.3. RHES 3.0 Server With Emulex HBA Card The RHES 3.0 server with Emulex HBA card requires specific configuration steps.

System Details:

load34 - 2.4.21-4.ELsmp Emulex Driver - LP10000 Driver kit: lpfc_2.4_driver_kit-7.3.6-2 - (http://www.emulex.com/ts/downloads/linuxfc/rel/736/lpfc_2.4_driver_kit- 7.3.6-2.tar.gz)

NOTE: The Emulex driver installation builds a new kernel by adding the Emulex module. You must use the new kernel after the reboot. The Linux server uses lilo to setup the boot order with the correct kernel. After every kernel change, you must add the proper entries in /etc/lilo.conf and then run lilo.

Safety Tips:

1. Make sure that you have a copy of /boot/initrd-2.4.21-4.ELsmp.img and

that you use /boot/vmlinuz-2.4.21-4.ELsmp as your convenient name.

For example, add the following entries to /etc/lilo.conf: cp /boot/initrd-2.4.21-4.ELsmp.img /boot/initrd-2.4.21-4.ELsmpcopy.img cp /boot/vmlinuz-2.4.21-4.ELsmp /boot/vmlinuz-2.4.21-4.ELsmpcopy

Make sure a backup copy exits in case of corruption in the kernel image. Add the following entries in /etc/lilo.conf* to get an extra linuxcopy entry at the next reboot:

image=/boot/vmlinuz-2.4.21-4.ELsmpcopy label=linuxcopy initrd=/boot/initrd-2.4.21-4.ELsmpcopy.img read-only append="root=LABEL=/"

2. Install the Emulex driver using their install script, lpfs-install.

At the end of the driver install script, the script creates a kernel with a word "elx" appended to the original kernel name. For example:

Original kernel: initrd-2.4.21-4.ELsmp.img Kernel with Emulex driver: initrd-2.4.21-4.ELsmp.img.elx


05/04/07 Rev. A 19 of 37

3. Edit /etc/lilo.conf with the new kernel. *Original /etc/lilo.conf entries:* image=/boot/vmlinuz-2.4.21-4.ELsmp label=linux initrd=/boot/initrd-2.4.21-4.ELsmp.img read-only append="root=LABEL=/"

*New /etc/lilo.conf entries:* image=/boot/vmlinuz-2.4.21-4.ELsmp label=linux initrd=/boot/initrd-2.4.21-4.ELsmp.img.elx read-only append="root=LABEL=/"

4. Run lilo -v.

5. Reboot the system. Now everything should work fine.

Uninstall the driver

1. Use the same lpfc-install script as follows:

lpfc-install --uninstall 2. At the end of the script, the script creates a kernel without driver with the same name as

/boot/initrd-2.4.21-4.ELsmp.img.elx. The script does not put back the original kernel name initrd-2.4.21-4.ELsmp.img. Just run the lilo (no change in /etc/lilo.conf as it already has initrd-2.4.21-4.ELsmp.img.elx ).

3. Reboot the system.

4.4. Configuring HP-UX HBAs Data Domain has tested the VTL feature with various HP HBA cards and drivers, including the A6826A, A5158A, and A6795A HBAs. For current support, please refer to the Compatibility Matrices, Backup Software compatibility using VTL entry (https://support.datadomain.com/compat_matrix.php). The following sections provide brief instructions on setting up HBAs in an HP-UX environment. Refer to the online HP support/compatibility, installation, and configuration information for further detail regarding your implementation. HP-UX environments normally include the HBA driver and firmware as part of the operating system. The steps to install an HP HBA are as follows: • Identify the necessary drivers / firmware and update if necessary • Physically install the HBA


05/04/07 Rev. A 20 of 37

To determine the current version of HBA firmware and drivers installed use the fcmsutil command. alexa:</># ioscan -fnC fcClass I H/W Path Driver S/W State H/W Type Description=================================================================fc 1 0/4/1/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter

/dev/td1

alexa:</># fcmsutil /dev/td1Vendor ID is = 0x00103cDevice ID is = 0x001029

XL2 Chip Revision No is = 2.3PCI Sub-system Vendor ID is = 0x00103c

PCI Sub-system ID is = 0x00128cTopology = PTTOPT_FABRIC

Link Speed = 2GbLocal N_Port_id is = 0x010400

N_Port Node World Wide Name = 0x50060b00001348c7N_Port Port World Wide Name = 0x50060b00001348c6

Driver state = ONLINEHardware Path is = 0/4/1/0

Number of Assisted IOs = 1059203Number of Active Login Sessions = 0

Dino Present on Card = NOMaximum Frame Size = 2048

Driver Version = @(#) libtd.a HP Fibre Channel Tachyon TL/TS/XL2 Driver B.11.11.12 (AR1204) /ux/kern/kisu/TL/src/common/wsio/td_glue.c: Oct 11 2004, 14:45:41

Drive

r

HBA

4.4.1. Troubleshooting for HP-UX 11.11 The commands in this section are for troubleshooting connectivity problems between a restorer and an HP-UX server. The san show summary command displays the world-wide-node name (WWNN), world-wide-port name (WWPN), and switch port ID for the restorer and the server. The vtl initiator show command displays the WWPN. On the restorer, enter the vtl initiator show command. The output shows the initiator (host HBA) WWPN and whether the initiator is online. Note that for HP-UX the initiator is identified as online while I/O is active and offline when I/O is inactive. If the initiator is not defined, then the initiator name is not present in the command output: sysadmin@dd410-2# vtl initiator show Initiator WWPN Status --------- ----------------------- ------- 50:06:0b:00:00:38:95:e8 Offline --------- ----------------------- ------- For example, the following output is for an HP A6795A HBA connecting through a Fibre Channel switch. The DD OS san summary show command identifies initiator information as well as the restorer information. The Target section gives WWNN, WWPN, and port ID for the media server. If the WWPN of the HBA is present in the output of san summary show and vtl initiator show, it indicates that the Restorer was able to communicate with the initiator.


05/04/07 Rev. A 21 of 37

sysadmin@dd410-2# vtl initiator showInitiator WWPN Status--------- ----------------------- ------alexa 50:06:0b:00:00:13:48:c6 Online--------- ----------------------- ------

sysadmin@dd410-2# san show summaryInitiator Mode PortsTarget Mode PortsHBA 0: WWNN 20:00:00:e0:8b:82:9c:da WWPN 21:00:00:e0:8b:82:9c:da

Port ID: 0x010000 Port State: Link Up - 2Gb/s F_PortNode 0: WWNN 50:06:0b:00:00:13:48:c7 WWPN 50:06:0b:00:00:13:48:c6

Port ID: 0x010400 Roles: unknown Port State: OnlineName: alexa Nexus : Inactive

Initiator alexa defined and online

Initiator alexa

To verify that the HBA is installed, issue the command ioscan –fnC fc on the HP-UX host. If the S/W state is CLAIMED, then the HBA is installed and functioning. An S/W state of NO_HW or no entry for the HBA indicates the HBA installation is not successful. alexa:</># ioscan -fnC fcClass I H/W Path Driver S/W State H/W Type Description=================================================================fc 1 0/4/1/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter

/dev/td1

Claimed

5. VTL Device OS Discovery and Configuration For a listing of specific backup software releases supported with the restorer VTL feature, see the Data Domain Support web site, Compatibility Matrices, Backup Software compatibility using VTL entry (https://support.datadomain.com/compat_matrix.php).


05/04/07 Rev. A 22 of 37

The procedures that allow backup software to recognize restorer devices vary for different network configurations. For a restorer: • Direct attached or SAN attached to a Solaris backup server, see the Direct attached or SAN

attached to an HP-UX system, see Using the Restorer With HP-UX Servers section on page 35.

Solaris 8 and Solaris 9 Backup Servers section below. • Direct attached or SAN attached to a Windows backup server, see the Windows Backup

Servers section on page 24. • Direct attached or SAN attached to a RedHat Linux backup server, see the RedHat Backup

Servers section on page 25. • Direct attached or SAN attached to an EMC Celerra system, see the Using the Restorer VTL

with EMC Celerra section on page 28. • Direct attached or SAN attached to a Network Appliance system, see Using the Restorer VTL

with Network Appliance section on page 28. • Direct attached or SAN attached to an HP-UX system, see Using the Restorer With HP-UX

Servers section on page 35.

5.1. Solaris 8 and Solaris 9 Backup Servers When setting up a Solaris backup server, note the following: • Each restorer device (virtual tape drive or media changer) is seen by Solaris as an individual

LUN, not as a target. • A restorer is seen as a target, such as target=0. Each virtual device from the restorer is part of

the same target. • Each restorer can include up to 48 LUNs (devices) that would be available to a backup server..

However, a restorer has a maximum of 48 devices for all media managers that access the restorer.

• All devices defined for a single restorer appear on a single target and start with LUN0 (LUN zero).

Take the following actions before configuring backup software or otherwise trying to access a restorer as a tape device: 1. Attach fiber cabling to the HBAs in the restorer and in the Solaris system so that the systems

can communicate. Check the link light at each HBA to check that the cables are properly connected and the HBA is online.

2. On the Solaris system, use an editor to open the file /kernel/drv/st.conf. 3. In the file, find the tape-config-list line. The line is usually commented out. 4. Uncomment the tape-config-list line. Do not just copy the line and uncomment the

copy, as NetBackup looks only at the first instance of the line.


05/04/07 Rev. A 23 of 37

5. Add a line for the IBM ULTRIUM. The uncommented line and the new line should look as follows. In the second line, the spacing is important. Use a tab between each of the three entries:

tape-config-list= "IBM ULTRIUM-TD1", "IBM Ultrium-1", "LTO-1";

6. On the Solaris system (except for Solaris 8), run the following commands to read the

changed configuration files. On Solaris 8 systems, reboot with the command reboot -- -r.

> update_drv st > devfsadm -C > devfsadm -c 'scsi'

7. On the restorer, enter the following commands:

# vtl disable # vtl enable

8. To check that the Solaris system has entries for the restorer virtual tape drives, run the following command on the Solaris system. The output should be similar to the following when no other devices are defined in the /dev/rmt file.

# ls -l /dev/rmt lrwxrwxrwx 1 root other 49 Aug 15 14:26 /dev/rmt/0 -> ../../devices/pci@1f,2000/fibre-channel@1/st@0,6: lrwxrwxrwx 1 root other 49 Aug 15 14:26 /dev/rmt/1 -> ../../devices/pci@1f,2000/fibre-channel@1/st@0,7:

9. To check that tape drive status is seen by the Solaris system:

• On the restorer, use the VTL commands to load a virtual tape into a virtual tape drive. For example, load a tape into drive 2.

• On the Solaris system, enter the following commands. The first command in the example

below looks at drive 1 (one) on the restorer and reports back that the drive is empty. The second command looks at drive 2 (/dev/rmt/1 from the example above) and reports that a tape is loaded.

> mt -f /dev/rmt/0 status /dev/rmt/0: no tape loaded or drive offline > mt -f /dev/rmt/1 status IBM Ultrium LTO tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0


05/04/07 Rev. A 24 of 37

5.2. Windows Backup Servers For Windows releases that are supported with the restorer VTL feature, see the Data Domain Support web site, Compatibility Matrices, Backup Software compatibility using VTL entry (https://support.datadomain.com/compat_matrix.php). After configuring VTL on the restorer and connecting the restorer and backup server HBAs, do the following procedures on Windows backup servers. 1. For more complete monitoring of HBAs, install HBA-monitoring software such as

HBAnywhere for Emulex HBAs or SANSurfer for QLogic HBAs. 2. Reboot the Windows system. 3. To check that the Windows server sees all the Data Domain devices, open Device Manager

on the Windows server. Look at Tape Drives for drives and Medium Changers for the medium changer. Note that the Unknown Medium Changer entry is correct. The final display should show a tape drive for each virtual tape drive that you created on the restorer.


05/04/07 Rev. A 25 of 37

4. The HBA management software can also be helpful in verifying that the VTL is visible to the

Windows server. Note that the Robot is assigned LUN 0 and the four tape drives are assigned LUNs 1-4.

5.3. RedHat Backup Servers For RedHat releases that are supported with the restorer VTL feature, see the Data Domain Support web site, Compatibility Matrices, Backup Software compatibility using VTL entry (https://support.datadomain.com/compat_matrix.php). Take the following actions on the RedHat system (with some exceptions as noted) before configuring backup software or otherwise trying to access a restorer as a tape device. Note: If the RedHat kernel on your backup server is not already enabled to handle multiple LUNs, follow the procedure in the section Enable Multiple LUNs in the Kernel on page 27 of this document.

5.3.1. Discover Restorer VTL Devices on RedHat Linux To discover the devices, you can manually alter the modules.conf file on Red Hat Linux backup servers with the 2.4 kernel; however, the rescan-scsi-bus.sh open source script makes the task much easier. This section uses the script in the example. On the backup server: 1. From the web, find the open source script rescan-scsi-bus.sh and put the script on

the backup server under the /etc directory.


05/04/07 Rev. A 26 of 37

2. Create the file /etc/rc.modules. Add the following lines to the file to automatically

load the HBA (assumed to be a QLogic 2300) driver at boot time and to have the system scan for multiple LUNs.

modprobe qla2300 modprobe st /etc/rescan-scsi-bus.sh -l -w -r -c

3. Look at the file /etc/rescan-scsi-bus.sh and check that the variable lunsearch

has at least as many numbers listed as the target restorer has devices (virtual tape drives and media changers). Add LUN numbers to the variable if needed.

4. On the restorer, configure and enable the VTL feature. 5. Attach the RedHat system and the restorer to the network fabric. 6. Reboot the RedHat system. 7. On the RedHat system, enter the following command to display all SCSI devices seen by the

system. All devices from a restorer use the same ID, but each device has a different LUN number.

# cat /proc/scsi/scsi Host: scsi0 Channel: 00 Id: 00 LUN: 00 Vendor: STK Model: L180 Rev: 0306 Type: Medium Changer ANSI SCSI revision: 03 Host: scsi0 Channel: 00 Id: 00 LUN: 01 Vendor: IBM Model: ULTRIUM-TD1 Rev: 27Q1 Type: Sequential-Access ANSI SCSI revision: 03

8. Run the following commands and save the output from the second command.

# cd /proc/scsi/sg # cat device_hdr > devices

9. Check that the output from the cat device_hdr command has as many lines as the target

restorer has devices. Each line represents one restorer device. Type 1 devices are tape drives and type 8 devices are media changers. The output should be similar to:

host chan id lun type opens qdepth busy online 0 0 0 1 1 0 16 0 1 0 0 0 2 1 0 16 0 1 0 0 0 3 1 0 16 0 1 0 0 0 4 1 0 16 0 1 0 0 0 5 8 0 16 0 1 0 0 1 0 8 0 16 0 1 0 0 2 0 1 0 16 0 1 0 0 3 0 1 0 16 0 1


05/04/07 Rev. A 27 of 37

10. Check that the directory /dev has at least as many sgX (where X is a number) character

special device files as the restorer has devices and as many stX and nstX files as the restorer has LUNs. For example, the /dev/sgX files for the output above would be /dev/sg0 through /dev/sg7.

11. Reboot the RedHat system. NOTE: On a restorer, the vtl create command can create a library with up to 9000 slots.

However, the third-party MTX utility cannot report status on a library with 9000 slots. Data Domain has not done testing to find the absolute limit for MTX, but a library with 1024 slots is known to work.

5.3.2. Enable Multiple LUNs in the Kernel With multiple LUNs, the Linux kernel on your backup server must recognize multiple LUNs. By default, most Linux kernels do not recognize multiple LUNs. NOTE: The procedure and commands in this section are general guidelines to reach a specific

end result -- enable multiple LUNs. Because of the fluid nature of Linux releases and patch levels, the procedure and commands may not be appropriate for your Linux system. If the general procedure and commands in this section for making kernel changes are not familiar to you or do not apply to your specific Linux release, please contact your Linux vendor for detailed instructions. Data Domain cannot assume any responsibility for the accuracy and usability of the procedure and commands with a specific Linux release.

1. Obtain and install kernel sources for your Linux release. If needed, contact your Linux

vendor for assistance. 2. On your Linux backup server, go to the directory: /usr/src/linux. 3. Run one of the following commands as appropriate for your system:

> make xconfig > make meunconfig

4. Select Device Drivers. 5. Look at SCSI Device Support for (depending on the Linux release) something similar to

Probe all Luns on each SCSI device or SCSI-multi-LUN. 6. Make sure that the checkbox for SCSI Device Support is checked. 7. Do a standard compile and install of the Linux kernel. If needed, contact your Linux vendor

for assistance.


05/04/07 Rev. A 28 of 37

5.4. Using the Restorer VTL with EMC Celerra For EMC Celerra systems and releases that are supported with the restorer VTL feature, see the Data Domain Support web site, Compatibility Matrices, Backup Software compatibility using VTL entry (https://support.datadomain.com/compat_matrix.php).

5.4.1. Installation and Configuration

1. On the restorer, configure the VTL, create tapes, and load the tapes into the newly created virtual tape library. The example creates a VTL with 4 drives and 128 slots.

2. Log on as user nasadmin and configure the Celerra for NDMP.

[nasadmin@celerra-cs0 nasadmin]$ server_param server_2 -facility NDMP -modify bufsz -value 256

server_2 : done Warning 17716815750: server_2 : You must reboot server_2 for bufsz changes

to take effect. [nasadmin@celerra-cs0 nasadmin]$ server_param server_2 -facility PAX -

modify readWriteBlockSizeInKB -value 128 server_2 : done Warning 17716815750: server_2 : You must reboot server_2 for

readWriteBlockSizeInKB changes to take effect. [nasadmin@celerra-cs0 nasadmin]$ server_cpu server_2 -reboot -monitor now server_2 : reboot in progress 4.0.0.0.0.0.0.0.0.0.3.3.4.done

3. If necessary, configure the Fibre Channel switch. Gather the restorer WWPN and Celerra AUX-0 port WWPN before starting this set of tasks. You can obtain the WWPNs from a variety of sources, such as san show summary (on a restorer). The simplest way to find WWPNs is from the switch, a process that varies by manufacturer. Data Domain suggests connecting the Celerra and the restorer to the switch before configuring the zoning.

4. If necessary configure LUN masking on the restorer.


05/04/07 Rev. A 29 of 37

5. As user nasadmin, check that the restorer is accessible to the Celerra, create the tape devices (TLU) on the Celerra, and confirm that the devices are created on the Celerra.

6. Create the devices.

[nasadmin@celerra-cs0 nasadmin]$ server_devconfig server_2 -create -scsi -nondisks -monitor y

Discovering storage (may take several minutes) server_2 : done

[nasadmin@celerra-cs0 nasadmin]$ server_devconfig server_2 -probe -scsi -nondisks -monitor y

server_2 : SCSI non-disk devices : chain= 0, scsi-0 : no devices on chain chain= 1, scsi-1 : no devices on chain chain= 2, scsi-2 : no devices on chain . . . chain= 31, scsi-31 : no devices on chain chain= 32, scsi-32 stor_id= celerra_id= tid/lun= 0/0 type= jbox info= STK L180 0306 tid/lun= 0/1 type= tape info= IBM ULTRIUM-TD1 4561 tid/lun= 0/2 type= tape info= IBM ULTRIUM-TD1 4561 tid/lun= 0/3 type= tape info= IBM ULTRIUM-TD1 4561 tid/lun= 0/4 type= tape info= IBM ULTRIUM-TD1 4561 . . .

The Restorer Robot & four drives are present


05/04/07 Rev. A 30 of 37

7. List the devices to confirm that they are created.

8. As user root, assign a Celerra data mover user and password.

[nasadmin@celerra-cs0 nasadmin]$ su Password: [root@celerra-cs0 nasadmin]# /nas/sbin/server_user server_2 -add -password

ndmp Creating new user ndmp User ID: 1000 Group ID: 1000 Comment: NDMP User Home directory: /home/ndmp Shell: /bin/bash Changing password for user ndmp New passwd: Retype new passwd:

5.4.2. Tips

• While reference 1 indicates that a reboot is needed to recognize a restorer connected to port AUX0, Data Domain testing found that recognize a restorer can be recognized without performing a reboot.

• If the restorer VTL feature is used by multiple hosts, Data Domain recommends configuring LUN masking on the restorer. LUN masking requires DD OS 4.0.3.3 or later.

• Maintain the Celerra fcTach setting at 0x8000 (default) for both direct and SAN connections. The setting enables the Celerra to auto-negotiate the fibre channel speed.

• EMC provides an extensive list of Tech Notes relating to Celerra operation and administration, NDMP configuration, and configuring backup applications with the Celerra. If possible, obtain an EMC Powerlink account to access the documents. The following screenshot lists useful documents available from Powerlink:

[nasadmin@celerra-cs0 nasadmin]$ server_devconfig server_2 -list -scsi -nondisks -monitor y

server_2 : Scsi Device Table name addr type info gk01 c0t0l0 disk 5 021902000000APM00034901268 jbox1 c32t0l0 jbox STK L180 0306 tape2 c32t0l1 tape IBM ULTRIUM-TD1 4561 tape3 c32t0l2 tape IBM ULTRIUM-TD1 4561 tape4 c32t0l3 tape IBM ULTRIUM-TD1 4561 tape5 c32t0l4 tape IBM ULTRIUM-TD1 4561


05/04/07 Rev. A 31 of 37

• Helpful Celerra commands, with server_2 as the example hostname:

o To see what devices are visible to the Celerra:

server_devconfig server_2 -probe -scsi -all -monitor y

o To see what devices are configured on the Celerra:

server_devconfig server_2 -list -scsi -all -monitor y

o To create the restorer VTL devices on the Celerra:

server_devconfig server_2 -create -scsi -nondisks -monitor y

o To view NDMP related parameters on the Celerra:

server_param server_2 -facility NDMP –list

server_param server_2 -facility PAX –list


05/04/07 Rev. A 32 of 37

o To determine the Celerra OS revision level:

server_version server_2

o To determine a data mover IP address:

server_ifconfig server_2 -all

o To determine what file systems are available for backup/restore:

server_export server_2 -list

5.4.3. Gotchas

• Make sure that a media interface adapter (MIA) is available to convert the copper (HSSDC) connection from the back of the Celerra (port AUX0) to a fiber optic LC connection. Most Fibre Channel switches currently use LC fiber connections.

• The Celerra command line interface is case sensitive.

• Data Domain was not able to add the directive set type = vbb to the NetBackup policy when developing this Tech Note. If the directive is added, the policy fails. Add the directive set type = tar, which is recommended by EMC.

• When is rebooting a Celerra Data Mover necessary:

o Reference Error! Reference source not found. specifies a reboot for the Celerra data mover(s). However, a reboot was not necessary for the configuration (see Error! Reference source not found.) used in the development of this document.

o A data mover reboot is required for changes to take effect after modifying the performance tuning parameters bufsz and readWriteBlockSizeInKB.

• All implementations of NDMP use directory level references and cannot backup and restore a single file or multiple individual files unless the file or files are in a directory that holds no other files. The issue might arise when verifying backup and restore functionality.

5.4.4. Performance Tuning

• Reference Error! Reference source not found. (pages 55 – 56) provides performance tuning guidance. The simple process of updating the tape buffer size and read/write block size on the Celerra is recommended as a starting point. Note that modifying the parameters requires a data mover reboot for the changes to take effect.

o server_param server_2 -facility NDMP -modify bufsz -value 256

o server_param server_2 -facility NDMP -modify readWriteBlockSizeInKB -value 128


05/04/07 Rev. A 33 of 37

5.4.5. Troubleshooting The most common problem is the lack of device discovery on the Celerra. A few troubleshooting options may help determine the cause:

• Are the restorer and Celerra present on the switch? (See output from the commands switchshow and nsshow for Brocade switches.)

• Confirm that LUN masking is configured appropriately. A quick way to confirm LUN masking is to delete LUN masking for the Celerra. Make sure the WWPN (world wide port name) is used.

• Does output from the restorer command san show summary indicate that the nexus is active?

Node 0: WWNN 50:06:01:60:b0:22:e4:5d WWPN 50:06:01:62:30:22:e4:5d Port ID: 0x010000 Roles: unknown Port State: Online

Name: Default Nexus : Active

5.5. Using the Restorer VTL with Network Appliance The following information is for backup configurations that include a Network Appliance system in configurations described as direct attached or SAN attached between the Network Appliance system and the restorer virtual tape devices. The following graphic shows a logical configuration with a NetWorker storage node, Network Appliance filer, and a Data Domain restorer.

5.5.1. Verifying NetApp and VTL Connectivity 1. After verifying that the DDR is connected and online, check that the tape and media changers

are visible to the filer. Use the following two commands:

# sysconfig -t # sysconfig -m

2. From the above output, verify that the filer has the devices discovered and in the right order.

If not, use the storage unalias and storage alias commands on the filer to change the aliases that refer to the restorer VTL devices.

3. Use the Network Appliance storage command for further status of port state, media

changers, and virtual tape drives. 4. Enable NDMP on the filer.

NetApp 1 Storage Node

DDR1


05/04/07 Rev. A 34 of 37

NOTE: In most cases, NetApp uses NDMP with a backup server to perform backups. By

default, NDMP is disabled and must be enabled before backups or restores can be successful. NDMP configuration on the backup server varies by application and is not covered in this document. Please refer to the appropriate backup application tech note.

5.5.2. Troubleshooting Tips A Network Appliance system that implements requests to a restorer may not see the restorer VTL devices after a restorer reboot. To work around this issue, try the following:

• First disable and re-enable the FCP switch port to which the restorer is attached. Run the sysconfig commands on the Network Appliance system to check if the devices are now online.

• If the devices are still not discovered, unplug the VTL port, reboot the restorer. Wait for the VTL processes and file system to be enabled, then re-plugin the restorer. Run the NetApp sysconfig commands to see if the VTL devices are still online.

• As a last resort, reboot the Network Appliance system. NOTE: For a Network Appliance filer to discover virtual devices on a restorer, the restorer

must have at least one library and a LUN0 (LUN zero) must exist in one library. On the restorer, use the vtl lunmask show command to list libraries and LUNs. If no LUN masks exist, all restorer VTL libraries reside in the Default LUN mask group with a media changer assigned to LUN0.

5.5.3. When using a CISCO MDS switch, NetApp Filer, and VTL: When a filer and restorer are connected through a Cisco MDS Fibre Channel switch, any VTL changes on the restorer, such as the creation or deletion of VTLs or LUN masks, are not dynamically updated by the filer. To force the filer to discover changes:

• Run the following commands on the restorer after changes:

# vtl disable Disabling VTL, please wait… VTL is disabled.

Verify that the VTL is disabled: # vtl status VTL admin_stat: disabled

Enable VTL: # vtl enable Starting VTL, please wait…


05/04/07 Rev. A 35 of 37

VTL is enabled. Verify that VTL is enabled:

# vtl status VTL admin_stat: enabled, process_state: running

• In some cases, the switch port where the restorer is attached may need to be disabled and

enabled. NOTE: For Network Appliance systems and releases that are supported with the restorer VTL

feature, see the Data Domain Support web site, Compatibility Matrices, Backup Software compatibility using VTL entry (https://support.datadomain.com /compat_matrix.php).

5.6. Using the Restorer With HP-UX Servers When setting up an HP-UX backup server, note the following: • Each restorer virtual device (virtual tape drive or media changer) is seen by HP-UX as an

individual LUN, not as a target. • A restorer is seen as a target, such as target=0. Each virtual device from the restorer is part of

the same target. • Each restorer can include up to 48 LUNs (devices) that would be available to a backup server..

However, a restorer has a maximum of 48 devices for all media managers that access the restorer.

• All devices defined for a single restorer appear on a single target and start with LUN0 (LUN zero). LUN numbers are configurable by using the command vtl lunmask add ….

• The LUN limit of HP-UX is 8 for a single target, which allows for the configuration per HP-UX host of up to 1 robot & 7 drives per restorer or combination of changers and drives totaling 8 virtual devices.

• Normally the backup and restore application requires use of the IBM supplied driver for LTO drives (atdd). Check with the backup and restore application to determine the necessary tape drivers to load and load them at this time.

• For VTL access by HP-UX hosts Data Domain recommends LUN 0 for the changer. Use the command vtl lunmask … to manipulate VTL device LUN numbers.


05/04/07 Rev. A 36 of 37

Take the following actions before configuring backup software or otherwise trying to access a restorer as a tape device: 1. Attach fiber cabling to the HBAs in the restorer and in the HP-UX system so that the systems

can communicate. Check the link light at each HBA to check that the cables are properly connected and the HBA is online. If the VTL is not configured do so now (see Detailed VTL Setup Example on page 9). Note that the virtual tapes (see tape) and changer (see autoch) are present. In some cases the changer is controlled by a different host and is not present.

alexa:</># ioscan -fn | egrep -w "tape|autoch" autoch 4 0/4/1/0.1.0.255.0.0.0 schgr CLAIMED DEVICE STK L180 tape 21 0/4/1/0.1.0.255.0.0.1 atdd CLAIMED DEVICE IBM ULTRIUM-TD1 tape 22 0/4/1/0.1.0.255.0.0.2 atdd CLAIMED DEVICE IBM ULTRIUM-TD1 tape 23 0/4/1/0.1.0.255.0.0.3 atdd CLAIMED DEVICE IBM ULTRIUM-TD1 tape 24 0/4/1/0.1.0.255.0.0.4 atdd CLAIMED DEVICE IBM ULTRIUM-TD1 2. Create the special files for the tape devices using the command insf. Note that the output

is truncated and shows just tape devices and the changer: alexa:</># insf -e insf: Installing special files for schgr instance 5 address 0/3/1/0.1.4.255.0.0.0 insf: Installing special files for stape instance 28 address 0/3/1/0.1.4.255.0.0.1 insf: Installing special files for stape instance 29 address 0/3/1/0.1.4.255.0.0.2 insf: Installing special files for stape instance 30 address 0/3/1/0.1.4.255.0.0.3 insf: Installing special files for stape instance 31 address 0/3/1/0.1.4.255.0.0.4 3. To check that the tape drive is accessible by the HP-UX system:

• On the restorer, use the VTL commands to load a virtual tape into a virtual tape drive. For example, load a tape into drive 2.

sysadmin@dd410-2# vtl tape insert vtl1 drive 2 barcode AAA000L1


05/04/07 Rev. A 37 of 37

• On the HP-UX system, enter the following commands. The first command in the example below looks at drive 1 (one) on the restorer and reports back that the drive is empty. The second command looks at drive 2 (/dev/rmt/29m from the example above) and reports that a tape is loaded and online. To determine what device (i.e. /dev/rmt) maps to which LUN / VTL device, reference the output form the command ioscan –fnC tape.

alexa:</># mt -f /dev/rmt/28m status Drive: IBM ULTRIUM-TD1 Format: Status: [0] File: 0 Block: 0 alexa:</># mt -f /dev/rmt/29m status Drive: IBM ULTRIUM-TD1 Format: Status: [41114018] BOT online compression immediate-report-modeFile: 0 Block: 0

No tape loaded

Tape loaded

alexa:</># ioscan -fnC tape Class I H/W Path Driver S/W State H/W Type Description ======================================================================== tape 28 0/3/1/0.1.4.255.0.0.1 stape CLAIMED DEVICE IBM ULTRIUM-TD1 /dev/rmt/28m /dev/rmt/28mnb /dev/rmt/c9t0d1BESTn /dev/rmt/28mb /dev/rmt/c9t0d1BEST /dev/rmt/c9t0d1BESTnb /dev/rmt/28mn /dev/rmt/c9t0d1BESTb tape 29 0/3/1/0.1.4.255.0.0.2 stape CLAIMED DEVICE IBM ULTRIUM-TD1 /dev/rmt/29m /dev/rmt/29mnb /dev/rmt/c9t0d2BESTn /dev/rmt/29mb /dev/rmt/c9t0d2BEST /dev/rmt/c9t0d2BESTnb /dev/rmt/29mn /dev/rmt/c9t0d2BESTb tape 30 0/3/1/0.1.4.255.0.0.3 stape CLAIMED DEVICE IBM ULTRIUM-TD1 /dev/rmt/30m /dev/rmt/30mnb /dev/rmt/c9t0d3BESTn /dev/rmt/30mb /dev/rmt/c9t0d3BEST /dev/rmt/c9t0d3BESTnb /dev/rmt/30mn /dev/rmt/c9t0d3BESTb tape 31 0/3/1/0.1.4.255.0.0.4 stape CLAIMED DEVICE IBM ULTRIUM-TD1 /dev/rmt/31m /dev/rmt/31mnb /dev/rmt/c9t0d4BESTn /dev/rmt/31mb /dev/rmt/c9t0d4BEST /dev/rmt/c9t0d4BESTnb /dev/rmt/31mn /dev/rmt/c9t0d4BESTb

data domain vtl

Documents

elsmp labellinux

rootlabel

fnc fc class

installing

attach fiber

cisco mds

card show

virtual tape