AG补丁问题 [英] AG Patching question

查看:132
本文介绍了AG补丁问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

所以,我想做的是与sql补丁有关(这与普通的sql补丁有关 - 在同一sql版本中的CU / SP)

So, what i want to do is related with sql patching (This pertains to normal sql patching - CU's/SP's in the same sql version)

可以修补吗?在一个周末对prod AG节点说,下周应用程序测试,如果一切正常,请在下周末更新BCP AG节点 - 我想这样做的原因是如果应用程序报告后有问题初始prod修补我们
有一个env(bcp)我们可以故障转移,直到问题在Prod中得到解决。 

Can patching be done say on prod AG nodes on one weekend , apps test on it on the next week, if all is fine , update the BCP AG nodes on next weekend - The reason i want to do this is if there is a issue reported by apps after the initial prod patching we have a env (bcp) where we can failover till the issue is resolved in Prod. 

我的问题是 - 是否有可能从如果需要,可以修补未修补的bcp,这可能在AG吗?

My question is - Is it possible to failover sql from a patched prod to unpatched bcp if needed, is that possible in AG?

其次,人们如何修补他们的AG环境,请不要回答滚动升级,这不是关于最小化停机时间(https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/upgrading-always-on-availability- group-replica-instances?view = sql-server-2017)
,我只对知道感兴趣如果人们首先考虑修补1 env并等待一段时间&然后修补其他。

And secondly, how are people going about patching their AG env's , please don't answer about rolling upgrades ,this is not about minimizing downtime(https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/upgrading-always-on-availability-group-replica-instances?view=sql-server-2017) , I am only interested in knowing if people are looking into patching only 1 env first and waiting for some time & then patching other.

也许我会以错误的方式解决它,人们卸载CU,SP如果问题并且只是完成prod-bcp补丁 - 这是最好的方法?

Maybe i am going about it a wrong way, do people uninstall the CU's , SP's if issues and just do the complete prod-bcp patching together - is that the best way?

谢谢

D

推荐答案

您好SQLRocker

 

>> ;我的问题是 - 是否可以将sql从修补的prod故障转移到未修补的bcp(如果需要),这可能在AG吗?

>>My question is - Is it possible to failover sql from a patched prod to unpatched bcp if needed, is that possible in AG?

 

据我所知,我们只能从较低版本的可用性副本故障转移到啊更新版本的可用性副本,并且无法逆转它。安装补丁后,sql server的生成版本
将会改变。

As far as I know, we can only fail over from a lower version of availability replica to a higher version of availability replica, and can't reverse it. After installing patches, the build version of sql server will change.

 

>>我只想知道人们是否只想修补1个env先等待一段时间&然后修补其他。

>>I am only interested in knowing if people are looking into patching only 1 env first and waiting for some time & then patching other.

 

该链接表示每个可用性副本的升级应该很快。可用性副本的版本长时间不一致,这可能导致大量数据不同步
,并且需要在辅助副本和主副本之间同步的数据量变得非常大。

The link says that the upgrade of each availability replica should be fast. The version of the availability replicas is inconsistent for a long time, which may result in a large amount of data being unsynchronized, and the amount of data that needs to be synchronized between the secondary replica and the primary replica becomes extremely large.

 

希望这可以帮到你。

最好的问候,

Dedmon Dai

Dedmon Dai


这篇关于AG补丁问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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