Question & Answer
Question
When storing data in a disk storage pool with cache enabled, why do large data objects not maintain a cache version in the pool after migration?
Cause
The node option SPLITLARGEObjects manages how large objects are handled. It results in large objects being split into 10Gb fragments so they are easily managed during server operations. Fragmented objects are not eligible for disk cache operation, and as such results in the data being removed from disk during migration operations.
Answer
The default value for SPLITLARGEObjects is YES, which helps to optimize server processing. To keep a cache copy of large files in disk based storage pools after migration operations, it is necessary to update the node and set the value of SPLITLARGEObjects to 'NO'.
Related Information
Product Synonym
TSM
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg22012431