In this article, you will learn :
- What is Sherpany Storage Extender
- What is the required setup for Sherpany Storage Extender
- Which migration from Sherpany managing documents to SSE or from SSE to Sherpany managing documents is supported
- If Sherpany supports different ways of configuring Sherpany Storage Extender
What is Sherpany Storage extender?
The Sherpany Storage Extender (SSE) is a hybrid-cloud solution that unites the benefits of SaaS with the need for on-premise data storage, including disaster recovery and backups. It is a high-performance object storage server designed for large-scale private cloud infrastructure. SSE is hardware-agnostic and works on various physical and virtual/container environments.
Sherpany stores after encryption all the documents the user uploads to the application in the S3 storage. With SSE, all the documents uploaded by your users will be stored in the location chosen by you.
What is the required setup for Sherpany Storage Extender?
The Sherpany application can work with any S3 compatible storage which we can access from our network either via direct link or a secure tunnel (i.e. SSH).
If you choose to pursue a hybrid-cloud SaaS approach, the integration team develops the required technical steps to get the SSE up and running. We provide you with an SSE integration template that serves as the starting point for individualization to your specific enterprise needs.
Which migration from Sherpany managing documents to SSE or from SSE to Sherpany managing documents is supported?
Sherpany supports migration in both ways. It would be possible to start using Sherpany without SSE and implement it later. It would also be possible to do it the other way around: start using Sherpany with SSE and later skip it and have all the data in our data center.
Does Sherpany support different ways of configuring Sherpany Storage Extender?
If you don’t have any S3-compatible storage, Sherpany can provide you with a VMware image running docker with minIO on it to make mounted storage available via S3-API. The running docker is also responsible for creating a VPN tunnel to our servers using OpenVPN.