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

Moving a branch and subbranches to a new server

wmh

The environment is TS 5.5.2 on two seperate Solaris servers. A Dev and a Prod box.

We are getting ready to migrate to a new server a Large branch with many subbranches, each having multiple WA's and Editions.

From the reading it appears the best way to do this is to create a new iwstore of that branch with iwmigrate, then move the new iwstore to the new server. Then use iwmigrate again to incorporate the branch into the existing iwstore on the other server.

Is this the best way? Any suggestions or tips to offer?

Thank,
Marty

Find more posts tagged with

Comments

james1

Well, I suppose you could deactivate the store, copy it to the 2nd server, activate it there, and then delete any branches you don't want. Not sure if that will save you any time or not -- I guess it depends on how many branches you want to keep (i.e., migrate) vs. how many you want to delete.

-- James

--
James H Koh
Interwoven Engineering

wmh

There is an existing iwstore on the 2nd server. Are you saying copy the iwstore to the 2nd server as a second store, delete the branches, then use iwmigrate?

james1

Sorry, I misunderstood you, I didn't realize that you needed to integrate these branches into a non-empty store.

You should probably disregard my previous post.

-- James

--
James H Koh
Interwoven Engineering

gwen1

Do you need to maintain history of the branches you are migrating to the new server? If not you may be better off recreating branches on new server copying content, applying extended attributes, etc.

iwmigrate needs for the backingstore you are reading from to be active and one you are writing to not activated. Sounds like on your new server you would be wanting to add this to the default backingstore. There is not a way to deactivate the default store. If you are not trying to migrate to the default store on the second server would not be a problem. Also, branches should not already exist in the new store for this to work properly.

This is the only workaround for migrating to default we came up with, but decided against in our situation. ... use iwmigrate on first server... copy that store to second server, firststore. stop teamsite on second server. as root or with sudo mv default directory to new name, newdefault, outside of iw-store. mv firstore to become default directory. start teamsite. migrate content from default to the newdefault backingstore. after migration stop teamsite, mv newdefault back to default, and restart.