Nathan - PowerPoint Presentation

Slide1
Slide2

Nathan MuggliESE Program ManagerMicrosoft Corporation

Exchange Storage for Insiders

Todd LuttinenStore Program ManagerMicrosoft Corporation

ARC306Slide3

AgendaStorage Trends

Larger, but not FasterData-At-Rest ProtectionPower Consumption

ESEExchange 2013 SP1 ESE EnhancementsUpdate on Windows Server 2012 R2 and Exchange 2013 Sp1Future Exchange Storage EnhancementsStoreArchitecture overviewExchange 2013 SP1 Store EnhancementsFuture Exchange Store EnhancementsExchange 2013 recapSlide4

Storage Trends

LARGER,

BUT NOT FASTERSlide5

Larger,

but not Faster

Drives3.5 HDD Capacity in GBAreal Density required @ 7 plattersAreal Density GB sq” (PMR)SMR & HAMR intended to close the Areal Density gapSlide6

Shingled Write Overview

head

motion

corner

head

scans

cross

head

motion

corner

head

write

head

progressive

writes

down track

track

In a shingled write, the data tracks are written in a particular direction radially, and are only written once with a write head wider than the track pitch

Conventional Recording uses a track pitch that keeps data separate.

Shingle Write Recording overlaps tracks, allowing for a narrower track pitch. Each track is only written once until any remaining valid data is moved.Slide7

Storage Trends

DATA-AT-REST PROTECTIONSlide8

POWER CONSUMPTION

Storage TrendsSlide9

ESE on Phone

DEVICE POWER CONSUMPTION

http://research.microsoft.com/~ranveer/docs/email-energy.pdf Slide10

Storage Trends - Takeaway

Larger but not Faster Drives

Exchange 2013 reduces IOPS by +50% compared with Exchange 2010. Supports multiple databases per volume to maximize available IOPSJBOD still best for COGS (capacity + performance + cost)Continue riding IOPS/Capacity curve up to 10TB (PMR) DrivesContinue riding IOPS/Capacity curve up to 10TB (PMR) DrivesSMR Drives not supported with Exchange 2013Data-at-rest ProtectionUtilize Bitlocker for Data-at-rest protection with Exchange 2013Office365 is already utilizing Bitlocker. From http://trustoffice365.com “All email content is encrypted on disk using BitLocker Advanced Encryption Standard (AES) encryption. Protection covers all disks on mailbox servers and includes mailbox database files, mailbox transaction log files, search content index files, transport database files, transport transaction log files”Self-Encrypting-Drives (SED) promising but not viable in Enterprise scenarios due to the requirement of Drives being directly attached to ATA channel.Power Consumption

Don’t ignore benefit of power efficient Storage technologies.

Helium technology very promising for both Areal Density increase and Power consumption decrease (-2 watts compared

to conventional drive)Slide11

What’s newExchange 2013 SP1

ESE EnhancementsSlide12

Exchange 2013 SP1 ESE Enhancements

Tracing improvements

ESE ETW Tracing New Keywords and Tasks for every component from transactions to i/o xperf -start JetStressTrace -on Microsoft-Exchange-ESE -f Microsoft-Exchange-ESE-Trace.etlxperf -stop JetStressTracexperf Microsoft-Exchange-ESE-Trace.etlESE IO Debug ChannelExchange 2013 JetStressPerformanceDatabase extension +30% improvementTool EnhancementsESEUTIL verbose output optionsLog Dump, Space Report, Table/Page/Node DumpKeywords

Error

Performance

Trace

Transaction

Space

BF

IO

LOG

Task

BFRESMGR

JETTraceTag

Tasks

ESE_Trace

ESE_BF_Trace

ESE_Block_Trace

ESE_NewPage_Trace

ESE_ReadPage_Trace

ESE_PrereadPage_Trace

ESE_WritePage_Trace

ESE_EvictPage_Trace

ESE_TouchPage_Trace

ESE_LatchPage_Trace

ESE_DirtyPage_Trace

ESE_TransactionBegin_Trace

ESE_TransactionCommit_Trace

ESE_TransactionRollback_Trace

ESE_AllocExt_Trace

ESE_FreeExt_Trace

ESE_AllocPage_Trace

ESE_FreePage_Trace

ESE_IOREQHeapEnqueue_Trace

ESE_IOREQHeapDequeue_Trace

ESE_IOCompletion_Trace

ESE_LogStall_Trace

ESE_LogFlush_Trace

