ellsworth2000
asked on
Could I receive a script or another alternative that would restart the exchange 2000 services every day?
Good Day Experts,
I receive the event warning 9582 almost everyday:
The virtual memory necessary to run your Exchange server is fragmented in such a way that performance may be affected. It is highly recommended that you restart all Exchange services to correct this issue.
For more information, click http://www.microsoft.com/contentredirect.asp.
So I'd like create a script that would stop and restart the exchange services everymorning at 6:30am. What are some possible reasons that this action would not work or cause indesireable results? Also we're running Exchange Server 2000 Standard on SBS 2000.
Many Thanks,
Ellsworth
I receive the event warning 9582 almost everyday:
The virtual memory necessary to run your Exchange server is fragmented in such a way that performance may be affected. It is highly recommended that you restart all Exchange services to correct this issue.
For more information, click http://www.microsoft.com/contentredirect.asp.
So I'd like create a script that would stop and restart the exchange services everymorning at 6:30am. What are some possible reasons that this action would not work or cause indesireable results? Also we're running Exchange Server 2000 Standard on SBS 2000.
Many Thanks,
Ellsworth
ASKER
Hi Simon,
I'd love to fix the underlying problem but the more I research it ,the more MS articles I see that say ignore the problem and then about once a month the Server Crashes without any symptoms that I can identify. I've been running the Exchange Best Practices tool and the only two Critical Issues were that the databases haven't been backed up according to the analyzer. They have been backed up; I do this every weeknight using Vertias 9.1.
Another issue is that I receive many application logs that relate to the Recipient Update Service not working like it should or the exchange server losing connectivity to the Domain Controller. The exchange server is the domain controller so I don't understand that one( SBS 2000/Exchange 2000). And my custom made distribution groups do not transfer over to the mail clients (MS Outlook 2003).
Also when I create a new user through the SBS Console, the user isn't automatically added to the GAL. It seems to me that there is a lack of communication between the SBS console and Exchange. Have any ideas?
Many Thanks,
Ellsworth
I'd love to fix the underlying problem but the more I research it ,the more MS articles I see that say ignore the problem and then about once a month the Server Crashes without any symptoms that I can identify. I've been running the Exchange Best Practices tool and the only two Critical Issues were that the databases haven't been backed up according to the analyzer. They have been backed up; I do this every weeknight using Vertias 9.1.
Another issue is that I receive many application logs that relate to the Recipient Update Service not working like it should or the exchange server losing connectivity to the Domain Controller. The exchange server is the domain controller so I don't understand that one( SBS 2000/Exchange 2000). And my custom made distribution groups do not transfer over to the mail clients (MS Outlook 2003).
Also when I create a new user through the SBS Console, the user isn't automatically added to the GAL. It seems to me that there is a lack of communication between the SBS console and Exchange. Have any ideas?
Many Thanks,
Ellsworth
ASKER
Simon,
Here is the question that i have going on the GAL not being distribute to the mail clients:
https://www.experts-exchange.com/questions/22050973/SBS-2000-isn't-updating-GAL-on-MS-outlook-2003.html
Thanks,
Ellsworth
Here is the question that i have going on the GAL not being distribute to the mail clients:
https://www.experts-exchange.com/questions/22050973/SBS-2000-isn't-updating-GAL-on-MS-outlook-2003.html
Thanks,
Ellsworth
Common errors I see with SBS installations is things like the DNS servers on the network card set to external DNS servers rather than the domain controller itself.
For RUS issues, this is Microsoft's initial troubleshooting article: http://support.microsoft.com/default.aspx?kbid=288807
This is a more comprehensive article: http://support.microsoft.com/default.aspx?kbid=822794
For backups, make sure that you are doing information store backups, not mailbox backups. Mailbox backups are slow, inefficient and close to useless for most data recovery scenarios. They aren't considered to be a full backup of the Exchange server that is recognised by Microsoft.
Simon.
For RUS issues, this is Microsoft's initial troubleshooting article: http://support.microsoft.com/default.aspx?kbid=288807
This is a more comprehensive article: http://support.microsoft.com/default.aspx?kbid=822794
For backups, make sure that you are doing information store backups, not mailbox backups. Mailbox backups are slow, inefficient and close to useless for most data recovery scenarios. They aren't considered to be a full backup of the Exchange server that is recognised by Microsoft.
Simon.
ASKER
On the backups with in veritas, if I just check the box next to Microsft Exchange Mailboxes(not a specific mailbox but all of them) it doesn't back up everything that is needed to restore the e-mails?
Many Thanks to ya,
Simon
Many Thanks to ya,
Simon
If you select the option "Exchange Mailboxes" then Veritas basically opens every mailbox and extracts the contents.
What it doesn't pick up is any of the settings, permissions or other information that is held inside the database. It is basically backing up just the raw data.
While there is nothing wrong with doing that, as it is backing up the raw data if it gets something that it cannot read, you will get errors.
I haven't backed up mailboxes for many years and can think of only one occasion where I thought it would have been useful to have.
The rest of the time I do information store backups and restore the data that way.
Simon.
What it doesn't pick up is any of the settings, permissions or other information that is held inside the database. It is basically backing up just the raw data.
While there is nothing wrong with doing that, as it is backing up the raw data if it gets something that it cannot read, you will get errors.
I haven't backed up mailboxes for many years and can think of only one occasion where I thought it would have been useful to have.
The rest of the time I do information store backups and restore the data that way.
Simon.
ASKER
I just want to make sure I understand this completely. Backing up the information store, enables you to restore the "Raw Data", permissions, settings and additional database info?
Thanks,
Ells
Thanks,
Ells
The information store is the entire database. Combined with a system state backup on a domain controller it allows you to recover to a position very close to where you were at the point of failure. (I always say very close, just in case one annoying little setting doesn't come across).
In theory you could restore the information store and then replay the transaction logs and you would be back with everything as it was before the failure.
Mailbox and public folder backup would give you just the raw data - nothing else. No permissions, settings, Out of Office messages, rules etc.
Simon.
In theory you could restore the information store and then replay the transaction logs and you would be back with everything as it was before the failure.
Mailbox and public folder backup would give you just the raw data - nothing else. No permissions, settings, Out of Office messages, rules etc.
Simon.
ASKER
Thanks for all the infor Simon,
Is it possible that I could repair Exchange server or re-install it without screwing up the rest of SBS2000? And possibly that would fix the RUS?
Many Thanks,
Ellsworth
Is it possible that I could repair Exchange server or re-install it without screwing up the rest of SBS2000? And possibly that would fix the RUS?
Many Thanks,
Ellsworth
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Do you know if I would have to restore the data or would the edb and stm files remain the same?
Ells
Ells
If you reinstall on the top, then the existing files will work. The only thing that might happen is that Exchange doesn't start properly until you service pack the server.
Simon.
Simon.
ASKER
Oh okay. Thanks a bunch Simon!!! I'll see if I can do this over the Holiday Break.
Exchange shouldn't need to be restarted on a regular basis.
Get hold of the Exchange Best Practises tool from Microsoft and run that on the server. See if it flags anything being wrong.
Simon.