50 results about "Failover" patented technology

Methods, systems, and products for sustainable Reliability, Availability, and Serviceability (RAS) balancing based on predictive models includes predicting, based on one or more predictive models, a potential failure within a computing system, and provisioning, based on the potential failure, one or more redundant resources for failover.

Systems and methods for providing failover readiness prediction, comprise: during a training stage: selecting a first set of data from a database of historical failover data based at least in part on feature importance within the historical failover data; label encoding the first set of data; tokenizing the first set of data; converting the first set of data into a set of dense vector representations; and training a classification model using the set of dense vector representations; during a predication stage: receiving a request to predict a failover outcome for a given failover process; assessing a status of concurrent system conditions; and predicting at least one of a success probability of the failover process, or an expected time for at least one of a plurality of steps in the failover process, based at least in part on the classification model and the status of the concurrent system conditions.

An information handling system stores telemetry data for the information handling system. A processor collects the telemetry data and determines a target application associated with the telemetry data. The processor sets a quality of service for the target application based on a context of the target application. The processor determines whether a first network path or a failover network path associated with the target application is a preferred network path. In response to the first network path being the preferred network path, the processor provides the telemetry data from the target application over the first network path. In response to the failover network path being the preferred network path, the processors failover the target application to the failover network path. The telemetry data is provided based on the quality of service.

A system and method for achieving peripheral component interconnect express (PCIe) redundancy and recovery are disclosed. In some embodiments, the system comprises an accelerated compute fabric (ACF) comprising a PCIe switch, an application host communicatively coupled to the ACF using one or more upstream PCIe links, and an endpoint device communicatively coupled to the ACF using one or more downstream PCIe links. The application host is configured to send PCIe transaction layer packets (TLP) addressed to the ghosted endpoint devices through the one or more upstream PCIe links, and the ACF is configured to redirect the PCIe TLP packets to the endpoint device through the one or more downstream PCIe links.

Methods, systems, and devices for data management are described. Techniques described herein may enable a database management system (DMS) to link databases of a failover group that spans multiple data centers across different clusters for the different datacenters. For example, a centralized control entity may indicate to the clusters in different datacenters that one or more databases in a first datacenter are in a same failover group as one or more other databases in a second datacenter. A database of the first datacenter may be a primary backup database from which a first cluster in the first datacenter may obtain transaction log backups. The first cluster of the datacenter may replicate the backups to a second cluster of a second datacenter, which may enable the second cluster to refrain from obtaining backups from a secondary backup database within the second datacenter.

Configuring a virtualized environment in a telecommunications network is described. A plurality of primary virtual workloads are configured, including a first primary virtual workload, to use first processing resources on at least one host device in the network. A plurality of secondary virtual workloads are configured, including a first secondary virtual workload and a second secondary virtual workload, to use second processing resources on at least one host device in the network, each of the plurality of secondary virtual workloads being associated with a respective one of the primary virtual workloads. The secondary virtual workloads contend with one another. Causing, as part of a failover procedure, a processing resource access priority such that additional processing resources on at least one host device in the network are available to the first secondary virtual workload and not available to the second secondary virtual workload.

Disclosed are various embodiments for a hierarchically decisioned failover system. First, a health probe can calculate a respective instance health score for each of a plurality of application instances within an application service. Then, the health probe can calculate a service health score for the application service. Next, the health probe can calculate a zone health score for an application ecosystem. Subsequently, the health probe can initiate a failover of the application ecosystem from a first availability zone to a second availability zone based at least in part on the zone health score.

A system described herein may provide an interface between a Centralized Unit (“CU”) and a Network Repository Function (“NRF”) of a wireless network. A first CU may receive, from the NRF, an indication that a second CU is associated with a particular priority, and the first CU may subscribe to updated information, maintained by the NRF, that is associated with the second CU. The first CU may receive, based on the subscribing, updated priority information associated with the second CU, which indicates that the second CU is no longer associated with the particular priority. The first CU may maintain, based on the updated priority information indicating that the second CU is not associated with the particular priority, an indication that the first CU is associated with the particular priority. The first CU may accordingly perform functionality that was previously performed by the second CU.