ESE_EventLogInfo_Trace

ESE_EventLogWarn_Trace

ESE_EventLogError_Trace

ESE_TimerQueueSchedule_Trace

ESE_TimerQueueRun_Trace

ESE_TimerQueueCancel_Trace

ESE_TimerTaskSchedule_Trace

ESE_TimerTaskRun_Trace

ESE_TimerTaskCancel_Trace

ESE_TaskManagerPost_Trace

ESE_TaskManagerRun_Trace

ESE_GPTaskManagerPost_Trace

ESE_GPTaskManagerRun_Trace

ESE_ThreadCreate_Trace

ESE_ThreadStart_Trace

ESE_VersionPage_Trace

ESE_VersionCopyPage_Trace

ESE_CacheResize_Trace

ESE_CacheLimitResize_Trace

ESE_CacheScavengeProgress_Trace

ESE_ApiCall_Trace

ESE_ResMgrInit_Trace

ESE_ResMgrTerm_Trace

ESE_CachePage_Trace

ESE_MarkPageAsSuperCold_TraceSlide13

ESE ETW Tracing in Sp1Slide14

Exchange Server Jetstress 2013 Tool

Simulate Exchange disk I/O load on a serverVerify performance and stability of your disk subsystem before putting your Exchange server into a production environment

Jetstress simulates the Exchange database and log file loads produced by a specific number of usersUse Performance Monitor, Event Viewer, and ESEUTIL in conjunction with Jetstress to verify that your disk subsystem meets or exceeds the performance criteria you establishDownload from http://aka.ms/Jetstress2013Latest Version 15.0.775.8 Published Sep 11, 2013 Requirements.NET Framework 4.5Exchange 2013 binaries: ESE.DLL, ESEPerf.dll, ESEPerf.ini, ESEPerf.hxxVC11 runtimeSlide15

Exchange Server 2013 JetStress Tool

NEW UI OPTION TO ALLOW JETSTRESS TO CONTINUE RUNNING EVEN IF A DISK FAILSSlide16

Exchange Server 2013 JetStress Tool

Test Summary (failure) Due to Lost Flushes and TEST LOGSSlide17

Windows Server 2012 R2 &Exchange 2013 Sp1

Storage Technologies and impact on ExchangeSlide18

Windows Server 2012 R2 and Exchange 2013 SP1

Storage TechnologiesStorage Spaces

Tested with Exchange 2013 Sp1Storage TieringTested with Exchange 2013 Sp1ReFS for Data VolumesTested with Exchange 2013 Sp1Best Practice: Disable Integrity on ESE DB and Log FilesData DedupeNot Supported with live Exchange 2013 Sp1 databasesSlide19

RoadmapFuture Exchange ESE EnhancementsSlide20

Database Resiliency

Database Divergence Detection

Performance / IOPS reductionOpticsESE Developer experience Future Exchange ESE EnhancementsSlide21

Performance / IOPS reductionSearch Indexing from Passive Copies

Saves network bandwidth and reduces IOPsLog

compression improvementsReduces WAN costs through IOPs reductionLong Value contiguity improvementsFuture Exchange ESE EnhancementsSlide22

Future

Exchange

ESE EnhancementsOpticsTracing and Eventing improvementsSlide23

Future Exchange ESE Enhancements

ESE Developer experience

ISAM PowerShell Example: Export DB SchemaPersistent DictionaryISAM LayerA managed layer with object model which simplifies writing DB codeExposed via an assembly (Microsoft.Exchange.Isam.dll)Target Customers are Developers and sophisticated PowerShell IT Pros ESE MSDN Bloghttp://blogs.msdn.com/b/jet/ Slide24

Exchange 2013Information StoreSlide25

What is “Store” (aka MSExchangeIS)

Process that manages ESE mailbox database(s)Responsible for the following functionality:Logical schema of data in database (tables, rows, columns)

All read/write access to items in mailbox database via RPC operationsAccess control to items within mailbox Management of indices supporting client views over itemsReliable events supporting event-based assistant infrastructureMaintenance tasks to disconnect and drop mailboxes (SyncWithDS)Slide26

Exchange Storage History (1996-1999)

Exchange 4.0, Exchange 5.0, Exchange 5.5

Supports i386, Alpha, and MIPS architecturesBundled directory service (ExDS

)

Single

native store

process directly supporting MAPI clients

(1) mailbox EDB and (1) public folder EDB per server

Local

RAID storage (

18GB drives

,

volume sizes less than 200GB )

