Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Migrating Livelink9.7 from Solaris to Windows environment

Status
Not open for further replies.

vimal27

Programmer
Jul 9, 2007
3
US
We are currently checking the feasibilty of migrating our Livelink 9.7 servers ( front end webservers and admin servers)from Sun-Solaris10 to Windows 2003 servers. Please let me know if there is any documentation available for performing the same. I checked in the Opentext knowledge center and couldn't find any information there. Do we need to rebuild the index as part of such a migration?
 
If you are moving the storage for you index, then I would certainly rebuild it, generally with a move that complex I would recommend that you rebuild it.

As for the rest of the system, you should be fine just to connect the Windows servers to your database and update their config and it should be fine as the information is stored in the DB.

You would also need to review all the modules you have and ensure that they will run on Windows properly.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006
 
Thanks Greg.

I will check with our Infrastructure team to see whether they can make the existing EFS SAN accessible on the new Windows servers. It will help to migrate without reindexing. If they reccommend moving the storage to a new disk, then i will end up reindexing the entire EFS ( 6TB) which is time consuming.



 
to cut out on time in your solaris environment you could backup the partitions and when you re- create the windows one after all search processes and re-indexinh has started you can restore those saved indexes.Not usre if a solaris index backup would work in a windows livelink search restore test that if possible

also in unix the files are usually like /usr/....

in windows they are \\unc\mystore\000\123\2345\5678

not sure if providerdata table which holds that info would complain or not I would test accessing a old document that existed in the solaris file store to rule that out.
Why does org shift from solaris to windows ?

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010
 
Thanks appnair for your valuable suggestions. I am defenitely planning to test this in a dev environment before trying it on prod to uncover all these issues. I am almost sure that i have to update couple of entries in the KINI table to update the '/' with '\'. It seems like provider table stores the path information always with a '/'.

The organization is expecting to reduce the cost required for Server (Sun solaris) licencing and hardware by moving to Windows. I checked with OT regarding Linux, and they are not supporting LL9.7\9.7.1 on Linux. CS10 is supported on Linux, but there are couple of open issues which are not yet resolved ( as per opentext release notes).
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top