Quick answer: The short version of everything in this category: back up nightly at minimum, keep copies on a separate server in a separate location, keep history (not just a mirror), encrypt what is sensitive, and restore-test quarterly. Cloud2Y does not back up your VPS content for you — your data is your responsibility, and a Storage VPS makes it an easy one.
Overview
This roundup answers the questions we hear most about backups on Cloud2Y, in one place, with links to the detailed guides. If you are starting from zero, read the Storage VPS backup setup first — it is the 80% solution.
Quick answers to common questions
- Does Cloud2Y back up my server automatically? No — on unmanaged plans the OS and data are yours to protect. That is by design: you keep full control and full responsibility.
- What is the minimum sane setup? Nightly rsync of files + database dumps to a Storage VPS in another location, with 7/4/6 retention and a log you glance at weekly.
- Snapshots or file backups? Both have a place: platform snapshots are great before risky changes; file-level backups with history are what you restore data from months later.
- Where should backups live? Off the production box, ideally another region — Kyiv ↔ Amsterdam pairs are popular (see local vs remote).
- How much space do I need? Compressed size × retention factor + 30% headroom — the arithmetic is in the sizing guide.
- How do I know my backups work? You do not, until you restore one — schedule drills.
When to contact support
Plan sizing, cross-region setup, custom disk configurations, or a suspicious failure on a Storage VPS — open a ticket. For everything script-side, the guides in this category walk through working configurations.
Frequently asked questions
Does Cloud2Y automatically back up my VPS data?
No. On unmanaged plans your OS and data are your responsibility — which is why pairing production with a Storage VPS and an automated nightly job is the recommended baseline.
What is the minimum sane backup setup?
Nightly rsync of files plus database dumps to a Storage VPS in another location, GFS retention (7 daily / 4 weekly / 6 monthly), logs you actually read, and a quarterly restore drill.
Should backups live in a different region?
Ideally yes — a Kyiv production server with an Amsterdam backup target (or any two distinct Cloud2Y locations) survives even site-level incidents, not just single-server failures.
How do I know how much backup space I need?
Take your compressed data size, multiply by your retention factor, add about 30% headroom and a year of growth. With restic or borg, months of history often fit in twice the live size.
Related articles
- How to configure backups to a Storage VPS
- How often should you back up your server?
- Backup retention policy explained
- Common backup mistakes
Need reliable space for your backups? Order a Storage VPS at Cloud2Y →
