hp data protector

HP StorageWorksEnterprise Backup Solution with HP Data Protector implementation guide

Part number: 5697–6467Second edition: February 2007

Legal and notice information

© Copyright 2003–2007 Hewlett-Packard Development Company, L.P.

Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information is provided "as is" without warranty of any kind and 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.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.

Enterprise Backup Solution with HP Data Protector implementation guide

Enterprise Backup Solution with HP Data Protector implementation guide 3

About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Rack stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

HP-authorized reseller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Helpful web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Overview of Enterprise Backup Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Solution features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Solution components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Supported operating systems and platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Data Protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Important terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Manager-of-Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

EBS-specific requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Shared library and tape devices with multiple systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Multiple paths to tape devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Assigning a preferred MultiPath host within a backup policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Supported configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2 Installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Installing HP Storage Data Protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Installation best practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Import the additional hostnames for multiple LAN interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Device serialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Backup specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Patching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Cleaning tape support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Library and Tape Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3 High availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Clustered EBS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Unable to execute wide SCSI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Data Protector media allocation order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Error when configuring EADR or OBDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

A Additional resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25HP guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Other HP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Figures1 Example network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Device Autoconfiguration Wizard - Devices screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 MultiPath tape drive instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 MultiPath drive properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Contents

4

5 Non-MultiPath tape drive instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 MultiPath drive Device Properties dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Basic storage domain configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Clustered server EBS configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Tables1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6


About this guideThis guide provides information to help you configure HP Data Protector software on an HP StorageWorks Enterprise Backup Solution (EBS).

Intended audienceThis guide is intended for use by system administrators implementing an EBS configuration who are experienced with the following:

• Tape backup technologies and tape libraries• SAN environments and backup software• Fibre Channel technology

PrerequisitesBefore you install and configure HP Data Protector, make sure you have:

• Reviewed the EBS Compatibility Matrix• Properly installed and configured your EBS hardware according to the HP StorageWorks Enterprise

Backup Solution Design Guide

Related documentationIn addition to this guide, HP provides the EBS123 web site at http://www.hp.com/go/ebs with corresponding HP StorageWorks Enterprise Backup Solution information. The following is some of the content found on the EBS123 site:

• EBS Compatibility Matrix• Enterprise Backup Solution design guide• EBS example configurations• EBS white papers and implementation guides

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

6

Document conventions and symbols

WARNING! Indicates that failure to follow directions could result in bodily harm or death.

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT: Provides clarifying information or specific instructions.

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

Table 1 Document conventions

Convention Element

Medium blue text: Figure 1 Cross-reference links and e-mail addresses

