跳转到主内容

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

  1. 最后更新
  2. 另存为PDF
Views:
101
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 目标建立异步关系时出现"无常见 Snapshot"错误
避免警报
  • 查看 TR-4832：使用 NetApp SnapMirror for ONTAP 9.7 的三数据中心灾难恢复 了解扇出拓扑的最佳实践
  • 对异步关系使用 MirrorAllSnapshots 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.