For CIFS, NFS, or Rsync backups on senhasegura, a direct connection to the backup device is required. Using the Network Connector in these cases is not possible.
If a Network Connector is used, the backup must be stored in the AWS Bucket or Azure Blob. Therefore, to avoid complications, make sure to follow the appropriate guidelines depending on the connection method used.
Hey @Jade_Ariel, does this mean that Segura on SaaS, when using the network connector, will no longer support external backups or remote mounting to an on-prem target server? Therefore, as an alternative, is it recommended to direct external backups to an AWS S3 bucket or Azure Blob? Please correct me if I’m misunderstanding. Thanks!
Great question — and you’re mostly correct in your understanding.
Yes, when using Segura® SaaS with the Network Connector (NC), external backups of application data and session files to on-premises targets are not supported. In such cases, the recommended approach is to direct these external backups to cloud storage, such as an AWS S3 bucket or Azure Blob Storage.
However, when it comes to password (credential) backups, it’s still possible to use RSYNC via the NC, allowing clients to manage and store these backups externally if desired.
Here’s a summary of the backup responsibility in SaaS models:
In the SaaS model, Segura® is responsible for system backups (infrastructure, platform, etc.).
Credential backups, however, remain under the client’s responsibility and can be managed using RSYNC.
Appreciate the informative breakdown. However, I sighted that in the configuration for backups for credentials via RSYNC (as you mentioned) will still requires public key from the Segura PAM server. Which I believe is a roadblock for Segura SaaS since we do not have access to the CLI of it. Kindly advise.
When configuring backup via RSYNC in a Segura SaaS environment, you’ll need to contact our Support Team directly. They will provide you with the necessary information to complete the setup on the destination server;