The best part of cc:Mail? Asking a user to clean out their mailbox, they go to l:\ccdata and *boom* Full access to the database ftw. [cid:image001.jpg@01CB8587.60B317A0]
From: Don Ely [mailto:don....@gmail.com] Sent: Tuesday, November 16, 2010 11:05 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2010 deployment question I didn't want to remember CC:Mail... On Tue, Nov 16, 2010 at 8:01 AM, Jeff Steward <jstew...@gmail.com<mailto:jstew...@gmail.com>> wrote: LOL, yeah, I worked with that too, and a few versions of ::shudder:: CC:Mail. -Jeff Steward On Tue, Nov 16, 2010 at 10:53 AM, Don Ely <don....@gmail.com<mailto:don....@gmail.com>> wrote: MS Mail 3.0 was the shizzle... On Tue, Nov 16, 2010 at 5:47 AM, Jeff Steward <jstew...@gmail.com<mailto:jstew...@gmail.com>> wrote: Those three sentences made me think "Wow, we've come a long way since Exchange 4." -Jeff Steward On Tue, Nov 16, 2010 at 8:39 AM, Michael B. Smith <mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote: Yes. You need DAG for MB role, HT automatically does failover HA/FT, and a RPC Client Access Array on the CAS. The only challenge is that for true HA/FT, you'd need to load balance the CAS. If you don't load-balance CAS then you'll need to have a DNS entry for the FQDN of the RPC CAA with a low TTL and in the case of an extended failure, switch the IP address. (I teach a full day class on this, and that's not long enough to cover all of the various details, but those are the basics of the class in 3 sentences.) Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com<http://theessentialexchange.com/> -----Original Message----- From: Maglinger, Paul [mailto:pmaglin...@scvl.com<mailto:pmaglin...@scvl.com>] Sent: Tuesday, November 16, 2010 8:33 AM To: MS-Exchange Admin Issues Subject: Exchange 2010 deployment question We're working with a company to transition from Exchange 2003 to Exchange 2010. One of the features that excited me about Exchange 2010 was the ability to have database replication between two servers. My question - is it possible to have database replication and failover between the two servers if all the roles are on the two individual servers? I am not talking about high availability. I understood that there could be replication between two servers and if one of the two failed the other would take over. The difference is that with high availability the change would take minutes and with the other it could take 20-30 minutes. Much thanks. -Paul --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
<<inline: image001.jpg>>
