I'm building a new server to house xymon (among other items) and I need a smooth plan of action to migrate. Hobbit is at 4.2.0.
How can I maintain the historical data files and move the monitoring task from the old hobbit to the new xymon smoothly?
Frank M. Ramaekers Jr. | Systems Programmer | Information Technology | American Income Life Insurance Company | 254-761-6649 (732-6649)
This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at PrivacyAct at torchmarkcorp.com.
In a nutshell, I normally set up the same xymon UID and groups on both servers, tar the relevant directories, untar them on the new server, check I've got all files (e.g. initd/systemd files, ext script dependencies, etc), temporarily change the xymonserver IP address in the new server config and start xymon. If it works OK, I take another copy of the old server's xymon var stuff to bring the new server up to date, then change the IP address of the old server to something else, then change the IP address of the new server to the old one, change the xymonserver address in the config back and start again. If things break, you can always revert to the old server.
If the new server is using systemd and the old is on initd you'll need to sort that out separately, of course.
From: Xymon <xymon-bounces at xymon.com> on behalf of Frank M. Ramaekers <FRamaekers at ailife.com> Sent: Tuesday, July 24, 2018 6:29:07 AM To: 'Hobbit ListServ (Mailing List) (xymon at xymon.com)' Subject: [Xymon] Migrating Hobbit to xymon
I’m building a new server to house xymon (among other items) and I need a smooth plan of action to migrate. Hobbit is at 4.2.0.
How can I maintain the historical data files and move the monitoring task from the old hobbit to the new xymon smoothly?
Frank M. Ramaekers Jr. | Systems Programmer | Information Technology | American Income Life Insurance Company | 254-761-6649 (732-6649)
You'll also need to export and import the rrd files if you are moving from 32bit to 64bit.
Thanks, JT
From: Phil Crooker <Phil.Crooker at orix.com.au> To: "Frank M. Ramaekers" <FRamaekers at ailife.com>, "'Hobbit ListServ (Mailing List) (xymon at xymon.com)'" <xymon at xymon.com> Date: 24/07/2018 10:21 Subject: Re: [Xymon] Migrating Hobbit to xymon Sent by: "Xymon" <xymon-bounces at xymon.com>
In a nutshell, I normally set up the same xymon UID and groups on both servers, tar the relevant directories, untar them on the new server, check I've got all files (e.g. initd/systemd files, ext script dependencies, etc), temporarily change the xymonserver IP address in the new server config and start xymon. If it works OK, I take another copy of the old server's xymon var stuff to bring the new server up to date, then change the IP address of the old server to something else, then change the IP address of the new server to the old one, change the xymonserver address in the config back and start again. If things break, you can always revert to the old server.
If the new server is using systemd and the old is on initd you'll need to sort that out separately, of course.
From: Xymon <xymon-bounces at xymon.com> on behalf of Frank M. Ramaekers <FRamaekers at ailife.com> Sent: Tuesday, July 24, 2018 6:29:07 AM To: 'Hobbit ListServ (Mailing List) (xymon at xymon.com)' Subject: [Xymon] Migrating Hobbit to xymon
I’m building a new server to house xymon (among other items) and I need a smooth plan of action to migrate. Hobbit is at 4.2.0.
How can I maintain the historical data files and move the monitoring task from the old hobbit to the new xymon smoothly?
Frank M. Ramaekers Jr. | Systems Programmer | Information Technology | American Income Life Insurance Company | 254-761-6649 (732-6649)
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Thanks!
Frank M. Ramaekers Jr.
From: Phil Crooker [mailto:Phil.Crooker at orix.com.au] Sent: Monday, July 23, 2018 7:21 PM To: Frank M. Ramaekers; 'Hobbit ListServ (Mailing List) (xymon at xymon.com)' Subject: Re: Migrating Hobbit to xymon
In a nutshell, I normally set up the same xymon UID and groups on both servers, tar the relevant directories, untar them on the new server, check I've got all files (e.g. initd/systemd files, ext script dependencies, etc), temporarily change the xymonserver IP address in the new server config and start xymon. If it works OK, I take another copy of the old server's xymon var stuff to bring the new server up to date, then change the IP address of the old server to something else, then change the IP address of the new server to the old one, change the xymonserver address in the config back and start again. If things break, you can always revert to the old server.
If the new server is using systemd and the old is on initd you'll need to sort that out separately, of course.
From: Xymon <xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>> on behalf of Frank M. Ramaekers <FRamaekers at ailife.com<mailto:FRamaekers at ailife.com>> Sent: Tuesday, July 24, 2018 6:29:07 AM To: 'Hobbit ListServ (Mailing List) (xymon at xymon.com<mailto:xymon at xymon.com>)' Subject: [Xymon] Migrating Hobbit to xymon
I’m building a new server to house xymon (among other items) and I need a smooth plan of action to migrate. Hobbit is at 4.2.0.
How can I maintain the historical data files and move the monitoring task from the old hobbit to the new xymon smoothly?
Frank M. Ramaekers Jr. | Systems Programmer | Information Technology | American Income Life Insurance Company | 254-761-6649 (732-6649)
Please consider the environment before printing this e-mail
This message from ORIX Australia may contain confidential and/or privileged information. If you are not the intended recipient, any use, disclosure or copying of this message (or of any attachments to it) is not authorised. If you have received this message in error, please notify the sender immediately and delete the message and any attachments from your system. Please inform the sender if you do not wish to receive further communications by email.
ORIX has a Privacy Policy which outlines what kinds of personal information we collect and hold, how we may collect and handle it, and your rights regarding personal information. Please let us know if you would like a copy. The Privacy Policy and a Collection Statement are also available on our website<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.orix.com.au&d=DwMFaQ&c=laxeQK7vPmHfouIIPNyCfbQd49eK3u00U8Jdo0RFvts&r=EOaM1MkMLG24_TOy4m7EdDoX0CP9-c0YJ2kTdeagcqQ&m=4cH7kOYDuNvddp3tSu45HDaZRUIduRU0yZG9jvXb0oE&s=ClgKqDJieSivK0erHweYiVlzQNbcQsrPh0ODS4Iy9xU&e=>.
We do not accept liability for any loss or damage caused by any computer viruses or defects that may be transmitted with this message. We recommend you carry out your own checks for viruses or defects.
This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at PrivacyAct at torchmarkcorp.com.
participants (3)
-
FRamaekers＠ailife.com
-
jtrott＠dancrai.com
-
Phil.Crooker＠orix.com.au