locked
Seconday Site stuck in Recovering RRS feed

  • Question

  • The other day I had issues with my secondary site.  I used the  "Recover Secondary Site'  option.

    My Site stopped and never came back up!.  Status has been stuck in Recovery for the past 2 days.  Database replication is also broken between my primary site and secondary site.  Is there a way that I can restore my secondary site back to good health?

    Friday, January 9, 2015 4:26 PM

All replies

  • Can you check the ConfigMgrSetup.log on the secondary site computer to validate the installation was successful?

    I have not done a secondary site recovery, but I know that it needs to restore data from your primary site.  Is it possible the amount of data vs. the link to the secondary site is causing the problem?

    Jeff

    Friday, January 9, 2015 4:55 PM
  • there are no errors.  the last line says

    Secondary Site is now Active

    Friday, January 9, 2015 5:07 PM
  • i followed these instructions

    https://phyllisinit.wordpress.com/2014/11/08/secondary-site-replication-kept-going-to-degrade-and-failed/

    the link says successful but has not turned green yet

    Friday, January 9, 2015 6:42 PM
  • Any errors in rcmctrl.log on both sites?

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, January 9, 2015 10:44 PM
  • there are no errors!.  The logs  say replication is going on both the primary and the secondary site.
    Saturday, January 10, 2015 5:33 PM
  • Hi 

    Is the above issue has been fixed, I do face the same issue now, Site Recovery is Struck and database replication says link failed

    And there is no error in recmctrl.log

    Database replication completed with green but showing error on replicationLinkAnalysis.log

    7/14/2016 12:18:36 PM: ReplicationLinkAnalysis Verbose: 1 : SQL's error log file for SQL instance SMGSVA006.saipemnet.saipem.intranet\CONFIGMGRSEC is C:\Program Files\Microsoft SQL Server\MSSQL11.CONFIGMGRSEC\MSSQL\Log\ERRORLOG.
    7/14/2016 12:18:36 PM: ReplicationLinkAnalysis Information: 1 : Scanning SQL error log files for the string [Error: 2601,].
    7/14/2016 12:18:36 PM: ReplicationLinkAnalysis Verbose: 1 : Checking SQL error log file \\SMGSVA006.saipemnet.saipem.intranet\C$\Program Files\Microsoft SQL Server\MSSQL11.CONFIGMGRSEC\MSSQL\Log\ERRORLOG.
    7/14/2016 12:18:36 PM: ReplicationLinkAnalysis Verbose: 1 : Reading content of file \\SMGSVA006.saipemnet.saipem.intranet\C$\Program Files\Microsoft SQL Server\MSSQL11.CONFIGMGRSEC\MSSQL\Log\ERRORLOG.
    7/14/2016 12:18:37 PM: ReplicationLinkAnalysis Information: 1 : Completed replication link analysis thread.
    7/14/2016 12:18:37 PM: ReplicationLinkAnalysis Information: 1 : Enumerating failed rules list.
    7/14/2016 12:18:37 PM: ReplicationLinkAnalysis Information: 1 : Enumerating succeeded rules list.
    7/14/2016 12:18:37 PM: ReplicationLinkAnalysis Information: 1 : Returning Executed rules.
    7/14/2016 12:18:37 PM: ReplicationLinkAnalysis Error: 1 : Invalid Signature.
    7/14/2016 12:18:37 PM: ReplicationLinkAnalysis Error: 1 : System.IO.IOException: Invalid Signature.
       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
       at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
       at Microsoft.ConfigurationManager.ReplicationLinkAnalyzer.IsSysCommitTabError.ReadFileContent(String sqlErrorLogFile)
       at Microsoft.ConfigurationManager.ReplicationLinkAnalyzer.DataStoreWrapper.ReadFileContent(AccountInfo accountInfo, String serverName, String fileName)
       at Microsoft.ConfigurationManager.ReplicationLinkAnalyzer.IsSysCommitTabError.ScanLogFilesForError(Boolean checkAllLogs, DateTime checkDate, String sqlErrorLogPath, String comparisonString, DateTime& matchingLineDate)
       at Microsoft.ConfigurationManager.ReplicationLinkAnalyzer.IsSysCommitTabError.Run()

    Thursday, July 14, 2016 10:20 AM