"Read" is amount of data read from disk (zero blocks are omitted/skipped). As regards "transferred" metric then this is the amount of data transferred to target, after source-side dedupe and compression. On the target side this data is uncompressed, because replicated VMs have to be stored in native format, uncompressed. That is why dedupe and compression are reported as 1.x.
1.OK so the Read i understood and thought about it so you assured me , thanks.
2.we can disaTransfered Data should be but more than 1.4 GB ,or not? the 2 Machines are 12 GB , very ODD .
3.Backup Size 480 MB, what does it mean because its not Backup , its a Replication job.
4.Dedupe & Compression. you say only with Replication i will see always the same ? always 1.x ?
2. Not at all, since only 3.4 GBs of data has been read and was compressed to 1.4 GBs, which makes sense if you have many files that can easily be compressed (Word docs etc.). What kind of data do these servers have?
3. According to your report below, this number disaplays the "Horizon Connector" VM transferred data. Let me take a look at my replication job reports for more info.
4. Yes, compression will always be 1.x, but the dedupe ratio might not.
Ok, I have just looked through my internal lab reports and it seems to be a bug in this report. In my case "backup size" is reported as one of the "transferred" sizes, while "backup size" should be the size of VM replica including all restore points (snapshots). Thanks for the heads up!
It seems that the amount of transferred data for the first VM has been picked up as the "Backup size". I'm wondering what product version you're using. Thanks.
I don'y believe its the v7.x because i confirmed myself with the jobs so it works good , i think that maybe you need to update to latest version and than continue.