iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
How to automate Proxmox VM and LXC backups with Home Assistant? Let Proxmox VE create and retain the backups on its own schedule, then use Home Assistant to show status, coordinate related actions, and send alerts. This division is more reliable than trying to make Home Assistant act as the backup scheduler. Proxmox provides the native job engine, guest-consistency modes, storage targets, retention rules, and restore workflow; Home Assistant adds cross-system orchestration and visibility.
The built-in Home Assistant Proxmox VE integration is not documented as a “start backup job” control. It exposes Proxmox nodes, virtual machines, and containers, along with permission-gated control actions. If you need an on-demand trigger from Home Assistant, use a carefully restricted REST or SSH bridge and treat the resulting Proxmox task as asynchronous. Do not make a Home Assistant automation wait for an entire backup to finish.
Use Proxmox as the backup engine
Proxmox VE already schedules backups through its web interface, the vzdump tooling, and the cluster backup-job API at /cluster/backup. A job can select virtual machines (VMs) and Linux containers (LXCs), choose a destination, define a calendar, set a backup mode, and apply retention. Proxmox’s scheduler runs the configured jobs, including jobs that can be configured to repeat after a missed run when the host was offline or the scheduler was disabled.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →That native path has fewer moving parts than an automation that starts a shell command, waits for a remote process, interprets output, and then tries to decide whether the resulting archive is valid. Proxmox also records task state where its administrators already look for it. Home Assistant should therefore be an observer and coordinator around the job, not a replacement for it.
#1 Best Overall
- Secure private cloud - Enjoy 100% data ownership and multi-platform access from anywhere
- Easy sharing and syncing - Safely access and share files and media from anywhere, and keep clients, colleagues and collaborators on the same page
- Automated Backup Protection - Set-and-forget backups for Macs, PCs and mobile devices to multiple destinations including cloud and external drives
- Home Security System - Record and monitor your property 24/7 with support for multiple IP cameras and remote viewing
- 2-Year Warranty - Reliable hardware backed by Synology's expert customer support team and ongoing software updates
“These backups are always full backups – containing the configuration of VMs and container, and all data.”
The statement above describes integrated vzdump backups. Proxmox Backup Server (PBS) uses incremental transfer of changed data, so do not apply the “always full” description to PBS’s transfer behavior.
What you need before automating
- A reachable Proxmox VE node or cluster with the VMs and LXCs you intend to protect.
- At least one backup destination configured in Proxmox. This can be file-based storage such as NFS or a dedicated Proxmox Backup Server datastore.
- A list of guests, their business importance, acceptable downtime, and the data that must be restored first.
- A schedule that avoids competing with maintenance, replication, or unusually heavy guest workloads.
- A dedicated Proxmox account for Home Assistant connections, assigned only the permissions needed for the chosen monitoring or bridge operation.
- A restore plan and a separate test environment, or at minimum a documented procedure for restoring a guest without overwriting the production copy.
Keep the Proxmox API on a trusted network. Do not expose it directly to the public internet just to let Home Assistant reach it. Use encrypted transport, verify certificates where your deployment supports that, and restrict source addresses at the firewall.
Configure a native Proxmox backup job
Start here even if your eventual goal is event-driven control from Home Assistant. A working scheduled job provides a dependable fallback when Home Assistant is unavailable.
- Open the job editor. In the Proxmox web interface, go to Datacenter → Backup and create a new job.
- Select guests. Choose specific VMs and LXCs or a selection rule appropriate to your cluster. Avoid assuming that every guest should share one schedule; databases, development systems, and disposable test containers often need different treatment.
- Choose storage. Select the configured file storage or PBS datastore. Confirm that the destination is mounted and has enough usable capacity for the retention policy, temporary space, and growth of the guests.
- Set the calendar. Pick a time and repeat interval that fit your workload. If the job editor offers the option to repeat missed jobs, enable it only when catching up is safe for your storage and guest load.
- Choose a backup mode. Select snapshot, suspend, or stop after considering the consistency and downtime trade-off described below.
- Set notification and task behavior. Configure the job’s error-handling and notification options available in your installed Proxmox release. A failed task must remain visible to an operator or monitoring system.
- Configure retention. Use the keep-last, keep-hourly, keep-daily, keep-weekly, keep-monthly, and keep-yearly fields to describe how many recovery points should remain.
- Run a test. Start the job manually or wait for its first scheduled run. Check the task log, archive size, completion status, and destination contents.
- Perform a restore test. Restore one representative VM and one LXC, preferably under different operating conditions, into an isolated name or network. Verify boot, application data, network identity, and any guest-specific services.
Proxmox’s web interface writes the same kind of scheduled job that can be managed through its cluster backup API. Use the API when you need configuration as code or external orchestration, but validate the request schema and access-control requirements against the API viewer for the exact Proxmox release you run.
Choose the backup mode deliberately
| Mode | Downtime | Consistency and compatibility | When it fits |
|---|---|---|---|
| Snapshot | Lowest interruption for most guests | Can leave some application-level inconsistency; guest behavior and storage stack still matter | Normal workloads where brief filesystem-level inconsistency is acceptable and applications provide their own recovery mechanisms |
| Suspend | Guest is paused during the relevant phase | Documented as a compatibility mode; Proxmox recommends snapshot instead where supported | Specific compatibility cases in which snapshot behavior is unsuitable |
| Stop | Highest downtime | Strongest consistency because the guest is shut down for the backup | Critical systems that cannot tolerate an application-inconsistent image and can schedule a maintenance window |
Mode selection is not a substitute for application-aware protection. A database may need its own dump, replication, or quiescing procedure in addition to a VM or container image. Document the expected recovery point and recovery time for each guest, then choose the least disruptive mode that meets that requirement.
Rank #2
- 【Reliable External Storage System for Individuals and business】The 3.5 hard drive enclosure supports 2.5/3.5 inches HDD and SSD, max capacity up to 20TB for each hard drive, it's a ideal external hard drive enclosure for personal or enterprise using.Save space on your desktop or laptop.
- 【No heat】The sata enclosure built in Aluminum-Alloy materials and 2 inch Fan.Maximize the security of your data.Fan noise is around 40-50 decibels, not recommended if you are very sensitive to noise.
- 【Up to 5Gbps】This dual bay enclosure equips with advanced chips and USB 3.0 output interface.Transfer 1G files in 3-5 seconds with USB 3.0 Ports, which is 10 times faster than USB 2.0.
- 【Hot Swappable Convenience】The HDD enclosure supports hot swapping, allowing users to replace hard drives without powering off the device. This feature enhances convenience and efficiency in data transfer processes.
- 【Tool-Free Installation】Featuring a tool-free hard drive tray design, the external hard drive enclosure enables easy installation and removal of hard drives without requiring additional tools. Plug and play! No fuss, no muss!
Select a destination that matches your failure plan
| Destination | Strengths | Operational trade-offs |
|---|---|---|
| NFS or other file storage | Uses familiar network storage and can be shared by Proxmox nodes | Requires dependable mounts, network availability, capacity monitoring, and protection against a failure that affects both the production node and the storage |
| Proxmox Backup Server | Incremental transfers send newly changed data; client-side encryption is available; VM live restore can start a VM while remaining data copies in the background | Requires a PBS host, datastore configuration, access control, maintenance, and its own capacity and failure planning |
| Local file storage | Simple and fast for short-term or test backups | A disk or node failure can remove both the running guest and its backups; it should not be your only copy for important systems |
A two-bay NAS enclosure can be useful as optional NFS infrastructure, but neither a NAS nor PBS is required for Home Assistant integration. The important question is whether a destination survives the failures you are planning for: disk loss, a failed Proxmox node, accidental deletion, ransomware, or a site outage.
Apply retention without losing useful recovery points
Proxmox supports keep-last, keep-hourly, keep-daily, keep-weekly, keep-monthly, and keep-yearly policies. The rules are processed in order. Each later rule covers older backups that were not already covered by an earlier rule, so the resulting set is not simply the sum of every number entered.
Design retention from actual restore scenarios. For example, recent hourly points help recover from an accidental change discovered quickly, daily points cover a longer operational window, and monthly or yearly points preserve historical states. Estimate storage from the guests’ change rate, not only their virtual disk size. Full vzdump archives and PBS incremental transfer behavior have different capacity patterns.
Retention is not an archive strategy by itself. Keep at least one recovery copy outside the failure domain of the Proxmox host, protect access to the backup datastore, and periodically verify that the oldest points you expect to keep still exist.
Add Home Assistant for monitoring
Home Assistant’s Proxmox VE integration is the low-risk addition. It polls Proxmox data every 60 seconds and exposes entities for nodes, VMs, and containers. The integration documentation recommends a dedicated Home Assistant account in the Proxmox realm rather than using a personal administrator login.
- Create the dedicated Proxmox identity and assign the minimum read or control permissions required for the entities you want to expose.
- In Home Assistant, add the Proxmox VE integration through the integrations screen and enter the node address and dedicated credentials.
- Confirm that the expected node, VM, and LXC entities appear and that their state changes are reflected after the polling interval.
- Build dashboards showing guest state, node availability, and any backup-related information that your Proxmox version exposes through the API.
- Create alerts for a node becoming unavailable, a protected guest remaining stopped unexpectedly, or a backup indicator becoming stale.
Not all Proxmox storage types and data are fully exposed through the Proxmox VE API, so the integration cannot be assumed to provide a complete storage-capacity or backup-history view. Use Proxmox task logs and the destination’s own monitoring for authoritative backup results.
Rank #3
- Entry-level NAS Personal Storage：UGREEN NAS DH2300 is your first and best NAS made easy. It is designed for beginners who want a simple, private way to store videos, photos and personal files, which is intuitive for users moving from cloud storage or external drives and move away from scattered date across devices. This entry-level NAS 2-bay perfect for personal entertainment, photo storage, and easy data backup (doesn't support Docker or virtual machines).
- Set Your Devices Free, Expand Your Digital World: This unified storage hub supports massive capacity up to 64TB.*Storage drives not included. Stop Deleting, Start Storing. You can store 22 million 3MB images, or 2 million 30MB songs, or 43K 1.5GB movies or 67 million 1MB documents! UGREEN NAS is a better way to free up storage across all your devices such as phones, computers, tablets and also does automatic backups across devices regardless of the operating system—Window, iOS, Android or macOS.
- The Smarter Long-term Way to Store: Unlike cloud storage with recurring monthly fees, a UGREEN NAS enclosure requires only a one-time purchase for long-term use. For example, you only need to pay $459.98 for a NAS, while for cloud storage, you need to pay $719.88 per year, $2,159.64 for 3 years, $3,599.40 for 5 years. You will save $6,738.82 over 10 years with UGREEN NAS! *NAS cost based on DH2300 + 12TB HDD; cloud cost based on 12TB plan (e.g. $59.99/month).
- Blazing Speed, Minimal Power: Equipped with a high-performance processor, 1GbE port, and 4GB RAM on Board, this NAS handles multiple tasks with ease. File transfers reach up to 125MB/s—a 1GB file takes only 8 seconds. Don't let slow clouds hold you back; they often need over 100 seconds for the same task. The difference is clear.
- Let AI Better Organize Your Memories: UGREEN NAS uses AI to tag faces, locations, texts, and objects—so you can effortlessly find any photo by searching for who or what's in it in seconds. It also automatically finds and deletes similar or duplicate photo, backs up live photos and allows you to share them with your friends or family with just one tap. Everything stays effortlessly organized, powered by intelligent tagging and recognition.
The integration documents permission-gated control actions for supported guest operations. It does not document a first-class “start backup job” action. Do not build an automation that expects a backup button to appear among those entities.
Use a REST or SSH bridge only for a specific orchestration need
An external trigger can make sense when a backup must be coordinated with another event—for example, after a Home Assistant-controlled system has completed a shutdown or before a planned change. It is not necessary merely to run nightly backups; the native Proxmox scheduler is better suited to that.
RESTful Command pattern
Home Assistant’s RESTful Command integration can issue HTTP methods such as POST from an automation and can expose the returned status and content for inspection. The exact Proxmox endpoint, request body, authentication method, and privilege set are version-sensitive details. Confirm them in the API viewer and current access-control documentation before deploying anything.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Create a narrowly scoped Proxmox credential for the bridge. Prefer a token or account limited to the required cluster backup operation instead of a broad root credential.
- Verify the request manually against a non-production guest or a maintenance window. Confirm that Proxmox returns a task identifier rather than treating an HTTP response as proof that the archive is complete.
- Configure the Home Assistant command to make the short request and record the returned status and task identifier.
- Use a separate polling automation to query task state until Proxmox reports success or failure. Set a maximum polling period and a failure path; never wait forever.
- Notify only after the task reaches a terminal state, and include the guest, destination, task result, and timestamp in the message.
The bridge should start or configure a Proxmox task, not stream the backup through Home Assistant. Keep credentials in Home Assistant’s secret storage, verify TLS certificates, and make sure a timeout or network interruption cannot cause an unsafe retry that launches duplicate work.
SSH bridge pattern
Home Assistant’s Shell Command integration can run a local command or an SSH call, but each process is terminated after 60 seconds. On Home Assistant OS, the command runs inside the homeassistant container, not as the host’s system root. The documented key location is /config/.ssh, and known-host verification should be enabled.
- Generate a dedicated SSH key for the bridge and place it in Home Assistant’s protected configuration area.
- Install only the corresponding public key on the Proxmox side, with a restricted account and a forced command or wrapper where practical.
- Test host-key verification and a harmless command before allowing any backup-related action.
- Have the remote command submit the Proxmox task and return immediately with its task identifier.
- Track completion through Proxmox task status rather than keeping the shell process open. A backup that lasts longer than 60 seconds will otherwise be cut off by Home Assistant even if Proxmox continues working.
Do not interpret an SSH session ending as evidence that the backup failed or succeeded. The authoritative result is the Proxmox task and archive verification.
Rank #4
- High Speed Data Transmission: The D2-320 hard drive enclosure (a DAS, NOT a NAS) adopts USB 3.2 Gen2 protocol for high-speed data transmission up to 10Gbps. With 2 hard drives in RAID 0, the read/write speed can reach up to 521MB/s (SATA III HDD 8TB x 2). With 2 SSD's in RAID 0, the read speed can reach 1075MB/s (SATA III 1TB SSD x 2)
- Multiple RAID Configurations: The D2-320 is a hardware RAID enclosure and it supports RAID 0, RAID 1, JBOD and SINGLE which can better satisfy various demands of users. In RAID 1, data will be in a mirror backup. When there is a damaged hard drive, you can directly replace the hard drive, and the data will be recovered automatically. This provides an absolute security for the data
- Super-Large Storage Capacity: The D2-320 USB storage enclosure can support up to two 3.5" and 2.5" SATA HDD, as well as 2.5" SATA SSD, with a maximum capacity of 22TB per drive, providing users with up to 44TB (22TB x 2) of storage space
- Intelligent Temperature Control: The D2-320 HDD enclosure has an intelligent temperature-controlled and low-noise fan that automatically adjusts its speed based on the temperature of the hard disk. This feature ensures that the hard disk operates at its best temperature and provides better heat dissipation
- Tool-Free Hard Drive Installation: The D2-320 external hard drive enclosure features a tool-free hard drive tray design that allows for easy installation and removal of hard drives without the need for any tools. Furthermore, the D2-320 incorporates a brand new Push-lock unique design from TerraMaster, which automatically locks the hard drive tray when you insert the hard drive, preventing the hard drive from falling out or disconnecting
Design Home Assistant automations around states, not delays
A robust automation has explicit stages and failure branches:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall- Preflight: check that the Proxmox node is reachable, the destination is available, and the selected guests are in an expected state.
- Submission: call the approved REST or SSH bridge only when the orchestration event requires it.
- Task capture: save the returned Proxmox task identifier with the guest and start time.
- Polling: query status at a reasonable interval and stop after a defined deadline.
- Completion: notify on success only after the task is terminal and the result indicates success.
- Failure: notify with the error, preserve the task identifier for investigation, and avoid automatic retries that could overlap a still-running task.
- Staleness: alert when no successful backup has occurred within the expected window, even if Home Assistant itself is still online.
For ordinary nightly protection, omit the bridge entirely: let Proxmox schedule the job and have Home Assistant monitor the resulting health signals. This avoids coupling backup execution to Home Assistant restarts, upgrades, or network outages.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Secure the integration and credentials
- Use a dedicated Proxmox account or API token for Home Assistant; do not embed a full administrator password in an automation.
- Grant only the permissions required by the monitoring or bridge operation, and review them after Proxmox upgrades.
- Keep the API and SSH endpoints on a private management network or behind a firewall allowlist.
- Use TLS certificate verification for HTTPS and strict known-host verification for SSH.
- Store secrets in Home Assistant’s secret-management mechanism, not in dashboards, notifications, or shared YAML snippets.
- Audit task logs and Home Assistant automation traces after changing credentials or permissions.
- Protect the backup destination itself. Anyone who can delete or alter all recovery points can defeat an otherwise correct automation.
Troubleshoot common failure patterns
The job never runs
Check that the job is enabled, its schedule uses the expected timezone, the Proxmox scheduler is running, and the node was online at the scheduled time. If missed-job repetition is enabled, verify that catching up will not create an unsafe load spike.
The task starts but fails on storage
Inspect the Proxmox task log, confirm that the NFS mount or PBS datastore is online, and check free space, permissions, and network reachability. A destination that is mounted read-only or has reached a datastore limit can produce a task failure even when the guest is healthy.
The backup succeeds but the application is unusable after restore
Revisit the mode choice and application consistency requirements. Snapshot mode minimizes downtime but does not guarantee an application-consistent image. Add application-native exports or schedule a stop-mode backup during maintenance when the workload demands it.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsHome Assistant shows an old state
The integration polls about every 60 seconds, so a change is not necessarily immediate. Confirm the entity’s last update, then compare it with Proxmox’s task log. If storage or task data is missing, use Proxmox’s own interface or API rather than assuming the integration exposes every field.
Best Value
- 【Advanced Home Data & Media Hub】For advanced home users who need phone backup, file storage, and centralized data management. Centralize family photos, 4K videos, movies, computer backups, and personal files in one place while running multiple apps for home entertainment and everyday data management. Suitable for households with growing digital libraries and multiple NAS use cases.
- 【Built for Creators, Media Servers & Advanced Apps】Powered by the Intel N100 Quad-Core CPU, 8GB DDR5 RAM, 2.5GbE networking, and dual M.2 NVMe slots, DXP2800 handles large files and heavier workloads with ease. Run Docker, virtual machines, and media server applications compatible with Plex—ideal for content creators, tech enthusiasts, and advanced home users managing 4K videos, RAW photos, personal media libraries, and multiple NAS apps.
- 【Up to 80TB for Growing Digital Libraries】 Supports up to 80TB of storage using two HDD bays and two M.2 NVMe SSD slots for family photos, movies, RAW photos, 4K videos, work files, and device backups. AI photo management supports recognition of people, objects, scenes, and locations, album organization, and duplicate photo detection. HDDs and SSDs are not included.
- 【AI-powered Home Surveillance】Turn DXP2800 into a centralized home surveillance hub by connecting compatible network cameras and storing recordings locally on your NAS. AI-powered features include Face Recognition, People Detection, and Pet Detection, helping advanced home users review important events more efficiently while managing home surveillance and personal data in one place.
- 【One data Center Across Your Devices】Keep files from desktops, laptops, phones, tablets, and other devices together instead of scattered across cloud accounts and external drives. Access, back up, organize, and share data across Windows, macOS, Android, iOS, web browsers, and compatible smart TVs—ideal for creators and advanced home users working across multiple devices.
The SSH automation times out
A 60-second Shell Command limit is expected. Change the design so SSH submits the task and exits; track the asynchronous Proxmox task separately. Do not increase confidence in a backup merely because the remote command returned before the timeout.
The REST call returns an error or permission denial
Recheck the endpoint and payload against the installed release’s API viewer, then inspect the account’s path-specific permissions and token settings. Treat a successful HTTP submission as different from a successful backup task.
Make restore testing part of the schedule
A backup is useful only if it can be restored. At a planned interval, select recovery points from different ages and restore representative VMs and LXCs into an isolated network. Verify that the guest boots, its disks and configuration are present, services start, and the restored identity cannot conflict with production.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Record the time required to locate a recovery point, restore it, repair any application-level issues, and return the service to operation. PBS’s VM live restore can start a VM while the remaining data is copied in the background, which may reduce service wait time, but the restored guest still needs validation before it is treated as recovered.
Document who approves a production restore, how to stop a mistaken restore, and how to recover when the primary Proxmox node is unavailable. Keep that procedure independent of Home Assistant so a failure of the automation layer does not prevent disaster recovery.
Which approach should you choose?
| Approach | Best use | Main trade-offs |
|---|---|---|
| Proxmox scheduled job | Regular unattended VM and LXC backups | Native scheduling, retention, and task logging; less suited to timing a backup around Home Assistant events |
| Home Assistant Proxmox integration | Dashboards, guest visibility, and documented permission-gated control | Convenient entity view, but no documented backup-job action and incomplete exposure of some storage data |
| REST or SSH bridge | A specific cross-system event must submit a Proxmox task | Requires version-specific API validation, least-privilege credentials, asynchronous task tracking, and careful error handling |
| Proxmox Backup Server | Dedicated destination, incremental transfers, encryption, and live restore | Adds a server and datastore to operate; its capacity, access, and failure planning must be maintained |
For most installations, the recommended design is straightforward: create and test Proxmox jobs first, place them on storage that survives a host failure, configure retention and restore drills, then add Home Assistant monitoring and alerts. Add a REST or SSH trigger only when a real orchestration requirement justifies its additional credentials and asynchronous state handling.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
