Keep the original PR #228 report at a fixed commit link with contributor credit. Direct operators to the bilingual migration guide and its recovery requirements, and record the merged contribution. Signed-off-by: Feng Ruohang <rh@vonng.com>
1.3 KiB
Single-node migration from MinIO to SILO
The maintained migration procedure and single-node case study belong to the companion documentation site:
Follow the guide's deployment checks, consistent backup procedure, verification steps and rollback requirements. Modern single-node/single-drive erasure deployments are distinct from the retired filesystem backend; historical FS installations need the filesystem migration procedure.
Paris Y. (@yupoet) contributed the production report in #228, describing a 2026-09-26 forward upgrade to SILO 20260916. The original report is retained as historical evidence. Its FS terminology and unconditional metadata, healthcheck, multipart-listing and rollback claims are superseded by the maintained guide. The report is not independent verification of a newer release, a complete historical-object audit, or a reverse downgrade.