migrate server
list Eric Jacobs
Our current Xymon server is running on a vmware vm. The powers-that-be want it to run on a physical machine. Unfortunately there is no V2P converter. So I've set up a new Linux box. Looking for the best way to migrate from old server to new one -- Eric Jacobs Thomas Publishing Company Infrastructure and operations Information Technology Group Phone: XXX-XXX-XXXX Email: user-2ad24e73f3d4@xymon.invalid
list Larry Barber
I recently moved to a new server. The way I did it was to install the newest Xymon release on the new server. Set up a Xymon proxy on the old server so it can feed both the old and new servers. Make sure the new installation is running right. Then use scp to move over all of the data directory. Turn off your old machine. If you have any proxies running anywhere you will have to point them to the new server after you have switched over, before you shutdown the old server. Same with any network tests you are running from your main server. That's about it, it went really smoothly for me. If you are running any network tests from your main server, be sure the firewalls are set up for the new server. Thanks, Larry Barber On Tue, Nov 13, 2012 at 10:56 AM, Eric Jacobs
▸
<user-2ad24e73f3d4@xymon.invalid>wrote:
Our current Xymon server is running on a vmware vm. The powers-that-be want it to run on a physical machine. Unfortunately there is no V2P converter. So I've set up a new Linux box. Looking for the best way to migrate from old server to new one -- Eric Jacobs Thomas Publishing Company Infrastructure and operations Information Technology Group Phone: XXX-XXX-XXXX Email: user-2ad24e73f3d4@xymon.invalid
list Ryan Novosielski
I did this recently but also changed the hostname and upgraded from 4.2.3 to 4.3.10 at the same time and had trouble with the graphs. Any obvious gotchas to look out for there?
▸
From: Larry Barber [mailto:user-6ef9c2864140@xymon.invalid]
Sent: Tuesday, November 13, 2012 07:21 PM
To: Eric Jacobs <user-2ad24e73f3d4@xymon.invalid>
Cc: xymon at xymon.com <xymon at xymon.com>
Subject: Re: [Xymon] migrate server
I recently moved to a new server. The way I did it was to install the newest Xymon release on the new server. Set up a Xymon proxy on the old server so it can feed both the old and new servers. Make sure the new installation is running right. Then use scp to move over all of the data directory. Turn off your old machine. If you have any proxies running anywhere you will have to point them to the new server after you have switched over, before you shutdown the old server. Same with any network tests you are running from your main server. That's about it, it went really smoothly for me. If you are running any network tests from your main server, be sure the firewalls are set up for the new server.
Thanks,
Larry Barber
On Tue, Nov 13, 2012 at 10:56 AM, Eric Jacobs <user-2ad24e73f3d4@xymon.invalid<mailto:user-2ad24e73f3d4@xymon.invalid>> wrote:
Our current Xymon server is running on a vmware vm. The powers-that-be want it to run on a physical machine. Unfortunately there is no V2P converter. So I've set up a new Linux box. Looking for the best way to migrate from old server to new one
--
Eric Jacobs
Thomas Publishing Company
Infrastructure and operations
Information Technology Group
Phone: XXX-XXX-XXXX<tel:XXX-XXX-XXXX>
Email: user-2ad24e73f3d4@xymon.invalid<mailto:user-2ad24e73f3d4@xymon.invalid>
list Larry Barber
I didn't have any trouble moving the graphs, and I made a similar leap in versions, but I stuck with the 32 bit architecture and didn't have any problems. I did have problems with my DR/Backup server, which is 64 bit, but recompiling and reinstalling rrd and Xymon fixed them. I didn't try to move the rrd files onto this machine. Since its my backup its getting all the same data that my main server is so its building its own graphs, if a true DR situation arose we could live without the graphs.
▸
Thanks,
Larry Barber
On Tue, Nov 13, 2012 at 9:04 PM, Novosielski, Ryan <user-ae4522577e16@xymon.invalid>wrote:
I did this recently but also changed the hostname and upgraded from 4.2.3 to 4.3.10 at the same time and had trouble with the graphs. Any obvious gotchas to look out for there? *From*: Larry Barber [mailto:user-6ef9c2864140@xymon.invalid] *Sent*: Tuesday, November 13, 2012 07:21 PM *To*: Eric Jacobs <user-2ad24e73f3d4@xymon.invalid> *Cc*: xymon at xymon.com <xymon at xymon.com> *Subject*: Re: [Xymon] migrate server I recently moved to a new server. The way I did it was to install the newest Xymon release on the new server. Set up a Xymon proxy on the old server so it can feed both the old and new servers. Make sure the new installation is running right. Then use scp to move over all of the data directory. Turn off your old machine. If you have any proxies running anywhere you will have to point them to the new server after you have switched over, before you shutdown the old server. Same with any network tests you are running from your main server. That's about it, it went really smoothly for me. If you are running any network tests from your main server, be sure the firewalls are set up for the new server. Thanks, Larry Barber On Tue, Nov 13, 2012 at 10:56 AM, Eric Jacobs < user-2ad24e73f3d4@xymon.invalid> wrote:Our current Xymon server is running on a vmware vm. The powers-that-be want it to run on a physical machine. Unfortunately there is no V2P converter. So I've set up a new Linux box. Looking for the best way to migrate from old server to new one -- Eric Jacobs Thomas Publishing Company Infrastructure and operations Information Technology Group Phone: XXX-XXX-XXXX Email: user-2ad24e73f3d4@xymon.invalid
list Henrik Størner
▸
On 14-11-2012 04:04, Novosielski, Ryan wrote:
I did this recently but also changed the hostname and upgraded from 4.2.3 to 4.3.10 at the same time and had trouble with the graphs. Any obvious gotchas to look out for there?
RRD-files are architecture-specific in format, so if you go from e.g. a 32-bit system to 64-bit you will need to convert all of your rrd-files. If your Xymon server changes IP, then you'll need to reconfigure all of the clients reporting to the server. Plus any firewall changes that might incur. Other that that, doing a new install on the new server and then copying all of the data- and configuration-files across should work fine. Regards, Henrik
list Peter Kache
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 14.11.2012 07:59, schrieb Henrik Størner:
▸
On 14-11-2012 04:04, Novosielski, Ryan wrote:I did this recently but also changed the hostname and upgraded from 4.2.3 to 4.3.10 at the same time and had trouble with the graphs. Any obvious gotchas to look out for there?RRD-files are architecture-specific in format, so if you go from e.g. a 32-bit system to 64-bit you will need to convert all of your rrd-files. If your Xymon server changes IP, then you'll need to reconfigure all of the clients reporting to the server. Plus any firewall changes that might incur. Other that that, doing a new install on the new server and then copying all of the data- and configuration-files across should work fine. Regards, Henrik
we just migrated from Hobbit 4.2.0 running on Debian Lenny to Xymon
4.3.10 on a new machine with Debian Squeeze and had to dump and
restore a lot of rrd databases since there is also a Cacti
installation on the same server.
There was one gotcha that took us some time: the language variables on
the two machines were set to different values and our restored rrds
got mangled with wrong min/max values. To avoid this you can simply
set the LANG Variable when dumping and restoring. We used the
following commands:
on the old machine:
cd /var/lib/hobbit/rrd && for i in `find ./ -type f -name "*.rrd"`;do
LANG=C rrdtool dump "$i" "$i.xml";done
transfer the xml files to the new machine
on the new machine:
cd /var/lib/xymon/rrd && for i in `find ./ -type f -name "*.rrd.xml"`;
do LANG=C rrdtool restore "$i" ${i%.xml};done
Regards,
Peter
- --
- ------
Besuchen Sie uns auf unseren nächsten Veranstaltungen:
- - European SharePoint Conference, 04. - 07.02.2013 Kopenhagen, Stand X
- ------
Dr. Peter Kache
Systemintegration
getit GmbH
Emil-Figge-Straße 76-80
44227 Dortmund
Tel: +XX.XXX.XXXX.XXX
Fax: +XX.XXX.XXXX.XXX
http://www.getit.de
Amtsgericht Dortmund, HRB-Nr. 13836
Geschäftsführung:
Dr. Thomas Krämerkämper (Vorsitzender)
Christoph Hecker
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJQo03HAAoJEIcsA0knPrMkHbIIAI1bAPAiOg+ZebI2EUZUzWD+
3UIK0RAbqdMClE7bhA9UyD3iSZAXHLcd6CpzUNBMYyuWYhC0vPE1Y9nyeX01CQ7i
NpaetRQEfS7P8LQRZ6Xr9ogqW9YxWVQKPHu4XD7aac3cllwQW9JXHmiGZchziphD
jCSvr7RAF0K2QXgy/BuOkVWSoOAO2V62i5QUz6d878XbLkYKBbPYHL1CcUFwE+uF
ZGC9ZJJ++xOJd+02BmSO+uuMrU69/DFs7KbQKAwt5+ChN2us3slNAD8HkXpUYzJo
+YIGs386atgKak5DKqls9wH+3XMyJVmpA/cyJbGooHqVQhOrB+tkK/CBu5+cyA8=
=UU8k
-----END PGP SIGNATURE-----
list Betsy Schwartz
Something must be in the air - we moved servers too, physical to virtual I just rsync'ed everything over from the old server to the new, stopped, did a final rsync and then moved the name and IP to a secondary interface on the new box. Then I cloned it and set up an rsync to the clone - if the primary dies we can just move the IP to the new box and we should be good to go. The "reconfigure client" thing bit me a couple times - xymon hardcodes the host IP into the binaries. I cloned a dev server and it fired up and started happily sending data to the primary before I rebuilt xymon. Oh and since our xymon server is on the vmware cluster - I also have another xymon server sitting on a physical box, doing nothing but watching bbd on the primary. It's job is to alert us if the primary xymon server goes down. I did manage to take down the primary a few weeks ago, by loading it up with some server-side scripts that were failing to return. I'm trying to get away from running server-side scripts on the primary now.
list Ryan Novosielski
▸
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/14/2012 01:59 AM, Henrik Størner wrote:
On 14-11-2012 04:04, Novosielski, Ryan wrote:I did this recently but also changed the hostname and upgraded from 4.2.3 to 4.3.10 at the same time and had trouble with the graphs. Any obvious gotchas to look out for there?RRD-files are architecture-specific in format, so if you go from e.g. a 32-bit system to 64-bit you will need to convert all of your rrd-files. If your Xymon server changes IP, then you'll need to reconfigure all of the clients reporting to the server. Plus any firewall changes that might incur. Other that that, doing a new install on the new server and then copying all of the data- and configuration-files across should work fine.
Well, I shall endeavor to try this again by the end of the week and see if I can nail anything down. Knowing it should work is something. I'm migrating from Solaris 9 to Solaris 10 at the same time, but not sure if that should make any difference. I suppose there could be an RRDTool version difference at the same time or something? I'd assume both of them are 64-bit, as both Solaris definitely are. - -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCjuO0ACgkQmb+gadEcsb7H9wCfcUxj9YjQhuqRgHyMJoPBFwVH E9cAnAmNfA0aBxu6Fct2ZQF4v0fNMbNG =OoCG -----END PGP SIGNATURE-----
list Ryan Novosielski
▸
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/14/2012 06:58 AM, Betsy Schwartz wrote:
The "reconfigure client" thing bit me a couple times - xymon hardcodes the host IP into the binaries. I cloned a dev server and it fired up and started happily sending data to the primary before I rebuilt xymon.
I have never experienced a problem with this. Which "host IP" is included in the binaries, and in which package? I reuse the same compile of client packages for all machines of the same architecture, just doing a make install.
▸
- --
- ---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlC/f0QACgkQmb+gadEcsb7sdgCfXMW51IY+HpJjcKoyptpgBhYN aiEAoMMEdVWsdQlOFgqS7rZrzF4IjWTq =DfTi -----END PGP SIGNATURE-----
list Betsy Schwartz
▸
On Wed, Dec 5, 2012 at 12:07 PM, Novosielski, Ryan <user-ae4522577e16@xymon.invalid> wrote:
The "reconfigure client" thing bit me a couple times - xymon hardcodes the host IP into the binaries. I cloned a dev server and it fired up and started happily sending data to the primary before I rebuilt xymon.I have never experienced a problem with this. Which "host IP" is included in the binaries, and in which package? I reuse the same compile of client packages for all machines of the same architecture, just doing a make install.
I was being sloppy, I apologize. Not the client, only the xymon server