The field of technology is data processing, or, more specifically, methods, apparatus, and products for proactively providing corrective measures for storage arrays.
Data centers may include many computing components including servers, network devices, and storage arrays. As the need for storage of large amounts of data and efficient access to that data increases, storage array technology is advancing. Such storage arrays may provide persistent storage for any number of computing devices in a data center. As the number of storage arrays in a data center increases and the types of such storage arrays begins to vary, different storage arrays may be susceptible to different types of problems. Preventing such disparate types of problems across a large set of storage arrays may be difficult. Further, each corrective measure deployed to prevent such a problem may adversely affect the performance of the storage array's performance during the deployment of the corrective measure.
Methods, apparatus, and products for proactively providing corrective measures for storage arrays are disclosed in this specification. Proactively providing such corrective measures for storage arrays includes: receiving data from a storage array, the data including one or more events; detecting, in dependence upon a problem signature, one or more events from the data indicative of a particular problem, where the problem signature comprises a specification of a pattern of events indicative of the particular problem experienced by at least one other storage array; determining whether the particular problem violates an operational policy of the storage array, the operational policy specifying at least one requirement for an operational metric of the storage array; and if the particular problem violates the operational policy of the storage array, deploying automatically without user intervention one or more corrective measures to prevent the storage array from experiencing the particular problem.
The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular descriptions of exemplary embodiments of the invention as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts of exemplary embodiments of the invention.
Exemplary methods, apparatus, and products for proactively providing corrective measures for storage arrays in accordance with the present invention are described with reference to the accompanying drawings, beginning with
The computing devices (164-170) in the example of
The local area network (160) of
The example storage arrays (102, 104) of
Each storage controller (106, 112) may be implemented in a variety of ways, including as an FPGA (Field Programmable Gate Array), a PLC (Programmable Logic Chip), an ASIC (Application Specific Integrated Circuit), or computing device that includes discrete components such as a central processing unit, computer memory, and various adapters. Each storage controller (106, 112) may, for example, include a data communications adapter configured to support communications via the SAN (158) and the LAN (160). Only one of the storage controllers (112) in the example of
Each write buffer device (148, 152) may be configured to receive, from the storage controller (106, 112), data to be stored in the storage devices (146). Such data may originate from any one of the computing devices (164-170). In the example of
A ‘storage device’ as the term is used in this specification refers to any device configured to record data persistently. The term ‘persistently’ as used here refers to a device's ability to maintain recorded data after loss of a power source. Examples of storage devices may include mechanical, spinning hard disk drives, Solid-state drives (“Flash drives”), and the like.
In addition to being coupled to the computing devices through the SAN (158), the storage arrays may also be coupled to the computing devices through the LAN (160) and to one or more cloud service providers through the Internet (172). The term ‘cloud’ as used in this specification refers to systems and computing environments that provide services to user devices through the sharing of computing resources through a network. Generally, the user device is unaware of the exact computing resources utilized by the cloud system to provide the services. Although in many cases such ‘cloud’ environments or systems are accessible via the Internet, readers of skill in the art will recognize that any system that abstracts the use of shared resources to provide services to a user through any network may be considered a cloud-based system.
One example cloud service in
The system of
The storage array services provider may also detect, in dependence upon a problem signature, one or more events from the data that are indicative of a particular problem. A ‘problem signature’ as the term is used in this specification refers to a specification of a pattern of events indicative of a particular problem experienced by at least one storage array in a multiple array storage environment. In this way, a problem signature may be used to project the occurrence of a problem in one or more storage arrays in the storage environment before that problem is exhibited. The generation of such a problem signature may be based on events from one or more storage arrays that experienced the particular problem. When multiple storage arrays, for example, suffer the same problem, the events leading up to the occurrence of the problem may be cross correlated amongst the arrays to identify a similar pattern of events. Such a pattern of events may be utilized to generate the problem signature for the particular problem. Then, when a storage array experiences the same pattern of events, even before experiencing the particular problem, the storage array services provider may, through the use of the problem signature, detect the events as indicative of the particular problem.
In another embodiment, a particular issue may occur on one or more arrays, set ‘A,’ but that same particular issue may not yet have occurred or have been observed on another one or more arrays, set ‘B.’ To generate a problem signature in such an environment, the one or more storage arrays of set ‘A’ may be inspected for common characteristics, such as software version, controller type, performance settings, and the like. The particular issue may arise on only set A, rather than set B, for various reasons and as an effect of such common characteristics. In some instances, for example, the particular issue may arise on set A due to set A running a newer software version then set B. In such an instance, when set B is upgraded to the newer software version, set B would match the problem signature for the particular issue and a candidate for the proactive upgrades.
In some embodiments, the cloud storage array services provider (176) may assign a severity level to each particular problem or each problem signature. The cloud storage array services provider may classify an application level of the corrective measures in dependence upon the severity of the problem and the potential impact of deploying corrective measures. For example, a problem signature may be classified as follows in descending order of likelihood for application:
In this way, highly severe problems that are common across many storage arrays, regardless of each of the storage arrays' operational policies, may be identified and corrective measures may be applied in accordance with the severity.
The storage array services provider (176) in the example of
If the particular problem violates the operational policy of the storage array, the storage array services provider may, automatically and without user intervention, deploy one or more corrective measures to prevent the storage array from experiencing the particular problem. Examples of corrective measures may include a software upgrade, a firmware upgrade, setting of performance parameters, and the like. In this way, a storage array may be prevented from experiencing a problem that has occurred on other storage arrays and prevented from operating in a manner that violates the operational policy of the storage array. Corrective measures may also include measures other than setting performance parameters. For example, modifying behavior of an algorithm executing on the storage array to prevent a crash or prevent experiencing a known issue or bug.
The term ‘prevent’ as used here may refer to preempt and correct as context requires. That is, in some instances, corrective measures are deployed in order to preempt a problem from occurring in a storage array that has not yet exhibited the problem identified in the problem signature. In such an instance, that problem may have been previously identified in one or more storage arrays in a multiple array storage environment. The one or more storage arrays exhibiting the problem may have similar or common characteristics to the storage array that has not yet exhibited the problem. In this way, through the deployment of corrective measures, a storage array may be preempted from exhibiting the problem that one or more other storage arrays previously exhibited.
In other examples, a problem may have been experienced by a storage array, and through the identification of the problem through the use of the problem signature as described above, corrective measures may correct the problem being experienced. In either case, the effect of the problem is reduced greatly. That is, because the problem or potential for a problem is identified at an early stage, the effect of the problem is greatly reduced. In some embodiments, the problem is avoided entirely and, in others, the problem is corrected at a very early stage.
Deploying corrective actions may be carried out in various ways. In some embodiments, the storage array services provider may deploy one or more corrective measures automatically, without a user's approval or with a user's inferred approval (such as through the user ‘opting-in’ to automatic deployments of corrective measures). In other embodiments, the storage array services provider may be configured to deploy corrective measures only upon a user's explicit approval. Examples of such deployment upon a user's explicit approval may include staging an update of software of the storage array and updating the software only responsive to receiving an approval from the user. Another example of such deployment of corrective actions upon a user's explicit approval may include the storage array services provider (176) recommending to a user a modification of one or more tuning parameters for the storage array. In such embodiments, the storage array services provider may push such modification to the storage array after the user's approves the recommendation.
Additionally, multiple tiers of criticality may be implemented in which problems that are less critical need not be pushed without a user's approval while problems for which corrective measures are highly critical may be automatically pushed without a user's permission. In some instances, such automatic corrective measures may be provided without a user's permission at the time of the deployment of such corrective measures, but with a user's permission to all such deployments. That is, a user may ‘opt-in’ to automatic corrective measures in some embodiments.
In some embodiments, a particular problem may be identified but the problem may not violate an operational policy of the storage array. In such embodiments, the storage array services provider (176) may be configured to flag the particular problem. The storage array services provider may also be configured to take any number of actions in addition to flagging the particular problem such as informing the user of the flagged problem or recommending one or more corrective actions to be carried out.
The arrangement of computing devices, storage arrays, cloud-based service providers, networks and other devices making up the exemplary system illustrated in
Proactively providing corrective measures for storage arrays in accordance with embodiments of the present invention is generally implemented with computers. In the system of
The storage array services provider (176) of
As mentioned above, the problem signature may be generated based on an analysis of data from one or more storage arrays that have experienced the particular problem. In the example of
Although proactively providing corrective measures for storage arrays in a multiple array storage environment is described here as being carried out generally by the storage array services provider (176), readers will understand that such steps may be carried out by other entities and modules. For example, the storage controller may execute a module of computer program instructions that proactively provides corrective measures for storage arrays, a management module (not shown in
Also stored in RAM (214) of the example storage array services provider (176) is an operating system (234). Examples of operating systems useful in computers configured for proactively providing corrective measures for storage arrays according to embodiments of the present invention include UNIX™, Linux™, Microsoft Windows™, and others as will occur to those of skill in the art. The operating system (234) and the cloud-based storage array services module (226) in the example of
The storage array services provider (176) of
The example storage array services provider (176) of
The exemplary storage array services provider (176) of
Readers of skill in the art will recognize that the components of the storage array services provider (176) as depicted in
As mentioned above, a storage array (102) may also be implemented, at least to some extent, as a computer. For further explanation, therefore,
The processor (314) is also coupled for data communications through PCIe (Peripheral Component Interface express) links (308, 310, 312, 322) to several Fibre Channel host bus adapters (302, 304), an Ethernet adapter (306), and a PCIe switch (324). The Fibre Channel host bus adapters (308, 310) may couple the storage controller to a storage area network, such the SAN (158) depicted in the example of
Readers of skill in the art will recognize that these components, protocols, adapters, and architectures are for illustration only, not limitation. Such a storage controller may be implemented in a variety of different ways. Each such way is well within the scope of the present invention.
For further explanation,
The method of
The method of
The method of
If the particular problem violates the operational policy of the storage array, the method of
If the particular problem does not violate the operational policy of the storage array, the method of
In some embodiments, such an action recommendation may include notifying a user of the storage array of physical corrective measures to be carried out by the user. That is, a corrective measure that cannot be carried within the storage array, through a software update or configuration change for example, may be identified as a means to prevent a particular problem. In such an embodiment, a user of the storage array may be notified to take such measures. A physical change, for example, such as utilizing a greater number or fewer number ports, may alleviate a problem identified in a problem signature. Such a corrective measure, however, cannot be applied by a storage array services provider.
Exemplary embodiments of the present invention are described largely in the context of a fully functional computer system. Readers of skill in the art will recognize, however, that the present invention also may be embodied in a computer program product disposed upon computer readable media for use with any suitable data processing system. Such computer readable storage media may be any transitory or non-transitory media. Examples of such media include storage media for machine-readable information, including magnetic media, optical media, or other suitable media. Examples of such media also include magnetic disks in hard drives or diskettes, compact disks for optical drives, magnetic tape, and others as will occur to those of skill in the art. Persons skilled in the art will immediately recognize that any computer system having suitable programming means will be capable of executing the steps of the method of the invention as embodied in a computer program product. Persons skilled in the art will recognize also that, although some of the exemplary embodiments described in this specification are oriented to software installed and executing on computer hardware, nevertheless, alternative embodiments implemented as firmware, as hardware, or as an aggregation of hardware and software are well within the scope of embodiments of the present invention.
It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims.
This application is a continuation application of and claims priority from U.S. patent application Ser. No. 14/920,994, filed on Oct. 23, 2015.
Number | Name | Date | Kind |
---|---|---|---|
5706210 | Kumano et al. | Jan 1998 | A |
5799200 | Brant et al. | Aug 1998 | A |
5933598 | Scales et al. | Aug 1999 | A |
6012032 | Donovan et al. | Jan 2000 | A |
6085333 | DeKoning et al. | Jul 2000 | A |
6643641 | Snyder | Nov 2003 | B1 |
6647514 | Umberger et al. | Nov 2003 | B1 |
6789162 | Talagala et al. | Sep 2004 | B1 |
7089272 | Garthwaite et al. | Aug 2006 | B1 |
7107389 | Inagaki et al. | Sep 2006 | B2 |
7146521 | Nguyen | Dec 2006 | B1 |
7334124 | Pham et al. | Feb 2008 | B2 |
7437530 | Rajan | Oct 2008 | B1 |
7493424 | Bali et al. | Feb 2009 | B1 |
7669029 | Mishra et al. | Feb 2010 | B1 |
7689609 | Lango et al. | Mar 2010 | B2 |
7743191 | Liao | Jun 2010 | B1 |
7899780 | Shmuylovich et al. | Mar 2011 | B1 |
8042163 | Karr et al. | Oct 2011 | B1 |
8086585 | Brashers et al. | Dec 2011 | B1 |
8271700 | Annem et al. | Sep 2012 | B1 |
8387136 | Lee et al. | Feb 2013 | B2 |
8437189 | Montierth et al. | May 2013 | B1 |
8452741 | Kuhr | May 2013 | B1 |
8465332 | Hogan et al. | Jun 2013 | B2 |
8527544 | Colgrove et al. | Sep 2013 | B1 |
8566546 | Marshak et al. | Oct 2013 | B1 |
8578442 | Banerjee | Nov 2013 | B1 |
8613066 | Brezinski et al. | Dec 2013 | B1 |
8620970 | English et al. | Dec 2013 | B2 |
8751463 | Chamness | Jun 2014 | B1 |
8762642 | Bates et al. | Jun 2014 | B2 |
8769622 | Chang et al. | Jul 2014 | B2 |
8800009 | Beda, III et al. | Aug 2014 | B1 |
8812860 | Bray | Aug 2014 | B1 |
8850546 | Field et al. | Sep 2014 | B1 |
8898346 | Simmons | Nov 2014 | B1 |
8909854 | Yamagishi et al. | Dec 2014 | B2 |
8931041 | Banerjee | Jan 2015 | B1 |
8949863 | Coatney et al. | Feb 2015 | B1 |
8984602 | Bailey et al. | Mar 2015 | B1 |
8990905 | Bailey et al. | Mar 2015 | B1 |
9124569 | Hussain et al. | Sep 2015 | B2 |
9134922 | Rajagopal et al. | Sep 2015 | B2 |
9209973 | Aikas et al. | Dec 2015 | B2 |
9250823 | Kamat et al. | Feb 2016 | B1 |
9300660 | Borowiec et al. | Mar 2016 | B1 |
9444822 | Borowiec et al. | Sep 2016 | B1 |
9507532 | Colgrove et al. | Nov 2016 | B1 |
20020013802 | Mori et al. | Jan 2002 | A1 |
20030145172 | Galbraith et al. | Jul 2003 | A1 |
20030191783 | Wolczko et al. | Oct 2003 | A1 |
20030225961 | Chow et al. | Dec 2003 | A1 |
20040080985 | Chang et al. | Apr 2004 | A1 |
20040111573 | Garthwaite | Jun 2004 | A1 |
20040153844 | Ghose | Aug 2004 | A1 |
20040193814 | Erickson et al. | Sep 2004 | A1 |
20040260967 | Guha et al. | Dec 2004 | A1 |
20050160416 | Jamison | Jul 2005 | A1 |
20050188246 | Emberty et al. | Aug 2005 | A1 |
20050216800 | Bicknell | Sep 2005 | A1 |
20060015771 | Vana Gundy et al. | Jan 2006 | A1 |
20060088049 | Kastein et al. | Apr 2006 | A1 |
20060129817 | Borneman et al. | Jun 2006 | A1 |
20060161726 | Lasser | Jul 2006 | A1 |
20060200726 | Gittins | Sep 2006 | A1 |
20060230245 | Gounares et al. | Oct 2006 | A1 |
20060239075 | Williams et al. | Oct 2006 | A1 |
20070022227 | Miki | Jan 2007 | A1 |
20070028068 | Golding et al. | Feb 2007 | A1 |
20070055702 | Fridella et al. | Mar 2007 | A1 |
20070109856 | Pellicone et al. | May 2007 | A1 |
20070150689 | Pandit et al. | Jun 2007 | A1 |
20070168321 | Saito et al. | Jul 2007 | A1 |
20070220227 | Long | Sep 2007 | A1 |
20070294563 | Bose | Dec 2007 | A1 |
20070294564 | Reddin et al. | Dec 2007 | A1 |
20080005587 | Ahlquist | Jan 2008 | A1 |
20080077825 | Bello et al. | Mar 2008 | A1 |
20080162674 | Dahiya | Jul 2008 | A1 |
20080195833 | Park | Aug 2008 | A1 |
20080262890 | Korupolu | Oct 2008 | A1 |
20080270678 | Cornwell et al. | Oct 2008 | A1 |
20080282045 | Biswas et al. | Nov 2008 | A1 |
20090077340 | Johnson et al. | Mar 2009 | A1 |
20090100115 | Park et al. | Apr 2009 | A1 |
20090198889 | Ito et al. | Aug 2009 | A1 |
20090287961 | Austin | Nov 2009 | A1 |
20100052625 | Cagno et al. | Mar 2010 | A1 |
20100211723 | Mukaida | Aug 2010 | A1 |
20100246266 | Park et al. | Sep 2010 | A1 |
20100257142 | Murphy et al. | Oct 2010 | A1 |
20100262764 | Liu et al. | Oct 2010 | A1 |
20100325345 | Ohno et al. | Dec 2010 | A1 |
20100332754 | Lai et al. | Dec 2010 | A1 |
20110072290 | Davis et al. | Mar 2011 | A1 |
20110125955 | Chen | May 2011 | A1 |
20110131231 | Haas et al. | Jun 2011 | A1 |
20110167221 | Pangal et al. | Jul 2011 | A1 |
20120023144 | Rub | Jan 2012 | A1 |
20120054264 | Haugh et al. | Mar 2012 | A1 |
20120079318 | Colgrove et al. | Mar 2012 | A1 |
20120131253 | McKnight et al. | May 2012 | A1 |
20120303581 | Calder et al. | Nov 2012 | A1 |
20120303919 | Hu et al. | Nov 2012 | A1 |
20120311000 | Post et al. | Dec 2012 | A1 |
20130007845 | Chang et al. | Jan 2013 | A1 |
20130031414 | Dhuse et al. | Jan 2013 | A1 |
20130036272 | Nelson | Feb 2013 | A1 |
20130071087 | Motiwala et al. | Mar 2013 | A1 |
20130145447 | Maron | Jun 2013 | A1 |
20130191555 | Liu | Jul 2013 | A1 |
20130198459 | Joshi et al. | Aug 2013 | A1 |
20130205173 | Yoneda | Aug 2013 | A1 |
20130219164 | Hamid | Aug 2013 | A1 |
20130227201 | Talagala et al. | Aug 2013 | A1 |
20130290607 | Chang et al. | Oct 2013 | A1 |
20130311434 | Jones | Nov 2013 | A1 |
20130318297 | Jibbe et al. | Nov 2013 | A1 |
20130326284 | Losh et al. | Dec 2013 | A1 |
20130332614 | Brunk et al. | Dec 2013 | A1 |
20140006357 | Davis et al. | Jan 2014 | A1 |
20140019813 | McLean et al. | Jan 2014 | A1 |
20140020083 | Fetik | Jan 2014 | A1 |
20140074850 | Noel | Mar 2014 | A1 |
20140082715 | Grajek et al. | Mar 2014 | A1 |
20140086146 | Kim et al. | Mar 2014 | A1 |
20140090009 | Li et al. | Mar 2014 | A1 |
20140096220 | Da Cruz Pinto et al. | Apr 2014 | A1 |
20140101434 | Senthurpandi et al. | Apr 2014 | A1 |
20140164774 | Nord et al. | Jun 2014 | A1 |
20140173232 | Reohr et al. | Jun 2014 | A1 |
20140195636 | Karve et al. | Jul 2014 | A1 |
20140201512 | Seethaler et al. | Jul 2014 | A1 |
20140201541 | Paul et al. | Jul 2014 | A1 |
20140208155 | Pan | Jul 2014 | A1 |
20140215590 | Brand | Jul 2014 | A1 |
20140229654 | Goss et al. | Aug 2014 | A1 |
20140230017 | Saib | Aug 2014 | A1 |
20140258526 | Le Sant et al. | Sep 2014 | A1 |
20140282983 | Ju et al. | Sep 2014 | A1 |
20140285917 | Cudak et al. | Sep 2014 | A1 |
20140325262 | Cooper et al. | Oct 2014 | A1 |
20140351627 | Best et al. | Nov 2014 | A1 |
20140373104 | Gaddam et al. | Dec 2014 | A1 |
20140373126 | Hussain et al. | Dec 2014 | A1 |
20150026387 | Sheredy et al. | Jan 2015 | A1 |
20150074463 | Jacoby et al. | Mar 2015 | A1 |
20150089569 | Sondhi et al. | Mar 2015 | A1 |
20150095515 | Krithivas et al. | Apr 2015 | A1 |
20150113203 | Dancho et al. | Apr 2015 | A1 |
20150121137 | McKnight et al. | Apr 2015 | A1 |
20150134920 | Anderson et al. | May 2015 | A1 |
20150149822 | Coronado et al. | May 2015 | A1 |
20150193169 | Sundaram et al. | Jul 2015 | A1 |
20150378888 | Zhang et al. | Dec 2015 | A1 |
20160085606 | Panasko | Mar 2016 | A1 |
20160098323 | Mutha et al. | Apr 2016 | A1 |
20160350009 | Cerreta et al. | Dec 2016 | A1 |
20160352720 | Hu et al. | Dec 2016 | A1 |
20160352830 | Borowiec et al. | Dec 2016 | A1 |
20160352834 | Borowiec et al. | Dec 2016 | A1 |
Number | Date | Country |
---|---|---|
0725324 | Aug 1996 | EP |
3365783 | Aug 2018 | EP |
WO 2012087648 | Jun 2012 | WO |
WO2013071087 | May 2013 | WO |
WO 2014110137 | Jul 2014 | WO |
WO 2016015008 | Dec 2016 | WO |
WO 2016190938 | Dec 2016 | WO |
WO 2016195759 | Dec 2016 | WO |
WO 2016195958 | Dec 2016 | WO |
WO 2016195961 | Dec 2016 | WO |
Entry |
---|
The International Search Report and the Written Opinion received for International Application No. PCT/US2016/016333 from the International Searching Authority (ISA), dated Jun. 8, 2016, 11 pages. |
ETSI, Network Functions Virtualisation (NFV); Resiliency Requirements, ETSI GS NFV-REL 001, V1.1.1 (Jan. 2015), Downloaded from: http://www,etsi.org, Link to Document: http://www.etsi.org/deliver/etsi_gs/NFV-REL/001_099/001/01.01.01_60/gs_NFV-REL001v010101p.pdf, European Telecommunications Standards Institute, 2015, 82 pages. |
Paul Sweere, Creating Storage Class Persistent Memory with NVDIMM, Published in Aug. 2013, Flash Memory Summit 2013, <http://ww.flashmemorysummit.com/English/Collaterals/Proceedings/2013/20130814_T2_Sweere.pdf>, 22 pages. |
PCMag. “Storage Array Definition”. Published May 10, 2013. <http://web.archive.org/web/20130510121646/http://www.pcmag.com/encyclopedia/term/52091/storage-array>, 2 pages. |
Google Search of “storage array define” performed by the Examiner on November 4, 2015 for U.S. Appl. No. 14/725,278, Results limited to entries dated before 2012, 1 page. |
Techopedia. “What is a disk array”. Published Jan. 13, 2012. <http://web.archive.org/web/20120113053358/http://www.techopedia.com/definition/1009/disk-array>, 1 page. |
Webopedia. “What is a disk array”. Published May 26, 2011. <http://web/archive.org/web/20110526081214/http://www.webopedia.com/TERM/D/disk_array.html>, 2 pages. |
Li et al., Access Control for the Services Oriented Architecture, Proceedings of the 2007 ACM Workshop on Secure Web Services (SWS '07), Nov. 2007, pp. 9-17, ACM New York, NY. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EPO) for International Application No. PCT/US2016/015006, dated Apr. 29, 2016, 12 pages. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EPO) for International Application No. PCT/US2016/015008, dated May 4, 2016, 12 pages. |
C. Hota et al., Capability-based Cryptographic Data Access Control in Cloud Computing, Int. J. Advanced Networking and Applications, col. 1, Issue 1, dated Aug. 2011, 10 pages. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EPO) for International Application No. PCT/US2016/020410, dated Jul. 8, 2016, 17 pages. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EPO) for International Application No. PCT/US2016/032084, dated Jul. 18, 2016, 12 pages. |
Faith, “dictzip file format”, GitHub.com (online). [Accessed Jul. 28, 2015], 1 page, URL: https://github.com/fidlej/idzip. |
Wikipedia, “Convergent Encryption”, Wikipedia.org (online), accessed Sep. 8, 2015, 2 pages, URL: en.wikipedia.org/wiki/Convergent_encryption. |
Storer et al., “Secure Data Deduplication”, Proceedings of the 4th ACM International Workshop on Storage Security and Survivability (StorageSS'08), Oct. 2008, 10 pages, ACM New York, NY. USA. DOI: 10.1145/1456469.1456471. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EPO) for International Application No. PCT/US2016/032052, dated Aug. 30, 2016, 17 pages. |
Microsoft, “Hybrid for SharePoint Server 2013—Security Reference Architecture”, <http://hybrid.office.com/img/Security_Reference_Architecture.pdf> (online), dated Oct. 2014, 53 pages. |
Microsoft, “Hybrid Identity”, <http://aka.ms/HybridIdentityWp> (online), dated Apr. 2014, 36 pages. |
Microsoft, “Hybrid Identity Management”, <http://download.microsoft.com/download/E/A/E/EAE57CD1-A80B-423C-96BB-142FAAC630B9/Hybrid_Identity_Datasheet.pdf> (online), published Apr. 2014, 17 pages. |
Jacob Bellamy-McIntyre et al., “OpenID and the Enterprise: A Model-based Analysis of Single Sign-On Authentication”, 2011 15th IEEE International Enterprise Distributed Object Computing Conference (EDOC), DOI: 10.1109/EDOC.2011.26, ISBN: 978-1-4577-0362-1, <https://www.cs.auckland.ac.nz/˜lutteroth/publications/McIntyreLutterothWeber2011-OpenID.pdf> (online), dated Aug. 29, 2011, 10 pages. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EPO) for International Application No. PCT/US2016/035492, dated Aug. 17, 2016, 10 pages. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EPO) for International Application No. PCT/US2016/036693, dated Aug. 29, 2015, 10 pages. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EP) for International Application No. PCT/US2016/038758, dated Oct. 7, 2016, 10 pages. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EP) for International Application No. PCT/US2016/040393, dated Sep. 22, 2016, 10 pages. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EP) for International Application No. PCT/US2016/044020, dated Sep. 30, 2016, 11 pages. |
Kwok Kong, Using PCI Express as the Primary System Interconnect in Multiroot Compute, Storage, Communications and Embedded Systems, IDT, White Paper, <http://www.idt.com/document/whp/idt-pcie-multi-root-white-paper>, retrieved by WIPO Dec. 4, 2014, dated Aug. 28, 2008, 12 pages. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EP) for International Application No. PCT/US2016/044874, dated Oct. 7, 2016, 11 pages. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EP) for International Application No. PCT/US2016/044875, dated Oct. 5, 2016, 13 pages. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EP) for International Application No. PCT/US2016/044876, dated Oct. 21, 2016, 12 pages. |
The International Search Report and the Written Opinion received from the International Searching Authority (ISA/EP) for International Application No. PCT/US2016/044877, dated Sep. 29, 2016, 13 pages. |
Xiao-Yu Hu et al., Container Marking: Combining Data Placement, Garbage Collection and Wear Levelling for Flash, 19th Annual IEEE International Symposium on Modelling, Analysis, and Simulation of Computer and Telecommunications Systems, ISBN: 978-0-7695-4430-4, DOI: 10.1109/MASCOTS.2011.50, dated Jul. 25-27, 2011, 11 pages. |
Number | Date | Country | |
---|---|---|---|
Parent | 14920994 | Oct 2015 | US |
Child | 15179301 | US |