rowl
ADSM.ORG Senior Member
TSM 8.1.0.0 on Linux.
I have some puzzling numbers that I am trying to understand. I ran a generate dedupstats for everything on my server, then when I select * from dedupstats I summed up the columes and see values like Protected = 200TB, Physical=40TB, Total Saved 160TB. So it appears around 80% savings and I am happy with that.
When I look at the TOTALSUROCC from the Status table it shows 200TB, and the used space in the file systems that make up my directory container storagepool add up to 200TB. Since this TOTALSUROCC is what we are licensed against I am concerned.
I was expecting the disk usage to be proportional to the deduplicated/compresses size of the data. So in this case 40TB (or maybe 80TB to account for 1/2 full containers) not the full size of the protected data.
The other puzzling thing I see here is that on the target server that I run protect stgpool and repl node to, the "Additional space for protected data" from q stg f=d is 5.5TB. Everything from the above source server is covered by the protect stg and node replication processes, so I don't see how I could only be storing 5.5TB there.
Does anyone have some insight into these values? Maybe we have a fundemental misunderstanding of the these, but I have not been able to find good definitions anywhere.
Thanks
-Rowl
I have some puzzling numbers that I am trying to understand. I ran a generate dedupstats for everything on my server, then when I select * from dedupstats I summed up the columes and see values like Protected = 200TB, Physical=40TB, Total Saved 160TB. So it appears around 80% savings and I am happy with that.
When I look at the TOTALSUROCC from the Status table it shows 200TB, and the used space in the file systems that make up my directory container storagepool add up to 200TB. Since this TOTALSUROCC is what we are licensed against I am concerned.
I was expecting the disk usage to be proportional to the deduplicated/compresses size of the data. So in this case 40TB (or maybe 80TB to account for 1/2 full containers) not the full size of the protected data.
The other puzzling thing I see here is that on the target server that I run protect stgpool and repl node to, the "Additional space for protected data" from q stg f=d is 5.5TB. Everything from the above source server is covered by the protect stg and node replication processes, so I don't see how I could only be storing 5.5TB there.
Does anyone have some insight into these values? Maybe we have a fundemental misunderstanding of the these, but I have not been able to find good definitions anywhere.
Thanks
-Rowl