Avamar Data Domain Integration Lab Guide 2014
Avamar Data Domain Integration Lab Guide 2014
September 2014
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, RSA, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC
Proven, EMC Snap, EMC SourceOne, EMC Storage Administrator, Acartus, Access Logix, AdvantEdge,
AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated
Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C-Clip,
Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON,
ClientPak, Codebook Correlation Technology, Common Information Model, Configuration Intelligence,
Configuresoft, Connectrix, CopyCross, CopyPoint, Dantz, DatabaseXtender, Direct Matrix Architecture,
DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E-Lab, EmailXaminer,
EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony,
Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover,
Infoscape, Infra, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor,
MirrorView, Navisphere, NetWorker, nLayers, OnAlert, OpenScale, PixTools, Powerlink, PowerPath,
PowerSnap, QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo,
SafeLine, SAN Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF,
StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX,
TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, VMAX, Vblock, Viewlets, Virtual Matrix, Virtual
Matrix Architecture, Virtual Provisioning, VisualSAN, VisualSRM, Voyence, VPLEX, VSAM-Assist,
WebXtender, xPression, xPresso, YottaYotta, the EMC logo, and where information lives, 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.
© Copyright 2014 EMC Corporation. All rights reserved. Published in the USA.
Purpose: In this lab, you will integrate a Data Domain with an Avamar
server.
Step Action
Log in to the Virtual Data Center with the user name and password provided to
you by the instructor.
5 At the vCloud login screen, enter the same User name and Password assigned to
you by your instructor. Then, click Login.
6 You will be using the Avamar DD 7.1 Lab vApp for all the labs for this course. To
get your own personal copy of the vApp, clone the vApp to My Cloud.
From the home screen, click Add vApp from Catalog and
9 Result: When the clone operation completes, you see a copy of the Avamar DD
7.1 Lab vApp in the home screen. The status of the vApp is Stopped.
Start the vApp by clicking the green Start button. Then, click Open.
10 To view a console window, click in the blue console icon of the virtual machine
that you want to work in. Click the win console.
Result: A new windows opens showing the console for that machine. When you
wish to work on another virtual machine, return to the vApp Diagram window
and click another console.
11 Once the machine has booted, send a Ctrl-Alt-Delete sequence to the Windows
machine by clicking the icon in the top right of the console window.
13 The virtual Data Domain systems in this lab use a temporary license. To activate
this license, open the configure DataDomain script folder on the Desktop.
Double-click the configure_DD01.bat and configure_DD02.bat files to run these
scripts.
Note: If the scripts fail, wait a few minutes for the Data Domains to complete
booting and try again.
14 The lab environment is now ready to use. The Avamar DD 7.1 Lab vApp consists of
these 5 virtual machines:
win - This is your primary Windows workstation for the labs. It also is a domain
controller and DNS for your configuration.
single01 - This is your Avamar single-node server.
single02 - This is a second Avamar single-node server. You will migrate to this server
in a later lab.
dd01 - This is a Data Domain system
dd02 - This is a second Data Domain system. You will migrate to this server in a later
lab.
Step Action
2 You must first configure DD Boost and SNMP on the Data Domain before it can be
added to the Avamar server.
Launch a web browser and browse to the Data Domain Enterprise Manager GUI for
your first Data Domain by entering the following address:
http://dd01.emc.edu
3 Select the dd01 in the tree on the left and click on Data Management DD Boost
from the tabs at the top of the interface.
Click OK.
8 Scroll down to the SNMP V2C Configuration section and click Create in the
Communities subsection.
10 The Data Domain is now ready to be added to the Avamar server. Log out of Data
Domain and close the web browser.
11 Launch Avamar Administrator from the link on the desktop. Log into single01
as MCUser with password MCUser1.
12 Open the Server interface and select the Server Management tab.
13 Select Actions Add Data Domain System. Enter the following information into
the dialog box:
Click Get Stream Info to see the maximum number of streams supported by the
Data Domain. Confirm any warnings and notifications that appear.
14 Click the SNMP tab. Enter avamarSNMP as the SNMP Community String.
15 Click OK. Ensure that the Data Domain has been added and click Close.
16 Click the Server Monitor tab and the Data Domain tab. Examine the Data Domain
statistics.
Step Action
2 Open Avamar Administrator. Log onto single01 with username MCUser and
password MCUser1.
3 Open the Backup and Restore interface. Select the win client from the tree on
the left. Select Windows File System C: Abackup from the plug-in
window.
5 Open the Activity interface and ensure that the backup completes successfully.
Note that the backup is being stored on the Data Domain by looking at the
Server column.
6 When the backup completes, open the C:\Abackup directory. Delete all files in
this directory.
8 Select the win client and click the Restore tab. Select the backup that was
performed in the previous part of this lab.
Select the Abackup directory and click Actions Restore Now. Click OK to start
the backup.
Step Action
1 Open Avamar Administrator if not already running. Log onto single01 with
username MCUser and password MCUser1.
2 View the Capacity section and make a note of the Avamar usage and the Data
Domain usage.
3 A window showing the Avamar server and metadata utilization appears. View
the capacity utilization and close the window.
4 Click the dd01.emc.edu link in the capacity section to open the Data Domain
management interface. Ignore any security certificate warnings.
5 Log in to the Data Domain GUI with the username sysadmin and password
student
6 In the next few steps, you will use CIFS to explore the organization of Avamar
data on a Data Domain. This is for exploration purposes only and is not typically
done in a production environment.
Select dd01.emc.edu from the left panel. Select Data Management > CIFS
7 Create a new CIFS share by selecting the Shares tab, and clicking Create.
Click OK
12 Explore the avamar-<SYS-ID> directory and the cur directory beneath it. The
directory in the cur directory represents the win client.
13 Open the directory representing the win client to view the directory that
represents the backup taken earlier.
14 Open the Data Domain interface. From the Data Management > CIFS > Shares
tab, select the col1 share and click Delete.
Purpose: In this lab, you will migrate data to perform both a Data
Domain replacement, and an Avamar server replacement.
Step Action
1 The dd01 Data Domain system is currently integrated with the Avamar server
single01. In this lab, you will replace dd01 with a new Data Domain system,
dd02, while keeping single01 in use.
2 Open putty from the link on the desktop. Open a session to single01.emc.edu.
Log in as admin with a password of EMCAvamar1!
5 Validate the new checkpoint with the following command. Use the CP-Tag
number from the previous step.
6 Wait a few minutes for the checkpoint validation to complete. Confirm that the
checkpoint is validated with the following command:
7 Determine the Avamar server’s system ID number. This number is used in the
name of the Data Domain’s MTree for the Avamar server.
avmaint hfscreatetime
Avamar-ID: _______________________________________
8 Launch a web browser and browse to the Data Domain Enterprise Manager GUI
for your Data Domain by entering the following address:
http://dd01.emc.edu
9 Add dd02 to the interface by clicking the Add above the left panel.
11 Select Replication from the top of the interface and click Create Pair.
Click OK. This will create the replication pair and begin replication.
13 Since our lab environment does not contain much data, the replication should
complete very quickly. Wait for the replication to show an Idle state and a
completion time of Completed.
14 Open Avamar Administrator if not already running. Log onto single01 with
username MCUser and password MCUser1.
16 In a putty session to single01, put the server into read-only mode with the
following command:
17 Return to the Data Domain GUI. Select the replication pair created earlier and
delete it by clicking Delete Pair.
18 Open putty from the link on the desktop. Open a session to the destination Data
Domain, dd02.emc.edu. Log in as sysadmin with a password of student
19 You will create and enable a DD Boost user. This will also ensure proper DD
Boost file ownership.
ddboost disable
23 Enable DD Boost:
ddboost enable
24 Create the SNMP community on dd02 and enable it with the following
commands:
snmp enable
Take the server out of read-only mode with the following command:
26 Open Avamar Administrator to the single01 server. Open the Server interface by
selecting Navigation > Server.
27 On the Server Management tab, select dd01.emc.edu and select Actions > Edit
Data Domain System.
28 Change the Data Domain System Name to dd02.emc.edu and click OK.
30 Open the Backup and Restore interface in Avamar Administrator. Select the win
client, click the Restore tab, and perform a test restore to ensure that the data is
still accessible.
Step Action
1 The dd02 Data Domain system is currently integrated with the Avamar server
single01. In this lab, you will replace single01 with a new Avamar server,
single02, while keeping the same Data Domain, dd02, in use.
2 Launch Avamar Administrator from the link on the desktop. Log into the
replacement Avamar server, single02 as MCUser with password MCUser1
3 Open the Server interface and select the Server Management tab.
4 Select Actions Add Data Domain System. Enter the following information
into the dialog box:
Click Get Stream Info to see the maximum number of streams supported by the
Data Domain. Confirm any warnings and messages.
5 Click the SNMP tab. Enter avamarSNMP as the SNMP Community String.
6 Click OK. Ensure that the Data Domain has been added and click Close.
7 Open putty from the link on the desktop. Open a session to single01.emc.edu.
Log in as admin with a password of EMCAvamar1!
8 Create a fresh backup of the MCS database by entering the following command:
mcserver.sh --flush
emserver.sh --flush
10 Initiate a full root-to-root replication and write the output to a log file. Enter the
following command on one line:
tail -f /home/admin/replicate_YYYMMDD.log
Wait for the replication to complete. Press Ctrl-C to exit the tail command.
12 Open putty from the link on the desktop. Open a session to the destination
server, single02.emc.edu. Log in as admin with a password of EMCAvamar1!
mcserver.sh --stop
Enter Y to confirm.
14 Restore the MCS database by entering the command below. You will be asked to
answer a series of prompts in the next few steps.
16 Enter the destination server, single02.emc.edu when asked for the Avamar
server to restore from.
Note: There is a delay of about a minute and many pages of output before the
next prompt appears.
21 Enter 1 to select the default value for the RMI machine IP address.
mcserver.sh --start
emserver.sh --stop
Enter Y to confirm.
26 Restore the EMS database by entering the command below. You will be asked to
answer a series of prompts in the next few steps.
27 Enter the destination server, single02.emc.edu when asked for the Avamar
server to restore from.
emserver.sh --start
30 The win client is currently activated to single01. However, single02 also contains
this client as an activated client. To ensure proper activation, you should
deactivate the client from single02 and then re-activate.
Launch Avamar Administrator from the link on the desktop. Log into the
replacement Avamar server, single02 as MCUser with password MCUser1
31 Open the Policy interface. Select the Policy Management > Clients tab.
32 Select the clients domain, and select the win.emc.edu client. Click Edit.
34 On the win client, right-click the Avamar Icon in the system tray and select
Manage > Activate Client.
36 Open the Backup and Restore interface in Avamar Administrator. Select the win
client, click the Restore tab, and perform a test restore to ensure that the data is
still accessible.
37 Tom complete the migration, you must delete the backup metadata from the
original Avamar server, and delete the data on the Data Domain that is still
referenced by the original Avamar.
Open putty from the link on the desktop. Open a session to the original server,
single01.emc.edu. Log in as admin with a password of EMCAvamar1!
38 Determine the ddr_index value for dd02. Enter the following command:
ddrmaint read-ddr-info
41 Launch Avamar Administrator from the link on the desktop. Log into the original
Avamar server, single01 as MCUser with password MCUser1
42 Open the Server interface and select the Server Management tab.
43 Select dd02.emc.edu from the tree on the left. Then, select Actions > Delete
Data Domain System.
When you are sure that you are finished with the labs, please perform these lab clean-up steps.
Step Action
1 Click My Cloud and then vApps from the left side of the main vCloud window.
3 When you are sure that you no longer want to work in this lab configuration, right-click
your vApp and select Delete.