<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
If i try and experiment on the same box (making sure everything is backed up)<BR>
Is the upgrade process an in-place upgrade?<BR>
<BR>
During the the ./configure do i specifiy the current install directory or a new directory?<BR>
<BR>
<BR>
If i do it on a test vm <BR> where am i copying the files to and will i need to manually change everything or do i run the upgrade script. <BR>
<BR>
I'm not following the upgrade procedure.<BR>
<BR>
Nick<BR>
<BR>
> To: willowbrookmagic@hotmail.com<BR>> Subject: RE: [Xymon] Xymon 4.3.2 released<BR>> Date: Thu, 7 Apr 2011 13:33:37 +0200<BR>> From: henrik@hswn.dk<BR>> CC: xymon@xymon.com<BR>> <BR>> Hi Nick,<BR>> <BR>> On Tue, 5 Apr 2011 13:22:21 -0400, Nick Camaldi<BR>> <willowbrookmagic@hotmail.com> wrote:<BR>> [...]<BR>> > I inherited the Xymon Server from a former employee, who was using 4.3.0<BR>> > beta2<BR>> > he had the installation in /opt/admin/xymon/linux/4.3.0-beta2/<BR>> > The questions i have is this, I want to make sure i don't mess this up<BR>> <BR>> please post this question to the mailing list - there are a lot more<BR>> people there who can help with this. I've taken the liberty of cc'ing the<BR>> mailing list here.<BR>> <BR>> My quick answer would be:<BR>> <BR>> 0) Use a test system - Virtualbox and VMware Player are free, and let you<BR>> setup a dedicated system for testing the new Xymon version without having<BR>> to install new hardware.<BR>> 1) Install the new Xymon version into a new directory. Dont bother with<BR>> how the old directory layout was - create a setup that you believe is<BR>> right.<BR>> 2) Copy the configuration files over from the old setup. You can see in<BR>> the docs/Renaming-430.txt directory what the mapping is between the old and<BR>> the new files. There shouldn't be any config files other than those in the<BR>> ~hobbit/server/etc/ directory, and perhaps some extensions in<BR>> ~hobbit/server/ext/<BR>> 3) Change a couple of the clients on the servers you monitor so they send<BR>> data to both the old system and the new test system. Just to make sure that<BR>> client handling works OK.<BR>> 4) When you're confident that the new setup works, shutdown the old Hobbit<BR>> installation, copy the setup from your virtual server over to the<BR>> production system, and everything should work.<BR>> <BR>> <BR>> Regards,<BR>> Henrik<BR>> <BR> </body>
</html>