公开(公告)号：US20170052717A1

公开(公告)日：2017-02-23

申请号：US14831808

申请日：2015-08-20

Applicant: VMware, Inc.

Inventor： Mayank RAWAT ,  Ritesh SHUKLA ,  Li DING ,  Serge PASHENKOV ,  Raveesh AHUJA

IPC: G06F3/06 ,  G06F17/30

CPC classification number: G06F17/30327 ,  G06F3/0608 ,  G06F3/0641 ,  G06F3/067 ,  G06F17/30088

Abstract: User data of different snapshots for the same virtual disk are stored in the same storage object. Similarly, metadata of different snapshots for the same virtual disk are stored in the same storage object, and log data of different snapshots for the same virtual disk are stored in the same storage object. As a result, the number of different storage objects that are managed for snapshots do not increase proportionally with the number of snapshots taken. In addition, any one of the multitude of persistent storage back-ends can be selected as the storage back-end for the storage objects according to user preference, system requirement, snapshot policy, or any other criteria. Another advantage is that the storage location of the read data can be obtained with a single read of the metadata storage object, instead of traversing metadata files of multiple snapshots.

Abstract translation: 同一个虚拟磁盘的不同快照的用户数据存储在同一个存储对象中。 类似地，同一个虚拟磁盘的不同快照的元数据被存储在同一个存储对象中，同一虚拟磁盘的不同快照的日志数据被存储在同一个存储对象中。 因此，快照管理的不同存储对象的数量不会与所拍摄的快照数量成比例增加。 此外，根据用户偏好，系统要求，快照策略或任何其他标准，可以选择多个持久存储后端中的任何一个作为存储对象的存储后端。 另一个优点是可以通过单次读取元数据存储对象来获取读取数据的存储位置，而不是遍历多个快照的元数据文件。

公开(公告)号：US20180150492A1

公开(公告)日：2018-05-31

申请号：US15882123

申请日：2018-01-29

Applicant: VMware, Inc.

Inventor： Mayank RAWAT ,  Ritesh SHUKLA ,  Li DING ,  Serge PASHENKOV ,  Raveesh AHUJA

IPC: G06F17/30 ,  G06F3/06

CPC classification number: G06F16/2246 ,  G06F3/0608 ,  G06F3/0641 ,  G06F3/067 ,  G06F16/128

Abstract: User data of different snapshots for the same virtual disk are stored in the same storage object. Similarly, metadata of different snapshots for the same virtual disk are stored in the same storage object, and log data of different snapshots for the same virtual disk are stored in the same storage object. As a result, the number of different storage objects that are managed for snapshots do not increase proportionally with the number of snapshots taken. In addition, any one of the multitude of persistent storage back-ends can be selected as the storage back-end for the storage objects according to user preference, system requirement, snapshot policy, or any other criteria. Another advantage is that the storage location of the read data can be obtained with a single read of the metadata storage object, instead of traversing metadata files of multiple snapshots.