Abstract: Provided are a computer program product, system, and method for hypervisor agnostic interchangeable backup recovery and file level recovery from virtual disks. Data is stored for a first virtual disk that represents data in a first format and metadata for the first virtual disk in a common data format in a storage having a fixed block length. A virtual disk file represents data in a second format that allows variable size blocks. Multiple instances of the fixed block length of blocks of data for the second virtual disk indicated in the virtual disk file are read. Each instance of the read fixed block length of blocks is written to the storage in the common data format with metadata describing the format of the blocks in the second virtual disk, and can be restored to a third virtual disk in the first or second format.

Abstract: There is disclosed in one example a network device, including: a hardware platform including at least a processor and a memory; a communication interface; and stored instructions on the memory to instruct the processor to provide a health monitoring engine (HME) configured to: communicatively couple to a network via the network interface; construct a reference template during a training period; observe watchdog behavior on the network during an observation period; identify an abnormality in the watchdog behavior including a substantial variance from the reference template; and trigger a resilience response to the substantial variance.

Abstract: Techniques disclosed herein provide for improved backup copy management in an information processing system. For example, a method comprises obtaining a set of one or more values representing a backup plan factor respectively corresponding to a set of one or more storage systems upon which data associated with the execution of application programs on one or more host servers coupled to the set of storage systems is stored. The method compares the obtained set of one or more values with a set of one or more threshold values. The method predicts whether a scheduled backup plan corresponding to each of the set of one or more storage systems is likely to fail based on a result of comparing the obtained set of one or more values with the set of one or more threshold values.

Abstract: The first computing system may interface with an operator of the application and a plurality of hosts of the application distributed between different partitions. The second and third computing systems may host first and second portion of the application in first and second partitions, respectively. The second and third computing systems may poll the first computing system to identify first and second value, respectively, representing state conditions of the first and second partitions, respectively, wherein the first and second partition state conditions are the active state, the passive state, and the fenced state. The second and third computing systems may receive responses from the first computing system comprising the first and second values, respectively, and based on the respective values, initiate a transition to the corresponding partition state condition. The first computing system may assign one of the first and second values to indicate which is the active state.

Abstract: A live migration/high availability system includes a first computing system having a first SCP subsystem coupled to first computing system components and a first hypervisor subsystem that provides a first virtual machine. Each time the first SCP subsystem receives snapshot commands from the hypervisor subsystem, it retrieves respective SCP component state information that was not retrieved in response to a previous snapshot command from each first SCP component included in the first SCP subsystem, and uses the respective SCP component state information to generate a respective SCP subsystem snapshot based on that snapshot command. The first SCP subsystem then transmits the SCP subsystem snapshots to a second SCP subsystem in a second computing system, and the second SCP subsystem uses the SCP subsystem snapshots to allow a second hypervisor subsystem on the second computing system to provide a second virtual machine that operates the same as the first virtual machine.

Abstract: This application discloses a disaster recovery deployment method, apparatus, and system, and relates to the field of network application technologies. The method includes: obtaining, by a master data center and a backup data center, disaster recovery control information; sending, by the master data center, the data corresponding to the service of the master data center to the at least one backup data center based on the disaster recovery control information; and deploying, by the backup data center, a disaster recovery resource for the master data center based on the disaster recovery control information, and backing up the received data. In other words, the master data center and the backup data center automatically back up resources and data based on the disaster recovery control information, and therefore, manual operation steps in a disaster recovery deployment process are simplified, and efficiency of disaster recovery deployment is improved.

Abstract: Writing to a storage system with data striping includes storing blocks of data in local memory until one or more full-stripe write operations can be performed, thus reducing write amplification on the data striped storage system. Crash recovery information includes storing the data associated metadata to respective persistent storage devices. Metadata associated with data from several clients is combined into fixed-size data blocks and stored on the respective persistent storage device.

Abstract: A system and method are presented for a replication protocol in a real-time statistical engine. A real-time statistical engine monitors external data sources and uses received data to derive on-demand statistics. The engine may be comprised of a plurality of instances. In an embodiment with two instances of the engine, the instances are labeled as a primary instance and a backup instance. In case of primary instance failure, client servers of the engine are able to connect to the backup instance and obtain the same statistics with minimal data loss. The communication system between the primary instance and the backup instance may be used to exchange information about requested statistics, to clean unused statistics and to unconditionally delete statistics for which computation has become impossible.