Provided in the embodiments of the present disclosure are a multi-replica data storage method, a multi-replica data reading method, a multi-replica data sealing method, and a device, a storage medium, and a program product. In the embodiments of the present disclosure, a fast failover mechanism provides more storage nodes than the number of replicas for storage failover, data is first written to replica nodes, and when a node fails and the failure is within a failover range, the data is written to candidate nodes, which is conducive to increasing the success probability of multi-replica storage; and within the failover range, it is not necessary to trigger a slow failover mechanism that triggers sealing of a data unit, thereby reducing the probability of triggering a failover mechanism and mitigating the access impact on a management node (e.g., an MS), and thus improving the data write efficiency and reducing the write latency.

Herein disclosed includes a system configured to implement a failover in scheduling services, the system comprising: server apparatuses each comprising a processing unit and a memory unit, wherein the system is configured to obtain a task to be executed and to associate the task with a label from which requirements of the task is identifiable, wherein the processing unit and the memory unit of each server apparatus are co-operable to configure the server apparatus as a service node capable of obtaining the task, and wherein the server apparatuses are configured to enter a competition mode in which the server apparatuses compete for the label, and one of the server apparatuses, which matches the requirements, obtains and holds the label, and converts from the service node to a target service node to execute the task, and if an exception happens to occur in the target service node, the server apparatus operating as the target service node is configured to release the label to idling server apparatuses to compete for the label, avoiding any unnecessary repetition and / or delay from the server apparatuses in executing the task. Herein disclosed also includes a method for implementing such failover in a system configured to schedule services.

A device includes a plurality of digital signal processors (DSPs) and analog crossbars in communication with the DSPs. The DSPs and crossbars dynamically adjust power consumption based on traffic load and / or a signal quality, leveraging traffic prediction models to optimize resource allocation. The system supports features such as powering down unused lanes, asymmetrically deactivating transmission or receiving lanes, and preemptively scaling resources during predicted traffic increases. Dynamic voltage and frequency scaling (DVFS) optimizes power usage based on link utilization and traffic priority, minimizing latency impacts during transitions. The switch controller integrates traffic prioritization algorithms, including weighted round-robin (WRR), to allocate power and bandwidth efficiently to high-priority traffic flows. Redundant crossbars handle overflow traffic or failover scenarios, transitioning between standby and active states dynamically.

Forechannel connections are established from client-side deduplication libraries to a namespace node of a set of namespace nodes formed as a cluster. The namespace nodes are responsible for namespace operations on files managed by a deduplication filesystem. The forechannel connections are responsible for carrying file data between the client-side deduplication libraries and the namespace node. Server-initiated connections are established from the namespace node to the client-side deduplication libraries. The server-initiated connections are responsible for carrying instructions from the namespace node to the client-side deduplication libraries. While a transfer of file data is in progress, the client-side deduplication libraries are instructed over the server-initiated connections to failover the transfer to one or more other namespace nodes. After the failover, the namespace node is upgraded.

Network address migration using a destination compute instance to update network configuration information in a cloud environment is disclosed. A network interface either using a private address within a subnet corresponding to the created network interface or using a floating address outside of the subnet corresponding to the created network interface is created. A first node of the HA pair with a service provider interface. The first node is an active data server of the HA pair, and the second node is a backup node of the HA pair. Requests are serviced the first node using the created network interface. Upon failure of the first node, the second node performs a failover, wherein if the first node was utilizing a floating address, the second node registers the second node with the service provider interface by adding an address of the second node to the route table.

A computing network provides a database service and implements a caching mechanism for processing database queries. The database services are provided using a primary replica of data and computing resources, and a secondary replica of the data and computing resources. The primary and secondary replicas are synchronized so that the secondary replica can provide the database services in place of the primary replica in response to a failover from the primary replica to the secondary replica. In response to initiating, by the database service, a failover from the primary replica to the secondary replica, the cached plans compiled by the secondary replica are used to process matching query batches by the secondary replica. The secondary replica processes the matching query batches without accessing plans compiled by the primary replica.

