I am testing the loggernet linux version under OpenSuSE (11.3). We already have a working windows loggernet which is collecting data from
about 20 stations through modem and internet. I have made a backup of
the network map in the windows version and tried to read this back up with the linux version (through a windows remote loggernet) but if fails.
The log file gives:
"2012-03-22 13:00:57.607","","5","Network logon succeeded","","Setup Screen","192.168.15.148:49230"
"2012-03-22 13:01:03.971","","5","Network logon succeeded","","LNBackup","192.168.15.148:49231"
"2012-03-22 13:01:21.000","","126","network lock started","","LNBackup"
"2012-03-22 13:01:21.091","","83","Restore from the configuration file failed","Failed to open XML config","2","No such file or directory"
"2012-03-22 13:01:21.091","","83","Restore from the configuration file failed","Failed to open XML config","2","No such file or directory"
"2012-03-22 13:01:21.091","","83","Restore from the configuration file failed","Unable to open the DND file: /var/opt/CampbellSci/LoggerNet/sys/bin/CsiLgrNet.dnd","2","No such file or directo
ry"
"2012-03-22 13:01:21.091","","83","Restore from the configuration file failed","Unable to open the DND file: /var/opt/CampbellSci/LoggerNet/sys/bin/CsiLgrNet.dnd.backup","2","No such file or
directory"
"2012-03-22 13:01:21.092","","132","working directory snapshot restored","/media/CORSAIR/NetworkAws.bkp"
"2012-03-22 13:01:25.227","","117","client logged off","","remote disconnect"
"2012-03-22 13:01:25.227","","127","network lock stopped"
The versions are:
windows loggernet: 3.4.0.15
linux loggernet: 4.1.24
windows loggernet remote:4.1.0.16
Any idea of how to solve this problem?
The Network backup file (*.bkp) contains, among other things, paths to where the .DAT files are going to be stored as scheduled collection is performed on dataloggers. So for example, your windows .bkp file will contain paths like
"C:\Campbellsci\LoggerNet\CR1000_Table1.dat"
However, in Linux that kind of file path is invalid. The equivalent path on Linux would be
"/var/opt/Campbellsci/LoggerNet/CR1000_Table1.dat"
There could also be issues caused by restoring a 3.4 .bkp in version 4.1, but usually that works OK. So for now, I would focus on getting the file paths changed from Windows format to Linux format.
Rather than try to modify the .bkp that was created by Windows, I think a better approach would be to create a "backup script" in the corascript interpreter, and then modify the script it creates. Then that modified script could be executed on the LNLinux server to create your network map. Look at the "create-backup-script" command in the corascript help/documentation.
I recommend you contact CSI support for assistance in doing this.
Hi,
in fact this is an old thread but ...
I would save the linux configuration (shedule, path, secure2-file, etc.) for a easy restore of the linux System.
Idea:
I consider it best, that I have to reinstall the LoggerNet Linux version first and than copying the stored files and folder to the appropriate Folder of the Linux installation.
Would that work??
Question:
Which folders and files I have to put in a appropriate archive (backup).
thanks in advance
Heiko,
The easiest way to assure a complete backup is to use the snapshot feature in LoggerNet. It will ensure that a set of CONSISTENT and COMPLETE files are backed up without having to shut down LoggerNet first. The original messages on this thread had to do with transferring a backup between windows and linux which may be possible but not beneficial because of differences in paths at the very least. This holds true whether you are attempting to restore from a a snapshot file or whether you are attempting to restore the files by hand.