<![CDATA[Migrating to a new server - can I take existing data?]]>If I want to move to a new server - both old and new are using NetXMS and Postgres - what are my options?

From the doco - there are options if the new DB is local and old DB is local and is connected to existing installation.
https://wiki.netxms.org/wiki/How_to_migrate_to_another_database

I know I can do export import of templates etc, but what about collected data - how do I transfer that across?

]]>https://forum.netxms.org/topic/5972/migrating-to-a-new-server-can-i-take-existing-dataRSS for NodeFri, 13 Nov 2026 20:48:17 GMTSun, 02 Jun 2019 07:10:40 GMT60<![CDATA[Reply to Migrating to a new server - can I take existing data? on Sat, 15 Jun 2019 02:01:38 GMT]]>Went with export / import. 1.4GB export file took about an hour to import - VM built as 4 core 12GB E2680 V4 CPU with all Flash storage - everything was local (iscsi to SAN). Included collected data.

Panicked when I started the console locally and pointed it at the new server - error.:(  Helps to start the NetXMS service first 🙂

Everything was perfect - the only thing I had to do in addition to the import was to copy the MIBS across.

]]>https://forum.netxms.org/post/25963https://forum.netxms.org/post/25963Sat, 15 Jun 2019 02:01:38 GMT<![CDATA[Reply to Migrating to a new server - can I take existing data? on Tue, 11 Jun 2019 10:42:25 GMT]]>Yes, export - copy - import  is another option. It may not work well on large databases though (because of space requirements, extra time to write export file, and on some systems hitting file size limit).

Best regards,
Victor

]]>https://forum.netxms.org/post/25926https://forum.netxms.org/post/25926Tue, 11 Jun 2019 10:42:25 GMT<![CDATA[Reply to Migrating to a new server - can I take existing data? on Sun, 09 Jun 2019 18:27:38 GMT]]>I assume that as an Option 2, I would be to do an export on the original server and do an import on the new server?

An extra step that might be seen as avoidable - but sometimes, getting a file from one server to another can be much simpler and quicker this way.

I have export working, so rather than opening up external connections - copying the SQLite export and importing is looking much easier.

]]>https://forum.netxms.org/post/25900https://forum.netxms.org/post/25900Sun, 09 Jun 2019 18:27:38 GMT<![CDATA[Reply to Migrating to a new server - can I take existing data? on Mon, 03 Jun 2019 16:29:59 GMT]]>In source config on new machine specify address of old server in DBServer. You may need to enable Postgres connections from new machine in pg_hba.conf on old machine.

Best regards,
Victor

]]>https://forum.netxms.org/post/25851https://forum.netxms.org/post/25851Mon, 03 Jun 2019 16:29:59 GMT<![CDATA[Reply to Migrating to a new server - can I take existing data? on Mon, 03 Jun 2019 14:51:51 GMT]]>Hi Victor - thanks for that.

The only trick is that I have POSTGRES on old machine and POSTGRES on new machine - both installed locally.

Running on the new machine - how would I do that?

]]>https://forum.netxms.org/post/25849https://forum.netxms.org/post/25849Mon, 03 Jun 2019 14:51:51 GMT<![CDATA[Reply to Migrating to a new server - can I take existing data? on Mon, 03 Jun 2019 07:32:18 GMT]]>Hi,

it is not necessary that both databases are local for nxdbmgr migrate - both just should be accessible from the machine where you running migration tool. Usually it's better to run migration on destination (new machine) - then you can create correct netxmsd.conf for use by new server, copy netxmsd.conf from old server under different name or path, change it so that DBServer points to old database server, and run nxdbmgr migrate.

Best regards,
Victor

]]>https://forum.netxms.org/post/25844https://forum.netxms.org/post/25844Mon, 03 Jun 2019 07:32:18 GMT