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

Branch migration issue.

kissthedevil

Hi Guys,

I'm trying to migrate a branch from Store A (CB) to Store B (default) on the same TS environment.

Env Details:
TS 6.7.2 SP2
RHEL 5 (Unix)

I carried the following steps for the same.

1. sudo /Interwoven/TeamSite/bin/iwstoreadm -d default
Result:
iwmount: Unmounting /lcms-ts/iwmnt/default...
Store default is deactivated

2. sudo /Interwoven/TeamSite/bin/iwmigrate -x -x -x -b /lcms-ts/iwmnt/CB/main/CodeBranch/ -o /lcms-ts/iw-store/default/ -f -t 5

Result:
[Wed Jun 16 01:10:25 2010] Shut down store 0x64 at "/lcms-ts/iw-store/default" (next id = 0x212200).
[Wed Jun 16 01:10:25 2010] Shutdown of backing store environment complete.
[Wed Jun 16 01:10:25 2010] Backing store environment is shut down
[Wed Jun 16 01:10:25 2010] iwmigrate failed
[Wed Jun 16 01:10:25 2010] iwmigrate can be restarted by running
[Wed Jun 16 01:10:25 2010] "iwmigrate -o /lcms-ts/iw-store/default//"

3. sudo /Interwoven/TeamSite/bin/iwmigrate -o /lcms-ts/iw-store/default//

Result:
[Wed Jun 16 01:10:25 2010] Shut down store 0x64 at "/lcms-ts/iw-store/default" (next id = 0x212200).
[Wed Jun 16 01:10:25 2010] Shutdown of backing store environment complete.
[Wed Jun 16 01:10:25 2010] Backing store environment is shut down
[Wed Jun 16 01:10:25 2010] iwmigrate failed
[Wed Jun 16 01:10:25 2010] iwmigrate can be restarted by running
[Wed Jun 16 01:10:25 2010] "iwmigrate -o /lcms-ts/iw-store/default//"

