Linux infrastructure · practical answers
What should Linux server maintenance include?
Scope and starting price
Choose the relevant service below. We confirm the systems covered, checks and final price before work begins. Additional work and third-party costs need to be included in the agreed quote.
Linux Server Support & Maintenance
From £99/month
Scoped ongoing monitoring, security updates, tested backups and troubleshooting for a small-business Linux server.
Linux Support servicesBackup Verification / Restore Testing
From £79
A separately scoped restore check where existing backup evidence needs to be established.
Backups & Recovery servicesKnow what is being maintained
Start with an inventory of the operating system, important services, storage, administrative access and backups. Identify which applications belong to a separate developer or supplier. This avoids a support gap where everyone assumes someone else owns a failing part of the system.
The agreement should distinguish recurring checks from new projects. Adding a server, moving hosting or upgrading an application across major versions may need a separate quote rather than silently becoming routine maintenance.
Plan updates around the service
Ubuntu documents that updates can require service restarts or a reboot before all changes take effect. It also provides controls for automatic update and restart behaviour. The maintenance approach should account for those effects on your workload.
Decide when changes can take place, what should be checked afterwards and how access will be recovered if the machine does not return normally. A successful package update is one check; the business application still needs to work.
Technical reference: Ubuntu Server: automatic updates, reboots and service restarts
Make routine work visible
Agree what records will be provided: completed maintenance, failed backup jobs, capacity concerns and items needing a business decision. A short record of unresolved issues is more useful than a generic healthy label.
Coverage, frequency, response arrangements and any out-of-hours work must be confirmed in the agreement. The advertised starting price does not define an emergency response time or unlimited changes.
Is this the right fit?
A good fit when
- A small-business Linux server needs an identified owner for routine technical care.
- You want maintenance and backup checks to be planned rather than left to memory.
Limits of the scope
- The starting arrangement does not imply continuous staffed monitoring, guaranteed uptime or a fixed response time.
- New deployments, major migrations, third-party charges and application development need explicit agreement.
What to prepare for an enquiry
- Server count, Linux versions, hosting location and a list of important services.
- Current maintenance and backup arrangements, including anything already handled by another supplier.
- Business hours, acceptable interruption windows and the person who can approve changes.
Start with a description and non-sensitive examples. Leave out passwords, API keys, private keys, recovery codes and customer data. Access arrangements are agreed separately if the work needs them.
Common questions
Are updates alone enough?
Updates are one part of maintenance. The agreement should also address the services people use, storage, failed jobs, backup evidence and outstanding issues.
Are backups included?
The maintenance catalogue includes tested backups within the agreed scope. Confirm what is backed up, where copies are kept, the restore checks and any storage charges before starting.
Is emergency support included?
Do not assume an emergency response commitment from the starting price. Coverage, contact routes and response arrangements must be agreed for the particular service.
Related answers
Cybersecurity
How do I improve the security of a Linux server?
Backups & reliability
How can I tell whether my backups will restore?
Backups & reliability