We had frequent hardware failures when we had Exchange on the Dell hardware. That was the experience that led us to focus on designing a setup that would allow for "fast" and reliable recoveries. Now that we no longer use the Dell hardware for Exchange we have few problems.
At 03:53 PM 1/8/2003 -0500, you wrote: >I'm more interested in how often he has hardware failures. It sounds like a >common event! > >------------------------------------------------------ >Roger D. Seielstad - MCSE >Sr. Systems Administrator >Inovis - Formerly Harbinger and Extricity >Atlanta, GA > > >> -----Original Message----- >> From: Chris Scharff [mailto:[EMAIL PROTECTED]] >> Sent: Wednesday, January 08, 2003 3:45 PM >> To: Exchange Discussions >> Subject: Re: Exchange 2000 Recovery >> >> >> Doesn't play hell with your SIS? >> >> On 1/8/03 13:20, "John W. Luther" <[EMAIL PROTECTED]> wrote: >> >> >> >> Hey. >> >> We have multiple small exchange servers that do their backups >> to recovery >> servers that have several mirrored drives so no single >> production server has >> any of its backups on the same drive mirror. With our >> database size limit >> we have one recovery server for every three mail servers. In >> addition we >> have at least one "hot spare" mail server. >> >> When there is an outage we note which folks are affected and >> then recreate >> their (now empty) mailboxes on the recovery server to get >> them back into >> email. We then Exmerge the backed-up mail out of the backups >> into the new >> mailboxes. Some tlog juggling has to be done in order to >> recover all mail, >> but it is fairly strait forward. >> >> Each of our servers costs ~6K using "off the shelf" >> components. We learned >> the value of lots of small servers when our Dell PowerEdge >> equipment crapped >> out on us repeatedly early last year. >> >> You could probably do this with three servers, then. One >> for production, >> one for recovery/backups and one hot spare. Under your limit, though? >> Well, I guess that would depend on your shopping ability and >> the components >> you choose. >> >> John >> >> John W. Luther >> Systems Administrator >> Computing and Information Services >> University of Missouri - Rolla >> >> At 11:02 AM 1/8/2003 -0800, Newsgroups wrote: >> >I am not aware of a budget but when I mentioned the solution from >> >"Marathon Technologies" they almost fell off their chairs. >> I think they >> >want to spend somewhere from $3k to $7K (Not sure, as they >> have not told >> >me anything). I told them that for that price the best >> thing they could >> >do is have another server and do a daily restore of the >> database on that >> >box and if the main server dies put up the new one instead. >> What do you >> >think? Any other ideas? >> > >> >Thanks >> > >> >-----Original Message----- >> >From: Chris Scharff [mailto:[EMAIL PROTECTED]] >> >Posted At: Wednesday, January 08, 2003 10:48 AM >> >Posted To: Exchange Newsgroups >> >Conversation: Exchange 2000 Recovery >> >Subject: Re: Exchange 2000 Recovery >> > >> >Seamless, transparent, automatic and cheap? Don't believe >> such a high >> >availability solution exists. Even overspeccing a single box >> to ensure >> >it's >> >fully redundant gets rather expensive on a per user basis >> for only 180 >> >users. What are the actual requirements surrounding the solution and >> >what >> >budget has been proposed to implement it? >> > >> >On 1/8/03 12:27, "Newsgroups" <[EMAIL PROTECTED]> wrote: >> > >> > >> > >> >We are looking into different methods of recovery from >> Exchange 2000. I >> > >> >know there are several ways of doing this. We want to be able to >> >recover w/ out any user interaction (by that we mean it would be >> >transparent to them and they don't want to be down for 4 to >> 6 hours). >> >We have about 180 users. I know we can cluster them but >> they don't want >> > >> >to go that route because of the cost. Will software or hardware >> >replication work and be transparent or are there any other >> technologies >> >that you may be aware of? >> > >> > >> > >> >_________________________________________________________________ >> >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] >> >> >> _________________________________________________________________ >> 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] >> > >_________________________________________________________________ >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]
