HP Data Protector Integration Guide 6.0

HP Data Protector 6.0 Integration Guide

Solutions Engineering Backup Recovery Systems Division EMC Data Domain 2421 Mission College Boulevard, Santa Clara, CA 95054 866-WE-DDUPE; 408-980-4800 Version 4.0, Revision A December 14, 2011 EMC Data Domain Proprietary and Confidential

Copyright © 2011 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC, Data Domain, and Global Compression are registered trademarks or trademarks of EMC Corporation in the United States and/or other countries. All other trademarks used herein are the property of their respective owners.

2

HP Data Protector 6.0 Integration Guide This tech note describes how to configure CIFS, NFS, and VTL to use Data Domain systems for backup and restore operations with the HP Data Protector 6.0 software. This document covers the topics shown in the following table: Related Documentation

Page 4

Prerequisites

Page 4

Restrictions

Page 4

Linux Configuration Settings

Page 5

NFS and CIFS Configuration Settings

Page 5

VTL Configuration Settings for the Data Domain System

Page 8

VTL Discovery and Configuration in HP Data Protector

Page 9

Backup Example

Page 11

Replication for VTL Media Pools

Page 12

Replication in an NFS Backup Environment

Page 12

Requirements

Page 12

Environment Overview

Page 13

Configuring NFS Replication

Page 13

Replication in a CIFS Backup Environment

Page 16

MultiPath (Library Sharing) Configuration

Page 18

Prerequisites

Page 18

Procedure for Sharing a Library

Page 18

Example Group Configuration

Page 22

HP Data Protector 6.0 Integration Guide

3

Related Documentation Please refer to the HP Data Protector 6.0 documentation on the installation media, especially the HP Data Protector 6.0 Installation and Licensing Guide. The IBM Tape Device Drivers Installation and User’s Guide is helpful for configuring tape drivers on HP-UX systems. For more information about the commands for configuring Data Domain systems, see the Data Domain Operating System User’s Guide.

Prerequisites The HP Cell Manager software should already be installed.

Restrictions Note the following restrictions when using Data Domain systems with HP Data Protector 6.0: •

Change the VTL drive concurrency level to 1 in the HP Data Protector software to get optimal compression.

•

For HP-UX 11.1x use the IBM LTO drivers. They are available from IBM: ftp://ftp.software.ibm.com/storage/devdrvr/

•

For HP-UX 11.23 and 11.31, use the native drivers.

•

For Solaris 10, install the sst driver from the HP Data Protector package for the changer and add lines like the following to the file sst.conf: name=”sst” parent=”fp” target=0 lun=0 fc-portwwn=”xxxxxxxxxxxxxxxx”

•

Update the HP Data Protector 6.0 software and the media server operating system to the latest available release. If your installation server runs HPUX 11.31 PA RISC and you want to perform a remote installation of HP Data Protector onto a Solaris 10 media server, first: a. Patch Solaris 10 to Update 6. b. Update HP Data Protector with patches 38943 and 38410.

It is likely that the above requirements apply to all remote installations of HP Data Protector onto Solaris 10 systems, regardless of the installation server operating system. •

4

Use the HP Data Protector software to change the VTL block size for each VTL drive to 256 KB. Note that, if you are copying from the VTL to another target library, the target library must support a media block size of 256 KB.

HP Data Protector 6.0 Integration Guide

Linux Configuration Settings HP Data Protector 6.1 Media Agent (MA) and Disk Agent (DA) running on the same RHEL 5 or SLES 11 Linux server with default xinetd.conf settings will have a maximum stream count of 5 for RHEL_5 and 15 for SLES_11. Each Media Agent and/or Disk Agent initiates one XINET instance. To increase the maximum number of XINET instances (increase the maximum stream count), HP recommends editing the value of the following Linex XINET parameters: 1. Edit /etc/xinetd.conf . a. RHEL 5.5 x86_64 instances

=

per_source

=

b. SLES 11 SP1 x86_64 instances

=

2. Restart the xinetd service or reboot the system. # service xinetd restart

or #/etc/init.d/xinetd restart

Note: This could be applicable to other Linux distributions and previous versions of HPDP as well.

NFS and CIFS Configuration Settings 1. Enter the settings shown in Table 1 in the General tab of the Properties window of the

