close

Вход

Забыли?

вход по аккаунту

?

Exchange 2007 and NetApp

код для вставкиСкачать
Exchange 2007 and
NetApp – Best
Practices and
Guidelines
Mark Arnold
Consulting Systems Engineer
Microsoft Solutions
NetApp
Agenda
п‚Ў Exchange 2007 Server Recap:
– Roles
– Server Sizing
п‚Ў Exchange Sizing
п‚Ў NetApp Sizing
–
–
–
–
Disks
Aggregates
Volumes & LUNs
Snap*
п‚Ў Exchange Care & Maintenance
п‚Ў Exchange Backup, DR & HA
В© 2008 NetApp. All rights reserved.
2
Exchange 2007
Roles
Exchange 2007 Roles
п‚Ў Mailbox
– Clustered role if necessary
п‚Ў Hub Transport
– Internally load balanced
– External facing need a load balancing solution (NLB, hardware
etc.)
п‚Ў Client Access
– Not load balanced
– Use DNS RR, NLB, hardware etc)
п‚Ў Edge
– DMZ
– Anti-spam engine, content filtering, Outlook safe list sync
п‚Ў Unified Messaging
– Voicemail & inbound faxing
В© 2008 NetApp. All rights reserved.
4
Exchange 2007
Server Sizing
Server Sizing
п‚Ў Mailbox Servers
– Start with 2GB minimum
п‚Ў Add 2GB per 4 SGs added
п‚Ў Add @5MB per mailbox
п‚Ў HT
– Start with 2GB
– Add 3KB per message (simultaneous)
– Add 1KB per recipient (per message)
п‚Ў CAS
– Start with 2GB
– Add 2MB per concurrent connection
п‚Ў Multi Role
– Start with mailbox role
– Add 1GB per additional role
– Add further memory as per calcs for individual role(s)
В© 2008 NetApp. All rights reserved.
http://msexchangeteam.com/archive/2007/01/16/432222.aspx
6
Host Memory
п‚Ў Maximize it
п‚Ў Our sizing example
– 4000 users, 8GB server = 1.48MB cache per
user
– 4000 users, 16GB server = 3.48MB cache per
user
п‚Ў IOPS
– More hits from cache = less reads from disk
– Microsoft tout 70% reduction
п‚Ў Verifiable, realistic and repeatable
В© 2008 NetApp. All rights reserved.
7
Database Sizing
п‚Ў Microsoft:
– 100 to 200GB per store
п‚Ў http://technet.microsoft.com/en-us/library/bb331954(EXCHG.80).aspx
п‚Ў NetApp
– Varies, depending on scenario
– Always larger
п‚Ў Limited Microsoft capability for rapid restores
п‚Ў Microsoft recommendation based on RTO
deliverables
В© 2008 NetApp. All rights reserved.
8
Why That Matters
п‚Ў Insufficient memory & processor will lead to
“Back Pressure”
– Server throttles back – reduced traffic flow
– http://technet.microsoft.com/en-us/library/bb201658(EXCHG.80).aspx
п‚Ў The Exchange admins will see suspicious
event log entries
п‚Ў Server reboots will impact FAS I/O
– Cache rebuild
п‚Ў Maximize the memory and suffer the short-term
performance degredation
В© 2008 NetApp. All rights reserved.
9
Newest Exchange Sizing Calculator
В© 2008 NetApp. All rights reserved.
10
Bottom Line
п‚Ў Use the Microsoft spreadsheet
п‚Ў Review their disk results
п‚Ў Remember that NetApp stores can be far
larger
– Restore times are better and steps easier
п‚Ў NetApp will be better on IOPS due to larger
disk availability
В© 2008 NetApp. All rights reserved.
11
NetApp Sizing
Disks
п‚Ў FC disks best, naturally
– Best reliability and capacity sweet-spot
– Always FC for the stores if SATA/FC mix
п‚Ў SATA?
– Acceptable solution for logs
п‚Ў If there are enough spindles
– Have more spares
п‚Ў SAS (20n0 series)
– Acceptable for both
– Usual aggregate separation rules
В© 2008 NetApp. All rights reserved.
13
Aggregates
п‚Ў One Aggregate
– Maximizes disk utilization
– Lose three disks, lose everything
– Perfectly acceptable for low to mid I/O
requirements
– Review FlexShare
п‚Ў Two Aggregates
– No dependency between logs and store disks
– More parity (at least four rather than two)
– Necessary for highest I/O requirements
В© 2008 NetApp. All rights reserved.
14
Volumes
п‚Ў Always FlexVols
– Space utilization flexibility
п‚Ў Volume limitations
– 5.3.7x = 23, 6.0.x = 25, 6.1.x = 150, 6.2x = 200, 6.3x = 200, 6.4x =
200, 6.5x = 200, 7.0 = 200 volumes per storage system (up to 100
traditional volumes or aggregates), 7.1 = 200 volumes per storage
system (up to 100 traditional volumes or aggregates)
– 7.2 = 200 to 500 volumes on a storage system, depending on the
storage system model
п‚Ў See the problem?
– Co-host logs first to reduce volume count
– Likelihood of restoring those volumes minimal
– But don’t share volumes across servers
п‚Ў Snapshot busy
В© 2008 NetApp. All rights reserved.
15
LUNs
п‚Ў Dedicate a LUN per store
п‚Ў Have separate LUNs for DB and Logs
п‚Ў Can share SMTP queue and Logs
 Don’t share a LUN for DB and SMTP queues
