Bug in bppllist -byclient ?
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
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?