Methods and systems for transferring a host image of a first machine to a second machine, such as during disaster recovery or migration, are disclosed. In one example, a first profile of a first machine of a first type is compared to a second profile of a second machine of a second type different from the first type, to which the host image is to be transferred. The first and second profiles each comprise at least one property of the first type of first machine and the second type of second machine, respectively. At least one property of a host image of the first machine is conformed to at least one corresponding property of the second machine. The conformed host image is provided to the second machine, via a network. The second machine is configured with at least one conformed property of the host image.

A vehicular control system includes a plurality of electronic control units (ECUs), each providing a respective quantity of computational units representative of an amount of processing power of the respective ECU. The ECUs operate a vehicle in a nominal autonomous operational mode when a sum of the quantity of computational units exceeds a threshold. The system, while the ECUs operate the vehicle in the nominal autonomous operational mode, and responsive to detecting a failure of one of the ECUs, determines whether a sum of the quantity of computational units of the remaining ECUs that do not have a failure exceeds the threshold. The ECUs, responsive to the system determining that the sum of the quantity of computational units of the remaining ECUs fails to exceed the threshold, switches from operating the vehicle in the nominal autonomous operational mode to operating the vehicle in a degraded autonomous operational mode.

Systems and methods for utilizing tablespace to export from a foreign database recovery environment are described. The system includes a backup host that operates in a foreign database recovery environment and receives a database from a source host operating in a native database recovery environment. The backup host receives export information including a tablespace identifier and a point-in-time. The tablespace includes file information for export from the backup host to the source host. A job is initiated on the backup host to generate script information (including logic for execution on the source host to recover the tablespace, at the point-in-time, in the database on the source host), create directories on the backup host, materialize file information including snapshots of the database and incremental changes to the database, and communicate the file information and the script information, via the directories, to the source host.

Recovery points can be used for replicating a virtual machine and reverting the virtual machine to a different state. A filter driver can monitor and capture input/output commands between a virtual machine and a virtual machine disk. The captured input/output commands can be used to create a recovery point. The recovery point can be associated with a bitmap that may be used to identify data blocks that have been modified between two versions of the virtual machine. Using this bitmap, a virtual machine may be reverted or restored to a different state by replacing modified data blocks and without replacing the entire virtual machine disk.

A sensor subsystem for vehicles, such as autonomous driving vehicles, has two network ports for which each network port is connectable to one of two in-vehicle computers (IVCs) for control, configuration, status and data transfers between the sensor subsystem and the two IVCs. The two IVCs can be structured as redundant IVCs. The sensor subsystem can replicate sensor data to the redundant IVCs. The sensor data can be raw image data, encoded image data, processed perception data, or a combination of the data. The two IVCs can be implemented with a modular design with each IVC disposed on a platform separate from the platform on which the second of the two redundant IVCs is disposed. The two IVCs can be replaced separately to reduce repair or replacement cost.

A “backup services container” comprises “backup toolkits,” which include scripts for accessing containerized applications plus enabling utilities/environments for executing the scripts. The backup services container is added to Kubernetes pods comprising containerized applications without changing other pod containers. For maximum value and advantage, the backup services container is “over-equipped” with toolkits. The backup services container selects and applies a suitable backup toolkit to a containerized application to ready it for a pending backup. Interoperability with a proprietary data storage management system provides features that are not possible with third-party backup systems. Some embodiments include one or more components of the proprietary data storage management within the illustrative backup services container. Some embodiments include one or more components of the proprietary data storage management system in a backup services pod configured in a Kubernetes node. All configurations and embodiments are suitable for cloud and/or non-cloud computing environments.

To address loss of access to computing instances in a cloud computing environment, techniques are introduced for moving an application between computing instances in the cloud computing environment. A computing service captures baseline or delta snapshots of the state of the application running on a first computing instance. A baseline snapshot is indicative of the full state of the application, and a delta snapshot is indicative of changes in the state since a most recent snapshot was captured. Responsive to receiving an indication that the first computing instance is to stop servicing the application, the computing service stops the application from running on the first computing instance and moves data from the captured snapshots to a second computing instance. The computing service resume execution of the application on the second computing instances and captures snapshots of the state of the application at the second computing instance.

A method and device for managing an emergency procedure of an emergency transaction mode that can be activated in the event of a computer attack on or a failure of a transaction network. The method may be carried out by an electronic device suitable for performing a transaction in a normal mode or in the emergency mode. The method performs operations that may include receiving an activation command for activating the emergency mode procedure, where the command includes an identifier of the procedure and first encrypted data; verifying the activation command, which includes verifying the first encrypted data; and if verification of the command is successful, activating the emergency procedure.

A storage system determines source addresses, and destination addresses in a storage system, for network traffic. The storage system determines a hash algorithm, from a plurality of hash algorithms. The hash algorithm is to be used across the source addresses for load-balancing the network traffic to the destination addresses. The storage system determines that the hash algorithm more closely meets one or more load-balancing criteria than at least one other hash algorithm, of the plurality of hash algorithms. The storage system distributes the network traffic from the source addresses to the destination addresses in the storage system, with load-balancing according to the determined hash algorithm.

A computer-implemented method, computer system and computer program product dynamically manage failure in an edge computing environment. According to the method, a request for executing a task may be sent to a first edge device according to a defined process, where the defined process is used to schedule tasks to be executed on edge devices. In response to the first edge device failing to execute the task, the defined process may be suspended. Then, a request for executing the task may be sent to a second edge device. A task result that is received first may be taken as the task result for the task, where the task result is from either the first edge device or the second edge device. And, continuing the rest of the defined process.