This invention discloses a multi-cluster data processing method and system based on a large-scale language model. The method collects multi-dimensional telemetry data from managed clusters; inputs the multi-dimensional telemetry data, business objectives, and dynamically generated prompts into a large-scale language model to obtain structured decisions; translates the structured decisions into configuration instructions for the target platform and executes the configuration instructions. This invention achieves global intelligent optimization and accurately proposes failover decisions, thereby improving data processing efficiency.

This invention provides a method for automatic failover of a central collector in a distributed IoT system and the IoT system itself. The method includes: a host computer sending an online status query message for devices via CoAP protocol multicast, statistically analyzing the device response results, identifying central collectors that fail to respond multiple times consecutively as faulty central collectors, and sending a fault notification message via protocol multicast, the message containing the IP address of the faulty central collector; each IoT terminal determining whether the message data contains the IP address of its currently reported central collector, and if so, sending a path switching request message to the host computer; upon receiving the path switching request message, the host computer selecting the central collector with the best computing resources to take over, sending a switchover response message to the IoT terminal, the message carrying the IP address of the central collector taking over; upon receiving the switchover response message, the IoT terminal sending a registration message to the central collector taking over to complete terminal registration, and sending a deregistration message to the faulty central collector to complete terminal deregistration, thereby realizing fault handling in the power distribution system.

The application provides an automatic detection method for database cluster automatic deployment, a storage medium and equipment, the automatic detection method comprises: an arbitrator, a master library and a plurality of backup libraries, the arbitrator is used for observing the running state of the master library and the backup library. The automatic failover method comprises: acquiring a failure signal of the master library; sending a failover command to a target backup library in the plurality of backup libraries; attempting to acquire feedback information sent by the target backup library, the feedback information comprising an execution result of the target backup library on the failover command; if the attempt result is failure, attempting to connect other backup libraries in the plurality of backup libraries except the target backup library; in the case that the attempt to connect the other backup libraries fails, stopping the running of the arbitrator. The automatic failover method of the database cluster of the application avoids the unavailability of automatic failover caused by the impulsive 'death' of the arbitrator, and greatly improves the availability of the cluster and the automatic failover system.

A device includes a plurality of digital signal processors (DSPs), analog crossbars in communication with the DSPs, and a switch controller. The switch controller facilitates control signals using in-band signaling within payload traffic or out-of-band signaling over a dedicated management interface. The system supports dynamic traffic prioritization based on real-time metrics, such as latency and traffic load, ensuring efficient resource allocation and seamless operation during congestion or reconfiguration. Redundant crossbars and failover mechanisms enhance fault tolerance, while granular backpressure selectively throttles traffic flows to prevent bottlenecks. Integrated diagnostic tools monitor performance and optimize traffic flow, enabling high-speed and reliable communication.

This invention discloses a high-speed retrieval method and system (lightweight native memory architecture) supporting single-machine and cluster deployment, relating to the fields of data retrieval, distributed clusters, and in-memory computing. This invention designs 20 core sub-logic items that can be implemented independently, combined arbitrarily, and integrated with other architectures. Based on a native memory direct control architecture, it has no dependencies on third-party databases, index engines, or middleware, adapts to low / medium / high-configuration servers, and supports seamless expansion in single-machine, multi-instance parallel, and distributed cluster modes. Retrieval response speed and concurrency capacity increase linearly with hardware configuration and the number of cluster nodes. This invention achieves targeted retrieval of structured data and eliminates redundant computation through core sub-logic such as full-scale one-time loading in memory, bidirectional reading with one-time sorting, and dual sliding window hotspot caching. On a low-configuration server with 2 cores and 2GB of RAM (single data ≤1KB), the core time for multi-condition retrieval of tens of millions of general-purpose structured data is ≤10ms, supporting 1000+ concurrent retrieval requests, and achieving 99.99% system stability under a fully closed-loop deployment. By employing sub-logic such as incremental synchronous seamless hot updates, low-load asynchronous backups, and layered fallback high availability, this invention achieves uninterrupted data maintenance and 1ms failover for node failures. A fallback node idle-time load-sharing mechanism improves hardware utilization. Three-layer security protection is decoupled from the retrieval process, achieving an illegal attack interception rate of ≥99.9% with protection-introduced latency ≤1ms. Any sub-logic of this invention can be individually embedded into a traditional retrieval architecture for lightweight upgrades, or combined or implemented in a closed loop for synergistic effects. It is widely adaptable to structured and hierarchical data retrieval scenarios across industries such as e-commerce, logistics, government affairs, and finance, significantly reducing deployment, upgrade, and maintenance costs. This invention addresses the industry pain points of existing retrieval systems, such as poor low-configuration compatibility, wasted high-configuration computing power, and difficulty in balancing security and efficiency, demonstrating high commercial and promotional value.

