Fiber Chanel

7/27/2019 Fiber Chanel

1/36

HP Enterprise Backup Solution design guide

AbstractThis guide describes how to use the HP Enterprise Backup Solution (EBS) to design a data protection solution.

HP Part Number: 5697-7309Published: June 2012Edition: Eleventh


2/36

Copyright 2012 Hewlett Packard.

Confidential computer software. Valid l icense from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial

Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under

vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express

warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall

not be liable for technical or editorial errors or omissions contained herein.


3/36

Contents

1 Overview..................................................................................................5Supported components..............................................................................................................6Supported topologies................................................................................................................6

Direct-attach parallel SCSI.....................................................................................................6Serial-attach SCSI (SAS)........................................................................................................6Point-to -point.......................................................................................................................6Switched fabric....................................................................................................................6

Platform and operating system support........................................................................................6Use of native backup programs and commands............................................................................7

2 Zoning......................................................................................................8Zone recommendations.............................................................................................................8

3 Configuration and operating system details....................................................9Nearline configuration information..............................................................................................9SAN utilities that may disrupt Nearline connectivity.......................................................................9HP-UX...................................................................................................................................10

Initial requirement (HP-UX 11.23 on IA-64 and PA-RISC)...........................................................10Initial requirement (HP-UX 11.31 on IA-64 and PA-RISC)...........................................................11HP-UX 11.31 can experience poor I/O performance on VxFS file systems due to memory blockingduring high system memory usage.......................................................................................12

Poor I/O performance resolution.....................................................................................12HP-UX 11.23: Disabling rewind-on-close devices with st_san_safe.........................................13Configuring the SAN.....................................................................................................13

Final host configurations ...........................................................................................13Installation checklist..................................................................................................14

Windows Server and Windows Storage Server..........................................................................14Configuring the SAN..........................................................................................................15

Installing the HBA device driver (Windows Server 2008/2003)..........................................15Storport considerations..................................................................................................15Installation checklist.......................................................................................................15

Windows 2003 known issues..............................................................................................15Target and LUN shifting.................................................................................................15Interop issues with Microsoft Windows persistent binding for tape LUNs...............................16Tape drive polling.........................................................................................................16Library slot count/Max Scatter Gather List issue................................................................17Tape.sys block size issue................................................................................................17Emulex SCSIport driver issue...........................................................................................17FC interface controller device driver issue.........................................................................18Not Enough Server Storage is Available to Process this Commandnetwork issue.................18

Updating the HP Insight Management Agents for Microsoft Windows using the ProLiant SupportPack Version 7.70 (or later).............................................................................................18

NAS and ProLiant Storage Server devices using Microsoft Windows Storage Server 2003...........19Known issues with NAS and ProLiant Storage Servers........................................................19

Tru64 UNIX...........................................................................................................................19Backup software patch.......................................................................................................20Configuring the SAN..........................................................................................................20Confirming mapped components.........................................................................................21Installed and configured host bus adapters............................................................................21

Visible target devices..........................................................................................................21Configuring switch zoning...................................................................................................21

Installation checklist............................................................................................................21

Contents 3


4/36

Red Hat and SUSE Linux..........................................................................................................22Operating system notes......................................................................................................22Installing HBA drivers and tools...........................................................................................22

Additional SG device files...................................................................................................23Installation checklist............................................................................................................23Linux known issues.............................................................................................................24

Rewind commands being issued by rebooted Linux hosts....................................................24Tape devices not discovered and configured across server reboots.......................................24

Sparse files causing long backup times with some backup applications................................25LUNs shifting after reboot...............................................................................................25Oracle Solaris........................................................................................................................25

Configuring the SAN..........................................................................................................25Oracle Solaris native driver configuration..............................................................................26Troubleshooting with the cfgadm utility.................................................................................27QLogic driver configuration for QLA2340 and QLA2342........................................................27Emulex driver configuration for LP10000 and LP10000DC......................................................28Configuring Oracle Servers for tape devices on SAN..............................................................30Configuring switch zoning...................................................................................................31Installation checklist............................................................................................................31

IBM AIX................................................................................................................................32Configuring the SAN..........................................................................................................32IBM 6228, 6239, 5716, or 5759 HBA configuration...............................................................32Configuring switch zoning...................................................................................................34Installation checklist............................................................................................................34Installing backup software and patches.................................................................................34

4 Backup and recovery of Virtual Machines ...................................................35HP EBS VMware backup and recovery strategy..........................................................................35HP Integrity Virtual Machines (Integrity VM)...............................................................................36HP EBS Hyper-V backup and recovery strategy...........................................................................36

4 Contents


5/36

1 OverviewThe HP Enterprise Backup Solution (EBS) is an integration of data protection and archiving softwareand industry-standard hardware, providing a complete enterprise class solution. HP has joinedwith leading software companies to provide software solutions that support the backup and restoreprocesses of homogeneous and heterogeneous operating systems in a shared storage environment.

EBS software partners data protection solutions incorporate database protection, storagemanagement agents, and options for highly specialized networking environments.

Data protection and archiving software focuses on using an automated LTO Ultrium tape libraryand/or Virtual Tape and/or NAS backup technologies.. The EBS combines the functionality andmanagement of Storage Area Network (SAN), data protection software, and scaling tools tointegrate tape and disk storage subsystems in the same SAN environment. Enterprise data protectioncan be accomplished with different target devices in various configurations, using a variety oftransport methods such as the corporate communication network, a server SCSI/SAS, SCSI, FCoE(Fibre Channel over Ethernet), or a Fibre Channel infrastructure. EBS typically uses a storage areanetwork that provides dedicated bandwidth independent of the local area network (LAN). Thisindependence allows single or multiple backup or restore jobs to run without the network trafficcaused by data protection environments. Depending on the data protection/archiving software

used, submitted jobs are run locally on the backup server to which the job was submitted. Data,however, is sent over the SAN backup/archive target to the tape library rather than over the LAN.This achieves greater speed and reduces network traffic. Jobs and devices can be managed andviewed from either the primary or any server or client connected within the EBS which has thesupported data protection software solution installed. All servers within the EBS server group candisplay the same devices.

Data protection and archiving software focuses on using an automated LTO Ultrium tape libraryand/or Virtual Tape and/or NAS backup technologies. The EBS combines the functionality andmanagement of Storage Area Network (SAN), data protection software, and scaling tools tointegrate tape and disk storage subsystems in the same SAN environment.

Enterprise data protection can be accomplished with different target devices in variousconfigurations, using a variety of transport methods such as the corporate communication network,a server SCSI/SAS, SCSI, FCoE (Fibre Channel over Ethernet), or a Fibre Channel infrastructure.EBS typically uses a storage area network that provides dedicated bandwidth independent of thelocal area network (LAN). This independence allows single or multiple backup or restore jobs torun without the network traffic caused by data protection environments.

Depending on the data protection/archiving software used, submitted jobs are run locally on thebackup server to which the job was submitted. Data, however, is sent over the SAN backup/archivetarget to the tape library rather than over the LAN. This achieves greater speed and reduces networktraffic. Jobs and devices can be managed and viewed from either the primary or any server orclient connected within the EBS which has the supported data protection software solution installed.

All servers within the EBS server group can display the same devices.

To implement an Enterprise Backup Solution:1. Consult the HP Enterprise Backup Solutions Compatibility Matrix available at: http://

www.hp.com/go/ebs.2. Consult the EBS design guide for EBS hardware configurations currently supported and how

to efficiently provide shared tape library backup in a heterogeneous SAN environment.3. Install and configure the backup application or backup software. Recommendations for

individual backup applications and software may be found in separate implementation guides.For more information about EBS, go to http://www.hp.com/go/ebs.

5
http://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebs


6/36


7/36

Use of native backup programs and commandsA limited number of backup programs and commands that are native to a particular operatingsystem are verified for basic functionality with SCSI direct-attached tape drives and autoloadersonly. Tape libraries and virtual library systems are not tested. These programs and commands arelimited in their ability to handle complicated backups and restores in multi-host, storage areanetworks (SANs). They are not guaranteed to provide robust error handling or performancethroughput. Use of these programs and/or commands in a user developed script is not recommendedfor use with tape libraries in an Enterprise Backup Solution shared storage environment. Refer tothe HP Enterprise Backup Solutions Compatibility Matrixat http://www.hp.com/go/ebs for a listof tested and supported applications that are specifically designed for backup and restoreoperations.

The following table shows the native utilities tested on each operating system (OS):

Table 1 Supported native utilities

WindowsLinuxHP-UXUtilities Supported

Tape drive commands

