Emc IP Holding Company LLC

Emc Corporation

John C Rokicki

Shelesh Chopra

Vladimir Mandic

Upanshu Singhal

Matthew Dickey Buchman

Scott Forrest Bingham

Venkatesha Murthy

Manuel Rodriques

Joseph G Murphy

Storage of discovered data object to storage layouts is described. A system receives a request to discover a data object to storage layout. The system determines if a discovery log stores a current data object to storage layout. The system provides a backup application with the current data object to storage layout in response to a determination that the discovery log stores the current data object to storage layout.

Storage of discovered data object to storage layouts

Definitions are received for allowable activity windows and epochs. Each epoch specifies a retention duration and allowable activity window. There can be a retention policy specifying that copies created during a particular time period of the allowable activity window are to be retained past a retention duration of an initial epoch. A determination is made as to whether a copy was created during the particular time period specified in the retention policy. If the copy was not created during the particular time period, the retention duration of the initial epoch is added to a creation time of the copy to obtain a date after which the copy should be deleted. If the copy was created during the particular time period, a retention duration of a subsequent epoch is added to the creation time to obtain the date. The date is then associated with the copy.

Systems and methods for managing copy creation and deletion

A set of logical containers are maintained in a cache, each logical container corresponding to a portion of a main snapshot catalog. First metadata of a first snapshot created by a first snapshot appliance is examined. Based on the first metadata examination, the first snapshot is cataloged into a first logical container. Second metadata of a second snapshot created by a second snapshot appliance is examined. Based on the second metadata examination, the second snapshot is cataloged into a second logical container, separate from the first logical container. A request is received to perform an operation involving one of the first or second snapshots. The request is matched to one of the first or second logical containers. The one of the first or second logical containers is searched to retrieve a snapshot responsive to the request without searching another of the first or second logical containers.

Intelligent snapshot cataloging using separate logical containers to reduce snapshot query times

Backup storage is configured to automatically take one or more snapshots of a protected device. After a plurality of snapshots of the protected device have been automatically taken by the backup storage, the backup storage is communicated with in order to catalog metadata associated with the plurality of snapshots.

High speed snapshots mechanism

A backup system comprises a tape backup storage storing a set of tape backup data, a snapshot backup storage storing a nearest snapshot, and a processor. The processor is configured to determine the nearest snapshot, wherein a snapshot time of the nearest snapshot is nearest in time to a backup time, and determine the set of tape backup data, wherein the set of tape backup data and the nearest snapshot enable recovery of a backup data.

Data recovery from multiple data backup technologies

Embodiments are described for dynamically modifying backup policy of an application using changes in metrics of a data set generated by the application and/or user-specified rules. Each application can have its own backup policy having a protection level that determines a frequency of backup for the application data set. An application can have an initial backup policy. An application backup policy can be based on the application type, a percent of change to the data set since the last backup, a size of the data set, or other metric. A user can specify a rule for the backup policy and protection level for the application. The backup policy or protection level can be dynamically updated in response to changes in the data set or a user-specified rule, on a per-application basis.

Application intelligent snapshot backups

A discovery is made of an object to be backed up on a storage array of a client. An object mapping is generated that maps the object to a LUN of the storage array where the object is located. The object mapping is stored at a backup server. A snapshot of the storage array is obtained. The object mapping is reviewed to identify on the snapshot the object to be backed up and the object is backed up to a backup storage unit.

Intelligent backup model for snapshots

In response to a request for data protection of a first resource of a first system, data protection methods are identified to provide data protection for the first resource. One or more of the data protection methods are selected based on one or more data protection objectives of a data protection plan that is associated with the first resource. The data protection objectives collectively specify an expected outcome of the data protection plan. For each of the selected data protection methods, a list of actions to be performed is determined to satisfy expected outcome of the data protection objectives. The list of actions is deployed to the first system and a second system that provides data protection for the first system, including provisioning one or more data protection services in the first and second systems to carry out the list of actions.

Outcome-based data protection using multiple data protection systems

A service level agreement (SLA) is defined for providing data protection with one of data protection levels on data stored in a first system. The SLA includes zero or more service level objectives (SLOs), where each SLO describes a data protection objective to be met. A rule engine applies a set of rules to the SLOs to determine a list of actions to be performed in order to achieve the data protection objectives specified by the SLOs. One or more data protection services are provisioned to be performed at the first storage system and a second storage system that provides data protection for the first storage system. An outcome of the data protection services is evaluated in view of the SLOs to determine whether the data protection objectives have been satisfied.

Rule-based systems for outcome-based data protection

Save set indexing outside of backup windows is described. A system creates a snapshot of a save set without creating an index of the save set. The system creates the index of the save set in response to creating the snapshot of the save set.

Save set indexing outside of backup windows

Discovering snapshot information based on storage arrays is described. A system identifies first snapshot information associated with a first storage array. The system identifies second snapshot information associated with a second storage array. The system outputs the first snapshot information and the second snapshot information via a user interface.

Method and system for discovering snapshot information based on storage arrays

A method and system are provided for dynamic provisioning of snapshots in a data backup system with a software defined storage (SDS). The method implemented by the backup system receives a snapshot provisioning request including a user selection of snapshot objectives by a dynamic snapshot module, converts a file system reference mapping to a logical unit number (LUN) of the SDS, consolidates the snapshot provisioning request to the mapping and snapshot frequency, and passes the consolidated snapshot provisioning request to the SDS to provision snapshots.

Dynamic provisioning of snapshots

Systems and methods for performing replication operations on a continuous data protection system. Exemplary systems include a continuous data protection system configured to save a series of transactions of a production application, the continuous data protection system configured to allow a point in time view of the series of transactions, a replication application communicating with the continuous data protection system, the replication application configured to initiate generation of at least one pseudosnapshot of the series of transactions saved on the continuous data protection system and initiate surfacing of a copy of at least a portion of the series of transactions that were saved before the generation of the at least one pseudosnapshot, and a remote server communicating with the replication application, the remote server configured to send replication instructions to the replication application.

Network configuration backup and restore operations using continuous data protection

Systems and methods for performing replication operations on a continuous data protection system. In one embodiment, a method includes identifying at least a portion of the series of transactions on the continuous data protection system to be included in the pseudosnapshot, identifying an initial time at which the pseudosnapshot begins, identifying a final time at which the pseudosnapshot ends, identifying a last transaction before the final time at which the pseudosnapshot ends, and creating an event marker identifying a particular point in time that the last transaction was saved on the continuous data protection system.

Growing community of inventors

Hopkinton, MA, United States of America

John C Rokicki