Server migration
list Ricardo Stella
Running an old version on old hardware and looking to migrate this to a new VM on RHEL8. I'd also most likely use Terbithia RPMs for this I saw a couple of posts on how to move all historical data over. Question for those who've done this, how did you handle IP addresses? I thought about setting up the server with a new temp IP address and have it do all outbound tests to make sure everything works. Then change the IP when decommissioning the old one. This would allow remote tests to report back. Or would you set up as new IP and have clients report to both, then remove the old one? TIA. -- ?(((=((===???(((================================================
list Josh Luthman
How critical is it that you have every last report? Clients only report back every 10 minutes, so if you can migrate in 5-15 minutes you'll in the worst case lose one report. When I migrated to a newer OS, I just moved it all over and then changed IPs once I was done.
▸
On Mon, Apr 11, 2022 at 12:48 PM Ricardo Stella <user-a9f2fdfdbc44@xymon.invalid> wrote:
Running an old version on old hardware and looking to migrate this to a new VM on RHEL8. I'd also most likely use Terbithia RPMs for this I saw a couple of posts on how to move all historical data over. Question for those who've done this, how did you handle IP addresses? I thought about setting up the server with a new temp IP address and have it do all outbound tests to make sure everything works. Then change the IP when decommissioning the old one. This would allow remote tests to report back. Or would you set up as new IP and have clients report to both, then remove the old one? TIA. -- ?(((=((===???(((================================================
list Ricardo Stella
No problems in missing some client data. I guess I could set up the new one to make sure everything works, then move the real data and change IPs? Reason for testing is that this old box was upgraded from hobbit and even from BB. Some clients are hobbit versions using bb structure. I've set BB up eons ago, then a few admins took over. Positions cut, now it's back on my belt. TIA. On Mon, Apr 11, 2022 at 2:10 PM Josh Luthman <user-4c45a83f15cb@xymon.invalid>
▸
wrote:
How critical is it that you have every last report? Clients only report back every 10 minutes, so if you can migrate in 5-15 minutes you'll in the worst case lose one report. When I migrated to a newer OS, I just moved it all over and then changed IPs once I was done. On Mon, Apr 11, 2022 at 12:48 PM Ricardo Stella <user-a9f2fdfdbc44@xymon.invalid> wrote:Running an old version on old hardware and looking to migrate this to a new VM on RHEL8. I'd also most likely use Terbithia RPMs for this I saw a couple of posts on how to move all historical data over. Question for those who've done this, how did you handle IP addresses? I thought about setting up the server with a new temp IP address and have it do all outbound tests to make sure everything works. Then change the IP when decommissioning the old one. This would allow remote tests to report back. Or would you set up as new IP and have clients report to both, then remove the old one? TIA. -- ?(((=((===???(((================================================
-- ?(((=((===???(((================================================
list Jeremy Laidman
▸
On Tue, 12 Apr 2022 at 06:33, Ricardo Stella <user-a9f2fdfdbc44@xymon.invalid> wrote:
No problems in missing some client data. I guess I could set up the new one to make sure everything works, then move the real data and change IPs?
That's what I'd do. But I've never actually had to do an in-place upgrade.
▸
Reason for testing is that this old box was upgraded from hobbit and even from BB. Some clients are hobbit versions using bb structure. I've set BB up eons ago, then a few admins took over. Positions cut, now it's back on my belt.
BB is going back a very long way! You must have some ancient hardware. Do you have an increasingly high device failure rate? If you had all new Xymon or Hobbit clients, the safest thing would be to have them report to two servers. Then you can copy all the data across to the new server, and see how it goes. If it doesn't work quite right, and you need to tweak a few things, the data is still being updated on the old server, so you haven't lost anything. You can wipe the data from the new server and try again. However, I have a feeling that BB clients cannot be configured to report to more than one server. But it's been literally decades since I had to deal with a BB client, so you might want to check this. Or, see about updating all of your clients to Xymon clients.
▸
On Mon, Apr 11, 2022 at 2:10 PM Josh Luthman <user-4c45a83f15cb@xymon.invalid>wrote:How critical is it that you have every last report? Clients only reportback every 10 minutes, so if you can migrate in 5-15 minutes you'll in the worst case lose one report.
I'm pretty sure the clients report back every 5 minutes, by default. The original clientlaunch.cfg [client] section: [client] ENVFILE $XYMONCLIENTHOME/etc/xymonclient.cfg CMD $XYMONCLIENTHOME/bin/xymonclient.sh @CLIENTFLAGS@ LOGFILE $XYMONCLIENTLOGS/xymonclient.log INTERVAL 5m sets the INTERVAL to 5 minutes. Nevertheless, even 5 minutes is likely to be enough to run a final rsync job, to synchronise the latest updated history/rrd files. However, just be aware that you might need to do some RRD file conversion. There were some changes in the format of RRD files somewhere along the way. You might need to do an export/import process for each one. J