IP Library › Granted Patent US 12,373,311
Granted Patent B2
US 12,373,311 · App. 18/331,881 · Granted Jul 29, 2025

Failover and recovery for replicated data instances

Inventors: Grant Alexander MacDonald McAlister (Seattle, WA); Swaminathan Sivasubramanian (Sammamish, WA)
Assignee: Amazon Technologies, Inc.
G06F11/1469G06F11/1443G06F11/1451G06F11/1464G06F11/2025G06F11/2056G06F11/2064G06F11/2069G06F11/2082G06F11/3006G06F16/178G06F16/275G06F11/2028G06F11/2041G06F11/2048G06F11/2076
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,373,311
App. No.
18/331,881
Granted
Jul 29, 2025
Kind
B2
Abstract

Replicated instances in a database environment provide for automatic failover and recovery. A monitoring component can periodically communicate with a primary and a secondary replica for an instance, with each capable of residing in a separate data zone or geographic location to provide a level of reliability and availability. A database running on the primary instance can have information synchronously replicated to the secondary replica at a block level, such that the primary and secondary replicas are in sync. In the event that the monitoring component is not able to communicate with one of the replicas, the monitoring component can attempt to determine whether those replicas can communicate with each other, as well as whether the replicas have the same data generation version. Depending on the state information, the monitoring component can automatically perform a recovery operation, such as to failover to the secondary replica or perform secondary replica recovery.

Claims (34)

1. A system, comprising:

a plurality of computing devices, respectively comprising one or more processors and a memory, that implement a cloud-based database service;

wherein the cloud-based database service is configured to:

detect a failure of a first replica of a database in a first data zone comprising a first one or more data centers, wherein the database is synchronously replicated to a second replica of the database in a second data zone comprising a second one or more data centers, wherein the second data zone is selected out of a plurality of data zones offered by a database service that hosts the database via an interface of the database service and wherein the selection of the second data zone is to create the second replica of the database in the second data zone;

responsive to the detection of the failure:

perform a failover to the second replica of the database in the second data zone from the first replica of the database in the first data zone; and

route client requests directed to the database to the second replica of the database in the second data zone instead of the first replica of the database in the first data zone without requiring a change in an address used by the clients to access the database at the first replica of the database in the first data zone prior to performing the failover.

2. The system of claim 1 , wherein the cloud-based database service is further configured to monitor health of the first replica of the database, wherein the failure of the first replica of the database is detected as a result of the monitoring.

3. The system of claim 1 , wherein the cloud-based database service is further configured to store an event indicative of the failure of the first replica as part of a log accessible via an interface.

4. The system of claim 1 , wherein the cloud-based database service is further configured to receive a request that enables replication of the database across the first data zone and second data zone.

5. The system of claim 1 , wherein the cloud-based database service is further configured to receive a request to create the database that specifies a replication parameter set to “true”.

6. The system of claim 1 , wherein the cloud-based database service is further configured to provide information regarding the failure in further response to the detection of the failure.

7. The system of claim 1 , wherein the second replica is a standby replica.

8. A method, comprising:

detecting, at a cloud-based database service, a failure of a first replica of a database in a first data zone comprising a first one or more data centers, wherein the database is synchronously replicated to a second replica of the database in a second data zone comprising a second one or more data centers, wherein the second data zone is selected out of a plurality of data zones offered by a database service that hosts the database via an interface of the database service and wherein the selection of the second data zone is to create the second replica of the database in the second data zone;

responsive to detecting the failure:

performing, by the cloud-based database service, a failover to the second replica of the database in the second data zone from the first replica of the database in the first data zone; and

routing, by the cloud-based database service, client requests directed to the database to the second replica of the database in the second data zone instead of the first replica of the database in the first data zone without requiring a change in an address used by the clients to access the database at the first replica of the database in the first data zone prior to performing the failover.

9. The method of claim 8 , further comprising monitoring health of the first replica of the database, wherein the failure of the first replica of the database is detected as a result of the monitoring.

10. The method of claim 8 , further comprising storing an event indicative of the failure of the first replica as part of a log accessible via an interface.

11. The method of claim 8 , further comprising receiving a request that enables replication of the database across the first data zone and second data zone.

