What you get in the Community Edition of BackupONE for Proxmox, where its limits lie, and how to plan a proper start — up to the restore test.

What is the Community Edition?
This is a standalone edition of BackupONE for host-level Proxmox backup. It is available without a trial period and without a time limit, within defined usage.
The free build is intended for Proxmox; backup of VMware and Hyper-V hosts is not included in this license. File and Image backup capabilities are subject to separate Freeware limitations, and are not available for such programs on Windows Server or on a computer connected to a domain. Proxmox backup itself is also available on these Windows environments.
Storage capacity, traffic, maintenance, and support must be planned separately. This is the standalone manufacturer's edition; the scope of BackupONE services is determined according to the selected service.
Where is it installed, and how does the data transfer?
The backup agent is installed on a Windows computer and connects to the host via the Proxmox API. There is no need to install a component on the host itself or set up a Proxmox Backup Server. A separate physical computer or a virtual Windows machine can be chosen, subject to communication requirements.
If the agent operates as a machine on the same host, according to Questions and answers in English, the machine running it is excluded from the backup. The dependency of the agent on the host must also be taken into account: a host failure can disable both. Before making a choice, plan how restoration will be performed in such a case.
What suits the free edition, and when do we consider an alternative?
Small and defined environment
Suitable for testing when the scope of the environment is within the stated limits, and the IT manager can maintain the software, check runs, and perform test restorations on an ongoing basis.
Large environment or managed service
If additional hosts are required, larger volume, or a combination of several Hypervisors, examine suitable commercial licensing. The manufacturer distinguishes between standalone VM Edition and Managed Backup, which adds central management of plans and environments.
When choosing an edition, compare management time, support, monitoring and reporting, not just licensing cost. Not every capability shown on a general product page is available in every edition and version. Verify commercial terms against the manufacturer’s VM edition information.
From planning to the first backup
-
Map the environment
Record the Proxmox version, number of hosts, processor sockets, and data volume. Mark critical machines and dependencies between applications, and define how much data can be lost and how long the service can be down. This data guides the frequency and testing of the restoration.
-
Prepare the Windows computer
The launch announcement mentions an agent in version 8.7. Currently, select a supported version and verify compatibility before installation. Building Community Edition replaces an existing standalone BackupONE installation; it should not be assumed that both can be installed side by side without planning the migration.
-
Define a dedicated account and communication
According to the BackupONE permissions document, create a dedicated backup user instead of using root. The documentation details PVEVMAdmin, PVESDNUser, and PVEDatastoreAdmin at the Datacenter level, and Sys.Modify for bandwidth limitation. Check the permissions actually required for the configuration and version.
The communication documentation specifies incoming connections to the Windows agent on ports 8007 and 3260. It is advisable to verify direction, source, and address range according to the updated network documentation; there is no need to open these services to the public to perform backup on an authorized network.
-
Choose a source, destination, and policy
Authors select the supported target, choose which machines will be included in the plan, and define a schedule and retention. The documentation describes a full backup followed by incremental backups; Synthetic Full and Forever Forward Incremental options also depend on the version and storage capabilities. Encryption is chosen and the access details are saved in a way that allows restoration.
-
Run and check the result
Do not settle for merely saving the plan. Check that the first run completed, that a restore point was created on the target, and that the selected machines actually appear in it. Document the time, volume, and errors, and then also verify an additional scheduled run.
-
Prove that recovery is possible
Perform a controlled restore to an isolated environment, without overwriting an active server. According to the documentation, it is possible to select a Proxmox server and a storage target, change the name, and set startup after restoration. After boot-up, check the application, data, and permissions, and document the time until service is restored.
Before defining the plan as 'ready'
- Someone is designated as responsible for checking successes, failures, and available capacity.
- There is an alert that will reach an available person even if the original server is not functioning.
- Access details, encryption, and restart procedures are documented and accessible to authorized personnel.
- The target does not depend only on that disk, host, or site that is being backed up.
- A test restoration was performed, and its result was checked against the business requirements.
To plan a setup that integrates several platforms, you can continue to the page BackupONE virtual machine backup. The edition is chosen according to the environment and the required operational responsibility, and it is not assumed that a licensing limitation is a recovery plan.


