EP1540498A2 - Apparatus and method for proxy cache - Google Patents
Apparatus and method for proxy cacheInfo
- Publication number
- EP1540498A2 EP1540498A2 EP03752475A EP03752475A EP1540498A2 EP 1540498 A2 EP1540498 A2 EP 1540498A2 EP 03752475 A EP03752475 A EP 03752475A EP 03752475 A EP03752475 A EP 03752475A EP 1540498 A2 EP1540498 A2 EP 1540498A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- file
- data
- client
- cache
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
- H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
Definitions
- Embodiments of the present invention relate generally to computer networks. More particularly, embodiments of the present invention relate generally to file systems and storage devices .
- LANs local area networks
- large organizations may also have smaller remote offices, branch offices, or/and other edge locations that have lower bandwidth and higher latency connectivity to the centralized data repositories.
- the edge locations may not have information technology (IT) staffs to service local data needs such as, for example, backing up the servers or replacing failing hardware and/or software.
- IT information technology
- Sharing data across large sites is also cumbersome. These sites are usually connected by dedicated high bandwidth links. However, the geographical distances between sites impose latencies that are unacceptable for many applications.
- the current solution is to provide a file server (such as a filer from Network Appliance, Inc.) at each edge location and automatically back up the server to a central location over the wide area network (WAN) .
- a file server such as a filer from Network Appliance, Inc.
- Read-only data that is shared across sites can be replicated by using asynchronous mirroring.
- Hypertext Transfer Protocol (HTTP) and streaming traffic can be cached using a network cache such as, for example, the NetCache appliance from Network Appliance, Inc.
- Managing file servers at edge locations can be expensive in terms of cost and/or resource .
- the task of backing up data across WANs requires careful planning and administration. Replicating read-only volumes across WANs is often an overkill.
- the invention provides an apparatus for caching data in a network, with the apparatus including a proxy cache configured to receive request for an object from a client and to fetch data blocks from a server.
- the proxy cache may be configured to cache the data blocks in a hierarchical relationship within the object.
- the object may be, for example, a data file, a directory, or a part of a data file such as a data block.
- the data blocks that are cached in the proxy cache define an active data set which is based upon a request from a client .
- Figure 1A is a block diagram of an apparatus in accordance with an embodiment of the invention.
- Figure IB is a block diagram of a proxy cache in accordance with an embodiment of the invention.
- Figure 1C is a block diagram illustrating a cache hit operation and a cache miss operation.
- Figure 2 is a block diagram illustrating a method of managing the active data set by use of an aging scheme or importance scheme, in accordance with an embodiment of the invention.
- FIG. 3 is a block diagram illustrating other methods for managing the active data set, in accordance with embodiments of the invention.
- Figure 4 is a block diagram of a file handle.
- Figure 5 is a block diagram illustrating example volumes in each server.
- Figure 6 is a block diagram illustrating a mapping of FS ⁇ d values for each volume in a particular server, in accordance with an embodiment of the invention.
- FIG. 7 is a block diagram of a network system including multiple proxy caches with identical mapped file handles, in accordance with an embodiment of the invention.
- Figure 8A is a block diagram illustrating a local directory for permitting a virtual name space, in accordance with an embodiment of the invention.
- Figure 8B is a block diagram illustrating a method of creating multiple mount points where a set of attributes are associated with a mount point.
- Figures 8C, 8D, and 8E are block diagrams of a method to provide consistency in cached data.
- Figure 9 is a block diagram illustrating the pre-fetching or pre-verification of attributes for data in a server, in accordance with an embodiment of the invention.
- Figure 10 is a block diagram illustrating components in a proxy cache for performing the pre-verification access, in accordance with an embodiment of the invention.
- Figure 11 is a block diagram illustrating a method of historical linking of verified objects, in accordance with an embodiment of the invention.
- Figure 12 is a block diagram, where a link is broken in response to a change in an attribute of an object, in accordance with an embodiment of the invention.
- Figure 13 illustrates a network system including a client, a proxy cache, and a server, for purposes of describing a cache hit condition in response to CIFS traffic from the client, in accordance with an embodiment of the invention.
- Figure 14 is a block diagram illustrating the operation for a CIFS request that results in a cache miss condition in the proxy cache, in accordance with an embodiment of the invention.
- Figure 15 is a block diagram illustrating the operation for an NFS request that results in a cache miss condition in the proxy cache, in accordance with an embodiment of the invention.
- Figure 16 is block diagram illustrating a network in accordance with an embodiment of the invention for purposes of describing a delay write operation.
- Figure 17 illustrates an embodiment of a proxy cache configured to cache an active data set that includes cached copies of particular logical copies of data in pre-determined memory area of the server.
- Figure 18 is a block diagram of a system for providing data coherency, in accordance with an embodiment of the invention.
- Figure 19 illustrates a block diagram including multiple proxy caches in a cluster configuration, in accordance with an embodiment of the invention.
- Figure 20 is a block diagram of a network, including clients, proxy caches, and a server arranged in a reverse proxy configuration, in accordance with an embodiment of the invention.
- Figure 21 shows a block diagram of a network 300, where only a single proxy cache 205(1) is coupled to the server 210 in the reverse proxy configuration.
- Figure 22 is a block diagram of a network 2400 in accordance with another embodiment of the invention.
- Figure 23 is a block diagram of a network 2500 in accordance with another embodiment of the invention.
- Figure 1A is a block diagram of a network 100, including client devices 105(1) to 105 (n) , servers 110(1) to 110 (m) , and a proxy cache (or proxy appliance) 115, with the components forming a forward proxy configuration in accordance with an embodiment of the invention.
- another embodiment of the invention provides a network including at least one proxy cache in a reverse proxy configuration.
- Embodiments of the invention include or provide at least some of the following features, as described below: (1) location independence and consolidation of name space; (2) on-demand sparse consistent replication of data; (3) load balancing; (4) remote disconnected access and modification of data; and/or (5) protocol transformation.
- n and m may be any suitable integer value.
- the number of client devices generally referred herein as client (s) 105) and the number of servers (generally referred herein as server(s) 110) may vary.
- the network 100 may be implemented with only one client device 105 and/or with only one server 110.
- the client devices 105 may be coupled via local area network (LAN) 120 to the proxy cache 115, while the servers 110 may be coupled via wide area network (WAN) 125 to the proxy cache 115.
- LAN local area network
- WAN wide area network
- the forward proxy configuration in Figure 1A permits data to be cached on-demand by the proxy cache 115.
- on-demand sparse consistent replication of data is permitted by the proxy cache 115.
- This on-demand caching operation is more efficient than conventional replication techniques and advantageously does not require the special software that is used in conventional replication techniques.
- the proxy cache 115 and client devices 105 can communicate with each other via LAN 120 by use of an open standard protocol 130, such as the Network File System (NFS) protocol. As described below, the open standard protocol 130 may also be other suitable open standard protocols such as the Common Internet File System (CIFS) protocol.
- the proxy cache 115 and servers 110 can communicate with each other via Wide Area Network (WAN) 125 by use of an open standard protocol 135, such as NFS.
- WAN Wide Area Network
- NFS Wide Area Network
- the clients 105 can now be heterogeneous by use of an open standard protocol such as NFS.
- the term heterogeneous clients means that clients from different manufacturers or vendors can be advantageously used. The clients will not require specialized software in order to communicate with the servers 110.
- a proxy cache 115 permits low overhead and cost with respect to network administration. Also, the proxy cache 115 may be administered or installed from a location remote from a server 110 or a client 105 in the network 100.
- the proxy cache 115 can identify the servers 110 and clients 105 that are coupled to the proxy cache 115 and the particular data files that are in the servers 110.
- the proxy cache 115 In the event of a cache hit, the proxy cache 115 will transmit the requested data to the requesting client 105. In the event of a cache miss, the proxy cache 115 will request the data from a server 110 and then provide the data to the requesting client 105. The data from the server 110 will be cached as an active data set 140 in the proxy cache 115 and is immediately available to the other clients 105.
- An active data set is an attribute of clients and their applications, and is cached data with reference for a given time period (or window of time) . Thus, the active data set can differ depending on the given time period (e.g., an active data set for a given time period of 2 minutes may differ for an active data set for a given time period of 1 day or 1 week) .
- the proxy cache 115 permits collaborative sharing of cached copies of data among the clients 105.
- the collaborative sharing situation assumes that a particular data requested from the server 110 by a client 105 will also be likely requested by at least another client 105.
- the proxy cache 115 will cache an active data set 140, which is a set of recently requested or frequently requested data that has not been flushed from the proxy cache 115.
- the active data set 140 will be a subset of the data stored in the server (s) 110.
- the read request 145 is received by the proxy cache 115 which checks if the particular part (e.g., data block) of that file or folder is cached locally in the proxy cache 115. If the requested particular data file is in the active data set 140, then a cache hit condition occurs, and the proxy cache 115 will transmit the requested data via LAN 120 to the requesting client device 105.
- the proxy cache 115 will send a request 155 to a server 110 to provide a copy of the missing data block in the requested data file.
- the cached file remains as part of the active data set 140, until the file is replaced in the active data set 140 by a suitable replacement strategy (such as, for example, a first-in-first-out management of data or the least recently used, LRU, algorithm) .
- a suitable replacement strategy such as, for example, a first-in-first-out management of data or the least recently used, LRU, algorithm
- other data replacement strategies may be used with respect to management of the active data set 140, in an embodiment of the invention.
- a file may be designated for permanent storage until a user of the client 105 issues a command to delete (flush) the file from the active data set 140.
- FIG. IB is a block diagram of a proxy cache 115 in accordance with one embodiment of the invention.
- the proxy cache 115 includes a network interface 161, a naming virtualization layer 162, an NFS service 163 and/or CIFS service 164 (and/or or other service) for parsing IP-based network traffic (or other types of traffic for fiber channel, storage area network or the like) , a local access layer 165, an NFS fill engine 166 and/or CIFS fill engine 167 and/or other suitable types of fill engines, a remote fills layer 168, a file system layer 169 (e.g., write-anywhere- file-layout or WAFL) , a storage device manager 170 (such a Redundant Array Of Independent (or Inexpensive) Disks layer, i.e., a RAID layer), and storage disk(s) 171.
- a network interface 161 includes a network interface 161, a naming virtualization layer 162, an NFS service 163 and/
- the network interface 161 includes components for receiving storage-related service requests from a client 105.
- a file system can logically organize information as a hierarchical structure of directories and files on the storage devices (e.g., disks).
- Each file (on the disks) may be implemented as a set of disk blocks configured to store information, such as text, whereas the directory may be implemented as a specially-formatted file in which information about other files and directories are stored.
- the storage device manager 170 manages the storage devices 171 in a storage system.
- the storage device manager 170 receives read and write commands from the file system 169 and processes the commands by accordingly accessing the storage system.
- the storage device manager 170 takes a block's logical address from the file system 169 and translates that logical address to a physical address in one or more storage devices 171 in storage system.
- the storage device manager 170 manages storage devices in accordance with RAID (Redundant Array of Independent, or Inexpensive, Disks) .
- RAID Redundant Array of Independent, or Inexpensive, Disks
- disk storage is typically implemented as one or more storage "volumes" that is formed by physical storage disks, defining an overall logical arrangement of storage space.
- Each volume is typically associated with its own file system, and the terms, volume and file system, will generally be used synonymously.
- the disks within a volume may be typically organized as one or more groups of RAID.
- a file handle is used to name an object such as a file in a file system, and is described in additional detail below in with reference to Figure 4.
- IP Internet Protocol
- the algorithm for computing the unique name is the MD5 hash algorithm, which takes a message and converts it into a fixed string of digits, also called a message digest. It is also noted that the NFS service layer 163 or the CIFS service layer 164 serves the function of parsing the request 172, depending on whether the request is an NFS request or CIFS request.
- the file system layer 169 will perform a lookup function in order to obtain a local cache file ID 183.
- a module 184 in the file system 169 can perform this lookup function. If there is no matching local cache file ID, then a cache miss occurs, which is described further below.
- the local cache file ID 183 is an index into an inode file 185 that points to an appropriate inode record 186.
- the inode record for an inode file 105 contains information describing the inode file associated with a given file system.
- an inode record is a data structure used to store information, such as metadata (attributes) , about a file, whereas the file data blocks are structures used to store the actual data for the file.
- the information contained in an inode record may include, e.g., ownership of the file, access permission for the file, size of the file, file type and references to locations on disk of the data blocks for the file.
- the inode record 186 for the inode file 185 contains a pointer to a file system data block (e.g., WAFL data block), generally referenced as 188.
- a file data block is defined as a minimum addressable amount of data handled by the file system.
- a file data block is capable of storing, for example, 4 kilobytes (KB) of data.
- the inode record 186 can also point to indirect blocks which in turn can point to other file data blocks or other indirect blocks.
- the indirect block 188d points to blocks 189a, 189b, and 189c, each of which may be file data blocks or indirect blocks .
- the inode numbers 187 in an inode record 186 points to the file data blocks or indirect blocks. It is also noted that an inode record 186 also includes attributes 190 of a file stored locally in the proxy cache 115. It is further noted that in one embodiment, the local cache file ID 183 is also an index into a second inode file 192 that points to an appropriate inode record 193 that contains server-side attributes for a file. Server-side attributes can include, for example, file system ID, file ID, block size, number of hard links, and space available on the file system. Of course, the second inode file 192 can be combined with the inode file 185. By creating the second inode file 192, the first inode file 185 will advantageously not require modification to perform some of the functions described with reference to Figure IC.
- an inode record includes a file buffer tree which is a data structure used to represent a file on a disk in a file system.
- the file buffer tree 191 is formed by the block numbers 187 and the blocks 188 and 189.
- An iovector 194 is then formed, where the iovector is a list of block numbers 187 in the file buffer tree 191.
- a block number 187 will indicate if a file data block is present or absent for a particular file.
- a module 195 can form the iovector 194 and determine the presence or absence of a file data block.
- a block number 187 will have a special value X (where X can be, e.g., -1 or -3) as shown by block number 187a, where the special value X indicates that the local cache file stored in the proxy cache 115 does not have a requested data block.
- a block number will not have the special value X, and the iovector is sent to the storage device manager 170 (e.g., a RAID layer).
- the storage device manager 170 e.g., a RAID layer.
- the requesting client 105 can, therefore, receive the requested file.
- the method described above can also be used to process requests for directories .
- the special value X in the list of block numbers permits the tracking of buffers (in the storage devices) in the proxy cache with missing data blocks for a requested file and thus permits the tracking of sparse data.
- the level of indirection permits a file handle to point to a different slot in the inode file, depending on the particular time, since a data block or cache file may be flushed from the proxy cache 115.
- a cache miss condition is triggered.
- a cache miss condition is triggered if a matching file ID 183 is not found by the file system 169 when performing the table lookup function after computing the unique name 182.
- the NFS fill engine 166 for an NFS request 196 (or CIFS fill engine for a CIFS request) will request the absent file data block from the server 110 with the data block.
- the absent file data block is shown as dashed box 188c. The request is sent by use of the server file handle, "FILEl ON SERVER1" , in the example above.
- the file data block is fetched (197) by the NFS fill engine 166 from the server 110, the data block is filled into the storage disk 171 by the remote fills layer 168, file system 169, and storage device manager 170.
- the block numbers in the buffer tree 191 is then updated and a file data block is allocated.
- the file data blocks are then sent to the requesting client 105 so that the requested file is provided to the client.
- the method described above can also be used to process requests for directories .
- FIG. IC permits sparse caching of file data blocks in a buffer tree within one file. This method advantageously permits partial file operations to be performed such as truncating operations or write operations in the middle of the file.
- a client 105 sends a request in the NFS protocol, a separate request is made for each data block. It is also noted that a separate request in the CIFS protocol is made for each data block.
- a first client 105 e.g., client 105(1) in Figure 1
- a request for data in data blocks 188a and 188b which are both cached in the proxy cache 115 in the example of Figure IC. It is noted that the number of request for data from a client may vary.
- a second client 105 (e.g., client 105(2) in Figure 1) sends a request for data in data blocks 188a, 188b, and 188c.
- the data blocks 188a and 188b are cached in the proxy cache 115 when the client requests were received by the proxy cache 115, while the data block 188c is absent from the proxy cache 115.
- the proxy cache 115 will fetch the data block 188c from a server 110, as similarly described above.
- the fetched data block 188c is allocated in the proxy cache 115 and then transmitted to the requesting client 105(2) by the proxy cache 115.
- another client 105 sends a request for data in data blocks 188b and 188c. Since data block 188c was previously fetched by the proxy cache 115 from a server 110 and allocated in proxy cache 115, the data blocks 188b and 188c are present in the proxy cache 115 when the client requests were received by the proxy cache 115. As a result, a cache hit condition is triggered, and the requested data blocks 188b and 188c are transmitted to the requesting client 105(1) by the proxy cache 115.
- the proxy cache 115 can fetch the absent data block 188 from a server 110 and cache the fetched data block 188 before sending the fetched data block 188 to the requesting client 105.
- replication of a partial object occurs in the proxy cache 115 in response to a client request, where a partial object is defined as one or more blocks of data of a file.
- the data block 188c was replicated in the proxy cache 115 in response to a client request and is subsequently available to other requesting clients 105.
- suitable data replacement policies may be used to flush (from the proxy cache 115) a data block 188 or a file defined by multiple data blocks 188.
- currently known replication techniques replicate entire files (e.g., entire volumes or entire sets of files are replicated in various mirroring techniques) .
- FIG. 2 is a graph 200 which illustrates a method of increasing the importance of cached data in the active data set 140 based upon the number of access or request for the cached data from a client (s) 105.
- the proxy cache 115 can be configured to dynamically assign and adjust an "importance" value to a cached data in the active data set 140 based upon the number of access or request for the cached data from a client 105. As the number of access or request to the cached data increases, the proxy cache 115 will increase the importance value of the cached data.
- a cached data in the active data set may be prevented from being flushed from the storage unit of the proxy cache 115 if, for example, the cached data attains an importance value Y (as graphically shown by point 205 in the graph of Figure 2) . It is noted that the function 206 in Figure 2 may have other graphical shapes such as a linear graph.
- FIG. 3 is a block diagram illustrating other methods 300 for managing the active data set 140, in accordance with embodiments of the invention.
- an active data set 140 may be replaced or flushed from the proxy cache 115 by a suitable method such as first-in-first-out (FIFO) method 305.
- FIFO first-in-first-out
- Other suitable replacement policies may be used such as the Least Recently Used (LRU) method.
- LRU refers to a replacement method, typically used in database management systems, where the block that has not been used for the longest time is the first to be replaced.
- a file in the active data set 150 may be locked (310) by a user by sending a lock command to the proxy cache 115 from a client 105, so that the lock command prevents the file from being deleted in the proxy cache.
- the user may send a lock command if, for example, the user is concerned that the link connection to a server 110 may be broken or that the server 110 may fail.
- an attribute (metadata) of an object e.g., file or data block of a file
- the user may provide (315) hints or indicators to the proxy cache 115 to designate particular cached files as important.
- the indicators will prevent the designated important files from being flushed from the storage unit (s) of the proxy cache 115.
- proxy cache 115 By use of the proxy cache 115, data can be distributed and replicated at various remote locations and advantageously avoid the use of conventional mirroring techniques to replicate data.
- the use of conventional mirroring techniques requires that entire data sets are mirrored at a pre-determined time or interval (e.g., on a nightly basis) and requires disk spaces for the entire data sets.
- the proxy cache caches 115 replicates data in the active data set 140 on-demand, and the active data set 140 advantageously eliminates the large disk requirements of previous methods for data replication. Additionally, the active data set 140 is automatically updated or flushed in response to a cache miss, and thus eliminates the special software requirements of previous methods for data replication.
- a client sends NFS requests to the NFS server with: (1) an NFS file handle that specifies the target of the operation, (2) the operation (lookup, read, write, change permissions), and (3) the user on whose behalf the request is sent.
- an NFS client wants to access a remote file system for the first time, the client first needs to obtain a root file handle, which is the file handle for an entry point into a volume (as noted above, the term "volume” is synonymous with the term "file system”) .
- the client host sends a mount request to the server's mount daemon, where the mount request is part of the protocol for accessing a root file handle and a daemon is a program that runs continuously and exists for the purpose of handling periodic service requests that a computer system expects to receive.
- the daemon program forwards the requests to other programs (or processes) as appropriate.
- the server's mount daemon verifies that the client has permission to access the requested file system.
- the mount daemon grants access, it sends a (directory) file handle back to the NFS client.
- the file handles are each, for example, 32 bytes of opaque identifier data. If a file name is changed, the file handle remains the same for that renamed file.
- the mounting process described above is a protocol to access a root file handle.
- NFS file handles are not globally/universally unique, since two different servers could use the same file handles. Traditionally, this condition is not a problem, as clients keep track of which file handles are associated with each particular server.
- a proxy cache 115 When a proxy cache 115 is used to consolidate mount points, it may export volumes from many different servers. Since these file handles are not unique, the proxy cache 115 may be unable to determine which file handle corresponds to which origin server, and this condition may result in a collision problem, since a first file in a first specific server and a second file in a second specific server may have identical file handles. The problem is exacerbated since the file handle is defined to be opaque, which means that typically the content of a file handle can not be determined and only the name of the file handle can be obtained.
- the proxy cache 115 is able to interpret file handles and determine the destination server 105 of any file handle. As a result, clients 105 can access data through a proxy cache 115 without an explicit knowledge of the particular server at which the data originates .
- a file handle 400 includes various fields such as an FSid (file system identifier) field 405, a file identification (ID) field 410, a generation number field 415, and a field 420 for other data.
- FSid file system identifier
- ID file identification
- a generation number field 415 a field 420 for other data.
- the FS i field 405 is about 4 to 8 bytes .
- An embodiment of the invention allows for the virtualization of server-side file handles.
- file handles can be mutated (translated) to allow for the construction of a uniform global name-space.
- File handles returned to clients can be changed to indicate that they map to different origin servers, different sets of export options, or that they cross mount points.
- changes to origin servers 110 can made without ever impacting the clients 105.
- FIGS 5 and 6 are diagrams that illustrate a method of consolidating the mount points and method of re-writing or mutation of file handles, in accordance with an embodiment of the invention.
- each server 110 typically includes volumes (e.g., Vol/Voll, Vol/Vol2, Vol/Vol3) , where each volume represents a file system.
- the server 110(1) may include volumes 505 to 515
- the server 110(2) may include volume 520 to 530.
- a mapping 600 of FS d values can be made for each volume in a particular server 110 and the mapping 600 may be stored in the proxy cache 115, in accordance with an embodiment of the invention.
- the translation of every FSi d value beneficially permits a determination of which server stores a particular file in response to a cache miss.
- a translation table 605 contains hash values N (e.g., Nl ,
- an FS id table 610 contains FSi d values for each volumes in the servers 110.
- Other FSi d values from other received file handles from the servers 110 are stored in the table 610 and translated or mutated into different values N in table 605.
- the proxy cache 115 uses the mapping 600 with the N values and the FSi d values in table 610 to determine the particular server 110 and file/volume to direct the file handle 620.
- the translated FSi d value N of the file handle 620 is converted by the proxy cache 115 into the appropriate FSi d value from table 610 before sending the file handle 620 to the destination server 110.
- a value N in table 600 is computed based on some hash that is based on the address of the server 110 with the volume and/or other identifiers.
- the hash for each N value is unique and thus avoids the name collision problem that was mentioned above.
- a value N may be an 8 byte number and may have a value set based on the server name, volume name and file name (e.g., filerl/VolO/fileO) .
- a value N may be calculated based on the server Internet Protocol (IP) address and the server file handle value by use of the MD5 algorithm as previously described above. Since the file handle value may not be unique across different servers, the server IP address can make each value of N distinct for files across different servers.
- IP Internet Protocol
- the mapping 600 can be duplicated in various proxy caches (e.g., proxy caches 115 and 705). As a result, the mapping 600 will be available from other proxy caches if a particular proxy caches fails. For example, if clients 105 are no longer able to access the proxy cache 115 due to device failure, then a fail-over 710 can be performed to the proxy cache 705 so that the clients 105 can access the proxy cache 705 with the mapping 600 for re-writing of the file handles 400
- a proxy cache (e.g., proxy cache 115) can be swapped with a new or another proxy cache (e.g., proxy cache 705) without requiring clients 105 to un-mount and re-mount their volumes and without requiring other changes in the clients 105.
- an embodiment of the invention also provides for the creation of a uniform global name-space.
- NFS mount points can not be nested (i.e., if a client mounts an NFS volume, then that volume can not contain other mount points) . This limitation makes the creation of a uniform view of a network very difficult.
- a proxy cache 115 can inform every client 105 about each server 110 (or new added server) by use of a single mount point.
- a virtual global view of the files i.e., virtual global name space
- each client 105 has information about each server 110 and about each file in each server 110 by use of the virtual global view of the files.
- the virtual global name space leads to ease in administration of the clients 105.
- volume name 805 in the proxy cache
- An example volume name can be, "/global" .
- the volume name 805 permits a virtual name space in accordance with an embodiment of the invention.
- a client 105 can mount the volume name 805 and view folders 810, 815, 820m associated with the servers 110(1), 110(2), and 110 (m) , respectively.
- Each folder 810, 815, and 820m will contain volume names assigned to particular servers.
- the volume name 805 points to serverllO (1) /vol505, serverllO (1) /vol510, serverllO (1) /vol515, serverllO (2) /vol520, serverllO (2) /vol525, serverllO (2) /vol530 , and to other known volumes in the servers 110. Therefore, the folders 805-820m are virtually mapped to the mount point via volume name 805.
- the clients need only know about a single mount point (e.g., /global) to access the appropriate servers 110.
- the mapping 600 (see Figure 6) is used to permit the file handles 400 to be virtual access points into volumes of servers 100, along with the re-writing of file handles in the NFS protocol.
- the mount process involves communicating with the server to get the root file handle for the file system, which can later be passed to the lookup Remote Procedure Call (RPC) to locate other file handles in the remote file system directory hierarchy.
- RPC Remote Procedure Call
- FStab file system table file
- each client 105 will be required to be reconfigured so that the clients are able to access the servers, resulting in the complicated and time consuming mount point management tasks of the previous approaches .
- each client will only need to mount the directory 805 and this single consolidated mount point leads to simplified mount point management.
- the mount point is un-mounted and mounted on the proxy cache 115, and as a result, the volume name 805 will not require un-mounting and re-mounting on the clients 105.
- the directory 805 provides the function of a file system table file where clients can access drivers and servers.
- the directory 805 provides a list of access points to remote file systems and associated attributes as stored in a remote server (s) 110.
- a file handle can be re-written in different ways for the same object.
- a file handle can be re-written in different ways based upon attributes of the associated local mount point on the proxy cache .
- a mount point is defined as a local volume name.
- the local volume name, user/read-only/employeel (see block 850) and local volume name, user/employeel (see block 855) will each yield two different file handles because the mount point for each local volume name differs.
- the mount point of user/read-only/employeel 850 is "user/read-only"
- the mount point of user/employeel 855 is "user” .
- a local volume name can have associated attributes or metadata such as access restrictions, eligibility for storage or cachebility, security attributes, authentication, and authorization levels for proxy cache devices, as well as readonly or write-only attributes for servers.
- the attribute associated with the same data can be changed by accessing a mount point associated with another volume that shares the same data.
- particular attributes can be associated with a particular mount point or access point, which can be hashed to form a unique identifier.
- the unique identifier is a hashing of a local volume name, file system ID, and server IP address by use of a suitable hashing algorithm such as MD5.
- the attribute (s) 856 is associated with the mount point 850
- the attribute (s) 857 is associated with the mount point 855.
- NFS Client Data Consistency From a client's point of view, the NFS consistency model guarantees serial ordering of file transactions. Once a transaction has completed and returned a particular version of a file, any transaction started thereafter for that same file is guaranteed to return a version at least as new or newer. We call this serial consistency. Understanding consistency in NFS is complicated by the fact that, for example, transactions span various amounts of time, can be pipelined, and depend on non-reliable transports. It is therefore useful to start by defining a few client concepts:
- the start of an NFS transaction is defined to be the time at which the first request RPC (Remote Procedure Call) is sent by the client. Subsequent DUP requests (duplicate requests) do not reset the start of the transaction, where a DUP request is a duplicate of a previously made request under the NFS protocol .
- a DUP cache on a file server stores responses to requests from client as well as a transaction identifier (XID) .
- Each NFS transaction has a unique XID (a request has a unique XID, while a response has an XID that matches the request) .
- a duplicate request has the same XID as the original request .
- Transaction end - The end of an NFS transaction is defined to occur when the client receives the first of potentially multiple DUP responses .
- Serial Transactions Two transactions are defined to be serialized if one completes before the other starts. Serial consistency is guaranteed for transactions only if they are themselves serialized.
- a particular file may be referenced by different file handles depending on the protocol version or export path used to access the file.
- a file is uniquely identified by a file handle. This implies that for cache clients, the same physical file imported on multiple mount points via different export paths or protocol versions may appear as multiple distinct files.
- Consistency - A Server's Point Of View A server typically does not know precisely when a transaction starts or completes on a client. It assumes that once it sends a response, it is received immediately by the client. When it receives a request, it assumes that it was initiated by the client after it received all previously sent responses. From the server's point of view, a transaction starts when the first request is received and ends when the first response is sent back.
- Modifying operations should execute preferably only once on the server.
- a REMOVE operation When it is first received by the server, the appropriate file is removed from the filesystem and a note of this is made in a DUP cache. Any future duplicate requests will be answered out of this DUP cache. This prevents duplicate requests from failing in case any prior responses were dropped on the way to the client.
- NFS Proxy Cache When a proxy cache sends a response out to a client, it must be able to guarantee that all requests received afterwards will be answered in a consistent way. This means that once a particular version of a file has been made known to a client, all future transactions for this file must return a version at least as fresh as the particular version.
- the proxy cache preferably is prepared to serve a consistent response on future cache hits. This is currently accomplished by making sure that, on cache misses, data is filled before the response is sent to the client.
- a proxy cache When a proxy cache boots up, it runs in proxy-only mode while the in-memory object cache is rebuilt. In an embodiment, fills are not logged and an unclean shutdown could leave the cache in an inconsistent state. So on boot, the proxy cache marks all cached objects as needing to be verified before cache hits can be served off the cached objects. The proxy cache confirms with the server that the object is the latest available version by checking the attributes of the object before providing the object to a client in response to a client request.
- the proxy cache On a reboot, the proxy cache aborts all transactions are aborted and transactions are restarted by the clients. Responses to cache-fill request en-route from servers will be dropped (discarded) by the proxy cache because their XIDs (transaction identifiers) will not be recognized (note that during reboot, typically a new XID mapping, for XIDs from subsequent requests, are created within the proxy cache, and hence the new XID mapping will not recognize the previous XIDs prior to the reboot occurrence). Following the reboot, any incoming client requests are treated as the first request of a new transaction. Restarting all transactions at boot makes it possible for the proxy cache to record the start time of all active transactions. This makes an embodiment of the invention of consistent fills possible.
- a cache fill may include either:
- a potentially inconsistent fill contains data which may be stale compared to that which was previously sent to a client.
- NFS version 2 it is not always possible to know if a response contains fresh data. This type of response is a candidate for an inconsistent fill.
- Reordered responses from a server occurring at a time when their associated file(s) changed are also candidates.
- the proxy cache must typically be conservative in its approach and guess "stale" when it can not tell for sure. Inconsistent fills force the proxy cache to verify freshness with the origin server before subsequent hits can be served for the file in question. This is in contrast to consistent fills which can immediately be followed by straightforward cache hits.
- all transactions are restarted and all cached content is marked for verification. This guarantees that all cached data starts off as consistent.
- An inconsistent fill for a file F is defined to be one which results from a transaction which was started by the cache prior to the last recorded change for F.
- the last recorded change is defined to be the last time at which a server response indicating a potential change was received by the proxy cache. This is when the change became visible to clients of the proxy cache.
- the proxy cache is preferably extremely conservative when keeping track of the Last Recorded Change for a file.
- the proxy cache processes a response from a server, it updates the last recorded change for the files associated with the transaction if any of the following are true, for example:
- the response is for an operation known to have modified the file. • The response does not include post-op attributes for the file (where a post-op attribute is an attribute of a file after an operation is executed on the file) .
- the response includes post-op file attributes and they are different than those currently cached.
- Our method for keeping track of the Last Recorded Change for each file is based on a hash table (see discussion below) keyed on unique file names (e.g., MD5 algorithm results).
- the files are typically reclaimed in an LRU. If a transaction is older than the oldest element in this LRU, we assume its last recorded change might have been reclaimed and we treat it as an inconsistent fill.
- a proxy cache may serve stale data to a client after a modifying operation has been committed directly with the origin server. It is important to note that while the proxy cache clients may get stale data, they however always get consistent data. To accommodate various tolerance for staleness by clients, a proxy cache allows a max- age to be specified for different data sets. This max-age is the maximum amount of time during which hits will be served before the freshness is verified with the origin server.
- Figure 8C shows a diagram of a case when a previous request RO from the proxy cache is made to a server, and the request RO is received by the server at time A0.
- a subsequent request Rl is then made by the proxy cache to the server, and the request is received at time Al .
- the data DO in response to the request RO is received by the proxy cache at a time subsequent to when the proxy cache received the data Dl in response to the request Rl .
- the subsequently received data DO is not the latest version of the file D.
- Figure 8D shows a diagram of a case when a previous request RO from the proxy cache is made to a server, and the request RO is received by the server at time A0.
- a subsequent request Rl is then made by the proxy cache to the server, and the request is received at time Al .
- the data DO in response to the request RO is received by the proxy cache at a time prior to when the proxy cache received the data Dl in response to the request Rl .
- a hash table 870 is stored in the proxy cache.
- the hash table will contain entries 872. Each entry will contain an object 873 (e.g., file or data block) and a last recorded change value 874.
- object 873 e.g., file or data block
- last recorded change value 874 e.g., the returned data DO will have an attribute LRCO indicating its last recorded change (when the object was last changed) .
- the returned data Dl will have an attribute LRC1 indicating its last recorded change.
- the proxy cache will make a request to verify the attribute of Dl to determine if Dl is the latest version of the data D.
- the fill engine 166 in the proxy cache 115 will send, for example, a GETATTR command to the server to obtain the attributes of the data D. This method permits data consistency to be achieved for data that is stored in the proxy cache.
- the server In the HTTP protocol, the server typically gives to clients an indicator on when the clients need to check for file updates in the server. In contrast, the NFS protocol does not provide for the server to notify the clients to check for server file updates.
- the various pre-verification methods described below permits the proxy cache to verify the attributes for data stored in a server.
- proxy cache 115 By use of the proxy cache 115, data can be consolidated over a WAN 125 when a server 110 and client 105 are separated via WAN 125 by a distance (e.g., the server 110 and client 105 are in different cities) .
- the proxy cache 115 reduces the latency when the client 105 requests for data stored in the server 110, so that the server 110 will seem local to the client 105.
- embodiments of the invention provide solutions to make sure that an open protocol, such as NFS, are able to transmit efficiently over a WAN 125. Clients that use NFS typically sequentially request information about each file in a folder.
- the latency of NFS over a WAN is advantageously reduced.
- the proxy cache 115 pre-fetches 910 the attributes for data in a server 910 and the server returns 915 the attributes so that the proxy cache 115 can determine any changes in the data.
- the proxy cache 115 can then send 920 the requested data to the client 105.
- data stored in the proxy cache 115 can be pre-verified for updates or changes by checking attributes of folders, subfolders, and/or files in the server (s 110).
- NFS e.g., directory or file
- the command GETATTR can be used (although other suitable operations can be used as well) .
- the GETATTR command is used for each particular object and checks the attribute which indicates if the particular object has been modified.
- NFS traffic can perform pre- verification of meta-data to accelerate the traffic.
- Various pre-verification access patterns can be used such as, for example, sequential access, random access, access to historical-based linking of neighbor objects. Verification by sequential access means that the attributes of multiple objects are verified in sequence.
- a client pre-verification creates the historical -based link, clients benefit from the constructed historical links. The historical -based linking of neighbor objects is described below. Weights can also be added to a created link, depending on the client. Options can also be added to break links.
- Figure 10 is a block diagram to show components in the proxy cache 115 for performing the pre-verification access, in accordance with an embodiment of the invention.
- the object EO may have an opaque file handle, and so there may be no way to find out the parent directory of the EO object.
- An element hash table 1005 and directory hash table 1010 stored in memory of the proxy cache 115 include information for directory D.
- the first four elements (E0 to E3 , for example) are loaded in the element hash table 1010. This method permits the creation of a link to the directory D and the capture of the sequence E0-E3 in a short period of time.
- the first four objects E0-E3 are hashed in table 1010 based on the file handle of object E0 file and predetermined neighbor objects E1-E3 and E0 will point (1015) to directory D in element hash table 1005.
- Objects E0-E4 are loaded, since a client 105 may request for object El or E2 , instead of object E0.
- the object E0 entry has sufficient information about its parent directory D in the hash table 1005.
- a next pointer is marked, in order to assume that the next object will be El. This pointer creates the sequential linking for an access pattern.
- the linking method of Figure 10 there is no need to determine the directory cookie ordering.
- the linking method maintains an ordering of operation per client 105.
- FIG. 11 is a block diagram illustrating a method of historical linking of verified objects, in accordance with an embodiment of the invention.
- An object is paired (linked) with a set of neighbor objects, if that object has been verified by a client. For example, a GETATTR D verification request from a client 105 will verify the object D. Since objects EO and El are neighboring object, objects EO and El are also pre-verified and are thus linked to object D.
- the pre-verification of objects is particularly useful, since the GETATTR traffic in the NFS protocol typically causes a bottleneck in the network.
- the NFS traffic over a WAN is optimized.
- previous approaches require transformation of the NFS traffic into a proprietary protocol to optimize the NFS traffic over a WAN.
- Figure 12 is a block diagram, where a link is broken in response to a change in an attribute of an object. For example, if object EO was pre-verified after a client 105 transmits a GETATTR E0 command, and a change in an attribute of the object E0 was detected, then the proxy cache 115 can proceed by reading the object E0 from the server 110 and cache the object E0.
- Figure 13 illustrates a network system including a client 105, a proxy cache 115, and a server 110, for purposes of describing a cache hit condition in response to CIFS traffic from the client 105.
- the protocol used in the traffic between the client 105 and the proxy cache 115 is an open protocol such as the CIFS protocol
- the protocol used in the traffic between the proxy cache 115 and server 110 is the NFS protocol .
- the proxy cache 115 can translate the CIFS traffic from the client 105 into NFS traffic to the server 110 (and translate the NFS traffic from the server 110 into CIFS traffic to the client 105) at the file system level, instead of performing the translation at the protocol level.
- the proxy cache 115 permits CIFS clients to access data in an NFS server if there is a cache miss.
- the CIFS protocol is not practical for use over a WAN due to the serialized operations and greater number of operations in the CIFS protocol. Additionally, the CIFS protocol is less well-defined and optimization of the CIFS protocol for use over the WAN may result in violations of the protocol.
- the proxy cache 115 can translate the CIFS traffic from a client 105 into NFS traffic to permit access to the server 110 if there is cache miss .
- Figure 13 is a diagram illustrating a cache hit condition for a CIFS request 1305 from a client 105.
- the stack 1310 queries a file system 1315 (e.g., a Write-Anywhere-File Layout or WAFL) and if the file system 1315 has the requested data, then the file system 1315 will pass the requested data 1320 to the stack 1310. The stack 1310 would then send the requested data 1320 to the requesting client 105. It is noted that a similar operation occurs if an NFS request is received by the proxy cache 115 from a client during a cache hit condition.
- a file system 1315 e.g., a Write-Anywhere-File Layout or WAFL
- Figure 14 is a block diagram illustrating the operation for a CIFS request that results in a cache miss condition in the proxy cache 115.
- the stack 1310 queries the files system 1315 for the requested data. Since the requested data is not in the file system 1315, the file system 1315 sends a query to an NFS client module 1325 (the module is typically implemented in code and executed on the client) which then sends an NFS request 1330 over the WAN to the server 110.
- the server 110 sends (1335) the requested data via the NFS protocol across the WAN to the NFS client module 1325.
- FIG. 15 is a block diagram illustrating the operation for an NFS request 1500 that results in a cache miss condition in the proxy cache 115.
- the stack 1510 will check the file system 1515 for the requested data.
- the proxy cache 115 sends an NFS request 1530 from the network interface 1505 to the server 110.
- the fill engine 1520 parses the server response 1535 and uses a data structure that permits communication between clients 105 and servers 110 and the opaque feature of the file handles.
- the requested data 1525 is allocated in the proxy cache 115 and then sent by the proxy cache 115 to the client 105.
- FIG. 16 is block diagram illustrating a network in accordance with an embodiment of the invention for purposes of describing a delay write operation.
- the proxy cache 115 is configured to perform delayed sparse write operations 1610 to the server 110 in response to a write operation 1605 from a client 105.
- proxy cache 115 can write the data to the server 110 to modify the files in the server 110.
- the write operation 1610 can be performed as a background operation of the proxy cache 115 or can be performed at a later time.
- the write data is sent to the local disk in the proxy cache first and write operation to the remote server may be delayed.
- the proxy cache 115 can serve as a staging area and can buffer the write data prior to performing the write operation 1610.
- the write operation 1610 can be performed at a rate slower than the rate of write operation 1605. Additionally or alternatively, the write operation 1610 can be performed at a delayed time or at a time subsequent to the write operation 1605.
- the proxy cache 115 can perform the write operation 1610 to the server 110 at a later time when the WAN becomes operational. This delayed write feature insures that the write data is eventually stored in the server 110, without slowing down or affecting the operation of the client 105.
- an embodiment of the invention avoids the need for conventional software for copying data, since the write operation 1610 to the server 110 is typically performed automatically.
- the write operation 1605 may be permitted to invalidate non-read-only data stored in the proxy cache 115. Additionally, write data that is cached in the proxy cache 115 does not require a deletion action, since the write data will be subsequently flushed from the proxy cache 115 by use of, for example, a FIFO operation as described above.
- the delayed write operation from the proxy cache 115 to the server 110 may be performed: (1) right away, (2) based upon a schedule, (3) during idle times in the network, and/or (4) based upon bandwidth limitations (e.g., perform the write operation during a time when there is maximum network bandwidth available) .
- Reservation rate control can be made to limit bandwidth traffic to proxy cache 115.
- bandwidth can be limited or managed by prioritizing based on various factors, such as, for example: (1) client IP information (layer 4 TCP/IP layer information) , (2) NFS information (layer 7) (e.g., user ID, operation types such as read or write, or (3) particular files (e.g., one particular directory may have higher priority than other directories) .
- bandwidth can be prioritized based upon the type of client that is sending the request or based on other factors as mentioned above.
- Figure 17 illustrates an embodiment of a proxy cache 115 configured to cache an active data set that includes subparts 1703 of a file system 1705 in a server 110.
- the subparts may be a subtree 1706 under a root 1707 and file usersl.
- the subtree 1703 may be fetched by the proxy cache 115 from the server 110 prior to a planned disconnect between the proxy cache 115 and server 110 so that required or particular data are always available for a client 105 to access in the proxy cache 115.
- the proxy cache 115 may be configured to the subtree 1706 in the server 110 prior to a planned disconnect operation.
- the proxy cache advantageously provides a method to replicate data without using the mirroring techniques of conventional approaches.
- the original cached copy of the data in the proxy cache 115 is not replaced with the new updated data from the server 110 until all of the data has been retrieved from the server 110.
- the replacement of data in the proxy cache 115 may occur at the directory level or file level.
- FIG. 18 is a block diagram of a system for using delegation, in accordance with an embodiment of the invention.
- the server 110(1) contains a copy 1810 of a subdirectory or file(s)
- the proxy cache 115 contains a cached copy 1805 of the data in the logical copy 1810.
- the cached copy 1805 in this instance would be included in the active data sets in the proxy cache 115.
- a server 105 can grant a "lock" of the logical copy 1810 to the proxy cache 115, and as a result, the proxy cache 115 can serve cache hits without the requirement that the proxy cache 115 checks the server 115 for file updates in the logical copy 1810.
- Any file updates that occur for the logical copy 1810 in the server 110(1) will cause the server 110(1) to inform the lock owner of the file updates. If a proxy cache 115 has a lock to a file in a server, then any write request to the file will typically go through the proxy cache 115 and a delayed write operation to the file may subsequently be performed by the proxy cache. The lock owned by the proxy cache 115 may be subsequently revoked by the server.
- Figure 19 illustrates a block diagram including multiple proxy caches 115a-115c in a cluster configuration, in accordance with an embodiment of the invention.
- the number of proxy caches 115 may vary in Figure 19.
- the cluster of proxy caches permits a method of an alternate route for client request traffic and data traffic if the primary proxy cache fails.
- the proxy caches 115 may be, for example, in different parts of the world or region. For example, if the proxy cache 115a is the primary cache and subsequently fails, then an alternate route for network traffic may be formed by selecting another proxy cache to be the primary proxy cache. For example, the proxy caches 115b and 115c may be chosen as the primary proxy cache.
- the updated proxy cache may be chosen based upon, for example, size (a larger-sized proxy cache will increase the probability of a cache hit), reduced traffic latency, location (e.g., choose a "peer" proxy cache or neighboring proxy caches) , and/or the particular data being requested.
- the global name space feature and file handle translation feature permits clients 105 to access one proxy cache instead of another proxy cache. The rewriting of file handles is used, since the different proxy caches do not know about each other; the re-writing of file handles permit the clients to properly re-route their requests to particular a particular proxy cache and to permit the different proxy caches to understand the same messages.
- names for an object are already imbedded with the name of the server.
- FIG 20 is a block diagram of a network 2200, including client devices 105(1) to 105 (n) , proxy caches 2205(1) to 2205 (p), and a server 2210 arranged in a reverse proxy configuration, in accordance with an embodiment of the invention.
- the proxy caches (generally referred in Figure 22 as
- the proxy caches 2205 permit the scaling or distribution of traffic to and from the server 2210.
- the proxy caches 2205 are locally connected to the server 2210 via LAN 2215.
- the variable p may be any suitable integer value.
- the number of proxy caches devices (generally referred in Figure 22 herein as 2205) may vary.
- the network 2200 may be implemented with only proxy cache 2205, particularly if the server 2210 has a slow rate of traffic processing speed.
- the client devices 105 may be coupled via WAN 125 to a load balancer 2220, such as a load balancing switch, which distributes traffic between the clients 105 and proxy caches 2205.
- the reverse proxy configuration in Figure 22 permits data to be cached on-demand by the proxy caches 2205.
- This on-demand caching operation is more efficient than standard replication techniques and does not require the special software for standard replication techniques.
- the multiple proxy caches 2205 permits a distribution of requests that are directed to the server 2210.
- the multiple proxy caches 2205 can collectively increase the chance of cache hits in response to a request from one of the clients 105, since each proxy cache 2205 will contain an active data set that may include the requested data.
- the multiple proxy caches 2205 can reduce the amount of requests that are transmitted to the server 2210 from a client 105.
- the multiple proxy caches 2205 increase the chance of a cache hit and provide on-demand data caching for the clients 105.
- the slow processing rate of the server 2210 will not serve as a bottleneck to client requests.
- the reverse proxy configuration in Figure 22 is very beneficial for read traffic (e.g., applications such as graphics rendering of movies) .
- mutation of file handles is typically not required in the reverse proxy configuration.
- the use of the proxy caches is less expensive than use of file servers and replication of data in the proxy cache can occur automatically without the need for specialized software.
- the load balancer 2220 distributes requests and data from cache hits. If there is a cache miss (i.e., none of the proxy cache 205 contains the requested data in their active data sets, then one of the proxy caches 205 will transmit a request to the server 210 for the requested data and will transmit the a cached copy of the data back to the requesting server.
- Figure 21 shows a block diagram of a network 2300, where only a single proxy cache 2205(1) is coupled to the server 2210 in the reverse proxy configuration. It is noted in this example that the server 2210 is sufficiently slow in processing rate. As a result, only one proxy cache 2205 may be implemented in the network 2300 for receiving client requests, for transmitting data back to the requesting client 105 if there is a cache hit, and for accessing the server 2210 if there is a cache miss.
- FIG 22 is a block diagram of a network 2400 in accordance with another embodiment of the invention.
- the proxy caches 2205(1) to 2205 (p) can communicate with a plurality of servers 2210(1) to 2210 (m) via a network switch 2405, for example.
- the variable m may be suitable integer value.
- the network switch 2405 may be implemented in the LAN 2215.
- the proxy caches 2205 permit the scaling or distribution of traffic to and from the plurality of servers 2210 and permit traffic acceleration to and from the servers 2210.
- the reverse proxy configuration in Figure 22 prevents the servers 2210 from acting as a bottleneck to client traffic, particularly if the servers are of slower processing capability.
- FIG. 23 is a block diagram of a network 2450 in accordance with another embodiment of the invention.
- a proxy cache 2505 is clustered with the proxy caches 2205(1) to 2205 (p), and can perform the various functions described above for clustered proxy caches.
- Embodiments of the invention advantageously reduce the latency for clients as opposed to prior approaches where clients are required to access a server for all data requests.
- Embodiments of the invention advantageously increase the ease of administration of clients and/or servers, since special software for clients are not required and servers may be easily administered at remote locations.
- Embodiments of the invention advantageously increase the ease of replication of data by avoiding required mirroring steps of previous approaches. Specifically, embodiments of the invention do not require administrators to permit the mirroring of data on given intervals.
- Embodiments of the invention advantageously require less disk requirements, since the total active data set is smaller in size than the total data set in a server. Less disk requirements lead to cheaper costs and less failure problems.
- Embodiments of the invention advantageously permit many clients to make many requests for data without saturating the network in the reverse proxy configuration.
- the various engines or modules discussed herein may also be, for example, software, commands, data files, programs, code, modules, instructions, or the like, and may also include suitable mechanisms.
- an embodiment of the invention may be implemented by using a programmed general purpose digital computer, by using application specific integrated circuits, programmable logic devices, or field programmable gate arrays, or by using a network of interconnected components and circuits. Connections may be wired, wireless, by modem, and the like.
- aspects of the invention may also be implemented in hardware, software, firmware, and/or a combination of any of hardware, software, or firmware.
Abstract
Description
Claims
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/245,828 US7171469B2 (en) | 2002-09-16 | 2002-09-16 | Apparatus and method for storing data in a proxy cache in a network |
US245828 | 2002-09-16 | ||
PCT/US2003/029398 WO2004025429A2 (en) | 2002-09-16 | 2003-09-16 | Apparatus and method for proxy cache |
Publications (3)
Publication Number | Publication Date |
---|---|
EP1540498A2 true EP1540498A2 (en) | 2005-06-15 |
EP1540498A4 EP1540498A4 (en) | 2005-12-07 |
EP1540498B1 EP1540498B1 (en) | 2016-03-30 |
Family
ID=31992195
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP03752475.8A Expired - Lifetime EP1540498B1 (en) | 2002-09-16 | 2003-09-16 | Apparatus and method for proxy cache |
Country Status (5)
Country | Link |
---|---|
US (3) | US7171469B2 (en) |
EP (1) | EP1540498B1 (en) |
JP (1) | JP4547264B2 (en) |
AU (1) | AU2003270764A1 (en) |
WO (1) | WO2004025429A2 (en) |
Families Citing this family (298)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7543018B2 (en) * | 1996-04-11 | 2009-06-02 | Aol Llc, A Delaware Limited Liability Company | Caching signatures |
US8239354B2 (en) | 2005-03-03 | 2012-08-07 | F5 Networks, Inc. | System and method for managing small-size files in an aggregated file system |
US7788335B2 (en) * | 2001-01-11 | 2010-08-31 | F5 Networks, Inc. | Aggregated opportunistic lock and aggregated implicit lock management for locking aggregated files in a switched file system |
US8195760B2 (en) * | 2001-01-11 | 2012-06-05 | F5 Networks, Inc. | File aggregation in a switched file system |
US20040133606A1 (en) | 2003-01-02 | 2004-07-08 | Z-Force Communications, Inc. | Directory aggregation for files distributed over a plurality of servers in a switched file system |
US7512673B2 (en) | 2001-01-11 | 2009-03-31 | Attune Systems, Inc. | Rule based aggregation of files and transactions in a switched file system |
US7509322B2 (en) | 2001-01-11 | 2009-03-24 | F5 Networks, Inc. | Aggregated lock management for locking aggregated files in a switched file system |
EP1368736A2 (en) | 2001-01-11 | 2003-12-10 | Z-Force Communications, Inc. | File switch and switched file system |
JP4020676B2 (en) * | 2002-03-26 | 2007-12-12 | 株式会社東芝 | Web system and Web system control method |
US7171469B2 (en) * | 2002-09-16 | 2007-01-30 | Network Appliance, Inc. | Apparatus and method for storing data in a proxy cache in a network |
JP4174049B2 (en) * | 2002-09-20 | 2008-10-29 | 松下電器産業株式会社 | Access control in intermediate network elements connecting multiple data communication networks |
CA2421825C (en) * | 2002-09-20 | 2012-07-10 | Mks Inc. | Version control system for software development |
US7877511B1 (en) | 2003-01-13 | 2011-01-25 | F5 Networks, Inc. | Method and apparatus for adaptive services networking |
US8015266B1 (en) * | 2003-02-07 | 2011-09-06 | Netapp, Inc. | System and method for providing persistent node names |
US7809693B2 (en) * | 2003-02-10 | 2010-10-05 | Netapp, Inc. | System and method for restoring data on demand for instant volume restoration |
US7574423B2 (en) * | 2003-03-20 | 2009-08-11 | International Business Machines Corporation | Partial data model exposure through client side caching |
JP2005018100A (en) * | 2003-06-23 | 2005-01-20 | Fujitsu Ltd | Network file server, information processor, and program |
DE10356724B3 (en) * | 2003-12-02 | 2005-06-16 | Deutsches Zentrum für Luft- und Raumfahrt e.V. | Method for reducing the transport volume of data in data networks |
US8010670B2 (en) | 2003-12-23 | 2011-08-30 | Slipstream Data Inc. | Meta-data based method for local cache utilization |
US20050198401A1 (en) * | 2004-01-29 | 2005-09-08 | Chron Edward G. | Efficiently virtualizing multiple network attached stores |
US7392295B2 (en) | 2004-02-19 | 2008-06-24 | Microsoft Corporation | Method and system for collecting information from computer systems based on a trusted relationship |
US7584382B2 (en) * | 2004-02-19 | 2009-09-01 | Microsoft Corporation | Method and system for troubleshooting a misconfiguration of a computer system based on configurations of other computer systems |
US8782654B2 (en) | 2004-03-13 | 2014-07-15 | Adaptive Computing Enterprises, Inc. | Co-allocating a reservation spanning different compute resources types |
US7739301B2 (en) * | 2004-03-17 | 2010-06-15 | Netapp, Inc. | Method and apparatus for improving file system proxy performance and security by distributing information to clients via file handles |
US7577640B1 (en) * | 2004-03-31 | 2009-08-18 | Avaya Inc. | Highly available, highly scalable multi-source logical database with low latency |
US7430571B2 (en) | 2004-04-30 | 2008-09-30 | Network Appliance, Inc. | Extension of write anywhere file layout write allocation |
US7409494B2 (en) * | 2004-04-30 | 2008-08-05 | Network Appliance, Inc. | Extension of write anywhere file system layout |
US20070266388A1 (en) | 2004-06-18 | 2007-11-15 | Cluster Resources, Inc. | System and method for providing advanced reservations in a compute environment |
EP1785880A4 (en) * | 2004-06-24 | 2007-12-05 | Nec Corp | Information service system, information server, portable terminal, information service control program and portable terminal control program |
US7640328B1 (en) * | 2004-06-30 | 2009-12-29 | Symantec Operating Corporation | Method and apparatus for prioritizing provisioning data in a provisioning server |
US8176490B1 (en) | 2004-08-20 | 2012-05-08 | Adaptive Computing Enterprises, Inc. | System and method of interfacing a workload manager and scheduler with an identity manager |
US20060047714A1 (en) * | 2004-08-30 | 2006-03-02 | Mendocino Software, Inc. | Systems and methods for rapid presentation of historical views of stored data |
US7664983B2 (en) * | 2004-08-30 | 2010-02-16 | Symantec Corporation | Systems and methods for event driven recovery management |
JP4437432B2 (en) * | 2004-09-30 | 2010-03-24 | 株式会社日立製作所 | Computer system |
US8095940B2 (en) | 2005-09-19 | 2012-01-10 | Citrix Systems, Inc. | Method and system for locating and accessing resources |
US8171479B2 (en) | 2004-09-30 | 2012-05-01 | Citrix Systems, Inc. | Method and apparatus for providing an aggregate view of enumerated system resources from various isolation layers |
US7680758B2 (en) | 2004-09-30 | 2010-03-16 | Citrix Systems, Inc. | Method and apparatus for isolating execution of software applications |
CA2586763C (en) | 2004-11-08 | 2013-12-17 | Cluster Resources, Inc. | System and method of providing system jobs within a compute environment |
US8458467B2 (en) | 2005-06-21 | 2013-06-04 | Cisco Technology, Inc. | Method and apparatus for adaptive application message payload content transformation in a network infrastructure element |
US7664879B2 (en) | 2004-11-23 | 2010-02-16 | Cisco Technology, Inc. | Caching content and state data at a network element |
US7987272B2 (en) * | 2004-12-06 | 2011-07-26 | Cisco Technology, Inc. | Performing message payload processing functions in a network element on behalf of an application |
US8082304B2 (en) | 2004-12-10 | 2011-12-20 | Cisco Technology, Inc. | Guaranteed delivery of application layer messages by a network element |
US8788674B2 (en) * | 2005-01-12 | 2014-07-22 | Blue Coat Systems, Inc. | Buffering proxy for telnet access |
US7885970B2 (en) * | 2005-01-20 | 2011-02-08 | F5 Networks, Inc. | Scalable system for partitioning and accessing metadata over multiple servers |
US7958347B1 (en) * | 2005-02-04 | 2011-06-07 | F5 Networks, Inc. | Methods and apparatus for implementing authentication |
US8863143B2 (en) | 2006-03-16 | 2014-10-14 | Adaptive Computing Enterprises, Inc. | System and method for managing a hybrid compute environment |
US9075657B2 (en) | 2005-04-07 | 2015-07-07 | Adaptive Computing Enterprises, Inc. | On-demand access to compute resources |
US7277899B1 (en) * | 2005-03-15 | 2007-10-02 | Adaptec, Inc. | Method and computer program for reducing storage space requirements in a file system comprising linkable files |
CA2601384A1 (en) | 2005-03-16 | 2006-10-26 | Cluster Resources, Inc. | Automatic workload transfer to an on-demand center |
US9231886B2 (en) | 2005-03-16 | 2016-01-05 | Adaptive Computing Enterprises, Inc. | Simple integration of an on-demand compute environment |
US20110258320A1 (en) * | 2005-04-07 | 2011-10-20 | Adaptive Computing Enterprises, Inc. | Elastic management of compute resources between a web server and an on-demand compute environment |
US20060248547A1 (en) * | 2005-04-14 | 2006-11-02 | International Business Machines Corporation | Multi-level cache apparatus and method for enhanced remote invocation performance |
US7689609B2 (en) * | 2005-04-25 | 2010-03-30 | Netapp, Inc. | Architecture for supporting sparse volumes |
US8055702B2 (en) * | 2005-04-25 | 2011-11-08 | Netapp, Inc. | System and method for caching network file systems |
US8447876B2 (en) * | 2005-06-02 | 2013-05-21 | Thomson Licensing | Content timing method and system |
US7613743B1 (en) * | 2005-06-10 | 2009-11-03 | Apple Inc. | Methods and apparatuses for data protection |
US7739318B2 (en) * | 2005-06-20 | 2010-06-15 | Netapp, Inc. | System and method for maintaining mappings from data containers to their parent directories |
US8266327B2 (en) * | 2005-06-21 | 2012-09-11 | Cisco Technology, Inc. | Identity brokering in a network element |
US20070083620A1 (en) * | 2005-10-07 | 2007-04-12 | Pedersen Bradley J | Methods for selecting between a predetermined number of execution methods for an application program |
US8131825B2 (en) * | 2005-10-07 | 2012-03-06 | Citrix Systems, Inc. | Method and a system for responding locally to requests for file metadata associated with files stored remotely |
US7945816B1 (en) * | 2005-11-30 | 2011-05-17 | At&T Intellectual Property Ii, L.P. | Comprehensive end-to-end storage area network (SAN) application transport service |
JP4795787B2 (en) * | 2005-12-09 | 2011-10-19 | 株式会社日立製作所 | Storage system, NAS server, and snapshot method |
US7743123B2 (en) * | 2005-12-19 | 2010-06-22 | Microsoft Corporation | Aggregating information from a cluster of peers |
US7640356B2 (en) * | 2006-03-10 | 2009-12-29 | Cisco Technology, Inc. | Method and system for reducing cache warm-up time to suppress transmission of redundant data |
US8832247B2 (en) * | 2006-03-24 | 2014-09-09 | Blue Coat Systems, Inc. | Methods and systems for caching content at multiple levels |
US7562078B1 (en) * | 2006-04-01 | 2009-07-14 | Network Appliance, Inc. | Retention of active data stored in memory |
US8417746B1 (en) | 2006-04-03 | 2013-04-09 | F5 Networks, Inc. | File system management with enhanced searchability |
US8151323B2 (en) | 2006-04-12 | 2012-04-03 | Citrix Systems, Inc. | Systems and methods for providing levels of access and action control via an SSL VPN appliance |
US9071506B2 (en) * | 2006-07-31 | 2015-06-30 | Hewlett-Packard Development Company, L.P. | Accessing web services using network management information |
JP4950295B2 (en) * | 2006-08-21 | 2012-06-13 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | Distributed server network for providing triple play services to end users |
US8046422B2 (en) * | 2006-08-21 | 2011-10-25 | Netapp, Inc. | Automatic load spreading in a clustered network storage system |
CA2705379C (en) | 2006-12-04 | 2016-08-30 | Commvault Systems, Inc. | Systems and methods for creating copies of data, such as archive copies |
US7840537B2 (en) * | 2006-12-22 | 2010-11-23 | Commvault Systems, Inc. | System and method for storing redundant information |
US7996421B2 (en) * | 2007-01-03 | 2011-08-09 | International Business Machines Corporation | Method, computer program product, and system for coordinating access to locally and remotely exported file systems |
US7844710B2 (en) * | 2007-02-27 | 2010-11-30 | Novell, Inc. | Proxy caching for directory services |
US8103783B2 (en) | 2007-03-12 | 2012-01-24 | Citrix Systems, Inc. | Systems and methods of providing security and reliability to proxy caches |
US7720936B2 (en) | 2007-03-12 | 2010-05-18 | Citrix Systems, Inc. | Systems and methods of freshening and prefreshening a DNS cache |
US7783757B2 (en) | 2007-03-12 | 2010-08-24 | Citrix Systems, Inc. | Systems and methods of revalidating cached objects in parallel with request for object |
US7584294B2 (en) * | 2007-03-12 | 2009-09-01 | Citrix Systems, Inc. | Systems and methods for prefetching objects for caching using QOS |
US20080228864A1 (en) * | 2007-03-12 | 2008-09-18 | Robert Plamondon | Systems and methods for prefetching non-cacheable content for compression history |
US7809818B2 (en) | 2007-03-12 | 2010-10-05 | Citrix Systems, Inc. | Systems and method of using HTTP head command for prefetching |
US8504775B2 (en) | 2007-03-12 | 2013-08-06 | Citrix Systems, Inc | Systems and methods of prefreshening cached objects based on user's current web page |
US8037126B2 (en) | 2007-03-12 | 2011-10-11 | Citrix Systems, Inc. | Systems and methods of dynamically checking freshness of cached objects based on link status |
US8701010B2 (en) | 2007-03-12 | 2014-04-15 | Citrix Systems, Inc. | Systems and methods of using the refresh button to determine freshness policy |
US8234327B2 (en) * | 2007-03-30 | 2012-07-31 | Netapp, Inc. | System and method for bandwidth optimization in a network storage environment |
WO2008130983A1 (en) * | 2007-04-16 | 2008-10-30 | Attune Systems, Inc. | File aggregation in a switched file system |
US8682916B2 (en) * | 2007-05-25 | 2014-03-25 | F5 Networks, Inc. | Remote file virtualization in a switched file system |
US7991910B2 (en) | 2008-11-17 | 2011-08-02 | Amazon Technologies, Inc. | Updating routing information based on client location |
US8028090B2 (en) | 2008-11-17 | 2011-09-27 | Amazon Technologies, Inc. | Request routing utilizing client location information |
US7908375B2 (en) * | 2007-07-11 | 2011-03-15 | Microsoft Corporation | Transparently externalizing plug-in computation to cluster |
US7958200B2 (en) * | 2007-08-14 | 2011-06-07 | International Business Machines Corporation | Methods, computer program products, and apparatuses for providing remote client access to exported file systems |
US8315999B2 (en) * | 2007-08-29 | 2012-11-20 | Nirvanix, Inc. | Policy-based file management for a storage delivery network |
JP2009059201A (en) * | 2007-08-31 | 2009-03-19 | Hitachi Ltd | Intermediate device for virtualizing and transferring file level |
US8041773B2 (en) | 2007-09-24 | 2011-10-18 | The Research Foundation Of State University Of New York | Automatic clustering for self-organizing grids |
US7925694B2 (en) | 2007-10-19 | 2011-04-12 | Citrix Systems, Inc. | Systems and methods for managing cookies via HTTP content layer |
AU2008311849A1 (en) | 2007-10-20 | 2009-04-23 | Citrix Systems, Inc. | Systems and methods for folder redirection |
US8171483B2 (en) | 2007-10-20 | 2012-05-01 | Citrix Systems, Inc. | Method and system for communicating between isolation environments |
US8180747B2 (en) | 2007-11-12 | 2012-05-15 | F5 Networks, Inc. | Load sharing cluster file systems |
US8548953B2 (en) * | 2007-11-12 | 2013-10-01 | F5 Networks, Inc. | File deduplication using storage tiers |
US20090204705A1 (en) * | 2007-11-12 | 2009-08-13 | Attune Systems, Inc. | On Demand File Virtualization for Server Configuration Management with Limited Interruption |
US8117244B2 (en) | 2007-11-12 | 2012-02-14 | F5 Networks, Inc. | Non-disruptive file migration |
US20090204650A1 (en) * | 2007-11-15 | 2009-08-13 | Attune Systems, Inc. | File Deduplication using Copy-on-Write Storage Tiers |
US20090271523A1 (en) * | 2007-11-30 | 2009-10-29 | Darrell Gentry | System, Method and Software for Using One Computer Network to Bypass a Portion of Another Computer Network |
US8352785B1 (en) | 2007-12-13 | 2013-01-08 | F5 Networks, Inc. | Methods for generating a unified virtual snapshot and systems thereof |
US8239345B2 (en) * | 2007-12-27 | 2012-08-07 | Microsoft Corporation | Asynchronous replication |
CN101217449B (en) * | 2008-01-09 | 2011-01-12 | 金蝶软件(中国)有限公司 | A remote call management procedure |
US8805949B2 (en) * | 2008-01-16 | 2014-08-12 | Netapp, Inc. | System and method for populating a cache using behavioral adaptive policies |
US8090877B2 (en) | 2008-01-26 | 2012-01-03 | Citrix Systems, Inc. | Systems and methods for fine grain policy driven cookie proxying |
US8560732B2 (en) * | 2008-02-19 | 2013-10-15 | Red Hat, Inc. | Peer-to-peer object distribution |
US8015262B2 (en) * | 2008-02-27 | 2011-09-06 | Sap, Ag | Stateless core service transaction patterns |
US7962597B2 (en) | 2008-03-31 | 2011-06-14 | Amazon Technologies, Inc. | Request routing based on class |
US8606996B2 (en) | 2008-03-31 | 2013-12-10 | Amazon Technologies, Inc. | Cache optimization |
US7970820B1 (en) | 2008-03-31 | 2011-06-28 | Amazon Technologies, Inc. | Locality based content distribution |
US8484162B2 (en) | 2008-06-24 | 2013-07-09 | Commvault Systems, Inc. | De-duplication systems and methods for application-specific data |
US8219524B2 (en) * | 2008-06-24 | 2012-07-10 | Commvault Systems, Inc. | Application-aware and remote single instance data management |
US9098495B2 (en) * | 2008-06-24 | 2015-08-04 | Commvault Systems, Inc. | Application-aware and remote single instance data management |
US8166263B2 (en) * | 2008-07-03 | 2012-04-24 | Commvault Systems, Inc. | Continuous data protection over intermittent connections, such as continuous data backup for laptops or wireless devices |
US8549582B1 (en) | 2008-07-11 | 2013-10-01 | F5 Networks, Inc. | Methods for handling a multi-protocol content name and systems thereof |
US20100049717A1 (en) * | 2008-08-20 | 2010-02-25 | Ryan Michael F | Method and systems for sychronization of process control servers |
WO2010036754A1 (en) | 2008-09-26 | 2010-04-01 | Commvault Systems, Inc. | Systems and methods for managing single instancing data |
US9015181B2 (en) * | 2008-09-26 | 2015-04-21 | Commvault Systems, Inc. | Systems and methods for managing single instancing data |
US8417895B1 (en) | 2008-09-30 | 2013-04-09 | Violin Memory Inc. | System for maintaining coherency during offline changes to storage media |
US8838850B2 (en) * | 2008-11-17 | 2014-09-16 | Violin Memory, Inc. | Cluster control protocol |
US8442059B1 (en) | 2008-09-30 | 2013-05-14 | Gridiron Systems, Inc. | Storage proxy with virtual ports configuration |
US8443150B1 (en) | 2008-11-04 | 2013-05-14 | Violin Memory Inc. | Efficient reloading of data into cache resource |
US8788758B1 (en) | 2008-11-04 | 2014-07-22 | Violin Memory Inc | Least profitability used caching scheme |
US8180730B2 (en) * | 2008-11-25 | 2012-05-15 | International Business Machines Corporation | Arbitration token for managing data integrity and data accuracy of information services that utilize distributed data replicas |
US8412677B2 (en) | 2008-11-26 | 2013-04-02 | Commvault Systems, Inc. | Systems and methods for byte-level or quasi byte-level single instancing |
US8868675B2 (en) * | 2008-12-04 | 2014-10-21 | Cisco Technology, Inc. | Network optimization using distributed virtual resources |
US8401996B2 (en) * | 2009-03-30 | 2013-03-19 | Commvault Systems, Inc. | Storing a variable number of instances of data objects |
US8667366B1 (en) | 2009-04-17 | 2014-03-04 | Violin Memory, Inc. | Efficient use of physical address space for data overflow and validation |
US8650362B2 (en) | 2009-04-17 | 2014-02-11 | Violin Memory Inc. | System for increasing utilization of storage media |
US20120042130A1 (en) * | 2009-04-24 | 2012-02-16 | Aaron Antony Peapell | Data Storage System |
US8090797B2 (en) | 2009-05-02 | 2012-01-03 | Citrix Systems, Inc. | Methods and systems for launching applications into existing isolation environments |
US8713252B1 (en) | 2009-05-06 | 2014-04-29 | Violin Memory, Inc. | Transactional consistency scheme |
US8578120B2 (en) | 2009-05-22 | 2013-11-05 | Commvault Systems, Inc. | Block-level single instancing |
US9069676B2 (en) | 2009-06-03 | 2015-06-30 | Violin Memory, Inc. | Mapping engine for a storage device |
US8402198B1 (en) | 2009-06-03 | 2013-03-19 | Violin Memory, Inc. | Mapping engine for a storage device |
US8930306B1 (en) | 2009-07-08 | 2015-01-06 | Commvault Systems, Inc. | Synchronized data deduplication |
WO2011022405A2 (en) * | 2009-08-17 | 2011-02-24 | Akamai Technologies, Inc. | Method and system for http-based stream delivery |
JP5208884B2 (en) * | 2009-08-17 | 2013-06-12 | 日本電信電話株式会社 | WEB information acquisition method and apparatus |
US8402246B1 (en) * | 2009-08-28 | 2013-03-19 | Violin Memory, Inc. | Alignment adjustment in a tiered storage system |
US8171064B2 (en) * | 2009-09-01 | 2012-05-01 | Netapp, Inc. | Methods and systems for concurrently reading direct and indirect data blocks |
US11720290B2 (en) | 2009-10-30 | 2023-08-08 | Iii Holdings 2, Llc | Memcached server functionality in a cluster of data processing nodes |
US10877695B2 (en) | 2009-10-30 | 2020-12-29 | Iii Holdings 2, Llc | Memcached server functionality in a cluster of data processing nodes |
US10721269B1 (en) | 2009-11-06 | 2020-07-21 | F5 Networks, Inc. | Methods and system for returning requests with javascript for clients before passing a request to a server |
US20110137966A1 (en) * | 2009-12-08 | 2011-06-09 | Netapp, Inc. | Methods and systems for providing a unified namespace for multiple network protocols |
US8484259B1 (en) | 2009-12-08 | 2013-07-09 | Netapp, Inc. | Metadata subsystem for a distributed object store in a network storage system |
US8180813B1 (en) | 2009-12-08 | 2012-05-15 | Netapp, Inc. | Content repository implemented in a network storage server system |
US9507799B1 (en) | 2009-12-08 | 2016-11-29 | Netapp, Inc. | Distributed object store for network-based content repository |
US9158788B2 (en) | 2009-12-16 | 2015-10-13 | International Business Machines Corporation | Scalable caching of remote file data in a cluster file system |
US8458239B2 (en) | 2009-12-16 | 2013-06-04 | International Business Machines Corporation | Directory traversal in a scalable multi-node file system cache for a remote cluster file system |
US8473582B2 (en) * | 2009-12-16 | 2013-06-25 | International Business Machines Corporation | Disconnected file operations in a scalable multi-node file system cache for a remote cluster file system |
US8495250B2 (en) | 2009-12-16 | 2013-07-23 | International Business Machines Corporation | Asynchronous file operations in a scalable multi-node file system cache for a remote cluster file system |
US9098560B2 (en) * | 2009-12-22 | 2015-08-04 | International Business Machines Corporation | Client message distribution in a distributed directory based on language and character sets |
US9495338B1 (en) * | 2010-01-28 | 2016-11-15 | Amazon Technologies, Inc. | Content distribution network |
US8204860B1 (en) | 2010-02-09 | 2012-06-19 | F5 Networks, Inc. | Methods and systems for snapshot reconstitution |
US9195500B1 (en) | 2010-02-09 | 2015-11-24 | F5 Networks, Inc. | Methods for seamless storage importing and devices thereof |
US8724487B1 (en) * | 2010-02-15 | 2014-05-13 | Cisco Technology, Inc. | System and method for synchronized reporting in a network environment |
US20110258708A1 (en) * | 2010-04-14 | 2011-10-20 | Nokia Corporation | Method, apparatus and computer program product for caching of content from server |
US20110276963A1 (en) * | 2010-05-04 | 2011-11-10 | Riverbed Technology, Inc. | Virtual Data Storage Devices and Applications Over Wide Area Networks |
US8347100B1 (en) | 2010-07-14 | 2013-01-01 | F5 Networks, Inc. | Methods for DNSSEC proxying and deployment amelioration and systems thereof |
US8959288B1 (en) | 2010-07-29 | 2015-02-17 | Violin Memory, Inc. | Identifying invalid cache data |
US8832384B1 (en) | 2010-07-29 | 2014-09-09 | Violin Memory, Inc. | Reassembling abstracted memory accesses for prefetching |
US8468181B2 (en) * | 2010-09-13 | 2013-06-18 | Marvell World Trade Ltd. | Distributed metadata cache |
US9003035B1 (en) | 2010-09-28 | 2015-04-07 | Amazon Technologies, Inc. | Point of presence management in request routing |
US9712484B1 (en) | 2010-09-28 | 2017-07-18 | Amazon Technologies, Inc. | Managing request routing information utilizing client identifiers |
US10958501B1 (en) | 2010-09-28 | 2021-03-23 | Amazon Technologies, Inc. | Request routing information based on client IP groupings |
US8572340B2 (en) | 2010-09-30 | 2013-10-29 | Commvault Systems, Inc. | Systems and methods for retaining and using data block signatures in data protection operations |
US8364652B2 (en) | 2010-09-30 | 2013-01-29 | Commvault Systems, Inc. | Content aligned block-based deduplication |
WO2012045023A2 (en) | 2010-09-30 | 2012-04-05 | Commvault Systems, Inc. | Archiving data objects using secondary copies |
US20120089700A1 (en) * | 2010-10-10 | 2012-04-12 | Contendo, Inc. | Proxy server configured for hierarchical caching and dynamic site acceleration and custom object and associated method |
US9286298B1 (en) | 2010-10-14 | 2016-03-15 | F5 Networks, Inc. | Methods for enhancing management of backup data sets and devices thereof |
US20120102134A1 (en) | 2010-10-21 | 2012-04-26 | International Business Machines Corporation | Cache sharing among branch proxy servers via a master proxy server at a data center |
US8452874B2 (en) | 2010-11-22 | 2013-05-28 | Amazon Technologies, Inc. | Request routing processing |
US9020900B2 (en) | 2010-12-14 | 2015-04-28 | Commvault Systems, Inc. | Distributed deduplicated storage system |
US8954446B2 (en) * | 2010-12-14 | 2015-02-10 | Comm Vault Systems, Inc. | Client-side repository in a networked deduplicated storage system |
US8972689B1 (en) | 2011-02-02 | 2015-03-03 | Violin Memory, Inc. | Apparatus, method and system for using real-time performance feedback for modeling and improving access to solid state media |
EP2485162A1 (en) * | 2011-02-08 | 2012-08-08 | Thomson Licensing | Method of sharing data in a home network and apparatus implementing the method |
US8635416B1 (en) | 2011-03-02 | 2014-01-21 | Violin Memory Inc. | Apparatus, method and system for using shadow drives for alternative drive commands |
US10467042B1 (en) | 2011-04-27 | 2019-11-05 | Amazon Technologies, Inc. | Optimized deployment based upon customer locality |
US8601220B1 (en) | 2011-04-29 | 2013-12-03 | Netapp, Inc. | Transparent data migration in a storage system environment |
CN102222086B (en) * | 2011-05-18 | 2014-11-26 | 广州市动景计算机科技有限公司 | Webpage viewing method and webpage viewing device based on mobile terminal as well as mobile terminal |
US8396836B1 (en) | 2011-06-30 | 2013-03-12 | F5 Networks, Inc. | System for mitigating file virtualization storage import latency |
US9355119B2 (en) * | 2011-09-22 | 2016-05-31 | Netapp, Inc. | Allocation of absent data within filesystems |
US8805956B1 (en) * | 2011-09-27 | 2014-08-12 | Trend Micro, Inc. | Data leakage prevention in cloud-endpoint model |
US8661068B1 (en) * | 2011-09-29 | 2014-02-25 | Emc Corporation | Managing global metadata caches in data storage systems |
US9813491B2 (en) | 2011-10-20 | 2017-11-07 | Oracle International Corporation | Highly available network filer with automatic load balancing and performance adjustment |
US8463850B1 (en) | 2011-10-26 | 2013-06-11 | F5 Networks, Inc. | System and method of algorithmically generating a server side transaction identifier |
US8977704B2 (en) * | 2011-12-29 | 2015-03-10 | Nokia Corporation | Method and apparatus for flexible caching of delivered media |
US9401968B2 (en) | 2012-01-20 | 2016-07-26 | Nokia Techologies Oy | Method and apparatus for enabling pre-fetching of media |
US9020912B1 (en) | 2012-02-20 | 2015-04-28 | F5 Networks, Inc. | Methods for accessing data in a compressed file system and devices thereof |
US9049246B2 (en) * | 2012-02-28 | 2015-06-02 | Red Hat, Inc. | Reducing web page loading time |
US9020890B2 (en) | 2012-03-30 | 2015-04-28 | Commvault Systems, Inc. | Smart archiving and data previewing for mobile devices |
US9154551B1 (en) | 2012-06-11 | 2015-10-06 | Amazon Technologies, Inc. | Processing DNS queries to identify pre-processing information |
US20130339310A1 (en) | 2012-06-13 | 2013-12-19 | Commvault Systems, Inc. | Restore using a client side signature repository in a networked storage system |
US9172744B2 (en) * | 2012-06-14 | 2015-10-27 | Microsoft Technology Licensing, Llc | Scalable storage with programmable networks |
US20140006618A1 (en) * | 2012-06-29 | 2014-01-02 | William M. Pitts | Method of creating path signatures to facilitate the recovery from network link failures |
US8850002B1 (en) * | 2012-07-02 | 2014-09-30 | Amazon Technologies, Inc. | One-to many stateless load balancing |
US9661097B2 (en) * | 2012-09-21 | 2017-05-23 | Evan Geffner | System and method for caching content at an end user'S customer premises equipment |
US9519501B1 (en) | 2012-09-30 | 2016-12-13 | F5 Networks, Inc. | Hardware assisted flow acceleration and L2 SMAC management in a heterogeneous distributed multi-tenant virtualized clustered system |
US9325711B2 (en) | 2012-12-11 | 2016-04-26 | Servmax, Inc. | Apparatus and data processing systems for accessing an object |
US9633022B2 (en) | 2012-12-28 | 2017-04-25 | Commvault Systems, Inc. | Backup and restoration for a deduplicated file system |
US9448941B1 (en) * | 2012-12-31 | 2016-09-20 | Emc Corporation | System and method for cache management |
US9633033B2 (en) | 2013-01-11 | 2017-04-25 | Commvault Systems, Inc. | High availability distributed deduplicated storage system |
US9645950B2 (en) * | 2013-01-31 | 2017-05-09 | Vmware, Inc. | Low-cost backup and edge caching using unused disk blocks |
US10375155B1 (en) | 2013-02-19 | 2019-08-06 | F5 Networks, Inc. | System and method for achieving hardware acceleration for asymmetric flow connections |
US9554418B1 (en) | 2013-02-28 | 2017-01-24 | F5 Networks, Inc. | Device for topology hiding of a visited network |
US9934230B1 (en) | 2013-02-28 | 2018-04-03 | Netapp, Inc. | Delegations for non-regular files |
US9948601B2 (en) | 2013-03-15 | 2018-04-17 | Netflix, Inc. | Evaluation of paths through graph-based data representation |
US9596297B2 (en) | 2013-05-16 | 2017-03-14 | Toshiba Global Commerce Solutions Holdings Corporation | Managing communications in a multi-client, multi-server environment |
US9875120B2 (en) * | 2013-06-24 | 2018-01-23 | Microsoft Technology Licensing, Llc | Virtualized components in computing systems |
US9424027B2 (en) * | 2013-07-29 | 2016-08-23 | Ralph Moore | Message management system for information transfer within a multitasking system |
KR101490516B1 (en) * | 2013-08-19 | 2015-02-05 | 주식회사 솔박스 | Method for providing content based on object and property information and http proxy server using the method |
US10324897B2 (en) | 2014-01-27 | 2019-06-18 | Commvault Systems, Inc. | Techniques for serving archived electronic mail |
US9646091B2 (en) * | 2014-02-24 | 2017-05-09 | Futurewei Technologies, Inc. | File joining on back end device |
JP2015164018A (en) * | 2014-02-28 | 2015-09-10 | 株式会社東芝 | Device, method, and program for providing content |
US9633056B2 (en) | 2014-03-17 | 2017-04-25 | Commvault Systems, Inc. | Maintaining a deduplication database |
US10380072B2 (en) | 2014-03-17 | 2019-08-13 | Commvault Systems, Inc. | Managing deletions from a deduplication database |
EP2922266A1 (en) | 2014-03-20 | 2015-09-23 | Thomson Licensing | Method for operating a cache arranged along a transmission path between client terminals and at least one server, and corresponding cache. |
US10542049B2 (en) | 2014-05-09 | 2020-01-21 | Nutanix, Inc. | Mechanism for providing external access to a secured networked virtualization environment |
US11838851B1 (en) | 2014-07-15 | 2023-12-05 | F5, Inc. | Methods for managing L7 traffic classification and devices thereof |
US11249858B2 (en) | 2014-08-06 | 2022-02-15 | Commvault Systems, Inc. | Point-in-time backups of a production application made accessible over fibre channel and/or ISCSI as data sources to a remote application by representing the backups as pseudo-disks operating apart from the production application and its host |
US9852026B2 (en) | 2014-08-06 | 2017-12-26 | Commvault Systems, Inc. | Efficient application recovery in an information management system based on a pseudo-storage-device driver |
US9575673B2 (en) | 2014-10-29 | 2017-02-21 | Commvault Systems, Inc. | Accessing a file system using tiered deduplication |
US10182013B1 (en) | 2014-12-01 | 2019-01-15 | F5 Networks, Inc. | Methods for managing progressive image delivery and devices thereof |
US10097448B1 (en) | 2014-12-18 | 2018-10-09 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10154068B2 (en) * | 2014-12-30 | 2018-12-11 | Akamai Technologies, Inc. | Self-adjusting tiered caching system to optimize traffic performance and origin offload |
US11895138B1 (en) | 2015-02-02 | 2024-02-06 | F5, Inc. | Methods for improving web scanner accuracy and devices thereof |
US10225326B1 (en) | 2015-03-23 | 2019-03-05 | Amazon Technologies, Inc. | Point of presence based data uploading |
US10834065B1 (en) | 2015-03-31 | 2020-11-10 | F5 Networks, Inc. | Methods for SSL protected NTLM re-authentication and devices thereof |
US10339106B2 (en) | 2015-04-09 | 2019-07-02 | Commvault Systems, Inc. | Highly reusable deduplication database after disaster recovery |
US9832141B1 (en) | 2015-05-13 | 2017-11-28 | Amazon Technologies, Inc. | Routing based request correlation |
US9760591B2 (en) | 2015-05-14 | 2017-09-12 | Walleye Software, LLC | Dynamic code loading |
US10324914B2 (en) | 2015-05-20 | 2019-06-18 | Commvalut Systems, Inc. | Handling user queries against production and archive storage systems, such as for enterprise customers having large and/or numerous files |
US20160350391A1 (en) | 2015-05-26 | 2016-12-01 | Commvault Systems, Inc. | Replication using deduplicated secondary copy data |
US9766825B2 (en) | 2015-07-22 | 2017-09-19 | Commvault Systems, Inc. | Browse and restore for block-level backups |
US10320905B2 (en) | 2015-10-02 | 2019-06-11 | Oracle International Corporation | Highly available network filer super cluster |
US10270878B1 (en) | 2015-11-10 | 2019-04-23 | Amazon Technologies, Inc. | Routing for origin-facing points of presence |
US10592357B2 (en) | 2015-12-30 | 2020-03-17 | Commvault Systems, Inc. | Distributed file system in a distributed deduplication data storage system |
US10404698B1 (en) | 2016-01-15 | 2019-09-03 | F5 Networks, Inc. | Methods for adaptive organization of web application access points in webtops and devices thereof |
US10797888B1 (en) | 2016-01-20 | 2020-10-06 | F5 Networks, Inc. | Methods for secured SCEP enrollment for client devices and devices thereof |
US11669320B2 (en) | 2016-02-12 | 2023-06-06 | Nutanix, Inc. | Self-healing virtualized file server |
US10296368B2 (en) | 2016-03-09 | 2019-05-21 | Commvault Systems, Inc. | Hypervisor-independent block-level live browse for access to backed up virtual machine (VM) data and hypervisor-free file-level recovery (block-level pseudo-mount) |
US10237350B2 (en) * | 2016-04-06 | 2019-03-19 | Reniac, Inc. | System and method for a database proxy |
US11349922B2 (en) | 2016-04-06 | 2022-05-31 | Marvell Asia Pte Ltd. | System and method for a database proxy |
US10795577B2 (en) | 2016-05-16 | 2020-10-06 | Commvault Systems, Inc. | De-duplication of client-side data cache for virtual disks |
US10846024B2 (en) | 2016-05-16 | 2020-11-24 | Commvault Systems, Inc. | Global de-duplication of virtual disks in a storage platform |
US11218418B2 (en) | 2016-05-20 | 2022-01-04 | Nutanix, Inc. | Scalable leadership election in a multi-processing computing environment |
US10075551B1 (en) | 2016-06-06 | 2018-09-11 | Amazon Technologies, Inc. | Request management for hierarchical cache |
AU2017290043A1 (en) * | 2016-06-28 | 2019-01-24 | Solano Labs, Inc. | Systems and methods for efficient distribution of stored data objects |
US10110694B1 (en) | 2016-06-29 | 2018-10-23 | Amazon Technologies, Inc. | Adaptive transfer rate for retrieving content from a server |
US10616250B2 (en) | 2016-10-05 | 2020-04-07 | Amazon Technologies, Inc. | Network addresses with encoded DNS-level information |
US10412198B1 (en) | 2016-10-27 | 2019-09-10 | F5 Networks, Inc. | Methods for improved transmission control protocol (TCP) performance visibility and devices thereof |
US11568073B2 (en) | 2016-12-02 | 2023-01-31 | Nutanix, Inc. | Handling permissions for virtualized file servers |
US11562034B2 (en) | 2016-12-02 | 2023-01-24 | Nutanix, Inc. | Transparent referrals for distributed file servers |
US10824455B2 (en) | 2016-12-02 | 2020-11-03 | Nutanix, Inc. | Virtualized server systems and methods including load balancing for virtualized file servers |
US10728090B2 (en) | 2016-12-02 | 2020-07-28 | Nutanix, Inc. | Configuring network segmentation for a virtualization environment |
US11294777B2 (en) | 2016-12-05 | 2022-04-05 | Nutanix, Inc. | Disaster recovery for distributed file servers, including metadata fixers |
US11288239B2 (en) | 2016-12-06 | 2022-03-29 | Nutanix, Inc. | Cloning virtualized file servers |
US11281484B2 (en) | 2016-12-06 | 2022-03-22 | Nutanix, Inc. | Virtualized server systems and methods including scaling of file system virtual machines |
US10831549B1 (en) | 2016-12-27 | 2020-11-10 | Amazon Technologies, Inc. | Multi-region request-driven code execution system |
US10740193B2 (en) | 2017-02-27 | 2020-08-11 | Commvault Systems, Inc. | Hypervisor-independent reference copies of virtual machine payload data based on block-level pseudo-mount |
US10985967B1 (en) | 2017-03-10 | 2021-04-20 | Loop Commerce, Inc. | Cross-network differential determination |
US11082519B2 (en) * | 2017-05-08 | 2021-08-03 | Salesforce.Com, Inc. | System and method of providing web content using a proxy cache |
US10567492B1 (en) | 2017-05-11 | 2020-02-18 | F5 Networks, Inc. | Methods for load balancing in a federated identity environment and devices thereof |
US11075987B1 (en) | 2017-06-12 | 2021-07-27 | Amazon Technologies, Inc. | Load estimating content delivery network |
US10664352B2 (en) | 2017-06-14 | 2020-05-26 | Commvault Systems, Inc. | Live browsing of backed up data residing on cloned disks |
JP6620788B2 (en) * | 2017-06-15 | 2019-12-18 | 富士通クライアントコンピューティング株式会社 | Data providing system, information processing method, and information processing program |
US10884980B2 (en) * | 2017-07-26 | 2021-01-05 | International Business Machines Corporation | Cognitive file and object management for distributed storage environments |
US10198469B1 (en) | 2017-08-24 | 2019-02-05 | Deephaven Data Labs Llc | Computer data system data source refreshing using an update propagation graph having a merged join listener |
US11163447B2 (en) * | 2017-09-03 | 2021-11-02 | Ashish Govind Khurange | Dedupe file system for bulk data migration to cloud platform |
US10742593B1 (en) | 2017-09-25 | 2020-08-11 | Amazon Technologies, Inc. | Hybrid content request routing system |
US10659531B2 (en) * | 2017-10-06 | 2020-05-19 | International Business Machines Corporation | Initiator aware data migration |
US11223689B1 (en) | 2018-01-05 | 2022-01-11 | F5 Networks, Inc. | Methods for multipath transmission control protocol (MPTCP) based session migration and devices thereof |
EP3756315A1 (en) * | 2018-03-01 | 2020-12-30 | Huawei Technologies Co., Ltd. | Packet-programmable statelets |
US10833943B1 (en) | 2018-03-01 | 2020-11-10 | F5 Networks, Inc. | Methods for service chaining and devices thereof |
CN110389859B (en) * | 2018-04-20 | 2023-07-07 | 伊姆西Ip控股有限责任公司 | Method, apparatus and computer program product for copying data blocks |
US11086826B2 (en) | 2018-04-30 | 2021-08-10 | Nutanix, Inc. | Virtualized server systems and methods including domain joining techniques |
US11194680B2 (en) | 2018-07-20 | 2021-12-07 | Nutanix, Inc. | Two node clusters recovery on a failure |
US11144251B2 (en) * | 2018-10-17 | 2021-10-12 | International Business Machines Corporation | Providing a global unique identifier for a storage volume |
US11770447B2 (en) | 2018-10-31 | 2023-09-26 | Nutanix, Inc. | Managing high-availability file servers |
US11010258B2 (en) | 2018-11-27 | 2021-05-18 | Commvault Systems, Inc. | Generating backup copies through interoperability between components of a data storage management system and appliances for data storage and deduplication |
US11025747B1 (en) | 2018-12-12 | 2021-06-01 | Amazon Technologies, Inc. | Content request pattern-based routing system |
US11698727B2 (en) | 2018-12-14 | 2023-07-11 | Commvault Systems, Inc. | Performing secondary copy operations based on deduplication performance |
US11537575B1 (en) * | 2019-02-04 | 2022-12-27 | Amazon Technologies, Inc. | Real-time database performance tuning |
US10880159B1 (en) * | 2019-03-18 | 2020-12-29 | Amazon Technologies, Inc. | Centralized access of configuration data for computing resources |
US20200327017A1 (en) | 2019-04-10 | 2020-10-15 | Commvault Systems, Inc. | Restore using deduplicated secondary copy data |
US11463264B2 (en) | 2019-05-08 | 2022-10-04 | Commvault Systems, Inc. | Use of data block signatures for monitoring in an information management system |
CN112839071B (en) * | 2019-11-25 | 2024-01-05 | 商汤集团有限公司 | Training system, training data access method and device, electronic equipment and medium |
US20210173811A1 (en) | 2019-12-04 | 2021-06-10 | Commvault Systems, Inc. | Optimizing the restoration of deduplicated data stored in multi-node replicated file systems |
US11429595B2 (en) | 2020-04-01 | 2022-08-30 | Marvell Asia Pte Ltd. | Persistence of write requests in a database proxy |
US11768809B2 (en) | 2020-05-08 | 2023-09-26 | Nutanix, Inc. | Managing incremental snapshots for fast leader node bring-up |
US11687424B2 (en) | 2020-05-28 | 2023-06-27 | Commvault Systems, Inc. | Automated media agent state management |
US11650957B2 (en) * | 2021-06-01 | 2023-05-16 | International Business Machines Corporation | Receiving at a cache node notification of changes to files in a source file system served from a cache file system at the cache node |
US11645238B2 (en) | 2021-06-01 | 2023-05-09 | International Business Machines Corporation | Notifying a cache file system of changes to files in a source file system served from the cache file system |
US11687417B2 (en) * | 2021-10-19 | 2023-06-27 | Spectra Logic Corporation | Secondary storage protection |
CN113961602B (en) * | 2021-10-28 | 2022-08-19 | 中国西安卫星测控中心 | Configuration method of distributed aerospace measurement and control data processing system |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6085234A (en) * | 1994-11-28 | 2000-07-04 | Inca Technology, Inc. | Remote file services network-infrastructure cache |
US20010000083A1 (en) * | 1997-10-28 | 2001-03-29 | Doug Crow | Shared cache parsing and pre-fetch |
Family Cites Families (71)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0619771A (en) * | 1992-04-20 | 1994-01-28 | Internatl Business Mach Corp <Ibm> | File management system of shared file by different kinds of clients |
US6026452A (en) * | 1997-02-26 | 2000-02-15 | Pitts; William Michael | Network distributed site cache RAM claimed as up/down stream request/reply channel for storing anticipated data and meta data |
US5963962A (en) * | 1995-05-31 | 1999-10-05 | Network Appliance, Inc. | Write anywhere file-system layout |
US5713017A (en) * | 1995-06-07 | 1998-01-27 | International Business Machines Corporation | Dual counter consistency control for fault tolerant network file servers |
US5864852A (en) * | 1996-04-26 | 1999-01-26 | Netscape Communications Corporation | Proxy server caching mechanism that provides a file directory structure and a mapping mechanism within the file directory structure |
US6282580B1 (en) * | 1996-07-02 | 2001-08-28 | Sun Microsystems, Inc. | Bridge providing communication between different implementations of object request brokers |
US5893140A (en) * | 1996-08-14 | 1999-04-06 | Emc Corporation | File server having a file system cache and protocol for truly safe asynchronous writes |
US5987506A (en) * | 1996-11-22 | 1999-11-16 | Mangosoft Corporation | Remote access and geographically distributed computers in a globally addressable storage environment |
US6026474A (en) * | 1996-11-22 | 2000-02-15 | Mangosoft Corporation | Shared client-side web caching using globally addressable memory |
WO1998027506A2 (en) * | 1996-12-17 | 1998-06-25 | Inca Technology, Inc. | Ndc consistency reconnect mechanism |
US5924116A (en) * | 1997-04-02 | 1999-07-13 | International Business Machines Corporation | Collaborative caching of a requested object by a lower level node as a function of the caching status of the object at a higher level node |
US5907678A (en) * | 1997-05-07 | 1999-05-25 | International Business Machines Corporation | Client/server system in which protocol caches for multiple sessions are selectively copied into a common checkpoint cache upon receiving a checkpoint request |
US6065058A (en) * | 1997-05-09 | 2000-05-16 | International Business Machines Corp. | Dynamic push filtering based on information exchanged among nodes in a proxy hierarchy |
JP4134357B2 (en) * | 1997-05-15 | 2008-08-20 | 株式会社日立製作所 | Distributed data management method |
US6578113B2 (en) * | 1997-06-02 | 2003-06-10 | At&T Corp. | Method for cache validation for proxy caches |
AU8061798A (en) * | 1997-06-09 | 1998-12-30 | Cacheflow, Inc. | Network object cache engine |
US7103794B2 (en) * | 1998-06-08 | 2006-09-05 | Cacheflow, Inc. | Network object cache engine |
CA2210755C (en) * | 1997-07-17 | 2003-12-23 | Ibm Canada Limited - Ibm Canada Limitee | Creating proxies for distribution of beans and event objects |
US6038601A (en) * | 1997-07-21 | 2000-03-14 | Tibco, Inc. | Method and apparatus for storing and delivering documents on the internet |
US5991810A (en) * | 1997-08-01 | 1999-11-23 | Novell, Inc. | User name authentication for gateway clients accessing a proxy cache server |
US5950205A (en) * | 1997-09-25 | 1999-09-07 | Cisco Technology, Inc. | Data transmission over the internet using a cache memory file system |
US6085193A (en) * | 1997-09-29 | 2000-07-04 | International Business Machines Corporation | Method and system for dynamically prefetching information via a server hierarchy |
WO1999023571A1 (en) * | 1997-11-03 | 1999-05-14 | Inca Technology, Inc. | Automatically configuring network-name-services |
US6292835B1 (en) * | 1997-11-26 | 2001-09-18 | International Business Machines Corporation | Network bandwidth and object obsolescence sensitive scheduling method and apparatus for objects distributed broadcasting |
US6493816B1 (en) * | 1998-03-30 | 2002-12-10 | International Business Machines Corporation | Method and apparatus for encapsulating address translation for shared persistent virtual storage |
US6389460B1 (en) * | 1998-05-13 | 2002-05-14 | Compaq Computer Corporation | Method and apparatus for efficient storage and retrieval of objects in and from an object storage device |
US6311216B1 (en) * | 1998-05-29 | 2001-10-30 | Microsoft Corporation | Method, computer program product, and system for client-side deterministic routing and URL lookup into a distributed cache of URLS |
US6330561B1 (en) * | 1998-06-26 | 2001-12-11 | At&T Corp. | Method and apparatus for improving end to end performance of a data network |
US6338117B1 (en) * | 1998-08-28 | 2002-01-08 | International Business Machines Corporation | System and method for coordinated hierarchical caching and cache replacement |
JP2000112793A (en) * | 1998-10-02 | 2000-04-21 | Toshiba Corp | Method for expanding database, database retrieval system and recording medium |
US6438652B1 (en) * | 1998-10-09 | 2002-08-20 | International Business Machines Corporation | Load balancing cooperating cache servers by shifting forwarded request |
US20020108025A1 (en) * | 1998-10-21 | 2002-08-08 | Nicholas Shaylor | Memory management unit for java environment computers |
US6178461B1 (en) * | 1998-12-08 | 2001-01-23 | Lucent Technologies Inc. | Cache-based compaction technique for internet browsing using similar objects in client cache as reference objects |
US6370620B1 (en) * | 1998-12-10 | 2002-04-09 | International Business Machines Corporation | Web object caching and apparatus for performing the same |
US6381602B1 (en) * | 1999-01-26 | 2002-04-30 | Microsoft Corporation | Enforcing access control on resources at a location other than the source location |
US6237060B1 (en) * | 1999-04-23 | 2001-05-22 | Sun Microsystems, Inc. | Cache management techniques |
US6553411B1 (en) * | 1999-05-18 | 2003-04-22 | International Business Machines Corporation | System and method for cache acceleration |
US6542964B1 (en) * | 1999-06-02 | 2003-04-01 | Blue Coat Systems | Cost-based optimization for content distribution using dynamic protocol selection and query resolution for cache server |
US6658463B1 (en) * | 1999-06-10 | 2003-12-02 | Hughes Electronics Corporation | Satellite multicast performance enhancing multicast HTTP proxy system and method |
US6463508B1 (en) * | 1999-07-19 | 2002-10-08 | International Business Machines Corporation | Method and apparatus for caching a media stream |
US6658462B1 (en) * | 1999-08-26 | 2003-12-02 | International Business Machines Corporation | System, method, and program for balancing cache space requirements with retrieval access time for large documents on the internet |
US6801927B1 (en) * | 1999-09-24 | 2004-10-05 | Akamba Corporation | Network adaptor card with reverse proxy and cache and method implemented therewith |
US6665705B1 (en) * | 1999-10-19 | 2003-12-16 | International Business Machines Corporation | Method and apparatus for proxy replication |
US6823377B1 (en) * | 2000-01-28 | 2004-11-23 | International Business Machines Corporation | Arrangements and methods for latency-sensitive hashing for collaborative web caching |
US7908337B2 (en) * | 2000-04-28 | 2011-03-15 | Adara Networks, Inc. | System and method for using network layer uniform resource locator routing to locate the closest server carrying specific content |
US7577754B2 (en) * | 2000-04-28 | 2009-08-18 | Adara Networks, Inc. | System and method for controlling access to content carried in a caching architecture |
US6760815B1 (en) * | 2000-06-02 | 2004-07-06 | Sun Microsystems, Inc. | Caching mechanism for a virtual heap |
US6854115B1 (en) * | 2000-06-02 | 2005-02-08 | Sun Microsystems, Inc. | Process persistence in a virtual machine |
US6643672B1 (en) * | 2000-07-31 | 2003-11-04 | Hewlett-Packard Development Company, Lp. | Method and apparatus for asynchronous file writes in a distributed file system |
US20020046266A1 (en) * | 2000-08-09 | 2002-04-18 | Muralidhar Kurudi H. | Computer-implemented method and apparatus for the cloning of input/output devices |
GB2366965A (en) * | 2000-09-01 | 2002-03-20 | Ncr Int Inc | Downloading data to a requesting client form the local cache of another client |
AU2002224448A1 (en) | 2000-10-26 | 2002-05-06 | Prismedia Networks, Inc. | Method and apparatus for large payload distribution in a network |
WO2002042874A2 (en) * | 2000-11-22 | 2002-05-30 | Azoth Technologies, Inc. | Method and architecture for serving and caching web objects on the modern internet |
US6741970B2 (en) * | 2001-02-26 | 2004-05-25 | International Business Machines Corporation | Method and apparatus for enhanced, high speed updating and storing of E-commerce orders in a server |
JP4191902B2 (en) * | 2001-02-28 | 2008-12-03 | 株式会社日立製作所 | Content distribution device |
US6813690B1 (en) * | 2001-06-12 | 2004-11-02 | Network Appliance, Inc. | Caching media data using content-sensitive identifiers |
US20030004998A1 (en) * | 2001-06-29 | 2003-01-02 | Chutney Technologies, Inc. | Proxy-based acceleration of dynamically generated content |
US6901410B2 (en) * | 2001-09-10 | 2005-05-31 | Marron Pedro Jose | LDAP-based distributed cache technology for XML |
US7412492B1 (en) * | 2001-09-12 | 2008-08-12 | Vmware, Inc. | Proportional share resource allocation with reduction of unproductive resource consumption |
US7200144B2 (en) * | 2001-10-18 | 2007-04-03 | Qlogic, Corp. | Router and methods using network addresses for virtualization |
US6886077B2 (en) * | 2001-12-21 | 2005-04-26 | International Business Machines Corporation | Context-sensitive caching |
US6907501B2 (en) * | 2002-01-25 | 2005-06-14 | Ntt Docomo Inc. | System for management of cacheable streaming content in a packet based communication network with mobile hosts |
US20030145112A1 (en) * | 2002-01-31 | 2003-07-31 | Keller S. Brandon | Assisted entering of addresses |
US20030163731A1 (en) * | 2002-02-28 | 2003-08-28 | David Wigley | Method, system and software product for restricting access to network accessible digital information |
US9087319B2 (en) * | 2002-03-11 | 2015-07-21 | Oracle America, Inc. | System and method for designing, developing and implementing internet service provider architectures |
US7133905B2 (en) * | 2002-04-09 | 2006-11-07 | Akamai Technologies, Inc. | Method and system for tiered distribution in a content delivery network |
US20030149581A1 (en) * | 2002-08-28 | 2003-08-07 | Imran Chaudhri | Method and system for providing intelligent network content delivery |
US7284030B2 (en) * | 2002-09-16 | 2007-10-16 | Network Appliance, Inc. | Apparatus and method for processing data in a network |
US7171469B2 (en) * | 2002-09-16 | 2007-01-30 | Network Appliance, Inc. | Apparatus and method for storing data in a proxy cache in a network |
US7093359B2 (en) * | 2002-09-17 | 2006-08-22 | Siemens Westinghouse Power Corporation | Composite structure formed by CMC-on-insulation process |
US7567991B2 (en) * | 2003-06-25 | 2009-07-28 | Emc Corporation | Replication of snapshot using a file system copy differential |
-
2002
- 2002-09-16 US US10/245,828 patent/US7171469B2/en not_active Expired - Fee Related
-
2003
- 2003-04-25 US US10/424,142 patent/US7191290B1/en not_active Expired - Fee Related
- 2003-09-16 AU AU2003270764A patent/AU2003270764A1/en not_active Abandoned
- 2003-09-16 EP EP03752475.8A patent/EP1540498B1/en not_active Expired - Lifetime
- 2003-09-16 JP JP2004536622A patent/JP4547264B2/en not_active Expired - Fee Related
- 2003-09-16 WO PCT/US2003/029398 patent/WO2004025429A2/en active Application Filing
-
2007
- 2007-01-16 US US11/654,381 patent/US7631078B2/en not_active Expired - Lifetime
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6085234A (en) * | 1994-11-28 | 2000-07-04 | Inca Technology, Inc. | Remote file services network-infrastructure cache |
US20010000083A1 (en) * | 1997-10-28 | 2001-03-29 | Doug Crow | Shared cache parsing and pre-fetch |
Non-Patent Citations (3)
Title |
---|
DINGLE A ET AL: "Web cache coherence" COMPUTER NETWORKS AND ISDN SYSTEMS, NORTH HOLLAND PUBLISHING. AMSTERDAM, NL, vol. 28, no. 11, May 1996 (1996-05), pages 907-920, XP004018195 ISSN: 0169-7552 * |
See also references of WO2004025429A2 * |
YU H ET AL: "A SCALABLE WEB CACHE CONSISTENCY ARCHITECTURE" COMPUTER COMMUNICATION REVIEW, ASSOCIATION FOR COMPUTING MACHINERY. NEW YORK, US, vol. 29, no. 4, October 1999 (1999-10), pages 163-174, XP000852196 ISSN: 0146-4833 * |
Also Published As
Publication number | Publication date |
---|---|
WO2004025429A3 (en) | 2004-07-01 |
US7171469B2 (en) | 2007-01-30 |
EP1540498A4 (en) | 2005-12-07 |
JP2005539315A (en) | 2005-12-22 |
US20040054777A1 (en) | 2004-03-18 |
US20070192444A1 (en) | 2007-08-16 |
JP4547264B2 (en) | 2010-09-22 |
AU2003270764A8 (en) | 2004-04-30 |
WO2004025429A2 (en) | 2004-03-25 |
EP1540498B1 (en) | 2016-03-30 |
AU2003270764A1 (en) | 2004-04-30 |
US7191290B1 (en) | 2007-03-13 |
US7631078B2 (en) | 2009-12-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7171469B2 (en) | Apparatus and method for storing data in a proxy cache in a network | |
US7284030B2 (en) | Apparatus and method for processing data in a network | |
US7552223B1 (en) | Apparatus and method for data consistency in a proxy cache | |
US7840618B2 (en) | Wide area networked file system | |
US8055702B2 (en) | System and method for caching network file systems | |
US7386674B1 (en) | Method and apparatus to provide a unified readahead scheme for multiple sources | |
US8682916B2 (en) | Remote file virtualization in a switched file system | |
US8015355B1 (en) | System and method for managing hard lock state information in a distributed storage system environment | |
US7721045B1 (en) | System and method for efficiently guaranteeing data consistency to clients of a storage system cluster | |
US6128627A (en) | Consistent data storage in an object cache | |
US7269608B2 (en) | Apparatus and methods for caching objects using main memory and persistent memory | |
US6289358B1 (en) | Delivering alternate versions of objects from an object cache | |
US6209003B1 (en) | Garbage collection in an object cache | |
US7587558B1 (en) | System and method for managing hard lock state information in a distributed storage system environment | |
US20070055703A1 (en) | Namespace server using referral protocols | |
US20070226320A1 (en) | Device, System and Method for Storage and Access of Computer Files | |
US20070088702A1 (en) | Intelligent network client for multi-protocol namespace redirection | |
US20070038697A1 (en) | Multi-protocol namespace server | |
US7249219B1 (en) | Method and apparatus to improve buffer cache hit rate | |
Krzyzanowski | Distributed File Systems Design | |
US7188157B1 (en) | Continuous update of data in a data server system | |
US20240119005A1 (en) | Mechanism to maintain data compliance within a distributed file system | |
US20240119025A1 (en) | Mechanism to maintain data compliance within a distributed file system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20050407 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL LT LV MK |
|
A4 | Supplementary search report drawn up and despatched |
Effective date: 20051021 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: 7G 06F 15/167 B Ipc: 7H 04L 29/06 A |
|
DAX | Request for extension of the european patent (deleted) | ||
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: NETAPP, INC. |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
INTG | Intention to grant announced |
Effective date: 20150930 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 786485 Country of ref document: AT Kind code of ref document: T Effective date: 20160415 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 60348746 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: FP |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160701 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 786485 Country of ref document: AT Kind code of ref document: T Effective date: 20160330 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160801 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 Ref country code: BE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 60348746 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20170103 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20170531 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160930 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160916 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160930 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160930 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160916 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20170927 Year of fee payment: 15 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: NL Payment date: 20170926 Year of fee payment: 15 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20170927 Year of fee payment: 15 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20030916 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20160330 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 60348746 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MM Effective date: 20181001 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20180916 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20181001 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190402 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180916 |