Size of Incremental Backups no Different from Full Backups for Virtual Machines
It is noticed that the size of the incremental backups of (all) my Virtual Machines are no different from their full backups, and the time taken is equally long as well. Which setting(s) is likely to have gone wrong?
Using exactly the identical backup plan, the issue is not observed for physical nodes.

- Log in to post comments

Thank you! My case is explained by 65528: Acronis Cyber Protect Cloud, Acronis Cyber Backup: Why incremental backup looks like full backup. Now it brings me to wonder if the time taken for incremental backups of my VM nodes is reasonable. They sure are taking much more time compared to physical nodes, in the same network, as if a full backup is taking place.
Incremental Backup of a VM
Incremental Backup of a Physical node
"Backup options" I'm using for my VMs
Alerts - no
Backup consolidation - no
Backup file name - default
Backup format - automatic selection (option greyed out)
Backup validation - no
Changed block tracking (CBT) - no
Compression Level - normal
Email notifications - use the system settings (default)
Error handling - default
Fast incremental/differential backup - Yes
File filters - not in use
LVM snapshotting - By the backup software
Multi-volume snapshot - Yes
Performance and backup window - default setting
Pre-post commands - no
Pre-post data capture commands - no
SAN hardware snapshots - no
Scheduling - Start all backups exactly as scheduled
Sector-by-sector backup - no
Splitting - Automatic
Tape management - default/not in use
Task failure handling - no
Task start conditions - Wait until the conditions from the schedule are met
Volume Shadow Copy Service (VSS) - Yes - Automatically select snapshot provider
Volume Shadow Copy Service (VSS) for virtual machines - Yes
Weekly backup - Monday (default)
Windows event log - Yes - Errors and warnings
- Log in to post comments

Hello Fang Cheng Tin
Besides the reasons listed in KB articles above, this could be due to the disabled Changed Block Tracked option or after defragmentation on the affected VM.
- Log in to post comments