I also had to do the export/import of rrd files when moving from RHEL4 on an i686 to RHEL 4 on a x86_64 processor type.

--David

Andy France wrote:

ZanDAhaR wrote on 28/02/2006 06:56:12 p.m.:

...

Hey guys,

Can't seem to find anything on this but then again I haven't gone through all the results that come up on the mailing list search either.

We moved from BB server to a Hobbit server a while ago but it was on the same box so there was no issue there. We are shuffling some old hardware around and decided to give our hobbit server some more grunt and also add some other odd apps on it. We'll want to progrssively move the hosts over to the new server so the clients are cool, just update the ip in windows ones, and the ip and hostname in the nix ones

As for the server I'm assuming I can just copy the data dir over for the host I'm moving. I cannot imagine there being anything server specific in any of the status messages or graphs ?

Watch out if you are changing OS/filesystem at all. Existing RRD files will need to be exported and imported rather copied if this is the case (I had to do this for a small-ish migration from Solaris x86 to Solaris Sparc).

...

So action plan would be, shut down client on XYZ, define it in bb-hosts file on NEWHOBBIT, has it out in the OLDHOBBIT bb-hosts file, copy appropriate data folders from OLDHOBBIT to NEWHOBBIT (update ownership if need be), update ip addy and hostname in XYZ client settings, start client XYZ, be happy :)

Any flaws in this thinking or suggestions of easier way even though I cannot imagine one can you please let me know

Thanks

Allan

Andy.

#####################################################################################

This email is intended for the person to whom it is addressed only. If you are not the intended recipient, do not read, copy or use the contents in any way. The opinions expressed may not necessarily reflect those of ZESPRI Group of Companies ('ZESPRI').

While every effort has been made to verify the information contained herein, ZESPRI does not make any representations as to the accuracy of the information or to the performance of any data, information or the products mentioned herein. ZESPRI will not accept liability for any losses, damage or consequence, however, resulting directly or indirectly from the use of this e-mail/attachments. #####################################################################################

ZanDAhaR <allan at zandahar.net> wrote on 01/03/2006 03:52:41 p.m.:

David Pullman wrote:

...

I also had to do the export/import of rrd files when moving from RHEL4

...

on an i686 to RHEL 4 on a x86_64 processor type.

--David

Andy France wrote:

...

ZanDAhaR wrote on 28/02/2006 06:56:12 p.m.:

...

Hey guys,

Can't seem to find anything on this but then again I haven't gone through all the results that come up on the mailing list search either.

We moved from BB server to a Hobbit server a while ago but it was on the same box so there was no issue there. We are shuffling some old hardware around and decided to give our hobbit server some more grunt and

also

...

...

add some other odd apps on it. We'll want to progrssively move the

...

...

hosts

...

over to the new server so the clients are cool, just update the ip in windows ones, and the ip and hostname in the nix ones

As for the server I'm assuming I can just copy the data dir over for the host I'm moving. I cannot imagine there being anything server specific in any of the status messages or graphs ?

Watch out if you are changing OS/filesystem at all. Existing RRD files will need to be exported and imported rather copied if this is the case (I had to do this for a small-ish migration from Solaris x86

...

...

to Solaris Sparc).

...

So action plan would be, shut down client on XYZ, define it in bb-hosts file on NEWHOBBIT, has it out in the OLDHOBBIT bb-hosts file, copy appropriate data folders from OLDHOBBIT to NEWHOBBIT (update ownership if need be), update ip addy and hostname in XYZ client settings, start client XYZ, be happy :)

Any flaws in this thinking or suggestions of easier way even though I cannot imagine one can you please let me know

Thanks

Allan

Andy.

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

Hmm ok I hadnt thought about that as I don't understand the inner workings of RRD etc. We're moving from a Pentium Pro 200 box on Redhat 7.2 to a Dual Athlon MP System on Redhat 9 (why RH9 you ask, its the ONLY supported OS for another application thats going on there and if we

hit any problems if its not RH9 they will not help us, poverty I know)

