Oddly enough, there was a FAQ about this appended to the bottom of your
message.  And now twice, at the bottom of this one.  

I'll prepend it, too:
http://www.swinc.com/resource/exch_faq_appxf.htm

> -----Original Message-----
> From: msxlist [mailto:[EMAIL PROTECTED]]
> Posted At: Saturday, September 08, 2001 06:07 PM
> Posted To: MSExchange Mailing List
> Conversation: PST, OSTor IS message storage
> Subject: PST, OSTor IS message storage
> 
> 
> dear all,
> 
> somehow i've managed to get in to a philisophical discussion about the
> best place to store messages. my opinion has always been that 
> the IS (or
> an OST) is the place. my colleague prefers PST's.
> 
> i think there was a thread in days gone by which discussed 
> the pros/cons,
> or maybe there is a FAQ on this.
> 
> off the top of my head, the "bad things" about PSTs are:
> 
> - loose single instance store
> - increase storage requires (rtf + plain text)
> - exposed to corruption and performance degradation if pst > 512Mb
> - loose ability to manually scan for PST-resident virus infections
> - increase bandwidth - eg 10 messages over WAN to 10 clients, 
> rather than
> 1 message over WAN to server, then 10 messages to clients over LAN
> increased reliance on scarce/expensive, inherently less reliable WAN
> capacity
> - loss of access to mailbox manager functionality
> - security exposure - lost notebook with PSTs much more likely to give
> access to stored email than server resident mailbox
> - more to configure in profile
> - not all rules will work (server side vs client side)
> - if a machine crashes, and the PST is in the default 
> location, mail goes
> with it. likewise, finding and saving the PST/PAB is another 
> thing to do
> during PC cascades
> - storage is more efficient with automatated whitespace 
> recovery on the
> IS, but no way to centrally manage PST compaction
> 
> the "good things" i can think of are:
> 
> - users become responsible for their own storage limits (do 
> they really ?
> will they not just lob their PST on to a network drive and 
> make the file
> system backup bigger, rather than the exchange server backup ?)
> - if the PST is on a network drive, mailbox-by-mailbox restores are
> relatively easy.
> - In moving mailboxes from one org to another, one of the 
> first steps is
> to get user messages out in to a PST. If you work with PSTs 
> anyway, you've
> got a head start.
> 
> Paul
> 
> 
> _________________________________________________________________
> List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
> Archives:               http://www.swynk.com/sitesearch/search.asp
> To unsubscribe:         mailto:[EMAIL PROTECTED]
> Exchange List admin:    [EMAIL PROTECTED]
> 

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to