Job hosting-offsite-backups-with-restore-test · revised 9 October 2026
Set up off-site backups for a website and prove a restore works
Back up one site and its database to a storage account you own, then restore a copy on staging and test pages and a record before signing off.
You might be seeing
- The hosting panel says backups are enabled but nobody has restored one
- You cannot say how old the last usable site and database copy is
- The host stores backups on the same server that could fail
No passwords, keys, card details or admin invites needed to start.
What usually happened
A backup that never leaves the hosting account can disappear with the server or a cancelled plan. File-only backups miss database records, and untested archives may be corrupt or need settings nobody kept. A real restore on a separate test site is the only way to see whether the copies include what the business needs.
Who it’s for: Owner of a business website that relies on host backups or has already lost work after a failed restore.
Usually starts when: You discover the host keeps backups on the same server, has no tested restore, or an update or outage made you fear losing bookings and records.
The result: A scheduled off-site copy of the site files and database lands in storage you own, and a sampled restore on staging shows the agreed pages and a named test record still work.
Check whether this job fits
Four short questions. Your answers stay on this page unless you choose to email them.
Checks you can run yourself
Find where today’s backups go
In your hosting panel, open Backups, Backup Wizard or JetBackup, or ask your host where its backups are stored.
Look for: Whether copies are kept on the same server, at the same provider, or somewhere separate you control, and how many days they keep.
Check the backup includes the database
Open the newest backup listing or ask your host what it contains.
Look for: Both the website files and a database export. A files-only backup of a site with bookings, orders or members is incomplete.
What you get
- The backup schedule, off-site destination, configured retention period, encryption settings and included files/database
- A restore log with archive date, file count and a named test database record
- The steps to restore without our involvement, and a test failure alert
Included
- One website with up to 10 GB of files and one database up to 2 GB
- A daily schedule to an off-site account you own, with the retention setting configured for at least 14 days of copies
- Encrypted transport and storage with scoped access and a documented key holder
- One full restore into a non-public staging location and tests of agreed pages and a database record
- One tested alert when a daily backup fails
Not included
- Guaranteeing that the host or storage provider will never fail
- Backing up mailboxes or other separate applications
- An ongoing paid backup-monitoring service
- Making a broken site or database healthy as part of a restore
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
The first scheduled backup contains both files and database in the client-owned off-site account, with a visible timestamp and expected size
Evidence: Storage listing and backup log
A separate staging environment restored from that archive loads each agreed page and the named test database record
Evidence: Restore log, screenshots and test record
A simulated failed backup sends an alert to the owner address, and the next successful run clears it
Evidence: Failure and recovery alerts
The documented restore steps work from a new isolated environment without access to the live server
Evidence: Second reviewer’s rerun note and log
The backup destination shows a retention setting of at least 14 daily copies, and transport and stored archives use the agreed encryption settings with recovery keys held by the client
Evidence: Screenshots or exported settings for retention, transport encryption, archive encryption and client-held key location; not a claim that 14 days have elapsed
Sign-off. You sign off after one scheduled copy, one independent staging restore, a tested failure alert, and checks of 14-day retention and encryption settings. Fourteen successful days are not claimed at sign-off.
If it fails. If the agreed acceptance checks do not pass, the client does not pay, and keeps our findings and rollback steps.
When it fits, and when we stop
It fits when
- You control the site, database and an off-site storage account or will create one
- The host permits scheduled exports or an approved backup tool
- A separate staging location can run a restore without touching live data
- Someone at your business can receive alerts and hold recovery keys
We stop and tell you if
- The host will not provide a complete database export or any permitted backup method
- A staging restore would expose unredacted sensitive customer data to unauthorised people
- The only backup is on an infected or compromised server and its integrity cannot be trusted
- The source is already corrupted and no known-good copy exists: repair is a separate job
What could go wrong
The backup job only reads from the site and writes to separate storage, so stopping it changes nothing on the site. Your host can remove the schedule; your storage account and its copies stay yours.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| An off-site archive lacks the database or recent uploads | Restore the full archive and check a named database record and uploaded file. |
| The storage account or encryption key is held only by a contractor | Client owns the storage account and recovery keys; the handover is sufficient to restore without SI. |
| A failed backup goes unnoticed for weeks | Send an alert to the owner and simulate a failure to prove it arrives. |
A second reviewer restores an archive using only the written guide, and checks who holds the storage account and its recovery key.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Record what the current backups contain, where they are stored and how long they are kept
- Set up a daily export of files and database to a storage account you own, with 14 days of copies
- Restore one archive into a separate staging location with no access to the live server
- Check the agreed pages, a named test record and an uploaded file on the restored copy
- Simulate a failed backup and confirm the alert reaches your address
- Independent rerun of the restore guide, then hand over the guide and settings
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the total price, a start window and a delivery date before you accept. Work starts only after agreed inputs, secure access, any licences and necessary permissions are in place. Hosting, platform and supplier charges are excluded unless the written quote includes them. No charge or booking is created by an enquiry.
Need to keep it working?
Discuss scheduled restore rehearsals and review of failed-backup alerts if you need someone to keep checking that recovery works.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing engineering lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Many managed hosts offer off-site backups with a restore service; ask for the exact retention and a test restore before buying another product.
- If the site is static with no database, a version-controlled copy of its files may be enough; this package is for sites with files and records to protect.
Questions
Is a backup real if we have never restored it?
You cannot know. This job includes restoring a copy to staging and checking a named page and record.
Where are the backups kept?
In a storage account you own, separate from the website host. The job sets a daily schedule and 14-day retention, proves one restore, and makes you the key holder; it does not claim 14 daily copies already exist.
Start with an email
Send us
- The host and platform your site uses
- Size of the site files and database, if the panel shows it
- Current backup method and where its copies are stored
- How much data you can afford to lose in an outage: one day or less
Later, once you agree
- A backup export made by your host and a staging environment in your account
- A storage account with a narrowly scoped destination and a key you hold
- One synthetic test record to look for after restore
- A company-controlled secure handoff agreed before access: no live passwords, keys, private code or customer records by ordinary email.
The client owns the accounts, domain, live system and keys. An AI agent prepares the change using only an authorised test copy or read-only information; a separate reviewer checks the risks, and the client or their site holder approves any live change. Synthetic Industry is owned by a person and remains accountable for the agreed work. We never ask for passwords in the first enquiry.
Or write to hello@syntheticindustry.ai with “hosting-offsite-backups-with-restore-test” as the subject.