Azure虚拟机HA上的SQL [英] SQL on Azure Virtual Machine HA

查看:79
本文介绍了Azure虚拟机HA上的SQL的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经针对"Azure VM上的SQL"测试了许多高可用性方案.

I've tested lots of HA scenarios for "SQL on Azure VM".

其中一种情况是使用2个节点配置AlwaysOn.

One of those scenario is to configure AlwaysOn using 2 nodes.

在总是在2个"节点上配置完后,当我测试将主节点故障转移到辅助节点时,它已成功完成.

After I configured Always on 2 node, when I test to failover primary to secondary, it was completed successfully.

但是,在辅助节点作为主节点故障转移并且恢复了原始主节点之后,我尝试从当前主节点(原始辅助节点)故障切换到当前辅助节点(原始主节点),但是失败了.

However, after secondary node failed over as primary node and original primary node was recovered, I tried to failover from current primary node(original secondary node) to current secondary node (original primary node) but it failed.

在这种情况下,我该如何解决?

In this case, how can I solve this?

此外,当测试从主节点到辅助节点的故障转移方案时,当前会话将断开连接.我可以配置为在发生故障转移时不断开会话连接吗?

Also, when testing failover scenario from primary node to secondary node, the current session is disconnected. Can I configure that the session will be not disconnected when occurring failover?

推荐答案

Adele

有时只是延迟了恢复过程.

Some times it's just delayed the recover procedure.

您可以检查Always On Health事件或Event Viewer日志以进行更多故障排除.

You can check your Always On Health Event, or Event Viewer logs for more troubleshooting.

对于第二个问题,您可以在可用性组属性"上更改会话超时,如下图所示.

As for the second question you can change the session timeout on your Availability Group Properties, like the image below shows.


这篇关于Azure虚拟机HA上的SQL的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