The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Jan. 20, 2015
Filed:
Jun. 06, 2011
Viktoriya Taranov, Bellevue, WA (US);
Alexander Hopmann, Seattle, WA (US);
Antonio Marcos Da Silva, Jr., Kirkland, WA (US);
Nikita Voronkov, Redmond, WA (US);
Kai Yiu Luk, Seattle, WA (US);
Ramanathan Somasundaram, Bothell, WA (US);
Artsiom Kokhan, Redmond, WA (US);
Siddharth Rajendra Shah, Bothell, WA (US);
Daniel Blood, Snohomish, WA (US);
Bhavesh Doshi, Redmond, WA (US);
Viktoriya Taranov, Bellevue, WA (US);
Alexander Hopmann, Seattle, WA (US);
Antonio Marcos Da Silva, Jr., Kirkland, WA (US);
Nikita Voronkov, Redmond, WA (US);
Kai Yiu Luk, Seattle, WA (US);
Ramanathan Somasundaram, Bothell, WA (US);
Artsiom Kokhan, Redmond, WA (US);
Siddharth Rajendra Shah, Bothell, WA (US);
Daniel Blood, Snohomish, WA (US);
Bhavesh Doshi, Redmond, WA (US);
Microsoft Corporation, Redmond, WA (US);
Abstract
A secondary location of a network acts as a recovery network for a primary location of the service. The secondary location is maintained in a warm state that is configured to replace the primary location in a case of a failover. During normal operation, the primary location actively services user load and performs backups that include full backups, incremental backups and transaction logs that are automatically replicated to the secondary location. Information is stored (e.g. time, retry count) that may be used to assist in determining when the backups are restored correctly at the secondary location. The backups are restored and the transaction logs are replayed at the secondary location to reflect changes (content and administrative) that are made to the primary location. After failover to the secondary location, the secondary location becomes the primary location and begins to actively service the user load.