Operational Command Reference Guide –

Frequently Used Commands

Table of Contents

1 Introduction...............................................................................................................................5

1
2 Commands................................................................................................................................6
2.1 Command to find list of VMs that are part of NetWorker VMware backup policies:...........................................6
2.2 Command to find the list of available backups of particular client in Avamar:......................................................6
2.3 Command to restart NetWorker services on windows host (including NMC services)...........................................7
2.4 Avamar model number and serial number:..........................................................................................................8
2.5 Command to find a particular word in all or specific file in a folder:......................................................................8
2.6 Couple of commands to obtain the details of VMware policy in NW 8.2...............................................................9
2.7 To view what process is using a TCP port in Windows Server 2008.....................................................................12
2.8 Curl commands (if telnet is not working on any system).....................................................................................13
2.9 Commands to add/remove clients to/from VMware policy in NW.......................................................................13
2.10 Deleting the Peer information of clients from both NetWorker server and client side.........................................15
2.11 Common usage of scanner command:...............................................................................................................16
2.12 NetWorker command line restore/recovery for filesystem..................................................................................17
2.13 Finding the serial numbers of Avamar servers:...................................................................................................20
2.14 Finding the IPMI (or iDRAC or ILO) of Avamar node or setting:...........................................................................21
2.15 NSR PUSH:........................................................................................................................................................21
2.16 MMINFO:...........................................................................................................................................................24
2.17 Changing retention of savesets..........................................................................................................................27
2.18 Manually deleting savesets from NetWorker......................................................................................................27
2.19 Deleting backups from Avamar..........................................................................................................................28
2.20 Joining / Adding DataDomains to Active Directory.............................................................................................30
2.21 Resetting AD Authentication back to workgroup...............................................................................................30
2.22 Lotus Notes Restore Commands:.......................................................................................................................32
2.23 To Perform Image Level Recovery using Command Line (NW 8.2).....................................................................34
2.24 Mail Notification command in NetWorker:.........................................................................................................35
2.25 NSRPORTS and NSRRPCINFO:..........................................................................................................................35
2.26 NSRCLONE........................................................................................................................................................37
2.27 Command to make savesets browseable from recoverable:...............................................................................37
2.28 Command for throttling replication in DataDomain using override option:........................................................39
2.29 Start / Stop / Restart DPA services.....................................................................................................................40
2.30 Steps to be taken after rebooting the CloudBoost – Everytime..........................................................................40
2.31 Uploading the logs to DELL EMC FTP link (if the logs are very large and can’t be uploaded to SR......................40

3 Logs........................................................................................................................................41
3.1 Avamar / VBA logs directory:..............................................................................................................................41

4 General Troubleshooting:.........................................................................................................42
4.1 Error or Alerts: Waiting for 1 writable volume(s) to backup clone pool................................................................42

5 VBA Troubleshooting:..............................................................................................................43
5.1 Re-registering the ebr plugin through the Vsphere MOB page:..........................................................................43
5.2 Restarting the VMtools on the VBA:...................................................................................................................43
5.3 Error: Stopping an instance of NMM save with process Id=1208 on host: sql03.shbca.shb.bank. There is another
instance of NMM save program is already running.........................................................................................................43
5.4 Finding the version of different components within VBA:...................................................................................43
5.5 Cross synching NetWorker and VBA..................................................................................................................44

2
6 Some Linux commands.............................................................................................................47

3
Revision History
Revision Date Author Description

1.0 xx Siddhartha Patwardhan Base Document

1.1 xx Siddhartha Patwardhan Added few commands and updated Table of

content format

1.2 xx Siddhartha Patwardhan Added Logs, Troubleshooting sections and few

more commands

1.3 xx Siddhartha Patwardhan Updated few more commands.

1.4 xx Siddhartha Patwardhan Updated few more commands.

1.5 xx Siddhartha Patwardhan Updated few more commands.

4
 1 Introduction

This document will act as the command reference guide for the day to day backup operations task at xyz’s IT
services.

5
 2 Commands

2.1 Command to find list of VMs that are part of NetWorker VMware backup
policies:
Note: The output list would not necessarily be part of active backup policies. Hence another
check of active policies are required to ensure these VMs are actually getting backed up.
 Login to VBA as admin
SCREENSHOT DELETED
 admin@emc-vba:~/>: mccli client show --recursive
SCREENSHOT DELETED

2.2 Command to find the list of available backups of particular client in Avamar:
 Login to Avamar as “admin”
 mccli backup show --name=/vcentera.abc. /VirtualMachines/OMS --verbose

2.3 Command to restart NetWorker services on windows host (including NMC

services).
 Login to NetWorker server and launch command prompt.
 Go to <Installed path>\EMC NetWorker\nsr\bin>
To stop all the services:
D:\Program Files\EMC NetWorker\nsr\bin>net stop nsrexecd
If NMC is on the same server, stop the NMC services as well using the following command:
D:\Program Files\EMC NetWorker\nsr\bin>net stop gstd

To start all the services:

D:\Program Files\EMC NetWorker\nsr\bin>net start nsrexecd
D:\Program Files\EMC NetWorker\nsr\bin>net start nsrd
D:\Program Files\EMC NetWorker\nsr\bin>net start gstd

6
 2.4 Avamar model number and serial number:
admin@avamar01:~/>: avsysreport chassis-info
=== Chassis information
Host Name : xyz
Chassis Model : Gen4T M600
Serial Number : CKMxxxxxx
Part Number : 100-580-207-03-FFF
BIOS Version : 41.91
admin@avamar01:~/>:

2.5 Command to find a particular word in all or specific file in a folder:

 C:\Windows\System32>find /i "word to be searched" "D

:\Program Files\EMC NetWorker\nsr\res\nsrdb.backup\00\*.*" > output.txt
Searches all the files for the specific word provided.
 C:\Windows\System32>find /i "word to be searched" "D
:\Program Files\EMC NetWorker\nsr\res\nsrdb.backup\00\daemon.raw" > output.txt
Searches specific file for the specific word provided.
1. /v – This switch will show any lines that don’t contain the string of words you specified.

2. /c – This switch tells the find tool to count how many lines contain your search terms.

3. /n – This switch shows the numbers that correspond with the lines.

4. /i – This switch tells find to ignore the case of text you are searching for.

2.6 To view what process is using a TCP port in Windows Server

Windows administrators sometimes have to track down network traffic or errant processes and then match that to network traffic. Here are scripts that
will aid in the connectivity forensics at the port and process level.

You may find yourself frequently going to network tools to determine traffic patterns from one server to
another; Windows Server 2008 (and earlier versions of Windows Server) can allow you to get that information
locally on its connections. You can combine the netstat and tasklist commands to determine what process is
using a port on the Windows Server.

The following command will show what network traffic is in use at the port level:

Netstat -a -n -o > test.txt

The -o parameter will display the associated process identifier (PID) using the port. This command will
produce an output similar to what is in Figure A. Figure A
7
With the PIDs listed in the netstat output, you can follow up with the Windows Task Manager (taskmgr.exe)
or run a script with a specific PID that is using a port from the previous step. You can then use
the tasklist command with the specific PID that corresponds to a port in question. From the previous
example, ports 5800 and 5900 are used by PID 1812, so using the tasklist command will show you the process
using the ports. Figure B shows this query. Figure B

2.7 Curl commands (if telnet is not working on any system)

curl -kv 172.24.95.35:443
curl -kv 172.24.95.35:902

8
 2.8 Uploading the logs to DELL EMC FTP link (if the logs are very large and can’t be
uploaded to SR.
To upload large files (3+ GB) to send to EMC Support, below method worked fine for VPLEX CD logs.

1. Get FTP link - you will get username and password

2. ftp ftp.emc.com (give FTP username and password)
3. bin
4. hash
5. put <filename.tar.gz>

Refresh ftp link to verify if the upload size is increasing.

9
 3 Logs

3.1 Avamar / VBA logs directory:

root@emc-vba:/usr/local/avamar/var/log/#: cd ..
root@emc-vba:/usr/local/avamar/var/#: ls -ltr | grep -i log
-rw-r--r-- 1 root root 7242 Dec 10 2013 change_nodetype.log
-rw-r--r-- 1 root root 418157 Jul 13 2016 axionfs_2f46704b-9afc-4a7c-9a0d-ff6c0221d3c8.log
-rw-r--r-- 1 root root 354793 Jul 13 2016 axionfs_c5a500f8-4167-480c-aa69-62dd918677e1.log
-rw-r--r-- 1 root root 371713 Jul 13 2016 axionfs_89fe1f44-138b-43c0-b45d-e328254ac645.log
-rw-r--r-- 1 root root 281388 Sep 5 2016 axionfs_99b205ae-a64e-41b5-aea1-307b6422f1fc.log
-rw-r--r-- 1 root root 260204 Sep 7 2016 axionfs_a7ee57a9-2c5d-4c70-8b3b-ba8f6bbeb1b1.log
-rw-r--r-- 1 root root 437937 Nov 14 15:23 axionfs_9a2e0991-d966-4d6f-aef4-0513d180ed4c.log
-rw-r--r-- 1 root root 342316 Nov 14 17:05 axionfs_e1c5e353-ce9f-40e0-a9f6-d6346c2e10c6.log
-rw-r--r-- 1 root root 1714982 Nov 17 09:51 axionfs_8f328c3d-d6aa-4b92-b5bd-fc60222e3b03.log
-rw-r--r-- 1 root root 546888 Nov 17 10:07 axionfs_88cb787c-0a9e-4a13-860d-9ac1b7e434fa.log
-rw-r--r-- 1 root root 521258 Nov 17 10:28 axionfs_6b51ed99-6263-450b-a9c5-cbac8c010285.log
-rw-r--r-- 1 root root 1492537 Jan 31 10:30 axionfs_7b6d9187-de71-4530-971e-60b5ee99800c.log
-rw-r--r-- 1 root root 1465701 Jan 31 10:31 axionfs_cf40d046-8fd7-40c8-af93-0a9c62530c41.log
-rw-r--r-- 1 root root 1362718 Jan 31 10:32 axionfs_70d74786-4f06-4b5c-8ddb-b35058966938.log
-rw-r--r-- 1 root root 1314033 Jan 31 10:36 axionfs_c93f42f4-58cc-4e25-84f3-a26250628a51.log
-rw-r--r-- 1 root root 1239664 Jan 31 10:41 axionfs_09db7304-ad45-491b-9e9c-38fea6eb1a70.log
-rw-r--r-- 1 root root 1153969 Jan 31 12:03 axionfs_f8492cd2-aec8-40de-8c00-6a7f09da59d3.log
-rw-r--r-- 1 root root 1154092 Jan 31 12:04 axionfs_6158b74b-9d84-4c4b-95f1-0a0c6d84c9b3.log
-rw-r--r-- 1 root root 285448 Jan 31 12:06 axionfs_613345eb-fa7d-4b0f-ab64-1572df44eabf.log
-rw-r--r-- 1 root root 1272081 Jan 31 12:20 axionfs_e7d3e65f-9f73-41e3-bb6a-3f37a29b5a34.log
-rw-r--r-- 1 root root 1153986 Jan 31 12:36 axionfs_8a491779-dd30-4b46-81c7-7b615fbed5ac.log
-rw-r--r-- 1 root root 1171017 Jan 31 12:37 axionfs_e5034d39-45fc-43e9-9f05-cd9ce62d71b4.log
-rw-r--r-- 1 root root 1154079 Jan 31 15:28 axionfs_e179594f-09a7-4254-a356-9c11342ef535.log
drwxrwx--- 3 admin admin 4096 Feb 1 10:22 log
-rw-r--r-- 1 root root 466129 Feb 6 16:06 axionfs_4f79f2ff-9807-4e80-8731-7ca13f79e70f.log
-rw-r----- 1 root root 4095441 Mar 17 01:00 axionfs_3.log
-rw-r----- 1 root root 4095433 Mar 17 13:01 axionfs_4.log
-rw-r----- 1 root root 4095397 Mar 18 01:01 axionfs_5.log
-rw-r----- 1 root root 4095401 Mar 18 13:02 axionfs_6.log
-rw-r----- 1 root root 4095437 Mar 19 01:03 axionfs_7.log
-rw-r----- 1 root root 4095457 Mar 19 13:04 axionfs_8.log
-rw-r--r-- 1 root root 405765 Mar 19 15:34 axionfs_34f716c4-5e6b-456d-b5ff-0c405e91bd95.log
-rw-r--r-- 1 root root 411486 Mar 19 15:37 axionfs_cd65acbc-7637-4511-bdd6-e72481c309e6.log
-rw-r--r-- 1 root root 712091 Mar 19 15:54 axionfs_e42d196e-b07d-4548-833c-3180beaf7142.log
-rw-r--r-- 1 root root 374683 Mar 19 15:58 axionfs_45e91602-9ca9-4bb5-b509-9a20b00db79e.log
-rw-r--r-- 1 root root 2257721 Mar 19 17:31 axionfs_b9f9b3a3-997a-47fb-8459-6e5bb8be0511.log
-rw-r----- 1 root root 4095416 Mar 20 01:04 axionfs_9.log
-rw-r--r-- 1 root root 659941 Mar 20 09:31 axionfs_2505b98b-4a3e-454a-bc26-477f15e832e1.log
-rw-r--r-- 1 root root 19510 Mar 20 12:03 site_inventory.log
-rw-r----- 1 root root 4091539 Mar 20 13:06 axionfs_10.log
-rw-r----- 1 root root 4095328 Mar 21 01:07 axionfs_0.log
-rw-r----- 1 root root 4095372 Mar 21 13:08 axionfs_1.log
drwxrwxr-x 2 admin admin 4096 Mar 21 15:00 ddrmaintlogs
-rw-r----- 1 root root 4095316 Mar 22 01:09 axionfs_2.log
-rw-r----- 1 root root 2752750 Mar 22 09:11 axionfs.log

10
11
 4 General Troubleshooting:

4.1 Error or Alerts: Waiting for 1 writable volume(s) to backup clone pool
Resolution:

( 1 ) Go to each of the Client’s Properties that are part of the group asking for “1 writable media” during the backup or
clone and then go to “Recover storage nodes:” section of Globals (2 of 2) and update the destination Storage node.

( 2 ) Ensure target sessions on each of the devices of the particular volumes are same i.e

Please make them all Target sessions= 25 and Max sessions= 60 from devices settings (Configuration tab).

12
 5 VBA Troubleshooting:

5.1 Re-registering the ebr plugin through the Vsphere MOB page:
Unregister existing EBR Plugin:
(1) Login vCenter MOB by going to https://your-vcenter-hostname.domain.com/mob
(2) From the MOB screen click on content > ExtensionManager
(3) Under "Methods" click on "UnregisterExtension" and enter com.vmware.ebr2 in the second window that pops up.
Then click on "Invoke Method":
(4) Close the second window and refresh the MOB, the plugin should be gone.
(5) Double click on the Lock on the configure tab of ebr-configure page and provide the EBR password when prompted.
(6) Update the Vcenter password in the password field and Save.
(7) Update the Networker password in the Networker Configuration tab.
(8) Restart the emwebapp.sh on the VBA Putty.

The VBA will be re-registered to the Vsphere and the plugin will be added to the MOB extension manager.

5.2 Restarting the VMtools on the VBA:

service vmware-tools restart

13