Just stop the server. Move your elog directory to the new server (including elogd.cfg, logbook directories, ...). Then check that the elogd.cfg needs modifications, like the URL which might have changed, then start the new server. V2.9.2 did have an old data format, which *should* be converted automatically. But first try it out before deleting the old server.
| Lesley Herren wrote: |
|
We are installing a new data center which will be based on Windows 2012 servers. Our current center is on Windows 2008 and will be decommissioned this year - 2008 servers (because of the security issue) will not be allowed in the new data center. So game plan is to install latest ELOG (3.1.2) on the 2012 server at the new data center and move the logs over from the 2008 server. I've looked through entries and do not see anything about moving the logs over from one system to another. In this case there are 2 concerns:
1. Has anyone moved the log entries from one system over to another?
2. Since we are also looking at updating version of ELOG - are there conversion steps necessary for the log entries or will v3.1.2 be able to use the log files from v2.9.2 as is?
Thank you, Lesley
|
|