m05res01

Avamar Node Addition, Module 5 - 1

Copyright 2010 EMC Corporation. Do not Copy - All Rights Reserved.

2010 EMC Corporation. All rights reserved. Avamar Node Addition 5 - 1

Module 5: Avamar Node AdditionUpon completion of this module, you will be able to: List the requirements to add a storage node to an Avamar

system Describe the Avamar Node Addition process Perform Avamar data node addition

The objectives for this module are shown here. Please take a moment to read them.




Node Addition What is it? In an Avamar multi-node RAIN system, you can add a

data node to increase capacity When adding a new node to the Avamar system, it is

advisable to balance the system to distribute existing backup data among the data nodes

DISCLAIMER: The node addition procedures in this module are provisional and should not be used at a customer site.




Node Addition Before you Begin Ensure that:

Operating System is installed on new node (non-data store only) Benchmark and stress tests are successfully run on the node (non-

data store only) Networking information is configured for new node Passwords on new node reflect the passwords for the existing

production Avamar system




Node Addition - Steps Update the hosts file on all nodes to add new nodes IP Address Ensure that you have a validated checkpoint Update the probe.xml file on the utility node and append the IP

address of the new node Synchronize the clocks on all hosts Suspend Avamar client activities Suspend Avamar replication cron job Start the new node Ensure new node comes online Perform balancing Resume client activities Resume Avamar replication cron job




Update Hosts File On All Nodes Update the hosts file on all nodes to add new nodes IP

Address

Add an entry for the new node




Ensure You Have a Validated Checkpoint It is very important to have a validated checkpoint you

can roll back to if required Checkpoints shown in Avamar Administrator - Server

window

Validated checkpoint




Update the probe.xml file Append a new node to the the probe.xml file using the

nodedb command:

nodedb add node --addr=192.168.100.6 --type=storage

.




Synchronize Clocks Across All Nodes Avamar requires that clocks on all nodes are synchronized The Avamar utility to perform time synchronization is asktime Asktime must be run:

as user dpn with ssh keys loaded on the utility node

Running asktime onthe utility node as user dpn

Desired output

.




Suspend Avamar Client activities Before adding a new node, you must suspend all client activities on the

Avamar system Utility to perform this task: avmaint Syntax: avmaint suspend

avmaint suspend halts existing client activities and denies any new client requests

Run this command from the utility node Must be run by user admin with ssh keys loaded

.




Suspend Avamar Replication Cron Job Before adding a new node, you must suspend the Avamar replication

cron job. Script to perform this task: suspend_crons

suspend_crons suspends activity of the Avamar replication cron job: repl_cron

Run this command from the utility node. Must be run by user admin with ssh keys loaded

.




Start the new node Start the new node, using the start.nodes command start.nodes

Used to start a node The --nodes=

must be specified If the --clean option is specified, all existing data on the node is deleted

.




Ensure that the new node is online Check node status, using the status.dpn command status.dpn

script used to return status of Avamar nodes Interval can be specified (optional)

For example, status.dpn 5, the node status is refreshed every 5 seconds

.




Avamar Server Dynamic Load Balancing Dynamic load balancing is a feature that allows the server

to dynamically move stripes in order to adjust storage utilization among nodes

Command: avmaint config balancemin=NUM

If NUM=0, no balancing is performed If NUM=1, only index stripes are balanced For NUM Values between 2 and 99

The balance process instructs the Avamar system to re-distribute data from the most full nodes to the least full nodes within NUMpercentage

Dynamic load balancing is a feature that allows the server to dynamically move stripes in order to adjust storage utilization among nodes.This behavior is controlled by the avmaint config balancemin=NUM command.

When this value is zero, no balancing is performed.

When this value is one, only index stripes are balanced.

For values between 2 and 99, this is a threshold percentage that will trigger load balancing for any node that exceeds that amount of available space (if a nodes available space minus the average of all other nodes is greater than or equal to this balance min value, it is deemed to be in need of balancing).RAIN is required in order for this feature to work.

Load balancing does not occur when the server is in a read-only state.

Stripes are not relocated if backups are in progress. However, once a stripe has been relocated, its data is migrated using the same mechanism as for decommission, which means that backups proceed, but performance is impacted.




Performing Balancing After the Node is online, as user admin on the utility

node, run the command:avmaint config balancemin=NUM --avamaronly




Monitoring Balancing Operation Monitor the status of the new node by typing:status.dpn




Turning Off Balancing To turn off balancing, as user admin on the utility

node, run the command:avmaint config balancemin=0 --avamaronly




Resume Avamar Client Activities and Replication Cron Job

Resume Avamar client activities: Utility to perform this task: avmaint Syntax: avmaint resume

Resume Avamar replication cron job, type: Script to perform this task: resume_crons

.




Exploration

Lab 5-1: Node Addition

Lab 5-1: Node Addition

In this lab, you add a new node to your multi-node Avamar server.




Module SummaryKey points covered in this module: Avamar Node Addition Avamar system load balancing

These are the key points covered in Module 5. Please take a moment to review them.




Course SummaryKey points covered in this course: EMC Avamar functionality Major components of EMC Avamar Installation and configuration of Avamar software (both

RAIN and NON-RAIN configurations) Installation of Avamar software by performing on-demand

and scheduled backups and recoveries Node failure simulation and node replacement Node addition and Avamar system load balancing

These are the key points covered in this course. Please take a moment to review them.

This concludes the training.




Closing Slide

m05res01

Documents

Transcript of m05res01