728x90

1. 메일 사용량이 많은경우

2. 메일 수발신 용량을 기본 조직전송값인 10mb 에서 더 큰값으로 변경해준 경우
3. 다수의 사용자에게 큰 사이즈의 첨부파일 전송 사용이 많을경우

세가지 조건이 겹치는 경우 버전버킷 임계치를 초과하여 백프레셔 현상이 일어남
백프레셔가 나는 경우 메일 전송이 30분에서 ~ 1시간 까지도 지연현상이 발생할수 있음

[해결방법]
EdgeTransport.exe.config 항목의 
VersionBuckets High/Medium/Normal Threshold 값을 적절하게 조절함
기본수치는 200/120/80 이나 서버 사양, 사용량에 따라 500/450/400 정도로 조절해도 무방함

더 정확하게 조절하려면 별도의 버전버킷 계산식 및 Perf 로그상의 실제 버전버킷 카운터를 주기적으로 모니터링 하는것이 필요


728x90
728x90

Exchange Server 2016


o view the build number for the version of Exchange 2016 that you’re running, run the following command in the Exchange Management Shell.

Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion

The following table shows the build numbers and general availability dates for each version of Exchange 2016.

Product nameRelease dateBuild number

Exchange Server 2016 RTM

October 1, 2015

15.01.0225.042

Exchange 2016 Preview

July 22, 2015

15.01.0225.016


Exchange Server 2013


To view the build number for the version of Exchange 2013 that you’re running, run the following command in the Exchange Management Shell.

Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion

The following table shows the build numbers and general availability dates for each version of Exchange 2013.

Product nameRelease dateBuild number

Exchange Server 2013 CU11

December 15, 2015

15.00.1156.006

Exchange Server 2013 CU10

September 15, 2015

15.00.1130.007

Exchange Server 2013 CU9

June 17, 2015

15.00.1104.005

Exchange Server 2013 CU8

March 17, 2015

15.00.1076.009

Exchange Server 2013 CU7

December 9, 2014

15.00.1044.025

Exchange Server 2013 CU6

August 26, 2014

15.00.0995.029

Exchange Server 2013 CU5

May 27, 2014

15.00.0913.022

Exchange Server 2013 SP1

February 25, 2014

15.00.0847.032

Exchange Server 2013 CU3

November 25, 2013

15.00.0775.038

Exchange Server 2013 CU2

July 9, 2013

15.00.0712.024

Exchange Server 2013 CU1

April 2, 2013

15.00.0620.029

Release to Manufacturing (RTM) version of Exchange Server 2013

December 3, 2012

15.00.0516.032

Exchange Server 2010

To view the build number for the version of Exchange 2010 that you’re running, run the following command in the Exchange Management Shell:

Get-Command ExSetup | ForEach {$_.FileVersionInfo} 

Exchange Server 2010 SP3 build numbers

Product nameRelease dateBuild number

Update Rollup 12 for Exchange Server 2010 SP3

December 15, 2015

14.03.0279.002

Update Rollup 11 for Exchange Server 2010 SP3

September 15, 2015

14.03.0266.002

Update Rollup 10 for Exchange Server 2010 SP3

June 17, 2015

14.03.0248.002

Update Rollup 9 for Exchange Server 2010 SP3

March 17, 2015

14.03.0235.001

Update Rollup 8 v2 for Exchange Server 2010 SP3

December 12, 2014

14.03.0224.002

Update Rollup 8 v1 for Exchange Server 2010 SP3 (recalled)

December 9, 2014

14.03.0224.001

Update Rollup 7 for Exchange Server 2010 SP3

August 26, 2014

14.03.0210.002

Update Rollup 6 for Exchange Server 2010 SP3

May 27, 2014

14.03.0195.001

Update Rollup 5 for Exchange Server 2010 SP3

February 24, 2014

14.03.0181.006

Update Rollup 4 for Exchange Server 2010 SP3

December 9, 2013

14.03.0174.001

Update Rollup 3 for Exchange Server 2010 SP3

November 25, 2013

14.03.0169.001

Update Rollup 2 for Exchange Server 2010 SP3

August 8, 2013

14.03.0158.001

Update Rollup 1 for Exchange Server 2010 SP3

May 29, 2013

14.03.0146.000

Exchange Server 2010 SP3

February 12, 2013

14.03.0123.004

Exchange Server 2007