– Changes random read / seq write profile
п‚Ў Assign a Volume / LUN for the Hub Transport
– Execute
http://technet.microsoft.com/en-
to move the database
– SnapMirror this to the DR site
us/library/bb125177.aspx
п‚Ў Makes your DR faster
В© 2008 NetApp. All rights reserved.
16
snap_info
п‚Ў Place transaction logs and snap_info on same
volume
– Same LUN for high I/O (i.e. many logs)
п‚Ў Keeps LUN count in check on big deployments
 SME Utilizes NTFS “Hard Links”
– SME edits pointers rather than executes a move
– More efficient on I/O for NTFS operations
В© 2008 NetApp. All rights reserved.
17
Sample Layout
В© 2008 NetApp. All rights reserved.
http://media.netapp.com/documents/tr-3578.pdf
18
FlexShare
Clients
Server
Server
Switch
Windows Applications
CIFS Home Directories
High Priority
Medium Priority
п‚Ў Option for Single
Aggregate
operation
п‚Ў Select transaction
logs for high
priority
FAS Storage System Running Data
ONTAPВ® with FlexShareв„ў
В© 2008 NetApp. All rights reserved.
19
Fractional Reserve
 Set to 100% for all Volumes…..
– Certainly for Logs
– Highly recommended for databases
п‚Ў Considerations for Reducing
– Database growth
п‚Ў Archiving solution ~ stable DB ~ reduction in FR
– Backup failure
п‚Ў Remote environment, accessibility ~ out-of-space
п‚Ў Retained SnapShots
– Reduced online retention (SnapMirroring
perhaps) promotes LUN size stability
В© 2008 NetApp. All rights reserved.
20
BlackBerry’s
п‚Ў Can be pain point in an Exchange environment
п‚Ў Easily avoided
– Add disks & monitor
п‚Ў Symptoms: Log Record Stalls
–
–
–
–
Too much data being added
Not enough IO capability to logs
Outlook client writes stop
Outlook client gets a “Waiting for Exchange
Server” message
п‚Ў Increase IOPS calculations for BB
environments
В© 2008 NetApp. All rights reserved.
21
Exchange 2007
Maintenance
Exchange Online Maintenance
п‚Ў By default between midnight and 4am
– Avoid Snaps at these times
– Co-ordinate Snaps and Maintenance across
controllers
– Don’t schedule Maintenance and SME
verification at the same time on the same
controller
п‚Ў Especially if other operations are active on the
controller
 Such as MRM – Message Records Management
В© 2008 NetApp. All rights reserved.
23
Overnight Operations
п‚Ў If time proves a constraint change the schedule to
alternate days
п‚Ў MRM could easily be a weekend only operation
п‚Ў Beware extensive MRM operations
– Increases cross site SnapMirror traffic if used
В© 2008 NetApp. All rights reserved.
24
Offline Defragmentation
п‚Ў What?
– Physical reduction in the EDB file size
– Exchange admins monitor for event id 1221
п‚Ў When?
– Never (never say never)
п‚Ў Why?
– Keep a store available and move mailboxes,
dismount and delete store files
В© 2008 NetApp. All rights reserved.
25
Content Indexing
 Now “MS Search”
