restore / replicate to different pool on new centera

The pool and profile is contained within the clip XML itself - Replication is replicating the clips and as such, it cannot change. Changing the pool (or profile) would change the clip and thus would change the clip ID.

Pool mapping is the only way to make this work and only if there is profile information stored in the clip and no pool info (i.e, it was written before pools were introduced).

Well, here's some of my confusion:

1) If I do a pool mapping on the source, can I replicate to the destination to the same named private pool mapped on the source, and thereby have a copy in a private pool on the target, or would I have to pool mapping on the target as well? This is assuming I could import the profile from the source to the target and update it to reflect the new pool.

2) To setup pool mapping I have to modify the application PEA file to point to the new mapped pool, right? Do I then not have access to data until the pool mapping is complete with that profile?

3) You say pool mapping works "only if there is profile information stored in the clip and no pool info". The PEA file for this application was created on an older OS version, so does this mean all data created or only data before upgrading wouldn't contain pool info?

4) The manual says pool mapping isn't recommended by EMC- why? Is there a performance impact (and how much)?

I recently did this at a customer site. I created the mapping on both source and target. Only then would the restore work. This is the only way I know of without pulling back all data to another storage medium and rewriting, to move data to another pool and then to subsequently migrate it.

Steve

Thanks!

So as I understand things (correct me if I'm wrong) - unless the application profile being used was setup to write to a private pool, the c-clips won't have any pool information in them. If the old clips don't have pool data in them, then you can only map them to a private pool, not change them to "belong" to that pool. So if mapping is done using the existing profile and I modify that profile to write to the private pool, then the old data is mapped from the default to the private and any new clip creations will contain pool data tagging it as belonging to the private pool.

Exactly - You got it