emc data domain gda administration guide · pdf file• dd os 5.2 administration guide...

Data Domain Global Deduplication Array Administration Guide

DD OS 5.2

Backup Recovery Systems DivisionData Domain LLC2421 Mission College Boulevard, Santa Clara, CA 95054866-WE-DDUPE; 408-980-4800

759-0032-0001 Revision ADecember 2011

2

Copyright © 2009-2011 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, Data Domain, Global Compression™, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

Contents

About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . 7

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

Required Additional Data Domain Documents . . . . . . . . . . . 7

Related Data Domain Documents . . . . . . . . . . . . . . . . . . . 8

Access to Documents at Data Domain . . . . . . . . . . . . . . 8

Access Data Domain Documents . . . . . . . . . . . . . . . 9

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Data Domain Support . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . .11

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Data Domain-Provided Hardware . . . . . . . . . . . . . . . . . . 12

Customer-Provided Infrastructure. . . . . . . . . . . . . . . . . . 14

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Network Connectivity . . . . . . . . . . . . . . . . . . . . . . . 14

Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Specifications and Site Requirements . . . . . . . . . . . . . 16

Rack Space and Interconnect Cabling . . . . . . . . . . . . . 16

Slot Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

System Port Naming. . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Global Deduplication Array Administration Guide 3

2 Network Overview . . . . . . . . . . . . . . . . . . . . . . 21

Physical Network Interfaces . . . . . . . . . . . . . . . . . . . . . .21

Logical Network Interfaces. . . . . . . . . . . . . . . . . . . . . . .21

Global Deduplication Array Networking Guidelines for DD Boost Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

About Subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

3 Installation and Configuration . . . . . . . . . . . . . . . 25

Installing and Configuring Each Controller. . . . . . . . . . . . .25

Configuring a Global Deduplication Array . . . . . . . . . . . . .27

Configuring a Two-Controller GDA using DD880 . . . . . . .28

Configuring a Two-Controller GDA using DD890 . . . . . . .30

Configuring a Single-Controller GDA using DD880 or DD890 31

Adding a Second Controller to a Single Controller Using DD880 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Adding a Second Controller to a Single Controller Using DD890 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Setting up DD Boost on the GDA . . . . . . . . . . . . . . . . .37

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Setting Up VTL on a GDA . . . . . . . . . . . . . . . . . . . . . .40

Guidelines and Recommendations for FC Zoning and Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Setting Up Collection Replication on a GDA. . . . . . . . . .44

4 Administration . . . . . . . . . . . . . . . . . . . . . . . . . 47

About the Enterprise Manager. . . . . . . . . . . . . . . . . . . . .47

Unsupported Features . . . . . . . . . . . . . . . . . . . . . . . . . .48

Using the CLI for Administrative Tasks . . . . . . . . . . . . . . .48

4 Contents

Using the Enterprise Manager for Administrative Tasks. . . . 49

Log In and Out of the Enterprise Manager . . . . . . . . 49

Adding or Removing an Array from the Network . . . . 50

Global Deduplication Array Status Page . . . . . . . . . . . 51

Managing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . 52

Master Versus Worker Controller Functionality . . . . . . . 52

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5 Global Versus Local Commands . . . . . . . . . . . . . . .57

CLI Variation in a GDA Environment . . . . . . . . . . . . . . . . 57

Disabled Global Commands . . . . . . . . . . . . . . . . . . . . . . 59

Local Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

A Upgrading a Data Domain System . . . . . . . . . . . . .61

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Upgrading Hardware to a GDA System. . . . . . . . . . . . . . . 62

Upgrading the DD OS . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Setting Up the Global Deduplication Array . . . . . . . . . . . . 63


6 Contents

About This Guide

This guide describes how to install, configure, and administer a Data Domain® Global Deduplication Array (GDA).

AudienceThis guide is for administrators and service providers who install, configure, and administer Data Domain Global Deduplication Arrays.

Required Additional Data Domain DocumentsThis guide is intended to be used in conjunction with the following documents:

• Data Domain Installation and Setup Guide that shipped with your Data Domain system.

• The Data Domain Global Deduplication Array supports the DD Boost protocol on the DD880 and DD890 GDA controllers. This guide provides basic setup information. For the complete installation and operation information, see the Data Domain Boost for OpenStorage Administration Guide.

• The Data Domain Global Deduplication Array supports the VTL feature on the DD890 GDA controller only. This guide provides basic setup information. For complete information, see the DD OS 5.2 Administration Guide.

• For more information about using the Enterprise Manager to administer a Global Deduplication Array, see the DD OS 5.2 Administration Guide.

• For information about cluster commands, see the DD OS 5.2 Command Reference Guide.


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

• Data Domain Operating System Release Notes, Version 5.2.x

• DD OS 5.2 Initial Configuration Guide

• DD OS 5.2 Administration Guide

• Data Domain Hardware Overview (for your system)

• Data Domain Expansion Shelf Hardware Guide

• Data Domain GDA Controller Upgrade Guide

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

• End-user documents, under Product Documentation.

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

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

• Data Domain hardware product numbers

• Data Domain operating system (DD OS) versions

• Backup applications and other application versions

• Application server and client operating system versions

• Hardware driver versions

8 About This Guide

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.


https://my.datadomain.com/documentation

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

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

Typeface or Symbol

Usage Examples

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

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

Monospace bold

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

Enter:# config setup

Monospace italic bold

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

# log view file_name

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

Pipe (|) and curly braces ({})

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

{arg1 | arg2}

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

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

[arg1, arg2, ...]

10 About This Guide

https://my.datadomain.com

1 Getting Started

This chapter covers the following topics:

• Introduction on page 11

• Licenses on page 12

• Data Domain-Provided Hardware on page 12

• Customer-Provided Infrastructure on page 14

• Slot Mapping on page 18

• System Port Naming on page 19

IntroductionAn EMC Data Domain Global Deduplication Array (GDA) presents a single deduplication storage pool to backup applications across two EMC Data Domain controllers. The first controller is known as the master controller, and the second as the worker controller. The two controllers are directly connected to each other with an optical interconnect cable.

A GDA configured with two DD890 controllers or two DD880 controllers supports the DD Boost protocol. Managed file replication is supported via the DD Boost plug-in, which is installed on media servers. Collection Replication is also supported with DD Boost for fast seeding between two GDAs. Each controller exports an external 10 GbE data interface to the outside world, and the DD Boost plug-in connects to both controllers through this interface.

Alternatively, a GDA configured with two DD890 controllers supports the Data Domain VTL feature. Backup servers can be connected over Fibre Channel (FC) directly or indirectly via an FC switch with up to eight 8 Gbps FC ports (four ports per controller).