NoYesYesTar

NoYesYesDD (dump)NoYesYesPax

NoYesYesMt

NoNoYesMake tape recovery (BFT) *

YesNoNoNT backup

Library and autochanger commands

NoNoYesMc

NoYesNoMtx

YesNoNoRSM1

1 * Make Tape Recovery - refer to Ignite-UX Administration Guide for HP-UX 11i for details of platform requirements and

interface type support

Use of native backup programs and commands 7
http://www.hp.com/go/ebshttp://www.hp.com/go/ebs


8/36

2 Zoning

Zone recommendationsDue to complexities in multi-hosting tape devices on SANs, it is best to make use of zoning toolsto help keep the backup/restore environment simple and less susceptible to the effects of changingor problematic SANs. Zoning provides a way for servers, disk arrays, and tape controllers to only

see what hosts and targets they need to see and use. The benefits of zoning include but are notlimited to:

The potential to greatly reduce target and LUN shifting

Reducing stress on backup devices by polling agents

Reducing the time it takes to debug and resolve anomalies in the backup/restore environment

Reducing the potential for conflict with untested third-party products

Zoning may not always be required for configurations that are already small or simple. Typicallythe bigger the SAN is, the more zoning is needed. HP recommends the following for determininghow and when to use zoning.

Use host-centric zoning. Host-centric zoning is implemented by creating a specific zone foreach server or host by World Wide Port Name, and adding only those storage elements tobe utilized by that host. Host-centric zoning prevents a server from detecting any other deviceson the SAN or including other servers, and it simplifies the device discovery process.

Disk and tape on the same HBAs is supported. For larger SAN environments, it is recommendedto also add storage-centric zones for disk and backup targets. This type of zoning is done byadding overlapping zones with disk and backup targets separated. See example below.

Figure 1 Zoning disk and tape

NOTE: Overlapping zones are supported.

NOTE: For HP StoreOnce Backup Systems zoning by World Wide Port Names is recommended,not Port ID's or Ports.

8 Zoning


9/36

3 Configuration and operating system details

Nearline configuration informationThe Enterprise Backup Solution (EBS) supports several operating systems (OSs). This section providesan overview for configuring the EBS using the following OSs:

HP-UX

Microsoft Windows

NAS or ProLiant Storage Server devices using Microsoft Windows Storage Server 2003 and2008

Linux

Oracle Solaris

IBM AIX

SAN utilities that may disrupt Nearline connectivitySome software products commonly found in SAN environments can interfere with the normal

functioning of backup and restore operations. These applications include system managementagents and monitoring software and a wide range of tape drive and system configuration utilities.

A list of known applications and the operating systems on which they are found is shown below.This list is not intended to be an exhaustive list.

Windows (all versions)

RSM polling (This must always be disabled for tape and library devices).

Qlogic QConvergeConsole (QCC)/SAN Surfer

Emulex OneCommandManager (OCM)/HBAnywhere (HBA configuration utilities)

Brocade Host Connectivity Manager (HCM) (HBA configuration utility)

HP System Insight Manager (management agents)

HP Library & Tape Tools (tape utilities):

mt commands (Linux/Unix)

mtx commands (Linux)

Oracle Explorer (Solaris)

EMS tape polling (HP-UX)

Emulex and Brocade tools

mtx and HP-UX media changer applet

When run concurrently with backup or restore operations, these applications, utilities, and commandshave been shown to interfere with components in the data path.

Some specific recommendations are:

SCSI Reserve & ReleaseIf your backup application supports the use of SCSI reserve andrelease, enable and use it. Reserve and release can prevent unwanted applications orcommands from taking control of a device.

SAN ZoningEBS recommends host-based SAN switch zoning by WWPN. When zoning isemployed, these applications are much less likely to interfere with tape device operation.

Nearline configuration information 9


10/36

HP-UXThe configuration process for HP-UX involves:

Upgrading essential EBS hardware components to meet the minimum firmware and devicedriver requirements.

NOTE: See the HP Enterprise Backup Solutions Compatibility Matrix for all current andrequired hardware, software, firmware, and device driver versions, including Hardware

Enablement Kits and Quality Packs on the HP website: http://www.hp.com/go/ebs. Installing the minimum patch level support. Go to the following website to obtain the necessary

patches:

http://www.hp.com/support

NOTE: See the installation checklist at the end of this section to ensure all of the hardwareand software is correctly installed and configured in the SAN.

Initial requirement (HP-UX 11.23 on IA-64 and PA-RISC)HP currently supports HP-UX 11.23 in an EBS environment using an HP AB465A, A9782A,

A9784A, A5158A, A6795A, A6826A, AB378A/AB378B, AB379A/AB379B, AD193A,AD194A, AD300A, AD299A, AD355A, or QMH2462 FC HBA. Contact HP or your HP resellerfor information on how to acquire these cards.

The following OS software bundles contain the drivers for the A5158A and A6795A adapters:

FibrChanl-00 B.11.23.0803 HP-UX (B11.23 IA PA) and all patches the bundle requires perbundle installation instructions

The following OS software bundles contain the drivers for the A6826A, A9782A, A9784A,AB378A, AB379A, AB465A, AD193A, AD194A, AD300A, and QMH2462 adapters:

FibrChanl-01 B.11.23.08.02 HP-UX (B11.23 IA PA) and all patches the bundle requires perbundle installation instructions.

The following OS software bundles contain the drivers for the AD299A and AD355A adapters:

FibrChanl-02 B.11.23.0712 HP-UX (B11.23 IA) and all patches the bundle requires perbundle installation instructions.

Patches and installation instructions are provided at the HP-UX support website:

http://h20566.www2.hp.com/portal/site/hpsc

NOTE: Accessing this site requires registration.

After the hardware is installed, proceed with the following steps:

NOTE: QMH2462 adapter support will not be listed using the swlist utility; however, the

current FibrChanl-01 bundle does support the adapter.

1. The drivers stape, sctl, and schgr must all be installed in the kernel. To see if these drivers areinstalled, enter the following command:

# /usr/sbin/kcmodule schgr sctl stape

The following example shows output from kcmodule where the stape driver is not installed:

CauseStateModule

explicitstaticschgr

dependstaticsctl

http://www.hp.com/go/ebshttp://www.hp.com/supporthttp://h20566.www2.hp.com/portal/site/hpschttp://h20566.www2.hp.com/portal/site/hpschttp://www.hp.com/supporthttp://www.hp.com/go/ebs


11/36

CauseStateModule

unusedstape

beststaticestape

If one or more of the above drivers is in the unused state, they must be installed in the kernel.If they are all installed (static state), proceed to the next section, Configuring the SAN.

2. Use kcmodule to install modules in the kernel, for example to install the stape module do the

following:# /usr/sbin/kcmodule stape=static

Enter Yes to backup the current kernel configuration file and initiate the new kernel build.

3. Reboot the server to activate the new kernel.

# cd /

# /usr/sbin/shutdown -r now

The HP-UX 11iv2 Quality Pack(QPK1123) December 2007 2010 (B.11.23.1012.086a) andHardware Enablement Pack (HWEable11i) December 2010 (B.11.23.1012.085a) contain requiredsoftware bundles. These patches and installation instructions are provided at the HP website:


NOTE: Accessing this site requires registration.

Initial requirement (HP-UX 11.31 on IA-64 and PA-RISC)HP currently supports HP-UX 11.31 in an EBS environment using an HP AB465A, A9782A,

A9784A, A6795A, A6826A, AB378A/AB378B, AB379A/AB379B, AD193A, AD194A ,AD300A, AD299A, AD355A, AD221A, AD222A, AD393A, QMH2462, or LPe1105 FC HBA.Contact HP or your HP reseller for information on how to acquire these cards.

The following OS software bundles are required for the A6795A and A5158A adapters:

FibrChanl-00 B.11.31.1003The following OS software bundles are required for the AB465A, A9782A, A9784A, A6826A,

AB378A/AB378B, AB379A/AB379B, AD193A, AD194A and AD300A adapters:

FibrChanl-01 B.11.31.1203

TFibrChanl-03 B.11.31.1203

FibrChanl-04 B.11.31.1203

The following OS software bundles are required for the AD299A, AD355A, AD221A, AD222A,AD393A, AH402A, AH403A, 403621-B21, and 456972-B21 adapters:

FibrChanl-02 B.11.31.0809 HP-UX (B11.31 IA PA) and all patches the bundle requires per

bundle installation instructions.Patches and installation instructions are provided at the HP-UX support website:


After the hardware is installed, proceed with the following steps:

