SeaweedFS doesn't seem production ready

### Self-Hosted Version

25.10

### CPU Architecture

x86_64

### Docker Version

not relevant

### Docker Compose Version

not relevant

### Machine Specification

- [x] My system meets the minimum system requirements of Sentry

### Steps to Reproduce

The seaweedfs docs do not include a full backup/restore strategy: https://github.com/seaweedfs/seaweedfs/wiki/Data-Backup

The existing solution requires downtime

> This example requires your entire cluster to pause(stop receiving writes) while the volumes are being backed up/transferred

### Expected Result

Stable local S3 provider

### Actual Result

Unstable local S3 provider

### Event ID

_No response_

Start with the SeaweedFS Data-Backup wiki page linked in the report and compare its stated downtime requirement with the self-hosted deployment. Done would require a documented backup/restore strategy that avoids downtime and establishes a stable local S3 provider; the issue does not name repository files or tests.

Written by the indexing model from the issue text.