Backups
A copy that is not on the same machine.
Back
Server care
Server Management
The server stays up after we leave.
Patches, backups, and a person to call when a disk or a service fails.
01
Backups you can restore
A copy that is not on the same machine.
02
Patches on a schedule
Not the night something breaks.
03
Someone who knows the cabinet
An engineer who has already seen your setup.
The work that keeps a server boring.
A server fails quietly: a disk fills, a backup stops, a patch waits for months. Management is the schedule that catches those before the office notices.
We look after servers we installed and servers that are already in the building, once we have seen how they are built.
What the job includes
- Patches on a set day, not the night something breaks
- A backup that is not stored on the same machine
- A restore test, so the backup is known to work
- Disk space and service checks, with an alert to a person
- A call path when the cabinet itself has failed
From the first visit to handover
- 01
See the server
What it runs, where the backup goes, and who uses it.
- 02
Set the schedule
Patch window, backup time, and who receives the alert.
- 03
Run it
Checks happen whether or not anyone has called.
- 04
Report
You hear about a failed backup before you need the files.
In practice
Quiet work that keeps the server boring.
Patches, backups, and a restore you know will work — before the office notices.
A closer look
Patches
On a schedule, not the night of an outage.
Alerts
Disk and services watched by a person.