Source: http://www.google.fr/patents/US9021198
Timestamp: 2017-11-19 21:51:10
Document Index: 617087410

Matched Legal Cases: ['Application No. 02747883', 'art 1', 'art 2', 'Application No. 2003', 'art 1', 'art 2']

Brevet US9021198 - System and method for sharing SAN storage - Google Brevets
According to various embodiments, systems and methods are provided that relate to shared access to Storage Area Networks (SAN) devices. In one embodiment, a Storage Area Network (SAN) host is provided, comprising: a server component; a first host bus adapter configured to be connected to a SAN client...http://www.google.fr/patents/US9021198?utm_source=gb-gplus-shareBrevet US9021198 - System and method for sharing SAN storage
Numéro de publication US9021198 B1
Numéro de demande US 13/010,694
Date de priorité 20 janv. 2011
Autre référence de publication US9578101, US20150207883, US20160127470, US20170118289
Numéro de publication 010694, 13010694, US 9021198 B1, US 9021198B1, US-B1-9021198, US9021198 B1, US9021198B1
Inventeurs Manoj Kumar Vijayan, Srikant Viswanathan, Deepak Raghunath Attarde, Varghese Devassy, Rajiv Kottomtharayil
Citations de brevets (637), Citations hors brevets (45), Référencé par (5), Classifications (11), Événements juridiques (1)
US 9021198 B1
According to various embodiments, systems and methods are provided that relate to shared access to Storage Area Networks (SAN) devices. In one embodiment, a Storage Area Network (SAN) host is provided, comprising: a server component; a first host bus adapter configured to be connected to a SAN client over a first SAN; a second host bus adapter configured to be connected to a SAN storage device over a second SAN; and wherein the server component is configured to manage a data block on the SAN storage device, receive a storage operation request from the SAN client through the first host bus adapter, and in response to the storage operation request, perform a storage operation on the data block, the storage operation being performed over the second SAN through the second host bus adapter.
1. A Storage Area Network (SAN) host, comprising:
a first host bus adapter configured to be connected to a SAN client over a first SAN;
a second host bus adapter configured to be connected to a SAN storage device over a second SAN; and
wherein the server component is configured to manage a data block on the SAN storage device, provide the SAN client with block access to the data block on the SAN storage device, receive a storage operation request from the SAN client through the first host bus adapter, and in response to the storage operation request, perform a storage operation on the data block, the storage operation being performed over the second SAN through the second host bus adapter.
2. The SAN host of claim 1, wherein the server component is further configured to determine whether the storage operation request is performed as the storage operation.
3. The SAN host of claim 1, wherein the server component is further configured to arbitrate between a plurality of storage operation requests.
4. The SAN host of claim 1, wherein the first host bus adapter connects to the SAN client through the first host bus adapter using Fiber Channel (FC), InfiniBand, or Serial Attached SCSI (SAS).
5. The SAN host of claim 1, wherein the second host bus adapter connects to the SAN storage device through the second host bus adapter using Fiber Channel (FC), InfiniBand, or Serial Attached SCSI (SAS).
6. The SAN host of claim 1, wherein the server component is further configured to perform dynamic provisioning of storage space on the SAN storage device for the SAN client.
7. The SAN host of claim 1, wherein the server component is further configured to provide a plurality of SAN clients with concurrent access to the SAN storage.
8. The SAN host of claim 1, wherein the first host bus adapter is in target mode.
9. The SAN host of claim 1, wherein the second host bus adapter is in initiator mode.
10. The SAN host of claim 1, wherein the server component is further configured to perform data de-duplication on the SAN storage device while performing the storage operation.
11. The SAN host of claim 1, wherein the storage operation is a file read, a file write, a file create, or a file delete operation.
12. The SAN host of claim 1, wherein the storage operation is a discovery request to the system.
13. The SAN host of claim 1, wherein the SAN storage device comprises a plurality of SAN storage devices managed by the server component as a pool of storage resources.
14. The SAN host of claim 13, wherein the server component is further configured to add a new SAN storage device to the pool when the new SAN storage device is added to the second SAN.
15. A method for a Storage Area Network (SAN) host, comprising:
receiving from a SAN client a request to perform a first storage operation on a SAN storage device, wherein the request is received over a first SAN through a first host bus adapter; and
in response to the request, performing a second storage operation on the SAN storage device, wherein the second storage operation is performed over a second SAN through a second host bus adapter;
wherein first host bus adapter and the second host bus adapter are each electronically coupled to a server component, the server component being configured to manage a data block on the SAN storage device and provide the SAN client with block access to the data block on the SAN storage device.
16. The method of claim 15, further comprises arbitrating whether the request is performed as the second storage operation.
17. The method of claim 15, further comprises arbitrating between a plurality of storage operation requests.
18. The method of claim 15, wherein when a plurality of storage operation requests are received, the method further comprises:
detecting a new SAN storage device on the second SAN; and
adding the new SAN storage to a pool of storage resources.
receiving a discovery request from the SAN client; and
transmitting a discovery response to the SAN client, wherein the discovery response represents the SAN host as a traditional SAN storage device.
Network bandwidth is limited and can be overloaded by large volumes of data stored and shared by networked devices. During operations such as system backups, transaction processing, file copying and transfer, and other similar operations, the network communication bandwidth often becomes the rate-limiting factor.
FIG. 1 illustrates an example of a traditional SAN implementation 10. There are multiple client nodes 15, 18, and 21 networked together using a LAN 12, which allows communication of ordinary data traffic between the nodes (15, 18, 21). Storage devices 12 are connected together through SAN 13, which provides high bandwidth network capacity for bandwidth-intensive data operations to and from the storage devices 12. As illustrated, client nodes 18 and 21 are also connected to SAN 13, allowing them high bandwidth data access to the storage devices 12. As discussed above, by utilizing the SAN to perform high bandwidth data access, the client nodes are not only moving bandwidth-intensive data operations from the LAN 19 to the SAN 13, but also accessing the data at higher data rates than are typically available on a traditional network such as LAN. Typically, SANs utilize high bandwidth network technologies, such as Fiber Channel (FC), InfiniBand, Internet Small Computer System Interface (iSCSI), HyperSCSI, and Serial Attached SCSI (SAS), which are not commonly utilized in traditional networks such as LANs.
In one embodiment, a Storage Area Network (SAN) host provided, comprising: a server component; a first host bus adapter configured to be connected to a SAN client over a first SAN; a second host bus adapter configured to be connected to a SAN storage device over a second SAN; and wherein the server component is configured to manage a data block on the SAN storage device, provide the SAN client with block access to the data block on the SAN storage device, receive a storage operation request from the SAN client through the first host bus adapter, and in response to the storage operation request, perform a storage operation on the data block, the storage operation being performed over the second SAN through the second host bus adapter. By providing the block access to the SAN storage device, the SAN host can appear to the SAN client as a locally attached storage device. The SAN client may then access data made available from the SAN storage device by the SAN host as if the SAN client has direct disk access to the SAN storage device.
In some embodiments, the SAN storage device comprises a plurality of SAN storage devices managed by the server component as a pool of storage resources. In some such embodiments. the server component is further configured to add a new SAN storage device to the pool when the new SAN storage device is added to the second SAN.
Additionally, the server component may configured to provide a plurality of SAN clients with concurrent access to the SAN storage. As such, the server component may be configured to arbitrate between a plurality of storage operation requests when they are received, either from a single SAN client or from multiple multiple SAN clients.
In some embodiments, a method for a Storage Area Network (SAN) host is provided, comprising: receiving from a SAN client a request to perform a first storage operation on a SAN storage device, wherein the request is received over a first SAN through a first host bus adapter; and in response to the request, performing a second storage operation on the SAN storage device, wherein the second storage operation is performed over a second SAN through a second host bus adapter. In some such embodiments, the method further comprises: arbitrating between a plurality of storage operation requests. In additional such embodiments, the method further comprises: detecting a new SAN storage device on the second SAN; and adding the new SAN storage to a pool of storage resources. In other such embodiments, the method further comprises: receiving a discovery request from the SAN client; and transmitting a discovery response to the SAN client, wherein the discovery response represents the SAN host as a traditional SAN storage device.
Before describing the invention in detail, it is useful to describe a few example environments with which the invention can be implemented. The systems and methods described herein can be implemented using a number of different storage architectures. One such exemplary storage architecture is described with reference to FIG. 2.
Turning now to FIG. 2, the example storage operation cell 50 shown in FIG. 2 may performs storage operations on electronic data such as that in a computer network. As shown in this example, storage operation cell 50 may generally include a storage manager 100, a data agent 95, a media agent 105, and a storage device 115. The storage operation cell 50 may also include components such as a client 85, a data or information store 90, databases 110 and 111, jobs agent 120, an interface module 125, and a management agent 130. Each media agent 105 may control one or Input/Output (I/O) devices such as a Host Bus Adaptor (HBA) or other communications link for transferring data from client 85 to storage devices 115. Such a system and elements thereof are exemplary of a modular backup system such as the CommVault® QiNetix system, and also the CommVault GALAXY® backup system, available from CommVault Systems, Inc. of Oceanport, N.J., and further described in U.S. Pat. Nos. 7,035,880 and 7,620,710 each of which is incorporated herein by reference in its entirety.
A storage operation cell, such as cell 50, may generally include combinations of hardware and software components associated with performing storage operations on electronic data. Exemplary storage operation cells according to embodiments of the invention may include, CommCells as embodied in the QNet storage management system and the QiNetix storage management system by CommVault Systems of Oceanport, N.J. According to some embodiments of the invention, storage operation cell 50 may be related to backup cells and provide some or all of the functionality of backup cells as described in U.S. Pat. No. 7,395,282, which is also incorporated by reference in its entirety. It should he noted, however, that in certain embodiments, storage operation cells may perform additional types of storage operations and other types of storage management functions that are not generally offered by backup cells.
It should be noted that references herein to data transfers should be understood to involve such storage operations as file creation, file deletion, file read, and file write. Additionally, one of ordinary skill in the art would understand and appreciate that data transfers described herein can be readily facilitated by other means of data operations in addition to just tile operations (such as database operations).
Continuing with reference to FIG. 3, SAN host 206 is shown comprising a first host bus adapter (HBA) 230, which enables connections to SAN clients 218 through the first SAN 203, and a second host bus adapter (HBA) 233, which enables connections to SAN storage devices 221 via the second SAN 209. In the illustrated configuration, the first SAN 203 and the second SAN 209 are isolated from one another, thereby allowing the SAN host 206 to manage and control (e.g., arbitrate) shared access of the SAN storage devices 221 by the SAN clients 218. Both the first host bus adapter 230 and the second host bus adapter 233 could utilize different types of bus technologies to facilitate communication over their respective SANs. For example, either the first host bus adapter 230 or the second host bus adapter 233 may utilize such network technologies as Fiber Channel (FC), InfiniBand, Internet Small Computer System Interface (iSCSI), HyperSCSI, and Serial Attached SCSI (SAS). The first host bus adapter 230 or the second host bus adapter 233 may simply be a traditional network interface, which allows such technologies as Internet Small Computer System Interface (iSCSI), Fiber Channel over Ethernet (FCoE), and ATA over Ethernet (AoE) to be utilized by SAN host 206 over the SANs.
As illustrated, the second SAN 209 connects SAN storage devices 221 together using SAN connections 215, and connects those SAN storage devices 221 to the SAN host 206. Similar to SAN clients 218, the SAN storage devices 221 may control one or more input/output (I/O) devices, such as a HBAs or other communication links, that allow them to connect to the second SAN 209. The SAN storage devices 221 may use, for example, Fiber Channel HBA to connect to the second SAN 209. Using a SAN connection 215, a SAN storage device 221 may, for example, transfer data to and from a SAN client on the second SAN 209 or on another SAN (e.g., first SAN 203). For instance, the SAN storage device 218 may transfer data over the second SAN 209 to the second SAN 209 via the illustrated SAN host 206.
The SAN host 206 may also function as a manager of storage operations, managing the blocks of data on one or more SAN storage devices. As manager, the SAN host 206 may also manage what storage operations are to be performed on SAN storage devices in response to a storage operation request from a SAN client. For example, SAN host 206 may include components that allow it to determine whether a storage operation should be performed on the SAN storage devices, and when a storage operation should be performed on the SAN storage devices. This management functionality may be utilized when, for example, two or more SAN clients are sharing access to a shared SAN storage device, and the SAN clients request concurrent access to the shared SAN storage device or pool. concurrent access to the same data on the shared SAN storage device, or concurrent access to the same allocation of storage space on the shared SAN storage. In further examples, this concurrent access may be to a pool of SAN storage devices rather than just a single SAN storage device. As such, the SAN host 206 may allow for concurrent shared access to one or more SAN storages devices while preventing deadlocks.
Additionally, as part of data management functionality, the SAN host 206 may function to track and maintain one or more SAN storage devices as a pool of (SAN) storage resources (i.e., storage pool). In doing so, SAN host 206 may be allowed to, for example, dynamically provision (i.e. allocate) storage space from the pool for a given SAN client. For example, if the SAN host 206 were managing a pool of SAN storage resources totaling 5 TB in free space, and three SAN clients request 1 TB each of storage space, rather than statically reserving 1 TB of space within the pool to each of the SAN clients, the SAN host 206 can make a dynamic allocation of 1 TB to each of the SAN clients. In doing so, the SAN host is capable of growing a SAN client's storage space allocation as requested (i.e., on-demand).
Further, by managing the SAN storage devices as a pool of SAN storage resources, the SAN host 206 can readily manage the addition of new SAN storage devices to the pool, thereby allowing the pool to grow dynamically. Specifically, the storage pool may allows the SAN host 206 to dynamically add or remove one or more SAN storage devices (e.g., 221) from the pool, thereby increasing or decreasing the overall pool size, at times without the SAN clients even being made aware of such changes. It should be noted that, for some embodiments, the SAN host 206 is capable of managing and presenting dynamically allocated storage spaces as Logical Unit Numbers (LUNs).
In some embodiments, the dynamic (e.g., on-demand) provisioning (i.e., allocation) of storage space on the pool of SAN storage resources and the tracking and maintenance of the pool may be tied into the managment function. For example, if a SAN client is writing to the shared pool of SAN storage resources and the pool reaches its capacity, the arbitrator could deny performance of the SAN client's storage write request.
In some embodiments, the SAN host 206 may manage the pool of SAN storage resources by way of a data repository (i.e., data store), which assists in the tracking and maintenance of the pool (e.g., tracking free storage space, tracking occupied storage space) and the allocation of storage space to SAN clients. In the illustrated embodiment, the tracking and maintenance of the pool of SAN storage resources (and, thus, the SAN storage devices 221) by the SAN host 206 is facilitated through data repository 236. Depending on the embodiment, the data repository 206 may be implemented as a data store, such as a database. Additionally, SAN host 206 may utilize the data repository 206 to manage data blocks within the storage pool. For example, management of data block may entail tracking ownership of data blocks to specific SAN clients, tracking storage of file data blocks that span multiple SAN storage devices (e.g., 221), tracking assignment of data blocks to specific allocated storage space, tracking occupied storage space within the storage pool, and tracking free storage space within the storage pool.
Through data repository 236, SAN host 206 can not only track dynamic provisioning and allocation of storage space within the storage pool to individual computing devices but, depending on the embodiment, can also dynamically add and remove SAN storage devices 221 from the storage pool. For example, when new SAN storage device 242 is added 245 to the second SAN 209, the SAN host 206 can add the new SAN storage device 242 to the its storage pool. In some such embodiments, the SAN host 206 may perform the discovery and addition of the SAN storage device 242 to the pool automatically upon the addition of the SAN storage device 242 to the second SAN 209. For example, SAN host 206 may be configured to actively monitor the second SAN 209 for the addition of any new SAN storage devices, and add any such SAN storage device to the storage pool.
In some embodiments, the server component 227 may also be configured to implement data de-duplication operations on the SAN storage devices 221, thereby increasing the over storage capacity of the SAN storage devices 221. For example, in particular embodiments, the data de-duplication may be implemented in the server component 227 such that de-duplication is transparent to the SAN clients 218 jointly accessing the SAN storage devices 218. According to one embodiment, the de-duplication may be facilitated through a hash table or other reference table that resides on the SAN host 206. The table references data that is shared amongst the SAN storage devices 221 managed by the SAN host 206. When the SAN host 206 is transferring data to the SAN storage devices 221, the SAN host 206 can use the table in a deduplication algorithm to determine if a data segment already exists on a SAN storage device 221. When it determines a copy already exists, the SAN host 206 may use the reference to an allocation of an existing copy of the data segment in place of the actual segment of data. Other de-duplication methodologies may be also employed by SAN host 206.
In some embodiments. when a client has data to transfer to or place in the shared storage, that client can run a deduplication algorithm on segments of the data and use its own representative instantiation of the reference table to determine whether the data segments already exist in a shared data store. Accordingly, for a given segment, the client can determine whether to send the entire data segment to the shared storage or just send a reference or pointer or other information from the reference table if the segment is duplicative of what is already in the data store. In a situation where the analyzed segment is not in the data store, the client device can send the hash value or other reference table information to the central storage (or other location maintaining the main reference table) so that the primary reference table can be updated with the information on the newly added segment.
FIG. 4 provides an example sequence of interactions 300 between entities of a SAN in accordance with one embodiment of the present invention. Turning now to FIG. 4, the sequence begins with the establishment 312 of a Storage Area Network (SAN) connection between a SAN client 303 and a SAN host 306 over a first SAN, and the establishment 315 of a SAN connection between the SAN host 306 and a SAN storage device 309 over a second SAN. Once the connections are established, SAN client 303 performs a storage operation through an API function call. In some embodiments, the function call 321 instructs a client component residing on the SAN client 303 to transmit 324 to the SAN host 306 a storage operation request corresponding to the API function call 321. The client component thereby performs a storage operation request on behalf of the SAN client 303. Additionally, by instructing the client component through the API function call 321, the interactions between the SAN client 303 and SAN host 306 are encapsulated by the API. This eases integration of some embodiments into existing SANs.
Returning to FIG. 2, in some embodiments, the system 200 of FIG. 3 may be implemented into storage operation cell 50 of FIG. 2. For example, in one embodiment, system 200 could be implemented such that: the client 85 would operate as one of the SAN clients 218 of FIG. 3; the data agent 95 would operate as the client component that interfaces with SAN host 206 over a first SAN; the storage manager 100, media agents 105, and host bus adapters (HBAs) 133 would collectively operate as SAN host 206 of FIG. 3, where the storage manager 100 in conjunction with the media agents 105 would operate as the server component 227 of FIG. 3, and the HBAs 133 would operate as multiple second host bus adapters (233) of FIG. 3; and storage devices 115 would operate as the SAN storage devices communicating with the HBAs 133 over a second SAN.
Turning now to FIG. 5A, method 400 begins as operation 403 with a SAN client (e.g., 218, 303) performing a discovery function call through an API. This causes the SAN client to send a discovery request to a SAN host at operation 406. Depending on the embodiment, when the discovery function call is executed in operation 403, the API may instruct a client component residing on the SAN client to transmit a discovery request to the SAN host in operation 406.
As used herein, the term module might describe a given unit of functionality that can be performed in accordance with one or more embodiments of the present invention. As used herein, a module might be implemented utilizing any form of hardware, software, or a combination thereof. For example, one or more processors, controllers, ASICs, PLAs, logical components, software routines or other mechanisms might be implemented to make up a module. In implementation, the various modules described herein might be implemented as discrete modules or the functions and features described can be shared in part in total among one or more modules. In other words, as would be apparent to one of ordinary skill in the art after reading this description, the various features and functionality described herein may be implemented in any given application and can be implemented in one or more separate or shared modules in various combinations and permutations. Even though various features or elements of functionality may be individually described or claimed as separate modules, one of ordinary skill in the art will understand that these features and functionality can be shared among one or more common software and hardware elements, and such description shall not require or imply that separate hardware or software components are used to implement such features or functionality.
US5163048 27 mars 1990 10 nov. 1992 U.S. Philips Corp. Two-wire extended serial bus communications system with collective echoing of data transmitted from peripheral stations
US6740933 13 sept. 2002 25 mai 2004 Samsung Electronics Co., Ltd. Semiconductor device having trench isolation structure and method of fabricating the same
US8603646 2 mars 2011 10 déc. 2013 Cheil Industries, Inc. Pyrrole compound and organic photoelectric device including the same
US20030212752 * 8 mai 2002 13 nov. 2003 Thunquest Gary Lee Mehthod and apparatus for supporting snapshots with direct I/O in a storage area network
US20040133915 * 7 nov. 2003 8 juil. 2004 Moody William H. System and method for controlling access to media libraries
US20040181476 * 13 mars 2003 16 sept. 2004 Smith William R. Dynamic network resource brokering
US20080115144 * 14 janv. 2008 15 mai 2008 Stt Webos, Inc. Method and Apparatus for Web Based Storage on Demand
US20080244055 * 14 janv. 2008 2 oct. 2008 Hitachi, Ltd. Computer that manages devices
US20090150608 * 9 févr. 2009 11 juin 2009 Masataka Innan Storage system and operation method of storage system
US20090282135 * 8 mai 2008 12 nov. 2009 Vinodh Ravindran Hba boot using network stored information
US20120059800 * 3 sept. 2010 8 mars 2012 Fanglu Guo System and method for scalable reference management in a deduplication based storage system
US20130056807 27 août 2012 7 mars 2013 Canon Kabushiki Kaisha Photoelectric converting apparatus
US20130262615 * 11 mars 2013 3 oct. 2013 Commvault Systems, Inc. Shared network-available storage that permits concurrent data access
US20140250123 6 mars 2014 4 sept. 2014 Commvault Systems, Inc. Interface systems and methods for accessing stored data
EP0381651A2 25 janv. 1990 8 août 1990 International Business Machines Corporation Managing method and apparatus for data storage
EP0599466A1 5 oct. 1993 1 juin 1994 Sony Corporation Apparatus and methods for managing picture data
EP0910019A2 31 juil. 1998 21 avr. 1999 International Computers Ltd. Remote backup system
EP1035690A2 6 mars 2000 13 sept. 2000 Sun Microsystems, Inc. E-mail archiving
GB2216368A Titre non disponible
JPH0746271Y2 Titre non disponible
WO2001016693A2 31 août 2000 8 mars 2001 Shutterfly, Inc. Multi-tier data storage and archiving system
WO2001080005A2 10 avr. 2001 25 oct. 2001 Gnp Computers, Inc. Distributed computing system clustering model providing soft real-time responsiveness and continuous availability
WO2005050381A2 15 nov. 2004 2 juin 2005 Commvault Systems, Inc. Systems and methods for performing storage operations using network attached storage
5 Cabrera, et al. "ADSM: A Multi-Platform, Scalable, Back-up and Archive Mass Storage System," Digest of Papers, Compcon '95, Proceedings of the 40th IEEE Computer Society International Conference, Mar. 5-Mar. 9, 1995, pp. 420-427, San Francisco, CA.
6 Catapult, Inc. Microsoft Outlook 2000 Step by Step, Published May 7, 1999, Collaborating with Others Using Outlook & Exchange, p. 8 including "Message Timeline.".
29 Microsoft Press Computer Dictionary Third Edition, "Data Compression," Microsoft Press, 1997, p. 130.
31 Office Action in European Application No. 02747883.3 dated Jul. 7, 2014.
32 Pitoura al., "Objects in Mobile Computing", IEEE Transactions on Knowledge and Data Engineering, vol. 13, No. 4, Jul.- Aug. 2001, pp. 571-592.
34 Rowe et al., "Indexes for User Access to Large Video Databases", Storage and Retrieval for Image and Video Databases II, IS, & T/SPIE Symp. On Elec. Imaging Sci. & Tech., Feb. 1994, pp. 1-12.
37 Swift et al., "Improving the Reliability of Commodity Operating Systems" ACM 2003.
38 Szor, The Art of Virus Research and Defense, Symantec Press (2005) ISBN 0-321-30454-3, Part 1.
39 Szor, The Art of Virus Research and Defense, Symantec Press (2005) ISBN 0-321-30454-3, Part 2.
40 Translation of Japanese Office Action dated Jul. 15, 2008, Application No. 2003/502696.
42 Veeravalli, B., "Network Caching Strategies for a Shared Data Distribution for a Predefined Service Demand Sequence," IEEE Transactions on Knowledge and Data Engineering, vol. 15, No. 6, Nov.-Dec. 2003, pp. 1487-1497.
43 Weatherspoon H. et al., "Silverback: A Global-Scale Archival System," Mar. 2001, pp. 1-15.
44 Witten et al., Data Mining: Practical Machine Learning Tools and Techniques, Ian H. Witten & Eibe Frank, Elsevier (2005) ISBN 0-12-088407-0, Part 1.
45 Witten et al., Data Mining: Practical Machine Learning Tools and Techniques, Ian H. Witten & Eibe Frank, Elsevier (2005) ISBN 0-12-088407-0, Part 2.
US9547429 * 28 mai 2013 17 janv. 2017 Ca, Inc. Visualized storage provisioning
US9729634 * 26 févr. 2016 8 août 2017 Google Inc. Isolating clients of distributed storage systems
US20160182637 * 26 févr. 2016 23 juin 2016 Google Inc. Isolating Clients of Distributed Storage Systems
Classification aux États-Unis 711/112, 711/E12.002
Classification internationale G06F3/06, G06F12/00
Classification coopérative G06F13/426, G06F3/0641, G06F3/0619, G06F3/064, G06F3/067, H04L67/1097, G06F3/061
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VIJAYAN, MANOJ KUMAR;VISWANATHAN, SRIKANT;ATTARDE, DEEPAK RAGHUNATH;AND OTHERS;SIGNING DATES FROM 20110322 TO 20110330;REEL/FRAME:026063/0979