Mapping equivalent hosts at distinct replication endpoints

Patent metadata

Field	Value
Publication number	US-12517873-B2
Application number	US-202016829956-A
Country	US
Kind code	B2
Filing date	Mar 25, 2020
Priority date	Mar 25, 2020
Publication date	Jan 6, 2026
Grant date	Jan 6, 2026

Abstract

A method of mapping equivalent hosts at distinct replication endpoints, the method including: receiving an indication that a first host mapped to a source dataset at a replication source is equivalent to a second host for a replica dataset at a replication target of the source dataset; transmitting, from the replication source to the replication target and based on an update to the source dataset received from the first host, metadata describing the update to the source dataset; and mapping, based on the indication that the first host mapped to the source dataset at the replication source is equivalent to the second host for the replica dataset at the replication target, the second host to the replica dataset at the replication target of the source dataset.

First claim

What is claimed is:

1 . A method comprising:
receiving an indication that, for a first host computing device that issues I/O operations directed to a source dataset and is mapped to the source dataset at a replication source, there is a second host computing device that is equivalent to the first host computing device, wherein the second host computing device can issue I/O operations directed to a replica dataset that is at a replication target and a replica of the source dataset; and automatically mapping, based on the indication that the second host computing device is equivalent to the first host computing device, the second host computing device to the replica dataset at the replication target.

2 . The method of claim 1 , wherein the first host computing device is one of multiple host systems mapped to the source dataset, and wherein mapping the second host computing device to the replica dataset includes mapping, for each of the multiple host systems mapped to the source dataset, a respective equivalent host system to the replica dataset on the replication target.

3 . The method of claim 1 , wherein the replication source is a storage system configured for continuous data protection of the source dataset, and wherein the replication target is a storage system.

4 . The method of claim 1 , wherein mapping the second host computing device to the replica dataset is performed responsive to creating the replica dataset on the replication target.

5 . The method of claim 1 , wherein a replica link specifies a replication policy between the replication source for the source dataset and a replication target for the replica dataset of the source dataset, and wherein the replica link further specifies one or more of: the dataset to replicate, a checkpoint policy, a metadata representation for the dataset, a metadata log, a metadata journal, or a continuous data replication policy.

6 . The method of claim 1 , wherein the dataset is included within a pod that includes a protection group, and wherein the protection group is replicated at the replication target as part of synchronizing the pod between the replication source and the replication target.

7 . The method of claim 6 , wherein the protection group applies to one or more volumes or datasets.

8 . The method of claim 6 , wherein the protection group is specified to apply to any volumes or datasets that are connected to the first host computing device mapped to the source dataset.

9 . The method of claim 6 , wherein the pod is synchronously replicated.

10 . The method of claim 6 , wherein the pod is asynchronously replicated.

11 . An apparatus comprising a computer processor, a computer memory operatively coupled to the computer processor, the computer memory having disposed within it computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the steps of:
receiving an indication that, for a first host computing device that issues I/O operations directed to a source dataset and is mapped to the source dataset at a replication source, there is a second host computing device that is equivalent to the first host computing device, wherein the second host computing device can issue I/O operations directed to a replica dataset that is at a replication target and a replica of the source dataset; and automatically mapping, based on the indication that the second host computing device is equivalent to the first host computing device, the second host computing device to the replica dataset at the replication target.

12 . The apparatus of claim 11 , wherein the first host computing device is one of multiple host systems mapped to the source dataset, and wherein mapping the second host computing device to the replica dataset includes mapping, for each of the multiple host systems mapped to the source dataset, a respective equivalent host system to the replica dataset on the replication target.

13 . The apparatus of claim 11 , wherein the replication source is a storage system configured for continuous data protection of the source dataset, and wherein the replication target is a storage system.

14 . The apparatus of claim 11 , wherein mapping the second host computing device to the replica dataset is performed responsive to creating the replica dataset on the replication target.

15 . The apparatus of claim 11 , wherein a replica link specifies a replication policy between the replication source for the source dataset and a replication target for the replica dataset of the source dataset, and wherein the replica link further specifies one or more of: the dataset to replicate, a checkpoint policy, a metadata representation for the dataset, a metadata log, a metadata journal, or a continuous data replication policy.

16 . The apparatus of claim 11 , wherein the dataset is included within a pod that includes a protection group, and wherein the protection group is replicated at the replication target as part of synchronizing the pod between the replication source and the replication target.

17 . The apparatus of claim 16 , wherein the protection group applies to one or more volumes or datasets.

18 . The apparatus of claim 16 , wherein the protection group is specified to apply to any volumes or datasets that are connected to the first host computing device mapped to the source dataset.

19 . The apparatus of claim 16 , wherein the pod is synchronously replicated.

20 . The apparatus of claim 16 , wherein the pod is asynchronously replicated.

Assignees

• Pure Storage Inc

Inventors

• Grunwald David
• Gill Thomas
• Brooks Connor
• Shukla Saurabh
• Touchette Larry
• Driscoll Alan

Classifications

• G06F16/1734

  Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs · CPC title

• G06F16/273

  Asynchronous replication or reconciliation · CPC title

• G06F16/164

  File meta data generation · CPC title

• G06F16/275

  Synchronous replication · CPC title

• G06F16/1824

  implemented using Network-attached Storage [NAS] architecture (distributed or networked storage systems G06F3/067; protocols for distributed storage of data in a network H04L67/1097) · CPC title