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 on mounted drives

Amit_LnT

Hi,
I know content stores can be migrated with iwmigrate. But I would like to know does this command work fine on mounted drives of external machines with NFS on unix? And same with mapped drives on windows ?

ENV: TS 6.5 SP2 on windows server 2003

Thanks in advance.... Smiley Happy

Find more posts tagged with

Comments

Adam Stoller

Hi,
I know content stores can be migrated with iwmigrate. But I would like to know does this command work fine on mounted drives of external machines with NFS on unix? And same with mapped drives on windows ?

ENV: TS 6.5 SP2 on windows server 2003

Thanks in advance....
AB

As long as you mount the drive on your server it should work just fine.

GroupedListChart.rptdesign

Amit_LnT

I was thinking the same, but had never done before. Thanks a lot for confirmation.

Amit_LnT

ok this is second query I have. As mentioned in the support article "it is not possible to migrate the content store from linux to windows".
My concern is if we mapped a unix folder on windows with NFS client, will it work the same way for iwmigrate?
Or is there any way to run the 'iwmigrate' in cross platform ?

Thanks,
AB

Adam Stoller

ok this is second query I have. As mentioned in the support article "it is not possible to migrate the content store from linux to windows".
My concern is if we mapped a unix folder on windows with NFS client, will it work the same way for iwmigrate?
Or is there any way to run the 'iwmigrate' in cross platform ?

Thanks,
AB

Interwoven does not support migrating the contents of the backing store between significantly different OS's (windows <-> unix).

They do, I believe, support migrating the contents of the backing store between flavors of a given OS - e.g.: W2K <-> W2K3, Solaris <-> Linux, etc.

The only way to migrate content in the backing store between significantly different OS's is to write a script that retrieves all the files via the file system interface from editions and/or staging and/or workareas and copies those files (along with their extended attributes) to a workarea on the target server, whereupon the files then need to get submitted - usually losing all historical comments and date information (it's possible to bring over that information too if you're willing to spend the time to do so, but ...)

The recent versions of OpenDeploy can be used to help facilitate this cross-OS migration by enabling the feature for transferring extended attributes as part of the deployment. If you're looking to preserve the comments and historical date information though, you'll probably want to avoid use OD for this and manage the extraction and transferring yourself on a file-by-file basis utilizing tools like iwattrib, iwrlog, etc. to retrieve the historical information.

Antharix

We adopted similar stratagy as Fish suggested and were successful though It involved a lot of manual intervensions.