'Sizing' 태그의 글 목록

2009. 8. 20. 09:12

SCCM 2007 Sizing (Rough) SystemCenter2009. 8. 20. 09:12

System Center Configuration Manager 2007 용량 산정

Site System

Maximum recommended number per site

Clients

Up to 200,000 per hierarchy

Primary Site Server

Up to 100,000 directly assigned clients

Secondary Site Server

Up to 500 secondary sites per primary

Note

The number of secondary sites recommended per primary site is based on reasonably well connected and reliable WAN network connections. Unreliable server hardware or network connections can dramatically reduce this number.

Management Point

Up to 25,000 clients

Note

To support more than 25,000 clients in one site, management point site systems can be configured to use Network Load Balancing (NLB).

Distribution Point

Up to 4,000 clients

Note

The number of clients that one distribution point can support is dependent on network speed, disk performance, and software distribution package size.

Branch distribution point

Up to 2,000 per site, each capable of supporting up to 100 clients.

Software update point

Up to 25,000 clients

Note

To support more than 25,000 clients in one site, software update point site systems can be configured to use Network Load Balancing (NLB).

System Health Validator point

Up to 100,000 clients (or one per hierarchy if less than 100,000 clients)

Fallback status point

Up to 100,000 clients (or one per site)

ConfigMgr Site Server

(running site server all roles not specifically listed on other servers)

Component

Capacity

CPU

Twin Processor with Quad Cores 2.2 Ghz

Disk

OS 80 GB Raid 1

ConfigMgr Application 80 GB RAID 10 or 5

Distribution Point 250 GB RAID 10 or 5

Data drive can be SAN or DAS if external

LAN

100 /1000 MB (sec) production LAN

1000 / MB or Fibre for NLN array Comms

RAM

8 GB

OS

Windows Server 2003/8 Standard Edition 64 bit

IIS

Network Load Balancing

Licences

Windows Server 2008 Standard Edition or 2003 R2 with SP2

ConfigMgr site server licence (only 1 required fo this implementation)

ConfigMgr Site Database Server

(running site server all roles not specifically listed on other servers)

Component

Capacity

CPU

Twin Processor with Quad Cores 2.2 Ghz

Disk

OS 80 GB Raid 1

Data 300 GB RAID 10 or 5

SQL Logs 300 GB RAID 10 or 5

Data drive can be SAN or DAS if external

LAN

100 /1000 MB (sec) production LAN

1000 / MB or Fibre for NLN array Comms

RAM

8 GB

OS Components

Windows Server 2003/8 Enterprise Edition 64 bit

IIS

Network Load Balancing

Licences

Windows Server 2008 Enterprise Edition (if clustering) or 2003 R2 with SP2

SQL Server 2005 Enterprise (if clustering support is needed otherwise standard will suffice)

20,000 ConfigMgr Client Access Licences

ConfigMgr Management Point Servers

Component

Capacity

CPU

Twin Processor with Dual Cores 2.2 Ghz

Disk

OS 80 GB Raid 1

Data 80 GB RAID 10 or 5

Data drive can be SAN or DAS if external

LAN

100 /1000 MB (sec) production LAN

1000 / MB or Fibre for NLN array Comms

RAM

8 GB

OS Components

Windows Server 2003/8 Standard Edition 64 bit

IIS

Network Load Balancing

Licences

Windows Server 2008 Standard Edition or 2003 R2 with SP2

ConfigMgr Software Update Point Server

Component

Capacity

CPU

Twin Processor with Dual Cores 2.2 Ghz

Disk

OS 80 GB Raid 1

Data 80 GB RAID 10 or 5

Data drive can be SAN or DAS if external

LAN

100 /1000 MB (sec) production LAN

1000 / MB or Fibre for NLN array Comms

RAM

8 GB

OS Components

Windows Server 2003/8 Standard Edition 64 bit

IIS

Network Load Balancing

Windows Software Update Services

Licences

Servers 2008 / 3 OS

ConfigMgr Remote/Branch Infrastructure Options

