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 usage query

itsamb

Hi,

I have a very basic query, but not able to understand completely from document.

I am migrating from TS 6.7 on W2003 to TS 7.4 on W2012. One of my friend has suggested to migrate the store as following way.

1. Copy the store from old server (6.7).

2. The default store location on new server (7.4) is C:\iw-store after installation

3. Copy the old store on new server (7.4) at location C:\oldStore\iw-store

4. Run iwmigrate command to migrate content from C:\oldStore\iw-store to C:\iw-store on new server

Is this really doable? From what I get in documents and examples, I need to provide Vpath of the source branch. Here, the source for me is the copy of the old content store C:\oldStore\iw-store.

What is the ideal way to migrate the store?

Thanks,

Amit

Find more posts tagged with

Comments

Adam Stoller

There are a number of ways you can do this - the method you outlined is certainly one of them.

There are also a number of caveats for the different methods that depend on what you're migrating, e.g.:

Are you migrating SitePublisher / LiveSite components & templates?
Are you migrating WFM workflows or just WFTs?
etc.

In terms of vpaths - based on the methodology you posted - you need to mount the temporary second store (C:\oldStore\iw-store) using either iwstoreadm or (my preference in this case) by adding the appropriate directives to the iw.cfg file.

You could search the forums for the terms "iwmigrate" and "iw.cfg" - which will provide a number of hits. Not sure how well the links work here, but two of the hits that should help are:

The titles of the thread are not 100% matches, but there is content within each/either of those threads that does apply to what you are trying to do.

Dan_Rivizzigno

Amit,

First, fish is correct in everything that he posted and you should search the KBs just so you understand what's involved.

However, unless you have some store corruption issues in the 6.7 store OR the store was originally created in 6.5 or earlier and you have NEVER run iwmigrate, it's not really necessary to run it again.

Also, you really don't need to migrate the entire store, worklfows and all. Migrating the workflow store almost always results in errors. You really only need to copy /iw-store/default and /iw-store/iwadmin to the new server and any other content stores that you may have created.

Alternatively, if you're trying to merge the 6.7 default store into the 7.4 default store, that's going to get tricky really fast. You may want to open a support case to find out if it's doable in your environment.

Dan

Adam Stoller

danrivizzig wrote:
[...]. You really only need to copy /iw-store/default and /iw-store/iwadmin to the new server and any other content stores that you may have created.
Alternatively, if you're trying to merge the 6.7 default store into the 7.4 default store, that's going to get tricky really fast. You may want to open a support case to find out if it's doable in your environment.
Dan

One solution for the above is to move the 7.4.x default store aside (e.g.: rename it to 74_default), move your 6.x default store into place as "default", mount the old store using iwstoreadm -a 74_default) and then use iwmigrate to migrate the "/741_default/main/component-guide" branch into the [what was the 6.x] default store (just in case you are, or are planning to use SP/LS in the future.

The primary reason for using iwmigrate on the 6.x store into the 7.4x store is to ensure that the backing store is "completely" in 7.4x format - if you just copy the store into place it will be "upgraded-in-place" which, though usually sufficient, does not guarantee that the resulting store takes full advantage of any upgrades in the backing store code. That being said, I don't believe there's been much upgrading of the backing store code for a while, so it's reasonably safe to avoid [most of the] iwmigrate process.

Note: If you run iwmigrate, remember to run both iwfsck afterwards to make sure the backing store is "clean", and then run iwfsshrink to remove redundant data - which iwmigrate tends to create.

itsamb

Thank you Adam and Dan for your input.

Adam, I followed the threads you referred. Steps I did is as below.

1. Copy the old store to new server (7.4) at location

C:/oldStore/iw-store-Backup-18Jun2014/iw-store (It is plain cntl + c and contl + v)

2. Edit the iw.cfg with following entry.

store_directory_old = C:\oldStore\iw-store-Backup-18Jun2014\iw-store\default
store_comment_old= backup temporarily

3. Execute following commands -

iwreset -ui

iwstoreadm -a old

Now, I able to see the store "old" mounted on Teamsite server.

But, there is nothing under the main branch. I am unable to see all the sub branches under main.

The iwstoreadm command seems to be creating a fresh store named "old", but not referring to the location which I have mentioned in iw.cfg.

Anything I missed here? Appreciate your input.

Thanks,

Amit

Adam Stoller

Without seeing the system, it's a bit difficult to tell - but from what you described, it sounds like the changes you made to iw.cfg were not processed and the iwstoreadm command created a new 'old' store within the configured iw-store location.

Since you're on Windows, it is unlikely that you modified the incorrect iw.cfg file (a common mistake on Unix implementations being the modification of IWHOME/etc/iw.cfg rather than /etc/iw.cfg; on Windows there is only IWHOME/etc/iw.cfg, so that's the right place to do things)

