Scheduled maintenance

The dullest part of administration is what prevents outages. The work runs to a schedule, not whenever someone remembers.

Review of logs and services

Daily. Prevents a node failing unnoticed and being discovered a week later.

Monitoring of disk space and resources

Daily. Prevents the database stopping because a disk is completely full.

Restore testing from backup

Monthly. Prevents the biggest surprise: a backup that will not restore.

Installation of security updates

Monthly. Prevents exploitation of already known vulnerabilities.

Review of accounts and permissions

Quarterly. Prevents former employees from accessing systems.

We document the infrastructure first and administer it second. A diagram, a list of services, where everything sits and what depends on what: this is a document that stays with you. Without it, administration becomes one person knowledge.

Frequently asked questions

A common situation. We start with an assessment: we find every server and service, work out what does what and produce a diagram. That takes one to four weeks depending on size. After that we administer from the documentation.

Before updating we take a snapshot or a backup, roll out to a test environment first if there is one, and do the work in an agreed window, usually at night or at the weekend. If something goes wrong, we roll back before the working day starts.

With both, including the Russian Linux distributions used for import substitution. A mixed setup, with the domain on Windows and some services on Linux, is normal for us.

If the company has many internal systems and constant change, an in-house specialist is valuable: they know the business better. In that case we take the infrastructure, the on-duty cover and the narrow specialisms, while they handle application-level work.

Tell us about your servers

How many servers you have, what runs on them and who supports them now. We will run an assessment and show what needs attention first.