12. The method of claim 8 , further comprising receiving a request to create the database that specifies a replication parameter set to “true”.

13. The method of claim 8 , further comprising providing information regarding the failure in further response to the detection of the failure.

14. The method of claim 8 , wherein the second replica is a standby replica.

15. One or more non-transitory computer-readable storage media storing program instructions that, when executed on or across one or more computing devices, cause the one or more computing devices to implement a cloud-based database service:

detecting, at the cloud-based database service, a failure of a first replica of a database in a first data zone comprising a first one or more data centers, wherein the database is synchronously replicated to a second replica of the database in a second data zone comprising a second one or more data centers, wherein the second data zone is selected out of a plurality of data zones offered by a database service that hosts the database via an interface of the database service and wherein the selection of the second data zone is to create the second replica of the database in the second data zone;

responsive to detecting the failure:

performing, by the cloud-based database service, a failover to the second replica of the database in the second data zone from the first replica of the database in the first data zone; and

routing, by the cloud-based database service, client requests directed to the database to the second replica of the database in the second data zone instead of the first replica of the database in the first data zone without requiring a change in an address used by the clients to access the database at the first replica of the database in the first data zone prior to performing the failover.

16. The one or more non-transitory computer-readable storage media of claim 15 , storing further program instructions that when executed on or across the one or more computing devices, cause the one or more computing devices to further implement monitoring health of the first replica of the database, wherein the failure of the first replica of the database is detected as a result of the monitoring.

17. The one or more non-transitory computer-readable storage media of claim 15 , storing further program instructions that when executed on or across the one or more computing devices, cause the one or more computing devices to further implement storing an event indicative of the failure of the first replica as part of a log accessible via an interface.

18. The one or more non-transitory computer-readable storage media of claim 15 , storing further program instructions that when executed on or across the one or more computing devices, cause the one or more computing devices to further implement receiving a request that enables replication of the database across the first data zone and second data zone.

19. The one or more non-transitory computer-readable storage media of claim 15 , storing further program instructions that when executed on or across the one or more computing devices, cause the one or more computing devices to further implement receiving a request to create the database that specifies a replication parameter set to “true”.

20. The one or more non-transitory computer-readable storage media of claim 15 , storing further program instructions that when executed on or across the one or more computing devices, cause the one or more computing devices to further implement providing information regarding the failure in further response to the detection of the failure.

