-
- Enthusiast
- Posts: 26
- Liked: 2 times
- Joined: Apr 21, 2015 11:50 am
- Full Name: Suresnes
- Contact:
How to read the backup result?
Hello,
Can anyone please explain how to read/understand the values displayed in the result (see below for a typical email)?
Data Read
Transferred
Backup size
Dedupe
Compression
and the result on disk:
Thanks a lot
Can anyone please explain how to read/understand the values displayed in the result (see below for a typical email)?
Data Read
Transferred
Backup size
Dedupe
Compression
and the result on disk:
Thanks a lot
-
- Veteran
- Posts: 391
- Liked: 107 times
- Joined: Apr 27, 2015 1:59 pm
- Full Name: Ryan Jacksland
- Location: NY, USA
- Contact:
Re: How to read the backup result?
I will take a shot at explaining, although I am sure some of the Veeam team members will correct me!
Data Read = That is the total drive size, listed as 50GB you most likely have a 50GB volume size
Transferred = That is the amount of data the backup job transferred to the destination. This will be much smaller than the Data Read because it does not need to copy all the data each time it backups, just the small incremental changes.
Backup Size = For me this is usually close to the Transferred size, but Backup Size lists the actual size on disk that the backup job used which disk usage sizes can vary from the true data size that was transferred.
Dedupe = Deduplication is the process of using similar data blocks and only making a single copy of them so you can have smaller backups for each jobs. In VEB this doesn't apply much because each VEB job is a single server. When you use VBR and you set a backup job to backup multiple virtual servers that were created with the same image this saves a bunch of backup space. Think of 5 servers that all have the same C:\Windows folder. In deduplication it would only backup 1 copy of that folder even though 5 servers use it. In a VEB job I would not expect this value to vary much as it only backs up a single server per job.
Compression = This process decresease the size of the backup on disk, so it takes all the backup data and compresses it to a smaller size to save space.
Hope that helps,
Cheers!
Data Read = That is the total drive size, listed as 50GB you most likely have a 50GB volume size
Transferred = That is the amount of data the backup job transferred to the destination. This will be much smaller than the Data Read because it does not need to copy all the data each time it backups, just the small incremental changes.
Backup Size = For me this is usually close to the Transferred size, but Backup Size lists the actual size on disk that the backup job used which disk usage sizes can vary from the true data size that was transferred.
Dedupe = Deduplication is the process of using similar data blocks and only making a single copy of them so you can have smaller backups for each jobs. In VEB this doesn't apply much because each VEB job is a single server. When you use VBR and you set a backup job to backup multiple virtual servers that were created with the same image this saves a bunch of backup space. Think of 5 servers that all have the same C:\Windows folder. In deduplication it would only backup 1 copy of that folder even though 5 servers use it. In a VEB job I would not expect this value to vary much as it only backs up a single server per job.
Compression = This process decresease the size of the backup on disk, so it takes all the backup data and compresses it to a smaller size to save space.
Hope that helps,
Cheers!
VMCE v9
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: How to read the backup result?
No comments on Jax's explanation actually...
Cheers
Mike
Cheers
Mike
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: How to read the backup result?
Mike,
Just push the 'Like Jax's post' button then
Just push the 'Like Jax's post' button then
-
- Enthusiast
- Posts: 26
- Liked: 2 times
- Joined: Apr 21, 2015 11:50 am
- Full Name: Suresnes
- Contact:
Re: How to read the backup result?
Thanks a lot @JaxIsland7575 for the explanations.
I just have one comment about it: I do not have any 50GB volume on this server.
I just have one comment about it: I do not have any 50GB volume on this server.
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: How to read the backup result?
What is the backup mode you are running and what was selected as a source for backup job? Thanks
-
- Enthusiast
- Posts: 26
- Liked: 2 times
- Joined: Apr 21, 2015 11:50 am
- Full Name: Suresnes
- Contact:
Re: How to read the backup result?
This is the Volume Level Backup because I only need to backup 2 of 3 volumes : C: and F:
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: How to read the backup result?
So the actual data read during the incremental run for both volumes C and F was ~50 Gigs. Sounds correct, or am I missing something?
-
- Enthusiast
- Posts: 26
- Liked: 2 times
- Joined: Apr 21, 2015 11:50 am
- Full Name: Suresnes
- Contact:
Re: How to read the backup result?
Actually C: is 115 GB
and F: is 22.6 GB
so the size of C: and F: is much more than 50 GB: 137.6 GB theoratically.
but when I take a look at the size in the Repository, it is 43 GB + incrementals
and F: is 22.6 GB
so the size of C: and F: is much more than 50 GB: 137.6 GB theoratically.
but when I take a look at the size in the Repository, it is 43 GB + incrementals
-
- Veteran
- Posts: 391
- Liked: 107 times
- Joined: Apr 27, 2015 1:59 pm
- Full Name: Ryan Jacksland
- Location: NY, USA
- Contact:
Re: How to read the backup result?
I have found a VBR post that has another definition of the read column
Original link: http://forums.veeam.com/vmware-vsphere- ... 15219.html
Cheers!
This looks more like the amount of data that changed rather than the total amount of data that exists.Our understanding of the "read" value is that it represents the number of changes on the source VM before de-duplication or compression is done - is this correct?
Why is this read value so high for these machines?
Original link: http://forums.veeam.com/vmware-vsphere- ... 15219.html
Cheers!
VMCE v9
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: How to read the backup result?
That is correct. The ‘data read’ counter is related to the read blocks, changed since the last backup job run.
Who is online
Users browsing this forum: No registered users and 21 guests