Consider the following scenario:
You use automatic seeding for the secondary replica of an AlwaysOn Availability Group in Microsoft SQL Server.
You back up a database [db1], you add files [f1] and [f2], and then you remove backup file [f1].
You change the physical name for file [f2] when you restore database [db1], and change the logical name from [f2] to [f1] (the file that was removed).
In this scenario, a conflict occurs for the secondary replica when you try to join the availability group in auto-seeding mode. Then, you receive the following error message:
DateTime spid97s Error: 911, Severity: 16, State: 1.
DateTime spid97s Database 'DatabaseName' does not exist. Make sure that the name is entered correctly.
DateTime spid97s Error: 4353, Severity: 16, State: 1.
DateTime spid97s Conflicting file relocations have been specified for file 'FileName'. Only a single WITH MOVE clause should be specified for any logical file name.
DateTime spid97s Error: 3013, Severity: 16, State: 1.
DateTime spid97s RESTORE DATABASE is terminating abnormally.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem is fixed in the following cumulative updates for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Learn about the terminology that Microsoft uses to describe software updates.