Continuity (7)
Continuation 17112731 · Dec 4, 2020
Continuation 15811565 · Nov 13, 2017
Continuation 15083210 · Mar 28, 2016
Continuation 14089616 · Nov 25, 2013
Continuation 13299601 · Nov 18, 2011
Continuation 12606097 · Oct 26, 2009
Related Publication 20230393953A1 · Dec 7, 2023
References Cited (277)
US 5555404A · Torbjørnsen et al. · 1996 [cited by applicant]
US 6018746A · Hill et al. · 2000 [cited by applicant]
US 6205465B1 · Schoening et al. · 2001 [cited by applicant]
US 6442707B1 · McGarth et al. · 2002 [cited by applicant]
US 6542907B1 · Cohen · 2003 [cited by applicant]
US 6560639B1 · Dan et al. · 2003 [cited by applicant]
US 6611867B1 · Bowman-Amuah · 2003 [cited by applicant]
US 6671821B1 · Castro et al. · 2003 [cited by applicant]
US 6675229B1 · Porter et al. · 2004 [cited by applicant]
US 6718481B1 · Fair · 2004 [cited by applicant]
US 6961768B2 · Davis et al. · 2005 [cited by applicant]
US 6981135B1 · Trask · 2005 [cited by applicant]
US 6985955B2 · Gullotta et al. · 2006 [cited by applicant]
US 6988139B1 · Jervis et al. · 2006 [cited by applicant]
US 7062559B2 · Yoshimura et al. · 2006 [cited by applicant]
US 7065624B1 · Zahavi · 2006 [cited by applicant]
US 7111194B1 · Schoenthal et al. · 2006 [cited by applicant]
US 7124289B1 · Suorsa · 2006 [cited by applicant]
US 7133907B2 · Carlson et al. · 2006 [cited by applicant]
US 7315826B1 · Guheen et al. · 2008 [cited by applicant]
US 7363382B1 · Bakke · 2008 [cited by examiner]
US 7415484B1 · Tulkoff et al. · 2008 [cited by applicant]
US 7418484B2 · Presley · 2008 [cited by applicant]
US 7478263B1 · Kownacki et al. · 2009 [cited by applicant]
US 7502329B2 · Li et al. · 2009 [cited by applicant]
US 7506021B2 · Polan et al. · 2009 [cited by applicant]
US 7536686B2 · Tan · 2009 [cited by applicant]
US 7624133B1 · Ojalvo · 2009 [cited by applicant]
US 7680771B2 · Cialini et al. · 2010 [cited by applicant]
US 7685292B1 · Kinsella et al. · 2010 [cited by applicant]
US 7734947B1 · Frangioso et al. · 2010 [cited by applicant]
US 7739543B1 · Pittman · 2010 [cited by examiner]
US 7769721B2 · Jeoka et al. · 2010 [cited by applicant]
US 7801932B2 · Krishnaswamy · 2010 [cited by applicant]
US 7877783B1 · Cline et al. · 2011 [cited by applicant]
US 7966528B2 · Troppmann et al. · 2011 [cited by applicant]
US 7971094B1 · Benn et al. · 2011 [cited by applicant]
US 7991749B2 · Nishikawa et al. · 2011 [cited by applicant]
US 8020037B1 · Schwartz et al. · 2011 [cited by applicant]
US 8041679B1 · Narayanan · 2011 [cited by applicant]
US 8074107B2 · Sivasubramanian et al. · 2011 [cited by applicant]
US 8078587B2 · Wahlert et al. · 2011 [cited by applicant]
US 8121981B2 · Simek et al. · 2012 [cited by applicant]
US 8150808B2 · Zha et al. · 2012 [cited by applicant]
US 8150904B2 · Queck et al. · 2012 [cited by applicant]
US 8156082B2 · Srivastava et al. · 2012 [cited by applicant]
US 8161318B2 · D'Souza et al. · 2012 [cited by applicant]
US 8307003B1 · Sheth et al. · 2012 [cited by applicant]
US 8352608B1 · Keagy et al. · 2013 [cited by applicant]
US 8364460B2 · Ostermeyer et al. · 2013 [cited by applicant]
US 8392915B2 · Friedman et al. · 2013 [cited by applicant]
US 8595547B1 · Sivasubramanian et al. · 2013 [cited by applicant]
US 9298728B2 · McAlister et al. · 2016 [cited by applicant]
US 9806978B2 · McAlister et al. · 2017 [cited by applicant]
US 10860439B2 · McAlister et al. · 2020 [cited by applicant]
US 20020019844A1 · Kurowski et al. · 2002 [cited by applicant]
US 20020032883A1 · Kampe et al. · 2002 [cited by applicant]
US 20020097672A1 · Barbas et al. · 2002 [cited by applicant]
US 20020147709A1 · Rajarajan et al. · 2002 [cited by applicant]
US 20030005091A1 · Ullmann et al. · 2003 [cited by applicant]
US 20030158940A1 · Leigh · 2003 [cited by applicant]
US 20030212775A1 · Steele et al. · 2003 [cited by applicant]
US 20030212898A1 · Steele et al. · 2003 [cited by applicant]
US 20040010487A1 · Prahlad et al. · 2004 [cited by applicant]
US 20040073676A1 · Honma et al. · 2004 [cited by applicant]
US 20040078637A1 · Fellin et al. · 2004 [cited by applicant]
US 20040148443A1 · Achiwa · 2004 [cited by applicant]
US 20040163008A1 · Kim · 2004 [cited by applicant]
US 20040174823A1 · Steele et al. · 2004 [cited by applicant]
US 20040225659A1 · O'Brien et al. · 2004 [cited by applicant]
US 20040236983A1 · Burton et al. · 2004 [cited by applicant]
US 20040260972A1 · Ji et al. · 2004 [cited by applicant]
US 20040260976A1 · Ji et al. · 2004 [cited by applicant]
US 20040260977A1 · Ji et al. · 2004 [cited by applicant]
US 20040268177A1 · Ji et al. · 2004 [cited by applicant]
US 20050004999A1 · Moore et al. · 2005 [cited by applicant]
US 20050027845A1 · Secor et al. · 2005 [cited by applicant]
US 20050038831A1 · Souder et al. · 2005 [cited by applicant]
US 20050050392A1 · Baba et al. · 2005 [cited by applicant]
US 20050114410A1 · Fujibayashi · 2005 [cited by applicant]
US 20050193245A1 · Hayden et al. · 2005 [cited by applicant]
US 20050198327A1 · Iwamura et al. · 2005 [cited by applicant]
US 20050210128A1 · Cannon et al. · 2005 [cited by applicant]
US 20050216788A1 · Mani-Meitav et al. · 2005 [cited by applicant]
US 20050243611A1 · Lubbers et al. · 2005 [cited by applicant]
US 20050262164A1 · Guiheneuf et al. · 2005 [cited by applicant]
US 20050283655A1 · Ashmore · 2005 [cited by applicant]
US 20060041641A1 · Breiter et al. · 2006 [cited by applicant]
US 20060053251A1 · Nicholson et al. · 2006 [cited by applicant]
US 20060104231A1 · Gidwani · 2006 [cited by applicant]
US 20060106675A1 · Cohen et al. · 2006 [cited by applicant]
US 20060106774A1 · Cohen et al. · 2006 [cited by applicant]
US 20060136929A1 · Miller et al. · 2006 [cited by applicant]
US 20070006015A1 · Rao et al. · 2007 [cited by applicant]
US 20070022122A1 · Bahar et al. · 2007 [cited by applicant]
US 20070061266A1 · Moore et al. · 2007 [cited by applicant]
US 20070061487A1 · Moore et al. · 2007 [cited by applicant]
US 20070083588A1 · Keller et al. · 2007 [cited by applicant]
US 20070094467A1 · Yamasaki · 2007 [cited by applicant]
US 20070156842A1 · Vermeulen et al. · 2007 [cited by applicant]
US 20070156872A1 · Stoyanova · 2007 [cited by applicant]
US 20070162420A1 · Ou et al. · 2007 [cited by applicant]
US 20070174691A1 · D'Souza et al. · 2007 [cited by applicant]
US 20070192329A1 · Croft et al. · 2007 [cited by applicant]
US 20070196700A1 · Chen et al. · 2007 [cited by applicant]
US 20070198700A1 · Vivian et al. · 2007 [cited by applicant]
US 20070234028A1 · Rothman et al. · 2007 [cited by applicant]
US 20070234115A1 · Saika · 2007 [cited by applicant]
US 20070244996A1 · Ahmed et al. · 2007 [cited by applicant]
US 20070260693A1 · Cardone et al. · 2007 [cited by applicant]
US 20070260696A1 · Bohannon et al. · 2007 [cited by applicant]
US 20070260912A1 · Hatasaki et al. · 2007 [cited by applicant]
US 20070271275A1 · Fassette et al. · 2007 [cited by applicant]
US 20070283443A1 · McPherson et al. · 2007 [cited by applicant]
US 20070288481A1 · Shinn et al. · 2007 [cited by applicant]
US 20070288526A1 · Mankad et al. · 2007 [cited by applicant]
US 20070288799A1 · Iguchi et al. · 2007 [cited by applicant]
US 20070299828A1 · Lewis et al. · 2007 [cited by applicant]
US 20070299955A1 · Hoffman et al. · 2007 [cited by applicant]
US 20080010513A1 · Devarakonda et al. · 2008 [cited by applicant]
US 20080016293A1 · Saika · 2008 [cited by applicant]
US 20080040509A1 · Werb et al. · 2008 [cited by applicant]
US 20080052327A1 · Buah · 2008 [cited by applicant]
US 20080065650A1 · Kim et al. · 2008 [cited by applicant]
US 20080104443A1 · Akutsu et al. · 2008 [cited by applicant]
US 20080109448A1 · Aboel-Nil et al. · 2008 [cited by applicant]
US 20080126734A1 · Murase · 2008 [cited by applicant]
US 20080134176A1 · Fitzgerald et al. · 2008 [cited by applicant]
US 20080134178A1 · Fitzgerald et al. · 2008 [cited by applicant]
US 20080183991A1 · Cosmadopoulos et al. · 2008 [cited by applicant]
US 20080189413A1 · Srivastava et al. · 2008 [cited by applicant]
US 20080263388A1 · Allen et al. · 2008 [cited by applicant]
US 20080301663A1 · Bahat et al. · 2008 [cited by applicant]
US 20090006888A1 · Bernhard et al. · 2009 [cited by applicant]
US 20090019535A1 · Mishra et al. · 2009 [cited by applicant]
US 20090037425A1 · Erickson et al. · 2009 [cited by applicant]
US 20090106411A1 · Lisiecki et al. · 2009 [cited by applicant]
US 20090158081A1 · Dake · 2009 [cited by examiner]
US 20090164853A1 · Gokhale et al. · 2009 [cited by applicant]
US 20090198940A1 · Ash et al. · 2009 [cited by applicant]
US 20090216881A1 · Ovy et al. · 2009 [cited by applicant]
US 20090271656A1 · Yokota et al. · 2009 [cited by applicant]
US 20090328065A1 · Wookey · 2009 [cited by applicant]
US 20100005531A1 · Largman et al. · 2010 [cited by applicant]
US 20100036851A1 · Paterson-Jones et al. · 2010 [cited by applicant]
US 20100077160A1 · Liu et al. · 2010 [cited by applicant]
US 20100169707A1 · Mathew et al. · 2010 [cited by applicant]
US 20100191713A1 · Lomet et al. · 2010 [cited by applicant]
US 20100211548A1 · Ott et al. · 2010 [cited by applicant]
US 20100250499A1 · McAlister et al. · 2010 [cited by applicant]
US 20100250748A1 · Sivasubramanian et al. · 2010 [cited by applicant]
US 20100251002A1 · Sivasubramanian et al. · 2010 [cited by applicant]
US 20100251242A1 · Sivasubramanian et al. · 2010 [cited by applicant]
US 20100251339A1 · McAlister · 2010 [cited by applicant]
US 20100262861A1 · Mazina · 2010 [cited by applicant]
US 20110004457A1 · Haviv et al. · 2011 [cited by applicant]
US 20110022883A1 · Hansen · 2011 [cited by applicant]
US 20110083138A1 · Sivasubramanian et al. · 2011 [cited by applicant]
US 20110099146A1 · McAlister et al. · 2011 [cited by applicant]
US 20110099147A1 · McAlister et al. · 2011 [cited by applicant]
US 20110099420A1 · MacDonald McAlister et al. · 2011 [cited by applicant]
US 20110178793A1 · Giffin et al. · 2011 [cited by applicant]
US 20110288847A1 · Narayanan et al. · 2011 [cited by applicant]
CN 101099172 · 2008 [cited by applicant]
CN 101501668 · 2009 [cited by applicant]
CN 101501688 · 2009 [cited by applicant]
CN 101512507 · 2009 [cited by applicant]
CN 101539841 · 2009 [cited by applicant]
FR 2870020 · 2005 [cited by applicant]
JP 2003330781 · 2003 [cited by applicant]
JP 2004206696 · 2004 [cited by applicant]
JP 2004272884 · 2004 [cited by applicant]
JP 2004362596 · 2004 [cited by applicant]
JP 2005339131 · 2005 [cited by applicant]
JP 2006048670 · 2006 [cited by applicant]
JP 2006065845 · 2006 [cited by applicant]
JP 2007115007 · 2007 [cited by applicant]
JP 2007516510 · 2007 [cited by applicant]
JP 2008009809 · 2008 [cited by applicant]
JP 2009522659 · 2009 [cited by applicant]
JP 2009230742 · 2009 [cited by applicant]
JP 2010533911 · 2010 [cited by applicant]
WO 2008014585 · 2008 [cited by applicant]
WO 2009012296 · 2009 [cited by applicant]
WO 2009036073 · 2009 [cited by applicant]
International Search Report mailed on Dec. 21, 2010, for International Application No. PCT/US10/54139 filed on Oct. 26, 2010, 2 pages. [cited by applicant]
Notice of Rejection mailed Sep. 10, 2013; in corresponding Japanese patent application No. 2012-536965. [cited by applicant]
International Search Report mailed on May 25, 2010 for International Application No. PCT/US10/029476 filed on Mar. 31, 2010, 2 pages. [cited by applicant]
International Search Report mailed on Dec. 2, 2010 for International Application No. PCT/US10/051757 filed on Oct. 7, 2010, 2 pages. [cited by applicant]
International Search Report mailed on Dec. 21, 2010 for International Application No. PCT/US10/54133 filed on Oct. 26, 2010, 2 pages. [cited by applicant]
International Search Report mailed on Dec. 21, 2010 for International Application No. PCT/US10/54141 filed on Oct. 26, 2010, 2 pages. [cited by applicant]
International Search Report mailed on Dec. 2, 2010 for International Application No. PCT/US10/54133 filed on Oct. 7, 2010, 2 pages. [cited by applicant]
Extended European Search Report for Application No. 10827394.7, Dated Oct. 13, 2015, Amazon Technologies, Inc., pp. 1-6. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Dec. 30, 2013; in corresponding U.S. Appl. No. 13/621,073. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Mar. 16, 2012; in corresponding U.S. Appl. No. 12/418,475. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Mar. 9, 2012; in corresponding U.S. Appl. No. 12/415,958. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Apr. 15, 2011; in corresponding U.S. Appl. No. 12/415,987. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Apr. 18, 2013; in corresponding U.S. Appl. No. 13/620,962. [cited by applicant]
Notice of Allowance and fee(s) Due mailed Jun. 1, 2012; in corresponding U.S. Appl. No. 12/415,968. [cited by applicant]
Amazon HQ Wiki, , “RDSMySQLConfigManagemenl/ConfigWorkflowDesign”, RDS/EDS/DesignDocs/7RDSMySQLConfigManagemenl/ConfigWorkflowDesign from hllps://w.amazon.com/index. [cited by applicant]
Battles, Breit et al., “Reducing Data Center Power Consumption Through Efficient Storage”, Google Scholar, <http://www.it-executive.nl/images/downloads/reducing-datacenter-power.pdf>, 2007, 9 pages. [cited by applicant]
Cordy, James R. , “Practical Language-Independent Detection of Near-Miss Clones”, ACM, <http:// delivery.acm.org/10.1145/1040000/1034915/p1-cordy.pdf>, 2001, 12 pages. [cited by applicant]
Ghemawat, Sanjay et al., “The Google File System”, SOSP'03, Bolton Landing, New York., Oct. 19, 2003, 15 pages. [cited by applicant]
Lahiri, Tirthankar et al., “Cache Fusion: Extending Shared—Disk Clusters with Shared Caches”, 27th VLDB Conference; Roma, Italy., 2001, 4 pages. [cited by applicant]
Lomet, David et al., “Recovery from ”Bad“ User Transactions”, ACM, <http://delivery.acmorg/10.1145/1150000/1142512/p337-lomel.pdf>, 2006, 10 pages. [cited by applicant]
Lorentz, Diana et al., “Oracle 9i SQL”, Release 2 (9.2), Oracle Corporation., 2002, 5 pages. [cited by applicant]
Mietzner, Ralph et al., “Towards Provisioning the Cloud: On the Usage of Multi-Granularity Flows and Services to Realize a Unified Provisioning Infrastructure for Saas Applications”, 2008 IEEE Congress on Services, Part… [cited by applicant]
Wang, Yi et al., “Virtual Routers on the Move: Live Router Migration as a Network- Management Primitive”, ACM, <http://delivery.acm.org/10.1145/1410000/1402985/p231-wang.pdf>, 2008, 12 pages. [cited by applicant]
Amazon HQ Wiki, , “RDSMySQLConfigManagemenl/ConfigExecSummary”, RDS/EDS/DesignDocs/RDSMySQLConfigManagemenl/ConfigExecSummary from hllps://w.amazon.com/index.php/RDS/EDS/ConfigExecSummary; downloaded Aug. 11, 2009, 2009. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Jun. 26, 2012; in corresponding U.S. Appl. No. 12/606,093. [cited by applicant]
Notice of Allowance mailed Jun. 28, 2012; in corresponding U.S. Appl. No. 12/418,475. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Jul. 12, 2011; in corresponding U.S. Appl. No. 12/606,097. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Jul. 5, 2012; in U.S. Appl. No. 12/415,958. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Jul. 9, 2013; in corresponding Japanese patent application No. 2012-533307. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Aug. 12, 2013; in corresponding U.S. Appl. No. 13/299,601. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Aug. 26, 2013; in corresponding U.S. Appl. No. 13/620,962. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Aug. 8, 2011; in corresponding U.S. Appl. No. 12/415,987. [cited by applicant]
Office Action mailed Oct. 3, 2013; in corresponding Canadian patent application No. 2,755,913. [cited by applicant]
Supplemental Notice of Allowance and Fee(s) Due mailed Oct. 25, 2013; in corresponding U.S. Appl. No. 13/294,099. [cited by applicant]
Written Opinion mailed Oct. 2, 2012; in corresponding Singapore patent application No. 201202967-4. [cited by applicant]
Written Opinion mailed Feb. 15, 2012; in corresponding Singapore patent application No. 201107040-6. [cited by applicant]
International Search Report mailed Dec. 23, 2010; in corresponding PCT patent application No. PCT/US10/54133. [cited by applicant]
Non-Final Office Action mailed Apr. 9, 2014; in corresponding U.S. Appl. No. 12/416,017. [cited by applicant]
Non-Final Office Action mailed May 7, 2014; in corresponding U.S. Appl. No. 13/621,044. [cited by applicant]
English translation of The First Office Action mailed Jun. 26, 2014; in corresponding Chinese patent application No. 201080056327.0. [cited by applicant]
The First Office Action mailed Jun. 26, 2014; in corresponding Chinese patent application No. 201080056327.0. [cited by applicant]
Final Office Action mailed Jul. 22, 2014; in corresponding U.S. Appl. No. 12/415,998. [cited by applicant]
1BM Redbook, SAN vol. Controller: Best Practices and Performance Guidelines ; Jul. 2007. [cited by applicant]
Unix/Linux Administration Logical Volume Management Guide; 2005. [cited by applicant]
IBM Redbook; z/NM and Linux on IBM System z the Virtualization Cookbook for Red hat Enterprise Linux 5.2.; Oct. 2008. [cited by applicant]
Non-Final Office Action mailed Jul. 30, 2014; in corresponding U.S. Appl. No. 12/575,381. [cited by applicant]
Office Action mailed Apr. 14, 2014; in corresponding Canadian patent application No. 2,776,384. [cited by applicant]
Examination Report mailed Oct. 19, 013; in corresponding Singapore patent application No. 01202870-0. [cited by applicant]
English translation for the Notice of Rejection mailed Sep. 10, 2013; in corresponding Japanese patent application No. 2012-536965. [cited by applicant]
Examination Report mailed Sep. 6, 2013; in corresponding Canadian patent application No. 2,778,456. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Dec. 30, 2013; in corresponding U.S. Appl. No. 13/620,999. [cited by applicant]
Examination Report mailed Oct. 29, 2012; in corresponding Singapore Patent Application No. 201202868-4. [cited by applicant]
Examination Report mailed Oct. 30, 012; in corresponding Singapore Patent Application No. 201107040-6. [cited by applicant]
Examination Report mailed Dec. 11, 2012 in corresponding Singapore Patent Application No. 201202502-9. [cited by applicant]
Examination Report Mailed May 17, 2013 in corresponding Singapore Patent Application No. 201202967-4. [cited by applicant]
Examination Report mailed Sep. 13, 2013; in corresponding Singapore Patent Application No. 201202868-4. [cited by applicant]
Extended European Search Report mailed Sep. 19, 2013; in corresponding European Patent Application No. 10827392.1. [cited by applicant]
Final Office Action mailed Oct. 14, 2011; in corresponding U.S. Appl. No. 12/415,958. [cited by applicant]
Final Office Action mailed Oct. 16, 2012; in corresponding U.S. Appl. No. 12/575,381. [cited by applicant]
Final Office Action mailed Oct. 19, 2011; in corresponding U.S. Appl. No. 12/418,475. [cited by applicant]
Final Office Action mailed Nov. 1, 2012; in corresponding U.S. Appl. No. 12/606,106. [cited by applicant]
Final Office Action mailed Dec. 19, 2011; in corresponding U.S. Appl. No. 12/415,968. [cited by applicant]
Final Office Action mailed Feb. 22, 2013; in corresponding U.S. Appl. No. 13/294,099. [cited by applicant]
Final Office Action mailed Mar. 22, 2011; in corresponding U.S. Appl. No. 12/415,998. [cited by applicant]
Final Office Action mailed May 8, 2013; in corresponding U.S. Appl. No. 12/416,017. [cited by applicant]
Non Final Office Action mailed Jan. 2, 2013; in corresponding U.S. Appl. No. 13/620,962. [cited by applicant]
Non Final Office Action mailed Jan. 31, 2014; in corresponding U.S. Appl. No. 12/415,998. [cited by applicant]
Non Final Office Action mailed Oct. 14, 2010; in corresponding U.S. Appl. No. 12/415,998. [cited by applicant]
Non-Final Office Action mailed Dec. 14, 2010; in corresponding U.S. Appl. No. 12/415,987. [cited by applicant]
Non Final Office Action mailed Feb. 14, 2011; in corresponding U.S. Appl. No. 12/606,097. [cited by applicant]
Non Final Office Action mailed Mar. 14, 2012; in corresponding U.S. Appl. No. 12/606,093. [cited by applicant]
Non Final Office Action mailed Mar. 18, 2013; in corresponding U.S. Appl. No. 13/299,601. [cited by applicant]
Non Final Office Action mailed Apr. 18, 2012; in corresponding U.S. Appl. No. 12/575,381. [cited by applicant]
Non Final Office Action mailed Apr. 29, 2011; in corresponding U.S. Appl. No. 12/415,968. [cited by applicant]
Non Final Office Action mailed May 2, 2011; in corresponding U.S. Appl. No. 12/418,475. [cited by applicant]
Non Final Office Action mailed May 2, 2011; in corresponding U.S. Appl. No. 12/415,958. [cited by applicant]
Non Final Office Action mailed May 28, 2013; in corresponding U.S. Appl. No. 12/606,106. [cited by applicant]
Non-Final Office Action mailed May 31, 2012; in corresponding U.S. Appl. No. 12/606,106. [cited by applicant]
Non Final Office Action mailed Jun. 20, 2013; in corresponding U.S. Appl. No. 13/620,999. [cited by applicant]
Non Final Office Action mailed Jun. 20, 2013; in corresponding U.S. Appl. No. 13/621,073. [cited by applicant]
Non Final Office Action mailed Jul. 23, 2013; in corresponding Japanese patent application No. 2012-536964. [cited by applicant]
Non Final Office Action mailed Jul. 23, 2013; in corresponding Japanese patent application No. 2012-536966. [cited by applicant]
Non Final Office Action mailed Aug. 19, 2011; in corresponding U.S. Appl. No. 12/416,017. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Nov. 13, 2013; in corresponding U.S. Appl. No. 12/606,106. [cited by applicant]
Non Final Office Action mailed Sep. 13, 2012; in corresponding U.S. Appl. No. 13/294,099. [cited by applicant]
Non Final Office Action mailed Sep. 14, 2012; in corresponding U.S. Appl. No. 13/299,601. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Oct. 24, 2012; in corresponding U.S. Appl. No. 12/606,093. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Nov. 13, 2012; in corresponding U.S. Appl. No. 12/415,968. [cited by applicant]
Notice of Allowance and Fee(s) Due mailed Dec. 26, 2013; in corresponding U.S. Appl. No. 12/415,958. [cited by applicant]
Office Action from Japanese Patent Application No. 2015/247729, Dated Feb. 21, 2017 (English Translation and Japanese version), pp. 1-9. [cited by applicant]
Extended European Search Report from Application No. 17186495.2, dated Dec. 22, 2017, Amazon Technologies, Inc., pp. 1-7. [cited by applicant]
Office Action from India Application No. 997/KOLNP/2012, Dated Jul. 20, 2018, pp. 1-6. [cited by applicant]