SQL Server Availability Group Auto Seeding is a wonderful thing, it saves database administrators time when setting up availability groups.  However I found an issue with the graphical user interface in bedded in SQL Server Management Studio that makes it appear as if auto seeding has failed and SQL Server ended the process.

When I was attempting to use the GUI to deploy a database to other replica’s in an availability group I received an error that stated “Restore Failed for Server, Exclusive Access could not be obtained because the database is in use.”  This caused me confusion as the server listed in the error is the secondary replica, the replica in which the GUI was doing restores on.  The only thing that could be using this database as it is restoring is the process doing the restore.  I found this error to be null, I did find a helpful DMV to monitor the physical stats on the seeding process, the DMV is named dm_hadr_physical_seeding_stats.

The physical seeding stats DMV shows you the status, transfer rate, start time of the sync, and estimated end time of the sync.  All of this information is listed by database name.  This DMV was able to provide me a status of the seeding when the GUI stated the sync failed and was ended.

The issue with the GUI was a bug in SSMS that has since been resolved.

The post SQL Server Availability Group Auto Seeding Error appeared first on VitaminDBA.