Collection replication can be used to replicate data between two GDAs using VTL.

A GDA controller has two 1 GbE ports that can be used for management and replication.

Note: The Global Deduplication Array does not support shared storage or failover from one controller to the other. If any controller is not working, the data on the array is unavailable.

LicensesLicenses are required for the following features:

• Global Deduplication Array membership: one license key per controller in the Global Deduplication Array.

• Replicator: one license key per controller in the Global Deduplication Array.

• DD Boost: one license key for the master controller.

• VTL: one license key for the master controller.

Note: The licenses are not installed on a new Global Deduplication Array prior to shipping.

Data Domain-Provided HardwareA Data Domain Global Deduplication Array consists of two controllers. Both controllers must have the identical hardware configuration; that is, the same amount of memory, the same type of NIC for protocol connection, the same external storage shelf configuration, and so forth.

Note: It is possible to purchase a Global Deduplication Array that consists of one controller that is ready for upgrade to the standard two-controller array. For upgrade instructions, see Appendix A Upgrading a Data Domain System.

12 Getting Started

• One serial port

• One 15-meter optical interconnect cable

Table 1-1: Data Domain-Provided Hardware

DD880 DD890

2 NVRAM cards, 1 GB each 2 NVRAM cards, 1 GB each

64 GB RAM 96 GB RAM

One to twelve ES20 shelvesorOne to twelve ES30 shelves

One to twelve ES20 shelvesorOne to twelve ES30 shelves

Two 1 GbE ports on the motherboard (eth0a, eth0b)

Two 1 GbE ports on the motherboard (eth0a, eth0b)

One 2-port 10 GbE optical card for interconnect (eth5a, eth5b)

One 2-port 10 GbE optical card for interconnect (eth1a, eth1b)

One 2-port 10 GbE optical card for DDBoost (eth4a, eth4b)-or-One 2-port 10 GbE copper card for DDBoost (eth4a, eth4b)

One 2-port 10 GbE optical card for DDBoost (eth4a, eth4b) -or-One 2-port 10GbE copper card for DDBoost (eth4a, eth4b) -or-Two 2-port 8 Gbps FC cards for VTL (4a, 4b and 7a and 7b)


Customer-Provided InfrastructureCustomer are responsible for providing the following infrastructure.

Hardware• An administrative console. Options include a Cat 5e or Cat 6

Ethernet cable attached to an Ethernet port (DHCP required), or a monitor (VGA port) and USB keyboard, or KVM for each controller.

Network ConnectivityFor network connectivity, the following IP addresses are required:

• For DD Boost, one internal IP address per controller for the 10 GbE connection between controllers. The subnet for this IP address must not clash with any external networks.

• One external IP address per controller for data traffic between the media servers and the controller for the 10 GbE interface. All media servers must be able to reach this IP address. This IP address can also be used for system management and replication traffic.

• One or two IP addresses per controller for system management and replication traffic for the 1 GbE network ports if using the 1 GbE network ports for these logical interfaces (see Chapter 2 Network Overview on page 21).

Note: Ethernet failover requires a dual-port NIC.

14 Getting Started

Figure 1-1: GDA with DD Boost Access over 10 GbE

Figure 1-2: GDA with VTL Access


StorageCustomer data is stored in the Data Domain-provided storage attached to the Global Deduplication Array. Each controller must be configured with an equal amount of storage capacity.

Specifications and Site RequirementsSee the Data Domain Installation and Setup Guide for your Data Domain Storage System.

Rack Space and Interconnect CablingNote: See the Data Domain Installation and Setup Guide for your Data Domain Storage System. The section “Connecting Multiple Expansion Shelves” shows the preferred installation diagram for a controller with populated shelves.

Controller Placement

Controllers in an array must be placed close to each other in the data center so that the interconnect cable can easily be routed between the two controllers.

Rack Installation

In the following example (see Figure 1-3 on page 17), two Data Domain controllers are installed, each in separate racks. The two racks are populated with a 12-shelf array, following the preferred installation diagram. The racks are 42-to-44 U racks spaced on 24-inch centers. Each controller is installed in the lower third of its rack. The cabling between the two racks runs along the top portion of the racks.

Attach the interconnect cables to the connectors on the 10 Gb Ethernet card. See Table 1-2, Controller Slot Assignments, on page 19 for slot location.

For planning purposes, note the following:

• The length of the cable needed to route the 10 GbE port to the right-hand side of the rack and turn upwards, ready to begin the vertical run is 18-inches. Use this routing if there is at most

16 Getting Started

one rack (35-to-41 inches space) between the two controllers, as shown in Figure 1-3 on page 17.

• Alternatively, route the interconnect cables on the side of the rack closer to the other controller. This routing results in about 24 more inches of allowable spaces between the racks, an amount sufficient to place up to two racks (59-to-65 inches space) between the two systems.

Figure 1-3: Cabling Two Controllers in Separate Racks (with 12 Shelves)


Slot MappingA controller has multiple PCI slots, which are numbered as shown in the following figures (numbering right-to-left when facing the rear of the system).

Figure 1-4: PCI Slot Location: DD880

Figure 1-5: PCI Slot Location: DD890

Table 1-2 on page 19 shows the slot assignments per controller. The supported card combinations are:

• NIC

• VTL

• NIC and NIC

• VTL and VTL

18 Getting Started

1

HBA 1

E -

ect)

• VTL and NIC

NIC indicates a 10GbE Ethernet card, which can be a dual-port copper or optical card.

VTL indicates a dual-port 8GbE Fibre Channel HBA card.

The supported models are shown in Table 1-2.

Slot 5 (DD880) or Slot 1 (DD890) contains a dual-port Ethernet card. This card is required to establish a redundant connection (two cables) between the two controllers, but is not required for a single-controller configuration.

System Port NamingA controller has two 1 Gb copper Ethernet ports on the motherboard.

These ports are always mapped as eth0a and eth0b. The other ports are identified by a combination of their slot number and port letter. The first port in a slot is labeled a and a second port is b. For example, a dual-port copper Ethernet card in Slot 4 has the port names eth4a and eth4b

Table 1-2: Controller Slot Assignments

Model Slot7 Slot 6 Slot 5 Slot 4 Slot 3 Slot 2 Slot

DD880 NVRAM 1 NVRAM 2 10 GbE (inter-connect)

10 GbE (DDBoost)

SAS HBA 3 SAS HBA 2 SAS

DD890 10 GbE (DDBoost)-or

8 Gbps FC (VTL)

NVRAM 1 NVRAM 2 10 GbE (DDBoost)-or

8 Gbps FC (VTL)

