Microsoft Technology Licensing, LLC

Other

Alexander Hopmann

Brian J Deen

Jason Matthew Cahill

Marc Keith Windle

Erick Raymundo Lerma

Nikita Voronkov

Viktoriya Taranov

Tarkan Sevilmis

Daniel Blood

Zach Rosenfield

Siddharth Rajendra Shah

Rebecca L Anderson

Balinder Malhi

Bhavesh Anil Doshi

Ramanathan Somasundaram

Artsiom Kokhan

Eric B Fox

Patrick Simek

Namita Gupta

Samuel Watkins Bent

David Jakob Jenni

Van Christopher Van

Jonathan M Luk

Doron Bar-Caspi

David Paul Harris Gorbet

Ricardo Prates De Oliveira

Marc Windle

Christopher Andrew Evans

Joel Mathew Soderberg

Arshish C Kapadia

Lauren Nicole Antonoff

Gregory Scott Friedman

Jeffrey David Henshaw

Javier Dalzell

Kshamta Jerath

Tittu Jose

Lisa M Lippert

Huy Q Nguyen

Michelle Lee Dauphiny

Daniel Evan Socolof

Vipins Gopinadhan

Kai Yiu Luk

Joshua Calvin Jenkins

Marcin Olszewski

Fabricio Chalub Barbosa Do Rosario

Vipins Gopinadham

Becky Anderson

Sid R Shah

Dan Rosenthal

Antonio Marcos Da Silva, Jr

Antonio Marcos Da Silva

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.

Automatic configuration of a recovery service

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.

Server farm management

Multiple camera angles of an interactive event are simultaneously transmitted as part of a broadcast. The simultaneous distribution of multiple synchronized streams of audio and/or visual information enables switching between cameras to be made by the audience members without interruption of the presentation of the event. In one embodiment, a performance studio might send out multiple synchronized concurrent streams. For example, a performance studio might transmit four distinct camera angles or streams, each at varying quality levels, such as the illustrated high-bandwidth and low-bandwidth encodings. Selection of the stream may also direct interactive feedback portions generated by the selecting audience member towards the selected object/individual. Alternatively, interactive feedback generated by the audience member may be directed globally to the producers of the event and selectively to the performers and other audience members of the event.

Switching camera angles during interactive events

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.

Replaying jobs at a secondary location of a service

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.

Placing objects on hosts using hard and soft constraints

Creating and deploying service-ready virtual hard disks

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.

Online database availability during upgrade

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.

Dynamically splitting multi-tenant databases

Systems and methods for synchronizing multiple copies of data in a network environment that includes servers and clients so that incremental changes made to one copy of the data can be identified, transferred, and incorporated into all other copies of the data. The synchronization can be accomplished regardless of whether modifications to the data have been made by a client while the client is in an on-line or off-line mode of operation. The clients cache data locally as data are modified and downloaded. The caching enables the clients to access the data and allows the synchronization to be performed without transmitting a particular version more than once between a client and a server. Such elimination of redundant data transmission results in an efficient use of time and network bandwidth.

Method and system for supporting off-line mode of operation and synchronization

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.

Recovery service location for a service

Growing community of inventors

Seattle, WA, United States of America

Alexander Hopmann