Abstract: Various embodiments relate to a distributed power system, including: a primary power management integrated circuit (PMIC) configured to receive a source voltage and connected to a primary communication bus, wherein the primary PMIC produces a secondary voltage on a voltage line, wherein the primary PMIC communicates with a microcontroller unit (MCU) via the primary communication bus; and a plurality of secondary PMICs connected to the primary PMIC via the voltage line, a secondary communication bus, and a fail line, wherein the plurality of secondary PMICs are configured to produce a pulsed signal on the fail line when a secondary PMIC fails, wherein the pulsed signal produced by each of the plurality of secondary PMICs have a unique pulse width that indicates to the primary PMIC the identity of the failed secondary PMIC.

Abstract: An example graphics system can include a first portion including a graphics driver and graphics hardware and a second portion communicatively coupled to the first portion. The second portion can include a display system communicatively coupled to a GUI application and a shim layer to shield the second portion from failure responsive to failure of the first portion.

Abstract: Methods, systems, and computer program products for cloud to cloud disaster recovery are disclosed. Exemplary embodiments may: discover one or more virtual machines associated with a first auto scaling group; and generate a plan to backup the one or more virtual machines to a second cloud.

Abstract: Systems and methods for unified application-level backup and restore using heterogeneous cloud-based backup service providers. An application programming interface is configured to process both data level replication operations as well as application-level operations that are executed to carry out high-level commands between a virtualized computing environment and any one or more of the heterogeneous cloud-based backup service providers. The API receives commands from applications in the virtualized computing environment. The API processes commands from the applications so as to facilitate replication of data to selected one or more cloud-based backup service providers. The commands perform data level replication operations as well as application-level operations for storing content to the cloud-based service provider. After a failure event and/or upon receipt of a restore command, the API initiates application-level operations that restore the application and its constituent entities.

Abstract: A memory device includes a non-volatile memory to store data, an execution trace buffer, and a media controller. The media controller receives data-modifying commands and adds the data-modifying commands to the execution trace buffer. The media controller executes the data-modifying commands to modify the data stored in the non-volatile memory and detects errors in the data stored in the non-volatile memory. The media controller repeats execution of data-modifying commands from the execution trace buffer in response to detecting an error.

Abstract: The disclosure herein describes placing delta components of a base component in target fault domains. One or more delta components are generated. When a first fault domain that lacks a sibling component of the base component is identified, the first fault domain is selected as a single delta target fault domain and a single delta component is placed on the single delta target fault domain. When a second fault domain that includes a first sibling component of the base component is identified and a third fault domain that includes a second sibling component of the base component is identified, the second fault domain and the third fault domain are selected as a first double delta target fault domain and a second double delta target fault domain, and a first double delta component and a second double delta component are placed on the first and second double delta target fault domains.

Abstract: Transaction recovery in a cloud computing environment. Transaction recovery includes determining whether a first container of a plurality of containers in the cloud computing environment is crashed. In response to the first container being crashed, the method may include determining at least one transaction log entry from a first log file corresponding to the first container. Transaction recovery includes retrieving at least one in-doubt transaction corresponding to the first container from a first database corresponding to the first container. Transaction recovery includes comparing the at least one transaction log entry with the at least one in-doubt transaction for transaction recovery.

Abstract: Assets are associated to a data protection policy. Configuration information is received for the data protection policy. The configuration information includes a data protection job to perform for the assets and a schedule for the data protection job. A shadow policy is generated that includes the configuration information. The data protection policy is executed. Upon detecting a failure of the data protection job for an asset, the asset is moved from the data protection policy to the shadow policy. The shadow policy is executed. Execution of the shadow policy includes calculating a base time value, adding a random time value to the base time value to obtain a wait time, and after the wait time has elapsed, retrying the data protection job.

Abstract: In the invention, a problem is solved in which, in order to achieve high performance and high reliability with the conventional multi-core and lockstep core, a redundant lockstep core is necessarily prepared to execute a multi-core program in which an error has occurred, a circuit area increases, and a cost and a power consumption increase. In the invention, a safe operation of a control system is secured by operating a software program operating on a multi-core in which an error has occurred as degenerate software on a core switched from a lockstep operation to a multi-core operation.

Abstract: Database recovery is based on workload priorities. A database workload is divided into a plurality of workload groups. A workload group of the plurality of workload groups is selected for recovery, in which the selecting is based on a priority of the workload group. One or more recovery actions are performed for the workload group selected for recovery.

Abstract: Systems and methods for re-aligning data replication configuration of a cross-site storage solution after a failover are provided. According to one embodiment, after a failover, the new primary distributed storage system orchestrates flipping of the data replication configuration of a peered consistency group (CG) to reestablish zero RPO and zero RTO protections for the peered CG. The primary causes the secondary distributed storage system to perform an atomic database operation on its remote configuration database to (i) delete an existing source configuration that identifies the secondary as a source of data replication; and (ii) persist a new destination configuration identifying the secondary as a destination of data replication.

