PROVIDER - Lightweight VM backup
NAKIVO
NAKIVO backs up and replicates VMware, Nutanix AHV, Hyper-V, and AWS EC2 from a single Director console and writes to ordinary NAS or object storage without a dedicated appliance, which is how it competes on price.
3.7pts
Detailed Notes
Pros 5 items
Cons 4 items
Service Overview
NAKIVO is a US-headquartered backup software vendor whose product is the pure-software NAKIVO Backup & Replication, which within Backup & Migration belongs to the "install and run, pick your own storage" camp. There is no dedicated backup appliance: it installs on a Linux host, a virtual machine, or a NAS, and targets plain NAS, SMB/NFS shares, or S3-compatible object storage.
Coverage centres on virtualization. VMware vSphere, Nutanix AHV, and Hyper-V are natively supported, and AWS EC2 joins through cloud integration. One Director console manages every job, and backup, replication, and restore share a single policy model, so cross-platform operations stay consistent and the learning curve concentrates on initial configuration.
Its two most practical traits are storage freedom and Flash VM Boot. Storage freedom means no vendor-certified appliance purchase: an existing NAS or an object storage bucket works as a target. Flash VM Boot mounts a backup file as a running virtual machine for availability checks or emergency cover, which turns verification from "queue for a restore" into "run a boot test".
Key Strengths
- No proprietary hardware: targets include NAS, SMB/NFS shares, and S3-compatible object storage, so existing storage assets get reused and no vendor appliance joins the rack
- One console across 4 platforms: VMware, Nutanix AHV, Hyper-V, and AWS EC2 jobs are orchestrated in one interface, avoiding multiple tools and credentials in hybrid estates
- Flash VM Boot for fast verification: a virtual machine boots from a backup in about 1 minute, confirming the copy is actually restorable and lowering the bar for restore drills
- Deduplication plus immutability: dedup and compression hold down storage use while immutable backups lock copies for the retention window, together reducing the risk of backups being encrypted
- Simple licensing: tiered by socket or VM count across 3 editions, so cost curves stay predictable when the estate grows and budgets can be pre-approved
Product Ecosystem
Platform capabilities
The core is the Backup & Replication job engine, handling image-level backup, replication, instant recovery, and storage snapshot integration. The model has two layers: a job defines sources, schedule, and retention, while a repository defines the medium and whether immutability is on. Incremental chains are periodically merged into synthetic fulls so a complete backup does not have to rerun and widen the window.
Supporting features include backup verification, capacity reporting, and alerting. Verification can boot a test machine through Flash VM Boot or run file-level integrity checks, and reporting covers job history, storage consumption, and success trends, which answers questions like which machines missed a backup last week.
Integrations
- Hypervisors: native vSphere, Nutanix AHV, and Hyper-V integration with application-consistent snapshots
- Public cloud: AWS EC2 protection with backups written to S3 or local storage
- Storage and media: NAS, SMB/NFS shares, S3-compatible object storage, plus local disks for a secondary copy
- Operations: REST endpoints and command-line invocation for job triggers and status queries, scriptable into existing monitoring
- Notification: email alerts and webhooks that route into ticketing or chat tools
Typical scenarios
Three patterns dominate: image-level backup and fast rollback for small and mid-size virtualization clusters; an offsite copy on NAS or object storage to satisfy 3-2-1 without buying new hardware; and a one-off full snapshot before an upgrade or migration, rolled back through Flash VM Boot if something breaks. All three share a tight storage budget with a real need to verify restores in-house.
Limitations
- Brand and ecosystem scale trail the top tier, so third-party monitoring templates, orchestration plugins, and community cases are sparser
- Multi-site cutover and large container estates require self-designed orchestration because no turnkey automation engine is included
- Director high availability is left to the customer and needs a documented restore path when the console fails
- Chinese-language UI and local support depend on authorized resellers, and complex incidents take longer to diagnose and escalate
Use Cases
- Small and mid-size VMware or Hyper-V clusters (★★★★☆): socket-based licensing plus an existing NAS keeps total spend an order of magnitude below appliance options
- Nutanix AHV environments (★★★★): AHV is natively supported, so hyperconverged platforms need no extra plugin or agent hunt
- Teams that already own NAS or object storage (★★★★☆): existing storage becomes the target and expansion follows buckets or volumes rather than new hardware
- Organizations running frequent restore drills (★★★☆): Flash VM Boot makes verification routine, though multi-site orchestration stays manual
- Large multi-site or container-first platforms (★★☆): orchestration depth and ecosystem breadth fall short, and platform vendors fit better at that scale
Pricing
| Item | Price | Notes |
|---|---|---|
| Foundation Edition | Annual subscription per socket or VM | Core backup and restore for single-site small estates, official price list governs |
| Business Edition | Annual subscription per socket or VM | Adds replication, reporting, and cloud integration, the common mid-tier choice |
| Enterprise Edition | Annual subscription per socket or VM | Full feature set and multi-cloud scenarios, with volume discounts at scale |
| Perpetual licence | One-time purchase plus annual support | Fold a 3-year-plus holding cost into the comparison; support renewal is usually a percentage of the licence |
Prices are published for socket and per-VM meters, and actual quotes vary with node count, edition, and channel. The table excludes storage media and services, and storage cost depends on the NAS or object storage unit price you choose.
FAQ
Does NAKIVO need a dedicated backup appliance?
No. One of its selling points is hardware neutrality: the Director installs on a Linux host, a virtual machine, a NAS, or even an ARM device, and targets can be a plain NAS, a share, or S3-compatible object storage. The trade-off is that performance follows your own hardware IO, so size it against the data volume.
How does it differ from Veeam?
Ecosystem depth and scale ceiling. Veeam has broader third-party integration, storage certifications, community material, and large-deployment references, with finer feature granularity. NAKIVO wins on light deployment, simple licensing, and storage neutrality, which usually prices better in mid-size estates while large multi-site platforms lean toward fuller ecosystems.
How is immutable backup configured?
Enable the immutable option on the repository and set the lock period, and ideally put object lock or WORM underneath so immutability is enforced at the storage layer rather than in the application. Align the lock period with the compliance requirement: too short provides no protection, too long inflates capacity indefinitely.
What should teams in mainland China watch for?
Two things. Licensing and support run through resellers, so service quality depends on their capability. And where the target is object storage, cross-border transfers slow offsite copies, so keep a complete local copy before replicating.
Code Examples
Trigger an on-demand backup over REST
#!/usr/bin/env bash
set -euo pipefail
# Endpoint and credentials come from environment variables; verify paths against official API docs
TOKEN=$(curl -s -X POST "${NAKIVO_API}/login" \
-H "Content-Type: application/json" \
-d "{\"username\":\"${NAKIVO_USER}\",\"password\":\"${NAKIVO_PASSWORD}\"}" \
| jq -r '.token')
JOB_ID="${NAKIVO_JOB_ID}"
curl -s -X POST "${NAKIVO_API}/jobs/${JOB_ID}/run" \
-H "Authorization: Bearer ${TOKEN}" \
-H "Content-Type: application/json" \
-d '{"type":"full"}' | jq .
Poll the session status separately: a success response only means the task was queued, not that the backup finished.
Check free capacity across repositories
#!/usr/bin/env python3
# Summarise free space per repository and flag anything under the threshold
import json
import os
import urllib.request
BASE = os.environ["NAKIVO_API"]
TOKEN = os.environ["NAKIVO_TOKEN"]
THRESHOLD_GB = int(os.environ.get("WARN_FREE_GB", "100"))
def get(path: str):
req = urllib.request.Request(f"{BASE}{path}", headers={"Authorization": f"Bearer {TOKEN}"})
with urllib.request.urlopen(req, timeout=30) as resp:
return json.loads(resp.read())
repos = get("/repositories").get("items", [])
for repo in repos:
free_gb = repo.get("freeSpaceBytes", 0) / 1024**3
state = "WARN" if free_gb < THRESHOLD_GB else "OK"
print(f"{state:4} {repo.get('name'):30} free={free_gb:.1f} GB")
Size the alert from growth rate times retention days; a free-percentage threshold alone misleads once deduplication ratios shift.
Community & Resources
- NAKIVO official site — Product matrix, supported platforms, and release notes
- NAKIVO help center — Installation, job configuration, and restore manuals
- NAKIVO pricing — Edition comparison and licensing meters
- NAKIVO blog — Virtualization backup practice and migration configuration examples