Recovery of LSF9 Application/Web servers

 1 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
JY
Advanced Member
Posts: 26
Advanced Member
    What is the best practice for Lawson LSF9 regarding production server recovery?
    As part of a disaster recovery plan, I would see the re-implementation of the Lawson application from scrathc as a last resort, in case all else fails.
    What do other Lawson Administrator's do in planning for the eventuality of restoring the Lawson application in case of server failure? I'm not referring to the database portion as that is fairly straight forward. I'm mainly interested in what others do with WebSphere, ADAM, and the LSF9 business logic.
    Jimmy Chiu
    Veteran Member
    Posts: 641
    Veteran Member
      Since Lawson officially announced support for virtualization, I have been developing a mirror server set in virtualized environment.

      Advantages
      With Lawson in virtualization environment, you can utilize VM snapshot etc on hourly basis with virtually no impact on performance.
      Hardware failure is covered by failover/Vmotion feature etc which are built into most virtualization platform. In the event of hardware failure, the failover/vmotion are almost instant.
      64bit lawson can take advantage of using "stand-alone" deployment scheme (Thus, 1-VM covers the portal/app/ldap).

      Without VM, I would use Acronis or similiar imaging software and schedule the backup according to your business need/acceptable rollback timeframe. This does not cover hardware failure, in that case, you probably need an additional server with same hardware configuration to restore the image into.