M 04 Res 02
M 04 Res 02
Lab Guide
Objectives:
References:
Fail a node
Perform data recovery
Decommission the failed node
Add a replacement data node
Version E
Page 1 of 26
Lab Guide
Desired Architecture
Simulate storage4 failure.
Add storage5 as a replacement node.
Avamar Utility
Node
Avamar Data
Node
Avamar Data
Node
Avamar Data
Node
Avamar Data
Node
Avamar Data
Node
(Spare)
utilitynode
storage0
storage1
storage2
storage3
storage4
192.168.100.2
192.168.100.3
192.168.100.4
192.168.100.5
192.168.100.6
192.168.100.7
Version E
Page 2 of 26
Lab Guide
Version E
Page 3 of 26
Step
2
Type: nodenumbers
Make note of the output
Lab Guide
Action
Version E
Page 4 of 26
Step
4
Click on Server.
Lab Guide
Action
Open a PuTTY session to storage3. Accept any warnings and login as user root
password: changeme.
Kill the storage nodes gsan process in order to cause the node to fail. Type:
killall gsan
Version E
Page 5 of 26
Lab Guide
Step
Action
9
To start Avamar Administrator in Windows, click the Avamar Administrator
shortcut on the desktop or from the Windows Start menu.
Enter the following information:
User Name: MCUser
Password: MCUser1
Domain Name: /
Administrator Server: utilitynode
Then, click Log On. Accept any JRE warnings.
Note: It may take several minutes for the log on; please be patient.
Version E
Page 6 of 26
Lab Guide
Step
Action
10 You will see an Avamar Alert popup that informs you that a node has gone offline.
Click View Details.
Study the information in the Event Detail window. Then, click Close.
Version E
Page 7 of 26
Lab Guide
Step
Action
11 From the Avamar Administrator menu, click Server.
The following screen appears. Note that Node 0.3 is red (offline).
Version E
Page 8 of 26
Lab Guide
Version E
Page 9 of 26
Lab Guide
Step
Action
2
Launch Avamar Administrator. Click Backup & Restore.
Version E
Page 10 of 26
Lab Guide
Step
Action
3
Expand the tree in the left pane and select your client.
Click the Select for Restore tab in the right pane.
Browse through your backup and select the C:\WINDOWS\Fonts\ariblk.ttf file.
Version E
Page 11 of 26
Lab Guide
Step
Action
4
Select Actions > Restore Now from the menu bar. Then, click OK to begin the
restore.
Click OK to confirm.
Version E
Page 12 of 26
Lab Guide
Step
Action
5
Monitor the progress of the restore by clicking Navigation > Activity. Verify that the
restore completes successfully.
Verify that the ariblk.ttf file was restored by checking the contents of the
C:\WINDOWS\Fonts folder on your client.
Version E
Page 13 of 26
Lab Guide
Step
Action
1
Open a PuTTY session to your utility node and login as user root password
changeme.
Type: nodenumbers and study the output.
Version E
Page 14 of 26
Lab Guide
Step
Action
2
In Avamar Administrator, select Navigation Server, and click the Checkpoint
Management tab.
Back in the PuTTy session for the utilitynode, change users to admin. Type:
su - admin
Load the admin SSH keys. Type:
ssh-agent bash
ssh-add ~/.ssh/admin_key
passphrase: P3t3rPan
Version E
Page 15 of 26
Lab Guide
Step
Action
4
Type the following to display information about the spare node:
nodedb print --nodes=0.spare.0
Version E
Page 16 of 26
Lab Guide
Step
Action
6
Verify that the probe.xml file contains information reflecting the replaced node:
nodedb print
Version E
Page 17 of 26
Step
8
Change users to user dpn. Type:
Lab Guide
Action
su - dpn
Load the dpn SSH keys, type:
ssh-agent bash
ssh-add ~/.ssh/dpnid
export SYSPROBEUSER=root
Version E
Page 18 of 26
Lab Guide
Step
Action
10 Enter n to the question Do you have a dedicated Avamar Subnet?
11
12
Version E
Page 19 of 26
Lab Guide
Step
Action
13 Enter y to proceed with the installation.
14
Version E
Page 20 of 26
Lab Guide
Step
Action
15 Enter y to watch for time synchronization.
16
This next step takes about 10 minutes. After completion, enter y to see the results.
Version E
Page 21 of 26
Step
17 Results:
Lab Guide
Action
18
Version E
Page 22 of 26
Lab Guide
Step
Action
19 Change user to admin and load the admin SSH keys. Type:
su - admin
ssh-agent bash
ssh-add ~/.ssh/admin_key
passphrase: P3t3rPan
20
Version E
Page 23 of 26
Lab Guide
Step
Action
21 Launch a new PuTTY session to your utility node and login as user root password
changeme.
Monitor the status of the new node by typing:
status.dpn <Number of seconds to refresh>
Version E
Page 24 of 26
Lab Guide
Step
Action
22 Go back to the SSH session running as the admin user and type: nodenumbers
23
In the PuTTY session to your utility node (host 1) logged on as root, monitor the
status of your nodes by typing:
status.dpn
Version E
Page 25 of 26
Lab Guide
Step
Action
24 Restart server operations and scheduled cron jobs. In the PuTTY session running as the
admin user, type:
avmaint resume
avmaint sched resume --avamaronly
25
26
View the Server Monitor in Avamar Administrator to see that the new node is online.
Version E
Page 26 of 26