Transcription

1 ZipMail for Microsoft Outlook Technical Benefits and receiving an Step by step analysis of elementary operations and ZipMail benefits Microsoft Exchange Administrators, All you ever wanted to know about disk space, network bandwidth, CPU and IOs consumed when sending and receiving s with attached Surprised about how fast your MS Exchange needs for disk space grows in time? Would like to understand why all is so slow since you migrated your Exchange servers to the Cloud? Looking for a simple solution to solve MS Exchange volume and performance issues? This presentation and next steps suggested at the end can help! Slide 1

2 A user attaches some to an File Size: In this and next slides, the amount of resource consumed for each type of resource is set to. For each type of resource, this is an arbitrary value given to the amount of resource consumed without any of our optimization software installed. For example: a file consumes a given number of CPU cycles. represents this number of cycles. a file consumes a given disk I/O. represents this number of disk I/O. etc. Slide 2

3 The user sends the to one recipient File Size: The and its attached are stored into the user local OST file and sent to the Exchange server. Slide 3

4 The transits on the network up to the MS Exchange server File Size: Network Bandwidth: The and its attached are uploaded to the MS Exchange server. Slide 4

5 The arrives on the MS Exchange server File Size: Network Bandwidth: The and its attached are uploaded to the MS Exchange server. Slide 5 the

6 The is processed by the MS Exchange server File Size: Network Bandwidth: The and its attached are stored into the sender s mailbox (Sent items folder) and the recipient s mailbox (Inbox). There are 2 physical copies of the (and of its attached ) in the MS Exchange database because MS Exchange does not provide deduplication. Slide 6 the Storing the in Sender + recipient mailboxes

7 The transits on the network to the recipient s PC File Size: Network Bandwidth: Network - download Network Bandwidth: Slide 7 The and its attached are downloaded to the recipient s PC. the reading the from the recipient mailbox

8 The arrives on the recipient s PC. It is stored into the user s OST file File Size: Outlook user s PC (recipient) File Size: Network Bandwidth: Network - download Network Bandwidth: The and its attached are downloaded to the recipient s PC. Slide 8 the reading the from the recipient mailbox

9 The user views or detaches the attached Outlook user s PC (recipient) Detaching File Size: File Size: Network Bandwidth: Network - download Network Bandwidth: The attached are saved to the recipient s PC hard drive. Slide 9 the reading the from the recipient mailbox

10 Fault tolerant MS Exchange server with 2 Database Availability Group members Outlook user s PC (recipient) Detaching File Size: File Size: Most often, MS Exchange servers are configured to be fault tolerant. Network Bandwidth: Network Bandwidth: Slide 10 MS Exchange databases are replicated to one or more MS Exchange servers configured as Database Availability Group (DAG) members. In our example, MS Exchange has been configured with Network 2 DAG - members. download Each DAG member hosts a copy of the MS Exchange databases. the Synchro DAG Member 1 Storing the in Sender + recipient mailboxes Net. Bandwidth: DAG Member 2 the reading the from the recipient mailbox

11 Exchange server databases backups Outlook user s PC (recipient) Detaching File Size: File Size: Network Bandwidth: Slide 11 Additional to fault tolerance, the MS Exchange databases can also be backedup on external storage devices. Depending on Network the backup - schedule, Download download for instance daily Network + weekly Network Bandwidth: + monthly, backup storage space needed can be several times the size of the backed-up databases. the Synchro DAG Member 1 Storing the in Sender + recipient mailboxes Net. Bandwidth: DAG Member 2 the reading the from the recipient mailbox Backup Operations Backup Space:

12 Exchange server database restore operations Outlook user s PC (recipient) Detaching File Size: File Size: Network Bandwidth: Slide Backup Space: 12 Network - Download download Backups sometimes need to be restored. Network Network Bandwidth: Restoring large MS Exchange databases can take a long time. the Synchro DAG Member 1 Restore Operations Storing the in Sender + recipient mailboxes Backup Operations Net. Bandwidth: DAG Member 2 the reading the from the recipient mailbox

