locked
Rebooting/shutting down Exchange 2007 server RRS feed

  • Question

  • Hi,

    I have a multi role Exchange server 2007 serving around 400 users. Lately, i noticed that the store.exe is consuming lots of memory and performance is sometimes affected. I plan to shutdown the server in order to upgrade the RAM on the server.

    Question:- Is there any specific procedure on how to shutdown/reboot an Exchange server 2007? 

    Last time, i tried the script below and it turns out that the Exchange information store was stuck in the "stopping" state. I have seen some people mentionning to dismount the databases prior to rebooting/shutting down an Exchange server 2007. Any thoughts?

    http://exchange.sembee.info/2007/shutdown-script.asp

    Any feedback would be much appreciated.

    Regards,

    Dave

    Wednesday, September 26, 2012 3:08 PM

Answers

  • On Wed, 26 Sep 2012 15:08:09 +0000, ITtech1979 wrote:
     
    >I have a multi role Exchange server 2007 serving around 400 users. Lately, i noticed that the store.exe is consuming lots of memory and performance is sometimes affected.
     
    Exchange consumes large amounts of memory to avoid problems with
    slower components of your server (i.e. the storage subsystem). Are you
    sure it's Exchange and not some memory/handle-leaking component that's
    also installed on the server (e.g., Anti-virus/Anti-spam or a bad
    driver)?
     
    >I plan to shutdown the server in order to upgrade the RAM on the server.
    >
    >Question:- Is there any specific procedure on how to shutdown/reboot an Exchange server 2007?
     
    Not if it's running on it's own machine.
     
    >Last time, i tried the script below and it turns out that the Exchange information store was stuck in the "stopping" state. I have seen some people mentionning to dismount the databases prior to rebooting/shutting down an Exchange server 2007. Any thoughts?
    >
    >http://exchange.sembee.info/2007/shutdown-script.asp
    >
    >Any feedback would be much appreciated.
     
    Are you running Exchange on a domain controller? If you are, then
    stopping Exchange services might make sense because of the
    dependancies on the AD from Exchange. Otherwise you probably have some
    other problem with the machine.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Proposed as answer by Evan Liu Thursday, September 27, 2012 8:27 AM
    • Marked as answer by ITtech1979 Thursday, September 27, 2012 12:37 PM
    Wednesday, September 26, 2012 9:31 PM

