NSS manual indicate that a machine cannot combine a VMware protection and a Standard/MSWindows/DB.
Our Client will have 80% of VM with the need to protect the inside DB as well, so they wonder how to address this use case.
The reason why is that NSS can only hold one NetBackup client name which is different between VMware (VM display name) and non VMware client based policies (DNS name).
There are two workarounds depending on their requirements:
- The work around is to register a machine twice, one for each scenario as per our example below (for CLWINSQL2012)
2: You can use VMware to protect MS SQL Server, you can select options in the policy.
This has already been captured as a requirement for a future release so is on the roadmap, but not yet scheduled
