Applying XAM processes

• US 9,727,588 B1
• Filed: 03/29/2010
• Issued: 08/08/2017
• Est. Priority Date: 03/29/2010
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Ostapovicz, Scott R., Wood, Douglas A., Todd, Stephen J., Gupta, Uday K.
• Primary Examiner(s): Robinson, Greta
• Application Number:
  US12/748,566
• Time in Patent Office: 2,689 Days
• Field of Search: 707705, 707707, 707803, 7079991, 707999102, 7079992, 707805, 707812, 707802, 707723, 707726, 707736, 707747, 707748, 707749, 707763, 707949, 707741, 707830, 705 11, 705 711, 705 729, 705 741
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/20 of structured data, e.g. relational data
• CPC Class Codes: G06F 3/0607 by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
• CPC Class Codes: G06F 3/0608 Saving storage space on storage systems
• CPC Class Codes: G06F 3/0647 Migration mechanisms
• CPC Class Codes: G06F 3/0667 at data level, e.g. file, record or object virtualisation
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 3/0686 Libraries, e.g. tape libraries, jukebox

Abstract

A method is used in applying XAM processes. A set of content is received via any of a file system interface, a block based interface, an object based interface to an object addressable data storage system. An object derived from the set of content and having an object identifier is stored in the object addressable data storage system. The object is made available for retrieval via the object based interface using the object identifier.

Claims

1. A method for use in applying XAM processes, the method comprising:

receiving a set of content via one of multiple different interfaces at an object addressable data storage system, wherein the storage system includes a file system interface, a block based interface, and an object based interface, wherein receiving includes attaching metadata to the set of content as it is received via one of the multiple different interfaces at the object addressable data storage system;

converting the set of content received via one of multiple different interfaces, wherein converting includes converting content received via the file system interface into a set of local files and asynchronously converting the local files to an XSet, converting content received via the block based interface into a set of local files and asynchronously converting the local file to an XSet, and content received via the object based interface includes converting the received content into local files in an object store and replicating an XSet as received;

storing, in the object addressable data storage system, an object derived from the set of content received via any of the file system interface, the block based interface, and the object based interface, the object having an object identifier, wherein storing includes unifying the derived object and storing the derived object in a unified object store;

utilizing XAM processes to index the metadata and the derived object from the set of content received via any of the file system interface, the block based interface, and the object based interface;

making the derived object available for retrieval via the object based interface using the object identifier; and

providing a singular, unified view of the metadata and the derived object derived from the set of content received via any of the file system interface, the block based interface, and the object based interface.

2. The method of claim 1, wherein the object addressable data storage system comprises indexed storage using XAM processes.

3. The method of claim 1, wherein the object addressable data storage system uses a unified, canonical format to house content arriving via any of the file system interface, the block based interface, and the object based interface.

4. The method of claim 1, wherein in the object addressable data storage system the set of content can be viewed using a XAM process.

5. The method of claim 1, wherein the set of content is converted to a local file supported by file system software and the local file is converted to an XSet and stored using XAM.

6. The method of claim 1, wherein the set of content is converted to an XSet and path and filename are included in the XSet as nonbinding metadata.

7. The method of claim 1, wherein the set of content is converted to an XSet and replication is applied to the XSet.

8. The method of claim 1, wherein the set of content is converted to an XSet and the XSet is visible through the object based interface.

9. The method of claim 1, wherein the set of content, if received via the object-based interface, is visible only via the object-based interface.

10. A system for use in applying XAM processes, the system comprising a processor and memory configured to:

receive a set of content via one of multiple different interfaces at an object addressable data storage system, wherein the storage system includes a file system interface, a block based interface, and an object based interface, wherein receive included attach metadata to the set of content as it is received via one of the multiple different interfaces at the object addressable data storage system;

convert the set of content received via one of multiple different interfaces, wherein convert includes convert content received via the file system interface into a set of local files and asynchronously converting the local files to an XSet, convert content received via the block based interface into a set of local files and asynchronously convert the local file to an XSet, and content received via the object based interface includes convert the received content into local files in an object store and replicate an XSet as received;

store, in the object addressable data storage system, an object derived from the set of content received via any of the file system interface, the block based interface, and the object based interface, the object having an object identifier, wherein store includes unify the derived object and store the derived object in a unified object store;

utilize XAM processes to index the metadata and the derived object from the set of content received via any of the file system interface, the block based interface, and the object based interface;

make the derived object available for retrieval via the object based interface using the object identifier; and

provide a singular view of the metadata and the object derived from the set of content received via any of the file system interface, the block based interface, and the object based interface.

11. The system of claim 10, wherein the object addressable data storage system comprises indexed storage using XAM processes.

12. The system of claim 10, wherein the object addressable data storage system uses a unified, canonical format to house content arriving via any of the file system interface, the block based interface, and the object based interface.

13. The system of claim 10, wherein in the object addressable data storage system the set of content can be viewed using a XAM process.

14. The system of claim 10, wherein the set of content is converted to a local file supported by file system software and the local file is converted to an XSet and stored using XAM.

15. The system of claim 10, wherein the set of content is converted to an XSet and path and filename are included in the XSet as nonbinding metadata.

16. The system of claim 10, wherein the set of content is converted to an XSet and replication is applied to the XSet.

17. The system of claim 10, wherein the set of content is converted to an XSet and the XSet is visible through the object based interface.

18. The system of claim 10, wherein the set of content, if received via the object-based interface, is visible only via the object-based interface.