Abstract: According to some embodiments, a system comprises a computer system comprising a processing unit, an interrupt controller, an internal watchdog, and a computer system reset interface. The system further comprises a watchdog controller comprising a secondary watchdog timer. Expiry of the computer system internal watchdog triggers the interrupt controller to cause the processing unit to collect debug information and triggers the watchdog controller to start a secondary watchdog timer. Expiry of the secondary watchdog timer triggers the watchdog controller to reset the computer system.

Abstract: A first non-volatile dual in-line memory module (NVDIMM) of a first server and a second NVDIMM of a second server are armed during initial program load in a dual-server based storage system to configure the first NVDIMM and the second NVDIMM to retain data on power loss. Prior to initiating a safe data commit scan to destage modified data from the first server to a secondary storage, a determination is made as to whether the first NVDIMM is armed. In response to determining that the first NVDIMM is not armed, a failover is initiated to the second server.

Abstract: Techniques for rebuilding a failed drive of a plurality of drives are provided. The techniques include: (a) determining a number of empty data stripes that have been allocated from the plurality of drives; (b) applying a set of decision criteria to the determined number to yield a decision, wherein applying the set of decision criteria yields a first decision at a first time and a differing second decision at a second time; (c) in response to the first decision at the first time, deallocating an empty data stripe that was allocated from the plurality of drives to yield a plurality of data extents on disparate drives of the plurality of drives and continuing to rebuild the failed drive onto at least one of the plurality of data extents; and (d) in response to the second decision at the second time, pausing rebuilding the failed drive until applying the set of decision criteria yields the first decision.

Abstract: Systems and methods for a service based disaster recovery system are disclosed. Embodiments may include the ability to configure and deploy a DR environment, including providing the ability to configure a DR service in the DR environment for one or more deployed primary services in a primary environment. An environment management database holds DR configuration data including the status of the deployed services. An environment manager may interact with the environment management database to determine an associated action for the services. The services may perform activation (e.g., wake up) or enter a standby mode (e.g., sleep) depending on the determined action.

Abstract: In an embodiment, a system includes a plurality of memory components and a processing device. The processing device includes a command-lifecycle logger component that is configured to perform command-lifecycle-logging operations, which include detecting a triggering event for logging command-lifecycle debugging data, and responsively logging command-lifecycle debugging data. Logging command-lifecycle debugging data includes generating the command-lifecycle debugging data and storing the generated command-lifecycle debugging data in data storage.

Abstract: A cluster of processing elements has a split mode in which the processing elements are configured to process independent processing workloads, and a lock mode in which the processing elements comprise at least one primary processing element and at least one redundant processing element, each redundant processing element configured to perform a redundant processing workload for checking an outcome of a primary processing workload performed by a corresponding primary processing element. A shared cache is provided, having a predetermined cache capacity accessible to each of the processing elements when in the split mode. In the lock mode, the predetermined cache capacity of the shared cache is fully accessible to the at least one primary processing element.

Abstract: Failover methods and systems for a networked storage environment are provided. A filtering data structure and a metadata data structure are generated before starting a replay of a log stored in a non-volatile memory of a second storage node, during a failover operation initiated in response to a failure at a first storage node. The second storage node operates as a partner node of the first storage node to mirror at the log one or more write requests received by the first storage node prior to the failure, and data associated with the one or more write requests. The filtering data structure identifies each log entry and the metadata structure stores a metadata attribute of each log entry. The filtering data structure and the metadata structure are used for providing access to a logical storage object during the log replay from the second storage node.

Abstract: A method of failure detection in a storage system is performed by the storage system. The method includes detecting a failure in a nonvolatile random access memory device that is in or coupled to a storage device having storage memory. The storage system has multiple NVRAM devices and multiple storage devices that have storage memory. The method includes taking a portion or all of the NVRAM device offline. Taking a portion or all of the NVRAM device offline is responsive to detecting the failure. Taking a portion or all of the NVRAM device off-line is while keeping online the storage memory of the storage device, sufficient ones of the NVRAM devices, and sufficient ones of the storage devices to provide reliable access to data and metadata in the storage system.

Abstract: Novel and useful system and methods of several functional safety mechanisms for use in an artificial neural network (ANN) processor. The mechanisms can be deployed individually or in combination to provide a desired level of safety in neural networks. Multiple strategies are applied involving redundancy by design, redundancy through spatial mapping as well as self-tuning procedures that modify static (weights) and monitor dynamic (activations) behavior. The various mechanisms of the present invention address ANN system level safety in situ, as a system level strategy that is tightly coupled with the processor architecture. The NN processor incorporates several functional safety concepts which reduce its risk of failure that occurs during operation from going unnoticed. The mechanisms function to detect and promptly flag and report the occurrence of an error with some mechanisms capable of correction as well.