01-31-2018 03:45 AM - edited 01-31-2018 03:57 AM
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.
Solved! Go to Solution.
01-31-2018 03:47 AM
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:
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
01-31-2018 03:47 AM
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:
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