Instantiating a first microservice-based platform instance in a first geographic region, wherein a first microservice of the first microservice-based platform instance performs index searching, a second microservice of the first microservice-based platform instance performs audit tracking, a third microservice of the first microservice-based platform instance performs object history tracking, and a fourth microservice of the first microservice-based platform instance performs entity matching. Instantiating a second microservice-based platform instance in a second geographic region, wherein the second microservice-based platform instance is a duplicate of the first microservice-based platform instance. Continuously synchronizing the first microservice-based platform instance and the second microservice-based platform instance. Receiving a query. Detecting a failure of the first microservice-based platform instance. Redirecting the query to the second microservice-based platform instance.

A stateless artificial intelligence game master system and method enables scalable, provider-agnostic interactive game experiences. The system comprises a stateless game server processing requests without persistent session state, a provider-agnostic AI orchestration engine supporting automatic failover between multiple language model providers, a context reconstruction module dynamically rebuilding game context from transaction logs, and a real-time integration module enforcing game mechanics without state persistence. The architecture achieves memory efficiency of approximately 16 kilobytes per session compared to 10+ megabytes for stateful implementations, enabling horizontal scaling without session affinity requirements. The system supports graceful degradation through template-based fallback when AI providers are unavailable. Security features include AES-256-GCM encryption of API credentials with session-specific initialization vectors. The invention addresses limitations of existing stateful AI game systems including memory accumulation, single-provider dependency, and session affinity requirements.

Instantiating a first microservice-based platform instance in a first geographic region, wherein a first microservice of the first microservice-based platform instance performs index searching, a second microservice of the first microservice-based platform instance performs audit tracking, a third microservice of the first microservice-based platform instance performs object history tracking, and a fourth microservice of the first microservice-based platform instance performs entity matching. Instantiating a second microservice-based platform instance in a second geographic region, wherein the second microservice-based platform instance is a duplicate of the first microservice-based platform instance. Continuously synchronizing the first microservice-based platform instance and the second microservice-based platform instance. Receiving a query. Detecting a failure of the first microservice-based platform instance. Redirecting the query to the second microservice-based platform instance.

This invention discloses a method, apparatus, device, and medium for failover of edge nodes in a power Internet of Things (IoT) system. The method includes generating and broadcasting a heartbeat message for each edge node in the target power IoT system, and receiving heartbeat messages from neighboring nodes. Each node dynamically generates a state topology diagram based on its own and its neighbors' real-time heartbeat messages, and performs state trend prediction and risk assessment based on pre-acquired historical state sequences to determine whether each edge node needs failover. When a faulty node needs failover, a target migration node is determined based on the faulty node's state topology diagram, and the faulty node's service data is synchronously migrated to the target migration node, enabling the target migration node to continue executing the power IoT tasks of the faulty node. This invention enables smooth and uninterrupted service migration, improving the continuity and stability of power IoT service task execution.

