- Posts: 13
- Liked: never
- Joined: Aug 02, 2009 3:12 pm
For example, immediately after running a full backup that took one hour to complete and that generated a 10G .vbk file, if I run the same job again, the job runs for another hour and but only generates a 100M .vbr file. Within the Veeam console, the subsequent/incremental backup is running for an hour, but only generates small .vbr files. This is all recorded in the log/report.
So is it actually using all this time to calculate differences on the guest VM, or is this time being used to merge/synthesize on the Veeam console (meaning, no load on the ESX server), or is it something else?
- VP, Product Management
- Posts: 5876
- Liked: 2717 times
- Joined: Jun 05, 2009 12:57 pm
- Full Name: Tom Sightler
vSphere 4.x has support for block change tracking and Veeam has previously stated that Veeam Backup 4 will include support for this feature so once this is available incremental backups should be much faster since it will literally only need to read the actual changed blocks (ESX does the effort of tracking changed blocks on the fly).