Data Domain Boost Admin Guide 759-0008-0001

Data Domain Boost for
OpenStorage
Administration Guide
Backup Recovery Systems Division

Data Domain LLC
2421 Mission College Boulevard, Santa Clara, CA 95054
866-WE-DDUPE; 408-980-4800
July 23, 2010

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

Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
DD Boost for OpenStorage Backup Application
Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Access to Documents at Data Domain . . . . . . . . . . . . . 11
Access Data Domain Documents . . . . . . . . . . . . . . 11
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Data Domain Support . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1 Introducing Data Domain Boost for OpenStorage . . .15

Supported Configurations . . . . . . . . . . . . . . . . . . . . . . . 16
2 Installing Data Domain Boost for OpenStorage . . . . .17

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 17
OST Plug-in and DD OS Upgrades . . . . . . . . . . . . . . . . 18
Firewalls and Ports . . . . . . . . . . . . . . . . . . . . . . . . . 18
Enabling DD Boost on a Data Domain System . . . . . . . . 18
NetBackup Installation . . . . . . . . . . . . . . . . . . . . . . . . . 19
Installing the OST Plug-In on Media Servers . . . . . . . . . 20
NetBackup Services . . . . . . . . . . . . . . . . . . . . . . . . . 23
NetBackup UNIX Services . . . . . . . . . . . . . . . . . . . 23
NetBackup Windows Services . . . . . . . . . . . . . . . . 24
DD Boost for OpenStorage Administration Guide 3

Backup Exec Installation . . . . . . . . . . . . . . . . . . . . . . . .24
Installing the Plug-In on Media Servers . . . . . . . . . . . . .24
Backup Exec Services . . . . . . . . . . . . . . . . . . . . . . . .25
Tuning Windows Media Servers for Performance. . . . . . . . .27
Uninstalling the Windows Plug-in. . . . . . . . . . . . . . . . . . .28
3 Data Domain Boost Features . . . . . . . . . . . . . . . . 29

Distributed segment processing. . . . . . . . . . . . . . . . . . . .29
Advanced Load Balancing and Link Failover . . . . . . . . . . . .33
Configuration Restrictions . . . . . . . . . . . . . . . . . . . . .35
Encrypted Optimized Duplication . . . . . . . . . . . . . . . . . .36
Low-Bandwidth Optimization Option . . . . . . . . . . . . . . . .37
4 Data Domain Boost for OpenStorage Configuration . 39

Configuring the Data Domain System . . . . . . . . . . . . . . . .39
Creating Storage Units . . . . . . . . . . . . . . . . . . . . . . .40
Configuring distributed segment processing . . . . . . . . .40
Configuring Advanced Load Balancing and Link Failover .41
Enabling Low-Bandwidth Optimization . . . . . . . . . . . .42
Enabling Encrypted Optimized Duplication . . . . . . . . . .43
Configuring a Media Server. . . . . . . . . . . . . . . . . . . . . . .44
4
NetBackup Configuration . . . . . . . . . . . . . . . . . . . . . 44
Concurrent Connection Limit . . . . . . . . . . . . . . . . 45
Registering Each Data Domain System . . . . . . . . . . 45
Adding Credentials . . . . . . . . . . . . . . . . . . . . . . . 46
Creating Disk Pools . . . . . . . . . . . . . . . . . . . . . . . 46
Creating Storage Units . . . . . . . . . . . . . . . . . . . . 50
Creating a Backup Policy . . . . . . . . . . . . . . . . . . . 53
Configuring Buffers . . . . . . . . . . . . . . . . . . . . . . 53
Configuring Optimized Duplication . . . . . . . . . . . . 55
Using Storage Lifecycle Policies to Automate Optimized
Duplication . . . . . . . . . . . . . . . . . . . . . . . . . 56
Optimized Synthetic Backups . . . . . . . . . . . . . . . 60
Backup Exec Configuration . . . . . . . . . . . . . . . . . . . . 66
Creating a Logon Account . . . . . . . . . . . . . . . . . . 67
Configuring Devices . . . . . . . . . . . . . . . . . . . . . . 67
Configuring Optimized Duplication . . . . . . . . . . . . 70
5 . . . . . . . . . . . . . . . Using the DD Boost Commands 81

ddboost Command Options . . . . . . . . . . . . . . . . . . . . . . 82
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
destroy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

ifgroup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
ifgroup add interface . . . . . . . . . . . . . . . . . . . . . .83
ifgroup del interface . . . . . . . . . . . . . . . . . . . . . .83
ifgroup disable . . . . . . . . . . . . . . . . . . . . . . . . . .84
ifgroup enable . . . . . . . . . . . . . . . . . . . . . . . . . .84
ifgroup show config . . . . . . . . . . . . . . . . . . . . . . .84
ifgroup reset . . . . . . . . . . . . . . . . . . . . . . . . . . .84
ifgroup status . . . . . . . . . . . . . . . . . . . . . . . . . . .85
file-replication . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
file-replication option reset . . . . . . . . . . . . . . . . .85
file-replication option set . . . . . . . . . . . . . . . . . . .85
file-replication option show . . . . . . . . . . . . . . . . .86
file-replication reset stats . . . . . . . . . . . . . . . . . .86
file-replication show active . . . . . . . . . . . . . . . . . .86
file-replication show detailed-file-history . . . . . . . .86
ddboost file-replication show detailed-file-history
[duration duration{day | hr}] . . . . . . . . . . . . . .86
file-replication show detailed-history . . . . . . . . . . .87
ddboost file-replication show detailed-history [duration
duration{day | hr}] [interval hr] . . . . . . . . . . . .87
file-replication show history . . . . . . . . . . . . . . . . .87
file-replication show file-history . . . . . . . . . . . . . .88
file-replication show performance . . . . . . . . . . . . .89
file-replication show stats . . . . . . . . . . . . . . . . . .89
option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
option reset . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
option set . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
option show . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
6
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
reset stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
show connections . . . . . . . . . . . . . . . . . . . . . . . . 92
show histogram . . . . . . . . . . . . . . . . . . . . . . . . . 93
show stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
storage-unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
storage-unit create . . . . . . . . . . . . . . . . . . . . . . 95
storage-unit delete . . . . . . . . . . . . . . . . . . . . . . 95
storage-unit show . . . . . . . . . . . . . . . . . . . . . . . 95
user-name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
6 Administration . . . . . . . . . . . . . . . . . . . . . . . . . .97
Data Domain System Administration . . . . . . . . . . . . . . . . 97
Restricting Export Permissions to DD Boost . . . . . . . . . 97
Optimized Duplication Version Compatibility . . . . . . . . 99
Modifying an Interface Group . . . . . . . . . . . . . . . . . . 99
Removing Advanced Load Balancing and Link Failover
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
NetBackup Administration . . . . . . . . . . . . . . . . . . . . . 102
Network Time-Outs . . . . . . . . . . . . . . . . . . . . . 102
Grouping Storage Units to Provide Failover . . . . . . 103
Backup Exec Administration . . . . . . . . . . . . . . . . . . . . 104

7 Basic Troubleshooting . . . . . . . . . . . . . . . . . . . 107
General Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 107
Data Domain System Settings for File-Replication . . . . . . . 108
NetBackup Troubleshooting . . . . . . . . . . . . . . . . . . . . . 108
Unable to Delete the Data Domain System . . . . . . . . . 108
Error Logging on the Media Servers . . . . . . . . . . . . . . 111
Resolving Failed Backups on Media Servers . . . . . . . . . 112
NetBackup Backup Jobs Fail on Solaris Media Servers . . 115
Optimized Duplication Job Fails . . . . . . . . . . . . . . . . 116
Backup Exec Troubleshooting . . . . . . . . . . . . . . . . . . . . 116
Basic Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 116
8
About This Guide
This guide explains how to install, configure, and use Data

