Simple Disaster Recovery?

[bhartnett]

I have a D&R excercise comming up and wanted to run a quick check with you all on recovering. (I had a hard time finding any procedures in the LiveLink documentation.)

We have a simple installation with Livelink server & admin running on one machine, and the database & external store on a separate server.

I'm thinking that I have to restore the SQL & external store first, then run the LL 9.5 install. During the install I would point it at the existing database & store, then apply patches and re-create the index.

Is that it, or have I missed it completely?

 

[ggriffit]

I'd start with the following KC articles on moving PROD to another environment, you may have to amend/avoid some of the steps if you are restoring to a setup with the same names/config as your current one.

SQL Server (

https://knowledge.opentext.com/know...jId=3499553&objAction=ArticleView&viewType=1)

Oracle (

https://knowledge.opentext.com/know...jId=3499593&objAction=ArticleView&viewType=1)

this is also covered in the Livelink Admin training course as well as the Architecture and Security workshops, although in varying levels of detail.

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

http://www.greggriffiths.org/livelink/

 

[bhartnett]

Thanks for the link. I've had a tough time finding this type of info in the KC. This doc is listing a few things I didn't consider. (users, etc...)

I did take the Admin last October, but it really didn't address recovery, more like simple maintenance. I was interested in the Architechture course but didn't see it in Irvine yet.

Thanks again for the help. I'm going to perform a few "dry-runs" before the actual exercise, and I'll let you know how it goes.

 

[scottchate]

We ran a Livelink environment with an external store, separate Linux/Oracle database server an Windows Admin/Search server and three Windows Livelink servers in a cluster.

We found the DR exercises we did went quite smoothly using a technique of keeping a backup of the Admin and Livelink servers 'Open Text' folder wher eall the Livelink software was contained. Then when the alternate Windows servers were ready, we'd install a plain Livelink version, then replace all its 'Open Text' folder contents with the saved version. This way when we hooked up the new server to the database the database table entries listing what modules were installed already matched the contents of the 'Open Text' folder we'd updated and there wasn't as much trouble trying to go through multiple Livelink module installations to get back to the originally running configuration.