Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Exchange Archiving & Database Injections
0 views
Skip to first unread message
charmcitybiz
Oct 8, 2009, 4:51:35 PM10/8/09
to
I recently had a conversation with a few Microsoft Knowledge Experts
and Technical Account Managers. They advised that we should consider
requiring a solution that utilizes Exchange backup and recovery APIs
as opposed to an EAS solution that utilizes custom database injections
to backup/recover Exchange data because it increases the likelihood of
corrupting the Exchange database. Does anyone have any insight to
this and why or why not this should be something we require?
and Technical Account Managers. They advised that we should consider
requiring a solution that utilizes Exchange backup and recovery APIs
as opposed to an EAS solution that utilizes custom database injections
to backup/recover Exchange data because it increases the likelihood of
corrupting the Exchange database. Does anyone have any insight to
this and why or why not this should be something we require?
![Mark Arnold [MVP]'s profile photo](http://lh3.googleusercontent.com/a-/ALV-UjWfOoakncIeAwDFlTp-kGUX3hCQcyUCiH7av8m1Ynjuwi6dWQ=s40-c)
Mark Arnold [MVP]
Oct 9, 2009, 7:54:34 AM10/9/09
to
OK. I've read this seven ways from Sunday and I have no idea what
you're talking about.
You talk about archiving. OK, easy enough. Then you talk about
Database Injections. Err, injected where? To Exchange or to an
Archiving solution?
Huh?
Care to re-think your question?
0 new messages