Forum Discussion

Krutons's avatar
Krutons
Moderator
4 years ago

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 ...
  • Krutons's avatar
    Krutons
    4 years ago

    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. 

davidmoline's avatar
davidmoline
Level 6

Hi Krutons 

I'm not going to be able to help with the API return, but the key difference bewteen an Oracle policy and a local file system backup is where and how the backup data stream is called. 

For a local file system backup the client name is contained in the policy and the backup is initiated from the master server. The backup image details will list this client name aagainst the backupid.

For the Oracle policy, the backup stream is initiated by the client and may be using the default client name. When this backup starts and communicates to the master, although it may be using the wrong client name (non-backup n/w name) the aliases you have mapped allow the backup to run aginst the OIP policy. 

What does the activity monitor show for the client name for each backup type. This may also be reflected in a bpimagelist output of the backupid for each type. 

Using the old RMAN scripts it was possible to set the client name using NB_ORA_CLIENT variable but I'm not sure this can be done using OIP or if it can how to do this.

Cheers
David

Krutons's avatar
Krutons
Moderator
4 years ago

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.