I don't think that's how it works Karel, the values are based on managed data and are normally around the same on the source and on the target.
On Mon, Jul 8, 2019 at 9:16 AM Karel Bos <tsm....@gmail.com> wrote: > As the target server only receives already dedupped data it makes sense > their will be no or barely anything to be dedupped. > > Regards, > > Karel > > On Mon, 8 Jul 2019 at 08:16, Stefan Folkerts <stefan.folke...@gmail.com> > wrote: > > > Hi all, > > > > I'm seeing something very strange at a customer site that has two > Spectrum > > Protect servers. > > One receives backups and is the replication source. > > The other is the replication target for that single source and doesn't > > receive any backup data. > > All data goes into a single containerpool on each server. > > > > Check this out: > > > > Containerpool on source: > > > > Deduplication Savings: 35,173 G (52.50%) > > Compression Savings: 16,083 G (50.54%) > > Total Space Saved: 51,255 G (76.51%) > > > > Containerpool on target: > > > > Deduplication Savings: 3,962 G (6.19%) > > Compression Savings: 34,193 G (56.97%) > > Total Space Saved: 38,155 G (59.63%) > > > > Deduplication is all but completely failing on the target. > > Everything is replicated (replicate node *) > > All filespaces and occupancy stats are equal on both sides. > > Has anybody seen this before. > > Running 8.1.7 > > > > Regards, > > Stefan > > >
