Monitoring
Your servers and the services on them are watched continuously. Anything unusual is reported before it shows up in the working day.
- Availability of servers and services
- Processor, memory and disk headroom
- Alerts to one named contact
Server support · Heinsberg district
Servers that keep running. IT you can count on.
Wasacon looks after servers and IT infrastructure for businesses across the Heinsberg district. Personal, secure and planned ahead, so your systems stay in the background and your business stays in front.
- One named contact
- Remote and on site
- GDPR compliant
- Aligned with BSI baseline protection
Systems monitored
Backup in place
Protection active
Illustrative view. It shows no readings from any customer system.
01Starting point
When a server stops, more than one machine stops with it
A server is rarely just a box. Files, applications, mailboxes, stock control and often the phone system all hang from it.
01
Work comes to a halt
Orders, quotes and invoices sit still for as long as the central application cannot be reached.
02
People lose access
Without a sign in to the server there is no route to drives, shares and shared folders.
03
Data is out of reach
The data is not lost, but it is no use to anyone while the path to it is broken.
04
Customer processes break off
Answers, appointments and commitments slip, and your customers notice that first.
05
Risk grows inside the workaround
Quick fixes made under pressure tend to outlive the emergency and weaken security while they last.
Good server support therefore starts with a business question rather than a technical one: what stops working in your company the moment a central system is unreachable? Those dependencies are the first thing we map.
Server support that spots problems before they become one.
02Service
Server support as an ongoing job
Support does not mean waiting for a fault. It means watching systems, keeping them current, protecting them and documenting them so that others could work with what is written down.
Maintenance and updates
Operating systems, server roles and firmware stay in a maintained state. Updates are scheduled rather than improvised.
- Patch management for servers and services
- Agreed maintenance windows
- A check after every update
Fault resolution
When something fails, the route to help is short. Much is solved remotely, the rest on site in the region.
- Remote support as the first step
- On site visits across the Heinsberg district
- A report naming cause and remedy
Security
Running a server and protecting it are the same job. Accounts, permissions and protective systems are maintained alongside the service itself.
- Hardening of server roles
- Permissions and access reviewed
- Firewall and endpoint protection aligned
Backup
A backup only counts once the restore has been tested. The backup design is built around exactly that.
- Backups on an agreed schedule
- A further copy away from the server room
- Regular restore tests
Documentation
You know at any time what your IT consists of, how it is connected and who may reach what. That holds even when we cannot be reached.
- An inventory of systems and services
- Network diagram and responsibilities
- A traceable record of changes
Looking after an estate starts with knowing it. An engagement therefore begins with an inventory and ends not at handover but with documentation that is still accurate a year later.
03Infrastructure
A server never stands on its own
Workstations, network, firewall, server, backup and cloud are one connected whole. Looking after the middle box only is looking after half the estate.
Select a building block to see its role and its connections.
Desktops, laptops and printers are where faults are noticed first. They are also the most common way in for malicious software.
Passes on to Network
Cabling, switches and wireless tie everything together. A cleanly built network is what allows a server to feel fast in the first place.
Passes on to Firewall and server
It separates the internal network from the internet, governs access from outside and is where remote connections end in a controlled way.
Passes on to Server
Data, applications and user accounts live here. The server is where availability, backup and permissions all meet.
Passes on to Backup and cloud
A backup is not a copy sitting next to the original. It is a separate route out of the running system that still holds when the original is damaged.
Passes on to Restore
Mailboxes, file storage and collaboration often sit partly on site and partly in the cloud. Both sides have to follow the same rules.
Passes on to Workstations
Monitoring watches the server, the network and the services. It produces the alert that lets support become anticipatory at all.
Passes on to Support
A schematic model, not a survey of a customer network.
04Protection
Server support without security is only half done
A well maintained server left open to the internet is not a well maintained server. Operation and protection are planned together.
Wasacon works with established products and follows GDPR requirements while taking its bearings from BSI baseline protection. There is no such thing as absolute security and nobody should promise it. What there is: layers of protection that support one another, and an operation that notices when one of them gives way.
Firewall and network edge
Access from outside runs through the firewall under control. Rules are maintained rather than set once and forgotten.
Endpoint protection
Servers and workstations are protected by software whose alerts somebody actually reads.
Updates
Known weaknesses are the most common way in. Scheduled updates close them before they are used.
Access and permissions
Everyone reaches what their job needs. Accounts of leavers are closed and remote access carries an extra layer.
Backup as the fallback
A tested backup is the answer to the case in which every other layer turned out not to be enough.
Alert colleagues
Technology helps when the people in front of it know how to recognise a suspicious message. Wasacon offers training for that.
05Backup
A backup that holds when it matters
A backup proves its worth when data comes back, not when it is written. That is why the design does not stop at the copy.
The live system
Servers, applications and files in daily use. The starting point whose state is captured.
Backup on a schedule
Backups run to a schedule that fits how you work, and every run is checked for success.
A copy off site
At least one copy sits away from the original, so that fire, theft or encryption cannot take both at once.
Verification
Backups are tested for readability. A backup nobody has ever restored is an assumption.
Restore
The practised way back into operation, with an agreed order for which system has to be running first.
06Cloud
On site, cloud, or both
Many businesses in the Heinsberg district now work in a mixed setup: the server in the building, mailboxes and collaboration in the cloud. Joining the two cleanly is part of server support.
Microsoft 365
Mailboxes, file storage and collaboration looked after, with user accounts and licences kept in view.
Hosting
Services that do not need to sit in your own server room run in a managed hosted environment.
Hybrid environments
A local server and the cloud work together, with accounts, permissions and backups aligned across both.
Moving to the cloud
A move is planned, carried out in stages and accompanied, so that the business keeps working throughout.
- Technology in use
- Microsoft 365
- Microsoft Azure
- Sophos
- UniFi
- Veeam
- DSGVO
- BSI-Grundschutz
07System overview
What ongoing support makes visible
Support means being able to answer at any time how the systems are doing. An overview of that kind looks like this.
Example system overview
Servers
running
Reachability of the central systems and the services on them.
Load
as expected
Processor and memory within the expected range.
Storage
sufficient
Free space on the volumes with warning time instead of surprise.
Backup
completed
The last backup run finished and was checked.
Protection
active
Firewall and endpoint protection reporting as intended.
Updates
scheduled
Pending updates with an agreed date.
This panel is an example. It shows no values from any customer system and is not connected to a monitoring service.
08In practice
Infrastructure in practice
Server support happens on equipment you can put your hands on. A few impressions of what that involves.
Select an image to view it enlarged.
09Process
Not just reacting, but looking after
Server support is not a project with an end date. It runs as a cycle in which every round improves the next.
-
01
Analyse
An inventory of the systems in place, their dependencies and the points where things go wrong today.
-
02
Structure
What has simply grown gets sorted: clear responsibilities, tidy accounts, documentation that can be followed.
-
03
Protect
Layers of protection and the backup are put in place and tested before routine operation starts.
-
04
Support
Monitoring, maintenance and support in day to day operation, with one named contact.
-
05
Improve
What we notice feeds back into planning. Capacity, processes and protection are sharpened.
The cycle then begins again.
10Audience
Who this is built for
Wasacon looks after small and medium sized businesses. Companies that depend on IT that works but do not want to run an IT department of their own.
Mid sized companies
Businesses with IT that has grown over time and need reliable operation rather than a series of rescues.
Trades businesses
Firms whose job handling, time recording and stock control all hang from the central system.
Medical practices
Organisations with particular requirements around data protection, availability and recorded access.
Law firms and offices
Professional services where confidentiality and cleanly governed access are part of the core business.
Retail and production
Businesses where a standstill on the central application is felt in the day immediately.
Growing companies
Firms whose IT should grow with the headcount instead of being improvised again each year.
11Region
From the Heinsberg district, for the Heinsberg district
Wasacon is based in Heinsberg and looks after businesses in the region. In server support short distances are not a detail, they are the difference between a remote session and a wait.
A great deal can be solved remotely. When hardware has to be swapped, a line checked or a system restarted in the building, distance is what counts. Wasacon states a travel time of around 60 minutes for Heinsberg, Erkelenz, Hückelhoven and Wegberg.
Towns served
- Heinsberg
- Erkelenz
- Hückelhoven
- Wegberg
- Geilenkirchen
- Wassenberg
- Gangelt
- Linnich
On site in around 60 minutes in Heinsberg, Erkelenz, Hückelhoven and Wegberg.
12 Wasacon
Why Wasacon
Regional IT support with a named contact, a clear focus on security and the ambition to notice a problem before the phone rings.
Wasacon is an IT service provider in the Heinsberg district and looks after small and medium sized businesses, from network and server management through IT security and cloud to backup and support. You are not talking to a rotating help desk but to one contact who knows your environment.
For day to day operation Wasacon states a response time of under four hours. That commitment applies to customers with a support contract and an agreed service level. Contract customers also have access to the Fast Help emergency service.
Local presence
A provider from the Heinsberg district who genuinely comes out when that is what is needed.
A named contact
Direct communication with no detours, instead of explaining it all again each time.
Security as the foundation
IT security is a dedicated focus at Wasacon rather than an extra at the end.
Anticipatory, not reactive
Monitoring and maintenance exist to avoid faults, not only to repair them.
Predictable support
Support packages make the effort calculable instead of dependent on the next incident.
The whole picture
Server, network, backup, cloud and workstations are looked at together.
13Questions
Common questions about server support
What businesses in the region usually want to know before starting.
Monitoring of the systems, maintenance and updates, protection, backup, fault resolution and documentation that somebody else could work from. The exact scope is agreed in advance and follows your environment.
Wasacon states a response time of under four hours. It applies to customers with a support contract and an agreed service level. A great deal is resolved considerably faster over a remote session, because no on site appointment is needed.
Yes. It starts with an inventory of the systems in place. Routine operation is then taken over and the environment tidied step by step, rather than everything being changed at once.
No. Whether local, hosted or mixed with cloud services depends on your applications, your data protection requirements and your internet connection. That question belongs at the start, not at the end.
To a schedule that fits how you work, with at least one copy away from the server room and with regular restore tests. A backup that has never been restored is an assumption rather than protection.
That is the aim. Inventory and documentation run alongside normal operation, and work on central systems is done in agreed maintenance windows.
Among others Microsoft 365 and Azure for cloud and collaboration, Sophos for endpoint and network security, UniFi for wireless infrastructure and Veeam for backup. The solutions are GDPR compliant and take their bearings from BSI baseline protection.
That depends on the size of your environment and the scope agreed. Wasacon works with monthly support packages so the cost stays predictable. The first conversation is free of obligation.
14Contact
Request server support
Describe your environment briefly and what is going wrong at the moment. You will get an assessment and a proposal for the next step.
Telephone +49 2452 860 83 73
Email info@wasacon.com
Address Am Diebsweg 22, 52525 Heinsberg
Availability Monday to Friday, 09:00 to 18:00
Useful for the first conversation
- How many servers and workstations are in use
- Which central application matters most
- Whether backups run today, and where to
- What last went wrong