Back to bug 2144180

Who When What Removed Added
Pratik Surve 2022-11-19 17:07:10 UTC Severity unspecified urgent
Benamar Mekhissi 2022-11-21 13:46:33 UTC Status NEW ASSIGNED
Mudit Agarwal 2022-11-22 07:44:20 UTC CC bmekhiss
Flags needinfo?(bmekhiss)
Mudit Agarwal 2022-11-29 13:35:15 UTC Flags needinfo?(bmekhiss)
krishnaram Karthick 2022-11-30 04:47:44 UTC CC kramdoss
RHEL Program Management 2022-11-30 04:47:53 UTC Target Release --- ODF 4.12.0
OpenShift BugZilla Robot 2022-12-04 17:55:18 UTC Status ASSIGNED POST
OpenShift BugZilla Robot 2022-12-04 17:55:19 UTC Link ID Github red-hat-storage/ramen/pull/85
OpenShift BugZilla Robot 2022-12-05 14:00:46 UTC Status POST MODIFIED
Shyamsundar 2022-12-05 14:03:52 UTC CC srangana
Mudit Agarwal 2022-12-06 13:56:45 UTC Fixed In Version 4.12.0-128
Status MODIFIED ON_QA
Sunil Kumar Acharya 2022-12-08 12:52:38 UTC Flags needinfo?(bmekhiss)
krishnaram Karthick 2022-12-14 16:11:56 UTC Status ON_QA ASSIGNED
OpenShift BugZilla Robot 2022-12-15 01:50:32 UTC Status ASSIGNED POST
OpenShift BugZilla Robot 2022-12-15 01:50:34 UTC Link ID Github red-hat-storage/ramen/pull/87
OpenShift BugZilla Robot 2022-12-15 02:04:31 UTC Status POST MODIFIED
Mudit Agarwal 2022-12-16 05:08:38 UTC Flags needinfo?(bmekhiss)
Link ID Github RamenDR/ramen/pull/670
Red Hat Bugzilla 2022-12-16 05:08:38 UTC Doc Type If docs needed, set a value No Doc Update
Shyamsundar 2022-12-16 13:15:31 UTC Status MODIFIED ON_QA
Fixed In Version 4.12.0-128 4.12.0-143
Red Hat Bugzilla 2022-12-31 19:22:33 UTC QA Contact prsurve kramdoss
Red Hat Bugzilla 2023-01-01 05:47:46 UTC CC srangana
Red Hat Bugzilla 2023-01-01 08:30:04 UTC CC bmekhiss
Assignee bmekhiss nobody
Red Hat Bugzilla 2023-01-01 08:32:32 UTC CC kramdoss
QA Contact kramdoss
Pratik Surve 2023-01-02 12:05:11 UTC Assignee nobody prsurve
Pratik Surve 2023-01-02 12:13:29 UTC Assignee prsurve nobody
QA Contact prsurve
Alasdair Kergon 2023-01-04 04:38:31 UTC Assignee nobody bmekhiss
Alasdair Kergon 2023-01-04 04:48:40 UTC CC bmekhiss
Alasdair Kergon 2023-01-04 05:07:00 UTC CC kramdoss
Alasdair Kergon 2023-01-04 05:46:39 UTC CC srangana
Pratik Surve 2023-01-18 06:52:24 UTC Status ON_QA VERIFIED
Benamar Mekhissi 2023-01-25 16:03:40 UTC Doc Text When we perform a failover or relocation, Ramen creates a writable copy of the application PVC. However, if the PVC contains a large number of files, it can take a long time for CephFS to create the copy from a snapshot. To address this issue, we have introduced a setting that allows the source to synchronize directly to the application PVC at the destination. Additionally, the destination will save a snapshot after the last successful synchronization as a backup in case the application PVC becomes corrupted.

To use Direct copy method, add the following entry to the Ramen ConfigMap
```
data:
ramen_manager_config.yaml: |
...
volsync:
destinationCopyMethod: Direct
```
Doc Type No Doc Update Known Issue
Red Hat Bugzilla 2023-01-31 23:39:08 UTC CC madam
Rejy M Cyriac 2023-02-08 14:06:28 UTC Resolution --- CURRENTRELEASE
Status VERIFIED CLOSED
Last Closed 2023-02-08 14:06:28 UTC
krishnaram Karthick 2023-02-23 06:52:17 UTC CC rcyriac
krishnaram Karthick 2023-02-23 06:52:50 UTC CC rcyriac
Elad 2023-08-09 17:00:43 UTC CC odf-bz-bot

Back to bug 2144180