Emc IP Holding Company LLC

Hewlett-packard Development Company, L.p.

Netapp, Inc.

Ibrix, Inc.

Dell Products Inc.

Emulex Design & Manufacturing Corporation

Tbrix, Inc.

Sudhir Srinivasan

Jean-Pierre Bono

Boris Zuckerman

Garth Richard Goodson

Shankar Pasupathy

Ravi Kumar Kavuri

Steven Orszag

Kaladhar Voruganti

Daniel E Cummins

Doron Tal

Marc A De Souter

Gaurav Makkar

Vitaly M Oratovsky

Minglong Shao

Philip Eric Jackson

Kevin J Shea

Shaji O John

Devon Reed

Himabindu Tummala

Walter Forrester

Dan Aharoni

Glenn A Dearth

Peter Puhov

Steven A Morley

Yaron Dar

Frederic Corniquet

G Paul Koning

Anurag Bhatnagar

Carl John Lindeborg

Dinesh Venkatesh

James Duda

Manny Ye

Robin Lee Brown

Walter O'Brien

Irina P Slutsky

Thirumale Niranjan

Igal Moshkovich

Joon-Jack Yap

Benjamin Levin

Anil C Kumar

Techniques are provided to manage data on shutdown of a data storage system. For example, a method comprises initiating a process to shut down a data storage system which comprises storage devices that store data associated with one or more non-persistent logical storage resources of a virtual storage layer which is configured by the data storage system. In response to initiating the process to shut down the data storage system, the method comprises: storing configuration data associated with the virtual storage layer, the configuration data comprising unique identifiers associated with the one or more non-persistent logical storage resources; and performing a data backup process to persistently store a copy of the data associated with the one or more non-persistent logical storage resources to a backup storage system.

Managing data on shutdown of storage system

A method, computer program product, and computing system for locally processing a plurality of data files stored on a local data storage system to effectuate the storage of one or more archivable files at one or more defined remote addresses on a remote data storage system. One or more identifiers, that locate the one or more archivable files at the one or more defined remote addresses on the remote data storage system, are stored on the local data storage system. A local database, that defines the one or more identifiers, is maintained on the local data storage system.

Storage management system and method

Techniques are presented for dynamically allocating memory between containers. These techniques include (a) assigning a first portion of memory to a first container and a second portion of memory to a second container, the first and second portions overlapping to form a shared portion of memory assigned to both containers; (b) during a first interval, caching first data in a particular page of the shared portion by first data storage software executing within the first container; (c) during a second interval, caching second data in the particular page of the shared portion by second data storage software executing within the second container; (d) during the first interval, selectively enabling the first data storage software to access the particular page and blocking the second data storage software from accessing the particular page; and (e) during the second interval, selectively enabling the second data storage software to access the particular page and blocking the first data storage software from accessing the particular page.

Dynamic allocation of memory between containers

Described herein is a system that provides data service failover in shared storage clusters. An example shared storage cluster can include multiple data node devices equipped to access to a shared storage location. Each of the data node devices can host multiple network attached storage (NAS) servers. For each NAS server at a data node device, a different data node device in the shared storage cluster can be designated as a backup node. The designated backup nodes for NAS servers at any one data node device in the shared storage cluster can be distributed across multiple other data node devices in the shared storage cluster, thereby sharing the burden of data node device failure across multiple other data node devices.

Data service failover in shared storage clusters

A technique for managing data objects in a data storage cluster realizes an application-accessible data object within a file that belongs to an internal file system. The internal file system runs on a computing node of the cluster and is backed by a LUN realized in block storage. The storage cluster achieves snapshots of the data object at the level of the file system, e.g., by snapshotting the file, such that the data object and its snapshots are all backed by the same LUN in the block storage.

Reducing feature dependencies of block storage used to back NAS cluster

A technique for replicating file systems to any number of targets includes obtaining a writeable snapshot of a file system on a source, performing cloud tiering of files in the snapshot, replacing the file contents of the snapshot with stubs pointing to the cloud, and generating a namespace backup of the snapshot that includes directories and stubs. The source system ships the namespace backup to the cloud, allowing any authorized target system to restore from the namespace backup to a local file-system replica, such that contents of the cloud-tiered files are made accessible on the target system from the restored namespace via the stubs.

Replicating file systems via cloud storage

An apparatus in one embodiment comprises a storage system having at least first and second storage tiers each comprising a plurality of storage devices. The first storage tier implements a file system having a user visible name space and a corresponding hidden data store. The second storage tier implements a cloud-based object store. The storage system is configured to controllably relocate files from the hidden data store of the file system of the first storage tier to the cloud-based object store of the second storage tier. In conjunction with the relocation of a given one of the files, the given file is replaced in the hidden data store with a corresponding stub providing user access via the user visible name space to an object comprising the given file in the cloud-based object store of the second storage tier. The controllable relocation is illustratively performed in accordance with one or more configured policies.

