Emails appear to be getting held on one of our Exchange 2007 SP2 Hub Transport servers, not sure why...maybe disk errors, maybe AV etc. I want to prevent new emails going to this HT and also clear the existing queues. Could someone tell me - i. Is it possible to take a HT 'out of rotation' for accepting new emails ii. If I permanently shut down a HT that has messages in its queues, will I lose these messages? iii. Are all messages in the HT queues held in the Queue Database iv. Is there a way to retrieve the contents of the Queue Database (and transaction logs?) and restore them to another server? Would this help in my situation?

i. Remove it from the connectors. ii. Yes. iii. As far as I know they are. iv. I'm sorry, I don't know.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Thanks for answering. >>i. Remove it from the connectors. Do you know how I would do this? I thought all HT's had implicit Receive Connectors by default which you couldn't remove?

On Fri, 14 Jan 2011 23:12:59 +0000, Smith1974 wrote: >Emails appear to be getting held on one of our Exchange 2007 SP2 Hub Transport servers, not sure why...maybe disk errors, maybe AV etc. I want to prevent new emails going to this HT and also clear the existing queues. Could someone tell me - i. Is it possible to take a HT 'out of rotation' for accepting new emails Yes. You can configure the mailbox server(s) with the "set-mailboxserver -SubmissionServerOverrideList <ht-server-list>" and exclude the HT server you don't want to be used. Set the receive connector(s) to listen on an IP address that doesn't exist in your organization. What I'm NOT certain of is whether or not that will prevent the HT-to-HT traffic. >ii. If I permanently shut down a HT that has messages in its queues, will I lose these messages? If you don't salvage the queue database, yes. >iii. Are all messages in the HT queues held in the Queue Database Yes. >iv. Is there a way to retrieve the contents of the Queue Database (and transaction logs?) and restore them to another server? You can mount the database on another HT server. >Would this help in my situation? That's impossible to say. If the problem is in the database, probably not. If you have multiple HT servers in the same AD site there's a pretty good chance that they're each configured in the same way. That should leave out the AV -- if it's really configured correctly and the same way on each machine. When you look at the queue viewer, n what state are the queues? If they're in "retry", what's the reason? You've looked the application event log, haven't you? Are there errors/warnings there about problems with memory, CPU consumption, disk space, etc.? Maybe that one HT server is suffering back-pressure problems? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

HI Amith, Lots of information have been given by Rich and Mike above, Including this I would advise you to check AV exclusion in problam HT sevrer, check whether Exchange databs is included in scanning. File-Level Antivirus Scanning on Exchange 2007: http://technet.microsoft.com/en-us/library/bb332342(EXCHG.80).aspx Anil

On Sat, 15 Jan 2011 08:22:25 +0000, Anil K Singh wrote: >Lots of information have been given by Rich and Mike above, I think Ed might be offended. ;-) --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thank you everyone, rebooting the server fixed the issue. Going to have to find out what caused it. To put my mind at rest, I'm wondering what to do if this happens again and rebooting the server doesn't resolve. Here is MS's description for the Submission override command: "The SubmissionServerOverrideList parameter is a static list of Hub Transport servers (which exist in the same Active Directory site as the Mailbox server) that the Mailbox server will notify when messages are ready for retrieval from a sender's outbox. This list overrides the list of dynamically discovered Hub Transport servers and can be used temporarily when you are troubleshooting a Hub Transport server and do not want it to receive mail submission notifications, or can be used to override the automatic load-balancing of notifications among all Hub Transport servers in the same Active Directory site as the Mailbox server" Let's say the affected AD site has 3 HT's; Hub1, Hub2, Hub3. Hub1 is the one with issues.....am I correct in thinking that running the command above and specifying only Hub2 and Hub3 will mean that: i. The mailbox servers in that site don't submit messages to Hub1 ii. HT's in other AD sites don't submit messages to Hub1 Is that correct? And, if things got really bad, I could carry out the command above and then look to export the Queue Database and associated logs to another HT? Thanks again!

On Sat, 15 Jan 2011 21:17:21 +0000, Smith1974 wrote: > > >Thank you everyone, rebooting the server fixed the issue. Going to have to find out what caused it. > >To put my mind at rest, I'm wondering what to do if this happens again and rebooting the server doesn't resolve. > >Here is MS's description for the Submission override command: > >"The SubmissionServerOverrideList parameter is a static list of Hub Transport servers (which exist in the same Active Directory site as the Mailbox server) that the Mailbox server will notify when messages are ready for retrieval from a sender's outbox. This list overrides the list of dynamically discovered Hub Transport servers and can be used temporarily when you are troubleshooting a Hub Transport server and do not want it to receive mail submission notifications, or can be used to override the automatic load-balancing of notifications among all Hub Transport servers in the same Active Directory site as the Mailbox server" > >Let's say the affected AD site has 3 HT's; Hub1, Hub2, Hub3. Hub1 is the one with issues.....am I correct in thinking that running the command above and specifying only Hub2 and Hub3 will mean that: > >i. The mailbox servers in that site don't submit messages to Hub1 That's correct. >ii. HT's in other AD sites don't submit messages to Hub1 That, I don't know. >Is that correct? > >And, if things got really bad, I could carry out the command above and then look to export the Queue Database and associated logs to another HT? Not "export". You'd replace the the database on the other HT with the one from the failed HT. It's "database portability" for HTs. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi, I, It's correct. II. The mailbox server only submits the email to the Hub server within the same site as the mailbox server, it doesn't use out-site Hub. For the mail.que database, you can move it to another Hub Server. Thanks AllenAllen Song