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; } } }

iwmigrate is failing on TS741

tsadminuser

Hi All,

I am migrating the contents from TS65(solaris) to TS741(linux).
here are steps i followed for migration.
1)	Create a temp store ts65st.
2)	Deactivate it
3)	Copy all the contents from /local/iw-store/iw-store/default/ to /iwstore-copy/TS65bk/
4)	Change the owner to iwts and permission to 775.
5)	Activate temp store and verify all the contents from TS ui.all the contenst are visible successfully from UI.
6)	deactivate default store on new teamsite server.
7)	run iwmigrate to migrate the branch and WA.
iwmigrate -b /TS65bk/main/www-tac -o /local/iw-store/iw-store/default –w

it fails on the step 7. please find the iwmigarte console logs attached.

Find more posts tagged with

Comments

Rick Poulin

The only errors I see in your log are these:

Edition edition.06-21-14 already exists in output backing store

So.. did you run the command twice in a row? If you activate your content store right now, is all the content that you expected present?

tsadminuser

looks like its failing because branches are already present with few WA and editions. I might need to specify WA or edition to migrate?

./iwmigrate -m /iwmnt/default -b /default/main/www-tac -o /local/iw-store/iw-store/tsbkst -w -only

Rick Poulin

Maybe? I can't answer that question without knowing the context of what you're trying to do.

Does it make sense that those branches and editions would already exist in your target store?

tsadminuser

yes, those branches are already exist in my store as i did migration few months ago. Now i need to update it with final set of contents using iwmigrate.

Is this mandatory to have empty store as target in order to have iwmigate successful?

as i just tried to use empty store for target. and it worked.

I have vey large store of size 165 GB so wanted to do it in 2-3 attempts.

Rick Poulin

You can do one edition at a time if you want, but this may be a very tedious process.

If your target store has not had manual changes since your last migration, then the easiest route is to delete the branch in the target store and remigrate the whole thing. That said, you may not actually want to keep your oldest editions, if your store is that large. Again, not entirely sure what your use case is.

Adam Stoller

If you want to do incremental migration (i.e.: You did an initial migration and then you do testing on the new system while still using the old system for "real work" and want to do a subsequent migration):

Make sure to take a complete backup of the initially migrated store before you do any testing / modification to the content in any of the branches.
Do your testing, etc.
When ready to do the incremental migration:

Restore the backup of the previously migrated store
Run your migration

That's the "basics".

To make the process a bit more efficient:

Before creating a copy of the active backing store for doing a migration to a new system - make sure to create a named edition on every branch that you plan to migrate - use a good symbolic name (e.g.: "PRE_MIGRATE_1", "PRE_MIGRATE_2", etc.)
When doing subsequent migrations - use the -s flag for iwmigrate - e.g.: -s PRE_MIGRATE_1 This will allow your subsequent / incremental migration to start from the last edition that was migrated, instead of trying to replay every edition that was already migrated.

If you didn't create a good symbolic edition on each branch before you did the initial migration, you can achieve a similar result by getting the name of the last edition in the previously migrated store (iwlasted) on a branch-by-branch basis before doing the incremental migration for that branch.

Migrate the workarea(s) after the branches, separately - with the -w -only flags.

If you're going to do muliple incremental migrations - remember to create a good backup of the migrated store before you make any changes to it - because you will need to restore to it in order to do the subsequent migration.

tsadminuser

So you mean , incremental migration can be done?

empty target store is not mandatory.

when i try to migrate using iwmigrate..it stops in between as there is already few WA and editions in migrated store(target store).

Is iwmigrate -s is the cmd i should use for incremental migration?

Adam Stoller

I suggest you read the documentation, search for KB articles, and/or get someone with experience in doing backing store migrations to come in and help you - but I'd start with making sure you read and understand the documentation and KB articles.

tsadminuser

I couldnt find any incremental migration document or KB in support site. Not even from support guys (i have a case opened with hp Interwoven for this)

This process looks to be very long for me, as i have 200 + WA and 100+ editions to be migrated.

its better to delete everything(branches) from default store on my new teamsite server as its still a test server.

Create same brach structure to make an empty store

and migrate everythig in 1 go from backup store using iwmigarte.

it will migarte branches , editions and WA as well.

Correct me if i am wrong.

Adam Stoller

tsadminuser wrote:

This process looks to be very long for me, as i have 200 + WA and 100+ editions to be migrated.
[...]

Whether you do an iwmigrate from scratch or handle it incrementally - it's going to take a while to go through the process. If you had planned in advance to do it incrementally, the incremental pass(es) would be significantly quicker than starting from scratch - but having not planned for doing that, the process of trying to figure out how to determine a way to get to a state where you can do an incremental migration is probably not worth the effort, so starting from scratch makes sense.

tsadminuser wrote:

its better to delete everything(branches) from default store on my new teamsite server as its still a test server.

If you're going to start from scratch - don't delete the branches from the default store - stop TeamSite, delete the entire default store, and then restart TeamSite. When TeamSite starts up, it will create a blank default store. This is WAY faster than deleting branches to achieve the same effect.

The other alternative - although not officially supported, is to just plop the old backing store in place on the new server and skip the iwmigrate process altogether. While it may work, you lose any potential gains that might have come about by changes to the backing store code. This is by far the fastest method - just probably the least "supported" given the versions that you're talking about.

tsadminuser

Thanks a ton fish !!

Both options looks good to me..but 2nd one is fastest one as i have 165Gb store to migrate and have to wait several hours to migrate that to default store.

let me try both options in my test server and see if i can implement it in dev and then production successfully Smiley Happy

tsadminuser

Hi Fish,

Can you suggest any KB or support doc for incremental migration?

I have only 24 hour window to complete this migration and want to do it real quick.

Adam Stoller

tsadminuser wrote:
Hi Fish,

Can you suggest any KB or support doc for incremental migration?
I have only 24 hour window to complete this migration and want to do it real quick.

Off the top of my head - no. I'm pretty sure there were some, but frankly - I've done so many migrations that I know most of the information innately and only check the docs and KBs for details while I'm in the process of settng up for it.

Since I'm not involved in a migration right now (and haven't been for a while) - references are not at the tips of my fingers.