~10MB mailbox on server (client PST storage) Slide27

Exchange Storage History (2000-2006)

Exchange 2000, Exchange 2003

Supports i386 architecture (virtual address space up to 3GB)Integration with Windows Active Directory

Single

native store

process directly supporting MAPI clients

Store support for 3rd

party code in-process (events, VSAPI)

Native protocol processes (POP, IMAP, OWA, SMTP) with front-end proxy

Inter-process communication via shared memory access

Support for up to 20 databases per

server (

database

= EDB

+ STM)

Integrated

full-text search (1

st

generation)

Shared storage clusters with Storage Array Networks (RAID LUN)

~100MB mailbox on server (client OST and PST storage)Slide28

Exchange 2007, Exchange 2010

Supports x64 architecture

Integration with Windows Active Directory

Single native store process directly supporting MAPI clients*

Store support for 3rd

party code in-process (events, VSAPI)

Managed Event and Time-Based Assistant Infrastructure

Managed protocol processes (POP, IMAP, OWA, EWS, EAS, MOMT*)

Inter-process communication via XSO/MAPI/RPC over TCP/IP

Support for up to 100

ESE databases per server

Integrated full-text search (2nd

generation)

Database replication, SAN and local JBOD (1-2 TB drives)

~10GB mailbox + ~10GB archive (client OST storage for primary)

* MOMT (RPC Client Access) introduced in Exchange 2010 (no MAPI client access direct to store)

Exchange Storage History (2007-2012)Slide29

Exchange Storage History (2013+)

Exchange 2013 and Beyond

Supports x64 architectureIntegration with Windows Active Directory

Managed store worker process per database

Managed Event and Time-Based Assistant Infrastructure

Managed protocol processes (POP, IMAP, OWA, EWS, EAS, MOMT) via Café

Inter-process communication via XSO/MAPI/RPC over LRPC

Support for up to 100* ESE databases per server

Integrated full-text search (3

rd

generation)

Database replication, local JBOD (4-8TB drives)

~200GB mailbox + ~200GB archive (OST client storage with sync slider)

* Exchange 2013 CU2 introduced support for up to 100 databasesSlide30

Exchange 2013 Storage High Level Architecture

RPC Client

processesStore workerRPC Server Processes with MAPI and AdminRPC endpointsLocal Inter-Process Communication is RPC-basedDatabaseand ProcessmanagementClient-Specific Protocols (POP, IMAP, SMTP, HTTP, EAS, etc)Slide31

IOPS Reductions: Store Schema Elements

Element

E2007E2010 E2013Physical Contiguity (ESE)Poor physical contiguity of leaf pages. Hence many, small size, IOs (1 for each page)Excellent physical contiguity of leaf pages. So fewer, large size IOs, spanning N pagesLogical Contiguity

(Store)

Headers for each folder kept in separate table. So many, small

size, IOs spread over many tables

Folder, Message

& Attachment table per mailbox. Message table consists of physical columns and property blobs. High message per page density means fewer large

lOs

to retrieve many messages for views

Temporal Contiguity

(Views)

All views and indexes updated each time a mail

is delivered. So many, small size, IOs spread over time

Views and indexes updated only when they are accessed by user. So fewer, large

sized, IOs done together.

Replacing Random IO with Sequential IO to squeeze more IOPS from storageSlide32

Database Schema ElementsTables optimized for sequential I/O

Global Tables

Globals – database version, etc Mailbox – MailboxNumber, Owner Info, Locale, LastLogonTime, etcDeliveredTo – duplicate delivery informationEvents – reliable events for assistantsTables partitioned by MailboxNumberFolder - FolderId, Item Count, Size, PropertyBlobMessage – DocumentId, MessageId, FolderId, PropertyBlob, OffPagePropertyBlob, MessageClass ordered by DateReceivedAttachment – AttachmentId, Name, Size, CreationTime, etcPhysicalIndexes (partitioned by LogicalIndex)Slide33

Database Schema ElementsIOPS reduction through Message Table Property Storage and Compression

Blobs used to store collection of MAPI properties

Referred to as On-page and Off-page property blobsESE compression optimizes physical storage of blob dataCompression more efficient when input contains more properties PropertyBlobProperties previously stored in Header table in single message table columnProperty promotion OffPagePropertyBlob  PropertyBlob possibleBlob size limited to eliminate LV tree access for core message propertiesOffPagePropertyBlobESE LV Hints push storage of this blob into separate LV treeReading LV tree involves large sequential I/O (some fragmentation)Slide34

