Abstract: Techniques for failover management using availability groups are described. According to some embodiments, customers can define one or more availability groups within their infrastructure. Each availability group may be associated with one or more rules which describe how the availability group should fail over. The availability group definition may define the resources included in the availability group, a target region to fail over to, and capacity reservations for the availability group in the target region. In some embodiments, the definition may also include a replication frequency for storage resources which defines how often data is backed up. Once a customer as created an availability group the customer is then able to either create resources in that availability group or associate already existing resources with the availability group. An availability group management service can ensure that data, capacity reservations and network infrastructure are defined and/or replicated to the target location.

Abstract: A method of cache hit ratio simulation using a partial data set includes determining a set of sampled addresses, the set of sampled addresses being a subset of all addresses of a storage system of a storage environment. The method further includes using, by a simulation engine, a cache management algorithm to determine a cache hit ratio of the sampled addresses, the cache management algorithm being also used by a cache manager to place a portion of the addresses of the storage system into cache during a runtime operation. The method further includes determining a quantity of memory access operations to frequently accessed addresses in the set of sampled addresses, and correcting, by the simulation engine, the cache hit ratio of the sampled addresses based on the quantity of memory access operations to the frequently accessed addresses in the set of sampled addresses. The simulation also handles sequential operations accurately.

Abstract: Method providing resilient execution of a service on a computing device. The service is stored in a non-volatile memory of the computing device and comprises instructions executable by a processor of the computing device. The processor generates an operational instance of the service, which comprises a reference to the service. The processor stores the operational instance of the service in the non-volatile memory with a read-write access right. The processor launches an executable instance of the service associated to the operational instance of the service. The launching comprises copying the instructions of the service from the non-volatile memory to a volatile memory of the computing device. The launching further comprises executing the instructions of the service copied into the volatile memory. The processor adds data generated by the execution of the instructions of the service to the operational instance of the service for permanent storage in the non-volatile memory.

Abstract: Migrating data from a first storage system to a second storage system includes transferring the data from the first storage system to a cloud storage, transferring the data from the cloud storage to the second storage system, quiescing the first storage system prior to transferring remaining data from the first storage system to the cloud storage, and transferring remaining data from the cloud storage to the second storage system to complete migration of the data. The cloud storage may be accessible only through a private network or via the World Wide Web. Quiescing the first storage system may include the first storage system rejecting write operations or may include one or more external systems coupled to the first storage system foregoing write operations. Snapshots may be performed at the first storage system in response to commands provided by a host coupled to the first storage system.

Abstract: One or more embodiments of a synchronization system facilitate selectivity synchronizing digital content items from a collection of digital content items to a local storage of a client device. In particular, one or more embodiments described herein collect and analyze recall data for users of a digital content management system with respect to digital content items to determine synchronization scores for the digital content items. One or more embodiments described herein further include selectively identifying a subset of the digital content items based on the synchronization scores to recommend for synchronization to a local storage of a client device.

Abstract: Disclosed herein is technology to compare different versions of a code object to determine if the versions include equivalent changes. An example method may include: determining a set of changes of a first version of a code object, wherein the code object comprises a plurality of versions; generating a first hash in view of the set of changes; accessing a second hash representing a set of changes of a second version of the code object; comparing, by a processing device, the first hash and the second hash; and indicating the set of changes of the first version and the set of changes of the second version are equivalent.

Abstract: Embodiments for optimizing dynamic resource allocations for storage-dependent workloads in a disaggregated computing environment. A new workload is assigned to a subset of a plurality of processors, the subset of processors assigned a subset of a plurality of memory devices associated with a plurality of storage devices. A determination is made that the new workload is categorized as a storage-dependent workload having a storage need which can be met primarily by a subset of the storage devices after having identified whether data requests associated with the new workload can be satisfied by the subset of memory devices. Pursuant to determining the new workload is the storage-dependent workload, a storage related action is proactively performed to increase efficiency of the new workload prior to commencement of a performance of the new workload.

Abstract: A distributed storage system including memory hosts and at least one curator in communication with the memory hosts. Each memory host has memory, and the curator manages striping of data across the memory hosts. In response to a memory access request by a client in communication with the memory hosts and the curator, the curator provides the client a file descriptor mapping data stripes and data stripe replications of a file on the memory hosts for remote direct memory access of the file on the memory hosts.

