一:重啟和停止服務
如許停止服務或重啟服務應徹底停止服務；
啟動服務順序(服務依賴）：
1. Microsoft Exchange System Attendant
2. Microsoft Exchange Directory
3. Microsoft Exchange Information Store
4. Microsoft Exchange Messaging Transfer Agent
5. Microsoft Exchange Internet Mail Connector
6. Microsoft Exchange Key Manager
二:服務依賴關系
The DS depends on the SA
The IS depends on the DS and SA
The MTA depends on the DS and SA
The IMC depends on the SA, DS, IS, and MTA
三:內建的恢復措施
The DS, IS, and MTA all have built-in startup recovery methods
The DS and IS both go through JET recovery
If the MTA service did not stop cleanly, it will perform an MTACheck at startup
四:服務啟動失敗
首先檢查事件察看器；
是否在修復過程中；
If the MTA will not start, try stopping the IS prior to starting the MTA. If the MTA will then start, start the IS and monitor the server
If the IMC fails to start, check the Hosts file. The IMC server must know each target server
Booting the server can do wonders. Sometimes the machine is simply in a state where a reboot is required
五:服務停止失敗
If a service is in an uncontrollable state, the process will have to be terminated before the service can be brought online.
If a service stop is aborted, it will leave the service in an unknown state. Use SRVINFO and the event application log to verify the state of a service.
To force a process to terminate, use KILL.EXE or PVIEW.EXE.
Use TLIST.EXE to verify the process has been successfully terminated
Performance Monitors性能監測
MSExchangeMTA, Work Queue Length.
MSExchangeMTA, Messages Delivered per Minute.
Exchange services processes
Paging File, % Usage
LogicalDisk, Free Megabytes, Instance:
MSExchangeIS, Active Connection Count.
MSExhangeDS, Pending Replications.
MSExchangeDS, Remaining Replication Updates
Exchange Monitors
Server monitors check each listed server to verify specific services are running. A Server Monitor can be used to track any Windows NT service if desired.
Link Monitors send “ping” messages to the listed servers. If the ping is not returned in a defined amount of time, an alert is sent to the TECHNICIAN pager.
Offline Defragmentation
Offline defragmentation is performed for two reasons. The first is to reduce the size of a database. The second reason is to create a defragmented database.
Because of tree fragmentation, there may be a situation when the IS will not accept messages fast enough to keep up with the incoming volume. When this is the case, an offline compaction will create a database that is free from the problems.
Before a database is compacted, its corresponding service must be stopped. It is recommended that all of the Exchange Services be stopped. clean
Offline Defragmentation
Database Consistency ——ESEUTIL /d PRIV.EDB， Other databases are DIR.EDB and PUB.EDB
Starting and stopping the database will make the database consistent. Alternately, EDBUTIL /R /IS or EDBUTIL /R /DS will do a “soft” recovery of the database and bring it to a consistent state
Procedure
Once the Exchange services have been stopped, change to the directory that contains the database to be defragmented. It is recommended that the database be backed up before defragmentation is performed. If there is an internal problem (other than normal JET BTREE corruption), there is a chance that defragmentation will result in an unusable database.
六:Procedure
Private and Public Information Stores
1. Net Stop MSEXCHANGEIS (also stop the MTA, DS, and SA)
2. Verify the services stopped cleanly
3. Change to D:\EXCHSRVR\MDBDATA
4. (Optional) XCOPY *.* \BACKUP\xxxx\ (where xxxx is the date, for example, “0929”)
5. D:\EXCHSRVR\BIN\EDBUTIL /D PRIV.EDB /N for the Private store
6. D:\EXCHSRVR\BIN\EDBUTIL /D PUB.EDB /N for the Public store
7. Start the Exchange services
Procedure
Directory Store
1. Net Stop MSEXCHANGEDS (also stop the MTA, IS, and SA)
2. Change to D:\EXCHSRVR\DSADATA
3. (Optional) XCOPY *.* \BACKUP\xxxx\ (where xxxx is the date, for example, “0929”)
4. D:\EXCHSRVR\BIN\EDBUTIL /D DIR.EDB /N
5. Start the Exchange services
七:Outlook Web Access
Outlook Web Access describes a set of services that allows the use of a Web browser as a mail client to access various Exchange services
HTTP Settings ——The HHTP protocol is enabled in all messaging sites, at the site leve ；
IIS Settings ——Due to limitations within Windows NT/LAN Manager, these systems are configured with BASIC Authentication + SSL. An SSL certificate is required for each server to enable the service
Escalation Path
When a problem cannot be resolved by the administrator(s) on duty, it needs to be escalated to the next support group.
First Tier ——Use the others in the first-tier team to troubleshoot and solve the problem ；
Second Tier ——When first tier cannot resolve a problem, the escalation path is to the second-tier escalation team ；This team is responsible for providing a solution or escalating to MTS ；
Third-Tier Engineering ——The engineering team is responsible for providing a solution or researching the issue so it can be resolved. This team also has the responsibility of escalating to MTS if required
八:Disaster Recovery Procedures
Problems with Exchange servers generally fall into one of the categories below:
1. Hardware failures
2. Database corruption
3. Accidentally deleted mail
4. Windows NT failures
5. Drive structure failures
6 . Clone to new hardware
As long as there is a backup of the database, the server can be restored. If the Information Transaction LOG files exist, then there will be no data loss.
If there isn’t a backup, then the server must be rebuilt from scratch. The DS database is required—if it isn’t available then there is no option but to completely rebuild the server.
九:Hardware Failures
If a component is damaged, the local hardware technician can replace the component. This plan assumes that the data on the hard drives is intact.
Database Corruption
If one of the Exchange databases is corrupt, restore it from the last backup.
A corrupt database will generally be found when the Exchange backup occurs. Look for event #25. Note that the recommendation is to restore from backup.
Accidentally Deleted Mail
If a customer accidentally deletes needed mail, a second machine must be used to do the restore. Because the entire IS database must be restored in order to retrieve the mailbox, the production server can
十:Windows NT Failures
A Windows NT failure is when the operating system is corrupted and won’t start or continually crashes. Be sure that the latest service packs have been tried before assuming there is corruption. Infrequent crashes are usually related to a bug, not corruption.
Recovering from a broken operating system isn’t as difficult as it seems. Since the databases should be intact, they can be “slid” into place once the software is replaced.
The procedure is to install Windows NT and Service Packs, install a dummy version of Exchange, and then put the data back into place.
Windows NT Failures
Drive Structure Failures
This section assumes that data on the D$ drive has been lost due to massive corruption or the loss of multiple drives in the RAID5 array. Tape backups of the DS and IS databases are required.
If the LOG files aren’t available, there will be data loss. The loss will be the data since the last backup
Clone to New Hardware
In these procedures only the databases and the tracking logs files are brought forward to the new server. This renders a server with clean Windows NT and Exchange installs
PSS Troubleshooting Tips
Recovering an Information Store That Will Not Start
Some things to check first:
nSufficient disk space on the drive that holds the database and log files
Windows NT Event Log
Make a full offline backup of the Information Store. This should include all EDB and LOG files (the location of these files can be seen in the Exchange Admin program on the Database Paths page of the Server object). These files are critical to development, so they can diagnose the problem and fix the code to recover from similar situations in the future
十一:PSS Troubleshooting Tips
Recovering a directory that will not start
Some things to check first:
nSufficient disk space on the drive that holds the database and log files
Windows NT event log
Make a backup of the DSADATA subdirectory. These files are critical to development, so they can diagnose the problem and fix the code to recover from similar situations in the future.
十二:PSS Troubleshooting Tips
Recovering an MTA That Will Not Start or Terminates Unexpectedly
Some things to check first:
Sufficient disk space on the drive that holds the MTADATA subdirectory
Windows NT Event Log
十三:Collect data
The following steps will help PSS and development determine what may have caused the MTA to have problems:
n?? Stop the MTA Service.
n?? Enable Maximum MTA logging through Exchange Admin for all diagnostics except APDU (which should be set to none) and Interoperability (which should be set to medium).
n?? Start the MTA Service.
n?? Reproduce the problem.
n?? Make a full backup of the MTADATA directory, including DB*.DAT and *.LOG files.
十四:First Attempt
n?? Run MTACHECK /V /F.
?
Second Attempt (escalate):
Escalate the problem to the next support group. They will work with you to determine the best path to follow.
十五:如何防止自己的 Exchnage Server 5.5 (SP3) 中繼未經授權的 SMTP 郵件。
——在 Admin 程序中，選擇 IMS Connector 并選擇 Properties。選擇 Routing 選項卡。如果選擇了 Reroute Incoming SMTP mail for other authorized domains，就會在路由框下面出現 Routing Restrictions 按鈕。單擊此按鈕，并從下列對話框中，選擇 Hosts and clients that successfully authenticate。停止和啟動 IMS。
十六:如果要使寄給收件人 A 的郵件能夠自動寄給收件人 B，可在服務器端執行如下操作：
用 Microsoft Exchange Administrator，單擊 Recipients 按鈕 (Crtl+Shift+E)
雙擊收件人 A
選擇 Delivery Options 選項卡。在 Alternate recipient 中，單擊 Modify，然后選擇收件人 B。如果希望收件人 A 和收件人 B 均可收到郵件，則選中 Deliver messages to both recipient and alternate recipient。 單擊 OK，應用更改。
十七:
以下是使用 Exchange 5.5 的 OWA 的一個技巧。安裝 Outlook 和帶 IIS 的 OWA 時，默認的 Web 頁是 IIS 示例頁。因而，用戶要得到自己的郵件，就不得不鍵入 http://server.domain.com/exchange。為了更便于用戶使用，我們用一個小型重新定向頁，作為默認頁。
對我們單位的內部人員來說，這個小東西非常好用，因為他們只需在地址欄中鍵入 servername，DNS 就會將其帶到正確的位置。對外部人員（即，有自己 ISP 的用戶），也僅需鍵入 servername.domain.com，而不用記住 /exchange 部分
十八:了解 Performance Optimizer
Performance Optimizer 按以下兩個重要類別提供建議或進行更改：
分析并推薦 Exchange Server 數據目錄的最佳硬盤位置。
分析并實現注冊表中內存和其它系統資源使用情況的設置。
在下列情況下，也應在安裝后手動運行 Performance Optimizer：
服務器角色變更；例如，在服務器中添加了連接器或其它功能，或從服務器中刪除了連接器或其它功能。
服務器、整個站點或組織中的郵箱數顯著增加或減少。
對 Exchange Server 計算機進行了硬件更改，如添加 RAM 或更改硬盤配置。
十九:了解 Performance Optimizer
在更改 Performance Optimizer 設置時，請牢記下列事項：
手動進行過大更改可能導致系統不穩定。應以較小增量進行更改（不超過當前值的 10% 到 20%）。
一次解決一個問題，并記錄每個更改在幾天時間內對服務器穩定性和性能的影響。盡管有時更改一個參數可能需要同時更改另外一個參數，但一次致力于解決一個問題的一般原則仍適用。
有關您要進行的更改將產生的結果，可請教 Microsoft Technical Supppot。Microsoft Knowledge Base 也包含有關已知能解決特定問題的 Performance Optimizer 更改的文章�？梢运阉鹘邮盏降腻e誤，或感興趣的 Performance Optimizer 參數。根據臆測進行手動更改可能引發問題，因此不建議這樣做。
對 Performance Optimizer 設置進行小的更改不是解決硬件不足的有效方案。減小某方面的參數值以提高其它方面的性能未必有效。Performance Optimizer 的內置選擇可以很好地調整硬件配置。如果站點中的拓撲和消息傳遞模式非常與眾不同，進行手動更改也許會有幫助。
請只為解決特定問題而更改 Performance Optimizer 設置，不要試圖進行全面更改。如果系統實際上沒有什么問題，在您手動更改了 Performance Optimizer 中的一半參數以后，可能就有問題了。
配置，管理并使用公共文件夾
在配置之前開發一個公共文件夾策略。
定義頂層文件夾創建以避免太多的根文件夾。
利用管理員程序將容許和其他屬性傳播到大的文件夾數。
通過使用服務器站點，復制，和親緣關系，將注意離集中在客戶連通性上。
為了完成客戶訪問，回顧域信任。
配置公共文件夾，并考慮向用戶提供創建協作解決方案的能力。
二十:公共文件夾使用技巧
加入定制表單來提供或檢查信息。利用Design Outlook Forms特性，在Outlook中構建定制表單，對于一般用戶來說是很自然很容易的事。
定義瀏覽來組織和發現信息。瀏覽可以是信息共享更容易。瀏覽允許對缺省選項進行個人化和簡化處理以便使公共文件夾中的信息更加有吸引力，并且容易閱讀。不只是提供文檔和發送者的列表，文檔作者及其最后編輯時間也被顯示，在Office文檔中定義的定制Office文檔屬性可以被升級。
創建規則來處理新的信息。
分配個人訪問容許。
二十一:增強 Exchange 的安全性
Microsoft Windows NT；
微軟服務包；
加密
病毒保護
服務賬號
Internet連接
代理服務器
Microsoft Exchange中的安全性設置
文章來源于領測軟件測試網 http://www.kjueaiud.com/
