Request to Add FTP Transfer Feature for System Backup v2 Files in EPP

Products Endpoint Protector Ideas
, ,
1

Which aspect of EPP are you submitting for?

Endpoint Protector Server

What is a one sentence summary of your feature request?

We suggest adding an option to automatically transfer System Backup v2 files to an external FTP server once a backup is completed.

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

Hello,

I would like to request an option to automatically send System Backup v2 files to an external FTP server after a backup finishes.

Currently, backup files created by System Backup v2 remain on the EPP appliance itself, and the only way to move them elsewhere is to download each file manually through the web console.
This means that if the appliance fails due to a disk issue, VM corruption, or an OS level problem, the backups are lost together with the server they were meant to protect.
Many enterprise customers also have internal security policies and audit requirements that mandate keeping backup data on storage separate from the source system, and the current manual process makes it difficult to meet those requirements consistently.

Scheduled backup for System Backup v2 is already on the roadmap, as confirmed in the following idea: Request to Add Scheduled Backup Feature for System Backup v2 in EPP
Scheduling on its own, however, still leaves the backup file on the same appliance, so an administrator has to log in and download it each time.
Adding FTP transfer on top of scheduling would complete the workflow and make backup operations fully unattended.

FTP is a good fit for this because FTP and SFTP are supported by virtually every enterprise file server and NAS, no additional agent or component is required on the EPP appliance, and the configuration only needs a host, port, credentials, and a target path.

Suggested implementation:

  • Protocol selection (FTP, FTPS, SFTP)
  • Host, port, user name, password or key, and target directory
  • Connection test button in the UI
  • Automatic transfer after each scheduled or manual backup completes
  • Retry on failure, with a log entry or alert when the transfer does not succeed
  • Optional retention setting to remove the local copy after a successful transfer

We would appreciate your consideration. Thank you.

How do you currently solve the challenges you have by not having this feature?

At the moment the entire process is manual.

2

Hi Sung,

Thank you for the detailed write-up — the case for off-appliance backup storage is well made. The risk of losing backups alongside the appliance they’re protecting is a genuine concern, and the compliance angle around segregated backup storage is one we hear from enterprise customers.

We don’t have changes to the backup and restore process planned in the near term, so this won’t be something we can act on quickly. That said, remote transfer as part of an automated backup workflow is something we’re thinking about for the longer run, and requests like this — especially ones that connect it to real operational and compliance requirements — are useful input for that planning. We have logged this accordingly in our backlog.