Professional Documents
Culture Documents
The objectives for this module are shown here. Please take a moment to read them.
-1
-2
Ensure that:
Operating System is installed on new node (non-data store only)
Benchmark and stress tests are successfully run on the node (nondata store only)
Networking information is configured for new node
Passwords on new node reflect the passwords for the existing
production Avamar system
-3
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
-4
-5
Validated checkpoint
2010 EMC Corporation. All rights reserved.
-6
-7
Running asktime on
the utility node as user dpn
Desired output
-8
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
-9
Before adding a new node, you must suspend the Avamar replication
cron job.
Script to perform this task: suspend_crons
- 10
- 11
- 12
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.
- 13
Performing Balancing
- 14
- 15
- 16
- 17
Exploration
- 18
Module Summary
Key points covered in this module:
These are the key points covered in Module 5. Please take a moment to review them.
- 19
Course Summary
Key points covered in this course:
These are the key points covered in this course. Please take a moment to review them.
This concludes the training.
- 20
Closing Slide
- 21