SAS HBA 2 SAS HBA 1 10 Gb(interconn


.

Table 1-3: DD880 Ports: Slot 4 with Dual-Port 10 GbE Card

Motherboard Slot 5

(interconnect) (a)

Slot 4

Selected NIC card Two 1 GbE copper ports

Dual-port optical 10 GbE

Dual-port copper or optical10 GbE

Port Names eth0a, eth0b eth5a, eth5b eth4a, eth4ba. When configured as a single-controller Global Deduplication Array, slot 5 might

be empty.

Table 1-4: DD890 Ports: Slot 4 and Slot 7 with Dual-Port 8 Gbps FC HBA (VTL) Card

Motherboard Slot 4 and Slot 7 Slot 1

(interconnect) (a)

Selected card Two 1 GbE copper ports

Dual-port 8 Gbps FC


Port Names eth0a, eth0b eth4a, eth4b eth7a, eth7b

eth1a, eth1b

a. When configured as a single-controller Global Deduplication Array, slot 1 might be empty.

Table 1-5: DD890 Ports Configured for DD Boost

Motherboard Slot 4 and Slot 7 Slot 1

(interconnect) (a)

Selected card Two 1 GbE copper ports

Dual-port optical10 GbE


Port Names eth0a, eth0b eth4a, eth4beth7a, eth7b

eth1a, eth1b

a. When configured as a single-controller Global Deduplication Array, slot 1 might be empty.

20 Getting Started

2 Network Overview


• Physical Network Interfaces on page 21

• Logical Network Interfaces on page 21

• Global Deduplication Array Networking Guidelines for DD Boost Configuration on page 23

Physical Network InterfacesThe Global Deduplication Array’s physical network interfaces are the 1 Gb Ethernet ports on the motherboard, the controller’s 10 GbE interconnect card, and the Ethernet or VTL cards. See Table 1-5 on page 18.

Optionally, you can configure Ethernet failover. Ethernet failover provides improved network stability, and is implemented with the net failover command. The virtual interface represents a group of secondary physical interfaces, one of which can be specified as the primary (the first interface to take over in a failover). See Configuring a Global Deduplication Array on page 27.

Logical Network InterfacesAs part of configuring a Global Deduplication Array, you will use the net config command to define the IP addresses for three logical network interfaces:

• Interconnect interface (also referred to as cluster interface), which identifies the Global Deduplication Array interconnect IP address on each controller.

• Management interface, which identifies the IP address for managing the controller (SSH or the Data Domain Enterprise


Manager, which is a graphical-user interface (GUI) application).

Note: To use the Enterprise Manager, a physical network interface on the master controller needs to be connected to an IP network with an IP address a Web browser can locate.

• Replication interface, which identifies the IP address for replication traffic.

Note: Each logical interface type can be associated to only one physical or virtual interface.

Table 2-1 shows the possible combinations of logical and physical interfaces.

Table 2-1: Logical and Physical Interface Combinations

LogicalInterfaces

Physical Interfaces

eth0a, eth0b eth5a, eth5b (DD880) oreth1a, eth1b (DD890)

eth4a, eth4b (Ethernet) or 4a, 4b (VTL)

Interconnect - Yes -

Management Yes - -

Replication Yes - Yes (DD880)

22 Network Overview

G
lobal Deduplication Array Administration Guide 23
Global Deduplication Array Networking Guidelines for DD Boost Configuration

Refer to Table 2-1, Logical and Physical Interface Combinations, on page 22.

• If the data traffic needs to flow through a private 10 GbE network, then the 1 GbE ports (eth0a and eth0b) can be configured for management and replication.

• If the 1 GbE interface on the Global Deduplication Array is configured for replication/management use, to avoid routing issues, place them on a different network from the 10 GbE interface, which is mostly used for data. If your environment does not allow for different networks, then add a host route to each Global Deduplication Array controller for each media server that needs to communicate with it.

• Use the two interconnect cables for link failover support.

About SubnetsEach Global Deduplication Array’s logical interface should be configured on a separate network; for example:

Note: Each interconnect interface must be on a private network because it is used for internal communication.

Node Name Serial Node Role Management Replication Cluster Node Num Number Interface Interface Interface-------------- ---------- --------- ----------- ------------ --------- --------master.abc.com 8DD8W43019 Master 192.168.2.1 10.1.1.1 8.8.8.44 1worker.abc.com 8DD8W43022 Worker 192.168.2.2 10.1.1.2 8.8.8.33 2-------------- ---------- --------- ----------- ------------ --------- --------

If the data, management, and replication interfaces need to be on the same network, for better performance, create explicit route entries to ensure that the data traffic flows through the 10 GbE interface. For example:

sysadmin@master(Master:1)# route show table

Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface

8.8.8.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5a

4.4.4.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4a

192.168.8.0 0.0.0.0 255.255.252.0 U 0 0 0 eth0a

127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo

0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 eth0a

Some interfaces can be configured on the same network; for example:

Management interface: 192.168.2.1 (network mask 255.255.255.0)

Data interface: 192.168.2.2 (network mask 255.255.255.0)

To ensure that traffic from these management and data interfaces uses the right interface, add the following routing entry:

# route add -host 192.168.2.100 dev eth0a

# route add -host 192.168.2.200 dev eth5a

Note: In the above configuration, 192.168.2.100 is the management client, and eth0a is the management interface. 192.168.2.200 is the data client, and eth5a is the data interface.

24 Network Overview

3 Installation and Configuration

The installation and initial configuration of a controller in a Global Deduplication Array is similar to that for a stand-alone Data Domain system.

Notes:

• Prepare to use the Installation and Setup Guide for your Data Domain Storage System, which is shipped with the controller, in conjunction with the instructions provided in this chapter.

• For installation of the ES20 or ES30 shelves, see the above guide and the chapter for cabling your Data Domain series system in the Data Domain Expansion Shelf Hardware Guide.

This chapter covers the following major topics:

• Installing and Configuring Each Controller on page 25

• Configuring a Global Deduplication Array on page 27

Installing and Configuring Each Controller1. Using the Installation and Setup Guide, follow the steps in

Section 1, Install Hardware to set up one or two GDA-ready Data Domain systems.

2. If working with two controllers:

a. For two controllers, cross connect the two interconnect cables to the two 10 GbE ports.

- For DD880, eth5a to eth5a and eth5b to eth5b on each controller.

- For DD890, eth1a to eth1a and eth1b to eth1b on each controller.


Note: See Rack Space and Interconnect Cabling on page 16 for more information.

3. Verify that you have done the following for each controller in the Global Deduplication Array as directed in Section 1, Install Hardware:

• For DD Boost, connected the external 10 GbE port or ports to your network.

• Connected the motherboard 1 GbE ports (eth0a and eth0b) to your network.

• Attached the disk shelves to the appropriate controllers via SAS cables to the SAS ports.

• Connected all power cables.

4. Turn the controllers on (ES20 or ES30 power and each controller) as directed.

5. Complete Section 2, Define the Data Domain System Information for Your Site in the Installation and Setup Guide included with your Global Deduplication Array.

6. Following the instructions given in Section 3, Perform Initial System Configuration of the Installation and Setup Guide, configure each controller separately.

Notes:

• Use the NFS configuration section to configure the admin host and the CIFS configuration section to add a share for /ddvar, which is used to retrieve logs from each controller. Any configuration done for /backup is removed when the controllers are made part of a Global Deduplication Array. If this section is skipped, to access /ddvar, you need to add an NFS export, or an NFS export and CIFS share for /ddvar.

• Group memberships for system administrative access via SSH, Telnet, and FTP for groups that exist on a Windows domain controller if CIFS administrative access is enabled on the Data Domain system with the adminaccess command must be set on each controller using the option set “dd admin groupn” command. See the command description in the DD OS Command Reference Guide for more information.


7. Add the attached disk shelf or shelves by entering:

# storage add enclosure enclosure-id

8. Skip Section 4, Configure the System for Data Access. The data access protocols supported by the Global Deduplication Array are DD Boost and VTL. Both of these are configured later.

9. Go to Section 6, Perform Optional Additional System Configuration, in the Installation and Setup Guide.

a. Because a user must already exist on the Data Domain system in order to be added as an DD Boost user, add a user.

b. The other configuration steps are optional, except for NFS configuration, which does not apply to a Global Deduplication Array.

10. Verify that the file system is operational by entering:

# filesys status

11. Initialize a new file system on both systems by entering:

# filesys destroy

# filesys create

This command deletes all data in the file system and creates a new one.

Configuring a Global Deduplication ArrayAfter the controllers have been installed and configured as described in Installing and Configuring Each Controller on page 25, configure the Data Deduplication Array (GDA) as described in this section.

For a list of Data Domain provided hardware, see Table 1-1 on page 13.

For information about controller slot assignments, see System Port Naming on page 19.


After the controllers have been installed and setup as described in Installing and Configuring Each Controller on page 25, configure the Data Deduplication Array (GDA) as described in this section.

The following instructions describe how to set up a two-controller or single-controller GDA, and how to expand a single-controller to a two-controller GDA.

Configuring a Two-Controller GDA using DD880This procedure sets up the worker controller and then the master controller. The Global Deduplication Array is created on the master controller after both controllers have been setup.

Perquisites:

• Two Global Deduplication-ready DD880 systems to serve as the two controllers. See Installing and Configuring Each Controller on page 25 for instructions on preparing the controllers.

• Master controller's interconnect IP and netmask.

• Master controller's Global Deduplication license.

• Worker controller's interconnect IP and netmask.

• Worker controller's Global Deduplication license.

Configuring a Two-Controller GDA using DD880

Configuring a Two-Controller GDA using DD890 Page 30

Configuring a Single-Controller GDA using DD880 or DD890

Page 31

Adding a Second Controller to a Single Controller Using DD880

Page 32


Page 35

Setting up DD Boost on the GDA Page 37

Setting Up VTL on a GDA Page 40

Setting Up Collection Replication on a GDA Page 44


Configure the worker controller

1. Install the GDA license on the worker controller.

# license add Global-Deduplication-license-key

2. Configure the interconnect interface by entering:

# net disable eth5a

# net disable eth5b

# net create virtual veth1

# net failover add veth1 interfaces eth5a, eth5b primary eth5a

# net config veth1 worker-controller-interconnect-ip netmask netmask

# net config veth1 type cluster

Configure the master controller

1. Install the Global-Deduplication Array license:



# net disable eth5a

# net disable eth5b





3. Create a Global Deduplication Array by entering:

# cluster create cluster-name

4. Add the worker to the array by entering:

# cluster add worker-name


5. From the master controller, enter:

# cluster show config

Check that the correct membership information for both controllers is displayed using the show config command.

Configuring a Two-Controller GDA using DD890This procedure sets up the worker controller and then the master controller. The Global Deduplication Array is created on the master controller after both controllers have been setup.

Perquisites:

• Two Global Deduplication-ready DD890 systems to serve as the two controllers. See Installing and Configuring Each Controller on page 25 for instructions on preparing the controllers.

• Master controller's interconnect IP and netmask.

• Master controller's Global Deduplication license.

• Worker controller's interconnect IP and netmask.

• Worker controller's Global Deduplication license.

Configure the worker controller

1. Install the Global-Deduplication Array license on the worker controller.



# net disable eth1a

# net disable eth1b






Configure the master controller




# net disable eth1a

# net disable eth1b







4. Add the worker to the array by entering:




6. Check that the correct membership information for both controllers is displayed. See show config on page 60.

Configuring a Single-Controller GDA using DD880 or DD890

This procedure sets up the master controller. The Global Deduplication Array is created on the master controller. A single controller GDA can later be expanded to two controllers.

Prerequisites:

• A Data Domain controller configured for a Global Deduplication Array to serve as the master controller. See Installing and Configuring Each Controller on page 25 for instructions on preparing the controllers.


• Master controller's Global Deduplication license

Configure the single controller (master)







4. Check that the correct membership information is displayed using the show config command.


This procedure adds a second controller (worker) to an existing single controller GDA. After this process, some data from the master controller may be migrated to the worker to rebalance the capacity. This data movement occurs automatically after the next cleaning phase.

Prerequisites:

• A single-controller Global Deduplication Array (master controller).

• A controller ready for use as a Global Deduplication Array to serve as the worker controller. See Installing and Configuring Each Controller on page 25 for instructions on preparing the controllers.

• Master controller's interconnect IP and netmask

• Worker controller's interconnect IP and netmask

• Worker controller's Global Deduplication license

Configure the worker and master controllers as directed below.


Run these steps on the worker controller

Note: This is the controller that serves as the worker controller in the Global Deduplication Array.


Note: The worker and master controllers have different licenses.


2. Configure the worker interconnect interface by entering:

# net disable eth5a

# net disable eth5b


# net failover add veth1 interfaces eth5a,eth5b primary eth5a



3. Set up the data interface.

# ddboost ifgroup add interface ip_of_eth4a


# ddboost ifgroup enable

This will allow for load balancing of backup and restore jobs against both interfaces. If one interface fails, jobs will fail over to the working interface.

Note: For customers using a 1 GbE network, a 4-port 1 GbE NIC can be used in place of a dual-port 10 GbE. In this case, all four 1 GbE interfaces can be added to the ifgroup.

4. If using collection replication:

# net config veth2 type “replication”


Notes:

• If you are using DD Boost managed file replication, you do not have to set up replication on the worker controller.

• Because we configured load balancing on the data interfaces, we highly recommend that the replication interface not be configured as an ifgroup member.

Run these steps on the master controller

Note: The master controller is the existing single-controller Global Deduplication Array.

1. Configure the master controller's interconnect interface by entering:

# net disable eth5a

# net disable eth5b



# net config veth1 master-controller-interconnect-ip netmask netmask


2. From the master controller, add the worker to the array.

# filesys disable


# filesys enable






This procedure adds a second controller (worker) to an existing single controller GDA. After this process, some data from the master controller may be migrated to the worker to rebalance the capacity. This will be done automatically after the next cleaning phase.

Prerequisites:

• A single-controller Global Deduplication Array (master controller).

• A controller ready for use as a Global Deduplication Array to serve as the worker controller. See Installing and Configuring Each Controller on page 25 for instructions on preparing the controllers.

• Master controller's interconnect IP and netmask

• Worker controller's interconnect IP and netmask

• Worker controller's Global Deduplication license

Configure the worker and master controllers as directed below.

Run these steps on the worker controller

Note: This is the controller that serves as the worker controller in the Global Deduplication Array.


Note: The worker and master controllers have different licenses.


2. Configure the worker interconnect interface by entering:

# net disable eth1a

# net disable eth1b






3. If using DD Boost, set up the replication interface. Skip this step if VTL is being used.




This will allow for load balancing of backup and restore jobs against both interfaces. If one interface fails, jobs will fail over to the working interface.

Note: For customers using a 1 GbE network, a 4-port 1 GbE NIC can be used in place of a dual-port 10 GbE. In this case, all four 1 GbE interfaces can be added to the ifgroup.

4. If using collection replication:


Notes:

• If you are using DD Boost managed file replication, you do not have to set up replication on the worker controller.

• Because we configured load balancing on the data interfaces, we highly recommend that the replication interface not be configured as an ifgroup member.

5. If using VTL, go to Setting Up VTL on a GDA on page 40.

6. If using collection replication, go to Setting Up Collection Replication on a GDA on page 44.


Run these steps on the master controller

Note: The master controller is the existing single-controller Global Deduplication Array.

1. Configure the master controller's interconnect interface by entering:

# net disable eth1a

# net disable eth1b



# net config veth1 master-controller-interconnect-ip netmask netmask


2. From the master controller, add the worker to the array.

# filesys disable


# filesys enable




Note: If VTL is enabled on the GDA, follow the Guidelines and Recommendations for FC Zoning and Load Balancing on page 41 to achieve better performance with a two-controller GDA.

Setting up DD Boost on the GDADD Boost can be enabled on any GDA. DD Boost requires a data interface to be defined on each controller. For the data interface, you have the option of setting up Ethernet failover using the net create virtual and net failover commands. See Global Deduplication Array Networking Guidelines for DD Boost Configuration on page 23 for more information.


DD Boost managed file replication can optionally be set up on the GDA. It supports:

• 1-to-1

• Many-to-1

• 1-to-many

• Cascaded replication (using NetBackup 6.5.4 and later)

Note: Managed file replication is set up only on the master controller.

Prerequisites

• DD Boost license

• Replication license (optional)

• Master controller’s data IP and subnet

• Worker controller's data IP and subnet.

Enable DD Boost

1. Add the DD Boost license and, if applicable, the Replication license using the license keys that Data Domain provided:

# license add license_key

2. A user must already exist on the GDA in order to be added as an DD Boost user.

Note: NIS is recommended if you want to have common users on controllers in the Global Deduplication Array. The user add command is local to a controller, and does not add the user to another controller.

3. Add a DD Boost user by entering:

# ddboost set user-name user-name

4. Enable DD Boost by entering:

# dboost enable


5. Create a storage unit by entering:

# ddboost storage-unit create storage-unit-name

6. To enable managed file replication, install the supplied replication license on the master controller.

# license add license_key

7. Configure the data transfer interfaces (10 GbE and/or 1 GbE interfaces) and ensure are reachable by all media hosts that need backup or restore access.

# ddboost ifgroup add interface ipaddr


The ifgroup setup must be done on each node, Master and Worker node.

Notes:

• If an ifgroup is disabled on the master, the management IP will be used for both master and worker data transfer.

• If an ifgroup is disabled on the worker, the management IP will be used for the worker, while the master node will perform Advanced Load Balancing.

• If an ifgroup is enabled on both interfaces, then Advanced Load Balancing will be performed independently on both nodes.

• The number of interfaces included in the ifgroup is totally independent for each node.

• If an ifgroup is enabled on the master, but the media host can not reach the ifgroup IP, the default management IP will be used instead for data transfer.

• If an ifgroup is enabled on both the master and worker, but the IP on worker is not reachable, DD Boost will attempt to retry on that IP and the job will fail. Therefore, it is expected that the host will be able to reach all IPs in the ifgroup on the worker node if it is able to reach the IPs on the master node.

• The GDA cluster IP may not be used in the ifgroup.


8. Configure the replication interface. The replication traffic can go over any Ethernet interface in the system:


9. If the replication traffic needs to be routed over the 1 GbE interface, enter:

# net config eth0-or-eth1 type replication

See the DD Boost Administration Guide for complete information about installing and configuring DD Boost. For instructions on how to configure managed file replication, which is the preferred replication method, see the Configuration chapter.

Setting Up VTL on a GDAThese instructions assume that the GDA is operational.

Set up VTL

1. Add the VTL license on the master controller:

# license add VTL license-code

2. Enable VTL in GDA configuration:

# vtl enable

3. Verify VTL status for the GDA:

# vtl status

4. Obtain the VTL port’s WWPN:

# vtl port show hardware

Port Model Firmware WWNN WWPN

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

1-5a QLE2562 5.02.00 20:00:00:24:ff:20:60:94 21:00:00:24:ff:20:60:94

1-5b QLE2562 5.02.00 20:00:00:24:ff:20:60:95 21:00:00:24:ff:20:60:95

2-5a QLE2562 5.02.00 20:00:00:1b:32:9a:e5:5e 21:00:00:1b:32:9a:e5:5e

2-5b QLE2562 5.02.00 20:01:00:1b:32:ba:e5:5e 21:01:00:1b:32:ba:e5:5e

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

5. Set up FC zoning between the VTL target mode HBA and initiators (backup servers).


Guidelines and Recommendations for FC Zoning and Load Balancing

• Create a single FC zone for all initiator ports available to communicate with VTL target FC ports. Use the vtl group command to control access of tape devices with initiators.

• If you create separate FC zones, access to the media changer is available only from the master controller. This requires access to the master controller’s VTL FC target port by a media server. Include the master controller‘s VTL port in a FC zone configured to communicate with a worker controller in a GDA.

• Division of I/O streams (number of tape devices) is recommended across all four FC ports available on the controller. A maximum of 512 tape devices are supported in a two-controller cluster GDA, which allows a maximum of 256 tape devices per controller in a GDA.

• A GDA consisting of a maximum of 128 tape devices per controller is recommended to achieve manual failover (re-direct of I/O from one controller to another controller) in the event of a failure of the VTL port or data path directed to VTL. Manual failover requires modification of the VTL port configuration using the vtl group modify command. Media changer is available on the master controller and cannot be moved from the master controller to the worker controller in event of a VTL port failure on the master controller.

Configure VTL

1. Ensure FC zoning has been implemented as described in Guidelines and Recommendations for FC Zoning and Load Balancing on page 41.

2. Run the vtl initiator show command to verify FC connectivity between VTL ports and initiator ports:

# vtl initiator show port 1-all


Create a VTL

1. Add vtl:

# vtl add lib1 slots 1000 caps 16

Issuing this command creates a VTL with 1000 slots and 10 cartridge access port. Modify these value as appropriate.

2. Add drives:

# vtl drive add lib1 count 128

This command adds 128 drives type LTO3 in a VTL lib1

3. Create tapes:

# vtl tape add A00000L3 count 1000 capacity 800

Issuing this command adds 1000 tapes (starting with barcode A00000L3) and a tape capacity of 800 GB.

4. Import tapes into library:

# vtl import lib1 barcode A00000L3 count 1000 element slot

5. Create an alias for the initiator attached to master controller:

# vtl initiator set alias media01 wwpn 21:00:00:1b:32:8e:88:d6

6. Create a VTL group:

# vtl group create media01”

7. Populate VTL group:

8. Add initiator to the VTL group:

# vtl group add media01 initiator media01

Examples

• Example of adding all tape drives and media changer to the master controller:

# vtl group add media01 vtl lib1 all primary-port 1-all


• Example of adding all tape drives to the master controller and media changer to the worker controller:

# vtl group add media01 vtl lib1 changer primary-port 1-all

# vtl group add media01 vtl lib1 drive 1-128 primary-port 2-all

• Example of adding 32 tape devices on each port and media changer to master controller:

# vtl group add media01 vtl lib1 changer primary-port 1-all

# vtl group add media01 vtl lib1 drive 1-32 primary-port 1-5a secondary -port 2-5a

# vtl group add media01 vtl lib1 drive 33-64 primary-port 1-5b secondary-port 2-5b

# vtl group add media01 vtl lib1 drive 65-96 primary-port 2-5a secondary-port 1-5a

# vtl group add media01 vtl lib1 drive 97-128 primary-port 2-5b secondary-port 1-5b

• Example of moving VTL tape drives (33-64) from the master controller (1-5b) to the worker controller (2-5b):

# vtl group modify media01 vtl lib1 drive 33-64 primary-port 2-5b secondary-port 1-5b

Note: Online help shows all of the vtl command options.


Setting Up Collection Replication on a GDACollection replication supports system mirroring.

The section describes how to configure and enable collection replication between two dual-controller Global Duplication Arrays.

Note: Ethernet failover requires a dual-port NIC.

Figure 3-1: Collection Replication between Two Global Deduplication Arrays

The following instructions assume that you have two properly configured Global Deduplication Arrays, each consisting of two controllers.

• One network interface (or corresponding virtual interface) must be configured for replication on each controller

• All controllers in the replication interfaces must be able to ping each other. The master controller replicates to the remote master controller, and the worker controller replicates to the remote worker controller in parallel.

• Sample static addresses are assigned to each controller’s replication interface. You can assign a different static IP address for direct links between the controllers and set up the corresponding route entries. See Table 2-1 on page 22 to identify which physical interfaces can be used for replication.


Configure the Source Controllers

Note: The subnet used below is for example purposes only. The network interface selected for collection replication is eth1a in this example. Any of the physical interfaces (or corresponding virtual interfaces) can be used for replication. All four controllers must have the same subnet, that is, they must all be interconnected on a network.

1. Assign a static IP address to each of the controller’s interfaces intended for replication by entering:

# net config eth1a 8.8.8.x.

Source_Master(Master:1) eth1a: 8.8.8.1

Source_Worker(Worker:2) eth1a: 8.8.8.2

2. Set the network interface for replication use at both controllers in the array by entering:

# net config eth1a type "replication"

Note: Although the example uses eth1a, the port can be any one of the controller’s available Ethernet interfaces.

3. Disable the file system on the master controller by issuing the filesys disable command.

4. On the source master controller, enter:

# replication add source col://Source_Master.datadomain.com destination col://Dest_Master.datadomain.com

5. On the source master controller, specify the connection host:

# replication modify col://Dest_Master.datadomain.com connection-host 8.8.8.3

6. Enable the file system using the filesys enable command. Enter the command from each controller.

7. Configure the destination controllers as described below.


Configure the Destination Controllers

1. Assign a static IP address to each of the controller’s interfaces intended for replication by entering:

# net config eth1a 8.8.8.x.

Dest_Master(Master:1) eth1a: 8.8.8.3

Dest_Worker (Worker:2) eth1a: 8.8.8.4

2. Set the network interface for replication use at both controllers in the array by entering:

# net config eth1a type "replication"

Note: Although the example uses eth1a, the port can be any one of the controller’s available Ethernet interfaces.

3. Disable the file system on the master controller by issuing the filesys disable command.

4. On the destination master controller, enter:

# replication add source col://Source_Master.datadomain.com destination col://Dest_Master.datadomain.com

5. On the destination master controller, specify the connection host:

# replication modify col://Dest_Master.datadomain.com connection-host 8.8.8.1

6. Enable the file system using the filesys enable command. Enter the command from each controller.

Start replication

To start the replication from the source Global Deduplication Array to the destination Global Deduplication Array, from the source master controller, enter:

# replication initialize col://Dest_Master.datadomain.com


4 Administration


• About the Enterprise Manager on page 47

• Unsupported Features on page 48

• Using the CLI for Administrative Tasks on page 48

• Using the Enterprise Manager for Administrative Tasks on page 49

• Troubleshooting on page 54

About the Enterprise ManagerYou can administer a Global Deduplication Array using the Data Domain Enterprise Manager, which provides a graphical user interface (GUI). There are some functions, however, such as creating a Global Deduplication Array, that require use of the command-line interface (CLI) cluster command.

Notes:

• If an administrative tasks can be performed using both the Enterprise Manager and the CLI, the Enterprise Manager method is described in this chapter. The Getting Started chapter in the DD OS Administration Guide describes how to access and use the Enterprise Manager to administer and monitor Data Domain systems.

• For more information about the cluster command and its options, see the cluster command chapter of the DD OS 5.2 Command Reference Guide.

Within the Enterprise Manager, the controllers within a Global Deduplication Array are treated as a unit. The way that you administer a single Data Domain controller or a Global Deduplication Array is basically the same. The master controller,


which behaves in the same way as a Data Domain system, manages its worker controllers in the array.

Note: Using the DD OS 5.2 version of the Enterprise Manager, you can manage a total of twenty Data Domain systems. For example, your view might contain twenty single controllers, or ten Global Deduplication Arrays, or four two-controller Global Deduplication Arrays and twelve single controllers.

Unsupported FeaturesA Global Deduplication Array does not support:

• Directory replication

• Cascaded replication

• Retention Lock

• NDMP commands

• System sanitization

• In-line encryption of data-at-rest

IMPORTANT: Because encryption is not supported, GDA replication and optimized duplication will not work if the source or destination GDA is encryption enabled.

• DD Boost and VTL protocols

Therefore, these features are not functional in the Enterprise Manager when you are viewing an array.

Note: VTL is supported on the DD890 controller only.

Using the CLI for Administrative TasksFor instructions on how to create a Global Deduplication Array, which is done using CLI commands, see Configuring a Global Deduplication Array on page 27.

The only way to completely delete a Global Deduplication Array is to use the cluster destroy command. For more information about the cluster command, see the DD OS 5.2 Command Reference Guide.

48 Administration

Some DD OS CLI commands apply only to a single-controller (master or worker) versus the Global Deduplication Array. To issue these commands, you need to use the cluster run command:

cluster run [host [host-list | all | worker ] cmd command

Using the Enterprise Manager for Administrative Tasks

The Enterprise Manager provides a management view of an already created Global Deduplication Array. The master controller represents the array, and you use it to access its functions.

To manage an array, you need to log into the master controller. If you log into a worker controller, Enterprise Management capability is limited to that single controller.

Log In and Out of the Enterprise Manager

1. Open a Web browser and enter the IP address or hostname of a master controller to connect to the system. It must be one of the following:

• A fully qualified domain name (for example, http://rstr01.datadomain.com)

• A hostname (http://rstr01)

• An IP address (http://10.5.50.5)

Note: For secure login, use https with an authorized certificate instead of http. When https is used, the browser warns if the certificate is not authorized.

2. At the login dialog box, enter the login name and password for a sysadmin or user (assigned during the initial configuration). See the DD OS 5.1 Initial Configuration Guide for details.

3. Click Login.

4. To log out, click the Log Out link in the top pane.


Adding or Removing an Array from the Network

Adding or removing a Global Deduplication Array within the Enterprise Manager updates the device tree to reflect the new configuration. The array itself is neither created nor deleted.

The Enterprise Manager recognizes all of the controllers added to a defined Global Deduplication Array. The Global Deduplication Array is displayed as a folder on the device tree that consists of one or two controllers.

When you remove a Global Deduplication Array, it can no longer be used to manage an array, and the view of the systems in the Enterprise Manager is re-organized to reflect the Global Deduplication Array’s removal.

Add a Controller to a Global Deduplication Array

1. Click the + Add icon on the Navigational pane.

The Add System(s) dialog box is displayed.

2. In the System Name text box, enter a hostname or IP address of any controller in the Global Deduplication Array to be added.

Note: The Enterprise Manager uses a proxy and port to communicate with all controllers in the Global Deduplication Array. If any controller is not reachable, you are prompted to enter a proxy and port for that controller. Unless you specify a proxy, by default it is set to the system name, and the port is set to 3009. 3.

3. (Optional) To specify a proxy and port to connect to the host:

a. Select the Advanced option. In the Connection Details pane, select Use Proxy and Use Custom Port.

b. Enter the proxy server hostname and the port.

4. For the Administration Credentials, enter the sysadmin user name in the User Name text box, followed by the password.

If the password is incorrect, you are prompted to re-enter a password.

5. Click OK.

50 Administration

After you have added a Global Deduplication Array, it is displayed in the device tree. Expand its folder to view its contents.

Changing Network Settings

After adding a controller to the Enterprise Manager, if you change its network settings so that the Enterprise Manager cannot communicate with its hostname, change its proxy and port, or place it behind a firewall, the Enterprise Manager reports a communication error for the controller.

To correct this problem, remove the controller from the Enterprise Manager and add it again using the correct proxy and port information.

Master and Worker Controllers

The Global Deduplication Array icon in the device tree indicates multiple systems. The master controller is distinguished from worker controllers by the letter M above the controller icon.

When you select a Global Deduplication Array controller in the device tree, the Global Deduplication Array’s name is displayed on the system panel.

Remove a Global Deduplication Array

1. Click the X Remove icon on the Navigational pane.

The Remove System(s) dialog box is displayed.

2. Click the check box of the Global Deduplication Array or Global Deduplication Arrays to be removed.

All controllers in the Global Deduplication Array will be removed from view within the Enterprise Manager.

3. Click OK.

Global Deduplication Array Status PageThe Status page differs depending on the controller’s role. For example, the Status > Summary page for a master controller is the same as for any Data Domain system.


The Summary page for a worker controller shows if the file system is running, but does not provide file system data.

For more information, see Master Versus Worker Controller Functionality on page 52.

Managing Licenses Use the master controller to manage licenses for the Global Deduplication Array. You can use the Enterprise Manager to manage licensing for all licenses except the Global Deduplication Array license itself, which must be added via the CLI.

Display Licenses

1. In the Navigational pane, expand the Global Deduplication Array and select a master controller.

2. Click the System Settings > Licenses tabs.

The Licensed Features pane is displayed. It shows the License Key for each feature.

Master Versus Worker Controller FunctionalityBy managing the master controller, you have access to all of the Global Deduplication Array functions. A small set of functionality is not supported for a worker controller (see Table 4-1 on page 52). If you select a non-supported function from the worker controller, a message indicates that this function is not available on the worker controller. Some of the functions on a worker controller are for monitoring only.

Table 4-1: Enterprise Manager Functionality

Function Master Controller Worker Controller Global Deduplication Array Summary

Alert Same as single controller

Same as single controller

Shows global results

File System Shows global results Same as single controller (Monitoring only)

Shows global results

52 Administration

NFS Same as single controller (/ddvar only)

Not Supported

CIFS Same as single controller (/ddvar only)

Not Supported

DD Boost Shows global results Not Supported

VTL Shows global results (DD890 only)

Not Supported

Disk Supported Supported

Network Same as single controller


Enclosure Same as single controller


Sysstat Same as single controller


Config Same as single controller


Admin access Same as single controller


License Shows global results Same as single controller (Monitoring only)

System Same as single controller


Auto-Support Same as single controller


Support Same as single controller


Log Same as single controller




TroubleshootingTable 4-2 provides basic troubleshooting tips.

Replication (collection only)Note: DD Boost optimized duplication is preferred for replication.

Shows global results Same as single controller (Monitoring only)

Snapshot Shows global results Not Supported

User Same as single controller



Table 4-2: Basic Troubleshooting

Symptom Possible cause Diagnose Solution

Slow backups Check to see if the media server CPU is busy.

Use iperf to test network speed from the media server to the Global Deduplication Array.

Remove any processes from the media server that could be taking up CPU resources. Add more media servers if necessary.

54 Administration

Check to see if the data traffic is going over the 10 GB network from the media server. The traffic can through the 1 GB interface if it is on the same network as the 10 GB interface.


If the 10 GB interface (Global Deduplication Array) is on the same network as the 1 GB interface, add a host route on the media server for the Global Deduplication Array going through the 10 GB interface.

Check to see if there are any 1 GB networks between the media server and the Global Deduplication Array.


Remove any routing through 1 GB networks.

No backups Check connectivity from media server to Global Deduplication Array.

Use ping or iperf to check if the Global Deduplication Array is reachable from the media server.

Check network cables connecting the media server and the switches. Check for failed ports or network interfaces.

Check connectivity between Global Deduplication Array controllers.

Use ping or iperf on each controller to make sure that the other's cluster interconnect IP is reachable.

Check network cables connecting the two controllers. Check for failed ports.

Table 4-2: Basic Troubleshooting (Continued)

Symptom Possible cause Diagnose Solution


56 Administration

5 Global Versus Local Commands


• CLI Variation in a GDA Environment on page 57

• Disabled Global Commands on page 59

• Local Commands on page 59

CLI Variation in a GDA EnvironmentThe following CLI commands differ when used within a Global Deduplication Array.

Table 5-1: CLI Commands Changes for Global Deduplication Array Environment

CLI Commands Within a Global Deduplication Array

cifs option

cifs share create,cifs share modify,

GDA supports limited CIFS options.

The /backup subdirectory is not supported in a Global Deduplication Array.

ddboost option In a GDA, ddboost option must be enabled.

filesys option reset,

replication add source

The low-bw-optim argument is not supported because low-bandwidth optimization is not supported for a Global Deduplication Array.


filesys destroy, filesys disable, filesys enable, filesys status

Because the file system in a Global Deduplication Array is treated as a single file system, the output differs.

license There are minor changes to the license command to reflect more than one controller.

license add You can use this command to add more than one license code.

license del You can delete a license feature and a license code.

license reset,license show

You can specify a system.

net conf ifname type GDA output differs from single node.

nfs add,nfs del

The /backup subdirectory is not supported in a Global Deduplication Array.

ntp status The ntp status (local NTP service status, time, and synchronization information) is shown for both master and worker Data Domain systems.

support upload bundle When executed on a master controller, uploads bundles from master and worker controllers. When used with the option local on master (support upload bundle local), uploads only from master. The behavior on a worker is same as on a single controller.




Disabled Global Commands Some Global commands are disabled on the master controller because the command is not supported. More frequently, commands are disabled on worker controllers since management is performed from the master controller.

Local CommandsWhen issuing commands that have not been modified for use in a Global Deduplication Array, use the cluster run command.

cluster run [host(host-list | all | worker}] cmd command

system show stats, system show detailed-stats

The output differs for a Global Deduplication Array if there is more than one controller.

system upgrade You install the system upgrade software on the master controller. All controllers are upgraded and rebooted. The output differs from that of a single controller.

vtl enable,vtl group add,vtl group modify,vtl group show,vtl initiator show,vtl port enable, vtl port disable, vtl port option,vtl port show

GDA output differs from single node.




A Upgrading a Data Domain System


• Before You Begin on page 61

• Upgrading Hardware to a GDA System on page 62

• Upgrading the DD OS on page 62

• Setting Up the Global Deduplication Array on page 63

Before You Begin1. If you are converting or adding an existing Data Domain

system with data into a Global Deduplication Array, all data will be lost on the Data Domain system being converted. You need to issue the filesys destroy command in order to convert or add an existing file system.

2. A Global Deduplication Array requires DD OS 5.0 or higher. If your Data Domain system is not running DD OS 5.0 or higher, order an upgrade package. Instructions for upgrading the DD OS are given in the Release Notes that accompany the package.

3. Obtain the following licenses, as appropriate:

• Global Deduplication Array membership: one license key per controller in the Global Deduplication Array.

• Replication: one license key per controller in the Global Deduplication Array.

• DD Boost protocol: one license key for the master controller.


4. Two arrays must be inter-connected. Obtain the appropriate interconnect cables to connect two arrays.

5. Convert each Data Domain system to Global Deduplication Array hardware specifications:

a. Three SAS cards are required. If the Data Domain system does not have a SAS card in slot 3, order another card.

b. 64 GB of memory is required. If the Data Domain system has fewer than 64 GB of memory, order additional memory.

Note: To determine how much memory is installed, log in as sysadmin and enter the system show meminfo command. Check the line that shows the total memory to determine your memory size.

Upgrading Hardware to a GDA System

Upgrade the hardwareFollow the instructions in the appropriate upgrade guide.

• Obtain the Data Domain GDA Controller Upgrade Guide, which is available via the Data Domain support portal.

• If the system to be upgraded does not have the specified number of SAS cards, install a SAS card as described in the SAS HBA Card Replacement and Upgrade for Expansion Shelves document for your Data Domain system.

• Install additional memory as described in the DIMM Replacement and Upgrade document for your Data Domain system.

Note: These documents are included with hardware components, and can be downloaded from the support portal at:https://my.datadomain.com/documentation.

Upgrading the DD OS Follow the instructions in the DD OS Release Notes.

62 Upgrading a Data Domain System

https://mydatadomain.com/documentation

Setting Up the Global Deduplication ArrayFollow the procedure given in Chapter 3, Installation and Configuration.


64 Upgrading a Data Domain System