| Subject: |
RE: Export old Zenoss to new Zenoss |
| Author: |
Jane Curry |
| Posted: |
2017-10-26 05:20 |
I am guessing that this is a Zenoss 4.x, given that you are running Centos 6.5??
Actually, before you build a new system, if it is the root file system that is running out of space, presumably you have everything in that root file system?? Zenoss will normally install in /opt/zenoss or, on older systems, in /usr/local/zenoss; have you considered using operating system techniques to backup everything and then create a new filesystem, /opt/zenoss, and then restoring? Zenoss will use virtually nothing directly under the / filesystem.
If you do decide to build a new box, then with a Zenoss 4.x system, you should be able to do a zenbackup, making sure that you get all the right flags to get everything, so something like:
$ZENHOME/bin/zenbackup --temp-dir=/fred/jctemp --mibs --libexec -v 10
Depending on your existing version of Zenoss affects the flags slightly - the --mibs and --libexec were relatively new additions in the life of 4.x. Older versions you also needed --save-mysql-access to backup the parameters with which to access MySQL in the new environment.
Beware that zenbackup creates the backup in its temporary workspace directory - /tmp by default, but you can control that with the --temp-dir flag. It then copies the backup to the destination; $ZENHOME/backups with a unique filename that it creates, by default; but you could use the --file parameter to specify an absolute path to a specific file anywhere you like.
You then build your new environment - I would stick with the same Operating System version probably, obviously with bigger disks, then install Zenoss - the same version you currently have. Copy your backup file over and then use zenrestore.
Bit since I used it but used to be a tried and tested method for building a "backup" box.
Cheers,
Jane
------------------------------
Jane Curry
Skills 1st United Kingdom
jane.curry@skills-1st.co.uk
------------------------------
| Subject: |
RE: Export old Zenoss to new Zenoss |
| Author: |
Ted Mottinger |
| Posted: |
2017-10-27 12:08 |
Thanks Jane, I have setup a new Zenoss server and now have most, if not all, of my original devices setup. I thought it would be a good learning experience. I have everything up and running except I'm getting several devices with errors, "C
onnection was refused by other side: 111: Connection refused.". I have a full attachment. What do I need to do to correct this? Doesn't seem to be much on the interweb about this as pertains to Zenoss. Thanks.------------------------------
Ted Mottinger
Network Engineer
Guy M Turner Inc.
Greensboro NC
3368099233
------------------------------
Attachments:
| Subject: |
RE: Export old Zenoss to new Zenoss |
| Author: |
Jane Curry |
| Posted: |
2017-10-30 06:19 |
Hi Ted,
Your screenshot shows a device in the /Discovered device class - is that really what you want? By default, stuff in /Discovered will have both SNMP modeler plugins and COMMAND-based modeler plugins assigned to it - so you are trying to talk to the device using both SNMP and ssh.
The error message is almost certainly coming from a failed ssh request - probably because you haven't setup a zCommandUser and CommandPassword that match the target device - indeed you may not WANT to access this device using ssh?
Your best bet would be to decide what this device really is and then move it out of the /Discovered class into something more appropriate. You will then need to remodel the device (off the Action icon at the bottom of the left-hand menu).
Cheers,
Jane
------------------------------
Jane Curry
Skills 1st United Kingdom
jane.curry@skills-1st.co.uk
------------------------------
