I am using SQL 2012 with Always ON and name of the application is Sharepoint. Today I saw following error message in SQL error log:-
2015-08-02 02:00:06.750 spid159s Error: 5123, Severity: 16, State: 1.
2015-08-02 02:00:06.750 spid159s CREATE FILE encountered operating system error 3(The system cannot find the path specified.) while attempting to open or create the physical file 'G:\MSSQL11.CZ01\MSSQL\DATA\WebAnalyticsServiceApplication_ReportingDB_723c45f0-4227-4938-9f5f-9aaa76684a1eAgg
2015-08-02 02:00:06.750 spid159s Error: 5123, Severity: 16, State: 1.
2015-08-02 02:00:06.750 spid159s CREATE FILE encountered operating system error 3(The system cannot find the path specified.) while attempting to open or create the physical file 'G:\MSSQL11.CZ01\MSSQL\DATA\WebAnalyticsServiceApplication_ReportingDB_723c45f0-4227-4938-9f5f-9aaa76684a1eAgg
2015-08-02 02:00:06.750 spid159s Error: 5123, Severity: 16, State: 1.
2015-08-02 02:00:06.750 spid159s CREATE FILE encountered operating system error 3(The system cannot find the path specified.) while attempting to open or create the physical file 'G:\MSSQL11.CZ01\MSSQL\DATA\WebAnalyticsServiceApplication_ReportingDB_723c45f0-4227-4938-9f5f-9aaa76684a1eAgg
2015-08-02 02:00:06.750 spid159s Error: 5183, Severity: 16, State: 1.
2015-08-02 02:00:06.750 spid159s Cannot create the file "WebAnalyticsServiceApplication_ReportingDB_723c45f0-4227-4938-9f5f-9aaa76684a1eAggregation20150809". Use WITH MOVE to specify a usable physical file name. Use WITH REPLACE to overwrite
an existing file.
2015-08-02 02:00:06.750 spid159s AlwaysOn Availability Groups data movement for database 'WebAnalyticsServiceApplication_ReportingDB_723c45f0-4227-4938-9f5f-9aaa76684a1e' has been suspended for the following reason: "system" (Source
ID 2; Source string: 'SUSPEND_FROM_REDO'). To resume dat
2015-08-02 02:00:06.750 spid159s Error: 3313, Severity: 21, State: 2.
2015-08-02 02:00:06.750 spid159s During redoing of a logged operation in database 'WebAnalyticsServiceApplication_ReportingDB_723c45f0-4227-4938-9f5f-9aaa76684a1e', an error occurred at log record ID (176384:117272:1). Typically, the specific
failure is previously logged as an error in th
It seems from application layer, one new datafile was created. There was CREATE FILE command that came from the primary replica, and when that transaction went through the redo phase on the secondary replica, it failed because of a mismatch in the directory structure between the two replicas. I can fix this issue by restoring full backup on secondary replica. Is it the only option to fix this issue? Also how can I make sure in future the same problem won't be happened? Is there any special configuration from Application layer where i need to change something? Any help would be highly appreciated.