п‚Ў Turned ON by default in 2007
п‚Ў Consumes additional @5% of database
– Factor into LUN sizing
п‚Ў Useful for:
– Outlook Web Access environments
– Non “Cached Mode” Outlook environments
– Cross mailbox searches
п‚Ў Improvements
– More efficient than 2003, far less I/O, far less
space consumed
В© 2008 NetApp. All rights reserved.
26
Exchange 2007
Backup & Restore
Microsoft DPM Solution
Typical recovery time:
Hours / days
Exchange Server
Backup server
Data
Disk Space
Logs
Disk Space
Empty
Tapetape
Single copy of data
Periodic backup
Offsite tape
В© 2008 NetApp. All rights reserved.
Asynchronous Mirroring with SnapMirrorВ®
Blocks in
LUN or File
Blocks
on the Disk
A
B
C
A
B
C
WAN
пЂўA
пЂўB
пЂўC
Snap 1
п‚Ў Add new system
п‚Ў Configure as mirror
В© 2008 NetApp. All rights reserved.
SnapMirror
пЂўA
пЂўB
пЂўC
Snap 1
п‚Ў Copying snapshot 1
п‚Ў Backup, DR and database
portability
Exchange 2007 HA
and DR solutions
When to use Microsoft solutions and
when to use NetApp to enhance
availability
Exchange Clustering & NetApp
п‚Ў LCR
– One server, two copies of nominated stores
п‚Ў SCC
– Two servers, one copy of data
п‚Ў CCR
– Two servers, two copies of all data
п‚Ў SCR
– A target server for LCR, SCC & CCR deployments
– SCR is the “DR” solution to the others’ HA solution
п‚Ў Database Portability
– The solution for SnapMirror
В© 2008 NetApp. All rights reserved.
31
Local Continuous Replication
п‚Ў Single server environment
п‚Ў Separate spindles for respective databases
п‚Ў Log shipping between log locations
п‚Ў No chance for log delays
п‚Ў No chance for database forking/cloning etc.
В© 2008 NetApp. All rights reserved.
32
Single Copy Clustering
п‚Ў Traditional model
п‚Ў Two servers, one copy of the data
 No longer the “recommended” solution
п‚Ў DB still prone to corruption
– Rendering the servers useless
 Can’t use the passive to backup the stores
В© 2008 NetApp. All rights reserved.
33
Clustered Continuous Replication
п‚Ў Dual server environment
п‚Ў Active/Passive only
п‚Ў Log shipping between log locations
п‚Ў No chance for log delays
п‚Ў No chance for database forking/cloning etc.
В© 2008 NetApp. All rights reserved.
34
Clustered Continuous Replication (CCR)
п‚Ў Uses MSCS
п‚Ў Automatic failover
– Should not assume a failback operation
п‚Ў Backup the passive
– The same or more spindles on the passive
п‚Ў The Exchange admins will push back
– Many touting “performance degraded” CCR
– Do CCR properly and faithfully duplicate nodes &
storage
п‚Ў Change volume layout
– Active / Passive different controllers
– More aggregates than normal
В© 2008 NetApp. All rights reserved.
35
Standby Continuous Replication
 Designed as the “Disaster Recovery” solution
п‚Ў Two servers, two copies of the information
п‚Ў Inbuilt 50 log delay
п‚Ў No ability to fork a database or restore to
previous version
В© 2008 NetApp. All rights reserved.
36
SCR (2)
 Acts as “target” for Standalone, CCR, SCC
– Many Sources to one Target
– Ships 1MB log files using RPC
– Manual failover
п‚Ў Recovery to original node is an extensive
undertaking
 Alternatively……
– SnapMirror
– Database Portability
п‚Ў http://technet.microsoft.com/enus/library/bb123954(EXCHG.80).aspx
В© 2008 NetApp. All rights reserved.
37
Database Portability
DR Site
Primary Data Center
Production
Archival & Compliance
Exchange Server (primary)
Archival
Application
SnapManager for Exchange/SMBR
Exchange
Server
(failover)
FC /
iSCSI
NetApp Secondary
Storage
NetApp SnapVault
SnapMirror
NetApp SnapLock
В© 2008 NetApp. All rights reserved.
NetApp
FAS
NetApp
FAS
(failover)
38
Section Summary Slides – Mailbox HA
Description
Redundancy
Failover
Ease of recovery
from corrupted
database
DRS solution
across 2
datacenters
Database
backup
improvements
Without HA
SCC
LCR
CCR
SCR
пѓ» Server
пѓ» Storage
пѓј Server
пѓ» Storage
пѓ» Server
пѓј Storage
пѓј Server
пѓј Storage
пѓј Server
пѓј Storage
пѓ» None
пѓј Auto -server
failover only
п‚Ў Manual storage
failover only
пѓј Auto/manual
- server &
storage
failover
п‚Ў Manual server &
storage
failover
п‚Ў Slow
- restore from
tape/disk
backup
п‚Ў Slow restore from
tape/disk
backup
 Moderate –
