G06F11/1458

Managing updates and copying data in a point-in-time copy relationship expressed as source logical addresses and target logical addresses

Provided are a computer program product, system, and method for managing updates and copying data in a point-in-time copy relationship expressed as source logical addresses and target logical addresses. A copy relationship indicates a source set of a subset of source logical addresses to copy to a target set comprising a subset of target logical addresses. An update is received to a source logical address that has not been copied. Determinations are made of the target logical address corresponding to the source logical address to be updated according to the copy relationship, a target group of target logical addresses in the target set that include the determined target logical address, and the source logical addresses in the source set that correspond to the target logical addresses in the target group. The determined source logical addresses are copied to the target logical addresses in the determined target group.

Apparatuses, methods and systems for determining a virtual machine state
09836347 · 2017-12-05 · ·

APPARATUSES, METHODS AND SYSTEMS FOR DETERMINING A VIRTUAL MACHINE STATE (“CRV”) (transforms register retrieval requests, via CRV components, into boot success messages and screenshot capture command invocation outputs. A method comprises determining when to capture a screenshot of a virtual machine's display output by observing the values of a virtual CPU's registers, or the entropy of the virtual CPU's register values, obtained from a hypervisor in communication with the virtual machine's virtual CPU. The method further comprises determining when the virtual machine is at a boot success state and capturing a screenshot of the virtual machine display output.

Long Running Operations Implementation
20230185602 · 2023-06-15 · ·

A system for processing database requests includes an operator module operable to receive a request requiring a long running operation, and assign an operation identification (ID) to the long running operation; and a database module for receiving the request and the operation ID, the database module including a database daemon for launching the long running operation, storing a state of the long running operation, and reporting a status of the long running operation.

Data backup with rolling baselines

First partial baseline data of a first storage system is identified. First changed data of the first storage system is identified. The first changed data comprises data that has changed since a previous point in time. First backup data is written to a second storage system. The first backup data comprises the first partial baseline data and the first changed data. After writing the first backup data to the second storage system, second partial baseline data of the first storage system is identified. The second partial baseline data does not include the first partial baseline data. Second changed data of the first storage system is identified. The second changed data comprises data that has changed since writing the first backup data. Second backup data is written to the second storage system. The second backup data comprises the second partial baseline data and the second changed data.

Recovery strategy with dynamic number of volumes

A system includes reception of a command to recover a database to a point in time, determining a log backup which covers the point in time, determination of a sequence identifier associated with the log backup, collection of log backups which are older than the determined log backup and associated with the sequence identifier, and a data backup associated with the sequence identifier, and execution of a recovery of the database based on the determined log backup and the collected log backups and data backup.

DIFFERENTIAL LOGGING OF COMPUTING PROCESSES

Techniques and solutions are provided to facilitate logging of computing processes. A computing process generates multiple log entries. A first portion of the multiple log entries are written to a first log. A second portion of the multiple log entries are written to the first log and to a second log, where the second portion is less than the first portion, such as being a proper subset of the first portion. Log entries can be determined to be written to the second log by scanning all or a portion of a log, by evaluating log entries as they are generated, or through computer code that causes log entries to be written to the second log. Typically, the second log is maintained for a longer period of time than the first log.

DATA DUPLICATION SYSTEM AND BACKUP METHOD
20230185673 · 2023-06-15 ·

The data duplication system comprises a first storage device having a first data protection area for storing backup images of multiple generations of a first volume for data read/write by an external device. The first data protection area is inaccessible to the external device. A second storage device coupled to the first storage device. The first storage device creates a second volume for storing a backup image of a particular generation of the plurality of generations of backup images stored in the first data protection area. The second storage device creates a third volume for storing the copy data, and a virtual volume that is mapped to the second volume of the first storage device. The second storage stores the backup data of a specific generation stored in the second volume in the third volume via the virtual volume by forming a pair that copies the data in the virtual volume and the third volume.

EDGED CLOUD APPLICATION BACKUP

In an approach for in-band selective data snapshot using fifth generation (5G) radio link control (RLC) channels for edged cloud application backups, a processor creates one or more RLC channels to transfer network data packets in a telecommunication network using a network slicing technology. A processor allocates the one or more RLC channels to one or more applications in a user device for dedicated packet routing requirements. A processor maps the corresponding RLC channels and applications with corresponding identifiers, respectively. A processor monitors the one or more applications for backups. A processor, in response to receiving an application's backup request, creates a copy of a datastore associated with the application based on changes monitored in the one or more applications.

Systems and methods for backing up heterogeneous virtual environments

The disclosed computer-implemented method for backing up heterogeneous virtual environments may include (1) identifying a request to back up a virtual machine executing on a host system, (2) creating a storage map of a virtual storage environment of the virtual machine by (a) identifying, from the host system, a virtual disk file that stores data for the virtual machine and (b) identifying, from a guest system operating within the virtual machine, one or more virtual storage devices that store data for the virtual machine, and (3) creating a unified backup of the virtual machine based on the storage map of the virtual storage environment by coordinating a backup operation of the virtual disk file with a backup operation of the virtual storage device. Various other methods, systems, and computer-readable media are also disclosed.

Dynamically meeting slas without provisioning static capacity
09838332 · 2017-12-05 · ·

In one example, a method for identifying and allocating resources in a computing system, including checking, while one or more backup processes are running, database connections in an auto scaling group to determine if a number of database connections in use in connection with the backup processes has decreased since a prior check was performed. When the number of database connections in use has decreased, an identification is made as to which of a plurality of queues each respectively associated with one of the backup processes has the greatest need for additional database connections. Next, various metrics are evaluated and, based on the evaluation of the metrics, one or more available database connections are assigned to the queue with the greatest need for additional database connections.