--- title: "Managed Server — operations per instance, with evidence instead of gut feeling" description: "Monitoring, patch windows, backup supervision with restore tests and capacity planning — per server instance, whether in your basement, a data centre or the cloud." canonical: "https://corevatis-redesign.pages.dev/en/services/managed-server/" lang: en schema_type: WebPage --- # Managed Server — operations per instance, with evidence instead of gut feeling Monitoring, patch windows, backup supervision with restore tests and capacity planning — per server instance, whether in your basement, a data centre or the cloud. ## The short version - **What:** Ongoing operations per server instance: monitoring, planned patch windows, backup supervision with restore tests, capacity, documentation. - **For whom:** Companies that still run their own servers — physical, virtualised or in the cloud. Which is almost everyone. - **Model:** Per instance per month, in tiers from monitoring to full operations. Where the server lives is secondary. - **Result:** Servers that are maintained instead of merely rebooted — and a restore log worthy of the name. A good fit if: - Your ERP runs on a server nobody wants to touch any more - The backup runs — but nobody has ever restored from it - Updates happen when there is time. So, rarely. "The server is running fine" is the most expensive sentence in mid-market IT. It runs — until the day it does not. And on that day it is decided whether the outage lasts an hour or a week: is there a current backup? Has anyone ever restored from it? Does anyone know everything that ran on the machine? Managed Server means those questions are answered before they are asked. ## Sound familiar? - The server in the basement runs the ERP, the inventory system and "a few other things" — a complete list exists nowhere. - Updates get installed "when it fits". The last reboot was months ago, and everyone is afraid of the next one. - The backup reports green. Whether that green turns back into a bootable system has never been tested. - The disk has been filling up for a year. Action will be taken when it is full — hectically. - The provider who set the server up is no longer reachable. Neither is the documentation. ## Why this happens Servers are invisible while they work. No user calls because a patch is missing — the pain arrives with the outage, all at once. That is why server care always loses against whatever burns visibly today. A server is also not a device but a promise: line-of-business systems, databases, interfaces hang on it — and usually knowledge that exists only in heads. Maintaining such a machine needs calm, a maintenance window and a way back. Exactly what daily business never provides. And the cloud does not solve this by itself: a virtual machine at a hyperscaler needs the same care as the iron in the basement — updates, monitoring, backup supervision, capacity. Only the hardware worry disappears, not the operational responsibility. That is why we price per instance, wherever it lives. ## What server operations include - **Monitoring and alerting** — services, load, storage, hardware health, security state, measured continuously with thresholds that fit your environment. The full disk becomes a calendar entry, not a Friday-afternoon emergency. - **Planned patch windows** — updates in agreed windows, with a prior snapshot and a controlled reboot. No machine that never gets restarted out of fear. - **Backup supervision with restore tests** — we do not just watch the job succeed; we restore at agreed intervals and log how long it took. A backup without a restore test is a hope, not a protection. - **Capacity and lifecycle** — is the database growing, will storage last another year, when is the hardware economically at its end? Replacement happens with lead time and comparable quotes. - **Documentation** — what runs on the machine, which dependencies exist, who owns the business side. Written so a successor could work with it. ## From → to: the same logic as the workplace - **Base** — monitoring, patch windows, backup supervision. Your IT keeps operational ownership; interventions billed by effort. - **Managed** — we run it: incident resolution included, restore tests on a fixed rhythm, capacity report. - **Complete** — full operations with extended hours, maintenance outside business hours, lifecycle ownership including renewal planning. Hosting itself — the question of *where* your servers should run — is deliberately [its own building block](/en/services/hosting): we operate your machines where they are. A migration is a project with its own quote, never a silent precondition. ## FAQ **Do you take over servers you did not build?** Yes — that is the normal case. We start with an assessment and document what we find. Then: we operate what exists and recommend changes only where they pay off for you. **Physical, virtual, cloud — which do you cover?** All three, with the same model: per instance. Location changes the price, not the care. **What about the old server that should really go away?** We operate it anyway — and tell you honestly what keeping it costs versus replacing it. The decision stays yours; we have no interest in selling you a migration that does not pay. **How fast are you when something fails?** Honest answer: we promise the response paths we can keep — and with monitoring we see most problems before they become outages. Concrete response times are agreed per tier in the offer, not printed as a marketing number. ## Related topics - [Proving your data actually comes back — the backup drill](/en/use-cases/backup-drill) - [Network & site — firewall, switches, site fee](/en/services/netzwerk-standort) - [Packages and pricing logic](/en/packages)