Abstract: A distributed storage system, which receives a write request from a client, includes a plurality of computers which receive power supply from a plurality of power supply units. A first computer, among the plurality of computers, which is a computer that receives the write request from the client, is configured to: cache updated data which is at least apart of data accompanying the write request; select n second computers which are n computers (n is a natural number) among computers each receiving power from a power supply unit different from a power supply unit of the first computer as transfer destinations of the updated data; and transfer the updated data to the selected n second computers, respectively. At least one of the n second computers, when caching the updated data from the first computer, is configured to return a result to the first computer.

Abstract: A memory device comprises a memory control unit including a processor configured to control operation of the memory array according to a first memory management protocol for memory access operations, the first memory management protocol including boundary conditions for multiple operating conditions comprising program/erase (P/E) cycles, error management operations, drive writes per day (DWPD), and power consumption; monitor operating conditions of the memory array for the P/E cycles, error management operations, DWPD, and power consumption; determine when a boundary condition for one of the multiple operating conditions is met; and in response to determining that a first boundary condition for a first monitored operating condition is met, change one or more operating conditions of the first memory management protocol to establish a second memory management protocol for the memory access operations, the second memory management protocol including a change boundary condition of a second monitored operating con

Abstract: Storage of discovered data object to storage layouts is described. A system receives a request to discover a data object to storage layout. The system determines if a discovery log stores a current data object to storage layout. The system provides a backup application with the current data object to storage layout in response to a determination that the discovery log stores the current data object to storage layout.

Abstract: In a storage system having a controller constructing a provision volume provided to a server system and an addition volume in which data to be stored in the provision volume is added and stored, when a provision volume copying instruction is received, the controller inserts a start marker indicating start time point of copying into address change history information and copies address conversion information of a provision volume while receiving update data to a provision volume from the server system, as address conversion information of a copy-destination volume. On the basis of a start marker of address change history information and history information, a change from start to completion of copying of the address conversion information of a copy-destination volume is reset to a state at the start time point of copying.

Abstract: Examples described herein include virtualized file servers which may include cloned instances of the virtualized file server. Cloning a virtualized file server may allow for testing of new and/or revised features, disaster recovery plans, or other configurations while maintaining availability of the parent (e.g., source) virtualized file server.

Abstract: Described herein is a system method for point in time blob restore. In response to receipt of a request to restore a particular blob range to a particular point in time, read and/or write operations on the particular blob range requested to be restored are blocked. Blob(s) in the particular blob range which have changed since the particular point in time are determined based, at least in part, upon information stored in a change log and/or a deleted blob store. A determination is made as to whether the requested restore operation can be performed, for example, based upon a restoration policy. When it is determined that the requested restore operation can be performed, blob(s) determined to have changed since the particular point in time based, at least in part, upon information stored in the change log and/or the deleted blob store are restored.

Abstract: An example printer includes a non-transitory computer-readable medium. The printer also includes a boot engine communicatively coupled to the non-transitory computer-readable medium. The boot engine is to load a boot image into a first portion of the non-transitory computer-readable medium. The boot image includes data from an operational state of an operating system. The printer includes a configuration engine. The configuration engine is to program a second portion of the non-transitory computer-readable medium while the boot engine is loading the boot image.

Abstract: A management apparatus, includes a memory; and a processor coupled to the memory and configured to: manage a library device including one or more drive devices, an accommodation shelf in which accommodation cells that accommodate a plurality of tape media are arranged, and a robot that performs conveyance operation to convey the tape media between the accommodation cells and the drive devices, receive an instruction to write a plurality of pieces of writing data, set, as an erasure coding set, two or more pieces of writing data having a data size less than a threshold among the plurality of pieces of writing data, and allocate the two or more pieces of writing data to one of the plurality of tape media.

Abstract: Techniques are described for allocating computing resources to customers of a multi-tenant web services platform. Computing capacity capable of running a computing instance is allocated to a customer. The computing capacity includes storage capacity that is disassociated from the allocated computing capacity when the allocated computing capacity is de-allocated from the customer. An indication that a virtual storage resource should be associated with the allocated computing capacity is received. The virtual storage resource is persisted independent of the allocation of the computing capacity to the customer. The storage capacity and the virtual storage resource are configured to synchronize data stored thereon while maintaining the storage capacity as an attached storage volume for the computing instance.

