openstorage (ost) administration guide · backups and duplications occur. administrators manage...

OpenStorage (OST) Administration Guide

Data Domain, Inc.2421 Mission College Boulevard, Santa Clara, CA 95054866-WE-DDUPE; 408-980-4800

759-0004-0002 Revision AFebruary 26, 2010

Copyright © 2010 Data Domain, Inc. All rights reserved.

Data Domain, the Data Domain logo, and Global Compression are trademarks or registered trademarks of Data Domain, Inc. All other trademarks used or mentioned herein belong to their respective owners.

Data Domain products are protected by one or more of the following patents issued to Data Domain. U.S. Patents 6,928,526; 7,007,141; 7,065,619; 7,143,251; 7,305,532; 7,373,464; 7,424,498; 7,434,015 and other patents and patents pending in USA and other countries.

Disclaimer: The information contained in this publication is subject to change without notice. Data Domain, Inc. makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Data Domain, Inc. shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.

2

About This Guide

This guide explains how to install, configure, and use Data Domain OST with Data Domain systems.

Related Data Domain DocumentsThe following Data Domain documents provide additional information:

• DD OS Release Notes 4.8

• DD OS 4.8 Initial Configuration Guide

• DD OS 4.8 Administration Guide

• DD OS 4.8 Command Reference

• DD OS 4.8 Command Reference Guide

• Data Domain Hardware Guide

• Data Domain Expansion Shelf Hardware Guide

• The Data Domain system installation and setup guides for each of the supported platforms (for example DD880, DD690g, and so forth).

• Symantec NetBackup OpenStorage Best Practices with Data Domain Deduplication.

OST Administration Guide 3

OST Backup Application DocumentationDocumentation for backup applications is available through the Symantec web site.

NetBackup Documentation

From the general Symantec support page, navigate to the NetBackup Server product page and search the knowledge base for Documentation.

Note: To locate a document, enter its title as a search criterion in your favorite search engine.

• NetBackup Shared Storage Guide

• NetBackup Troubleshooting Guide

• NetBackup Commands for UNIX and Linux

• NetBackup Commands for Windows

See these NetBackup documents for more information:

• NetBackup Backup, Archive, and Restore Getting Started Guide

• NetBackup Administrator's Guide for UNIX and Linux (two volumes)

• NetBackup Administrator’s Guide for Windows (two volumes)

• Best Practices for using Storage Lifecycle Policies in NetBackup 6.5.3 and 6.5.4. ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/327648.pdf

Symantec Backup Exec Documentation

This document is installed with the application:

• Symantec Backup Exec 2010 Administrator’s Guide

4

ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/327648.pdf

ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/327648.pdf

OST Backup Application Documentation

Access to Documents at Data DomainThe Documentation page at https://my.datadomain.com/documentation provides access to three categories of documents that are related to use of Data Domain products:

• End-user documents, under Product Documentation.

• Guides for how to integrate Data Domain systems with backup applications, Global Deduplication Arrays, and other applications, under Integration Documentation.

• Matrices that show which components are compatible with each other, under Compatibility Matrices:

• Data Domain hardware product numbers

• Data Domain operating system (DD OS) versions

• Backup applications and other application versions

• Application server and client operating system versions

• Hardware driver versions

To access Data Domain documents:

1. Log into the support portal at: https://my.datadomain.com/documentation.

2. To view end user documents, click Product Documentation and then perform the following steps:

a. Select the Data Domain model from the Platform list and click View.

b. On the row for the correct Data Domain operating system (DD OS) version, click View under Documentation.

c. Click the desired title.

3. To view integration-related documents, perform the following steps:

a. Click Integration Documentation.

b. Select a vendor from the Vendor menu.

c. Select the desired title from the list and click View.


https://mydatadomain.com/documentation

4. To view compatibility matrices, perform the following steps.

a. Click Compatibility Matrices.

b. Select the desired title from product menu and click View.

ConventionsThe following tables describe the typographical conventions used in this guide.The following table describes the typographical conventions used in this guide.

Typeface or Symbol

Usage Examples

Monospace Commands, command options, and parameters and computer output.

Use the config command to manage the Data Domain system configuration settings.

Monospace bold