All replies

  • On Wed, 26 Sep 2012 15:08:09 +0000, ITtech1979 wrote:
     
    >I have a multi role Exchange server 2007 serving around 400 users. Lately, i noticed that the store.exe is consuming lots of memory and performance is sometimes affected.
     
    Exchange consumes large amounts of memory to avoid problems with
    slower components of your server (i.e. the storage subsystem). Are you
    sure it's Exchange and not some memory/handle-leaking component that's
    also installed on the server (e.g., Anti-virus/Anti-spam or a bad
    driver)?
     
    >I plan to shutdown the server in order to upgrade the RAM on the server.
    >
    >Question:- Is there any specific procedure on how to shutdown/reboot an Exchange server 2007?
     
    Not if it's running on it's own machine.
     
    >Last time, i tried the script below and it turns out that the Exchange information store was stuck in the "stopping" state. I have seen some people mentionning to dismount the databases prior to rebooting/shutting down an Exchange server 2007. Any thoughts?
    >
    >http://exchange.sembee.info/2007/shutdown-script.asp
    >
    >Any feedback would be much appreciated.
     
    Are you running Exchange on a domain controller? If you are, then
    stopping Exchange services might make sense because of the
    dependancies on the AD from Exchange. Otherwise you probably have some
    other problem with the machine.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Proposed as answer by Evan Liu Thursday, September 27, 2012 8:27 AM
    • Marked as answer by ITtech1979 Thursday, September 27, 2012 12:37 PM
    Wednesday, September 26, 2012 9:31 PM
  • Agree with Rich.

    If your Exchange Server is running on its own machine, no need use any specific procedure to shutdown/reboot the Exchange Server.

    Thanks,

    Evan Liu

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tnmff@microsoft.com


    Evan Liu

    TechNet Community Support

    Thursday, September 27, 2012 8:34 AM
  • On Wed, 26 Sep 2012 15:08:09 +0000, ITtech1979 wrote:

    Thanks for the info Rich. Exchange is running on this server along with Symantec GFI. The DC is on a different server. I will dig further to see if GFI might be the cause of this issue.

    So there is no need to even dismount the databases before shutting down the server? I have read an IT guy's blog and he suggested that dismounting the Exchange databases prior to the shutdown prevents database corruption in some sort?

    Thanks again for your feedback.

    Cheers

    Dave

     
    >I have a multi role Exchange server 2007 serving around 400 users. Lately, i noticed that the store.exe is consuming lots of memory and performance is sometimes affected.
     
    Exchange consumes large amounts of memory to avoid problems with
    slower components of your server (i.e. the storage subsystem). Are you
    sure it's Exchange and not some memory/handle-leaking component that's
    also installed on the server (e.g., Anti-virus/Anti-spam or a bad
    driver)?
     
    >I plan to shutdown the server in order to upgrade the RAM on the server.
    >
    >Question:- Is there any specific procedure on how to shutdown/reboot an Exchange server 2007?
     
    Not if it's running on it's own machine.
     
    >Last time, i tried the script below and it turns out that the Exchange information store was stuck in the "stopping" state. I have seen some people mentionning to dismount the databases prior to rebooting/shutting down an Exchange server 2007. Any thoughts?
    >
    >http://exchange.sembee.info/2007/shutdown-script.asp
    >
    >Any feedback would be much appreciated.
     
    Are you running Exchange on a domain controller? If you are, then
    stopping Exchange services might make sense because of the
    dependancies on the AD from Exchange. Otherwise you probably have some
    other problem with the machine.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP

    Thursday, September 27, 2012 12:36 PM
  • On Thu, 27 Sep 2012 12:36:31 +0000, ITtech1979 wrote:
     
    >Thanks for the info Rich. Exchange is running on this server along with Symantec GFI. The DC is on a different server. I will dig further to see if GFI might be the cause of this issue.
    >
    >So there is no need to even dismount the databases before shutting down the server?
     
    No. Dismounting the databases is what will happen when the Information
    Store service is signaled to stop.
     
    >I have read an IT guy's blog and he suggested that dismounting the Exchange databases prior to the shutdown prevents database corruption in some sort?
     
    Did he also recommend running ESEUTIL every night? :-O
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Thursday, September 27, 2012 2:16 PM
  • Please see his blog below:-

    http://exchangeguy.blogspot.ca/2007/07/lesson-learned-stopping-exchange.html

    On Thu, 27 Sep 2012 12:36:31 +0000, ITtech1979 wrote:

     
    >Thanks for the info Rich. Exchange is running on this server along with Symantec GFI. The DC is on a different server. I will dig further to see if GFI might be the cause of this issue.
    >
    >So there is no need to even dismount the databases before shutting down the server?
     
    No. Dismounting the databases is what will happen when the Information
    Store service is signaled to stop.
     
    >I have read an IT guy's blog and he suggested that dismounting the Exchange databases prior to the shutdown prevents database corruption in some sort?
     
    Did he also recommend running ESEUTIL every night? :-O
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP

    Thursday, September 27, 2012 7:05 PM
  • On Thu, 27 Sep 2012 19:05:38 +0000, ITtech1979 wrote:
     
    >Please see his blog below:-
    >
    >http://exchangeguy.blogspot.ca/2007/07/lesson-learned-stopping-exchange.html
     
    Sorry, but I'm not buying it.
     
    There's no details in that blog beyond "Microsoft said...". I agree
    that rebooting a system will kill a running process that hasn't
    shutdown normally, but that won't cause the problem he's described. If
    it did I'd have screwed up lots of databases by forcibly killing the
    information store service.
     
    The only times I've had problems with damaged databases is when the
    system is powered off (or reset) and the disc controller is doing
    write caching and the backup battery is dead, or if the system runs
    out of memory pool. That discounts, of course, hardware problems like
    disk failures and such.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Friday, September 28, 2012 3:00 AM