michael_aiello
1 Copper

Migration from Centera to ECS using CAS

We have an application that stores Centera C-clip ids in a database. If we perform bulk-migration using ecs-sync, I would expect the C-clip ids we have stored would no longer be valid in accessing the ECS copy via CAS. Is that correct?

Thanks

Michael Aiello

ASG

Tags (1)
0 Kudos
2 Replies
8 Krypton

Re: Migration from Centera to ECS using CAS

michael.aiello,

ecs-sync uses the CAS raw-write operation, which completely replicates the original CDF and blob content.  The clip ID (CA) will remain exactly the same.  The only thing that will change is the pea file and endpoint.  So all of your database pointers will still be valid.  Please be aware that unlike ECS CAS Transformation, ecs-sync does not provide an instant cutover, so there will be some downtime during the final iterative copy, after which your applications will come back up using ECS.

In case you haven't already done so, I highly recommend engaging EMC professional services to handle the migration as they have a lot of experience with production CAS migrations, and would be able to answer any questions you have.

0 Kudos
Highlighted
jikvk09
1 Copper

Re: Migration from Centera to ECS using CAS

michael.aiello wrote:

We have an application that stores Centera C-clip ids in a database. If we perform bulk-migration using ecs-sync, I would expect the C-clip ids we have stored would no longer be valid in accessing the ECS copy via CAS. Is that correct?

Thanks

Michael Aiello

ASG

Hi, The clip ID (CA) will remain exactly the same. The only thing that will change is the pea file and endpoint.  So all of your database pointers will still be valid.