AOMEI Cyber Backup is a central backup console for business workloads rather than a personal folder-sync utility. It connects to VMware or Hyper-V environments, Windows machines, and Microsoft SQL Server sources, then schedules backups to storage chosen by the administrator. One web console shows jobs, recovery points, and restore actions across those devices. The protected workload and the machine running the console do not have to be the same computer.
Add the workload
The administrator first registers a source. VMware and Hyper-V protection can work at the virtualization layer, while Windows workloads may use an installed component. The account used to add a host needs the relevant administrative access. AOMEI Cyber Backup then discovers machines or databases that the account can see, and a task selects which objects to protect.
This setup makes naming and connectivity important. The official FAQ notes that a Hyper-V host name containing a single quote blocks supported backup or restore. VMware access may also depend on management services and network reachability. Test the connection before relying on a schedule; a job definition cannot protect a host that the backup server cannot authenticate or reach.
Set the schedule
An AOMEI Cyber Backup task chooses the source, destination, schedule, and retention behavior. Full, incremental, or differential chains change how later recovery points depend on earlier data. Deleting an archive can remove the related data chain, so storage cleanup needs more context than deleting the oldest-looking file from the destination. Use the console’s retention controls instead of manually pruning backup folders.
Destination format also matters. AOMEI Cyber Backup does not support storing a virtual machine larger than 4 GB on FAT32. The available free space must cover new backup data and any temporary work required by the workload. A destination that barely fits the first backup may fail as changed blocks accumulate.
Restore with intent
A full virtual-machine restore starts by selecting a recovery point and a destination. The protected virtual machine must shut down before the restore. On Hyper-V, restoring to the original location overwrites the original machine with the chosen backup state. Any newer data inside that machine disappears unless the administrator protects it separately first.
Restore to a new location avoids that overwrite, but it needs another target and a new virtual-machine name. The operator may also choose the datastore, memory, and virtual-processor values. This path suits verification because the restored machine can start separately, although network identity and application connections may require isolation to prevent two copies from acting as the same server.
Recover smaller items
Some backup types support mounting a recovery point and downloading selected files instead of restoring the whole workload. The browser packages chosen files for download, and the administrator should unmount the backup afterward to release resources. Granular recovery shortens a simple file retrieval, but it does not replace a full recovery drill for a failed server.
AOMEI Cyber Backup also restricts one account to one console session at a time. A second administrator login can end the first session, which becomes awkward during an incident. Assign operational responsibility before a restore and record the chosen recovery point. The useful test is not a green backup status alone: periodically restore a representative machine or database into an isolated target and confirm that the recovered service starts with the expected data.
