Implement data deduplication in IBM® Tivoli® Storage
Manager by using
the best practices to ensure that the benefits of data deduplication
are optimized on your system.
When you use data deduplication, your system can achieve benefits
such as these:
- Reduction in the storage capacity that is required for storage
pools on the server that are associated with a FILE-type device class.
This reduction applies for both server-side and client-side data deduplication.
- Reduction in the network traffic between the client and server.
This reduction applies for client-side deduplication only.
Using data deduplication requires an increase in resources on the Tivoli Storage
Manager server and
clients. The upper limit on the size of objects that are stored in
deduplicated storage pools is one primary consideration. However,
in general, a server that uses data deduplication must be allocated
additional resources.
When you implement the suggested practices for data deduplication,
you can help to avoid problems such as these on your system:
- Server outages that are caused by running out of active log space
or archive log space
- Server outages or client backup failures that are caused by exceeding
the IBM DB2® internal lock list limit
- Process failures and hangs that are caused during server data
management