跳转到主内容

为什么会生成sms.fanout.comm.snap.deleted"警报?

Views:
24
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

适用场景

  • ONTAP 9.7及更高版本
  • SnapMirror同步(SM-S)和SnapMirror异步扇出配置、如下所示:

1. PNG

问题解答

  • 使用SnapMirror同步(SM-S)和 SnapMirror异步关系的扇出配置可能会在SnapMirror源上记录以下警报:

Wed Jan 06 03:05:00 +0000 [ClusterA-01: rpl_worker_main: sms.fanout.comm.snap.deleted:alert]: SnapMirror Synchronous operation 'Update' for relationship '123456ab-1234-1234-abcd-0123456789ab' has cleaned up some of the old base Snapshot copies between the synchronous source and synchronous destination, which could result in no common Snapshot copy existing between the synchronous and asynchronous destinations.

  • 如果ONTAP检测到 扇出异步关系未复制由SM-S关系创建的SnapMirror通用Snapshot、则会生成此警报
  • 如果 SM-S关系发生灾难恢复场景、则异步目标与SM-S目标之间不会具有通用Snapshot、从而在尝试 从原始SM-S目标建立异步关系时导致出现"无通用Snap照"错误
避免警报
  • [1] 有关扇出拓扑的最佳实践、请查看TR-4832:《使用适用于ONTAP 9.7的NetApp SnapMirror进行三数据中心灾难恢复》
  • 对异步关系使用镜像所有Snapshot SnapMirror策略。这样可以确保 始终将SM-S关系创建的SnapMirror通用Snapshot复制到异步目标
  • 确保异步关系更新计划 的频率至少与SM-S的通用Snapshot创建计划相同(默认为每小时)

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
Scan to view the article on your device