1. The LPe1105 adapters support will not be listed using the swlist utility. However, the currentFibrChanl-01 and FibrChanl-02 bundles do support the adapters.

2. The drivers stape, sctl, and schgr must all be installed in the kernel. To see if these drivers areinstalled, enter the following command:

# /usr/sbin/kcmodule sctl schgr eschgr stape estape

HP-UX 11
http://h20566.www2.hp.com/portal/site/hpschttp://h20566.www2.hp.com/portal/site/hpschttp://h20566.www2.hp.com/portal/site/hpschttp://h20566.www2.hp.com/portal/site/hpsc


12/36

The following example shows output from kcmodule where the stape driver is not installed:

CauseStateModule

beststaticsctl

beststaticschgr

beststaticeschgr

unusedstape

beststaticestape

If one or more of the above drivers is in the unused state, they must be installed in the kernel.If they are all installed (static state), proceed to the next section, Configuring the SAN.

3. Use kcmodule to install modules in the kernel, for example to install the stape module do thefollowing:

# /usr/sbin/kcmodule stape=static

Enter Yes to backup the current kernel configuration file and initiate the new kernel build.

4. Reboot the server to activate the new kernel.

# cd /

# /usr/sbin/shutdown -r now

The HP-UX 11i Version 3 March 2012 release contains the current software bundles.

These patches and installation instructions are provided at the HP website:

http://software.hp.com

HP-UX 11.31 can experience poor I/O performance on VxFS file systems due tomemory blocking during high system memory usage

The HP-UX 11.31 kernel, subsystems, and file I/O data cache can consume up to 90 percent ofsystem memory during normal operation. When a heavy file I/O application such as a data

protection application starts, the memory usage can reach close to 100 percent. In such conditions,if VxFS attempts to allocate additional memory for inode caching, this can result in memory blockingand subsequent poor file I/O performance. In extreme conditions, this scenario can cause dataprotection applications to time out during file system reads, which could result in backup jobfailures.

Poor I/O performance resolution

To avoid the situation of backup job failures due to memory blocking, modify the kernel tunableparameter vx_ninode. The vx_ninode parameter determines the number of inodes in the inodetable to help VxFS in caching. By default, the size of the inode cache is decided (auto-tuned) atboot time by VxFS depending on the amount of physical memory in the machine.

When modifying the value of vx_ninode, HP recommends the following:

VxFS inode cache (number of inodes)Physical memory or kernel available memory

163841 GB

327682 GB

655363 GB

131072> 3 GB

To determine the current value of vx_ninode, run the following at the shell prompt:

# /usr/sbin/kctune vx_ninode

http://software.hp.com/http://software.hp.com/


13/36

To set vx_ninode to 32768, run the following command at the shell prompt:

# /usr/sbin/kctune vx_ninode=32768

NOTE: The kernel tunable parameters filecache_min and filecache_max control theamount of physical memory that can be used for caching file data during system I/O operations.By default, these parameters are automatically determined by the system to better balance thememory usage among file system I/O intensive processes and other types of processes. The valuesof these parameters can be lowered to allow a larger percentage of memory to be used for purposes

other than file system I/O caching. Determining whether or not to modify these parameters dependson the nature of the applications running on the system.

HP-UX 11.23: Disabling rewind-on-close devices with st_san_safe

Turning on the HP-UX 11.23 kernel tunable parameter st_san_safe disables tape device specialfiles that are rewind-on-close. This will prevent utilities like mt from rewinding a tape that is in useby another utility.

Some applications or utilities require rewind-on-close device special files (for example, the frecoverutility that comes with HP-UX). In this case, disabling rewind-on-close devices renders the utilityunusable. Most data protection applications such as HP Data Protector can be configured to useSCSI reserve/release, which protects them from rogue rewinds by other utilities.

The requirements of the data protection environment should be considered when determiningwhether or not to enable st_san_safe.

To determine if rewind-on-close devices are currently disabled, enter:

# /usr/sbin/kctune st_san_safe

If the value of st_san_safe is 1, then rewind-on-close devices are disabled. If the value is 0, thenrewind-on-close devices are enabled. To disable rewind-on-close devices, enter:

# /usr/sbin/kctune st_san_safe=1

Configuring the SAN

Set up the qualified tape library and router. See the documentation provided with each StorageArea Network (SAN) component for additional component setup and configuration information.

Due to current issues with the fcparray driver within HP-UX, HP recommends that there be no SCCLUN set to 0 on the router.

Final host configurations

When the preliminary devices and the appropriate drivers listed earlier are installed and the SANconfiguration is complete, the host should see the devices presented to it.

1. Run ioscan to verify that the host detects the tape devices.

# ioscan

2. After verifying that all devices are detected, check for device files assigned to each device.For HP-UX 11.31 legacy device special files (DSFs), run the following commands:

# ioscan -fnkC tape # ioscan -fnkC autoch

3. For HP-UX 11.31 persistent DSFs, run the following commands:

# ioscan -fnNkC tape # ioscan -fnNkC autoch

NOTE: Some data protection products might not currently support HP-UX 11.31-persistentDSFs for tape. See the data protection product documentation for more information.

4. If no device files have been installed, enter the following command:

# insf -C tape -e # insf -C autoch -e

HP-UX 13


14/36

Installation checklist

With a complete SAN configuration, review the questions below to ensure that all components onthe SAN are logged in and configured properly.

Are all hardware components at the minimum supported firmware revision, including: Server,HBA, Fibre Channel Switch, Fibre Channel to SCSI Router, Interface Manager, Command

View TL, tape drives, library robot?

Are all recommended HP-UX patches, service packs, quality packs or hardware ennoblement

bundles installed on the host? Is the minimum supported HBA driver loaded on the host?

Are all tape and robotic devices mapped, configured and presented to the host from the FibreChannel to SCSI Router, or Interface Manager?

Is the tape library online?

Is the Fibre Channel to SCSI router correctly logged into the Fibre Channel Switch?

Is the host HBA correctly logged into the Fibre Channel Switch?

If multiple Fibre Channel switches are cascaded or meshed, are all ISL ports correctly loggedin?

If using zoning on the Fibre Channel Switch, is the server HBA and Tape Library's FibreChannel to SCSI Router in the same switch zone (either by WWN or by switch Port)?

If using zoning on the Fibre Channel Switch, has the zone been added to the active switchconfiguration?

Windows Server and Windows Storage ServerThis section provides instructions for configuring Windows Server 2008 and Windows Server2003 in an Enterprise Backup Solution (EBS) environment.

Windows Storage Server is often the operating system used to build network attached storage(NAS) servers. While this is a modified build of Windows, it operates in the same manner as other

Windows servers in an EBS environment. The storage servers have limitations on how much theycan be changed. Refer to the storage server installation and administration guides for moreinformation:

http://www.hp.com/go/servers

The configuration process involves:


Installing the minimum patch/service pack level support for:

Windows Server 2008/2003 on 32- and 64-bit platforms

Data Protection software

See the following websites to obtain the necessary patches:

For HP: http://www.hp.com/support

For Microsoft: http://www.microsoft.com

NOTE: See the HP Enterprise Backup Solutions Compatibility Matrix for all current and requiredhardware, software, firmware, and device driver versions at http://www.hp.com/go/ebs.

See the Installation Checklist at the end of this section to ensure proper installation and configurationof the hardware and software in the SAN.

http://www.hp.com/go/servershttp://www.hp.com/supporthttp://www.microsoft.com/http://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.microsoft.com/http://www.hp.com/supporthttp://www.hp.com/go/servers


15/36

Configuring the SANThis procedural overview provides the necessary steps to configure a Windows Server 2008/2003host into an EBS. See the documentation provided with each storage area network (SAN) componentfor additional component setup and configuration information.

NOTE: To complete this installation, log in as an administrator with administrator privileges.

Installing the HBA device driver (Windows Server 2008/2003)

Obtain the appropriate Smart Component driver install package from http://www.hp.com.Double-click on the .exe file and the driver will be installed for you. A reboot might be necessaryafter the driver installation.

Storport considerations

EBS supports Storport configurations with the Brocade, Emulex and QLogic Storport mini-portdrivers. Prior to installing the Storport HBA driver, the Storport storage driver (storport.sys) must beupdated. Check the HP Enterprise Backup Solutions Compatibility Matrix for the currently supportedversion.

CAUTION: Failure to upgrade the Storport storage driver prior to installing the HBA mini-port

driver may result in system instability.


To ensure that all components on the SAN are logged in and configured properly, review thefollowing questions:

Are all hardware components at the minimum supported firmware revision, including: Server,HBA, Fibre Channel Switch, Fibre Channel to SCSI/FC Router, Interface Manager, Command

