The first issue you will probably run into when trying to use the “ostor-s3-admin” command is the following error message:

Volume id (-V) must be specified

You can get a list of all of your volume IDs by running “ostor-ctl get-config -V“. This will give you something like the following:

VOL_ID             TYPE     STATE
0100000000000002   OBJ     READY

You can then specify the appropriate volume ID with the “-V” argument to the “ostor-s3-admin” command.

Another common error that you can run into is something along the lines of:

Request failed due to internal error
Command=list-user-accounts failed with error=8(Requested object not found)

Although the exact message that you receive will vary depending upon the command that you are trying to run.

This error is caused by not specifying a user account to execute the command as. I resolved this by grabbing the main admin account user ID from the ACI/VHI S3 admin web interface and passing that with the “-i” argument.
Alternatively you can use “-e” instead of “-i” and pass the email address of the user account that you want to run the command as.

Another rather vague and unhelpful error message that you may receive from “ostor-s3-admin” is:

Bad user management cmd

This actually means that you have the arguments before the command – the “ostor-s3-admin” utility expects to receive the command (e.g. “list-user-accounts” or “list-all-buckets“) before the arguments such as the volume ID and user ID/email.

So for example the full commands should be run as:

ostor-s3-admin list-all-buckets -V volumeid -i userid

Or:

ostor-s3-admin delete-bucket -V volumeid -i userid -b bucketname

Obviously you will need to replace “volumeid“, “userid” and “bucketname” with the respective values.

The “delete-bucket” command is a very handy one that seems to be missing from a lot of the ACI/VHI S3 documentation – it will delete the specified bucket along with all of the contents, unlike the admin web interface which expects you to empty the bucket yourself first. This does however take a very long time to run on large buckets.

The post Acronis Cyber Infrastructure/Virtuozzo Hybrid Infrastructure S3 admin command line first appeared on Spheron1.

ACI is basically Virtuozzo Hybrid Infrastructure (VHI), but skinned blue instead of the usual red and with the Acronis Backup Gateway service added so that Acronis Cyber Protect can use it as for backup storage.
For those who aren’t familiar, VHI is Virtuozzo’s OpenStack distribution with their proprietary storage layer that is similar to Ceph, but apparently much more performant. Under the hood this uses VzLinux, which is Virtuozzo’s RetHat Enterprise Linux (RHEL) clone.

This means that much like other RHEL clones (e.g. AlmaLinux and Rocky Linux), ACI uses the Anaconda installer. As such, you would expect it to work with common methods of creating a bootable USB flash drive such as Ventoy or Rufus, however unfortunately that is not the case.

We found that when booting from a USB stick that was created using Ventoy or Rufus, ACI would fail to find the local package repository and end up asking you to configure a network installation source instead:

I’m not sure what makes the ACI installer so fragile compared to other Anaconda powered RHEL clones, but the fix for this is to avoid multi-boot solutions such as Ventoy and to write the ISO image directly to the USB stick without any modifications.

If using Rufus, then when creating your bootable USB flash drive, you will be prompted that Rufus has detected that you are using an ISOHybrid image and it will ask if you want to write in ISO mode (the default) or in DD mode:

Make sure to select “Write in DD Image mode” and your ACI installer will work normally.

Of course if you’re on Linux or macOS, then you can just use the dd command and be confident that it isn’t going to try and be clever and mess around with the data that is being written to the USB stick.

The post Acronis Cyber Infrastructure USB installer first appeared on Spheron1.