Avamar Data Store Gen3 Customer Service Guide
Avamar Data Store Gen3 Customer Service Guide
Avamar Data Store Gen3 Customer Service Guide
DATA STORE
GEN3
EMC CORPORATION
CORPORATE HEADQUARTERS:
HOPKINTON, MA 01748-9103
1-508-435-1000
WWW.EMC.COM
TABLE OF CONTENTS
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Scope and Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Product Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Your Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Typeface Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Notes, Tips and Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
6
6
7
General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
EMC Avamar Data Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
EMC Avamar Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Important Terms and Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Avamar Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Avamar Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Avamar Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Logical Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
20
20
21
24
27
29
30
30
TABLE OF CONTENTS
FOREWORD
Scope and Intended Audience
Scope This publication describes how to add or replace field replaceable units (FRUs) on
Intended Audience The information in this publication is primarily intended for EMC Customer Service
Engineers who are responsible for repairing Avamar Data Store servers at
customer sites. This document is not intended for use by customers who are
performing their own replacement parts servicing. In that case, discrete
documentation is provided with customer replaceable units (CRUs). The set of
CRUs is the same as FRUs except for the network switch.
Product Information
For current documentation, release notes, software updates, as well as
information about EMC products, licensing and service, go to the EMC AvaSphere
web site at http://Powerlink.EMC.com.
Typeface Conventions
FOREWORD
Your Comments
Your suggestions will help us continue to improve the accuracy, organization and
overall quality of the user publications. Please send your opinion of this document
to:
[email protected]
Please include the following information:
Product name and version
Document name, part number and revision (for example, A01)
Page numbers
Other details that will help us address the documentation issue
Typeface Conventions
The following table provides examples of standard typeface styles used in this
publication to convey various kinds of information.
EXAMPLE
Click OK.
- or Select File > Close.
DESCRIPTION
Type:
cd /tmp
--logfile=FILE
Installation Complete.
NOTE: This is a general note. Notes contain ancillary information intended to clarify a topic or procedure. Notes never
contain information that will cause a failure if ignored.
GENERAL INFORMATION
This chapter contains general information about the EMC Avamar Data Store
which is a packaged solution consisting of Avamar deduplication backup and
recovery software running on a preconfigured EMC-certified hardware platform.
EMC Customer Service Engineers should familiarize themselves with this
information before performing any maintenance activities on an Avamar Data
Store.
10
11
Functional Overview
GENERAL INFORMATION
Functional Overview
This topic provides detailed information about each part of the Avamar
client/server system and describes how the various parts interact with one
another.
Avamar Servers
All Avamar servers store client backups and also provide essential processes and
services required for client access and remote system administration.
A Word About Avamar Server Hardware Configurations. Avamar servers
are available in either single-node or scalable multi-node configurations. For the
most part, when using Avamar Administrator management console software, all
Avamar servers look and behave the same. The main differences among various
Avamar server configurations is the number of nodes and disk drives reported in
the server monitor.
Documenting specific differences in Avamar server hardware configurations is
beyond the scope of this publication. Whenever specific limitations and best
practices for certain configurations are known, they will be noted for your
convenience. However, these occasional notes should not be considered definitive
or exhaustive. Consult EMC Technical Support or your EMC reseller for additional
information about your specific hardware.
Nodes. The primary building block in any Avamar server is a node. Each node
is a self-contained rack-mountable network-addressable computer that runs
Avamar server software on the Linux operating system. Nodes can also contain
internal storage in the form of hard disk drives. If the node is configured with
internal storage (that is, a single-node server), it is internally mirrored to provide
robust fault tolerance.
Utility
Node
Storage
Nodes
Nodes that store the actual backup data. Multiple storage nodes are
configured with multi-node Avamar servers based upon
performance and capacity requirements. Storage nodes can be
added to an Avamar server over time to expand performance with
no downtime required. Avamar clients connect directly with Avamar
storage nodes; client connections and data are load balanced
across storage nodes.
NDMP
Accelerator
12
Functional Overview
GENERAL INFORMATION
Avamar Clients
Avamar provides client software for various computing platforms. Each client
comprises a client agent and one or more plugins.
AVAMAR CLIENT
FILE
SYSTEM
PLUGIN
APPLICATION
PLUGIN
AVAMAR SERVER
AGENT
MANAGEMENT CONSOLE
SERVER (MCS)
GEN 000995
Filesystem
plugins
Application
plugins
Free BSD
HP-UX
IBM AIX
Linux
Mac OS X
Microsoft Windows
Microsoft Windows Volume Shadow Copy Service (VSS)
SCO OpenServer
SCO UnixWare
Sun Solaris
Novell NetWare
VMware
IBM DB2
Lotus Domino
Microsoft Exchange
Microsoft Office SharePoint Server (MOSS)
Microsoft SQL Server
NDMP for NAS devices (EMC Celerra IP storage systems and
Network Appliance filers)
Oracle
13
Functional Overview
GENERAL INFORMATION
Avamar Administrator
Avamar Administrator is a graphical management console software application
that is used to remotely administer an Avamar system from a supported Windows
client computer.
Encryption
Avamar can encrypt all data sent between clients and the server in flight. Each
individual Avamar server can also be configured to encrypt data stored on the
server at rest.
In-Flight Encryption. In order to provide enhanced security during
client/server data transfers, Avamar supports two levels of in-flight encryption
(medium and high), which can be set on a client-by-client basis in client
properties, or for an entire group of clients in group properties. You can also turn
off in-flight encryption entirely.
At-Rest Encryption. The decision to encrypt all data stored in an Avamar
server is typically a one-time decision that is made when the server is initially
deployed at a customer site.
Logical Units
The RAID-1 (2 TB nodes) or RAID-5 (1 TB and 3.3 TB nodes) set in an Avamar
Data Store storage node is divided into four (1 TB node), three (2 TB node), or
two (3.3 TB node) equal size logical units (LUNs) at the RAID controller. LUNs are
mapped by the operating system.
LUN 0
For 1 TB and 2 TB nodes, LUN 0 is mapped according to the following table:
PARTITION
/boot
128 MB
/ (root)
8 GB
/var
1.5 GB
swap
4 GB
/bootalt
128 MB
/rootalt
8 GB
/varalt
1.5 GB
/data01
Remaining Space
14
Functional Overview
GENERAL INFORMATION
For 3.3 TB nodes, LUN 0 is mapped according to the following table:
PARTITION
/boot
128 MB
/ (root)
8 GB
/var
1.5 GB
swap
4 GB
/bootalt
128 MB
/rootalt
8 GB
/varalt
1.5 GB
/space
Remaining Space
Remaining LUNs
1 TB nodes - LUNs 1 through 3 are mapped to data partitions /data02
through /data04, respectively.
2 TB nodes - LUNs 1 and 2 are mapped to data partitions /data02 and
/data03, respectively.
3 TB nodes - LUN 1 is mapped to data partition /data01.
15
16
17
18
19
The procedure that follows uses the EMC Titan rack as an example. For Telco
installation, alter these instructions as required.
20
21
4. Pull the inner rail release buttons, then pull the node forward until it
extends into the locked position. See next image.
5. Slowly pull the node forward to the fullest extension allowed on the rail
assemblies.
IMPORTANT: If the customer site makes full extension of
the rail assemblies unsafe or impossible, refer to Limited
Space Procedure (page 23).
22
2. Press both blue tabs and slide the node into the rack until the blue tabs are
even with the front of the rack.
23
4. Insert and secure a tie wrap through the hole and slot on both rails.
5. From the front of the rack, pull the node forward again to the fullest
extension allowed by the tie wrap restriction on the rail assemblies.
24
25
5. Secure the rail assembly in the cabinet by inserting and tightening the
stabilizer screws directly behind each bezel latch.
6. Install the bezel.
(a) Press the bezel onto the latch brackets until it snaps into place.
26
Follow-On Configuration
REPLACING AVAMAR DATA STORE NODES
Follow-On Configuration
In order to put a node into service as a utility or storage node, certain follow-on
configuration procedures must be performed. First, you must configure the basic
networking capabilities of the node, and then contact Avamar Technical Support
for final configuration.
1. Configure your laptop as follows:
Static IP address: 10.99.99.99
Netmask: 255.255.255.0
Gateway: 10.99.99.5
2. Assign the original IP address to the new node:
(a) Connect the laptop to the eth1 network interface (Gb 2 port) of the new
node with a CAT6 Ethernet cable.
NOTE: The eth1 IP address on all nodes is 10.99.99.5.
User=root
Run netconfig
(c) Configure the basic networking capabilities of the node (eth0 network
interface, Gb 1 port) by typing the following on a single command line:
/usr/sbin/netconfig --ip=STATIC-IP-ADDR --netmask=NETMASK
--hostname=HOSTNAME --domain=DOMAIN --device=eth0
--gateway=GATEWAY
Where STATIC-IP-ADDR, NETMASK, HOSTNAME, DOMAIN and GATEWAY are
the static IP address, netmask, hostname, domain and gateway
settings for this node, respectively, as provided by the customer.
(d) Restart the network service by typing:
service network restart
(e) Verify the preceding data by typing:
ifconfig
(f) Verify basic network connectivity by typing:
ping STATIC-IP-ADDR
Where STATIC-IP-ADDR is the static IP address of the utility node of the
Avamar server.
(g) Reboot the node by typing:
reboot
(h) Exit the command shell.
(i) Disconnect the Ethernet cable from the eth1 network interface of the
node.
27
Follow-On Configuration
REPLACING AVAMAR DATA STORE NODES
3. After the replacement node reboots, verify basic network connectivity and
login capability by doing the following:
(a) Connect the laptop to port 24 of the network switch with a CAT6
Ethernet cable.
NOTE: If the switch is customer-provided (that is, different
from the standard Avamar Data Store equipment), ask the
customer about switch connectivity.
(b) Reconfigure the laptops IP address:
From Start, open Settings > Network and Dial-up Connections
and select Local Area Connection.
Select Properties.
Double-click Internet protocol (TCP/IP).
Click Use the following address.
Set the IP address to an available address on the network
(customer-provided).
Set the netmask and gateway as provided by the customer.
Click OK.
Click OK again.
In a command prompt window, type ipconfig to ensure the new IP
address is active.
If not, disable and reenable the Ethernet connection in the Local
Area Connection dialog box.
User=root
(c) Verify that you can log in to the replacement node as user root.
Connect to the node using its IP address. When prompted, type the
root user account password and press ENTER.
4. Exit the command shell.
5. Unplug the Ethernet cable between the laptop and node.
6. Contact Avamar Technical Support to coordinate final server configuration.
Avamar Technical Support will remotely connect to the server and
configure node type and network files as required.
28
Transplanting a Node
REPLACING AVAMAR DATA STORE NODES
Transplanting a Node
Transplanting a node is a process that replaces the node chassis but retains the
original hard drives. This process is indicated when server troubleshooting
indicates both of the following:
Node failure is located in a chassis component (for instance, memory).
All hard drives are working and contain valid data.
IMPORTANT: Coordinate with Avamar Technical Support
when transplanting a node.
The following procedure is similar to the Basic Node Remove and Replace
Procedure (page 20) in that a standard Avamar node FRU has been delivered to
the customer site. The differences are the following:
The replacement node is placed into operation as the new storage or utility
node.
The current spare node remains the spare.
The follow-on configuration procedure described previously is not required.
1. Perform the Locate and Remove Defective Node (page 21) procedure.
2. Place the defective and replacement nodes on a workbench.
NOTE: Refer to Removing a Hard Drive (page 39) and
Installing a Hard Drive (page 40).
3. Remove all hard drives from the replacement node and set them aside.
4. Remove each hard drive on the defective node one at a time and install it
in the same drive bay in the replacement node.
IMPORTANT: Ensure that you install each hard drive in the
correct drive bay. Switching each hard drive one at a time
decreases the chances of error.
5. Perform the Install Replacement Node (page 24) procedure.
6. Power up the node.
RAID software recognizes the original hard drives and prompts you to
import them to the new chassis hardware.
7. Select Import.
29
30
31
32
IMPORTANT: For switches received directly from the factory or from service logistics, use a standard Ethernet cable
to connect your service laptop to port 24 of the switch. For
switches previously configured to run in ADS Gen1 or Gen2
systems or other deployments, this Ethernet cabling method
will not work. You must first use a DB-9 to RJ-45 connector
serial cable to configure and enable an IP address on the
switch. Then, you can use the same Ethernet cabling and
instructions to configure the switch. Separate directions for
configuring the network switch using the two different cable
connections follow.
1. Locate the zipped switch files (ADS_Gen3_switch_config.zip) on EMC
Powerlink.
This file is posted in the Software Downloads and Licensing >
Downloads A-B > Avamar branch of the Support menu.
2. Download the zip file to C:/ directory on your laptop.
33
DO THIS
34
35
36
37
38
39
6. Pull the failed hard drive from the node chassis until it is free of the drive
bay.
40
: 0
Status
: Ok
Name
: Virtual Disk 0
State
: Ready
Progress
: Not Applicable
Layout
: RAID-5
Size
Device Name
: /dev/sda
Type
: SAS
Read Policy
: No Read Ahead
Write Policy
: Write Back
Cache Policy
: Not Applicable
: 64 KB
41
42
REQUIREMENT
43
44