HP OpenView Storage Data Protector Manager.

Table 1:

Library and Drive Type Settings

Setting

Value

Library Type

File Library

Drive Device Type File Library Media Type

File

HP Data Protector 6.0 Integration Guide

5

Figure 1:

Properties window, General tab

2. In the Repository tab, use the Data Domain system mount point or UNC path for the

file library by doing one of the following:

•

If you are using NFS, mount the Data Domain system on a local directory of the media server. Use the directory as the repository of a file library. See Figure 2.

Figure 2: •

6

Properties window, Repository tab

If you are using CIFS, specify the UNC path (\\dd510-7\backup in Figure 3) as shown:

HP Data Protector 6.0 Integration Guide

Figure 3:

Specifying a UNC path for CIFS

3. Set the following drive properties in the Advanced Options dialog box of the file

library:

a. In the Settings tab, set Concurrency to 1. See Figure 4.

Figure 4:

Advanced Options dialog box, Settings tab

b. In the Sizes tab, always set block size to 1024K. Set the other options to values that

are appropriate for your situation. See Figure 5.

HP Data Protector 6.0 Integration Guide

7

Figure 5:

Advanced Options dialog box, Sizes tab

VTL Configuration Settings for the Data Domain System Configure the Data Domain system with the following VTL settings: Table 2:

VTL Configuration Settings

Setting

Value

Library Changer model number STK L-180 Tape Drive model number

IBM-LTO-1

Tape Marker setting

hpdp1

Check that the tape marker type is set to auto or hpdp1. Verify that the tape marker setting is correct by running the following DD OS command on the Data Domain system: # filesys option show Marker-type Marker-type is: auto

Note: Only the auto marker setting is available with DD OS 5.0 and onward.

8

HP Data Protector 6.0 Integration Guide

VTL Discovery and Configuration in HP Data Protector Before discovering the Data Domain system and configuring Data Protector to use it, do the following tasks on the Data Domain system: 1. Create the virtual library, drives, CAPs, virtual cartridges, and groups. 2. Import the virtual cartridges into the VTL.

Windows discovery and configuration 1. Discover the devices by using the Device Manager. See Figure 6

Figure 6:

Windows Device Manager

2. In the HP Data Protector window, from the drop-down list box in the upper left,

select Devices & Media, right click Devices, and select Autoconfiguration.

HP Data Protector 6.0 Integration Guide

9

The Autoconfigure Devices wizard opens (Figure 7).

Figure 7:

Autoconfigure Devices wizard

3. Modify each VTL drive that is configured in HP Data Protector by following these

steps:

a. Set concurrency to1 (the default is 4) to obtain optimum compression. Use the

command Devices & Media > drive > Settings > Advanced to open the Advanced Options dialog box and make the change in the Settings tab.

Figure 8:

Advanced Options dialog box, Settings tab

b. In the Sizes tab, always set the Block size to 256 KB ( the default is 64 KB) to obtain

optimum compression. Set the other options to values that are appropriate for your situation. See Figure 9.

10

HP Data Protector 6.0 Integration Guide

Figure 9:

Advanced Options dialog box, Sizes tab

UNIX Discovery and Configuration See the HP Data Protector 6.0 Installation and Licensing Guide for information about setting up the changer and tape drives.

Backup Example 1. Start the HP Data OpenView Storage Data Protector Manager. 2. Select Backup from the action menu in the Tasks tab. 3. Select the Interactive Backup Wizard (see Figure 10). 4. Select the file or folder to back up. 5. Select the backup target and the VTL tape drive . 6. Start the backup.

HP Data Protector 6.0 Integration Guide

11

Figure 10: Backup Example

Replication for VTL Media Pools Follow these steps to configure replication: 1. Create the replication relationship between two Data Domain systems (the source

and destination unit relationship).

2. Replicate to the destination Data Domain system. 3. Configure the VTL drives and robot on the destination Data Domain system. 4. Discover and configure the destination VTL in HP Data Protector. 5. Export tapes from the source VTL by using the DD OS command vtl export. 6. Perform a barcode scan in HP Data Protector on the source VTL. 7. Import tapes into the Destination VTL using the DD OS command vtl import. 8. Perform a barcode scan in HP Data Protector.

