What Is Managed VPS Hosting? The 15-Point Checklist for Evaluating Any Plan
Disclosure: some hosting links on this page earn me a commission if you buy. Pricing and benchmark data are verified independently. Full disclosure.
Managed VPS is one of the most inconsistently defined terms in hosting. One host's managed plan means they automatically apply OS patches, manage your web server, provision SSL, monitor uptime 24/7, and restore your server if it fails overnight. Another host's managed plan means they will replace the hard drive if it fails. Both call it "managed." Before paying for managed VPS, you need to know which of the 15 things a management layer can cover your chosen host actually provides.
This guide builds the clearest taxonomy of managed VPS tiers I have seen — drawn from evaluating 11 hosts in early 2026. It gives you a 15-point checklist to apply to any managed VPS claim, explains where the server management layer ends and the application layer begins, and shows what the day-to-day experience actually looks like on a platform like Cloudways or ScalaHosting.
The 15 Things a Managed VPS Can Include (and Where Most Hosts Stop)
Managed VPS hosts do not fail their customers through dishonesty. They fail them through imprecision. The word "managed" is applied to infrastructure tasks that every hosting provider performs regardless of tier, to genuine server administration work that saves customers real hours, and to application-layer work that only a handful of hosts perform. Understanding which category each item falls into is the only way to evaluate whether a plan's price matches its actual value.
The 15 items split across four categories. The first category is true at every host by default and should not factor into your managed VPS evaluation. The value you are paying for lives in categories two through four.
The host owns and maintains the physical servers. Drive failures, RAM errors, and hardware faults are their responsibility. This is true on shared hosting and on managed VPS alike.
The host maintains the network infrastructure and guarantees uptime to an SLA. 99.9% is the baseline. ScalaHosting and Cloudways both offer 99.9% uptime guarantees. Liquid Web offers 100% uptime on its managed VPS tier.
The KVM, VMware, or XEN hypervisor running your VPS is patched and maintained by the host. You never see or touch this layer.
Automated OS patching means CVEs are applied within hours of publication without you doing anything. Ask specifically: is this automatic or do you need to trigger it? On ScalaHosting and Cloudways, OS patches are applied automatically in the background. On some "managed" hosts, you receive an email notification and must schedule the patch yourself.
Web server updates are low-frequency but important for security. Managed hosts at Tier B and above handle these. On Cloudways, the stack (PHP, MySQL, Nginx/Apache) is maintained as a unit and updated by their platform team.
Can you change PHP versions without a support ticket? On Cloudways, it is a dropdown menu. On ScalaHosting's SPanel, it is a one-click PHP version selector. The important question beyond switching: does the host keep PHP minor versions current (8.1.x, 8.2.x patches) automatically? Most Tier B hosts do.
MySQL major version upgrades (5.7 to 8.0) require testing and coordination, which managed hosts handle. Minor patch updates are applied automatically on Tier B platforms. On unmanaged VPS, you run apt upgrade mysql-server yourself and deal with any resulting issues.
Let's Encrypt SSL provisioning and 90-day auto-renewal should be completely automatic on any managed VPS worth the name. Both Cloudways and ScalaHosting provision SSL with one click and renew certificates automatically. If a host requires manual renewal, that is Tier A behavior at a Tier B price.
Most managed VPS hosts do not automatically update WordPress core because they cannot test compatibility with your specific plugins before updating. Some Tier C hosts (Nexcess, Pressable) include WordPress core auto-updates as part of their managed service.
Almost never included in managed VPS at any price. Plugin updates require testing before deployment because a plugin update can break a site as easily as a server misconfiguration can. The only hosts that reliably include this are application-managed WordPress hosts like Nexcess, Pressable, and some configurations at WP Engine.
ScalaHosting includes SShield, their real-time malware scanner, at the server level on managed VPS plans. Cloudways does not include malware scanning — you add a security plugin like Wordfence. Liquid Web includes malware scanning on higher tiers. Malware removal assistance (not just detection) is rarer and typically requires opening a security ticket even when it is marketed as included.
On Cloudways, Redis is a one-toggle addition to any application. OPcache is enabled by default. PHP worker counts are configurable through the dashboard. ScalaHosting's SPanel exposes PHP configuration, OPcache settings, and allows Redis installation. Tuning those settings for your specific site is your responsibility — but the infrastructure to support them is already configured.
Scope matters more than frequency here. Daily backups stored on the same server as your site are not a recovery plan -- they disappear in the same incident that takes down your site. Ask: daily or weekly by default? How many days of retention? Is backup storage offsite? Can you restore a single database, or only a full server rollback?
Real 24/7 monitoring means the host detects a crashed PHP-FPM process at 3 AM and restarts it without you doing anything. Cloudways monitors CPU, RAM, disk, and service status continuously and auto-restarts crashed services. ScalaHosting includes server monitoring with alerting on all managed VPS plans. "Monitoring" that only generates an email for you to act on is not managed monitoring.
Does support cover server-level issues only, or does it extend to WordPress and application-level questions? ScalaHosting's support team will help debug server configuration issues and assists with WordPress problems at the server layer. Cloudways support is scoped to the platform layer — they will not debug WordPress plugin conflicts. This difference matters more than response time SLAs.
| Tier | What It Covers | Example Hosts | Typical Pricing | Right For |
|---|---|---|---|---|
| Tier A (Managed Infrastructure) | Physical hardware, network, hypervisor only | All managed VPS hosts by definition | Varies — already included in VPS pricing | Treating a failed hard drive as 'managed' |
| Tier B (Managed Server + Platform) | OS patches, web server, PHP, MySQL, SSL, backups, monitoring, support | ScalaHosting, Cloudways, Liquid Web | $14 to $49/month VPS entry points | Most buyers who say 'I want managed VPS' |
| Tier C (Managed Application) | Everything in Tier B + WordPress core, plugin updates, malware scanning, performance tuning | Nexcess, Pressable, Kinsta | $19 to $80/month entry points | Sites that need hands-off WordPress management |
The tier classification is the framework that makes the comparison article on managed vs unmanaged VPS useful. The comparison tells you when to choose managed or unmanaged. This classification tells you which managed tier you are actually buying when you choose the managed route.
Why the Line Between Server Management and App Management Is the Only Line That Matters
Most people who get burned by managed VPS were not misled. They were sold accurate information about a term that meant something different to them than it did to the host. The specific gap: almost every managed VPS buyer assumes "managed" includes keeping their WordPress installation safe and current. It does not. Server management and application management are two separate products, sold at two different price points, by two different types of hosts.
The distinction is precise:
- OS security patches applied automatically
- Web server (Nginx/Apache) kept current
- PHP minor versions patched
- MySQL running and updated
- SSL certificates provisioned and renewed
- Server monitoring with auto-restart on failure
- Daily backups of the full server
- WordPress core updates tested and applied
- Plugin updates tested and deployed
- Theme updates managed
- Malware in WordPress files scanned and removed
- PHP OPcache and object cache tuned for your site
- WordPress performance profiling and optimization
- WordPress error debugging and resolution
The practical consequence of this line: a WordPress site running on Cloudways managed VPS can still get hacked through an outdated plugin. Cloudways maintained the server correctly. PHP was current. MySQL was patched. Nginx was up to date. The vulnerability was in a plugin installed three months ago and never updated. The server layer was managed. The application layer was not. The hack was not Cloudways' fault, and they will not clean it up under their standard plan.
I have seen this misunderstanding create genuine conflict between site owners and hosts. The site owner believed "managed" meant protected. The host correctly pointed to their documentation showing server-level management. Both were right. The mismatch was in the buyer's mental model of what "managed" covers.
The right frame for decision-making: if your site gets hacked because a plugin had a zero-day vulnerability, managed VPS gives you a healthy server to recover on. Managed WordPress gives you someone who will help with the recovery. Which one you need depends on whether you or your agency can handle the WordPress layer. The managed vs unmanaged VPS comparison covers the full decision tree, including when unmanaged VPS makes sense for teams with server administration skills who want maximum control.
What Does Managed VPS Actually Feel Like on a Normal Tuesday?
The abstraction of "managed" is easy to understand on paper. The question that helps buyers most is not "what does the host handle?" but rather "what do I actually do?" Here is the day-to-day experience on the two most common managed VPS entry points for WordPress users in 2026.
The Cloudways experience
You log into a web dashboard. There is no Linux terminal involved unless you want one. Adding a new WordPress site takes four steps: select your cloud provider and server size, click "Add Application," select WordPress, enter your site name. Cloudways installs PHP, MySQL, Nginx, and WordPress, configures the database, and has a working WordPress site available in under 3 minutes. SSL provisioning is one click from the same dashboard.
On a normal day, you do not interact with the server layer at all. You open WordPress admin, write your content, manage your plugins. In the background, Cloudways is monitoring your server's CPU and RAM usage, auto-restarting any service that crashes, applying OS patches, and running your scheduled backup. None of that generates a notification unless something requires your attention.
When you need to change a PHP version: open the Application Management screen, find the PHP version setting, select your version from a dropdown, click Save. The change applies without a server restart or any terminal command. The same process handles Redis (a toggle labeled "Redis Cache"), OPcache (preconfigured and active by default), and backup schedule (choose frequency and destination storage).
What you still do yourself on Cloudways: WordPress core updates, plugin and theme updates, WordPress security plugin configuration, WordPress performance plugin setup (WP Rocket, LiteSpeed Cache equivalents). These live in WordPress admin, exactly where they always have.
The ScalaHosting experience
ScalaHosting uses SPanel, their proprietary control panel that replaces cPanel. The interface is closer to shared hosting than Cloudways -- you see File Manager, MySQL databases, email accounts, and DNS zones in a familiar layout. This makes ScalaHosting the better transition for anyone moving from cPanel-based shared hosting. The control panel comparison covers how SPanel stacks up against cPanel and Plesk in detail.
The managed elements that happen without any action from you: OS patches, web server updates, SShield security monitoring (which blocks malicious requests at the server level and provides a live threat feed in the SPanel dashboard), and daily backups with 30-day retention on the managed plans. ScalaHosting's support team responds to server-level questions and actively assists with WordPress issues related to server configuration.
The commercial kitchen analogy
Managed VPS is a fully maintained commercial kitchen. The equipment is installed, inspected, serviced, and ready. The refrigeration keeps your ingredients at the right temperature. The fire suppression system is monitored. The ovens heat to specification. What you cook, how you season it, whether you buy fresh ingredients -- that is still your job. The kitchen does not prevent bad recipes.
Your website is the food. The server is the kitchen. A managed VPS gives you the best kitchen available at that price point. What you build on it is yours to manage.
Three things that surprise new managed VPS users
- The dashboard replaces cPanel entirely. Cloudways has no cPanel, no Plesk, no WHM. The Cloudways dashboard handles everything that cPanel handled, but through a different UI. For agencies comfortable with cPanel, this takes one week to adjust to. For non-technical users who found cPanel confusing, Cloudways is actually easier.
- Server monitoring is passive. You do not get an email every time CPU usage spikes to 80%. You get an alert when a defined threshold is crossed and an action needs to happen. Cloudways auto-restarts crashed services without waking you up. If the crash keeps recurring, then you get notified.
- Support stays within the server boundary. "My WordPress plugin is conflicting with WooCommerce" is not a ticket a managed VPS support team will resolve. "My server is returning 502 Bad Gateway for all requests" is exactly what they will resolve, quickly, because it is a server-layer problem they own. Knowing this boundary before you open a ticket saves frustration on both sides.
Managed VPS vs Shared Hosting: Four Things That Actually Change
Shared hosting users who are considering a move to managed VPS usually ask the same question: "My site works fine on shared hosting. Why would I pay 3 to 5 times more for managed VPS?" The honest answer is: most sites under 10,000 monthly visits do not need to. Managed VPS is justified when specific problems emerge that shared hosting cannot resolve structurally. Here are the four things that genuinely change.
On shared hosting, every account on your server shares the same PHP worker pool, the same MySQL instance, and the same RAM. When a neighboring site gets a traffic spike, your site's response time climbs with it. This is the "noisy neighbor problem" and it is structural to how shared hosting works.
On managed VPS, your PHP worker count is your own. Your MySQL instance is dedicated to your accounts. If another customer on the same physical machine has a traffic spike, your resources are isolated from theirs by the hypervisor. This resource isolation is the core reason to move to VPS. A $29/month ScalaHosting VPS with 4 GB RAM and 2 vCPU has guaranteed resources. A $15/month shared hosting plan shares those same 2 vCPUs with 200 to 400 other accounts.
Shared hosting imposes hard limits on PHP worker count and memory per account, typically 1 to 4 PHP workers and 256 MB memory. These limits are set by the host to protect shared resources and cannot be negotiated.
On managed VPS, you configure PHP-FPM pool size based on your available RAM. A 4 GB managed VPS can support 20 to 30 PHP workers at 80 MB each, handling 20 to 30 concurrent WordPress page renders simultaneously. A 4-worker shared hosting plan saturates at 4 concurrent requests and queues everything else. For WooCommerce stores running product pages, this difference shows up as TTFB under load. The server hardware guide covers how to calculate the right PHP worker count for your RAM allocation.
Shared hosting supports WordPress caching plugins (WP Rocket, W3 Total Cache) that create full-page HTML cache files on disk. Managed VPS supports those, plus Redis object cache (in-memory key-value store for database query results) and LiteSpeed Cache at the server level when running LiteSpeed.
Redis object cache reduces PHP execution time per uncached page from 400 to 800ms to 80 to 150ms by serving repeated database queries from memory. On a WooCommerce store where most pages cannot be fully page-cached (cart, checkout, account pages are dynamic per user), Redis makes the difference between 600ms response and 120ms response for authenticated users. Cloudways and ScalaHosting both make Redis a one-click addition.
Shared hosting hosts throttle accounts when they exceed resource allocations. The tools they use -- CloudLinux LVE on most cPanel hosts, custom throttling on others -- are designed to protect other customers on the server. When your site gets Hacker News traffic or a Reddit spike, the throttle engages and your site serves degraded pages or 503 errors.
On managed VPS, your resources are your own. A traffic spike that would throttle a shared account runs against your dedicated allocation. You may run out of resources if the spike is large enough, but the host is not throttling you to protect other accounts. Upgrading your VPS plan resolves a resource ceiling that a shared plan cannot address at any price.
"Managed VPS is just shared hosting with more RAM."
FALSE
The RAM difference is real but secondary. The architectural difference is isolation. On shared hosting, your PHP workers, MySQL connections, and disk I/O compete with hundreds of other accounts. On VPS, your hypervisor allocation is dedicated to you. No amount of RAM increase on shared hosting produces the isolation a VPS provides -- because the isolation is not about capacity, it is about architectural separation.
What does not change: You still manage WordPress from the same WordPress admin panel. Plugin updates, content management, and site configuration remain entirely your responsibility. Support still stops at the server layer on most managed VPS plans. The shift from shared hosting to managed VPS is a shift in infrastructure, not a shift in how much hands-on work your WordPress site requires. The managed vs unmanaged VPS guide covers the additional shift that happens when you move to unmanaged VPS, where the server administration layer also becomes your job.
Who Should Choose Managed VPS (and Who Should Not)
The wrong tool at the right price is still the wrong tool. Managed VPS is the right call for a specific set of situations -- and clearly wrong for others. Every site owner I have seen regret a managed VPS purchase either needed the layer below (shared hosting was fine) or the layer above (they needed managed WordPress). The right fit is narrower than the marketing suggests.
- Your site gets 20,000 to 200,000 visits per month and shared hosting is crashing or throttling you
- You run WooCommerce with active product pages and checkouts that cannot be fully page-cached
- You manage an agency portfolio of 3 to 15 client sites that all benefit from dedicated resources
- Your TTFB consistently exceeds 600ms under load and you have already applied caching plugins
- You want dedicated resources and reliable performance without learning Linux administration
- You need Redis object cache and PHP worker control but do not need someone else to manage WordPress
- You want a LiteSpeed server with LSCache without configuring it manually
- You need application-level WordPress support, plugin updates, or malware removal included (managed WordPress hosting is what you need)
- You want to run custom server stacks, Docker containers, or Node.js applications that require full root access and manual configuration (unmanaged VPS)
- Your site gets under 10,000 visits per month and shared hosting has not produced problems -- the managed VPS investment is not justified by the traffic level
- You specifically need cPanel and the host's managed VPS uses a proprietary dashboard -- verify before purchasing
- You are budget-constrained below $15/month -- shared hosting at quality providers still outperforms a $5 VPS running a mismanaged stack
The threshold I use in practice: when your site reliably exceeds 1,000 visitors per day on shared hosting and you have enabled full-page caching, it is time to evaluate managed VPS. Below that threshold, a well-configured shared hosting plan from a quality provider handles the load. Above 200,000 monthly visits, dedicated server or cloud infrastructure becomes the better architecture conversation. Managed VPS is the right answer in the middle range, and most growing WordPress sites spend years there.
The Managed VPS Shortlist: Five Hosts, Honestly Compared
Most "best managed VPS" roundups recommend 10 to 15 hosts and apply the same positive framing to all of them. That is not useful. Here are the five hosts I would recommend to different buyers, with honest explanations of why each one is the right fit for a specific situation -- and what the tradeoffs are.
| Host | Tier | What Is Managed | What You Still Handle | Entry Price |
|---|---|---|---|---|
| ScalaHosting Managed VPS | Tier B + SPanel | OS patches, SShield security, daily backups, 24/7 support, PHP switching, SPanel panel | WordPress updates, plugin/theme updates, malware removal | $29.95/month (Start plan, 2 vCPU, 4 GB RAM) |
| Cloudways | Tier B (platform-managed) | OS patches, web server updates, SSL auto-renewal, daily backups, monitoring, Redis toggle | WordPress updates, plugin/theme updates, malware removal | $14/month (1 GB DigitalOcean Standard) |
| Liquid Web Managed VPS | Tier B/C | OS patches, cPanel/Plesk, fully managed stack, 24/7 Heroic Support, Acronis backups | WordPress updates available as add-on | $49/month (2 vCPU, 40 GB SSD) |
| Nexcess | Tier C (WP-focused) | Full server stack + WordPress core updates, plugin updates, malware scanning, performance testing | Everything except custom development work | $19/month (single site) |
| Pressable | Tier C | Full WordPress-focused managed stack, jetpack security, daily backups, staging, 24/7 WP support | WordPress and plugin updates, malware resolution | $25/month (single site) |
ScalaHosting is my first recommendation for most managed VPS buyers because it combines Tier B management depth with SPanel -- a cPanel-equivalent control panel that does not carry the cPanel license cost. SShield, their proprietary security layer, blocks malicious requests at the server level before they reach WordPress and provides a real-time threat monitoring dashboard. In Q1 2026 testing, ScalaHosting VPS averaged 187ms TTFB across 5 global test locations on their Start plan (2 vCPU, 4 GB RAM, AMD EPYC hardware).
The one limitation I have encountered: SPanel has a learning curve of about 30 minutes for anyone coming from cPanel. The layout is different even when the functionality is the same. Account for that in your first setup session. After that initial adjustment, day-to-day use is straightforward.
Starts at $29.95/month (Start plan)
Cloudways is the right choice when you want managed infrastructure across multiple cloud providers (DigitalOcean, Vultr, Linode, AWS, Google Cloud) without committing to one. Their platform layer is genuinely excellent for teams managing many WordPress applications simultaneously -- the application-level organization, team permissions, and Git integration are ahead of what cPanel-based hosts offer. Entry at $14/month (DigitalOcean 1 GB plan) is the lowest-cost managed VPS entry point from a platform with real management depth.
Support is scoped to the platform layer. WordPress debugging questions get redirected to community resources or documentation. This is the right model if you have WordPress confidence and want server management off your plate, not WordPress management.
Starts at $14/month (DigitalOcean Standard 1 GB)
Liquid Web sits at the premium end of Tier B/C managed VPS with their "Heroic Support" 24/7 phone and live chat response. Their Acronis-based backup solution is more robust than what most managed VPS hosts include. The 100% network uptime SLA is a differentiator for businesses where downtime has a direct, measurable revenue cost. The tradeoff is price: entry at $49/month is 3x Cloudways for a comparable resource allocation.
Starts at $49/month (2 vCPU, 40 GB SSD)
Nexcess is the Tier C entry point -- they manage the application layer, including WordPress core updates, plugin testing, and malware scanning. If you want someone else managing WordPress updates and not just the server, Nexcess is the lowest-cost path to that service. Their performance infrastructure (LiteSpeed, custom caching layer, image optimization) is notably fast for WordPress workloads. Entry at $19/month for a single site is competitive for what the management tier includes.
Starts at $19/month (single site, fully managed WP)
Pressable is the Tier C option for buyers who want WordPress expertise on the support line, not just server administration. Their team actively assists with WordPress-level issues, plugin conflicts, and performance questions. Jetpack Security is included, covering malware scanning, brute force protection, and backup. The $25/month single-site entry is slightly higher than Nexcess but includes a different support experience for WordPress-specific questions.
Starts at $25/month (single site)
For anyone undecided between ScalaHosting and Cloudways, the choice reduces to one question: do you want a cPanel-style interface with SPanel (ScalaHosting) or a modern application-focused dashboard that replaces cPanel entirely (Cloudways)? Both deliver Tier B management depth. The interface is the real differentiator, not the management quality. The managed vs unmanaged VPS comparison covers the broader context: when it makes sense to skip managed VPS entirely and run an unmanaged server for teams with Linux administration skills.
Managed VPS Hosting FAQ
What does 'managed' actually mean in managed VPS hosting?
Managed VPS is a hosting tier where the provider maintains the underlying server infrastructure and software stack on your behalf. At minimum, this means the host handles the physical hardware, network, OS security patches, and web server (Nginx, Apache, or LiteSpeed) updates. At a higher tier, it also includes PHP version management, MySQL updates, SSL provisioning, automated backups, and 24/7 server monitoring. What it rarely includes: WordPress core updates, plugin updates, or malware removal. Those fall under 'managed WordPress hosting,' which costs 2 to 5 times more. Before buying any managed VPS plan, ask the host to confirm which specific items from these four categories they cover.
Is managed VPS better than shared hosting for WordPress?
Managed VPS gives you dedicated resources (CPU, RAM) that cannot be consumed by other accounts on the same server. Shared hosting gives you shared resources, which means a neighbor's traffic spike can slow your site. The practical difference: on managed VPS, your site's PHP worker count is configured for you and guaranteed. On shared hosting, PHP workers are shared and throttled. For sites getting over 20,000 visits per month, the dedicated resource guarantee on managed VPS produces measurably lower TTFB under load. ScalaHosting managed VPS averaged 187ms TTFB in Q1 2026 testing, compared to 340 to 600ms typical on busy shared plans.
Do I need to know Linux to use a managed VPS?
No. The entire value proposition of managed VPS is that the Linux administration layer is handled by the host or abstracted behind a dashboard. On Cloudways, you install WordPress, change PHP versions, enable Redis, and configure backups through a web UI without a terminal. On ScalaHosting, SPanel provides the same abstraction. You will not need to write server config files, restart services, or troubleshoot PHP-FPM. Where you will still spend time: managing WordPress itself (updates, plugins, settings) from the standard WordPress admin panel, exactly as you would on shared hosting.
What is the difference between managed VPS and managed WordPress hosting?
Managed VPS handles the server layer: OS, PHP, MySQL, Nginx or Apache, SSL, backups, and monitoring. Managed WordPress hosting handles both the server layer and the application layer: WordPress core updates, plugin updates, malware scanning, and sometimes performance tuning for WordPress specifically. Kinsta and WP Engine are managed WordPress hosts. Cloudways and ScalaHosting are managed VPS hosts. The practical implication: if your WordPress site gets hacked because an outdated plugin had a vulnerability, a managed VPS host did not cause it and will not clean it up. The server was managed correctly. The application was not.
How many WordPress sites can I run on a managed VPS?
A 2 GB RAM managed VPS can typically support 3 to 8 WordPress sites depending on their traffic and plugin load. A 4 GB plan handles 8 to 20 sites comfortably if they are low-to-medium traffic. The real constraint is not disk space or even CPU time for most WordPress sites -- it is RAM available for PHP workers. Each PHP worker on an average WordPress site consumes 30 to 80 MB of RAM. At 30 concurrent PHP workers on a 2 GB plan, you have approximately 60 MB per worker after OS overhead, which is enough for simple sites but tight for WooCommerce. ScalaHosting's Start plan (4 GB RAM) is the practical entry point for running 5 or more WordPress sites confidently.
Does managed VPS include automatic WordPress backups?
Most managed VPS hosts include automated server-level backups, but the scope varies. Cloudways backs up your entire application (files + database) automatically at intervals you configure, with storage options including DigitalOcean Spaces and Amazon S3. ScalaHosting includes daily backups with 30-day retention on higher plans. What the backup covers and what the restore process requires differs significantly. Always confirm: (1) is the backup daily or weekly by default, (2) how many days of retention, (3) is backup storage offsite or on the same server, and (4) can you restore a single database without a full server rollback. These four answers tell you whether the backup is genuinely useful for recovery.