Einleitung
With the update to Silent Brick Version 2.57 previously configured S3 Shares without Object Locking are not supported anymore and need to be migrated.
After the Update your S3 Share will be deactivated and replaced by an SMB connection in order to gain access to the data. This Guide describes how to migrate Data from this SMB Connection to a new S3 Share on the Silent Brick System.
-
-
In Silent Brick Version 2.57 the S3 server is updated to a new version. This version offers increased performance and a significantly reduced overhead for S3 shares with object locking.
-
Due to an updated S3 Server existing S3 shares without object locking can no longer be accessed via S3 API and must be migrated manually.
-
-
-
If S3 Services without object locking were configured on your system, the update mechanism will automatically move your data to a folder on the system, to which you can set an SMB share.
-
This process will generate 2 messages in the Notifications Tab
-
-
-
One message for the deprecated support of the “NAS Gateway Mode”
-
One message for the conversion of the share
-
The path to the existing data is also specified in this message
-
The old S3 share has been converted. This can be recognised by mode snsd
-
The converted S3 share is empty and can be written to again. The data from the old S3 share must be copied manually via a SMB share.
-
-
-
Create a new SMB share with the path specified in the converted message
-
Share name from converted message
-
Assign a share name of your choice
-
You can also assign users and groups
-
Save the changes
-
The new SMB share should now be visible
-
-
-
If you now mount the SMB share you have just created, you will see all the buckets of the previous S3 share
-
-
-
Now check the available space on the volume
-
If there are no more 60% free, please contact FAST Support
-
If 60% or more space is available, go to Step 7
-
-
-
If you are already using an add-on for S3 in Windows Explorer, the data can be copied using this tool.
-
MinIO provides a client for Windows and Linux via which the copy process can be executed via the terminal
-
You can see the individual bucket names in the SMB share.
-
Create these bucket names again in the new S3 share.
-
Right-click on the S3 share -> Manage
-
Now enter the old bucket name and save the change
-
-
-
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 new S3 share.
-
Click on the S3 share to open the share info
-
We now need the share name (test 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 Test https://172.20.44.167:9000 abcd1234 secretkey --api S3v4 --insecure
-
If the command runs through cleanly, a confirmation appears
-
-
-
To copy a bucket, execute the following command
-
mc cp \\<server IP address\share name\bucket name\> <S3 share name\bucket name\> --insecure --recursive
-
For this example
-
mc cp \\172.20.44.167\Old_S3_Data\test\ Test\test\ --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>
-
-
-
In the S3 share, you can now see that it is no longer empty because data has been transferred.
-
Team
