Abstract: Faults are managed in a virtual machine network. Failure of operation of a virtual machine among a plurality of different types of virtual machines operating in the virtual machine network is detected. The virtual machine network operates on network elements connected by transport mechanisms. A cause of the failure of the operation of the virtual machine is determined, and recovery of the virtual machine is initiated based on the determined cause of the failure.

Abstract: Systems and methods for mobile application accessibility testing are disclosed. According to one embodiment, in a test bench comprising at least one computer processor, a method for mobile application accessibility testing may include: (1) identifying an accessibility checkpoint for testing; (2) generating a test command for the accessibility checkpoint; (3) communicating the test command to a mobile electronic device, the mobile electronic device having a mobile application to be tested, an instrument application, and probe application in a memory thereof; (4) executing the test command on the mobile application to be tested using the instrument application; and (5) collecting results of the execution using the probe application.

Abstract: In part, the disclosure relates to a real-time fault tolerant system. The system may include a first computing device, a second computing, and a hardware interconnect. The first computing device may include one or more memory devices, one or more processors, a first network interface operable to receive device data and transmit output data over a time-slot-based bus, wherein the output data is generated from processing device data, and a first real-time checkpoint engine. The second computing device may include similar components or the same components as the first computing device. The hardware interconnect is operable to permit data exchange between the first computing device and the second computing device. Checkpoints may be generated by checkpoint engines during lower-priority communication time slots allocated on the time slot-based bus to avoid interfering with any real-time communications to or from the first and second computing devices.

Abstract: A data protection system configured to replicate data may generate rescue packages that allow the system to recover when communication between a splitter or source of the production data being replicated and an appliance that stores the replicated data is disrupted. The rescue package is stored on a datastore and is then retrieved by the data protection system or another splitter. After processing the rescue package, which may contain IOs that the data protection is unaware of due to the communication disruption, replication may resume normally.

Abstract: A method, computer program product, and computer system for identifying a bit for an allocation unit. It may be determined if data has been modified on the allocation unit while degraded. A rebuild of the allocation unit may be executed when the bit is a first value. The rebuild of the allocation unit may be skipped when the bit is a second value.

Abstract: Providing for high availability in a data analytics pipeline without replicas, including: creating a data analytics pipeline, wherein each component of the data analytics pipeline is deployed within a container; creating a failover container; detecting that a component within the data analytics pipeline has failed; and responsive to detecting that the component within the data analytics pipeline has failed, deploying the component within the data analytics pipeline that has failed in the failover container.

Abstract: A method for backing up data is performed by a backup manager. The method includes obtaining, by the backup manager, a first request from a host, wherein the first request is associated with an application on the host; in response to the first request: obtaining backup policies; obtaining a tag associated with the application; making a first determination that the tag indicates that the application is a cloud native application; and in response to the first determination: associating the application with a cloud native backup policy, wherein the cloud native backup policy is one of the backup policies; and initiating backup generation of the application based on the cloud native backup policy.

Abstract: A method and apparatus for recovery from node crash, an electronic device, and a storage medium are provided. The method is applicable to a proxy server in a master-slave system. The master-slave system further includes a target master node controlled by the proxy server and a target slave node corresponding to the target master node. If the target master node and the target slave node crash, the proxy server obtains a pre-stored persistent file from the target slave node. The target slave node stores a backup of cache data cached in the target master node, and the persistent file is generated based on cache data in the target slave node. A target master node that does not crash is deployed based on the persistent file; and a target slave node corresponding to the target master node that does not crash is deployed. In this solution, after the target master node and the target slave node both crash, the master-slave system can be recovered to a normal working state.

Abstract: In some examples, a data management and storage (DMS) cluster comprises peer DMS nodes and a distributed data store implemented across the peer DMS nodes. The peer DMS nodes are configured to collectively implement operations in a method of remote linking of snappables for data transfer between a first node cluster and a second node cluster among the peer DMS nodes.

Abstract: A system and method improve the performance of non-volatile memory storage by rebuilding, on the fly, “lost data” in response to a read request, which identifies data to be read or recovered, by identifying a parity data storage device in a set of data storage devices that contains parity corresponding to the identified data; sending a reconstruction request to a respective data storage device, which may be the parity data storage device or other data storage device in the system, to reconstruct the identified data, and receiving the identified data from the respective data storage device. The reconstruction request commands the respective data storage device to retrieve, via peer-to-peer read requests, from other data storage devices, data from one or more data blocks, and to reconstruct the identified data based on the retrieved data and parity data locally stored at the parity data storage device.

Abstract: In general, in one aspect, the invention relates to a method for accessing backup data includes receiving a live mount connection request from a client device, in response to the live mount connection request: generating a directory, populating the directory with a backup control file image and a plurality of pointers to backup data file images in a second directory, wherein the backup control file image is obtained from the second directory, restoring at least a portion of the backup data file images in the directory using the backup control file image and at least a portion of the backup data file images in the second directory, and providing after the restoring, a handle to the directory to the client device.