Multi-tier storage system with controllable relocation of files from file system tier to cloud-based object storage tier

A method, computer program product, and computing system for locally processing a plurality of data files stored on a local data storage system to identify an archivable file for storage on a remote data storage system. A remote tiering appliance is enabled to obtain the archivable file, wherein the remote tiering appliance stores the archivable file at a defined remote address on the remote data storage system. An identifier is received from the remote tiering appliance that locates the archivable file at the defined remote address on the remote data storage system. The identifier is stored on the local data storage system.

An apparatus comprises a storage system comprising a plurality of storage nodes each comprising one or more storage devices. Each of the storage nodes further comprises a network protocol target configured to receive delivery of input-output (IO) operations from a network protocol initiator of a host device, a data server configured to execute the IO operations on a given storage node, and a data client configured to communicate the IO operations to at least one of the data server on the given storage node and one or more data servers corresponding to one or more additional ones of the plurality of storage nodes. The data client has knowledge of a distribution of data across the plurality of storage nodes.

Utilization of networking protocol for seamless integration of compute nodes with software-defined storage nodes

A method, computer program product, and computing system for storing a plurality of identifiers on a local data storage system. The plurality of identifiers locate a plurality of archived files at a plurality of defined remote addresses on a remote data storage system. The deletion of at least one of the plurality of identifiers is sensed, thus defining at least one deleted identifier. Temporal information of the at least one deleted identifier is compared to temporal information for a data protection operation performed on at least a portion of the local data storage system.

A technique for managing cloud storage provides a unified framework that supports both block-type data, such as LUNs (Logical UNits) and volumes, and file-type data, such as files, and expresses both types of data in the form of objects, which form a common base for both types of data. The framework includes a single API (application program interface) for managing storage and retrieval of block-derived objects and file-derived objects from the cloud, e.g., from a cloud-based data store.

Managing cloud storage of block-based and file-based data

Shipping local snapshots of logical units of data storage (LUNs) to cloud storage, wherein the local snapshots reside on local physical storage of a data storage system, includes replicating a baseline local snapshot of a LUN to a cloud-backed LUN backed by cloud physical storage of cloud storage system, and taking a first snapshot of the cloud-backed LUN to establish a baseline cloud-backed snapshot. For a subsequent local snapshot of the LUN, the method (1) identifies data content differences between the subsequent local snapshot and the baseline local snapshot, (2) updates the cloud-backed LUN by applying the data content differences, and (3) takes a second snapshot of the cloud-backed LUN, the second snapshot being a cloud-backed copy of the subsequent local snapshot and containing, in the cloud physical storage, (a) first blocks unique to the second snapshot and (b) second blocks shared with the baseline cloud-backed snapshot.

Data storage system with LUN snapshot shipping using volume-to-object translation

A block I/O request processing threads executes only on a processor core to which it is assigned. After it executes for a period of time, the block I/O request processing thread yields its assigned processing core to another type of thread that is runnable on the processing core, such as a file I/O request processing thread. When there are no block I/O requests for a block I/O request processing thread to process, it is suspended from being executed. A monitor thread running on another processing core detects that a newly received block I/O request is available for processing, and makes the block I/O request processing thread runnable again. The block I/O request processing thread may be assigned a higher priority than file I/O request processing threads, and preempt any runnable file I/O request processing threads when it is made runnable to process the newly received block I/O request.

Sharing processor cores in a multi-threading block i/o request processing data storage system

A data processing system backs up snapshots of storage objects to cloud storage by identifying to a cloud gateway a set of snapshots to be archived, and making the set available to the cloud gateway. Upon request by the cloud gateway, snapshot metadata is provided that includes offsets and lengths of data extents of the set of snapshots. On further request of the cloud gateway using the metadata, the data extents of the set of snapshots are provided to the cloud gateway, which uses the extents to create corresponding objects and stores the objects in the cloud storage, each object including the data extents and the snapshot metadata for a respective snapshot. Backup and restore are initiated by the gateway or by the data storage system in different embodiments.

Data processing system with cloud archiving of data object snapshots

Archiving local logical units of data storage (LUNs) to cloud storage, wherein the local LUNs reside on local physical storage of a data storage system, includes establishing a mirror between a local LUN and a cloud-backed LUN backed by cloud physical storage of a cloud storage system, the mirror making data contents of the cloud-backed LUN identical to data contents of the local LUN. Once the mirror is established, then (a) a stub is deposited on the local LUN to direct subsequent IOs to the cloud-backed LUN, and (b) local physical storage of the local LUN is released for allocation to other local LUNs. Subsequent IOs to the local LUN are satisfied from the cloud-backed LUN. An archived LUN can be restored by a restore process.

Data storage system with LUN archiving to cloud using volume-to-object translation

Growing community of inventors

Acton, MA, United States of America

Sudhir Srinivasan