It is now possible to restore from the destination Data Domain system. See the Data Domain Operating System User’s Guide for more detailed instructions.

Replication in an NFS Backup Environment This section describes a method on for restoring or copying data from a Data Domain replication destination restorer to an HP Data Protector 6.0 server. Note: The HP Data Protector servers used in Data Domain testing were running SUSE Linux 10.

Requirements •

12

The remote HP Data Protector server must be running the same OS as the original HP Data Protector server that sent data to the restorer. HP Data Protector 6.0 Integration Guide

•

The remote HP Data Protector needs to mount the destination restorer using the same mount path as the original HP Data Protector server.

•

HP Data Protector must have the latest patch installed.

•

The Data Domain restorers in the replication pair must use the same DD OS version.

•

Two HP Data Protector servers each with its own HP Data Protector catalog database.

•

HP Data Protector Server A and HP Data Protector Server B need to use the same mount path and same parameters.

Environment Overview Figure 11 shows an example backup environment. Alaska

San Francisco

WAN

Data Domain B Destination

Data Domain A Source

Gigabit Ethernet

Gigabit Ethernet

Server B SUSE 10

Server A SUSE 10 Disk SATA Conenction

3U

Disk SATA Connection

HP DP Catalog DB Server A

3U

HP DP Catalog DB Server B

Figure 11: NFS Backup Environment

Configuring NFS Replication This procedure refers to the environment in Figure 11. 1. On Server A, mount the /backup NFS share from Data Domain system A (San

Francisco).

2. Change (cd) to that mount directory and create a directory for storing the HP Data

Protector backup data.

In this example, use /ddr/data as the mount path, with a directory called data. 3. Configure replication on the restorers and initialize replication so that data from Data

Domain system A is replicated to Data Domain system B (Alaska).

4. On Server B, create the same mount point that is used by Server A. HP Data Protector 6.0 Integration Guide

13

5. Mount the NFS share /backup from Data Domain system B.

In our example, when you cd to /ddr you should see the directory data when you run the ls command. The permissions for the directory should be read-only. 6. Verify the permissions by trying to create a file or directory in the data directory. The

attempt should fail.

7. Create the HP Data Protector device on Server B with the same path as Server A.

In our example the HP Data Protector device would have the following path: /ddr/ data. 8. From the server in San Francisco, run a backup to Data Domain system A. 9. When the backup to Data Domain system A is complete, copy the Server A

configuration to a file. Use the following command:

omnidownload –library libraryname -file filename

In our example, the command is: omnidownload –library library-A –file /tmp/file_serverA

The following is a sample downloaded file: NAME "library-A" DESCRIPTION "" HOST ServerA.datadomain.com POLICY Filelibrary TYPE File REPOSITORY "/dd/dd560-1/hp-dp-6/0200007f546434f4150e3950004.fd" "/dd/dd560-1/hp-dp-6/0200007f5464359db50e3950007.fd" "/dd/dd560-1/hp-dp-6/0200007f5464367cb50e395000a.fd" "/dd/dd560-1/hp-dp-6/0200007f54643716a50e395000d.fd" "/dd/dd560-1/hp-dp-6/0200007f546448b3f50e3950010.fd" DIRECTORY "51200 2 0 10 /dd/dd560-1/hp-dp-6" MGMTCONSOLEURL "" 10. Edit the configuration file that you created with the omnidownload command and change the NAME and HOST parameters to reflect the Server B device name and new

host server.

11. After making the changes, save the file.

The edited file would be similar to the following example, with changes to the first and third lines: NAME "library-B" DESCRIPTION "" HOST ServerB.datadomain.com 14

HP Data Protector 6.0 Integration Guide

POLICY Filelibrary TYPE File REPOSITORY "/dd/dd560-1/hp-dp-6/0200007f546434f4150e3950004.fd" "/dd/dd560-1/hp-dp-6/0200007f5464359db50e3950007.fd" "/dd/dd560-1/hp-dp-6/0200007f5464367cb50e395000a.fd" "/dd/dd560-1/hp-dp-6/0200007f54643716a50e395000d.fd" "/dd/dd560-1/hp-dp-6/0200007f546448b3f50e3950010.fd" DIRECTORY "51200 2 0 10 /dd/dd560-1/hp-dp-6" MGMTCONSOLEURL "" 12. Copy the edited file to Server B. 13. On Server B run the following command: omniupload –modify_library libraryname -file filename

