Adding External File System Storage on the FileCatalyst Server
Posted by Aly Essa, Last modified by Aly Essa on 30 September 2019 10:32 AM
After the FileCatalyst Server has been installed you may want to use an object storage mount as a primary or alternative storage device. The FileCatalyst Server currently supports Amazon S3 Buckets, Azure Blob Storage, OpenStack Swift3, Backblaze, Google or SMB/CIFS storage mounts.
You can use this article to add the object storage to your FileCatalyst Server deployment.
FileCatalyst Server v3.7 and newer.
There are two methods to add Amazon S3 Buckets, Azure Blob Storage, OpenStack Swift3 or SMB/CIFS mount points on the FileCatalyst Server. You will need to enable the Advanced view to see the File Systems tab.
- Adding object storage mounts as External File Systems.
Using this method will only allow you to use one instance of each object storage available (Amazon S3 Buckets, Azure Blob Storage, OpenStack Swift3 or SMB/CIFS).
For example, you will now be able to mount 2 two Amazon S3 Buckets. If you already have one Amazon S3 Bucket the option will disappear when trying to add another one.
If you have a requirement to use multiple object storage points of the same type please see the URL Composition Method.
- In the FileCatalyst Server Remote Admin navigate to File System tab on the left and click +New.
- From the drop-down list select the type of object storage you would like to add.
- Enter your File System Access Key, Secret Key and Endpoint path. Hit the Test button to connect to the object storage.
- You will now be able to configure the object storage as the Users Home Directory, Virtual File or as a Virtual Folder.
- URL Composition Method
The alternative method is to configure the object storage using the URL Composition method. This allows you to use more than one object storage type. You can use the URL Syntax and add it as a Users Home Directory, Virtual Folder or Virtual File.
- Amazon S3:
- Scheme: s3
- Default Endpoint: s3.amazonaws.com
- Full Syntax: s3://<access key>:<secret key>@s3.amazonaws.com/<bucket>/<path>
- Azure Blob Storage:
- Scheme: msab
- Default Endpoint: core.windows.net
- Full Syntax: msab://<account name>:<account key>@core.windows.net/<container>/<path>
- OpenSwift Stack3
- Scheme: swift3
- Default Endpoint: blank
- Full Syntax: swift3://<account name>:<account key>@<endpoint>:<port>/<container>/<path>
- Default Endpoint: blank
- Full Syntax: smb://<username>:<password>@<host or IP>/<share>/<path>
- Goolge Cloud Storage
- Scheme: gcs
- Default Endpoint: api.backblaze.com
- Full Syntax: gcs://<json credentials filename>:<enter any value for password>@googleapis.com/<container>/<path>
- Scheme: b2
- Default Endpoint: googleapis.com
- Full Syntax: b2://<access key>:<secret key>@api.backblaze.com/<bucket>/<path>
For special notes, limitations and other configurations please see our External File Systems Document.