DAOS Updates for Domino 8.5.1
September 22 2009
Now that we know Domino 8.5.1 is just around the corner (thanks, Ed Brill!), it's time to wet your whistles a bit on what you're going to see! Let's talk about something I know you'll really like .... DAOS!! Just when we thought those Lotus developers couldn't get any better, they've gone and outdone themselves! Here's what's coming for DAOS in 8.5.1.
As we talk about what's new, we need to make sure we understand what you *already* get as a part of DAOS in Domino 8.5.
Currently, when an email is received that has an attachment in it, the attachment is extracted and stored in an external file (NLO). DAOS then determines if the DAOS store already has a copy of the attachment and if so, latches on to the existing copy of the object, bumps the reference count, and then deletes the duplicate object. This happens on each server that receives the email - and each server would receive and store its own copy of the attachment. With this, you get net disk savings because only one copy of the attachment is stored, BUT, unfortunately, that's limited to a server-by-server basis..there is NO savings when that file is transferred across the network.
Now, we've talked before about how DAOS saves you I/O operations on the server. This is because in processes like copy-style compact, DAOS can detect that we are copying a DAOS object from a DAOS enabled database on the server to another DAOS enabled database on the same physical server, and then short-cut the process and just increment the reference count of the object and return a "DAOS ticket" to the database getting the new copy. Essentially, this is copying the DAOS ticket instead of copying the object itself. We call this inter-server copying. Again, you get savings in I/O operations and bytes written for inter server objects, but NO savings across servers.
So now that we're all on the same page, let's talk about what's NEW in Domino 8.5.1...!!!
Let's face it...most of us have multiple servers in our environments. And, as mail messages, etc. move from one server to another server, there's a lot of copying of objects (ie. replication) that goes on. In Domino 8.5.1, DAOS is now enhanced so that it can EXTEND its optimization between clients and servers, and among servers!! This is intra-server copying! So, instead of sending a copy, the sending server says "I'm sending you an attachment with this unique key" and the receiving server can say "Wait..I already have it, here's the ticket..send that to me instead" or "Yup, it's unique, send the whole attachment, but only send it once for all my users"!! Make sense? So now, DAOS is smart enough to save you bandwidth across the network - and even better - this will happen automatically between any two 8.5.1 clients and/or servers as long as the recipient is DAOS enabled!! That's right...the sender does not need to be using DAOS!
There's a lot of potential here! Imagine if you will, you are at home and you're about to send an email with 2 large attachments on it. In the past, you would send the email and "wait" while replication occurred and those attachments got sent. NOW though...if those attachments already exist on the server, only the ticket gets sent...NOT the entire attachment!! So, a replication process that might have taken you minutes before only takes seconds now! Talk about making it easy!
Now, obviously, there's a great more detail involved than what I've just outlined for you - and a lot more that's coming! (a LOT more) But, you get the idea here. DAOS goes one step further in 8.5.1 to save both network bandwidth AND disk I/O AND disk space in your Domino environment! So now we see...
Now, you just need to get to Domino 8.5.1!!!
Really...does it get any better than this????!!
As we talk about what's new, we need to make sure we understand what you *already* get as a part of DAOS in Domino 8.5.
Currently, when an email is received that has an attachment in it, the attachment is extracted and stored in an external file (NLO). DAOS then determines if the DAOS store already has a copy of the attachment and if so, latches on to the existing copy of the object, bumps the reference count, and then deletes the duplicate object. This happens on each server that receives the email - and each server would receive and store its own copy of the attachment. With this, you get net disk savings because only one copy of the attachment is stored, BUT, unfortunately, that's limited to a server-by-server basis..there is NO savings when that file is transferred across the network.
Now, we've talked before about how DAOS saves you I/O operations on the server. This is because in processes like copy-style compact, DAOS can detect that we are copying a DAOS object from a DAOS enabled database on the server to another DAOS enabled database on the same physical server, and then short-cut the process and just increment the reference count of the object and return a "DAOS ticket" to the database getting the new copy. Essentially, this is copying the DAOS ticket instead of copying the object itself. We call this inter-server copying. Again, you get savings in I/O operations and bytes written for inter server objects, but NO savings across servers.
So now that we're all on the same page, let's talk about what's NEW in Domino 8.5.1...!!!
Let's face it...most of us have multiple servers in our environments. And, as mail messages, etc. move from one server to another server, there's a lot of copying of objects (ie. replication) that goes on. In Domino 8.5.1, DAOS is now enhanced so that it can EXTEND its optimization between clients and servers, and among servers!! This is intra-server copying! So, instead of sending a copy, the sending server says "I'm sending you an attachment with this unique key" and the receiving server can say "Wait..I already have it, here's the ticket..send that to me instead" or "Yup, it's unique, send the whole attachment, but only send it once for all my users"!! Make sense? So now, DAOS is smart enough to save you bandwidth across the network - and even better - this will happen automatically between any two 8.5.1 clients and/or servers as long as the recipient is DAOS enabled!! That's right...the sender does not need to be using DAOS!
There's a lot of potential here! Imagine if you will, you are at home and you're about to send an email with 2 large attachments on it. In the past, you would send the email and "wait" while replication occurred and those attachments got sent. NOW though...if those attachments already exist on the server, only the ticket gets sent...NOT the entire attachment!! So, a replication process that might have taken you minutes before only takes seconds now! Talk about making it easy!
Now, obviously, there's a great more detail involved than what I've just outlined for you - and a lot more that's coming! (a LOT more) But, you get the idea here. DAOS goes one step further in 8.5.1 to save both network bandwidth AND disk I/O AND disk space in your Domino environment! So now we see...
- Net disk savings because only one copy of the attachment is stored
- Option to use a separate, low-cost storage device for attachments
- Savings in I/O operations and bytes written for inter-server object copies
- Savings in bytes transferred across the network
- Savings in I/O operations and bytes written by other servers
Now, you just need to get to Domino 8.5.1!!!
Really...does it get any better than this????!!
