Writing Exchange 2003 DR documentation
in [Microsoft Exchange]
|
From: Mike on 26 Apr 2010 04:29 Hi there, I'm not sure to be in the right group. I will however post my message here. I actually don't have problems with my exchange environment, my question is more disaster recovery oriented. I'm trying to put in place all possible problem scenarios with decision tree to help decision maker.take decisions (in case of disaster). I'm System engineer in the company, and competences are more active directory oriented. However, in my daily job, I support exchange users and I'm "exchange administrator" too. You know, budget restrictions. So, I will ask if any of you guys have written such exchange 2003 DR document and on what I must pay attention. If you have some external links just don't hesitate to send it to me. I will highly appreciate your ideas. Many thanks in advance for your help and your time. Mike
From: Mark Arnold [MVP] on 26 Apr 2010 10:27 On Mon, 26 Apr 2010 10:29:34 +0200, "Mike" <no(a)spam.com> wrote: >Hi there, >I'm not sure to be in the right group. I will however post my message here. >I actually don't have problems with my exchange environment, my question is >more disaster recovery oriented. I'm trying to put in place all possible >problem scenarios with decision tree to help decision maker.take decisions >(in case of disaster). I'm System engineer in the company, and competences >are more active directory oriented. However, in my daily job, I support >exchange users and I'm "exchange administrator" too. You know, budget >restrictions. So, I will ask if any of you guys have written such exchange >2003 DR document and on what I must pay attention. If you have some external >links just don't hesitate to send it to me. I will highly appreciate your >ideas. > >Many thanks in advance for your help and your time. > >Mike > Actually MS did a pretty comprehensive one way back in the day: http://technet.microsoft.com/en-us/library/bb125070(EXCHG.65).aspx Have a go through that and see what else you need.
From: Ed Crowley [MVP] on 26 Apr 2010 20:14 And while that's an excellent, authoritative and complete document, it is probably way more than you need or even want for your internal purposes because it is, in a word, massive. I recommend that you start by identifying the disaster scenarios you envision happening, and apply the appropriate techniques to remedy them. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "Mark Arnold [MVP]" <mark(a)mvps.org> wrote in message news:hk8bt5dt5hlcjj4efonnf9u90hmtth22kd(a)4ax.com... > On Mon, 26 Apr 2010 10:29:34 +0200, "Mike" <no(a)spam.com> wrote: > >>Hi there, >>I'm not sure to be in the right group. I will however post my message >>here. >>I actually don't have problems with my exchange environment, my question >>is >>more disaster recovery oriented. I'm trying to put in place all possible >>problem scenarios with decision tree to help decision maker.take decisions >>(in case of disaster). I'm System engineer in the company, and competences >>are more active directory oriented. However, in my daily job, I support >>exchange users and I'm "exchange administrator" too. You know, budget >>restrictions. So, I will ask if any of you guys have written such exchange >>2003 DR document and on what I must pay attention. If you have some >>external >>links just don't hesitate to send it to me. I will highly appreciate your >>ideas. >> >>Many thanks in advance for your help and your time. >> >>Mike >> > Actually MS did a pretty comprehensive one way back in the day: > http://technet.microsoft.com/en-us/library/bb125070(EXCHG.65).aspx > Have a go through that and see what else you need.
From: Mark Arnold [MVP] on 27 Apr 2010 09:09 Oh yeah. Don't print it!
From: Ed Crowley [MVP] on 27 Apr 2010 20:58
unless you own stock in Hammermill. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "Mark Arnold [MVP]" <mark(a)mvps.org> wrote in message news:mgodt5d9s2j2u1rfa7qsfd6tfc6lgc4pj7(a)4ax.com... > Oh yeah. Don't print it! |