There seems to be a problem with the database size figures reported by the DAOS estimator for databases smaller than 1 MB.
I have just run version 1.2 of the DAOS estimator tool (offline) against a recently decommissioned Domino 6.5 server to get an idea of how to plan DAOS implementation for it’s Domino 8.5 replacement.
Most of the results seem correct (and very encouraging), but databases smaller than 1 MB seem to have their file sizes reported wrongly. Here’s an excerpt:
Subject: DAOS estimator glitch is a little worse than I thought
As well as underestiating the size of databases smaller than 1 MB, the DAOS estimator tool seems to be applying the same mistaken logic to reporting its calculations for estimated DAOS object size, and projected space savings.
My 400+ databases show about 20 where the estimator thinks there will be 0-0.9 KB of DAOS storage, zero between 1 and 1023 KB and the rest from 1 MB up to 6.6 GB. I’m pretty sure the projected saving for those first 20 databases needs to be multiplied by 1024 (or rewritten as MB).
Subject: More serious errors in Summary output, too
There’s are two more (different) issues with the Summary output that the DAOS estimator produces.
#1. The “Total DAOS Eligible Attachments” line is missing and in its place is a second “Total Duplicate Attachments found” line, next to which the tool reports the overall total attachment number.
#2. The Estimated Size of DAOS Dir figure appears to be out by a factor of 1024 (quoting MB where it should be GB).
Here’s what this looks like in my environment:
Summary:
Total DB's analyzed: 438
Total DB's skipped due to errors: 0
Total Size of NSF's Examined: 504.3 GB
Total Attachments found: 1017299
Total Duplicate Attachments found: 658842
Total Duplicate Attachments found: 1017299
Estimated Size of DAOSified NSF's: 143.3 GB
Estimate Size of DAOS dir: 126.8 MB
Total Disk Savings: 247.8 GB
Compression Statistics:
None: 457840
Huffman: 558936
LZ1: 523
Huffman on LZ1 servers: 0