Abstract: Techniques are presented for implementing non-host-based migration in a manner that is not subject to certain types of data corruption. This may be accomplished by preventing any hosts from having write access to a target LUN until it can be confirmed that all applications that access a source LUN have been shut down. This arrangement prevents accidentally writing to the target LUN while the source LUN is still being accessed. As a further precaution, just in case the confirmations are incorrect, a target data storage system can direct a source data storage system to remove access to the source LUN from all of the hosts, which has a similar effect. The migration can then proceed.

Abstract: Techniques are presented for implementing non-host-based migration in a manner that is not subject to certain types of data corruption. This may be accomplished by preventing any hosts from having write access to a target LUN until it can be confirmed that all applications that access a source LUN have been shut down. This arrangement prevents accidentally writing to the target LUN while the source LUN is still being accessed. As a further precaution, just in case the confirmations are incorrect, a target data storage system can direct a source data storage system to remove access to the source LUN from all of the hosts, which has a similar effect. The migration can then proceed.

Abstract: A data management method and system for migrating a data volume from a source array to a destination array includes receiving an indication of a source volume to migrate from the source array to the destination array wherein the source volume comprises a clustered volume associated with a plurality of cluster hosts. A path-flip is performed by the host multipath module, to switch the paths between source and destination array. This switch is done in a seamless manner, without disrupting host I/O. The path-flip includes transferring associated metadata from source to destination and can be performed even in clustered and/or multi-host environments. Sanity timers are built-in to ensure that the path-flip completes within a stipulated time-frame and, if not, the path-flip process is aborted and I/O is resumed without any disruption.

Abstract: A method may include establishing, by a MPIO driver of a host information handling system, an I/O path between the host information handling system and the source storage array as an active I/O path and a path between the host and the target storage array as a passive I/O path. The method may also include performing a snapshot-based iterative replication between the source storage array and the target storage array, wherein successive iterations of the snapshot-based iterative replication comprise I/O to the source storage array occurring during an immediately previous iteration of the snapshot-based iterative replication. The method may further include, upon completion of the snapshot-based iterative replication, establishing, by the MPIO, the I/O path between the host and the source storage array as a passive I/O path and the path between the host and the target storage array as the active I/O path.

Abstract: A method and system perform a background copy of a source volume to a migration volume. The source volume has an asynchronous replication relationship with a disaster recovery (DR) volume. A migration volume snapshot may be obtained and host I/O to the source volume may be disabled. A post-copy replication of the source volume is performed to synchronize the source volume and the DR volume. A replication snapshot, comprising a snapshot of the DR volume, is obtained and an identifier of the replication snapshot is modified in accordance with an identifier of the migration snapshot. For example, the identifier of the migration snapshot may be copied to the replication snapshot. Thereafter, an existing replication relationship between the source volume and the DR volume may be disabled and a post-migration replication relationship between the migration volume and the DR volume established such that subsequent replication are incremental or delta replications.

Abstract: A data management method and system for migrating a data volume from a source array to a destination array includes receiving an indication of a source volume to migrate from the source array to the destination array wherein the source volume comprises a clustered volume associated with a plurality of cluster hosts. A path-flip is performed by the host multipath module, to switch the paths between source and destination array. This switch is done in a seamless manner, without disrupting host I/O. The path-flip includes transferring associated metadata from source to destination and can be performed even in clustered and/or multi-host environments. Sanity timers are built-in to ensure that the path-flip completes within a stipulated time-frame and, if not, the path-flip process is aborted and I/O is resumed without any disruption.

Abstract: A method may include establishing, by a MPIO driver of a host information handling system, an I/O path between the host information handling system and the source storage array as an active I/O path and a path between the host and the target storage array as a passive I/O path. The method may also include performing a snapshot-based iterative replication between the source storage array and the target storage array, wherein successive iterations of the snapshot-based iterative replication comprise I/O to the source storage array occurring during an immediately previous iteration of the snapshot-based iterative replication. The method may further include, upon completion of the snapshot-based iterative replication, establishing, by the MPIO, the I/O path between the host and the source storage array as a passive I/O path and the path between the host and the target storage array as the active I/O path.