|Professional Services||Second Signal||Presentations||Andrew's Blog||Support|
This morning, I set up DAOS on my Domino 8.5 Beta server. Its a Win32 machine running in my office. My customer facing servers are not upgraded yet. Since my mail file is replicated onto more than one clustered server, I saw no danger in giving DAOS a try today. So far, everyone I know who's been testing it is increasingly comfortable with its ability to handle problems as well or better than data stored in the NSF natively.
DAOS pulls file attachments out of the NSF and stores them in an arcane file tree on disk maintained by the Domino server. It eliminates duplicates of the same file (based on hash values) and It is TOTALLY transparent to users. When you open documents, you see the attachments as normal. If you have local replicas, they're unaffected. You literally cannot tell unless you're in the Admin client and looking for the information. It's what the old "single copy object store" was supposed to do (at least the way we wanted it to), but never worked out at all.
Setting it up means enabling it on the server document, setting a couple of options on the database advanced properties, and running a copy-style compact on the database. I knew I'd see some heavy benefit, but didn't expect to see a 50% reduction in the total disk space used. At the end of the run, I've gone from half a gigabyte to well under 250megs. On top of that, nearly 200 megs of file is now stored in DAOS which means that view updates and anything else requiring a database scan is going to be much faster.
The real big value comes when you look at using DAOS in places with many mail users sharing files. The lack of duplication should be tremendous.
Please wait while your document is saved.
the attachments DAOS? I wonder if the Domino Backup APIs see them or if there
is some other process we will need to use