Data Backup for Websites, VPS and Dedicated Servers
Backups protect projects from accidental deletion, failed updates, application mistakes and data loss during incidents. For production infrastructure, copies should be stored separately from the primary server with a defined retention period, restore process and recovery testing.
- Classic backup: simple FTP/backup storage for VPS, dedicated servers and manual backup jobs.
- S3 Object Storage: S3-compatible buckets for archives, application data, containers and disaster recovery.
- Separate copies help recover from application mistakes, failed updates, deleted files and local server incidents.
- For production, restore testing matters as much as archive creation.
Backup does not replace monitoring, security practices or recovery testing. For critical data, define RPO/RTO, retention, encryption, access controls and regular restore tests.
Which backup option fits
Classic backup
Simple storage for archives, manual copies, rsync/FTP workflows and smaller server projects.
S3 Object Storage
S3-compatible storage for large archives, application data, container workloads, backup and disaster recovery.
Storage dedicated servers
Storage servers fit cases where you need full control over disks, RAID/software stack and private storage design.
Custom backup policy
For production, define backup frequency, retention period, geography, access controls, monitoring and restore procedure.
Classic backup tariffs
Classic is the current simple pricing grid for FTP/backup storage. It fits smaller websites, VPS, dedicated servers and manual backup jobs.
50 GB
FTP/backup storage for VPS, dedicated servers and custom backup workflows.
- 50 GB
- $1 / month
100 GB
FTP/backup storage for VPS, dedicated servers and custom backup workflows.
- 100 GB
- $1.75 / month
200 GB
FTP/backup storage for VPS, dedicated servers and custom backup workflows.
- 200 GB
- $3 / month
Additional storage
FTP/backup storage for VPS, dedicated servers and custom backup workflows.
- each extra +100 GB
- $1 / month
S3 Object Storage tariffs
The S3 grid is based on the public Object Storage model: S3-compatible API, buckets, on-demand or commitment storage, transfer out and request-based billing. Final commercial terms should be confirmed before ordering.
S3 Storage Space On Demand
Pay for used storage without a commitment. Suitable for growing backup, archive and variable data volume scenarios.
- 0-50 TB: $0.0260 / GB
- 50-500 TB: $0.0249 / GB
- 500+ TB: $0.0239 / GB
S3 Storage Space Commitment
Commitment pricing from 500 GB for projects with predictable storage volume.
- 500 GB-50 TB: $0.0223 / GB
- 50-500 TB: $0.0214 / GB
- 500+ TB: $0.0205 / GB
S3 Transfer out
Separate pricing for outbound traffic. Important for restores, CDN origin use and frequent archive downloads.
- 0-10 TB: $0.0033 / GB
- 10-50 TB: $0.0021 / GB
- 50+ TB: $0.0015 / GB
S3 API requests
Requests are priced separately, which matters for applications, frequent sync jobs, lifecycle tasks and many small objects.
- PUT/COPY/POST/LIST: $0.0057 / 1000 calls
- GET/SELECT: $0.00047 / 1000 calls
- S3-compatible API
Where S3 backup fits
Backup and Disaster Recovery
Store backup copies of websites, VPS, databases, application files and configuration outside the primary infrastructure.
Data Archive
S3 Object Storage fits long-term archives, media libraries, logs and data that should remain accessible through an API.
Application Data
Applications can store images, videos, documents and user-generated files through the S3 API.
Containers and CI/CD
Object storage can be used for container workloads, artifacts, releases and backup jobs.
What to decide before launch
Retention
Decide how many copies to keep: daily, weekly, monthly, immutable/archive copies and dedicated restore points.
Restore test
A backup is useful only after files, databases and configuration are successfully restored in a test.
Access and encryption
Separate credentials, limit permissions, use HTTPS/S3 credentials and encryption where required.
Traffic and requests
For S3, consider storage, transfer out, PUT/GET requests, object count and sync frequency.
FAQ
Classic backup or S3 Object Storage?
Classic is simpler for smaller archives and manual backup jobs. S3 is better for growing volumes, automation, application data, buckets, API access, versioning and disaster recovery workflows.
Does S3 work with common backup tools?
Yes, when the tool supports an S3-compatible API. Before launch, test endpoint settings, credentials, bucket policy, upload/download behavior and restore.
Can S3 store object versions?
S3 Object Storage typically supports versioning at bucket level, allowing different object versions to be accessed through the S3-compatible API.
Is backup included with VPS or servers?
Terms differ by service. For production, order separate backup storage or define a clear backup policy.
How often should backups run?
It depends on how fast data changes. Online stores, CRMs and account systems usually need more frequent backups than static websites.
What matters more: backup or restore testing?
Both are required. Without restore testing, you cannot know whether archives can be used during an incident.
Need a clear backup setup?
Describe the server type, data volume, update frequency, retention, geography and restore requirements. We will help choose Classic, S3 or storage server design.