Storage 100
1.50 usd/ mo.
- Storage
- 100 GB
- FTP access
- Included
- SSH access
- Included
- Rsync access
- Included
- Nextcloud interface
- Included
Copies live apart from the server they insure. A failed disk, a broken system or an unreachable site will not touch them.
from 1.50 usd / month
The plans differ only in volume; everything else is the same. The monthly price depends on how long you order for.
Storage 100
1.50 usd/ mo.
Storage 500
3.00 usd/ mo.
Bestseller
Storage 1000
4.50 usd/ mo.
Storage 2000
8.25 usd/ mo.
Storage 5000
21.00 usd/ mo.
Prices exclude tax and payment-system fees. The exact amount due is shown in the client area when you place the order. How tax is calculated
Count not the current size of your data but that size multiplied by retention depth: how many generations of copies have to sit there at once.
Copies of one or two websites, a small database or server configs. They fit when backups run to tens of gigabytes and have to be kept for a week or two.
Enough for several generations at once: daily copies for a week plus weekly ones for a month. People take it when one last copy has stopped being enough.
Copies of several servers, heavy databases, file archives and media. People take these when backups are already measured in terabytes.
Send us the volume of your data and the retention depth you want, and we will suggest a plan and help estimate room to grow. Guessing wrong is no disaster: moving up a plan does not move your data.
Ask usEverything that is hard or slow to put back together.
Files and the database of WordPress, a store or a company website, kept apart from the server they run on.
Scheduled MySQL and PostgreSQL dumps, with several generations for when the damage is noticed late.
System snapshots and control-panel exports that must not stay on the same machine.
Documents, media and accumulated project data that are rarely opened and cannot be lost.
Working systems that take longer to rebuild by hand than to redeploy a server from scratch.
One more site besides the working server and local storage, the one that stands in a different building.
Three steps from ordering to the first copy in place.
STEP 1
In the order you choose the plan and the term. The longer the term, the lower the monthly price.
STEP 2
Ten minutes after payment your share is ready, and the client area holds the storage address, the login and the password.
STEP 3
From there the schedule is yours: what to copy, how often, and how many generations to keep. Support will point out where the address and login go in your particular system.
A copy on the same server saves you from exactly one thing: somebody deleting the wrong file. Everything else it goes through together with the server: the disk fails, the file system falls apart, the machine becomes unreachable, and the backup is gone precisely when it was needed.
Remote storage breaks that link. It stands on different hardware, in a different building, on different power, so a failure on the working server cannot reach the copies. That is the point of the 3-2-1 rule: three copies, two different media, one of them somewhere else.
Inside the storage the data does not sit on one disk either. A Ceph cloud cluster holds it: files are spread across several nodes, so losing a single disk or server does not lose the copies.
We are rated on independent sites, where the reviews can be read in full.
HostAdvice 2026
HostAdvice 2024
HostAdvice 2021
What people ask before their first order.
Backup hosting is separate storage for your backup copies. Wherever your main data lives, if the primary hardware fails or becomes unreachable, the copy on a remote server stays intact.
Yes, and that is the usual case. The service is not tied to anything and does not require the main server to be ours: another hosting provider's server, a machine in the office or a home NAS will all do: anything that can send files over FTP, SSH or Rsync.
You do. We provide the space and the access to it; what to copy, where and on what schedule is decided on your side. Server control panels can copy to a remote server with their own built-in tools; all they need is the storage address, a login and a password.
If the built-in way does not fit, write to support: we will suggest an approach for your system and share our own scripts for Unix-like systems.
The data is available over protocols built for file transfer: FTP and Rsync. Every plan also includes SSH access, so you can always inspect what is stored on the server, plus the Nextcloud web interface for working from a browser.
As many as you keep yourself. The storage is a place, not a backup system: it does not version files and will not hold yesterday's copy back if today's was written over it.
So set the retention depth on your side, in the copying schedule: seven daily copies and four weekly ones, for example. Work out the space for them in advance, or the generation you need will have been overwritten exactly when you need it.
The time is limited not by the storage but by the size of the copy and the link on the receiving end: a terabyte cannot come down faster than the network of the server you are restoring to allows. Traffic on our side is unmetered and we do not charge for it, so downloading a copy costs nothing extra.
If a restore has to fit into a specific window, test that in advance on a real copy rather than on the day of the outage.
Different clients' data on the storage is isolated from one another: one client cannot see what another keeps there. Access to your share is opened by your login and password.
The files are stored exactly as you sent them; the storage does not encrypt them itself. If the contents are sensitive, encrypt the archive on your side before sending: the key then never leaves your own infrastructure.
In Warsaw, Poland. The storage runs at that site only and the service offers no choice of country, so the copies stay within the European Union.
Worth keeping in mind if you took the main server in Switzerland in order to hold data outside the EU: copies sent from it into this storage will end up inside the EU. When jurisdiction is the reason for choosing Zurich, agree the backup arrangement with us before ordering.
Move up to a larger plan. The plans differ only in volume and are otherwise identical, so the change breaks nothing: the data stays where it is, and what changes is the expiry date of the paid service. Moving down works the same way.
The client area issues a European-format invoice, and a closing document is available once it is paid. The tax depends on who is buying: EU companies with a VAT number fall under reverse charge, outside the EU it is 0%, and EU private individuals pay their own country's rate. It is all set out on the payment and documents page.
Three services it is usually ordered alongside.
On a VPS we take a nightly copy ourselves, but there is one of it and it lives on our side. A second copy, one that would survive a failure of ours too, is kept separately.
Linux VPS plans →We hold no copies of a dedicated server at all: what to copy and where is the owner's call. This is the case where storage is bought together with the server.
Dedicated servers →Accounting software and staff desktops: one shared database, where losing a day's work costs more than the space for copies.
Windows VPS plans →Then we take the nightly copy ourselves and it comes with the plan. Separate storage is for when the copies have to be yours: your schedule, your retention, your access.
Pick a volume, and the credentials arrive in the client area, and from there the copies run on your schedule.
Choose a plan