01-06-2017 08:15 AM - edited 01-06-2017 08:57 AM
01-06-2017 08:55 AM
NSS uses VIP policies to protect VMWare infrastructure. This applies to both vCenter and vCloud environments.
For vCloud environments, VIP policies are the only option, for vCenter ones, non-VIP policies can be used but NSS uses VIP only.
NSS portal uses VIP policies for VMWare. For other policies e.g. windows or standard, there is no concept of intelligence so machines are just added as clients to policies.
NetBackup has other policy types that have an intelligent version (SQL Server, Oracle, HyperV) but NSS does not support them
NSS supports the script based version of the above policies.
01-06-2017 08:55 AM
NSS uses VIP policies to protect VMWare infrastructure. This applies to both vCenter and vCloud environments.
For vCloud environments, VIP policies are the only option, for vCenter ones, non-VIP policies can be used but NSS uses VIP only.
NSS portal uses VIP policies for VMWare. For other policies e.g. windows or standard, there is no concept of intelligence so machines are just added as clients to policies.
NetBackup has other policy types that have an intelligent version (SQL Server, Oracle, HyperV) but NSS does not support them
NSS supports the script based version of the above policies.
03-12-2018 09:14 AM
Greetings Jon!
Are there any changes regarding MSSQL/Oracle VIP integration with NSS?
Do you have these enhancements planned in future roadmaps?
03-12-2018 09:24 AM
No, there aren't any changes regarding MSSQL/Oracle VIP policies on the roadmap at the moment.
Unless the NBU API introduces support, there is no way to do it based on existing interfaces.
FYI , some customers have been doing some clever stuff with the Script based polices like deploying the script (via Powershell) when the request to backup the database is invoked, although restore is still a manual process.
03-12-2018 09:34 AM - edited 03-12-2018 10:05 AM
With the release of NBU 8.1.1 we have started to publish our API's. I'm working with the NSS development team to start to introduce those API's into NSS, which will help the product become more efficient as there will be less load on NBU itself.
In the next release, we've already done some work around Oracle. I'm not so sure about SQLserver, as the API's start to appear there. Having said that, it may not be enough for NSS.
Similarly, the NSS team have the ability to input into the API release schedule so they can identify gaps, or functionality that they need.
Siobhan Ellis
Product Manager for Service Provider Product Strategy, NSS and NetBackup Reporting.