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: 68873     Entry time: Fri Dec 14 15:46:14 2018     Reply to this: 68874
Icon: Question  Author: Frank Baptista  Author Email: caffeinejazz@gmail.com 
Category: Question  OS: Windows  ELOG Version: 3.1.2 
Subject: Logbook architecture and availability 

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-2eba886