Replication Operations on SILO

Site Replication Overview

Mon, 01 Jan 0001 00:00:00 +0000

SILO upgrade requirements: the September IAM repairs require a coordinated upgrade of all participating nodes and a backup containing deletion history. Read IAM Upgrade and Recovery and Audit Historical Replica State, and use the component matrix to distinguish main from published artifacts.

Site replication configures multiple independent MinIO deployments as a cluster of replicas called peer sites.

A site replication deployment with two peer sites. A load balancer manages routing operations to either of the two sites. Data written to one site automatically replicates to the other peer site.

Site replication assumes the use of either the included MinIO identity provider (IDP) or an external IDP. All configured deployments must use the same IDP. Deployments using an external IDP must use the same configuration across sites.

IAM Upgrade and Recovery

Mon, 01 Jan 0001 00:00:00 +0000

The IAM repairs in Server #191 and #192 persist deletion revisions and parent revocation boundaries. They prevent delayed site events from restoring revoked identities and older grants. They require a coordinated upgrade of all participating servers, including nodes without site replication that share an IAM backend. Mixed old/new nodes on that backend and rolling downgrade are unsupported.

Release status: these repairs are in the September source baseline, not Server 20260903. This procedure is preparation for a build containing those repairs. Isolated upgrade/restore observations and remaining recovery checks are tracked in #200; see the validation scope. Publication of this page does not establish production upgrade acceptance.

Audit Historical Replica State

Mon, 01 Jan 0001 00:00:00 +0000

Upgrading to the September replication repairs prevents new errors. It does not rewrite old Content-Encoding, reconstruct lost tags or establish that historical delete-marker purge work has converged. #201 tracks inventory and recovery readiness. No affected production installation has been identified by this review.

Read-only version inventory

Start with stored aws-chunked Content-Encoding, the transport token addressed by #194. Inventory all versions on the authoritative site and replicas. Checking only current objects misses historical versions; a normal COPY can preserve polluted source metadata.