184 IBM ProtecTIER Implementation and Best Practices Guide
12.2.6 Encryption
Encryption makes each piece of data (including duplicate data) sent to the ProtecTIER serve
unique. Encryption affects the data matching rates and the factoring performance. Even if the
same data is sent each time, it appears as different data to the deduplication engine. Disable
any encryption features for the ProtecTIER server defined for the backup server.
12.2.7 Multiplexing
Do not use the multiplexing feature of any backup application with the ProtecTIER product.
Although the ProtecTIER product works with these features, the benefits (disk savings) of the
HyperFactor algorithm and compression is reduced. Disable any multiplexing features that
the ProtecTIER product defined for the backup server.
12.2.8 Tape block sizes
To optimize the backup server performance, set the block size for data sent to the (virtual)
tape drives to
256 KB or greater.
12.2.9 Type of data backed up
Another factor that affects performance in a ProtecTIER environment is the type of data
targeted for backup. Some data is well-suited for data deduplication and other data is not. For
example, small files (less than 32 KB in size) commonly found in operating systems do not
factor well, although the built-in compression might reduce their stored size. For more
information about data types, see Chapter 20, “Application considerations and data types” on
page 277.
Reevaluate your current backup workloads. Decide which backups are not good candidates
for ProtecTIER deduplication.
12.3 General advice for backups
Generally, the preferred method of operation for using the ProtecTIER product is to imitate
the procedure used with physical cartridges. Implement the time frame mode of operation so
that, for every 24-hour cycle, there is a backup window and then a replication window. The
user must ensure that there is enough bandwidth (TCP/IP and SAN) and time allotted so that
there is no overlap and no replication backlog.
Here is a typical operational flow:
1. Perform regular daily backups to the ProtecTIER system during the defined
backup window.
2. After the daily backups are complete, perform a full catalog/DB backup to cartridge to the
ProtecTIER repository.
3. Set up the system so that replication starts and is finished before the next backup
cycle starts.
4. The user must have a complete and easily recoverable set of their latest daily backups,
including the backup application catalog image.

Get IBM ProtecTier Implementation and Best Practices Guide now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.