Reporting on client versions

[Ed_Wilts]

In a multi-platform, multi-version environment, it is sometimes tough to keep track of who is running what version, or what physical servers hosts the virtual server.  We've put together a script that we run weekly that spits out CSV file with data captured from every client.  Here's a sample entry:
z11i.bck.mrll.com,borodin.bck.mrll.com,6.5.4,HP-UX,B.11.11,HP9000-800,
This shows that we have a virtual server that we back up named z11i.bck.mrll.com residing on physical server (technically the client name configured on the host) named borodin, running 6.5.4.  We add the OS and hardware.

Given this, we can see things like this:
[root@osiris local]# wc -l client-versions.csv
     639 client-versions.csv

Of these 639 NetBackup clients, we can see that we have 557 unique physical servers:
[root@osiris local]# awk -F, '{print $2}' client-versions.csv | sort -u | wc -l
     557

Of the client names, 330 are running some variant of Windows and 241 are Linux:
[root@osiris local]# grep ,Windows client-versions.csv | wc -l
     330
[root@osiris local]# grep ,Linux client-versions.csv | wc -l
     241

We want everybody ideally at 6.5.4 (where our master is), but only 397 out of 557 are there today:
[root@osiris local]# grep ,6.5.4, client-versions.csv | wc -l
     397

We still have a dozen back on ancient releases:
[root@osiris local]# grep ,6.0MP client-versions.csv | wc -l
      12

How many diferent names do we use to back up borodin:
[root@osiris local]# grep borodin.bck.mrll.com client-versions.csv | wc -l
       8
so we know we need 1 license, not 8 client licenses.

These are the types of things that help you quickly report on wht your environment looks like.   The script takes a LONG time to run because it has to talk to every client name to get the information.

It requires a shell script and awk.