Jump to content


reinos

CAS Restored (1511) - all sites in maintenance mode

Recommended Posts

Hi

have restored my CAS from database backup (without reference to any primary site) but now each console (CAS, Primary) starts in read-only mode and database replication shows "Link failed".

  • spdiagdrs shows the following on the primary

LocalTime    SiteCode    ParentSite    SiteType    SiteStatus    SQLInstance    DBName    CertificateThumbprint
2017-06-28 07:13:12.973    NPS    CAS    Primary    MAINTENANCE_MODE    server.subdomain.domain.com    CM_NPS    0xEBC6799CFD10DF9B85E9F218D1A3C7539EA7D20B

  • Thats from the rcmctrl.log

Running Telemetry queries.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    7476 (0x1D34)
Found 0 telemetry queries to run.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    7476 (0x1D34)
   On entry: recovery status for link [CAS, NPS, Hardware_Inventory_31] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
Successfully run 0 Telemetry queries.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    7476 (0x1D34)
   On exit: recovery status for link [CAS, NPS, Hardware_Inventory_31] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, SEL, Hardware_Inventory_31] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, SEL, Hardware_Inventory_31] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
ProcessTelemetry performed as requested    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    7476 (0x1D34)
   On entry: recovery status for link [CAS, NPS, Hardware_Inventory_32] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, NPS, Hardware_Inventory_32] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, SEL, Hardware_Inventory_32] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, SEL, Hardware_Inventory_32] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, NPS, Hardware_Inventory_33] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, NPS, Hardware_Inventory_33] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, SEL, Hardware_Inventory_33] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, SEL, Hardware_Inventory_33] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, NPS, Hardware_Inventory_34] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, NPS, Hardware_Inventory_34] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, SEL, Hardware_Inventory_34] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, SEL, Hardware_Inventory_34] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, NPS, Hardware_Inventory_35] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, NPS, Hardware_Inventory_35] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, SEL, Hardware_Inventory_35] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, SEL, Hardware_Inventory_35] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, NPS, Hardware_Inventory_36] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, NPS, Hardware_Inventory_36] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, SEL, Hardware_Inventory_36] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, SEL, Hardware_Inventory_36] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, NPS, CMUpdates Status] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, NPS, CMUpdates Status] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, SEL, CMUpdates Status] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, SEL, CMUpdates Status] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, NPS, Hardware_Inventory_37] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, NPS, Hardware_Inventory_37] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On entry: recovery status for link [CAS, SEL, Hardware_Inventory_37] is StartRecovery. Site status PreparedForRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
   On exit: recovery status for link [CAS, SEL, Hardware_Inventory_37] is StartRecovery.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:44    8144 (0x1FD0)
Retry for process replication is requested.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:45    8144 (0x1FD0)
Cleaning the RCM inbox if there are any *.RCM files for further change notifications....    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:45    7608 (0x1DB8)
Rcm control is waiting for file change notification or timeout after 60 seconds.    SMS_REPLICATION_CONFIGURATION_MONITOR    28.06.2017 07:23:45    7608 (0x1DB8)

Best regards

Reiner

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.