Commands the user types at the command prompt (#).

Enter:# config setup

Monospace italic bold

Command variables the user types at the command prompt (#).

# log view file_name

Italic Book titles, and variables. Refer to the DD OS 4.8 Command Reference Guide for complete descriptions of DD OS commands.

Pipe (|) and curly braces ({})

Choose (pipe) between a required argument (curly braces) in the CLI.

{arg1 | arg2}

Brackets ([]) and ellipses (...)

One or more (list with commas and elipses) optional (bracket) arguments in the CLI.

[arg1, arg2, ...]

6

Audience

AudienceThis guide is for system administrators who are familiar with Symantec backup applications and general backup administration.

Data Domain SupportTo resolve issues with Data Domain products, contact your contracted support provider or visit us online at https://my.datadomain.com.


Contents

Related Data Domain Documents . . . . . . . . . . . . . . . . . . . 3

OST Backup Application Documentation. . . . . . . . . . . . . . . 4

Access to Documents at Data Domain . . . . . . . . . . . . . . 5

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Data Domain Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Introducing OST. . . . . . . . . . . . . . . . . . . . . . . . . .15Supported Configurations . . . . . . . . . . . . . . . . . . . . . . . 16

2 Installing OST . . . . . . . . . . . . . . . . . . . . . . . . . . .17Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 17

OST and DD OS Upgrades . . . . . . . . . . . . . . . . . . . . . 18

Firewalls and Ports . . . . . . . . . . . . . . . . . . . . . . . . . 18

Enabling OST on a Data Domain System. . . . . . . . . . . . 18

NetBackup Installation . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installing the Plug-In on Media Servers . . . . . . . . . . . . 21

NetBackup Services . . . . . . . . . . . . . . . . . . . . . . . . . 23

NetBackup UNIX Services . . . . . . . . . . . . . . . . . . . 23

NetBackup Windows Services . . . . . . . . . . . . . . . . 23

Backup Exec Installation . . . . . . . . . . . . . . . . . . . . . . . . 24

Installing the Plug-In on Media Servers . . . . . . . . . . . . 24


Backup Exec Services . . . . . . . . . . . . . . . . . . . . . . . .25

Tuning Windows Media Servers for OST Performance. . . . . .26

Uninstalling the Windows Plug-in. . . . . . . . . . . . . . . . . . .27

3 Data Domain OST Features . . . . . . . . . . . . . . . . . 29Distributed Segment Processing . . . . . . . . . . . . . . . . . . .29

Advanced Load Balancing and Failover . . . . . . . . . . . . . . .33

Low-Bandwidth Optimization Option . . . . . . . . . . . . . . . .35

4 OST Configuration . . . . . . . . . . . . . . . . . . . . . . . 37Configuring the Data Domain System . . . . . . . . . . . . . . . .38

Creating Logical Storage Units (LSUs). . . . . . . . . . . . . .38

Configuring Distributed Segment Processing . . . . . . . . .38

Configuring Advanced Load Balancing and Failover. . . . .39

Enabling Low-Bandwidth Optimization . . . . . . . . . . . .40

Configuring a Media Server. . . . . . . . . . . . . . . . . . . . . . .41

NetBackup Configuration. . . . . . . . . . . . . . . . . . . . . .41

Concurrent Connection Limit . . . . . . . . . . . . . . . . .42

Registering Each Data Domain System . . . . . . . . . . .42

Adding Credentials . . . . . . . . . . . . . . . . . . . . . . .43

Creating Disk Pools . . . . . . . . . . . . . . . . . . . . . . .43

Creating Storage Units . . . . . . . . . . . . . . . . . . . . .47

Creating a Backup Policy . . . . . . . . . . . . . . . . . . .50

Configuring Buffers . . . . . . . . . . . . . . . . . . . . . . .52

Configuring Optimized Duplication . . . . . . . . . . . . .54

Using Storage Lifecycle Policies to Automate Optimized Duplication . . . . . . . . . . . . . . . . . . . . . . . . . .55

10

Backup Exec Configuration . . . . . . . . . . . . . . . . . . . . 59

Creating a Logon Account . . . . . . . . . . . . . . . . . . 60

Configuring Devices . . . . . . . . . . . . . . . . . . . . . . 61

5 Using the OST Commands . . . . . . . . . . . . . . . . . . .65ost Command Options . . . . . . . . . . . . . . . . . . . . . . . . . 66

enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

destroy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

ifgroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

ifgroup add interface . . . . . . . . . . . . . . . . . . . . . 67

ifgroup del interface . . . . . . . . . . . . . . . . . . . . . 67

ifgroup disable . . . . . . . . . . . . . . . . . . . . . . . . . 68

ifgroup enable . . . . . . . . . . . . . . . . . . . . . . . . . . 68

ifgroup show config . . . . . . . . . . . . . . . . . . . . . . 68

ifgroup reset . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

ifgroup status . . . . . . . . . . . . . . . . . . . . . . . . . . 68

lsu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

lsu create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

lsu delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

lsu show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69


opt-dup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

opt-dup option reset . . . . . . . . . . . . . . . . . . . . . .70

opt-dup option set low-bw-optim . . . . . . . . . . . . . .70

opt-dup option show . . . . . . . . . . . . . . . . . . . . . .70

opt-dup reset stats . . . . . . . . . . . . . . . . . . . . . . .70

opt-dup show active . . . . . . . . . . . . . . . . . . . . . .71

opt-dup show history . . . . . . . . . . . . . . . . . . . . . .71

opt-dup show image-history . . . . . . . . . . . . . . . . .72

opt-dup show performance . . . . . . . . . . . . . . . . . .73

opt-dup show stats . . . . . . . . . . . . . . . . . . . . . . .73

option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

option set boost . . . . . . . . . . . . . . . . . . . . . . . . .74

option reset . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

option show . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

reset user-name . . . . . . . . . . . . . . . . . . . . . . . . .75

reset stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

set user-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

show connections . . . . . . . . . . . . . . . . . . . . . . . .76

show histogram . . . . . . . . . . . . . . . . . . . . . . . . . .77

show image-duplication active . . . . . . . . . . . . . . . .78

show stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

show user-name . . . . . . . . . . . . . . . . . . . . . . . . .78

status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

6 Administration. . . . . . . . . . . . . . . . . . . . . . . . . . 81Data Domain System Administration. . . . . . . . . . . . . . . . .81

12

Optimized Duplication Version Compatibility . . . . . . . . 81

Removing Advanced Load Balancing/Failover Configuration82

Modifying an Interface Group . . . . . . . . . . . . . . . . . . 83

NetBackup Administration . . . . . . . . . . . . . . . . . . . . . . 85

Network Time-Outs . . . . . . . . . . . . . . . . . . . . . . 86

Duplicate Images (NBU Workaround) . . . . . . . . . . . 87

Grouping Storage Units to Provide Failover . . . . . . . 87

Backup Exec Administration . . . . . . . . . . . . . . . . . . . . . 89

7 Basic Troubleshooting . . . . . . . . . . . . . . . . . . . . .91General Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 92

NetBackup Troubleshooting . . . . . . . . . . . . . . . . . . . . . 93

Unable to Delete the Data Domain System . . . . . . . . . 93

Error Logging on the Media Servers . . . . . . . . . . . . . . 95

Resolving Failed Backups on Media Servers . . . . . . . . . 97

NetBackup Backup Jobs Fail on Solaris Media Servers . 100

Optimized Duplication Job Fails . . . . . . . . . . . . . . . 101

Backup Exec Troubleshooting . . . . . . . . . . . . . . . . . . . 102

Basic Troubleshooting . . . . . . . . . . . . . . . . . . . . . . 102


1 Introducing OST

OpenStorage (OST), which is a feature of Symantec’s backup and recovery products, enables media servers to communicate with storage systems without the need for storage systems to emulate tape.

Data Domain OpenStorage (OST) software consists of a plug-in that you install on each media server that communicates with a Data Domain storage server, which can be a Data Domain controller, a gateway, or a Global Deduplication Array.

The backup application system sets policies that control when backups and duplications occur. Administrators manage backup, duplication, and restores from a single console and can use all of the Data Domain system’s features, including WAN-efficient replicator software. The application manages all images (collections of data) in the catalog, even those created by the Data Domain system.

The Data Domain system exposes pre-made disk volumes called Logical Storage Units (LSUs) to an OST-enabled media server. Multiple media servers, each with the Data Domain OST plug-in, can use the same LSU on a Data Domain system as a storage server. Each media server can run a different operating system, provided that it is supported by Data Domain.

Figure 1-1 shows an example configuration of OST using NetBackup.


Introducing OST

Figure 1-1: OST Configuration Using NetBackup

Supported ConfigurationsData Domain supports OST on the following Data Domain systems:

• Data Domain systems (DD5xx, DD6xx, DD880)

• Data Domain gateway systems (DD560g, DD580g, DD690g, DD880g)

• Data Domain Global Deduplication Array systems

The plug-in version must be compatible with your Data Domain and backup application configurations. Data Domain does not support combinations other than those detailed in the Data Domain OST Compatibility List, which is available from the Data Domain Support portal (https: //my.datadomain.com). Navigate to the Documentation > Compatibility List page and select Data Domain OST Compatibility List.

16

2 Installing OST

This chapter covers the following topics:

• Installation Overview on page 17

• NetBackup Installation on page 20

• Backup Exec Installation on page 24

• Tuning Windows Media Servers for OST Performance on page 26

• Uninstalling the Windows Plug-in on page 27

Installation OverviewThe overall steps for installing OST are as follows:

1. Obtain the license required to enable OST on the Data Domain system. You can purchase an OpenStorage license key for a Data Domain system directly from Data Domain.

• The basic license allows you to back up and restore image data.

• A separate replication license enables you to perform optimized duplication. You must obtain a replication license for both the source and destination Data Domain systems.

2. Enable OST on the Data Domain system.

3. Install the Data Domain OST plug-in software on each media server.

4. After completing the installation steps described in this chapter, configure OST as described in Chapter 3.


Installing OST

OST and DD OS UpgradesIf you upgrade the DD OS to a version with increased OST functionality, you must also upgrade the OST plug-in. You must perform the upgrade as described in Installing the Plug-In on Media Servers on page 21.

Firewalls and PortsThe Data Domain system as it is initially configured does not work through a firewall (a media server to a Data Domain system, or from one Data Domain system to another). If you need the Data Domain system to work in the presence of a firewall, contact your contracted support provider.

The following ports must be open in a firewall for OST backups and optimized duplication to work:

• TCP 2049 (NFS)

• TCP 2051 (Replication)

• TCP 111 (NFS portmapper)

• TCP xxx (select a random port for NFS mountd)

Enabling OST on a Data Domain SystemEvery Data Domain system that is enabled for OpenStorage must have a unique name. You can use the Data Domain system’s DNS name, which is always unique.

Enable OST

1. On the Data Domain system, log in as an administrative user.

2. Verify that the file system is enabled and running by entering:

# filesys status

The file system is enabled and running.

18

Installation Overview

3. Add the OST license using the license key that Data Domain provided:

# license add license_key

License “ABCE-BCDA-CDAB-DABC” added.

4. Set the OST user by entering:

# ost set user-name ost-user

5. Disable and then re-enable OST for this user-name modification to take effect. Enter:

# ost disable

6. Enable OST by entering:

# ost enable

OST enabled

Notes:

Only one OST user can be configured for OST access on a Data Domain system at a time. The username and password must have already been set up on the Data Domain system using the DD OS CLI command: user add username [password password]

For example, to add a user with a login name of jsmith and a password of usr256 with administrative privilege, enter:

# user add jsmith password usr256

• The user must be configured in the backup application in order to connect to the Data Domain system.

Backup applications consists of two separate kinds of servers—media servers and a master server that manages clients and media servers. The master server can also be a media server. The OST plug-in is installed on the media server.


Installing OST

NetBackup InstallationThis section describes the common commands used to monitor and administer an OST installation in the NetBackup environment.

Note: Commands that run on the command line can be entered on either the master or the media server. If you run commands from the master server, use the -media_server option to tell NetBackup where to direct the operation that queries the plug-in about the storage server’s properties.

This guide uses the NetBackup commands located in the following directories, which you need to add to your UNIX or Windows PATH.

Add these directories to the UNIX PATH

/usr/openv/netbackup/bin

/usr/openv/netbackup/bin/admincmd

/usr/openv/volmgr/bin

Add these directory locations to the UNIX PATH

$ export PATH=$PATH:/usr/openv/netbackup/bin: /usr/openv/netbackup/bin/admincmd:/usr/openv/volmgr/bin

Add these directory locations to the Windows PATH

$ PATH=%PATH%;C:\Program Files\Veritas\NetBackup\bin; C:\Program Files\Veritas\NetBackup\bin\admincmd; C:\Program Files\Veritas\Volmgr\bin

20

NetBackup Installation

Installing the Plug-In on Media ServersThe OST plug-in software must be installed on media servers that need to access the Data Domain system. When you upgrade the UNIX OST plug-in, the previous version of the plug-in is overwritten; therefore, you do not have to remove it.

Install the UNIX plug-In 1. Download the latest version of the OST plug-in from the Data

Domain Support web site.

2. Save the file on the media server in a location of your choice.

3. Stop the backup application’s Remote Manager and Monitor Service (nbrmms) process if it is running by entering:

# nbrmms -terminate

4. Install the OST plug-in (a set of libraries in a gtar package called OST.)

5. Use the tar command to uncompress the file:

# tar -vxf filename

6. The package also contains an installation script called install.sh, which verifies whether or not nbrmms has been stopped before starting the installation. Enter:

# install.sh -d directorypath

The directory path is optional. If you do not specify a directory path, the script uses /usr/openv/lib/ost-plugins, which is where the backup application normally looks for packages. The shared library files that the script installs are libstspiDataDomain.so and libstspiDataDomainMT.so.

The plug-in recognizes DataDomain as the Data Domain vendor prefix.

7. If the plug-in already exists, you are prompted to enter y to proceed.

8. Restart the backup application’s nbrmms process by entering:

# nbrmms


Installing OST

Install the Windows plug-In The Windows plug-in installer is libstspiDataDomainSetup.exe. It supports 32- and 64-bit Windows plug-ins.

Prepare for installation

1. Download the latest version of the Windows OST plug-in installer from the Data Domain Support web site.

2. Double-click the set-up executable to launch the installer.

The installer determines whether NetBackup is installed and whether its respective services are running. If the installer detects a service running it displays a message to this effect and exits.

3. Before starting the installation, stop any NetBackup services. Follow the instructions given in NetBackup Windows Services on page 23 to stop the service.

Start the installation

1. If the services have been stopped, the installer displays the license agreement. Read the terms and Click I Agree to continue.

2. In the Choose Components dialog box, select either the 32- or 64-bit version of the plug-in for installation.

3. In the Choose Install Location dialog box, the correct destination folder is shown. This should not be changed. Click Install to start the installation.

A progress bar monitors the installation.

4. When the Installation is complete, you can click the Show details button to view the files installed and their location.

5. Restart all services. See NetBackup Windows Services on page 23.

6. Tune the Windows media server for OST performance. See Tuning Windows Media Servers for OST Performance on page 26.

22

NetBackup Installation

NetBackup ServicesFollow the instructions for starting, stopping, and restarting UNIX or Windows services.

NetBackup UNIX Services

Stop UNIX services

Enter:

# nbrmms -terminate

Start or restart UNIX services

Enter:

# nbrmms

NetBackup Windows Services

Start, stop, or restart Windows services

1. Go to Start > Control Panel > Administrative Tools > Services.

2. In the Services window, services are listed in alphabetical order by name. Locate the name NetBackup Remote Manager and Monitor Service. Its Status field shows the state of the service.

3. Select the service and right-click.

4. The menu that displays has options to Stop, Start, or Restart the service. Select the appropriate menu option.


Installing OST

Backup Exec InstallationThis section covers the following topics:

• Installing the Plug-In on Media Servers on page 24

• Backup Exec Services on page 25

Installing the Plug-In on Media ServersThe OST plug-in software must be installed on media servers that need to access the Data Domain system.

Install the Windows plug-InThe Windows plug-in installer is libstspiDataDomainSetup.exe. It supports 32- and 64-bit Windows plug-ins.

Prepare for installation

1. Download the latest version of the Windows OST plug-in installer from the Data Domain Support web site.

2. Double-click the set-up executable to launch the installer.

The installer determines whether Backup Exec is installed and whether its respective services are running. If the installer detects a service running it displays a message to this effect and exits.

3. Before starting the installation, stop any Backup Exec services. Follow the instructions given in Backup Exec Services on page 25 to stop the service.

Start the installation

1. If the services have been stopped, the installer displays the license agreement. Read the terms and Click I Agree to continue.

2. In the Choose Components dialog box, select either the 32- or 64-bit version of the plug-in for installation.

24

Backup Exec Installation

3. In the Choose Install Location dialog box, the correct destination folder is shown. This should not be changed. Click Install to start the installation.

A progress bar monitors the installation.

4. When the Installation is complete, you can click the Show details button to view the files installed and their location.

5. Restart all services. See Backup Exec Services on page 25.

6. Tune the Windows media server for OST performance. See Tuning Windows Media Servers for OST Performance on page 26.

Backup Exec Services

Start, Stop, or Restart Windows services

1. Within Backup Exec, go to Tools > Backup Exec Services.

2. In the Backup Exec Services Manager window, select the server in the list and click the appropriate services button on the right side of the dialog box.

3. When the processing of the services is completed, click OK in the Backup Exec Services dialog box.


Installing OST

Tuning Windows Media Servers for OST Performance

This procedures applies to NetBackup and Backup Exec.

Tune the Windows media servers1. Within REGEDT32, navigate to

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\Tcpip\Parameters\.

2. Add a new DWORD value named GlobalMaxTcpWindowSize and set the value to 2097152 (decimal).

3. Add a new DWORD value named TcpWindowSize and set the value to 2097152 (decimal).

4. Add a new DWORD value named Tcp1323Opts and set the value to 1.

5. Restart the Windows server.

Note: To address Windows 2003 SP2 network performance issues on 32-bit Windows Servers 2003, search the Microsoft Support knowledge base for related information.

26

Uninstalling the Windows Plug-in

Uninstalling the Windows Plug-inThis procedures applies to NetBackup and Backup Exec.

Uninstall the Windows plug-in1. Stop the backup application’s services.

2. Do one of the following:

a. Uninstall the Data Domain OpenStorage plug-in via Window’s Control Panel uninstall/remove program feature (as you would uninstall a typical Windows program).

b. Double-click libstspiDataDomainUninstall.exe, which was installed in the same directory as the plug-in. Click Uninstall. After the uninstall, click Show details to view which files were removed.


Installing OST

28

3 Data Domain OST Features

These Data Domain OST features apply to NetBackup and Backup Exec:

• “Distributed Segment Processing” on page 29

• “Advanced Load Balancing and Failover” on page 33

• “Low-Bandwidth Optimization Option” on page 35

For instructions on how to configure these features, see Chapter 4, OST Configuration.

Distributed Segment ProcessingThe Data Domain OST Plug-in 2.0 supports two modes of operation. In the first mode, the Data Domain OST plug-in sends all of the data directly to the Data Domain system over the LAN. The Data Domain system then deduplicates the data and stores it on disk. This approach is referred to as OST and was the only mode previously available until DD OS 4.7. Data Domain OST Plug-in 2.0 introduces the Distributed Segment Processing feature. This feature requires DD OS 4.8.

OST Mode

In this mode, the OST plug-in sends the data directly to the Data Domain system over the LAN. The Data Domain system then segments, deduplicates, and compresses the data before it is written to the disk. A high-level data flow for OST on a single-controller Data Domain system is shown in Figure 3-1. The Data Domain OST plug-in runs on the media server.


Data Domain OST Features

Figure 3-1: High-level Data Flow for OST

Distributed Segment Processing

Distributed Segment Processing adds functionality to the Data Domain OST plug-in to distribute the deduplication process, which avoids sending duplicate data to the Data Domain system configured as a storage server.

Distributed Segment Processing provides the following benefits:

• Potentially higher throughput versus sending all of the data over the LAN to the Data Domain system because the OST plug-in sends only unique data to a Data Domain System. The throughput improvements depend on the redundant nature of the data being backed up. In general, the higher the redundancy, the greater the throughput.

• Allows utilizing existing 1 GbE infrastructure to achieve higher throughput than is physically possible over 1 GbE links. The network bandwidth requirements are significantly reduced since only the unique data is sent over the LAN to the Data Domain systems.

• Failed backups can potentially go much faster. If a large backup fails in the middle or towards the end, when it is restarted by the

30

Distributed Segment Processing

backup application, the data t already sent to the Data Domain system does not have to be resent. This results in faster completion of the backup on retry.

The data flow for a single-controller Data Domain system with the Distributed Segment Processing option enabled is shown in Figure 3-2.

Figure 3-2: High-level Data Flow with Boost option enabled

In the configuration shown in Figure 3-2, the Data Domain OST plug-in breaks up the backup image data into segments and checks with the Data Domain system for segments that are already stored on the Data Domain system, and sends only unique segments. The deduplication process is distributed between the OST plug-in and the Data Domain system. The OST plug-in’s handling of data is transparent to the backup application, and the plug-in does not store any data on the media server.

For Data Domain Global Deduplication Array with two controllers, the data flow is as shown in Figure 3-3. The incoming data for a backup image is distributed between the two controllers based on a mapping maintained by the Data Domain controller designated as master.



Note: See the Data Domain Global Deduplication Administration Guide for more details on configuring a Global Deduplication System.

The OST plug-in sends chunks directly to the corresponding Data Domain controller based on the mapping by breaking it up into smaller segments and sending only the segments that are not stored on the Data Domain system.

Figure 3-3: High-level Data Flow for a Global Deduplication System with Boost Option Enabled

Note: The OST plug-in negotiates the local compression algorithm with the Data Domain system. The default local compression configured on a Data Domain system is lz.

See the DD OS Administration Guide for more information about local compression and its configuration.

You manage Distributed Segment Processing via the ost option commands. Data Domain recommends that you use Distributed Segment Processing if your network connection is 1 Gb Ethernet. See “Configuring Distributed Segment Processing” on page 38.

32

Advanced Load Balancing and Failover

Advanced Load Balancing and FailoverNetBackup and Backup Exec allow only one IP address per storage server. For Data Domain systems that require multiple 1 GbE links to obtain full system performance, it is necessary to set up multiple storage servers on the Data Domain systems (one per interface) and target the backup policies to different storage servers to spread the load on the interfaces.

The Advanced Load Balancing and Failover feature allows for combining multiple Ethernet links into a group. One of the interfaces in the group is registered with the backup application. The plug-in negotiates with the Data Domain system on the interface registered with the backup application to obtain an interface to send the data. The load balancing provides higher physical throughput to the Data Domain system compared to configuring the interfaces into a virtual interface using Ethernet level aggregation.

The Data Domain system load balances the connections coming in from multiple media servers on all the interfaces in the group. The load balancing is transparent to the backup application. Because Advanced Load Balancing and Failover works at the OST plug-in and DD OS layer, it is seamless to the underlying network connectivity and supports both physical and virtual interfaces.

The data transfer is load balanced based on the number of connections outstanding on the interfaces. Only connections for backup and restore jobs are load balanced.This feature is supported with OST plug-in 2.0 or later communication with a Data Domain system that runs DD OS 4.8 or later.

Figure 3-4 shows an example high-level configuration diagram. The interface marked in red is registered with the backup application.



Figure 3-4: High-level Configuration Diagram

Benefits of Advanced Load Balancing and Failover are as follows:

• Eliminates the need to register multiple storage servers (one for each interface) with the backup application, which can potentially simplify installation management.

• If one of the interfaces in the group goes down while the Data Domain system is still operational, the subsequent incoming backup jobs are routed to the available interfaces.

Note: The in-flight backup jobs to the interface that went down will fail and need to be restarted.

• The backup and restore jobs are automatically load balanced on multiple interfaces in the group, which can potentially result in higher utilization of the links.

For more information, see “Configuring Advanced Load Balancing and Failover” on page 39.

34

Low-Bandwidth Optimization Option

Low-Bandwidth Optimization OptionThe low-bandwidth optimization option reduces the WAN bandwidth utilization. It is useful if optimized duplication is being performed over a low-bandwidth network (WAN) link. This feature provides additional compression during data transfer.

Low-bandwidth compression is available to Data Domains systems with an installed Replication license. The option is enabled on a per Data Domain system basis and applies to all optimized duplication jobs on that system.

For more information, see “Enabling Low-Bandwidth Optimization ” on page 40 and the discussion of this topic in the DD OS Administration Guide.



36

4 OST Configuration


• Configuring the Data Domain System on page 38

• Creating Logical Storage Units (LSUs) on page 38

• Configuring Distributed Segment Processing on page 38

• Configuring Advanced Load Balancing and Failover on page 39

• Enabling Low-Bandwidth Optimization on page 40

• Configuring a Media Server on page 41

• NetBackup Configuration on page 41

• Backup Exec Configuration on page 59


OST Configuration

Configuring the Data Domain SystemYou need to create a Logical Storage Unit (LSU) for each Data Domain controller enabled for OpenStorage. LSUs correspond to disk pools on the media server. Disk pools are collections of disk volumes that the backup application administers as single entities.

Each LSU is a top-level subdirectory of the /backup/ost directory; there is no hierarchy among LSUs.

Note: The following configuration procedures apply to NetBackup and Backup Exec.

Creating Logical Storage Units (LSUs)

Create LSUs

1. On the Data Domain controller, enter:

# ost lsu create lsu_name

Each LSU name must be unique.

2. Repeat the above step for each OST-enabled Data Domain controller.

Configuring Distributed Segment ProcessingThe Distributed Segment Processing option is configured on the Data Domain system and applies to all the media servers and the Data Domain OST plug-ins installed on them. If Distributed Segment Processing is disabled on the Data Domain system, then the data flow from the media servers is as shown in Figure 3-1 on page 30. If Distributed Segment Processing is enabled, then the data flows as shown in Figure 3-2 on page 31 for single controller Data Domain systems and Figure 3-3 on page 32 for Global Deduplication Array systems.

The option can be configured using the following command:

# ost option set boost {enabled | disabled}

Note: Enabling or disabling the Distributed Segment Processing option does not require a restart of the Data Domain file system.

38

Configuring the Data Domain System

Distributed Segment Processing is supported with OST plug-in 2.0 or later communicating with a Data Domain system that is running DD OS 4.8 or later.

Distributed Segment Processing is enabled by default on a system initially installed with DD OS 4.8. If a system is upgraded from DD OS 4.6.x or 4.7.x to DD OS 4.8, and the OST license is installed at the time of the upgrade, Distributed Segment Processing is not automatically enabled.

Distributed Segment Processing is enabled by default on Global Deduplication Array configurations and cannot be disabled.

Configuring Advanced Load Balancing and FailoverSteps for configuring an interface group on the Data Domain system by adding four existing interfaces to the group, and registering the Data Domain with the backup application are described below.

Configure Advanced Load Balancing and Failover

1. Add the interfaces into the group:

# ost ifgroup add interface 192.168.1.1




Note: Only one default interface group can be created in DD OS 4.8, and this group cannot be named.

2. Select one of the above interfaces to register with the backup application. It is recommended that you create one failover interface and register that interface with the backup application.

Data Domain recommends that the interface be registered with a resolvable name using DNS or any other name resolution mechanism. Using NetBackup and assuming that 192.168.1.1 is


OST Configuration

named dd22.abc.com, execute the following command on the media server:

nbdevconfig -creatests -st 9 -stype DataDomain -storage_server dd22.abc.com -media_server load64

Note: The interface registered with the backup application is used by the backup application and the Data Domain OST plug-in to communicate with the Data Domain system. If this interface is not available, then no backups to that Data Domain system are possible.

3. Enable the feature on the Data Domain system:

# ost ifgroup enable

4. Verify the configuration Data Domain system:

# ost ifgroup show config

Interface

-------------

192.168.1.1

192.168.1.2

192.168.1.3

192.168.1.4

-------------

Note: You manage Advanced Load Balancing and Failover via the ost ifgroup commands. See Chapter 5, Using the OST Commands.

After the interface group is setup, you can add or delete interfaces from the group. See Modifying an Interface Group on page 83.

Enabling Low-Bandwidth Optimization To enable the low-bandwidth option, enter:

# ost opt-dup option set low-bw-optim enabled

Low bandwidth optimization enabled for optimized duplication.

Note: Enabling or disabling the low-bandwidth option does not require a restart of the Data Domain file system. After enabling it,

40

Configuring a Media Server

however, you need to run a full cleaning cycle on the Data Domain system for it to be effective.

See ost opt-dup on page 69 for more details on how to monitor and manage low-bandwidth optimization.

No configuration changes are necessary on the media server as this feature is transparent to the backup applications. Turning on this feature takes additional resources (CPU and memory) on the Data Domain system, so it is recommended that this option be used only when optimized duplication is being done over low-bandwidth networks with less than 6 Mbps aggregate bandwidth.

Note: The low-bandwidth option for optimized duplication is supported only for standalone Data Domain systems.

Configuring a Media ServerMedia server configuration depends on the backup application being used. See the appropriate configuration section.

• NetBackup Configuration on page 41

• Backup Exec Configuration on page 59

NetBackup ConfigurationNote: The examples in this chapter assume the following configuration:

• A media server with the name load64 that runs NBU 6.5.1.

• OST-enabled Data Domain systems named dd22 and dd23.

Media server configuration consists of the following procedures:

• registering each Data Domain system;

• adding credentials for each media server that is to communicate with a Data Domain system;

• creating disk pools;

• creating storage units, which are collections of disk pools; and

• setting backup policies.


OST Configuration

Follow these recommended practices:

• To avoid the need for frequent DNS lookups, add every media server host/IP address to the Data Domain system using the net hosts add ipaddr {host | "alias host"}... command.

Note: DNS reverse lookup has been added for every media server accessing the Data Domain system as of DD OS 4.6.3.

• To avoid DNS lookup for every OST job, also add the Data Domain system IP address into the media server’s /etc/hosts file.

Note: Commands that run on the command line can be entered on either the master or the media server. If you run commands from the master server, use the -media_server option to tell NBU where to direct the operation that queries the plug-in about the storage server’s properties.

Concurrent Connection Limit

With NetBackup, the default number of concurrent connections (jobs) from a single media server is 64. To increase this number, contact your Data Domain systems engineer.

Registering Each Data Domain System

Register the Data Domain systems

1. On the media server, start the backup application’s services. See NetBackup Services on page 23.

2. Verify that the plug-in is detected by the backup application by entering:

# bpstsinfo -pi

The output shows the vendor version, which is the plug-in version, and the build version, which is the OST API version.

3. Register a Data Domain system by entering:

# nbdevconfig -creatests -st 9 -stype DataDomain -storage_server dd22 -media_server load64

42


In this case, the storage_server can be either an IP address or a hostname, such as dd22.

4. Repeat the above procedure for each OST-enabled Data Domain system.

Adding Credentials

Add credentials

1. On a media server that is to communicate with a Data Domain system, enter:

# tpconfig -add -storage_server dd22 -stype DataDomain -sts_user_id username -password password

2. Repeat the above step for each media server that is to communicate with a specific Data Domain system.

After you add the credentials, the backup application does the following:

• Saves the credentials so the media server can log into the Data Domain system.

• Configures the media server as a data mover that can transfer data between the primary storage (the backup application’s client) and the storage server (the Data Domain system). The backup application maintains an access path between the media server and the storage server.

Creating Disk Pools

Disk pools are collections of disk volumes that the backup application administers as single entities. Disk pools correspond to Logical Storage Units (LSUs).

Note: Each disk pool requires a unique name.

The backup application provides a command line interface (CLI) and a graphical user interface (GUI). You can use either to create disk pools.


OST Configuration

Create a disk pool using the CLI

1. The backup application’s Remote Manager and Monitor Service (nbrmms) must be running. To restart it, enter:

# nbrmms

2. Obtain the identity of the LSU on the Data Domain system (dd22) by entering:

# nbdevconfig -previewdv -storage_server dd22 -stype DataDomain > /tmp/dvlist

3. Create a disk pool using the information obtained from the previous command by entering:

# nbdevconfig -createdp -dp dd22_lsu1_dp -stype DataDomain -storage_servers dd22 -dvlist /tmp/dvlist

The disk pool name must be unique.

Output similar to the following is displayed:

Disk pool dd22_lsu1_dp has been successfully created with 1 volume.

Create a disk pool using the GUI

1. Open the NetBackup Administration Console’s Devices window.

44


2. In left pane of this window, expand the Media and Device Management node. Expand the Devices node. Right-click Disk Pools. Select New Disk Pool from the menu.


OST Configuration

3. The Disk Pool Configuration Wizard is displayed. Select the Data Domain system from the Storage server list, and click Next.

4. Select (check) the LSU in the Volume Name list, and click Next.

46


5. In the Disk Pool Properties window, enter a unique name for the disk pool in the Disk Pool name text box. Click Next.

6. After creating the disk pool, you are given the option of continuing to use the GUI to create a storage unit, which is a collection of disk pools. For instructions, see Creating Storage Units on page 47.

Creating Storage Units

A storage unit contains a disk pool. Multiple storage units can be grouped together into a Storage Unit Group. You can create storage units using either the CLI or the GUI.

Note: Each storage unit requires a unique name.

Create storage units using the CLI

Enter a command similar to the following:

# bpstuadd -label dd22_lsu1_su -dp dd22_lsu1_dp -host load64a -M load64a

Note: There is no output from this command.


OST Configuration

Create storage units using the GUI

1. Open the NetBackup Administration Console’s Storage window.

2. In the left pane, expand the NetBackup Management node. Under the Storage node, right-click Storage Units, and select New Storage Unit from the menu.

48


3. In the New Storage Unit dialog box, enter a unique name for the new storage unit.

4. For the Storage unit type, select Disk from the list.

5. For the Disk type, select OpenStorage (DataDomain) from the list.

6. For the Disk Pool, select the desired disk pool from the list.

7. Select the media servers that can access this storage unit.

• If any media server is allowed to access the storage unit, select Use any available media server.

• If a storage unit needs to be visible to a select set of media servers, select (check) the name of each in the Media Servers list.

Note: If a server does not appear in the list, verify that its Data Domain OST plug-in has been installed and that its login credentials have been configured.

8. Click OK.


OST Configuration

Creating a Backup Policy

You can initiate backups manually at any time. Optionally, you can set up a backup policy, which initiates backups automatically according to the conditions you specify. You can set up a backup policy using either the command line interface (CLI) or the graphical user interface (GUI).

When the policy is run, the backup application selects a media server that has been configured as a data mover.

Create a backup policy using the CLI

Enter commands similar to the following:

# bppolicynew mypolicy

# bpplinfo mypolicy -set -v -residence dd22_lsu1_su

<2>bpplinfo: INITIATING: version NetBackup 6.5 created: 2007072322 <2>bpplinfo: EXIT status = 0

# bpplsched mypolicy -add Fullbackup -st FULL

# /bpplclients mypolicy -add load64a Linux SuSE2.6

# bpplinclude mypolicy -l -add /etc

# bpplinclude mypolicy -l -add /home

Create a backup policy using the GUI

1. Open the Administration Console’s Policies window.

2. In the left pane of the window, expand the NetBackup Management node. Right-click Policies and select New Policy from the menu.

50


3. In the Change Policy dialog box, set your policies following these guidelines:

• Do not select compression.

• Select the desired lifecycle policy from the Policy storage list.


OST Configuration

Note: The icons for storage unit (su) and storage lifecycle policy differ.

Configuring Buffers

You can set the number and size of various buffers, but cannot change their size limits. The location for these files depends on your operating system.

• The UNIX file location is /usr/openv/netbackup.

• The Windows file location is install_path\netbackup\db\config.

For best performance, set the SIZE_DATA_BUFFERS and SIZE_DATA_BUFFERS_DISK to 262144.

Create buffer files

To set the number and size of buffers, create the following files, as appropriate for your operating system.

NET_BUFFER_SZ

• Description: TCP/IP socket buffer size

• Media: N/A

52


• Default on UNIX: 32,032

• Default on Windows: 32,032

NUMBER_DATA_BUFFERS

Note: The number must be a power of two.

• Description: Number of shared data buffers.

• Media: Tape

• Default on UNIX: 8/4 (Non-multiplexed/multiplexed.)

• Default on Windows: 16/8 (Non-multiplexed/multiplexed.)

NUMBER_DATA_BUFFERS_RESTORE


• Media: Tape



NUMBER_DATA_BUFFERS_DISK

Note: The number must be a power of two.


• Media: Disk



SIZE_DATA_BUFFERS

Note: The size must be a multiple of 32 KB. The default used when this file does not exist is 32 KB. The maximum value supported by the Data Domain plug-in is 1 MB.

The default value when the file exists, and the recommended value for best performance is 256 KB.

• Description: Size of shared data buffers.


OST Configuration

• Media: Tape

• Default on UNIX: 64 KB

• Default on Windows: 64 KB

SIZE_DATA_BUFFERS_DISK

Note: The size must be a multiple of 32 KB.The default used when this file does not exist is 32 KB. The maximum value supported by the Data Domain plug-in is 1 MB.

The default value when the file exists, and the recommended value for best performance is 256 KB.

• Description: Size of shared data buffers.

• Media: Disk



SIZE_DATA_BUFFERS_NDMP

• Description: Buffer size for NDMP backups.

• Media: N/A



Configuring Optimized Duplication

The Data Domain OST plug-in enables a media server to specify a duplication process and delegate its execution to the Data Domain system. This sharing has the following advantages:

• The backup application system retains control of creating and duplicating backup images and keeps track of all copies in its catalog, which ensures easy and efficient recovery.

• Optimized duplication removes the media server from having to create duplicates of backup images, which reduces the load on the backup application system and frees it for other work.

• The Data Domain system uses its efficient replication process for deduplicated data. The process is optimized for Wide Area

54


Networks (WANs), which reduces the overall load on the WAN.

Notes:

Prior to NetBackup version 6.5.4, when an optimized duplication job failed, duplication job retry attempted to use conventional duplication. This resulted in sending the fully inflated complete backup image from the source OpenStorage storage unit through one, or possibly two, NetBackup media servers to the destination OpenStorage storage unit.

NetBackup version 6.5.4, by default, does not retry a failed optimized duplication job unless it was initiated by means of a Storage Lifecycle Policy. When retried via a Storage Lifecycle Policy, the job attempts to use optimized duplication only. The default behavior can be overridden by configuring NetBackup to retry with conventional duplication. See the Veritas NetBackup™ Shared Storage Guide UNIX, Windows, Linux Release 6.5.4 document for detailed information.

Data Domain recommends that you add the destination Data Domain system’s IP address to the source Data Domain system using the net hosts add ipaddr {host | "alias host"}... command.

Note: All media servers, source and destination, must have permission to access both Data Domain systems. It is recommended that you add all of the media servers that need to access a Data Domain system to it using the net hosts add command.

Using Storage Lifecycle Policies to Automate Optimized Duplication

A storage lifecycle policy consists of a list of destinations for backup images and a retention period for each image. A lifecycle process creates, retains, and finally expires the images. Using storage lifecycle policies allows you to specify different retention periods for the initial backup and for the duplicate copies. For example, you might specify one retention period for the original local backup and another for a duplicate at a disaster recovery site.


OST Configuration

Notes:

If there is a preferred link or IP address for sending the optimized duplication data between two Data Domain storage servers, use that link or address when creating the destination storage server.

Should you ever want to start optimized duplication manually, use the NBU CLI command bpduplicate, which is described in your Symantec documentation.

Create a storage lifecycle policy

This example creates a lifecycle policy that backs up to an OST-enabled Data Domain system and then creates a duplicate copy on another OST-enabled Data Domain system. There are two storage destinations. The first serves as backup to the first OST-enabled Data Domain system. The second storage destination is used for duplication to the second OST-enabled Data Domain system.

1. Open the NetBackup Administration Console’s Storage window.

2. In left pane of the window, expand the NetBackup Management node and then the Storage node. Right-click Storage Lifecycle Policies. Select New Storage Lifecycle Policy from the menu.

56


3. In the New Storage Lifecycle Policy dialog box, enter a lifecycle policy name in the Storage lifecycle policy name text box.

4. Click the Add button to add a new storage destination to the list.

5. In the New Destination dialog box, select either Backup or Duplication, depending on how the policy is to be used. In this example, select Backup.

6. Select the storage unit (dd22_lsu1_su) from the list.

7. Select one of the retention types:

• Fixed

Fixed retention means that the backup is retained for a specific period of time. Afterwards, NetBackup deletes information about the expired backup, and the files in the


OST Configuration

backup become unavailable to restore operations. Fixed retention enables you to use different retention periods for backup copies on local and remote Data Domain systems. For example, you might retain backups at the local Data Domain system for one week and the copies at a remote disaster recovery Data Domain system for four weeks.

• Staged capacity managed

This type means that the Data Domain system serves as a staging device before it is duplicated to a final destination. The Data Domain system must be configured to use disk staging. S

Note: Disk staging is supported in DD OS 4.6 and later.

• Expire after duplication

This type applies only to backup destinations, not to duplication destinations. As soon as NetBackup duplicates the backup, NetBackup deletes information about the backup and the files in the backup become unavailable to restore operation.

8. Click OK in the New Destination dialog box.

9. Return to the New Storage Lifestyle Policy dialog box.

10. Click the Add button.

11. In the New Destination dialog box, select a different storage unit for Duplication. Click OK, which adds it to the list in the New Storage Lifecycle Policy dialog box.

12. Click OK.

58


Backup Exec Configuration When you launch the Backup Exec application, its Home page is displayed. This page guides you through the configuration procedures. It provides links to Backup Exec technical support and documentation, as well as an alerts and job history summaries.

Note: For information on setting up, scheduling, and monitoring jobs, see the Symantec Backup Exec 2010 Administrator’s Guide.

Figure 4-1: Backup Exec Home Page

Complete these Getting Started steps (as shown in the upper-left of the home page):

1. Create a logon account.

2. Configure devices.

Notes:

• Click the icon to the left of the task to launch a wizard or assistant that guides you through the configuration step.

• A green check to the left of a task indicates that a task has been completed.


OST Configuration

Creating a Logon Account

Follow these steps to create a logon account.

Create a logon account

1. Double-click the icon to the left of 1) Create Logon Accounts in the Getting Started panel of the Home page. The Logon Account Wizard Welcome dialog box is displayed. Click Next.

2. In the Set Up a Logon Account dialog box, select Add a new logon account, and click Next.

3. In the Enter Logon Account Credentials dialog box, enter the Data Domain system’s OST user name and password. Click Next.

4. In the Logon Account Name dialog box, type an account name that describes this logon account. Click Next.

5. In the Type of Logon Account dialog box, make the account available to all Backup Exec users. Click Next.

6. In the Default Logon Account dialog box, select No. The Data Domain system account is usually not the Backup Exec system logon. Click Next.

7. Verify your account settings as shown in the Logon Account Summary dialog box. Click Back to edit prior selections. If the account information is correct, click Next.

8. The Completing the Logon Account Wizard dialog box is displayed. Click Finish.

60


Configuring Devices

Follow these steps to configure devices.

Configure devices

1. Create a logical storage unit on the Data Domain system. See Creating Logical Storage Units (LSUs) on page 38.

2. From the Backup Exec Home page, select Configure Devices from the Tools menu. Select Add OpenStorage from the menu.

3. Configure the AddOpenStorage Device dialog box’s General tab as follows:

• Name: Enter the name of the Data Domain system.

• Server: Enter the Data Domain host name.

• Select the logon account name previously created.

• Select DataDomain as the server type.

• Logical storage unit: Select logical storage unit.

• Concurrent Operations: Specify the number of concurrent operations for the device.

The total number of concurrent connections (jobs) from a single media server plug-in to all associated OpenStorage logical storage units is 16. The concurrent operations limit for a single device can be determined as follows:


OST Configuration

16 >= # OpenStorage logical storage units + ∑ concurrent operations for each logical storage unit

In the case of a single Data Domain system with a single logical storage unit, the concurrent operation count can be set as high as 15.

4. Click OK.

5. Configure the AddOpenStorage Device dialog box’s Advanced tab as follows:

• Accept the default values for Disk Space Management and Direct Access.

• Specify a Data stream chunk size from 64 KB to 256 KB. For best performance, 256 KB is recommended.

6. Click OK.

7. Click the Sharing tab.

A single Data Domain logical storage unit can be shared by multiple media servers when the shared media servers are associated with a single primary media server.

In the media servers list, select the primary media server, and click OK.

62


8. You must restart the Backup Exec services when a new Data Domain system is added. In the Restart Services dialog box, click Restart Now.

After the device has been configured, the new logical storage unit is displayed in the Devices page (Figure 4-2).

Figure 4-2: Backup Exec Devices


OST Configuration

64

5 Using the OST Commands

This chapter describes the OST commands that you use to manage the OST feature on the Data Domain system.

Note: For information about OST commands that you can access using the Enterprise Manager’s graphical-user interface, see the DD OS 4.8 Administration Guide.

The ost command includes the following options.

destroy Delete all LSUs and their contents from the Data Domain system.

Page 66

disable Disable OST. Page 66

enable Enable OST. Page 66

ifgroup For Advanced Load Balancing and Failover: Manage interface groups (IP addresses) on a Data Domain private network that distribute data transfer.

Page 66

lsu Create and delete an LSU, or list the LSUs and images in an LSU.

Page 69

opt-dup Set, reset, or show the status of the low- bandwidth optimization option for optimized duplication. Show or reset statistics, history, and performance.

Page 69

option Set, reset, or show the status of the Distributed Segment Processing feature.

Page 74

reset Delete the OST user and reset statistics. Clear all job connection counters shown in the output of the ost show connections command in the event that network connection is lost

Page 75

set user-name Set an OST user. Page 76

show Show the OST user name, connections, OST histogram, statistics, or OST image-duplication status.

Page 76


Using the OST Commands

ost Command Options

enableost enable

Administrators use this command to create and export the /backup/ost directory.

Whenever the user, user ID (UID), or group ID (GID) changes, the Data Domain system updates all images and LSUs the next time that the ost enable command is issued.

destroyost destroy

Administrators use this command to delete all LSUs and their contents from the Data Domain system. The command permanently removes all of the data (images) contained in the LSUs.

You must also manually remove (expire) the corresponding catalog entries.

disableost disable

Administrators use this command to disable OST for the Data Domain system.

ifgroupNotes:

ifgroup is an interface group.

Advanced Load Balancing and Failover is not supported for a Global Deduplication Array.

status Show whether OST is enabled or disabled. Page 79

66

ost Command Options

ifgroup add interfaceost ifgroup add interface ipaddr

Administrators use this command to add an IP address to a private network that is to process data transfer. The IP address must be configured on the Data Domain system, and its interface enabled.

The command checks if the IP address is valid. If not, a message reports the IP address is invalid (either because it is not configured on the Data Domain system, or its interface is not enabled). Use the net show settings or net show config commands to view available IP addresses.

If the IP is valid, the message IP added to list is displayed. After adding an IP address as an interface, you need to enable Advanced Load Balancing and Failover using the ost ifgroup enable command.

Note: Failover is not an automatic process. If an interface (or a NIC that has multiple interfaces) fails, all the in flight jobs to that interface fail and need to be restarted by the backup administrator. However, any jobs that are started subsequent to the failure will get routed to the healthy interfaces.You can add public or private IP addresses for data transfer connections.

Notes:

• 1 GigE and 10GigE connections cannot be used in the same interface group.

• You can add public or private IP addresses for data transfer connections.

ifgroup del interfaceost ifgroup del interface ipaddr

Administrators use this command to remove a valid IP address added as an interface.

If you are attempting to delete the last IP address interface, you are informed that the ifgroup will be disabled and are given the option of terminating this command.



ifgroup disableost ifgroup disable

Administrators use this command to disable the Advanced Load Balancing and Failover option for new jobs. Currently running jobs are not affected.

If the OST feature is disabled, the message disabled is displayed.

ifgroup enableost ifgroup enable

Administrators use this command to enable Advanced Load Balancing and Failover. At least one IP address must have already been added.

ifgroup show configifgroup show config

Use this command to show the IP addresses that have been added to the ifgroup.

ifgroup resetifgroup reset

Administrators use this command to reset Advanced Load Balancing and Failover links.

For a reset to occur, the Advanced Load Balancing and Failover feature must be disabled; and there must be no active jobs. If there are active jobs, a message informs you that the system is busy and that jobs need to complete. You are asked to try again later.

If the Advanced Load Balancing and Failover links are reset, a message to this effect is displayed.

ifgroup statusifgroup status

Use this command to show whether OST Link Aggregation is enabled or disabled.

68

ost Command Options

lsu

lsu createost lsu create lsu-name

Administrators use this command to create an LSU with a given name.

Note: If you invoke the filesys destroy command, you need to run ost disable followed by ost enable and then create an LSU using ost lsu create. If you do not run this series of commands, the Data Domain system reports an error.

lsu deleteost lsu delete lsu-name

Administrators use this command to delete a specified LSU and all of its contents. You must also manually remove (expire) the corresponding catalog entries.

lsu showost lsu show [compression] [lsu-name]

Use this command to display the names of all LSUs or, optionally, the names of all images in a specified LSU.

To display the compression for all LSUs (the original byte size, global compression, and local compression for all LSUs), enter the compression option.

Note: To interrupt the output of this command, press Ctrl+C.

opt-dupNote: The low-bandwidth optimization option is not supported in a Global Deduplication Array.



opt-dup option resetost opt-dup option reset {low-bw-optim}

Administrators can use this command to reset low-bandwidth optimization to its default value, which is disabled.

opt-dup option set low-bw-optim ost opt-dup option set low-bw-optim {enabled | disabled}

Low-bandwidth optimization, which is disabled by default, is designed for use on networks with less than 6 Mbps aggregate bandwidth. Do not use this option if maximum filesystem write performance is required.

This command, which is available to administrators only, must be entered on both Data Domain systems—the source and destination (target) systems.

After you enable low-bandwidth optimization on both systems, both systems must undergo a full cleaning cycle to prepare the existing data. Enter this CLI command on the source and destination systems:

# filesys clean start

The amount of time the cleaning cycle takes depends on the amount of data currently on the Data Domain system.

opt-dup option showost opt-dup option show [low-bw-optim]

Use this command to show whether low-bandwidth optimization is enabled or disabled for optimized duplication.

opt-dup reset statsost opt-dup reset stats

Administrators can use this command to reset opt-dup statistics when OST is enabled.

70

ost Command Options

opt-dup show activeost opt-dup show active

Use this command to show the status of an OST image duplication transfer to a destination Data Domain system.

The low-bandwidth optimization status output indicates either that it is enabled and running, or that it is enabled but there is a configuration mismatch.

04/28 11:29:43

Outbound image name /backup/example.tar

Target host name 127.2.0.1

Low-bw-optim enabled and running

Logical bytes to transfer 436,874,240

Logical bytes already transferred 104,659,157

opt-dup show historyost opt-dup show history [ duration duration{day | hr}] [interval hr]

Use this command to show the data transfer history between the source and destination (target) Data Domain systems. The following information is shown for inbound and outbound traffic for a given duration at a specified interval:

• amount of pre-compressed data in KB

• amount of post-compressed data in KB

• network transfer data in KB



ors

• low-bandwidth optimization factor

• number of errors

opt-dup show image-historyost opt-dup show image-history [duration duration{day | hr}]

Use this command to show the data transfer history for inbound and outbound traffic on each image in Data Domain system’s backup directory for a given duration at a specified interval. The following is shown for inbound and outbound traffic by date and time:

• amount of pre-compressed data in KB

• amount of post-compressed data in KB

• network transfer data in KB

• low-bandwidth optimization factor

• number of errors

Example of OST opt-dup show history command output:

Date Time Direction Pre-Comp (KB)

Post-Comp (KB)

Network (KB)

Low-bw-optim

Errors

2009/08/31

11:14 Inbound 47,738 26,634 27,527 1.32 0

2009/08/31

11:14:09 Outbound 14,327 8,638 9,034 1.21 0

Example of OST opt-dup show image history command output:

Date Time Direction Filename Pre-Comp (KB)

Post-Comp (KB)

Network (KB)

Low-bw-optim

Err

2009/08/31

15:13:09 Inbound /backup/source.tar

47,738 26,634 27,527 1.32 0

2009/08/31

15:13:09 Outbound /backup/destin.tar

14,327 8,638 9,034 1.21 0

72

ost Command Options

opt-dup show performanceost opt-dup show performance [interval sec] [count count]

Use this command to display in real time, for a given duration at a specified interval, the amount of pre-compressed outbound and inbound data versus the actual network throughput, or post-compressed data.

04/30 11:14:16

Outbound Inbound

Pre-comp Network Pre-comp Network

(KB/s) (KB/s) (KB/s) (KB/s)

--------- --------- --------- ---------

0 0 1644 325

0 0 2901 470

0 0 2430 458

0 0 14390 300

0 0 0 70

0 0 2308 446

0 0 2814 552

0 0 3010 529

opt-dup show statsost opt-dup show stats

Use this command to monitor outbound and inbound traffic on a Data Domain system during replication. The compression ratio increases when low-bandwidth optimization is enabled.



Direction: Outbound

Network bytes sent: 88,383,976

Pre-compressed bytes sent: 436,874,240

Bytes after filtering: 153,080,417

Bytes after low-bw-optim: 145,547,868

Bytes after local compression: 83,628,271

Compression ratio: 4.9

Direction: Inbound

Network bytes received: 88,383,976

Pre-compressed bytes received: 436,874,240

Bytes after filtering: 153,080,417

Bytes after low-bw-optim: 145,547,868

Bytes after local compression: 83,628,271Compression ratio: 4.9

option

option set boostost option set boost {enabled | disabled}

Administrators can use this command to enable or disable the Distributed Segment Processing feature on the DD OS. By default, it is enabled for DD OS 4.8. If this feature presents any problem for a media server, use this command to disable the feature on the Data Domain system.

Distributed Segment Processing is supported only if the installed version of the OST plug-in is version 2.0 or later, and the feature is enabled on the DD OS.

Notes:

Distributed Segment Processing is enabled by default in DD OS 4.8. If a system is upgraded from DD OS 4.6.x or 4.7.x to DD OS 4.8, and the OST license is installed at the time of the

74

ost Command Options

upgrade, Distributed Segment Processing is not automatically enabled.

If the Distributed Segment Processing feature is enabled in a Global Deduplication Array, you cannot disable it.

option resetost option reset [boost]

Administrators use this command to reset Distributed Segment Processing to the default option, which is enabled.

option showost option show [boost]

Use this command to show whether the Distributed Segment Processing option is enabled or disabled.

reset

reset user-nameost reset user-name ost-user

Use this command to delete the ost-user.

reset statsost reset stats

Administrators use this command as follows:

• to reset all statistics when OST is enabled, or

• as a network recovery procedure to clear job connections after the network connection has been lost.



set user-nameost set user-name ost-user

Administrators use this command to set the OST user name when OST is enabled.

• You must disable and then re-enable OST for OST user-name modifications to take effect.

• There can be only one OST user at a time. The username and password must have already been set up on the Data Domain system using the DD OS CLI command: user add username [password password]

• The user must be configured in the backup application in order to connect to the Data Domain system.

show

show connectionsost show connections

Use this command to show the following information:

• the number of active clients, and for each active client:

• the client’s name

• whether or not the client is idle (yes/no)

• the number of installed CPUs

• the amount of memory in MiB

• the installed OST plug-in version number

• the name and version of the operating system

• the backup application’s version number.

• the number of connections that a system uses for OST, and whether these connections are spread across interfaces using Advanced Load Balancing and Failover. (See sample output for client connections below.)

76

ost Command Options

• the number of connections used for a given group, even when the interface has been removed from the ifgroup.

• an overview of interfaces available for OST.

Note: For a Global Deduplication Array, the ifgroup status is always disabled, and the Member column value is always no.

show histogramost show histogram op

Use this command to display an OST histogram for the Data Domain system.

Client Connections:

Max Client Connections: 149

ifgroup status: Enabled

Interface ifgroup -------------- Connections --------

member Backup Restore Control * Total

----------------- -------- -------- -------- -------- --------

192.168.54.138 yes 15 0 2 17

192.168.52.192 yes 15 0 3 18

192.168.55.206 yes 16 0 3 19

----------------- -------- -------- -------- -------- --------

Total Connections 46 0 8 54

----------------- -------- -------- -------- -------- --------

* Control connections for opt-dup, image operations

op The name of the NFS operation.

mean-ms The mathematical mean time for completion of the operations.



show image-duplication activeost show image-duplication active

Use this command to show the OST image duplication status.

show statsost show stats [interval seconds]

Use this command to show the output of previous show stats command, the number of bytes written to and read from OST images contained in LSUs, and the number of OST images created and deleted from LSUs. The number of errors encountered for each operation is also shown. Optionally, you can show statistics for a specific number of seconds.

If Distributed Segment Processing is enabled, the number of bytes transferred via DISTRIBUTED SEGMENT PROCESSING and the amount of compression achieved is displayed.

show user-nameost show ost-user

Use this command to display the current OST user.

stddev The standard deviation for time to complete operations, derived from the mean time.

max-s The maximum time taken for a single operation.

2,4,6,8, or 10ms

The number of operations that took less than the specified number of milliseconds (ms).

100ms The number of operations that took between 10 ms and 100 ms.

1s The number of operations that took between 100 ms and one second.

10s The number of operations that took between 1 second and 10 seconds.

>10s The number of operations that took over 10 seconds.

78

ost Command Options

statusost status

Enter this command to determine whether OST is enabled or disabled.



80

6 Administration

This chapter covers the following major topics:

• Data Domain System Administration on page 81

• NetBackup Administration on page 85

• Backup Exec Administration on page 89

Data Domain System AdministrationThis section covers the following topics:

• Optimized Duplication Version Compatibility on page 81

• Removing Advanced Load Balancing/Failover Configuration on page 82

• Modifying an Interface Group on page 83

Optimized Duplication Version CompatibilityThe Data Domain policy of upgrade compatibility for optimized duplication follows:

• All maintenance and patch versions within a family, are backwardly compatible. A family is identified by the first two digits of the release number, such as 4.8. For example, 4.8.0.0, 4.8.0.2, 4.8.1.0, and 4.8.2.0 are backwardly compatible.

• Optimized duplication is backward compatible across two consecutive release families, such as 4.6 and 4.5, although only the current release within each family is tested.

• The destination Data Domain system must be at the highest version. Cases in which the destination node is at a lower revision than the source node or nodes are not supported.


Administration

• For bidirectional optimized duplication, both destination and source must run the same release.

• Optimized duplication over WAN should use the Data Domain replication command to adjust for low bandwidth and long latency.

Removing Advanced Load Balancing/Failover Configuration

The following example illustrates removing a configured interface group on the Data Domain system.

1. Make sure that no jobs are active from the backup application to the Data Domain system. You can do this from the Data Domain system by checking the status of existing connections in the interface group by using the following command:

# ost ifgroup show connections

See Figure 6-1 on page 84 for sample output.

2. En sure that there are no pending jobs from any of the connected media servers to this system.

3. Disable the feature on the Data Domain system:

# ost ifgroup disable

4. Reset the interface group:

# ost ifgroup reset

All the interfaces are released from the group. However, media servers can still access the OST storage server on the Data Domain system on the interface registered with the backup application. In the example above, the Data Domain system is still registered with the backup application using 192.168.1.1.

Optimized Duplication Setup

Load balancing depends upon backup and restore. It is recommended that you exclude one interface from the ifgroup and reserve it for the optimized duplication path between the source and target Data Domain systems.

82

Data Domain System Administration

Configuration Restrictions

• The interfaces can only be added to the group using an IP address.

• Even though the Advanced Load Balancing and Failover feature works with both 1GbE interfaces and 10 GbE interfaces in a group, it is not a recommended setup. It is recommended to have like interfaces (in terms of link speed) in a group.

• Since only one interface group is supported on the Data Domain system, for connecting more than one media server, a switch is needed in the middle.

• The feature is not supported on two-controller Global Deduplication Array.

Modifying an Interface GroupAfter the interface group is setup, you can add or delete interfaces from the group. The following example shows how to remove an interface from the configured interface group on the Data Domain system.

1. Make sure that no jobs are active from the backup application to the Data Domain system on the interface that you wish to remove from the group. You can do this from the Data Domain system by checking the status of existing connections in the interface group by enter the following command:

• # ost ifgroup show connections


Administration

Sample output:

Figure 6-1: Sample Output for ost ifgroup show connections Command

2. Remove the interface from the group on Data Domain system:

# ost ifgroup del 192.168.1.3

After this, the interface 192.168.1.3 is released from the group and would no longer be used by the OST Storage Server for any jobs from the media servers.

Note: Removing the interface registered with the backup application makes the OST storage server on the Data Domain system inaccessible to the media servers. The configuration of the group on the Data Domain system is not deleted.

To make any changes to any interface that is added to the interface group on the Data Domain system at the network layer, remove the interface from the group and add it back.

If you make changes using the net command that modify the interfaces, such as enabling an interface that is configured for

Client Connections:

Max Client Connections: 149

ifgroup status: Enabled

Interface ifgroup -------------- Connections --------

member Backup Restore Control * Total

----------------- -------- -------- -------- -------- --------

192.168.54.138 yes 15 0 2 17

192.168.52.192 yes 15 0 3 18

192.168.55.206 yes 16 0 3 19

----------------- -------- -------- -------- -------- --------

Total Connections 46 0 8 54

----------------- -------- -------- -------- -------- --------

* Control connections for opt-dup, image operations

84

NetBackup Administration

ifgroup, execute the ost show connections command to update the load balancing view. This updating allows the ifgroup to use the interface. See page 76 for more information about the ost show connections command.

NetBackup AdministrationThis section covers the following topics and procedures:

• Find your OST version on page 85

• Find your NetBackup version on page 85

• Network Time-Outs on page 86

• Duplicate Images (NBU Workaround) on page 87

• Grouping Storage Units to Provide Failover on page 87

• Delete a Data Domain storage server on page 88

Find your OST versionEnter:

# bpstsinfo -pi

The output shows the vendor version, which is the plug-in version, and the build version, which is the OST API version.

Find your NetBackup version

NetBackup

Search the file [NetbackupInstall_Dir] version.

Sample output from this command looks like:

HARDWARE SOLARIS

VERSION NetBackup? 6.5

RELEASEDATE Mon Jul 23 16:30:00 CDT 2009

BUILDNUMBER 20070723


Administration

Network Time-Outs

Backup and restore jobs often take a long time to complete. Although the OST plug-in can recover from temporary network interruptions, the operating system on the backup application system might terminate a job prematurely if the backup application time-outs are set too low.

Data Domain recommends setting time-outs to at least 30 minutes (1800 seconds).

Note: After losing a network connection, administrators should issue the ost reset stats command to clear job connections.

Set backup application time-out using the CLI

Add the following two lines to the file[NetBackupInstall_directory]/bp.conf:

CLIENT_CONNECT_TIMEOUT = 1800

CLIENT_READ_TIMEOUT = 1800

Note: The time-out value is expressed in seconds.

Set backup application time-out using the GUI

1. Expand the NetBackup Management node.

2. Expand Host Properties.

3. Select Master Servers.

4. In the right pane, double-click the machine name.

In the property dialog box that is displayed, change the time-out values.

86

NetBackup Administration

Duplicate Images (NBU Workaround)

When using the NetBackup graphical user interface to duplicate images, select Media ID in the Search for images panel of the Search tab.

Grouping Storage Units to Provide Failover

The administrator can specify a group of storage units to share a workload. The administrator tells the backup application system how to choose among the storage units in the group for the next job by setting one of the following selection criteria:

• Failover (This is the recommended setting)

Setting failover as the selection criterion ensures that a backup job does not fail if the storage unit to which it is directed fails. The backup application chooses another storage unit in the same group to finish the job.

• Prioritized

• Round robin

• Load balance


Administration

Delete a Data Domain storage server

Warning:This procedure removes all of the data and resources associated with the storage server. Do not attempt this procedure unless it is necessary.

1. Delete all of the images specified by the BACKUP_ID by entering:

# bpexpdate -backupid BACKUP_ID -d 0

2. Delete all of the policies from the GUI.

3. Delete all of the storage units by entering:

# bpstudel -label SU_NAME

4. Delete all the disk pools by entering:

# nbdevconfig -deletedp -stype DataDomain -dp pool-name

5. Delete the storage server by entering:

# nbdevconfig -deletests -storage_server dd22 -stype DataDomain

Note: You can use the GUI to delete the images, lifecycle policies, storage units, and disk pools.

For troubleshooting information, see Unable to Delete the Data Domain System on page 93.

6. Remove the credential using the tpconfig command.

# tpconfig -update-storage_server dd22 -stype DataDomain -sts_user_id username -password password

88

Backup Exec Administration

Backup Exec AdministrationThis section covers the following topics:

• Find your OST version on page 89

• Find your Backup Exec version on page 89

• Delete LSUs on Data Domain Systems on page 89

• Recover backup images on an OST device on page 90

Find your OST version1. Go to the Backup Exec install directory and find the file

libstspiDataDomain.dll.

2. Right-click the file’s name and select Properties from the menu.

3. Select the Details tab. The OST version is displayed as the file version.

Find your Backup Exec versionFrom the Backup Exec Home page, select About from the Help menu.

Delete LSUs on Data Domain SystemsThere are two options for deleting a LSU on a Data Domain controller:

• You can erase all media within a Backup Exec device (a Data Domain controller’s LSU) and then delete the device from Backup Exec.

• You can also delete the device from Backup Exec even if media remains in the device. The LSU remains on the Data Domain controller and some files are left in the LSU. To recover this space, delete the LSU on the Data Domain controller by entering:

# ost lsu delete lsu name


Administration

Recover backup images on an OST device1. From the Backup Exec Home page, select the Devices tab.

2. Select the Data Domain system LSU on the Devices page.

3. Select a media label.

4. Right-click the media label, and select Restore from the menu.

90

7 Basic Troubleshooting

This chapter provides basic troubleshooting tips that might enable customers to resolve issues on their own. For issues that cannot be resolved, customers should contact their contracted support providers.


• General Troubleshooting on page 92

• NetBackup Troubleshooting on page 93

• Backup Exec Troubleshooting on page 102

For more information, see the Data Domain Knowledge Base, which is available at (https: //my.datadomain.com.


Basic Troubleshooting

General Troubleshooting When investigating problems, be aware that the Data Domain OST software has components on both a Data Domain system and a backup application system. The two environments must be compatible. The following troubleshooting considerations apply to both systems:

• Supported Configurations

Ensure that you have a supported configuration as specified in the OST Compatibility List. A supported configuration can become unsupported if any component changes.

The OST Compatibility List is available from the Data Domain Support portal (https: //my.datadomain.com). Navigate to the Documentation > Compatibility List page and select Data Domain OST Compatibility List.

• Authorization Failures

If you encounter authorization failures, ensure that all of the systems have correct access credentials for the other systems. Configuring a Media Server on page 41 provides instructions on establishing user credentials.

92

NetBackup Troubleshooting


Unable to Delete the Data Domain SystemThis procedure assumes the following:

• You are unable to delete the Data Domain system.

• You have already run the nbdevconfig command with the deletests option and it has failed, which means that the emm or rmms process might be down.

• All of the images for the specified Data Domain have expired. For instructions on how to expire an image, see your NBU documentation.

If you are still unable to delete the Data Domain system, follow these steps:

1. Enter:

# nbdevconfig -deletests -storage_server DDR -stype DataDomain

2. If core files result, contact Data Domain Support. Otherwise, continue to the next step.

3. Follow the instructions below for your operating system.

On a Windows System

1. Restart the NetBackup services on the media server by running these two executable files:

NBUInstallPath\NetBackup\bin\bpdown.exe

NBUInstallPath\NetBackup\bin\bpup.exe

2. Run deletests again. If it fails, enable more detailed NBU logging by opening the NBUInstallPath\NetBackup\nblog.conf file and adding this entry:

NBSTSI=OID=202

3. Enable detailed logging messages on media servers as described in Error Logging on the Media Servers on page 95.



On a UNIX System

1. If rmms restarts but emm does not, verify that all of the processes are up, especially emm or rmms.

2. If these processes are not up, enter:

# /bp/bin/goodies/netbackup start

3. Run deletests again. If it still fails, enable more NBU logging by opening the /bp/nblog.conf file and adding this entry:

NBSTSI=OID=202

4. Enable detailed logging messages as described in Error Logging on the Media Servers on page 95.

Check the InstallationProblems with basic operations such as backups may result from improper installation.

1. Verify that the files are in the correct location by entering the following, depending on your operating system:

a. On a UNIX system, enter:

# ls /usr/openv/lib/ost-plugins/

The command output should be the names of the shared library files:

libstspiDataDomain.so

libstspiDataDomainMT.so

a. On a Windows system, enter:

C:\Program Files\Veritas\bin\ost-plugins

The command output should be the name of the shared library file libstspiDataDomain.dll.

2. Determine the plug-in version by entering:

# bpstsinfo -pi

The vendor version shown in the output is the Data Domain plug-in version, and build version is the version of the OST API.

94


Note: If the bpstsinfo command fails, check the log files in the /usr/openv/netbackup/logs/admin directory.

Check CredentialsTo display credentials for all Data Domain systems registered as storage servers, enter the following command from the backup application system:

# tpconfig -dsh -all_hosts -stype DataDomain

If you receive a message stating that you failed to add credentials for the Data Domain system (OpenStorage server), follow the procedure Adding Credentials on page 43, which describes how to set up credentials and check for errors and inconsistencies.

Resolve License ErrorIf the Configure Disk Pool wizard reports a license error, do the following:

1. Open the file bp.conf.

2. Check if it contains an extra CLIENT_NAME entry.

3. Delete any extra CLIENT_NAME entry.

Note: An extra entry can occur after upgrading NetBackup from version 6.0 to 6.5.

Error Logging on the Media ServersThe error log is the main tool for troubleshooting problems related to NetBackup in an OST environment. Before starting a backup, restore, or optimized duplication operation, enable logging on the NetBackup media server. Follow the instructions for the media server’s operating system, or use the NetBackup GUI.

Enable Error Logging on a UNIX System

Enter:

# /usr/openv/netbackup/logs/mklogdir



Enable Error Logging on a Windows System

Enter:

C:\Program Files\Netbackup\logs\mklogdir.bat

Enable logging via the GUI

1. Open the NetBackup Administration Console’s Devices window.

1. In left pane of this window, expand the NetBackup Management node.

2. Expand Host Properties and select Master Servers.

3. In the right pane, double-click the machine name.

4. In the Property directory tree, select Logging, which displays the Logging dialog box.

5. Set the Global Logging level to 4, and click OK.

After you have enabled logging, the OST plug-in prefixes error and informational log messages with the name DataDomain.

96


Resolving Failed Backups on Media ServersSearch for plug-in error messages in the log file as described below for the media server’s operating system.

Resolve failed backups on a UNIX system

Enter:

# cat /usr/openv/netbackup/logs/bptm/LOGFILE_DATE | grep DataDomain

The command selects lines from the specified log file that contain the word DataDomain. The plug-in uses DataDomain as a prefix for its log messages.

Resolve failed backups on a Windows system

1. Enter:

C:\Program Files\Veritas\logs\bptm\LOGFILE_DATE.log

2. Open the log file and search for the word DataDomain.

Resolve failed image duplication

1. Search for plug-in error messages in the media server log files, which are specific to the server’s operating system:

UNIX

• For read_image:

/usr/openv/netbackup/logs/bpdm

• For write_image:

/usr/openv/netbackup/logs/bptm

• For opt-dup:

/usr/openv/netbackup/logs/bpdm

Windows

• For read_image:

C:\Program Files\Veritas\logs\bpdm



• For write_image:

C:\Program Files\Veritas\logs\bptm

• For opt-dup:

C:\Program Files\Veritas\logs\bpdm

2. Verify that the replication license is installed by entering:

# license show

3. For further assistance, contact your contracted support provider.

Resolve time-out error

1. Verify that the client can ping the Data Domain system.

2. Verify that the file system is running on the Data Domain system by entering:

# filesys status

3. Verify that NFS is running on the Data Domain system by entering:

# nfs status

Plug-In Log MessagesWhen the plug-in encounters an error, it returns an EPLUGIN error code to NetBackup and logs a reason for the error.

1. Determine if the reason is one of the following:

• Write Length Exceeds Limit Error

The write buffer data size is limited. If you receive an exceeds limit error message, change the buffer size to a value within the specified limit as described in Configuring Buffers on page 52.

• Program Not Registered

The following output indicates that the program is not registered:

(: RPC: Program not registered)

98


2. Register the OST plug-in by installing a valid license:

# license add ost-license-code

3. Verify that the file system is running on the Data Domain system by entering:

# filesys status

Cannot Connect on Socket ErrorThis error results when the command nbdevconfig -creatests has been run, but the storage server is not created because of a socket connection error.

Follow these steps:

1. Check to make sure the nbemm process is running. If it keeps failing upon startup, usually there is an issue with the NBU database.

2. Use the vxlogview utility to check the logs located in /usr/openv/logs/51216-*.log for errors.

3. Recreate the Database. Enter:

# /usr/openv/db/bin/create_nbdb -drop



NetBackup Backup Jobs Fail on Solaris Media Servers

If an image backup job fails with a media write error (84) at the start of the job, a typical activity monitor job detail might contain the following:

2/28/2009 3:36:22 AM - Critical bptm(pid=1750) failure to open sts for storage server apoddrrp01: plug-in reports error 2060046 plugin error

2/28/2009 3:36:23 AM - end writing media open error(83)

The bptm log may contain information similar to the following:

01:33:02.585 [28874] <16> apoddrrp01: /usr/openv/lib/ost-plugins/libstspiDataDomain.so:stspi_open_server STS_EPLUGIN Can't connect to mountd on apoddrrp01 (: RPC: Miscellaneous tli error - An event requires attentionError 0)

In the above example, an entry in/etc/inet/ipsecinit.conf has enforced encryption on traffic from port 665 (sun-dr). However, the Solaris operating system had Sun Dynamic reconfiguration disabled. As a result, although the media server used port 665 to connect via NFS to the Data Domain system, the packet did not leave the media server because it was not encrypted.

To fix this problem, you need to disable dynamic reconfiguration.

Disable dynamic reconfiguration

1. Uncomment or remove sun-dr entries in /etc/inet/inetd.conf:

sun-dr stream tcp wait root /usr/lib/dcs dcs

sun-dr stream tcp6 wait root /usr/lib/dcs dcs

2. Have inetd reread the configuration file, by entering:

kill -HUP pid-inetd

100


3. Uncomment or remove the sun-dr entries in /etc/inet/ipsecinit.conf:

{dport sun-dr ulp tcp} permit {auth_algs md5}

{sport sun-dr ulp tcp} apply {auth_algs md5 sa unique}

4. Remove the active IPsec configuration from the running system.

a. Obtain the index numbers by entering:

ipsecconf |grep sun-dr

b. Delete the policy for sun-dr by entering:

ipsecconf -d index

Optimized Duplication Job FailsThe replicator software license for optimized duplication is required on both the source and destination Data Domain systems that run DD OS 4.7 or later.

If this license is not installed, an optimized duplication job fails. A typical activity monitor job detail indicates a media write error (84) occurred. The NetBackup bpdm log states that the NFS operation is not supported.

Add license for replicator

1. Obtain a replicator license code from Data Domain.

2. From the command-line interface on each Data Domain system, add the license code:

# license add license code



Backup Exec Troubleshooting

Basic Troubleshooting• Verify that the concurrent connections (jobs) count is set

properly for all logical storage units.

• NetBackup: The default number of concurrent connections from a single media server is 64. To increase this number, contact your Data Domain systems engineer.

• Backup Exec: The total number of concurrent connections from a single media server plug-in to all associated OpenStorage logical storage units is 16. This number was specified when you configured the device. See Configuring Devices on page 61.

• When encountering a problem, try to stop Backup Exec services and restart them. If this does not work:

• Reboot the server.

• Start the debugger and try to recreate the problem.

Check the InstallationProblems with basic operations such as backups may result from improper installation.

1. Verify that libstspiDataDomain.dll is in C:\Program Files\Symantec\Backup Exec.

2. Determine the plug-in version by right-clicking on the DLL and opening its Properties > Details.

Check Credentials for a Data Domain system1. From the Backup Exec Home page, go to the Devices page.

2. Right-click the OpenStorage device and display its Properties. Note the logon account.

3. From the system menu go to Network > Logon Account Management.

102


4. Select the logon account and verify its User name. Try to edit the account to verify the password. This User name and password should match the OST user name and password on the Data Domain system.

Resolve License Error1. If the OpenStorage option is not enabled, from the Backup Exec

Tools menu select Install Options and License Keys on this Media server.

2. Click Next to go to Configure Options. See Figure 7-1.

3. Open the Backup Exec Options and verify that the Deduplication Option is selected.

4. Click Cancel to avoid making unintended changes.

Figure 7-1: Backup Exec Review Features for Installation Page



Set up active debuggingUse the Backup Exec debugging utility to troubleshoot Backup Exec issues.

1. From the Backup Exec Home page, from the Tools menu select Support Utilities > Run the Debug Monitor for Active Debugging.

The Backup Exec Debug Monitor is displayed.

Figure 7-2: Backup Exec Debug Monitor

2. The following Capture options must be selected (enabled): Job Engine, Backup Exec Server, and Device and Media

3. Capture to file must be enabled.

4. From the Tools > Settings menu, select the Device and Media Debug setting (see Figure 7-3). Select Enable verbose logging if it is not enabled.

104


Figure 7-3: Settings Menu

The log file that is captured is named media server-SGMon.txt. It is located in the logs directory.



106