Version_1.14.20260105

Version 1.14.20260105

Schema Update:

See API Changelog
for API additions, deprecations and breaking changes.

Version_1.14.20251215

Version 1.14.20251215

Schema Update:

See API Changelog
for API additions, deprecations and breaking changes.

Version_1.14.20251208

Version 1.14.20251208

Schema Update:

See API Changelog
for API additions, deprecations and breaking changes.

Version_1.14.20251109

Version 1.14.20251109

Schema Update:

See API Changelog
for API additions, deprecations and breaking changes.

Version_1.14.0

Version 1.14.0

Schema Update:

See API Changelog
for API additions, deprecations and breaking changes.

New Features:

• Get-RscMssqlAvailabilityGroup : updated cmdlet to include cluster fields,
  added -Relic and -Replica filters.

Fixes:

• Fix GraphQLClient.cs Exception Handling
  PR

Version_1.13.1

Version 1.13.1

Schema Update:

See API Changelog
for API additions, deprecations and breaking changes.

Version_1.13.0

Version 1.13.0

New Features:

Multi-DC MSSQL database management

Manage the protection for these multi-DC replicas as a single linked group. Two new cmdlets have been introduced for this:

Get-RscMssqlLinkedAvailabilityGroup - This cmdlet will show the linked status for any replica availability groups across multiple Rubrik clusters.

Protect-RscLinkedWorkload - This cmdlet manages linking replica availability groups or databases and SLA assignment for the linked group.

Fixes:

• Get-RscMssqlDatabaseRecoveryPoint -LastFull was previously returning the snapshot date, which is not the same as the recovery date, resulting in recoveries that would still perform log recoveries in addition to the snapshot recovery. The cmdlet has been updated to get use the correct time property.

• Get-RscSnapshot has been updated to include MssqlAppMetadata.EndBackupTimestampMs, needed to get the SQL recovery time for snapshot restores. The cmdlet has also been refactored to make future modifications easier.

• New cmdlet Get-RscMssqlLinkedAvailabilityGroup

Breaking Changes:

Version_1.12.7

Version 1.12.7

Schema Update:

See API Changelog
for API additions, deprecations and breaking changes.

Fixes:

• Get-RscSnapshot now retrieves snapshots for MSSQL databases. MSSQL database snapshots are tied to the DAG ID, not the ID of the object. Pipeline support now works with Get-RscMssqlDatabase:

# Retrieve all snapshots for "example" database
Get-RscMssqlDatabase -Name "example" -Relic:$false -Replica:$false | Get-RscSnapshot

• Protect-RscWorkload now works with MSSQL databases. MSSQL database protection is tied to the DAG ID, not the ID of the object.

# Assign "example" database to the Bronze SLA
Get-RscMssqlDatabase -Name "example" -Relic:$false -Replica:$false | Protect-RscWorkload -Sla (Get-RscSla Bronze)

Version_1.12.6

Version 1.12.6

Schema Update:

See API Changelog
for API additions, deprecations and breaking changes.

Fixes:

• Bugfix in StartRscManagedVolume and StopRscManagedVolume

Breaking Changes:

• Up to 1.12.5, when creating an empty Query object with -FieldProfile EMPTY, the object
  was automatically populated with minimum fields (with the AutoField feature), since
  an empty query is invalid. Starting in 1.12.6, we changed the rationale with empty
  Query objects: when you now create an empty Query object with -FieldProfile EMPTY,
  the object does contain an empty query. It is then up to the user to populate the
  fields manually in that query. We believe it is a better model. However, it implies
  that anybody who had scripts purposely creating an empty Query object (expecting
  AutoField to give them some field specification) and sending it as-is to the API
  server, will now break. Note though that it is a very peculiar scenario: if you
  wanted to created an auto-filled object, you'd give -FieldProfile DEFAULT,
  or rather, not specify any field profile since it defaults to DEFAULT.

Version_1.12.5

Version 1.12.5

Schema Update:

See API Changelog
for API additions, deprecations and breaking changes.

Fixes:

• Fixed compatibility with PowerShell 5