2 Responses to “Introducing the DXi6701 and DXi6702. Deduplication Without Compromise.”

  1. matt says:

    will it support arbitrary 3rd party storage as target? The $/TB for these appliances is far beyond obscene. I don’t mind buying the head unit and the software and intelligence that go with. But I want to hook up arbitrary SAS/FC/iSCSI-presented LUNs to the unit. Think budget storage enclosures the like of BackBlaze or HP MSA600 or DDN/NexSan bulk expansion chassis.

  2. We also realize that cost is important. You might be surprise at the pricing of the new DXi6700 units–they are substantially lower than earlier generations, and about half the cost of competitors. Users also tell us that they save enough money by putting dedupe appliance that the systems pay for themselves in less than a year–pay attention to operating expense as well as acquisition.

    Technically, putting a dedupe head on generic storage can work, but it usaully means substantial compromises in performance and utility–more than we think makes sense for most customers. It also requires significantly increased qualification testing which raises costs. That’s becuase to work well, the disk needs specific RAID configuration, the data integrity features of the disk subsystems need to integrate with the appliance itegrity protocols, reporting features need to support detailed, disk-level details, and full regression testing has to be maintained across multiple applications and oerating scenarios. Those issues don’t mean that this product approach won’t ever make sense, but it helps to explain why several vendors who started down that path ended up focusing instead on providing more traditional appliances.

Leave a Reply