Page tree
Skip to end of metadata
Go to start of metadata

Article State

Approved

Article Number

KB-20161216152303

Product

EMC Networker 8.x
SummarySteps to decommission a VBA Node

Language

EN

DE

Issue



Cause



Solution

STEP 1: Remove all save sets for the client-id for this VBA node.
STEP 1/PART 1: On NetWorker server we need to query the information for this particular VBA node so it can be deleted. You can either use NMC or command line to find all backups that need to be deleted.
STEP 1/PART 1/Option 1: To find all backups for a particular VBA node using NMC GUI:

A. Log in to NetWorker Management Console
B. Go to ‘Media’ tab and select ‘Save Sets’, then select ‘ VMware Backup Appliance Online ’ as shown below:

 

 

Note: Please do NOT select any VBA that you do NOT want to delete.
C. Then for the
 ‘Query Save Set’ tab, select only the required entries in VBA Name that you want to find the information for. Keep in mind that the goal is to query the information for this particular VBA node so it can be deleted. Below example shows that ‘vbalabnode2x.vba.lab’ was selected to be queried:

 


 

D. Now change the ‘Save Time From’ to select an approximate timeframe when VBA was initially deployed. Example below shows  the'From'value being changed to ‘June 2012’ and then selecting a date ‘1st’:

 


 

E. After selecting the appropriate query parameters, click the ‘Save Set List’ tab. Here view the output to ensure that all data Save sets in this output belong to the VBA you intend to delete. Example below shows the VBA ‘vbalabnode2x.vba.lab’ data being displayed:

 


STEP 1/PART 1/Option 2To find all backups for a particular VBA node using CLI on NetWorker server use mminfo as shown here:  
Syntax: mminfo -c <vba-name> -kot

For Example: To find all backups for VBA named 'vbalabnode2x.vba.lab' run query:
 

mminfo -c vbalabnode2x.vba.lab –kot
Output:

 volume        type   vm_name         date     time         size ssid      fl backup_size
dd2x15.001  Data Domain VM2      6/22/2015 7:49:57 AM   41 GB xxxxx cr  41 GB
dd2x15.001  Data Domain VM1      6/22/2015 7:53:52 AM   41 GB xxxxxx cr  41 GB
dd2x15.001  Data Domain VM2      6/22/2015 7:54:02 AM   41 GB xxxxxx cr  41 GB
 

STEP 1/PART 2: Once the required SSID have been identified to delete, you can now use either of the options to purge the data.
Note: If your system shows no backups for the VBA, skip this part
STEP 1/PART 2/Option 1: If the VBA is online and if there is a unique volume where all the SSIDs are stored, i.e. there is no other data on this volume- you can delete this volume
STEP 1/PART 2/Option 2: If the VBA is online and if there is no unique volume that contains all the SSID, then you can use nsrmm command to delete the individual Save set. Syntax:  nsrmm -d -S <SSID>
For Example: Below example shows command to delete

nsrmm -d -S xxxxxxxx
Delete file and media index entries for save set `4253582084'? y
98999:nsrmm: Save set 4253582084 has been successfully deleted from VBA server 'vbalabnode2x.vba.lab'
Note: The above command deletes one saveset at a time. Please take extreme caution to ensure you delete only the save sets that belong to the VBA you intend to delete 
STEP 1/PART 2/Option 3: If the VBA is NOT online, then use the ‘-X’ option to delete the Save set:
nsrmm -X -d -S <SSID>

Note: The ‘-X’ flag is available through support cumulative release 8.2.1.6 or newer. Please update the NetWorker server to 8.2.1.6 or newer to avail this fix
For Example: nsrmm -X -d -S 4237053710
Delete file and media index entries for save set `4237053710'? y

STEP 2Remove all workflows associated with the VBA:

A. Login to NMC
B. Go to Configuration tab and click ‘VMware Protection Policies’
C. Sort the policies by ‘VBA List’
D. Open the first policy that has this VBA listed, go to ‘VMware Backup Appliance Selection’ tab and uncheck the VBA name.

