Discovery of Backup Clients which are not configured for backup

[vikas19]

Hi All

Is there anyways to auto discover clients which are not configured for backup.For ex I am using Syamntec Netbackup to backup all the clients in my organization and it happens that a new client(a new server) was added to Data Center and it was not informed to Backup team and therefore its backup was not configured.

So is there any feature available in any backup or 3rd party software to auto discover clients which are not configured for backup

or a case where there was a new Filesystem created and it was not schedule to be backup although other Filesystem backup is taken for the client.Is there any way to discover such missing info from the backup software?

Regards Vikas

[RamNagalla · Accepted solution]

if your enviornmnet and new servers are adding as VM guests..

and also if you are making backups through VMware policy type with query builder... netbackup can auto discover the VMs and make the backups 

if the servers are physical , i dont think there is a way in netbackup to identify ..

and i believe its the responsiblity of the server/app owner to decide and let backup team to about the data protection of the new server.

i would suggest you to ...talk with your managemet and help them to Define a Process to check and test all prerequisites before server going live/Production.

that is how most of them do.... only Defined Process will help you in this case...

[mph999]

bpcoverage -c <client name>

Try that command and see if the information returned is useful

Eg

             UNCOVERED - Mount Point not covered by an active policy

             MULTIPLE  - Mount Point covered by multiple active policies

CLIENT: womble

   Mount Point           Device                Backed Up By Policy   Notes

   -----------           ------                -------------------   -----

   /                     /dev/dsk/c1t0d0s0                           UNCOVERED

   /devices              /devices                                    UNCOVERED

   /disk3p0              /dev/dsk/c1t2d0s0                           UNCOVERED

   /disk3p1              /dev/dsk/c1t2d0s1                           UNCOVERED

   /disk3p3              /dev/dsk/c1t2d0s3                           UNCOVERED

   /disk3p4              /dev/dsk/c1t2d0s4                           UNCOVERED

   /etc/dfs/sharetab     sharefs                                     UNCOVERED

   /etc/mnttab           mnttab                                      UNCOVERED

   /export/home          /dev/dsk/c1t0d0s7                           UNCOVERED

   /netbackup            /dev/dsk/c1t1d0s1                           UNCOVERED

   /sp1                  /dev/dsk/c1t0d0s3                           UNCOVERED

   /sp2                  /dev/dsk/c1t0d0s4                           UNCOVERED

   /sp3                  /dev/dsk/c1t0d0s6                           UNCOVERED

   /srt                  /dev/dsk/c1t0d0s5                           UNCOVERED

   /system/contract      ctfs                                        UNCOVERED

   /system/object        objfs                                       UNCOVERED

[Anonymous]

Alternatively this could be a bit intense, you could run a port scan on the bpcd service port (13872) on your IP ranges to auto-discover hosts that DON'T have netbackup installed/active.

So something like nmap or windows based Softperfect Network scanner (free - excellent tool BTW and portable!)

And those that come back with port open and would presume are netbackup clients, could also be admin consoles. But you can eliminate those and highlight the remaining candidates as new NB clients.

Assuming these are physical servers.

If VMware virtual hosts then should use the NetBackup VMware Intelligent Policy method to discover those not backed up.

[Marianne]

bpcoverage will work for clients with NBU installed and policies configured.

I agree with Nagalla - there has to be written instructions to server managers to notify backup team of new servers. All about 'policies and procedures'....

If I'm not mistaken, OpsCenter Analytics has a report where a server list can be used as input and then checked against policies to produce a report. Still no 'go out and discover' feature.

[vikas19]

If I am not wrong, there is feature in EMC Data Protection Analyzer to auto discover any client which is not configured for backup.Not sure if it checks only for EMC networker clients on server which are not configured for backup

Ideally yes, Server team should notify backup team but in very big organization where there are small sites whose backups are not managed centrally there could be situation where the process is not followed.

[Marianne]

We can unfortunately not comment on EMC DPA....

Written instructions in a large organization means that a server owner accepts full responsibility for getting his/her server added to the backup system.

[mph999]

With bpcoverage command could it not be used  ?

Feed it a list of clients, if some don't return any info, they are not configured ....  or am I missing something.

M

[Anonymous]

In the case of your query
or a case where there was a new Filesystem created and it was not schedule to be backup although other Filesystem backup is taken for the client.Is there any way to discover such missing info from the backup software?

This would of course fall into the remit of clients in a policy that DID NOT have ALL_LOCAL_DRIVES specified in the selection - at the least.

But Martin's recommendation of bpcoverage is best way, but then when you have loads of servers you want a way to automate...

There is (on UNIX/LINUX) the check_coverage script in /usr/openv/netbackup/bin/goodies

You can input a list of hosts to check for coverage - see the header below

#!/bin/sh
# $Header: check_coverage.sh,v 1.11 2010/07/30 21:10:28 $
#******************************************************************************
# $Copyright: Copyright 1993 - 2011 Symantec Corporation, All Rights Reserved $
#******************************************************************************
#
# check_coverage [-coverage] [-hardware] [-hosts [local_hosts_file]] [-client ] [-mailid ]
#
# This script can produce three reports which gather various types of
# information about the clients being backed up by the server.  The reports
# are:
#        File System Backup Coverage Report
#        Policy Hardware/OS Report
#        Hosts Report
#
# By default all three reports are generated.
#
# The File System Backup Coverage Report detects file systems that are not
# backed up by any policy and file systems that are backed up by more than
# 1 policy.  Currently, this report is supported for UNIX, Windows
# NT/2000/XP/NET/2003/95/98/Me, and PC-IA64 Windows XP/NET/2003 clients.
#
# The Policy Hardware/OS Report displays Hardware and Operating System for
# clients.
#
# The Hosts Report indicates which hosts are in a NetBackup policy on the
# server.  By default, 'ypcat hosts' is used to get a hosts list, however
# a hosts file (e.g., /etc/hosts) can be specified.
#
# To specify a specific report use the -coverage, -hardware, or -hosts options.
# The -client option can be used to generate a report for a specific client.
# Note that the -client option only applies to the coverage and hardware
# reports.  The -mailid option can be used to mail the reports to a specific
# user.
#
# This script may be used in a crontab entry to have the reports generated and
# mailed to you once per day.
#
# caveat:
#   -not tried on all platforms, some may require modifications.