In our example, the command would be the following, where file_serverA is the edited file that was copied over from Server A: omniupload –modify_library library-B –file /tmp/file_serverA

A new icon should appear in the File Depot's Name column on the HP Data Protector management graphical user interface. The icon should show a question mark (circled in Figure 12). The question mark means that the data is present but not recognized by HP Data Protector on Server B.

Figure 12: Data is Not Yet Recognized. 14. To import the file depot, right-click the new icon and select Import.

Figure 13 shows the new icon after the import finishes. Note: The imported data comes from the restorer that is associated with Server B: Data Domain system B in our example. For the import to Server B to succeed, HP Data Protector 6.0 Integration Guide

15

replication of the data from Data Domain system A to Data Domain system B must be complete. A scan failure typically means that the data is not yet replicated to Data Domain system B.

Figure 13: Import has Finished 15. You can now copy the recently imported data to another device.

Replication in a CIFS Backup Environment For replicating backups stored on CIFS shares in an HP Data Protector environment, the process is the same as described in “Replication in an NFS Backup Environment” on page 12 for NFS. However, the information that needs to be changed in the file you export with the omnidownload command in Step 9 on Page 14 is slightly different. The following is a sample file created by using the omnidownload command: NAME "dd510-3" DESCRIPTION "Data Domain Restorer" HOST yoda2.ae.datadomain.com POLICY Filelibrary TYPE File REPOSITORY "\\dd510-3\backup\HP\a30ca8c054a7c57e750bb850001.fd" "\\dd510-3\backup\HP\a30ca8c054a7c587a50bb850004.fd" "\\dd510-3\backup\HP\a30ca8c054a7c591150bb850007.fd" "\\dd510-3\backup\HP\a30ca8c054a7c59e050bb85000a.fd" "\\dd510-3\backup\HP\a30ca8c054a7c5acf50bb85000d.fd" "\\dd510-3\backup\HP\a30ca8c054a7c5b7050bb850010.fd" "\\dd510-3\backup\HP\a30ca8c054a7c5c3250bb850013.fd" "\\dd510-3\backup\HP\a30ca8c054a7c5d2a50bb850016.fd" 16

HP Data Protector 6.0 Integration Guide

"\\dd510-3\backup\HP\a30ca8c054a7c62bf50bb850019.fd" DIRECTORY "5120 2 0 10 \\dd510-3\backup\HP" MGMTCONSOLEURL ""

Edit the configuration file that you created with the omnidownload command and change the NAME and HOST parameters to reflect the replica appliance device name and name of the replica host server, and change the name of the UNC path in the REPOSITORY section of the file. Starting from the example file shown on the previous page, the next example changes the library information to reflect that the replica CIFS data is on a Data Domain system called dd510-6, connected to host yoda1, and named dd510-6 under devices in the HP Data Protector cell. NAME "dd510-6" DESCRIPTION "Data Domain Restorer" HOST yoda1.ae.datadomain.com POLICY Filelibrary TYPE File REPOSITORY "\\dd510-6\backup\HP\a30ca8c054a7c57e750bb850001.fd" "\\dd510-6\backup\HP\a30ca8c054a7c587a50bb850004.fd" "\\dd510-6\backup\HP\a30ca8c054a7c591150bb850007.fd" "\\dd510-6\backup\HP\a30ca8c054a7c59e050bb85000a.fd" "\\dd510-6\backup\HP\a30ca8c054a7c5acf50bb85000d.fd" "\\dd510-6\backup\HP\a30ca8c054a7c5b7050bb850010.fd" "\\dd510-6\backup\HP\a30ca8c054a7c5c3250bb850013.fd" "\\dd510-6\backup\HP\a30ca8c054a7c5d2a50bb850016.fd" "\\dd510-6\backup\HP\a30ca8c054a7c62bf50bb850019.fd" DIRECTORY "5120 2 0 10 \\dd510-6\backup\HP" MGMTCONSOLEURL ""

HP Data Protector 6.0 Integration Guide

17