View TL, tape drives, library robot?

Are all recommended Windows Server 2008/2003 patches and service packs installed onthe host?

Is the minimum supported HBA driver loaded on the Windows server?

Is the tape library/VLS/D2D/NAS targets online?

Is the host HBA correctly logged into the Fibre Channel Switch?

If using zoning on the Fibre Channel Switch, is the server HBA and Tape Library's FibreChannel Port(s) in the same switch zone (by WWN or PWWN)?

Is the Removable Storage Manager (RSM) in Windows Server disabling Properly? (SeeWindows 2003 known issues for more information on RSM.)

Is the Test Unit Ready (TUR) command stopped? (See Windows 2003 known issues for moreinformation on TUR.)

Has connectivity and performance been tested using HP Library and Tape Tools (L&TT)?

Windows 2003 known issues

Target and LUN shifting

Device binding can be helpful in resolving issues where device targets, and sometimes even LUNs,shift. For operating systems such as Windows and HP-UX, issues can arise when a given target orLUN changes in number. This can be caused by something as simple as plugging or unplugginganother target (typically a disk or tape device) into the SAN. In most cases this can be controlledthrough the use of good zoning and/or persistent binding.

Windows Server and Windows Storage Server 15
http://www.hp.com/http://www.hp.com/


16/36

The Windows operating system can still have issues even when zoning and binding are used. Thecause of many of these issues is due to the way that Windows enumerates devices. Windowsenumerates devices as they are discovered during a scan sequence. They are enumerated withdevice handles such as such as TAPE0, TAPE1, and so on. The Windows device scan sequencegoes in the order of bus, target, and LUN. Bus is the HBA PCI slot, then target, which isrepresentative of a WWN, and LUN, which is representative of a device behind the WWN. Theorder will be the lowest bus, then a target and its LUNs, then on to the next target, until it sees nomore on that HBA. Then on to the next HBA, and its targets and LUNs. A common cause for device

shifting is when the tape device is busy and cannot respond in time for the OS to enumerate it.Each device after that shifts up a number.

Note the target persistency in the Emulex One Connect Manager utility or QLogic's utility. Thesame applies to LUN binding in the Emulex full port driver utility.

Some backup applications communicate with the tape device by using the Windows device name.As noted, the device name may shift and cause a problem for the backup application. Someapplications monitor for this condition and adjust accordingly. Other applications must wait for areboot and scan of devices, or the application must be manually reconfigured to match the currentdevice list.

What neither of the binding utilities do is affect Windows' device enumeration.

NOTE: Some vendor applications use device serialization and are not affected by LUN shifting.

Interop issues with Microsoft Windows persistent binding for tape LUNs

Windows Server 2003 provides the ability to enable persistence of symbolic names assigned totape LUNs by manually editing the Windows registry. Symbolic name persistence means that tapedevices will be assigned the same symbolic name across reboot cycles, regardless of the order inwhich the operating system actually discovers the device. This feature was originally released byMicrosoft as a stand-alone patch and was later incorporated into SP1. For more information, goto the following website:

http://www.microsoft.com/ and search for support article KB873337 for details

The persistence registry key is as follows:HKey_Local_Machine\System\CurrentControlSet\Control\Tape\Persistence

NOTE: Persistence=1 symbolic tape names are persistent

Persistence=0 non-persistent

Persistence is disabled by default. When you enable persistence, symbolic tape names (also referredto as logical tape handles) change significantly. For example, \\.\Tape0 becomes \\.\Tape2147483646 . It is not possible to configure the new symbolic tape name. Some applicationsare unable to correctly recognize and configure devices that have these longer persistent symbolicnames.

As a workaround, persistent binding of Fibre Channel port target IDs, enabled through the FibreChannel host bus adapter utilities (such as Emulex Once Connect Manager, Brocade (HCM), orQLogic (QCC)) can provide some benefit. Target ID binding assures that targets are presented ina consistent manner but cannot guarantee consistent presentation of symbolic tape names.

Tape drive polling

The Windows Removable Storage Manager service (RSM) polls tape drives on a frequent basis.Windows built-in backup software (NTBACKUP) relies on the RSM polling to detect media changesin the tape drive. In SAN configurations, this RSM polling can have a significant negative impacton tape drive performance.

http://www.microsoft.com/http://www.microsoft.com/


17/36

NOTE: For SAN configurations, HP strongly recommends disabling RSM polling.

NOTE: Removable Storage Manager is no longer available as of Windows 7 and WindowsServer 2008 R2.

Library slot count/Max Scatter Gather List issue

The Max Scatter Gather List parameter for the Emulex driver must be changed for hostswith a library that has a slot count greater than 2000. The recommended fix is to make the Windowsregistry parameter MaximumSGList a value of 0x40 (64) or greater which allows the transfer oflarger blocks of data. This may already be a default parameter in newer driver revisions.

Tape.sys block size issue

At the end of March 2005, Microsoft released Service Pack 1 (SP1) for the Windows Server 2003platform. With SP1, Microsoft changed the driver tape.sys to allow for NTBackup tapes writtenon 64-bit Windows 2003 Server to be read or cataloged on 32-bit Windows 2003 Server systems.The change in the tape.sys driver imposes a limit on the data transfers to a block size of nogreater than 64KB. Performance issues will be more apparent on all high-performance tape drivessuch as the HP Ultrium 960 and SDLT 600 using the tape.sys driver.

As a result, backup applications using HP tape drivers (hplto.sys, hpdat.sys, hpdltw32.sys,hpdltx64.sys, and hpdltw64.sys) and tape.sys driver may experience poor performanceand/or failed backup jobs. If experiencing either of these symptoms, check the backup applicationwith the software vendor to see if the backup application is using the Microsoft tape driver, tape.sys.

Microsoft released a hotfix that replaces the affected tape.sys file with a version that removesthe 64KB limitation on block sizes; see http://support.microsoft.com/kb/907418/en-us. Thishotfix was integrated into Windows 2003 Service Pack 2 (SP2).

Emulex SCSIport driver issue

A potential tape I/O performance issue has been discovered with Windows Server 2003 32-bitsystems configured with Emulex SCSIPort mini-port HBA drivers. This issue only affects those backup

applications using tape block sizes/transfer lengths exceeding 128KB. Emulex SCSIPort mini-portHBA drivers use a MaximumSGList entry in the Windows registry that defines the maximum datatransfer length supported by the adapter for SCSI commands.

Early Emulex drivers, version 5.5.20.8 and older, set this registry entry to a value of 33 decimal(21 hexadecimal) limiting SCSI transfers to a maximum of 128KB. Beginning with version 5.5.20.9,this registry entry was increased to 129 decimal (81 hexadecimal) increasing SCSI transfers to512KB. The issue surfaces when upgrading an installed Emulex HBA SCSIPort mini-port driverfrom driver version 5.5.20.8 and earlier to driver version 5.5.20.10 or later (driver version 5.5.20.9is exempt from this issue). During the upgrade, the existing MaximumSGList registry entry is notmodified from 33 to 129. Since it remains at the lower value (33), the SCSI transfer length remainsat 128K, thus possibly affecting performance when large block sizes/transfer lengths are used.

To resolve this issue, modify the MaximumSGList in the registry as follows:

CAUTION: Using the Registry Editor incorrectly can cause serious, system-wide problems. Microsoftcannot guarantee that any problems resulting from the use of Registry Editor can be solved. Usethis tool at your own risk. Back up the registry before editing.

1. Click Start > Run to open the Run dialog box.2. Enter regedit to launch the registry editor.3. Navigate to the following registry key:

\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lpxnds\Parameters\Device\MaximumSGList

4. Change the REG_DWORDvalue from 33 to 129.

Windows Server and Windows Storage Server 17
http://support.microsoft.com/kb/907418/en-ushttp://support.microsoft.com/kb/907418/en-us


18/36

FC interface controller device driver issue

In Windows environments, the Hardware Discovery Wizard detects the presence of the controllerLUN, identifies it to the user as HP FC interface controller, and prompts for installation of a devicedriver. The FC interface controller does not require a device driver and is fully functional withoutthe device driver. However, until a device entry is created in the System Registry, the Windowsoperating system (OS) will classify it as an unknown device.

Each time the server is booted, the Hardware Discovery Wizard will prompt for installation of adriver file. A device information file (.inf) is available, which installs a null device driver andcreates a device entry in the System Registry. The .inf file is located on the HP website for yourproduct or by searching for HP_CPQ_router_6.zip or later version. By using this file, a storagerouter can be essentially 'registered' with the device manager once, minimizing user interaction.