Branch Size (# users)

ConfigMgr Remote Architecture

Capacity / Licence Requirements

0-3 users

No local infrastructure

No ConfigMgr specific licence required beyond the ConfigMgr CAL

3-25 users

Single Branch Distribution Point

No ConfigMgr specific licence required beyond the SCCM CAL

25 – 100 users

Dual Branch Distribution Points (fault tolerance and capacity as images and packages will be extensively used)

No ConfigMgr specific licence required beyond the SCCM CAL

100 – 1000 users

Distribution Point

Windows Server 2003 / 2008 NTFS volume with 100 GB of capacity.

Can leverage existing file / application server capacity.

No ConfigMgr specific licence required

1000 – 2000 users

Secondary SCCM site Server

No ConfigMgr specific licence required beyond the SCCM CAL.

Windows Server 2003 / 2008 server licence

2000 users +

Primary site server

ConfigMgr site server

:

Posted by 커널64

2009. 8. 19. 14:09

SCDPM 2007 용량 산정 시 고려 사항 SystemCenter2009. 8. 19. 14:09

System Center Data Protection Manager 2007 Sizing

권장 사양
CPU: 2.33GHz 이상 Quad-Core
Memory: 4GB
Pagefile: 복구 지점 볼륨 합의 0.2% 필요
(예를 들어, 복구 지점 볼륨이 총 3TB이면 페이지 파일은 6GB가 추가되어야 한다. 또한, 32bit 운영체제 VSS non-paged pool의 제약으로 10TB 이상의 데이터를 보호하는 경우 반드시 64bit 운영체제가 필요하다.)

플랫폼 별 제약 사항

플랫폼	데이터 원본 제한	권장 디스크 공간
32bit	150개의 데이터 원본 단일 DPM 서버 당 50개의 서버 권장	10TB Secondary DPM 서버의 경우 6TB
64bit	300개의 데이터 원본 단일 DPM 서버 당 75개의 서버 권장	45TB

네트워크 고려 사항
동기화 중에 네트워크가 단절되면 DPM은 끊어진 부분부터 다시 전송을 시작한다.
일관성 확인 중에 네트워크가 단절되는 경우 5분 이내에 다시 네트워크 연결이 재개되면 일관성 확인을 다시 수행하며 5분 이내에 네트워크 연결이 재개되지 않는다면 일관성이 없는 것으로 표시된다.

네트워크 속도와 데이터 원본 크기 별 전송 시간

데이터 크기	1Gbps	100Mbps	32Mbps	8Mbps	2Mbps	512Kbps
1GB	< 1분	< 1시간	< 1시간	< 1시간	1.5시간	6시간
50GB	< 10분	1.5시간	5시간	18시간	71시간	284시간
200GB	< 36분	6시간	18시간	71시간	284시간	1137시간
500GB	< 1.5시간	15시간	45시간	178시간	711시간	2844시간

:

Posted by 커널64

2009. 8. 5. 14:11

Exchange Server 2007 Sizing Collaboration2009. 8. 5. 14:11

Exchange Server 2007 용량 산정 (사이징)

Mailbox Role
Factors
- Number of mailboxes
- Mailbox average size
- User profiles
- Security/auditing mechanisms
- Use of mobile devices (Blackberry included)
- Outlook mode (online/cached)
- Archiving/Messaging Record Management
- High Availability Model (CCR, LCR, SCR)
- Cache Warming

사용자 유형 카테고리

User type	Send / receive per day (50K messages)	Database cache / user	IOPS / user	Logs Generated / Mailbox
Light	5 / 20	2MB	0.11	6
Medium	10 / 40	3.5MB	0.18	12
Heavy	20 / 80	5MB	0.32	14
Very Heavy	30 / 120	5MB	0.48	36

CPU
1 processor core for every 1,000 light/medium user mailboxes
1 processor core for every 500 heavy user mailboxes
8 cores maximum

Memory
2GB + 2 ~ 5MB/mailbox (위 사용자 유형에 따라)
32GB maximum 권장 (32GB 이상은 비용 문제 발생)
최소 메모리는 다음 표와 같이 저장소 그룹의 개수에 따라 달라진다.

Number of Storage Group	Exchange 2007 RTM	Exchange 2007 SP1
1-4	2GB	2GB
5-8	4GB	4GB
9-12	6GB	5GB
13-16	8GB	6GB
17-20	10GB	7GB
21-24	12GB	8GB

Network
1 x Gbit minimum
With CCR use separate NICs for public and private networks

Disk
Use the Exchange 2007 Mailbox Server Role Storage Requirements Calculator.
또는 다음 항목 고려
- Balance I/O performance and Capacity
- Add 5% onto database LUN size for Content Indexing
- Add 10% onto database LUN size for Overhead / white space
- The default Deleted Items retention period (14 days) adds up to 30% in the database LUN
- Take SLA factors into account (database recovery time, backup window, etc.)
- Target for 100GB of maximum database size

HUB Transport Role
Factors
- Mail queue stored in JET database
- CCR (Transport Dumpster)
- Message rate
- Message tracking
- Average message size
- Number of enabled transport agents
- Antivirus and third-party applications
- Journaling

CPU
소규모 조직의 경우 1개 또는 2개의 코어 필요
중/대규모의 경우 다음 표 참고

	With A/V and A/S	Without A/V and A/S
서버 당 권장 코어 수	8	4
허브 전송 서버 : 사서함 서버 비율	1:5	1:7

Memory
2GB minimum, 16GB maximum
1GB per core
Large queue scenarios
- Per message overhead: 3KB
- Per recipient overhead: 1KB
Edgesync overhead (>tens of thousands of mail-enabled objects)
- 4K per mail-enabled object

Disk
디스크 용량 = 평균 메시지 크기 x 최대 큐
mail.que 파일과 로그 파일의 위치는 시스템 디스크와 분리 권장 (RAID 10)
LCR 또는 CCR 환경에서 Transport dumpster의 영향
- Capacity consumed by the transport dumpster =
number of storage groups x maximum transport dumpster size
Back Pressure:
- RTM: 최소 4GB 여유 공간
- SP1: 최소 500 MB 여유 공간

Hub Transport I/O (steady state)	Transport Dumpster Enabled	Transport Dumpster Disabled
Total IOPS/message (~40KB)	17	4
Log Write IOPS/message (sequential)	7	2
Database Write IOPS/message (random)	7	2
Database Read IOPS/message (random)	3	0

Network
Gbit Recommended

CAS Role
Factors
- Non-MAPI 클라이언트의 수 (CAS 서버에서 메시지 변환 작업 발생)
- OWA rendering
- Enabled services
> IMAP, POP3
> Outlook Anywhere
> Exchange ActiveSync
- Web services
> AutoDiscover
> Availability
> OOF
- OAB distribution

CPU
Up to 4 cores
1 : 4 CAS : Mailbox cores

Memory
2GB/core
16GB Maximum

Disk
특별한 요구 사항 없음

Network
Gbit recommended

Edge Transport Role
Factors
- Message rate
- Average message size
- Number of enabled transport agents
- A/V and A/S
- SMTP Connections
- Percentage of malware

CPU
2 processor cores recommended
Up to 4 cores

Memory
2GB minimum, 16GB maximum
1GB/core

Disk
Capacity = (average message size x maximum queue) + Logs
Transport rules and message rate influence the IOPS needed
Back Pressure:
- RTM: 최소 4GB 여유 공간
- SP1: 최소 500 MB 여유 공간

Network
2 x Gbit recommended (1 in, 1 out)

Active Directory / Global Catalogs

	32-bit	64-bit
GC : Mailbox server 코어 비율	1 : 4	1 : 8 전체 Active Directory Database (NTDS.DIT)를 메모리에 Cache 할 수 있을 만큼의 충분한 메모리를 반드시 설치하여야 한다.
1GC near XX users	Every 10,000 users	Every 20,000 users

:

Posted by 커널64

달력

« 2025/1 »

'Sizing'에 해당되는 글 3건

SCCM 2007 Sizing (Rough) SystemCenter2009. 8. 20. 09:12

SCDPM 2007 용량 산정 시 고려 사항 SystemCenter2009. 8. 19. 14:09

Exchange Server 2007 Sizing Collaboration2009. 8. 5. 14:11

Beyond IT

카테고리

최근에 올라온 글

최근에 달린 댓글

글 보관함

티스토리툴바