11.07.2015 Views

Installation and User's Guide - Services and Support

Installation and User's Guide - Services and Support

Installation and User's Guide - Services and Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

IBM Confidential1. Verify that you are running version 5.3.0 (or later) of the Tivoli StorageManager server <strong>and</strong> Tivoli Storage Manager API.2. Edit the options file for Data Protection for Exchange <strong>and</strong> add thefollowing three options:a. Add the enableclientencryptkey yes option.b. Add the encryptiontype option with the type of encryption to use.c. Add your include statements with the include.encrypt option. Forexample, to encrypt all Exchange data, specify the following:include.encrypt *\...\*To encrypt all the data in Storage Group 1, specify the following:include.encrypt "SERVER_NAME\Storage Group 1\...\*"COMPRESSIonThis option instructs the Tivoli Storage Manager API to compress databefore sending it to the Tivoli Storage Manager server; this reduces traffic<strong>and</strong> storage requirements. If you enable compression, it affectsperformance in two ways:v CPU utilization is higher on the machine on which Data Protection forExchange is running.v Network b<strong>and</strong>width utilization is lower because fewer bytes are sent.v Storage usage on the Tivoli Storage Manager server is reduced.You may want to specify compression yes if any of the following conditionsexist:v The network adapter has a data overload.v Communications between the Data Protection for Exchange <strong>and</strong> TivoliStorage Manager server are over a low b<strong>and</strong>width connection.v There is heavy network traffic.v You can also use the compressalways yes option (with the compressionyes setting) to specify that file compression continues even if the filegrows as a result of compression.It may be better to specify compression no in the following cases:v The computer running Data Protection for Exchange has a CPUoverload; the added CPU usage can impact other applications includingthe Exchange Server. You can monitor CPU <strong>and</strong> network resourceutilization using the Performance Monitor program shipped withWindows.v You are not constrained by network b<strong>and</strong>width; in this case, you canachieve the best performance by leaving compression NO <strong>and</strong> enablinghardware compaction on the tape drive, which also reduces storagerequirements.The Tivoli Storage Manager administrator can override the compressionoption setting for the Data Protection for Exchange node when registeringor updating the node by specifying, on the Tivoli Storage Manager serverside, that a particular node:v Always uses compression.v Never uses compression.v Leaves the decision up to the client (default value).Considerations:Chapter 3. Configuring Data Protection for Exchange 41

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!