Virtual server maintenance
We watch allocated memory and disk space, update the hosted systems and take a snapshot before every change.
From a single operating system install on one machine to continuous support of the directory service and the virtualisation environment.
We install from scratch, migrate personal settings and documents, select the drivers and put the applications back.
We clean up the startup list, remove the infection and replace the single component dragging everything down. It often works out cheaper than buying a new machine.
Configuring roles and services, applying patches, watching resource usage, reviewing event logs and preventing failures.
The directory service, centralised settings, permissions and discipline in accounts: an employee leaves and their access ends the same day.
We watch allocated memory and disk space, update the hosted systems and take a snapshot before every change.
Several systems share the same hardware: costs are lower, rolling back is instant and moving between nodes happens without stopping work.
An update went wrong, the database was damaged, everything froze in the middle of the reporting period, the connection licences ran out.
New hardware or a disk array, from racking it to the day people start working on it.
Failures are prevented by the dullest part of maintenance. That is why it runs strictly to a schedule rather than when someone gets round to it.
Every day. Stops you missing a failed component you would otherwise learn about a week later.
Every day. Stops the database halting because a drive has filled up.
Once a month. Removes the main danger: a backup you cannot restore from.
Once a month. Closes the holes that have become common knowledge, attackers included.
Once a quarter. Removes access from people who left the organisation long ago.
First we document the estate and only then take it on. The diagram, the list of services, where the data sits and the chains of dependencies come together in a document that is yours for good. Without it all the knowledge lives in one specialist's head and leaves with them.
That is how it is almost everywhere. We start with discovery: finding every node and service, establishing who is responsible for what, drawing the diagram. It takes from a week to a month depending on scale. After that the work follows the document rather than guesswork.
Before installing anything we take a snapshot; if there is a separate test rig we try it there first, and the work itself is done at an agreed time, usually at night or at the weekend. If it goes wrong, the rollback to the previous configuration is finished before the working day starts.
Both platforms, including the local Linux builds used when migrating to trusted software. A mixed setup where the directory service runs on Windows and the application services on Linux is entirely routine for us.
If there are many internal applications and they change constantly, an in-house specialist earns their keep: they understand the business from within. With that split we keep the hardware, the round-the-clock duty and the specialist knowledge, while they keep the applied work.
Укажите количество машин, перечень работающих на них систем и того, кто их сейчас ведёт. Сделаем обследование и назовём первоочередные задачи.
Request received
It is already with a manager. You will get an answer within the working day, and urgent requests go to the duty engineer immediately.
There is no such city in the list. Check the spelling.