Servers · Virtualisation · Administration
Build server and virtualisation environments that fit.
School platforms, applications and file storage need a suitable technical foundation. We plan and maintain server and virtualisation environments around existing services, resources and ongoing operational needs.
Understand services and dependencies
Which applications run on which systems? Where is data stored, and which services support sign-in or teaching? We assess the existing environment, including networks, storage and backups.
Requirements determine capacity, structure and priorities. Planning involves more than the load on an individual server: growth, maintenance and the order of a possible recovery also influence the design.
Server architecture
Understand dependencies across the layers.
Changes to a shared resource can affect several services. This overview makes the relationships visible.
Services
Applications & data
School platform, applications and file storage with their dependencies.
Virtualisation
Virtual machines & platform
Choose Hyper-V, Proxmox or VMware to suit the environment and support requirements.
Infrastructure
Hosts, storage & network
Shared resources determine capacity and affect maintenance and recovery.
Plan backup across all layers: required data, system configurations, access and the order in which services are restored.
Choose an appropriate platform
We work with Hyper-V, Proxmox and VMware. The choice depends on existing equipment, applications, support and administrative requirements. Existing expertise and licences form part of that decision.
Virtualisation brings several systems onto shared hardware and simplifies some administrative tasks. It also creates dependencies on hosts, storage and networking. These need to be planned alongside the individual virtual machines.
- Plan servers and required resources
- Set up and configure the virtualisation environment
- Account for network and storage connections
- Document the technical structure and responsibilities
Migrate in clearly defined steps
Before a changeover, we assess the source environment and establish which systems will be transferred, rebuilt or retired. Backups, available access and necessary preparatory work are part of the process.
The proposed migration is tested as appropriate for the environment. We agree the changeover window, checks and a possible return to the previous state. Required applications and connections are checked after the migration before ongoing operations are handed over.
Administration and changes during operation
New applications, growing data volumes and software updates change the demands on an environment. We support agreed server administration, configuration and troubleshooting, and record significant changes.
Maintenance requires an overview of the services affected. We agree which systems will be worked on, in what order, and who will assess the potential impact on teaching or administration. This puts technical changes in the context of everyday operations.
Include backups and networking in the plan
A virtual machine alone does not provide a recovery plan. Data and configuration backups, required access and the order in which services should be restored all need to be established.
Network connections and sufficient storage capacity are also part of the environment. We coordinate these tasks with server planning so that technical responsibilities and dependencies remain clear.
Questions about server environments
Does an existing virtualisation platform need to be replaced?
Not necessarily. We assess its condition, support, available resources and application requirements. This establishes whether maintenance, expansion or a change of platform is appropriate.
How is downtime considered during migration?
Potential interruptions depend on the applications, data and migration method. We assess these dependencies and agree a suitable changeover window and subsequent checks.
Can you administer an existing environment?
Yes. We establish the available documentation, access, software and licensing status, and existing responsibilities. These provide the basis for agreeing the scope of support.
Which server services need to change?
Your existing platform, applications and planned changes help us establish the scope of support or migration.