none
Не работает группа доступности AlwaysON RRS feed

  • Общие обсуждения

  • Доброго времени суток.

    Пытаюсь создать группу доступности, процесс проходит без каких либо ошибок. В логе ошибок тоже не нашел

    2016-10-14 15:52:43.69 spid51      [INFO] HkHostDbCtxt::Initialize(): Database ID: [6] 'BackupLocDb_c61606fc-46d3-4b97-9e01-ab16e1baa2b5'. XTP Engine version is 0.0.
    2016-10-14 15:52:43.69 spid51      Starting up database 'BackupLocDb_c61606fc-46d3-4b97-9e01-ab16e1baa2b5'.
    2016-10-14 15:52:43.70 spid51      [INFO] HkHostDbCtxt::Initialize(): Database ID: [6] 'BackupLocDb_c61606fc-46d3-4b97-9e01-ab16e1baa2b5'. XTP Engine version is 0.0.
    2016-10-14 15:52:43.74 spid51      [INFO] HkHostDbCtxt::Initialize(): Database ID: [6] 'BackupLocDb_c61606fc-46d3-4b97-9e01-ab16e1baa2b5'. XTP Engine version is 0.0.
    2016-10-14 15:52:43.76 spid51      Setting database option RECOVERY to FULL for database 'BackupLocDb_c61606fc-46d3-4b97-9e01-ab16e1baa2b5'.
    2016-10-14 15:52:43.76 spid51      Setting database option RESTRICTED_USER to ON for database 'BackupLocDb_c61606fc-46d3-4b97-9e01-ab16e1baa2b5'.
    2016-10-14 15:52:44.11 Backup      Database backed up. Database: BackupLocDb_c61606fc-46d3-4b97-9e01-ab16e1baa2b5, creation date(time): 2016/10/14(15:52:43), pages dumped: 338, first LSN: 34:144:74, last LSN: 34:192:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\server38\shares\SQLALWAYSON\BackupLocDb_c61606fc-46d3-4b97-9e01-ab16e1baa2b5.bak'}). This is an informational message only. No user action is required.
    2016-10-14 15:52:44.13 Backup      BACKUP DATABASE successfully processed 331 pages in 0.157 seconds (16.470 MB/sec).
    2016-10-14 15:52:48.86 spid51      The state of the local availability replica in availability group 'AlwaysON' has changed from 'NOT_AVAILABLE' to 'RESOLVING_NORMAL'.  The state changed because the local availability replica is joining the availability group.  For more information, see the SQL Server error log, Windows Server Failover Clustering (WSFC) management console, or WSFC log.
    2016-10-14 15:52:49.04 spid52      Always On: The local replica of availability group 'AlwaysON' is preparing to transition to the primary role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.
    2016-10-14 15:52:49.05 spid52      The state of the local availability replica in availability group 'AlwaysON' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'.  The state changed because the availability group is coming online.  For more information, see the SQL Server error log, Windows Server Failover Clustering (WSFC) management console, or WSFC log.
    2016-10-14 15:52:49.05 Server      The lease worker of availability group 'AlwaysON' is now sleeping the excess lease time (164812 ms) supplied during online. This is an informational message only. No user action is required.
    2016-10-14 15:52:49.06 spid18s     DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: D6BE828A-6ED2-4CE1-9F42-48FC28ADCB8B:0
    2016-10-14 15:52:49.06 spid18s     DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: D6BE828A-6ED2-4CE1-9F42-48FC28ADCB8B:0
    2016-10-14 15:52:49.07 Server      The state of the local availability replica in availability group 'AlwaysON' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'.  The state changed because the local replica has completed processing Online command from Windows Server Failover Clustering (WSFC).  For more information, see the SQL Server error log, Windows Server Failover Clustering (WSFC) management console, or WSFC log.
    2016-10-14 15:52:56.98 Server      The компонент Service Broker endpoint is in disabled or stopped state.
    2016-10-14 15:52:56.98 Server      Started listening on virtual network name 'SQL'. No user action is required.

    На второй ноде errorlog чист

    Но после создания вижу что вторая нода не включена в группу доступности:

    Жму правой кнопкой на второй ноде, затем "включить в группу доступности" и получаю следующую картину:

    На первой ноде в лог приходит:

    2016-10-14 16:00:37.38 spid49s     A connection for availability group 'AlwaysON' from availability replica 'CLUSTERNODE1' with id  [5E231847-6275-4A45-98CF-54B73F5EEFBA] to 'CLUSTERNODE2' with id [D6BE828A-6ED2-4CE1-9F42-48FC28ADCB8B] has been successfully established.  This is an informational message only. No user action is required.

    На второй:

    2016-10-14 16:00:37.34 spid55      The state of the local availability replica in availability group 'AlwaysON' has changed from 'NOT_AVAILABLE' to 'RESOLVING_NORMAL'.  The state changed because the local availability replica is joining the availability group.  For more information, see the SQL Server error log, Windows Server Failover Clustering (WSFC) management console, or WSFC log.
    2016-10-14 16:00:37.41 spid45s     The state of the local availability replica in availability group 'AlwaysON' has changed from 'RESOLVING_NORMAL' to 'SECONDARY_NORMAL'.  The state changed because the availability group state has changed in Windows Server Failover Clustering (WSFC).  For more information, see the SQL Server error log, Windows Server Failover Clustering (WSFC) management console, or WSFC log.
    2016-10-14 16:00:37.45 spid50s     A connection for availability group 'AlwaysON' from availability replica 'CLUSTERNODE2' with id  [D6BE828A-6ED2-4CE1-9F42-48FC28ADCB8B] to 'CLUSTERNODE1' with id [5E231847-6275-4A45-98CF-54B73F5EEFBA] has been successfully established.  This is an informational message only. No user action is required.

    В чем проблема? почему не синхронизируется база?

    14 октября 2016 г. 13:04