Updating a server without downtime

A server must not be left without updates, yet every update risks taking the site down. The risk is managed with a process: small security fixes are installed automatically, major changes follow a plan with a snapshot, testing and a ready rollback, and reboots are grouped into a maintenance window. Here is how to set this up on a single VPS.

Updated 07.11.2026 · Find a VPS for your needs →

Server updates come in two kinds, and they need to be handled differently. Security fixes are released often, change little and almost never break anything, so it is best to install them automatically on the same day. Planned upgrades, such as a new version of the operating system, PHP, the database or the panel, change how programs behave, so they are prepared and tested. Downtime is most often caused not by an update as such but by a major change being installed as if it were a minor one.

Automatic security updates

On Ubuntu Server, the unattended-upgrades package is installed and enabled by default: once a day it installs security updates only, and the other origins in /etc/apt/apt.conf.d/50unattended-upgrades are commented out. The frequency is set in 20auto-upgrades, and the log is written to /var/log/unattended-upgrades/. Debian uses the same package, but a minimal installation may not include it; how to enable it is described on the Debian Wiki page.

On AlmaLinux and other RHEL-compatible systems, the same job is done by dnf-automatic. By default it does not install updates: in /etc/dnf/automatic.conf you set upgrade_type = security and apply_updates = yes, and then enable the dnf-automatic.timer timer.

Neither tool reboots the server by default. That is the right behaviour: a server should not restart at peak time. But the reboot must not be forgotten either, because an updated kernel and libraries only take effect after a restart. On Ubuntu and Debian, the file /run/reboot-required signals that a reboot is needed; on AlmaLinux, the command dnf needs-restarting -r does. It is worth adding this check to your server monitoring and doing the reboot itself in a maintenance window.

A snapshot before a planned upgrade

Before any major change, take a disk snapshot in the host's control panel. If the upgrade goes wrong, it returns the server to its original state within minutes. According to the accsly.io catalog as of November 2026, backup terms are described by 1,644 of 2,247 VPS hosts, and 318 of them explicitly mention snapshots. If your host does not offer snapshots, you need a full backup before the upgrade, one that you have already verified by restoring it.

Two caveats. A snapshot is usually stored in the same place as the server's disk and does not replace a backup: if the storage fails, both are lost. In addition, a snapshot of a running database may be inconsistent, so before taking it you dump the database or briefly stop writes. How to build a complete backup setup is explained in the article VPS backups: strategies and tools, and plans with space for backups are on the page VPS for backups.

Blue-green and rolling updates on a single VPS

Zero-downtime techniques come from large systems with several servers behind a load balancer: blue-green keeps two complete copies and switches traffic from one to the other, while a rolling update takes servers out of service one at a time. On a single VPS, the same ideas apply to the application, though not to the operating system itself.

  • Release directories. Each version of the site is deployed to its own directory, such as releases/2026-11-07, and the web server points to a current symlink. The new version is prepared alongside (dependencies, build, cache), and then the link is switched with a single command. Rolling back means pointing the link at the previous directory.
  • Two application instances. The new version is started on another port or in another container, checked, and then nginx is switched over to it. Reloading the nginx configuration does not drop connections: according to the nginx documentation, the master process first checks the configuration and keeps running with the old one if there is an error, while the old worker processes finish serving their clients. Still, run nginx -t beforehand. How to run applications in containers is described in the article Docker on a VPS: getting started.
  • Backward-compatible database migrations. While both versions are running, the database has to work for both. So schema changes are split into steps: first add the new columns and tables, deploy the code that uses them, and remove the old ones only in the next release.

Upgrading the operating system itself to a new major version cannot be done without downtime on a single server. It is more reliable to set up a second VPS with the new system, move the site to it, test it and switch DNS, having lowered the records' TTL in advance; how to do this is explained in the article Domains and DNS for a server owner. For the duration of the move, it is convenient to take the second server with hourly billing. How to choose a system version so that such moves happen less often is covered in the article Linux distributions for a server: Ubuntu, Debian, AlmaLinux.

Kernel updates without a reboot

Kernel live patching fixes critical vulnerabilities in the running kernel without rebooting the server. On Ubuntu, this is Livepatch, part of the Ubuntu Pro subscription, which is free for personal use on up to five machines. RHEL-compatible systems have their own mechanisms, including commercial services.

The technology has its limits. Only functions that the kernel can trace can be patched, a restriction described in the Linux kernel documentation, so some fixes only arrive with a new kernel. Canonical states plainly that Livepatch does not replace scheduled reboots; it only lets you postpone them to a maintenance window. And most importantly for a VPS: only KVM virtualization gives you your own kernel. On OpenVZ and LXC the kernel is shared and the host updates it; more on this in the article KVM or OpenVZ: which to choose.

