A backup on the same server is not a backup.
If the machine that holds your site also holds the only copy of it, one failure takes both. Your copies live on separate storage that Hostrena owns and runs — on a schedule you set yourself, restorable in a click, and downloadable to your own computer whenever you want it.
Stored away from the server that made it
Every copy is written to independent storage that we own and operate — not to a folder on your hosting account, and not to a third-party account you have no relationship with. A disk failure, a bad deploy or a compromise on the hosting server cannot reach the backups.
- Separate storage infrastructure, owned and run by Hostrena
- Physically apart from the server that produced the copy
- Backups are not counted against your hosting disk quota
- Encrypted in transit and at rest, restorable only from your account
Your schedule, not a fixed nightly window
A news site and a brochure site do not need the same cadence. You choose the interval per site, and you can change it whenever the site changes.
Stores taking orders, sites with comments or user submissions — anywhere losing a day would mean losing real transactions.
Active sites publishing regularly. The default we suggest, and the right answer for most accounts.
Company sites and portfolios that change on purpose rather than continuously.
Take a copy yourself, right now, before an update or a redesign — as many times as you like, on top of the schedule.
You set the retention too — how many copies are kept before the oldest rolls off — so a mistake you notice three weeks later is still recoverable rather than already overwritten.
Three things you can always do
A backup you cannot get at is not insurance. All three of these are yours, at any moment, without opening a ticket.
Put the site back to any kept copy in one click — the whole account, one site, one database, or a single file you deleted by accident.
Pull any snapshot down to your own computer as a standard archive. It is your data, and you never need our permission to hold a copy of it.
Browse the kept copies by date and see what each one contains before you commit, so you restore the right day rather than the most recent one.
What one snapshot actually contains
A copy of the files alone is the most common way a "backup" turns out to be useless. Everything below is captured together.
The application, its uploads, themes, plugins and anything else in the account — not a selected subset.
Captured at the same moment as the files, so the restore lands consistent instead of half a version apart.
Mailboxes, forwarders and autoresponders on the account, so a restore does not quietly lose someone’s inbox.
DNS zone, cron entries, PHP settings and SSL — the details that take longest to rebuild by hand.
As many sites as you run
Backup capacity is sized to what you actually host, not sold in tiers that force you to choose which site matters. Agencies and resellers holding dozens of client sites are the normal case here, not an exception.
- No cap on the number of websites protected
- Capacity sized to your accounts, extended when you grow
- One dashboard covering every site you hold
- Per-site schedule and retention, set independently
Backup questions
Does the backup use up my hosting space?
No. Copies are written to separate storage and are not counted against your hosting disk quota. That is the whole point of holding them off the server — a backup that fills the disk it is protecting causes the outage it was bought to prevent.
How fast is a restore?
Small sites are back in a few minutes; large stores with heavy databases take longer, mostly spent writing the database. You can also restore just one file or one database instead of the whole account, which is usually what you actually need and finishes almost immediately.
Can I keep a copy myself?
Yes, and we encourage it. Any snapshot downloads as a standard archive to your own machine. Your data should never be somewhere you cannot retrieve it from — including from us.
What if I only notice a problem weeks later?
That is what retention is for. You choose how many copies are kept before the oldest rolls off, so if a corruption or a bad edit only shows up three weeks on, an older copy is still there. Set retention against how long a problem could plausibly hide on your site, not against how much space it uses.
Are backups protected if my site is hacked?
Yes — that is a large part of why they live elsewhere. A compromise on the hosting account cannot reach or delete them, and copies are encrypted at rest. It is also why keeping several older copies matters: you want a restore point from before the compromise, not one taken after it.
Can you back up a site hosted elsewhere?
Talk to us — depending on what access that host allows, it is often possible. Tell support what the site runs on and who hosts it and we will tell you honestly whether we can protect it properly or only partially.
Find out what you would lose today
Tell us how many sites you run and how often they change. We will size the storage and the schedule with you — no tier you have to squeeze into.