Skip Navigation Links

Evaluating Deduplication Solutions: What You Should Really Consider
from  BakBone Software

View This Now

White Paper

Description:
Understand deduplication, and how it can be implemented - single instance storage (SIS) vs deduplication, fixed vs. variable block, inline vs post-process, source vs target-side, and ratios and retention periods. In this paper, we will explain what elements you should consider and how the right decision will make your life easier.

BakBone White Paper Sample

SNIA defines Single Instance Store (SIS) as the replacement of duplicate files or objects with a reference to a shared copy1. While Single Instance Storage is not defined as a deduplication technology by SNIA, many people confuse SIS with deduplication.

The key difference between SIS and deduplication is that SIS evaluates the data stream at the file level by looking for duplicate files while deduplication evaluates the data stream at the block or byte level. With SIS, even a small change to a file will cause it to be seen as a new and different file and be stored again. This means, that if you have a document and a user copies or renames the file, it will be seen as an entirely new file and will be stored again. With deduplication, the entire file contents will be seen as duplicate. As a result SIS delivers less space savings versus deduplication.

View This Now


View all resources by BakBone Software