Услуга · System administration

Server administration

A server failure differs from a broken computer in scale: it is not one person who stops but the whole organisation. That is why the work is built on prevention - monitoring, an update calendar and regular checks that the archives really do unpack.

Alerts
to the person on duty, not to a mailbox
Windows
updates on a calendar
Archives
verified by restoring
Inventory
a diagram and credentials

What the work includes

We work with both Windows and Linux to one scheme: handover against an inventory, monitoring, a written procedure.

Discuss the scope

Services

User directory, file shares, printing, web servers, application servers.

Monitoring

Load, memory, free space, disk array health, service response.

Updates

We install in agreed windows and always with a prepared way of going back.

Archives

We configure it, watch it run and periodically restore from it, rather than ticking a box in the job list.

Failures

After every crash we find the cause and make sure it does not recur.

Inventory

A diagram, the purpose of each machine, credentials in protected storage.

How it goes

Taking the infrastructure over takes a few days; after that everything runs to a set routine.

01

Inventory

Which machines, which roles, the state of updates, disks and archives.

02

Clearing the backlog

First we close the urgent items: space running out, old patches, missing copies.

03

Alerts

We configure alerts so that they reach a live engineer on duty.

04

Routine

Planned work, update windows, a monthly status summary.

Alerts sent to a shared mailbox are read by nobody. On paper monitoring is in place and the letters arrive, but in reality the server went down overnight and the accountant broke the news in the morning. The signal must reach a specific person who has both the time and the authority to react.

Questions and answers

Patches that close vulnerabilities within a week of release. Everything else monthly, in an agreed window. Machines untouched for years we bring up in steps and always with a state snapshot taken first.

It is, and it costs practically nothing: free space, availability and disk health are all watched with built-in tools. The difference between the system warned us in advance and we arrived and nothing works is measured in hours of downtime.

Separate it on the network and plan a replacement. No patches means the risk grows every month. Until replacement is possible we restrict access to it and step up monitoring.

We will take the servers under watch

Write how many servers you have and what runs on them. We will make an inventory and show where to begin.