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 6.5 SP2 store from W2K to Windows 2003

System

Hello all,
I have a little project of moving our TeamSite Backend store to a new Windows 2003 server. I have seen quite a few articles and posts about migration tools and processes. However their seems to be a bit of conflict in the best practices in making this work correctly. I am ready to test this process. Can someone please recommend some best practices? Here is what I aleady have in place to make sure this work:

1. A copy of the prod backend store (6.5 SP2) taken after a iwfreeze
2. A VMWare windows 2003 server with TeamSite 6.5 SP2 installed.
3. All the same local user and groups created on the new Windows 2003 server.

What should be the next steps? Keep in mind I want to keep extended attributes in place. Is it an iwidmap or like utility? I really appreciate your help.

Find more posts tagged with

Comments

Adam Stoller

Hello all,
I have a little project of moving our TeamSite Backend store to a new Windows 2003 server. I have seen quite a few articles and posts about migration tools and processes. However their seems to be a bit of conflict in the best practices in making this work correctly. I am ready to test this process. Can someone please recommend some best practices? Here is what I aleady have in place to make sure this work:

1. A copy of the prod backend store (6.5 SP2) taken after a iwfreeze
2. A VMWare windows 2003 server with TeamSite 6.5 SP2 installed.
3. All the same local user and groups created on the new Windows 2003 server.

What should be the next steps? Keep in mind I want to keep extended attributes in place. Is it an iwidmap or like utility? I really appreciate your help.

There appear to be [at least] two schools of thought here:

(there are others too - so you should probably do your own search).

Migrateduser

That looks like pretty good advice. I have been reading the the iwidmap documents. Its the iwmigrate posts that have been throwing me off. I actually spoke with a TeamSite rep yesterday and he didn't mention iwmigrate at all. He said that iwidmap should be all that is needed.

Adam Stoller

That looks like pretty good advice. I have been reading the the iwidmap documents. Its the iwmigrate posts that have been throwing me off. I actually spoke with a TeamSite rep yesterday and he didn't mention iwmigrate at all. He said that iwidmap should be all that is needed.

I don't think iwmigrate is necessary - and neither did Interwoven, at least for some period of time - however your mileage may vary if you do a whole-cloth copy of the backing store (in this case, you're staying with the same product version so the argument about proper upgrading of the backing store probably doesn't apply). That being the case - iwidmap and iwstoreadm are probably all you need to read up on.