SVHT Silent Brick Software 2.57 Copy S3 to S3 Share

First of all check the available space on the volume

If there are no more 60% free, please contact FAST Support since data can not duplicated.

If 60% or more space is available, go to the next step in this manual

Keep in mind that existing data may underly an object locking retention and may not be deleteable within time.

Alternatively create a new Volume on an empty Silent Brick as copy target.

MinIO provides a client which will be used in this manual to copy the data

If you are already using an add-on for S3 in Windows Explorer, the data can be copied using this tool.

We recommend to write down the share settings and to rename the share and to alter the port. So a new share can be set up with the original settings.

In this example, the existing S3 share old_data_object_lock is to be copied

Right-click on the old share to display the existing buckets using Manage Buckets

Write down the bucket names of the existing share

Now create a new share on the target Volume.

The share name cannot be changed later. Therefore, use a share name that can be easily customised at the source

Use the settings of the old share to make a later connection as simple as possible

Now generate the same buckets on the new share as on the old existing share

Right-click on the new share.

Klick on Manage Buckets

Use Create New Bucket

Now enter the bucket name and save the changes.

Do this for each bucket of the old share

Download the MinIO client for your Operating System from the Minio Download Page

Install the Client and follow the following step (here described for Windows):

Now copy the mc.exe file to the path

C:\Users\<my_user>\mc\

This is necessary so that the mc config file located in this folder can be accessed.

To configure the client, we now need some data from the old S3 share. Click on the S3 share to open the share info

We now need the share name (old_data_object_lock) here, the IP address or machine name and the S3 port

Then we need the access key and the secret key

This data must now be entered in the mc Config file. This file is located in Windows under

C:\Users\<my_user>\mc\config.json

Switch to C:\Users\<my_user>\mc\

Run the following command to fill the mc config,json with the needed data

mc config host add <S3 share name> https://<IP_address:port> <access_key> <secret_key> --api S3v4 --insecure

In this example: mc config host add old_data_object_lock https://172.20.44.167:9001 abcd1234 secretkey --api S3v4 --insecure

If the command runs through cleanly, a confirmation appears

We now have to do the same steps for the new share

Click on the S3 share to open the share info

We now need the share name (new_data_object_lock) here, the IP address or machine name and the S3 port

Then we need the access key and the secret key

The information for the new S3 share must now also be entered in the mc Config file.

Switch to C:\Users\<my_user>\mc\

Run the following command to fill the mc config,json with the needed data

mc config host add <S3 share name> https://<IP_address:port> <access_key> <secret_key> --api S3v4 --insecure

In this example: mc config host add new_data_object_lock https://172.20.44.167:9002 abcd1234 secretkey --api S3v4 --insecure

If the command runs through cleanly, a confirmation appears

To copy a bucket, execute the following command

mc cp <Source S3 share name\bucket name\> < Target S3 share name\bucket name\> --insecure --recursive

For this example

mc cp old_data_object_lock\bucket1\ new_data_object_lock\bucket1\ --insecure --recursive

If the command runs through cleanly, a confirmation appears

You can now use mc ls to check the contents of the bucket

mc ls <share name>/<bucket name> --insecure

Now carry out the step for all your shares. Pay attention to the fill quantity of your volume

In the new S3 share, you can now see that it is no longer empty because data has been transferred.