Not Enough Server Storage is Available to Process this Commandnetwork issue

A network issue was observed where a backup application was unable to make a networkconnection to a remote network client. The error that was reported from Windows 2003, throughthe backup application, was Not enough server storage is available to process this command. Thiserror can occur with various versions of Windows Server (NT, 2000, 2003) that also has Norton

AntiVirus or IBM AntiVirus software installed. This is a known network issue documented in thefollowing Microsoft Knowledge Base article at

http://support.microsoft.com/default.aspx?scid=kb;en-us;177078

To resolve the issue, a registry edit is required. Please review the steps detailed in the MicrosoftKnowledge Base Article to resolve the issue.

Updating the HP Insight Management Agents for Microsoft Windows using the ProLiant SupportPack Version 7.70 (or later)

When updating the HP Insight Management Agents for Microsoft Windows using the ProLiantSupport Pack Version 7.70 (or later) the Disable Fibre Agent Tape Support option is inadvertentlyunchecked by default. This occurs because the previous data in the registry is not saved duringthe software update from the Management Agents Version 7.60 (or earlier).

Figure 4 shows the Disable Fibre Agent Tape Support option selected prior to the ProLiant SupportPack Version 7.70 (or later) update installation.

Figure 2 Updating the HP Insight Management Agents for Microsoft Windows using the ProLiantSupport Pack Version 7.70 (or later)

http://support.microsoft.com/default.aspx?scid=kb;en-us;177078http://support.microsoft.com/default.aspx?scid=kb;en-us;177078


19/36

Follow the link below to see the full advisory:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&obectID=c0122 9672

NAS and ProLiant Storage Server devices using Microsoft Windows Storage Server2003

Server storage differs from direct-attached storage in several ways.

Stored data can have multiple sets of file attributes due to heterogeneous access (NFS, SMB,Novel, Macintosh).

The storage server is typically not supported by a console.

Storage server vendors are often forced to use a common backup protocol, NDMP, becauseof lack of backup application support of the underlying or customized storage server OS.

Storage servers using Data Protection Manager (DPM) provide administrative tools for protectingand recovering data on the file servers in the network.

HP NAS and HP ProLiant Storage Server devices are built on Windows Storage Server (WSS)2003. Backup applications supported by Windows 2003 also run on WSS 2003, and the terminalservices on the Microsoft based storage server supports backup application's GUI. The major

backup vendors are actively testing their applications on the WSS framework.All tape devices (both SCSI and FC connected) supported by the Windows systems are automaticallyavailable on Windows Storage Server 2003 storage server solutions. Since most storage serversare built with a specialized version of the OS, some of the device drivers may be outdated orunavailable. Updates to the storage server product from HP may have more current drivers. Theseupdates are available for download from the HP server website. Newer tape device drivers aremade available from hardware and software vendors and are used on these platforms. See thefollowing website for the HP Enterprise Backup Solutions Compatibility Matrixand certified Windowsdevice drivers: http://www.hp.com/go/ebs.

Known issues with NAS and ProLiant Storage Servers

Storage servers are highly dependent on networking resources to serve up data. Backup applicationsare also highly dependent on networking resources to establish communications with other backupservers to coordinate the usage of the tape libraries. At times this dependency on networkingservices can conflict, and the backup application may lose contact with the other servers, causingbackups to fail. Take note of any extended networking resources used for storage servers that maybe shared with backup, such as NIC teaming, and make sure that communications are not broken.

Tru64 UNIXThe configuration process for Tru64 UNIX can be a somewhat seamless process. When firmwareand driver revisions of the components are at minimum EBS acceptable levels, the integrationprocess is as simple as installation of hardware and configuring devices to the SAN fabric. Thisis possible because Tru64 UNIX maintains driver and configuration parameters in the OS kerneland device database table. It is recommended, however, that if new console firmware is available,it is applied as outlined below to Tru64 UNIX servers in an EBS.

NOTE: Refer to the HP Enterprise Backup Solutions Compatibility Matrix for all current andrequired hardware, software, firmware, and device driver versions at: http://www.hp.com/go/ebs.

To ensure correct installation and configuration of the hardware, see Installation checklist(page 14).

Tru64 UNIX 19
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&obectID=c0122%209672http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&obectID=c0122%209672http://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&obectID=c0122%209672http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&obectID=c0122%209672


20/36

Backup software patchRefer to your backup software vendor to determine if any updates or patches are required.

Configuring the SANThis procedural overview provides the necessary steps to configure a Tru64 UNIX host into anEBS. Refer to the documentation provided with each storage area network (SAN) component foradditional component setup and configuration information.

1. Prepare the required rack mounted hardware and cabling in accordance with the specificationslisted in backup software user guide as well as the installation and support documentation foreach component in the SAN.

NOTE: Loading Console firmware from the Console firmware CD may also update the hostbus adapter (HBA) firmware. This HBA firmware may or may not be the minimum supportedby EBS. Refer to the HP Enterprise Backup Solutions Compatibility Matrix for minimum supportedHBA firmware revisions.

2. Upgrade the AlphaServer to the latest released Console firmware revision.

Refer to http://www.hp.com/support to obtain the latest Console firmware revision.

a. Boot the server to the chevron prompt (>>>).b. Insert the Console firmware CD into CD-ROM drive.c. To see a list of all accessible devices, at the chevron prompt, type:

>>> show dev

d. Obtain the CD-ROM device filename from the device list. Where DQA0 is an exampleCD-ROM device filename for the CD-ROM drive, at the chevron prompt type:

>>> Boot DQA0

e. Complete all of the steps in the readme file, as noted in the message prompt.f. If the minimum supported HBA firmware revision was installed in this step, go to step 3.

If the minimum supported HBA firmware revision was not installed in this step, upgrade

at this time. Refer to the release notes provided with the HBA firmware for installationinstructions. To verify the latest supported revisions of HBA firmware and driver levels forthe 32-bit KGPSA-BC, and 64-bit KGPSA-CA, FCA2354, FCA2384, FCA2684 andFCA2684DC, refer to the HP Enterprise Backup Solutions Compatibility Matrix at: http://www.hp.com/go/ebs.

NOTE: HBA firmware can be upgraded before or after installing Tru64 UNIX. The driverwill be installed after Tru64 UNIX is installed. Contact Global Services to obtain the mostcurrent HBA firmware and drivers.

3. Install the Tru64 patch kit.

a. Refer to the release notes and perform the steps necessary to install the most current Tru64patch kit.b. The current patch kit installs the current Tru64 UNIX HBA driver. To verify that the installed

HBA driver meets minimum support requirements, refer to the HP Enterprise BackupSolutions Compatibility Matrix at: http://www.hp.com/go/ebs.

4. Upgrade the HBA driver if the HBA does not contain the most current supported driver.

http://www.hp.com/supporthttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/support


21/36

a. Contact Global Services to obtain the latest HBA driver.b. Upgrading the HBA driver may require building a new kernel. Create a backup copy of

the kernel file (/vmunix) before building a new kernel.c. If building a new kernel was necessary, reboot the server. If building a new kernel was

not necessary, at a Tru64 UNIX terminal window type:

# hwmgr -scan scsi.

5. Verify that the Tru64 UNIX host is logged in to the Fibre Channel switch.

Make sure that the server logs in to the switch as an F-port.

Confirming mapped componentsThis section provides the commands needed to confirm that the components have been successfullyinstalled in the SAN.

Installed and configured host bus adaptersTo obtain a list of all host bus adapters (HBAs) that are physically installed and configured in theserver, enter the following command in a terminal window on the Tru64 host:

# emxmgr -d

For Tru64 5.1b the following command is recommended:

# hwmgr -show fibre

Visible target devices

WWN of the routerTo view a list of target devices that are visible to each installed HBA onthe Tru64 UNIX host, enter the following command where emx0 is the name of the HBA.

# emxmgr -t emx0

For Tru64 5.1b the following command is recommended:

# hwmgr -show fibre -adapter -topology

Verify that the WWN of the router is included in the list.

Tape and Robot DevicesTo view a list of all of the tape

Tape and Robot DevicesTo view a list of all of the tape and robotic devices that are visibleand configured by Tru64 UNIX host, enter the following command:

# hwmgr -view dev

Tru64 UNIX dynamically builds all device files. This process may take several minutes.

Configuring switch zoningIf zoning will be used, either by World Wide Name or by port, perform the setup after the HBA

has logged into the fabric. Refer to the Fibre Channel switch documentation for complete switchzone setup information. Ensure that the World Wide Name (WWN) or port of theFibre-Channel-to-SCSI bridge is in the same zone as the WWN or port of the HBA installed in theserver.