Maintenance window and rollback

A maintenance window is a time chosen in advance when traffic is lowest, usually night-time in your main audience's time zone, when reboots and planned changes are allowed. The time is taken from the site's analytics, not picked at random. If customers or employees use the site, they are warned in advance. The window is not only for you: the host also carries out maintenance, and how hosts announce it is covered in the article SLA and uptime: what hosts promise.

The rollback plan is drawn up before the work starts, not after something has broken:

  • define the failure signs in advance (errors in the logs, rising response times, a failed check of key pages) and a deadline after which you roll back instead of trying to fix things further;
  • for code, switch the symlink or nginx back to the previous release;
  • for packages, AlmaLinux has dnf history undo, which reverts the last transaction; Ubuntu and Debian have no built-in package rollback, so there you rely on the snapshot;
  • a snapshot restores the entire disk, and everything written after it (orders, messages, sign-ups) will be lost. That is why the site is put into maintenance or read-only mode for the duration of a risky upgrade.

After the update, check the key pages and error logs and compare response times with the usual figures. If you ran load testing before launch, the same scenario will quickly show after a major update whether the site has become slower.

FAQ

Is it safe to enable automatic updates on a server?

For security updates, yes: they change little and close vulnerabilities on the day they are released. Automatically installing everything, including new program versions, is not a good idea, and reboots are best done manually in a maintenance window.

Do I need to reboot the server after updates?

After updating the kernel and core libraries, yes; otherwise the old versions keep running. On Ubuntu and Debian, the file /run/reboot-required signals this; on AlmaLinux, the command dnf needs-restarting -r does.

Does a VPS snapshot replace a backup?

No. A snapshot is usually kept on the same storage as the server's disk and is meant for a quick rollback after a failed update. A backup should be stored separately, ideally with another provider.

Can the kernel be updated without a reboot?

Partly: live patching fixes critical vulnerabilities in the running kernel; on Ubuntu this is Livepatch. It only works on KVM, does not fix everything and does not replace scheduled reboots.

How do I update a website on a single VPS without downtime?

Deploy each version to its own directory and switch a symlink, or start the new version alongside the old one and switch nginx over to it. Make database migrations compatible with both versions.

How do I move to a new Ubuntu or Debian version without downtime?

On a single server, you cannot: an OS upgrade requires a reboot and may take a while. To avoid downtime, move to a second server with the new system and switch DNS.

Plans on this topic

KVM VPS/VDSVPS for a websiteVPS for an online storeVPS for DockerVPS for CI/CD runners

