text: If a signature match is found, the data chunk is replaced by a reference to a stored chunk, 
  which reduces storage space that is required for storing the data. Conversely, if no match is 
  found, the data chunk is stored without modification and its signature is added to the 
  deduplication database. 
  
  To maximize the space that is available for the deduplication database, the system distributes 
  it between all nodes in the I/O groups that contain deduplicated volumes. Each node holds 
  a distinct portion of the records that are stored in the database. If nodes are removed or 
  added to the system, the database is redistributed between the anodes to ensure optimal use 
  of available resources. 
  
  Depending on the data type that is stored on the volume, the capacity savings can be 
  significant. Examples of use cases that typically benefit from deduplication are virtual 
  environments with multiple VMs running the same operating system and backup servers. In 
  both cases, it is expected, that multiple copies of identical files exist, such as components of 
  the standard operating system or applications that are used in the organization. Conversely, 
  data that is encrypted or compressed at the file system level do not benefit from deduplication 
  because these operations remove redundancy of the data patterns. 