Are all hardware components at the minimum supported firmware revision, including: Server,HBA, Fibre Channel switch, Fibre Channel to SCSI router, Interface Manager, Command ViewTL, tape drives, library robot?

Are the current Tru64 operating system patches installed, and is the server running the current

console firmware?

Tru64 UNIX 21


22/36

Is the minimum supported HBA driver loaded on the host?

Are all tape and robotic devices mapped, configured, and presented to the host from the FibreChannel to SCSI Router, or Interface Manager?


Is the Fibre Channel to SCSI router correctly logged into the Fibre Channel switch?

Is the host HBA correctly logged into the Fibre Channel switch?


If using zoning on the Fibre Channel switch, is the server HBA and Tape Library's Fibre Channelto SCSI router in the same switch zone (either by WWN or by switch port)?

If using zoning on the Fibre Channel switch, has the zone been added to the active switchconfiguration?

Red Hat and SUSE LinuxThis section provides instructions for configuring Linux in an Enterprise Backup Solution (EBS)environment. The configuration process involves:

Upgrading and installing the EBS hardware components to meet the minimum firmware anddevice driver requirements (this includes all supported server, Fibre Channel Host Bus Adapters(FC HBA), switches, tape libraries, tape drives, and interconnect components).

Installing the minimum required patches, both for the operating system and the backupapplication.

NOTE: See the HP Enterprise Backup Solutions Compatibility Matrix for all current and requiredhardware, software, firmware, and device driver versions at: http://www.hp.com/go/ebs.

Operating system notes

In general, EBS configurations are not dependent on a specific kernel errata level. This is notthe case for support of HP disk storage products. EBS follows the recommended minimumkernel errata versions as documented for HP disk arrays. This support can be found on theSingle Point of Connectivity Knowledge (SPOCK) web site at: http://www.hp.com/storage/spock. Access to SPOCK requires an HP Passport account.

HP recommends installing the kernel development option (source code) when installing anyLinux server. Availability of source code ensures the ability to install additional device supportsoftware that will be compiled into the kernel.

Installing HBA drivers and toolsObtain the latest HP-supported Emulex or Qlogic driver kit from the HP support website:

1. From an Internet browser, go to http://www.hp.com.2. Click Support and Drivers.3. In the For Product box, search for the driver kit appropriate for your model HBA (for example,

FCA2214, A6826A or FC2143).4. Select the operating system version of the system in which the HBA is installed.5. See the driver kit release notes.6. Install the driver kit by running the Install script included in the kit. HP recommends using the

Install script instead of running individual RPMs to ensure that drivers are installed with theappropriate options and that the fibre utilities are installed properly.

http://www.hp.com/go/ebshttp://www.hp.com/storage/spockhttp://www.hp.com/storage/spockhttp://www.hp.com/http://www.hp.com/http://www.hp.com/storage/spockhttp://www.hp.com/storage/spockhttp://www.hp.com/go/ebs


23/36

7. Beginning with the driver kits that included the 8.01.06 QLogic driver and the 8.0.16.27Emulex driver (both kits released October 2006), execute the following script found in thefibreutils directory: # cd /opt/hp/hp_fibreutils/pbl # ./pbl_inst.sh -i

8. Reboot the server to complete the installation.

NOTE: Step 7 of the above procedure was introduced to eliminate the need to havehp_rescan -a run as part of /etc/rc.local (or some other boot script). In previousversions of the driver kit, executing the hp_rescan utility was necessary to work around an

intermittent issue with device discovery of SCSI-2 tape automation products. Executing thepbl script inserts the probe-luns utility into the boot sequence and identifies and addsSCSI-2 device strings for legacy tape products into the kernel's blacklist. The result is that allof the supported tape libraries and drives should be discovered correctly without any additionalsteps by the user.

9. Verify that the host has successfully discovered all tape drive and library robotic devices usingone of the following methods:

Review the device listing in /proc/scsi/scsi

Review the output from the hp_rescan command

Review the output from the lssgcommand

If there are devices that have not been successfully discovered, review the HBA driver installationprocedure above, particularly step 5, then proceed to the Installation checklist (page 14).

HP's fibre utilities, located in the /opt/hp/hp_fibreutils directory, are installed as part ofthe driver kit and include the following:

hp_rescan: used to force a rescan of all SCSI buses

scsi_info: used to query a device

adapter_info: displays HBA information (i.e. World Wide Names)

lssd: lists disk devices (sd device files)

lssg: lists online and nearline devices (sg device files) hp_system_info: lists system configuration information

Additional SG device filesIn most environments, the default number of SG device files is sufficient to support all of the requireddevices. If the environment is fairly large and the default number of SG device files is fewer thanthe combined total of disk, tape, and controller devices being allocated to the server, then additionaldevice files need to be created. SG device files are preferable to the standard st (symbolic tape)device files due to SCSI timeout values that may not be sufficient in length to support some tapeoperations.

To create additional SG device files, perform the following:

# mknod /dev/sgX c 21 X

X signifies the number of the device file that does not already exist. For additional commandoptions, see the mknod man page.


Are all hardware components at the minimum supported firmware revision, including: server,HBA, Fibre Channel switch, interface controller, Interface Manager, CommandView TL, tapedrives, library robot?

Are there any required Linux operating system patches missing (required patches are noted

on the EBS Compatibility Matrix)?

Red Hat and SUSE Linux 23


24/36

Is the supported HBA driver loaded on the host?

Are all tape and robotic devices mapped, configured, and presented to the host from theinterface controller or Interface Manager?


Is the FC-attached tape drive logged into the Fibre Channel switch (F-port)?

Is the interface controller logged into the Fibre Channel switch (F-port)?

Is the host HBA correctly logged into the Fibre Channel switch (F-port)? If multiple Fibre Channel switches are cascaded or meshed, are all ISL ports correctly logged

in?

If using zoning on the Fibre Channel switch, is the interface controller, or tape drive, configuredinto the same switch zone as the host (either by WWPN or by switch port number)?

If using zoning on the Fibre Channel switch, has the host's zone been added to the activeswitch configuration?

Linux known issues

Rewind commands being issued by rebooted Linux hostsDevice discovery that occurs as part of a normal Linux server boot operation issues a SCSI rewindcommand to all attached tape drives. For backup applications that do not employ SCSI Reserveand Release, if the rewind command is received while the tape drive is busy writing, the result isa corrupted tape header and an unusable piece of backup media.

This issue could manifest itself as either a failed verify operation, a failed restore operation, or theinability to mount a tape and read the tape header. If a backup verification is not completed, thenormal backup process might not detect that an issue exists. This issue is present today in SUSEEnterprise Linux 9 and will become an issue for SUSE Enterprise Linux 8 and Red Hat EnterpriseLinux 3 and 4 with the introduction of the QLogic v8.01.06 and Emulex v8.0.16.27 driver kits.

NOTE: Refer to Customer Advisory c00788781 for additional details on the new driver kits andtheir associated installation procedure changes.

The scope of this issue includes any EBS configuration that uses a backup application which doesnot implement SCSI Reserve and Release and contains at least one Linux host which has sharedaccess to tape devices. Backup applications known to be affected are HP Data Protector (allversions) and Legato NetWorker prior to v7.3.

The only recommended work-around for affected applications is to not reboot Linux servers whileother hosts are running backups.

Tape devices not discovered and configured across server reboots

Tape drives disappear from Linux servers after the host reboots. This issue was identified andcommunicated in Customer Advisory OT050715_CW01, dated 26 September 2005. Adding theline "hp_rescan -a" to /etc/rc.d/rc.local resolved the issue. Hp_rescan is an HP Host Bus Adapter(HBA) utility included and installed with the Fibre Channel HBA driver kit.

This issue, which affects Red Hat installations and, intermittently some SUSE Linux installations, isnow understood to be an issue with the mid-layer SCSI driver and interaction with SCSI-2 tapeautomation products. The permanent resolution to this issue is to upgrade to the latest Fibre Channeldriver kit (QLogic 8.01.06 or Emulex 8.0.16.27, both released in October 2006). This driver kitintroduced a revised installation procedure, incorporating the probe-luns utility into the bootsequence. The revised installation procedure was outlined earlier in this section and was alsocommunicated in Customer Advisory c00788781, dated 11 October 2006.



25/36

Sparse files causing long backup times with some backup applications

Some Integrity and X64 64-bit HP Servers running the Red Hat Enterprise Linux 3 operating system(or later) may have longer than expected system backup times or appear to be stalled when backingup the following file:

