Windows Server backups
Backups that have actually been restored, every time
Most server backups are never tested until the day they are needed. ServerMaid backs up your websites, databases and configuration on a schedule, then verifies every set: every file's fingerprint, every archive opened end to end, and every database dump replayed into a scratch schema to prove it restores. Kept on local disk or a network share, with retention you set.
Backups module, £59 £29.50 per server for twelve months. 30-day money-back promise.
What is in a backup set
Everything a rebuild would need
Website files
One archive per website under the websites root: wwwroot, private files, logs if you want them. Sites with backups switched off are skipped.
Database dumps
One dump per user database, made with the server's own tools and the stored root credentials passed securely, never on a command line. System schemas are skipped.
Configuration
ServerMaid's configuration, the desired state of the server and a full configuration snapshot, so the server can be put back the way it was. The secret vault is never included.
Verified, not assumed
What happens after every run
Fingerprints checked
Every item's SHA-256 is compared with the manifest written during the run. A mismatch marks the set as failed and raises an alert.
Archives opened
Every archive is opened and every entry read to the end, so a truncated or corrupt file is found today, not on restore day.
Dumps replayed
Each database dump is replayed into a temporary scratch schema and dropped again. If it does not restore, you hear about it now.
Restore
Restore one website, one database, or any mix
Pick exactly what
The Backups page lists what a set holds with a tick box each. The confirmation names exactly what will be overwritten; nothing else on the server is touched.
Safety backup first
Before anything is restored, a backup of exactly what will be replaced is taken. If that fails, nothing is restored. Replaced website folders are kept beside the restored ones.
Schedule and destination
Hourly, daily at a time you choose, or weekly. Local disk or a UNC share with stored credentials. Retention in days, applied after each run.
Questions about backing up a Windows web server
Where do the backups go?
A folder on local disk, a second drive, or a network share with credentials stored in ServerMaid's encrypted vault. Each run writes a dated set under the server's name.
Does a backup slow the websites down?
Runs are scheduled for a quiet time you choose, files are archived with the standard Windows compression library and dumps stream to disk. On a typical small server a run finishes in minutes.
Are backups part of the health score?
Yes. A missed run, a failed verification or a last set older than the schedule allows deducts points with the reason shown and a fix offered.
Can I restore to a different server?
Website archives and database dumps are standard zip and SQL files, so they can be used anywhere. Restoring a whole set onto a new server built by ServerMaid is straightforward: build, then restore.
What if my licence lapses?
Scheduled backups that are already configured keep running. ServerMaid only pauses new changes, never the protection already in place.
Know your backups work before you need them
Add the Backups module to any ServerMaid server. Verified by restore after every run, and restorable one site at a time.