Disaster Recovery Plan

We are being asked to come up with a disaster recovery plan for our Lawson HR/Payroll system and curious as to what others are doing. Thank you

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

Happy 2017! We have a decent, reliable and tested failover/DR plan in place here at Children's. Of course, yours will depend much on your platform/software but here's our basics, in case that's of any help to you:

- 3 Key AIX Servers: LSF, Landmark and Database (Oracle)

- All 3 of the above are each equipped with a failover box of equal capacity.

- All 3 of the above are equipped with a disaster recovery boxes of equal capacity at a different physical location.

- We're using IBM AIX HA technology for when a failover or DR has to take place.

- In the case of a down and need to move from PROD, option #1 is to move to failover environment; option #2 is to move to the DR environment.

- I've built, what I've called, "master scripts" for LSF and Landmark that bring up everything in the correct order on both LSF and Landmark (of course, it checks to be sure the database is up first and LSF comes up first followed by Landmark.)

- We've tested the failover and DR both manually and when forced to (network hardware issue - OUCH!) and found that things have gone down and come up fine, with just a bit of tweaking.

- As for our Windows apps, e.g. LBI, MSCM, Punchout, these are all on Windows VMware boxes that are, allegedly, also set for failover/DR but these *have not* been tested yet.

- Oh, and one warning: Be sure you have provisions in place to be sure everything is down in one place (PROD) before everything comes up in another place(DR/Failover). We learned the hard way, while doing some testing (glad it was then) that Lawson absolutely doesn't like having two sets of things running in two different same-named places (lase, ladb, etc). Yuk!

Let me know if you have questions,

Lenny

unknown

Two comments: 1) We have start/stop scripts that do the same as your "master scripts". They are very helpful for CTP and ESP installation! 2) Test your Windows apps. Murphy's Law will apply, that which is not tested is bound to fail.

Our own DR is tied to our AWS hosting. The start/stop scripts are critical to recover from service interruptions.

todd-brown

Lenny, are you using Tivoli Directory Server in your current Lawson envs?

Lawson user experience 10.1.0 Presentation Open Discussion and Dem.mp4

unknown

Ah yes, TDS!! Way to bring back repressed memories!

Yes, we do use TDS and, for DR/Failover purposes, it's very picky about hostname, specifically a configuration file called db2nodes.cfg (in the sqllib directory of tds). In my master script, the tds start/stop checks this file for the current hostname and then, if they don't match, copies an appropriate file into place. Hope this isn't TMI.

Lenny

todd-brown

Yes we have struggled with that piece of the failover. So your saying all I have to do is modify that db2nodes.cfg file? Also when you failover does your root vg fail over as well? If not, like I am assuming, then do you just do TDS install on both servers?

Copyright © 2025 Infor. All rights reserved.