Use of mulitple cache

[wwwalton]

If I add a node that is cache only to each of the storage sets I use, a new NID results.  Do all of these in fact go the same cache that NID(0) uses? or is there duplication of the object, it appears that only one store takes place, ie. cache is cache.  Doing this would seem to allow migration to different storage strategy down the road should I want to move from one NID to another. Is this reasoning correct?
Thanks,
-walt

[Justin Derrick]

Hi Walt.

There's only one cache on the Multiplatforms version of CMOD -- even though it can consist of multiple filesystems.

It sounds like you're creating Storage Sets for new Application Groups -- which is something that I recommend as a best practice for CMOD Admins.  I usually suggest that each Storage Set have it's own node in TSM as well, but it doesn't sound like you're doing that.  (Although, I don't think defining Storage Sets in this way prevents you from adding a TSM node later on.)

Honestly, I'm a little fuzzy on exactly what you're doing and why.  If you can fill us in a little more on what you're doing (and trying to achieve), I'd greatly appreciate it. 

Happy New Year!

-JD.

[wwwalton]

Relates to an earlier post of getting off TSM/Centera.  The decision was to use cache only.  We've extended jfs sizes as needed and changed cache retention times in each group to match what it was in TSM.  So, since we have objects in TSM that are not in cache, I have to go through and copy from the TSM node to cache. So, the plan was to use the arsadmin and do retrieves from the TSM node both data and index, and store in the new cache only node for each corresponding node.  I noticed that defining a new cache only node in each storage set, caused a new NID value and so I guess I'd have to use that NID when doing the store operation, even though it all goes to the same cache.
-walt