You are on page 1of 5

EMC Corporation, Technology Solutions Functional Overview Checklist

Introduction
This document is provided to <Customer Name and allows us to collect in!ormation
necessary to implement and veri!y the EMC
"
Avamar Implementation service#
The sections that !ollow include $uestions a%out your speci&c data environment#
Avamar Functional Overview Checklists
1. Avamar Implementation Checklist
Avamar
Implementat
ion
Functional
Overview
Task Task
Comple
te
Data
Complete
Comments
System Overview
'vamar System (esign and )asic
Functionality

(escri%e each system used to make up grid
con&guration#

E*plain 'vamar +,- and each sections role in
the overall usage o! the product#
(iscuss 'vamar so!tware product concepts#

E*plain 'vamar licensing and show the
customer capacity overview !rom 'vamar +,-
Server Module#
Provide customer
focus on Capacity
mgmt. and review
its importance.
E*plain to customers the how to review alerts
and system status#
.e!erence the Avamar Administrators Guide as source o! in!ormation
** Completed during -mplementation Service
Client / 0lug1-n -nstall and Test 0roduction Clients **
'vamar -mplementation Service Functional Overview Checklist234532667 0age 4
EMC Avamar Implementation
Checklist Model Number: PS-BAS-ADMN ADMNA A!E
EMC Corporation, Technology Solutions Functional Overview Checklist
Avamar
Implementat
ion
Functional
Overview
Task Task
Comple
te
Data
Complete
Comments

'ctivate clients to 'vamar utility node via
F8(N# **
-nstallations
's we only install ten 946: clients and 92: ()
plug1ins on a %asic 0S engagement, ask
customer to provide uni$ue client types and
applications such as E*change, S8;, Oracle,
and Share0oint, i! applica%le# **
E*plain install points<

O%tain clients agents and plug1ins o= o! grid
9documents and download we% page:

Choose correct 9or nearest: client type 9%rie>y
e*plain:<

-! windows, use cases !or vss or otm
Applicable to 6.X
clients using the
4.X client for Win
!!!
-! plugin, %ase client agent installed &rst
-! windows clusters, special cluster install
pattern, determine client installation location
and cover the !ollowing<
-nstall locations, si?e re$uirements, cache
operation
-nstall and activate client to 'vamar ,tility
Node via F8(
'vamar (omains
Con&gurations
(iscuss use cases around creating (omains
should customer desire separation o! clients
%y department responsi%ility, operating
system, or application !unctions# This may %e
re$uired %y customer as there may %e
multiple groups who have responsi%ility !or
daily %ackups and or restores#

Show customer how to create 'vamar
(omains as %est descri%ed %y the 'vamar
)est 0ractices +uide

,sing the 'vamar +,-, navigate to the
'dministration section, select 'ctions, New
(omain
'vamar (atasets
(iscuss with the customer creation o! 'vamar
(atasets# The (ataset is typically where
client3application options are de&ned !or the
type o! %ackup you are per!orming# Typically
an individual 'vamar (ataset is created !or
each type o! operating system or speci&c
plug1in type used %y the customer 9e#g#,
@indows File Systems, ;inu*, E*change, and
S8;:#
'vamar -mplementation Service Functional Overview Checklist234532667 0age 2
EMC Corporation, Technology Solutions Functional Overview Checklist
Avamar
Implementat
ion
Functional
Overview
Task Task
Comple
te
Data
Complete
Comments

,sing 'vamar +,-, navigate to Tools 11
(atasets

'lways use a naming convention 9e#g#,
serversAdataset:# Belp is in policy wi?ard# 's
customer is driving, they will choose the
options they care a%out, and you can discuss
these#

E*plain dataset properties and evaluation
order<
Source data list
E*clusion list
-nclusion list
0lug1in options

Bighlight pre1 and post1script &elds, throttles,
advanced options, CmoreC option
'vamar Schedules
(iscuss with the customer creation o! 'vamar
Schedules# The 'vamar Schedule is typically
con&gured to de&ne daily %ackup times /
%ackup window duration# (uring the
discussion o! the %ackup schedule
con&guration we typically discuss the 'vamar
Maintenance Cycle covering their !unctions
and impact on the (aily )ackup window the
customer desires to implement#

,sing 'vamar +,-, navigate to Tools 11
Schedules

'lways use a naming convention ###
serversAschedule 9helps in policy wi?ard:

's customer is driving, they will choose the
options they care a%out, and you can discuss
these

)rie>y review %ackup window with customer
'vamar maintenance is %etween * and *
Customer %ackup window is %etween y and y
E*plain schedule points
'vamar .etention
0olicies
(iscuss with the customer creation o! 'vamar
.etention 0olicies# The 'vamar .etention
0olicy is typically con&gured to de&ne a
custom set o! daily, weekly, monthly, or yearly
retention type to %e applied to %ackups
per!ormed#
(ependent on what
was sold# (irect
discussion and
reiterate how they
were si?ed and
capacity etc#
'vamar -mplementation Service Functional Overview Checklist234532667 0age 5
EMC Corporation, Technology Solutions Functional Overview Checklist
Avamar
Implementat
ion
Functional
Overview
Task Task
Comple
te
Data
Complete
Comments

,sing 'vamar +,-, navigate to Tools 11
0olicies

'lways use a naming convention 9e#g#,
serversAretention1policy:# Belp is in policy
wi?ard# 's customer is driving, they will
choose the options they care a%out, and you
can discuss these#

0oint out advanced option 9avoid %asic, do
advanced ### letDs you set !ull retention
choices:

'lways have successive &elds logically larger
than previous &elds 9e#g#, 4E days, E weeks,
42 months, 2 years:

+rid was si?ed per si?ing spreadsheet, which
took customer retention policy and data types
into account
E*plain how every %ackup is logically a !ull

(ailies get tagged as weekly, weeklies get
tagged as monthly
'vamar +roup
Con&guration
(iscuss with customer the re$uirement to
create 'vamar +roups# The groups are
created to separate clients %y operating
systemF and %y application !unctions#

Show customer how to create 'vamar +roups
as %est descri%ed %y the 'vamar )est
0ractices +uide

,sing the 'vamar +,-, navigate to the 0olicy
section, select 'ctions, New +roup

,sing newly de&ned groups, edit each group
to map a previously con&gured (ataset,
Schedule, / .etention 0olicy to use as a
de&ned set o! con&guration options#

,sing each newly de&ned group, add
applica%le clients to each group# Clients must
%e part o! the domain where the group has
%een previously de&ned#
Enterprise Manager
.eview .eview the System Maintenance ta% which
provides access to work>ows#
Customer enabled
wor"#ow may be
included in future
Avamar releases
.eplication
Con&guration
.eview
.eview the .eplication Con&guration
speci&cally !or Single Node3.O)O
environment
$%cludes &4!!
nodes
'vamar -mplementation Service Functional Overview Checklist234532667 0age E
EMC Corporation, Technology Solutions Functional Overview Checklist
Avamar
Implementat
ion
Functional
Overview
Task Task
Comple
te
Data
Complete
Comments
'vamar S@ ,pgrade
Overview
E*plain that EMC per!orms all upgrades and
let them know they need to open an S. to
re$uest an upgrade and that upgrades are
oGine activities#
0assword
Maintenance
E*plain the importance !or the customer to
maintain passwords and password security
'efault passwords
removed in (.!
0roHect Closure 0roHect Closure
Con&rm -)+ !orm9s: su%mitted
Con&rm grid9s: reporting to 'valanche

Ialidate grid9s: associated with appropriate
site -(9s: in SJ.
Con&rm .un )ook delivered to customer
Su%mit 0roHect Completion Form

.emind customer to complete 'ssurance o!
Solution 8uality 9'S8: survey

Ieri!y customer su%mitted 'ssurance o!
Solution 8uality 9'S8: survey
.e!erence the Avamar PEQ and ACG Tools as source o! in!ormation
'vamar -mplementation Service Functional Overview Checklist234532667 0age K

You might also like