The Data Transferred section is where everything starts to be different between all scenarios. I’ll skip also the Data Processed and Data Read which is obvious that it’s the RAW capacity allocated on the vSphere VMFS Datastore which is 5 VM x 50GB VMDK files prior to doing any kind of manipulation on the data itself. So for starters as we can see the Processing rate and T hroughput Peak is almost the same in all cases, because the network connectivity are the same here. I’m not a real expert here in the Backup Appliance department and it’s not in my ally but because of my Veeam Backup & Replication projects I only want to point out the results here and the difference between behaviors observed. I’ve created for each of the scenarios a Job with the same five (5) identical windows machines in order to get the highest ratio from each mechanism. Note: For a deep dive on more features of each Deduplication appliance go to the Veeam Backup & Replication help Center section. Data will be transferred fully over the network and the deduplication and compression will be done on the appliance itself. HP StoreOnce currently works with Veeam B&R integration only via CIFS and not using HPs StoreOnce Catalyst which is the matching feature like EMC DataDomain DDBoost. HP StoreOnce - Similar to the EMC DataDomain CIFS behavior that is what we expect from this solution.
Also disable the Veeam Backup & Replication Compression and deduplication mechanism for the specific job as we did with the EMC DataDomain DDboost drivers.
0 kommentar(er)