/var/log/lastlog

This file is known as a "sparse file." The sparse file may appear to be over a terabyte in size andthe backup software will take a long time to back up this file. Most backup software applications

have the capability to handle sparse files with special sparse command flags. An example of thisis the "tar" utility, which has the "-sparse" or "-S" flag that can be used with sparse files.

If your backup application does not include support for backing up sparse files, then /var/log/lastlog should be excluded from the backup.

LUNs shifting after reboot

The Linux 2.6 kernel and later enhanced the management of the attached devices through theintroduction of udev. the udev device manager provides users with a persistent naming processfor all devices across reboots. For details on how to configure udev refer to the appropriate Linuxdistribution documentation.

If the application requires persistent device mapping, run the ISV device configuration wizard.

Oracle SolarisThis section provides instructions for configuring Oracle Solaris in an Enterprise Backup Solution(EBS) environment. The configuration process involves:


Installing the following minimum patches for Oracle Solaris:

Solaris 9 requires 112233-12, 112834-06, and 113277-51

Solaris 10 SPARC requires 118822-36 and 118833-36

Solaris 10 x86/64 requires 118855-36

Installing the minimum patch/service pack level support for the backup software

See the following websites to obtain the necessary patches:


For Solaris: http://www.oracle.com

NOTE: Refer to the HP Enterprise Backup Solutions Compatibility Matrix for all current andrequired hardware, software, firmware, and device driver versions at: http://www.hp.com/go/ebs.

See Installation checklist (page 14) to ensure that the hardware and software in the SAN iscorrectly installed and configured.

Configuring the SANThis procedural overview provides the necessary steps to configure an Oracle Solaris host into anEBS. See the documentation provided with each storage area network (SAN) component foradditional component setup and configuration information.

Currently supported adapters for Oracle Solaris include Oracle, QLogic, and Emulex-brandedHBAs. HP EBS supports all 4Gb and 8Gb HBAs with the Sun native driver. For some models of2Gb HBAs, the QLogic qla and Emulex lpfc drivers are supported.

Oracle Solaris 25
http://www.hp.com/supporthttp://www.sun.com/http://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.sun.com/http://www.hp.com/support


26/36

Device binding can help resolve issues where device targets shift. Issues can arise when a giventarget or LUN changes number. In most cases, this can be controlled through the use of goodzoning or persistent binding. When using QLogic or Emulex drivers, configuring for persistentbinding is recommended. For the Oracle native driver, persistent binding is not necessary unlessrecommended by the backup application vendor or for an environment where tape devices willbe visible across multiple hosts.

For configuring persistent binding with the Sun native driver, see the Oracle document Solaris SANConfiguration and Multipathing Guideat http://docs.oracle.com/cd/E19253-01/820-1931/

index.html.

Oracle Solaris native driver configuration1. Prepare the required rack mounted hardware and cabling in accordance with the specifications

listed in backup software user guide as well as the installation and support documentation foreach component in the SAN.

NOTE: To complete this installation, a root login is required.

2. For Solaris 9, download the current Sun StorEdge SAN Foundation Software (SFS) from http://www .sun.com/storage/san. Select the following files for download:

Install_it Script SAN 4.4.x (SAN_4.4.x_install_it.tar.Z) Install_it Script SAN 4.4.x Readme (README_install_it.txt)

The README document explains how to uncompress the downloaded file and execute theInstall_it Script.

NOTE: From Oracle's site, the Install_it Script is considered an optional download, but doesinclude all required SFS packages and patches for Solaris 9. The Install_it Script will identifythe type of HBA and version of Solaris before installing the appropriate SFS packages andpatches.

3. SFS functionality is included within the Solaris 10 operating system. The Solaris native

SUNWqlc driver is included with Solaris 10. For Solaris 10 01/06 or later release,SUNWemlxs and SUNWemlxu driver packages are included. To obtain SUNWemlx packages,go to Oracles Products Download page at http://developers.sun.com/products/ . Search forStorageTek Enterprise Emulex Host Bus Adapter Device Driver. Install the appropriate patch:

SUNWqlc on Solaris 10 SPARC, install patch 119130-33 or later

SUNWqlc on Solaris 10 x86/64, install 119131-33 or later

SUNWemlx on Solaris 10 SPARC, install patch 120222-31 or later

SUNWemlx on Solaris 10 x86/64, install patch 120223-31 or later

4. Update the HBA fcode if needed using the flash-upgrade utility included in the appropriatepatch.

SG-XPCI1FC-QF2 (X6767A) and SG-XPCI2FC-QL2 Patch 114873-05 or later

SG-XPCI2FC-QF2 (X6768A) and SG-XPCI2FC-QF2-Z Patch 114874-07 or later

SG-XPCI1FC-EM2 and SG-XPCI2FC-EM2 Patch 121773-04 or later

SG-XPCI1FC-QF4 (QLA2460) and SG-XPCI2FC-QF4 (QLA2462) Patch 123305-04 orlater

5. Reboot the server with -r option:

#reboot -- -r

6. Use the cfgadm utility to show the HBA devices:

#cfgadm -al

http://docs.oracle.com/cd/E19253-01/820-1931/index.htmlhttp://docs.oracle.com/cd/E19253-01/820-1931/index.htmlhttp://%20www%20.sun.com/storage/sanhttp://%20www%20.sun.com/storage/sanhttp://developers.sun.com/products/http://developers.sun.com/products/http://%20www%20.sun.com/storage/sanhttp://%20www%20.sun.com/storage/sanhttp://docs.oracle.com/cd/E19253-01/820-1931/index.htmlhttp://docs.oracle.com/cd/E19253-01/820-1931/index.html


27/36

7. Use the cfgadm utility to configure the HBA devices. c2 is the HBA device in this example.

#cfgadm -c configure c2

8. Use devfsadm utility to create device files:

#devfsadm

Troubleshooting with the cfgadm utility

Getting the status of FC devices using cfgadm:# cfgadm -al

Example output for above command:

This output shows a media changer at LUN 0 for the 100000e0022229fa9world wide name,and tape and disk devices at LUN 0 for other world wide names. The devices are connectedand have been configured and are ready for use. The cfgadm -al -o show_FCP_devcommand can be used to show the devices for all LUNs of each Ap_Id.

Fixing a device with an unusable condition:

If the condition field of a device in the cfgadm output is unusable, then the device is in astate such that the server cannot use the device. This may have been caused by a hardwareissue. In this case, do the following to resolve the issue:

1. Resolve the hardware issue so the device is available to the server. 2.2. After the hardware issue has been resolved, use the cfgadm utility to verify device status

and to mend the status if necessary:

Use cfgadm to get device status:

# cfgadm -al

For a device that is unusable use cfgadm to unconfigure the device and thenre-configure the device. For example (this is an example only, your device worldwide name will be different):

# cfgadm -c unconfigure c4::100000e0022286ec

# cfgadm f -c configure c4::100000e0022286ec

Use cfgadm again to verify that the condition of the device is no longer unusable:

# cfgadm -al

QLogic driver configuration for QLA2340 and QLA2342Substitute for your device name appropriately.

Oracle Solaris 27


28/36


2. After installing the HBA, verify proper hardware installation. At the OpenBoot PROM okprompt, type:

show-devs

If the HBA is installed correctly, an entry similar to the following is displayed (the path will

vary slightly depending on your configuration):/pci@1f,4000/QLGC,qla@5

Verify the HBA hardware installation in Solaris at the shell prompt by typing:

prtconf -v | grep QLGC

If the HBA is installed correctly, and the driver has not yet been installed, a device similar tothe following is displayed:

QLGC,qla (driver not attached)

NOTE: To complete this installation, log in as root.

3. After installing the HBA, install the device driver. The driver comes with the HBA or can beobtained from http://www.qlogic.com.

4. To ensure that no previous device driver was installed, at the prompt, type:

#pkginfo | grep QLA2300

If no driver is installed, a prompt is returned. If there is a driver installed, verify that it is thecorrect revision by entering:

#pkginfo -l QLA2300

If the driver needs to be removed, enter:

#pkgrm

5. Install the new driver. Navigate to the directory where the driver package is located and at

the prompt, type:#pkgadd -d ./

6. Make sure that the driver is installed. At the prompt, type:

#pkginfo -l QLA2300

7. Look at /kernel/drv/qla2300.conf (the device configuration file) to make sure theconfiguration is appropriate.

Fibre Channel tape support is enabled. An example follows:

hba0-fc-tape=1;

Persistent binding can be configured by binding SCSI target IDs to the Fibre Channel world

