We just purchased an upgraded server in which to host Observium on and I would like to know the “best” way to migrate over all of our monitored devices. I’m not concerned with any of the graphed data being migrated, or any of the old Observium config. I only want to do a mass export of all of the devices and their properties. Will a dump of the ‘devices’ and ‘devices_locations’ tables suffice? Are there other tables/directories/configs I need to be concerned about?
Thanks,
Josh Williams
Bureau of Technology Management
WI Department of Corrections
Copy the entire database, along with the rrd directory and config.php.
It's pretty easy, only possible complexity is adding the mysql username and password back!
You /will/ break your installation if you try to copy individual tables. I don't know why anyone would even want to mess around like that. You could truncate super large (GB+) tables before the mysql dump if you think it'll take too long.
adam. On 2018-02-28 17:41:23, Josh Williams joshwilliams3737@gmail.com wrote: We just purchased an upgraded server in which to host Observium on and I would like to know the “best” way to migrate over all of our monitored devices. I’m not concerned with any of the graphed data being migrated, or any of the old Observium config. I only want to do a mass export of all of the devices and their properties. Will a dump of the ‘devices’ and ‘devices_locations’ tables suffice? Are there other tables/directories/configs I need to be concerned about? Thanks, Josh Williams Bureau of Technology Management WI Department of Corrections
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
I'm not worried about size of the tables, we just only want the devices and their custom location/geoloaction/ect settings brought over. We also don't want to bring over the config.php file as the original (server) has many of the lines manually changed rather than relying on the web interface to apply the custimaztions. The thought being that the new server installation will be easier to others on the team to work with if mostly managed over the web gui...
I suppose the simplest way to explain what i'm trying to accomplish is that we want a new server stood like we don't have an existing one, but I don't want to take the time to add all of the devices in again.
I've made the new servers' Database name and root username and password the same as the old one in hopes to ease the migration some.
I'm sure i'm butchering my explanation of this so for that I'm sorry.
PS. For what it's worth Adam we (Wisconsin DOC) love your product. Just wanted to throw that in there :)
-Josh
On Wed, Feb 28, 2018 at 12:14 PM, Adam Armstrong adama@observium.org wrote:
Copy the entire database, along with the rrd directory and config.php.
It's pretty easy, only possible complexity is adding the mysql username and password back!
You /will/ break your installation if you try to copy individual tables. I don't know why anyone would even want to mess around like that. You could truncate super large (GB+) tables before the mysql dump if you think it'll take too long.
adam.
On 2018-02-28 17:41:23, Josh Williams joshwilliams3737@gmail.com wrote:
We just purchased an upgraded server in which to host Observium on and I would like to know the “best” way to migrate over all of our monitored devices. I’m not concerned with any of the graphed data being migrated, or any of the old Observium config. I only want to do a mass export of all of the devices and their properties. Will a dump of the ‘devices’ and ‘devices_locations’ tables suffice? Are there other tables/directories/configs I need to be concerned about?
Thanks,
Josh Williams
Bureau of Technology Management
WI Department of Corrections
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/ cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Id recommend copying the database and rrds and then make a new config.php.
Then go through the config.php and add the relevant bits to the database.
Adam.
Sent from BlueMail
On 28 Feb 2018, 19:41, at 19:41, Josh Williams joshwilliams3737@gmail.com wrote:
I'm not worried about size of the tables, we just only want the devices and their custom location/geoloaction/ect settings brought over. We also don't want to bring over the config.php file as the original (server) has many of the lines manually changed rather than relying on the web interface to apply the custimaztions. The thought being that the new server installation will be easier to others on the team to work with if mostly managed over the web gui...
I suppose the simplest way to explain what i'm trying to accomplish is that we want a new server stood like we don't have an existing one, but I don't want to take the time to add all of the devices in again.
I've made the new servers' Database name and root username and password the same as the old one in hopes to ease the migration some.
I'm sure i'm butchering my explanation of this so for that I'm sorry.
PS. For what it's worth Adam we (Wisconsin DOC) love your product. Just wanted to throw that in there :)
-Josh
On Wed, Feb 28, 2018 at 12:14 PM, Adam Armstrong adama@observium.org wrote:
Copy the entire database, along with the rrd directory and
config.php.
It's pretty easy, only possible complexity is adding the mysql
username
and password back!
You /will/ break your installation if you try to copy individual
tables. I
don't know why anyone would even want to mess around like that. You
could
truncate super large (GB+) tables before the mysql dump if you think
it'll
take too long.
adam.
On 2018-02-28 17:41:23, Josh Williams joshwilliams3737@gmail.com
wrote:
We just purchased an upgraded server in which to host Observium on
and I
would like to know the “best” way to migrate over all of our
monitored
devices. I’m not concerned with any of the graphed data being
migrated, or
any of the old Observium config. I only want to do a mass export of
all
of the devices and their properties. Will a dump of the ‘devices’ and ‘devices_locations’ tables suffice? Are there other tables/directories/configs I need to be concerned about?
Thanks,
Josh Williams
Bureau of Technology Management
WI Department of Corrections
_______________________________________________ observium mailing
list
observium@observium.org http://postman.memetic.org/ cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Ok, sounds good.
Thanks for your help with this.
Cheers,
Josh
On Wed, Feb 28, 2018 at 1:42 PM, Adam Armstrong adama@memetic.org wrote:
Id recommend copying the database and rrds and then make a new config.php.
Then go through the config.php and add the relevant bits to the database.
Adam.
Sent from BlueMail http://www.bluemail.me/r?b=12200 On 28 Feb 2018, at 19:41, Josh Williams joshwilliams3737@gmail.com wrote:
I'm not worried about size of the tables, we just only want the devices and their custom location/geoloaction/ect settings brought over. We also don't want to bring over the config.php file as the original (server) has many of the lines manually changed rather than relying on the web interface to apply the custimaztions. The thought being that the new server installation will be easier to others on the team to work with if mostly managed over the web gui...
I suppose the simplest way to explain what i'm trying to accomplish is that we want a new server stood like we don't have an existing one, but I don't want to take the time to add all of the devices in again.
I've made the new servers' Database name and root username and password the same as the old one in hopes to ease the migration some.
I'm sure i'm butchering my explanation of this so for that I'm sorry.
PS. For what it's worth Adam we (Wisconsin DOC) love your product. Just wanted to throw that in there :)
-Josh
On Wed, Feb 28, 2018 at 12:14 PM, Adam Armstrong adama@observium.org wrote:
Copy the entire database, along with the rrd directory and config.php.
It's pretty easy, only possible complexity is adding the mysql username and password back!
You /will/ break your installation if you try to copy individual tables. I don't know why anyone would even want to mess around like that. You could truncate super large (GB+) tables before the mysql dump if you think it'll take too long.
adam.
On 2018-02-28 17:41:23, Josh Williams joshwilliams3737@gmail.com wrote:
We just purchased an upgraded server in which to host Observium on and I would like to know the “best” way to migrate over all of our monitored devices. I’m not concerned with any of the graphed data being migrated, or any of the old Observium config. I only want to do a mass export of all of the devices and their properties. Will a dump of the ‘devices’ and ‘devices_locations’ tables suffice? Are there other tables/directories/configs I need to be concerned about?
Thanks,
Josh Williams
Bureau of Technology Management
WI Department of Corrections
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi -bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (3)
-
Adam Armstrong -
Adam Armstrong -
Josh Williams