Abstract: A server system comprising storage devices, processing devices and a storage fabric all operating according to a storage fabric protocol. The storage fabric comprises a plurality of individual switches having a modular design from which an overall switch is built, and the individual switches have individual respective configuration settings which determine which processing devices are allocated to use which of the storage devices. The system comprises an API enabling a software control function to configure the overall switch. The API is operable to receive from the control function an overall mapping of the storage devices to the processing devices instead of requiring the individual configuration settings of each of the individual switches to be specified by the control function, the API being configured to convert the overall mapping into the individual configuration settings of the individual switches to produce the overall mapping.

Abstract: A storage system includes stripes, extents included in one stripe among the stripes reside on storage devices in the storage system, respectively, and the storage system includes an address mapping between the stripe and storage devices where the extents reside. Regarding one extent, a storage device where the extent resides is determined among the storage devices based on the address mapping. The stripe is added to a rebuild list of the storage system in accordance with determining the storage device is a failed storage device, the rebuild list comprising a stripe that is to be rebuilt in the storage system. The storage system is rebuilt based on stripes in the rebuild list. Accordingly, the performance of a rebuild operation may be improved, and the time for the rebuild operation may be reduced. Further, there is provided a corresponding device and computer program product for managing a storage system.

Abstract: A method for linking a selected portion of the data stored in a source database to a set of target database(s), determining that a crash of the source database has occurred, and restoring a latest database state of the source database, with the restoration including: triggering a remote recovery process, and restoring data of the selected portion in the source database from: copy(ies) of data entries stored in one, or more, target database(s) of the set of target database(s), and records from a recovery log file of the source database for data entries that have a later timestamp than corresponding copies of the data entry(ies) as stored in the target database(s) of the set of target database(s).

Abstract: In some embodiments, a processing system includes at least one hardware block configured to change operation as a function of configuration data, a non-volatile memory including the configuration data for the at least one hardware block, and a configuration module configured to read the configuration data from the non-volatile memory and provide the configuration data read from the non-volatile memory to the at least one hardware block. The configuration module is configured to: receive mode configuration data; read the configuration data from the non-volatile memory; test whether the configuration data contain errors by verifying whether the configuration data are corrupted and/or invalid; and activate a normal operation mode or an error operation mode based on whether the configuration data contain or do not contain errors.

Abstract: The fail-over computer cluster enables multiple computing devices to operate using adaptive quorum rules to dictate which nodes are in the fail-over cluster at any given time. The adaptive quorum rules provide requirements for communications between nodes and connections with voting file systems. The adaptive quorum rules include particular recovery rules for unplanned changes in node configuration, such as due to a disruptive event. Such recovery quorum rules enable the fail-over cluster to continuing to operate with various changed configurations of its node members as a result of the disruptive event. In the changed configuration, access to voting file systems may not be required for a majority-group subset of nodes. If no majority-group subset remains, nodes may need direct or indirect access to voting file systems.

Abstract: A processing device in a memory system receives, from a host system, a request for a debug slave address associated with a system management bus port of a memory sub-system and sends a response comprising the debug slave address to the host system. The processing device receives, from the host system, a request to enable the system management bus port to receive a request for debug information directed to the debug slave address, receives, from the host system, the request for debug information directed to the debug slave address, and sends the debug information to the host system over a system management bus coupled to the system management bus port of the memory sub-system.

Abstract: A method and apparatus for performing node information exchange management of an all flash array (AFA) server are provided. The method may include: utilizing a hardware manager module among multiple program modules running on any node of multiple nodes of the AFA server to control multiple hardware components in a hardware layer of the any node, for establishing a Board Management Controller (BMC) path between the any node and a remote node among the multiple nodes; utilizing at least two communications paths to exchange respective node information of the any node and the remote node, to control a high availability (HA) architecture of the AFA server according to the respective node information of the any node and the remote node, for continuously providing a service to a user of the AFA server; and in response to malfunction of any communications path, utilizing remaining communications path(s) to exchange the node information.

Abstract: The disclosure herein describes enhancing data durability of a base component using multiple delta components. A first and second delta component are generated based on the base component becoming unavailable. A write operation targeted for the base component is routed to the first delta component and to the second delta component. Based on routing the write operation targeted for the base component to the first delta component and to the second delta component, a bit associated with a data block affected by the write operation is changed in each of the tracking bitmaps of the first and second delta components. Based on detecting the base component becoming available, one delta component of the first and second delta components is selected, and the data block affected by the routed write operation is synchronized from the selected delta component to the base component. Later, the first and second delta components are removed.

Abstract: A method for maintaining linked databases including a source database and a target database, maintaining first metadata in a recovery log file of the source database, maintaining second metadata that identifies portions of data that are replicated from the source database to the target database as part of the selected partitions of the selected tables, receiving an indication that a crash of the source database has occurred, determining a first recovery metric value for recovering the source database's, determining a second recovery metric value for recovering the source database's data from the target database based on the second metadata, and determining whether to recover the source database's data from the recovery log file of the source database or from the target database based on a comparison of the determined first recovery metric value and the second recovery metric value.