Abstract: A method, a system, and a computer program product for executing a takeover process. A takeover process of a primary computing system by a secondary computing system is triggered. The secondary computing system stores transaction data replicated from the primary computing system. Writing of a redo log of transaction data of one or more transactions into storage by the primary computing system is suspended. The redo log is written by the primary computing system prior to the suspending is transmitted to the secondary computing system. The takeover process of the primary computing system by the secondary computing system is executed upon receiving and persisting the redo log at the secondary computing system.

Abstract: Failure impact analysis (or “impact analysis”) is a process that involves identifying effects of a network event that are may or will results from the network event. In one example, this disclosure describes a method that includes generating, by a control system managing a resource group, a resource graph that models resource and event dependencies between a plurality of resources within the resource group; detecting, by the control system, a first event affecting a first resource of the plurality of resources, wherein the first event is a network event; and identifying, by the control system and based on the dependencies modeled by the resource graph, a second resource that is expected to be affected by the first event.

Abstract: A method, computer program product, and computing system for receiving, via a first node of a plurality of nodes, data for storage in a storage system. The data may be written, via the first node, to one or more data pages of a log buffer of the first node. One or more page descriptors associated with the one or more data pages may be generated via the first node. The one or more page descriptors may be sent to a second node concurrently with the writing of the data to the one or more data pages of the log buffer of the first node.

Abstract: In some examples, a memory module includes an error status indicator, an error address register, and error tracking circuitry. The error tracking circuitry may detect that memory data stored at a memory address for the memory module includes an error. In response, and without overwriting the memory data stored at the memory address, the error tracking circuitry may set the error status indicator and store the memory address in the error address register.

Abstract: A method of simulating device state changes in an integrated system includes receiving a transaction request from a client device, storing the transaction request as a first event in an event log, transmitting the transaction request to a terminal device, storing the transmission of the transaction request as a second event in the event log, receiving a device response from the terminal device, storing the device response as a third event in the event log, and when the integrated system is under test, a simulator replays the stored events in the integrated system under test.

Abstract: Technology for determining whether an inter-process type message has been successfully sent from a first process to a second process running on a single computer with a single processor(s) set. A variable (for example, a bit value) is used to indicate whether the inter-process message has been communicated between the processes. A timer and a predetermined timeout threshold are used to determine if the inter-process message has been pending for too long without being successfully communicated.

Abstract: A variety of applications can include apparatus and/or methods to preemptively detect detect one memory blocks in a memory device and handle these memory blocks before they fail and trigger a data loss event. Metrics based on memory operations can be used to facilitate the examination of the memory blocks. One or more metrics associated with a memory operation on a block of memory can be tracked and a Z-score for each metric can be generated. In response to a comparison of a Z-score for a metric to a Z-score threshold for the metric, operations can be performed to control possible retirement of the memory block beginning with the comparison. Additional apparatus, systems, and methods are disclosed.

Abstract: A new alert associated with a computer information technology issue to be remediated is received. Matching previous alerts similar to the new alert are determined. One or more successful remediation actions of the matching previous alerts are identified. The one or more successful remediation actions are evaluated. A performance of a selected one of the one or more successful remediation actions is initiated.

Abstract: Provided are a computer program product, system, and method for using mirror path statistics in recalling extents to a primary storage system and a secondary storage system from a third storage system, A recall request is received to recall extents from the third storage that were migrated from the primary storage or the secondary storage to the third storage. A determination is made as to whether mirror paths used to migrate extents from the primary storage to the secondary storage exceed a degradation criteria. Commands are sent to cause the recall extents to be recalled from the third storage to both the primary storage and the secondary storage in response to determining that the mirror paths exceed the degradation criteria.

Abstract: A method and technique for data lifecycle management includes storing in a memory from a monitored system one or more metrics. A fault from the monitored system is identified and a first metric from the one or more metrics as being related to the fault is identified. A lifespan is assigned to the first metric, and the first metric is removed from the memory if the lifespan is over.

Abstract: Examples of techniques for function modification for software application testing are described herein. An aspect includes, based on a function call to a function by an application under test that is being tested using a test case in a testing environment, determining whether modification of the function is enabled. Another aspect includes, based on determining that modification of the function is enabled, running the function in a modified mode.

Abstract: A method is provided. The method of resetting a system, comprising: receiving data from the electronic sub-system; determine if a non-hardware fault is detected; if a non-hardware fault is detected, then performing a software reset of the electronics sub-system; if no non-hardware fault has been detected, then determining if a hardware fault is detected; and if a hardware fault is detected, then performing a hardware reset of the system.