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:
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:
An electronic discovery (eDiscovery) application is used in managing an electronic discovery process across different electronic data sources using a central interface. The eDiscovery application assists in managing: authentication support for the different data sources; accessing the different data sources; placing holds on content across the different data sources; searching and filtering content across the different data sources; gathering data across the data sources; and the like. The eDiscovery application may be configured as an application on premise, a cloud based service and/or a combination of a cloud based service and an application.
Abstract:
An electronic discovery (eDiscovery) application is used in managing an electronic discovery process across different electronic data sources using a central interface. The eDiscovery application assists in managing: authentication support for the different data sources; accessing the different data sources; placing holds on content across the different data sources; searching and filtering content across the different data sources; gathering data across the data sources; and the like. The eDiscovery application may be configured as an application on premise a cloud based service and/or a combination of a cloud based service and an application.
Abstract:
Una aplicación de descubrimiento electrónico (eDiscovery) se utiliza para la administración de un proceso de descubrimiento electrónico a través de las diversas fuentes de datos electrónicas utilizando una interfase central. La aplicación eDiscovery ayuda a la administración: soporte de autenticación para las diferentes fuentes de datos; acceder las fuentes de datos diferentes; colocar espera sobre el contenido a través de las diferentes fuentes de datos; buscar y filtrar contenido a través de las diferentes fuentes de datos; reunir datos a través de las fuentes de datos; y los similares. La aplicación eDiscovery puede ser configurada como una aplicación sobre una premisa, un servicio basado en nube y/o una combinación de un servicio basado en nube y una aplicación.
Abstract:
Technologies are described herein for exporting content items from multiple disparate content sources to a single repository. Query parameters are received for locating content items hosted by one or more content servers of different types for export. Native search queries are generated for each content server from the query parameters and are executed on each content server. An export manifest listing the content items for export is built from query results received from the content servers. Each content item listed in the export manifest is then retrieved from the corresponding content server and stored in a single export repository.
Abstract:
Technologies are described herein for locating relevant content items across multiple disparate content sources. Query parameters are received from a user interface for defining a query for searching a number of content sources located on multiple, disparate content servers. A native search is executed on each of the content servers based on the received query parameters, and query statistics and other data regarding content items in the content sources matching the query parameters are received. The query statistics are aggregated across the content servers and presented in the user interface. The presentation of the query statistics may be broken out by each content source, by each query phrase segmented from the query, and the like. In addition, a preview of a number of content items matching the query parameters is presented based on the data received.
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.