跳转到主内容

哪些快照会自动删除、哪些快照应处于繁忙状态?

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

适用场景

  • SnapMirror
  • SnapVault
  • 7-模式 Data ONTAP

问题解答

是否应删除繁忙的Snapshot?

哪些快照应自动删除?

  • SnapMirror仅保留最新的Snapshot、并在下次更新成功完成后立即删除上一个Snapshot。
  • SnapVault 和常规卷快照将根据计划中设置的Snapshot保留值进行删除。

 

哪些快照不会自动删除?

  • 通过SnapMirror重新同步、SnapMirror还原、SnapVault 还原、SnapRestore 、转储创建的快照 不会自动删除VolCopy和ndmpcopy。

 

哪些快照应处于繁忙状态?

  • qtree SnapMirror (QSM)和SnapVault 会锁定目标上最后创建的快照、因为下次增量更新需要该快照。在源上、Snapshot归创建它的服务所有、但它未锁定。
  • 请注意、对于卷SnapMirror (VSM)、在SnapMirror更新期间、源卷上的所有快照都将标记为"繁忙"、因为所有快照都会传输。VSM更新完成后、繁忙状态将自动从卷快照中清除。

    传输完成后、快照将恢复为"snapmirror"状态。之后、SnapMirror关系中的第一个快照将被删除。由于传输而同时保留为"繁忙"的任何快照都将被释放。

    For example
     

    Volume testvol1
    working...

    %/used %/total date name
    ---------- ---------- ------------ --------
    0% ( 0%) 0% ( 0%) Apr 16 10:33 f840-ca3(0033583371)_dstsm.31 (busy,snapmirror)
    0% ( 0%) 0% ( 0%) Apr 16 10:33 test1 (busy)
    1% ( 0%) 0% ( 0%) Apr 16 10:31 f840-ca3(0033583371)_dstsm.30 (busy,snapmirror)

    f840-ca1> snapmirror status
    Snapmirror is on.
    Source Destination State Lag Status

    f840-ca1:testvol1 f840-ca3:dstsm Source 00:02:10 Transferring (136 KB done)

    f840-ca1> snap list testvol1
    Volume testvol1
    working...

    %/used %/total date name
    ---------- ---------- ------------ --------
    0% ( 0%) 0% ( 0%) Apr 16 10:33 f840-ca3(0033583371)_dstsm.31 (snapmirror)
    0% ( 0%) 0% ( 0%) Apr 16 10:33 test1

  • 此外、如果某个Snapshot正在由NDMP备份或转储使用、则该Snapshot将标记为"(busy、backup[#]、snapmirror)"。备份完成或备份终止后、繁忙状态将自动清除。要确定备份是否正在使用Snapshot、请运行"backup status"命令。

  • LUN或卷克隆、CIFS共享、RAID镜像等锁定其各自的Snapshot。

    注意请参见知识库: 快照显示为繁忙。 

  • 从Data ONTAP 7.3开始、添加了一些功能、可以在SnapMirror目标基础上构建FlexClones、而不会导致SnapMirror传输失败。但是、对于Data ONTAP 7.3之前的版本、FlexClone会锁定SnapMirror快照:您可以克隆SnapMirror卷、但必须注意、SnapMirror目标的克隆会锁定从中创建克隆的Snapshot副本。这样、如果此卷属于SnapMirror级联、则它还会锁定源卷以及级联中的每个卷中的该副本。此外、如果FlexClone卷是从目标卷中的Snapshot副本创建的、而该副本不是最新的副本、 因此、已锁定Snapshot副本、如果源卷上不再存在该Snapshot副本、则每次更新都需要删除目标卷上的该副本。在这种情况下、对目标卷的所有SnapMirror更新都将失败、直到克隆被销毁或拆分为止。如果克隆是从SnapMirror目标中的最新Snapshot副本创建的、则不会发生这种情况、因为该副本仍存在于源卷中。

 

使用snap list -b vol_name命令定义哪个服务拥有Snapshot:在Data ONTAP 7.0.2及更高版本中可以使用"-b"选项。第一列列出了卷中的所有Snapshot。第二列列出了Snapshot的所有者(如果该Snapshot处于繁忙状态)。如果Snapshot不繁忙、则不会报告任何所有者。

system>snap list -b vol1
Volume vol1 working...
name                                 owners
-----------                          -----------
snap1                                LUN clone
clone_vclone.1                       volume clone
system(0033604314)_vol1_q1-dst.2     snapmirror


在对繁忙的Snapshot尝试执行快照删除时、输出内容类似于Snapshot的所有者列表、但无法执行快照删除。例如:

System>snap delete -a vol1
Are you sure you want to delete all snapshots for volume vol1?
Y snap delete -a: Remaining snapshots are currently in use by dump, snap restore, SnapMirror, a CIFS share, RAID mirroring, LUNs or retained by SnapLock.
Please try to delete remaining snapshots later.
System>snap delete vol1 system(0033604314)_vol1_q1-dst.2        
Snapshot system(0033604314)_vol1_q1-dst.2 is busy because of snapmirror

追加信息

附加信息 _text

 

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.