Topic: Failure working off in AlwaysOn
The task: to test operation AlwaysOn at a failure.
It is given: Tuned synchronous AlwaysOn in Failover a cluster, one basis, is synchronized, the second is adjusted on reading (ApplicationIntent=ReadOnly)
The check scenario: the cluster (the first thus works and there transactions are theoretically possible) falls, we lift AlwaysOn on the second with possible loss of the data, we work there, we lift reversely a cluster, we are returned on the first with loss of the data on the first .
At scenario implementation we rest against a problem at a reset stage on the first with loss on them the data.
The situation is visible on the enclosed picture.
The first . As it to synchronize reversely - it is not clear. To deduce basis from AlwaysOn and reversely to add synchronizing from zero - (on it occupies some days).
Found such to dock , there write:
If loss of the data is comprehensible to your business purposes, it is possible to restart bases of the data-addressees. At renewal of basis of the data-addressees, the first step of its synchronization is rollback. If sending queue contained any log records at the moment of failure of the server, Appropriate transactions will be lost, even if they have been fixed.
However it did not happen.
How it is possible to synchronize repeatedly the first the data with the second without breaking AlwaysOn and without deducing from it basis?
In technology beginners, do not kick strongly. If , I will be grateful.