Emc IP Holding Company LLC

Emc Corporation

Venu Varma

Kiran Bachu

Daniel Ravan

Ynn-Pyng Tsaur

Backup metadata deletion based on backup data deletion is described. A system receives a request to delete a backup data set associated with a host, a path, and a backup time. The system identifies a backup metadata object associated with the host and the path. The system determines whether the requested backup time is the earliest backup time associated with any backup data set associated with the host. The system determines whether the identified backup metadata object is a backup metadata deletion object associated with the backup time if the backup time is the earliest backup time. The system deletes the identified backup metadata object if the identified backup metadata object is a backup metadata deletion object associated with the backup time.

Backup metadata deletion based on backup data deletion

A system for building a restore list for a restore includes a processor and a memory. The processor is configured to determine whether a next sibling record of a directory index record of a root directory includes a subdirectory or a file, wherein the content of the directory index is determined from an incremental backup of the root directory. In the event that the next sibling record comprises a subdirectory of the root directory, the processor is configured to push a directory path associated with the next sibling record onto a directory stack. In the event that the next sibling record comprises a file, the processor is configured to add the latest index record associated with the file to a restore list in the event that the file is not already in the restore list. The restore list is provided for a restore of the state of data of the root directory at a desired time.

Efficient building of restore list

A system for an efficient data rehydration comprises a server, one or more reader device managers, a writer device manager, and a verifier. The server is for receiving a restore list comprising a plurality of storage locations and lengths for performing a data rehydration. The one or more reader device managers is for reading a data set indicated by the restore list by reading the plurality of storage locations for the lengths from one or more storage nodes. The plurality of storage locations and lengths indicate chunks from a client system stored as part of a full or as an incremental backup session on a storage device attached to a storage node. The writer device manager is for transferring the data set to a save node. A verifier is for verifying transfer of the data set.

Efficient data rehydration

A system for building a restore list includes a processor and a memory. The processor is configured to determine whether a next sibling record includes a directory. The directory is popped from a directory stack. In the event that the next sibling record includes a subdirectory of the directory, the processor is configured to push a directory path associated with the next sibling record onto the directory stack. In the event that the next sibling record does not include a subdirectory, the processor is configured to add the latest index record associated with the latest index record to a restore list. The memory coupled to the processor and configured to provide the processor with instructions.

Growing community of inventors

San Jose, CA, United States of America

Venu Varma