Domain Boost for OpenStorage with Data Domain systems.
Related Documents
The following Data Domain system documents provide additional
information:
• DD OS Release Notes Version 5.0
• DD OS 5.0 Initial Configuration Guide
• DD OS 5.0 Administration Guide
• DD OS 5.0 Command Reference
• DD OS 5.0 Command Reference 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).
DD Boost for OpenStorage Backup Application

Documentation
Documentation 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_En
terprise_Server/327648.pdf
• NetBackup 6.5 Hardware Compatibility List that includes

information for supported OpenStorage servers can be found
at http://seer.entsupport.symantec.com/docs/284599.htm
• NetBackup 7.x Hardware Compatibility List that includes
Symantec Backup Exec Documentation

This document is installed with the application:
• Symantec Backup Exec 2010 Administrator’s Guide
• Backup Exec 2010 Hardware Compatibility List that includes
10 About This Guide

Access to Documents at Data Domain
The Documentation page at
https://my.datadomain.com/documentation provides access to
three categories of documents that are related to use of Data
Domain products:
• User guides, under Product Documentation.
• Guides for how to integrate Data Domain systems with backup
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 software versions
• Backup software server and client operating system
versions
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.

4. To view compatibility matrices, perform the following steps.
a. Click Compatibility Matrices.
b. Select the desired title from product menu and click View.
Conventions
The following tables describe the typographical conventions used
in this guide.The following table describes the typographical
conventions used in this guide.
Typeface or Usage Examples