Database ESE cache management

Algorithm will allocate total ESE cache available for all store worker processes based on physical RAM~20% of total memory allocated to ESE cache (when running with

MaximumActiveDatabases)ESE cache allocated to each database (store worker process) based on number of local database copies and MaximumActiveDatabases configurationStatic amount of ESE cache allocated to passive and active database copiesPassive database allocates 20% of max ESE cache target used for active databaseStore worker process will only use max cache target when operating as activeMax cache target computed at service process startupRestart service process when adding/removing copies or changing maximum active database configuration Slide35

Exchange IOPS Trend

+99% * Reduction!

* Similar usage profile (93% reduction with increased usage profile)Slide36

Multiple Database Copies/ JBOD Disk

Active User Distribution

Number of copies/disk less than or equal to number of copies per databaseUse DB copy activation preference to distribute active users across available disks hosting database copiesBudget for server/disk failures and passive IOPS requirementsIf lag copy used, don’t have to capacity plan for all DB copies active

Server2

DAG

DB1 Active

DB2 Passive

DB3 Passive

DB4 Passive

Server1

Server3

Server4

DB1 Passive

DB2 Active

DB3 Passive

DB4 Passive

DB1 Passive

DB2 Passive

DB3 Active

DB4 Passive

DB1 Passive

DB2 Passive

DB3 Passive

DB4 ActiveSlide37

Database Process Isolation & Management

Microsoft Exchange Replication service process (msexchangerepl.exe)Responsible for issuing mount/dismount operations to store

Initiates failovers on failures reported by ESE, Store, Search and RespondersStore service process/controller (Microsoft.Exchange.Store.Service.exe)Manages worker process lifetime based on mount/dismount operations receivedLogs failure item when store worker process problems detected (exit, hung)Terminates store worker process in response to “dirty” dismount during failoverStore worker process (Microsoft.Exchange.Store.Worker.exe)One process per database, RPC endpoint instance is database GUIDDatabase started in passive state, responsible for block-mode replication Fast transition to active when mounted, responsible for processing RPC operationsTransition from passive  active increases worker ESE cache size 5XSlide38

Elimination of scheduled maintenance

Recurring maintenance implemented within time-based assistant (TBA) infrastructure as multiple assistants:

StoreMaintenance: lazy index maintenance, isinteg, discretionary Subobject cleanupStoreUrgentMaintenance: SubObject cleanup (threshold exceeded)StoreDirectoryServiceMaintenance: disconnected mailbox expirationWorkload Management monitors CPU and replication health Task execution throttled/deferred when resource pressure existsRPC latency monitor disabled (to be replaced by disk health resource monitor in future release )Background ESE database scanning rate further throttledBased on datacenter disk failure analysis, target to complete background database scan within 4 weeks (based on multiple databases on 8 TB disks)Periodic tasks to generate mailbox quota notification removedQuota notifications generated at mailbox logon time no more than once dailySlide39

Mailbox Quota Management & Notifications

Over-quota notification overhead reducedStorage utilization computed in real-time as CRUD operations performed

At logon time, system evaluates mailbox quota against policy and sends over-quota notification message once per notification interval (daily)Quota notifications are NOT sent to inactive mailboxesMailbox size calculation is more accurate measurement of mailbox database storage usedIncludes both internal and end-user items/propertiesRepresents 100% of logical storage used by mailbox in databaseReported mailbox size will likely increase when moved to Exchange 2013No increase in database footprint, just the attribution of logical space to each mailboxShould plan to increase quota per mailbox by ~30% to accommodate change in space accountingSlide40

Exchange 2013 SP1 Store Enhancements

ManagementDatabase

schema updatesNew mailbox shape limitsEnhancements for space investigationsRetrieve status of mailbox repair tasksScalabilitySupports more databases per serverConvert additional RPC operations frequently holding exclusive locks to shared locks Limit concurrent waiters on mailbox lock (MailboxLockMaximumWaitCount = 10)MonitoringAlerting by HealthSet to consolidate number of alerts per serverDatabaseRepeatedMountsMonitor to detect repeated database failoversDatabaseAvailabilityMonitor  DatabaseAvailabilityEscalationProcessingMonitorMiscelleneousLastLogonTime property moved from source server to target serverMore cases support mailbox signature preserving move (no need to restart Outlook)Performance fix for EmptyFolder (schema change)Slide41

Database Schema Upgrades (Exchange Team Blog)

