Congratulations in moving into production with Zenoss. I'm happy
you're confident enough in it to use it in production. :)
As for moving the data...
First start by going to your trunk version and running $ZENHOME/bin/
zenbackup.py. You can pass --help to it to get additional
information about the arguments and options you can pass. By default
without any arguments zenbackup.py will place a .tar.gz into $ZENHOME/
backups. Since you're going to end up removing $ZENHOME we should
put that backup someplace else:
$ cd $ZENHOME/bin
$ ./zenbackup.py --file=/someplace/safe/zenbackup-trunk.tar.gz
That backup contains:
- Your performance data (rrd data in the $ZENHOME/perf directory)
- Your model information (the data in ZODB, including MIBs)
- Your event data (the data in MySQL)
Once you do that make a backup of $ZENHOME. I'd do something like this:
# shut down zenoss
$ cd $ZENHOME/bin
$ ./zenoss stop
# make sure everything is down, kill -9 it if it is not
$ ps auxww | grep zenoss
# go one directory above ZENHOME
$ cd `dirname $ZENHOME`
# make a tarball for extra-safe keeping
$ tar cjf /someplace/safe/zenoss-trunk.tar.bz2 zenoss
# copy zenoss to a safe place for extra-extra-safe keeping
$ mv zenoss /someplace/safe/zenoss-trunk
# cross your fingers
$ rm -rf $ZENHOME
Then download the latest version of zenoss and install it however you
are comfortable. I recommend the RPM if you're on a RPM based box
since upgrades are literally "rpm -U zenoss-newversion.rpm".
After you install you can use zenrestore.py against the tarball
zenbackup created. It will copy your rrdfiles, events database, and
model information. You can do it like this:
$ cd $ZENHOME/bin
$ ./zenrestore --file=/someplace/safe/zenbackup-trunk.tar.gz
Make sure you read this:
The only thing I think could trip you up is if you're new on the
trunk and have had to run zenmigrate since the last release. Lotsa
lotsa stuff has changed, and if you're pretty regularly "svn up"'ing
and running zenmigrate then your ZODB will not be compatible with the
1.1.0 version you're going to install. The same is true with the
events database. But far less has changed there.
Good luck!
-c
On Mar 28, 2007, at 3:19 PM, cfriedline wrote:
Apologies for the cross-post, but my previous email to the list
does not show in the forum.
Does anyone have steps from moving from trunk to source without
losing any data? I assume it's not as simple as installing using
the tarball over the existing installation.
I'm looking to move Zenoss into production and want to leave the
trunk to provide some control over our install.
Thanks.
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=4942#4942
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
