Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Logbook architecture and availability, posted by Frank Baptista on Fri Dec 14 15:46:14 2018 
    icon2.gif   Re: Logbook architecture and availability, posted by Stefan Ritt on Fri Dec 14 16:00:45 2018 
       icon2.gif   Re: Logbook architecture and availability, posted by Frank Baptista on Fri Dec 14 17:22:31 2018 
          icon2.gif   Re: Logbook architecture and availability, posted by Stefan Ritt on Fri Dec 14 20:05:08 2018 
             icon2.gif   Re: Logbook architecture and availability, posted by Frank Baptista on Fri Dec 14 20:52:46 2018 
                icon2.gif   Re: Logbook architecture and availability, posted by Frank Baptista on Fri Feb 1 19:20:35 2019 ELOG_Screen_Capture_-_Missing_formatting.PNGelogd.cfg
                   icon2.gif   Re: Logbook architecture and availability, posted by Frank Baptista on Fri Feb 1 21:59:46 2019 
Message ID: 68876     Entry time: Fri Dec 14 20:05:08 2018     In reply to: 68875     Reply to this: 68877
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Question  OS: Windows  ELOG Version: 3.1.2 
Subject: Re: Logbook architecture and availability 

I would call the laptops the "master" being responsible for pushing data to the central server which you can call "slave"

 

Stefan

Frank Baptista wrote:

Thanks Stephan! I guess I was making it harder than it is.  I'm still a little fuzzy -- in this instance, am I correct in saying that each laptop would be considered a "master", and the remote (network) server considered the "slave"?  Also, I'm not sure quite sure -- which server should be assigned responsibility for performing periodic synchronization between the laptop and the central elog server?

Thanks again for all you do -- Happy Holidays!

Frank

Stefan Ritt wrote:

Sure that's easy. Install elog on each laptop separately, so they run without network. Then, set up a central elog server, and use "mirroring" as explained in the documentation at https://elog.psi.ch/elog/config.html#mirroring

So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server.

Best,
Stefan

Frank Baptista wrote:

I have a setting which makes ELOG a perfect solution, but there's a situation that I'm struggling to get my head around. We have 3 separate laboratories, each one containing a number of temperature chambers, which run almost constantly over a number of shifts. Each temperature chamber has it's own logbook (laptop). So far, pretty simple.
My dilemma is, our network goes down for maintenance/updates (more often than I'd like), but our operation cannot afford to stop during network interruptions.
With that said, I thought about whether I could run a "local" logbook on each laptop/chamber, and somehow mirror the local logbook to the main ELOG server.
Perhaps I'm over-thinking this...do you have any recommendations?

 

 

 

ELOG V3.1.5-fe60aaf