Move data from one pool to another

Koen,

Short answer, yes if the data was initially written with a profile to the default pool, you can move it to another pool using the built in pool mapping functionality of the Centera.

If you already have a custom profile with a custom home pool, the only way to change pools would be to pull all data off the box and rewrite it with the new profile (or same profile with a different home pool).

This is from the Online Help. This comes with Centera Console's iso which you can download on PowerLink.

Home > Support > Software Downloads and Licensing > Downloads C > Centera Console Software


"Centera Configuration

Pool Migration of Legacy Data

The purpose of this procedure is to explain how to migrate C-Clips from the default pool to a custom application pool. C-Clips can be migrated provided they were written using the SDK 2.3 or higher.

EMC discourages to use pool migration as a general practice. Contact your EMC representative if you want move data from the default pool to a custom application pool.

C-Clips written using version 2.2 SP2 or earlier will always belong to the default pool. It is not possible to migrate these C-Clips to an application pool.

This procedure consumes system resources and you may notice an impact on performance whilst it is running. The migration task is, however, gated to 10 C-Clips/second per node so the impact will be minimal.

When a migration task is completed, the active mapping must remain on the cluster - this allows C-Clips to retain their new pool membership when regenerated or restored.

Selecting the Target Application Pool

C-Clips can be moved based on the profile that originally wrote the C-Clip. If different applications were writing to the default pool using different profiles, the C-Clips can be moved to application specific pools. If they both used the same profile, including the anonymous profile, they can be moved but not separated.

Procedure

Follow this procedure on each cluster in the replication topology to ensure that the pool ownership on each cluster is consistent.

1.

Launch the CLI and connect to the source cluster.
2.

Add a mapping between the profile used to write the C-Clips to the default pool and a pool using the create poolmapping command. The pool needs to exist on the cluster for the command to work and cannot be the default pool.
3.

The mappings are placed on the scratchpad which is used to prepare mappings until the user has the correct mappings to start the actual migration.
4.

View the scratchpad pool mapping to check that it is correct using the show pool mapping command.
5.

Follow the procedure from Step 2 for each profile with legacy data in the default pool.
6.

Once the mappings are in place, activate the pool mapping and start the migration task using the migrate poolmapping start command. This command copies all scratchpad mappings to the active mappings and re-starts the migration process.
7.

Monitor the migration task using the show pool migration command."