Abstract: A disaster recovery site storage array causes an instance of a host application or selected executables running on a host server to validate changes to an asynchronously updated replica of a storage object. Snapshots of the replica are generated before and after each set of changes to the replica are received from a remote storage array. Validation is performed by mounting snapshots to the instance of the associated host application and causing the host application instance to validate the data. If a snapshot is determined to be invalid, then the replica to recovered with the most recent known-valid snapshot. Alternatively, if each set of changes is validated prior to being applied to the replica, invalid changes are not applied to the replica. Unvalidated snapshots may be accumulated and validated independently from application of sets of changes to the replica, thereby decoupling validation from replication.

Abstract: An apparatus comprises at least one processing device comprising a processor coupled to a memory. The at least one processing device is configured to initiate generation of a remote backup copy for a consistency group subject to replication from a first storage system to a second storage system, and responsive to receipt of a freeze indication from at least one application that utilizes the consistency group in the first storage system, to direct the first storage system to enter a write hold state. The at least one processing device is further configured to direct the second storage system to generate the remote backup copy from the consistency group as currently replicated from the first storage system to the second storage system, and responsive to receipt of a copy complete indication from the second storage system, to direct the first storage system to exit the write hold state.

Abstract: Snapshots are created on replicated storage systems R1 and R2 in a manner resulting in identical snapshots being generated on R1 and R2. In response to an instruction to create a snapshot on a storage system (R1 and/or R2), command-phase write operations (CWOs) are held and data-phase write operations (DWOs) are completed on the storage system before the snapshot is created. Determining that DWOs includes querying processes, and using information, available on the storage system, by which a state of a write operation—e.g., whether the write operation is a DWO and when the DWO completes—may be determined. A CWO queue may be maintained on the storage system for tracking the status of CWOs. A DWO queue may be maintained on the storage system for tracking DWOs, to determine DWOs when the snapshot is created, and track their processing, including when they are completed.

Abstract: Memory of a storage system is made available (i.e., exposed) for use as host memory of a host, for example, as an extension of the main memory of the host. The host may be directly connected to an internal fabric of the data storage system. Portions of the storage system memory (SSM) may be allocated for use as host memory, and this may be communicated to the host system. The host OS and applications executing thereon then may make use of the SSM as if it were memory of the host system, for example, as second-tier persistent memory. The amount of SSM made available may be dynamically increased and decreased. The SSM may be accessed by the host system as memory; i.e., in accordance with memory-based instructions, for example, using remote direct memory access instructions. The SSM may be write protected using mirroring, vaulting and other techniques.

Abstract: An apparatus comprises at least one processing device comprising a processor coupled to a memory. The at least one processing device is configured to initiate generation of a remote backup copy for a consistency group subject to replication from a first storage system to a second storage system, and responsive to receipt of a freeze indication from at least one application that utilizes the consistency group in the first storage system, to direct the first storage system to enter a write hold state. The at least one processing device is further configured to direct the second storage system to generate the remote backup copy from the consistency group as currently replicated from the first storage system to the second storage system, and responsive to receipt of a copy complete indication from the second storage system, to direct the first storage system to exit the write hold state.

Abstract: Snapshots are created on replicated storage systems R1 and R2 in a manner resulting in identical snapshots being generated on R1 and R2. In response to an instruction to create a snapshot on a storage system (R1 and/or R2), command-phase write operations (CWOs) are held and data-phase write operations (DWOs) are completed on the storage system before the snapshot is created. Determining that DWOs includes querying processes, and using information, available on the storage system, by which a state of a write operation—e.g., whether the write operation is a DWO and when the DWO completes—may be determined. A CWO queue may be maintained on the storage system for tracking the status of CWOs. A DWO queue may be maintained on the storage system for tracking DWOs, to determine DWOs when the snapshot is created, and track their processing, including when they are completed.

Abstract: Memory of a storage system is made available (i.e., exposed) for use as host memory of a host, for example, as an extension of the main memory of the host. The host may be directly connected to an internal fabric of the data storage system. Portions of the storage system memory (SSM) may be allocated for use as host memory, and this may be communicated to the host system. The host OS and applications executing thereon then may make use of the SSM as if it were memory of the host system, for example, as second-tier persistent memory. The amount of SSM made available may be dynamically increased and decreased. The SSM may be accessed by the host system as memory; i.e., in accordance with memory-based instructions, for example, using remote direct memory access instructions. The SSM may be write protected using mirroring, vaulting and other techniques.

Abstract: A system identifies a storage device that stores a computer cluster's database and a storage device that stores the computer cluster's transaction logs. The system creates a snapshot of the storage device that stores the database and/or a snapshot of the storage device that stores the transaction logs. The system mounts at least one snapshot on any host that is accessible to the data management system's native interface. The system enables the native interface to catalog a database recovery name created for the database snapshot and/or a transaction log recovery name created for the transaction logs snapshot. The system enables recovery of the database and/or the transaction logs by storing a mapping from the database recovery name to a database backup identifier created for the database snapshot and/or a mapping from the transaction log recovery name to a transaction log backup identifier created for the transaction logs snapshot.

Abstract: Techniques for processing I/O operations may include: receiving, an I/O operation including a tag value denoting a process of a database application that issued the I/O operation; determining, in accordance with the tag value, whether the I/O operation is directed to a data file storing content of a database or a log file of recorded operations of the database; and responsive to determining the I/O operation is directed to a data file storing content of the database, performing processing including: determining a current configuration setting of the database that indicates whether the database is configured for use with the database application as an in-memory database; and determining, in accordance with current configuration setting of the database, a first service level objective for the I/O operation, wherein the first service level objective for the I/O operation is a default service level objective or a revised service level objective.

