From 870528844f2841ee41c474ae93a41fda6cabcabc Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Mon, 13 Nov 2023 18:35:39 +0200 Subject: [PATCH] OADP 1.3 DataMover restore hook issue --- .../installing/data-mover-intro.adoc | 1 + snippets/snip-post-mig-hook | 10 ++++++++++ 2 files changed, 11 insertions(+) create mode 100644 snippets/snip-post-mig-hook diff --git a/backup_and_restore/application_backup_and_restore/installing/data-mover-intro.adoc b/backup_and_restore/application_backup_and_restore/installing/data-mover-intro.adoc index 18a0ef6c7d..ae9d2fd428 100644 --- a/backup_and_restore/application_backup_and_restore/installing/data-mover-intro.adoc +++ b/backup_and_restore/application_backup_and_restore/installing/data-mover-intro.adoc @@ -23,6 +23,7 @@ include::snippets/technology-preview.adoc[leveloffset=+1] * You must perform a data cleanup after you perform a backup, if you are using OADP 1.1 Data Mover. See xref:../../../backup_and_restore/application_backup_and_restore/installing/oadp-cleaning-up-after-data-mover-1-1-backup-doc.adoc#oadp-cleaning-up-after-data-mover-1-1-backup-doc[Cleaning up after a backup using OADP 1.1 Data Mover]. +include::snippets/snip-post-mig-hook[] [id="oadp-data-mover-prerequisites"] == OADP Data Mover prerequisites diff --git a/snippets/snip-post-mig-hook b/snippets/snip-post-mig-hook new file mode 100644 index 0000000000..ffeed3e10f --- /dev/null +++ b/snippets/snip-post-mig-hook @@ -0,0 +1,10 @@ +:_content-type: SNIPPET + +[NOTE] +==== +Post-migration hooks are not likely to work well with the OADP 1.3 Data Mover. + +The OADP 1.1 and OADP 1.2 Data Movers use synchronous processes to back up and restore application data. Because the processes are synchronous, users can be sure that any post-restore hooks start only after the persistent volumes (PVs) of the related pods are released by the persistent volume claim (PVC) of the Data Mover. + +However, the OADP 1.3 Data Mover uses an asynchronous process. As a result of this difference in sequencing, a post-restore hook might be called before the related PVs were released by the PVC of the Data Mover. If this happens, the pod remains in `Pending` status and cannot run the hook. The hook attempt might time out before the pod is released, leading to a `PartiallyFailed` restore operation. +==== \ No newline at end of file