Infrastructure to

safely upgrade schema of each database in an Exchange 2013 DAG deploymentRequests database schema upgrade for each of the local database copies during CU or Service Pack installationRequestedDatabaseSchemaVersion set to MaximumSupportedDatabaseSchemaVersion for each databaseCurrent database schema info can be retrieved for each database using Get-MailboxDatabase (using -Status parameter)CurrentSchemaVersion: current database schema versionRequestedDatabaseSchemaVersion: equal CurrentSchemaVersion after next database mountSupported versions of each database copy can be retrieved using Get-MailboxDatabaseCopyStatusMinimumSupportedDatabaseSchemaVersion: minimum schema version supported by database copyMaximumSupportedDatabaseSchemaVersion: maximum schema version supported by database copyUpdate-DatabaseSchema can be used to manually request upgradeSchema upgrade at mount time when RequestedDatabaseSchemaVersion > CurrentSchemaVersionMailbox schema upgrade at first logon after database schema upgradeSlide42

Example: Database Schema Upgrade

Server2

DAG

DB3 Passive

Server1

Server3

Server4

DB3 Passive

DB4 Passive

DB1 Passive

DB1 Passive

DB2 Passive

1. Remove active databases from S1

2. Upgrade S1,

max supported version increased from 0.121 to 0.126

(

schema upgrade request for each local DB copy fails because other servers only support 0.121

)

3. Remove active databases from S2

4. Upgrade S2 ,

max supported version increased from 0.121 to 0.126

(

schema upgrade request for each local DB copy fails because other servers only support 0.121

)

5. Remove active databases from S3

6. Upgrade S3 ,

max supported version increased from 0.121 to 0.126

(

schema upgrade request for each local DB copy fails because other servers only support 0.121

)

7. Remove active databases from S4

8. Upgrade S4 ,

max supported version increased from 0.121 to 0.126

(

schema upgrade request for each local DB copy succeeds because all servers support 0.126

)

DB1 Active

DB1 Passive

DB1 Passive

0.121 capable

0.126 capable

0.121 capable

0.126 capable

0.121 capable

0.126 capable

0.121 capable0.126 capableDB2 Passive

DB2 PassiveDB2 ActiveDB1 PassiveDB2 PassiveDB3 PassiveDB3 Active

DB3 Passive

DB4 ActiveDB4 PassiveDB4 PassiveDB4 Passive9. Move DB4 to S4 (DB4 schema upgrade succeeds during mount operation

)DB4 ActiveDB1, DB2, DB3 schema upgrade on next mountSlide43

Mailbox Shape Limits

Enforce practical limits that prevent runaway usage

Preserve QoS for well behaved mailboxesLimits in Exchange Online (online documentation)MailboxMessagesPerFolderCountWarningQuota : 900000MailboxMessagesPerFolderCountReceiveQuota : 1000000DumpsterMessagesPerFolderCountWarningQuota : 2750000DumpsterMessagesPerFolderCountReceiveQuota : 3000000FolderHierarchyChildrenCountWarningQuota : 9000FolderHierarchyChildrenCountReceiveQuota : 10000FolderHierarchyDepthWarningQuota : 250FolderHierarchyDepthReceiveQuota : 300Limits in on-premises product default to UnlimitedExplicitly set using set-Mailbox cmdletDisplayed using get-MailboxStatistics cmdlet

# of

msgs

per folder

# of

msgs

per dumpster folder

# of folder children anywhere in hierarchy

Depth of folder hierarchySlide44

MailboxStatistics: Physical vs. Logical Space

Previously required ESEUTIL /MS on offline DB copy

Get-MailboxStatistics extended to display physical table sizes of each mailboxGet-MailboxStatistics with identity parameter will provide current statsGet-MailboxStatistics with database parameter will provide cached stats[PS] D:\>Get-MailboxStatistics <MailboxId>| FL *sizeTotalDeletedItemSize : 3.545 GB (3,805,959,899 bytes)TotalItemSize : 45.73 GB (49,100,346,075 bytes)MessageTableTotalSize : 18.02 GB (19,344,031,744 bytes)MessageTableAvailableSize

: 31.69 MB (33,226,752 bytes)

AttachmentTableTotalSize

: 8.071 GB (8,665,759,744 bytes)

AttachmentTableAvailableSize

: 2.906 MB (3,047,424 bytes)

OtherTablesTotalSize

: 73.47 MB (77,037,568 bytes)

OtherTablesAvailableSize