13 with attached file sent to one recipient Outlook user s PC (recipient) Detaching File Size: File Size: Network Bandwidth: Slide Backup Space: 13 Network - Download download Network Network Bandwidth: This is the complete picture! the Synchro DAG Member 1 Restore Operations Storing the in Sender + recipient mailboxes Backup Operations Net. Bandwidth: DAG Member 2 the reading the from the recipient mailbox

14 Now, let s install ZipMail for Microsoft Outlook on the sender s PC and look at the benefits it delivers. Slide 14

15 A user attaches some to an File Size: ZipMail This time, ZipMail for Microsoft Outlook is installed. At the time the user attaches the, ZipMail starts making them smaller. Slide 15

16 The user sends the to one recipient File Size: ZipMail Let s take the hypothesis that ZipMail reduces the selected to attach by %. To do so ZipMail consumes a given amount of local CPU, disk I/O and time (from a few tenths of a second to a couple of seconds depending on the size of the attached ). This is barely perceptible for the user; first because it is a fast operation and second because with smaller, next operations on the like inserting it in the OST file and uploading it to the MS Exchange server will take % less time and resources. Slide 16

17 The transits on the network up to the MS Exchange server File Size: ZipMail Network Bandwidth: The and its attached are uploaded to the MS Exchange server. Thanks to ZipMail the upload is 2 times faster and consumes 2 times less network bandwidth and router processor cycles. Slide 17

18 The arrives and is processed on the MS Exchange server File Size: ZipMail Network Bandwidth: On the MS Exchange server, it takes 2 times less CPU cycles and disk I/O to process the and to store it in the MS Exchange databases. The is processed 2 times faster. The consumes 2 times less storage space in the MS Exchange databases. Slide 18 the Storing the in Sender + recipient mailboxes

19 The transits on the network to the recipient s PC File Size: ZipMail Network Bandwidth: Network - download Network Bandwidth: The download is 2 times faster. It consumes 2 times less network bandwidth and router processor cycles. Slide 19 the reading the from the recipient mailbox

20 The arrives on the recipient s PC. It is stored into the user s OST file File Size: ZipMail Outlook user s PC (recipient) Network Bandwidth: Network - download Network Bandwidth: The received is processed 2 times faster by the recipient s PC. It consumes 2 times less space in the user s OST file. Slide 20 the reading the from the recipient mailbox

21 The user views or detaches the attached File Size: File Size: ZipMail Outlook user s PC (recipient) Detaching Network Bandwidth: Network - download Network Bandwidth: If the user saves the attached on disk, the detach operation is 2 times faster. The detached consume 2 times less disk space. The recipient does not need ZipMail. Slide 21 the reading the from the recipient mailbox

22 Fault tolerant MS Exchange server with 2 Database Availability Group members File Size: File Size: ZipMail Outlook user s PC (recipient) Detaching With fault tolerant MS Exchange servers Network Bandwidth: configured with 2 or more DAG members, each Router DAG Processor: member hosts a copy of the MS Exchange databases. The is synchronized between DAG members 2 times faster. The synchronization consumes 2 times less CPU, network bandwidth and time. Network - download The volume reduction benefits apply to all DAG member databases. Network Bandwidth: Slide 22 Synchro DAG Member 1 the Net. Bandwidth: Storing the in Sender + recipient mailboxes DAG Member 2 the reading the from the recipient mailbox

23 Exchange server databases backups File Size: File Size: ZipMail Outlook user s PC (recipient) Detaching Additional to fault tolerance, the MS Exchange databases can also be backed-up on external storage devices. Depending Network on the Bandwidth: backup schedule, for instance daily + weekly + monthly, backup storage space needed can be several times the size of the backed-up databases. Thanks to ZipMail, the need for backup space is 2 times less. Network - download The backup of the is 2 times faster. Network Bandwidth: It and consumes 2 times less CPU and I/O. Slide Backup Space: 23 Synchro DAG Member 1 the Net. Bandwidth: Storing the in Sender + recipient mailboxes DAG Member 2 the reading the from the recipient mailbox Backup Operations