More in the guide

  • Hosting for a company website and domain mailA company website rarely gets heavy traffic, but it comes with staff mail on the domain, lead forms with personal data and an accounts department that needs invoices. Shared hosting covers all of this in one plan, provided you check the mail limits in advance, set up SPF, DKIM and DMARC and choose a host that works with companies. Below is what to look at and what it costs.
  • Hosting for a landing page or business card siteA landing page or a business card site does not need a powerful server or a VPS: the simplest shared hosting plan for a few dollars a month is enough. What matters more is that the plan includes free SSL, the domain stays yours and the page opens quickly on a phone. Below is how to choose a plan, what to check in it and what it costs.
  • How to choose hosting for an online shopA small shop on WooCommerce, OpenCart or 1C-Bitrix runs fine on a good shared hosting plan. Its requirements are stricter than those of a business card site, though: recent PHP and database versions, HTTPS on every page, headroom in the limits for sales and backups from which orders can be restored quickly. Below is what to check in a plan, what it costs and when it is time to move to a VPS.
  • A database on a VPS: PostgreSQL or MySQLA database is almost never limited by the processor; memory and disk are what hold it back. If the working set fits in the cache, queries are fast even on an inexpensive server; if it does not, disk speed decides everything. Here is how to choose between PostgreSQL and MySQL, how much memory to give the database, which disk to pick and how to avoid losing data.
  • File storage on a VPS: disks and object storageA project's files, such as user uploads, product photos, videos, documents and archives, grow faster than the database and the code. You can keep them on the server's disk, on a separate volume or in object storage, and the choice determines the price per terabyte, the speed and what happens to the files when you change servers. Here are the options and prices according to the accsly.io catalog.
  • How to leave a host without losing anythingPeople leave hosts for all sorts of reasons: prices went up, the server got slow, support stopped answering, or you need a different country. During a move you can lose data, emails, your domain and the money for months already paid. Here is an order of steps in which the old and new servers run side by side for a while, so that switching off the old one breaks nothing.
  • CI/CD on your own VPSA dedicated build server pays off when hosted CI minutes run out, builds are slow or jobs need access to internal resources. But a runner executes any code in the repository, so a mistake in its setup exposes the production server and every secret. Here is how GitLab and GitHub runners work, what resources they need, how to deploy over SSH and where to keep the keys.
  • Server logs and login auditingLogs answer three questions: what broke, who logged in to the server and what they did there. You only get an answer if logging is enabled, the logs are kept long enough and they are not stored only on the server that may have been compromised. Here is where to find logs on Linux, which commands show logins, how to set up rotation and what to do in advance so that there is something to investigate after an incident.
  • VPS for developers: staging environmentsA staging environment exists so that you find the bug before your customers do. It should match the production server in software and configuration, but it can have half the resources and live for just a few days. Here is how to keep staging cheap, how to run several versions on one server and how to make sure a copy of the site does not end up in search results or send emails to real customers.
  • Linux distributions for a server: Ubuntu, Debian, AlmaLinuxFor a server, the choice is most often between three free distributions: Ubuntu, Debian and AlmaLinux. All three are stable and suitable for a website or a bot; they differ in how long they are supported, in their packages and in which panels and programs officially run on them. According to the accsly.io catalog as of November 2026, all three images are offered by 631 of the 1,241 hosts whose template list is known.
  • Load testing a website before launchA load test answers two questions: how many visitors a site can handle on the chosen server and what breaks first. It is run on your own server and only there: the load generator is a separate machine, the host has been notified and external services are replaced with stubs. Here are the numbers to watch, the tools that produce them and how to use them to choose a plan.
  • CDN: when a website needs oneA CDN stores copies of a site's files on servers around the world and delivers them to each visitor from the nearest one. This speeds up loading of images, scripts and video and takes load off your server, but it does not make a slow CMS faster and does not replace choosing the right country for your server. Here is when a CDN is really needed and when a single VPS in the right place is enough.
  • Domains and DNS for a server ownerYou can switch servers in an evening, but a domain stays with a project for years. Through DNS, the domain points to your server, your mail and third-party services, and a single wrong record can take the site offline or send your emails to spam. Here are the records a VPS owner will need, how caching works, where to keep the zone and how to move to a new server without visitors noticing.
  • SSL certificates: free and paidA free certificate encrypts the connection just as reliably as a paid one: browsers make no distinction between them in terms of security. The difference lies in what the certificate authority checks, how long the certificate lasts and who is responsible for renewing it. According to the accsly.io catalog as of November 2026, free SSL is explicitly listed in 1,449 shared hosting plans from 178 hosts. Here is when that is enough and when a certificate is worth paying for.
  • 152-FZ and hosting: where to store the dataIf a website or service collects personal data of Russian citizens, that data must be recorded and stored in databases located in Russia: this is Part 5 of Article 18 of Federal Law No. 152-FZ. For choosing a VPS, this means the data centre's country matters, not the host's, and copies abroad fall under separate rules. Here is what the law requires, what duties fall on the server owner, how it applies to companies outside Russia and which setups are used in practice.
  • GDPR and choosing a hostThe EU General Data Protection Regulation (GDPR) does not require data to be kept in the EU, but it does require a data processing agreement with the host and a lawful mechanism for any transfer of data out of the EU. According to the accsly.io catalog as of November 2026, 61% of VPS hosts have servers in the EU, but almost half of them are registered outside the European Economic Area. Here is why that matters and what to check in the terms.
  • Hosting provider jurisdiction: what it affectsEvery server has two countries: the one where the data centre stands and the one where the company renting it out is registered. According to the accsly.io catalog as of November 2026, these are different countries for 15% of VPS hosts. The first determines latency and the rules on where data is stored; the second determines the law of the contract, the court for disputes, the documents your accountant receives and whose authorities can request your data. Here is what each of them changes.
  • How to compare VPS prices: the price of a resource unitA plan's price tells you how much you will pay, but not how much you get for that money. According to the accsly.io catalog as of November 2026, a gigabyte of memory on a 1 GB plan costs a median $8.00 a month, while on a 4 GB plan it costs $5.00. Here is how to work out the price per vCPU, per gigabyte of memory and of disk, and what to bring to a common basis before you compare two offers.
  • SLA and uptime: what hosts promiseAn SLA of 99.9% allows a host 43 minutes of downtime a month, 99.99% about four. But a percentage in an advert is not yet a commitment: the commitment is the document that says what counts as downtime, what is excluded and how much you get back. Most often that is a discount on the next invoice, not money. Here is how to read such documents and how to check availability yourself.
  • Free trials and money-back guaranteesThere are two ways to test a server before paying for a month or a year: a free trial or a money-back guarantee. According to the accsly.io catalog as of November 2026, 11% of VPS hosts offer a trial and 36% a money-back guarantee. But at many of them the terms apply only to shared hosting, only to the first order or only to card payments. Here is what to check so that the guarantee actually works.
  • Cloud server or VPSA cloud server and a VPS are usually the same KVM virtual machine. The difference lies in what surrounds it: a cloud sells resources by the hour through an API and offers network disks, snapshots and ready-made services, while a classic VPS is a fixed monthly plan with a local disk and a traffic allowance. Here is which of this you actually need and what it costs.
  • Dedicated server or VPSA VPS is a slice of a physical server, a dedicated server is the whole machine. With 4 cores and 8–16 GB of memory a VPS costs almost half as much, with 4 cores and 32 GB the prices are equal, and with 64 GB on 8 cores or 128 GB on 16 cores a dedicated server in the catalog is a third cheaper than a virtual one. Here is what else changes besides the price: neighbours, guarantees, delivery time, hardware failures and remote management.
  • Shared hosting or VPS for a websiteShared hosting is a ready place for a site where the host looks after the server. A VPS is your own server where you set everything up. For a landing page or an ordinary WordPress site, hosting is enough and costs several times less. You need a VPS when the account limits are too tight for the site or when it needs software that hosting does not allow. Below is what each option includes, what it costs and a table to help you choose.
  • DDoS protection: what hosting providers actually give youEvery second host now lists "DDoS protection" in its plans. Behind that line there may be multi-terabit filtering, or only the right to take your address offline when an attack bothers the neighbours. Here is what protection is made of, how L3/L4 differs from L7, and how to tell from the contract what you are buying.
  • Mail server on a VPS: SPF, DKIM, DMARCInstalling Postfix or a ready-made bundle like Mailcow on a VPS takes an hour. Getting your mail into the inbox rather than spam is harder: mailbox providers look at the port, the server's address, its reputation and three DNS records. Here is what to check with the host before buying and how to set up SPF, DKIM and DMARC.
  • Server monitoring: uptime, load, alertsWithout monitoring you learn that the server is down from your visitors, and that the disk is running out when the database stops writing. A few checks from outside and a dozen metrics from inside are enough to see a problem before users do. Here is what to measure, where to run checks and how to do it for free.
  • How to read hosting plans: the hidden limitsA plan card shows cores, memory, disk and a monthly price. Yet two plans with identical numbers can cost different amounts a year later and behave differently under load. The difference lies in terms printed in small type, in the acceptable use policy, or only in the contract. Below are eight places worth checking before you pay.
  • IPv4 and IPv6 on a serverA typical VPS has one public IPv4 address and, if the host supports it, an IPv6 subnet. An extra IPv4 address almost always costs money, and the cheapest plans sometimes come without their own IPv4 at all. Here is where the shortage comes from, what you can do with IPv6 alone and which address settings a mail server needs.
  • Bandwidth and traffic: what 1 Gbps and unlimited really meanA server plan usually has two network lines: port speed and traffic volume. The first says how fast the server can send data, the second how much it can send in a month. They are linked by simple arithmetic, and once you know it, it is easy to see what "1 Gbps unlimited" actually offers and whether "5 TB" will be enough for you.
  • Docker on a VPS: getting startedDocker lets you run a bot, a website, a database and monitoring on one server without them getting in each other's way, and moving to another VPS comes down to copying a couple of files and the data. Installation takes five minutes; the real trouble starts later: database ports exposed to the internet, logs growing to tens of gigabytes and data that vanished along with a container. Here is how to avoid all of that from the start.
  • How to move a website from shared hosting to a VPSThe move itself takes a couple of hours; the mistakes usually happen around it: a forgotten cron job, .htaccess rules that nginx does not read, an AAAA record with the old address, or mail that disappeared along with the IP change. Below is the order of steps with commands and checks for a PHP and MySQL site.
  • Server control panels: ISPmanager, FASTPANEL, aaPanelA panel turns a VPS into the kind of dashboard you know from shared hosting: sites, databases, mail and certificates are set up with a few clicks instead of editing config files. The three panels most often installed on Russian and budget international servers are ISPmanager, FASTPANEL and aaPanel. They differ in price, memory requirements and how much of the server they take over.
  • Windows VPS for 1CA rented server for 1C saves you from the office PC under a desk that nobody updates or backs up. But 1C on a VPS has its own quirks: the software licence is tied to the parameters of the virtual machine, users need both 1C and Windows licences, and core speed matters more than core count. Here is how to put together a 1C server for a small company.
  • Windows VPS: licensing, RDP and secure sign-inA Windows server costs more than Linux not only because of memory: the price includes a licence, and how it is arranged decides whether you are compliant and how many people can connect. An exposed RDP port is also the most common way such servers get hacked. Here are both topics.
  • When to move from shared hosting to a VPSA VPS does not make a site faster by itself: it gives you resources and freedom, and with them the job of running a server. Here is how to tell that hosting has become too small, when the problem can be solved without moving, and how to migrate a site so visitors notice nothing.
  • VPS backups: strategies and toolsOn a VPS, backups are your job, even if the plan says "backups included". We go through what exactly to back up, why a host snapshot is not enough, how to set up restic or BorgBackup in half an hour, and how to make sure you can actually restore from a backup.
  • First 10 steps after buying a VPS: securityBots start guessing passwords on a new server within minutes of it getting a public IP. Below are ten steps that close the most common holes in about an hour: commands for Ubuntu and Debian, the differences for AlmaLinux and Rocky Linux, and the checks that keep you from locking yourself out of your own server.
  • How to choose a country for your serverPut the server where your visitors are. For an audience across Europe, Germany, the Netherlands and Finland are convenient; for North America, the US East Coast. If you serve EU users, keeping the data in the EU makes GDPR simpler. Price hardly decides it: at the same host a server in Frankfurt, Amsterdam or New York usually costs the same, and only Asia and Australia are noticeably more expensive.
  • Hourly billing: when it pays offHourly billing pays off if you need the server for less than three weeks a month: for a test, a build, a one-off heavy job. At most hosts an hour costs exactly the monthly price divided by 730 hours, so over a full month you hardly overpay. The overpayment hides elsewhere: hourly plans are dearer on average, and for a server that runs all year, monthly billing or a year paid in advance usually comes out cheaper.
  • How much RAM and how many cores a website needsMost websites are fine with 2 GB of memory and one or two cores; a shop with thousands of products needs 4 GB and two cores. Memory matters more than cores: when it runs out, the site slows down or crashes, while an extra core without memory adds almost nothing. Below I show how to work out the memory for your site and how to see what it actually uses.
  • KVM or OpenVZ: which to chooseIn 2026 KVM is almost always the right pick: it costs a dollar or two more per month than OpenVZ, but everything runs on it, from Docker to Windows. OpenVZ makes sense in one narrow case, explained below, and at the end you will find the commands to check your own server in a minute.
  • NVMe or SSD: does it matter for a websiteFor a small site the difference between NVMe and SSD is barely noticeable, because pages are served from memory rather than from disk. It shows up in shops and sites with a large database. At the same host NVMe costs only about $0.50–1 a month more, and sometimes less, so what usually decides it is not the disk type but its size and how the host has limited it.
  • What is a VPS, in plain EnglishA VPS is a slice of a powerful physical server that you rent and that behaves like a separate computer, with its own operating system, its own IP address and full control. Below is how it differs from shared hosting, who needs one, what it costs and what to check right after you buy it.
  • VPS for a Telegram bot: what the bot needs and how to pick a planA bot with a menu and a few commands runs fine on the cheapest server, while a bot with broadcasts, files and a database hits completely different limits. Here is what a bot really consumes, which Telegram limits shape the choice of server and how to avoid overpaying.
  • How to test VPS ping and speed before you payThe numbers in a plan do not tell you the latency to your users or how fast the disk really is. Most of this can be measured before you pay, the rest in the first hour after launch. Here are the tools and how to read the results.
  • Corporate network on a VPS: remote access to the officeA rented server can become the hub of a company's private network: remote employees and branch offices connect through it to the ERP, file server, CRM and Git. Here are the common layouts, protocols, server requirements and security basics.
  • How to choose a VPS: the 7 specs that matterTwo plans with the same "2 cores, 4 GB, 50 GB" can differ several times in speed and twice in price a year later. Here is what stands behind each line of a VPS plan and what to check before you pay.
  • VPS vs VDS: is there a difference and what actually mattersIn most markets VPS and VDS mean the same thing: a virtual server. The difference that really affects your work is hidden not in the name but in the virtualization type and whether resources are guaranteed.