How to completely remove a NetWorker client
I've worked on too many customer sites where clients have been removed incorrectly on the command-line, or even via the console interface, but associated client file index has remained;
Whilst NMC is a good quick tool to adding and removing clients, it's not the most reliable tool when it comes to cleaning up; nsradmin and the command-line have always been my friend.
I created this post as a quick how to guide to removing a backup client under NetWorker in it's entirety (lock, stock and barrel).
A word of caution, before you begin to remove a client, make sure you have a recent/valid bootstrap backup; If we make any mistakes down the line we can easily recover.
Client Side (optional)
If the client no longer has a requirement to be backed up by the NetWorker server, we can perform one or all of the following:
- Simply stop the NetWorker daemons/services on the client, or
- Alternatively remove the package/binaries from the client. There's no problem with leaving the client software installed and running, it'll just sit there doing nothing until it gets a request from a backup server.
NOTE: You can't just stop the daemons/services on the client and think that's it; you need to disable the client in the save groups, and/or remove the configuration on the server.
The actions needed on the server side requires a little more thought it's a little more trickier, but in a nutshell the following steps are required:
- Delete all savesets for the client
# for SSID in `mminfo -av -r 'ssid(53)' -c <client>` do echo $SSID nsrim -d -y -S $SSID done
- Delete the client file index
# nsrck -YR <client> # rm -r /nsr/index/<client>
- Remove client entries from the media database
# nsrim -c <client> -X
- Remove the client resources from the backup server
# echo "delete type: NSR client; name: <client>;" | \ nsradmin -i -
- remove client entries from the software repository [added 28/07/2007]
# echo "delete type: NSR Installed Software; name: <client>;" | \ nsradmin -d /nsr/res/cpdb -i -
As a seasoned backup administrator and implementer I've had to run through the above a good few hundred times. To save time I cobbled the above together in a script, and added some sanity checks into the process; It's that simple.
Here's a sample of the output from my script:
# ./remove-networker-client.ksh ================================================================================ remove-networker-client.ksh (1.0.4) This script removes a CLIENT from the Backup Server by performing the following: 1. Deletes all savesets for a given client 2. Deletes the client file index 3. Removes all references in the media database for the client 4. Removes client configuration and resources from the backup server 5. Removes client entries from the backup software repository *** USE WITH CAUTION *** USE WITH CAUTION *** USE WITH CAUTION *** *** USE WITH CAUTION *** USE WITH CAUTION *** USE WITH CAUTION *** -------------------------------------------------------------------------------- Which client do you want to delete? alpha99 Do you want to delete client "alpha99" [y/n]? y Deleting client "alpha99" will also delete all it's savesets, are you sure [y/n]? y -------------------------------------------------------------------------------- removing client "alpha09"... Deleting savesets... f8730817-00000006-9d2c836e-532c836e-3766000b-5de57b88 2de04daf-00000006-b76d12c4-536d12c4-014a000b-5de57b88 080e4dcd-00000006-c9765092-53765092-0e38000b-5de57b88 : : 8cc9e19a-00000006-ba6d128a-536d128a-0147000b-5de57b88 f2850a76-00000006-e1764f86-53764f86-0e20000b-5de57b88 Deleting client file index... 9503:nsrck: WARNING: -R will completely remove the following file indices: alpha99 If it was not your intent to completely remove the above client file indices, kill this command now. You have 6 seconds. If it was not your intent to completely remove the above client file indices, kill this command now. You have 4 seconds. If it was not your intent to completely remove the above client file indices, kill this command now. You have 2 seconds. Pruning Media Database... 86069:nsrim: Processing 1 clients 86068:nsrim: Managing 308 volumes. Avamar: 1642 GB used, 4206 save sets, appendable, 4165 browsable save sets, 41 recoverable save sets schlumpf05.005: 0 KB used, 0 save sets, appendable (manual recyclable) schlumpf05.VDrive.001: 266 TB used, 1717 save sets, appendable, 1712 browsable save sets, 5 recoverable save sets : : CI4027: 394 GB used, 352 save sets, full, 7 recoverable save sets, 345 recyclable save sets CI4028: 374 GB used, 124 save sets, full, 104 browsable save sets, 20 recoverable save sets 86073:nsrim: Compressing media database. Deleting client... deleted resource id 220.127.116.11.0.0.0.0.0.0.0.0.18.104.22.168.22.214.171.124(16) deleted resource id 126.96.36.199.0.0.0.0.0.0.0.0.188.8.131.52.184.108.40.206(14) Removing client from software repository... deleted resource id 0.35.81.31.0.0.0.0.0.0.0.0.220.127.116.11.172.20.176.28(2) deleted resource id 0.215.14.228.0.0.0.0.0.0.0.0.18.104.22.168.172.20.176.28(3) deleted resource id 0.34.81.31.0.0.0.0.0.0.0.0.22.214.171.124.172.20.176.28(2) ================================================================================
You can download a copy of my script, here