Dedupliation appliance as primary repo

It is definitely possible, but the performance will not be the same as sending to ReFS/XFS or even NTFS.  It is recommended to send to block then use Dedupe appliances for LTR versus primary repo.  I know even with using DDBoost for Data Domain the speeds are still not the greatest and especially doing Synthetic Full backups too is painful.

If this is what the budget allows, then you need to set expectations that backups may or may not complete in the window.  Copy jobs and tape jobs can run off schedule so no issues there.

I agree, the magic of deduplication pays the price of performance.

With my little of experience, when you setup those appliances, you can choose if you want to “enable” or “turn on” deduplication on each repository you create.

So for me, a good approach would be to setup the primary DXI with a none dedup repo for first / initial copy, and then a second repo, secondary copy deduped for better retention / space optimization.

The second DXI, even replicated from the primary one natively with quantum functionality, or also a backup copy job destination deduplicated for very long archive / secondary copy with full dedup capabilities.

Just a quick and simple idea.

cheers.

Agree with my colleagues, always a bad idea using deduplication devices as primary repositories…. I never recommended it using like this : the performance is bad.