re-point to
passive
database copy
пѓј Rapid failover to
passive node
пѓј Moderateactivate the
standby server
and initiate
script
п‚Ў Complex require 3rd
party
replication
solutions
п‚Ў Complex require 3rd
party
replication
solutions
п‚Ў Complex require 3rd
party
replication
solutions
п‚Ў Complex require 3rd
party
replication
solutions
пѓјModerate Out of the box
solution for
site resiliency
 Kinda –
backup/snaps
hot on passive
copy to relieve
the active
node I/O
 Yes –
backup/snaps
hot on passive
copy to relieve
the active
node I/O
 No – SCR
copy backup
useless to
active copy
 None –
 None –
backup/snaps
backup/snaps
hot the
hot the
database
database
during off peak during off peak
hours
hours
В© 2008 NetApp. All rights reserved.
39
Section Summary Slides – Mailbox HA
Description
Without HA
SCC
LCR
CCR
SCR
Hardware setup
complexity &
choice
пѓј Easier &
more storage
choice
п‚Ў More
complicated &
lesser storage
choice
пѓј Easier &
more storage
choice
пѓј Easier &
more storage
choice
пѓј Easier &
more storage
choice
Administration
complexity
пѓјVery Simple
- 1 set of
database set &
no clustering
environment to
be managed
пѓјSimple
-1 set of
database to be
managed
- complex
clustering
environment to
be managed
п‚ЎComplex
-2 sets of
database to be
managed
- no clustering
environment to
be managed
п‚ЎVery complex
- 2 sets of
database &
complex
clustering
environment to
be managed
п‚ЎComplex
- 2 sets of
database and
extra standby
server to be
managed
Maturity of the
solution
пѓј Traditional
deployment
пѓј Matured
-multi nodes
clustering
solution was
introduced
since E2K3
п‚ЎNew in E2K7
-Note: the
favored choice
as enterprise
solution
п‚ЎNew in E2K7
- Gaining
acceptance,
especially on
NetApp
пѓј Complex and
immature
solution. Not
widely adopted
due to
nervousness
В© 2008 NetApp. All rights reserved.
40
Single Mailbox Recovery
п‚Ў Take the option
п‚Ў Microsoft capabilities
– None
– Restore to RSG and Exmerge/Alternate
п‚Ў NetApp capabilities
–
–
–
–
–
FlexClone the SnapShot (if you have it)
Mount the LUN
SMBR
Forget about the RSG
Has PF recoverability
В© 2008 NetApp. All rights reserved.
41
Retention
SnapShot Retention
п‚Ў Store sensible numbers
– How many depends on you
– RPO and RTO trade-offs
п‚Ў SnapVault
п‚Ў NearStore
 Can assist “Discovery” & “Compliance” issues
В© 2008 NetApp. All rights reserved.
43
Rapid Granular Data Recovery from Exchange
Backups: Single Mailbox Recovery
Exchange Environment
 If you don’t actually need
a compliance solution
but need to retain mail
FC or
IP SAN
Single
Mailbox Recovery
Primary
Storage
п‚Ў Rapidly recover storage
group, message, folder,
or mailbox
п‚Ў From any location or
media
п‚Ў Exchange recovery
environment not required
Tape
Secondary
Storage
44
В© 2008 NetApp. All rights reserved.
п‚Ў Advanced search
capabilities
Summary
п‚Ў Memory
п‚Ў Disk mixing
п‚Ў Exchange Calculator
– Have NetApp run internal calculator
п‚Ў Resiliency if necessary (SCC / CCR)
п‚Ў Storage Replication
п‚Ў Volumes / LUNs
п‚Ў Store Size
п‚Ў SMBR
п‚Ў Manage Maintenance Windows
В© 2008 NetApp. All rights reserved.
45
Questions
mark.arnold@netapp.com
В© 2008 NetApp. All rights reserved.
46
Документ
Категория
Презентации
Просмотров
11
Размер файла
1 756 Кб
Теги
1/--страниц
Пожаловаться на содержимое документа