cancel
Showing results for 
Search instead for 
Did you mean: 

Bug in bppllist -byclient ?

LT2013
Level 4

Wrote a script to remediate backup clients in multiple NB policies (running 7.5.0.6 on RH Linux servers).

So I use the bppllist command with the -byclient option to get all the policies for each client:

bppllist -byclient hostname | grep ^CLASS | awk '{ print $2 }'

What I discovered is that if I have 2 clients named as follows: zhostname and hostname, the bppllisting for hostname will include the policies for zhostname (we use a 'z' prefix to designate a solaris zone). Below is non-filtered output of the command..

# bppllist -byclient dbpnyu14 -U | more
------------------------------------------------------------

Policy Name:       UNIX-BK

  Policy Type:         Standard
  Active:              yes
  Effective date:      05/26/2004 00:00:00
  Client Compress:     no
  Follow NFS Mounts:   no
  Cross Mount Points:  no
  Collect TIR info:    no
  Block Incremental:   no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          yes
       Interval:       15
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           (specific storage unit not required)
  Volume Pool:         UNIX
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      0 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Solaris       Solaris8      zbcsprd5
                 Solaris       Solaris10     zdbpnyu14
                 Solaris       Solaris8      zappnyu35
                 Solaris       Solaris8      zappnyu27
                 Solaris       Solaris10     appnyu100

  Include:  ALL_LOCAL_DRIVES

 

1 ACCEPTED SOLUTION

Accepted Solutions

mnolan
Level 6
Employee Accredited Certified

Was testing this, cannot replicate.  Have some other ideas regarding aliases once my lab comes back up later today.  Did you do anything regarding client aliases before adding the name to a policy?

View solution in original post

5 REPLIES 5

SymTerry
Level 6
Employee Accredited

What NetBackup version are you running? It looks like it sees the dbpnyu14 in zdbpnyu14 like a grep would when searing policies.

Off hand I dont see any etracks for bugs on this. If this is a new bug and your on a current version of netbackup, please open a case to log and track it.

 

mnolan
Level 6
Employee Accredited Certified

Will test in house with 7.5.0.6 and RH master.

mnolan
Level 6
Employee Accredited Certified

Was testing this, cannot replicate.  Have some other ideas regarding aliases once my lab comes back up later today.  Did you do anything regarding client aliases before adding the name to a policy?

LT2013
Level 4

Spoke to a Sym Engineer and he pointed me in the alias direction, and sure enough, that was the issue.

The hostnames were in different policies. In speaking with some more tenured folks here, there was a P2V initiative a while ago, moving physical solaris servers to zones, and they simply added the "z" prefix to the physical server hostname...and aliased it. The NB admin added the "z" host to a new policy and never removed the old physical server hostname from another policy.

mnolan
Level 6
Employee Accredited Certified

Good to know, I'll skip the testing. Thank you for posting what the resolution was.