跳转到主内容

哪些快照会自动删除、哪些快照应该占线？

  1. 最后更新
  2. 另存为PDF
Views:
29
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

适用于

  • SnapMirror
  • SnapVault
  • 7-模式 Data ONTAP

解答

是否应删除繁忙的快照？

哪些快照应自动删除？

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

 

哪些快照不会自动删除？

  • SnapMirror 重新同步、 SnapVault 恢复、快照恢复、转储、卷复制和 NDMPCopy 创建的快照不会自动删除。

 

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

  • qtree SnapMirror （ QSM ）和 SnapVault 锁定目标上最后创建的快照，因为下次增量更新需要该快照。在源上、创建快照的服务拥有该快照、但未锁定该快照。
  • 请注意，对于卷 SnapMirror （ VSM ）、由于传输了所有快照、因此在 SnapMirror 更新期间源卷上的所有快照都将标记为“忙碌”。VSM 更新完成后、卷快照中的繁忙状态将自动清除。

    Once the transfer has completed the snapshot will go back into a "snapmirror" state. The first snapshot from the snapmirror relationship will then be deleted. Any snapshot that was also held as "busy" because of the transfer will be released.

    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

  • 此外，如果某个快照正由 NDMP 备份或转储使用、则快照将被标记为“（繁忙、备份 [#] 、 SnapMirror ）”。备份完成后或备份终止时，“忙碌”状态将自动清除。要确定备份是否正在使用快照、请运行 " 备份状态 " 命令。

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

    注：请参见 KB ：快照显示为繁忙。 

  • 从 Data ONTAP 7.3 开始、新增了功能以允许在 SnapMirror 目标上构建 FlexClone 、而不会导致 SnapMirror 传输失败。但是，对于 Data ONTAP 7.3 之前的版本、 FlexClone 会锁定 SnapMirror 快照：您可以克隆 SnapMirror 卷、但您必须知道 SnapMirror 目标的克隆会锁定创建克隆的 Snapshot 副本。在执行此操作时、如果卷是 SnapMirror 级联的一部分、它还会锁定源卷和级联中每个卷中的副本。此外，如果从目标卷中的 Snapshot 副本（不是最新副本）创建 FlexClone 卷、 因此，已锁定 Snapshot 副本、如果源卷上不再存在该 Snapshot 副本、则每个更新都需要删除目标上的副本。在这种情况下，对目标卷的所有 SnapMirror 更新都将失败，直到克隆被销毁或分离。如果从 SnapMirror 目标中最新的 Snapshot 副本创建克隆、则不会发生这种情况，因为源卷中仍然存在该副本。

 

Use snap list -b vol_name command to define which service owns a Snapshot: The "-b" option is available in Data ONTAP 7.0.2 and later. The first column lists all the Snapshots in a volume. The second column lists owners of the Snapshot, if it is busy. If the Snapshot is not busy, no owners are reported.

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

When a snap delete is attempted on a busy Snapshot, the output is a similar list of owners of the Snapshot, failing the snap delete. For example:

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