Subject: Not sure if this leads anywhere - still my comments
DAOS is a nightmare! I would advise not to touch it=> Nobody is focing you to do so - and one of the very best Admin I know did detailed testings even before it got public beta, and was impressed by it.
- Cluster servers (you need one DAOS repository per server)
=> If it would not be so, I’d be asking for at least an option to get it this way (cluster failover - one server down, I still want all data accessible)
- DAOS Requires transaction logging (transaction logs should be on another server so it doubles your numbers of servers) and will reduce your server performance by one third.
=> from all what I know, transactional logging is, if making a noteable change in server performance at all, as likely going to improve server performance than to cost anything. (Based on high load server and dedicated harddrives for the log - I have never seen any other numbers). If there is different numbers out there, I would like to learn (Do you happen to have any links?)
- Security (you can visit directly the attached files in the DAOS file system repository (even when in Huffman format, you can easily decode them by program). It is so very easy for a hacker to have a program scanning all the attached files of all of the users searching for particular keywords (EVEN THE ONES IN DELETED EMAILS because they are not removed automatically) and to pick only the ones needed) on a USB flash drive.
=> From what I know, it can be switched on and off database by database. Everyone is free to use and decide any way.
=> From what I know, the files are removed, but with a time distance of something like 2 or 4 weeks. This way for many restore procedures, it is enough to restore the database, as the files are likely to still be there. To me this looks like a good compromise between deleting immediately and never - there is good reasons to ask for both.
=> Encrypted file systems are available - often enough out of the box of the OS manufacturer, and I guess it is a tough world we live in, with lots of other problems, too, if we can’t expect harddrives and their access in carefully monitored servers in server rooms to be save in general.
- Consistency / backups. You cannot backup a NSF file doing a file copy. The attached files are not in anymore.
=> True. Not to store an attachment send to 12 people at the same time in 12 different databases was the intended target from the very beginning. If it is a requirement to store it 12 times (as basic to have it on tape 12 times) I guess it is the wrong tool - But I honestly don’t see how something working better for this purpose would have to be designed.
- What about millions of file inside a Windows file system??? Is it only supported???
=> Sorry, not sure, what you are trying to say. - A limitation of the number of files on the harddrive? Or in one single Folder in the harddrive? - I honestly don’t know where the limitations are, if they would apply, and if the propper measurements are done.
This is simply crazy to see IBM providing a such unprofessional answer to volume issues.
=> If you care to do so, can you share the idea how something better from your point of view would have to look like?
It is well known by any senior Notes/database administrator that moving files outside databases (and particularly for email databases) and replacing them by links is the source of tons of problems because the consistency and security of the databases is lost.
=> Not sure if a file in an nsf is more secure than outside in general, but I take your point.
These kinds of “features”, like the previous SCOS “Single copy Object Store” that as NEVER worked, will kill Notes in time.
=> I take this point too, but for me, going thru the SCOS concept ment to be convinced, that this is not what I want, and DAOS is -from a high level view- different, and to me worth trying. However, if you got bitten by SCOS, and decide to stay away from DAOS at least for now, I can understand this very well.