mc replicate resync

The mc replicate resync command resynchronizes all objects in the specified AIStor bucket to a remote replication target.

This command requires first configuring the remote bucket target using the mc replicate add command. You must specify the resulting remote ARN as part of running mc replicate resync.

This command supports rebuilding an AIStor deployment using an active-active replication remote as the “backup” source. See the following tutorials for more information on active-active replication.

Syntax

Example

The following command resynchronizes the content of the mydata bucket on the myaistor AIStor deployment to the remote AIStor deployment associated to the specified --remote-bucket:

mc replicate resync start \
   --remote-bucket "arn:minio:replication::d3c086c7-1d64-40c2-954b-fe8222907033:mydata" \
   myaistor/mydata

Syntax

The command has the following syntax:

mc [GLOBALFLAGS] replicate resync start|status  \
                 --remote-bucket "string"       \
                 [--older-than "string"]        \
                 ALIAS

Brackets [] indicate optional parameters.
Parameters sharing a line are mutually dependent.
Parameters separated using the pipe | operator are mutually exclusive.

Copy the example to a text editor and modify as-needed before running the command in the terminal/shell.

Parameters

ALIAS

Required

The alias of the AIStor deployment and full path to the bucket or bucket prefix which AIStor uses as the replication source. For example, the following command starts replication using the data bucket on the AIStor deployment associated to the myaistor alias.

mc replicate resync start myaistor/data --remote-bucket "ARN"

start

Required

Starts the resynchronization procedure using the specified bucket as the source and the --remote-bucket as the remote target.

Version changed

Starting with AIStor Client RELEASE.2025-07-28T19-02-30Z, specify either the destination bucket’s ARN or an ALIAS/BUCKET to --remote-bucket. Previous versions require passing the destination bucket’s ARN.

Mutually exclusive with mc replicate resync status.

status

Required

Returns the status of resynchronization on the specified bucket to all remote targets.

Include the --remote-bucket argument to filter the status output to only the specified remote target.

Mutually exclusive with mc replicate resync start.

--remote-bucket

Required

Specify the destination deployment and bucket.

Version changed

Starting with AIStor Client RELEASE.2025-07-28T19-02-30Z, specify either the destination bucket’s ARN or an ALIAS/BUCKET. Previous versions require passing the destination bucket’s ARN.

You can retrieve the ARN using mc replicate ls. If you use the --json flag, the rule.Destination.Bucket field contains the ARN for any given replication rule.

Starting with RELEASE.2025-07-05T15-07-57Z, the output of mc replicate ls includes the ARN.

older-than

Optional

Specify a duration in days where AIStor only resynchronizes objects older than the specified duration.

Only valid with mc replicate resync start.

cancel

Optional

Cancel a current resync job.

Global flags

This command supports any of the global flags.

Examples

Resynchronize remote replication target from source bucket

The following mc replicate resync command resynchronizes all objects on the specified source bucket to the remote target regardless of their replication status:

mc replicate resync start --remote-bucket "arn:minio:replication::UUID:data" primary/data

Replace primary/data with the ALIAS and bucket to resync.
Replace the --remote-bucket value with either the ALIAS/BUCKET or the ARN of the remote target.

Using ALIAS/BUCKET for the --remote-bucket value requires AIStor Client RELEASE.2025-07-28T19-02-30Z or later.

Use mc replicate ls to list all configured remote replication targets.

Behavior

S3 compatibility

The mc commandline tool is built for compatibility with the AWS S3 API and is tested with AIStor and AWS S3 for expected functionality and behavior.

MinIO provides no guarantees for other S3-compatible services, as their S3 API implementation is unknown and therefore unsupported.

While mc commands may work as documented, any such usage is at your own risk.