Methods, systems, and computer programs encoded on computer storage media, for implementing MPP relational databases using containers. One example system initiates primary containers to implement database segment instances. Each segment of the database is stored on a respective storage volume. Each storage volume is mounted on a respective primary container. The system detects a failure of a first primary container that is a segment instance of a first database segment. In response to the detection, the system performs a recovery process. The system unmounts, from the failed first primary container, a first storage volume storing the first database segment. The system selects a standby container from a pool of standby containers and mounts the first storage volume on the selected standby container. The system is reconfigured so that it processes queries for the first database segment using the selected standby container instead of the failed first container.

An apparatus comprises a first storage system comprising a plurality of storage devices. The first storage system is configured to participate in a replication process with a second storage system. The first storage system is further configured to identify data to be replicated to the second storage system as part of the replication process, to obtain information characterizing network behavior of at least one network connecting the first storage system to the second storage system, to select a compression method from a set of available compression methods based on the obtained information characterizing the network behavior of said at least one network, to compress the data to be replicated to the second storage system utilizing the selected compression method, and to provide the compressed data to the second storage system.

A continuous data protection unit (CDP unit) is arranged to receive from a primary splitter, a copy of incoming data sent to a primary storage in the form of incoming change sets. The CDP unit comprises CDP data mover, and CDP storage unit. The CDP data mover is arranged to receive the incoming change sets and write recovery data based on one or more change sets to the CDP storage unit and to a recovery unit arranged to hold a copy of the recovery data.

A computer program product, system, and method for determining a number of chunks written to a storage volume during a first replication cycle; determining a host write rate based on the number of chunks written to the storage volume during the first replication cycle; estimating a number of chunks written during a second replication cycle; determining a target rate based on the estimated number of chunks written during the second replication cycle; and transmitting chunks written during the second replication cycle at the target rate.

A system includes determination of a plurality of meta-copysets of a plurality of storage devices, each of the meta-copysets including a first number of storage devices, determination of a first copyset of a second number of storage devices from a first one of the meta-copysets, where the second number is less than the first number, storage of first data in a fault-tolerant format using the first copyset, determination to migrate the first data from a first storage device of the first copyset, and, in response to the determination to migrate the first data, determine a second copyset of the second number of storage devices including a storage device from the first meta-copyset which is not in the first copyset, and the storage devices of the first copyset except for the first storage device of the first copyset and storage of the first data in a fault-tolerant format using the second copyset.

Methods, computer program products, and systems are presented. The methods include, for instance: analyzing a dataset associated with a service provided by the data protection service provider in order to determine a policy for when and how to replicate the respective components of the dataset corresponding to the service from a source site to a target site, such that the target site may perform the service with a minimum cost.

A streamlined approach enables customers to retain management control over their data in a database-as-a-service (DBaaS) setting, by providing managed backup copies outside cloud service providers' sphere of control. An illustrative data storage management system provides control over performing backup operations to generate managed backup copies, storing managed backup copies, recovering managed backup copies in whole or in part, migrating managed backup copies, and migrating DBaaS instances. Management control also extends to choices of where to store the managed backup copies, whether on the same cloud computing platform as the source DBaaS, on a different cloud computing platform, and/or in a non-cloud data center.

A method, system, and computer program product for intercepting IO to a virtual machine file system by a storage based splitter, replicating, via a replication appliance, the IO to a replica of the image; the replica of the image containing a replica of the virtual machine file system, and periodically mounting the replica of the virtual machine file system to create entries for a database tracking information about the virtual machines running in the hypervisor.

Application service configuration of a timeframe for performing dataloss failover (failover that does not attempt full data replication to the secondary data store) from a primary data store to the secondary data store. A data-tier service, such as perhaps a database as a service (or DBaaS), could receive that configuration from the application service and automatically perform the dataloss failover as configured by the application service. This relieves the application service from having to manage the failover workflow while still allowing the application service to appropriately balance the timing of dataloss failover, which will depend on a very application-specific optimal balance between the negative effects of operational latency versus dataloss.

In one aspect of the present description, safe data commit scan operations of individual data storage systems of a distributed data storage system may be synchronized to reduce the occurrence of reductions in input/output (I/O) response times. In one embodiment, a set of safe data commit scan operations of the individual data storage systems of a distributed data storage system are synchronously timed to substantially overlap in time within a single synchronized safe data commit scan set interval to reduce or eliminate the occurrences of reductions in input/output response times outside the synchronized safe data commit scan set interval. Other features and aspects may be realized, depending upon the particular application.