Overview
If a file is accidentally removed from an Amperity-managed SFTP location, customers often ask whether the file can be restored or retrieved from a backup.
This article explains Amperity’s SFTP file retention policy and what options are available.
Important to Know About SFTP File Retention
In Amperity, SFTP locations are designed for data delivery and ingestion, not long-term storage.
Key points:
Files on Amperity SFTP servers are not backed up
Files are retained for a limited time window
Once a file is deleted or expires, it cannot be recovered
Because of this, Amperity Support cannot restore deleted SFTP files.
Why Files Cannot Be Restored
SFTP locations do not maintain historical backups or archives
Deleted files are permanently removed after the retention period
Amperity does not store copies outside the SFTP location
This behavior is expected and applies to all customers.
What You Can Do Instead
If a required file is missing:
Re-generate the file from your source system
Re-upload the file to the SFTP location
Maintain your own backups before uploading files to SFTP
These steps ensure data can be recovered if a file is removed accidentally.
Best Practices
Keep a local or cloud backup of all files sent to SFTP
Treat SFTP as a transfer location, not a storage system
Re-upload files promptly if ingestion fails
Monitor file delivery and retention timelines
Summary
Amperity SFTP servers do not retain backups of uploaded files.
If a file is deleted or expires, it cannot be recovered, and the file must be re-created and uploaded again from the source system.
Applies To
Amperity SFTP
File-based data ingestion
Data delivery and retention policies