Summary:
Total DB's analyzed: 1108
Total DB's skipped due to errors: 0
Total Size of NSF's Examined: 374.1 GB Total Attachments found: 531489
Total Duplicate Attachments found: 297511
Total DAOS Eligible Attachments found: 531489
Estimated Size of DAOSified NSF's: 57.3 GB
Estimate Size of DAOS dir: 167.9 MB
Total Disk Savings: 157.8 GB
That comes to a savings of 42%, according to my rudimentary math skills. I expect even more reduction in disk space when we turn on design and document compression.
The README file that you really ought to read before running daosest, shows the switches you can use:
You can either run the DAOS Estimator with the server up or down. To run it on the server you can type 'lo daosest [parameters]' or to run it with the server down go to a command prompt and cd to the Domino directory. Then type daosest -h to the get help screen as shown here:
IBM DAOS Savings Estimator tool, Version 1.0
Copyright (c) IBM 2008. All rights reserved.
daosest[OPTIONS]
-h display this message
-ooutput to file
-v Verbose, display's file information.
. . . You can send the output to a file using the -o option. The advantage of using this feature versus piping the output to a file is that information is still sent to the console to let the user know what database is currently being analyzed. Also the file output is slightly wider, allowing for better readability.
Technorati tag: DAOS Lotus Domino
Comment posted by paul02/24/2009 05:56:48 AM
OK, estimation data sounds good but people don't see what will happen after DAOS is implemented.
You will typically setup the prune period to 30-60 days (it is recommended by IBM due to backup issues). It means that in these 60 days you will have in your disk many many attachments that should not be there anymore. These attachments come from deleted emails and from SPAMS (even if your antispam software deletes the email, DAOS will put the attachments there).
So it will in practice increase the disk space and you will backup garbage.
My boss asked me to implement DAOS but after researching in deep about it, we talked and we decided not to go ahead.
Anyway the estimator results shows how "uneducated" the users are... even with DAOS if users send big atts to many many persons it will mean loss of bandwidth thus server performance issues. And DAOS estimator does not show emails sent to internet!
Comment posted by Vitor Pereira02/24/2009 06:07:32 AM
Homepage: http://www.vitor-pereira.com
@Paul - do you just copy & paste this stuff or do you write it every time you comment on someone's blog?
Comment posted by Andrew Pollack02/24/2009 06:54:17 AM
Homepage: http://www.thenorth.com/apblog
@Paul - you make the assumption that -ALL- users delete the files from their mail files more frequently than every 30 days. DAOS would only increase use size if every single one of your users deletes every file attachment in less time than that 30 day pruning cycle, and that even in that case you don't run the pruning cycle more frequently.
If even one of your users keeps each of those files, DAOS will at the very least break even, and will provide savings of 1 * filesize for each additional copy of the file in every mail file.
If every one of your users is so disciplined as to delete all file attachments from email in less than 30 days, then there is no reason not to set the pruning cycle time to shorter -- say 7 days for your perfect user population.
There may be very good reasons for some places not to deploy DAOS -- particularly until backup and restore issues are more well understood and best practices have evolved and been tested by the user base as a whole. That's why its not mandatory or automatic. The reasons you mentioned, however, are not among them.
BlogSphere V1.3.1
Join The WebLog Revolution at BlogSphere.net