Enhancing Data Consistency and Reliability: Introducing a New Option …

…for Snapshot Sync

Prior to this fix, when using VolSync with the copyMethod set to 'Direct', the replication
process from the source to the destination snapshot directly synchronizes with the
application PVC. However, if there is a loss of connectivity between the two clusters
during the sync process, it can lead to an inconsistent synchronization, leaving the
application PVC in an unpredictable state.

To address this issue, this commit introduces an additional option for customers to
choose from. This new option involves performing a snapshot sync from the source to
the destination cluster, syncing it to a temporary PVC. However, on the destination
cluster, a 'Direct' copy to the Application PVC is utilized. This approach improves
the speed and reliability of the snapshot sync process at the expense of additional
storage usage.

It is important to note that this approach requires three times the storage compared
to the current method, which may not be suitable for all customers.

Signed-off-by: Benamar Mekhissi <bmekhiss@redhat.com>

controllers/drplacementcontrol_controller_test.go

@@ -1081,7 +1081,7 @@ func ensureDRPolicyIsDeleted(drpolicyName string) {
 				drpolicyName,
 			),
 		),
-		"DRPolicy %s not not found\n%s",
+		"DRPolicy %s not found\n%s",
 		drpolicyName,
 		format.Object(*drpolicy, 0),
 	)