MultiPath (Library Sharing) Configuration This procedure explains how to share a VTL library between HP Data Protector servers. HP Data Protector refers to this feature as MultiPath.

Prerequisites •

The VTL must already be configured.

•

The Data Domain systems must use DD OS 4.4.x.x or later. Earlier versions did not support multi-initiator access.

•

Every shared server needs to be in a separate group. This separate groups needs to include the shared library and the initiators of a specific server.

Procedure for Sharing a Library To share a VTL library: 1. On the Data Domain system, enable access to the VTL from each HP Data Protector

server.

a. Configure VTL groups. b. Create a group with the hosts and VTLs to be shared.

For an example of a group configuration, see “Example Group Configuration” on page 22. 2. Establish communication between the HP Data Protector servers that will share the

VTL drives.

The servers should appear under Clients. See Figure 14.

Figure 14: Verifying Client Communication

18

HP Data Protector 6.0 Integration Guide

3. Configure the VTL devices on each HP Data Protector server.

To use the Autoconfiguration wizard: a. Select Devices & Media, select Devices, and right-click and select Auto Configure

Devices.

b. In the Client Systems page of the wizard, select the hosts that will share the VTL.

See Figure 15.

Figure 15: Device Autoconfiguration wizard, Client Systems page

HP Data Protector 6.0 Integration Guide

19

c. In the Devices page of the wizard, choose the library and drives that correspond

to the VTL. See Figure 16.

Figure 16: Device Autoconfiguration wizard, Devices page d. Also in the Devices page of the wizard, confirm that Automatically Configure

MultiPath devices is selected.

4. To use a specific drive for a backup, assign the drive when you define the Backup

Task.

a. Choose the clients and object to back up. b. Select the library and drives. c. Open the Device Properties dialog box by selecting the drive and clicking

Properties > Use Preferred MultiPath Host > hostname.

20

HP Data Protector 6.0 Integration Guide

d. Assign the drive to a client as shown in Figure 17.

Figure 17: Device Properties dialog box

HP Data Protector 6.0 Integration Guide

21

Example Group Configuration Below is an example that shows the group configuration for a HP Data protector server named hp-1 and Media Agents named commvault, ibm-1, and sun-2: # vtl group show all Group: commvault Initiators: Initiator Alias Initiator WWPN ------------------------------------commvault_a 10:00:00:00:c9:71:05:e4 commvault_b 10:00:00:00:c9:71:05:e5 ------------------------------------Devices: Device Name LUN Primary Ports Secondary Ports ----------------------------------------vtl1 changer 0 all all vtl1 drive 1 1 all all ... vtl1 drive 10 10 all all Group: hp-1 Initiators: Initiator Alias Initiator WWPN ------------------------------------hp-1_a 50:06:0b:00:00:38:95:ea hp-1_b 50:06:0b:00:00:38:95:e8 ------------------------------------Devices: Device Name LUN Primary Ports Secondary Ports ----------------------------------------vtl1 changer 0 all all vtl1 drive 1 1 all all ... vtl1 drive 10 10 all all ----------------------------------------Group: ibm-1 Initiators: Initiator Alias Initiator WWPN ------------------------------------ibm-1_a 10:00:00:00:c9:2d:51:52 ------------------------------------Devices: Device Name LUN Primary Ports Secondary Ports ----------------------------------------vtl1 changer 0 all all vtl1 drive 1 1 all all ... vtl1 drive 10 10 all all ----------------------------------------Group: sun-2 Initiators: Initiator Alias Initiator WWPN ------------------------------------sun-2_a 10:00:00:00:c9:3a:f9:49 sun-2_b 10:00:00:00:c9:4b:42:dc 22

In-use Ports -----------all all all

In-use Ports -----------all all all ------------

In-use Ports -----------all all all ------------

HP Data Protector 6.0 Integration Guide

------------------------------------Devices: Device Name LUN Primary Ports Secondary Ports ----------------------------------------vtl1 changer 0 all all vtl1 drive 1 1 all all ... vtl1 drive 10 10 all all -----------------------------------------

In-use Ports -----------all all all ------------

Group: TapeServer Initiators: None Devices: None

HP Data Protector 6.0 Integration Guide

23

24

HP Data Protector 6.0 Integration Guide