未在服务总线中复制的高级层消息...是否有任何消息复制或备用解决方案？ [英] Messages not replicated in Service Bus for premium tier...Is there any solution for message replication or alternative?

问题描述

元数据 ：
队列，主题和订阅等实体;以及与命名空间关联的服务属性。  请注意，只会自动复制实体及其设置。消息不会被复制。

Metadata: Entities such as queues, topics, and subscriptions; and their properties of the service that are associated with the namespace. Note that only entities and their settings are replicated automatically. Messages are not replicated.

如何在高级层中复制服务总线的消息，尤其是那些未实现可用区域的区域。

推荐答案

理想情况下中断和灾难的可用性和恢复计划
"。

地理灾难恢复（如果没有使用可用区域）目前只能确保配对时，元数据（队列，主题，订阅，过滤器）将从主命名空间复制到辅助命名空间，并且不会复制消息。

Geo-Disaster recovery (if no availability zones are used) currently only ensures that the metadata (Queues, Topics, Subscriptions, Filters) are copied over from the primary namespace to secondary namespace when paired and messages are not replicated.

因此，此时的建议是创建
Azure区域，其中包含可用区域。但是，您可以创建
功能请求，以便在没有可用区域的情况下进行邮件复制。做好投资以获得牵引力。

So, the recommendation at this point is to create service bus cluster in Azure regions where availability zones are present. But yes you can create the feature request for message replication where availability zones are not present and do upvote it to get traction.

这篇关于未在服务总线中复制的高级层消息...是否有任何消息复制或备用解决方案？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！