Abstract: Techniques are provided for managing the utilization of shared memory resources among a plurality of asynchronous replication workloads. A data replication system maintains a respective replication journal for each replication workload in an allocated portion of system memory of a source server node. Each replication journal is divided into journal barrier intervals by respective individual barriers for transmission to a destination server node. The data replication system waits for a triggering event to occur for generating a common barrier, wherein the triggering event is configured to prevent exhaustion of the allocated portion of system memory for storing the replication journals. The common barrier is generated to close the replication journals of some or all of the replication workloads in advance of the respective individual barriers associated, and the replication journals closed by the common barrier are transmitted to the destination server node.

Abstract: 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.

Abstract: A data storage device includes a memory array including a plurality of memory cells; and a controller in communication with the memory array and configured to: store, in a map update buffer, one or more map segments including one or more logical address to be unmapped; determine, among logical address to physical address (L2P) entries of the one or more map segments stored in the map update buffer, L2P entries having the same memory block number; and selectively perform a first unmap operation or a second unmap operation according to whether all the L2P entries stored in the map update buffer have the same memory block number.

Abstract: The disclosure generally describes methods, software, and systems for performing automatic backups to the cloud. Application code in a database system updates rows and columns in the database for an updated object, and automatically performs a backup of database information to the cloud. Performing the backup includes directly executing a REST call to the cloud storage solution to which the backup of the database information is performed. Performing the backup includes: sending a request, using a REST call, to create a new object in the cloud storage solution; in response to receiving an acknowledgement of a successful creation of the new object, sending, to the cloud storage solution, REST PUT calls that include contents of the object for the cloud storage solution to store into the created new object; receiving, from the cloud storage solution, a specific key identifying the backup; and locally storing the specific key.

Abstract: A technique includes causing an agent device to setup a replication partnership between a first storage node and a second storage. Causing the agent device to setup the replication partnership includes configuring a proxy server that is associated with the second storage node to establish a secure communication channel for the replication partnership over a public network. Configuring the proxy server includes storing in the proxy server credentials for authenticating the first storage node to use the secure communication channel; and establishing port translations to be used in the secure communication channel in communicating replication data between the first storage node and the second storage node. Causing the agent device to setup the replication partnership may also include communicating replication partnership information to the second node.

Abstract: A plurality of storage drives, for managing data. includes: transmitting a first data update command which specifies a first address, and first new data to a first storage drive included in the plurality of storage drives; updating a sequence number of the first address managed in the first storage drive in response to the first data update command; transmitting a first redundant data update command which specifies a second address of old redundant data, data for updating the old redundant data, and the updated sequence number, to a second storage drive which stores the old redundant data associated with the first address and which is included in the plurality of storage drives; updating the old redundant data based on the data for updating the old redundant data; and updating a sequence number of the second address managed in the second storage drive according to the updated sequence number.

Abstract: Disclosed herein are systems and method for backing up data in a clustered environment. A clustered resource to be backed up is selected, wherein the clustered resource is stored on a common storage system and operated on by a cluster-aware application executing on two or more nodes of a computing cluster. A first backup agent executing on a first node of the computing cluster may determine a list of changes to the clustered resource and may receive at least one list of changes to the clustered resource that are tracked by peer backup agents executing on other nodes of the computing cluster. The first backup agent may merge the lists of changes to the clustered resource, and may generate a consistent incremental backup using data retrieved from the common storage system according to the merged lists of changes to the clustered resource.

Abstract: Disclosed are systems and methods of synchronization between a source and a target. The synchronization relationship can be quickly and easily be created for disaster recovery, real-time backup and failover, thereby ensuring that data on the source is fully-protected at an off-site location or on another server or VM, for example, at another data center, a different building or elsewhere in the cloud. Common snapshots available on both the source and target can act as common recovery points. The common recovery points can be used to locate the most recent snapshot in common, between the source and target, to enable a delta sync of all subsequently written data at the source to the target after an offline event.

Abstract: There is disclosed techniques for data reduction reporting in storage systems. For example in one embodiment, the techniques comprise update a counter denoting an amount of data reduction obtained when a data reduction feature associated with a data reduction requirement is enabled in the storage system when one or more allocation units in a storage system satisfy a data reduction requirement of the storage system. The techniques further comprise generating a snapshot of at least a portion of a file related to the said allocation units such that a first relationship exists when the snapshot is generated and a second relationship exists when the snapshot or the file is updated. The techniques also comprise determining a data reduction attributed to the data reduction feature based on an amount of data reduction denoted by the data reduction counter and an amount of sharing and/or unsharing of indirect blocks including mapping pointers in the relationship between the snapshot and the file.

