Object level Migration to a new system

[sandeepveldi]

Hi All,
Please let me know if any one has dealt with a data migration strategy from one CMOD system to another at an object level instead of going through document level processing?

Thanks in advance,
SV

[Alessandro Perucchi]

Hello Sandeep,

I've dealt with CMOD migration on lots of cases, on lots of level, even on the object level.

What are you trying to do exactly? Cache migration, TSM migration, Rename of CMOD instance, Consolidation of Library Server/Object Server, something else?

Cheers,
Alessandro

[markrussell]

Sandeep,

Like Alex, not sure what you mean exactly, but if it's migrating an Ondemand library server, we have recently done this using the xml interface (combination of xml export and xml add).

To migrate the actual documents (there were 4 million of them), we copied the contents of the data table segments of the migrated application groups to their corresponding tables in the destination Library server. During the copy, we had to change a field in each segment (PRI_NID) so that it pointed to the existing storage node. In this way, the documents in TSM could be accessed from a different OnDemand instance without having to physically move them.

The official method to migrate documents is "arsdoc get" and "arsload", however in our case this would have taken far too long.

[Justin Derrick]

Hi Sandeep.

Most migrations are a great opportunity to fix problems with Application Groups -- issues with number of rows per database table, or the expiration type.  So don't eliminate the possibility of using arsdoc to get your documents and reload them into a newly defined AG with a slightly different configuration.

Moving objects themselves can be tricky, but you haven't told us what the goal is -- are you moving to new storage media?  (Optical to tape, disk to tape, etc.)  Or are you trying to do a shortcut for a hardware migration?  Where are the objects right now? (Cache, or TSM?)

-JD.

[sandeepveldi]

All,
Thanks for your responses. The purpose is to copy data from an existing CMOD system to a brand new CMOD system with beefed up hardware. Also, as JD mentioned there can be some application group changes like addtional index fields and changes to DB2 table size etc.
I'm aware of using arsadmin retrieve to get the Objects out of CMOD. But, can we store it without any performance issues to the new system (Assuming that database data will be exported seperately, enriched and then loaded to the new database seperately).

Regards,
SV