This RRD was created on other architecture

I use Munin for some graphing of system and application stats. Like most graphing open source projects its based on the widely used RRDTool.

I recently was moving my munin instance from a xen instance on 64bit Ubuntu install, to a bare metal 32bit install. Moving munin consists of the moving the munin.conf file and moving the /var/lib/munin directory. After moving it I noticed graphs weren’t updating as expected and came across this is the munin-update.log:

This RRD was created on other architecture

Not surprising that RRD files are platform specific. Came across this blog post that has a couple of shell scripts to handle this. Since the blog post is in German I will summarize what they do:

1. dump.sh:

This does a find in your /var/lib/munin directory looking for all “.rrd” files. It takes each file and uses the rrdtool “dump” option to dump the information into a corresponding xml file.

2. restore.sh

This takes the xml data and creates a new rrd file from the xml file. Before creating the new rrd file from the xml file it copies the original rrd file to backup file with an extension of “.bak”.

When I did this I copied the munin directory to a 64bit host to run dump.sh since the rrd files were originally created on 64bit host. I then copied the directory back over to the 32bit machine to run the restore.

You can find the scripts on Frank Helmschrott’s blog posting. I will include a slightly modified version here:

dump.sh:

#!/bin/bash
MUNIN_DIR="/var/lib/munin"

for f in `find ${MUNIN_DIR} -name '*.rrd' -print` ;

do
f_xml=`dirname ${f}`/`basename ${f} .rrd`.xml
rrdtool dump "$f" > "${f_xml}"
chown root:0 "${f_xml}"
done

restore.sh:

#!/bin/bash
MUNIN_DIR="/home/kenc/munin"

for f in `find ${MUNIN_DIR} -name '*.xml' -print` ;
do
f_rrd=`dirname ${f}`/`basename ${f} .xml`.rrd
mv -f "${f_rrd}" "${f_rrd}.bak"
chown root:0 "${f_rrd}.bak"
rrdtool restore "$f" "${f_rrd}"
chown munin:munin "${f_rrd}"
done