24 Exchange server database restore operations File Size: File Size: ZipMail Outlook user s PC (recipient) Detaching Network Bandwidth: Network - download Backups sometimes need to be restored. Network Bandwidth: Restoring s with optimized attached is 2 times faster. Slide 24 Synchro Restore Operations DAG Member 1 the Net. Bandwidth: Storing the in Sender + recipient mailboxes DAG Member 2 the reading the from the recipient mailbox Backup Operations Backup Space:

25 with attached file sent to one recipient ZipMail for Microsoft Outlook installed on the sender s PC File Size: File Size: ZipMail Outlook user s PC (recipient) Detaching Network Bandwidth: Network - download Network Bandwidth: Now we have the almost complete picture! Slide 25 Synchro Restore Operations DAG Member 1 the Net. Bandwidth: Storing the in Sender + recipient mailboxes DAG Member 2 the reading the from the recipient mailbox Backup Operations Backup Space:

26 The previous slides were about an sent to one single recipient. What about an sent to 10 recipients? Let s calculate the total network and MS Exchange storage savings delivered by ZipMail for Microsoft Outlook when sending a 20 MB attached file reduced to 10 MB to 10 users. Slide 26

27 Thanks to ZipMail for Microsoft Outlook, for this single 20 MB sent to 10 recipients, we saved: On a server with no DAG, 110 MB of MS exchange storage and 110 MB of network bandwidth. On a server with a DAG and 2 DAG members, 220 MB of MS exchange storage and 220 MB of network bandwidth. Without ZipMail With ZipMail MS Exchange server No DAG Network Savings Exchange server storage savings 1 First upload (network): 20 MB 10 MB (*1) 10 MB 10 MB In the sender MS Outlook OST or PST file: 20 MB 10 MB MS Exchange server DAG with 2 DAG members Network Savings Exchange server storage savings 2 On the MS Exchange server: a) No DAG: Storage: 220 MB 110 MB (*2) 110 MB or b) with 2 DAG members: Network (Synchronization): 220 MB 110 MB 110 MB Storage: 440 MB 220 MB 220 MB 3 Reception of the by its recipients (network): 200 MB MB (*1) MB MB In the recipient MS Outlook OST : 200 MB MB (*1) (*2) see next slides Total savings: 110 MB 110 MB 220 MB 220 MB Slide 27

28 ROI Think about a few hundred, thousands, 10,000,,000 or more than 2,000 Microsoft Outlook users worldwide, like at our largest customers, and you can easily imagine the massive ROI ZipMail is able to deliver in terms of Microsoft Exchange storage and network usage. Performance This astounding level of volume reduction has for effect to boost the overall performance of your Microsoft Exchange organization. Having two times less messaging volume to handle is the same as doubling your network bandwidth and storage capacity and doubling the power of your MS Exchange servers. (*1) (*2) see next slides Slide 28

29 (*1) Volume optimization delivered by ZipMail on the network also applies on network links under the control of network optimization appliances and network compression software. The reason is that the ZipMail native XML file optimization (for DOCX, XLSX, PPTX, VSDX etc. ) and image file optimization (for JPG, PNG, GIF etc. ) is out of the scope of network compression appliances and software that make use of traditional (Zip like) compression that is inefficient on XML and image. This is also true for low level disk compression. (*2) From Microsoft Exchange 2010 and higher, there is no Single Instance Storage (SIS) option available anymore. This means that a given sent to 10 users is stored 11 times (including its attachments) in the MS Exchange store (one physical copy per recipient plus one copy in the sender Sent Items folder). Like for network compression, the volume optimization delivered by ZipMail on storage also applies on storage devices supporting low level disk compression. Slide 29

30 Next Steps Thanks very much for your attention. We hope you enjoyed this presentation. Would you like to go further, please see below for next steps: To know more about ZipMail for Microsoft Outlook please see the home page of ZipMail for Microsoft Outlook including videos of the ZipMail optimization features, samples of MS Office and Picture (before and after ZipMail optimization), download of a ZipMail for MS Outlook fully functional evaluation version, a detailed list of ZipMail for Microsoft Outlook features and more interesting items. Make sure to contact us at any time, we'll be most pleased to answer any questions you may have about ZipMail for Microsoft Outlook. Slide 30