wide port name of the router or tape device. To set up persistent binding, the persistent bindingonly option is enabled. An example follows.

hba0-persistent-binding-configuration=1;

After enabling persistent binding only, router or tape drive world wide port names (wwpn) isbound to SCSI target IDs. For example, if a router has a wwpn of 1111222233334444 andis visible to hba0, bind it to SCSI target ID 64 as follows:

hba0-SCSI-target-id-64-fibre-channel-port-name = 1111222233334444;

Emulex driver configuration for LP10000 and LP10000DCSubstitute for your device name appropriately. The example shown is for a dual FC port adapter

connected to the fabric.

http://www.qlogic.com/http://www.qlogic.com/


29/36


NOTE: To complete this installation, a root login is required.

2. After installing the HBA, verify proper hardware installation. At the OpenBoot PROM okprompt, type:

show-devsIf the HBA installed correctly, devices similar to the following will be displayed (the path willvary slightly depending on your configuration).

/pci@8,700000/fibre-channel@1,1

/pci@8,700000/fibre-channel@1

Verify the HBA hardware installation in Solaris at the shell prompt by typing:

prtconf -v | grep fibre-channel

3. Install the HBA device driver. The driver can be obtained from http://www.emulex.com.4. To ensure that no previous device driver was installed, at the prompt, type:

#pkginfo -l lpfcIf no driver is loaded, a prompt is returned. If there is a driver installed, verify that it is thecorrect revision. If the driver removal is required, enter:

#pkgrm

5. Install the new driver. Navigate to one directory level above where the driver package directoryis located and at the prompt, type:

#pkgadd -d

Select the lpfc package

6. Make sure that the driver is installed. At the prompt, type:

#pkginfo -l lpfc7. Verify the HBA driver attached by typing:

#prtconf -v | grep fibre-channel

If the driver attached, devices similar to the following are displayed:

fibre-channel, instance #0

fibre-channel, instance #1

8. Look at /kernel/drv/lpfc.conf (the device configuration file) to make sure the configuration isappropriate.

For World Wide Port Name binding, add the following line:

fcp-bind-method=2;For FCP persistent binding, the setting fcp-bind-WWPN binds a specific World Wide PortName to a target ID. The following example shows two NSR FC ports zoned in to the secondinterface on the HBA:

Oracle Solaris 29
http://www.emulex.com/http://www.emulex.com/


30/36

NOTE: The interface definitions appear in /var/adm/messages. The interfaces lpfc0 andlpfc1 map to the following devices:

lpfc0 is /pci@8,700000/fibre-channel@1

1lpfc1 is /pci@8,700000/fibre-channel@1,1

NOTE: Refer to comments within the lpfc.conf for more details on syntax when setting

fcp-bind-WWPN. Add the following to item 2 within section Configuring Oracle Servers for tapedevices on SAN:

For LP10000 adapter:

name="st" class="scsi" target=62 lun=0;




Configuring Oracle Servers for tape devices on SAN

NOTE: The information in the following examples, such as target IDs, paths, and LUNs, areexamples only. The specific data for your configuration may vary.

NOTE: This section applies to Solaris 9 and Solaris 10 prior to Update 5 (05/08). Configurationof the st.conf file is no longer required with Solaris 10 Update 5 (05/08) or later. Tape deviceswill be discovered automatically after a reboot.

1. Edit the st.conf file for the type of devices to be used and also for binding. The st.conffile should already reside in the /kernel/drv directory. Many of the lines in the st.conffile are commented out. To turn on the proper tape devices, uncomment or insert the appropriatelines in the file.

tape-config-list=

NOTE: The tape-config list is composed of a group of triplets. A triplet is composed of theVendor ID + Product ID, pretty print, and the data property name. The syntax is very important.There must be eight characters for the vendor ID (COMPAQ or HP) before the product ID(DLT8000, SDLT600, Ultrium, etc). In the above line, there are exactly two spacesbetweenCOMPAQand DLT8000, and there are exactly six spaces between HPand Ultrium.The order of the triplets is also important for Ultrium tape drives for discovery. The pretty printvalue will be displayed in the boot log /var/adm/messages for each tape drive discoveredthat matches the associated vendor ID + product ID string.

Below the tape config list is a list of data property names used to configure specific settingsfor each device type.



31/36

Some data protection applications handle the SCSI reservation of the tape drives and othersrequire the operating system to do so. For a complete description of setting SCSI reservation,see the options bit flag ST_NO_RESERVE_RELEASE on the man page for st.

The ST_NO_RESERVE_RELEASE flag is part of the fourth parameter in the data property name.For LTO1-data and LTO2-data, a value of 0x9639 means the operating system handlesreserve/release and a value of 0x29639 means the application handles reserve/release. ForLTO3-data and LTO-4 data, a value of 0x18659 means the operating system handlesreserve/release and a value of 0x38659 means the application handles reserve/release.

2. Define tape devices for other adapters by adding lines similar to the following to the SCSItarget definition section of the st.conf file.

Example for QLogic adapters:

name=st class=scsi parent=/pci@1f,4000/QLGC,qla@1

target=64 lun=0;

name=st class=scsi parent=/pci@1f,4000/QLGC,qla@1

target=64 lun=1;

NOTE: The parent is the location of the HBA in the /devices directory.

NOTE: The target can be chosen; however, it must not conflict with other target bindings inthe st.conf and sd.conf files.

3. Perform a reconfiguration reboot (reboot ---r) on the server and verify that the new tapedevices are seen in /dev/rmt.

Configuring switch zoningIf zoning will be used, either by World Wide Name or by port, perform the setup after the HBAhas logged into the fabric. Refer to the Fibre Channel switch documentation for complete switchzone setup information. Ensure that the World Wide Name (WWN) or port of theFibre-Channel-to-SCSI bridge is in the same zone as the WWN or port of the HBA installed in theserver.


To ensure that all components on the SAN are logged in and configured properly, review thefollowing questions:

Are all hardware components at the minimum supported firmware revision, including: Server,HBA, Fibre Channel switch, Fibre Channel to SCSI router, Interface Manager, Command ViewTL, tape drives, library robot?

Are all recommended Solaris patches installed on the host?

Is the minimum supported HBA driver loaded on the host?

Are all tape and robotic devices mapped, configured and presented to the host from the FibreChannel to SCSI router, or Interface Manager?


Oracle Solaris 31


32/36

Is the Fibre Channel to SCSI router correctly logged into the Fibre Channel switch?

Is the host HBA correctly logged into the Fibre Channel switch?


If using zoning on the Fibre Channel switch, is the server HBA and Tape Library's Fibre Channelto SCSI router in the same switch zone (either by WWN or by switch port)?

If using zoning on the Fibre Channel switch, has the zone been added to the active switchconfiguration?

IBM AIXThe configuration process for IBM AIX in an EBS environment involves:

Upgrading essential EBS hardware components to meet the minimum firmware and devicedriver requirements

Installing the minimum patch level support for:

IBM AIX

Backup softwareRefer to the following websites to obtain the necessary patches:


For IBM: http://www.ibm.com

NOTE: Refer to the HP Enterprise Backup Solutions Compatibility Matrix for all current andrequired hardware, software, firmware, and device driver versions at http://www.hp.com/go/ebs.

Refer to the Quick Checklist at the end of this section to ensure proper installation and configurationof all of the hardware and software in the SAN.

Configuring the SANThis procedural overview provides the necessary steps to configure an AIX host into an EBS. Referto the documentation provided with each storage area network (SAN) component for additionalcomponent setup and configuration information.

NOTE: To complete this installation, log in as root.

Prepare the required hardware and cabling in accordance with the specifications listed in chapter2 of this guide as well as the installation and support documentation for each component in theSAN.

IBM 6228, 6239, 5716, or 5759 HBA configurationNOTE: See the EBS compatibility matrix concerning IBM AIX OS version support for these HostBus Adapters.

1. Install the latest maintenance packages for your version of AIX. This ensures that the latestdrivers for the 6228/6239/5716/5759/5773/5774 HBA are installed on your system. For

AIX 4.3.3, the latest packages must be installed because the base OS does not contain driversfor the newer HBAs.

2. Install the IBM 6228/6239/5716/5759/5773/5774 HBA, and restart the server.3. Ensure that the card is recognized. At the prompt, type:

#lsdev -Cc adapter

http://www.sun.com/http://www.ibm.com/http://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.hp.com/go/ebshttp://www.ibm.com/http://www.sun.com/


33/36

There is a line in the output similar to the following:

fcs0 Available 1D-08 FC Adapte

Documents

Fiber Chanel