Migrate content store from Windows to linux

I have been tasked with migrating an exiting windows content store to a fresh Linux installation. I have read through the clt guide and iwmigrate seems relevant to windows to windows or linux to linux migrations.

Any advise/pointers on how to proceed would be appreciated.

My environment is

Current OS: Windows 2003 SP2
Teamsite version: 6.7.2(currently without sitepublisher)

New OS: Linux 4
TeamSite Version: 6.7.2

Find more posts tagged with

Comments

nipper

You cannot move a store from Windows to Linux.

You need to manually migrate branches instead. It is not easy. If you need history, it gets quite difficult. If you do not have editions, then it is pretty much impossible to get history.

windy

You cannot move a store from Windows to Linux.

You need to manually migrate branches instead. It is not easy. If you need history, it gets quite difficult. If you do not have editions, then it is pretty much impossible to get history.

Thanks Nipper. When you say manually migrate branches; how can this be accomplished. I can create editions to keep this history. Thanks again.

nipper

Thanks Nipper. When you say manually migrate branches; how can this be accomplished. I can create editions to keep this history. Thanks again.

No you cannot create editions to get the history. The needed to be done when the events happened not after the fact.

You can use OpenDeploy to copy one branch to another location, set it up to copy extended attributes.

mart2001

How about from linux <-> solaris??

They use different file formats....

nipper

How about from linux <-> solaris??

They use different file formats....

I have not tried that, so I do not know. I do knot DOS->Linux won't work

Adam Stoller

How about from linux <-> solaris??

They use different file formats....

Theoretically, migrating between linux and solaris should be do-able using iwmigrate. It might even be possible through copying the entire store - though I haven't personally dealt with either scenario - so take the information with the proverbial grain of salt.

The entire model of ownership, permissions / access rights are so distinctly different between Windows and any flavor of Unix that performing such a migration via a utility [correctly in all cases] is impossible - so you're left with doing N "surface" copies between the two servers and figuring out how to preserve what you want to preserve yourself.

Consider the following:

Unless the answer to the first question is "just the last version" - you're in for a fair amount of coding and testing, each time you answer "yes" to the other questions, you're adding that much more complexity and thus that much more effort to design, implement, and test / debug your solution.It all can be done - it's just a matter of how much time and expertise you're providing for getting it done. As a guess - I'd say the above options range from about 1 day to 6 months of dedicated effort depending on what you need to do and depending on the skills of the person attempting to do it (based on the skill-level indicated by some of the posts I've seen on DevNet in recent months - you could easily double or triple the amount of time needed)

windy

so you're left with doing N "surface" copies between the two servers and figuring out how to preserve what you want to preserve yourself.

I appreciate the advice Ghotti. At this point I would just keep the latest version since I am migrating a dev environment and I pretty much have free rein regarding how I get this done. By N surface copies, do you mean physically copying the files from windows to Linux or am I getting the wrong end of the stick?

Adam Stoller

I appreciate the advice Ghotti. At this point I would just keep the latest version since I am migrating a dev environment and I pretty much have free rein regarding how I get this done. By N surface copies, do you mean physically copying the files from windows to Linux or am I getting the wrong end of the stick?

If it's just the latest version - don't worry about 'N' - just do a surface copy from source to target.
This could be done using OD, or creating a zip file (winzip, pkzip, etc.) and copying and then expanding it on the other side, etc.

I'm not sure if EA transfer with OD works between disparate OS's (I think it should, but I don't know if it does) - if not, and you have files that need EAs transferred, you'll have to do that yourself (there are various scripts floating around to do this, but it's not that difficult to roll your own and at least that way you know what you've done)

You'll have to repeat the process you create for each branch you want to "migrate" - and of course you'll have to create all the target branches and workareas beforehand, or write an entire process that records all that information on the source side and can be played back to create them on the target side.

So - yes - you need to physically copy the files from point-A to point-B and any desired EAs as well.

windy

Thanks Ghoti - muchos gracias

windy

This could be done using OD.....

Quick question regarding using OD to transfer the files; can one deploy files between 2 OD base servers?

ISCBorisB

Quick question regarding using OD to transfer the files; can one deploy files between 2 OD base servers?

Yes, absolutely. Any OD Base can operate as a receiver - with the same security settings, etc

windy

Yes, absolutely

Ok - thanks ISCBorisB. This will be a first for me :-).

windy

This is a follow-on question regarding this issue.

I am attempting to migrate a windows Teamsite server content to to a linux Teamsite server.

My deployment configuration file is as follows....

[html]

[/html]

When I run this deployment, I get the error message

LIB: 2010-01-18 20:00:25 Receiver-ERROR: ERROR: [/default/main/PF] is not an allowed deployment path.

Thanks in advance for your help(or insults) :-)

nipper

What do you think it means ? Hint: you are probably right.

How much have you worked with OpenDeploy ? A quicker perusal of the OpenDeploy Admin manual would be in order, this is quite easy.

windy

What do you think it means ? Hint: you are probably right.

How much have you worked with OpenDeploy ? A quicker perusal of the OpenDeploy Admin manual would be in order, this is quite easy.

Thanks.

I have specified the targetFilesystem areas as "/.iwmnt/default/main/PF" and /.iwmnt/default/main", and /iwmnt/default/main/PF", and /iwmnt/default/main" , but still getting the same error. It may be something obvious, but I don't see it. Thank for your help.

nipper

And the error says /default/main

Adam Stoller

And the error says /default/main

Not to mention that you (windy) seem to be assuming that you (again, windy) can deploy branches as if they were normal directories - which won't work on the target-side either.