Abstract: An information processing apparatus includes a master storage that is a nonvolatile semiconductor memory, a slave storage that is a nonvolatile semiconductor memory, a determination unit configured to determine a free storage area of the master storage, an instruction unit configured to provide an instruction to write dummy data into the area determined by the determination unit, and a control unit configured to perform one of rebuild control to rebuild the slave storage on a basis of the master storage and mirroring control on the master storage and the slave storage. The instruction unit provides an instruction to write dummy data into the free area before the control unit performs rebuild control.

Abstract: Techniques for enabling fail-safe operations of storage devices are described. A device may be configured to delete an inode in a failsafe manner. A device may be configured to mark directory entries as not in use and ensure this goes to disk before anything else. A device may be configured to create an inode in a failsafe manner. A device may be configured to allocate and initialize a cluster and ensure this is written to disk before anything else. In this manner, a volume may be in a predictable state upon a failure occurring.

Abstract: Present-day blockchain architectures suffer from several problems, including poor extensibility and scalability. This may stem from tying two parts of the consensus architecture, namely canonicality and validity, too closely together. The Polkadot architecture, which is a heterogeneous multi-chain, provides better extensibility and scalability by setting canonicality and validity apart. Compartmentalizing canonicality and validity and keeping overall functionality to a minimum of security and transport introduces practical core extensibility in situ. Scalability is addressed through a divide-and-conquer approach to canonicality and validity, scaling out of its bonded core through the incentivization of untrusted public nodes. The heterogeneity of this architecture enables many highly divergent types of consensus systems interoperating in a trustless, fully decentralized “federation,” allowing open and closed networks to have trust-free access to each other.

Abstract: Techniques for processing data may include: receiving source physical storage allocation units that include valid data and one or more holes of unused physical storage, wherein each source physical storage allocation unit has an associated timestamp denoting a most recent destaging time of any data stored on the source physical storage allocation unit; determining an age for each source physical allocation unit based on the associated timestamp of the source physical allocation unit; for each source physical storage allocation unit, determining one of multiple age buckets for the source physical allocation unit based on the age of the source physical allocation unit; and for a first of the age buckets including two source physical allocation units, performing first processing including: relocating at least some valid data from the two source physical storage allocation units to a target physical storage allocation unit.

Abstract: Policies can be applied to, and enforced for, specific resources by applying a corresponding tag to those resources. An entity, such as a customer of a resource provider, can generate one or more policies to be applied to a set of resources, where those policies can relate to data retention, backup, lifecycle events, and other such aspects. Each policy can be associated with a particular tag, which may comprise a key-value pair to be applied to various resources. A policy enforcement manager can determine the tagged resources and ensure that the relevant policies are applied. The policies can include logic or intelligence for performing a variety of tasks with respect to resources, groups of resources, or types of resources, as identified using the tags.

Abstract: A method, computer program product, and computer system for invalidating, by a target, all data in a first volume. A source may scan a hash to address table for a second volume to be migrated to the first volume. Data in the second volume may be migrated to be stored in the first volume by pushing information from the hash to address table to the target.

Abstract: Virtual machine synchronization and recovery is disclosed. At a first instance in time, a first snapshot request to generate a first snapshot of a virtual machine (VM) is received. The VM utilizes a storage unit. A first snapshot layer is generated for the storage unit. The first snapshot layer preserves a state of the storage unit at the first instance in time. A first VM record that corresponds to the first snapshot request and that includes a first VM record identifier (ID) is generated. The first VM record ID is stored in metadata associated with the first snapshot layer, and the first VM record is stored in a first location.

Abstract: Present-day blockchain architectures suffer from several problems, including poor extensibility and scalability. This may stem from tying two parts of the consensus architecture, namely canonicality and validity, too closely together. The Polkadot architecture, which is a heterogeneous multi-chain, provides better extensibility and scalability by setting canonicality and validity apart. Compartmentalizing canonicality and validity and keeping overall functionality to a minimum of security and transport introduces practical core extensibility in situ. Scalability is addressed through a divide-and-conquer approach to canonicality and validity, scaling out of its bonded core through the incentivization of untrusted public nodes. The heterogeneity of this architecture enables many highly divergent types of consensus systems interoperating in a trustless, fully decentralized “federation,” allowing open and closed networks to have trust-free access to each other.

