LSF9 Disaster Recovery - iSeries

Sort:
You are not authorized to post a reply.
Author
Messages
StephenV
Basic Member
Posts: 20
Basic Member

    Hello!

    Has anyone executed a disaster recovery test with Lawson V9?  I am currently in the process of documenting what we will need to do when we restore Lawson on our hot site box.  Some things I'm concerned about: 

    1. In 7.2 we did a POSTNEW72 to update user space.  I can't find a similar command in 9.0.0.3. Does anyone know if this needs to be done in v9?

    2.  Do I need to be concerned about or refresh the LDAP bind?

    3. Does anyone know of any concerns regarding restoring Websphere? Do the applications restore, or do the .ear files need to be redeployed? 

    Any comments are welcome.  Lawson's support site does not have much in the way of documentation for disaster recovery.

    Thanks!

    Stephen

    Brian Dusheck
    New Member
    Posts: 2
    New Member
      Stephen - 

      We are in the process of setting up a Disaster Recovery environment on system i for Lawson 0.

      I see you posted this over a year ago, but I was wondering if you were able to successfully do this.  I am getting pretty close, but if you are open to exchanging ideas, I would appreciate it.  I can be reached via email at bdusheck@centrastate.com or via posting to this chain.
      peter@ur.com
      New Member
      Posts: 1
      New Member

        Were implementing an HA enviornment with lawson 901 on the 'i'.... using mimix to do the replication ......

        I can tell you that I have moved the entire websphere ND directory structure from one system to another multiple time without issue.

        We backed up /QIBM/Userdata/websphere/appserver/V61/ND and restored directly to another machine.... no problem.

        If the sytsm names are different, websphere will complain,... but this can be resollved with a 'change hostname' process performed on websphere.... i googles for that one......

         

        Hope that helps a least a little.

         

        P.

        You are not authorized to post a reply.