To view the build number for the version of Exchange 2007 that you’re running, run the following command in the Shell:

Get-Command ExSetup | ForEach {$_.FileVersionInfo} 

Exchange Server 2007 SP3 build numbers

Product nameRelease dateBuild number

Update Rollup 18 for Exchange Server 2007 SP3

December, 2015

08.03.0445.000

Update Rollup 17 for Exchange Server 2007 SP3

June 17, 2015

08.03.0417.001

Update Rollup 16 for Exchange Server 2007 SP3

March 17, 2015

08.03.0406.000

Update Rollup 15 for Exchange Server 2007 SP3

December 9, 2014

08.03.0389.002

Update Rollup 14 for Exchange Server 2007 SP3

August 26, 2014

08.03.0379.002

Update Rollup 13 for Exchange Server 2007 SP3

February 24, 2014

08.03.0348.002

Update Rollup 12 for Exchange Server 2007 SP3

December 9, 2013

08.03.0342.004

Update Rollup 11 for Exchange Server 2007 SP3

August 13, 2013

08.03.0327.001

Update Rollup 10 for Exchange Server 2007 SP3

February 11, 2013

08.03.0298.003

Update Rollup 9 for Exchange Server 2007 SP3

December 10, 2012

08.03.0297.002

Update Rollup 8-v3 for Exchange Server 2007 SP3

November 13, 2012

08.03.0279.006

Update Rollup 8–v2 for Exchange Server 2007 SP3

October 9, 2012

08.03.0279.005

Update Rollup 8 for Exchange Server 2007 SP3

August 13, 2012

08.03.0279.003

Update Rollup 7 for Exchange Server 2007 SP3

April 16, 2012

08.03.0264.000

Update Rollup 6 for Exchange Server 2007 SP3

January 26, 2012

8.03.0245.002

Update Rollup 5 for Exchange Server 2007 SP3

September 21, 2011

8.03.0213.001

Update Rollup 4 for Exchange Server 2007 SP3

May 28, 2011

8.03.0192.001

Update Rollup 3-v2 for Exchange Server 2007 SP3

March 30, 2011

8.03.0159.002

Update Rollup 2 for Exchange Server 2007 SP3

December 10, 2010

8.03.0137.003

Update Rollup 1 for Exchange Server 2007 SP3

September 9, 2010

8.03.0106.002

Exchange Server 2007 SP3

June 7, 2010

8.03.0083.006


728x90
728x90

OfficeMain 1732921 - Three index systems suspended on production server (Feeding Controller Bug)

현재 Exchange 2013에서는 Fix되지 않았으며 차기 버전(2016)에서 Fix되었습니다.

아래와 같이 Action Plan을 전달 드립니다.

1. 현재 실패하고 있는 Database 중에 가장 작은 DB를 확인합니다.

2. Active Database의 Content Index를 Rebuild 합니다.

1) Microsoft Exchange Search 서비스 중지

2) Microsoft Exchange Search Host Controller 서비스 중지

3) 선택한 하나의 DB Catalog Folder 이름 변경(탑재되어 있는 서버의 DB 폴더)

4) 위의 두 서비스 시작


728x90
728x90


Get-MailboxDatabaseCopyStatus * | where {$_.파라메터이름 -eq "검색값"}

예)

Get-MailboxDatabaseCopyStatus * | where {$_.ContentIndexState -eq "Failed"}

728x90
728x90

이벤트 ID : 1021

Source : MSExchangeTransport

내용

수신 커넷터 ****이(가) IP 주소 xxx.xxx.xxx.xxx에서 받는 연결을 거부했습니다.

이 원본 IP 주소에 의해 이 커넷터에 대한 원본(20)당 최대 연결 수에 도달 했습니다.


원인 수신커넥터의 최대인바운드 초과로 발생

해결 최대 인바운드를 무제한으로 설정


1. 수신커넥터 정보 확인

   Get-ReceiveConnector | Select Name,MaxInbound*

MaxInboundConnectionPerSource : 20

MaxInboundConnectionPercentagePerSource : 2

기본 설정값이 되어있음을 확인


2. 최대인바운드커넥터로 설정

Get-ReveiceConnector Lotteshopping* | Set-ReceiveConnector -MaxInboundConnectionPerSource unlimited -MaxInboundConnectionPercentagePerSource 100


감사합니다.

728x90

+ Recent posts