Abstract: A capacity control module which manages a physical storage area provided by each of storage devices in a cluster by dividing the physical storage area into a physical storage area having a predetermined size, in a plurality of storage nodes configuring a storage system, and, a storage control module which receives an I/O request from a higher-level device are provided, two storage control modules, which are arranged in different storage nodes and configure a redundancy configuration, are managed as a storage control module pair, the capacity control module preferentially allocates each of the physical storage areas in the vicinity of an arrangement destination of each of the storage control modules configuring the storage control module pair, to the storage control module pair, and storage data is read from or is written on the physical storage area, according to a command applied from the storage control module.

Abstract: Examples disclosed herein provide systems, methods, and software for attaching an application to a computing system. In one example, a method of attaching at least one application to the computing system includes identifying an application attach triggering event, and identifying at least one application based on the application attach triggering event. The method further includes attaching an application volume to the computing system that contains the at least one application, and filtering one or more applications from the application volume that are not the at least one application.

Abstract: Examples include compressed extent versions. Examples may create an empty target virtual volume tree having a tree structure of a source virtual volume tree of a source storage system, the source virtual volume tree comprising source base and source snapshot virtual volumes, each representing respective versions of a plurality of extents, wherein each of the extents corresponds to a different portion of an address space of the source base virtual volume. Examples may include compressed extent collections, each comprising a compressed representation of multiple populated versions of a single extent from the source base and snapshot virtual volumes, the multiple populated versions compressed relative to one another.

Abstract: A new snapshot of a storage volume is created by instructing computing nodes to suppress write requests. An orchestration layer implements a multi-role application that is provisioned with virtualized storage and computation resources. A snapshot of the application may be created and used to rollback or clone the application. Clones snapshots of storage volumes may be thin clones. An application may use multiple orchestration approaches and objects of the multi-role application may be discovered and added to an application definition. The application definition may be used to create snapshots of the application and perform operations using the snapshots. Rolling back may include deleting objects other than PVCs, followed by rolling back storage volumes mounted to the PVCs, followed by recreating objects according to an application snapshot. PVCs created by a custom resource may be deleted along with the custom resource with the PVCs being recreated before recreating the custom resource.

Abstract: Provided is a method for correcting pinned data in a primary storage. A primary storage controller may detect a pinned data set on a primary storage. In response to detecting the pinned data set, the primary storage controller may instruct a secondary storage controller to transmit a copy of the pinned data set to the primary storage controller. The copy of the pinned data set may be stored in a secondary storage that is communicatively coupled to the secondary storage controller. The secondary storage may include a synchronous copy of the primary storage. The primary storage controller may receive the copy of the pinned data set from the secondary storage controller. The primary storage controller may also write the copy of the pinned data set over the pinned data set on the primary storage.

Abstract: Embodiments include methods, apparatus, or processors configured to access a tracking enabled storage volume associated with a container; perform a full backup of the storage volume, where performing the full backup includes defining a full backup point; perform a first incremental backup of the storage volume based on the full backup point, where performing the first incremental backup includes defining a current backup point; determine whether a backup termination condition has been met; upon determining that the backup termination condition has not been met: performing a subsequent incremental backup of the storage volume based on the current backup point; and updating the current backup point. Embodiments may restore the tracking enabled storage volume from the full backup and the incremental backups.

Abstract: A system for upgrading an application running on a virtual computing instance (VCI) can include a processing resource, a memory resource, and a VCI manager. The VCI manager can be executed by the processing resource and the memory resource and can be configured to cause a first VCI that is running the application to be copied as a second VCI, cause an updated version of the application to be installed on the second VCI, and cause a private network to be generated between the first VCI and the second VCI. The VCI manager can be further configured to cause data to be synchronized between the first VCI to the second VCI via the private network and cause the application running on the first VCI to be deactivated and cause the updated version of the application to be activated on the second VCI.

Abstract: Described herein is a multi-user retail photo kiosk system that includes multiple touch screen and Graphic User Interface (GUI) controlled consumer photo editing, photo print and product selection, and photo order placement terminals and multiple photo printers. The user photo kiosk terminals can receive images. Billing and payment is accomplished using barcoded receipts provided at the user terminal for payments for purchased photo products. A printer array incorporating various printers capable of producing prints or various sizes and formats can be configured as a horizontal counter or as a vertical tower and includes means to alert the user that their photo print order is complete. In addition, the system automatically notifies operators if equipment service, maintenance, media refilling, and/or post printing finishing procedures are required.

