Update VolSync backup configuration to Direct copy method

[ldpliu]

Summary

• Update VolSync backup configuration copyMethod from Snapshot to Direct
• Aligns with recommended disaster recovery backup practices

Changes

Documentation (doc/simulation/backup_restore/backup/)

• Change copyMethod: Snapshot to copyMethod: Direct in volsync-config.yaml

Test plan

• Verify backup/restore simulation documentation is accurate
• Test disaster recovery scenarios with Direct copy method
• Ensure configuration aligns with VolSync best practices

Related Issues

Related to: open-cluster-management-io/policy-collection#544

🤖 Generated with Claude Code

Signed-off-by: daliu@redhat.com

Summary by CodeRabbit

• Chores
  • Updated backup configuration settings to change the copy mechanism used for backup operations.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ldpliu
Once this PR has been reviewed and has the lgtm label, please assign clyang82 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 210c78da-59e9-48f0-8ef6-3cd4d9a20cb5

📥 Commits

Reviewing files that changed from the base of the PR and between dbf6081 and e5183f6.

📒 Files selected for processing (1)

• doc/simulation/backup_restore/backup/volsync-config.yaml

---

📝 Walkthrough

Walkthrough

A YAML configuration file for volsync backup was updated to change the backup copy method from Snapshot to Direct in a ConfigMap definition. All other configuration settings remain unchanged.

Changes

Cohort / File(s)	Summary
Configuration Update doc/simulation/backup_restore/backup/volsync-config.yaml	Modified copyMethod field from Snapshot to Direct in the volsync ConfigMap data.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A carrot's backup method shifts today,
From snapshots fast to direct's gentle way,
The config sings a simpler song,
With volumes flowing smooth and strong! 📦✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating VolSync backup configuration to use Direct copy method instead of Snapshot.
Description check	✅ Passed	The description provides a clear summary, explains the change rationale, documents affected files, and includes a test plan, though it lacks the template emoji/icon prefix and checkbox structure.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ldpliu]

/hold need to wait open-cluster-management-io/policy-collection#544 merged

[ldpliu]

Related Jira Issues:

• https://redhat.atlassian.net/browse/ACM-32308