NetBackup API 8.3.0.1 License Capacity Client Details
Not sure if anyone will be able to give me some insight on how this works but worth a try.
I'm writing a powershell script to curl the license capacity client details for a list of clients that are using specific storage. The clients are DB hosts that are backed up with an OIP policy and a local file system backup plus some specific VM's. I'm seeing weird behavior when looking at a few of the DB hosts. For example, one of the client is the following (I've edited the names of clients/policies/servers for obvious reasons.
[root@master admincmd]# ./bppllist -L -byclient <client name backup network> | grep <beginning of policy name>_
Policy Name: <oip policy>
Policy Name: <local file system policy>
So this is expected because that is the client name that is used for both backups. I know this client has multiple mapped names such as the following.
<client name non backup network>
<ip>
<VIP DB FQDN>
<VIP DB backup network>
<client name backup network>
However, the output from the curl I get is the following.
Using the <client name backup network>
[
{
"clientName": "<client name backup network>",
"clientConsumptionMB": 0
"policyDetails": [
{
"backupId": "backupid",
"policyName": "<local file system backup>",
"masterServer": "<master>",
"policyType": "Standard",
"policyConsumptionMB": 0
},
{
"backupId": "backupid",
"policyName": "<local file system backup>",
"masterServer": "<master>",
"policyType": "Standard",
"policyConsumptionMB": 0
}
]
}
]
Using the <client name non backup network>
[
{
"clientName": "<client name non backup network",
"clientConsumptionMB": 0,
"policyDetails": [
{
"backupId": "backupid",
"policyName": "<oip backup>",
"masterServer": "<master>",
"policyType": "Oracle",
"policyConsumptionMB": 0
},
{
"backupId": "backupid",
"policyName": "<oip backup>",
"masterServer": ">master>",
"policyType": "Oracle",
"policyConsumptionMB": 0
}
]
}
]
Why does the client name not using the backup network return the OIP backups?
Hello davidmoline
Both policies are using the client with the backup network name. The DB is registered using the client with backup network name. It looks like the OIP policies might be going off of the client name in the bp.conf so the client name the DB is registered with is irrelevant in the eyes of the curl return for license capacity client details for OIP policies.