cancel
Showing results for 
Search instead for 
Did you mean: 

NSS manual indicate that a machine cannot combine a VMware protection and a Standard/MSWindows/DB.

TraceyBunyard
Level 5
Employee

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.

1 ACCEPTED SOLUTION

Accepted Solutions

TraceyBunyard
Level 5
Employee

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:

  1. The work around is to register a machine twice, one for each scenario as per our example below (for CLWINSQL2012)

VOX  cumulate a VMware.png

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

View solution in original post

1 REPLY 1

TraceyBunyard
Level 5
Employee

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:

  1. The work around is to register a machine twice, one for each scenario as per our example below (for CLWINSQL2012)

VOX  cumulate a VMware.png

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