: 736 KB (753,664 bytes)

Logical Mailbox Size

(

TotalItemSize

+

TotalDeletedItemSize

)

Physical Mailbox Size (

MessageTableTotalSize

+

AttachmentTableTotalSize

+

OtherTablesTotalSize

)

49.273 GB

26.158 GB

Ratio of Logical to Physical size will vary by mailbox based on contentSlide45

Mailbox Repair Task Status

New-MailboxRepairRequest

used to create repair tasks, new CorruptionTypes added for more casesCan scope all mailboxes on database or a specific mailboxSome CorruptionType values cause resource expensive tasks that can impact end-user experienceGet-MailboxRepairRequest will retrieve repair task status from store (not persisted between mounts)Can scope database, mailbox or specific task ID (returned by New-MailboxRepairRequest)Summary of progress (% completion) of all tasks (corruption types) and sum of corruptions detected/fixed[PS] D:\data\scripts>Get-MailboxRepairRequest 425a70a1-7b24-47ef-98f9-3131b7f309b4\da6ef632-e5ed-4193-bbfa-3fa4f70afa11 Identity : 425a70a1-7b24-47ef-98f9-3131b7f309b4\da6ef632-e5ed-4193-bbfa-3fa4f70afa11Mailbox : ac2dcfd6-555b-460e-85bf-1c656367dc2cSource : OnDemandPriority : HighDetectOnly : FalseJobState : SucceededProgress : 100

Tasks : {

SearchFolder

,

FolderView

,

AggregateCounts

}

CreationTime

: 3/18/2014 7:08:49 PM

FinishTime

: 3/18/2014 7:10:53 PM

LastExecutionTime

: 3/18/2014 7:10:53 PM

CorruptionsDetected

: 0

ErrorCode

:

CorruptionsFixed

: 0

TimeInServer

: 00:01:53.1760000

Corruptions : {}Slide46

Store-Specific Managed Availability Scenarios

Name

Trigger/Recovery sequenceDatabase Availability16 logon failures in 22 minutes  EscalateStore service not running2 failures in 12 minutes  Restart service  Bugcheck  Escalate

Database Free space

Free disk space drops below 10%



Escalate

Store service process repeatedly crashing

3 crashes for store service in 1 hour



Escalate

Store worker process repeatedly crashing

3 crashes for store work (across all workers) in 1 hour



Escalate

Percent RPC requests

90% of available threads per

database for 10 min



Database Failover



Escalate

70ms RPC latency

70ms RPC

Avg

latency for 10 min  Determine impact scope  Escalate150ms RPC latency

150ms RPC Avg latency for 10 min  Determine impact scope  EscalateMailbox quarantinedMore than 1 mailbox quarantined on database for 10 minutes  Escalate

Assistants service not running

2 failures in 12 minutes  Restart service  EscalateEvent assistants behind watermarksAssistant watermark age exceeds 1 hour threshold for 4 hours 

EscalateNumber of active background tasksCount of active background tasks exceeds threshold for 15 min  Escalate

Database Repeatedly Mounting

3 database mount attempts in 1 hour  EscalateSlide47

Future Exchange Store EnhancementsPulsing Index Creation

Index operations require exclusive mailbox lockDivide single long operation into multiple shorter operations

Allows other RPC operations to be processed during index creationPotential to increase latency of RPC operation that caused index creationAutomated Mailbox Repair TasksProactively detect and repair mailbox corruptionsDiscretionary workload that occurs during non-peak hoursTasks interrupted when resource monitors show unhealthy stateOnly targets mailboxes with logon activityMailbox repair task can occur no more than once per interval (month)Management support for passive databasesSlide48

SummaryExchange mailbox storage has…

Compared with Exchange 2010, reduced DB IOPS by 40-78%*...again!

Optimized for large disks (up to 8TB) and mailboxes (+100GB) Optimized for large/slow/low-cost disks (SATA/Tier2)JBOD/RAID'less storage a viable option for the massesBetter isolation leading to higher reliabilityBuilt-in monitoring and recovery to drive higher availabilityImproved with every CU based on experiences from Exchange Online!* Outlook online vs. cache mode scenariosSlide49

Please complete session evaluationsSlide50

Go

to

the Pre-Release Programs BoothTell us about your Office 365 environment/or on premises plansGet selected to be in a programTry new features first and give us feedback!Start now at:http://prereleaseprograms-public.sharepoint.com/Pre-Release Programs TeamBe first in

line

!Slide51
Slide52

© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.