My average mailbox move takes around 5 minutes. Actual risk of mail being NDR'd is a number significantly close to zero (e.g. I moved 1100 users from one server to another one evening and received 0 complaints about bounced or missing mail). Mail which is sent during that time is bounced, not lost, so the sender can simply try and resend the message... not like the occasional odd NDR doesn't happen anyway.
What's the actual problem we're trying to solve here or is this just an academic exercise? -----Original Message----- From: Herold Heiko To: Exchange Discussions Sent: 1/29/2002 6:01 AM Subject: RE: Move mailbox = can't reveive ? OK users should not be connected during move mailbox - no problem. But mail can't be delivered ? Let's see, this means a) every connector on every exchange server must be down, no user anywhere must be connected, or b) every connector on the source and destination server must be down, they must not be able to communicate with any other exchange server in the same org/site, but they still must be able to communicate with a domain controller. Oh, no user logged in those two servers obviously. Seems not exactly an easy task if you don't want to risk loosing mail during a move mailbox... is there any way to do this ? Every network has moments when there are few users and external mail is trickling in slowly, but still not 100% sure. For the drive space issue... I was still thinking, what if on a partition is say, pub.edb only ? BTW I'm just copying the exchange resource kit and service pack on that partition :) Heiko _________________________________________________________________ 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]
