...
- The node_admin tool now supports more complete snapshotting of nodes (with
act=dump), which optionally includes the node's RRD files, events and other historic records.
When importing a thusly dumped node withact=importit is now possible to have all identifiers localised to the current system (withlocalise_ids=true); this causes the imported node to be 'adopted' by and become active on the current NMIS system immediately.
This mechanism allows a node to be moved completely between NMIS systems, without losing any of the node's history.
Dumping a Node
...
Backup, Migrate or just play with a Node
Simple node export and import are described above, however, with NMIS9 you can backup a node and perform node migrations using the node_admin.pl tool, the functions to do this are dump and restore.
Dump (or Backup) a Node
Using the node_admin.pl tool you can dump a node including all database records and RRD files into a ZIP file.
| Code Block |
|---|
/usr/local/nmis9/admin/node_admin.pl node=NODENAME act=dump everything=1 file=/tmp/NODENAME-dump.zip |
This file would represent a backup of that node at this time. The file can then be used on another server to restore or could be used to restore the node on the same server.
Restoring a Node
To restore a node to the same poller you would not need to localise_ids option, if you wanted to copy/migrate the node to another server you would need to localise the ids so that the poller thinks it the node belongs to it.
| Code Block |
|---|
/usr/local/nmis9/admin/node_admin.pl act=restore file=NODENAME-dump.zip localise_ids=1 |
Caveats: you can not restore a node to a server if there is already a node existing with that name, you should rename the node before dumping. This would include if the server was acting as a master and receiving the node from a remote poller.