Redundancy Problems

[BryanD]

I am trying to implement redundancy on two computers using Lookout v6.0.2.  One computer (primary) has an unlimited development license, and the other (secondary) has a unlimited runtime license.  The computers also have client licenses installed on both.  The server process is loaded on both machines using the same name.  When I developed the client process I used a full pathname for everything versus Symbolic Link, because I have a large amount of discrete controls (pushbuttons, etc.) connected to field devices that I wanted both computers to access. 

The client and server processes work fine during normal operation with no problem. 

I have created a process called "redundancy" on the client machine per the developer's manual.  This process is setup to load the server process in the event of a failure on the primary, but it doesn't work.  My state file is being updated from machine to machine properly, but the server process never loads on the client machine.

I have tried to check for syntax or other errors in the loader and monitor blocks and everything looks OK.  I have tried shutting down the process only, Lookout, and powering down the primary computer with no success.

Any suggestions would be appreciated.

[Ryan.S]

You can test Monitor and Loader objects separately.

On client machine, create a Monitor object to monitor the primary server process, then stop the server process and see if monitor goes high.

On client machine, create a Loader object and connect a swtich to "load", then you will see if it successfully loads the process when switch goes high.

I mean you first need to find out whether monitor or loader has the problem.

[BryanD]

Thanks for the help.  My resume will never include typing.  I had an error on both the loader and monitor blocks.  Redundancy is working properly now.

[reandy]

Has anyone had any success with having the process files (*.l4p) on a shared volume? (and using redundency using the Loader and Monitor objects)

I tryed this and it did not work...

Create a test process, and name it Master. Save Master on a network drive/folder.

Create a test process, and name it Monitor. Save Monitor on a network drive/folder. (yes, the loader is pointed to the Master file on the shared network drive/folder, and yes, i can open/run Master by clicking File/Open on this computer).

Run Master on one computer

Run Monitor on another computer

Shut down Master

Observations: Monitor notices that Master is not running any more, but Loader doesn't do anything, and no alarm is generated.

Make these changes:

copy process file Master to the local c:\program files\national instruments\lookout 6.1\

change the loader to run the Master file from the local hard drive.

Try experiment again.

Everything works as expected

any ideas? Can anyone duplicate this issue?

thanks

Rich

[Ryan.S]

The monitor is fine. The problem is in the loader.

You need to map the remote folder to the local driver. For example, I put process1.l4p to \\aaa\bbb, which is on a remote computer, and then I map the network drive which creates a local drive, such as Z:\, and map this drive to the network folder. I am able to load the process1.l4p file through the Z:\.
The point is that the process file parameter of loader should not be like \\xxx\xx

[reandy]

Awesome Ryan!!

I made a mapped drive to my network place (I was using \\xxx\xx\) and now it is working just as advertised!!

Thanks again, and clicking the Kudos button

richA