[PBM-1143] Add support for WebDAV backups

[dalbani]

https://jira.percona.com/browse/PBM-1143

[dalbani]

What's missing to this PR is maybe an integration test? Maybe it's not obvious to me how to do that.

[defbin]

try to add it here

percona-backup-mongodb/e2e-tests/cmd/pbm-test/run.go

Lines 28 to 31 in 86d5528

	{"AWS", "/etc/pbm/aws.yaml"},
	{"GCS", "/etc/pbm/gcs.yaml"},
	{"Azure", "/etc/pbm/azure.yaml"},
	{"FS", "/etc/pbm/fs.yaml"},

[dalbani]

OK, then I need to fire up a WebDAV server, as I can't rely on a external service like S3 or Azure.

[defbin]

to run the test:
env MONGODB_VERSION=6.0 TESTS_BCP_TYPE=logical e2e-tests/run-all

on Apple Silicon you can try:
env MONGODB_VERSION=6.0.6-arm64 TESTS_BCP_TYPE=logical e2e-tests/run-all

[dalbani]

Although it's all green, I am not sure if what I pushed actually run the E2E test for WebDAV 🤨

Speaking of E2E setup, I'm wondering if this choice of path-ignores is correct:

percona-backup-mongodb/.github/workflows/ci.yml

Line 22 in 4ed2332

paths-ignore:

In the sense that:

When all the path names match patterns in paths-ignore, the workflow will not run. If any path names do not match patterns in paths-ignore, even if some path names match the patterns, the workflow will run.

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-excluding-paths

For example, I only committed to e2e-tests/pkg/tests/sharded/cluster.go in 96b095e, and, yet, CI ran.

[ImTheKai]

Hi @dalbani,

just for me to better understand the use-case of WebDAV in 2023. In which scenario and where do you actually need WebDAV? Can you elaborate a little more on your needs?

Thanks,
Kai

[dalbani]

Well, even though it's 2023, WebDAV is very much "alive".
I can name for example two storage providers which offer WebDAV-backed repositories — and no S3 compatible endpoint:

• Hetzner Storage Box
• Microsoft OneDrive — yep, it's technically possible to connect via WebDAV, you can look it up 😃

And there are other (open source) implementations of WebDAV servers available for self-hosted deployments.

[ImTheKai]

Hey,

we've investigated and surveyed our current customer base, and there isn't genuine interest in WebDAV. Given that we need to maintain the code for a very long time, given support and SLAs, we don't consider adding it to the project.

So I'll close this PR, so you don't wait any longer on a decision that might never happen. Nevertheless thanks a lot for the contribution.

[dalbani]

Thanks for your feedback.
In the end, I've come to the conclusion that logical backups are not suited to my use case.
Due to the size of my database, the generated backup files were like 200+ GB (!), even with the best compression.
So I need to have a look at physical backups, is my understanding.