ZipMail for Microsoft Outlook · 2019. 3. 12. · ZipMail for Microsoft Outlook Technical Benefits...
Transcript of ZipMail for Microsoft Outlook · 2019. 3. 12. · ZipMail for Microsoft Outlook Technical Benefits...
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 1
ZipMail for Microsoft OutlookTechnical Benefits
Sending and receiving an emailStep 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 emails with attached files
• 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!
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 2
• In this and next slides, the amount of resource consumed for each type of resource is set to 100.
• 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:Attaching a file consumes a given number of CPU cycles. 100 represents this number of cycles.Attaching a file consumes a given disk I/O. 100 represents this number of disk I/O. etc.
A user attaches some files to an email…
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 3
The user sends the email to one recipient…
The email and its attached files are stored into the user local OST file and sent to the Exchange server.
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Sendingemail
100
OST Storage:
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 4
The email and its attached files are uploaded to the MS Exchange server.
The email transits on the network up to the MS Exchange server…
Network - Email upload
100
100
100Network Bandwidth:Time:
Router Processor:
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Sendingemail
100
OST Storage:
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 5
The email arrives on the MS Exchange server…
The email and its attached files are uploaded to the MS Exchange server.
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Sendingemail
100
OST Storage:
Network - Email upload
100
100
100Network Bandwidth:Time:
Router Processor:
Exchange Server
Receivingthe email
CPU:Disk I/O:
Time: 100
100
100
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 6
• The email and its attached files are stored into the sender’s mailbox (Sent items folder) and the recipient’s mailbox (Inbox).
• There are 2 physical copies of the email (and of its attached files) in the MS Exchange database because MS Exchange does not provide deduplication.
The email is processed by the MS Exchange server…
Exchange Server
Receivingthe email
CPU:Disk I/O:
Time: 100
100
100
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Sendingemail
100
OST Storage:
Network - Email upload
100
100
100Network Bandwidth:Time:
Router Processor: Storing the email inSender + recipient
mailboxes
100
100100
100
100
100
Mailbox Storage:
Transaction Logs:
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 7
Network - Email download
100
100100Network Bandwidth:
Time:Router Processor:
The email transits on the network to the recipient’s PC…
The email and its attached files are downloaded to the recipient’s PC.
7
Exchange Server
CPU:Disk I/O:
Time: 100
100
100
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Sendingemail
100
OST Storage:
Network - Email upload
100
100
100Network Bandwidth:Time:
Router Processor:
100
100100
100
100
100
Mailbox Storage:
Transaction Logs:
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 8
Outlook user’s PC (recipient)
CPU:Disk I/O:
Time:
File Size: 100
100
100
Receivingemail
100
OST Storage:
The email and its attached files are downloaded to the recipient’s PC.
The email arrives on the recipient’s PC.It is stored into the user’s OST file…
Network - Email download
100
100100Network Bandwidth:
Time:Router Processor:
Exchange Server
CPU:Disk I/O:
Time: 100
100
100
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Sendingemail
100
OST Storage:
Network - Email upload
100
100
100Network Bandwidth:Time:
Router Processor:
100
100100
100
100
100
Mailbox Storage:
Transaction Logs:
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 9
The email attached files are saved to the recipient’s PC hard drive.
The user views or detaches the attached files…
Outlook user’s PC (recipient)
Detachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Receivingemail
100
OST Storage:
Network - Email download
100
100100Network Bandwidth:
Time:Router Processor:
Exchange Server
CPU:Disk I/O:
Time: 100
100
100
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Sendingemail
100
OST Storage:
Network - Email upload
100
100
100Network Bandwidth:Time:
Router Processor:
100
100100
100
100
100
Mailbox Storage:
Transaction Logs:
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 10
Outlook user’s PC (recipient)
Detachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Receivingemail
100
OST Storage:
Network - Email download
100
100100Network Bandwidth:
Time:Router Processor:
Exchange Server
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Sendingemail
100
OST Storage:
Network - Email upload
100
100
100Network Bandwidth:Time:
Router Processor:
Receivingthe email
CPU:Disk I/O:
Time: 100
100
100
Storing the email inSender + recipient
mailboxes
100
100
100
100
100
100
Mailbox Storage:
Transaction Logs:
Fault tolerant MS Exchange server with 2 Database Availability Group members
• Most often, MS Exchange servers are configured to be fault tolerant.
• 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 2 DAG members. Each DAG member hosts a copy of the MS Exchange databases.
Exchange Server DAG Member 1
CPU:Disk I/O:
Net. Bandwidth:Time: 100
100
100
100Synchro
CPU:Disk I/O:
Time: 100
100100
100
100
100
100
100100
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 2
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 11
Network - Email upload
100
100
100Network Bandwidth:Time:
Router Processor:
Network Bandwidth: 100
Time: 100
Router Processor: 100
Network - Email Download
Exchange server databases backups
11
CPU:Disk I/O:
Time:Backup Space: 100
100
100100
Backup Operations
Outlook user’s PC (recipient)
Detachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Receivingemail
100
OST Storage:
Exchange Server
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Sendingemail
100
OST Storage:
Receivingthe email
CPU:Disk I/O:
Time: 100
100
100
Storing the email inSender + recipient
mailboxes
100
100
100
100
100
100
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 1
CPU:Disk I/O:
Net. Bandwidth:Time: 100
100
100
100Synchro
CPU:Disk I/O:
Time: 100
100100
100
100
100
100
100100
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 2
Network - Email download
100
100100Network Bandwidth:
Time:Router Processor:
• Additional to fault tolerance, the MS Exchange databases can also be backed-up on external storage devices.
• Depending on the backup schedule, for instance daily + weekly + monthly, backup storage space needed can be several times the size of the backed-up databases.
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 12
Network - Email upload
100
100
100Network Bandwidth:Time:
Router Processor:
Network Bandwidth: 100
Time: 100
Router Processor: 100
Network - Email Download
CPU:Disk I/O:
Time:Backup Space: 100
100
100100
Backup Operations
Outlook user’s PC (recipient)
Detachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Receivingemail
100
OST Storage:
Exchange Server
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Sendingemail
100
OST Storage:
Receivingthe email
CPU:Disk I/O:
Time: 100
100
100
Storing the email inSender + recipient
mailboxes
100
100
100
100
100
100
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 1
CPU:Disk I/O:
Net. Bandwidth:Time: 100
100
100
100Synchro
CPU:Disk I/O:
Time: 100
100100
100
100
100
100
100100
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 2
Network - Email download
100
100100Network Bandwidth:
Time:Router Processor:
• Backups sometimes need to be restored.
• Restoring large MS Exchange databases can take a long time.
Exchange server database restore operations
CPU:Disk I/O:
Time: 100
100
100
Restore Operations
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 13
Network - Email upload
100
100
100Network Bandwidth:Time:
Router Processor:
Network Bandwidth: 100
Time: 100
Router Processor: 100
Network - Email Download
CPU:Disk I/O:
Time:Backup Space: 100
100
100100
Backup Operations
Outlook user’s PC (recipient)
Detachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Receivingemail
100
OST Storage:
Exchange Server
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
100
100
100
Sendingemail
100
OST Storage:
Receivingthe email
CPU:Disk I/O:
Time: 100
100
100
Storing the email inSender + recipient
mailboxes
100
100
100
100
100
100
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 1
CPU:Disk I/O:
Net. Bandwidth:Time: 100
100
100
100Synchro
CPU:Disk I/O:
Time: 100
100100
100
100
100
100
100100
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 2
Network - Email download
100
100100Network Bandwidth:
Time:Router Processor:
CPU:Disk I/O:
Time: 100
100
100
Restore Operations
This is the complete picture!
Email with attached file sent to one recipient
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 14
Now, let’s install ZipMail for Microsoft Outlook on the sender’s PC and look at the benefits it delivers.
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 15
• This time, ZipMail for Microsoft Outlook is installed.
• At the time the user attaches the files, ZipMail starts making them smaller.
A user attaches some files to an email…
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
ZipMail
100
100
100
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 16
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
ZipMail
100
100
100
The user sends the email to one recipient…
• Let’s take the hypothesis that ZipMail reduces the selected files to attach by 50%.
• 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 files).
• This is barely perceptible for the user; first because it is a fast operation and second because with smaller files, next operations on the email like inserting it in the OST file and uploading it to the MS Exchange server will take 50% less time and resources.
OST Storage:
Sendingemail
50
50
50
50
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 17
• The email and its attached files are uploaded to the MS Exchange server.
• Thanks to ZipMail the email upload is 2 times faster and consumes 2 times less network bandwidth and router processor cycles.
The email transits on the network up to the MS Exchange server…
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
ZipMail
100
100
100
OST Storage:
Sendingemail
50
50
50
50
Network - Email upload
Network Bandwidth:Time:
Router Processor: 50
50
50
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 18
The email arrives and is processed on the MS Exchange server…
• On the MS Exchange server, it takes 2 times less CPU cycles and disk I/O to process the email and to store it in the MS Exchange databases.
• The email is processed 2 times faster.
• The email consumes 2 times less storage space in the MS Exchange databases.
Exchange Server
Receivingthe email
CPU:Disk I/O:
Time:
Storing the email inSender + recipient
mailboxes
Mailbox Storage:
Transaction Logs:
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
ZipMail
100
100
100
OST Storage:
Sendingemail
50
50
50
50
50
50
50
50
5050
50
50
50
Network - Email upload
Network Bandwidth:Time:
Router Processor: 50
50
50
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 19
• The email download is 2 times faster.
• It consumes 2 times less network bandwidth and router processor cycles.
The email transits on the network to the recipient’s PC…
Exchange Server
CPU:Disk I/O:
Time:
Mailbox Storage:
Transaction Logs:
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
ZipMail
100
100
100
OST Storage:
Sendingemail
50
50
50
50
50
50
50
50
5050
50
50
50
Network - Email upload
Network Bandwidth:Time:
Router Processor: 50
50
50
Network - Email download
Network Bandwidth:Time:
Router Processor: 50
50
50
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 20
• The received email is processed 2 times faster by the recipient’s PC.
• It consumes 2 times less space in the user’s OST file.
The email arrives on the recipient’s PC.It is stored into the user’s OST file…
Exchange Server
CPU:Disk I/O:
Time:
Mailbox Storage:
Transaction Logs:
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
ZipMail
100
100
100
OST Storage:
Sendingemail
50
50
50
50
50
50
50
50
5050
50
50
50
Network - Email upload
Network Bandwidth:Time:
Router Processor: 50
50
50
Network - Email download
Network Bandwidth:Time:
Router Processor: 50
50
50Outlook user’s PC (recipient)
CPU:Disk I/O:
Time:
OST Storage:
Receivingemail
50
50
50
50
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 21
• If the user saves the attached files on disk, the detach operation is 2 times faster.
• The detached files consume 2 times less disk space.
• The recipient does not need ZipMail.
The user views or detaches the attached files…
Exchange Server
CPU:Disk I/O:
Time:
Mailbox Storage:
Transaction Logs:
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
ZipMail
100
100
100
OST Storage:
Sendingemail
50
50
50
50
50
50
50
50
5050
50
50
50
Network - Email upload
Network Bandwidth:Time:
Router Processor: 50
50
50
Network - Email download
Network Bandwidth:Time:
Router Processor: 50
50
50Outlook user’s PC (recipient)
Detachingfiles
CPU:Disk I/O:
Time:
File Size: OST Storage:
Receivingemail
50
50
50
50
50
50
50
50
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 22
Fault tolerant MS Exchange server with 2 Database Availability Group members
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
ZipMail
100
100
100
OST Storage:
Sendingemail
50
50
50
50
Network - Email upload
Network Bandwidth:Time:
Router Processor: 50
50
50
Network - Email download
Network Bandwidth:Time:
Router Processor: 50
50
50Outlook user’s PC (recipient)
Detachingfiles
CPU:Disk I/O:
Time:
File Size: OST Storage:
Receivingemail
50
50
50
50
50
50
50
50
• With fault tolerant MS Exchange servers configured with 2 or more DAG members, each DAG member hosts a copy of the MS Exchange databases.
• The email is synchronized between DAG members 2 times faster.
• The synchronization consumes 2 times less CPU, network bandwidth and time.
• The volume reduction benefits apply to all DAG member databases.
Exchange Server
Receivingthe email
CPU:Disk I/O:
Time:
Storing the email inSender + recipient
mailboxes
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 1
CPU:Disk I/O:
Net. Bandwidth:Time:
Synchro
CPU:Disk I/O:
Time:
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 2
50
50
50
50
5050
50
50
50
50
50
50
50
50
50
50
50
50
50
50
5050
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 23
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
ZipMail
100
100
100
OST Storage:
Sendingemail
50
50
50
50
Network - Email upload
Network Bandwidth:Time:
Router Processor: 50
50
50
Network - Email download
Network Bandwidth:Time:
Router Processor: 50
50
50Outlook user’s PC (recipient)
Detachingfiles
CPU:Disk I/O:
Time:
File Size: OST Storage:
Receivingemail
50
50
50
50
50
50
50
50
Exchange Server
Receivingthe email
CPU:Disk I/O:
Time:
Storing the email inSender + recipient
mailboxes
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 1
CPU:Disk I/O:
Net. Bandwidth:Time:
Synchro
CPU:Disk I/O:
Time:
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 2
50
50
50
50
5050
50
50
50
50
50
50
50
50
50
50
50
50
50
50
5050
• Additional to fault tolerance, the MS Exchange databases can also be backed-up on external storage devices.
• Depending on the 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.
• The backup of the email is 2 times faster.
• It and consumes 2 times less CPU and I/O.
Exchange server databases backups
CPU:Disk I/O:
Time:Backup Space:
Backup Operations
50
50
5050
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 24
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
ZipMail
100
100
100
OST Storage:
Sendingemail
50
50
50
50
Network - Email upload
Network Bandwidth:Time:
Router Processor: 50
50
50
Network - Email download
Network Bandwidth:Time:
Router Processor: 50
50
50Outlook user’s PC (recipient)
Detachingfiles
CPU:Disk I/O:
Time:
File Size: OST Storage:
Receivingemail
50
50
50
50
50
50
50
50
Exchange Server
Receivingthe email
CPU:Disk I/O:
Time:
Storing the email inSender + recipient
mailboxes
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 1
CPU:Disk I/O:
Net. Bandwidth:Time:
Synchro
CPU:Disk I/O:
Time:
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 2
50
50
50
50
5050
50
50
50
50
50
50
50
50
50
50
50
50
50
50
5050
CPU:Disk I/O:
Time:Backup Space:
Backup Operations
50
50
5050
Exchange server database restore operations
• Backups sometimes need to be restored.
• Restoring emails with optimized attached files is 2 times faster.
CPU:Disk I/O:
Time:
Restore Operations
50
50
50
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 25
Outlook user’s PC (sender)
Attachingfiles
CPU:Disk I/O:
Time:
File Size: 100
100
100100
ZipMail
100
100
100
OST Storage:
Sendingemail
50
50
50
50
Network - Email upload
Network Bandwidth:Time:
Router Processor: 50
50
50
Network - Email download
Network Bandwidth:Time:
Router Processor: 50
50
50Outlook user’s PC (recipient)
Detachingfiles
CPU:Disk I/O:
Time:
File Size: OST Storage:
Receivingemail
50
50
50
50
50
50
50
50
Exchange Server
Receivingthe email
CPU:Disk I/O:
Time:
Storing the email inSender + recipient
mailboxes
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 1
CPU:Disk I/O:
Net. Bandwidth:Time:
Synchro
CPU:Disk I/O:
Time:
Mailbox Storage:
Transaction Logs:
Exchange Server DAG Member 2
50
50
50
50
5050
50
50
50
50
50
50
50
50
50
50
50
50
50
50
5050
CPU:Disk I/O:
Time:Backup Space:
Backup Operations
50
50
5050
CPU:Disk I/O:
Time:
Restore Operations
50
50
50
Now we have the almost complete picture!
Email with attached file sent to one recipientZipMail for Microsoft Outlook installed on the sender’s PC
Sendingthe email
reading the email from the
recipient mailbox
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 26
• The previous slides were about an email sent to one single recipient.
• What about an email 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.
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 27
1 First email upload (network): 20 MB 10 MB (*1) 10 MB 10 MB
In the sender MS Outlook OST or PST file: 20 MB 10 MB
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 email by its recipients (network): 200 MB 100 MB (*1) 100 MB 100 MB
In the recipient MS Outlook OST files: 200 MB 100 MB
Total savings: 110 MB 110 MB 220 MB 220 MB
MS Exchange server MS Exchange server
savings
No DAG DAG with 2 DAG members
Exchange
server
storage
savings
Network
Savings
Network
Savings
Exchange
server
storageWithout
ZipMail
With
ZipMail
Thanks to ZipMail for Microsoft Outlook, for this single 20 MB email 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.
(*1) (*2) see next slides
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 28
• ROIThink about a few hundred, thousands, 10,000, 100,000 or more than 250,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.
• PerformanceThis 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 email network bandwidth and storage capacity and doubling the power of your MS Exchange servers.
(*1) (*2) see next slides
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 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. files) and image file optimization (for JPG, PNG, GIF etc. files) is out of the scope of network compression appliances and software that make use of traditional (Zip like) compression that is inefficient on XML files and image files.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 email 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.
www.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.comwww.smallerfaster.com
Slide 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 files (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.