Troubleshoot a Failed Add-File Operation (Always On Availability Groups)
In some Always On availability group deployments, file paths differ between the system that hosts the primary replica and systems that host a secondary replica. If the file path of an add-file operation does not exist on a secondary replica, the add-file operation will succeed on the primary database. But the add-file operation will cause the secondary database to be suspended. This, in turn, causes the secondary replica to enter the NOT SYNCHRONIZING state.
We recommend that, if possible, the file path (including the drive letter) of a given secondary database be identical to the path of the corresponding primary database.
To resolve this problem the database owner must complete the following steps:
Remove the secondary database from the availability group. For more information, see Remove a Secondary Database from an Availability Group (SQL Server).
On the existing secondary database, restore a full backup of the filegroup that contains the added file to the secondary database, using WITH NORECOVERY and WITH MOVE (specifying the file path on the server instance that hosts the secondary replica). For more information, see Restore a Database to a New Location (SQL Server).
Back up the transaction log that contains the add-file operation on the primary database, and manually restore the log backup on the secondary database using WITH NORECOVERY and WITH MOVE.
Prepare the secondary database for re-joining the availability group, by restoring, WITH NO RECOVERY, any other outstanding log backups from the primary database.
Rejoin the secondary database to the availability group. For more information, see Join a Secondary Database to an Availability Group (SQL Server).
Overview of Always On Availability Groups (SQL Server)
Manually Prepare a Secondary Database for an Availability Group (SQL Server)
Troubleshoot Orphaned Users (SQL Server)
Troubleshoot Always On Availability Groups Configuration (SQL Server)