E. Wait for the ‘State’  column to change to ‘Success’
F. [Optional] If you no longer need to back up a particular vCenter server. Log in to nsradmin and delete ‘nsr hypervisor’ as per below instructions:
On the NetWorker server, open a shell and type ‘nsradmin –p nsrd’ to get to the prompt
nsradmin> p type: nsr hypervisor; name: <vcenter-name>
For Example: Below is the example of delete a reference to vCenter named ‘VC4.vba.lab’
 

nsradmin> p type: nsr hypervisor; name: VC4.vba.lab’
type: NSR hypervisor
name: VC4.vba.lab;
comment: ;
service: VMware VirtualCenter;
endpoint: "https://VC4.vba.lab/sdk";
username: administrator@vba.lab;
password: *******;
command: nsrvim;
proxy: nw4;
nsradmin> d
Delete ? yes

Note: This step may need to be done using offline nsradmin if VBA is NOT responding

STEP 3: Delete VBA MTree:

A. On the NetWorker server, run the below nsradmin commands to find the VBA DPN ID:
nsradmin> show name
nsradmin> show DPN ID
nsradmin> p type: nsr vba server; name: <VBA-FQDN>
Example output:
 nsradmin
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> show name
nsradmin> show DPN ID
nsradmin> p type: nsr vba server; name: vbalabnode2x.vba.lab
                        name: vbalabnode2x.vba.lab;
                      DPN ID: xxxxxxxxxxx;
Make note of the DPN ID. This will help us determine the storage unit, for example, for the above DPNID, the storage unit will be 'avamar-1435099427'
B. Log in to Data domain system using PuTTY(or similar SSH utility) as a user with 'admin' role. Then run below command to delete:
ddboost storage-unit delete <storage-unit>
Example: ddboost storage-unit delete avamar-1435099427
C. [Optional] Start a filesystem clean on data domain to reclaim space:
filesys clean start

STEP 4: Remove VBA server resource using nsradmin:
Note: This step is to be performed ONLY for the VBA you wish to delete. Please take caution to make copy the nsrdb, if this has not been done already.
Syntax: nsradmin> d type: NSR VBA Server;  name: vbalabnode2x.vba.lab
For Example: Below example shows command to delete a VBA called ‘vbalabnode2x.vba.lab’
nsradmin> d type: NSR VBA Server;  name: vbalabnode2x.vba.lab

type: NSR VBA Server;
name: vbalabnode2x.vba.lab;
comment: ;
vCenter Host: vbalabnode2x.vba.lab;
 vCenter Web Client Host: ;
 Total Capacity: ;
 Total Capacity in bytes: ;
 Used Capacity: ;
Last Validated Checkpoint: ;
 Last Validated Checkpoint Tag: ;
Online: ;
VBA Version: ;
Policy List: ;
Policy Client Mapping: ;
External Proxy Hosts: ;
VBA recover checkpoint tag: ;
configuration error: ;
VBA Internal Proxies: Enabled;
VBA Adhoc Backups: Enabled;
VBA Restrict Transport Mode to Hotadd Only: Disabled;
Staging DDR pool for Disaster recovery from non-DDR devices: ;
Delete? Y
deleted resource id 156.x.xxx.x.x.x.x.x.xxx.xxx.xxx.xx.xx.xxx.x.x(7)

Note: This step may need to be done using offline nsradmin if VBA is NOT responding

STEP 5Remove client resource for that VBA from NMC
Syntax:  nsradmin> d type: nsr client; name : vbalabnode2x.vba.lab
For Example: Below example shows how to delete client for ‘vbalabnode2x.vba.lab’
 

nsradmin> d type: nsr client; name : vbalabnode2x.vba.lab
type: NSR client;
name: vbalabnode2x.vba.lab;
server: nw4.vba.lab;
client id: xxxx-xxxxx-xxxxx-xxxx-0xxxxx-xxxxx;
Delete? Y
deleted resource id 153.x.xxx.x.x.x.x.x.xxx.xx.xxx.xx.xx.xxx.x.x3)


STEP 6: Delete the VBA Appliance:
You can now delete the relevant VBA node VM from the vCenter server.

STEP 7: If the External proxy is no longer needed- delete the external proxy virtual machine


Workaround

Notes

Note: It is highly recommended to do the following steps to backup your nsrdb and mm directory before following this procedure:

1. Log on to NetWorker server and open the following directory <networker-install>\nsr

2. Make a copy of the following directories: res\nsrdb AND mm





Attachments


Change