When you mention that the restore point (I’m assuming incremental) is larger than the changed, it makes me wonder two things. First, are you backing up the repository for this backup job, creating some kind of exponential growth? Second, is there any kind of encryption on the source system that might make it impossible for Veeam to only back up changed blocks?
Been struggling with two ongoing issues in VBR and VSPC, and its eating away at man hours constantly trying to fix them.
- on a daily basis, backup jobs are failing in VSPC (or running forever).
- Restore Points will become larger than the changes made to the system
(for example, running a daily backup and 100 MB of data is added to the server between daily backup jobs, the next restore point created is often multiple times larger than 100 MB, often into the GBs)
I wanted to pose this to the community to see if there is anyone who’s encountered or resolved either of these issues.
Hello,
For the 1 I have no idea.
For the 2 there could be lot s of reason…
Be sure cbt is used in your job or you will backup more data.
If you have database on the server you will have more data to backup than what you add on it.
Then even if you add 100mb of data lot s of files are updated when the system is power on and you will never have only 100mb size incremental if your last backup was 1 days ago.
Check if the backup job is using CBT for incremental. CBT can reset if the VM is moved to another host or if storage vMotion happens which makes the next incremental much larger.
Even with only 100 MB of changes Veeam still backs up system state and metadata, so the size will always be a bit more than the actual data change. If CBT was reset, turn it back on and run an active full to get the chain back to normal
You say the job fails regulary. Has the job ever finished successfully?
Otherwise a full backup is tried every day and this would explain why more data is written each day.
