HP StoreOnce D2D2500 Implementation Manual page 20

Figure 18: Backup—results Incremental
vRanger efficiently removes whitespace (unallocated blocks and zero filled blocks) and deleted data before sending it
to StoreOnce Backup System, which further enhances this with inline target deduplication. The deduplication ratio
above is calculated as User Data Stored/Size On Disk. Remember that the original disk size for the selected VMDKs
was 432 GB. If we take that in consideration, the end-to-end deduplication values are over 30:1.
vRanger Resource Management needs to be tuned as we only had 2 ESX(i) hosts and want to be able to run three
simultaneously backup tasks. If we add more CPU to the vRanger virtual or physical machine, the maximum number
of tasks per Repository and locally can be increased accordingly.
Figure 19: vRanger Resource Management
To measure how much longer it takes to restore from a chain of incremental backups compared to a full backup we
used a 50 GB Windows virtual machine. It was restored using vRanger LAN-Free option. In our test case it reads the
virtual machine data over LAN from the StoreOnce Backup System and then uses the VMware vStorage API to write
data directly to the 4 Gbit/s Fibre Channel SAN. The time difference was only 14 percent. This was achieved
because vRanger never restored the same blocks multiple times from different Savepoints, only the blocks needed to
recreate the backup were restored from the required incremental backups in the restore chain.
20