A method is used in managing storage operations in a data storage environment. An I/O request is received a server having a server cache where the server cache contains cached data previously supplied from a storage system in communication with the server. At the storage system, determine if the I/O request can be at least partially satisfied from the cached data.
Legal claims defining the scope of protection, as filed with the USPTO.
1. A method for use in managing storage operations in a data storage environment, the method comprising: receiving an I/O request at a server having a server cache, the server cache containing cached data previously supplied from a storage system in communication with the server, wherein the cached data includes a first and second storage object, wherein the first and second storage objects are stored in memory spaces corresponding to different virtual machine clients and the second storage object is a pointer to the first storage object; providing logical storage space corresponding to each virtual machine client, wherein logical storage space associated with a second virtual machine is a pointer to logical space associated with a first virtual machine; at the storage system, determining that data associated with the I/O request is data that has been replicated and that the I/O request can be at least partially satisfied from the cached data; determining that the data associated with the I/O request is a pointer to non-replicated data; returning the pointer to the server cache; and storing the pointer in the server cache such that the I/O request can be satisfied by the server cache.
2. The method of claim 1 , further including instructing the server to add a flag to the I/O request.
3. The method of claim 2 , wherein the flag indicates that the data associated with the I/O request is being stored in the server cache.
4. The method of claim 1 , further including: evicting data associated with the I/O request from the server cache; and sending an indicator to the storage system indicating that the data has been evicted.
5. The method of claim 1 , further including instructing the storage system to send an indicator to the server indicating that the data associated with the I/O request is to be stored in the server cache.
6. The method of claim 1 , further including identify, at the storage system, data to be stored in the server cache and data to be evicted from the server cache.
7. The method of claim 1 , wherein the information indicative of a location where the replicated data object is stored is a pointer to a location storing contents of the data object.
8. The method of claim 1 , wherein data associated with the I/O request is stored according to at least one of a file, object, or block access protocol.
9. The method of claim 1 , wherein the I/O operation is a read request.
10. The method of claim 1 , wherein the server is a virtual server and the data storage system is a virtual data storage system.
11. A system for use in managing storage operations in a data storage environment, the system comprising: first logic configured to receive an I/O request at a server having a server cache, the server cache containing cached data previously supplied from a storage system in communication with the server, wherein the cached data includes first and second storage objects, wherein the first and second storage objects are stored in memory spaces corresponding to different virtual machine clients and the second storage object is a pointer to the first storage object; second logic configured to provide logical storage space corresponding to each virtual machine client, wherein logical storage space associated with a second virtual machine is a pointer to logical space associated with a first virtual machine and determine, at the storage system, that data associated with the I/O request is data that has been replicated and that the I/O request can be at least partially satisfied from the cached data, wherein the second logic is further configured to determine that the data associated with the I/O request is a pointer to non-replicated data; third logic configured to return the pointer to the server cache; and fourth logic configured to store the pointer in the server cache such that the I/O request can be satisfied by the server cache.
12. The system of claim 11 , wherein the first logic is further configured to instruct the server to add a flag to the I/O request.
13. The system of claim 12 , wherein the flag indicates that the data associated with the I/O request is to be stored in the server cache.
14. The system of claim 11 , wherein the first logic is further configured to: evict data associated with the I/O request from the server cache; and send, an indicator to the storage system indicating that the data has been evicted.
15. The system of claim 11 , wherein the second logic is further configured to send an indicator to the server indicating that the data associated with the I/O request is to be stored in the server cache.
16. The system of claim 11 , further including fifth logic configured to identify data to be stored in the server cache and data to be evicted from the server cache.
17. The system of claim 11 , wherein the information indicative of a location where the replicated data object is stored is a pointer to a location storing contents of the data object.
18. The system of claim 11 , wherein data associated with the I/O request is stored according to at least one of a file, object, or block access protocol.
19. The system of claim 11 , wherein the I/O operation is a read request.
20. The system of claim 11 , wherein the server is a virtual server and the data storage system is a virtual data storage system.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
December 30, 2011
December 2, 2014
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.