Professional Documents
Culture Documents
Legal and notice information Copyright 20032007 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.
Contents
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rack stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP-authorized reseller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Helpful web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. .. .. . . . . . . . . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ....... ....... ....... ....... ....... ....... ....... ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5 5 6 7 7 7 7
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Overview of Enterprise Backup Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Solution features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Solution components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Supported operating systems and platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Data Protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Important terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Manager-of-Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 EBS-specific requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Shared library and tape devices with multiple systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Multiple paths to tape devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Assigning a preferred MultiPath host within a backup policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Supported configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing HP Storage Data Protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation best practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Import the additional hostnames for multiple LAN interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . Device serialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Patching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cleaning tape support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Library and Tape Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. .. .. .. .. . . . . . . . . . . . . . . . . . . . . 17 17 18 18 19 19 19 20 20 20
3 High availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Clustered EBS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Unable to execute wide SCSI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Data Protector media allocation order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Error when configuring EADR or OBDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
A Additional resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
HP guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Other HP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Figures
1 2 3 4 Example network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Autoconfiguration Wizard - Devices screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MultiPath tape drive instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MultiPath drive properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enterprise Backup Solution with HP Data Protector implementation guide
12 12 13 13
3
5 6 7 8
Non-MultiPath tape drive instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MultiPath drive Device Properties dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic storage domain configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clustered server EBS configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . .
13 14 15 21
Tables
1
Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Intended audience
This 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
Prerequisites
Before 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 documentation
In 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
Convention
Medium blue text: Figure 1 Medium blue, underlined text (http://www.hp.com) Bold font
Text emphasis File and directory names System output Code Text typed at the command-line Code variables Command-line variables
Emphasis of file and directory names, system output, code, and text typed at the command line
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:
NOTE:
TIP:
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 support
Telephone 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 reseller
For 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.
Introduction
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 vendors 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 features
HP 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 components
Solution 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.
Data Protector
The 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 ManagerThe 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 AgentInstall 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 ServersClient systems with connected backup devices and the Media Agent installed. Installation ServerThe 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-Managers
Data 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 repositoryThis 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.
10
Introduction
Enterprise reportingThe MoM can generate reports on a single-cell basis as well as for the entire enterprise environment.
EBS-specific requirements
EBS 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.
11
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.
12
Introduction
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.
13
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 configurations
Figure 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.
14
Introduction
The basic EBS storage domain may consist of a heterogeneous connection of multiple servers sharing multiple libraries and RAID array storage systems.
RAID array storage FC SAN switch Sun Solaris UNIX cluster HP ProLiant server Sun Solaris UNIX server HP NAS server HP PA-RISC server
2 4 6 8 10 12
HP tape library storage IBM p-series UNIX server HP AlphaServer HP PA-RISC cluster HP AlphaServer cluster Microsoft cluster
15
16
Introduction
Installation checklist
To 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.
17
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.
18
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 serialization
The 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 specifications
Data 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 upthe data sources on the Disk Agent clients 2. Selecting where to back up tothe backup devices connected to the Media Agent clients 3. Selecting how to back upbackup options 4. 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 Administrators Guide for complete instructions on configuring backup specifications.
Patching
Data 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.
19
Performance
For 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.
20
High availability
For information on configuring HP-MC/ServiceGuard, Microsoft Cluster Server, and VERITAS Cluster Server for Solaris, see the Data Protector web site at: http://www.hp.com/go/dataprotector 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
3 5
4 2 7
Ethernet Microsoft Cluster servers Private Ethernet link RAID array storage FC SAN Switch
2 4 6 8
21
22
High availability
Troubleshooting
This 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..
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.
23
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.
24
Troubleshooting
Additional resources
The 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: http://www.hp.com/go/ebs
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 resources
See 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
25
26
Additional resources
Index
A
additional resources 25 assigning preferred path 14 audience 5 authorized reseller, HP 7 Autoconfiguration Wizard 11, 12, 18, 19 drive servers 10
E
EBS basic storage configuration 15 clustered configuration 21 Compatibility Matrix 9, 14 design guide 9, 14 Example Configurations 14 features 9 overview 9 web site 5, 25 enterprise reporting 11
B
backup software, removal 17 backup specifications 19 backups direct or indirect path 11 Synthetic Full 9 Virtual Full 9 best practices 18
F
Fibre Channel disk storage 9 ports 17 switches 17 firmware revision 17
C
Cell Manager 10, 11, 17, 18 centralized licensing repository 10 Centralized Media Management Database 10 Command View TL 17 Compatibility Matrix 14 conventions document 6 text symbols 6
H
hardware components 9 platforms 9 setup 9 HBA driver 17 help, obtaining 7 high availability 21 host-centric zoning 17 HP authorized reseller 7 storage web site 7 Subscribers choice web site 7 technical support 7
D
Data Protector cell 10, 11 Cell Manager 10 clients 11 Disk Agent 10 drive servers 10 GUI 11 high availability 21 important terms 10 installation 17 Installation Server 10 Manager of Managers 10 Media Agent 10, 11, 18 other backup software 17 setup wizard 19 virtual host feature 18 Device Autoconfiguration Wizard 11, 12, 18, 19 device serialization 19 disaster recovery 21 Disk Agent 10 DNS Connection Check tool 18 document conventions 6 prerequisites 5 related documentation 5 documentation, HP web site 5
I
installation best practices 18 checklist 17 Installation Server 10, 17 Internal Database 10 Interswitch Link ports 17
L
Library and Tape Tools (L&TT) 20
M
Manager of Managers 10 mapped devices 17 Media Agent 10, 11, 18 MultiPath tape drive 11, 12, 13 multiple paths to tape devices 11
27
O
Online Database Backup 17 Open File Manager 17 operating systems, supported 9
P
patches 17 performance tweaking 20 platforms, supported 9 port 5555 18 prerequisites 5
R
rack stability, warning 7 related documentation 5
S
SAN interconnects 9 SCSI reserve 11 Secure Manager 17 setup wizard 19 solution features 9 Subscribers choice, HP 7 symbols in text 6
T
tape libraries 9 technical support, HP 7 text symbols 6 time zones 18 troubleshooting 23
V
virtual host feature 18
W
warning, rack stability 7 web sites Data Protector 19, 21 EBS123 5, 25 HP documentation 5 HP storage 7 HP Subscribers choice 7 OpenView support 23 support 7
Z
zoning 17
28