Symbol
Monospace Commands, command Use the config command to
options, and parameters manage the Data Domain
and computer output. system configuration
settings.
Monospace Commands the user types at Enter:
bold the command prompt (#). # config setup
Monospace Command variables the user # log view file_name
italic bold types at the command prompt
(#).
Italic Book titles, and variables. Refer to the DD OS Command
Reference Guide for complete
descriptions of DD OS
commands.
Pipe (|) and Choose (pipe) between a {arg1 | arg2}
curly braces required argument (curly
({}) braces) in the CLI.
Brackets ([]) One or more (list with [arg1, arg2, ...]
and ellipses commas and ellipses)
(...) optional (bracket)
arguments in the CLI.
12 About This Guide

Audience
This guide is for system administrators who are familiar with
Symantec backup applications and general backup administration
Data Domain Support

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

14 About This Guide
1 Introducing Data Domain
Boost for OpenStorage
Data Domain Boost (DD Boost) for OpenStorage enables media

servers to communicate with storage systems without the need for
Data Domain storage systems to emulate tape. In the context of
Symantec backup applications (NetBackup and Backup Exec),
there are two components to the software:
• An OST plug-in that you install on each media server. This
plug-in includes the DD Boost libraries for integrating with the
DD Boost server running on the Data Domain system.
• The DD Boost server that runs on Data Domain systems. A
Data Domain system can be a single Data Domain system, a
gateway, or a Global Deduplication Array.
The backup application (NetBackup or Backup Exec) 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 features of DD Boost, including WAN-
efficient replicator software. The application manages all files
(collections of data) in the catalog, even those created by the Data
Domain system.
The Data Domain system exposes pre-made disk volumes called
storage units to a DD Boost-enabled media server. Multiple media
servers, each with the Data Domain OST plug-in, can use the same
storage unit 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 Data Domain Boost
for Open Storage using NetBackup.

Figure 1-1: Data Domain Boost for OpenStorage Configuration Using
NetBackup
Supported Configurations
Data Domain supports DD Boost on the following Data Domain
systems:
• Data Domain systems (DD5xx, DD6xx, DD8xx)
• Data Domain gateway systems (DD560g, DD580g, DD690g,
DD880g)
• Data Domain Global Deduplication Array systems
The OST plug-in version must be compatible with your Data
Domain system and backup application configurations. Data
Domain does not support combinations other than those detailed
in the DD Boost for OpenStorage Compatibility List, which is available
from the Data Domain Support portal (https:
//my.datadomain.com). Navigate to the Documentation >
Compatibility List page and select DD Boost for OpenStorage
Compatibility List.
16 Introducing Data Domain Boost for OpenStorage

2 Installing Data Domain Boost
for OpenStorage
This chapter covers the following topics:

• Installation Overview on page 17
• NetBackup Installation on page 19
• Backup Exec Installation on page 24
• Tuning Windows Media Servers for Performance on page 27
Installation Overview
The overall steps for installing Data Domain Boost are as follows:
1. Obtain the license required to enable DD Boost on the Data
Domain system. You can purchase a DD Boost license key
directly from EMC.
• The basic license allows you to back up and restore 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 and configure DD Boost on the Data Domain system. At
a minimum, configuration includes specifying the DD Boost
user name and password, and creating storage units.
3. Install the OST plug-in software on each media server.
4. After completing the installation steps described in this

chapter, configure DD Boost as described in Chapter 3.

OST Plug-in and DD OS Upgrades
The OST plug-in and the DD OS maintain compatibility as defined
in the DD Boost for OpenStorage Compatibility List. Consult that list
before upgrading either the OST plug-in or the DD OS.
To take advantage of new features in a DD OS release, upgrade the
OST plug-in to a corresponding version. Although an older
version of the OST plug-in maintains compatibility with a newer
version of DD OS, it does not take advantage of the new
functionality available in the DD OS. Perform the upgrade as
described in Installing the OST Plug-In on Media Servers on page 20.
Firewalls and Ports

The 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
network support provider.
The following ports must be open in a firewall for DD Boost
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 DD Boost on a Data Domain System

Every Data Domain system that is enabled for Data Domain Boost
must have a unique name. You can use the Data Domain system’s
DNS name, which is always unique.
Enable DD Boost
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
18 Installing Data Domain Boost for OpenStorage

The file system is enabled and running.
3. Add the DD Boost license using the license key that Data
Domain provided:
# license add license_key
License “ABCE-BCDA-CDAB-DABC” added.
4. Set the DD Boost user by entering:
# ddboost set user-name ddboost-user
5. Enable DD Boost by entering:
# ddboost enable
DD Boost enabled
Notes:
Only one user can be configured for DD Boost 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.
NetBackup Installation
This section describes the commands used to install an OST plug-
in within a NetBackup environment.
NetBackup environments consist of media servers and a master
server. The master server manages clients and media servers and
can also function as a media server. The OST plug-in must be
installed on each media server. If a master server is also configured
as a media server, then the OST plug-in must also be installed on
the master/media server.

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
Installing the OST Plug-In on Media Servers

The 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. There are no
special instructions for uninstalling the OST plug-in on UNIX
systems.

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.)
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.
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
Correct UNIX plug-in installation or update

failure (AIX Media Servers)
1. Stop the NetBackup Remote Manager and Monitor Service
(nbrmms).
2. Enter:
# ./install.sh

a plugin already exists, do you want to proceed
with installation? (y or n) y
Installing the Data Domain OpenStorage Client
Libraries ...
cp libstspiDataDomain.so /usr/openv/lib/ost-
plugins/libstspiDataDomain.so
cp: /usr/openv/lib/ost-
plugins/libstspiDataDomain.so: Cannot open or
remove a file containing a running program.
ERROR in copying libstspiDataDomain.so to
/usr/openv/lib/ost-plugins/libstspiDataDomain.so,
error = 1
The install script might fail and display an error message that
indicates that the plug-in already exists. This failure occurs if a
plug-in is already installed and is being replaced by another
instance.
If the install script fails:
1. Execute the following command:
# /usr/sbin/slibclean
2. Enter:
# ./install.sh
Because the modules have now been unloaded from memory,
the install.sh script should now run correctly.
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:
a. Stop any NetBackup services. Follow the instructions given

in NetBackup Windows Services on page 24 to stop the
service.
b. Remove any previous plug-in version using either the
Windows Control Panel or
libstspiDataDomainUninstall.exe.
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 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.
3. When the Installation is complete, you can click the Show
details button to view the files installed and their location.
4. Restart all services. See NetBackup Windows Services on page 24.
5. Tune the Windows media server for performance. See Tuning

Windows Media Servers for Performance on page 27.
NetBackup Services
Follow 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.
Backup Exec Installation

This 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 Servers

The OST plug-in software must be installed on media servers that
need to access the Data Domain system. Because Backup Exec
supports OpenStorage only on Windows media servers, the
following section covers instructions for Windows servers only.
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 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:
a. Stop any Backup Exec services. Follow the instructions

given in Backup Exec Services on page 25 to stop the service.
b. Remove any previous plug-in version using either the
Windows Control Panel or
libstspiDataDomainUninstall.exe.
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 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.
3. When the Installation is complete, you can click the Show
details button to view the files installed and their location.
4. Restart all services. See Backup Exec Services on page 25.
5. Tune the Windows media server for DD Boost performance.

See Tuning Windows Media Servers for Performance on page 27.
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.
To upgrade the plug-in

1. Run the Backup Exec Services Manager and stop all services
(do not close the dialog box).
2. Remove the old plug-in and install the new plug-in.
3. Return to the Backup Exec Services Manager dialog box to

restart all services.
4. Close the dialog box.

Tuning Windows Media Servers for
Performance
This procedures applies to NetBackup and Backup Exec.
Tune the Windows media servers

1. Select Run from the Start menu and enter regedit in the text
box.
2. Go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\Tcpip\Parameters.
3. Right-click and select New. Enter the name Register-to-
set and select DWORD REG.
4. Right click Register-to-set and select Modify.
5. Do one of the following:
a. Set the value of this parameter:

TcpTimedWaitDelay =10
GlobalMaxTcpWindowSize = 4000000
TcpWindowSize = 262144
Tcp1323Opts = 1
EnablePMTUDiscovery =1
SackOpts = 1
TcpMaxDupAcks = 2
b. Copy and paste this data into a file with a .reg extension
-------------------------
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
Tcpip\Parameters]
"TcpTimedWaitDelay"=dword:0000000a
"GlobalMaxTcpWindowSize"=dword:003D0900
"TcpWindowSize"=dword:00040000

"Tcp1323Opts"=dword:00000001
"EnablePMTUDiscovery"=dword:00000001
"SackOpts"=dword:00000001
"TcpMaxDupAcks"=dword:00000002
------------------------------
6. Double-click the reg file, or import it from regedit.
7. You must reboot Windows for the settings to take effect.
Note: To address Windows 2003 SP2 network performance issues

on 32-bit Windows Servers 2003, search the Microsoft Support
knowledge base for related information.
Uninstalling the Windows Plug-in

This procedures applies to NetBackup and Backup Exec.
Uninstall the Windows plug-in

1. 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.

3 Data Domain Boost Features
These DD Boost features apply to NetBackup and Backup Exec:

• Distributed segment processing on page 29
• Advanced Load Balancing and Link Failover on page 33
• Low-Bandwidth Optimization Option on page 37
• Encrypted Optimized Duplication on page 36
For instructions on how to configure these features, see 4 Data

Domain Boost for OpenStorage Configuration.
Distributed segment processing

Distributed segment processing distributes parts of the
deduplication process to the OST plug-in, which avoids sending
duplicate data to the Data Domain system configured as a storage
server. The option to distribute the processing can be either
enabled or disabled on a Data Domain system. The OST plug-in
negotiates with the Data Domain system for the current setting of
the option and behaves appropriately. Therefore, the OST plug-in
offers two modes of operation for sending backup data to a Data
Domain system: one with distributed segment processing option
enabled and the other with the distributed segment processing
option disabled.

Figure 3-1: High-level Data Flow with distribute segment processing
disabled
Distributed segment processing disabled

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 in this scenario for a
single-system Data Domain system with distributed segment
processing disabled is shown in Figure 3-1. The OST plug-in runs
on the media server.
Distributed segment processing enabled

In this mode, the deduplication process is distributed between the
OST plug-in and the Data Domain system. The data flow for this
mode is show in Figure 3-2.
Parts of the deduplication process are run on the OST plug-in so
that only unique data is sent to data to a Data Domain system over
LAN. The OST plug-in segments, computes IDs for the segments,
checks with the Data Domain system for duplicate segments,
compresses unique segments that are not found on the Data
Domain system, and sends the compressed data to Data Domain
system. The Data Domain system then stores unique data on disk.
A high-level data flow for in this scenario for a single-system Data
Domain system is shown in Figure 3-2. The OST plug-in runs on
the media server.
Figure 3-2: High-level Data Flow with distributed segment

processing enabled
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 file 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 distributed segment processing 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.
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, the overall workload on the media
server, and the capability of the media server. In general,
greater throughput is attained with higher redundancy and
greater media server workload and media server capability.
• 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 backup application, the data already sent to
the Data Domain system does not have to be resent. This
results in faster completion of the backup on retry.
See the DD OS Administration Guide for more information about
local compression and its configuration.
You manage distributed segment processing via the ddboost
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 40.
Advanced Load Balancing and Link Failover

NetBackup 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 Link Failover feature allows
for combining multiple Ethernet links into a group. Only one of the
interfaces on the Data Domain system is registered with the
backup application. The OST 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 Link Failover works at the DD
Boost software 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.
Notes:
The optimized-duplication connection between the Data
Domain systems is not part of the load balancing. A single IP
address is used for the target Data Domain system.
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.
Figure 3-4 shows an example high-level configuration diagram. The
interface marked in red is registered with the backup application.
Figure 3-4: Example Advanced Load Balancing and Link Failover

Configuration Diagram
The Advanced Load Balancing and Link Failover feature can be
used in conjunction with other network layer aggregation and
failover technologies. The sample configuration in Figure 3-4 shows
one such possibility. The links connecting the media servers and
the switch that connects to Data Domain system are put in an
aggregated failover mode. This configuration provides network
failover functionality from end-to-end in the configuration. Any of

the available aggregation technologies can be used between the
media server and the switch.
The Advanced Load Balancing and Link Failover functionality also
works in conjunction with other network layer functionality on the
Data Domain systems, including VLAN tagging and IP aliasing.
This functionality allows additional flexibility in segregating traffic
into multiple virtual networks, all of which run over the same
physical links on the Data Domain system.
Note: See the DD OS 5.0 Administration Guide for more
information about how to configure VLAN tagging and IP aliasing
on a Data Domain system.
Benefits of Advanced Load Balancing and Link 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.
• 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.
• All in-flight jobs to the failed interface transparently are failed
over to healthy operational links. From the point of view of the
backup application (NetBackup or Backup Exec), the jobs
continue uninterrupted.
For more information, see Configuring Advanced Load Balancing and
Link Failover on page 41.
Configuration Restrictions
• The interfaces can be added only to the group using an IP
address.
• Even though the Advanced Load Balancing and Link 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 Global Deduplication Arrays.
Encrypted Optimized Duplication

The media servers (NetBackup or Backup Exec) set up optimized
duplication jobs between two Data Domain systems after
authenticating them using the pre-configured DD Boost user name
and password. When an optimized job is set up by the media
servers, if encrypted optimized duplication is enabled, the source
and destination Data Domain systems encrypt the session between
the two Data Domain systems using Secure Sockets Layer (SSL), so
all image data and metadata is sent encrypted over WAN.
Enabling this option on Data Domain system is transparent to the
backup applications (NetBackup and Backup Exec). When the
backup application requests Data Domain system to perform an
optimized duplication job, the source and destination systems
negotiate automatically to perform encryption without knowledge
of the requesting backup application. Encrypted optimized
duplication uses the ADH-AES256-SHA cipher suite. There is no
ability to configure a different suite in DD OS 5.0.
Encrypted optimized duplication is available to Data Domain
systems with an installed Replicator license. The option is enabled
on a per Data Domain system basis and applies to all optimized
duplication jobs on that system. Both the source and the
destination Data Domain systems that are participating in
optimized duplication jobs must have this option enabled for it to
take effect.
Encrypted optimized duplication can be used in conjunction with
the encryption of data-at-rest feature available on DD OS with the
optional Encryption license. When encrypted optimized
duplication is used with the encryption of data-at-rest feature, the
encrypted backup image data is encrypted again using SSL for
sending over WAN.

Notes:
Both the source and the destination Data Domain systems must
be running DD OS 5.0 or later to use this feature.
Enabling this feature does not require restarting the file system
on a Data Domain system.
The low-bandwidth optimization option and the encryption
can be used in conjunction with each other.
For more information, see Enabling Encrypted Optimized Duplication
on page 43 and the discussion of this topic in the DD OS 5.0
Administration Guide.
Low-Bandwidth Optimization Option

The low-bandwidth Replicator 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 and
is recommended only for optimized duplication jobs that occur
over WAN links that have fewer than 6 Mb/s of available
bandwidth.
The low-bandwidth optimization option is available to Data
Domains systems with an installed Replicator license. The option
is enabled on a per Data Domain system basis and applies to all
optimized duplication jobs on that system.
Enabling this option on Data Domain system is transparent to the
backup application. When the backup application requests a Data
Domain system to perform an optimized duplication job, the
source and destination systems automatically perform the
additional compression without involvement of the requesting
backup application.
All Data Domain systems that participate in optimized duplication
jobs must have this option enabled for it to take effect.
For more information, see Enabling Low-Bandwidth Optimization on
page 42, and the discussion of this topic in the DD OS 5.0
4 Data Domain Boost for
OpenStorage Configuration

• Configuring the Data Domain System on page 39
• Creating Storage Units on page 40
• Configuring distributed segment processing on page 40
• Configuring Advanced Load Balancing and Link Failover on

page 41
• Enabling Low-Bandwidth Optimization on page 42
• Registering Each Data Domain System on page 45
• Enabling Encrypted Optimized Duplication on page 43
• Configuring a Media Server on page 44
• NetBackup Configuration on page 44
• Backup Exec Configuration on page 66
Configuring the Data Domain System

You need to create one or more storage units for each Data Domain
system enabled for OpenStorage in a NetBackup or Backup Exec
installation. In a NetBackup system, a storage unit corresponds to
disk pools on the media server whereas in a Backup Exec system, it
corresponds to a tape repository.
Note: The following procedures for configuring a Data Domain
system apply to NetBackup and Backup Exec.

Creating Storage Units
Create storage units
1. On the Data Domain system, enter:
# ddboost storage-unit create storage-unit_name
Each storage unit name must be unique.
2. Repeat the above step for each Boost-enabled Data Domain
system.
Configuring distributed segment processing

The distributed segment processing option is configured on the
Data Domain system and applies to all the media servers and the
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 system Data Domain
systems and Figure 3-3 on page 32 for Global Deduplication Array
systems.
The option can be configured using the following command:
# ddboost option set distributed-segment-processing
{enabled | disabled}
Note: Enabling or disabling the distributed segment processing
option does not require a restart of the Data Domain file system.
Distributed segment processing is supported with OST plug-in 2.2
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 DD Boost 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.
40 Data Domain Boost for OpenStorage Configuration

Configuring Advanced Load Balancing and Link
Failover
Steps 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 Link

Failover
1. Add the interfaces into the group:
# ddboost ifgroup add interface 192.168.1.1
Note: Only one default interface group can be created in DD OS
4.8, 4.9, or 5.0 releases, and this group cannot be named.
2. Select one of the interfaces on the Data Domain system to
register with the backup application. It is recommended that
you create one failover aggregated interface and register that
interface with the backup application.
Note: It is not mandatory to have one of the interfaces in the
ifgroup registered with the backup application. An interface
that is not part of the ifgroup can also be used to register 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
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 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:
# ddboost ifgroup enable
4. Verify the configuration Data Domain system:
# ddboost 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 Link Failover
via the ddboost ifgroup commands.
After the interface group is setup, you can add or delete interfaces
from the group. See Modifying an Interface Group on page 99.
Enabling Low-Bandwidth Optimization

To enable the low-bandwidth option, enter:
# ddboost file-replication 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,
however, you need to run a full cleaning cycle on the Data Domain
system for it to be effective.
See ddboost file-replication on page 85 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.
Notes:
For more information on this feature, see the DD OS 5.0
The low-bandwidth option for optimized duplication is
supported only for standalone Data Domain systems.
Enabling Encrypted Optimized Duplication

To enable the low-bandwidth option, enter:
# ddboost file-replication option set encryption
enabled
The output indicates that the encryption you requested was
enabled.
See the ddboost file-replication on page 85 for more details on how
to monitor and manage encryption option for optimized
duplication.
No configuration changes are necessary on the media server as this
feature is transparent to the backup applications NetBackup and
Backup Exec. Turning on this feature takes additional resources
(CPU and memory) on Data Domain system.
Notes:
Enabling or disabling the encrypted optimized duplication
option does not require a restart of the Data Domain file
system.
For more information on this feature, see discussion of this
topic in the DD OS 5.0 Administration Guide.

Configuring a Media Server
Media server configuration depends on the backup application
being used. See the appropriate configuration section.
• NetBackup Configuration on page 44
• Backup Exec Configuration on page 66
NetBackup Configuration
Note: The examples in this chapter assume the following
configuration:
• A media server with the name load64 that runs NBU 6.5 or
7.0.
• DD Boost-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.
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 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 and Backup Exec, the default number of
concurrent connections (jobs) from a single media server is 64. To
increase this number, contact your EMC technical consultant.
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 plug-in
version.
3. Register a Data Domain system by entering:
# nbdevconfig -creatests -stype DataDomain
-storage_server dd22 -media_server load64
In this case, the storage_server can be either an IP address or
a hostname, such as dd22.
Note: NetBackup 7 allows the credentials to be configured
from within NetBackup as well. See the NetBackup
documentation for more information.
4. Repeat the above procedure for each DD Boost-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
Note: NetBackup 7 allows the credentials to also be configured
from within NetBackup. See the NetBackup documentation for
more information.
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
storage units.
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.
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 storage unit 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_storage-unit1_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_storage-unit1_dp has been
successfully created with 1 volume.
Create a disk pool using the GUI

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

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.
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 storage unit in the Volume Name list, and
click Next.
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 50.
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_storage-unit1_su -dp
dd22_storage-unit1_dp
-host load64a -M load64a
Note: There is no output from this command.
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.
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 OST
plug-in has been installed and that its login credentials have been
configured.
8. Click OK.

Creating a Backup Policy
For instructions on creating a backup policy, see the Symantec
NetBackup Administration Guide.
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
• 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.
• 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 OST plug-in enables a NetBackup 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 files and keeps track of all copies in its
catalog, which ensures easy and efficient recovery.
• Optimized duplication removes the media server from the data
path in creating duplicate copies of backup images, which
reduces the load on the backup application system and frees it
for other work.
• The Data Domain system uses Wide Area Network (WAN)
efficient replication process for deduplicated data. The process
is optimized for WANs, which reduces the overall load on the
WAN bandwidth required for creating a duplicate copy.
• Data Domain Replicator software features, such as Low-
Bandwidth Optimization Option, can be used transparent to
the backup application to reduce further the data sent over
WAN links that are fewer than 6 Mb/s.
• Data Domain Replicator software features, such as Encrypted
Optimized Duplication, can be used transparent to the backup
applications. This feature allows all data sent over the WAN
for the purpose of creating duplicate copies to be encrypted,
which provides higher security.

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 file 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 files and a retention period for each file. A lifecycle process
creates, retains, and finally expires the files. 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.
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 the Symantec NetBackup documentation.
Create a storage lifecycle policy

This example creates a lifecycle policy that backs up to a DD Boost-
enabled Data Domain system and then creates a duplicate copy on
another DD Boost-enabled Data Domain system. There are two
storage destinations. The first serves as backup to the first DD
Boost-enabled Data Domain system. The second storage
destination is used for duplication to the second DD Boost-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.

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_storage-unit1_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

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.
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.
Note: NetBackup 6.5.4 introduced Hierarchical Duplication,

which allows creation of up to ten duplicate copies using Storage
Lifecycle Policies. Policies can be defined such that the third copy
can be sourced from the second copy, which is the first duplicate
copy. See the NetBackup documentation for more information.

Optimized Synthetic Backups
Optimized Synthetic backups creates a full backup image from
incremental backup images and an older full backup image. The
source, incremental, and old full backup images are read internally
in the Data Domain system and then written to the target image on
the same Data Domain system.
Optimized synthetic backups provide the following benefits:
• Enables the ability to create a full backup without the need
actually do a full backup. This reduces the backup windows for
protecting large file systems.
• Provides performance enhancement in creating synthetic
backups since the data from the source images (incremental
and full) to the target image do not traverse the network.
• Reduces the load on media servers as they are no longer in the
data path when creating a synthetic backup.
• The synthetic backups do not take any additional space on the
Data Domain system as the data for the synthetic backup is
deduplicated against existing data for incremental backups
and older full backups that are already written to the Data
Domain system.
The following limitations apply to synthetic backups in general:
• The policy type must be either Standard or MS-Windows.
• The Collect True Image Restore Information With Move
Detection option must be selected on the policy Attributes tab.
• The schedule that is created for a synthetic backup must have
Synthetic Backup selected.
• At least one traditional, full backup must be run successfully to
create a full image. The synthetic backup jobs fails if there is
not at least one previous full image.
For more information on configuring synthetic backups, see the
NetBackup Administrator's Guide. There are no special
considerations for creating optimized synthetic backups. All of the
policy attributes that apply to regular synthetic backups, also
apply to optimized synthetic backups.

Number of Streams Supported
Each optimized synthetic backup accounts for two streams—one
write and one read stream. Therefore, the maximum number of
concurrent streams for the synthetic backup cannot exceed half of
the total streams supported for the Data Domain system.
Configuring Optimized Synthetic Backups

For NetBackup policies, this capability is utilized with the
synthetic backup. The policy option for synthetic backup,
documented by Symantec, should be followed. Prior to this
release, the synthetic backup would have resulted in a read of the
source image files followed by a write to the target image.
If you already have NetBackup installed with a storage unit
defined, you need to enable the feature prior to using it. Enter:
# nbdevquery -listdp -U -dp disk pool name
# nbdevconfig -changests -storage_server storage
server name -stype storage server type
-setattribute OptimizedImage
# nbdevconfig -changedp -dp disk pool name -stype
storage server type -setattribute OptimizedImage
Use the following command to verify the OptimizedImage:
# nbdevquery -listdp -U -dp disk pool name

For example:
# nbdevquery -listdp -U -dp ddr12-su
Disk Pool Name : ddr12-su
Disk Pool Id : ddr12-su
Disk Type : DataDomain
Status : UP
Flag : Patchwork
Flag : Visible
Flag : OpenStorage
Flag : SingleStorageServer
Flag : CopyExtents
Flag : AdminUp
Flag : InternalUp
Flag : LifeCycle
Flag : CapacityMgmt
Flag : FragmentImages
Flag : Cpr
Flag : FT-Transfer
Flag : OptimizedImage
Raw Size (GB) : 4922.90
Usable Size (GB) : 4922.90
Num Volumes : 1
High Watermark : 98
Low Watermark : 80
Comment :
Storage Server : rtp-ddr12.datadomain.com
Creating a Policy for Synthetic Backup Using NetBackup

This example creates a policy that executes a full backup,
subsequent differential incremental backups, and synthetic full
backups based on the full and incremental backups. When this
policy is used in conjunction with a DD Boost-enabled Data
Domain system running DD OS 5.0.0 or later and with OST plug-in
3.0.0 or later, NetBackup invokes optimized synthetics on the Data
Domain system, which creates the synthetic backup without any
data movement over the network.
Note: There are no special settings for creating a policy for using
optimized synthetics. You can use the same backup policy to create
regular synthetic backups as for optimized synthetics, but must
use the appropriate DD OS and OST plug-in versions.

To create a new policy (called test57):
1. Open the NetBackup Administration Console’s Storage dialog
box.
2. In left pane of the window, expand NetBackup Management >
Storage. Right-click Policies. Select New Policy from the menu.
3. In the Add New Policy dialog box, the Policy type must be
either MS-Windows or Standard. Select Collect true image restore
information.
4. Select the Schedules tab and add schedules for full backup,
incremental backups, and synthetic backups as shown in the
figures below.

Figure 4-1: Adding a Schedule for a Full Backup (RealFull)
Note: An initial full backup must be performed before a synthetic
full backup.
Figure 4-2: Adding a Schedule for a Daily Differential Incremental

Backup (DailyIncremental)

Figure 4-3: Adding a Schedule for a Synthetic Backup (SyntheticFull)
After schedules for full, incremental, and synthetic backups are
created, the Schedule tab resembles Figure 4-4.
Figure 4-4: Schedule Tab

5. After the schedule is created, make appropriate selections in
the Clients tab to create the new policy that executes synthetic
backups.

Note: You can make other necessary changes before creating the
policy. See the NetBackup Administrator’s Guide for details.
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-5: 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.
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
user name and password set for DD Boost. 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.
Configuring Devices
Follow these steps to configure devices.
Configure devices
1. Create a storage unit on the Data Domain system. See Creating
Storage Units on page 40.

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.
• Storage unit: Select 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 OST plug-in to all associated OpenStorage
storage units is 48. The concurrent operations limit for a single
device can be determined as follows:
48 >= # OpenStorage storage units + ∑ concurrent operations
for each storage unit
In the case of a single Data Domain system with a single
storage unit, the concurrent operation count can be set as high
as 47.

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 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.
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 storage unit is
displayed in the Devices page (Figure 4-6).
Figure 4-6: Backup Exec Devices
Configuring Optimized Duplication

The ways to develop duplication jobs in Backup Exec are described
in detail in the Symantec Backup Exec 2010 Administrator’s Guide.
You can attach an associated duplicate job to any backup job, or
duplicate a previous backup set.
The 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 files 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 files, which reduces the load on
the backup application system and frees it for other work.

• The Data Domain system uses Wide Area Network (WAN)
efficient replication process for deduplicated data. The process
is optimized for WANs, which reduces the overall load on the
WAN bandwidth required for creating a duplicate copy.
• Data Domain Replicator software features, such as Low-
Bandwidth Optimization Option, can be utilized transparent to
the backup application for further reducing the data sent over
WAN links that are less than 6 Mb/s.
• Data Domain Replicator software features, such as Encrypted
Optimized Duplication, can be used transparent to the backup
applications. This feature allows all data sent over the WAN
for the purpose of creating duplicate copies to be encrypted,
which provides higher security.
Data Domain recommends that you add the destination Data
Domain system’s IP address to the source Data Domain system
using the command:
net hosts add ipaddr {host | "alias host"}
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.
To duplicate an image from one system to another, the following
conditions must be met:
• The Data stream chunk size for devices configured on both
Data Domain systems between which optimized duplication is
to take place must be set to the same value. It is recommended
that this value be 256 KB as shown in the OpenStorage Device
Properties dialog box.

Figure 4-7: OpenStorage Device Properties (General Tab)
This value is set during storage unit creation when the media
device representing the storage unit on the Data Domain
system is added to Backup Exec.
• The Concurrent Operations count of the destination Data
Domain system is greater than or equal to that of the source
Data Domain system. See Figure 4-7.
Add a duplication job to an existing job

These instructions assume that you have developed a backup job
that is running (or scheduled to be run) in order to generate a
backup set on the source Data Domain system (media device ddr5).
1. Open the Job Setup panel.

2. In the left panel, select Backup Tasks > New job to duplicate
backup sets.
3. In the New Job to Duplicate Backup Sets dialog box, select the
Duplicate backup sets following a job option, and click OK.
4. In the Source > Job panel, select an available job that is running
or scheduled to be run, pf86, as shown below.
5. In the Destination > Device and Media panel, select the remote
Data Domain system, in this case a device named ddr8 as
shown below. Complete file options as required.

6. In the Settings > General panel, verify that the source Data
Domain system is set properly, in this example a device named
ddr5 as shown below.
The Job Monitor panel displays the status of the jobs as they are
scheduled and run.

The scheduled backup jog, pf86, and a scheduled duplicate
backup job are shown below:
Each time the backup job runs, the duplicate job is run after it.

The Job History contains job statistics and log events for each of
two jobs:

Duplicate a previous job
Prerequisite: An existing backup job and at least one backup set
saved on the source Data Domain system (media device named
ddr5 in this example).
1. Open the Job Setup panel.
2. Select the New job to duplicate backup tasks in the left hand
sub-panel:
3. In the New Job to Duplicate Backup Sets, select the Duplicate
existing backup sets option, and click OK.

4. In the Source > Selections panel, select an available media set
that has been created on media device ddr5.
5. In the Destination Device and Media panel, select the remote

Data Domain system, in this case a device named ddr8.
Complete file options as required.

6. In the Settings > General panel, verify that the source Data
Domain system is set properly, in this example a device named
ddr5.
7. You can schedule this duplication for later, or click Run Now
to start it.
The Job Monitor panel displays the status of the job as it runs.

Upon completion the job is moved to the Job History list.
The Job History contains job statistics and log events.

5 Using the DD Boost
Commands
This chapter describes the DD Boost commands that you use to

manage the DD Boost feature on the Data Domain system.
Note: For information about configuring DD Boost using the
graphical-user interface-based Enterprise Manager, see the DD OS
5.0 Administration Guide.
The ddboost command includes the following options.
destroy Delete all storage units and their contents Page 82
from the Data Domain system.
disable Disable DD Boost. Page 82
enable Enable DD Boost. Page 82
ifgroup For Advanced Load Balancing and Link Page 82
Failover:
Manage interface group (IP addresses) on a
Data Domain private network that
processes data transfer.
file- Set, reset, or show the status of the low- Page 85
replication bandwidth optimization and/or
encryption option for optimized
duplication. Show or reset statistics,
history, and performance.
option Set, reset, or show the status of the Page 90
distributed segment processing feature.
reset Delete the DD Boost user and reset Page 91
statistics. Clear all job connection counters
shown in the output of the ddboost show
connections command in the event that
network connection is lost
show Show the DD Boost connections, DD Boost Page 92
histogram, or statistics.

status Show whether DD Boost is enabled or Page 94
disabled.
storage-unit Create and delete a storage unit, or list the Page 95
storage units and files in a storage unit.
user-name Reset, set, or show DD Boost users. Page 95
ddboost Command Options
enable
ddboost enable
Administrators use this command to enable DD Boost.
Whenever the user, user ID (UID), or group ID (GID) changes, the
Data Domain system updates all files and storage units the next
time that the ddboost enable command is issued.
destroy
ddboost destroy
Administrators use this command to delete all storage units and
their contents from the Data Domain system. The command
permanently removes all of the data (files) contained in the storage
units.
You must also manually remove (expire) the corresponding
catalog entries.
disable
ddboost disable
Administrators use this command to disable DD Boost for the Data
Domain system.
ifgroup
Notes:
ifgroup is an interface group.
82 Using the DD Boost Commands

Advanced Load Balancing and Link Failover is not supported
for a Global Deduplication Array.
ifgroup add interface

ddboost 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 Link Failover using the ddboost
ifgroup enable command.
Notes:
• If an interface (or a NIC that has multiple interfaces) fails, all
the in-flight jobs to that interface transparently fail over to a
healthy interface in the ifgroup. Any jobs that are started
subsequent to the failure are routed to the healthy interfaces.
You can add public or private IP addresses for data transfer
connections.
• It is not recommended that you use 1 GigE and 10 GigE
connections in the same interface group.
• You can add public or private IP addresses for data transfer
connections.
ifgroup del interface

ddboost 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 disable
ddboost ifgroup disable
Administrators use this command to disable the Advanced Load
Balancing and Link Failover option for new jobs. Currently
running jobs are not affected and continue to run.
If DD Boost is disabled, the message disabled is displayed.
ifgroup enable
ddboost ifgroup enable
Administrators use this command to enable Advanced Load
Balancing and Link Failover. At least one IP address must have
already been added.
ifgroup show config

ifgroup show config
Use this command to show the IP addresses that have been added
to the ifgroup.
ifgroup reset
ifgroup reset
Administrators use this command to reset Advanced Load
Balancing and Link Failover links.
For a reset to occur, the Advanced Load Balancing and Link
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 Link Failover links are reset, a
message to this effect is displayed.

ifgroup status
ifgroup status
Use this command to show whether Link Aggregation is enabled
or disabled.
file-replication
Note: The low-bandwidth optimization option is not supported in
a Global Deduplication Array.
file-replication option reset

ddboost file-replication option reset {low-bw-optim |
encryption}
Administrators can use this command to reset low-bandwidth
optimization and/or encryption to its default value, which is
disabled.
file-replication option set

ddboost file-replication option set {encryption {enabled |
disabled}|low-bw-optim {enabled | disabled}
This command must be entered on both Data Domain systems—
the source and destination (target) systems. Only an administrator
can set these two options.
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.
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. Encryption
must be enabled on both the source and destination systems.

file-replication option show
ddboost file-replication option show [low-bw-optim]|
[encryption]
Use this command to show whether low-bandwidth optimization
and/or encryption is enabled or disabled for optimized
duplication.
file-replication reset stats

ddboost file-replication reset stats
Administrators can use this command to reset file-replication
statistics when DD Boost is enabled.
file-replication show active

ddboost file-replication show active
Use this command to show the status of a DD Boost file replication
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.
file-replication show detailed-file-history

ddboost file-replication show detailed-file-history [duration
duration{day | hr}]
This command shows the file-replication history over time. The
output is organized by file; it is not cumulative data. You must
specify a duration.
The data for each file name is organized by date, time, and
direction (outbound or inbound). Values are given in KB for pre-
compressed, post-filtered, post-low-bw-option, post-compressed,
and network data. The last value is an error code; 0 indicates no
error occurred. A sample line with a description of each column
follows:
• Date: 2010/06/16
• Time: 07:48:22
• Direction: Outbound
• File name:
/data/col1/x-ddp1/PEOST_00000001:0000000000:BEOST:4:0::
• Pre-compressed: 3,765,837
• Post-filtered: 30,802
• Post-low-bw-optim: 30,802
• Post-compressed: 17,423
• Network: 65,550
• Error code: 0
file-replication show detailed-history

ddboost file-replication show detailed-history [duration
duration{day | hr}] [interval hr]
This command shows the file-replication history over time. A
cumulative history is shown, as opposed to a view by file name.
You must specify a duration.
Data is organized by date, time, and direction (outbound or
inbound). Cumulative values are given in KB for pre-compressed,
post-filtered, post-low-bw-option, post-compressed, and network
data. The last value is an error code; 0 indicates no error occurred.
file-replication show history

ddboost file-replication 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
• low-bandwidth optimization factor

• number of errors
Example of Boost file-replication show history command output:
Date Time Direction Pre- Post- Netwo Low- Errors

Comp Comp rk (KB) bw-
(KB) (KB) optim
2010/08/31 11:14 Inbound 47,738 26,634 27,527 1.32 0
2010/08/31 11:14:09 Outbound 14,327 8,638 9,034 1.21 0
file-replication show file-history

ddboost file-replication show file-history [duration
duration{day | hr}]
Use this command to show the data transfer history for inbound
and outbound traffic on each file 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 Boost file-replication show file history command

output:
Date Time Directio Filename Pre-Comp Post-Comp Network Low-bw- Error
n (KB) (KB) (KB) optim s
2009/08/31 15:13:09 Inbound /backup/so 47,738 26,634 27,527 1.32 0

urce.tar
2009/08/31 15:13:09 Outboun /backup/d 14,327 8,638 9,034 1.21 0

d estin.tar

file-replication show performance
ddboost file-replication 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
file-replication show stats

ddboost file-replication 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,271
Compression ratio: 4.9
option
option reset
ddboost option reset distributed-segment processing
Administrators use this command to reset distributed segment
processing to the default option, which is enabled.
option set
ddboost option set distributed-segment-processing {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 5.0. 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.2 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 DD Boost license is installed at the time of the
upgrade, distributed segment processing is not
automatically enabled.
• If a system is upgraded from DD OS 4.9 to DD OS 5.0 and
the boost option was disabled before the upgrade, then
the distributed-segment-processing option is disabled after
the upgrade.
Distributed segment processing feature is always enabled in a
Global Deduplication Array, and it cannot be disabled.
option show
ddboost option show distributed-segment processing
Use this command to show whether the distributed segment
processing option is enabled or disabled.
reset
reset stats
ddboost reset stats
Administrators use this command as follows:
• to reset all statistics when DD Boost is enabled, or
• as a network recovery procedure to clear job connections after
the network connection has been lost.

show
show connections
ddboost 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 DD Boost,
and whether these connections are spread across interfaces
using Advanced Load Balancing and Link Failover. (See
sample output for client connections below.)
• 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 DD Boost.

Note: For a Global Deduplication Array, the ifgroup status is
always disabled, and the Member column value is always no.
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 file-replication, file operations
show histogram
ddboost show histogram op
Use this command to display a DD Boost histogram for the Data
Domain system.
op The name of the NFS operation.
mean-ms The mathematical mean time for completion of the
operations.
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 The number of operations that took less than the
10ms 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.
show stats
ddboost show stats [interval seconds] [count count]
Use this command to show the output of previous show stats
command, the number of bytes written to and read from files
contained in storage units, and the number of files created and
deleted from storage units. The number of errors encountered for
each operation is also shown. Optionally, you can show statistics
for a specific number of seconds. The count displays the number of
lines equal to the count value.
If distributed segment processing is enabled, the number of bytes
transferred via distributed segment processing and the amount of
compression achieved is displayed.
status
ddboost status
Enter this command to determine whether DD Boost is enabled or
disabled.

storage-unit
storage-unit create
ddboost storage-unit create storage-unit-name
Administrators use this command to create a storage unit with a
given name.
storage-unit delete
ddboost storage-unit delete storage-unit-name
Administrators use this command to delete a specified storage unit
and all of its contents. You must also manually remove (expire) the
corresponding catalog entries.
storage-unit show
ddboost storage-unit show [compression] [storage-unit-name]
Use this command to display the names of all storage units or,
optionally, the names of all files in a specified storage unit.
To display the compression for all storage units (the original byte
size, global compression, and local compression for all storage
units), enter the compression option.
Note: To interrupt the output of this command, press Ctrl+C.
user-name
reset
ddboost reset user-name
Use this command to delete the specified DD Boost user.
set
ddboost set user-name user-name
Administrators use this command to set the DD Boost user name
when DD Boost is enabled.

show
ddboost show user-name
Use this command to display the current DD Boost user.

6 Administration
This chapter covers the following major topics:

• Data Domain System Administration on page 97
• NetBackup Administration on page 102
• Backup Exec Administration on page 104
Data Domain System Administration

• Restricting Export Permissions to DD Boost on page 97
• Optimized Duplication Version Compatibility on page 99
• Modifying an Interface Group on page 99
Restricting Export Permissions to DD Boost

Data Domain systems export the default mount created for
DD Boost /backup/ost as follows:
/backup/ost *
(rw,no_root_squash,no_all_squash,insecure)
By default, with this export definition, the DD Boost service is
accessible to all media server clients. To restrict access to a certain
set of media servers, remove this default export definition and add
a new export definition to specify only those media servers.
This example shows removing the default export and adding a
new export definition with access restricted to two specific media
servers, mediaserver1.datadomain.com and
mediaserver2.datadomain.com:
ddboost disable
nfs del /backup/ost *
nfs add /backup/ost mediaserver1.datadomain.com
mediaserver2.datadomain.com
(rw,no_root_squash,no_all_squash,insecure)
ddboost enable
This set of steps creates an export entry that enables DD Boost
access only to the two specified media servers. You must explicitly
specify the export options (rw,no_root_squash,
no_all_squash,insecure) that are to override the default
export option of secure. The insecure option is required to
allow the DD Boost client software to use a broader range of host-
side TCP port numbers.
If there is no specific export entry established, the ddboost
enable operation installs the default export entry, which allows
all hosts to access the DD Boost service. However, if there is any
export entry already established for /backup/ost, the ddboost
enable operation does not modify the export list, thus allowing
the already-installed export controls to be honored.
Prior to DD OS 5.0, the default /backup/ost * entry was always
added during ddboost enable.
Notes:
Disabling DD Boost disables data access to all media servers.
Administrators need to ensure that no backup jobs are running
to the Data Domain system during these operations.
A fully-qualified domain name, an IP address, or a DNS
resolvable name of the client must be specified during the
modification of the client access list.
The rw option is required on the export entry to allow the
media server to write backup data to the Data Domain system.
98 Administration
Optimized Duplication Version Compatibility
The 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.
• 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.
• To configure encrypted optimized duplication, both the source
and the destination must run DD OS 5.0 or later.
Modifying an Interface Group

After 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:
• # ddboost show connections

Sample output:
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 file-replication, file operations
Figure 6-1: Sample Output for ddboost ifgroup show

connections Command
2. Remove the interface from the group on Data Domain system:
# ddboost 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 DD Boost Storage Server
for any jobs from the media servers.
Note: Removing the interface registered with the backup
application makes the Data Domain system inaccessible to the
media servers. The configuration of the ifgroup on the Data
Domain system is not deleted.
100 Administration
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
ifgroup, execute the ddboost show connections command to
update the load balancing view. This updating allows the ifgroup
to use the interface. See page 92 for more information about the
ddboost show connections command.
Removing Advanced Load Balancing and Link

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:
# ddboost ifgroup show connections
See Figure 6-1 on page 100 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:
# ddboost ifgroup disable
4. Reset the interface group:
# ddboost ifgroup reset
All the interfaces are released from the group. However, media
servers can still access the DD Boost 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.

NetBackup Administration
This section covers the following topics and procedures:
• Find your OST plug-in version on page 102
• Find your NetBackup version on page 102
• Network Time-Outs on page 102
• Grouping Storage Units to Provide Failover on page 103
Find your OST plug-in version

Enter:
# bpstsinfo -pi
The output shows the vendor version, the plug-in version, and the
build 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
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).
102 Administration
Note: After losing a network connection, administrators should
issue the ddboost 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.
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

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 files 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 files, lifecycle policies,
storage units, and disk pools.
For troubleshooting information, see Unable to Delete the Data
Domain System on page 108.
6. Remove the credential using the tpconfig command.
# tpconfig -update-storage_server dd22 -stype

DataDomain -sts_user_id username -password password
Backup Exec Administration

• Find your OST plug-in version on page 105
• Find your Backup Exec version on page 105
• Delete storage units on Data Domain Systems on page 105
• Recover backup files on an OpenStorage device on page 105
104 Administration
Find your OST plug-in version
1. 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 plug-in version is displayed as

the file version.
Find your Backup Exec version

From the Backup Exec Home page, select About from the Help
menu.
Delete storage units on Data Domain Systems

There are two options for deleting a storage unit on a Data Domain
system:
• You can erase all media within a Backup Exec device (a Data
Domain system’s storage unit) 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 storage unit remains on the Data
Domain system and some files are left in the storage unit. To
recover this space, delete the storage unit on the Data Domain
system by entering:
# ddboost storage-unit delete storage-unit name
Recover backup files on an OpenStorage device

1. From the Backup Exec Home page, select the Devices tab.
2. Select the Data Domain system storage unit on the Devices

page.
3. Select a media label.
4. Right-click the media label, and select Restore from the menu.

106 Administration
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 107
• Data Domain System Settings for File-Replication on page 108
• NetBackup Troubleshooting on page 108
• Backup Exec Troubleshooting on page 116
For more information, see the Data Domain Knowledge Base,

which is available at (https: //my.datadomain.com.
General Troubleshooting
When investigating problems, be aware that the DD Boost
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 DD Boost for OpenStorage Compatibility List. A supported
configuration can become unsupported if any component
changes.
This list is available from the Data Domain Support portal
(https: //my.datadomain.com). Navigate to the Documentation >
Compatibility List page and select DD Boost 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 44 provides instructions on
establishing user credentials.
Data Domain System Settings for File-

Replication
For all DD OS versions, the replication throttle command
controls replication. Setting the throttle too low can lead to
optimized duplications to fail for NetBackup and Backup Exec.
NetBackup Troubleshooting
Unable to Delete the Data Domain System

This 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 files for the specified Data Domain have expired. For
instructions on how to expire a file, 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 111.
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 111.
Check the Installation

Problems 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 include 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 DD
Boost API.
Note: If the bpstsinfo command fails, check the log files in the
/usr/openv/netbackup/logs/admin directory.
Check Credentials
To 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 46, which describes how to
set up credentials and check for errors and inconsistencies.
Resolve License Error

If 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 Servers

The error log is the main tool for troubleshooting problems related
to NetBackup in an OpenStorage 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.
Resolving Failed Backups on Media Servers

Search 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 file 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_file:
/usr/openv/netbackup/logs/bpdm
• For write_file:
/usr/openv/netbackup/logs/bptm
• For file-replication:
/usr/openv/netbackup/logs/bpdm
Windows
• For read_file:
C:\Program Files\Veritas\logs\bpdm
• For write_file:
C:\Program Files\Veritas\logs\bptm
• For file-replication:
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 Messages

When 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 53.
• Program Not Registered

The following output indicates that the program is not
registered:
(: RPC: Program not registered)
2. Enable DD Boost by installing a valid license:
# license add ddboost-license-code
3. Verify that the file system is running on the Data Domain
system by entering:
# filesys status
Cannot Connect on Socket Error

This 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 a file 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

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 Fails

The 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 storage units.

• Backup Exec: The total number of concurrent connections
from a single media server plug-in to all associated
OpenStorage storage units is 16. This number was specified
when you configured the device. See Configuring Devices on
page 67.
• 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 Installation

Problems 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 system

1. 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.
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 user name set for DD Boost and
password on the Data Domain system.
Resolve License Error

1. 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 debugging

Use 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.

Figure 7-3: Settings Menu
The log file that is captured is named media server-
SGMon.txt. It is located in the logs directory.

Data Domain Boost Admin Guide 759-0008-0001

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Domain Boost Admin Guide 759-0008-0001

Uploaded by

Copyright:

Available Formats

Data Domain Boost for

Backup Recovery Systems Division

July 23, 2010

About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Introducing Data Domain Boost for OpenStorage . . .15

2 Installing Data Domain Boost for OpenStorage . . . . .17

DD Boost for OpenStorage Administration Guide 3

3 Data Domain Boost Features . . . . . . . . . . . . . . . . 29

4 Data Domain Boost for OpenStorage Configuration . 39

5 . . . . . . . . . . . . . . . Using the DD Boost Commands 81

DD Boost for OpenStorage Administration Guide 5

DD Boost for OpenStorage Administration Guide 7

This guide explains how to install, configure, and use Data

DD Boost for OpenStorage Backup Application

DD Boost for OpenStorage Administration Guide 9

• NetBackup 6.5 Hardware Compatibility List that includes

Symantec Backup Exec Documentation

10 About This Guide

Access Data Domain Documents

DD Boost for OpenStorage Administration Guide 11

Typeface or Usage Examples

12 About This Guide

Data Domain Support

DD Boost for OpenStorage Administration Guide 13

Data Domain Boost (DD Boost) for OpenStorage enables media

DD Boost for OpenStorage Administration Guide 15

16 Introducing Data Domain Boost for OpenStorage

This chapter covers the following topics:

• NetBackup Installation on page 19

• Backup Exec Installation on page 24

• Tuning Windows Media Servers for Performance on page 27

4. After completing the installation steps described in this

DD Boost for OpenStorage Administration Guide 17

Firewalls and Ports

Enabling DD Boost on a Data Domain System

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

18 Installing Data Domain Boost for OpenStorage

DD Boost for OpenStorage Administration Guide 19

Add these directories to the UNIX PATH

Add these directory locations to the UNIX PATH

Add these directory locations to the Windows

Installing the OST Plug-In on Media Servers

20 Installing Data Domain Boost for OpenStorage

3. Stop the backup application’s Remote Manager and Monitor

5. Use the tar command to uncompress the file:

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

Correct UNIX plug-in installation or update

DD Boost for OpenStorage Administration Guide 21

Install the Windows plug-In

Prepare for installation

22 Installing Data Domain Boost for OpenStorage

a. Stop any NetBackup services. Follow the instructions given

Start the installation

5. Tune the Windows media server for performance. See Tuning

NetBackup UNIX Services

Stop UNIX services

Start or restart UNIX services

NetBackup Windows Services

Start, stop, or restart Windows services

2. In the Services window, services are listed in alphabetical order

Backup Exec Installation

• Backup Exec Services on page 25