bm admin update
Description
The bm admin update command updates all Buckit servers in the deployment.
The command also supports using a private mirror server for environments where the deployment does not have public internet access.
After running the command, a prompt displays to confirm the update.
Type y and [ENTER] to confirm and proceed with the update.
The user must have write permissions for the target location where the binary installs.
Use bm admin on Buckit Deployments Only
Buckit does not support using bm admin commands with other
S3-compatible services, regardless of their claimed compatibility with Buckit
deployments.
Considerations
Updates are Non-Disruptive
bm admin update updates the binary and restarts all Buckit servers in the deployment simultaneously.
Buckit operations are atomic and strictly consistent and as such the restart process is non-disruptive to applications.
Buckit strongly recommends only performing simultaneous upgrade-and-restart procedures. Do not perform “rolling” (that is, one node at a time) upgrade procedures.
Permissions
The user running the command must have write permissions to the target path where the Buckit Server binary installs.
Examples
Use bm admin update to update each minio server process in the Buckit deployment:
bm admin update ALIAS
Replace ALIAS with the alias of the Buckit deployment.
After running the command, answer yes to the prompt to confirm and process the update.
Syntax
bm admin update has the following syntax:
bm admin update ALIAS \
[MIRROR_URL] \
[--yes]
bm admin update supports the following arguments:
- ALIAS
The
aliasof the Buckit deployment to update.If the specified
ALIAScorresponds to a distributed Buckit deployment,bm admin updateupdates all Buckit servers in the deployment at the same time.Use
bm alias listto review the configured aliases and their corresponding Buckit deployment endpoints.
- MIRROR_URL
The mirror URL of the
minioserver binary to use for updating Buckit servers in theALIASdeployment.
Behavior
Binary Compression
This feature does not apply to systemctl managed deployments.