Patents by Inventor Alexander Hopmann
Alexander Hopmann has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).
-
Patent number: 11720456Abstract: A secondary location is configured as a recovery service 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 secondary location is automatically updated to reflect a current state of the primary location that is actively servicing user load. Content changes to the primary location are automatically reflected to the secondary location. System changes applied to the primary location are automatically applied to the secondary location. For example, removing/adding machines, updating machine/role assignments, removing adding/database are automatically applied to the secondary location such that the secondary location substantially mirrors the primary location. After a failover to the secondary location, the secondary location becomes the primary location and begins to actively service the user load.Type: GrantFiled: November 11, 2021Date of Patent: August 8, 2023Assignee: Microsoft Technology Licensing, LLCInventors: Viktoriya Taranov, Daniel Blood, Alexander Hopmann, Sid R. Shah, Tarkan Sevilmis, Nikita Voronkov, Ramanathan Somasundaram, Artsiom Kokhan, Bhavesh Doshi
-
Publication number: 20220066892Abstract: A secondary location is configured as a recovery service 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 secondary location is automatically updated to reflect a current state of the primary location that is actively servicing user load. Content changes to the primary location are automatically reflected to the secondary location. System changes applied to the primary location are automatically applied to the secondary location. For example, removing/adding machines, updating machine/role assignments, removing adding/database are automatically applied to the secondary location such that the secondary location substantially mirrors the primary location. After a failover to the secondary location, the secondary location becomes the primary location and begins to actively service the user load.Type: ApplicationFiled: November 11, 2021Publication date: March 3, 2022Applicant: Microsoft Technology Licensing, LLCInventors: Viktoriya Taranov, Daniel Blood, Alexander Hopmann, Siddharth Rajendra Shah, Tarkan Sevilmis, Nikita Voronkov, Ramanathan Somasundaram, Artsiom Kokhan, Bhavesh Doshi
-
Patent number: 11176008Abstract: A secondary location is configured as a recovery service 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 secondary location is automatically updated to reflect a current state of the primary location that is actively servicing user load. Content changes to the primary location are automatically reflected to the secondary location. System changes applied to the primary location are automatically applied to the secondary location. For example, removing/adding machines, updating machine/role assignments, removing adding/database are automatically applied to the secondary location such that the secondary location substantially mirrors the primary location. After a failover to the secondary location, the secondary location becomes the primary location and begins to actively service the user load.Type: GrantFiled: April 2, 2019Date of Patent: November 16, 2021Assignee: Microsoft Technology Licensing, LLCInventors: Viktoriya Taranov, Daniel Blood, Alexander Hopmann, Siddharth Rajendra Shah, Tarkan Sevilmis, Nikita Voronkov, Ramanathan Somasundaram, Artsiom Kokhan, Bhavesh Doshi
-
Patent number: 10795733Abstract: A cloud manager controls the deployment and management of machines for an online service. A build system creates deployment-ready virtual hard disks (VHDs) that are installed on machines that are spread across one or more networks in farms that each may include different configurations. The build system is configured to build VHDs of differing configurations that depend on a role of the virtual machine (VM) for which the VHD will be used. The build system uses the VHDs to create virtual machines (VMs) in both test and production environments for the online service. The cloud manager system automatically provisions machines with the created virtual hard disks (VHDs). Identical VHDs can be installed directly on the machines that have already been tested.Type: GrantFiled: January 2, 2019Date of Patent: October 6, 2020Assignee: Microsoft Technology Licensing, LLCInventors: Jason M. Cahill, Alexander Hopmann, Marc Keith Windle, Erick Raymundo Lerma
-
Patent number: 10585766Abstract: A secondary location is configured as a recovery service 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 secondary location is automatically updated to reflect a current state of the primary location that is actively servicing user load. Content changes to the primary location are automatically reflected to the secondary location. System changes applied to the primary location are automatically applied to the secondary location. For example, removing/adding machines, updating machine/role assignments, removing adding/database are automatically applied to the secondary location such that the secondary location substantially mirrors the primary location. After a failover to the secondary location, the secondary location becomes the primary location and begins to actively service the user load.Type: GrantFiled: June 6, 2011Date of Patent: March 10, 2020Assignee: Microsoft Technology Licensing, LLCInventors: Viktoriya Taranov, Daniel Blood, Alexander Hopmann, Siddharth Rajendra Shah, Tarkan Sevilmis, Nikita Voronkov, Ramanathan Somasundaram, Artsiom Kokhan, Bhavesh Doshi
-
Publication number: 20190294515Abstract: A secondary location is configured as a recovery service 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 secondary location is automatically updated to reflect a current state of the primary location that is actively servicing user load. Content changes to the primary location are automatically reflected to the secondary location. System changes applied to the primary location are automatically applied to the secondary location. For example, removing/adding machines, updating machine/role assignments, removing adding/database are automatically applied to the secondary location such that the secondary location substantially mirrors the primary location. After a failover to the secondary location, the secondary location becomes the primary location and begins to actively service the user load.Type: ApplicationFiled: April 2, 2019Publication date: September 26, 2019Applicant: Microsoft Technology Licensing, LLCInventors: Viktoriya Taranov, Daniel Blood, Alexander Hopmann, Siddharth Rajendra Shah, Tarkan Sevilmis, Nikita Voronkov, Ramanathan Somasundaram, Artsiom Kokhan, Bhavesh Doshi
-
Publication number: 20190138366Abstract: A cloud manager controls the deployment and management of machines for an online service. A build system creates deployment-ready virtual hard disks (VHDs) that are installed on machines that are spread across one or more networks in farms that each may include different configurations. The build system is configured to build VHDs of differing configurations that depend on a role of the virtual machine (VM) for which the VHD will be used. The build system uses the VHDs to create virtual machines (VMs) in both test and production environments for the online service. The cloud manager system automatically provisions machines with the created virtual hard disks (VHDs). Identical VHDs can be installed directly on the machines that have already been tested.Type: ApplicationFiled: January 2, 2019Publication date: May 9, 2019Applicant: Microsoft Technology Licensing, LLCInventors: Jason M. CAHILL, Alexander HOPMANN, Marc Keith WINDLE, Erick Raymundo LERMA
-
Patent number: 10180860Abstract: A cloud manager controls the deployment and management of machines for an online service. A build system creates deployment-ready virtual hard disks (VHDs) that are installed on machines that are spread across one or more networks in farms that each may include different configurations. The build system is configured to build VHDs of differing configurations that depend on a role of the virtual machine (VM) for which the VHD will be used. The build system uses the VHDs to create virtual machines (VMs) in both test and production environments for the online service. The cloud manager system automatically provisions machines with the created virtual hard disks (VHDs). Identical VHDs can be installed directly on the machines that have already been tested.Type: GrantFiled: May 22, 2015Date of Patent: January 15, 2019Assignee: MICROSOFT TECHNOLOGY LICENSING, LLC.Inventors: Jason M. Cahill, Alexander Hopmann, Marc Keith Windle, Erick Raymundo Lerma
-
Patent number: 9442813Abstract: Jobs submitted to a primary location of a service within a period of time before and/or after a fail-over event are determined and are resubmitted to a secondary location of the service. For example, jobs that are submitted fifteen minutes before the fail-over event and jobs that are submitted to the primary network before the fail-over to the second location is completed are resubmitted at the secondary location. After the fail-over event occurs, the jobs are updated with the secondary network that is taking the place of the primary location of the service. A mapping of job input parameters (e.g. identifiers and/or secrets) from the primary location to the secondary location are used by the jobs when they are resubmitted to the secondary location. Each job determines what changes are to be made to the job request based on the job being resubmitted.Type: GrantFiled: August 7, 2015Date of Patent: September 13, 2016Assignee: Microsoft Technology Licensing, LLCInventors: Daniel Blood, Alexander Hopmann, Siddharth Rajendra Shah, Viktoriya Taranov, Tarkan Sevilmis, Nikita Voronkov
-
Patent number: 9311199Abstract: Jobs submitted to a primary location of a service within a period of time before and/or after a fail-over event are determined and are resubmitted to a secondary location of the service. For example, jobs that are submitted fifteen minutes before the fail-over event and jobs that are submitted to the primary network before the fail-over to the second location is completed are resubmitted at the secondary location. After the fail-over event occurs, the jobs are updated with the secondary network that is taking the place of the primary location of the service. A mapping of job input parameters (e.g. identifiers and/or secrets) from the primary location to the secondary location are used by the jobs when they are resubmitted to the secondary location. Each job determines what changes are to be made to the job request based on the job being resubmitted.Type: GrantFiled: September 17, 2014Date of Patent: April 12, 2016Assignee: Microsoft Technology Licensing, LLCInventors: Daniel Blood, Alexander Hopmann, Siddharth Rajendra Shah, Viktoriya Taranov, Tarkan Sevilmis, Nikita Voronkov
-
Publication number: 20160019098Abstract: A cloud manager controls the deployment and management of machines for an online service. A build system creates deployment-ready virtual hard disks (VHDs) that are installed on machines that are spread across one or more networks in farms that each may include different configurations. The build system is configured to build VHDs of differing configurations that depend on a role of the virtual machine (VM) for which the VHD will be used. The build system uses the VHDs to create virtual machines (VMs) in both test and production environments for the online service. The cloud manager system automatically provisions machines with the created virtual hard disks (VHDs). Identical VHDs can be installed directly on the machines that have already been tested.Type: ApplicationFiled: May 22, 2015Publication date: January 21, 2016Applicant: MICROSOFT TECHNOLOGY LICENSING, LLCInventors: Jason M. Cahill, Alexander Hopmann, Marc Keith Windle, Erick Raymundo Lerma
-
Publication number: 20150347244Abstract: Jobs submitted to a primary location of a service within a period of time before and/or after a fail-over event are determined and are resubmitted to a secondary location of the service. For example, jobs that are submitted fifteen minutes before the fail-over event and jobs that are submitted to the primary network before the fail-over to the second location is completed are resubmitted at the secondary location. After the fail-over event occurs, the jobs are updated with the secondary network that is taking the place of the primary location of the service. A mapping of job input parameters (e.g. identifiers and/or secrets) from the primary location to the secondary location are used by the jobs when they are resubmitted to the secondary location. Each job determines what changes are to be made to the job request based on the job being resubmitted.Type: ApplicationFiled: August 7, 2015Publication date: December 3, 2015Applicant: Microsoft Technology Licensing, LLCInventors: Daniel Blood, Alexander Hopmann, Siddharth Rajendra Shah, Viktoriya Taranov, Tarkan Sevilmis, Nikita Voronkov
-
Publication number: 20150317187Abstract: Objects are placed on hosts using hard constraints and soft constraints. The objects to be placed on the host may be many different types of objects. For example, the objects to place may include tenants in a database, virtual machines on a physical machine, databases on a virtual machine, tenants in directory forests, tenants in farms, and the like. When determining a host for an object, a pool of hosts is filtered through a series of hard constraints. The remaining pool of hosts is further filtered through soft constraints to help in selection of a host. A host is then chosen from the remaining hosts.Type: ApplicationFiled: June 29, 2015Publication date: November 5, 2015Applicant: Microsoft Technology Licensing, LLCInventors: Alexander Hopmann, Marc Keith Windle, Patrick Simek, Erick Raymundo Lerma, Dan Rosenthal
-
Patent number: 9075661Abstract: Objects are placed on hosts using hard constraints and soft constraints. The objects to be placed on the host may be many different types of objects. For example, the objects to place may include tenants in a database, virtual machines on a physical machine, databases on a virtual machine, tenants in directory forests, tenants in farms, and the like. When determining a host for an object, a pool of hosts is filtered through a series of hard constraints. The remaining pool of hosts is further filtered through soft constraints to help in selection of a host. A host is then chosen from the remaining hosts.Type: GrantFiled: October 20, 2010Date of Patent: July 7, 2015Assignee: Microsoft Technology Licensing, LLCInventors: Alexander Hopmann, Marc Keith Windle, Patrick Simek, Erick Raymundo Lerma, Dan Rosenthal
-
Patent number: 9069620Abstract: A cloud manager controls the deployment and management of machines for an online service. A build system creates deployment-ready virtual hard disks (VHDs) that are installed on machines that are spread across one or more networks in farms that each may include different configurations. The build system is configured to build VHDs of differing configurations that depend on a role of the virtual machine (VM) for which the VHD will be used. The build system uses the VHDs to create virtual machines (VMs) in both test and production environments for the online service. The cloud manager system automatically provisions machines with the created virtual hard disks (VHDs). Identical VHDs can be installed directly on the machines that have already been tested.Type: GrantFiled: October 20, 2010Date of Patent: June 30, 2015Assignee: Microsoft Technology Licensing, LLCInventors: Jason M. Cahill, Alexander Hopmann, Marc Keith Windle, Erick Raymundo Lerma
-
Patent number: 9043370Abstract: An online service includes databases that are upgraded while still processing requests. For example, web servers continue to request operations on the database while it is being upgraded. The schema of the database is upgraded before the web servers are upgraded to utilize the upgraded schema. Changes that are made to the upgraded schema are backwards compatible with the schema being used during the upgrade process. Restrictions are placed on the operations performed on the database during the upgrade process. After upgrading the schema, the web servers of the online service are upgraded to use the upgraded schema.Type: GrantFiled: April 8, 2013Date of Patent: May 26, 2015Assignee: Microsoft Technology Licensing, LLCInventors: Alexander Hopmann, Balinder Malhi, Zach Rosenfield, Marc Windle, Erick Raymundo Lerma
-
Patent number: 9015177Abstract: An online service includes managed databases that include one or more tenants (e.g. customers, users). A multi-tenant database may be split between two or more databases while the database being split continues processing requests. For example, web servers continue to request operations on the database while content is being moved. After moving the content, tenant traffic is automatically redirected to the database that contains the tenant's content.Type: GrantFiled: February 15, 2013Date of Patent: April 21, 2015Assignee: Microsoft Technology Licensing, LLCInventors: Jason M. Cahill, Alexander Hopmann, Eric Fox, Balinder Malhi, Zach Rosenfield, Marc Keith Windle, Patrick Simek
-
Publication number: 20150039931Abstract: Jobs submitted to a primary location of a service within a period of time before and/or after a fail-over event are determined and are resubmitted to a secondary location of the service. For example, jobs that are submitted fifteen minutes before the fail-over event and jobs that are submitted to the primary network before the fail-over to the second location is completed are resubmitted at the secondary location. After the fail-over event occurs, the jobs are updated with the secondary network that is taking the place of the primary location of the service. A mapping of job input parameters (e.g. identifiers and/or secrets) from the primary location to the secondary location are used by the jobs when they are resubmitted to the secondary location. Each job determines what changes are to be made to the job request based on the job being resubmitted.Type: ApplicationFiled: September 17, 2014Publication date: February 5, 2015Applicant: Microsoft CorporationInventors: Daniel Blood, Alexander Hopmann, Siddharth Rajendra Shah, Viktoriya Taranov, Tarkan Sevilmis, Nikita Voronkov
-
Patent number: 8938638Abstract: 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.Type: GrantFiled: June 6, 2011Date of Patent: January 20, 2015Assignee: Microsoft CorporationInventors: Viktoriya Taranov, Alexander Hopmann, Antonio Marcos Da Silva, Jr., Nikita Voronkov, Kai Yiu Luk, Ramanathan Somasundaram, Artsiom Kokhan, Siddharth Rajendra Shah, Daniel Blood, Bhavesh Doshi
-
Publication number: 20140337502Abstract: A cloud manager assists in deploying and managing networks for an online service. The cloud manager system receives requests to perform operations relating to configuring, updating and performing tasks in networks that are used in providing the online service. The management of the assets may comprise deploying machines, updating machines, removing machines, performing configuration changes on servers, Virtual Machines (VMs), as well as performing other tasks relating to the management. The cloud manager is configured to receive requests through an idempotent and asynchronous application programming interface (API) that can not rely on a reliable network.Type: ApplicationFiled: July 29, 2014Publication date: November 13, 2014Applicant: Microsoft CorporationInventors: Jason M. Cahill, Zach Rosenfield, Marc Keith Windle, Alexander Hopmann, Balinder Malhi, Erick Raymundo Lerma, Ricardo Prates de Oliveira, David Paul Harris Gorbet, Doron Bar-Caspi, Joshua Calvin Jenkins, Jonathan Luk, Michelle Lee Dauphiny, Vipins Gopinadhan