mc batch start

Example

The following command creates a basic YAML file for a replicate job on the mybucket bucket of the myminio alias.

mc batch start myminio jobfile.yaml

The output of the above command is something similar to:

Successfully start 'replicate' job `B34HHqnNMcg1taynaPfxu` on '2022-10-24 17:19:06.296974771 -0700 PDT'

Syntax

The command has the following syntax:

mc [GLOBALFLAGS] batch start    \
                       ALIAS   \
                       JOBFILE

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 on which to start the batch job.

For example:

mc batch start myminio replicate.yaml

JOBFILE

Required

A YAML-defined batch job. The job may have as many tasks as desired; there is no predefined limit.

Global Flags

This command supports any of the global flags.

Example

Start a Batch Job

The following command starts the batch of job(s) defined in the file replication.yaml on the deployment at alias myminio:

mc batch start myminio ./replication.yaml

Replace myminio with the alias of the AIStor deployment that should run the job.
Replace ./replication.yaml with the yaml-formatted file that describes the batch job. Use the file path relative to your current location.

The output of the above command is similar to the following:

Successfully start 'replicate' job `E24HH4nNMcgY5taynaPfxu` on '2022-09-26 17:19:06.296974771 -0700 PDT'

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.

AIStor 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.

Permissions

You must have the admin:StartBatchJob permission on the deployment to start jobs.