Um, there's no SIS between vaults that I know of. I'd still like to jump on the bandwagon and recommend the two vaults tho. Why? Well, let's put security, and all the other reasons you might think you want to do it, and put it in the happy box. There, isn't it happy? Okay, the reason I usually advocate is this: Files and emails are different things, and they get used differently. Not only is it a good idea to put these things in to seperate vaults, it's a good idea to put these vaults on different servers so they have their storage service and archive space. All this sorta assumes you're in a >1000 user environment. If you're smaller then that, and don't want a second server (silly person), then sure, nuthing wrong with putting everything on a single server (still recommend two sep vaults). Converse is also true, no matter how small you are, if you're archiving aggressively from either source, then it makes sense to seperate out the services. A bunch of reasons for this, performance, predictability, availability, moxy, and um...a bunch of others.
Usually I tell people this, and they shake their head at me. So then I have to say, "Besides, imagine if you have a gig archive of mail and files. You're looking for a file you got in email, that you copied to your archived homedir. You do a search from the website, guess how many hits you get. At least 3. One fer the msg, one for the attachment, and then one for the file. It makes sense logically to most humans to search seperately for those data types, and trust me, the pull down is really not hard. They will get used to it." Then most people nod.
Okay, less coffee in the future I promise.
micah
