Comprehensive data protection for all workloads
- Posts: 85
- Liked: never
- Joined: Mar 03, 2011 4:48 pm
- Full Name: Enrico
I did some checking and calculation from last weekends full backups. The speed varies a lot ranging from 16MB/s to 40MB/s sometimes even when backing up from the same LUN. This speed is the real speed not the processing rate. With real speed I mean, actual used disk space in the VM (not the vmdk size) divided by the processing time minus 1minute.
Why is that? Differences at dedupe or compression? Unfortunately I can't say because they were all backed up in one job and I see the Dedpue/compression ratio only for the whole job.
- SVP, Product Management
- Posts: 28238
- Liked: 5013 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
I am splitting this into the new topic, not to hi-jack the original thread. The difference is caused by whitespace (zeroed blocks) and duplicate blocks (already backed up by the same job). Both increase the VMDK processing rate because there is no need to read and write certain blocks. Thanks.
Users browsing this forum: Bing [Bot], Google [Bot] and 29 guests