New-RubrikHost - sets SLA assignment to Direct assignment

[SahFari]

Sometimes SLA assignment sets to Direct on a newly created database if we do a “Host-Refresh” using New-RubrikHost. This doesn’t always happen, sometimes, it does it correctly!

We assign SLAs on Host/Instance/AG level and assignment are often ‘Derived from MSSQLSERVER’ or Derived from some AG/or another SQL instance if we have another SQL instances.

Today, I created a database in my own name, Fari, on 2 servers.

Actually, I deleted that database from a lab server as a test (checking permissions in SQL Server). I restored the database from RSC and did an export of that database to another lab server.

Ran the command New-RubrikHost.

We have created a report job that sends us an email if a database is missing SLA och have a Direct SLA assignment.

I got the email that both these databases had Direct SLA assigned to them. I Cleared existing assignment for these databases, and when it was approved by QAuth Approver, the assignment was changed from Direct to ‘Derived from Fari’! The is no AG or instance called Fari!

Did another update certificate and a new host-refresh from RSC and assignment changed to ‘Derived from MSSQLSERVER’ in RSC. CDM showed it correctly ‘Derived from MSSQLSERVER’ after changes by QAuth Approver (QAuth Policy).

This isn't the first time New-RubrikHost has changed SLA assignment to direct.