|Subject:||Why do backing up VHD files take long|
|Creation date:||6/7/17 9:02 AM|
|Last modified on:||6/20/17 3:14 PM|
Why do VHD files take long to backup?
Users often complain backing up VHD (Virtual hard drives) file take a very long time in Syncrify. This page explains the reason and also an alternative method to use.
The rsync algorithm used in Syncrify tries to determine the delta between two versions and then sends this delta over to the destination, which is then
merged with the older copy of the file on the server. This is called the block-matching process.
The amount of time spent in determining delta (block-matching) is directly proportional to the amount of data that is modified within a file.
For example, if a file is modified towards the end, matching occurs very quickly. A good example of such a file is a PST file for MS Exchange.
On the other side of the spectrum, a file that is modified from all over will not only take a long time for block matching
to occur but the resulting delta will also be almost as big as the actual file. VHD files are notorious when it comes
to changes. Typically, a hard-disk gets modified from blocks that physically reside in different locations and
therefore, it is very likely to have a VHD file that is modified about 90%.
In summary, there are two problems when using rsync with VHD files:
- It takes a long time to match blocks
- The resulting delta is often as big as the actual file, diminishing the network bandwidth benefit you achieve when backing up other files.
An alternative method
If Syncrify client and server are taking to each other on a fast network, it may be faster to just use
, which will copy the entire file without matching any blocks.
Add a comment to this document
Do you have a helpful tip related to this document that you'd like to share
with other users? Please add it below. Your name and tip will appear at the
end of the document text.