Not quite. Copy pools are normally not colocated...so are not clones of storage pools.
>>> [EMAIL PROTECTED] 08/08/03 09:52AM >>> >Is it possible to have onsite versioning different than offsite versioning. >Ex. They want to have 7 versions onsite and just 3 versions offsite. In >the TSM realm, is this possible, feasible, or else, As Andy touched on yesterday, a given file has only one policy affecting it; so you cannot have multiple policies for the same file. Realizing that file identity is a combination of node, filespace, and filename, you could, however, employ differing file system identies on the client to effect different identities and thus use different managment classes for the same data - but, of course, multiple copies of the same data, which multiplies your storage requirements. "Offsite" means copy storage pools, which are exact images of onsite primary storage pools, so no fooling around. I would seek to have "They" removed from the premises. Whimsical data storage requirements waste valuable time. Richard Sims, BU
