We received a requirement from a leading paint manufacturer in New Zealand to implement a mobile Infor M3 Server stack, which would allow the customer to move the server stack from one computer network to another. We needed to configure the M3 environment in an architecture where the IP address and the subnets could be changed at the customer’s request. The customer automate the copy of the server images to a disaster recovery location at regular intervals. The idea behind this architecture was to minimize the time in setting up the environment in case of a disaster.
Figure 1: Disaster Recovery Server Migration
In a typical disaster recovery situation, the server IP addresses would change. To avoid this, we configured Infor M3 Standard Components and its satellite products to communicate with the DNS names. After implementing this server architecture, we tested it by simulating a server disaster recovery situation by changing the IP addresses and mapping the new IP addresses to the existing DNS names of the server stack. The test proved that after simulating the disaster scenario, the M3 Environment was up and running as expected.
Figure 2: After DNS configuration you will notice both internal and external Addresses have changed
The new method of implementing the architecture was very beneficial to the customer in two ways. Firstly, the new disaster recovery set up was implemented without requiring the client to invest on additional expensive disaster recovery solutions as the solution was built on top of existing infrastructure. Secondly, the new solution prevented the customer from having to reimplementing Infor M3 after a disaster situation.
Technical Consultant – Project Delivery