SNAPSHOT METADATA ARRANGEMENT FOR EFFICIENT CLOUD INTEGRATED DATA MANAGEMENT

    公开(公告)号:US20180121453A1

    公开(公告)日:2018-05-03

    申请号:US15338219

    申请日:2016-10-28

    Applicant: NetApp, Inc.

    Abstract: A storage appliance arranges snapshot data and snapshot metadata into different structures, and arranges the snapshot metadata to facilitate efficient snapshot manipulation, which may be for snapshot management or snapshot restore. The storage appliance receives snapshots according to a forever incremental configuration and arranges snapshot metadata into different types of records. The storage appliance stores these records in key-value stores maintained for each defined data collection (e.g., volume). The storage appliance arranges the snapshot metadata into records for inode information, records for directory information, and records that map source descriptors of data blocks to snapshot file descriptors. The storage appliance uses a locally generated snapshot identifier as a key prefix for the records to conform to a sort constrain of the key-value store, which allows the efficiency of the key-value store to be leveraged. The snapshot metadata arrangement facilitates efficient snapshot restore, file restore, and snapshot reclamation.

    SYNCHRONOUS REPLICATION FOR FILE ACCESS PROTOCOL STORAGE

    公开(公告)号:US20170147601A1

    公开(公告)日:2017-05-25

    申请号:US14948653

    申请日:2015-11-23

    Applicant: NetApp Inc.

    Abstract: One or more techniques and/or computing devices are provided for implementing synchronous replication. For example, a synchronous replication relationship may be established between a local storage controller hosting local storage and a remote storage controller hosting remote storage (e.g., replication may be specified at a file, logical unit number (LUN), or any other level of granularity). Data file operations may be implemented in parallel upon the local storage and the remote storage. Independent metadata file operations may be independently implemented from data file operations upon the local storage, and upon local completion may be remotely implemented upon the remote storage. In-flight data file operations may be drained before dependent metadata file operations are locally implemented upon the local storage, and upon local completion may be remotely implemented upon the remote storage.

    LOW OVERHEAD RESYNCHRONIZATION SNAPSHOT CREATION AND UTILIZATION

    公开(公告)号:US20250053316A1

    公开(公告)日:2025-02-13

    申请号:US18810870

    申请日:2024-08-21

    Applicant: NetApp, Inc.

    Abstract: One or more techniques and/or computing devices are provided for resynchronization. For example, a request may be received to create pseudo snapshots of a first consistency group, hosted by a first storage controller, and a second consistency group, hosted by a second storage controller, having a synchronous replication relationship with the first consistency group. Incoming client write requests are logged within an intercept tracking log at the first storage controller. After a first drain without hold of incoming write requests is performed, a first pseudo common snapshot of the second consistency group is created. After a second drain without hold of incoming write operations is performed, a second pseudo common snapshot of the first consistency group and the intercept tracking log is created. The pseudo snapshots and the intercept tracking log (e.g., indicating a delta between the pseudo snapshots) are used to resynchronize the first and second consistency groups.

    Re-aligning data replication configuration of primary and secondary data serving entities of a cross-site storage solution after a failover event

    公开(公告)号:US11966307B2

    公开(公告)日:2024-04-23

    申请号:US17751410

    申请日:2022-05-23

    Applicant: NetApp, Inc.

    CPC classification number: G06F11/2069 G06F11/2092 G06F2201/85 H04L67/1097

    Abstract: Systems and methods for re-aligning data replication configuration of a cross-site storage solution after a failover are provided. According to one embodiment, after a failover, the new primary distributed storage system orchestrates flipping of the data replication configuration of a peered consistency group (CG) to reestablish zero RPO and zero RTO protections for the peered CG. The primary causes the secondary distributed storage system to perform an atomic database operation on its remote configuration database to (i) delete an existing source configuration that identifies the secondary as a source of data replication; and (ii) persist a new destination configuration identifying the secondary as a destination of data replication. Then, the primary performs an atomic database operation on its local configuration database to (i) delete an existing destination configuration identifying the primary as the destination; and (ii) persist a new source configuration identifying the distributed storage system as the source.

Patent Agency Ranking