Dell Products Inc.

Emc IP Holding Company LLC

Nicholas W Von Hein

Michael Ferrari

Daryl Francis Kinney

Shakil Anwar

Tao Tao

Sandeep Chandrashekhara

Kevin M Tobin

George F Lettery

Akshay Kumar Srivastava

Shruti Gupta

Gu Huang

John Copley

Subramanian Venkatraman

Memory management processes allocate and recycle pages of replication data pointer (RDP) metadata space in shared memory. When the RDP page currently allocated to an IO thread becomes full, that RDP page is released, and a new RDP page is allocated to the IO thread. The released page eventually becomes fragmented and is added to a list of RDP pages that are ranked based on partial fullness. An IO thread that needs a new RDP page is allocated a mostly empty RDP page from the ranked list, if such a page is available. Otherwise, a new completely empty RDP page is allocated to the IO thread. Use of the ranked lists reduces latency associated with allocation of new RDP pages. Contention between IO threads for RDP metadata space is reduced because each IO thread has exclusive rights to the free RDP metadata space in its currently allocated page.

Allocating system RDP metadata space with IO performance priority

Generation of new snapshots of a storage object are prompted based on changes to the storage object. An absolute storage change condition is satisfied when the aggregate amount of changed data since the most recent snapshot satisfies a threshold that represents a predefined amount of storage capacity, e.g., N GB. A percentage of used storage change condition is satisfied when the aggregate size of the changes expressed as a percentage of the provisioned storage capacity of snapped storage object satisfies a predetermined threshold, e.g., X % of Y TB. A percentage of provisioned storage change condition is satisfied when the aggregate amount of the changes in terms of percentage of utilized storage capacity of storage object satisfies a predetermined threshold expressed as a percentage of the utilized capacity of the storage object, e.g., P % of Z TB.

Change-based snapshot mechanism

Snapsets containing snapshots from a group of storage volumes are assigned snapset IDs. The same snapset ID is applied to each snapshot of the snapset, and is a globally unique value within the storage system. The snapset ID is assigned to a snapshot upon creation, and remains the same regardless of creation or deletion of other snapshots on the storage volume. By assigning a snapset ID to each snapshot of the snapset, and maintaining the snapset ID as a constant value as long as the snapshot is maintained on the storage system, it is possible to easily determine which snapshots form a given snapset. Control operations on particular storage groups or across storage groups are implemented by specifying particular actions to be taken on snapsets or snapshots, which are identified using the snapset IDs.

Method and apparatus for deterministically identifying sets of snapshots on a storage system

Targetless snapshot schedules are defined by policy objects that include a snap creation interval, maximum snap count, and schedule ID. Multiple schedule IDs can be associated with a single storage object to implement different concurrent targetless snapshot schedules with a single storage object. Multiple storage objects may use the same targetless snapshot schedule independently. Because the targetless snapshot schedules are implemented independently, discard of old snapshots to maintain a snap count for a first storage object does not cause discard of snapshots for a second storage object. Further, discard of old snapshots to maintain a snap count for a first schedule does not cause discard of snapshots for a second schedule applied to the same storage object.

Grouping of multiple concurrent schedules of point-in-time snapshots for consistently defined data image protection

Targetless snapshots that are in use are excluded from discard and exempted from inclusion against a snapshot retention count limit. Snapshots that are linked to a target volume are considered to be in use. Snapshots having a persist attribute set are considered to be in use. Snapshots having an expiration attribute set are considered to be in use until at least the expiration time. Snapshots having an age limit attribute set are considered to be in use until reaching at least the specified age. The snapshot retention count limit can be updated with a command. Other commands discard snapshots created before a specified time or older than a specified age, provided the snapshots are not in use. A terminate all command prompts discard of all snapshots that are not in use.

Compliance recycling algorithm for scheduled targetless snapshots

Techniques for providing snapshots of logical devices may include: receiving a first request to create a first snapshot of a logical device; responsive to the first request, performing first processing including storing first information in a cache slot, the first information identifying the first snapshot and the logical device used as a source of the first snapshot; receiving a second request to activate one or more snapshots, including the first snapshot, identified by information stored in the cache slot; and responsive to receiving the second request, performing second processing including initiating execution of an asynchronous process that performs snapshot activation processing for the one or more snapshots identified by the cache slot.

Growing community of inventors

Riverside, RI, United States of America

Nicholas W Von Hein