What does the output of iwstoreadm -l (lower-case L) show?

Are you sure you put the iw.cfg entries into the proper location (within the [iwserver] block)?

Have you tried restarting the iwserver process (rather than just doing an iwreset -ui)?

(note: You should probably do an iwstoreadm -d old and manually remove c:\iw-store\old [or wherever 'old' got created] before restarting the iwserver process)

itsamb

Adam,

I edited correct file IW-HOME/etc/iw.cfg. System is TS 7.4.1 on windows 2012.

The entry added in iw.cfg is as below.

[iwserver]

store_directory_old = C:\oldStore\iw-store-Backup-18Jun2014\iw-store\default
store_comment_old= backup temporarily

I again followed the steps you mentioned above, but result is same. Please find attachement for output.

Thanks,

Amit

Dan_Rivizzigno

Amit,

It's reading this setting:

store_comment_old= backup temporarily

But it's not reading this one:

store_directory_old = C:\oldStore\iw-store-Backup-18Jun2014\iw-store\default

You have an extra space after 'old' right before the equals sign. Remove it so it looks like this:

store_directory_old=C:\oldStore\iw-store-Backup-18Jun2014\iw-store\default

Run iwstoreadm -d old.

Run iwreset to read the new config.

Run iwstoreadm -a old.

Let us know what happens.

Dan

itsamb

Dan,

Good catch. You were right. Now, all the contents are available through UI. Thank you.

Another thing that I tried and it also worked.

1. Copy the contents under old default store to C:\iw-store\oldCopy on 7.4

2. Run iwstoreadm -a oldCopy

It did not require any entry in iw.cfg. It worked and all the branches, contents available under oldCopy store also.

Thanks,

Amit

itsamb

Now, I am facing issue with iwmigrate. I successfully mounted old store. Then,

1. iwstoreadm -d default (This is default 7.4 store)

2. iwmigrate.exe -m Y:\old -o C:\iw-store\default -b /old/main -d -g > migration_log.txt 2>&1

It failed with attached log. Is there any error in the syntax of the command ?

Thanks,

Amit

Dan_Rivizzigno

Amit,

The error is this:

Unable to set user to adminstrator for server session

There is a quirk in the tool that's probably related to legacy code in the tool. It's looking for a user account on the server that's named Administrator. You've likely renamed the administrator account for security reasons. You can either rename it back to Administrator or just create a temporary account on the server named Administrator that you can delete later on.

Dan

itsamb

You are correct Dan. The local admin account is renamed on our server. So I created a user 'Administrator', added to the administrator groups. Then ran the same coomand. This time it said

Error(err=925), AddPermissionEntry failed for /default/main. Continuing.

Attached is the detail log. Any pointers...

Thanks,

Amit

Dan_Rivizzigno

Did you check the copied store when you brought it up to see if the users and groups are listed properly? You might have to run iwidmap to remap invalid users or groups on the store. It's trying to set permissions or roles on the migrated store and is probably running into an invalid user. If it's still running, let it run. But note that you'll likely have to reset permissions or run iwidmap on the default store after it's done.

Dan

itsamb

Dan,

We had run the iwidmap on the copied store. But, what I could see is that, there are some entries in idmapusers.xml as below.

It looks like some users were created and then deleted on the older server. I will remove these entries, rerun the iwidmap and then iwmigrate. Will let you know the output. Thanks again.

Thanks,

Amit

itsamb

Still faced same issue. Then I gave full rights on the souce and target store to Administrator account.

Ran following command -

iwmigrate -g -b /old/main/ -o /iw-store/default -d

It showed success, but created only temp_workarea, no content.

Then tried below

iwmigrate -g -b /old/main/branchName -o /iw-store/default -d

Finally, it ran and migrating the content. It is still running. Will update if any issue.

Hopefully this helps others who stuck in the same boat. Smiley Happy

Dan_Rivizzigno

Amit,

It didn't migrate anything because you used the -d switch, which tells iwmigrate not to recursively migrate sub-branches. You only migrated the main branch. Also, you're not migrating the workareas either because you didn't use -w, so you will only have the temp_workarea created. Once you're done with this initial migration, you can migrate the workareas like this in a second run:

iwmigrate -g -b /old/main/branchName -o /iw-store/default -d -w only

Again, note that with -d, ONLY the branchName branch will be migrated.

Dan

Adam Stoller

In addition to @danrivizzig's response - if you have a sizeable branch structure (like more than 3 or 4 with a year or more's worth of history) - you are generally better off migrating one branch at a time, and then doing iwfsshrink's in between every 2 or 3 migrations - because the iwmigrate process creates lots of "redundant data" that bloats the target backing store. Or, at the very least, keep a watch on your available disk space before running each branch's migration.