An NFS export is created on a node of a data protection appliance. The export includes a backup to be accessed by an access object service hosted by the node. The node is in a cluster of nodes including other AOB services and NFSv3 servers accessible via external IP addresses. Each AOB service has access to other portions of the filesystem assigned to other AOB services. The export is mounted at an NFSv3 client which conducts data protection IO on the export using an external IP address to the node. A mapping of the export is maintained. Upon a node failure, resource utilization of other nodes is probed to select a failover node. The mapping is consulted to identify the IP address associated with the failed node. The IP address is migrated to the failover node.

A disaster recovery system includes a first IHS (Information Handling System) at an edge location. A monitoring client operating on the first IHS collects snapshots of an application operating on the first IHS and transmits the snapshots to a recovery client operating at a remote location. The first IHS also transmits periodic signals to the recovery client. The disaster recovery system also includes a second IHS at a datacenter location. A recovery client operating on the second IHS receives and stores the snapshots of the application operating on the first IHS and initiates failover operations of the first application using the stored snapshots upon failure to receive the periodic signals from the monitoring client.

The present invention relates to a system for secure deployment of microservice instance over load-balanced kubernetes, and a method thereof. The system and method facilitates the secure deployment and orchestration of microservice instances and web services on load-balanced Kubernetes containers across diverse Cloud Service Providers' (CSPs) Infrastructure as a Service (IAAS) environments. The present invention addresses the need for secure web service operation and ensures failover support to maintain zero downtime for complex applications. The system facilitates the creation and secure export of custom micro instances as encrypted files, enabling their protected migration. Redundancy of web services is provided across distributed Kubernetes environments to ensure continuous service for end-users even during micro instance failures

A system and method for efficient fast failover of a primary link to a secondary link comprising monitoring an amount of user packets on said primary link and sending synthetic packets on said secondary link at a predetermined rate based on said amount of user packets wherein said predetermined rate is changed as a function of change in said amount of user packets.

This application discloses a core network disaster recovery and failover assessment method, apparatus, and electronic equipment, relating to the field of communication technology. The method includes: performing multi-dimensional simulations based on disaster recovery and failover assessment requirements to obtain simulation results; based on the simulation results, assessing the signaling impact, network element resilience, and service recovery degree of disaster recovery and failover on related network elements of the target network, determining the assessment results characterizing the impact of disaster recovery and failover on the target network; the assessment results characterize the service implementation capability, network element resilience, and network element capacity carrying capacity of the target network, providing a basis for network optimization decisions. This application addresses the technical problem that existing solutions lack specific assessment capabilities for disaster recovery and failover scenarios, and cannot assess the impact on core network-related network elements during disaster recovery and failover. It promotes network security prevention and control in disaster recovery and failover scenarios from passive response to proactive prediction and prevention, significantly improving the stability and service continuity of the core network.

A computer implemented method includes maintaining information indicative of whether a data replication relationship between a dataset associated with the local CG (CG1) and a mirror copy of the dataset stored on a remote CG (CG2) of a remote distributed storage system is in an in-synchronization (InSync) state or an out-of-synchronization (OOS) state, determining whether a CG storage expansion process is in progress, and in response to determining the OOS state and whether the primary storage site has a failure, initiating an automatic unplanned failover (AUFO) workflow without manual intervention on the original volumes in the CG1 of a first storage cluster of the primary storage site and the original volumes in the CG2 of a second storage cluster when the CG storage expansion process is in progress with a new source volume to be a member of CG1 and a new destination volume to be a member of CG2.

This application discloses a server dead time management method, apparatus, device, and storage medium, relating to the field of server resource management technology. The server dead time management method includes: if it is determined that the target server has failed, determining whether the global status identifier of the target server is "running"; if it is determined that the global status identifier is "running", setting the global status identifier to "down", and initializing the global reference count of the target server through an active port usage table, wherein the initial value is the number of ports using the target server when the failure occurred; when the port successfully completes the failover from the target server, decrementing the global reference count by one to obtain an updated global reference count; when the updated global reference count decreases to zero, setting the global status identifier to "running", and the target server resumes use. This application can shorten the server failure recovery time.