If I do a uname -m they both say i686, uname -p one says unknown other says athlon. Should this be an issue ? Also if they are different enough

will the graphs just not work or be corrupted or not update ? Can someone please assist me in how to import/export the rrd files then as I

have never done that before. Been looking in the rrd docs but still not entirely sure what I need/want.

The proxy idea sounds good although I don't know if its going to be warranted in this case as we don't have a huge number of hosts to deal with.

Thanks for the feedback guys

Allan

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

As the systems are both Linux, are same-endian (i686). and same FS (ext3?), I can only surmise that you should be able to just copy the RRD files.

If they are not compatible then the updates will fail as rrdtool will not be able to read the existing format.

As far as actually converting them goes, I kind of did it on the fly so don't have any useful scripts to pass on :-) It's pretty easy and the RRDTOOL website does provide examples (http://rrdtool.trexle.net/doc/rrddump.en.html)

HTH, Andy. #####################################################################################

This email is intended for the person to whom it is addressed only. If you are not the intended recipient, do not read, copy or use the contents in any way. The opinions expressed may not necessarily reflect those of ZESPRI Group of Companies ('ZESPRI').

While every effort has been made to verify the information contained herein, ZESPRI does not make any representations as to the accuracy of the information or to the performance of any data, information or the products mentioned herein. ZESPRI will not accept liability for any losses, damage or consequence, however, resulting directly or indirectly from the use of this e-mail/attachments. #####################################################################################

On 2/28/06, ZanDAhaR <allan at zandahar.net> wrote:

Ok cool so basically the graphs stop updating if theyre NQR after the move, I guess thats pretty effortless to test, move a host onto the new box and come back in a day and see what happens I suppose.

I think you could find out sooner than that - just copy an rrd over to the new system and try to dump it:

 rrdtool dump datafile.rrd

If you get XML, it's probably all good. If it complains, you need to do the export at the original host and import it on the new host. I just copied an rrd over from a Sparc system to an x86 system, and rrdtool dump tells me:

*** glibc detected *** double free or corruption (out): 0x0804a170 *** Abort

whereas doing the same with a locally-created rrd I get a stream of xml. Likewise, going back to the original system I can dump the original file just fine.

Ralph Mitchell

ZanDAhaR wrote:

If I do a uname -m they both say i686, uname -p one says unknown other says athlon. Should this be an issue ? Also if they are different enough will the graphs just not work or be corrupted or not update ? Can someone please assist me in how to import/export the rrd files then as I have never done that before. Been looking in the rrd docs but still not entirely sure what I need/want.

If there is a problem, you'll know real quick if you start the new server and there are errors in your rrd-data.log. It will report an error updating every file and say something about the file having been created on another architecture.

I did an rsync of everything and did some trial runs with the new server, saw those errors, and realized I had to convert.

It was something along the lines of using rrdtool dump, which makes xml files, rsyncing them over, then doing a rrdtool restore. I did two shell scripts, one on each server, and I just did the rsync command to copy only .xml. I don't have the first script, since that box got recycled, but the second one was still around.

1. Use a script to descend into the rrd directories for each host, and do a rrdtool dump for each .rrd file. That will make an xml file for each test for each host.

2. rsync the .xml files over.

3. Use a script to descend into the dirctories and usr rrdtool restore for each xml file to make an rrd file.

(My distro of rrdtool does not include rrddump, although the man pages refer to it. But rrdtool dump apparently does the same thing.)

Here's a sample script on the receiving end. Our host names end in .gov. I did it as root, so I had to add a chown in the script.

#!/bin/sh

RRDDIR="/opt/hobbit/data/rrd"

cd $RRDDIR

for HOST in *.gov do cd $HOST

     for f in *.xml
        do
             echo $HOST
             b=`echo $f | sed 's/\.xml//'`
             `rrdtool restore $f $b.rrd`
             chown hobbit:hobbit $b.rrd
        done
     cd $RRDDIR

done

--David