Hi @Андрей Михалевский,
Thank you for your reaching out and welcome to Microsoft Q&A!
Please refer to Always On failover cluster instances (SQL Server), it can help you better understand the concept of Failover Clustering. As mentioned in the article:
When there is hardware or software failure of a server, the applications or clients connecting to the server will experience downtime. Redundant nodes protect the availability of the SQL Server instance when it is an FCI instead of a standalone instance. Only one of the nodes in the FCI owns the WSFC resource group at a time. In case of a failure (hardware failures, operating system failures, application or service failures), or a planned upgrade, the cluster moves the resource group ownership to another WSFC node. This process is transparent to the client or application connecting to SQL Server. This minimizes the downtime the application or clients experience during a failure.
Could you please advise me what I should do after step 3?
As mentioned in the article you posted, convert the secondary replica into the primary replica for the planned manual failover. You could observe how the data of the database in your two nodes changes.
This is my Failover Cluster:
I hope this helps! If you have any more issues or need further assistance, feel free to share with us!
Best regards,
Lucy Chen
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
https://docs.microsoft.com/en-us/answers/support/email-notifications