Table of Contents |
---|
...
Code Block |
---|
/usr/local/nmis9/bin/nmis-cli act=fixperms |
Model Files
We can move all the model customisations in the models-custom directory. We can use rsync for this again.
NOTE Some models may need to be adjusted. Specially if they are using nmis internal functions.
Plugins
We have moved the conf/plugins directory using rsync. But the custom plugins need to be adapted to NMIS9.
Here you can find further information.
Step 6. Copy RRDs
Step 7: Verify
...
- The destination server is a brand new server with nmis9 installed.
- nmis9 has been running for a couple of cycles to create the inventory. Then, it should be stopped.
- We would need the last installers from all the products in the /tmp directory.
Step 1.
...
We can use rsync for this:
...
Installers running
Run the installers for each application. All the data should be automatically migrated.
Step 2. Customise configuration
Same steps as the other procedure.
Step 3. opConfig data
Run the migration script:
Code Block |
---|
/usr/local/omk/bin/opconfig-cli.pl act=migrate-nodes debug=9 |
Step 4. opReports data
Same steps as the other procedure.
Step 5. opCharts data
Run the migration script:
Code Block |
---|
/usr/local/omk/bin/opcharts-cli.exe act=migrate-monitored-services dir=/usr/local/nmis8/var/service_status debug=1 |
Notes
- It is important to update nmis 9 first and leave running for a couple of poll cycles so inventory is created. nmis9 will create its own inventory, as this is now saved in the db and has a specific format. These data will be used for other scripts from the apps to migrate some data.
- opconfig and opevents share the same database in the old version. This is because the products database name should be changed to "nmis", the old database name.
- nmis8 didn't use mongo. This is because opConfig has its own nodes database. We don't want to replicate information, so now opConfig will use nmisng database to get the nodes information. We would need to use the opConfig migration script to porte some specific configurations from the internal database to nmis.