bplist returns filenames with incorrect policy name

[sk1ds]

Hi,

I am experiencing a strange problem recently. We have a number of policies that backup Oracle databases.

The policies and backups are running and completing successfully, but when I run a bplist against a specific policy, it returns no results.

However, I can see the backup file (or oracle backup piece) that was backed up under one policy, showing up under a different policy name in the bplist output.

So, for example, the following bplist returns no entity found for the policy Oracle_dm01

$ /usr/openv/netbackup/bin/bplist -C db01 -k Oracle_dm01 -t 4 -R -s 07/27/2017 /
EXIT STATUS 227: no entity was found
$ /usr/openv/netbackup/bin/bplist -C db02 -k Oracle_dm01 -t 4 -R -s 07/27/2017 /
EXIT STATUS 227: no entity was found
$

 However, if I identify a particular backup piece and the Policy name from the Oracle RMAN output log as follows;

$ cat netbackup.out.170728_200019 | egrep 'NB_ORA_POLICY|nlsah0em_1_1'

NB_ORA_POLICY: Oracle_dm01
piece handle=nlsah0em_1_1 tag=TAG20170728T222942 comment=API Version 2.0,MMS Version 5.0.0.0

And then search for that backup piece with bplist, it shows up under a different policy (Oracle_dm01_CBM) which is a valid policy name, but does not backup this database

$  /usr/openv/netbackup/bin/bplist -C db01 -Listpolicy -t 4 -R -s 07/27/2017 / | grep nlsah0em_1_1
76283904 0 0 0 76283904 1 0 -1 -3 33204 oracle dba 76283904 1501245017 1501244983 1501244983 1501244983 2 32 Oracle_dm01_CBM 13 /nlsah0em_1_1 1 0 1
$

This is actually causing me a problem when trying to restore, becuase during the restore, it is searching for particular backup pieces against a particular policy but unable to match them becuase Netbackup thinks they are under a different policy.

Any ideas why this could be happening?

Thanks

Neil

[Marianne]

This has been a known issue for a long time. See: https://www.veritas.com/support/en_US/article.TECH31742

[sk1ds]

Thanks Marianne,

We must have been really lucky over the last couple of years then, becuase this has just worked without ever having to provide the Policy name.

I have made the necessary change to ensure the policy name is provided, and will monitor this over the remainder of the week.

I presume that the policy name is not required to be provided during restore?

Thanks

[Marianne]

The problem is only seen when a client appears in more than one policy with open window.
There is no need to specify policy name during restore.