- It's out of order
- has been released
Have the same issue in my development environment. What OS is you media server(s)? I ask because support will tell you that if you use Oracle Linux, that OS is not supported even in 8.2, I believe they say it stopped being supported in 8.1.2. Which I don't understand because HPE lists the plugin as supported for NetBackup 8.2 with Oracle Linux and says 8.3 should be supported since it's listed as a minor release.
Forgot to mention, the HPE StoreOnce Catalyst Plugin that I have is 4.2.2.
@Marianne when you run /usr/openv/netbackup/bin/admincmd/bpstsinfo -pi
The HPE StoreOnce Catalyst Plug-in is no longer listed.
You can uninstall the plugin then reinstall but it doesn't fix the issue. If you try to repair the plugin, you get the message that it's already installed.
One or more newer versions of the product are already installed.
An upgrade is not applicable in this case.
EDIT: This is what I have found out from my contact.
The issue is that HPE’s OST plug-ins don’t work with NetBackup 8.3. The OST API version bumped to v12 in NB 8.3. The plug-in detects the version, says is isn’t supported and doesn’t load. NetBackup has flagged this issue to HPE.
I has two media servers with Oracle Linux 6.10, NetBackup 8.2 and HPE OST Catalyst Plug-in for Veritas NetBackup 4.2.2 and it works fine. Master Server is NetBackup 8.3 on RHEL 7.7 with Plug-in 4.2.2 and does not see the HPE StoreOnce 5100.
Until HPE releases a new version of the HPE OST Plugin, it will not work with NetBackup 8.3.
Here is the info from the plugin.log file.
2020-08-04 13:46:07.543485 (local 09:46) : ERROR : 12610_2521563008 : -1 : - : Global : stspi_init : Ln 331 : OST API version 12 NOT SUPPORTED
I was also told that Oracle Linux is supported for 8.2 and that the HCL will be updated.
Veritas development is following up with HP. It's a problem with the implemention of a version check on the HP plugin side. A version check shoudn't be needed as OST is backwards compatible. The plugin only needs to identify as V11 and the NBU side will understand how to route the operations.
The issue regarding disk pool size's being shown wrong is a known issue with NetBackup 8.1.2 and 8.2 when you are using the older plugin (not 4.2.2). If you can't upgrade the OST plugin, in the mean time open your StoreOnce Catalyst Stores page in the HPE StoreOnce Web GUI. Then go to the Catalyst store that is displaying wrong in NetBackup and change the "Physical Data Size Quota" from "No Limit" to a value which disk is showing on HP StoreOnce. Otherwise, just upgrade the OST plugin if you're running NetBackup 8.1.2 or 8.2 and not HPE OST Plugin 4.2.2
If you are using NetBackup 8.1.2 or 8.2 and are not using the HPE OST Plugin version 4.2.2 and the disk pools are not showing the correct size in NetBackup.
Open the HPE StoreOnce Web GUI and login.
Click "StoreOnce" on the left hand size to expand the menu.
Click "StoreOnce Catalyst" on the left hand size to expand the menu.
Click "Stores" on the left and side.
Select the store that you want to view/edit.
You'll see something like this.
|Data Job Log Retention Period (Days)||
|Inbound Copy Job Log Retention Period (Days)||
|Outbound Copy Job Log Retention Period (Days)||
|Primary (Default) Transfer Policy||
|Secondary Transfer Policy||
|Physical Data Size Quota||
|Logical Data Size Quota||
|Store Encryption Enabled||
Change the "Phyiscal Data Size Quota" from "No Limit" to the usable disk size on that HPE StoreOnce Appliance.
Refresh/Update the disk pool in NetBackup, it will now show the correct size.
Otherwise just upgrade the plugin to 4.2.2 and it will resolve the issue. If you do make these changes and then upgrade, remember to change the "Physical Data Size Quota" back to "No Limit".
This is not a fix to get the HPE OST Plugin to work with NetBackup 8.3, that is currently not an option with the current plugin that HPE has released to the public.
6 months away from the new HPE Catalyst Plugin being released.
However, Veritas has informed me of the following.
From our Engineering team:
Yes, but there’s good news.
Yes, it does look like a new HPE Catalyst plug-in is a few months away. (It’s probably more like three months than six.)
However, customers aren’t going to have to wait that long. The OST developers are putting a fix into 18.104.22.168 so plug-ins built with earlier API versions will load and run with the new v12 API introduced in NB 8.3.
As such, they should have a working plug-in again in a few weeks when 22.214.171.124 is available.
Looks like we’ll have one in a few weeks!