Abstract: A storage system in one embodiment comprises at least one storage array comprising a plurality of storage devices. The storage array is configured to communicate over one or more networks with a plurality of host devices. The storage array is further configured to receive one or more commands from a given one of the host devices directing that a particular user-defined name be assigned to a particular one of the storage devices, and responsive to receipt of the one or more commands, to determine if any other user-defined name is already assigned to the particular storage device, and if there is no other user-defined name already assigned to the particular storage device, to assign the particular user-defined name to the particular storage device and to store information characterizing the assignment of the particular user-defined name to the particular storage device in persistent memory of the storage array.

Abstract: A storage system in one embodiment comprises at least one storage array comprising a plurality of storage devices. The storage array is configured to communicate over one or more networks with a plurality of host devices. The storage array is further configured to receive one or more commands from a given one of the host devices directing that a particular user-defined name be assigned to a particular one of the storage devices, and responsive to receipt of the one or more commands, to determine if any other user-defined name is already assigned to the particular storage device, and if there is no other user-defined name already assigned to the particular storage device, to assign the particular user-defined name to the particular storage device and to store information characterizing the assignment of the particular user-defined name to the particular storage device in persistent memory of the storage array.

Abstract: One example method includes receiving an IO associated with a process initiated by an application, where the IO is identified by a tag that corresponds to the process. The method further includes saving the tag on a device that is an element of a storage group (SG) that is specific to the application, and correlating the tag with a data protection process that is associated with the application. When a request is received to perform an SG protection process, the SG protection process is performed on the tagged device.

Abstract: A storage system in one embodiment comprises at least one storage array comprising a plurality of storage devices. The storage array is configured to communicate over one or more networks with a plurality of host devices. The storage array is further configured to receive one or more commands from a given one of the host devices directing that a particular user-defined name be assigned to a particular one of the storage devices, and responsive to receipt of the one or more commands, to determine if any other user-defined name is already assigned to the particular storage device, and if there is no other user-defined name already assigned to the particular storage device, to assign the particular user-defined name to the particular storage device and to store information characterizing the assignment of the particular user-defined name to the particular storage device in persistent memory of the storage array.

Abstract: One example method includes receiving an IO associated with a process initiated by an application, where the IO is identified by a tag that corresponds to the process. The method further includes saving the tag on a device that is an element of a storage group (SG) that is specific to the application, and correlating the tag with a data protection process that is associated with the application. When a request is received to perform an SG protection process, the SG protection process is performed on the tagged device.

Abstract: Techniques for processing I/O operations may include: receiving, an I/O operation including a tag value denoting a process of a database application that issued the I/O operation; determining, in accordance with the tag value, whether the I/O operation is directed to a data file storing content of a database or a log file of recorded operations of the database; and responsive to determining the I/O operation is directed to a data file storing content of the database, performing processing including: determining a current configuration setting of the database that indicates whether the database is configured for use with the database application as an in-memory database; and determining, in accordance with current configuration setting of the database, a first service level objective for the I/O operation, wherein the first service level objective for the I/O operation is a default service level objective or a revised service level objective.

Abstract: In one aspect, a method includes receiving a read or write command from a requester to read data from or write data to a database, inserting in a status message on a status of the read or write command an identifier to identify technology of storage for the data and providing the status message associated with the read or write command to the requester.

Abstract: A method, computer program product, and computing system for defining a storage space having a defined capacity within a storage system. The storage system includes a frontend system and a backend system. A first portion of the storage space is located within the frontend system. A second portion of the storage space is located within the backend system. Usage of a data item stored within the storage space is monitored to identify a usage pattern. The data item is migrated to either the first portion of the storage space or the second portion of the storage space based, at least in part, upon the usage pattern.

Abstract: An apparatus comprises a profiled data object service manager configured to generate at least one profiled data object service instantiation responsive to an invocation by a profiled data object service user. The profiled data object service manager comprises a profiled data object service reasoner configured to parse the user invocation, to map the parsed user invocation to one or more relevant profiled data objects using profiles of respective profiled data objects and relationships among multiple profiled data objects, to select one or more services to be instantiated based on the relevant profiled data objects, and to generate one or more instantiable service invocations for the one or more selected services. Additional functionality of the profiled data object service manager may comprise one or more of policy enforcement, service instantiation and service orchestration. The service manager is implemented using at least one processing device comprising a processor coupled to a memory.

Abstract: A method, system and program product for enabling migration of Virtual Machines with concurrent access to data across two geographically disperse sites to enable load balancing across the two geographically disperse sites, by presenting over a network a read writable logical volume at a first site, presenting over a network a read writable logical volume at a second geographically disparate site; wherein the first volume and the second volume are configured to contain the same information, and enabling read write access to the volume at the first site or the volume at the second site for a first virtual machine while keeping the data consistent between the two sites to enable transparent migration of the virtual machine to load balancing across the two sites according to at least one load balancing metric.

Abstract: In one aspect, a method includes receiving a read or write command from a requester to read data from or write data to a database, inserting in a status message on a status of the read or write command an identifier to identify technology of storage for the data and providing the status message associated with the read or write command to the requester.