Medium blue, underlined text (http://www.hp.com)

Web site addresses

Bold font • Key names

• Text typed into a GUI element, such as into a box

• GUI elements that are clicked or selected, such as menu and list items, buttons, and check boxes

Italics font Text emphasis

Monospace font • File and directory names

• System output

• Code

• Text typed at the command-line

Monospace, italic font • Code variables

• Command-line variables

Monospace, bold font Emphasis of file and directory names, system output, code, and text typed at the command line


Rack stability

WARNING! To reduce the risk of personal injury or damage to equipment:• Extend leveling jacks to the floor.• Ensure that the full weight of the rack rests on the leveling jacks.• Install stabilizing feet on the rack.• In multiple-rack installations, secure racks together.• Extend only one rack component at a time. Racks may become unstable if more than one component is

extended.

HP technical supportTelephone numbers for worldwide technical support are listed on the HP support web site: http://www.hp.com/support/.

Collect the following information before calling:

• Technical support registration number (if applicable)• Product serial numbers• Product model names and numbers• Applicable error messages• Operating system type and revision level• Detailed, specific questions

For continuous quality improvement, calls may be recorded or monitored.

HP strongly recommends that customers sign up online using the Subscriber's choice web site: http://www.hp.com/go/e-updates.

• Subscribing to this service provides you with e-mail updates on the latest product enhancements, newest versions of drivers, and firmware documentation updates as well as instant access to numerous other product resources.

• After signing up, you can quickly locate your products by selecting Business support and then Storage under Product Category.

HP-authorized resellerFor the name of your nearest HP-authorized reseller:

• In the United States, call 1-800-282-6672.• Elsewhere, visit the HP web site: http://www.hp.com. Then click Contact HP to find locations and

telephone numbers.

Helpful web sitesFor other product information, see the following HP web sites:

• http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/go/ebs• http://www.hp.com/support/ • http://www.docs.hp.com • http://www.hp.com/go/tape

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

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

http://www.hp.com

http://www.hp.com

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

http://www.hp.com/go/e-updates

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

http://www.docs.hp.com



1 IntroductionOverview of Enterprise Backup Solutions

Implementing an Enterprise Backup Solution (EBS) can be challenging. HP understands that for any given Storage Area Network (SAN) environment there may be one or more vendor’s hardware and software present. Each of these components, including software, servers, interconnects and target devices must work together. The HP EBS group is dedicated to providing thorough integration testing of industry standard, heterogeneous, and multi-vendor SAN environments. The output of this work can be found at http://www.hp.com/go/ebs in the form of the HP StorageWorks EBS Compatibility Matrix, HP StorageWorks Enterprise Backup Solution Design Guide, and the various software implementation guides, such as this one.

This guide is intended to address many of the integration issues that you may encounter when setting up your EBS. This guide provides new feature information, best practices, and troubleshooting tips from an EBS perspective. This guide is not meant to replace the supporting documentation for the application, but is provided to supplement that documentation with special configuration issues that might not be covered in the application documentation.

See the HP StorageWorks Enterprise Backup Solution Design Guide for proper hardware setup and configuration. See the HP StorageWorks EBS Compatibility Matrix for the complete list of tested and supported EBS hardware and software. Certain limitations apply and are noted where applicable.

Solution featuresHP is committed to providing technologically advanced data protection and disaster recovery solutions. The HP Data Protector EBS features the following:

• A robust backup solution that offers the lowest total cost of ownership in the enterprise space.• Easy deployment in heterogeneous environments and automated high performance backup and restore

from tape or disk.• Advanced features such as Virtual Full backups and Synthetic Full backups.

Solution componentsSolution components include:

• Heterogeneous operating systems such as Windows®, HP-UX, Linux, Tru64, NetWare, Solaris, and AIX• Hardware platforms including Network Attached Storage (NAS), Intel, and AMD-based ProLiant

servers, blade servers, and RA-RISC based servers• SAN interconnects such as Fibre Channel switches, host bus adapters, and Fibre Channel to SCSI tape

drive interconnects• Fibre Channel disk storage such as the HP EVA, XP, MSA, and VA• Tape libraries such as the HP ESL-E Series, EML, and MSL• HP Data Protector

For a complete list of tested and certified solution components, see the EBS Compatibility Matrix at http://www.hp.com/go/ebs.

Supported operating systems and platformsThe EBS with Data Protector supports several operating systems and platforms. See the HP Data Protector Platform & Integration Support Matrix for the complete listing of supported Cell Manager, Installation Server, and Backup Agent support. This matrix can be found in "support matrices" at http://www.hp.com/go/dataprotector.


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


10 Introduction

Data ProtectorThe Data Protector cell is a network environment that includes a Cell Manager and client systems that run agents. The Cell Manager is the "traffic cop" that controls the activities and Internal Database (IDB) within the Data Protector cell. It is not necessary to administer the backup and restore activities directly from the Cell Manager itself, because any client within the cell (as supported) can connect to the Cell Manager over the network and be used to administrate the activities of the cell. Client systems are imported into a cell and belong to a single Cell Manager. Multiple cells may exist, each with their own Cell Manager. This environment may be managed by a single Manager of Managers or "MoM."

Client systems run agents that are allocated according to what the client needs to do. For example, in a typical EBS environment a client is installed with a Media Agent and a Disk Agent. The Media Agent is installed on a server if that server is going to have direct access to a tape device for backup and restore. The tape devices can be directly attached or allocated over a SAN. The Disk Agent is allocated to a server if that server is going to read data from a disk device, whether local or remote.

Important terms• Cell Manager—The Cell Manager is the main system in the cell. The Cell Manager:

• Manages the cell from a central point• Contains the Internal Database (IDB)• Runs core Data Protector software• Runs Session Managers that start and stop backup and restore sessions and write session

information to the IDB• Disk Agent—Install the Disk Agent on client systems you want to back up. The Disk Agent reads or

writes data from a disk on the system and sends or receives data from the Media Agent. The Disk Agent is also installed on the Cell Manager, allowing you to back up data on the Cell Manager, the Data Protector configuration, and the IDB.

• Media Agent—(For servers that have direct access to tape drives.) During a backup session, the Media Agent receives data from the Disk Agent and sends it to the device for writing to the medium. During a restore session, the Media Agent locates data on the backup medium and sends it to the Disk Agent. The Disk Agent then writes the data to the disk. The Media Agent also manages the robotics control of a library.

• Drive Servers—Client systems with connected backup devices and the Media Agent installed.• Installation Server—The Installation Server holds a repository of the Data Protector software

packages for a specific architecture. The Cell Manager, by default, is also an Installation Server.

NOTE: Installation Servers are used to perform push installs and upgrades from a central location. In heterogeneous environments (UNIX® and Windows), two Installation Servers are required. The UNIX Installation Server is used to push to UNIX clients and a Windows Installation Server is used to push to Windows clients.

Manager-of-ManagersData Protector provides the MoM for management of large environments with multiple cells. The MoM allows you to group multiple cells into a larger unit, which can be managed from a single point. New cells can be added, or existing cells can be split. MoM provides:

• Centralized licensing repository—This optional feature enables simplified licensing management.

• Centralized Media Management Database (CMMDB)—The CMMDB allows you to share devices and media across several cells in a MoM environment. Using CMMDB, devices in one cell are accessible to other cells that use the CMMDB.• With the CMMDB, you can share high-end devices between cells in the multi-cell environment. One

cell can control the robotics, serving several devices that are connected to systems in different cells. Even the Disk Agent to Media Agent data path can go across cell boundaries.


• Enterprise reporting—The MoM can generate reports on a single-cell basis as well as for the entire enterprise environment.

EBS-specific requirementsEBS with Data Protector requires that the Media Agent be installed on all clients that have access to SAN-shared tape devices. One server must have the Cell Manager software installed while all other servers only require the Media Agent. Disk Agents are also required for clients (SAN or LAN) that require a disk service to be read for backup.

Shared library and tape devices with multiple systemsData Protector allows libraries and individual tape drives to be dynamically shared between multiple Data Protector clients that run the Media Agent. Each server can access any of the shared drives as needed and each server "owns" the drive it has active. Data Protector uses a lock name to ensure that an active tape drive is reserved to an individual server, within the Data Protector cell. This prevents two Data Protector Media Agents from accessing the same physical device at the same time. See the HP Data Protector Administrator's Guide for more information on configuring device locking.

IMPORTANT: Unless special configuration steps are taken, a SCSI reserve is not placed on the active tape device. The locking mechanism is only valid for servers that are within the Data Protector cell. Rogue servers can potentially disrupt or corrupt active Data Protector backup sessions. Care must be taken with servers that have access to shared tape devices when rebooting, performing device scans, or when using utilities like tar or dd in UNIX. For more information, see the "Rogue applications" section in the HP StorageWorks Enterprise Backup Solution Design Guide located at http://www.hp.com/go/ebs.

Data Protector provides the Device Autoconfiguration Wizard to make configuring shared libraries and drives fast and easy. Using the wizard helps to eliminate mistakes that are made when shared devices are manually configured. For the complete list of supported operating systems and platforms, please see http://www.hp.com/go/dataprotector.

The Autoconfiguration Wizard is run from the Cell Manager, or any client that runs a Data Protector GUI that is connected to the Cell Manager. The wizard does the following activities:

• Performs device discovery on each client that has the Media Agent installed• Adds robotic libraries and shared drives to the Data Protector Devices configuration• Configures device locking for shared drives• Can automatically configure "MultiPath devices"

Multiple paths to tape devicesIn an environment with shared tape devices, there may be many paths a server can take to reach a particular tape device. A server running the Media Agent within Data Protector can access a shared tape device through two connection paths. The first is a "direct" path (bus, target, lun) to a shared tape device over Fibre Channel, SCSI, or iSCSI. The second is an "indirect" path to that same shared tape device through the LAN to an alternate server running a Media Agent. See Figure 1 for a depiction of a direct and indirect path.

A shared tape device that can be accessed either directly or indirectly by a Media Agent server is defined as a "MultiPath" device within Data Protector. To ensure optimal performance, verify that the direct path is used for backups. Slow backup performance may be an indicator that the indirect path is being used for a backup.

To verify the order of the configured paths to a shared "MultiPath" tape device, review the drive properties for each shared tape device. The following example explains how to review and configure a MultiPath tape device.



12 Introduction

Assume there are two servers named samick and pure that both have connections to a shared tape drive as shown in Figure 1. The direct path from pure to the tape drive shows the most efficient route, and the indirect route through samick to the tape drive should only be used if the direct path becomes unavailable.

Figure 1 Example network

Each server is recognized by the tape devices when Group by Devices is selected (Figure 2) in the wizard. When Autoconfiguration is performed, the option Automatically configure MultiPath devices is checked by default.

Figure 2 Device Autoconfiguration Wizard - Devices screen


After the Autoconfiguration completes, there is one instance of each MultiPath tape drive (Figure 3). The servers having access to these tape drives are no longer shown.

Figure 3 MultiPath tape drive instances

To check that the Autoconfiguration Wizard determined the most efficient path to a tape drive, you should access the properties dialog box for each MultiPath drive and see the configured paths taken by each client. For example, Figure 4 shows that the pure client has two paths to the tape device. The path order follows the route as read from top to bottom, therefore it goes over the LAN to the samick client to reach the tape drive. The most efficient route should be directly from the pure client to the tape device, as shown by the second configured path.

The path order can be changed within the properties dialog box. Reorder the configured paths for pure by moving the appropriate path up in the list, then click Set. This ensures that backups of pure will use its local direct path to tape.

Figure 4 MultiPath drive properties dialog box

If MultiPath devices are not automatically set up in the Device Autoconfiguration Wizard, there is an instance of each drive for each host like that shown in Figure 5.

Figure 5 Non-MultiPath tape drive instances

To avoid these multiple instances, run the Device Autoconfiguration Wizard with Automatically select MultiPath devices selected.

14 Introduction

Assigning a preferred MultiPath host within a backup policyAn alternate way to assign a preferred path is within the backup policy. If the backup policy is created to back up a single host, the Use preferred MultiPath host option may be set. This option is available within the MultiPath drive properties dialog box that is found in the Destination tab of the backup policy (Figure 6).

Figure 6 MultiPath drive Device Properties dialog box

If a single backup policy is created to back up multiple hosts, the use of Use preferred MultiPath host may require some data traffic to use a LAN connection in order to reach the assigned preferred host.

Supported configurationsFigure 7 shows a diagram of a basic storage domain configuration. Please see the EBS Compatibility Matrix for the latest list of certified and supported EBS components. See the HP StorageWorks Enterprise Backup Solution Design Guide for help with properly configuring your certified and supported hardware. Also, see the HP StorageWorks Enterprise Backup Solution example configurations for help with layout and design of your EBS. These documents can be found at http://www.hp.com/go/ebs.



The basic EBS storage domain may consist of a heterogeneous connection of multiple servers sharing multiple libraries and RAID array storage systems.

Figure 7 Basic storage domain configuration

1 RAID array storage 2 HP tape library storage3 FC SAN switch 4 IBM p-series UNIX server5 Sun Solaris UNIX cluster 6 HP AlphaServer7 HP ProLiant server 8 HP PA-RISC cluster9 Sun Solaris UNIX server 10 HP AlphaServer cluster11 HP NAS server 12 Microsoft cluster13 HP PA-RISC server

16 Introduction


2 Installation and configurationBefore installing your backup software, see the supporting documentation for each individual hardware component, as well as the HP StorageWorks Enterprise Backup Solution Design Guide for assistance in setting up your hardware.

Installation checklistTo ensure that all components on the SAN are logged in and configured properly, you must be able to answer yes to each of the following questions:

• Are all hardware components at the minimum supported firmware revision (HBA, Fibre Channel switch, router, tape library drives, tape library robot, and Virtual Library)?

• Is the minimum patch level support for the operating system installed?• Is the minimum supported HBA driver loaded on the host?• Is the tape library online?• Are all tape and robotic devices mapped and configured in Command View TL?• Are all tape and robotic devices being allocated to hosts through Secure Manager?• If using a Virtual Library, is LUN masking set up to allocate devices to the appropriate hosts?• Are the Fibre Channel ports of the tape library correctly logged into the Fibre Channel switch?• Is the host server correctly logged into the Fibre Channel switch?• If the Fibre Channel switches are cascaded or meshed, are all Interswitch Link (ISL) ports correctly

logged in?• Are the Fibre Channel ports of the tape library and the host server HBA in the same switch zone (either

by World Wide Name (WWN) or Port)?• Does the host server detect all of the tape and robotic devices intended to be used?• Are the latest Data Protector patches installed?

NOTE: HP recommends placing devices in host-centric zones and making them available to the server. Host-centric zoning is implemented by creating a specific zone for each server or host and adding only those storage elements that are used by that host. Host-centric zoning prevents a server from detecting any other devices on the SAN, including other servers. Host-centric zoning also simplifies the device discovery process.

Installing HP Storage Data ProtectorAfter all components on the SAN are logged in and configured, the system is ready for the installation of Data Protector. See the HP OpenView Storage Data Protector Installation and Licensing Guide or contact HP customer support for detailed installation procedures and requirements.

IHP recommends that you install in the following order:

1. Cell Manager2. Installation Server3. Data Protector clients, and add-on products such as Open File Manager, Online Database Backup,

and so on4. Any additional Data Protector add-on products

NOTE: HP recommends that you remove any other backup software currently configured on your system before installing Data Protector. Other backup software, tape device applications that are part of the OS, and SAN or system management software can negatively affect how Data Protector installs and functions.

18 Installation and configuration

The Cell Manager and Installation Servers are installed directly from the CD or from the software package located on the server hard drive. After you have installed the Cell Manager and Installation Servers you can then install the components on various client systems using the Data Protector Installation GUI.

There are certain hardware and software requirements that need to be met by Installation Servers and Cell Managers before you start installing the software. A dedicated port, generally port 5555, needs to be available throughout the cell. Different Linux distributions often reserve port 5555 for another device. Check /etc/services for assigned ports on Linux servers. See the HP OpenView Storage Data Protector Installation and Licensing Guide for details.

Installation best practices• Follow the HP StorageWorks EBS Compatibility Matrix and the HP StorageWorks Enterprise Backup

Solution Design Guide.• The matrix of hardware, software, and firmware is updated monthly and helps customers and

support personnel maintain their EBS environment. It is not necessary to immediately update an environment to the latest revision on the matrix. However, you should be aware of updates and changes if you experience any problems that may be related to newer or older software, driver, or firmware versions.

• The design guide describes currently supported EBS hardware configurations and how to efficiently and effectively provide shared tape library backup in a heterogeneous SAN environment.

• Do not create cells with multiple time zones. Each cell should be within one time zone.• Limit rebooting during backup windows.

• Rebooting hosts in an EBS environment during backup windows can cause job failures and configuration errors.

• When rebooting is necessary, verify the configuration of the host when maintenance or reboot is complete.

• Use the DNS Connection Check tool to verify if:• The Cell Manager properly resolves every other client of the cell• Every client of the cell properly resolves the Cell Manager• Every system, on which the Media Agent was installed, resolves every other client• Each system resolves every other system accommodating a Media Agent

• Be sure the latest Data Protector and operating system patches have been installed.• Make sure that each media server scanned with the Autoconfiguration Wizard sees and has configured

all required tape devices. On UNIX systems, make sure that a device file has been created or assigned. On Windows systems that are running the Storport HBA driver, install the tape device drivers. On Windows systems that are not running the Storport HBA driver, it is recommended that tape device drivers are not installed.

• Use the Device Autoconfiguration Wizard for all supported platforms.This wizard coordinates device configuration among all the hosts in a shared storage environment. It is essential that all hosts be configured properly with the appropriate device name, index, robot drive number, media, drive type, and device locking.

Import the additional hostnames for multiple LAN interfacesIn Data Protector, there exists the ability to import the additional hostnames for multiple LAN interfaces using the Virtual Host feature in the GUI. For most customers it is much easier to import the additional hostname from the GUI (and less error-prone), than to type in complicated omnirc file entries.

To use this feature, first configure the client host that matches the hostname of the system. For the Cell Manager, it should be installed first using its primary hostname. Next, import the additional hosts as follows:

1. From the Data Protector GUI (Manager.exe):Select Clients context, then right-click Clients and select Import Client. Type in the hostname assigned to additional LAN interface. Select Virtual Host, then Finish.


2. Configure correct hostnames in logical device settings to use alternate LAN interfaces for Media Agents (see the HP OpenView Storage Data Protector Administrator's Guide for details).

3. Configure correct hostnames in backup specifications to use alternate LAN interface for Disk Agents (see the HP OpenView Storage Data Protector Administrator's Guide for details).

Device serializationThe Data Protector setup wizard uses device serialization, a firmware feature that allows device identification and configuration. Each robot and drive found in the configuration returns a unique serial number. For any robots in the configuration, an additional command is issued to the robot. The robot returns the number of drives and the serial number for each of the drives contained in the robot. This information is used by the wizard to determine the correct drive index for each drive in the robot.

NOTE: Use of the Data Protector Device Autoconfiguration Wizard is recommended, but it is also possible to configure devices manually. Default device attributes may be changed after using either configuration method.

Backup specificationsData Protector has a wizard that allows the administrator to specify a backup source, destination, options, and schedule.

Configuring a backup consists of the following steps:

1. Selecting what to back up—the data sources on the Disk Agent clients2. Selecting where to back up to—the backup devices connected to the Media Agent clients3. Selecting how to back up—backup options4. Optionally, you can schedule an unattended backup

Before setting the backup specifications, consider the following:

• You need to have a Disk Agent installed on every system that is to be backed up, unless you use NFS (on UNIX) or Network Share Backup (on Windows) for backing up these systems.

• You need to have at least one backup device configured in the Data Protector cell.• You need to have media prepared for your backup.

NOTE: Before use, tape media must be formatted. If tapes are formatted, write attributes are changed (such as block size or segment size), and it is necessary to reformat the media to accept the new attribute settings.

• You need to have appropriate user rights for performing a backup.

See the HP OpenView Storage Data Protector Administrator’s Guide for complete instructions on configuring backup specifications.

PatchingData Protector provides a convenient patching mechanism that enables push upgrades from the Data Protector GUI. Unless a special circumstance exists, patches are typically installed on the Cell Server, and then pushed out to the clients. See the accompanying documentation for the individual patch that is being installed for specific instructions on its installation. Patches can be downloaded from the http://www.hp.com/go/dataprotector web site.


20 Installation and configuration

Cleaning tape supportHP Data Protector provides automatic cleaning for most devices using a cleaning tape. This medium will be used automatically by Data Protector if a dirty drive event from the device is detected.

• For SCSI libraries it is possible to define which slot holds a cleaning tape.• For devices with a bar code reader, Data Protector recognizes cleaning tape bar codes automatically if

they have the CLN prefix.• For devices without a cleaning tape, a dirty drive detection will cause a cleaning request to be

displayed on the session monitor window. The operator must clean the device manually. You cannot continue your backup without cleaning the drive, since the backup may fail because data may not be correctly written and stored on the media.

Library and Tape Tools Library and Tape Tools (L&TT) is a utility provided by HP for managing the HP tape libraries. L&TT is used to upgrade firmware, perform diagnostics and manage media within a supported tape library. L&TT is the preferred troubleshooting tool that can be used to generate support tickets for problem escalation. For more information on L&TT, see the HP StorageWorks Enterprise Backup Solution Design Guide at http://www.hp.com/go/ebs. Additionally, L&TT can be found at http://www.hp.com/go/tape under Value Added Features.

PerformanceFor additional information on performance tweaking, see the Performance: Finding bottlenecks chapter in the HP StorageWorks Enterprise Backup Solution Design Guide located at http://www.hp.com/go/ebs.



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


3 High availabilityFor information on configuring HP-MC/ServiceGuard, Microsoft Cluster Server, and VERITAS Cluster Server for Solaris, see the Data Protector web site at:


Data Protector enables you to meet high availability needs by:

• Integrating with clusters (HP-MC/ServiceGuard, Microsoft Cluster Server, VERITAS Cluster Server) to ensure fail-safe operation with the ability to back up virtual nodes

• Enabling the Data Protector Cell Manager itself to run on a cluster• Supporting online database application programming interfaces• Integrating with high availability solutions such as the HP StorageWorks Disk Array XP, HP

StorageWorks Virtual Array, HP StorageWorks Enterprise Virtual Array, or EMC Symmetrix• Providing various disaster recovery methods for Windows and UNIX platforms

Clustered EBS configurationThe EBS with Data Protector supports back up and restore of the primary and secondary nodes of a clustered pair of HP-UX MC/Service Guard and Microsoft Windows servers with failover.

Figure 8 Clustered server EBS configuration

1 Ethernet 2 Cell Server3 Microsoft Cluster servers 4 Server Node 15 Private Ethernet link 6 Server Node 27 RAID array storage 8 HP tape library9 FC SAN Switch

1

2

3

4

5

6

7

8

9


22 High availability


4 TroubleshootingThis chapter lists issues and solutions for situations that can occur during installation, implementation, and administration of the HP StorageWorks Enterprise Backup Solution (EBS) with HP Storage Data Protector.

Additionally, the HP OpenView support web site is available at http://support.openview.hp.com..

Unable to execute wide SCSI commandsYou are unable to execute wide SCSI commands in the tape library. For example, the library may respond to some, but not all SCSI commands. This typically indicates a bad electrical connection on pins used for wide commands. Replace cables, terminators, and devices located on the bus where the fault is located.

Data Protector media allocation orderIf you are receiving unexpected mount requests, or if it is confusing as to the order in which Data Protector is using tapes in the tape library or media pools, the following information should be helpful.

The sequence of media allocation is in the order of the following Data Protector media sets:

1. Preallocated media—Media named in the datalist device options preallocation list. Preallocated media in poor condition will not be used. The pool policy can be Strict or Loose. This media set is not sorted.Order of use—As specified in the datalist, provided that this will not break any other rules such as those relating to protection and appendable media.

2. Appendable Media—Media in "good" condition, with some currently protected data objects, but the media is not full. The pool must be appendable. This media set is sorted according to the time of the last write. The most recently written medium is listed first.Order of use—When one or more media have protected objects, the most recently written media is reused first.

3. Uninitialized Media—Media is assumed by Data Protector to not yet have a Data Protector header and that it can be auto-initialized as required during backups. The pool policy must be Loose to allow auto-initialization and the global file needs InitOnLoosePolicy=1. This media set is only available in exchanger devices. This media set is sorted with "blank" media ahead of media with an "unknown" header.Order of use—a. "Blank" media is used first.b. "Unknown" media is only used when there is no "blank" media.

4. Free Media—Media in good condition with no currently protected objects. This media set is sorted according to the time of the last write. The least recently written medium is listed first.Order of use—Least recently medium is used first.

5. Overflow Media—Media in fair condition with no currently protected objects. This media will only be used if no good condition media are available. This media set is sorted according to the total number of overwrites. The medium with the least number of overwrites is listed first.Order of use—Least recently used medium is used first.

See the HP OpenView Storage Data Protector Administrator’s Guide for additional information.

Error when configuring EADR or OBDRWhen attempting to configure Enhanced Automatic Disaster Recovery (EADR) or One Button Disaster Recovery (OBDR) on a Windows platform, the following message is displayed:

Automatic DR information could not be collected. Aborting the collecting of system recovery data.

The above issue has been seen if:

1. Device Manager shows an incorrectly configured device.Check if all storage devices are configured correctly. If Device Manager reports a device as "Unknown Device," install the proper device drivers before you perform EADR/OBDR.

http://support.openview.hp.com

24 Troubleshooting

You could see a message similar to DRIM_WIN_ERROR 13 SetupDiGetDeviceRegistryProperty in the log file <Data_Protector_home>\tmp\autodr.log.

2. There is insufficient registry space available.It is recommended that you set the maximum registry size to at least twice that of the current registry size.The following message would be seen in the autodr.log:ERROR registry 'Exception while saving registry'

...

WindowsError: [Errno 1450] Insufficient system resources exist to complete the requested service.

On Windows, the registry size can be changed as follows:

1. Right-click My Computer.2. Select Properties.3. Click the Advanced tab.4. Select Performance Options.5. Click Change... for Virtual Memory.

The displayed window has an option to set the maximum registry size.


A Additional resourcesThe HP StorageWorks Enterprise Backup Solution web site has many useful white papers, technical notes, and related user guides to assist you in using backup software solutions in an EBS environment. View this information at:


HP guides• HP StorageWorks Enterprise Backup Solution Design Guide• HP StorageWorks Enterprise Backup Solution with HP Storage Data Protector Implementation Guide

(this guide)• HP StorageWorks SAN Design Guide

Other HP resourcesSee the HP OpenView support web site at http://support.openview.hp.com. This site includes:

• Searchable Knowledge Base• Discussion forum• E-mail notifications• HP software self-healing services

http://support.openview.hp.com


26 Additional resources


Index

Aadditional resources 25assigning preferred path 14audience 5authorized reseller, HP 7Autoconfiguration Wizard 11, 12, 18, 19

Bbackup software, removal 17backup specifications 19backups

direct or indirect path 11Synthetic Full 9Virtual Full 9

best practices 18

CCell Manager 10, 11, 17, 18centralized licensing repository 10Centralized Media Management Database 10Command View TL 17Compatibility Matrix 14conventions

document 6text symbols 6

DData Protector

cell 10, 11Cell Manager 10clients 11Disk Agent 10drive servers 10GUI 11high availability 21important terms 10installation 17Installation Server 10Manager of Managers 10Media Agent 10, 11, 18other backup software 17setup wizard 19virtual host feature 18

Device Autoconfiguration Wizard 11, 12, 18, 19device serialization 19disaster recovery 21Disk Agent 10DNS Connection Check tool 18document

conventions 6prerequisites 5related documentation 5

documentation, HP web site 5

drive servers 10

EEBS

basic storage configuration 15clustered configuration 21Compatibility Matrix 9, 14design guide 9, 14Example Configurations 14features 9overview 9web site 5, 25

enterprise reporting 11

FFibre Channel

disk storage 9ports 17switches 17

firmware revision 17

Hhardware

components 9platforms 9setup 9

HBA driver 17help, obtaining 7high availability 21host-centric zoning 17HP

authorized reseller 7storage web site 7Subscriber’s choice web site 7technical support 7

Iinstallation

best practices 18checklist 17

Installation Server 10, 17Internal Database 10Interswitch Link ports 17

LLibrary and Tape Tools (L&TT) 20

MManager of Managers 10mapped devices 17Media Agent 10, 11, 18MultiPath tape drive 11, 12, 13multiple paths to tape devices 11

28

OOnline Database Backup 17Open File Manager 17operating systems, supported 9

Ppatches 17performance tweaking 20platforms, supported 9port 5555 18prerequisites 5

Rrack stability, warning 7related documentation 5

SSAN interconnects 9SCSI reserve 11Secure Manager 17setup wizard 19solution features 9Subscriber’s choice, HP 7symbols in text 6

Ttape libraries 9technical support, HP 7text symbols 6time zones 18troubleshooting 23

Vvirtual host feature 18

Wwarning, rack stability 7web sites

Data Protector 19, 21EBS123 5, 25HP documentation 5HP storage 7HP Subscriber’s choice 7OpenView support 23support 7

Zzoning 17

hp data protector

Documents