nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Content Migration - Solaris to Linux

hymatron

Hi,
I just want to make sure the path that our team is taking will work.

We have successfully mounted our old Solaris content store on our new environment.

What we need to do is move a particular branch/workarea from the old store to the new one. Which is also a mounted store.

All Editions and versions must be migrated.

Is iwmigrate the correct tool for the job? Is it possible to run iwmigrate to split the branch we need and have the destination path be the new store?

Will iwmigrate merge the data that is on the new store with the data that is being split from the old one?

Or is there another tool that will copy records with versions across stores to similar branches?

Thank-you

Find more posts tagged with

Comments

Migrateduser

I think the iwmigrate will only do the latest edition. you can try writing a script to go through the whole store and copying older versions and editions to the new store.

Adam Stoller

Hi,
I just want to make sure the path that our team is taking will work.

We have successfully mounted our old Solaris content store on our new environment.

What we need to do is move a particular branch/workarea from the old store to the new one. Which is also a mounted store.

All Editions and versions must be migrated.

Is iwmigrate the correct tool for the job?

In general, yes, this is the correct tool for the job.

Is it possible to run iwmigrate to split the branch we need and have the destination path be the new store?

What do you mean by "split"?
iwmigrate copies content, metadata, and event information from one backing store into another backing store. You can specify a start and end edition to use (if you don't want all of them). You can specify a recursive migration that will also migrate all sub-branches (but I don't recommend that). iwmigrate does not "split" branches in and of itself - but through the use of start/end edition specifications you could migrate the first N editions from Branch-A in Store-A to Store-B and a different N editions from Branch-A in Store-A to Store-C (why you would want to do that - I'm not sure, but you can).

Will iwmigrate merge the data that is on the new store with the data that is being split from the old one?

iwmigrate does not do merging - it replays historical events to recreate the contents of a branch from one store to another store. You can either do this starting with a blank target store, or with a target store that is the untouched result of a previous iwmigrate. You cannot (to the best of my knowledge) iwmigrate a branch into a store that contains a branch of the same name with different contents.

Or is there another tool that will copy records with versions across stores to similar branches?

Thank-you

Other than doing a lot of hack-coding (IMO) - I do not believe there is a tool to do what you seem to be asking - but I may not be understanding what you are asking.

hymatron

Hey thanks for the replies so far.

I guess I need to qualify a few things.

When I mentioned "split" I was referring to iwmigrate being able to extract a workarea/branch from an existing store and move it to a new store. I was trying to say "split" the store.

When I mentioned "merge" I was hoping that the destination path of iwmigrate could be a pre-existing already populated store.

That way the workarea/branch being removed from the source could be inserted merged into the destination (and hopefully the destination can already have pre-existing data)

Adam Stoller

Hey thanks for the replies so far.

I guess I need to qualify a few things.

When I mentioned "split" I was referring to iwmigrate being able to extract a workarea/branch from an existing store and move it to a new store. I was trying to say "split" the store.

When I mentioned "merge" I was hoping that the destination path of iwmigrate could be a pre-existing already populated store.

That way the workarea/branch being removed from the source could be inserted merged into the destination (and hopefully the destination can already have pre-existing data)

Okay - let's go with those clarifications:

Okay?

Frederik

When I mentioned "split" I was referring to iwmigrate being able to extract a workarea/branch from an existing store and move it to a new store. I was trying to say "split" the store.

When I mentioned "merge" I was hoping that the destination path of iwmigrate could be a pre-existing already populated store.

yes, you can copy 1 branch out of a source store that has many branches.

yes, you can copy that branch into an existing store, (best) if that store doesn't have that same branch already.

so you can copy /store-old/branchA/branchB to /store-new/branchA/branchB. Unfortunately, you cannot put the branch at another relative location: it's impossible to copy it to /store-new/branchA/brC/brD/newbranchX.

After the copy with iwmigrate (and verification of success), you can delete the old branch in the old store with iwrmbr CLT.

Note that iwmigrate only migrates EDITIONS of a branch. So it doesn't migrate the modified stuff in a workarea, nor does it copy STAGING (if there are submits in staging after the latest edition)

Adam Stoller

Note also: After performing an iwmigrate - make sure to run an iwfsshrink on the target store - as iwmigrate tends to cause massive amounts of duplicate data - iwfsshrink gets rid of it.