tomd1976
asked on
Effect of restarting SMTP service on Hub Transport servers
Does anyone know if this willl cause any loss of emails or any other problems?
For instance, if I had a problem where messages were q'ing up on an HT, my first thought is to restart the SMTP service. Is this correct?
For instance, if I had a problem where messages were q'ing up on an HT, my first thought is to restart the SMTP service. Is this correct?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No,you can reboot the HT server with no issues ,No message will be lose.
Viralrathod is right. Reboot away.
The way it works is as such
1. Some server is trying to reach your server to send you an email.
2. The remote server cannot communicate with your server, because it is rebooting, temporarily shut down etc..
3. The remote server will keep trying typically for a period of 2 days before giving up and sending a bounce message to the original sender.
1. Some server is trying to reach your server to send you an email.
2. The remote server cannot communicate with your server, because it is rebooting, temporarily shut down etc..
3. The remote server will keep trying typically for a period of 2 days before giving up and sending a bounce message to the original sender.
ASKER
Thanks everyone, but I was thinking more of messages that had been recv by the HT but were being processed?
I remember something about a Queue DB on the HT's? And if you lost the server then you could restore this to another server etc
I remember something about a Queue DB on the HT's? And if you lost the server then you could restore this to another server etc
As soon as it starts back up it will process all the messages in it's queue that weren't acknowledged to have been sent successfully.
What version of exchange are we talking about? Exchange 2007?
"If the Hub Transport Server role is installed on the recovered Exchange 2007 server, you may also need to restore any saved message queue databases (which in Exchange 2007 are stored in an ESE database and not in the NTFS file system as was the case with Exchange 2000 and 2003) and place them in the right folder (should be done while the Microsoft Exchange Transport service is stopped, which is why it’s a good idea to run the RecoverServer switch with the /DoNotStartTransport syntax if you’re recovering an Exchange 2007 server with the Hub Transport Server role installed), as well as re-configure any Receive connectors as these are stored locally on the Hub Transport Server and not in Active Directory like is the case with Send Connectors."
"If the Hub Transport Server role is installed on the recovered Exchange 2007 server, you may also need to restore any saved message queue databases (which in Exchange 2007 are stored in an ESE database and not in the NTFS file system as was the case with Exchange 2000 and 2003) and place them in the right folder (should be done while the Microsoft Exchange Transport service is stopped, which is why it’s a good idea to run the RecoverServer switch with the /DoNotStartTransport syntax if you’re recovering an Exchange 2007 server with the Hub Transport Server role installed), as well as re-configure any Receive connectors as these are stored locally on the Hub Transport Server and not in Active Directory like is the case with Send Connectors."
The above is from here:
http://www.msexchange.org/tutorials/Recovering-Exchange-2007-Server-RecoverServer-switch.html
http://www.msexchange.org/tutorials/Recovering-Exchange-2007-Server-RecoverServer-switch.html
Exchange 2010 is pretty much the same: http://exchangeserverpro.com/exchange-2010-hub-transport-server-backup-and-recovery
ASKER
How about rebooting the HT server? Any chance of losing messages by doing that?