The official recommendation ...
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q259751.
According to this, you may only need as little as 10MB to free up the
service.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Jim Brady
Sent: Monday, January 28, 2002 10:01 AM
To: Exchange Discussions
Subject: RE: Move mailbox = can't reveive ?

Users shouldn't be connected to the server while their mailboxes are
being moved, nor can mailboxes accept mail while they are being moved
(assuming your using the mailbox tool).

1 GB question - done this myself and works great ... freeing up a few
hundred MB does get the store back up quickly, although I've never see
this on a best practices list.  Quicker than moving the logs to another
drive.  

Jim

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Herold Heiko
Sent: Monday, January 28, 2002 6:30 AM
To: Exchange Discussions
Subject: Move mailbox = can't reveive ?

EX4.4 sp4

say, server Gateway (IMC connector only), server A and server B
(mailboxes).
During move mailbox from A to B arrived a incoming mail (smtp to
Gateway) for the mailbox on the move.
server A sent back a reply Your message ... did not reach the following
recipient(s):

<Display name> on Mon, 28 Jan 2002 12:33:39 +0100
     Unable to deliver the message due to a communications failure
        The MTS-ID of the original message is: c=us;a= ;p=<...>
;l=<Gateway>020201281117D5DWCYXN
     MSEXCH:MSExchangeMTA:<site>:<server A>

Is this normal ? During move mailbox incoming external mail is rejected
? I could not find any reference to this in technet (well, searched only
for a couple of minutes to be honest, found nothing related).

Similary, I was looking exactly when a services will shut down for no
more space available (now you know why I'm moving mailboxes :), the only
thing I found was several references (EX 5.5 Server Guide, Administering
and Maintaining, the Disaster Recovery White paper and similar) to
res1.log and res2.log. Those are 5MB each and are used as last resort
when the disk is full - does this mean services shut down really at the
last moment (new page can't be allocated) ?
Somehow I always thought it would shutdown with some % of disk space
still available.

If the services do shutdown when the store partition is really full
could it be considered a good practice creating a 1GB (or something)
file, which can be deleted in order to create space as last resort...
say, to restart services and move somewhere else some mailboxes or
public folders ?
Then decide if to spank the users who eat space like peanuts or the
managers who want won't allow space limits, in order to use the
"infinite resources" approach for supposedly faster development but
won't fund the same infinite (or at least sufficent) approach to server
space ?
 
Heiko

-- 
-- PREVINET S.p.A.            [EMAIL PROTECTED]
-- Via Ferretto, 1            ph  x39-041-5907073
-- I-31021 Mogliano V.to (TV) fax x39-041-5907087
-- ITALY

_________________________________________________________________
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]

Reply via email to