Unsolved
This post is more than 5 years old
1 Rookie
•
47 Posts
0
425
February 20th, 2010 08:00
move legacy data from default pool to new virtual
Help,
In setting up replication from one site to another, we needed to differentiate this centera and pool from another, so essentially inward star replication. However since these are gen3 nodes and the cluster has been around through various code versions, still contained only the default pool. Any virtual pools had not been set up until now. So now that I have, how can I safely move the existing data from the default pool to this new virtual pool?
Thanks
EMCDennis
124 Posts
0
February 22nd, 2010 07:00
A clip is a XML file that contains metadata and blob references. The clip content address (the clip ID) is based off of the md5sum of the clip XML content.
Pool information is stored inside the clip XML meta-data. Any changes to a clip will change the md5sum of the clip thus the content address of the clip itself.
Because of this, you cannot change the pool of an object without changing the clip and thus the clip ID.
In order to change the pool requires that the application read the data back and then rewrite it to the proper pool and then delete the old clip.
There is pool mapping that allows you to map clips that are written without pool information (written to the default pool) to a specific pool. This is a logical mapping and does not actually change clip content. This can be used to map all such clips to a pool however you cannot map certain clips to one pool and other clips to another. It is all or nothing.
Hope this answers your question
holgerjakob_c0722c
2 Intern
•
337 Posts
0
March 2nd, 2010 12:00
Hi rpereira
The command to look for is create poolmapping . There is a good documentation in the online help installed with CenteraViewer resp. the Centera Tools.
As you can see the poolmapping maps all clips that were written by a given profile to a new application pool. You can migrate data written by three profiles to the default pool to three different application pools.
ATTENTION: There is one restriction for this. This only works for objects that were written by an application using SDK 2.3 or later. Previously the creation profile tag is missing in the CDF that is required for CentraStar to figure out which clips need to be migrated to the application pool. The Clips written with an even older SDK remain in the default pool.
I've had this a couple of times and so far we were always lucky that there was only one application with SDK older than 2.3. This was always acceptable for the customer to have the data of just one application in the default pool.
If you want to be able to find out before you migrate let me know. I can issue a trial license for ApplicationAudit that would read all your CDF Metadata into a SQL database and you could have a look at the CDF's from your application before you get started. We could also assist you remotely if need be.
Best regards, Holger
holger.jakob@informatio.ch