Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
AvailabilityGroup backup history added #6251
Type of Change
Have Get-DbaDbBackupHistory play nice with AG backup history spread across nodes
Little bit of recursion
Added another property to the BackupHistory object: AvailabilityGroupName
If the SqlInstance is an AG listener then fire off a gddbh query to each node. For last,
If an instance is specified and the requested dbs are in an AG, then it will query all nodes in the AG for that database, but only use the instance for the other dbs.
Removed ParameterSet as it doesn't appear to do anything anymore.
Commands to test
Ok. So you might be able to answer this scenario without me having to dig through code...or see what was changed.
I have 3 node AG setup, the 3rd async replica is located at a DR site and is a named instance, but also because of security requires a custom port (not using 1433). I know in SMO that SQL Server class for AvailabilityGroup knows nothing of this port and only has the server name. When I pass in the listener in order to pull that backup history how is your code going to connect to that 3rd instance?
Now mind you I completely understand if it will break because we have the same issue in the DSC module for SQL Server and AG builds. If you can lay out how it connects to the other replicas to pull backup history I'm good with merging....