Abstract:
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.
Abstract:
Content that is stored at a secondary location for a service is crawled before it is placed in operation to assist in maintaining an up to date search index. The content that is crawled at the secondary location includes content that is obtained from the primary location of the service. When a crawler at the secondary location attempts to access content that is stored at the primary location, the crawler is directed to access the corresponding copy of the content that is stored at the secondary location instead of accessing the content at the primary location. The content may be crawled at the secondary location at different times, such as when the information is updated, according to a schedule, and the like.
Abstract:
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.
Abstract:
A history of locations of tenant data is maintained. The tenant data comprises data that is currently being used by the tenant and the corresponding backup data. When a tenant's data is changed from one location to another, a location and a time is stored within the history that may be accessed to determine a location of the tenant's data at a specified time. Different operations trigger a storing of a location/time within the history. Generally, an operation that changes a location of the tenant's data triggers the storing of the location within the history (e.g. upgrade of farm, move of tenant, adding a tenant, load balancing of the data, and the like). When tenant data is needed for an operation (e.g. restore), the history may be accessed to determine the location of the data.
Abstract:
método, meio de armazenamento legível por computador e sistema de recuperação de dados de locatário através de movimentos do locatário a presente invenção refere-se à manutenção de um histórico de localizações de dados de locatário. os dados de locatário compreendem dados que estão atualmente sendo utilizados pelo locatário e os dados de cópia de segurança correspondentes. quando um dado do locatário é alterado de uma localização para outra, uma localização e um tempo são armazenados dentro do histórico, que pode ser acessado para determinar uma localização dos dados do locatário em tempo especificado. operações diferentes acionam um armazenamento de uma localização/tempo dentro do histórico. geralmente, uma operação que altera uma localização dos dados do locatário, aciona o armazenamento da localização dentro do histórico (por exemplo, atualização de propriedade rural, movimento de locatário, adição de um locatário, balanceamento de carregamento dos dados e semelhantes). quando os dados de locatário são necessários par uma operação (por exemplo, restaurar), o histórico pode ser acessado para determinar a localização dos dados.
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.
Abstract:
During an outage at a primary location for an online service that is temporary in duration (e.g. a "temporary outage"), requests are temporarily switched from the primary location to a secondary location for the online service. The temporary outage may be caused by many different reasons (e.g. power outage, planned maintenance, and the like). The secondary location may be configured as read only during the temporary outage such that users are still able to access their data during the temporary without causing changes to be made to the data. The requests to the primary location of the online service are automatically redirected to be handled by the secondary location. When the temporary outage ends, the requests are automatically switched back to the primary location.
Abstract:
Una ubicación secundaria de una red actúa como una red de recuperación para una ubicación primaria del servicio. La ubicación secundaria se mantiene en un estado semiactivo que está configurado para reemplazar la ubicación primaria en caso de una conmutación por error. Durante la operación normal, la ubicación primaria proporciona activamente servicios de carga de usuarios y realiza copias de seguridad que incluyen copias de respaldo completas, copias de respaldo incrementales y registros de transacciones que se replican automáticamente a la ubicación secundaria. Se almacena información (p. ej. tiempo, número de intentos) que puede ser utilizada para asistir en la determinación de cuándo las copias de respaldo son restauradas correctamente en la ubicación secundaria. Se restauran las copias de respaldo y se reproducen los registros de transacciones en la ubicación secundaria para reflejar los cambios (de contenido y administrativos) que se realizan a la ubicación primaria. Luego de la conmutación por error a la ubicación secundaria, la ubicación secundaria se convierte en la ubicación primaria y comienza a proporcionar activamente servicios para la carga de usuarios.
Abstract:
A history of locations of tenant data is maintained. The tenant data comprises data that is currently being used by the tenant and the corresponding backup data. When a tenant's data is changed from one location to another, a location and a time is stored within the history that may be accessed to determine a location of the tenant's data at a specified time. Different operations trigger a storing of a location/time within the history. Generally, an operation that changes a location of the tenant's data triggers the storing of the location within the history (e.g. upgrade of farm, move of tenant, adding a tenant, load balancing of the data, and the like). When tenant data is needed for an operation (e.g. restore), the history may be accessed to determine the location of the data.
Abstract:
Se mantiene un historial de ubicaciones de datos de inquilino. Los datos de inquilino comprenden datos que se están utilizando actualmente por el inquilino y los datos de respaldo correspondientes. Cuando se cambian los datos de inquilino de una ubicación a otra, se almacenan una ubicación y un tiempo dentro del historial que puede accederse para determinar una ubicación de los datos de inquilino en un tiempo especificado. Diferentes operaciones activan un almacenamiento de una ubicación/tiempo dentro del historial. Generalmente, una operación que cambia una ubicación de los datos de inquilino activa el almacenamiento de la ubicación dentro del historial (por ejemplo, mejora de granja, movimiento de inquilino, agregar un inquilino, balance de carga de los datos, y similares). Cuando se necesitan datos de inquilino para una operación (por ejemplo, restaurar), el historial puede accederse para determinar la ubicación de los datos.