4. sudo /Interwoven/TeamSite/bin/iwstoreadm -a default
Result:
mkdir: `/lcms-ts/iwmnt/default': Stale NFS file handle
chmod: cannot access `/lcms-ts/iwmnt/default': Stale NFS file handle
df: `/lcms-ts/iwmnt/default': Stale NFS file handle
iwmount: Mounting /lcms-ts/iwmnt/default...
iwmount: Mounted /lcms-ts/iwmnt/default.
Store default is activated.Every time I execute the iwmigrate command its failing. I'm not sure why this is happening. Could anyone help me on the same and point out whats going wrong?

Find more posts tagged with

Comments

Adam Stoller

Hi Guys,

I'm trying to migrate a branch from Store A (CB) to Store B (default) on the same TS environment.

...
2. sudo /Interwoven/TeamSite/bin/iwmigrate -x -x -x -b /lcms-ts/iwmnt/CB/main/CodeBranch/ -o /lcms-ts/iw-store/default/ -f -t 5

The argument for -b should be a vpath not a file system path - try:

sudo /Interwoven/TeamSite/bin/iwmigrate -g -b /CB/main/CodeBranch -o /lcms-ts/iw-store/default -d

Is it safe to assume that your backing store is on a separate server (NAS/SAN)? If so - you will probably have to reboot your TeamSite server to fix the "Stale NFS file handle" issue.

kissthedevil

The argument for -b should be a vpath not a file system path - try:
sudo /Interwoven/TeamSite/bin/iwmigrate -g -b /CB/main/CodeBranch -o /lcms-ts/iw-store/default -d

Thanks for the reply. I got the above thing but the problem is now everytime I execute the above command for this specific branch it gives me the below result. And I'm not aware of the command toget rid of this thing and start over again.

iwmigrate: 6.7.2 Build 70082 Interwoven
***************************************************************
***************************************************************
Before running this command, please ensure that:

1) You have obtained the latest version of iwmigrate from
support.interwoven.com.
***************************************************************
***************************************************************
Command line: /Interwoven/TeamSite/bin/iwmigrate -g -b /CB/main/CodeBranch -o /lcms-ts/iw-store/default -d
[Thu Jun 17 01:47:01 2010] iwmigrate has detected that the last run was aborted.
[Thu Jun 17 01:47:01 2010] Please issue the following command "iwmigrate -o /lcms-ts/iw-store/default" to restart

Also correct me if I'm wrong, the path "/CB/main/CodeBranch" and "/lcms-ts/iwmnt/CB/main/CodeBranch" would be the same as the first one will be a symbolic link in Unix which will point to the iwmnt location.

I recommend using the
-g
flag to get rid of the annoying prompt to start after you've issued the command (it's not really documented, but it was intended for use with a graphical user interface)

This is good one. Will keep a note of this one.

I recommend using the
-d
flag to avoid recursing through sub-branches as part of the migration process. I prefer to handle each branch separately as it's easier to figure out where things succeed / fail, etc.

I want to migrate the branch along with the sub-branches. However, will try this option too to see whether it works.

I have never used the
-f
or
-t
flags so I can't really comment on those

-f is to do a full clone of all every edition in the branch. -t is for the timeout.

I don't recall the use of the
-x
flag to be significantly helpful, but I've done this kind of thing a fair number of times

Yep, you're right. The -x option isn't that significant. Just used it to see if anything comes up.

I
Is it safe to assume that your backing store is on a separate server (NAS/SAN)? If so - you will probably have to reboot your TeamSite server to fix the "Stale NFS file handle" issue.

Yes you're right. The backing store is on the NAS. And, I'm aware of this resolution. Thanks for the resolution anyways. This my main concern at this point of time as it gets mounted/unmounted even after giving the errors.

Adam Stoller

Thanks for the reply. I got the above thing but the problem is now everytime I execute the above command for this specific branch it gives me the below result. And I'm not aware of the command toget rid of this thing and start over again.

There is a file that lives within the backing store. I can't remember if it's the source or target store - so you'll have to check both - but basically you're looking for something like either:

preserve history - and thus I've never tried using it.Good luck

nipper

Thanks for the reply. I got the above thing but the problem is now everytime I execute the above command for this specific branch it gives me the below result. And I'm not aware of the command toget rid of this thing and start over again.

iwmigrate: 6.7.2 Build 70082 Interwoven
***************************************************************
***************************************************************
Before running this command, please ensure that:

1) You have obtained the latest version of iwmigrate from
support.interwoven.com.
***************************************************************
***************************************************************
Command line: /Interwoven/TeamSite/bin/iwmigrate -g -b /CB/main/CodeBranch -o /lcms-ts/iw-store/default -d
[Thu Jun 17 01:47:01 2010] iwmigrate has detected that the last run was aborted.
[Thu Jun 17 01:47:01 2010] Please issue the following command "iwmigrate -o /lcms-ts/iw-store/default" to restart

Once you start, you have to finish the migration or clean up first.

You can remove everything in the destination store and then remove the IWMIGRATE.RUNNING file (or something like that) from the original store.

The default is to continue the migration from the point it stopped. Which is fine if you were low on disk and added disk or a scenario like that. But for a migrate that never really started, you need to clean up and try again.

kissthedevil

There is a file that lives within the backing store. I can't remember if it's the source or target store - so you'll have to check both - but basically you're looking for something like either:
/lcms-ts/iw-store/default/iwmigrate.restart
/lcms-ts/iw-store/CB/iwmigrate.restart
Find and remove that file - then try running the iwmigrate command again.Assuming is a dangerous thing sometimes - if the command is expecting a vpath - give it a vpath, not a file system path.I can't say I fully understand the documentation on this part, but it clearly says that '-f' does not preserve history - and thus I've never tried using it.

Good luck

The file that I removed was on the target /lcms-ts/iw-store/default/iwmigrate.restart.

I tried using the -f option but didn't work for some reason. Tried the option with -d worked well. Thanks for the help

kissthedevil

Once you start, you have to finish the migration or clean up first.

You can remove everything in the destination store and then remove the IWMIGRATE.RUNNING file (or something like that) from the original store.

The default is to continue the migration from the point it stopped. Which is fine if you were low on disk and added disk or a scenario like that. But for a migrate that never really started, you need to clean up and try again.

The problem was that the migration just failed without copying any content. i was able to see that in the log and hence restarted the migration.

The bigger problem was every time I continued the migration from the last time it failed. And the same error Please issue the following command "iwmigrate -o /lcms-ts/iw-store/default" to restart followed there on. It was kinda into an infinite loop. Finally happy that the command provided by GHOTI worked... Smiley Happy