Inventory and profiles
For every server we record its purpose, the software it runs, its dependencies, its users and when vendor support ends. The document belongs to you, even if you change provider one day.
Suppose you run a construction company in Murska Sobota with forty staff. Your servers were set up a decade ago by an outside IT man who came when called and has now retired. What he left behind is a file server full of cost estimates, bills of quantities and interim payment claims, a SQL Server holding the Pantheon database, and a Linux virtual server at Hetzner running the portal where subcontractors upload documents. Everything works, until it does not. Nobody knows which passwords are still valid, whether the backup covers the database, or what would happen if a disk died in the week a payment claim is due with the client. That is an organisational gap rather than a technical one: all knowledge of the systems lived in one person's head. Our job is to move it onto paper and into a routine. Each server gets a description, a named owner on our side, a maintenance calendar and a backup that we really restore to a test system once a month. Location does not matter: a cabinet in your office, an EU data centre or an EU region of Azure or AWS. All the work is remote.
We agree the scope in writing before we take over, so it is clear what falls to us, what stays with the software supplier and what remains with you.
For every server we record its purpose, the software it runs, its dependencies, its users and when vendor support ends. The document belongs to you, even if you change provider one day.
A snapshot or fresh copy is taken before each round of updates. Patches reach a less important system first and the critical ones afterwards. If Pantheon refuses to start after an update, we are back where we were within minutes.
A backup nobody has restored is wishful thinking. Each month we restore a chosen server or database to a separate test system, confirm the data opens and log how long it took.
Database and transaction log backups, index upkeep, growth monitoring and keeping an eye on the size cap of the Express edition. During software upgrades we work alongside the supplier, who keeps responsibility for the application itself.
Key-based SSH, a host firewall, unattended security patches where they are safe, and planned moves to new PHP and database versions that we rehearse on a copy first.
We do not just shout when a disk is full. We track how fast it fills, so we can tell you space will run out in four months and you can budget calmly.
Personal accounts for every administrator, VPN with multi-factor sign-in, no remote desktop open to the internet, and logs that show who was connected and when.
After the takeover the service runs within a plan or on actual time at €50 per hour plus VAT.
We gather every credential we can find, change it and store it in a password vault registered to your company. Old shared accounts are closed.
Disk and hardware condition, missing patches, unsupported versions and a first test restore. Findings are sorted by urgency.
We fix maintenance windows outside office hours, freeze periods when servers are left alone, and your contact people.
A monthly report covering patches, the restore test and capacity trends, plus a quarterly video review with management.
A backup no one has restored is only an assumption. When we take over an estate we often find a nightly job that reports “success” but skips the database because it was locked during the copy, or copies kept on a disk attached to the same server, where ransomware would encrypt them along with everything else. So we run our first restore test in the very first month and show you how long getting back to work would really take.
Patches installed and deferred, with reasons; the result and duration of the restore test; disk usage with its trend; alerts raised and how we dealt with them; and deadlines falling in the next three months. It is short and written so a managing director can follow it.
Not necessarily, but Express caps each database at 10 GB. Once a database hits that limit, the software stops taking new entries. We watch the size and suggest archiving, a clean-up with the software supplier or a move to a licensed edition well before it matters.
Regular support for Windows Server 2012 and 2012 R2 is over, so the server no longer gets routine security fixes. We plan how to move its roles to a supported version and time the work around your accounting deadlines. Meanwhile we restrict its exposure to the internet as tightly as possible.
We do not visit sites. We identify the fault remotely, find the correct part number and raise the warranty claim. The disk is then replaced by the vendor's technician, data centre staff or one of your colleagues following our instructions, while we stay on a video call and watch the array rebuild.
That depends on your plan: 4 hours on Start, 1 hour on Business and 15 minutes on Premium, within working hours, Monday to Friday, 9:00-17:00. Premium clients also receive an out-of-hours channel in their contract.
Tell us what servers you have, where they are and which important applications run on them. We will come back with questions and an estimate of the effort.
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
No town by that name here. Check the letters, or settle for the nearest larger place. Our engineers work only over the internet, so Kočevje and Koper get precisely the same treatment.