Abstract: There is provided a system, comprising: a hardware processor(s) executing a code for: receiving a request to identify data for execution of action(s) in a limited allocated memory resource (LAMR) of a blockchain storage system, the LAMR defining storage space for storing data of smart contracts, when the requested data is not found in the LAMR, acquiring a cryptographic proof of the requested data from the LAMR, using the cryptographic proof for acquiring a copy of the requested data from a virtual allocated memory resource (VAMR), storing the copy of the requested data in the LAMR for performing the action(s) by the blockchain storage system using the stored copy, the performance of the action(s) updates the stored copy in the LAMR, replacing the cryptographic proof with a new cryptographic proof created by processing the updated stored copy in the LAMR, and storing the updated stored copy in the VAMR.

Abstract: Techniques are provided for background deduplication using trusted fingerprints. Trusted fingerprints of blocks are inserted into a trusted fingerprint store as the blocks are being allocated by a file system sequentially according to block numbers of the blocks. In this way, the trusted fingerprint store is indexed by block numbers of where the blocks are stored. Blocks that are to be deduplicated are identifying by sorting the blocks based upon weak fingerprints, and moving duplicates to a dup file. The dup file is sorted based upon block numbers. Trusted fingerprints are loaded from the trusted fingerprint store for deduplicating the blocks within the dup file.

Abstract: Systems, methods, computer-readable media are disclosed for influencing serverless function placement across hosts within a network. A method includes receiving a notification from a network component, the notification indicating a performance bottleneck in association with one or more instances of a serverless function being executed at one or more hosts of a network; initiating at least one additional instance of the serverless function in response to the performance bottleneck; and sending a message to the network component identifying the at least one additional instance of the serverless function, the network component directing network traffic based on the message.

Abstract: A request is received to perform a point in time copy operation from a source volume to a space efficient target volume. A controller copies data stored in a group of data storage units, from the source volume to a non-volatile storage, to preserve the point in time copy operation. A background process asynchronously copies the data from the non-volatile storage to the space efficient target volume to commit a physical point in time copy of the data from the source volume to the target volume.

Abstract: Technologies are disclosed herein for identifying and resolving firmware component dependencies within a firmware project. Dependency information is generated and stored for firmware components that can be used to create a firmware project. The dependency information may define one or more mandatory dependencies, optional dependencies, and/or incompatible dependencies. The dependency information for the firmware components in the firmware project is evaluated to identify any unsatisfied dependencies when a firmware project is opened, when a firmware component is added to a firmware project, when a firmware component in a firmware project is updated, or when the firmware project is built. If any unsatisfied dependencies are identified, the dependencies can be satisfied by adding a firmware component to the firmware project, updating a firmware component in the firmware project, or by removing a firmware component from the firmware project.

Abstract: A non-volatile storage apparatus comprises a non-volatile storage and a control circuit connected to the non-volatile storage. The non-volatile storage structure is organized into multiple partitions. Each partition is preassigned to a different data shaping level. Data to be stored in the non-volatile storage is shaped based on its entropy. The control circuit is configured to write shaped data to a partition of the multiple partitions that is preassigned to a same shaping level as the shaped data.

Abstract: A request is received to perform a point in time copy operation from a source volume to a space efficient target volume. A controller copies data stored in a group of data storage units, from the source volume to a non-volatile storage, to preserve the point in time copy operation. A background process asynchronously copies the data from the non-volatile storage to the space efficient target volume to commit a physical point in time copy of the data from the source volume to the target volume.

Abstract: An apparatus comprises a host device that includes a multi-path input-output (MPIO) driver configured to control delivery of input-output (IO) operations from the host device to first and second storage systems over selected paths through a network. The MPIO driver is further configured to obtain a copy command associated with at least one of the IO operations, to identify a plurality of paths shared between source and destination logical storage devices of the copy command, to select a particular path from the identified paths, and to send the copy command to one of the first and second storage systems over the selected path. The first and second storage systems in some embodiments are arranged in an active-active configuration relative to one another. A given one of the source and destination logical storage devices may comprise a paired logical device established in accordance with the active-active configuration of the first and second storage systems.