Skip to content

Troubleshoot bucket replication#

If MinIO bucket replication is not working as expected, follow these steps to identify and resolve the issue.

  1. Verify the replication status:

    mc replicate status <source alias>/<bucket name> --insecure

    Example output:

    $ mc replicate status source-alias/source-1 --insecure
  Replication status since 15 minutes
  Summary:
  Replicated:                   0 objects (0 B)
  Queued:                       ● 0 objects, 0 B (avg: 0 objects, 0 B ; max: 0 objects, 0 B)
  Workers:                      0 (avg: 0; max: 0)
  Received:                     0 objects (0 B)
  Transfer Rate:                0 B/s (avg: 0 B/s; max: 0 B/s)
  Errors:                       0 in last 1 minute; 0 in last 1hr; 0 since uptime

    Check for the following indicators:

    • Replicated objects count is increasing.
    • No errors are reported.
    • Workers are active during replication.

    If all values remain at 0, replication may not be configured correctly.

  2. Resolve TLS certificate verification errors.

    Example error:

    $ mc replicate add source-alias/source   --remote-bucket "https://<MinIO accessKey>:<MinIO secretKey>:<MinIO instance API URL>/destination"   --replicate "delete,delete-marker,existing-objects" --insecure
mc: <ERROR> unable to configure remote target. Remote service connection error (Remote service endpoint offline, target bucket: destination or remote service credentials: minio invalid
        Get "https://<MinIO instance API URL>/destination/?location=": tls: failed to verify certificate: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "*.cloudapp.azure.com")).

    This error indicates that the TLS certificate presented by the remote MinIO instance is not trusted by the client.

    Example resolutions:

    • Verify that the TLS certificate includes the correct Subject Alternative Names (SAN) for both MinIO endpoints.
    • Ensure the certificate is trusted by both MinIO deployments.
    • Confirm that the same certificate (or trusted CA) is used on both clusters.
    • Verify that MinIO is configured to use the custom TLS secret.

  3. Restart MinIO services if replication is unresponsive or configuration changes are not applied:

    $ mc admin service restart <destination alias> --insecure

    Example output:

    Service status: ▰▰▱ [DONE]
Summary:
    ┌───────────────┬─────────────────────────────┐
    │ Servers:      │ 1 online, 0 offline, 0 hung │
    │ Restart Time: │ 134.977792ms                │
    └───────────────┴─────────────────────────────┘