All C-Clips for an application have to be contained in one CAS Virtual Pool on ViPR.  Unlike in Centera there is no capability to grant read access to an application's access profile to other CAS Virtual Pools on a ViPR cluster.  Therefore you will need to migrate C-Clips an application wants to access from the source Centera into the one CAS Virtual Pool that the application has an access profile for.  This will likely require you to obtain a C-Clip list from the application and use that list as the source C-Clip list.  As opposed to querying for all C-Clips that are accessible by the Centera's anonymous profile, as you would then need to filter out what C-Clips belongs to what application.  Some/most applications do include clip metadata attributes in the C-Clip which would allow your migration tool/process to identify the C-Clip owner but some applications do not.  In these cases you have a challenge!
A Centera has to be migrated into ViPR CAS. The legacy data is housed in the Default-pool (historic reasons), as well as in a couple of accesspools. Each Profile has a defined accesspool as home-pool and granted read capabilities in the Default pool. Is this configuration supported on ViPR CAS? To my understanding, it is not. What is the best practice to place and Access the legacy data on ViPR after it has been migrated?  Thanks Ralf
ViPR CAS: pool/profile relation?